You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: edloach [Submitted to the original trac issue database at 4.36pm, Monday, 2nd February 2009]
I recently decided to use ITOworld's OSM Mapper product to track down anything tagged with source=NPE in this area with a view to visiting it to create a track. It looks like there are some users using Potlatch to trace the NPE maps (as I have done) and using highway=unclassified rather than highway=road to indicate the road hasn't been physically checked. I've also seen areas where these seem to later get changed to tertiary when they are checked which to me looks terrible. While adding highway=road to the available choices in the popup list can't guarantee a user will use it, it may improve the chances.
The text was updated successfully, but these errors were encountered:
Reporter: edloach
[Submitted to the original trac issue database at 4.36pm, Monday, 2nd February 2009]
I recently decided to use ITOworld's OSM Mapper product to track down anything tagged with source=NPE in this area with a view to visiting it to create a track. It looks like there are some users using Potlatch to trace the NPE maps (as I have done) and using highway=unclassified rather than highway=road to indicate the road hasn't been physically checked. I've also seen areas where these seem to later get changed to tertiary when they are checked which to me looks terrible. While adding highway=road to the available choices in the popup list can't guarantee a user will use it, it may improve the chances.
The text was updated successfully, but these errors were encountered: