Closed GerritGue closed 1 year ago
Hi,
Thanks for opening an issue. The geometry column in SimpleFeatures should generally be called "geom". Issues arise if this is not the case because in some instances I (lazily) declared the geometry column to always be named "geom" rather than providing flexibility. Maybe that is the issue? One workaround is to read the file with ArchGDAL and convert it to a SimpleFeature object (https://acgold.github.io/SimpleFeatures.jl/dev/reference/#SimpleFeatures.df_to_sf).
I created SimpleFeatures so I could test out Julia for a project focused on a large commuting dataset, so there are some cases where I prioritized functionality for my use case rather than general use. I have since left my postdoc position and gotten a new job, and I am not able to keep this package up to date as the Julia GIS ecosystem is maturing. PRs are very welcome, but I would also highly recommend taking a look at GeoDataframes and ArchGDAL which have much better long-term support. It looks like GeoDataframes recently added the ability to hold CRS data within DataFrame metadata (https://github.com/evetion/GeoDataFrames.jl/releases/tag/v0.3.2), which was the functionality that was previously lacking and spurred me to create SimpleFeatures.
Thank your for your reply, this solves the issue and congrats on your new position
Hi,
first of all, thank you for your efforts to bring the functionality of the sf package to Julia!
Describe the bug
While diving into the package, I ran into an error regarding SpatiaLite (".sqlite") files. I just created a dummy file containing random points which can be downloaded here.
Minimal Working Example
I get the following error message:
Reading the data with ArchGDAL works as expected
leads to
Reading GeoJSON and GeoPackage files works as expected.
Edit: I also tried to load the file using GeoDataFrames and it works as expected:
leads to
Versioninfo()
And I am using SimpleFeatures.jl v0.2.2