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
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.
The text was updated successfully, but these errors were encountered:
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.
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 aVectorResource
instead of aTableResource
.The text was updated successfully, but these errors were encountered: