OSGeo Planet

Gary Sherman: Leaflet Day 9 - Calculating Distance with Turf.js

OSGeo Planet - Mon, 2019-02-04 17:02
Today we’re going to use Turf.js to calculate the distance between any two points along the trail. Turf.js is billed as providing “Advanced geospatial analysis for browsers and Node.js.” The distance calculated is a straight line (“as the crow flies”) distance rather than actual trail miles. Including Turf.js To calculate the distance we need to include Turf.js. Rather than install it locally, just add this line to the head of your HTML:
Categories: OSGeo Planet

gvSIG Team: The 4th gvSIG Festival is coming

OSGeo Planet - Mon, 2019-02-04 16:26

For the fourth year running we launch the 4th gvSIG Festival, the online conference in which anyone in the world with an Internet connection can attend or participate as a speaker. The event will be held in March 27th and 28th 2019.

This year we want to make a special appeal to the group of women who are part of the gvSIG Community. We would like that a large percentage of the presentations of this 4th Festival are given by you, so we encourage you to present your proposals.

In the gvSIG project we have always wanted to work and contribute our bit in the fight against gender discrimination. In internal debates we have always taken into account that within a movement such as open source software, and the values associated to it, the obvious absence of women should be worrying. And maybe it’s the biggest problem. That should be worrying and it is not.

The sector of open source geomatics, and gvSIG, do not escape these dynamics either. Even significant progress, there’s an obvious absence of women in our collective. And the worst thing, we not only find that there are only a few initiatives that allow to create spaces to favour their integration, but it seems that it is not necessary.

And even if it’s only a little that we can contribute, we would like to start working on this small step to help to reverse this situation.

gvSIG festivals are open to any presentation related to the project, from anywhere in the world and in any language. From now on, we start the path to the next ‘4th gvSIG Festival’.

The information about the proposals submission can be found on the event website: www.gvsig.com/festival

Categories: OSGeo Planet

gvSIG Team: Llega el 4º gvSIG Festival

OSGeo Planet - Mon, 2019-02-04 16:15

Por cuarto año consecutivo lanzamos el 4º gvSIG Festival, las jornadas on-line en las que cualquier persona del mundo con conexión a internet puede asistir o participar como ponente. La fecha, 27 y 28 de marzo de 2019.

Este año queremos hacer un llamamiento especial al colectivo de mujeres que forman parte de la Comunidad gvSIG. Nos gustaría que un gran porcentaje de las ponencias de este 4º Festival fuera impartido por vosotras, por lo que os animamos a presentar vuestras propuestas.

En el proyecto gvSIG siempre hemos querido trabajar y aportar nuestro granito de arena en la lucha contra la discriminación de género. En debates internos siempre hemos considerado que dentro de un movimiento como el del software libre, y los valores que a él asociamos, la ausencia manifiesta de mujeres debería resultarnos preocupante. Y quizá ese es el mayor de los problemas. Que debería ser preocupante y no lo es.

El sector de la geomática libre, y gvSIG, tampoco escapan a estas dinámicas. Aún con significativos avances, hay una ausencia preocupante de mujeres en nuestro colectivo. Y lo que es peor, no sólo encontramos que casi no existen iniciativas que sirvan para crear espacios que favorezcan su integración, sino que no se ve necesario.

Y aunque sólo sea un poco lo que podamos aportar, nos gustaría comenzar a trabajar dando este pequeño paso para ayudar a revertir esta situación.

Los Festivales gvSIG están abiertos a cualquier ponencia relacionada con el proyecto, desde cualquier parte del mundo y en cualquier idioma. Desde ya, damos por iniciado el camino al próximo ‘4º gvSIG Festival’.

La información para el envío de propuestas la podéis encontrar en la web del evento: www.gvsig.com/festival

Categories: OSGeo Planet

Markus Neteler: Happy birthday OSGeo!

OSGeo Planet - Mon, 2019-02-04 14:05

On February 4, 2006 OSGeo held its first meeting in Chicago, with 25 participants representing 18 groups and over 20 different Open Source GIS projects, and 39 others participating via Internet Relay Chat. During the meeting, participants made important decisions in the formation and organization of the foundation, including the name, structure and purpose. The consensus reached in Chicago opened the way for the establishment of a productive and representative foundation.

Today we are happy to announce that the we have meanwhile over 32,800 unique subscribers in the huge list of over 290 OSGeo mailing lists!

And: check out the web site of the OSGeo foundation.

1. More to come this year!

… see here for the growing list of events

The post Happy birthday OSGeo! appeared first on GFOSS Blog | GRASS GIS and OSGeo News.

Categories: OSGeo Planet

gvSIG Team: Graphical output of an archaeological project: Layouts. GIS applied to Archeology

OSGeo Planet - Mon, 2019-02-04 14:00


We have reached the end of the course about GIS for Archaeologists, where you are going to learn to create a Layout with the different cartographic elements such as scale, north, legend … For this you will start from a View of our GIS with archaeological sites cartography.

For all those who finish the course and want to get a certificate, we will publish a post with the instructions for it soon. Stay alert!

We remind you that the data to follow the course can be downloaded in a compressed .zip file from this link.

Remember that for doubts about software use, carrying out the exercises, and problems that you find when carrying out the course, you can use the gvSIG users mailing list.

We hope that this course is useful for you and that allows you to become a regular gvSIG Desktop user. From our part we will continue working to improve this great collaborative project that allows us to have hundreds of thousands of users in more than 160 countries.

Module 7. Graphical output of an archaeological project: Layouts

Previous modules:

Module 1: Preparation of an archaeological project

Module 2: Digitalizing prospection areas

Module 3: Analysis of prospection results: Vector geoprocessing

Module 4: Working with historical maps: Georeferencing images

Module 5: Territorial analysis of archaeological sites: Raster geoprocessing and Digital Elevation Models

Module 6: Hydrological analysis to locate archaeological material or sites

Categories: OSGeo Planet

Paul Ramsey: Dr. JTS comes to Crunchy

OSGeo Planet - Mon, 2019-02-04 13:00

Today’s an exciting day in the Victoria office of Crunchy Data – our local staff count goes from one to two, as Martin Davis joins the company!

This is kind of a big deal, because this year Martin and I will be spending much or our time on the core computational geometry library that powers PostGIS, the GEOS library, and the JTS library from which it derives its structure.

Why is that a big deal? Because GEOS, JTS and other language ports provide the computational geometry algorithms underneath most of the open source geospatial ecosystem – so improvements in our core libraries ripple out to help a huge swathe of other software.

JTS came first, initially as a project of the British Columbia government. GEOS is a C++ port of JTS. There are also Javascript and .Net ports (JSTS and NTS).

Each of those libraries has developed a rich downline of other libraries and projects that depend on them. On the desktop, on the web, in the middleware, JTS and GEOS power all of it.

So we know that work on JTS and GEOS on our side is going to benefit far more than just PostGIS.

I’ve already spent a decent amount of time on bringing the GEOS library up to date with the changes in JTS over the past few months, and trying to fulfill the “maintainer” role, merging pull requests and closing some outstanding tickets.

As Martin starts adding to JTS, I now feel more confident in my ability to bring those changes into the C++ world of GEOS as they land.

Without pre-judging what will get first priority, topics of overlay robustness, predicate performance, and geometry cleaning are near the top of our list.

Our spatial customers at Crunchy process a lot of geometry, so ensuring that PostGIS (GEOS) operations are robust and high performance is a big win for PostgreSQL and for our customers as well.

Categories: OSGeo Planet

Fernando Quadro: Curso de GeoServer – Turma 15

OSGeo Planet - Mon, 2019-02-04 10:36

Caros leitores,

Quero convidá-los a participarem do Curso Online de GeoServer que estarei ministrando pela GEOCURSOS. O objetivo do curso é que você aprenda a disponibilizar, compartilhar e editar dados geográficos na internet com o GeoServer.

No curso serão abordados tópicos como: configuração de dados, criação de estilo com SLD, padrões OGC, interface administrativa (web), visualização cartográfica com OpenLayers, REST API, Segurança, entre outros.

O curso ocorrerá entre os dias 19 e 28 de março (terças, quartas e quintas) das 20:00 as 22:00 (horário de Brasília).

Aqueles que poderem divulgar para seus contatos, agradeço. Quem quiser saber mais informações sobre o curso, pode obtê-las no site do curso (http://www.geocursos.com.br/geoserver), twitter (http://twitter.com/geo_cursos) e pelo facebook (http://www.facebook.com/geocursosbr).

Categories: OSGeo Planet

gvSIG Team: Salida gráfica de un proyecto arqueológico: Mapas. SIG aplicados a Arqueología

OSGeo Planet - Mon, 2019-02-04 09:23

Llegamos al final del curso de SIG aplicado a arqueología, donde aprenderemos a crear un Mapa con los distintos elementos cartográficos como escala, norte, leyenda…Para ello partiremos de una Vista de nuestro SIG con cartografía de yacimientos.

Para todos los que acabéis el curso y queráis obtener un certificado, en breve publicaremos un post con las instrucciones para ello. ¡Estad atentos!

Os recordamos que los datos para poder seguir el curso los podéis descargar comprimidos en un fichero .zip en este enlace.

Para dudas en el manejo del software, realización de los ejercicios y problemas que puedan surgir en la realización del curso, siempre podéis utilizar la lista de usuarios de gvSIG.

Esperamos que hayáis encontrado útil este curso y os permita convertiros en unos usuarios habituales de gvSIG Desktop. Por nuestra parte seguiremos trabajando para continuar mejorando este gran proyecto colaborativo que permite que tengamos ya cientos de miles de usuarios en más de 160 países.

Tema 7. Análisis hidrológico para localizar materiales o yacimientos arqueológicos

Temas anteriores

Tema 1: Preparación de un proyecto arqueológico: vistas, capas y tablas

Tema 2: Digitalizar zonas de prospecciones

Tema 3: Análisis de resultados de prospecciones: Geoprocesos vectoriales

Tema 4: Trabajando con mapas antiguos: Georreferenciación de imágenes

Tema 5: Análisis territorial de yacimientos: Geoprocesos ráster y Modelos Digitales de Terreno

Tema 6: Análisis hidrológico para localizar materiales o yacimientos arqueológicos

Categories: OSGeo Planet

Free and Open Source GIS Ramblings: Movement data in GIS #20: Trajectools v1 released!

OSGeo Planet - Sat, 2019-02-02 13:57

In previous posts, I already wrote about Trajectools and some of the functionality it provides to QGIS Processing including:

There are also tools to compute heading and speed which I only talked about on Twitter.

Trajectools is now available from the QGIS plugin repository.

The plugin includes sample data from MarineCadastre downloads and the Geolife project.

Under the hood, Trajectools depends on GeoPandas!

If you are on Windows, here’s how to install GeoPandas for OSGeo4W:

  1. OSGeo4W installer: install python3-pip
  2. Environment variables: add GDAL_VERSION = 2.3.2 (or whichever version your OSGeo4W installation currently includes)
  3. OSGeo4W shell: call C:\OSGeo4W64\bin\py3_env.bat
  4. OSGeo4W shell: pip3 install geopandas (this will error at fiona)
  5. From https://www.lfd.uci.edu/~gohlke/pythonlibs/#fiona: download Fiona-1.7.13-cp37-cp37m-win_amd64.whl
  6. OSGeo4W shell: pip3 install path-to-download\Fiona-1.7.13-cp37-cp37m-win_amd64.whl
  7. OSGeo4W shell: pip3 install geopandas
  8. (optionally) From https://www.lfd.uci.edu/~gohlke/pythonlibs/#rtree: download Rtree-0.8.3-cp37-cp37m-win_amd64.whl and pip3 install it

If you want to use this functionality outside of QGIS, head over to my movingpandas project!

Categories: OSGeo Planet

Gary Sherman: Leaflet Day 8 - Zoom to Feature

OSGeo Planet - Fri, 2019-02-01 23:40
In this post we’ll add a zoom button to pan the map to one of the towns in the trail stops layer. Adding a Dropdown Box and Button The first thing to do is add the select element and a button to the HTML: <select id='zoombox'> </select> <input type="button" id="zoomTo" value="Zoom to town"> We’ll populate the options for the select element using the town GeoJSON. Creating a Dictionary and Populating the Select Box Next we loop through the towns in the GeoJSON layer and create a dictionary that maps the town name to its data, then add each as an option to a select element:
Categories: OSGeo Planet

OTB Team: The road to OTB 7

OSGeo Planet - Fri, 2019-02-01 17:11
The lastest OTB release, version 6.6.1, was released more than six months ago! We usually aim for a release every 3 months, so what happened? Let’s take a look. OTB is a large project with many components, modules and dependencies. After more than 10 years of development, we have accumulated a lot of technical debt: […]
Categories: OSGeo Planet

Even Rouault: SRS barn raising: 8th report. Ready for your testing !

OSGeo Planet - Thu, 2019-01-31 20:04
This is the 8th progress report of the GDAL SRS barn effort.
As the title implies, a decisive milestone has now been reached, with the "gdalbarn" branches of libgeotiff and GDAL having been now merged in their respective master branch.
On the PROJ side, a number of fixes and enhancements have been done:- missing documentation for a few functions, the evolution of cs2cs and the new projinfo utility has been added- the parser of the WKT CONCATENATEDOPERATION construct can now understand step presented in a reverse order- a few iterations to update the syntax parsing rules of WKT2:2018 following the latest adjustments done by the OGC WKT Standard Working Group- in my previous work, I had introduced a "PROJ 5" to export CRS using pipeline/unitconvert/axisswap as an attempt of improving the PROJ.4 format used by GDAL and other products. However after discussion with other PROJ developers, we realize that it is likely a dead-end since it is still lossy in many aspects and can cause confusion with coodinate operations. Consequently the PROJ_5 convention will be identical to PROJ_4 for CRS export. And the use of PROJ strings to express CRS themselves is discouraged. It can still makes sense if using the "early-binding" approach and specifying towgs84/nadgrids/geoidgrids parameters. But in a late-binding approach, WKT is much more powerful to capture important information like geodetic datum names.- when examining how the new code I added those past months with the existing PROJ codebase, it became clear that there was a confusion when importing PROJ strings expressing coordinate operations versus PROJ strings expressing a CRS. So for the later use case, a "+type=crs" must be added in the PROJ string. As a consequence the proj_create_from_proj_string() and proj_create_from_user_input() functions have been removed, and proj_create() can now been used for all types of PROJ strings.- The PROJ_LIB environment variable now supports multiple paths, separated by colon on Unix and semi-colon on Windows
On the GDAL side,
  • the OGRCoordinateTransformation now uses the PROJ API to automatically compute the best transformation pipeline, enabling late-binding capabilities. In the case where the user does not provide an explicit area of use and several coordinate operations are possible, the Transform() method can automatically switches between coordinate operations given the input coordinate values. This should offer behaviour similar to previous versions  for example for NAD27 to NAD83 conversion when PROJ had a +nadgrids=@conus,@alaska,@ntv2_0.gsb,@ntv1_can.dat hardcoded rule. This dymanic selection logic has also been moved to PROJ proj_create_crs_to_crs() function. Note that however this might not always lead to the desired results, so specifying a precise area of interest, or even a specific coordinate operation, is preferred when full control is needed.
  • gdalinfo, ogrinfo and gdalsrsinfo now outputs WKT2:2018 by default (can be changed with a command line switch). On the API side, the exportToWKT() method will still export WKT1 by default (can of course be changed). The rationale is that WKT consumers might not be ready yet for WKT2, so this should limit the backward compatibility issues. In the future (couple of years timeframe), this default WKT version might be upgraded when more consumers are WKT2-ready.
  • A RFC 73: Integration of PROJ6 for WKT2, late binding capabilities, time-support and unified CRS database document was created to document all the GDAL changes. After discussion with the community, this RFC has been approved
  • As a result, all of the above mentionned work has now been merged in GDAL master
  • Important practical discussion: GDAL master now depends on PROJ master (and ultimately PROJ 6.0 once it is released)
Consequently, on the pure development front, most of the work has now been completed.  As all those changes done those last months deeply impact SRS related functionnality in GDAL and PROJ, we rely now on your careful testing to spot the inevitable issues that have not yet been detected by their respective automatic regression test suites. The earlier they are detected, the easier they will be fixable, in particular if they impact the API.
Categories: OSGeo Planet

Marco Bernasocchi: You gave us feedback – we give you QField 1.0 RC3

OSGeo Planet - Thu, 2019-01-31 06:51

We are really happy to announce the release a new great milestone in QField’s history, QField 1.0 Release Candidate 3! (Yes, you might have got a glimpse of the broken RC2 if you where very attentive)

Thanks to the great feedback we received since releasing RC1 we were able to fix plenty of issues and add some more goodies.

We would like to invite everybody to install this Release Candidate and help us test it as much as possible so that we can iron out as many bugs as possible before the final release of QField 1.0.

List of fixes since RC1:
• fixed bad synchronization / geopackage files not written) (PR #455)
• fix glitches in portrait mode (PR #423 and #439)
• fix highlighting of points (search and feature selection) (PR #443)
• fix GPS info window overlapping search icon (PR #438)
• redesign of scale bar (PR #438)
• fix crash in feature form (with invalid relations) (PR #440)
• fix date/time field editing (PR #421 and #458)
• fix project not loading the correct map theme (fix #459)
• fix QGS or QGZ does not exist (PR #453)

Unfortunately, due to necessary updates in the SDK we target, we had to drop support for Android 4.4. The minimum Android requirement as of this RC is Android 5.0 (SDK version 21).

In case playstore does not suggest an update to QField Lucendro 0.11.90, the last working version for Android 4.4, we suggest all Android 4.4 users to uninstall QField 1.0 RC 1 (which was broken on android 4.4) and reinstall QField from the store. This way you should get If you don’t use play store, you can find all QField releases under https://qfield.org/releases

You can easily install QField using the playstore (https://qfield.org/get), find out more on the documentation site (https://qfield.org) and report problems to our issues tracking system (https://qfield.org/issues)

QField, like QGIS, is an open source project. Everyone is welcome to contribute to make the product even better – whether it is with financial support, enthusiastic programming, translation and documentation work or visionary ideas.

If you want to help us build a better QField or QGIS, or need any services related to the whole QGIS stack don’t hesitate to contact us.

Categories: OSGeo Planet

Gary Sherman: Leaflet Day 7 - Coordinates

OSGeo Planet - Wed, 2019-01-30 15:39
In this post, we’ll do a couple of things: Clean up the display of coordinate precision in our popups Add the current coordinates to the map as the mouse moves Coordinate Precision Display The current map displays the latitude and longitude with seven decimal places. This is more than we need to see when displaying information about locations: Fixing this is easy to do using the JavaScript function toFixed.
Categories: OSGeo Planet

EOX' blog: Using Python interface of VirES in EOX Jupyter Platform

OSGeo Planet - Tue, 2019-01-29 15:28
This blog post describes the experiences of using the freely available Python- and web-clients to the VirES for Swarm (more information here) interface that provides highly interactive data manipulation and retrieval interface for ESA’s Swarm constellation mission science products (more […]
Categories: OSGeo Planet

GIS for Thought: Mapping Strava Data

OSGeo Planet - Tue, 2019-01-29 09:00

In 2018 we started a running club at work.

I created a quick script to parse the data on Strava to a ShapeFile, which can be easily animated with QGIS.

The script only works with Garmin files, GPX, TCX, and FIT.

Source: https://github.com/HeikkiVesanto/Strava-Garmin-Parser

Example:

Categories: OSGeo Planet

Martin Davis: Hilbert and Morton Curves in JTS

OSGeo Planet - Tue, 2019-01-29 01:14
I just landed a JTS pull request for Hilbert and Morton (Z-order) codes and curves.
Hilbert Curve of level 3Morton Curve of level 3
Apart from pretty pictures of fractals, the goal is to support experimenting with Packed Hilbert R-trees, as an alternative to the current Sort-Tile-Recursive packing strategy (implemented as STRtree in JTS).  STRtrees are heavily used to speed up spatial algorithms inside JTS (and externally as per recent report). So if Hilbert curve-based packing provides better performance that would be a big win.


Categories: OSGeo Planet

Fernando Quadro: OpenStreetMap no apoio ao desastre de Brumadinho

OSGeo Planet - Mon, 2019-01-28 17:56

Na tarde de sexta-feira (25/01), uma barragem de rejeitos de minério de ferro, da mineradora Vale em Brumadinho-MG, se rompeu, deixando dezenas de mortos e centenas de desaparecidos.

Na própria sexta-feira a comunidade OpenStreetMap (OSM) iniciou um esforço colaborativo de mapeamento para montar um mapa base pré-desastre para ajudar a planejar a busca e o resgate das vítimas, bem como na recuperação a longo prazo da cidade de Brumadinho.

Em cerca de 24 horas, a comunidade OpenStreetMap de todo o mundo mapeou toda a área do desastre, e em 48 horas foi mapeada praticamente toda a área atingida pela lama. Tudo que foi mapeado, pode ser impresso para orientar equipes de busca e salvamento, resgate de pessoas, resgate de fauna, delimitação de zona restrita ainda sob risco, cálculo de áreas atingidas, etc.

Os dados estão disponíveis para as organizações que estão trabalhando no local. A delegação de Israel, que veio ao Brasil para auxiliar nos esforços de resgate, e as equipes do Centro de apoio em Brumadinho estão utilizando os mapas do OSM para realizar o planejamento das ações do resgate.

Nesse trabalho, está sendo utilizada o HOT/OSM, plataforma que já foi utilizada no desastre de Mariana, no terremoto do Haiti e outras diversas tragédias ao redor do mundo.


Gostaria de aproveitar a oportunidade de agradecer a todos os voluntários que estão dedicando um pouco do seu tempo para ajudar colaborativamente neste mapeamento, em especial ao amigo Narcélio de Sá, que foi quem relatou as informações acima no seu instagram.

Categories: OSGeo Planet

Gary Sherman: Leaflet Day 6 - GeoPackage Layers

OSGeo Planet - Mon, 2019-01-28 17:01
In this post we’ll switch gears and install Leaflet locally, then add a layer from a GeoPackage file. Installing Leaflet Up until now we’ve been using a hosted version of Leaflet. In other words, each time we load the map, a request is made to fetch the Leaflet CSS and JavaScript. There are a couple of ways to install Leaflet: download it from the website or install with npm. In both cases you’ll need to move leaflet.
Categories: OSGeo Planet

gvSIG Team: Hydrological analysis to locate archaeological material or sites. GIS applied to Archeology

OSGeo Planet - Mon, 2019-01-28 11:02


At this penultimate module of the course about GIS for Archaeologists, you will see how to perform hydrological analysis from a Digital Elevation Model (DEM), that will be able to help to locate archaeological material.

If you haven’t done the previous exercises, we recommend you to start with the first module.

We remind you that the data to follow the course can be downloaded in a compressed .zip file from this link.

Remember that for doubts about software use, carrying out the exercises, and problems that you find when carrying out the course, you can use the gvSIG users mailing list.

Module 6. Hydrological analysis to locate archaeological material or sites

Previous modules:

Module 1: Preparation of an archaeological project

Module 2: Digitalizing prospection areas

Module 3: Analysis of prospection results: Vector geoprocessing

Module 4: Working with historical maps: Georeferencing images

Module 5: Territorial analysis of archaeological sites: Raster geoprocessing and Digital Elevation Models

 

Categories: OSGeo Planet
Syndicate content