Hello,

I downloaded "Gridded Population of the World, Version 3 (GPWv3): Centroids". It is really terrific data! Bravo!

But I must say that I wasn't able to use correctly administrative level names: problems with diacritic symbols (like "ñ", "ç", "à" etc.).

I couldn't identify encoding of data (unicode, ISO8859-1, ?). So please could you give information about this encoding (inside metadata?).

Thanks in advance.
Michel (France)

RE : http://sedac.ciesin.org/maps/client

Hello,

The blue background is confusing, because I associate blue with the color of sea.

It is particularly true of the world map of Flood Hazards, I can not associate easily the colors on the maps, and the colors in the legend.

Yours sincerely,

Do you plan to provide your data layers as REST services?

By having to download multiple files, 50 records at a time, it increases the chance for error. But also means I need to spend lots of time making sure I got everything.

If you want to use SEDAC WMS with openlayers.js, it would be nice to provide a (link to a ) working sample code like http://jsfiddle.net/F9pUs/ (which actually does not show the SEDAC layer)

This isn't really feedback, but I didn't see another way to contact you about updating the list of small-area estimate studies. I worked with colleagues on a poverty map of the Lao PDR that is not included in the list. Here is the link: http://www.laoatlas.net/links/PDF/The%20Geography%20of%20Poverty%20and%20Inequality%20in%20the%20Lao%20PDR.pdf. Thanks, Nick

perhaps this can be a snapshot image before trying to load the client everytime someone visits the home page. Click on the snapshot would enable the client or something like that..

Besides theme, year published, and year of data, can we have geographical coverage? Some users may be looking for data in specific areas, so it would be nice to have that upfront.

I downloaded ( by hand) all of the tiles in GMIS in a geographic projection. When I examined the booundary tiles (01, and 60) it is clear that these were not projected properly from UTM and have longitude extents of 360 degrees.

Map client – needs to point back to the source of the data – e.g. through link that show where the basic data is coming from, or through citation information in legend or label. This would enable readers to get reference documentation as well as getting the source datasets. Also would be useful to be able to print out the map and map metadata.

The browse and faceted search performs great. My only thought is that it would be better to have the data listed in one column instead of two. Browse could be smaller on this page – then larger once you select your method of access (i.e., Website, download, maps, more….