You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if there's a reason coordinates are provided as strings rather than floats. Most geospatial libraries for Python require coordinates to be of type float (such as shapely or pysal), also common geospatial data formats such as GeoJSON store coordinates as floats.
As I am usually integrating mordecai with other geospatial libraries, having the coordinates returned as floats would make this integration a tiny bit smoother. :)
The text was updated successfully, but these errors were encountered:
Thanks for that report! Floats are certainly more useful than strings for lat and lon and I'll change that in the next version. And if you haven't filled out the user survey yet, I'd love to get your thoughts on what else is working or not: https://z0l4ihmu0ud.typeform.com/to/b8FmCfMt
I was wondering if there's a reason coordinates are provided as strings rather than floats. Most geospatial libraries for Python require coordinates to be of type float (such as shapely or pysal), also common geospatial data formats such as GeoJSON store coordinates as floats.
As I am usually integrating mordecai with other geospatial libraries, having the coordinates returned as floats would make this integration a tiny bit smoother. :)
The text was updated successfully, but these errors were encountered: