OpenStreetMap

tyr_asd has commented on the following diary entries

Post When Comment
Latest Changes 2 months ago

But the area actually contains an object that was modified in the changeset: https://www.openstreetmap.org/way/101781403 (a typo in the tag contact:website was fixed). Not sure why it doesn't show up on "the changesets viewer in JOSM" (btw: never heard about this, is it a new plugin?) … maybe it's a bug/deficiency on their part?

Latest Changes 2 months ago

It could be improved by focusing on only data modified in the area.

@PierZen: I'm not sure if I got your message right, but the Latest-Changes tool should already do exactly what you suggested. Also, I can't seem to get the mentioned changeset popping up when opening the latest-changes link you posted…

How do you classify land use on OSM? Do you believe you could do it well? 4 months ago

same here :-/

History of all Tags 6 months ago

Yes, sure. But one of my main design goals for this tool was to avoid having to set up and run any kind of database containing the full OSM data, so that's not really an option for me, unfortunately.

But if anyone out there already runs a (daily) updated OSM DB which could produce deltas of the counts of tags in their db (for little extra processing cost), please contact me – I'd love to use that data for updating the taghistory service.

History of all Tags 6 months ago

@SafwatHalaby: yes, but regular planet diffs don't contain all necessary data to keep this kind of data up to date (because they don't include the tags the modified osm objects had before the diff). Overpass' augmented diffs could in principle work, but they have other technical issues, see: https://github.com/tyrasd/taghistory/issues/10

10 years of OSM data history 6 months ago

Right. I've changed the wording now. :)

Btw: I managed to find the pre-rails ruby code of the website/api you pointed at earlier: https://trac.openstreetmap.org/browser/subversion/sites/www.openstreetmap.org/ruby/api/osm/dao.rb?rev=2808#L1062 which seems to correspond to OSM's API version 0.3 (while the rails-port started at version 0.4 afaics).

10 years of OSM data history 6 months ago

Thanks for the clarification and background information, Richard! (But what exactly do you think is not quite accurate in my text?)

RTK test, Aerial pictures accuracy, and OSM Database Accuracy 7 months ago

Very impressive!

Btw: 7 decimal digits already correspond to about 1.1cm.

Odd brown area 7 months ago

Aha! Here we probably have our bad boy: https://www.openstreetmap.org/way/512314784 (a building with one node in Vienna and the rest of its nodes in Zambia).

Odd brown area 7 months ago

@maxerickson: If that was the case, could it also explain that this glitch is only visible on zoom 19 and not on any other zoom level?

Odd brown area 7 months ago

wow, that's odd.

The brown area has an apparently horizontal edge (at a latitude of approximately 40.13558) when you follow it from here eastwards (up until a longitude of ~27.47677), and a regular zig-zag structure in southwards direction. Towards the north-west it looks "randomly glitchy".

Better Walking Papers 10 months ago

Very cool, but a main killer feature from the original walking papers is missing here (as far as I can see): the ability to automatically georeference scanned-in walking papers to quickly have them in an OSM editor as a background layer.

OSM Node Density – 2017 10 months ago

@Jedrzej Pelka: You mean the short flash of a black screen when switching layers, right? Does it look better now? I've now actually added in a bit of fading to make the layer switching smoother.

@imagico: Right. But I'm not sure if Joost (or anyone else) has already had time to actually look into it, though.

Sync your overpass queries with your osm account 10 months ago

@Zverik yeah, I think so.

Sync your overpass queries with your osm account 10 months ago

@CloCkWeRX: There's already a ticket for that on github: #219.

Better Maps - The riverbank and the bridge/forest 12 months ago

JOSM's ContourMerge plugin can also be quite helpful in such situations (especially if you want to avoid creating "unnecessary" multipolygon relations for areas without actual holes): First, split the forest very roughly along the river, unglue the middle section and use ContourMerge to join the two forest halves with the respective riverbank outlines.

Visualizing OSM.org's Map Views about 1 year ago

PS: For those interested in the technical implementation details: Recently I've switched out Vladimir Agafonkin's rbush library with his kdbush implementation, which offers even faster indexing, resulting shaving off another few seconds of startup times. Awesome stuff!

OSM Node Density – 2016 Update about 1 year ago

Jennings, I think I just run the commands as explained here (I'm not sure why it reads zoom=16 here – this should also be 15 or lower). That generates a 1 gigapixel (32768x32768) density map, which cut into tiles corresponds to max zoom level 7 on the slippy map: http://tyrasd.github.io/osm-node-density/#7/-7.961/-248.373/latest,places

I tried to use my tms tile source https://s3-eu-west-1.amazonaws.com/osm-node-density/2016/{z}/{x}/{y}.png with mapboxgl as well, and see similarly blurry results. Not sure what's going on. Maybe it's related to https://github.com/mapbox/mapbox-gl-js/issues/4552?

Preparing accurate history and caching changesets about 1 year ago

Hey. Great work and thanks for providing this as a service!

PS: are the cached (raw) augmented diffs also publicly available?

Lets have changeset mentions about 1 year ago

Biggest problem is probably finding unambigous syntax for all the sorts of mentions (node/way/relation/changeset/user) that people want.

What about just using URIs as identifiers? Github shortens typed URLs to other tickets: http://github.com/project/issues/123 becomes #123. That should work for us as well (e.g. http://www.openstreetmap.org/<type>/<id> becomes type/id or something similar). For user mentions the @username pattern is already a well established.