[postgis-devel] ST_AsFlatGeobuf / ST_FromFlatGeobuf ?

Martin Davis mtnclimb at gmail.com
Wed Sep 23 09:20:14 PDT 2020


+1 for this.

The complexity of GeoPackage has always dismayed me.  Lack of
streamability is a big disadvantage, as is the requirement for a complex
boutique piece of software to read it.

On Wed, Sep 23, 2020 at 12:35 AM Björn Harrtell <bjorn.harrtell at gmail.com>
wrote:

> FlatGeobuf is an alternative to GeoPackage, shapefile, GML, GeoJSON and
> similar simple features representations. I see it as a general purpose
> serialization format between systems where direct database access is not
> suitable or possible, but with a minimal performance hit.
>
> FlatGeobuf is "cloud optimized" in that it is designed for optimal and
> streaming I/O. So in a sense you could say FlatGeobuf is the equivalent of
> COG for lossless vector data. This is an area where I believe GeoPackage
> fails and I think it's a big drawback of that format. For example it makes
> GeoPackage pretty much unusable as a WFS / OGC API output format but I
> believe FlatGeobuf fits that use case perfectly.+1
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20200923/7b71f7e9/attachment.html>


More information about the postgis-devel mailing list