That's definitely not the Reed Lakes Trail, fyi

Hi there - just so you know, make sure you convert elevation data into meters!

@ZeLonewolf Ooookay - that's a new constriction I wasn't aware of. Or is that something you made up just now?
i.e. "You can't map from Strava unless you can see the trail or are performing a survey"

Ugh. So - the current ref tagging for forest ways is pure chaos, both on OSM and in the real world. The USFS has come forward and **appears** to have endorsed the usage of "FS" as a forest road prefix, and "TR" as a forest trail prefix.
The difference between the two is necessary because in some NFs/ranger districts the road and trail numbers are similar, and there's a need to separate out FS 350 from TR 350.
Some RDs on the IVM have even started adding the TR prefix to the trail numbers there, when they have a lot of trail number collision.
The main thing is that the NF prefix is to no longer be used - although it does appear that some RDs are purposefully still using it just to be rebellious. *sigh* Whatever.
I'm going to be initiating a change to the OSM wiki soon, detailing all of this, and encouraging mappers to climb on board.
Let me know your thoughts!

No problem - the IVM is an invaluable resource, and if I could I'd reference it in my changesets. The problem is that there's not enough room for sources in changeset fields - I commonly am using 5-10 different sources at once as I map, and the changeset schema won't let me list more than a couple.
I've been thinking of posting my sources on my user page as a blanket sourcing document - better than nothing ?

So I've fixed the access on the AT - that was a complete brainfart on my part - thanks for spotting it.

So the WMNF - like all NFs I map in - expressly allows mountain bikes in most areas:
"All trails, roads, and *travel corridors on the White Mountain National Forest are open to mountain bikes except in Congressionally designated Wilderness areas, on the Appalachian Trail, or where otherwise posted.
https://www.fs.usda.gov/activity/whitemountain/recreation/bicycling

I don't see anything about stock usage though, and that's weird. But horses are commonly allowed by default on most USFS trails. I'm fixing the AT screw-up right now - I've seen that in some ranger districts they ignore the AT's special regulations for the IVM, which is pretty lazy on their part.

Actually - I just notice that this is part of the AT, so that HAS to be bad data. Investigating...

The USFS themselves mark that trail as "Managed For Hiking" and "Open To Pack And Saddle" and "Open To Biking". Is there local signage that contradicts this? If so, it wouldn't be the first time.

https://www.fs.fed.us/ivm/index.html?minx=-7983168&miny=5485679&maxx=-7981878&maxy=5487733&exploremenu=no
(click on the trail)

Oh jeez - thanks for reminding me. I forgot to toggle the different Strava modes to see if there was any non-winter activity - looks like it tapers off to the first north fording of Ship Creek. Would you agree that this whole route is a 'piste_type=hike' situation?

FYI - I'm planning to map all the way down to Indian Creek - let me know if you have any insight as a local. I always cede way to those that are local on-the-ground.

Hi Hans - All of the above, actually. The winter route is very easy to follow on Strava (much to my surprise - I expected the trail to be much more diffuse and unmappable), and the summer trail to the east is mostly satellite/Lidar imagery and some Strava, with topo maps guiding the way (trail is VERY hard to pick out in places). I plan to tag trail visibility accordingly.

> I just think there's a high risk of bad mapping when singularly using Strava data without a secondary reference (personal knowledge, another map, etc.) My people getting lost comment is a sentiment that guides my OSM mapping. "Would I be comfortable if a friend used this data to plan their hiking trip" etc.

Oh okay - my misunderstanding of your comment. I'm ALWAYS using more than one source when I map: besides Strava, OSM GPS traces and satellite imagery, I'm also using the USFS IVM (https://www.fs.fed.us/ivm/) and/or the USFS GDS portal (https://data-usfs.hub.arcgis.com/) and whatever local maps and/or trail reports I can find.
I'm completely anal about accuracy and usability, with the knowledge that what I'm mapping will pop into Mapbox/Natural Atlas/AllTrails/ArtOfTheTrek/etc etc within a few months.
And yeah... I might use iD, but I'm definitely not a beginner mapper.
But always happy and eager to learn and be educated - so on a similar friendly note, thanks for keeping me on point and accountable. It's good that there are other mappers paying attention!

@TomPar Despite what you said, you ARE being overly dramatic. As if my failure to post a speed limit tag on a road makes me liable for a driver's crash or speeding ticket. Likewise, my mapping of a trail or bushwhack route does NOT make me liable for another human's actions or issues on that trail.
I won't even get started on your apparent hostility toward armchair mapping.
Your comments have been noted, but please understand that if we solely rely on in-person survey for mapping, OSM would be nowhere.

Hi there - a very fair question. I actually took them from Strava traces, and only mapped the strongest tracks. I don't normally map bushwhack trails (kind of goes against the whole point of bushwhacking), but the Strava traces were crazy strong, as if these were well-treaded trails.
To be honest, it bugged me afterward that I had added them - I know full well that seeing trails mapped where you want to bushwhack takes all the fun out of it. So based on all that, I'm going to pare them down right now...

Disregard - I added it back myself.

I respect what you're doing, but not how you're doing it. Way #978055205 was deleted by you an hour ago. Can you revert it back please?
It's a valid trail - it's the Tunnel Bypass Trail ffs, and you deleted the bypass!

It appears you're deleting trails that aren't recognized by the NPS?

And thx btw

The issue wasn't that it was 'primary', it was that it was 'primary_link', which won't even render until zoomed in for most data users.

Hey there - you changed the highway classification on NC 212 to "primary_link", which is the designation for an onramp/offramp or access road from another arterial way. I am changing this back to Secondary in a few places where I am mapping near the NC/TN border - can you do the same for the rest of this highway?
Let me know if you need more info or any clarification - thanks!