On Fri, Aug 5, 2011 at 2:15 PM, Gregor Horvath gre...@ediwo.com wrote:
I am not a native English speaker, so if new_id is better than
superseded_by than I vote for new_id.
Regarding the added semantics I am very cautious. Because it will be
impossible to model all semantics of ID meaning
Steve Bennett wrote:
In general I think there's some value in what you're describing here,
not just for id stability, but in better understanding the history and
provenance of objects, which helps with attributing authorship. Some
sort of more generic meta-tagging scheme might be good
Hi,
I have thought through this again and think we should keep it simple and
stupid (KISS):
Am Wed, 3 Aug 2011 20:36:38 +0200
schrieb Gregor Horvath gre...@ediwo.com:
** splitting of ways (old ID would then point to only half)
A split to A,B:
A.superseded_by = B
A does not get
Hi Steve,
Am Thu, 4 Aug 2011 10:56:49 +1000
schrieb Steve Bennett stevag...@gmail.com:
In general I think there's some value in what you're describing here,
not just for id stability, but in better understanding the history and
provenance of objects, which helps with attributing authorship.
Hi,
critique welcome:
Proposal superseded_by tag
--
OSM ID's do not describe physical objects but geometrical objects on a
map. If an a geometrical object supersedes another one with a different
ID it should be possible to tag this relationship for some better
Hi,
I must say wow, as I did not expect my mail to trigger such a long
discussion, that even already brings up proposals. I was busy with some
tasks and therefore did not reply in the past three days.
But its great to see such response ;)
So as it was pointed out multiple times already,
On Thu, Aug 4, 2011 at 4:36 AM, Gregor Horvath gre...@ediwo.com wrote:
** re-mapping of stuff in the course of the license change
- re-structuring of relations
- 0.7 area data type (lots of existing areas get a new ID)
superseded_by tag
That's an interesting use case - let's say A
7 matches
Mail list logo
