I've update a local hiking trail in OSM, which required breaking it into smaller segments (ways), so that the smaller segments could be appropriately tagged with track/path, surface, bridge, etc. At the same time, I wanted to add overall trail information: name, ref, maintainer, etc. Rather than add that information to each individual segment, I created a Hiking Route relation to contain all the segments, and added the trail info to that. However, when the OSM map tiles refreshed, the trail name no longer rendered. It must only render the name of the way, not a relation that it is part of. This made me wonder if I did the wrong thing.

What is the correct way to do this? Should the trail info be duplicated on each segment?

For some trail systems in the area there are segments that are considered part of multiple routes, which would be possible to represent with the route approach.

What is the best practice advice for this?

asked 14 Sep '15, 23:27

Elerius's gravatar image

Elerius
56114
accept rate: 0%

edited 15 Sep '15, 06:51

aseerel4c26's gravatar image

aseerel4c26 ♦
32.1k16239551


It sounds like you are doing it right (adding route information only to the relation; compare with this other question or that question)
… but the map you are looking at is just not displaying hiking routes. Are other hiking routes shown? Check at e.g. http://hiking.waymarkedtrails.org (your new hiking trail) or other hiking maps/services.

Info about the usual tagging is at https://wiki.openstreetmap.org/wiki/Hiking#Tagging_walking_and_hiking_Route_Networks

permanent link

answered 15 Sep '15, 06:06

aseerel4c26's gravatar image

aseerel4c26 ♦
32.1k16239551
accept rate: 17%

edited 15 Sep '15, 06:33

Thanks for the advice. I wasn't aware of that waymarked trails, which is good to know about. However, it appears to be using tiles that are served up from osm.org tile server, which is the tile set that doesn't have trail labels for hiking trails unless it is on the way itself.

I still feel like I'm doing it right, and that this just reflects a deficiency in that specific tile renderer. Like I said, the relation approach is the only way to capture certain data. I might wait until the cycle map tiles refresh, which I think are more useful for hiking trail maps anyway.

(15 Sep '15, 16:04) Elerius
1

@Elerius: the background tiles are in fact the same which you see as default map on osm.org, right. But waymarkedtrails.org overlays the hiking routes (which have been extracted from OSM data, of course and as mentioned on the site and in the copyright map header). This is the power of the open OSM data - everybody can build maps and services based on the raw data to enhance some specific view. Having only one map which shows everything in a way best for hikers, boat drivers, HGV drivers, … would be impossible.

Yes, you are doing it right. Compare with other hiking routes, e.g. this one (randomly selected by me).

Cycle maps likely will not render hiking routes as that is out of scope for them. If you just like the OpenCycleMap as background with your hiking routes, check gpsies.com, select the OpenCycleMap as background and select the "waymarked trails" as overlay.

(15 Sep '15, 19:39) aseerel4c26 ♦
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:

×189
×138
×70
×27
×25

question asked: 14 Sep '15, 23:27

question was seen: 2,343 times

last updated: 15 Sep '15, 19:43

powered by OSQA