[Tagging] Navaid relation?

marc marc marc_marc_irc at hotmail.com
Tue May 21 22:38:23 UTC 2019


Le 22.05.19 à 00:16, Florian Lohoff a écrit :
> 
> Hi marc,
> 
> On Tue, May 21, 2019 at 10:02:53PM +0000, marc marc wrote:
>> Hello,
>>
>> Le 21.05.19 à 23:46, Florian Lohoff a écrit :
>>> Currently all Routing/Navigation application try hard to find
>>> the nearest or best point on the routeable network for a given
>>> destination lat/lon or object.
>>
>> with best, you mean : only one ? that look like wrong
>> a destination can have several points depending on the type
>> of locomotion.
>> the same type of locomotion can have several points, e.g. several ways
>> that desert a station by foot, several other for car, ...
> 
> What is the expectation to get navigated to when selecting a park?

there is no such thing as "a single point that makes everyone agree"
take the case of a square park fenced by a fence, surrounded by 4 
streets each with a pedestrian entrance to the park.
those arriving from the north will probably want to stop at the street 
to the north, while those arriving from the south will probably want to 
stop at the street at the south entrance.
Those who have difficulty walking will probably prefer the car park 
closest to an entrance, while others will prefer parking for people with 
reduced mobility or free parking, all while they have all come by car.
on the basis of which objective criteria will you decide which point of 
the public network is most suitable to reach the park?

>> put one or more node on the outer with entrance=yes/main :)
>> I use foot/vehicle/bicycle=designed to describe the type
>> of locomotion for this entrance
> 
> This does not work for all cases and all objects.

an exemple at least ?

>>> - Houses which are routeable by road a but are near road b
>>
>> add door/entrance but also add missing ways to connect to the road A
> 
> Doesnt work - You are navigating by car but you only have a footway up
> to hour house - Still the house is near road b - thus you get navigated
> to the wrong street.

that's a bug/a feature needed in the routing, all info exist in osm
to find the path to reatch to the house, instead of leaving you at
a closer location but whose routing to the house is unknown

> Detaching addresses from house geometries putting it near the road 
> i expect people to be navigated to.

so UGLY ! You decide, for the example of the park, that everyone
must use YOUR favorite entrance.
it is tagging for your-routing, instead of allowing routing to have 
personalized options (shortest route, least walking, close to a parking, 
disabled accessible up to the poi)

Regards,
Marc


More information about the Tagging mailing list