On 19/5/20 8:01 pm, European Water Project wrote:
Thank you all for responding. I've commented in order
Dear François & Jo,
There are 240,000 drinking fountains nodes (with the two tag forms)
tagged globally. Although, your suggestion seems a reasonable one,
unless there is master plan for unique id maintenance, I am loathe to
adding ref tags which might end up being poorly maintained stale
pollution.
Dear Mateusz,
If I understand correctly, I can query the database for historic data
states. For how long is the historic data maintained ? Do all of the
servers below have the historic data ?
'https://lz4.overpass-api.de/api/interpreter';
' https://overpass-api.de/api/interpreter';
'https://overpass.kumi.systems/api/interpreter';
'http://overpass.openstreetmap.fr/api/interpreter';
'https://z.overpass-api.de/api/interpreter';
'https://overpass.nchc.org.tw';
Dear Simon,
What do you mean by "+ version" ? Are you referring to a timestamp or
a something else ?
The version number.
See https://www.openstreetmap.org/way/173244595#map=18/-33.89163/151.27633
Way 173244595 is presently version 13. Version 1 would be when it was
first created.
For ways, which I am only starting to look to consider, maybe I could
look for objects with a similar geometric center for the replacement
object.
Best regards,
Stuart
On Tue, 19 May 2020 at 11:41, Simon Poole <si...@poole.ch
<mailto:si...@poole.ch>> wrote:
It should be noted that (for Nodes) id + version is actually
stable (Ways and Relations are more complicated).
So if you have id + version, you can
- check that it is the current version of the object (all fine and
dandy)
- check if there is a later (undeleted) version, check if it
(depending on your criteria) is still the "same object", update
version in your reference
- if the last version is deleted or your criteria for it being the
same object doesn't hold, search in the vicinity for a replacement
object.
Doing the same for Ways and Relations requires including a
location reference of some kind as geometry changes are not
reflected in the versions, but can work in principle the same.
Simon
Am 19.05.2020 um 09:43 schrieb European Water Project:
Dear All,
I am looking for a way to create permanent links to specific
objects (fountains and cafés) with images within our application
... and I have a couple of questions.
How quickly do OSM node and ways numbers mutate ? What
percentage should I expect to change each year. If the
percentage of ids mutates slowly enough .. maybe this is still
the best bad short term option ?
I was pointed to this wiki :
https://wiki.openstreetmap.org/wiki/Permanent_ID
On the discussion page, it is mentioned that a solution is being
targeted for end 2020 . Will there be a tool to translate actual
osm node and ways numbers to the new permalink ids.
Apparently Mangrove uses GEO URI to create perma links towards
objects. https://en.wikipedia.org/wiki/Geo_URI_scheme. How do
they deal with node repositioning ? I could create a link name
with first 5 latitude num followed by first 5 longitude num...
but as soon as someone moves the node I would get a broken link...
Thanks for your help and advice
Best regards,
Stuart
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org <mailto:Tagging@openstreetmap.org>
https://lists.openstreetmap.org/listinfo/tagging
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org <mailto:Tagging@openstreetmap.org>
https://lists.openstreetmap.org/listinfo/tagging
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
