[Tagging] Navaid relation?

[Florian Lohoff]

Hi Peter,

On Wed, May 22, 2019 at 10:15:57AM +0200, Peter Elderson wrote:
> >  Id imaging a relation which says
> > object A -> car -> Node B (on routable graph)
> > So whenever i tell my nav software to bring me to object A the node
> > selected on the routable graph as a destination will be Node B.
> 
> One relation per mode of transport then? So a complex obejct a could have
> many navaid relations? Or one relation containing all nodes, with roles for
> transport mode?

type navaid
name Foobar (Optional if object does not carry a name or you map
             multiple different location)
source <object to reach> (Multiple ones sharing the same transport destination)
car    <node to go to>
bicyle <node to go to>
foot   <node to go to>

Just as the rough first version. You want to keep this to a minimum for
cases where an algorithm cant choose the right solution or is making
wrong decisions based on correct geometries.

A mall with parking south and north would get 2 navaid relations

	name "Mall foo - North"
	name "Mall foo - South"

With their parking lot entries as the nodes to go to by car
and their entrance for foot. Currently you might be lucky
that your Nav Software does a full text search and somebody
named the parking lots with the complete name although
they should only carry a ref=North/South.

So a navigation preprocessor would not try to find a node on the
routable network by algorithm but by hinting in case it finds
this relation.

It currently works by accident and because people tweak
the data to get their result. Either geometries, additional tags
or additional name tags on unrelated objects. 

People start mapping for the router/nav software. A relation like this
could help solve the need of hinting the software without abusing
other tags, tag move, geometry tweaking.

Flo
-- 
Florian Lohoff                                                 f at zz.de
        UTF-8 Test: The 🐈 ran after a 🐁, but the 🐁 ran away
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20190522/dc7eb2f1/attachment.sig>