Welcome to my fifth OpenStreetMap NextGen development diary.
This week has been mostly focused on GPS Traces 🛰.
🔖 You can read my other development diaries here:
osm.org/user/NorthCrab/diary/
🐙 This project is open-source and publicly available:
https://github.com/Zaczero/openstreetmap-ng
GPS Traces Demo
It’s best to experience the refreshed traces in a video form, so I prepared a short demo (no audio):
⏯️ https://files.monicz.dev/osm/traces-demo.mp4
For comparison, here’s how the same trace looks on the current website:
osm.org/user/bielebog/traces/11326871
You will quickly notice the super-fast upload speed and the new trace animations. If there’s something wrong with the file you attached, you will receive instant feedback on the upload page. One new feature is possibility to edit trace name. Previously, this feature has been hidden behind API 0.6.
One more planned feature is rendering the map behind the trace animation. Now that the system works on individual coordinates, it will be fairly easy to implement. Traces without a human-understandable point of reference are not as useful as they could be.
Unified Traces URLs
Let’s start with discussing the current URL routes.
- If you want to access a way, you visit
/way/<ID> - If you want to access a note, you visit
/note/<ID> - If you want to access a trace, you visit
/user/<USER>/traces/<ID>
Which is not consistent. OpenStreetMap-NG unifies this experience by introducing a new URL route: /trace/<ID>. All existing URLs remain backwards compatible and are automatically redirected.
Short-Term Development Plan
There’s just a few things left before reaching the core feature parity with the existing website. Those are the things I want to finish before inviting new contributors ツ.
- Elements sidebar (50% work in progress)
- User Diaries
- User Profiles
- Applications (OAuth) settings


As we announced in a
As we announced in the