OpenStreetMap
OSM Perfect Intersection Editor official launch announcement
Posted by Mikhail Kuzin on 13 October 2025 in English. Last updated on 14 October 2025.Good day, friends!
We’re excited to announce the official launch of our OSM editor.
OSMPIE — OSM Perfect Intersection Editor
This specialized editor helps users efficiently add and correct road and intersection data.
The application enables you to:
- Visualize roads and intersections based on the OSM semantic model.
- Verify tags and road structures — inaccuracies and inconsistencies are instantly visible.
- Share links to your edits for discussion and review before uploading data to OSM.
- Export render data to GeoJSON.
The OSM semantic model is almost perfect but lacks a few elements for creating truly flawless intersections. OSMPIE provides several specific tags and extensions for existing ones. Their syntax and application are detailed in the documentation, which includes compelling examples.
Explore the key features:
- Detailed rendering of lane graphs and area road models.
- Comprehensive changeset viewer with git-style comparison.
- Dynamic positioning on modified objects with change highlighting.
- Before-and-after visualization of edits.
- Automatic correction of public transport routes and more.
- Support for custom tiles for high-quality road rendering.
- Easy sharing of your work.
- GeoJSON export of graphs and polygons, plus direct API access.
Visit our website: https://osmpie.org to discover the editor’s full capabilities and learn how to use it.
GitHub: https://github.com/kuzinmv/osmpie-doc/tree/master — submit bug reports and feature requests here.
Subscribe to our Telegram news channel: https://t.me/OSMPIE .
Join our Telegram chat: https://t.me/+PlcXv3TETBkyYzUy for quick assistance and answers to your questions.
We look forward to discussing smooth roads and proper intersections in OSM with you in this thread.
Discussion
Comment from catgirlseraid on 15 October 2025 at 00:28
It seems to break quite badly in left hand drive countries, not accounting for the difference in driving sides of the road. If lane count isn’t set its assumed to be one which doesn’t make sense when a road isn’t tagged as one way. this leads to some very confusing situations such as the sample intersection below.
Comment from Mikhail Kuzin on 15 October 2025 at 02:27
Hello, sorry, but the system isn’t yet fully adapted for left-hand traffic. We understand this, and I think we’ll work on it as soon as possible (but it’s a complex task).
As for how to render a situation where the number of lanes isn’t marked at all, even though it’s a two-way road, based on our limited experience with mapping and various options, we’ve adopted the one that’s common in our area.
As a rule, these roads don’t look like the ones you’re showing. The one you’ve shown is a more complex intersection, and osmpie just pointed out that more tags are needed to ensure the display is correct.
We’d be grateful if you could provide links or examples of roads where lanes and onways aren’t marked, and how such a road would be correctly displayed in most cases.
I would be grateful if next time you add a link to bake (or bakeID), sometimes it’s difficult to find the place from a screenshot.
https://osmpie.org/app/s/ed00be681dd642cdbebf076a07e194bf
Comment from catgirlseraid on 15 October 2025 at 02:35
Thanks for your reply! I’m happy to help out with testing if needed. I didn’t supply a link to the intersection as i fixed the lane tags afterwards, but here’s another nearby example osm.org/#map=19/-41.336413/173.181508
Perhaps defaults for amount of lanes if untagged based off countries could be a good idea but that might be a lot to manage. Have you considered if you aren’t already, defaulting to a different amount of lanes based off what type of highway it is?
Looks like an awesome tool and I’m excited to watch its development.
Comment from Mikhail Kuzin on 15 October 2025 at 03:08
There are three key components to OSMPIE: - OSM sematic model parser - Estimate (Heruistics) - Rendering
And currently, 2 & 3 are hardcoded, meaning the end user has no control over these processes. The user can only influence the structure of objects and tags.(1)
Of course, we realized almost immediately that some customization would be needed to ensure the user sees the closest possible result, depending on the location they’re in.
For example, bus stops (platforms) in Germany and the USA are rendered backwards from the stop position, while in Russia, they’re typically rendered in both directions (backwards and forwards). There are countries that adhere to the Vienna Convention, and there are all the others, plus, of course, right-hand traffic, with its own nuances. + Different types of markings that perform the same functions. For example, in Russia, bus lanes are separated by a solid line, while in Germany they may not be separated at all, or by a dashed line, etc.
Therefore, we assumed that there would be some complex settings for each user that would affect both rendering and estimation. But this was impossible to achieve in the first version. This is only for the community that is accustomed to this type of app and understands the concepts. In the first version, we tried to simplify the UI, entities, and settings as much as possible.
Comment from jakecopp on 15 October 2025 at 06:00
Is the editor closed source? The Github link seems to be to documentation rather than code.
FYI the Terms and Conditions and Privacy Policy links at the bottom of https://osmpie.org/ are broken.
Comment from Mikhail Kuzin on 15 October 2025 at 07:15
Yes, the code is closed, and we don’t yet understand why we should open it. There are also some technical difficulties – OSMPIE has grown out of our products and is now a separate application, but a mono repository complicates things.
Thanks… we’ll definitely add information there when we figure out what needs to be written there. )))
Comment from Kovoschiz on 15 October 2025 at 11:11
Diary doesn’t work for proper high visibility discussion. I’m not using Telegram either, as it’s tied to phone number, not allowing organizing different identities with OSM. I have created a post detailing the problems here. https://community.openstreetmap.org/t/complaint-and-criticism-against-osmpie-for-redefining-and-promoting-poorly-thought-tags-without-discussing-and-annoucing-clearly/136885