>> I've tagged some cycle crossing drawn as a single node with
>> highway=crossing, foot=no and bicycle=yes. I would not use access=no
>> because it can be misunderstood and routing software could prevent
>> access to the main street.
>From your description it seems that the node might be forbi
If the cycleways coming to the crossing are tagged as foot=no, then why
does the crossing have to be tagged with access tags?
Janko
2013/4/10 Alberto
> >> I've tagged some cycle crossing drawn as a single node with
> >> highway=crossing, foot=no and bicycle=yes. I would not use access=no
> >>
Hi all,
Sometime ago, I started thinking about this topic, if anyone remembers my emails; work got very busy these past few
months. I second the idea of using ref:LOCODE as LOCODEs also apply to airports, road terminals, oil terminals, and
rail stations as well as ports, so having something
On 07/04/2013 19:37, Martin Atkins wrote:
Hi all,
I do mapping in San Francisco, CA and I'm frustrated about the
inconsistent levels of detail we typically use when mapping urban
environments.
It looks just fine to me, Martin.
Cheers
Dave F.
___
Hi.
I've just updated the page to remove roles specification.
The specific roles chapter became a specific elements one since it gives
useful recommendation to map elements.
Nevertheless no roles remain on it as for not confusing mappers.
If there are no formal suggestion or comments left, I wo
