-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a need to standardize geom
and geometry
across ecosystem
#164
Comments
We have
@evetion I noticed this the other day too, is there a reason to still use Also GADM.jl recently fixed their |
Using |
We should as much as possible standardise table columns, it's worth the long term simplicity |
Understanding that GI.geometrycolumns is being implemented making this less of an issue: e.g.
or just
|
|
Yeah... good demonstratiion that |
I'm finding
geom
andgeometry
used interchangeably but this creates some conflicts across package. It seems like some guidance might be needed:Documenting some of what I've noticed:
@evetion uses
geom
in GeoDataFrames which then can not be passed directly to @rafaqz Raster.rasterize@asinghvi17 also uses
geom
in GeometryOpsGeoInterface has a
GeometryCollection
but a function call that isgetgeom
Shapefile creates a
geometry
columnThe text was updated successfully, but these errors were encountered: