On Mon, Jul 19, 2010 at 11:54 PM, Richard Mann
wrote:
> I don't think we're reaching any consensus that key:paved is an idea
> to be positively recommended, so I think it's probably best to record
> it in the wiki as "some people do this".
>
> I think the wiki would also benefit from a few notes s
2010/7/19 John Smith :
> On 19 July 2010 23:47, M∡rtin Koppenhoefer wrote:
>> No, I didn't miss that. I was replying to Pieren in the cited message.
>> You're right, it is not impossible, still it requires a bit of effort
>> due to the number of surface values.
>
> There is only a limited number o
On 19 July 2010 23:47, M∡rtin Koppenhoefer wrote:
> No, I didn't miss that. I was replying to Pieren in the cited message.
> You're right, it is not impossible, still it requires a bit of effort
> due to the number of surface values.
There is only a limited number of values that would be consider
On 19 July 2010 23:54, Richard Mann
wrote:
> I don't think we're reaching any consensus that key:paved is an idea
> to be positively recommended, so I think it's probably best to record
> it in the wiki as "some people do this".
Won't this still confuse people? This is the reason for not having i
I don't think we're reaching any consensus that key:paved is an idea
to be positively recommended, so I think it's probably best to record
it in the wiki as "some people do this".
I think the wiki would also benefit from a few notes saying which
values should be treated as paved (in the sense of d
2010/7/19 John Smith :
> On 19 July 2010 23:33, M∡rtin Koppenhoefer wrote:
>> the difference is that surface=paved is preliminary and paved=yes is
>> definite.
>> What's the difference between surface=paved and surface=cobblestone
>> and surface=asphalt? That is the question to which surface=pave
On 19 July 2010 23:33, M∡rtin Koppenhoefer wrote:
> the difference is that surface=paved is preliminary and paved=yes is definite.
> What's the difference between surface=paved and surface=cobblestone
> and surface=asphalt? That is the question to which surface=paved
> cannot deliver a satisfying
2010/7/19 Pieren :
> I think that's really stupid. Again, just to make 0.5% contributors happy,
> we create a dupplicated tag ... Then wait 2 months and a newcomer will ask
> "what's the difference between 'surface=paved' and 'paved=yes' ?".
the difference is that surface=paved is preliminary and
On 19 July 2010 19:06, Steve Bennett wrote:
> No, because there is:
> surface=paved
> surface=asphalt
> surface=concrete
> surface=cement
>
> And since "paved" is usually shorthand for "can be driven on safely at
> full speed without getting the car dirty", you might include
> surface=metal, surfa
On Mon, Jul 19, 2010 at 2:10 PM, Richard Mann <
richard.mann.westoxf...@googlemail.com> wrote:
> I've updated the wiki page to try to explain it more clearly. I've
> included Martin's paved=yes flag (though personally, I'd probably just
> make it clear in the table that some values such as concret
I've updated the wiki page to try to explain it more clearly. I've
included Martin's paved=yes flag (though personally, I'd probably just
make it clear in the table that some values such as concrete should be
treated as paved)
Richard
___
Tagging mailin
On 19.07.2010 13:16, M∡rtin Koppenhoefer wrote:
>>> http://wiki.openstreetmap.org/wiki/Key:paved
>
> I did that, because of 2 reasons:
> 1) there is a number of users who think that surface gets more and
> more complicate to evaluate due to the level of detail. They say (and
> it is IMHO true for
On 19.07.2010 09:06, Steve Bennett wrote:
> On Sun, Jul 18, 2010 at 2:42 AM, Tobias Knerr wrote:
>> While the list of surface values is *potentially* unbounded, it is
>> finite at any given time. For practical purposes, just teach that list
>> of surface values on the wiki to your renderer, do a q
2010/7/16 Richard Welty :
> On 7/15/10 5:45 PM, John Smith wrote:
>>
>> On 16 July 2010 07:42, Richard Mann
>> wrote:
>>
>>>
>>> Can't find it on the wiki - do you have a ref?
>>>
>>
>> http://wiki.openstreetmap.org/wiki/Key:paved
I did that, because of 2 reasons:
1) there is a number of users
On 7/19/10 2:55 AM, Steve Bennett wrote:
On Sat, Jul 17, 2010 at 11:15 PM, Richard Welty wrote:
i might add that if we're looking at the introduction of new semantics in
order
to make adding unpaved=yes/no ok, it's going to take a great deal to
convince
me.
It's not "adding" new semanti
On 19 July 2010 19:06, Steve Bennett wrote:
> And since "paved" is usually shorthand for "can be driven on safely at
> full speed without getting the car dirty", you might include
> surface=metal, surface=paving_stones...
surface=wood for wooden bridges...
___
On Mon, Jul 19, 2010 at 6:29 PM, Richard Mann
wrote:
> I think surface started as a binary paved/unpaved for roads (with
> paved assumed by default, and paved meaning tarmac), and has got
> extended to cover cobbled roads, and (subsequently) as a way of adding
> more info for tracks/paths.
>
> So
On Mon, Jul 19, 2010 at 4:29 AM, Richard Mann
wrote:
> There's a bit of a grey area for well-maintained unsealed paths/roads,
> but the binary paved=yes/no doesn't really help. I tend to use other
> clues - that it's got a higher road classification, or is flagged as
> being part of a cycle route.
I think surface started as a binary paved/unpaved for roads (with
paved assumed by default, and paved meaning tarmac), and has got
extended to cover cobbled roads, and (subsequently) as a way of adding
more info for tracks/paths.
So for most purposes, the principal distinction is between paved and
On Sun, Jul 18, 2010 at 2:42 AM, Tobias Knerr wrote:
> While the list of surface values is *potentially* unbounded, it is
> finite at any given time. For practical purposes, just teach that list
> of surface values on the wiki to your renderer, do a quick tagwatch
> check to find out whether there
On Sat, Jul 17, 2010 at 11:15 PM, Richard Welty wrote:
> ummm, does this type of semantic (with two inconsistent tags, one has
> priority)
> appear anywhere else in OSM?
There are lots of places where tag inconsistency can arise (eg,
highway=cycleway, bicycle=no) but I'm not aware of anyone forma
On 2010-07-16 at 06:50, Steve Bennett wrote:
> On Fri, Jul 16, 2010 at 8:43 AM, John Smith wrote:
>> That was what I was trying to figure out, is there a good reason for
>> such a tag, or is it going to just confuse people.
>
> IMHO yes it's useful, because the paved/unpaved distinction is by far
On 7/17/10 8:20 AM, Steve Bennett wrote:
This isn't a problem I have any idea how to resolve just now. My
comments above were quite simple: having inconsistent paved=yes/no,
and surface=xxx is not a problem, because the central authority
(whatever it is) can simply define one as taking precedenc
On Sat, Jul 17, 2010 at 8:42 PM, Alan Mintz
wrote:
> The current planet tagwatch has 19243 different keys, and shop, leisure, and
> amenity have over 1000 values each. Many of these are mis-spellings,
> capitalization errors, import-source-specific tags, etc., but it also
> seems like a lot of peo
At 2010-07-16 21:55, Steve Bennett wrote:
On Fri, Jul 16, 2010 at 2:57 PM, Richard Welty wrote:
> from a data modeling perspective, though, it's redundant and thus creates
> the opportunity for inconsistency and unresolvable error.
Do "data modelling perspectives" normally deal with folksonomie
On 17 July 2010 14:55, Steve Bennett wrote:
> Do "data modelling perspectives" normally deal with folksonomies
> though? By its very nature, the data entered by OSM editors is far
> more susceptible to inconsistency than, say, a corporate database.
There is plenty of commercial and government dat
On Fri, Jul 16, 2010 at 2:57 PM, Richard Welty wrote:
> from a data modeling perspective, though, it's redundant and thus creates
> the opportunity for inconsistency and unresolvable error.
Do "data modelling perspectives" normally deal with folksonomies
though? By its very nature, the data enter
On 16 July 2010 14:50, Steve Bennett wrote:
> the most important one for roads. The problem is that surface=* is an
> unbounded list, so renderers potentially have to support surface=dirt,
What do they do when there is no surface tag? How is this any
different than an unknown value?
On 7/16/10 12:50 AM, Steve Bennett wrote:
IMHO yes it's useful, because the paved/unpaved distinction is by far
the most important one for roads. The problem is that surface=* is an
unbounded list, so renderers potentially have to support surface=dirt,
gravel, cobblestone, mud, cracked_concrete,
On Fri, Jul 16, 2010 at 8:43 AM, John Smith wrote:
> That was what I was trying to figure out, is there a good reason for
> such a tag, or is it going to just confuse people.
IMHO yes it's useful, because the paved/unpaved distinction is by far
the most important one for roads. The problem is tha
On 16 July 2010 08:28, Richard Welty wrote:
> geez, that really should go away. surface= already serves
> the purpose, and is a lot more flexible.
That was what I was trying to figure out, is there a good reason for
such a tag, or is it going to just confuse people.
_
On 7/15/10 5:45 PM, John Smith wrote:
On 16 July 2010 07:42, Richard Mann
wrote:
Can't find it on the wiki - do you have a ref?
http://wiki.openstreetmap.org/wiki/Key:paved
geez, that really should go away. surface= already serves
the purpose, and is a lot more flexible.
richa
On Thu, Jul 15, 2010 at 11:42 PM, Richard Mann <
richard.mann.westoxf...@googlemail.com> wrote:
> Can't find it on the wiki - do you have a ref?
>
> Richard
>
>
The key:surface has been modified as well:
http://wiki.openstreetmap.org/wiki/Key:surface
Pieren
___
On 16 July 2010 07:42, Richard Mann
wrote:
> Can't find it on the wiki - do you have a ref?
http://wiki.openstreetmap.org/wiki/Key:paved
___
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/tagging
Can't find it on the wiki - do you have a ref?
Richard
On Thu, Jul 15, 2010 at 10:30 PM, John Smith wrote:
> On 16 July 2010 07:26, Richard Mann
> wrote:
>> 1300 uses worldwide, against 1.9m for surface=
>>
>> So a wiki entry that says maybe you should consider using
>> surface=paved/unpaved in
On 16 July 2010 07:26, Richard Mann
wrote:
> 1300 uses worldwide, against 1.9m for surface=
>
> So a wiki entry that says maybe you should consider using
> surface=paved/unpaved instead might be sensible
I was more curious about use cases, or is this just another smoothness tag?
1300 uses worldwide, against 1.9m for surface=
So a wiki entry that says maybe you should consider using
surface=paved/unpaved instead might be sensible
Richard
On Thu, Jul 15, 2010 at 10:16 PM, John Smith wrote:
> I noticed someone just added paved=yes/no to the wiki, is this needed?
>
> Won't
I noticed someone just added paved=yes/no to the wiki, is this needed?
Won't this just end up confusing people between surface=paved?
___
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/tagging
38 matches
Mail list logo
