are clipping options from leaflet implemented in folium?

I’m completely new to folium and leaflet as of today, so maybe this is a silly question. I am plotting a LineString (though Polygon has the same behavior) on map and I noticed that I get visual artifacts when I scroll the map such that the perimeter is off the viewable area.

From googling around, I think it sounds and looks pretty much like this issue.

Edit 10/22: fixed a wrong variable name Here’s a simple version to illustrate:

import folium

lat, lon = (44, -93)
m = folium.Map(location=(lat, lon),
               zoom_start=12)

## used to be in the variable `box`; fixed as noted above
coords = [[-93.2, 43.8], [-92.8, 43.8], [-92.8, 44.2], [-93.2, 44.2]]
line = {'type': 'Feature',
        'geometry': {'type': 'LineString',
                     'coordinates': coords }
        }

folium.GeoJson(line, name='line',
               style_function=lambda x: {'color': '#999999',
                                         'fill': '#999999',
                                         'opacity': 0.8,
                                         'fillOpacity': 0.5}).add_to(m)
m

This is what I get on Chromium 62.0.3202.62 and Firefox 56.0.1:

Is this an instance of the clipping documented on the leaflet issue? If so, is there a way to get at CLIP_PADDING or padding as referenced over there?

[jwhendy]

Bah. Well, as is not that surprising (as it happens to me often), in the process of clarifying my thoughts for an issue at leaflet, I had a sudden burst of insight: what if the issue is the fact that I defined a LineString and then said to give it a fill?

Reviewing some documentation I’d run into when starting to play with folium, I found this on that geometry:

Points and lines are also similar in that they have no area: there is no inside or outside.

Huh. Well that’s interesting. Only one way to find out how this plays out in folium/leaflet and that was to specify 'type': 'Polygon' instead, which I also learned requires one more level of list nesting. With the original example above, I just changed it to this:

coords = [[
    [-93.2, 43.8],
    [-92.8, 43.8],
    [-92.8, 44.2],
    [-93.2, 44.2],
    [-93.2, 43.8],
]]
line = {'type': 'Feature',
        'geometry': {'type': 'Polygon',
                     'coordinates': coords }
        }

It worked! I don’t get that triangle artifact with this method. Pretty sure it’s a fluke that you can specify a fill for a line, but perhaps that’s an abuse of the shape’s intent and it just doesn’t handle it well?

Mystery solved, programmer’s angst resolved, thorn in brain removed… I can now sleep well tonight, and thanks once again for the assistance/patience! Hopefully this trail of breadcrumbs helps someone down the road.

[jwhendy]

Figured it out. 0.5.0 release is dated 2017-09-13; looks like vector_layers were created or refactored on 2017-09-17. I installed from git and now I can use this.

My real shape is a complex polygon and I still show clipping/glitching with GeoJson, but vector_layers.Polygon is working great. Thanks!