Tickets are now on sale for the State of the Map conference 2019 in Heidelberg, Germany. The conference runs from the 21st-23rd September. As always, if you are eager to start, we offer an Early Bird discount, but hurry, as these special prices are only available for a limited time.We have had a large number […]
Tickets are now on sale for the State of the Map conference 2019 in Heidelberg, Germany. The conference runs from the 21st-23rd September. As always, if you are eager to start, we offer an Early Bird discount, but hurry, as these special prices are only available for a limited time. We have had a large number of talks submitted to both the regular and academic tracks, so this year promises to have some really interesting topics. Come and be a part of what should be the biggest SotM to date!
Early bird ticket prices
There are many different tickets on offer, so make sure you select the correct one when ordering.
Regular – €180 (early bird) Regular tickets for €180 are available for individuals.
Community – €75 (early bird) If you are a member of the volunteer OSM community, you can get your SotM ticket for a special discounted price of €75.
Supporter – €700 (early bird) For those businesses who want to help support the SotM but cannot sponsor, we offer the supporter ticket costing €700.
Included in your ticket
Included in your ticket is:
entrance for one person to the social dinner and
use of local public transport in Heidelberg (VRN), so you don’t have to worry about paying for public transport each time you use it.
Additional offers
Alongside the regular tickets, we have some extras to offer.
Additional persons to social dinner – €50 per person If you are bringing more people with you to Heidelberg who are not attending the conference, you can still buy extra tickets for the social dinner. Each one is €50.
Heidelberg Altstadt guided tour – €15 Heidelberg has a very historic city center, and we are pleased to offer a guided tour which will take place in the afternoon of 20th September, costs €15 per person and will last approximately 3 hours.
The State of the Map conference is the annual, international conference of OpenStreetMap, organised by the OpenStreetMap Foundation. The OpenStreetMap Foundation is a not-for-profit organisation, formed in the UK to support the OpenStreetMap Project. It is dedicated to encouraging the growth, development and distribution of free geospatial data for anyone to use and share. The OpenStreetMap Foundation owns and maintains the infrastructure of the OpenStreetMap project. The State of the Map Organising Committee is one of our volunteer Working Groups.
What is OpenStreetMap OpenStreetMap was founded in 2004 and is a international project to create a free map of the world. To do so, we, thousands of volunteers, collect data about roads, railways, rivers, forests, buildings and a lot more worldwide. Our map data can be downloaded for free by everyone and used for any purpose – including commercial usage. It is possible to produce your own maps which highlight certain features, to calculate routes etc. OpenStreetMap is increasingly used when one needs maps which can be very quickly, or easily, updated.
Here is a small evidence of why one should rather avoid mapping “individual” dunes:
they’re usually moving.
Sometimes they may even move across the oceans…
Below is what I could roughly, localy measure, with help from Sentinel & Landsat.
Saharan dunes - Adrar, Algeria
♦
Direction of movement: SW ~200m / 30years
There where the wind turns the corner, at www.osm.org
Here is a small evidence of why one should rather avoid mapping “individual” dunes:
they’re usually moving.
Sometimes they may even move across the oceans…
Below is what I could roughly, localy measure, with help from Sentinel & Landsat.
I have been testing precision localization for a few years now using RTK, PPP calculations, and RTKLIB.
Since a few weeks, I have my own GNSS base, which allows me to generate gpx traces with an accuracy of a few centimeters, or a few tens of centimeters.
Here is an example of about 15 overlapped gpx traces:
♦
I think I’m not the only one interested in high-precision localization, and th
I have been testing precision localization for a few years now using RTK, PPP calculations, and RTKLIB.
Since a few weeks, I have my own GNSS base, which allows me to generate gpx traces with an accuracy of a few centimeters, or a few tens of centimeters.
Here is an example of about 15 overlapped gpx traces:
I think I’m not the only one interested in high-precision localization, and the arrival of smartphones with dual-frequency gnss receivers will probably accelerate the movement, which is a great thing for OpenStreetMap.
Of course, I send these traces to the Osm servers, and they are available for everyone.
The problem is that theses gpx are mixed with the others, look at this:
At this time, I don’t know how contributors can know that they are of better quality, I don’t know how to “enhance” them.
How could we do that?
The GPX format does not store information on point accuracy, but allows you to add private namespaces. However, everyone must use the same one. I don’t think it’s a good idea.
On the developers’ discussion list, there was mention of a version 2 of the gpx format, but the last message was almost a year ago.
The files generated with Rtklib are .pos files that include all the necessary information. Could the database handle this format?
One last point:
- by default, the coordinates of the gpx files must be in the WGS84 system. The problem is that Osm data is not necessarily in this system, but rather in the datum used locally. In France, it is the RGF93, which is derived from the European ETRS89 datum. I think that all European data are in ETRS89 and not in WGS84. There is currently a gap of about 70cm between ETRS89 and WGS84, and this is gradually increasing.
So, the GPX traces I send to the Osm servers are not in WGS84, but in ETRS89. I do not respect the GPX standard. I think it should be possible to specify in the gpx files the used datum.
Today I finally sat down and spun off generate_tiles.py to its own repository,
so people can follow its development without having to clone my own osm-carto
fork. This happened just after I finished making the storage thread optional,
because I usualy have as many rendering threads as cores I have, so that extra
thread was not only compiting with them, but also it spent some time
de
Today I finally sat down and spun off generate_tiles.py to its own repository,
so people can follow its development without having to clone my own osm-carto
fork. This happened just after I finished making the storage thread optional,
because I usualy have as many rendering threads as cores I have, so that extra
thread was not only compiting with them, but also it spent some time
de/marshaling the metatiles between processes, so I'm not sure it's worth it.
Maybe if I had more cores?
The new repo is here. There are
some other tools there (hence the tools in the repo's name), but they're not so
polished or documented. You're free to look and ask :)
What if I do a release, I hear (it must be the voice in my head)? Why not! I even
decided to go bold and tagged it as
v1.0.
OpenStreetMap Blogs
Direction of movement: SW ~200m / 30years
Direction of movement: WSW ~200m / 6years
At this time, I don’t know how contributors can know that they are of better quality, I don’t know how to “enhance” them.