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 would refer to their address as on "F Street" or "First Street" in conversation, but the ref is still useful for navigation if it's placed on signs in addition to the local name. Some roads only have a name like (California) State Highway 99, which is used by the locals as their house or business street address, so in that case you can use both name=Highway 99 (or whatever the most common signs and addresses say) in addition to ref=CA 99 or similar. On 8/19/19, brad <bradha...@fastmail.com> wrote: > 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 >> identifies a feature. >> >> While it's best to have the common name in the tag name=, like >> name=Corkscrew Gulch Road, it's okay to have more than one ref in the >> tag ref, separated by semicolons. Many database users can handle this. >> Eg: >> >> name=Corkscrew Gulch Road >> ref=CR 2;FS 729.2B >> >> If there are other, less common actual names, consider using >> alt_name=* or loc_name=* (local, informal names), but in this case it >> looks like there is just one name, but multiple reference numbers. >> >> Joseph >> >> On 8/19/19, Rob Savoye <r...@senecass.com> wrote: >>> 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 segments, all with >>> different names common and USFS names. We prefer the common name or the >>> USFS name, but I have no control over what Dispatch gives us. >>> >>>> name=CR 2 / Corkscrew Gulch Road / FS 729.2B alt_name=CR 2; Corkscrew >>>> Gulch Road; FS 729.2B >>>> If you have several name or several ref, you can use the “;” >>>> separator >>> Ah, I've used that elsewhere, didn't think about it for road names. >>> The problem though is since the name gets displayed, too many long road >>> names obscures the map. I've had similar problems with house addresses >>> in the more densely populated areas. When I produce a KML file from OSM >>> data, I put all the names in the description popup. That works in GPS >>> map apps, but not in OsmAnd. Plus I wonder if that would break routing... >>> >>> - rob - >>> >>> _______________________________________________ >>> Tagging mailing list >>> Tagging@openstreetmap.org >>> https://lists.openstreetmap.org/listinfo/tagging >>> >> _______________________________________________ >> Tagging mailing list >> Tagging@openstreetmap.org >> https://lists.openstreetmap.org/listinfo/tagging > > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging