-
Notifications
You must be signed in to change notification settings - Fork 24
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
a single file is probably not going to replace shapefiles #10
Comments
Also I mentioned security about sqlite based formats on twitter, I don't have anything concrete but my security scene is tingling, a database, that can have stored procedures feels an awfully lot like a program that executes code which is not something I'd really trust coming from somebody I don't trust. |
Sqlite has no stored procedures. |
yeah true, though they do have triggers which is what I was thinking of as it can act similarly |
Any particular concerns here? The amount of damage a SQL trigger can do is fairly limited. Worst thing I can think of is that you attach an additional database and a trigger happens to do destructive writes in a table of that attached database. |
you could write a lot of data to the current or other database, the other database could have important stuff (aren't passwords sometimes stored in sqlite database) which would be bad to be overwritten. |
What about GeoParquet? #52 |
Not a good format (at least with current tooling) if editing is important. |
And that's good! one of the issues with shapefiles is that it tried to be all things to all men, so instead we can recommend different formats for different things
data interchange
For making data available and sending it places geojson, csv, kml and gml fill that role, with geojson being the leading one, csv used for super simple point data, and gml used for more complex stuff that geojson can't handle, with geojson being the recommendation for most stuff because 99% of users aren't going to have data that needs gml.
data editing
This is where geopackage, file geodatabase, and spatialite come in, and this is going to honestly depend on what software you are using, file geodatabase is probably a good choice if you're editing in ESRI and geopackage or spatialite would be a great choice for non esri world, just don't post them online when making your data available, post it as geojson.
The text was updated successfully, but these errors were encountered: