Du kannst das ja schon auch hier oder im Forum auf Deutsch melden, mit der Bitte das weiterzuleiten.

… findet diesen auslösenden Issue und dazugehörigen Pull Request:

• Nested lists are incorrectly displayed in user messaging interface · Issue #2103
• Switch to using kramdown for markdown formatting by tomhughes · Pull Request #2111

Da wurde nicht Markdown durch kramdown, sondern ein Markdown Renderer “redcarpet” durch einen anderen Markdown Renderer “kramdown” ersetzt.

Warum sind viele Grafik-verlinkungen in OSM-Blogs nun seit Tagen kaputt, und warum merkt das keiner der Verantwortlichen und/oder fühlt sich verantwortlich?

Und warum meldest Du das nicht einfach?

Zumindest sind die groben Beleidigungen raus. Wäre schön, wenn Du das nächste Mal eine Nacht drüber schlafen und den abfälligen Ton weglassen könntest.

Keine Ahnung, was das soll und wo das kommuniziert wurde, es interessiert mich auch nicht.

Schade, denn dann hättest Du gesehen, dass das alles gar nicht so abwegig und willkürlich war, wie hier dargestellt.

Eine kurze Suche nach “kramdown” auf https://github.com/openstreetmap/openstreetmap-website

Also unsere Admins und Mitstreiter beleidigen geht gar nicht, egal aus welchem Grund. Bitte alle Schimpfwörter und Beleidigungen komplett entfernen.

Thanks for sharing.

I always thought that it would be nice to replace those routes wiki tables with dynamically generated ones in HTML/JavaScript.

There was an attempt to add a table tab to Overpass Turbo, but unfortunately didn’t complete.

Or a dedicated web page that can list relations of a given type for a specific area, e.g. using DataTables or similar, and maybe show a map next to it. Completion percentage could be calculated from the distance tag and the actual length of the way members.

Meines Wissens sind nur die Gebäude von OSM, Straßen weiterhin von HERE: https://wego.here.com/?map=50.98022,11.3689,15,normal

Waymarked Trails can search for route relations: https://hiking.waymarkedtrails.org/#search?query=H%C3%A4rn%C3%B6

An alternative for administrative boundaries might be downloading already compiled geometries from the Boundaries Map (not sure if incomplete relations are included).

For ongoing monitoring there is the daily Missing Boundaries report (maybe scraping and filtering for relations of interest).

Update: issue #4552 is fixed in Release v0.44.0.

Thanks for the example. Nice gimmick transitioning the saturation.

• The OSM tiles are raster which are rendered at discrete zoom levels, but the GL interface allows for smooth scrolling. The result might be slightly blurry tiles and may not be as crisp as viewing them in Leaflet.

Not sure if above quote is implying this: not only scaled tiles at fractional zooms are blurry as expected, but currently on some environments also at discrete zoom levels, see issue #4552 Raster tiles aren’t perfectly crisp at integer zoom levels.

Drag & drop of a changeset URL works for me with Firefox and Chrome on Ubuntu (but might not work this way on mobile).

Given achavi already open in a separate window and a link to an osm.org changeset, e.g. https://www.openstreetmap.org/changeset/53657054:

• instead of clicking the link, drag it onto the map in achavi in the other window
• or on the osm.org changeset page drag the icon on the left of the address bar onto the map in achavi in the other window, similar to creating a desktop shortcut

It might be useful to also add OSMCha and changeset-map to your page:

• https://osmcha.mapbox.com/changesets/53657054
• https://osmlab.github.io/changeset-map/#53657054

There is also still the Map of Turn Restrictions by Zartbitter, it just moved to a new location (formerly at map.comlu.com). I updated the link at Relation:restriction > Tools.

and https://lists.openstreetmap.org/pipermail/talk/2015-July/073516.html

See also https://twitter.com/penorman/status/621965005454336000

I fear there is no easy solution.

Haven’t used any of this, just some ideas:

1. tippecanoe to aggragate/simplify into vector tiles
2. full history planet has all versions of an object (version=”1” = added, visible=”false” = deleted). Osmium library can read the history planet, e.g. by: * converting to OPL File Format (text) + Unix tools (grep, …)
   http://docs.osmcode.org/opl-file-format-manual/
   http://media.jochentopf.com/media/2014-06-15-talk-sotmeu2014-osmium-en-slides.pdf p. 16ff (videos see bottom http://osmcode.org/docs.html) * writing a handler for Node.js/Python Bindings or C++
   http://blog.jochentopf.com/2015-09-02-osmium-is-growing-up.html
3. maybe a public WMS server has a projection you like, OpenLayers 3 gets client-side raster reprojection

You can see how geometries changed by comparing old (dark, brownish red) and new (green) geometries (see legend). Highlighting only the changed segments is not implemented yet. Turning the “changes” layer off and on might help. For ways, added, deleted or moved nodes are shown. You might need to zoom in as nodes and old geometries are not shown on lower zoom levels for perfomance reasons.

Yes, it can handle and visualize deletes and delete-only changesets (example).

The problem with regular OSM data is that deleted elements are not included (only in full history planet) and regular diffs (OsmChange format) have delete information but without geometry (node lat/lon or way nodes are missing).

For the server part, achavi is relying on the Overpass API - where all the hard work is done - and it’s Augmented_Diffs (now using the adiff query) that contain the old version with geometry for modified and deleted objects.

The previous Overpass version created augmented diff files by gathering the state of all changed objects before applying the minutely diffs. The new Overpass attic feature keeps a complete version history since the license change and creates augmented diffs on-the-fly.

Yes, “changed geometry” is one of the main missing features, that’s what I meant with “highlight only changed segments” in the Future section.

I have no idea how many changesets it can handle, but OpenLayers 2.x is not good at handling many features, that’s one reason why there is the OL3 rewrite. The idea is to switch to Leaflet, but not highest priority right now. Reading from planet.osm is not really supported, Overpass augmented diff is the only format that will be supported.

I have set a loading limit of 50M characters because larger XML files were crashing the Browser, there will be a console error when reached.

RSS would need to be provided by a separate service, as achavi is a pure client-side JS project relying on the Overpass API. And Overpass API doesn’t have changeset meta data yet (I’m using the OSM API for the single changeset feature), so changeset comments would be a missing piece for RSS and in comparison to the OWL history list.

Also, I wouldn’t say “completely replace” as OWL was meant to be integrated into openstreetmap.org which achavi clearly is not. But I guess it can serve the same purpose, just with a different approach.

I’m still amazed that OWL is now actually showing detailed changes.

Also excited to hear about plans for vector tiles.

What are the plans for the OWL Viewer? When I first saw it showing change geometries, I thought there might be some synergies with the Augmented Change Viewer I’m working on. But after the switch to Leaflet I’m not so sure anymore.