> Anders Torger <and...@torger.se> hat am 14.12.2020 15:49 geschrieben:
> 
> Okay, but why does the OSM-Carto renderer, and all other renderers known 
> to man(?) make multiple text labels then, when it should be a single 
> one? 

OSM-Carto renders labels primarily based on the following constraints:

* due to the requirement of real time updates more complex operations are 
severely restricted.  Clustering features, aggregating the clusters 
geometry-wise and labeling the aggregates are such operations.
* we want the relationship between the data in the database and the rendering 
results to be intuitively understandable for the mapper so they can derive 
useful feedback from the map.  That also limits the complexity of data 
processing we can use.
* like all zoomable interactive maps OSM-Carto has to deal with the problem 
that high quality labeling is zoom level dependent.  At the same time having 
different approaches to labeling at different zoom levels adds a lot of 
complexity to the style - and OSM-Carto is already one of the most complex map 
styles in existence.  Hence compromises are made that look better on some zoom 
levels than on others.

As far as other map styles are concerned - i have said that before: high 
quality cartography is expensive and the bulk of the digital map market is low 
quality and low price - hence requires low costs.  And the willingness to 
engage in strategic investment in methods for high quality cartography in the 
wider OSM ecosystem as well as in the open source GIS sector is so far rather 
small.  

What can you do as a mapper:  Produce an accurate representation of the 
geography that is non-complex in structure, is easy for you to map and maintain 
and that is consistent with how others map things and don't adjust your mapping 
to what you believe is most convenient for data users.

--
Christoph Hormann
https://www.imagico.de/

_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Reply via email to