I am creating hiking routes for some of the trails in my area. Several of these trails include an "entry" way from the trailhead to a loop. After completing the loop, one walks back to the trailhead along the "entry" way in the opposite direction. I am not sure about the correct way to represent this in the route.

It seems like I should add the "entry" way twice, once at the beginning of the route and once at the end. JSOM gives me an warning when adding it twice, but lets me. Second time, the hike in in the opposite direction of the way, and seems like it would be appropriate to "reverse" the way for this (to keep the elevation plots/navigation correct). I tried applying the role "backward" and "reverse", but JSOM gives warnings for both. And "backward" appears to be defined to mean ONLY in the direction opposite the way (but I want to use the way in both directions). https://wiki.openstreetmap.org/wiki/Relation:route

Here is a route where I used the role "backward" for the second pass along the "entry" way
https://www.openstreetmap.org/relation/11965330

Here is a route where I reused the "entry" way without a role:
https://www.openstreetmap.org/relation/11965331

Guidance for the best practice? (and any other suggestions for these routes)

Thanks

asked 01 Dec '20, 04:27

TroyH's gravatar image

TroyH
4125
accept rate: 0%

JOSM gives a prompt regardless when you add a member twice. This is about editing. It's less of a "warning" as validator ones.

(01 Dec '20, 20:50) Kovoschiz

I agree with Kovoschiz, I would see this warning as JOSM prompting you to check that you really did intend to add the member twice, rather than suggesting it is an error.

As far as I am aware, it is fine to add ways twice to hiking routes if that is how you would walk the route in reality. The "meaning" of the double appearance is implied by the order of the members. Here is a slightly different example where I mapped a short trail that requires one section in the middle of the route to be walked twice to reach a viewpoint and return: https://hiking.waymarkedtrails.org/#route?id=7157490&map=18!36.725!-4.4078 . It seems to work OK, e.g. waymarkedtrails correctly works out the mapped length counting this section twice.

If you feel the entry way is more like a way of getting to the "real" route rather than fully part of the route, then you could consider using the approach role as InsertUser mentioned. There is more on roles here: https://wiki.openstreetmap.org/wiki/Proposed_features/Recreational_route_relation_roles . These roles are relatively new. Possibly if I was mapping my above example now I would consider the "excursion" role for the repeated section.

(02 Dec '20, 08:05) alan_gr

The pages for hiking and foot routes suggests that the approach role can be used for paths back to parking etc.

The forward and backward roles were once the generally accepted tagging for single direction parts of public transport routes (often a loop at the end) and would refer to the direction the bus/tram etc. travelled relative to the direction the way is drawn in OSM. In many areas the less ambiguous but more difficult to edit PTv2 is preferred and documentation of the older relation style is getting more difficult to find. The page you linked suggests that these roles may still be in use for cycle routes.

permanent link

answered 01 Dec '20, 08:41

InsertUser's gravatar image

InsertUser
7.7k647128
accept rate: 20%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×162
×36
×9
×3

question asked: 01 Dec '20, 04:27

question was seen: 226 times

last updated: 02 Dec '20, 08:06

powered by OSQA