Specificity vs Readability
Skrevet af 3ngineer den 29 april 2017 på English Sidst opdateret den 22 maj 2017.Sometimes I wonder if the ability to define such specific details actually makes the map more confusing and inconsistent rather than informative. By no means am I an expert, but I have a feeling that there’s a lot of info that’s practically not needed. The ability to add it just makes people fight and unhappy with others’ judgement. Also, the map can become confusing when very similar types of things are drawn different ways; I think that contributes to OSM’s messiness. Nevertheless, if we take out too much info, we would just become Google maps XD so perhaps just ensuring similar things have similar styles is the best approach.
Diskussion
Kommentar fra Warin61 skrevet 29. april 2017 kl. 22:29
Some seek dirt roads, others avoid them. Same thing with toll roads. I have detailed some inclines too .. under 15% is my cut off point.
Those might be some of the ‘details’ you regard as ‘practically not needed’?
Kommentar fra Alan Trick skrevet 30. april 2017 kl. 18:44
This really depends on what you’re up to, but on things like back-country trails I often find it very helpful to know things like trail_visibility & sac_scale.
There are certainly a lot of ways that have superfluous tags as a consequence of import scripts though.
Kommentar fra Carnildo skrevet 1. maj 2017 kl. 21:24
Speed limits are pretty useful when finding the fastest route.
Kommentar fra Piskvor skrevet 2. maj 2017 kl. 15:41
Different people care about different details. Lane attributes? Destination signs? Maxspeed? Lit? Wheelchair access? Stairs with stroller ramps?
“I don’t need this” != “this is useless”.