Better test case is "node/1" (
https://blog.openstreetmap.org/2015/12/25/openstreetmappy-christmas/ )
* https://www.openstreetmap.org/node/1/history
2018-03-06 11:26 GMT+01:00 Frederik Ramm :
> Hi,
>
> we're all concerned about the environment these days. "Reduce, Reuse,
>
@Yves unfortunately would be hard to implement as reverting
reuses/undeletes the object if I'm not mistaken. So someone could just
undelete a node than move it to where they need to.
On Mar 6, 2018 5:47 AM, "Yves" wrote:
> Hi Frederik,
> For my curiosity, is it a feature of
2018-03-06 11:43 GMT+01:00 Yves :
> Hi Frederik,
> For my curiosity, is it a feature of the API to:
> _ allow users to choose an ID?
>
sure, you need this for any modification. Just upload a new version of a
deleted object and you resurrected it.
Cheers,
Martin
On 06/03/18 10:26, Frederik Ramm wrote:
Long story short, please don't do it - let the API assign you new node
IDs to your stuff instead of building ingenious contraptions to recycle
old nodes.
The reality is they are not 'old nodes' simply nodes which are not
currently visible. I think I
Hi Frederik,
For my curiosity, is it a feature of the API to:
_ allow users to choose an ID?
_ not re-assign an old ID?
Yves
Le 6 mars 2018 11:26:55 GMT+01:00, Frederik Ramm a écrit :
>Hi,
>
>we're all concerned about the environment these days. "Reduce, Reuse,
>Recycle"
Hi,
we're all concerned about the environment these days. "Reduce, Reuse,
Recycle" is certainly something to strive for in the real world out there.
However, for the second time now I've encountered a user who thought it
was a good idea to reclaim old node IDs for new edits. A couple of
6 matches
Mail list logo