stamen / terrain-classic

World-wide CartoCSS port of Stamen's classic terrain style
ISC License
144 stars 35 forks source link

Encoding issues for Natural Earth peaks #64

Open almccon opened 8 years ago

almccon commented 8 years ago

pasted image at 2016_07_07 01_07 am Alada? Tepe Qurnat as Sawd?

See also https://github.com/stamen/terrain-classic/commit/c85ab647913c790db9cb0f3a7e97cac3c5e2dc47, #44, #55

almccon commented 8 years ago

I tried importing it with utf-8 like in https://github.com/stamen/terrain-classic/commit/c85ab647913c790db9cb0f3a7e97cac3c5e2dc47, but no difference. We think the shapefile is messed up. Here's QGIS:

screen shot 2016-07-07 at 7 jul 7 59 07

For now, the short term hacky-fix will be to do CartoCSS overrides of the names for these few messed-up peaks.

almccon commented 8 years ago

16 peaks need fixing: (filtered on '?') screen shot 2016-07-07 at 7 jul 11 26 32

fjht commented 7 years ago

I noticed problems with other mountain Mulhacén in Spain renders "Mulhacn" and maybe could be the same issue.

http://maps.stamen.com/terrain/#6/40.091/-3.465 screenshot at 2016-08-18 18 30 37 screenshot at 2016-08-18 18 30 51

In OSM the reference for Mulhacén is not rendered but there's a GeoName near where label "Mulhacn" is.

http://www.openstreetmap.org/search?query=Mulhacen#map=9/37.0382/-2.6559 screenshot at 2016-08-18 18 58 43

nvkelso commented 7 years ago

This will be fixed in the next version of Natural Earth – around 50 peaks were affected as far back as v1.4 but exacerbated by bad unicode conversions along the way.

Related: https://github.com/nvkelso/natural-earth-vector/issues/202