On 07/05/12 10:34, Jonathan Harley wrote:
On 06/05/12 17:22, Andrew M. Bishop wrote:
Andy Streetm...@andystreet.me.uk writes:
On Fri, 2012-05-04 at 14:32 +0100, Andrew Chadwick wrote:
I'd agree that generic consumers will struggle with highway=path,
designation=* but that is a wider OSM
As a relatively new mapper, two things stand out to me.
1) What Potlatch offers will be used. That means
h=footway/cycleway/bridleway/track will be used over h=path
2) The footway/cycleway/bridleway classification scheme makes perfect
sense to me. Any path I see I in town I can easily classify
On a slightly different tangent, how if at all do we have have timed
restrictions on access types?
As the other day I was walking around the Ridgeway:
http://www.openstreetmap.org/?lat=51.422242618282993lon=-1.8314579782714844zoom=15layers=B000FTF
1. Some byways have permissions of no
I believe these tags should contain something along the lines of 'uk',
'sco' etc. Not because I'd wish the prefix to show the region, but because
the designations are unique and need I believe the tags need to be unique.
So for an Area of Outstanding Beauty resulting from UK created legislation
And on another slight different tangent, I've noticed a lot of 'implied
surfaces' in both versions
eg *Please note*: omitting the
surfacehttp://wiki.openstreetmap.org/wiki/Key:surface
=* tag implies it *is unpaved*
What's the background for suggesting not providing a surface tag will
result in an
5 matches
Mail list logo
