[Talk-us] Trail Route Relationships
Alex Mauer
hawke at hawkesnest.net
Wed May 12 17:32:34 BST 2010
On 05/11/2010 10:25 PM, Val Kartchner wrote:
> On Mon, 2010-05-10 at 12:07 -0500, Alex Mauer wrote:
>> On 05/07/2010 03:04 PM, Val Kartchner wrote:
>>> Which levels should be assigned as the "name" for each trail segment?
>>> The rest will be used in the "name" for the route relationships? Once I
>>> get an answer, I'll change the trails for consistency.
>>
>> Basically, follow the directions[1] for working with route
>> relationships. Create a relation for each trail section as you have,
>> give it the name of the section. Then create a super-relation
>> containing all the trail sections, and give it the name of the trail
>> network. Assign each of them an appropriate route type[2]. Add any
>> extra stuff, e.g. foot=*, bicycle=*, horse=*.
>>
>> I’ll admit to doing a bit of tagging for the renderer where I’ve had to
>> map similar trails, by using the ref=* tag to hold the section name, and
>> name=* to hold the global trail name.
>
> The responses are for the words that I asked, but were not really for
> the question that I should have asked. Let me try to phrase the
> question a different way.
>
> Here is a simplified diagram of part of the trails that I need to map:
>
> A B C
> -----+-----------------------+-----
> | |
> \_____________________/
> D
>
> Sections A, B and C are part of the Ogden River Parkway. Sections B and
> D are part of the 21st Street Pond Trail. All of these are part of the
> Ogden Trail Network. The Ogden River Parkway is part of the Centennial
> Trail. The Ogden Trail Network and the Centennial Trail will obviously
> be done with relationships.
>
> The big question is about section B: Which trail should be used for the
> "name" for this section? Should B be part of the longer Ogden River
> Parkway then B & D be done as a relationship? Should it be done the
> other way around? Should B attributes be "name=Ogden River Parkway" and
> "name_1=21st Street Pond Trail"?
>
> Which name should take priority?
If you're talking about the lowest-level name (i.e. the one on the way),
I think it would be acceptable to either use the one as signed assuming
there's only one, or otherwise just leave it empty and leave it to
renderers to pick up the name(s) from the relations.
I don't think it's a problem for B to be in the two relations...
This may be obvious, but you'd presumably need the following relations:
Relation 1, containing A, B, C
name=Ogden River Parkway
Relation 2, containing B, D
name=21st Street Pond Trail
Relation 3, containing relation 1 and 2
name=Ogden Trail Network
Relation 4, containing relation 1 (and presumably other relations)
name=Centennial Trail
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 554 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20100512/1d3ba565/attachment.pgp>
More information about the Talk-us
mailing list