[OSM-talk] Macromapping problems

Yves yvecai at gmail.com
Tue Aug 22 04:39:55 UTC 2017


I'm quite certain that this could be solved by a crowdsourced OpenLabelMap, 
Mountain ranges come into discussion in various mailing lists from time to time every year, but any solution faces the ground truth rule and high resolution of OSM a hard way. 
A separate database is IMHO the way to go. 
A crowdsourced version of Natural Earth, maybe? 
Yves 

Le 22 août 2017 01:42:35 GMT+02:00, "Daniel Koć" <daniel at xn--ko-wla.pl> a écrit :
>I guess most of you understand the problems of so called "micromapping"
>
>(very detailed geo data mapping). But when I started to look at the 
>opposite end (macro level), it looks even worse.
>
>Low zoom rendering on default map style lacks lot of important things 
>(see https://github.com/gravitystorm/openstreetmap-carto/issues/2688 ).
>
>We have basically:
>
>- land/water distinction (but some big lakes are missing for example)
>
>- ice areas
>
>- country (and district) borders
>
>- capitals and big cities
>
>- big roads
>
>- nature reserves
>
>- railway and ferry lines
>
>- big military areas
>
>
>What we don't have there:
>
>- big landuses, like forests, farmlands, sands and grasslands
>
>- ocean and sea names
>
>- continent names
>
>- big deserts
>
>- big mountain chains
>
>- big rivers
>
>
>Of course we can have some of them, but while landuses can be added 
>quite easily, it's different with the rest. Rivers have their own 
>problems, which we've just started to solve with crafting some 
>classification, but all the big area objects share at least one common 
>issue: lack of precise borders.
>
>That's probably why we have Asia mapped as a node in the middle of
>nowhere:
>
>http://www.openstreetmap.org/node/36966065
>
>the same for Andes:
>
>http://www.openstreetmap.org/node/3446705497
>
>and not a trace of Sahara _desert_ in Nominatim:
>
>http://www.openstreetmap.org/search?query=sahara
>
>
>You get the picture probably. We started as a city-scale project with 
>routing as the most important goal, but now we're "The map" for every 
>GIS data-related activity. I think this is the time to look how should 
>we map the biggest objects in the world? Our attitude is high accuracy 
>and ground truth, which are not easy to apply there.
>
>There are also other problems, like no special tools for macro objects 
>probably - for example Overpass service is choking with some data 
>requests even at country level. Another problem is importing data for 
>planet/continents, because there's too much of them already. There is a
>
>tool to filter some of them (
>https://github.com/gmgeo/osm-carto-lowzoom 
>), but it's not easy to customize - you need some programming skills.
>
>How do you think we could improve macro level mapping, rendering and 
>data analysis?
>
>
>-- 
>"Like a halo in reverse" [M. Gore]
>
>
>_______________________________________________
>talk mailing list
>talk at openstreetmap.org
>https://lists.openstreetmap.org/listinfo/talk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20170822/a9de5359/attachment.html>


More information about the talk mailing list