Ancestors

Written by Health Is Wealth on 2024-09-15 at 16:22

So, @streetcomplete when filling in the questions using the Street Complete app, where are the additional details such as; the road surface, street lighting etc viewable? I can't see such details on the OpenStreetMap website or the OrganicMaps app, even with overlays... So, where are they viewed? What's the point in filling these details in? Are they collected just in case someone develops an app that decides to show this info maybe? #openstreetmap #OrganicMaps

=> More informations about this toot | More toots from healthiswealth@fosstodon.org

Toot

Written by Alan Grant on 2024-09-15 at 18:05

@healthiswealth @streetcomplete The default map at osm.org does distinguish paved from unpaved surfaces, although subtly - in the screenshot the southern Carretera Austral is paved, the northern part and route 235 unpaved.

Surface is, if anything, more important for routing than for rendering. Some routers such as cycle.travel allow you to directly include or exclude certain surfaces, others will adjust estimated travel time depending on the surface.

=> View attached media

=> More informations about this toot | More toots from alan@en.osm.town

Descendants

Written by Alan Grant on 2024-09-15 at 18:20

@healthiswealth @streetcomplete There are also highly customisable map applications such as OsmAnd, which has options to "show road surface" and "show street lighting".

And then there are other uses for OSM data apart from rendering and routing, such as research and statistics. So it's hard to know how any given tag might be used.

=> More informations about this toot | More toots from alan@en.osm.town

Written by Health Is Wealth on 2024-09-15 at 21:56

@alan @streetcomplete Thanks Alan! Yep understand now from everyone's replies inc yours, thank you 😊

=> More informations about this toot | More toots from healthiswealth@fosstodon.org

Proxy Information
Original URL
gemini://mastogem.picasoft.net/thread/113142893073464058
Status Code
Success (20)
Meta
text/gemini
Capsule Response Time
372.694742 milliseconds
Gemini-to-HTML Time
1.371667 milliseconds

This content has been proxied by September (3851b).