Interesting! Since the data is on a node on the street way, how do we
figure out if it's left/right side? kerb:left/right=*? Or do we figure it
out spatially (find the driveway way and do some math)?
On Sun, Jul 16, 2017, 1:14 PM marc marc wrote:
> Le 16. 07. 17 à
Le 16. 07. 17 à 20:38, Nick Bolten a écrit :
>> There is no need to use so many section. A crossing is a node, not a
>> section/way. So put one kerb=raised on the way and kerb=lowered on the
>> node. It's done :-) You have the same number of section/tag in both cases.
> Hmm, I'm not sure I
> There is no need to use so many section. A crossing is a node, not a
section/way. So put one kerb=raised on the way and kerb=lowered on the
node. It's done :-) You have the same number of section/tag in both cases.
Hmm, I'm not sure I understand. Which node would get kerb=lowered? Since
I'm
> You can tag the curbs at each side of a crossing using left/right tags,
and you can find out the length by looking at the road's width (or estimate
it from the number of lanes). It's not perfect, but at least there are good
enough ways to deal with this
But you can't handle the directional
Le 16. 07. 17 à 14:24, Svavar Kjarrval a écrit :
> I do think that the routers should
> be programmed to evaluate when it's safe to suggest to the user to cross
> the street without a specifically mapped crossing.
it is already the case
use sidewalk tag on the way when you can cross the street
use
Le 16. 07. 17 à 01:29, Nick Bolten a écrit :
> a block with 10 driveways would
> actually need to be split into 10 lowered/flush curb sections and 11
> raised sections, for a minimum of 21 segments for a single block.
There is no need to use so many section.
A crossing is a node, not a
On lau 15.júl 2017 11:13, marc marc wrote:
>
> Your demonstration is only that a wrong map create sometimes a wrong
> routing :-)
> What will your reaction be when Mapzen tell you to cross a road where it
> is impossible ? However this is exactly the current map for [2]
> You would not agree
On Fri, Jul 14, 2017 at 07:01:55PM +0200, Michael Reichert wrote:
Hi,
> There are two open questions regarding the definition:
> - What qualifies a track to have highspeed=yes? Minimum speed, curves,
> type of traffic, fencing, train protection etc. are the relevant
> factors. But it has not
On 15.07.2017 19:06, Nick Bolten wrote:
[...]
> It can't properly describe
> crossings, since they've been condensed into a node, but important
> information like length, the curbs at each side (direction of
> traversal + curb type both matter), APS directionality, etc, are all
> essentially