southkorea / southkorea-maps Goto Github PK

Attribute NL_NAME_2 - containing Korean and Chinese characters - is illegible.

Hello,

Thank you for these great files. Would it be possible to add the census area divisons as well ? As far as I know, these are the smallest units used for population count, something equivalent to census tracts in the USA (example on this map: http://cfile235.uf.daum.net/image/1977DB344F94E93838D23C).

Cheers,
Francois

Coordinates have too large values.
They should have values such as [ 126.271987338792329, 33.109158944008691 ].

ex: kostat/2012/json/submunicipalities-geo.json

{
"type": "FeatureCollection",                                                                                
"features": [
{ "type": "Feature",
"properties": { "code": "3902062", "name": "예래동", "name_eng": "Yeraedong", "base_year": "2012" }, 
"geometry": { "type": "Polygon", "coordinates": [ [ [ 147972.970269332377939, -18146.812690775732335 ], [ 147881.628420894761803, -18206.289605131110875 ], [ 147843.39323666630662, -18287.009287894874433 ], [ 147817.903019478806527, -18259.396299857762642 ], [ 147766.922837691759923, -18155.310603178048041 ], [ 147293.222467965155374, -18752.210393314802786 ], [ 146923.611023385106819, -19304.505798392870929 ], [ 146845.016038033500081, -19457.448492387033184 ], [ 146806.780631734669441, -19567.90729302177715 ], ...

Please add Dockdo!

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Provided maps are not rendered properly in Google Fusion Table.

example)

According to this answer, Fusion Table just renders maximum 10 polygons per each region.

One possible workaround to this is: sort polygons by their size in descending order. Then maybe the most important regions of each province/city will be rendered properly.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.