Part 1: osm.org/user/Negreheb/diary/405306
Part 2: osm.org/user/Negreheb/diary/406030

360° Mapping Salzburg – Update #3: Better Mounting, Better Coverage

Hello OSM Community,

I’m continuing my effort to capture 360° images of the city of Salzburg for use in Mapillary and Panoramax. The goal remains the same: improve OpenStreetMap data, especially in areas with unresolved notes where better visual context can help.

Progress So Far

Here’s the current state of coverage from my 360° image collection:

My Route Planning Setup

To plan my routes, I’ve been using OSMAnd’s built-in GPX recording and map display. This allows me to see where I’ve already been and make instant decisions on which streets to cover next - without having a router trying to direct me back on track constantly.

I can also choose freely whether to ride on streets, paths, or cycleways depending on conditions. This flexibility has proven much more practical than relying on pre-planned routes.

… See full entry

Hello OSM Community,

I’m still working on capturing 360° images of the city of Salzburg for Mapillary and Panoramax. My goal is to enhance OSM data in Salzburg, especially in areas with notes that could be resolved with better visual context - something 360° images can provide.

Progress as of now

Route Planning Challenges

So, i tried some tools to plan a route efficiently to cover as many streets as possible without overlapping - essentially the Chinese Postman Problem.

• Bikerouter: manual tedious labour involved to cover every street
• everystreet challenge: no GPX download, so useless. No developtment.
• RunEveryStreet: More automated approach, but key features missing and some bugs, and I didn’t get a response to my suggestions unfortunately.

Unfortunately, none of these tools fully met my needs, so i did it more practical.

The Solution I’m Using

… See full entry

Hello OSM Community,

I’m currently working on a project to capture 360° images of the city of Salzburg for Mapillary, and possibly for Panoramax later. My goal is to enhance OSM data in Salzburg, especially in areas with notes that could be resolved with better visual context—something 360° images can provide.

Getting the Camera

I reached out to the OSM Belgium team to ask if I could borrow one of their 360° cameras. To my surprise, they informed me that there was already a GoPro MAX 360 in Austria! After checking with the local OSM chat, it turned out that mcliquid had the camera and kindly offered to send it to me.

Route Planning Challenges

Before starting the project, I wanted to plan an efficient route to cover as many streets as possible without overlapping - essentially the Chinese Postman Problem. Unfortunately, I couldn’t find a tool for this problem.

Initially, I tried bikerouter.de to created a GPX route. After importing it into OSMAnd, I found that it wasn’t working as expected - it tried to auto-route between the points instead of following the plan I made. This wasn’t practical for me for capturing 360° images.

The Solution I’m Using Currently

I eventually opted to use OSMAnd’s built-in recording feature. By activating the setting, I could record my route in real-time and have the GPX displayed directly on the map. This way, while cycling, I could instantly see where I had already been and decide on the fly which streets to cover next. This flexibility worked much better for capturing pictures around Salzburg.

Managing the Photos for Upload

From past experience, I knew that the Mapillary uploader struggles when handling too many files at once, leading to issues that require a full reset of the uploading-tool.

To avoid this, I used PowerShell to split the images into folders of 250 files each, which made the upload much smoother and basically error-free. This small step ensured that I could process and upload my imagery without hiccups.

… See full entry

Hello Community,

Recently, I embarked on a quest to explore second-hand stores and made an intriguing discovery—not only about the variety of hidden treasures but also about the limitations of the existing data in OpenStreetMap.

At the beginning of my search i obviously used OSM to look for second hand shops. I used https://openstreetbrowser.org/ and created a custom category with the code

query: 13: nwr[shop=second_hand]

and discovered that there are just few second-hand stores mapped in my area. I was sure that this is not possible and so i searched the internet to create my own list while cross-referencing various websites, blogs and platforms.

To optimize my exploration, I looked to create an efficient route—the classic Traveling Salesman Problem. There are various tools and APIs that can be utilized for this purpose. After some deliberation, I opted for Routexl, which best suited my needs as its possible to use it for free if you don’t have more than 20 points.

Armed with the list and the route, I got out with my bicycle on two separate days to visit most of the second-hand stores and map them. But my journey didn’t end there. I checked again with the OpenStreetBrowser and and shared it the first time within a local community. The community then showed me another second-hand store specializing in computers—an aspect I had not previously considered, as my focus was on clothing stores.

Now there are two already mapped stores where its not clear if they are still in operation. More research and exploration is required to keep everything recent.

It was interesting to discover how these store did not get mapped previously or did not get any attention even after they got added to OSM. It was a nice experience to find something that might be needed locally.

Lets fill the map with new discoveries!

Generell ist vieles unter den Stichworten Quality assurance zu finden. Hier ein paar Sachen, die ich mir selbst herausgesucht habe.

• osm.wiki/Quality_assurance
• https://www.fossgis.de/konferenz/2011/programm/events/218.de.html

Fehlersuche direkt mit OSM

osm.org rechts Layer anzeigen und unter “Overlays zur Fehlersuche aktivieren” den Punkt “Hinweise/Fehlermeldungen” anwählen.

RSS-Feed einrichten

osm.wiki/DE:Notes#RSS-Feed

Mapper in der Umgebung finden

Vor allem für ländliche Gegenden geeignet, um neue Mapper zu finden. In einer Stadt erscheinen wohl viele Einmalmapper.
http://resultmaps.neis-one.org/oooc?zoom=14&lat=39.1101172&lon=26.5561453&layers=B00FTFT

Externe Quellen

• Geofabrik OSM Inspector - https://tools.geofabrik.de/osmi/
• keep it right - https://www.keepright.at/report_map.php (Tagging kontrolle)
• OSM Relation Analyzer - http://ra.osmsurround.org/
• MapDust - http://www.mapdust.com/ (Über Skobbler erfasste Routingfehler)
• ITO Map - http://product.itoworld.com/map/main (Bestimmte Eigenschaften hervorheben)
• Adressabdeckung - https://osm-austria-building-coverage.thomaskonrad.at/
• RSS-Feed über Changesets anlegen https://tyrasd.github.io/osm-qa-feeds/
• https://osmcha.mapbox.com/

Direkt für Salzburg

• https://www.keepright.at/report_map.php?lang=de&lat=48.1971&lon=11.8043&zoom=14
• http://qa.poole.ch/?zoom=16&lat=48.19747&lon=11.80559&layers=FTTFB0
• http://osmose.openstreetmap.fr/de/map/#zoom=14&lat=47.8254&lon=13.04673&item=xxxx&level=1&tags=&fixable=
• https://osm-suspects.gbconsite.de/map#15/47.8219/13.0427/osm-wrongcity-minimalmissing-wrongstreet-wronghousenumber-outsideplz-falsepositive-dupes

JOSM

• Validator Plugin - osm.wiki/JOSM/Validator

Overpass

• https://overpass-turbo.eu/ Mit diesem Tool können eigenen Suchanfragen abgesetzt werden, allerdings wird hier Code benötigt. Beispiele:
  osm.wiki/DE:Overpass_API/Beispielsammlung

Meine Zusammenfassung über das, was ich oft benötige und eine Info an andere, wieso ich etwas wie tagge. Bei Kritik gern kommentieren.

Generell gilt: Nur weil ich “meine” Variante für besser halte, lösche oder ändere ich nach Möglichkeit keine falschen Tags. Ist etwas falsch eingetrag und wird im Zuge dessen geändert, werden auch die Tags angepasst.

Statistiken zu dem, was ich gemacht habe: http://www.hdyc.neis-one.org/?Firefishy

Daten sammeln

Unter anderem mit http://fieldpapers.org/ oder rein für Hausnummern bzw. Adressen - Streeetcomplete. Vespucci von F-Droid wird untersucht. Generelle Infos zum Drucken auf Papier osm.wiki/OSM_on_Paper

Adressen

osm.wiki/Addresses Bei Gebäuden mit mehr als 2 Adressen (Eckgebäude) wird laut meiner Info z. B. von der Post die Adresse als Hauptadresse verwendet, die auf der Hausmauer des Haupteinganges ist.

Freistehendes Gebäude

z. B. Einfamilienhaus

• Grundsätzlich am Gebäudepolygon
• Wenn möglich mit entrance=yes (oder =main) und Adresse darauf

Zusammenhängende Gebäude

z. B. Wohnblock

• wenn optisch klar getrennt(Unterschiedliche Dachfarbe, Geometrie), Gebäudepolygon getrennt und Adresse ans Polygon
• wenn optisch nicht klar getrennt, ein Gebäudepolygon mit Adresse an entrance=yes node

Straßen

Gehsteige

~~Ich tagge das ganze doppelt:~~

1. footway vorhanden aber nicht wirklich baulich getrennt: Straße mit sidewalk=both/left/right zur Straße
2. footway vorhanden mit klarer baulichen Trennung z. B. Grünstreifen, Gebüsch, …: extra Weg zeichnen, footway=sidewalk, Straße mit sidewalk=seperat
3. außerorts, wenn der Pfad nicht wirklich parallel zur Straße verläuft: foot=use_sidepath
4. kein Gehsteig, Fußgänger muss am Grünstreifen gehen: sidewalk=no
5. foot=no nur, wenn es durch entsprechende Verkehrszeichen angezeigt wird. Auf Autobahnen und Kraftfahrstraßen ist das default.

… See full entry