Skip to content
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

Make sure non-spatial tabular datasets are described as Tables, not Vectors. #63

Open
davemfish opened this issue Jan 14, 2025 · 1 comment
Labels
bug Something isn't working
Milestone

Comments

@davemfish
Copy link
Collaborator

sqlite .db files can be opened by GDAL as vector datasets. That can be inconvenient if the sqlite file is not a spatial database. Similar to the CSV case, just because GDAL can open it does not mean we want to describe the resource as a VectorResource instead of a TableResource.

@davemfish davemfish added the bug Something isn't working label Jan 14, 2025
@davemfish
Copy link
Collaborator Author

We might want to rethink how we determine the correct metadata model for a dataset. Perhaps checking for geometries, or coordinates, or something like that. In the interest of getting this right longer-term, I'm putting it in a 0.2.0 milestone.

@davemfish davemfish added this to the 0.2.0 milestone Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant