just faced this kind of error when closing turns on random roads and saving local changes. Everything else is working fine. Can somebody advise how to fix this problem?
We are using docker version of editor 2.27.3 + postgresql DB + Latvian map
Hello, Mystic Meg here. “2.27.3” looks like an iD version number, but I’ve no idea why you are using “docker version” - what different functionality does it have to regular iD and where does “postgresql DB” fit in? Which “Latvian map” is it - is it one I can see in regular iD?
1556950 is a cycle route that meanders through Latvia and Estonia. My guess is that either (a) someone else has edited part of that cycle route while you were editing and deleted a member or (b) something has gone wrong in the special version of your editor. The relation was last edit 10 days ago, which suggests (a) is less likely to be the issue.
Hi Mystic Meg, we are using serveral map editors on one Linux OS so we need to use docker in our case. All instructions was from this manual openstreetmap-website/DOCKER.md at master · openstreetmap/openstreetmap-website · GitHub . Latvian Map - pbf file was downloaded and pushed to editor from Geofabric resource. All needed functions are working except saving changes from turn restrictions as privided in screenshot. Map editor and frontend is our internal resource so we do not publish it to internet and use it for our project.
OK, so (still guessing here) you’re not editing the OpenStreetMap database at all - you’re editing your own shared copy of it? Do the results of that find their way into OpenStreetMap at some later stage somehow?
It’s something that looks a bit like the “iD” editor - is it, and have you modified that in any way?
If the question was from a regular iD user I’d suspect that two people have modified the same relation (specifically, one has deleted an object that is part of the relation that the other has downloaded), and that the user with the problem needs to undo past their changes to the relation, save, and then in a new session go forward again (so that they will download a new copy of the relation).
Hi, sounds like you’re creating your own database that’s derived from OSM data. Just making sure you’re aware of the ODbL license terms that apply in this case.
- Where you make our data or any Derivative Database available to others, it must continue to be licensed under the ODbL. This is often referred to as Share-Alike.
- If you create a Produced Work, you can apply whatever terms you like to the Produced Work, but you must upon request offer recipients either a copy of your data and any Derivative Databases under the terms of the ODbL or the means of creating the Derivative Databases upon request.
- You must attribute the use of our data in both of the above cases.
1 Like