Hi Richard
On 12/6/19 2:07 PM, Richard Duivenvoorde wrote:
On 06/12/2019 07.58, Matthias Kuhn wrote:
On 12/6/19 7:52 AM, Alexander Bruy wrote:
пт, 6 груд. 2019 о 08:44 Matthias Kuhn <[email protected]> пише:
Meanwhile, why not use a well known spatial data file format?
I can be wrong, but using spatial data formats can be lossy in some
cases,
e.g. shapefile/dbf has limits for the field name length and field
length. Some
other formats may lack support for some datatypes, like datetime etc.
Of course is there is a format which allow fast and lossless storage
we should
use it
I think GeoPackage should be fairly stable for this kind of usage.
Well, yes, may be, but given I've seen some issue (locks/crashes etc
etc) with GeoPackages, and myself having issue with true
DateTime/TimeZones's in it... I thought to propose an alternative :-)
Since these files are created as an output and no concurrent access is
expected, I don't think there's a risk for locking issues here.
For DateTime/TimeZones etc, are we sure we will be in a better situation
with "our own" serialized format?
My impression is that the community is experiencing some drawbacks with
GeoPackage/SQLite, but maybe I'm wrong.
Other proposals are very welcome as well. I don't insist on GeoPackage.
All I do is being a bit skeptic that rolling our own format will
magically solve problems that one hundred other formats did not solve :-)
Regards
Matthias
Regards,
Richard Duivenvoorde
_______________________________________________
QGIS-Developer mailing list
[email protected]
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
QGIS-Developer mailing list
[email protected]
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
