[Tagging] Merging tagging scheme on wiki pages of Hiking, route=hiking, route=foot and Walking routes

Peter Elderson pelderson at gmail.com
Thu Aug 15 15:55:32 UTC 2019

I do it a lot. Take it from me and all other route maintainers - You can't
maintain long routes with ID.

Most of the damage is done by other things then deletion. E.g. shifting a
way, connecting ways, extending a way, shortening a way, closing a way,
cutting a way.

Vr gr Peter Elderson

Op do 15 aug. 2019 om 17:39 schreef Paul Allen <pla16021 at gmail.com>:

> On Thu, 15 Aug 2019 at 16:20, Peter Elderson <pelderson at gmail.com> wrote:
>> Still most problems arise because ID edits damage routes.
> iD used to damage routes in the past.  After an update a couple of months
> ago it seems
> to now maintain the sorting of routes, even if you insert or delete
> elements.
>> The mappers aren't even aware of the problems, and even if they were, I
>> can't see how they could repair broken and unordered routes of several
>> hundreds up to several thousands of members with ID.
> The way it used to be, I don't think they could repair unordered routes
> with only two members,
> using iD.  That changed.  There's still no automatic sort (that I've
> found) but you can manually
> re-order route members.  And in some ways it makes tracing routes easier
> than jOSM when
> you have routes where ways are traversed more than once in the same
> direction.
> For those wondering, with long routes with segments of different lengths,
> the "zoom to" feature
> of jOSM and (new) iD is useful.  But with ways that appear more than once,
> if you zoomed to
> a second (or third, or fourth) occurrence of a way in a route then jOSM
> reset your place in the
> list of ways to th first occurrence in the list, not the occurrence you
> were looking at.  Not helpful
> when you're checking the connectivity of the whole route, especially if
> you didn't notice it
> happened.  iD doesn't silently change where you are in the list when you
> zoom to the
> 100th way in the list just because that way is also in the list at the
> 37th position.
> I think ID does a fine job, all in all, but preserve, repair and maintain
>> route relations cannot be done with ID.
> I haven't played with it enough to be sure, but it seems no longer to
> damage routes if you
> add or remove members, and you can re-order the members. I find the new
> functionality
> makes it easier to inspect routes than with jOSM.  But maybe I haven't
> used a complex enough route
> as a test case, and in some cases it still damages routes.  But it's
> definitely not as bad as it was.
> --
> Paul
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20190815/afa3f9a8/attachment.html>

More information about the Tagging mailing list