Something I didn’t understand while viewing the github page.
Why is it a goal to bypass OSMF redactions ?
(“Tag redactions” was marked as done and “geometry redactions” was marked as not yet done)
Redactions greatly interfere with the display of edit geometry and hinder understanding of the past. OSMCha and Achavi don’t encounter this problem because they use their own database and Overpass, which don’t synchronize redactions. This means that if you’re viewing the history of a way/relation or changeset, the script may show you the incorrect state of an object. In practice, this rarely prevents us from drawing the right conclusions, but still.
In theory, it’s possible to make a fallback to the Overpass API, but even Overpass isn’t always all-powerful.
For example, if we’re talking about objects hidden in 2012, when the license changed. Yes, the OSM website isn’t allowed to show these objects, but ultimately, we sacrificed the integrity of the database history. I wanted to create a tool that could display changesets for any time.
As a result, all viewers make compromises:
- Anything based on Overpass will lag on large bboxes and won’t work if Overpass breaks. And it won’t show any changes made before 2012.
- OSMCha has to have its own database and can quickly display only the latest changesets. If unsuccessful, fallback to Overpass
- Result Maps has to have its own database and shows edits only for the last month
- FacilMap and Easy_Changeset_Viewer are close in implementation to the script, but also suffer from redactions and lack of optimization
- better-osm-org is additionally sensitive to changes on the osm.org
By the way, if you know of any tools that are useful to have links to, please let me know.
For example, I’m currently challenging myself to write a visualizer for the full history of relation geometry. None of the tools I know of can display intermediate versions. Not all can even show a simple history of big relations.
1 Like
1.3.2 a little spontaneous update:
-
The Edit menu now has a link to the new editor OSMPIE
-
I’m tired of watching the voting process on the wiki and counting the votes manually, so now the script is trying to show the intermediate voting results.
11 Likes
…why? It’s nowhere close to being finished at this point (and its UI is still too clunky)
At least there is an interesting render. Well, it’s in this menu for the same reason as Rapid.
I can guess that you are skeptical about this editor, so:
- You can disable both Rapid and OSMPIE in the settings (item:
Add new editors into Edit menu) - Use
EandShift+Eto open iD and JOSM without opening this menu.
I am also aware of disputes in the tagging scheme and have even reported problems with broken route relations. But since the script is not an OSM website that is used by beginners who may not be aware of problems, I think you will check your edits in this editor.
I also have a small personal reason: I am very sad to see how we spent a lot of time on bureaucracy Proposal - OSM.org Editor Inclusion Policy Updated Proposal - OSM.org Editor Inclusion Policy - Draft 2 (200+ messages!)
instead of allowing mappers to add whatever links and editors they want.