We frequently receive requests from researchers about “old” OpenStreetMap data. In one instance we’ve been asked whether we could provide data for a city road grid – for the year 1980! So let’s take a minute to explain what is possible and what isn’t. In general, you can download older data files – for the […]
We frequently receive requests from researchers about “old” OpenStreetMap data. In one instance we’ve been asked whether we could provide data for a city road grid – for the year 1980! So let’s take a minute to explain what is possible and what isn’t.
In general, you can download older data files – for the 1st of January of each year – from our download server. Just click on the “raw directory index” link and you’re presented with a list of available files – either .osm.pbf or shape files. Sometimes when we’ve split up a country in smaller regions at some point, you might only find more recent files for the small regions, but older files for the whole country.
OpenStreetMap keeps a full history of everything, so it is possible to extract even more fine-grained snapshots – say for the 1st of each month since 2014! This will require the “osmium” utility (with its –time-filter option), as well as a “full history” file. Such files are available (for the whole world) from planet.openstreetmap.org, but also for individual continents or countries from our project-internal download server. (Because these files contain metadata that may be personal data, access is only allowed with an OSM login.)
There are a number of caveats that apply to working with historic OSM data though. First and foremost: An OSM data set of time X tells you what OSM knew about the world at that time – and not what the world was like at that time. If a building has been there for 100 years but was only added to OSM in 2020, then the 2018 data set will not contain that building. You can get an idea of what to expect in an old OSM data set from the “chronology” tab of the taginfo service (globally at taginfo.openstreetmap.org, or for individual regions at taginfo.geofabrik.de). Here’s a graph of the “building” tag for Spain:
As you can see, OSM currently has about 4.5 million building objects in Spain, and in 2014 we had about 450,000. Does that mean that 90% of Spain’s buildings have been erected in the last 10 years? No – it only means that OSM was much smaller in 2014 than it is today!
Because OpenStreetMap was invented in 2004, obviously any data export for any time before 2004 will be completely empty. In the early years we also had a few incompatible data model changes, and the license change in 2012 meant that some data had to be removed again. So, going back further than the license change will really give you very patchy results, and is not recommended for most use cases.
Another thing to consider is that in some areas the mapping methods have changed, and something that was mapped as X in 2014 might today be Y. Depending on what research you are doing, it might be necessary to adapt your filters to that.
If you would like to enlist our help in extracting historic information from OpenStreetMap, we’re happy to make you an offer.
I have been interested in making “before and after” comparisons of mapping progress for a while. The rich and beautiful OSM-carto style as it appears in standard OSM is a particularly important element of what I wanted to achieve, but it remains quite difficult to render historical map data in this style.
I have been interested in making “before and after” comparisons of mapping progress for a while. The rich and beautiful OSM-carto style as it appears in standard OSM is a particularly important element of what I wanted to achieve, but it remains quite difficult to render historical map data in this style.
This guide mostly follows the ohsome guide from 2018 but taken further and with updates. Please be aware that I have done little to optimise the workflow so far; this is more of a proof-of-concept at the moment.
I started out mapping in August 2020 and mapped almost exclusively in my old hometown whilst I was stuck there during COVID. I spent a lot of time mapping this area very comprehensively and wanted to visualise my work. Big shoutout to user John Bek who greatly helped with building tracing, which is quite tedious. The Blue Mountains towns of Katoomba, Leura and Wentworth Falls featured are now some of the most comprehensively mapped in Australia.
Previous method
The most genuine way of rendering historical tiles is from the planet file. I previously tried running an OSM tile server in docker with data extracted from the pbf file downloaded from geofabrik. In windows I installed docker in an ubuntu VM and then installed the
“minimal effort” tile server following the github instructions. After a lot of messing around, I was able to generate tiles for a particular moment in time:
I think the way the pbf was spliced made the large natural=wood relations disappear, so elements are missing unless I generated tiles for a much wider area.
Either way a lot of effort, and I never figured out how to procedurally generate tiles at different timesteps.
New method
Software requirement
Internet browser (I hope you have this already)
QGIS (version must be 3.14 or newer)
ffmpeg
Get the data
I have been using ohsome visualisation tools for a while, but only quite recently I became aware of the ohsome API endpoint for Full History extraction of a region of interest.
The first step is to get the bounding box coordinates of your area of interest.
Tip: in OSM, the url is formatted like this:
https://www.openstreetmap.org/#map=19/{y}/{x}
where {y} is the latitude in [-90,90] and {x} is the longitude [-180,180]
Note down the lat/lon pairs x₁,y₁ for the northwest corner and x₂,y₂ for the southeast corner.
Now you can construct the API GET request. Amend the following example as necessary and paste it into your browser URL bar.
The bboxes parameter is structured like bboxes={x_1},{y_1},{x_2},{y_2} as below.
I have split up the request by querystring parameter for readability. Change bboxes, keys, time and types.
You’ll now want to repeat this step using the following combinations:
Key
Way
Relation
Vector geometry
highway
Yes
No
Linestring
waterway
Yes
No
Linestring
railway
Yes
No
Linestring
building
Yes
Yes
Polygon
landuse
Yes
Yes
Polygon
natural
Yes
Yes
Polygon and Linestring
amenity
Yes
Yes
Polygon
leisure
Yes
Yes
Polygon
These categories should cover the vast majority of what you can see rendered in OSM-carto. You might want to also download power as linestring for power lines, etc.
You will get 13 GeoJSON files out of this; you can simply drag them into QGIS. Note that when downloading type=way geometry, in QGIS you will be given a choice of what geometry type to use as a vector layer. For instance, natural=* ways may be either a polygon (area) such as in natural=wood or Linestring such as in natural=cliff. I recommend you import them both separately if required.
You should also download relation areas (multipolygons) for common area types according to the table. Conveniently, ohsome API will also clip large relations to the bbox that you chose.
Altogether you will probably have 14 vector layers.
Styling in QGIS
The most time-consuming part is styling everything to look like it does on OSM. I suggest adding OpenStreetMap as a layer on top so you can colour-sample directly.
Start by setting your QGIS project canvas colour to the OSM blank land colour #F2EFE9 (Project > Properties… (Ctrl + Shift + P) > General > Background Colour).
Highways
After importing your GeoJSONs into QGIS, you can open the Layer Properties and go to the Symbology tab. Set the type to Categorized, set the filter to your key (eg. highway) and click Classify.
At this point, you’ll probably get a bunch of junk mixed in with the common highway types. Just delete the ones you don’t want. Then change Categorized to “Rule based”.
You don’t really need to do that many modifications here, just a few like discriminating service roads from driveways and parking aisles etc. I didn’t bother with the more subtle stuff like tracktype, surface and access etc.
You now want to decide on a zoom level to encompass all your data, and consider the resolution of your final animation (I recommend 1080 x 1920). My map scale for the animation is 1:16255, which is between zoom level 15 and 16, I picked that just arbitrarily.
OSM roads are composed of an inner stroke and an outer stroke. You can symbolise this with two lines, one slightly thicker than the other. For mine, major roads were set to 1.8mm and 2.0mm for the thin and thick lines.
Minor roads such as links, residential, unclassified etc should be thinner. I used 1.3mm and 1.5mm. For all cases, make sure you set the Join and Cap style to “Round”.
If you want to be able to render your map at multiple zoom levels, you’ll need to adjust the thicknesses for each zoom level and enable Scale range such as below, according to this guide. This will be quite time consuming.
After you’ve finished copying all the colours, you’ll want to set the rendering order. Click “Symbol Order…” button and set the order as below;
The aim is to have the thick, dark outer stroke to level 0 and the thin, lighter stroke to higher numbers according to the road classification.
Finally, in the Temporal property tab, enable Dynamic Temporal Control and set the Limits to “include start, include end” and set the Start field to @validFrom and the End field to @validTo. Note that this is a fairly new feature in QGIS and performs much better in my experience than the plugins that the original ohsome blog post used.
You can now check if everything is working by opening the Temporal Controller Panel (clock icon) in one of the toolbars up the top of the QGIS main UI. Try scrubbing through the timeline and see how the data changes.
I ended up turning driveways and parking aisles off because they encumbered the map too much at my zoom level.
Other stuff
This is what my Leisure non-relation polygons look like. These are the only categories I kept.
Most of them are fairly straightforward, however some things like leisure=natural_reserve are less intuitive and also drawn above everything else, so you may want to separate it into its own layer.
To get the green stroke that is only inside the polygon, I set the effect “Inner glow” with zero blur radius. Make sure you uncheck “Source” otherwise the inner part won’t be transparent. I set it to #B6DEB6 and slightly transparent just by estimating it, I’m sure you could probably figure out the actual correct colour from OSM-carto repository but this will do for now.
Here are my settings for leisure=garden.
Some other interesting ones are natural=cliff;
wetland=marsh;
and natural=scrub and natural=wood were basically the same but with different SVG symbols that I thought were a fairly close match from what I already had installed. I didn’t really try that hard for it to be accurate because most of this stuff you can’t really see anyway.
For waterways, I set it to rule-based where intermittent=yes was the only rule for the dashed line style, and then everything else was rendered the same.
You can check this imgur album for other settings.
Finally, make sure your layers are all in a sensible order. I put linestrings and nature reserve over the top of everything else. Landuse was on the bottom; amenities and leisure above that and then natural on top of those. OSM-carto has a lot of rules for this but the goal is not really an exact replication here.
Note that I didn’t render labels or point icons, this is on purpose; I feel like it isn’t really appropriate for a timelapse video.
Animating everything
Make sure all layers have the same Temporal settings. Now in the Temporal Controller, check to make sure everything looks good. Set the Step interval to 1 month, make sure your viewport is roughly in the centre of your Area of Interest, Save the project, and now you should be ready to export the animation. Set the resolution to something sensible, I suggest 1080 x 1920. I tried 4K but my laptop struggled hard. Again, I suggest testing it with a short timespan first to make sure your settings are dialled in correctly.
It should save the frames as png images in the format usually “projectname0001.png” etc.
Compile the video with ffmpeg
Open your terminal and change the directory to the folder with all your png frames. Here is my script below. It includes a date counter in the format YYYY mm in the top left corner. You can get rid of the -vf flag if you don’t want the counter. Make sure you change the input name to your own one.
The drawbox and drawtext draws a transparent background for the date counter and the text with the counter. This increments the month every frame, and the year every 12 frames, starting Jan 2008.
I found that the video won’t play for some people, or in Windows media player, or upload to Reddit without adding the pixel format flag -pix_fmt yuv420p.
Wrapping up
If you have trouble with any of the steps, or suggestions on how to improve the workflow or the rendering, please leave a comment. Good luck and have fun.
J’ai un peu oublié de faire ça ces derniers temps, n’est-ce pas?
Pour faire court, j’ai été occupé par mon déménagement (qui a finalement eu lieu) et j’avoue que la motivation pour faire des vidéos était assez basse. D’ailleurs, je n’ai “que” huit nouvelles vidéos depuis le dernier update en juin.
Ce mappeur OpenStreetMap vous montre comment utiliser Strava avec
Coucou 👋😅
J’ai un peu oublié de faire ça ces derniers temps, n’est-ce pas?
Pour faire court, j’ai été occupé par mon déménagement (qui a finalement eu lieu) et j’avoue que la motivation pour faire des vidéos était assez basse. D’ailleurs, je n’ai “que” huit nouvelles vidéos depuis le dernier update en juin.
J’avais une deuxième partie de prévue, mais c’est là que mon déménagement est venu s’intercaler et lorsque j’ai récupéré du temps après celui-ci, ce que je montrais était déjà devenu obsolète en gros.
On finit avec deux vidéos beaucoup plus récentes :
Et voilà pour cet interminable pavé de texte. Pour l’instant, je suis pris entre nos fameux trottoirs sérésiens et le “tri” manuel d’un tag particulier. Je voudrais bien faire une vidéo sur le sujet, mais je ne sais trop si je dois faire ça via une session live ou quelque chose de plus didactique (avec ma fabuleuse rhétorique d’homme des cavernes 🤣).
Pour cartographier un centre de données
# pour débuter
wiki.openstreetmap.org/wiki/Tag:telecom=data_center
il est necessaire de
telecom data_center mandatory
operator The operator of the datacenter. In the case of a corporate datacenter, this will be the organisation which owns it. In the case of a colocation facility, this will be the c
Pour cartographier un centre de données
# pour débuter
operator The operator of the datacenter. In the case of a corporate datacenter, this will be the organisation which owns it. In the case of a colocation facility, this will be the colocation company. recommended
operator:wikidata Q recommended
*name The name of the datacenter. recommended
ref The operator's reference for the datacenter (usually a three or four character abbreviation). recommended
For some time I’ve been looking after a raster map style that’s designed to be a useful “England and Wales rural pedestrian” map, and also to showcase some of the richness of data that might not be obvious from basic “general” map styles such as the ones on OpenStreetMap.Org.
A goal for some time has been an offline version of that map style. At any useful level of detail that
For some time I’ve been looking after a raster map style that’s designed to be a useful “England and Wales rural pedestrian” map, and also to showcase some of the richness of data that might not be obvious from basic “general” map styles such as the ones on OpenStreetMap.Org.
A goal for some time has been an offline version of that map style. At any useful level of detail that requires different technologies to be used, and the first parts of that - a vector map schema and a web map style - are now available (though not yet available offline).
The online version of that map is available here. It’ll take a couple of seconds to appear.
How vector maps work
Essentially, something takes OSM data (such as a “.pbf” file) and creates “vector map tiles” from it, often as a large “.mbtiles” file. This file is essentially a small database containing information about what features are present at what zoom levels (but not what they should look like). The client (in this case a web browser running some JavaScript) reads a file that contains details about the desired display style and uses that to present map features to the user.
The software used to create the vector map tiles was Tilemaker. The Javascript libraries used by the web browser are from MapLibre and the map style was created using the MapLibre Style Spec.
Vector map schemas
Various vector map schemas exist for use with OpenStreetMap data. OpenMapTiles is one; Shortbread is another.
I looked at both of these, but neither contained all the data that I knew that I wanted. However, my existing raster maps already consolidate OSM data into a format designed for display, so the obvious approach was to define a schema based on that.
Both osm2pgsql and Tilemaker use lua for scripting, which means that much of the required code is already written needing only cosmetic modifications. Some code is already shared between the two projects; eventually most or all of the “schema” code will be.
Simplifying the schema
The raster display map style dates from what was in OSM Carto in about 2014, before it was changed to be less useful as a pedestrian map.
There are about 76 layers in there, which is significantly more than required. I reduced this to 9. Of those, “water” just contains merged-in coastline data and “poi” isn’t extracted by default (it’s a catch-all designed to spot another that hasn’t been picked up in “land1” and “land2”). The readme has more information.
The new vector map style
The styling options available with MapLibre are broadly similar to CartoCSS but with more control of how things change from one zoom level to another.
I’ve tried to make the new style more consistent both about how each layer is defined in the code, and also about how it appears. For example, all text uses the same font; with different colours used to show different classes of features and text size used to show differences in a class.
The fonts used are from Klokantech, in turn based on Google’s noto.
Road shields had to be reimplemented from scratch, resulting in proper UK/IE versions as opposed to the nondescript-looking raster ones.
When reimplementing the new style I found a number of feature combinations which had simply never been handled by the raster display code, such as derelict canal bridges, so the new vector display style actually handles more data combinations than the old raster one.
Some raster features haven’t been implemented fully or at all yet - notably “way area” controls on zoom level of things such as island names.
A debug vector map style
In order to see what’s present in the vector map tiles a debug style has also been created, although that is not yet deployed anywhere.
Speed and size
The vector tiles and the style to interpret them are quite large, so loading an initial page does take a few seconds. This is less of an issue than it might be as the eventual goal of this project is offline maps; if map tiles are already on a device the time to load is obviously less.
Creating a vector map of Britain and Ireland takes 12 minutes on a server where a database reload of the equivalent for raster maps takes 90. Each resulting “.mbtiles” file is about 4GB; each equivalent database for raster tiles about 40GB, plus about 10GB of metatile cache.
Na základě dokončení opravy vedení linek MHD jsem mohl začít pracovat na webu, který má za cíl přehledně zobrazoval vedení autobusů, trolejbusů a tramvají ve městě Brně se všemi variantami konečných v aktuálním znění bez výluk kratších než 2 měsíce. Web je statický, založený pouze na HTML, JS a CSS. Projekt je na GitHub, kde rovněž hostuje v rámci GitHub Pages.
Webová aplikace mhd-brno.c
Na základě dokončení opravy vedení linek MHD jsem mohl začít pracovat na webu, který má za cíl přehledně zobrazoval vedení autobusů, trolejbusů a tramvají ve městě Brně se všemi variantami konečných v aktuálním znění bez výluk kratších než 2 měsíce. Web je statický, založený pouze na HTML, JS a CSS. Projekt je na GitHub, kde rovněž hostuje v rámci GitHub Pages.
Webová aplikace https://mhd-brno.cz je veřejná, nicméně obsahuje funkce, které pomáhají v práci řidičům MHD ve službě na trasách, které běžně nejezdí a potřebují ověřit její vedení, zastávky a orientovat se na trase v souvislosti se svojí polohou, tedy v reálném čase.
Hlavní funkce webu
Zobrazení mapy (OSM a ČÚZK).
Načítání relací linek Public Transport, kde je jedním z operátorů DPMB pomocí Overpass API.
Zobrazení všech variant trsy s možným výběrem varianty, kdy se k ní vypíší i zastávky dle pořadí na trase.
Získání a udržování polohy uživatele (typicky řidiče MHD) ve středu obrazovky a natáčením mapy ve směru jízdy. Nejedná se o plnou navigaci, ale pro orientaci vedení linky slouží dobře.
Udržování rozsvíceného displaye při aktivní poloze uživatele.
Instalace do mobilu jako webová aplikace (PWA). Zde bohužel vlivem známé chyby na straně Apple v systému iOS neakceptuje požadavek na stále rozsvícenou obrazovku. Při otevření webu běžnou cestou v prohlížeči Safari však vše funguje bezchybně.
Requests for comments have been made on these proposals:
virtual_tour=* to link to 3D virtual tours of locations such as museums, hotels, or stores.
rental:powerbank=yes for mapping stations that allow users to rent portable power banks for charging mobile devices on the go.
Voting is underway until Friday 15 November on the proposal to deprecate busway=* for bus lanes.
The vote on the proposal to add the tag sac_scale=strolling, which indicates a wide and smooth path, was accepted with 28 votes in favour, five against, and two abstentions.
Community
[1] Calvin Menttor blogged, in his OSM user diary, about his participation in the State of the Map Nigeria 2024. Kingsley Amankwe also published about his experience in the event and both were very pleased with the opportunity to participate.
Alexey Zakharenkov discussed an algorithm designed to detect missing stations on public transport routes in OpenStreetMap, overcoming problems such as accidental station deletions by comparing pairs of route variant ‘twins’ for discrepancies using the Wagner-Fischer algorithm, which detects mismatches similar to text-editing errors.
jjKlaus asked, on the OSM Community forum, how to handle the ongoing border disputes between Guyana and Suriname and between French Guiana and Suriname in South America.
SColchester shared insights from the 10th annual Missing Maps meeting in Nairobi, Kenya, where members discussed the project’s growth, challenges with their website, strategies for using OpenStreetMap data in humanitarian work, and plans to relaunch a data quality internship to promote community engagement and skill-building.
Some Amateur described the use of OpenStreetMap data during a firefighting operation, highlighting the critical role that detailed land-use mapping (such as ponds and wetlands) plays in real-world navigation, especially for emergency responders and outdoor enthusiasts who rely on offline, terrain-based guidance.
Christopher Beddow explored the evolution, cultural significance, and changing nature of place names (toponyms) throughout history, from colonial renaming and local vernacular names to digital innovations that may erase or preserve traditional toponyms. He highlighted examples such as Aotearoa in New Zealand, Romansh names in Switzerland, and the mixing of indigenous and colonial names in North America, noting how past naming conventions reflect local culture and geography.
The Local Chapters and Communities Working Group of the OpenStreetMap Foundation is looking for volunteers to help refine its membership model to better accommodate informal user groups and thematic communities by researching membership practices, coordinating discussions, and drafting recommendations.
Events
The Geospatial devroom is returning to FOSDEM 2025 and is seeking proposals for talks on topics such as FOSSGIS software, geospatial visualisation, geospatial AI, IoT, and OpenStreetMap. The devroom, scheduled for Saturday 1 February in Brussels, is looking for 25-minute presentations and 10-minute lightning talks. Submissions are due by Sunday 1 December and the selected speakers will be notified by Sunday 15 December.
The results of the Scientific seminar in support of the Rio Grande do Sul (Brazil), organised► by the IVIDES.org, are now available for free download (in Portuguese). The presentation and video files can be found > on Wikimedia Commons. There is also a mapping project on the HOT Tasking Manager, where you can collaborate.
The recordings and photography from the State of the Map Nigeria 2024 have been published. You can watch the videos and see the amazing photos of this event, which was held in the City of Ile-Ife.
The community poll for FOSSGIS 2025 is now open and can be taken until Sunday 17 November. The results will be included in the programme committee’s evaluation as a community opinion poll.
Campus du libre will be held► at the Université Jean Moulin Lyon 3, campus de la Manufacture des Tabacs (Campus of the Tobacco Factory), on Saturday 23 November.
The OSM Kerala Community Meetup 2024 is now the State of the Map Kerala 2024, the first regional OpenStreetMap conference to be held in India. The event will be on 16–17 November in Wayanad, Kerala and will focus on open mapping for disaster resilience, GIS, and humanitarian needs. Sponsored by partners including Meta and FOSS United, the event invites mapping enthusiasts to participate in talks, workshops, and networking activities. The sessions will be covering disaster preparedness, community resilience, and open data initiatives, among other topics.
State of the Map’s official Mastodon account tooted on several upcoming local, regional, and national State of the Map conferences, as well as other map-related events around the world. They suggested that event organisers who are planning a local State of the Map event apply for a SotM Quick Licence from the OpenStreetMap Foundation.
OSM research
Students at Malmö University (Sweden) have investigated the effectiveness of using OpenStreetMap data versus traditional cadastral data for predicting public violent crime in three Swedish cities of different sizes and found that while cadastral data generally produces more accurate predictions in smaller cities, OSM data produces comparable results in larger cities, suggesting the potential utility of OSM for spatial crime analysis.
Humanitarian OSM
The Spanish OpenStreetMap community has organised► a mapping response to the tragic flooding that occurred on 29 October in the Valencia Province.
The Indonesian OpenStreetMap community has organised a mapping response to the Mount Lewotobi Laki-Laki eruption in East Flores, East Nusa Tenggara, Indonesia, which occurred► early on Monday 4 November at 02:48 local time, resulting in at least nine fatalities. Many victims were killed► by large rocks from the eruption that broke through house roofs. The eruption also triggered► intense fires in homes and a school building, causing extensive damage.
Maps
Christoph Hormann discussed updates to his AC Style map symbols, including redesigned waste and recycling symbols, new symbols for towers, masts, cranes, benches, and oil wells, with an emphasis on readability, functionality, and cultural relevance for global map users.
OSM in action
The Louvre is using► an OpenStreetMap-based map on its website to visually display the locations of its loaned artworks around France and internationally, improving public access to its collection through geographic mapping and cultural outreach.
Altilunium has developed Cmaxz, an OpenStreetMap-based weather radar map viewer.
PickYourPlace announced the launch of its real estate platform designed to provide comprehensive neighbourhood insights, such as safety, property values and accessibility data, to help users make informed housing decisions, initially focusing on Calgary, Canada, with plans for expansion.
OldMapsOnline is offering► a vast, interactive archive of over 500,000 historical maps, allowing users to overlay these maps with modern OpenStreetMap data for comparison. The platform features a timeline slider to explore specific time periods and is valuable for historians, genealogists, and urban planners interested in studying geographic change and urban development over time.
Sylvain Machefert tooted that the Bordeaux-Nantes Intercités trains use dynamic displays with an OpenStreetMap-based map and Wikimedia Commons photos, although he noted the lack of Creative Commons licence attribution for the images.
Open Data
OpenSuperMaps has extended its data coverage to New Zealand, allowing users to download enhanced map files with detailed address and geographic data for use in mapping applications such as OsmAnd.
Licenses
KevinOs reflected on his effort to align local open data licences with Canada’s Open Government License, by comparing regional variations, noting minor differences in wording and attribution requirements tailored to specific legal frameworks. He highlighted inconsistencies in documentation across Alberta cities and advocated for clearer attribution guidelines and wiki updates by OpenStreetMap’s legal working group to ensure compliance and transparency.
Software
The Prototype Fund, a key resource for supporting OpenStreetMap and other open source projects, confirmed► its continuation until at least 2029, with one funding round per year. New updates include increased team funding of up to GBP 78,800 (USD 102,000), eligibility for EU-based team members, and a shift in funding priorities to support data security and software components projects and less on civic tech.
Jaller94’s tool provides downloadable GPX files that identify missing Stolpersteine (Holocaust memorial stones, we have covered previously) in the neighbourhoods of Berlin, Germany, and allows users to upload these files to OpenStreetMap applications such as OsmAnd to complete local data for memorial locations.
Routing24 is a free client-side route optimisation tool designed for small businesses and solo drivers, enabling efficient multi-stop planning with support for multiple vehicles and business rules such as delivery windows, all based on C++/WASM, and OpenStreetMap data. It does not currently support mobile devices.
OpenAI has announced that ChatGPT now includes Mapbox for map views, enhancing ChatGPT’s ability to provide geographic context and navigation details directly in conversations. The Mapbox integration allows users to access detailed, interactive maps and supports more intuitive location-based responses for ChatGPT’s new search feature.
Programming
For the Smart Mobility Lab Hackathon in Kigali, the Trufi Association has challenged students to create OSM and AI-driven solutions to improve transportation. Their creativity will shape urban mobility in Rwanda.
Siarhei Ivanou has published the source code for his service City Indexes, which calculates housing attractiveness indexe for cities in Belarus, Russia, and some European cities.
Releases
Peter announced the release of GraphHopper Routing Engine version 10.0. This release fixed a long-standing issue with u-turn routing, added several improvements to turn restriction implementations, and included an enhanced version of GraphHopper Maps with text search functionality.
OpenStreetBrowser’s maxspeed category now shows speed limit signs from zoom level 16, with icons that adjust directionally to reflect the actual orientation of the traffic sign.
The Vespucci 20.2.0.1 beta release has introduced enhancements including support for HEIC/HEIF images on Android 10+, multi-select in tag-only editing mode, conflict resolution for partial uploads, and auto-selection of Overpass query results, along with various UI, rendering, and code improvements.
Martin Raifer announced several updates to overpass turbo, including an auto-styler wizard and additional MapCSS features.
Did you know …
… that osm2streets can convert OpenStreetMap data into detailed, lane-specific street networks, making it easier for developers to render and analyse complex road structures?
… that Navigator is a popular free multi-platform satnav app powered by Mapfactor, based on maps from the OpenStreetMap project, which can be used in your own applications?
OSM in the media
Anne-Karoline Distel corrected a speed limit discrepancy on Kilkenny’s Bennettsbridge Road (Ireland) using OpenStreetMap, Mapillary, and field data collection. She updated the map to reflect accurate speed signs and thereby promoted OpenStreetMap as a reliable tool for local navigation updates.
Other “geo” things
The Garmin Tread 2 navigator integrates OpenStreetMap data for turn-by-turn navigation on unpaved roads, plus US Forest Service maps, and trails for off-road adventures. In combination with high-resolution satellite imagery, public land boundaries, and extensive topographic information over North America, it provides versatile guidance for rugged outdoor exploration including snowmobiling.
Google is rolling out generative AI-powered updates to Google Maps, Google Earth, and Waze using its Gemini model, enhancing features such as conversational search, contextual navigation, hazard reporting, and AI-based recommendations. The new features will be initially available to selected testers.
Esri’s 3D base maps, augmented with data from Overture Maps and OpenStreetMap, is providing detailed globally accessible geographic representations that support urban planning, environmental management, and infrastructure development. These 3D maps incorporate highly detailed building data and are continually updated with open-source and community contributions, enabling Esri to provide immersive visualisations to users worldwide, including targeted support for underrepresented regions such as Africa.
Upcoming Events
Where
What
Online
When
Country
Hobart
FOSS4G SotM Oceania 2024
2024-11-05 – 2024-11-08
Gent
OpenStreetMap + pizza + velopark – meetup
2024-11-08
Salzburg
Maker Faire Salzburg 2024
2024-11-09
København
OSMmapperCPH
2024-11-10
Zürich
169. OSM-Stammtisch Zürich
2024-11-11
中正區
OpenStreetMap x Wikidata Taipei #70
2024-11-11
Budapest
OSM Találkozó 2024-11-12
2024-11-12
Hamburg
Hamburger Mappertreffen
2024-11-12
San Jose
South Bay Map Night
✓
2024-11-13
Vitoria-Gasteiz
XV edición de las Jornadas Ibéricas de Infraestructuras de Datos Espaciales (JIIDE)
2024-11-13 – 2024-11-15
Salt Lake City
OSM Utah Monthly Map Night
2024-11-14
München
Münchner OSM-Treffen
2024-11-13
Lorain County
OpenStreetMap Midwest Meetup
✓
2024-11-14
OSM US Pre-Geoweek Mappy Hour
2024-11-14
Berlin
197. Berlin-Brandenburg OpenStreetMap Stammtisch
2024-11-14
Bochum
Bochumer OSM Treffen
2024-11-14
Saint-Claude
Conférence Apéro OpenStreetMap
2024-11-15
Vythiri
State of the Map Kerala 2024
2024-11-15 – 2024-11-16
Saint-Claude
Cartographie collaborative pour tous
2024-11-16
Град Зрењанин
Okupljanje u Zrenjaninu
2024-11-17
Hannover
OSM-Stammtisch Hannover
2024-11-18
Internationale GeoWoche – Online Mapathon von DRK, HeiGIT, MSF Deutschland & Österreich
I created this template to aid project co-ordination in tasking managers, and contributors seeking feeback. It has gone through several iterations; this is the one that I currently use. I think that there will likely be some alterations, because I see some potential impovements, though I haven’t yet received feedback regarding it from mappers.
Following interest in the template
Preface
I created this template to aid project co-ordination in tasking managers, and contributors seeking feeback. It has gone through several iterations; this is the one that I currently use. I think that there will likely be some alterations, because I see some potential impovements, though I haven’t yet received feedback regarding it from mappers.
Following interest in the template I use for validation comments from other validators, I am going to share the current version I use in this diary entry.
Please, try it out and share your ideas, experiences, and results.
Thank you to anthaas for the idea of publishing a diary entry about it.
My experience is in using the HOT TM so there may be some idiosyncratic parts which should be modified to be accurate/function within whichever TM is being used.
I have not yet seen what if any impact this has on 3rd pass validation.
Design Rationale
It was over two years ago now that I (in)validated my first tasks on the HOT tasking manager. I took a break from that until ~ 7 months ago when I started validating some more tasks here and there. Then ~ 4 months ago SColchester put me onto a good project for a beginer validator, and after that I was validating tasks at a significantly greater rate. It was also his comment on a previous diary entry of mine that insired a change in this temlpate.
After (in)validating a greater number of tasks via the HOT TM, I soon found that I was repeating myself quite a lot. For instance, linking to learning resources, events and thanking users for their contributions was very standard. I didn’t exactly fancy writing the same thing over and over, and I wanted to reach more contributors, so I decided to create something that’d make the process more efficient and idealy result in a higher quality of contributions.
The HOT TM comments section supports markdown formatting, so I decided to apply the skills I’d aquired while improving the formatting of the MMLWG FTOTW & Mid-Month Mapathon OSMCal listings, to create a standard validation comment template. This template would include a standard message, along with space for tasks specific comments and contributor feedback.
A clear distinction was made between the feedback that I was giving to a contributor, or contributors, and the reason(s) why I (in)validated a task. This is because the two may or may not be related, and I wanted to create something that was easy to reference for contributors who go on to complete an invalidated task, and for future validators.
Fig.1. Annotated Screenshot Example
There was a time where I would make annotated screenshots, and post them on tasks (with a legend) to provide visual feedback, however at some point I figured that if I’m going to be pointing to and drawing features; I might as well just map and upload them, so I have since transistioned to using OSMCha. This works well, but some things are irrelevant in changeset comments and verifications. For example, It often doesn’t make sense for me to submit changeset comments about what wasn’t mapped. Even if a task is not complete, the contributions themselves may be of a high quality.
A significant proportion of regular users who contribute via the HOT TM do not know how to access a task’s changesets, nor use OSMCha. Given this, and that feedback will also be provided to absolute beginers I saw it necessary to add sentences directing users on how to access it.
Given that mappers contribute on a voluntary basis, that tasks and projects are not homogenous in density of features, or difficulty, and that validators can multi-task validate. I decided to add text about splitting tasks, becasue projects make more continuous progress by ‘locking it in’ if a smaller area is submitted after being well mapped, as opposed to a larger one that would later be invalidated. This would probably be better located in the project instructions or completion panel of a task, so that initial contributors are aware of this option.
I wanted all of the users who contributed to a task which was later (in)validated to be notified hence “#contributors”.
Adding a link to Nicolelaine’sContinuing you contribution web page to this template could also be a good idea (especially when validating via the HOT TM), becasue it contains many HOT related links and explanations. The short URL also lends itself well to being added to a changeset comment, given the character restriction.
View the task change-sets via task data in top right of the task window.
View an entire validated task, by lodaing the data in an editor via the task window.
If you cannot complete the entire task, either due to time constraints or your ability, then it may be a good idea to split the task: you don’t have to do it all yourself, nor all in one go.
Thank you for your contribution. #contributors
A mapping event is hands down the best way to recieve feedback and interact with other mappers. Here’s one that occurs regularly.
# Validation Feedback
## Reason(s) for (in)validation (generally not exhaustive)
-
## Before attempting to map an invalidated task, or for feedback:
- Check the [project](https://tasks.hotosm.org/projects/PROJECT_ID#questionsAndComments) and task comments.
- View the task change-sets via task data in top right of the task window.
- View an entire validated task, by lodaing the data in an editor via the task window.
If you cannot complete the entire task, either due to time constraints or your ability, then it may be a good idea to split the task: you don't have to do it all yourself, nor all in one go.
Thank you for your contribution. #contributors
---
A mapping event is hands down the best way to recieve feedback and interact with other mappers. [Here's](https://www.tickettailor.com/events/missingmapslondon?) one that occurs regularly.
You can find other events [here](https://osmcal.org/)
Learning resources and links can be found [here](https://wiki.openstreetmap.org/wiki/Beginners%27_guide)
Usage
Copy the code and ensure that the first line is empty, then save it as the master validation template file (I use notepad). After you choose a project to validate substitute the project ID for “PROJECT_ID” in the template. Currently this seems to only send a user to the project page and not the specific section, but maybe the functionality could be improved in future.
You can also add project specifc tips or cautions in the ‘Before attempting to map an invalidated task’ section, e.g. ‘beware the primary imagery source is off-nadir which means that you can see the Eastern walls of buildings; take care to not include the walls of a building in its footprint.
Then just copy the code and paste it into a markdown supported text box, add task/user specific feedback, then submit the comment.
You can then save this as a project specific version of the template, or just close the template without saving after validating.
A template like this one works well in tandem with a tool like peculiar theater’s crib sheet, becuase it provides structure and formatting to the task/user specific comments you provide.
Even if you don’t provide any feedback as a validator, posting this template in the comments can still help contriutors obtain feedback by viewing task changesets to see the changes you’ve made, or by guiding them to alternate sources. Good changeset comments can help others to understand your contributions.
If a task should need to be invalidated again, then probably only the validation feedback and and reasons for (in)validation need to be posted, as to not take up space in the comments with redundant information.
Edit 1: Added (I use Notepad).
Edit 2: Added split task paragraph in the Design Rationale section
Mise à jour du taux de complétion des adresses dans OpenStreetMap. Cet article fait suite à une série d’autres articles ici en septembre 2022, en mai 2023, et en mai 2024, où je compare le nombre d’adresses par communes en Wallonie entre la source de référence des adresses (ICAR) et OSM.
Mais cette fois-ci, j’ai aussi mis à jour la source des adresses officielles (ICAR), ce qui fait que
Mise à jour du taux de complétion des adresses dans OpenStreetMap. Cet article fait suite à une série d’autres articles ici en septembre 2022, en mai 2023, et en mai 2024, où je compare le nombre d’adresses par communes en Wallonie entre la source de référence des adresses (ICAR) et OSM.
Mais cette fois-ci, j’ai aussi mis à jour la source des adresses officielles (ICAR), ce qui fait que la progression dans la complétion des adresses semble reculer! J’ai aussi corrigé le calcul en omettant les adresses OSM dupliquées par un point dans un polygone (typiquement un noeud d’un commerce/horeca qui contient l’adresse et qui se trouve dans un batiment avec la même adresse -> certains adresses étaient comptés en double).
En Wallonie, 1,206,060 adresses sont répertoriés dans OSM, contre 1,829,093 dans ICAR (65.9 %). On était à 64.4 % en septembre 2022 et 67.1% en mai 2023 et 73.2% en mai 2024. La mise à jour de le source des adresses semble faire reculer la complétion, mais pourtant les adresses OSM progressent toujours et à un rythme régulier!
Attention, beaucoup d’adresses officielles sont maintenant définies AVANT la construction des immeubles, typiquement dans les nouveaux lotissements. Cela fait de facto qu’arriver à 100% pour certaines communes n’est pas vraiment pertinent. Dans la commune de Habay par exemple, on a un taux de complétion de 85% seulement alors que l’immense majorité des batiments construits sont dans OSM avec leur adresse: des dizaines voire centaines d’adresses non encore construites sont déjà dans ICAR.
Voici une carte choroplète, montrant, pour chaque commune, le degré de complétion des adresses dans OSM par rapport à ICAR. Les limites de provinces sont soulignées par un trait plus gras.
Les 10 communes où les adresses ont le plus progressé sont:
Quevy
Ittre
Court-Saint-Etienne
Froidchapelle
Erquelinnes
Honelles
Tubize
Ath
Mont-Saint-Guibert
Mons
Et les communes où les adresses sont le moins complètes sont:
In January, I introduced Overpass Ultra v2 and then
in June I provided some updates. Today I’m excited to share that
Overpass Ultra is now simply Ultra(v3) as it has evolved beyond simply being an Overpass
client into a general purpose MapLibre GL JS IDE.
Since my last update, the following features have been implemented, culminating in the release & announcment of Ultra:
Since my last update, the following features have been implemented, culminating in the release & announcment of Ultra:
More extensive documentation
The concept of query providers
Auto-sorting of paint and layout layer styling directives
Fallback glyphs
Bundled icons as named sprite sheets
HTMLControl to add custom controls, including titles to a map
📘 Documentation
At the end of June, I announced overpass-ultra.us/docs on Mastodon. In addition to basic documentation about Ultra, it includes many Examples which are focused more on Ultra’s capabilities than the specifics of quering Overpass as there are already many resources for how to do that. It also includes a MapLibre Examples section which includes ports of many MapLibre GL JS Examples to help demonstrate Ultra’s capabilities as a MapLibre IDE rather than as an Overpass client.
The astute observer will notice that both of these are styled without defining any custom MapLibre layers. This is because there is partial KML styling support in the kml provider’s default layers, and the geojson provider’s default layers implements the mapbox simplestyle spec.
🔍 More Query APIs
In addition to Ultra’s original overpass provider, it now has an ohsome provider that uses the ohsome API extract endpoint and a sparql provider that can be used with services such as QLever and the Wikidata Query Service.
For an example of how to query QLever, see this example.
🪄 The auto provider
You might have noticed that you don’t need to specify that you’re running overpass queries, or that the above are loading GeoJSON & KML data. This is because many of the query providers are supported by a special auto provider which is configured as the default.
Not all providers are automatically detected, such as the ohsome and sparql providers. You can specify those with the
type: YAML front-matter key.
You can always find what providers are available and which can be detected by default in Ultra’s help menu.
🖌️ Auto-sorting of paint and layout layer styling directives
Inspired by map-gl-utils, Ultra allows for paint and layout keys to be
defined at the top-level of a layer definition, and will automatically move them into the correct section for you.
for example, instead of defining a layer like this:
- type: symbol
paint:
icon-color: '#6dad6f'
icon-halo-color: white
icon-halo-width: 2
layout:
icon-image: maki:garden
it can be defined like this:
- type: symbol
icon-color: '#6dad6f'
icon-halo-color: white
icon-halo-width: 2
icon-image: maki:garden
🔠 fallback glyphs
Typically, when adding text labels with MapLibre, you must specify a font that exists in glyphs endpoint specified by your style. This presents two main issues for Ultra:
You might not know what fonts are available within the glyphs of the style you’ve selected
The glyphs used by most of the provided styles on overpass-ultra.us doesn’t support MapLibre’s default text-font value of Open Sans Regular,Arial Unicode MS Regular.
To aid with this problem, Ultra wraps access to glyph fetching and returns the appropriate range in the Noto Sans Regular font if the specified (or default) font is unavailable.
tl;dr - you don’t need to specify a text-font when adding labels using a symbol layer
📍 Bundled Icons
When I initially added bundled icons, they were simply available as PNGs to be used with Ultra’s support for PNG URLs.
I’ve since discovered MapLibre’s support for multiple sprite sheets, and have updated Ultra to add Maki & Temaki as spritesheets to the style with the names maki and temaki.
So now, instead of using:
icon-image: /icons/maki/garden.png
You can use
icon-image: maki:garden
Note: using icon-image: /icons/maki/garden.png will still work.
It can also be used for more building more complex custom controls such as creating a link or modal control.
Note however, that the HTML is passed through DOMPurify, so you can’t use Javascript.
What’s next?
I have more ideas than I can remember or have time to implement. I hope to get around to some of them. Among them are:
new query providers
replace the download button with an export dialog which additionally includes the ability to export the style.json or an HTML file of a full interactive map
the ability to add default style layers to the query front matter for easier customization without having to start styling from scratch
documentation about Ultra’s architecture, how to make a white-label deployment of Ultra, & how to implement a new query provider
and more
If you have your own ideas for features or new query providers for Ultra, leave a comment or message me on Mastodon at @trailstash@mapstadon.space
If you want to verify your OSM-account and get that nice badge, this is possible.
Place <a href='link to your mastodon account' rel='me'>_some text, e.g. my mastodon_</a> in your profile (Click your user profile on the top right > my profile > Edit profile).
Then, on your Mastodon-account, go to Preferences > P
Hey all,
If you want to verify your OSM-account and get that nice badge, this is possible.
Place <a href='https://link to your mastodon account' rel='me'>_some text, e.g. my mastodon_</a> in your profile (Click your user profile on the top right > my profile > Edit profile).
Then, on your Mastodon-account, go to Preferences > Public Profile. Under ‘extra fields’, set ‘OpenStreetMap’ to the left and a link to your account to the right.
Pengetahuan adalah bagian dari peradaban.
Peradaban adalah hasil dari kemajuan.
Kemajuan adalah proses dari peradaban.
Pengetahuan-peradaban-kemajuan=sejarah.
Sejarah adalah hasil dari pengetahuan-peradaban-kemajuan.
Sehingga sejarah adalah Wujud dari kehidupan.
Tak ada sejarah yg tak ada kehidupan.
Begitu pula kehidupan yg tak ada sejarah.
🙏🏻 Swastika
Pengetahuan adalah bagian dari peradaban.
Peradaban adalah hasil dari kemajuan.
Kemajuan adalah proses dari peradaban.
Pengetahuan-peradaban-kemajuan=sejarah.
Sejarah adalah hasil dari pengetahuan-peradaban-kemajuan.
Sehingga sejarah adalah Wujud dari kehidupan.
Tak ada sejarah yg tak ada kehidupan.
Begitu pula kehidupan yg tak ada sejarah.
OpenStreetMap Belgium organise un mapathon à Bruges dans le cadre de notre participation à l’AMAI « Projet Lili-app ». L’application Lili aidera les personnes malvoyantes à trouver et à suivre le meilleur itinéraire à l’aide de leur smartphone. L’application prendra en compte les infrastructures telles que les trottoirs et les passages piétons, ainsi que les aménagements spéciaux tels que les pavés
OpenStreetMap Belgium organise un mapathon à Bruges dans le cadre de notre participation à l’AMAI « Projet Lili-app ». L’application Lili aidera les personnes malvoyantes à trouver et à suivre le meilleur itinéraire à l’aide de leur smartphone. L’application prendra en compte les infrastructures telles que les trottoirs et les passages piétons, ainsi que les aménagements spéciaux tels que les pavés tactiles et les feux de circulation avec signaux sonores.
Dans un premier temps, un prototype de l’application sera développé, limité à la ville de Bruges. Pendant le mapathon, nous ajouterons les infrastructures manquantes à OpenStreetMap. Tout le monde est le bienvenu. Nous aidons les débutants à faire leurs premiers pas. Il y aura également des tâches plus complexes pour les cartographes expérimentés.
Plus d’informations et inscription via MeetUp ou OSMcal. La restauration est assurée pour tous les participants inscrits.
OpenStreetMap Belgium organiseert een mapathon in Brugge als onderdeel van onze deelname aan het AMAI “Lili-app project”. De Lili-app zal mensen met een visuele beperking helpen om de beste route te vinden en te volgen met hun smartphone. De app zal rekening houden met infrastructuur zoals trottoirs en zebrapaden en speciale voorzieningen zoals tactiele bestrating en verkeerslichten met geluidssign
OpenStreetMap Belgium organiseert een mapathon in Brugge als onderdeel van onze deelname aan het AMAI “Lili-app project”. De Lili-app zal mensen met een visuele beperking helpen om de beste route te vinden en te volgen met hun smartphone. De app zal rekening houden met infrastructuur zoals trottoirs en zebrapaden en speciale voorzieningen zoals tactiele bestrating en verkeerslichten met geluidssignalen.
In eerste instantie wordt een prototype van de app ontwikkeld dat beperkt is tot de stad Brugge. Tijdens de mapathon zullen we ontbrekende infrastructuur toevoegen aan OpenStreetMap. Iedereen is welkom. We helpen beginners met hun eerste stappen. Er zullen ook complexere taken zijn voor ervaren mappers.
Meer info en registratie via MeetUp of OSMcal. Catering is voorzien voor alle geregistreerde deelnemers.
OpenStreetMap Belgium is organizing a mapathon in Bruges as part of our participation in the AMAI “Lili-app project”. The Lili-app will help visually impaired people find and follow the best route using their smartphone. The app will take into account infrastructure such as sidewalks and pedestrian crossings and special facilities such as tactile paving and traffic lights with sound signals. Initia
OpenStreetMap Belgium is organizing a mapathon in Bruges as part of our participation in the AMAI “Lili-app project”. The Lili-app will help visually impaired people find and follow the best route using their smartphone. The app will take into account infrastructure such as sidewalks and pedestrian crossings and special facilities such as tactile paving and traffic lights with sound signals.
Initially, a prototype of the app will be developed that is limited to the city of Bruges. During the mapathon, we will add missing infrastructure to OpenStreetMap. Everyone is welcome. We help beginners take their first steps. There will also be more complex tasks for experienced mappers.
More info and registration via MeetUp or OSMcal. Catering is provided for all registered participants.
With OpenStreetMap data becoming ever more relevant, more and more external parties want topics of interest to them to be mapped in great detail. Do you want to help on topics that we care most about? Have a look at the top mapping tasks list on the wiki! Let us just highlight two organizations we are working with. First, Fietsberaad Vlaanderen is integrating their Velopark project with OpenStreetM
With OpenStreetMap data becoming ever more relevant, more and more external parties want topics of interest to them to be mapped in great detail. Do you want to help on topics that we care most about? Have a look at the top mapping tasks list on the wiki!
Let us just highlight two organizations we are working with.
First, Fietsberaad Vlaanderen is integrating their Velopark project with OpenStreetMap. A tool was developed to easily link OSM bicycle parkings to the official data in Velopark. This will in turn make it easier to fully integrate OSM data in their tool. As a little incentive for your contributions, you can apply for volunteer fees if you contribute to the project. More details via the forum.
Second, our corporate member the Belgian National Crisis Centre, intensively uses OpenStreetMap data in their crisis management application Paragon. With help from the community, they already developed the fire station data in OSM to be the best source for this info in Belgium. Current projects focus on:
Hospitals: some hospitals are actually missing a main tag! But mostly the task is about adding official references (which will make it easier to link official data sources) and emergencies entrances
Schools: for Paragon, having schools as polygons is a real added value. OSM is really not complete when it comes to schools! Some were mapped without a name, some are just a point, some are entirely missing
Police stations: a lot of police stations in OSM cannot be found in official data. This is often because the station has closed, or it is not really a police station (but a back-office, a customs office, …)
Les données OpenStreetMap devenant de plus en plus pertinentes, de plus en plus de parties externes souhaitent que les sujets qui les intéressent soient cartographiés de manière très détaillée. Voulez-vous nous aider sur les sujets qui nous tiennent le plus à cœur ? Jetez un coup d’œil à la liste des principales tâches de cartographie sur le wiki ! Permettez-nous de mettre l’accent sur deux organis
Les données OpenStreetMap devenant de plus en plus pertinentes, de plus en plus de parties externes souhaitent que les sujets qui les intéressent soient cartographiés de manière très détaillée. Voulez-vous nous aider sur les sujets qui nous tiennent le plus à cœur ? Jetez un coup d’œil à la liste des principales tâches de cartographie sur le wiki !
Permettez-nous de mettre l’accent sur deux organisations avec lesquelles nous travaillons.
Tout d’abord, Fietsberaad Vlaanderen intègre son projet Velopark à OpenStreetMap. Un outil a été développé pour relier facilement les parkings à vélos OSM aux données officielles de Velopark. Cela facilitera à son tour l’intégration complète des données OSM dans leur outil. En guise d’encouragement pour vos contributions, vous pouvez demander à bénéficier d’une indemnité de bénévolat si vous contribuez au projet. Plus de détails sur le forum.
Deuxièmement, notre membre corporatif, le Centre national de crise belge, utilise intensivement les données OpenStreetMap dans son application de gestion de crise Paragon. Avec l’aide de la communauté, ils ont déjà développé les données sur les casernes de pompiers dans OSM pour en faire la meilleure source d’information en Belgique. Les projets actuels se concentrent sur :
Hôpitaux : certains hôpitaux n’ont pas d’étiquette principale ! Mais il s’agit surtout d’ajouter des références officielles (qui permettront de relier plus facilement les sources de données officielles) et les entrées des urgences.
Schools : pour Paragon, le fait d’avoir des écoles sous forme de polygones est une réelle valeur ajoutée. OSM n’est vraiment pas complet en ce qui concerne les écoles ! Certaines ont été cartographiées sans nom, d’autres ne sont qu’un point, d’autres encore sont entièrement manquantes.
Postes de police : de nombreux postes de police dans OSM ne peuvent pas être trouvés dans les données officielles. Cela est souvent dû au fait que le poste a fermé, ou qu’il ne s’agit pas vraiment d’un poste de police (mais d’un back-office, d’un bureau de douane, …).
Nu OpenStreetMap gegevens steeds relevanter worden, willen steeds meer externe partijen onderwerpen die voor hen van belang zijn gedetailleerd in kaart brengen. Wil je helpen met onderwerpen waar we het meest om geven? Kijk dan eens naar de top mapping tasks lijst op de wiki! Laten we even twee organisaties uitlichten waarmee we samenwerken. Ten eerste, Fietsberaad Vlaanderen integreert hun Velopar
Nu OpenStreetMap gegevens steeds relevanter worden, willen steeds meer externe partijen onderwerpen die voor hen van belang zijn gedetailleerd in kaart brengen. Wil je helpen met onderwerpen waar we het meest om geven? Kijk dan eens naar de top mapping tasks lijst op de wiki!
Laten we even twee organisaties uitlichten waarmee we samenwerken.
Ten eerste, Fietsberaad Vlaanderen integreert hun Velopark project met OpenStreetMap. Er werd een tool ontwikkeld om OSM-fietsparkeerplaatsen gemakkelijk te koppelen aan de officiële gegevens in Velopark. Dit zal het op zijn beurt gemakkelijker maken om OSM-gegevens volledig te integreren in hun tool. Als kleine stimulans voor je bijdragen kun je een vrijwilligersvergoeding aanvragen als je bijdraagt aan het project. Meer details via het forum.
Ten tweede maakt ons lid, het Belgisch Nationaal Crisiscentrum, intensief gebruik van OpenStreetMap-gegevens in hun crisismanagementapplicatie Paragon. Met hulp van de gemeenschap hebben ze de brandweerkazernegegevens in OSM ontwikkeld tot de beste bron voor deze informatie in België. Lopende projecten richten zich op:
Ziekenhuizen: sommige ziekenhuizen missen een hoofdtag! Maar meestal gaat het om het toevoegen van officiële referenties (waardoor het gemakkelijker wordt om officiële gegevensbronnen te koppelen) en spoedingangen.
Scholen: voor Paragon is het hebben van scholen als polygonen een echte toegevoegde waarde. OSM is echt niet compleet als het gaat om scholen! Sommige zijn in kaart gebracht zonder naam, sommige zijn slechts een punt, sommige ontbreken geheel of gedeeltelijk.
Politiebureaus: veel politiebureaus in OSM zijn niet terug te vinden in de officiële gegevens. Dit is vaak omdat het bureau gesloten is, of omdat het niet echt een politiebureau is (maar een back-office, een douanekantoor, …).
OpenStreetMap Blogs
I think the way the pbf was spliced made the large 
►
for FOSSGIS 2025 is now open and can be taken until Sunday 17 November. The results will be included in the programme committee’s evaluation as a community opinion poll.
►
►
►
the source 
Fig.1. Annotated Screenshot Example
