spacing typecast to int

[jwardbond]

voronoi-diagram-for-polygons/longsgis/longsgis.py

Line 86 in bb6ff49

spacing = int(0.25 * minimum_distance(gdf)) # less than 0.5? The less, the better?

Hello!

This line here changes spacing to int. This works okay for certain projected coordinate systems, but fails for others (any time spacing < 0, which happens when using e.g. buildings in EPSG:4326).

I think the code is still functional if this is taken out, and spacing is left as a float. Is there a reason for this type conversion?

[longavailable]

This line here changes spacing to int. This works okay for certain projected coordinate systems, but fails for others (any time spacing < 0, which happens when using e.g. buildings in EPSG:4326).

Exactly. int() will not work on the most case in a geometry coordinate system(GCS).

I think the code is still functional if this is taken out, and spacing is left as a float. Is there a reason for this type conversion?

No too much reason. int type is simple than float, especially in most PCS situations.

Let's see if float will work better.