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 post and 2 tutorials on single-file open geospatial standards #150
Conversation
To ease reviewing, herewith the compiled html versions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice work!! 👍
I have some suggestions, but it is up to you to decide how to deal with them.
Thanks @hansvancalster for reviewing. Regarding putting GPKG after GeoJSON, I have some counterideas, so I'll await other people's ideas:
It's a good idea to show how to add multiple layers in GPKG, I'll add that. Regarding rasters in a GPKG, it seems I only tried it with a GRTS master grid - and that means my footnote in the article has a mistake (I've messed up with RasterLite here, will fix it). I was coping at that time with very large numbers (Int32 GRTS addresses), which is supported by GeoTIFF but not by GPKG. (And the RasterLite alternative got so inflated with larger rasters (file size) compared to GeoTIFF (really a lot) that that option was not good enough to me). So yes, I'll give GPKG another try for rasters, with more simple data; I'm curious whether it is better at filesize than RasterLite (which is also an SQLite implementation). Anyhow, for vector data GPKG was much more efficient in filesize than SpatiaLite (another SQLite implementation). Both RasterLite and SpatialLite exist longer but clearly GPKG is now preferred and it is the only one which is embraced and maintained by the OGC consortium. |
Co-Authored-By: Hans Van Calster <hans.vancalster@inbo.be>
Long live git. It seems I did an experiment with rasters in GPKG (although obsoleted it because of the unsupported Int32 type). See these lines. And the conclusion was: GPKG filesize can even be smaller than GeoTIFF 😃 ! Some work is to be done, obviously. It may even be better to split off GPKG in a separate tutorial, combining vector & raster, or perhaps just add another GPKG section in the raster tutorial. Actually I prefer the latter, hence keeping vector & raster separated; mixing up both will complicate matters and make it more difficult to the reader. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice tutorial. I've a few comments.
Co-Authored-By: Thierry Onkelinx <ThierryO@users.noreply.github.com>
Co-Authored-By: Thierry Onkelinx <ThierryO@users.noreply.github.com>
A few approaches have been tried and compared. More information is available at r-spatial/stars#250
Herewith newly compiled html output. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great post! I very much appreciate the extra effort you have put into this. The comparison tables are great and each of the tutorials are very instructive. 👍
Is this online yet? Wanna read it. 😄 |
Just 😉 |
I believe it is time to introduce these formats to scientists so that they learn and implement their usage.