Re: [Talk-us] Reference numbers to use for hiking trail route relations

Further investigation shows that they're National Forest Trails, allocated by the forestry service, like the forest service roads. Some kind of network allocation like the forest roads might be appropriate - something like: network = US:NFRS:Kaniksu:FT perhaps? Other proposed tags

Re: [Talk-us] Reference numbers to use for hiking trail route relations

Thanks Kevin. Only problem now is identifying the authority. I suspect it's Idaho Panhandle National Forests but will have to investigate further. Roger the pack trail - will give it some consideration. On Sun, Oct 11, 2020 at 08:42:32PM -0400, Kevin Kenny wrote: > On Sun, Oct 11, 2020 at

Re: [Talk-us] National Forest refs/names

County Road 14, Boundary County ID. TIGER name is "Camp Nine Road", joins with a forest road labelled in the US Forest Roads Overlay as just "Camp Nine". Around 48.7993305N 116.2837172W Mark. On 2020/07/30 8:12, Paul Johnson wrote: > Could we get some examples of what you mean? > > On Wed,

Re: [Talk-us] National Forest refs/names

That seems sensible. What about the general case (i.e. no continuity with a county road?) - to add "road" or not? On 2020/07/30 7:09, Paul Johnson wrote: > I'd generally include the whole name including "Road" in that case. > > On Wed, Jul 29, 2020 at 5:03 PM >

Re: [Talk-us] National Forest refs/names

Quick question for clarification. The US Forest Roads overlay in JOSM shows the name of forest roads without "Road"; e.g. "Burton Creek B". Should the suffix "road" be added or is it redundant and a waste of bytes? (Sometimes there may be continuity from, say, a County Road with e.g. "Burton

Re: [Talk-us] Labeling forestry service roads/tracks

Thanks, that sounds very sensible. I'll use it in lieu of any better suggestions. Mark. On 2020/07/21 7:48, Mike Thompson wrote: > > > On Mon, Jul 20, 2020 at 4:46 AM > wrote: > > Mike, > > Good idea on the route references. What should the network be set

Re: [Talk-us] Labeling forestry service roads/tracks

Thanks Tod. Mark. On 2020/07/21 8:58, Tod Fitch wrote: > >> On Jul 20, 2020, at 4:48 PM, Tod Fitch > > wrote: >> >> >>> On Jul 20, 2020, at 4:35 PM, Clifford Snow >> > wrote: >>> >>> On Mon, Jul 20, 2020 at 3:46 AM >>

Re: [Talk-us] Labeling forestry service roads/tracks

Thanks Clifford. Mark. On 2020/07/21 10:08, Clifford Snow wrote: > The legend is just for the USFS road layer that is served by Mapbox on > JOSM. > > > Sent from my Android phone. > > On Mon, Jul 20, 2020, 4:48 PM Tod Fitch > wrote: > > >> On Jul 20, 2020, at

Re: [Talk-us] Labeling forestry service roads/tracks

Mike, Good idea on the route references. What should the network be set to? On 2020/07/20 7:56, Mike Thompson wrote: > > > On Sun, Jul 19, 2020 at 4:49 PM > wrote: > >  For > roads that appear to be public access (e.g. to go to a lake) but are >

Re: [Talk-us] Labeling forestry service roads/tracks

Clifford, Could you repost the legend? It's hard/impossible to make out the surface reliably from aerial photos. On 2020/07/20 14:18, Clifford Snow wrote: > If you are using JOSM there is a USFS road layer. The color of the way > indicates surface and highway classification if I remember

[Talk-us] Labeling forestry service roads/tracks

Hi folks, Editing in Boundary County, Idaho in the Panhandle, I've been extending the forest landuse area around Bonners Ferry and have come across a difficulty in classifying forest roads. It seems that many have been automatically imported and have highway=residential, which is just plain

[Talk-us] Labeling county roads (Idaho)

Newby here. Started mapping an area of the Idaho panhandle around the Kootenai river. I notice that currently minor roads have a "County Road nn" name but TIGER2019 data also has names such as "Acacia Avenue". I think most map users would want to use the "Acacia Avenue" name as it what would be