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


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

gvSIG Team: Análisis hidrológico para localizar materiales o yacimientos arqueológicos. SIG aplicados a Arqueología

OSGeo Planet - Mon, 2019-01-28 09:59

En este penúltimo módulo del curso de SIG aplicado a arqueología, veremos como a partir de un Modelo Digital de Terreno (MDT) podemos realizar varios análisis hidrológicos que nos servirán para localizar material arqueológico.

Si aún no has realizado los ejercicios anteriores, te recomendamos que empieces por el primer módulo.

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.

Tema 6. 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

Categories: OSGeo Planet

GeoServer Team: GeoServer 2.15-RC Released

OSGeo Planet - Mon, 2019-01-28 09:54

We are happy to share a GeoServer 2.15-RC milestone release with downloads (zip|war|exe), documentation (html|pdf) and extensions.

This release candidate is provided for everyone considering a Java 11 operational environment in 2019.  A release candidate provides a final to support the development team with early feedback:  your assistance and participation is requested!

This release is a result of participation in the OSGeo Java 2018 Code Sprint and is made in conjunction with GeoTools 21-RC and GeoWebCache 1.15-RC. We would like to thank organizations participating in the code sprint (Boundless, GeoSolutions, GeoCatAstun TechnologyCCRi) along with sprint sponsors (Gaia3Datol, osgeo:uk, Astun Technology). Our gratitude goes out to the individuals who worked so hard to bring everything together.


In addition to Java 11 support this release includes:

  • JAI-EXT enabled by default, in other words, support for NODATA pixels on by default
  • Add JSON as a Legend Output format (GISP 173)
  • Printing plugin upgrade version of JTS
  • SLDService become an official extension, with a number of improvements in it SLDService (classification of raster data too, equal area classification, standard deviation filtering)
  • Allow configuring services on a per layer basis
  • GeoFence upgraded from community module to official extension
  • WPS “GetExecutions” vendor operation allows each user to get the list of running processes (limited to his account for normal users, showing all processes if the request is made by an admin)
  • Autocomplete support for SLD 1.0 in style editor
  • Improvements for vector tile production, both in terms of output correctness and production performance
  • Upgrade NetCDF dependencies
  • QA work adding PMD and ErrorProne checks in the build
  • and a large number of bug fixes.
Java 11 Support

The provided binary download works with either Java 8 or Java 11. Tomcat 9 or newer is required for the WAR install.

We will the update the user guide compatibility list based on your feedback and testing of this 2.15-RC milestone release. Please note that Java 11 no longer supports the Java 2 extension mechanism used for native JAI and native ImageIO.

This is a good opportunity to review your operational environment and help test GeoServer with the environment you intend to use in 2019.

Java Roadmap Considerations

Our initial concerns with respect to continued availability of the Java 8 platform have been alleviated by industry action and commitment. Extensive Java 8 support options are now available, with RedHat making a public commitment to contribute fixes to the OpenJDK 8 codebase, and a range of organizations committed to making OpenJDK 8 builds available on a range of platforms.

Oracle has changed to a six month release schedule, donating additional components to OpenJDK to make it lead platform. Long term support (beyond six months) is being offered from a range of organizations notably RedHat OpenJDK  and Adopt OpenJDK.

The net effect of these changes:

  • If you have been using Oracle JDK up until now it is time to review your options
  • Java 8 will continue to be available
  • The Java ecosystem is now led by the open-source Open JDK project

See the GeoTools user guide for a table outlining the Java 8 and Java 11 alternatives to consider in the year ahead.

About GeoServer 2.15 Series

Additional information on the GeoServer 2.15 series:

Categories: OSGeo Planet

GeoTools Team: GeoTools 21-RC release ready for testing

OSGeo Planet - Mon, 2019-01-28 09:25
GeoTools project is closing out 2018 with a GeoTools 21-RC milestone release featuring Java 11 compatibility: geotools-21-RC-bin.zip geotools-21-RC-doc.zip geotools-21-RC-userguide.zip geotools-21-RC-project.zip maven repository This release candidate is a preview of GeoTools 21 giving everyone a chance to help test Java 11 compatibility. Highligths: Works with Java 11 Features JAI-EXT
Categories: OSGeo Planet

Markus Neteler: Call for testing: GRASS GIS with Python 3

OSGeo Planet - Sun, 2019-01-27 23:32

Please help us testing the Python3 support in the yet unreleased GRASS GIS trunk (i.e., version “grass77” which will be released as “grass78” in the near future).

1. Why Python 3?

Python 2 is end-of-life (EOL); the current Python 2.7 will retire in 11 months from today (see https://pythonclock.org). We want to follow the “Moving to require Python 3” and complete the change to Python 3. And we need a broader community testing.

2. Download and test!

Packages are available at time:

3. Instructions for testing 4. Problems found? Please report them to us

Problems and bugs can be reported in the GRASS GIS trac. Code changes are welcome!

Thanks for testing grass77!

The post Call for testing: GRASS GIS with Python 3 appeared first on GFOSS Blog | GRASS GIS and OSGeo News.

Categories: OSGeo Planet

Free and Open Source GIS Ramblings: Dealing with delayed measurements in (Geo)Pandas

OSGeo Planet - Sun, 2019-01-27 17:26

Yesterday, I learned about a cool use case in data-driven agriculture that requires dealing with delayed measurements. As Bert mentions, for example, potatoes end up in the machines and are counted a few seconds after they’re actually taken out of the ground:

Yield mapping in agriculture, there's a delay of ~10 – 15 seconds in data logging between intake of potato and the measurement which is at the 'end' of the processing in the machine, during which the machine drives forward. pic.twitter.com/Bo60oUIH2e

— Bert Rijk (@BertRijk) January 26, 2019

Therefore, in order to accurately map yield, we need to take this temporal offset into account.

We need to make sure that time and location stay untouched, but need to shift the potato count value. To support this use case, I’ve implemented apply_offset_seconds() for trajectories in movingpandas:

def apply_offset_seconds(self, column, offset): self.df[column] = self.df[column].shift(offset, freq='1s')

The following test illustrates its use: you can see how the value column is shifted by 120 second. Geometry and time remain unchanged but the value column is shifted accordingly. In this test, we look at the row with index 2 which we access using iloc[2]:

def test_offset_seconds(self): df = pd.DataFrame([ {'geometry': Point(0, 0), 't': datetime(2018, 1, 1, 12, 0, 0), 'value': 1}, {'geometry': Point(-6, 10), 't': datetime(2018, 1, 1, 12, 1, 0), 'value': 2}, {'geometry': Point(6, 6), 't': datetime(2018, 1, 1, 12, 2, 0), 'value': 3}, {'geometry': Point(6, 12), 't': datetime(2018, 1, 1, 12, 3, 0), 'value':4}, {'geometry': Point(6, 18), 't': datetime(2018, 1, 1, 12, 4, 0), 'value':5} ]).set_index('t') geo_df = GeoDataFrame(df, crs={'init': '31256'}) traj = Trajectory(1, geo_df) traj.apply_offset_seconds('value', -120) self.assertEqual(traj.df.iloc[2].value, 5) self.assertEqual(traj.df.iloc[2].geometry, Point(6, 6))
Categories: OSGeo Planet

GIScussions: Entryism in Open Communities

OSGeo Planet - Sun, 2019-01-27 17:18

If you are a follower of the OpenStreetMap Foundation mailing list you may recall that there was a flurry of concern in late November 2018 regarding 100 new members, all of whom worked for the Indian data factory GlobalLogic. The new members had all signed up in a relatively short time period just prior to the cutoff point for new members to vote in the annual OSMF Board Elections and understandably some people thought that this influx of new members might signify an intent by GlobalLogic to influence the outcome of the election (readers in the UK and US may be hearing an echo at this point).

It turned out that the new members had misread the cutoff conditions and had in fact missed the cutoff by a few hours so no influence was exerted on the elections.

Entryism (also referred to as entrism or enterism, or as infiltration) is a political strategy in which an organisation or state encourages its members or supporters to join another, usually larger, organisation in an attempt to expand influence and expand their ideas and program. In situations where the organization being “entered” is hostile to entrism, the entrists may engage in a degree of subterfuge and subversion to hide the fact that they are an organisation in their own right.


Subsequently the Membership Working Group of OSM undertook a detailed study of what had happened and what conclusions might be drawn. This was a careful and moderate response to the incident that proposed a series of recommendations for further discussion.

I follow two open communities OSGeo and OSM, I’m less active in OSM nowadays, and there has always been a concern within these communities about retaining a defence against “bad actors”, particularly businesses trying to influence or take over the foundation of the community. I’m not suggesting that GlobalLogic were a “bad actor” – you should read the MWG report and form your own judgement.

Both the OSGeo Foundation and the OpenStreetMap Foundation restrict membership to individuals as a protection against a corporate takeover. I must admit that until now I had always considered the concern about corporate takeover to be a bit paranoiac and unlikely, in my opinion there is something of a thread of anti corporatism in both OSM and OSGeo. Now I am wondering whether I was wrong about attempts at a takeover.

So could what happened in the OSM last year also happen to OSGeo? The membership models are different:

  • In OSM anyone can become a member of the OSMF by signing up and paying an annual fee of £15, there has been talk about reducing this fee for people from low income countries. There is no requirement to be an active mapper or even to be an occasional mapper.
  • OSGeo membership is described as Charter Membership and members have to be proposed, seconded and previously voted on by the existing Charter Members. Charter Membership is seen as a recognition of past contributions to the OSGeo community and projects. There is no membership fee.

In the past OSGeo held annual elections for Charter Membership, there were a fixed number of places and those candidates who got the most votes were elected i.e. not everyone who was proposed and seconded was elected. In 2014 this process was changed (with limited discussion in my recollection) to remove the cap on numbers elected by allowing all candidates who receive more ‘for’ votes than ‘against’ and at least 5% of the electorate to be elected. In 2016 the process was further amended to not require a vote, if you are proposed and seconded and not vetoed (a Charter Member can veto a candidate privately) you are elected. Charter Membership has grown quite rapidly (420+ CMs after 2018 elections) and the diversity of membership has been extended as one no longer needs high profile amongst active community members to be elected in a competitive vote. This is almost certainly a good change within OSGeo.

The new Charter Membership election process does potentially open membership up to manipulation as there is limited scrutiny of proposed members and most people are, quite rightly, reluctant or cautious about using their veto. It hasn’t happened, it’s unlikely to happen but the experience of the OSM community last year suggests that what I thought was paranoia could be sensible prudence. This matters because Charter Members elect the board of OSGeo and the board can change policies and processes and after electing the board the membership has no mechanism (apart from the next board election) to overturn decisions of the board.

I think that growing Charter Membership makes it more difficult for entryism to occur but I’m not sure.

What is clear to me now is that as OSM and OSGeo have become more established and mainstream with substantial commercial entities embedded within their ecospheres the potential for conflicts of interest is likely to grow. It may be time to revisit the articles of association to ensure that we have adequate protections. Perhaps this is something that OSGeo should be discussing?

Categories: OSGeo Planet

Gary Sherman: Leaflet Day 5 - Working with Features

OSGeo Planet - Sun, 2019-01-27 14:19
Today we’ll add towns along the trail route that are mentioned in the novels. I hesitate to call them towns, because in 1902, many of them consisted of a view indigenous people and sometimes a roadhouse. The method to add these locations will be to add a GeoJSON layer and loop through each town, adding a marker and popup with some info. The Data The data for the locations is from the GNIS database for Alaska, containing over 35,000 locations.
Categories: OSGeo Planet

Free and Open Source GIS Ramblings: Movement data in GIS #19: splitting trajectories by date

OSGeo Planet - Sat, 2019-01-26 15:58

Many current movement data sources provide more or less continuous streams of object locations. For example, the AIS system provides continuous locations of vessels (mostly ships). This continuous stream of locations – let’s call it track – starts when we first record the vessel and ends with the last record. This start and end does not necessarily coincide with the start or end of a vessel voyage from one port to another. The stream start and end do not have any particular meaning. Instead, if we want to see what’s going on, we need to split the track into meaningful segments. One such segmentation – albeit a simple one – is to split tracks by day. This segmentation assumes that day/night changes affect the movement of our observed object. For many types of objects – those who mostly stay still during the night – this will work reasonably well.

For example, the following screenshot shows raw data of one particular vessel in the Boston region. By default, QGIS provides a Points to Path to convert points to lines. This tool takes one “group by” and one “order by” field. Therefore, if we want one trajectory per ship per day, we’d first have to create a new field that combines ship ID and day so that we can use this combination as a “group by” field. Additionally, the resulting lines loose all temporal information.

To simplify this workflow, Trajectools now provides a new algorithm that creates day trajectories and outputs LinestringM features. Using the Day trajectories from point layer tool, we can immediately see that our vessel of interest has been active for three consecutive days: entering our observation area on Nov 5th, moving to Boston where it stayed over night, then moving south to Weymouth on the next day, and leaving on the 7th.

Since the resulting trajectories are LinestringM features with time information stored in the M value, we can also visualize the speed of movement (as discussed in part #2 of this series):

Categories: OSGeo Planet

Gary Sherman: Leaflet Day 4 - Basemaps and Overlays

OSGeo Planet - Sat, 2019-01-26 00:00
Today we’ll add some basemaps and a couple of controls to our map. So far we’ve been using OpenStreetMap as our back drop. There are a couple of tile servers that will give us a little more of a “back in the day” look. We’ll also add attribution to the map so we give credit where credit is due, as well as a scale bar. Complete code for the map can be viewed at the bottom of this post.
Categories: OSGeo Planet

Gary Sherman: Leaflet Day 3 - The Trail

OSGeo Planet - Fri, 2019-01-25 18:03
Background In 1902 the only way from the port of Valdez to the Fortymile gold fields was a nearly 400 mile trail through the Alaska wilderness. The Valdez-Eagle trail plays a key role in novels two and three. Adding the Trail to a Leaflet Map To add the trail to our map, we will convert it from a shapefile to GeoJSON. There is more than one way to do this—you could use ogr2ogr, but we chose to use QGIS, since it would not only convert it, but transform the coordinate system at the same time.
Categories: OSGeo Planet

GIS for Thought: OpenStreetMap Ireland 2018 Visualized

OSGeo Planet - Thu, 2019-01-24 15:35

2018 was a very productive year for OpenStreetMap in Ireland.

Around 70k nodes added, 60k ways added, and 160k polygons added.

Finally a company was formed to facilitate becoming a fully fledged local chapter.

What does that look like day to day:

Categories: OSGeo Planet

Gary Sherman: Leaflet Day 2 - Adding a Marker

OSGeo Planet - Thu, 2019-01-24 15:13
I’m starting off slow, so today we’ll add a marker with some extra features. Since the map from yesterday is already centered on the big earthquake, lets add a marker there. Adding a Marker To create a marker, Leaflet uses the L.marker class: var earthquakeMarker = L.marker([61.346, -149.955]); This creates the marker, but it needs to be added to the map: earthquakeMarker.addTo(map); This gives us: Good so far, but looking at the map tells us nothing about the marker.
Categories: OSGeo Planet

FOSS4G 2019 Bucharest: Open Call for Contributions FOSS4G 2019 Bucharest!

OSGeo Planet - Thu, 2019-01-24 12:43


We kindly invite you to come and share your ideas, projects, struggles and accomplishments at the biggest geospatial gathering of the year. You can contribute to the FOSS4G 2019 program by submitting one or more of the classic contributions: a workshop, a talk, an academic paper.

By virtue of the wonderful FOSS4G 2019 Bucharest venue, we are happy to announce that we will accept an approximate number of 300 talks, 40 workshops and 25 academic papers!
The topics envisaged for FOSS4G 2019 follow the lines of the most recent developments in our domain. Thus, the FOSS4G 2019 program will be shaped and coloured in the 6 general topics, unfolding in 10 main themes:


  • Software development;
  • Transition to FOSS4G;
  • Use cases & applications;
  • Education & research;
  • Digital economy;
  • Open data.


  • Software status, new project development;
  • Standards, interoperability, SDIs, INSPIRE implementations;
  • FOSS4G implementations in strategic application domains (land management, crisis/disaster response, smart cities, population mapping, climate change, ocean and marine monitoring etc.);
  • Analysis, manipulation and visualization of geospatial data;
  • Data collection, data sharing, big data, data exploitation platforms;
  • Sensors, remote sensing, laser-scanning, structure from motion;
  • New trends: IoT, Indoor mapping, machine learning, drones;
  • Community & participatory FOSS4G;
  • FOSS4G in education;
  • Business products powered by FOSS4G.

Do visit the dedicated pages for all necessary details for each of the three types of contributions: talks, workshops and academic papers and pay special attention to the deadlines as they are distinct!

Categories: OSGeo Planet

Gary Sherman: Two Weeks of Leaflet - Day 1

OSGeo Planet - Wed, 2019-01-23 21:52
Background We at Locate Press have been working on a new book: Leaflet Cookbook, by Numa Gremling. The book is chock-full of over 300 pages of recipes and information to get the most of your web maps. The book is content complete and available as a preview. I’ve dabbled in Leaflet in the past, but only scratched the surface. So, I’ve decided to spend two weeks starting from the ground up and create a decent web map.
Categories: OSGeo Planet

Gary Sherman: Two Weeks of Leaflet - Day 1

OSGeo Planet - Wed, 2019-01-23 21:52
Background We at Locate Press have been working on a new book: Leaflet Cookbook, by Numa Gremling. The book is chock-full of over 300 pages of recipes and information to get the most of your web maps. The book is content complete and available as a preview. I’ve dabbled in Leaflet in the past, but only scratched the surface. So, I’ve decided to spend two weeks starting from the ground up and create a decent web map.
Categories: OSGeo Planet
Syndicate content