Crossing the dateline causes a polygon display wrap issue about folium

[ocefpaf]

If anyone finds this issue take a look at:

Leaflet/Leaflet#1293

[wrobstory]

I'm honestly not sure how to address this- seems like a GeoJSON or TopoJSON polygon issue?

[scardine]

@wckoeppen: this artifact is a common projection issue, but a cartographer would be able to explain it better than me (I'm just a programmer). Post this as a question at http://gis.stackexchange.com/ and you will get a good explanation and a few solutions.

[wckoeppen]

Thanks @scardine, I know I can change those lons manually (with code), but it seems overkill for the simple display that I'm using this for. I'll probably just live with it.

[birdage]

that sucks.....

[scardine]

I'm thinking about alternatives for solving this:

• automatically split polygons that cross the international date line
• have an alternative projection where the international date line is placed somewhere else

[birdage]

@wckoeppen do you have a branch that contains an example we can look at, that also includes the geojson you are using? might take a look over the weekend

[wckoeppen]

@birdage whoops! sorry, somehow I missed seeing this. Here's the ipython notebook:
https://github.com/wckoeppen/bering-seabird-vulnerability/blob/master/bin/Bering%20Seabirds.ipynb

The geojson is in the second cell.

(But don't judge me on my terrible loops and other bad coding practices, I'm new.)

[birdage]

@wckoeppen ALL THE JUDGEMENT! (kidding, ill take a look)

[ocefpaf]

I'm honestly not sure how to address this- seems like a GeoJSON or TopoJSON polygon issue?

After reading a lot about the GeoJSON format specs I found out that the recommend way around this issue is to break the -180, 180. Here is an example:

http://nbviewer.ipython.org/gist/ocefpaf/f03e2cb878c891716518

I am closing since we don't have any plans to try to be smart about this issue and do that automatically.