Re: [Talk-us] Tagging of county roads

2010-05-26 Thread Alan Mintz

At 2010-05-25 22:55, Apollinaris Schoell wrote:
On 26 May 2010, at 24:25 , Alan
Mintz wrote:
 It seems that the county road number should go in the ref tag, and
this is 
 what I've seen in some cases, but where should the county and state
go? 
 I've used is_in:county and is_in:state_code in the past for other
things 
 (like bridges and mileposts), but people don't seem to like these,
and 
 they're not exactly right - I'm not trying to say where the roads
are, just 
 complete the reference tag with what's on the signage.
 
you answered already, is_in is wrong for this purpose. the ref tag is the
place to use.

 Currently, for example, I'd tag Santiago Canyon Road in Orange
County, CA, as:
 
 highway=secondary
 ref=S18
 is_in:county=Orange
 is_in:state_code=CA
 
what does the S mean in the ref?
It's just a part of the reference numbering. County road references
are a letter followed by one or more numbers, and this is how it's signed
(see http://en.wikipedia.org/wiki/County_Route_S18_%28California%29 for
the example mentioned below).

is it a state route or a
county road?
I'm talking about county roads, not state routes.

I think most use CA for state hw.
It's hard to tell if this is correct. Even hw shields are inconsistent.
most shields in california use the number only but some shields and
official documents use other abbrev like SR. 
I think to match the what's on the ground rule we should change CA to SR,
but it's very common across US already and only if there is a broad
consensus this should be done
It seems you are talking about state routes here, not county
roads.

 Does it make sense to add a
network=US:CA:Orange tag (like the relation) 
 instead of the is_in:* tags?
this is as wrong as is_in tags, someone invented it to tag for a
renderer. network=Orange should be sufficient and correct.

But there are counties named Orange in other states, which is why I want
to include the state somehow - it's as important a part of the complete
reference as the county.

--
Alan Mintz alan_mintz+...@earthlink.net



___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Tagging of county roads

2010-05-26 Thread Apollinaris Schoell

On 26 May 2010, at 10:11 , Alan Mintz wrote:
 what does the S mean in the ref?
 
 It's just a part of the reference numbering. County road references are a 
 letter followed by one or more numbers, and this is how it's signed (see 
 http://en.wikipedia.org/wiki/County_Route_S18_%28California%29 for the 
 example mentioned below).
 
 
  is it a state route or a county road?
 
 I'm talking about county roads, not state routes.
 

In other counties in CA they are J, never seen the S for county roads. good to 
know

 
 I think most use CA for state hw. It's hard to tell if this is correct. Even 
 hw shields are inconsistent. most shields in california use the number only 
 but some shields and official documents use other abbrev like SR. 
 I think to match the what's on the ground rule we should change CA to SR, 
 but it's very common across US already and only if there is a broad 
 consensus this should be done
 
 It seems you are talking about state routes here, not county roads.
 

yes, similar situation tough. quite inconsistent in reality and in osm

 
  Does it make sense to add a network=US:CA:Orange tag (like the relation) 
  instead of the is_in:* tags?
 
 this is as wrong as is_in tags, someone invented it to tag for a renderer. 
 network=Orange should be sufficient and correct.
 
 But there are counties named Orange in other states, which is why I want to 
 include the state somehow - it's as important a part of the complete 
 reference as the county.

not really needed, the state and country polygons with the coordinates define 
where it is. sure there is some redundant info in osm and it doesn't harm to 
have more data.
in general the better tag structure and very common approach is to define a 
namespace like this

network=Orange
network:state=CA (or california to make it human readable)
network:country=US, but this is probably overkill

this is much easier to understand for humans and it is easier to parse by 
applications. packing all info into a single tag value by some cryptic codes is 
tagging for a specific application.

 --
 Alan Mintz alan_mintz+...@earthlink.net
 ___
 Talk-us mailing list
 Talk-us@openstreetmap.org
 http://lists.openstreetmap.org/listinfo/talk-us
 


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us