could use*

Hi,

Clicking “help” in Achavi reveals the following: “A single changeset can be visualized by drag & drop of a changeset URL or using a bookmarklet”. Drag and drop does not work. and I wanted something a non tech-savvy user could and which is convenient on mobile. This rules out link editing or bookmarklets.

For the record, We (Israel) are mapping military bases that are public knowledge. But it seems some mappers prefer not mapping the inner details. Old extensive discussion here: https://forum.openstreetmap.org/viewtopic.php?id=3820

I think in theory you can have all the info. - An initial OSM DB populated from a planet file starting from where you’ve ceased updating your current data - When a new diff arrive, the old state of each node is in your OSM DB, and the new state can be extracted from the diff. These are used to update the statistics. - Apply the diff to the OSM DB planet file, and now you can repeat the process the next day.

I don’t know how easy or complicated that’d be in practice.

Spam.

Please stop spamming. Openstreetmap is not for ads.

@tyr_asd have you considered processing daily planet diffs?

I added this to the quality assurance page: osm.wiki/Quality_assurance#OSM_Tag_History

Thanks!

I like rorym’s hierarchy system.

@Tordanik, that would be a problem, because a single bucket allows a single value, and sometimes you need more. think: amenity=park, surface=grass.

@rorym alternatively, one might argue that “building” is not an “artificial bucket”, so the traditional key-value system would still be used for buildings.

I agree that the current system is probably good enough :)

@rorym, I would say there is a difference between, say, “building” and “landuse”.

The former is not what I would describe as an “artificial bucket”, it’s actually a useful, real world piece of data, while the latter is an artificial construct with little use on its own (this is why we see many building=yes but rarely landuse=yes).

Since “building” is a useful attribute, the building could be tagged [“building”, “gazebo”], and a generic building can be tagged [“building”] rather than building=yes. This is why I suggested [shop, florist, watches]. The shop part is useful for a data consumer, even if it doesn’t care about or doesn’t recognize florist,watches.

@Piskvor I clearly said that traditional tagging is required for some values. Numbers fall into that category.