Re: [Tagging] roads with many names

2019-08-19 Thread Rob Savoye
On 8/18/19 10:05 PM, Kevin Kenny wrote: > route=road relations provide a way to group all the individual > segments of a numbered route into a coherent whole, and allow for > better handling of things like the choice of highway shield and the > handling of concurrencies (where two numbered routes

Re: [Tagging] roads with many names

2019-08-18 Thread Andrew Davidson
On Mon, Aug 19, 2019 at 1:45 AM Julien djakk wrote: > > If you have several name or several ref, you can use the “;” separator > > Name tags with ";" in them get flagged as a problem to fix by validators. If there are more than one alternative names for something I use alt_name=* alt_name:1=*

Re: [Tagging] roads with many names

2019-08-18 Thread Joseph Eisenberg
I would have expected tracktype=grade2 for a gravel road. Is it common to use grade1 in that area for very well built, quality gravel roads? Joseph On Mon, Aug 19, 2019 at 12:11 PM Johnparis wrote: > Don't know how you deduced "no space?" from Martin's comment. A space is > an alphanumeric

Re: [Tagging] roads with many names

2019-08-18 Thread Kevin Kenny
On Sun, Aug 18, 2019 at 11:30 PM Rob Savoye wrote: > > Tag *names*, by contrast, use an underscore instead of a space. > > Kevin Kenny's comment above indicates what appears to be the > > consensus on the tag name(s) in the USA. So in theory you might have > >

Re: [Tagging] roads with many names

2019-08-18 Thread Paul Johnson
On Sun, Aug 18, 2019 at 10:24 PM Joseph Eisenberg < joseph.eisenb...@gmail.com> wrote: > F Street and 1st Street (usually written out as First Street, though > this depends on the local standards) are a common name, which goes in > the name field. > It can also be regionally dependent. Oklahoma

Re: [Tagging] roads with many names

2019-08-18 Thread Rob Savoye
On 8/18/19 9:09 PM, Johnparis wrote: > Don't know how you deduced "no space?" from Martin's comment. A space > is an alphanumeric character. In any case, as I mentioned, there is I just read too much into example of 'CR2'... I'm just trying to get it right, so routing works better. I prefer the

Re: [Tagging] roads with many names

2019-08-18 Thread Joseph Eisenberg
F Street and 1st Street (usually written out as First Street, though this depends on the local standards) are a common name, which goes in the name field. 1st Street might also be part of County Road (CR) #312, which would be ref=CR 312 or =CR312 or similar. The idea is that most people locally

Re: [Tagging] roads with many names

2019-08-18 Thread brad
So is F street, or 1st street a name or a ref? On 8/18/19 10:27 AM, Joseph Eisenberg wrote: It looks like "CR 2" is a "ref" rather than a name, and so is FS 729.2B. A ref=, short for "reference number" (or more properly "reference alphanumeric string") is a set of letters and numbers that

Re: [Tagging] roads with many names

2019-08-18 Thread Johnparis
Don't know how you deduced "no space?" from Martin's comment. A space is an alphanumeric character. In any case, as I mentioned, there is normally a local consensus on space-versus-no space, and as others have mentioned, it's up to you. The problem with space-vs-no space arises particularly with

Re: [Tagging] roads with many names

2019-08-18 Thread Paul Johnson
On Sun, Aug 18, 2019 at 10:16 AM Rob Savoye wrote: > Where I live in rural Colorado, many of the roads have 3 names. The > county designated one like "CR 2", but often have an alternate name > everyone uses like "Corkscrew Gulch Road", and then many have a US > Forest Service designation like

Re: [Tagging] roads with many names

2019-08-18 Thread Warin
On 19/08/19 05:16, Paul Allen wrote: On Sun, 18 Aug 2019 at 19:55, Rob Savoye > wrote:   So no space ? USFS roads use "FS " with a space, at least that seems to be common. So should those be "FS739.1A' ? My opinion is "paint the label."  Others disagree. 

Re: [Tagging] roads with many names

2019-08-18 Thread Joseph Eisenberg
Slightly off-topic: one of the posts mentioned that this road is tagged highway=track. However, if the road is the main access to a house, it should be highway=unclassified. Or it could even be highway=tertiary since it is a country road, if it connects to a number of houses or a hamlet or

Re: [Tagging] roads with many names

2019-08-18 Thread Kevin Kenny
On Sun, Aug 18, 2019 at 12:28 PM Richard Fairhurst wrote: > Rob Savoye wrote: > > Where I live in rural Colorado, many of the roads have 3 names. > > The county designated one like "CR 2", but often have an alternate > > name everyone uses like "Corkscrew Gulch Road", and then many > > have a US

Re: [Tagging] roads with many names

2019-08-18 Thread Paul Allen
On Sun, 18 Aug 2019 at 19:55, Rob Savoye wrote: > So no space ? USFS roads use "FS " with a space, at least that seems > to be common. So should those be "FS739.1A' ? > My opinion is "paint the label." Others disagree. Make up your own mind which is better. -- Paul

Re: [Tagging] roads with many names

2019-08-18 Thread Rob Savoye
On 8/18/19 12:42 PM, Martin Koppenhoefer wrote: > names in OSM are usually in natural language, CR2 is probably what > OpenStreetMap calls a ref, which is for numbers and alphanumeric > codes. The other name is also looking like a code, I agree with > Richard’s suggestion to use one name and 2

Re: [Tagging] roads with many names

2019-08-18 Thread Paul Allen
On Sun, 18 Aug 2019 at 19:33, Martin Koppenhoefer wrote: > > > for several names it is common to use variations of the name tag, like > alt_name reg_name etc. > Yep. And in many cases those, along with loc_name, may be the best way to handle it. But only name (and ref, if used) get rendered

Re: [Tagging] roads with many names

2019-08-18 Thread Martin Koppenhoefer
sent from a phone > On 18. Aug 2019, at 20:36, Rob Savoye wrote: > > Luckily a neighbor called it in, he wasn't home. using 'loc_name' or > 'alt_name' makes sense. This entire area doesn't even exist in Google > Maps, so people not using OSM couldn't find it till we gave directions > on the

Re: [Tagging] roads with many names

2019-08-18 Thread Rob Savoye
On 8/18/19 12:24 PM, Paul Allen wrote: > If the owner calls in a fire at his house, he's going to use his own > wrong name for the road.  So you'd probably be best to have it as a loc_name, > then > there's a chance of somebody other than you finding it. Luckily a neighbor called it in, he

Re: [Tagging] roads with many names

2019-08-18 Thread Martin Koppenhoefer
sent from a phone > On 18. Aug 2019, at 17:41, Paul Allen wrote: > > Ugly and probably breaks many explicit and implicit rules. You'll no doubt > find out > all the ways it is a bad idea very shortly. for several names it is common to use variations of the name tag, like alt_name

Re: [Tagging] roads with many names

2019-08-18 Thread Paul Allen
On Sun, 18 Aug 2019 at 18:29, Rob Savoye wrote: > > Since I usually validate by truck, I use whatever the street sign > says, since that's what the driver uses. A few weeks ago we were at a > structure fire and a local had put up his own road sign, but with the > wrong name! We decided to

Re: [Tagging] roads with many names

2019-08-18 Thread Rob Savoye
On 8/18/19 11:09 AM, Johnparis wrote: > Normally it would be "ref:usfs" rather than "usfs:ref". Thanks, I just found the ref=* page. Also noticed 'loc_name' and 'nat_name', and it looks like those plus ref* are used for routing. Anyway, I like the ref:usfs tag, and will use that, and ref= for

Re: [Tagging] roads with many names

2019-08-18 Thread Johnparis
Normally it would be "ref:usfs" rather than "usfs:ref". I frequently use tags like "ref:FR:STIF" where STIF is an agreed tag within FR (France). And yes, the main ref for the cited road would be "ref=CR 2". Included spaces in a ref tag vary by local consensus. Some places might use "ref=CR2". If

Re: [Tagging] roads with many names

2019-08-18 Thread Rob Savoye
On 8/18/19 10:27 AM, Richard Fairhurst wrote: > name=Corkscrew Gulch Road > ref=CR 2 > usfs:ref=FS 729.2B Interesting, I didn't realize "usfs:ref" is a tag. I have used ref for camp site numbers, didn't know it supported alphanumerics. I dug around, and don't see usfs:ref being used, at least

Re: [Tagging] roads with many names

2019-08-18 Thread Richard Fairhurst
Rob Savoye wrote: > Where I live in rural Colorado, many of the roads have 3 names. > The county designated one like "CR 2", but often have an alternate > name everyone uses like "Corkscrew Gulch Road", and then many > have a US Forest Service designation like "FS 729.2B". name=Corkscrew

Re: [Tagging] roads with many names

2019-08-18 Thread Joseph Eisenberg
It looks like "CR 2" is a "ref" rather than a name, and so is FS 729.2B. A ref=, short for "reference number" (or more properly "reference alphanumeric string") is a set of letters and numbers that identifies a feature. While it's best to have the common name in the tag name=, like name=Corkscrew

Re: [Tagging] roads with many names

2019-08-18 Thread Rob Savoye
On 8/18/19 9:41 AM, Paul Allen wrote: > Assuming that "CR 2" is a name and not a ref, one possibility that > springs to mind, and which will no doubt be highly controversial is Yes, it's county designated name. It's gets messier than that, as sometimes "CR 2" might include multiple other road

Re: [Tagging] roads with many names

2019-08-18 Thread Julien djakk
Hello Rob ! If you have several name or several ref, you can use the “;” separator Julien “djakk” Le dim. 18 août 2019 à 17:17, Rob Savoye a écrit : > Where I live in rural Colorado, many of the roads have 3 names. The > county designated one like "CR 2", but often have an alternate name >

Re: [Tagging] roads with many names

2019-08-18 Thread Paul Allen
On Sun, 18 Aug 2019 at 16:17, Rob Savoye wrote: > Where I live in rural Colorado, many of the roads have 3 names. The > county designated one like "CR 2", but often have an alternate name > everyone uses like "Corkscrew Gulch Road", and then many have a US > Forest Service designation like "FS