OpenStreetMap
Hi all,
Just a quick heads up that MapComplete 0.14 is deployed!
Apart from lots of fixed bugs and performance improvements, a new theme showing OpenStreetMap notes has landed! Especially the filter functionality should come in handy
And of course, there are plenty of (new) themes, such as the street lighting theme (thanks Robin!) or the postboxes and -offices map (by nicolelaine).
And -by now- over 1000 individual contributors have used MapComplete.
Hi everyone,
A new version of MapComplete has been deployed. It has a lot of exciting new themes and features, which I’d like to highlight in this diary entry.
The Flemish touristical agency (Toerisme Vlaanderen) has asked me to create a tool to help them to map charging stations, restaurants, café’s, …
This has resulted in quite some fun new themes:
At last, the theme I’ve quickly made as demo with hackerspaces and makerspaces is online as well.
At the same time, I’ve been doing lots of work on improving performance. A lot has changed under the hood, resulting in a way more robust and fast experience. On high zoom levels, the OSM-API is used directly, bypassing overpass all together. If overpass-api.de is down, failover to other instances is now builtin. At last, caching is a bit more aggressive and if the data on your machine is recent, no new data is loaded at all.
Earlier releases had some important features to, which I’d like to highlight as they can be important for theme builders:
A bit over a year ago, I received a phone call: We would like to have some project about nature and forests, where people can like go out and add data about those. Oh, it has to be really simple to use.
Some months and some funding later, the first version of MapComplete was born. While it had a specific focus then, it has grown a lot. Today, MapComplete is a map viewer for a certain theme, where the configuration for that theme decides what features are visible with which icons. When a map feature is clicked, known information is shown and the user is invited to add more information and to add pictures.
By now, there are about 20 themes for multiple topics, such as bicycle shops and pumps, playgrounds, public bookcases and much more. And it is relatively easy to create and load your own theme.
The ease of use and flexibility has lead to a steady increase of contributors that way. Thursday 15th of april was the day the editor saw its 500’th contributor:
Hello everyone,
As a coach for the Open Summer of Code in Belgium, I thought the community would be interested in reading a little about it and get inspired - along with reading how many of the teams used a map and specifically OSM.
If you have never heard about the Open Summer of Code yet, it is an awesome project. Students create an open source or open data application which a real client needs. The client -often, but not always a governmental organization- sponsors the students. During the four week program, the students get relevant workshops, gain lots of experience, have lots of networking opportunities and are exposed to other Open Source projects and ideas. This all is organized by Open Knowledge Belgium, a small but amazing organisation which furthers the use of open data in Belgium.
This year 73 (!) students participated, along with 17 coaches, making this eight edition bigger then ever. Furthermore, oSoc has been more international then ever, with lots of international students and projects and having a spinoff in Spain. This first Spanish edition had 10 students whom enjoyed it a lot. In other words, don’t hesitate to contact us. Wherever you are, you are welcome as student, coach, client of partner organization or perhaps even as organizer of your own edition.
For me personally, it was the first I participated to oSoc. I had the honor of coaching two teams, quite a challenge for someone just stepping in; but whatever challenge arose, there was always some coach with the right expertise to help out. Furthermore, with Ben Abelshausen (Xivk) and Jonathan Belien (jbelien) being coaches as well, OpenStreetMap was well represented, especially when Joost Schouppe passed by as well.
Today, I got the question how I quickly added a ton of notes. I use OSMAND for this, with a few tweaks.
For now, your note is not send over to OSM.org but remains on your own device!
EDIT: M!dgard figured out a way to make this step obsolete and to import them directly into JOSM. See his diary entry here
After surveying, you’ll have a ton of notes. To upload them all at once:
You can also enter your credentials with the ‘OSM Editing’ plugin settings, so that you don’t have to enter them over and over again.
If you are gonna add a lot of POIs with the same presets (e.g. benches, AED, …), you can also make a quick action for that. Play around!
I’m from Bruges (Belgium). You know, that famous medieval city in Belgium.
As everyone in Belgium knows, the center of Bruges is paved mostly in sett/cobblestones. Personally, I’m pretty fond of those sett pavements. They’re way nicer to see then asphalt (not to mention conrete plates), the absorb a lot of heat in the summer (cooling the city) which is released again in autumn.
But, as the bicycle is my primary means of transportation, one drawback comes to mind: they’re uncomfortable to cycle on - especially when pulling a cart. Some types of set pavement are to be avoided then - I’d rather drive 200 meters over asphalt than 100 over the big boulder. However, the smaller sett -often laid in arcs- is more comfortable to drive on and has a smaller penalty.
This implies that more information should be added to the ‘surface’-tag. In this document, I propose a few extra tags to deal with this extra information; and what kind of sett these are. These tags are used in Bruges; feel free to use them in other places as well.
All example pictures are taken by me, and may be used freely for OSM-related endeavours (e.g. wiki, tools, …).
First things first.. What is sett stone? And what are cobblestones?
According to Wikipedia, Cobblestone is a natural building material based on cobble-sized stones, and is used for pavement roads, streets, and buildings. Sett is distinct from a cobblestone by being quarried or shaped to a regular form, whereas cobblestone is generally of a naturally occurring form.
In practice, cobblestone is often used in OSM to describe sett stones - although incorrectly. The wiki itself acknowledges this:
After some experimenting and help from the Belgian OSM Community, I figured out how to tweak the parameters for the routing engine and steer the navigation process. It seemed as if the technical documentation was missing, so lets write it here.
All parameters for the routing file are stored in a single XML.
You can find this XML on the OSMAnd github. Head over there, and download it. EDIT: By now, all the documentation has been included upstream. Everything you can read here, you an also find in the github routing.xml file. This diary entry can still serve as a gentle introduction.
This document should be placed in a place where OsmAnd will find it. As I chose ‘external storage’ to store my maps (settings -> general settings -> Data Storage Folder (under miscellaneous title), adding this custom routing is easy.
Plug your phone in your computer and go to the path /sdcard/Android/data/net.osmand.plus/files. Copy routing.xml over.
routing.xml is actually documented quite good! Read the docs there to get some general idea.
The parameters are split per profile. I edited the bicycle profile, as that is what I use most (also see my previous diary entry).
Over there, add a toggle, e.g., if you want to avoid sett surfaces:
<parameter id="avoid_sett" name="Strongly prefer asphalt and paving stones" description="Tries to route around sett and cobblestone, ideal if riding with a cycling cart" type="boolean"/>
The id is the name you’ll use in if-statements, the name is what shows up in OSMAnd. Save the file as described above and restart OsmAnd. Start navigation to somewhere. If you click the settings (the cogwheel on the bottom when starting navigation), your new parameter should show up!
Routing considers three major aspects:
Each of those aspects has its own section in the xml; you can’t miss them.
Hello everyone,
The 26th of september was an OSM-meetup in Bruges. The few guys which where there - and especially Joost, must have gotten some weird and extremely contagious disease, called ‘mapperitis’. It has been the start of a growing involvement in the mapping efforts of OSM.
Although I’ve been using OSM as my navigation of choice for years now (prob. 5), it’s only recently I’ve actively begun mapping. Altough my first mapping were the ski routes on holiday, that was a one-off - until now.
Using streetcomplete, I’ve been surveying the surfaces of Bruges, which contains - as you guessed it, a lot of sett (aka ‘neat cobblestone’). In the meantime, I’ve been spreading that contagous mappiritis around as well - until it reached someone of the Fietsersbond. One of them had recently seen the talk by Escada and was wondering if it would be possible to map all cycling routes, their surface area and width, to test if they meet the vademecum. “Yes, this is possible” was my answer of course!
I followed by a short showcase of OSM, overpass-turbo and how easy it was to enter all this info. Although he was impressed, he was a bit scared of how much work it seemed to be - and that it is an older and not so tech-savy person didn’t help either.
That was a week ago*. By now, the north of Bruges (the center) is surface-mapped, and around 50 cycleways are measured.
*(To be honest, it was two weeks. However, I was on holiday one week, so I couldn’t map)
In the mean time, I was confronted with another problem. Quite often, I’m cycling around with a cycle cart. These things are slowed down tremendously by sett stones. So I wondered, wouldn’t it be possible to tweak the OSMAnd routing to avoid those nasty cobblestones?
After a few inquirements on the community riot channel, it turned out to be possible. And not only possible, it was easy as well!