This is a static archive of our old OpenStreetMap Help Site. Please post any new questions and answers at community.osm.org.

unable to read contour line numbers

0

Looking at Map with CyclOSM layer turned on. Contour lines show up well but unable to read the associated numbers, no matter what the level of zoom. Is there a setting to increase the number size / clarity?

https://www.openstreetmap.org/search?query=28.77840%20-17.95834#map=17/28.77839/-17.95835&layers=Y

asked 12 May '22, 08:37

fdg334's gravatar image

fdg334
11113
accept rate: 0%

Basically if compare with a map company (Ordanance Survey) that does things well, we are getting a few things wrong:

https://getoutside.ordnancesurvey.co.uk/guides/understanding-map-contour-lines-for-beginners/

1) The contour line should not strike out the number!

2) Numbers need to be bigger;

3) Numbers need to be in a dense/solid colour;

4) In many cases it is not necessary to put numbers on every single line - that declutters the map;

Any comments?

(12 May '22, 08:59) fdg334

One Answer:

5

No, there is no such setting, as what you are looking at are composite raster images.

If you have issues with the style as presented you need to take that up with the creator and operator of the the specific map layer. In this case as a few clicks on the attribution lines will show you https://github.com/cyclosm

answered 12 May '22, 10:41

SimonPoole's gravatar image

SimonPoole ♦
44.7k13326701
accept rate: 18%

edited 12 May '22, 10:54

Understood. Thanks for the explanation.

Have now spent some time exploring the github page but can't figure out any way to give feedback or to contact the creator. :(

(13 May '22, 18:42) fdg334
2

Go to https://github.com/cyclosm/cyclosm-cartocss-style/issues and create an issue. You'll need a github account to do that. Please be polite, and don't make assumptions about how easy it will be to fix or make value judgements about the quality of the map; just describe your issue concisely and dispassionately.

(14 May '22, 08:53) Richard ♦

Thanks @Richard. Just seen your comment and have created an issue as suggested.

(21 May '22, 18:39) fdg334

Source code available on GitHub .