Support FlatGeobuf as media_type

[ashiklom]

FlatGeobuf is an awesome, performant open-source alternative to ESRI ShapeFiles, GeoJSON, etc. for vector data. I am proposing the addition of a pystac.MediaType.FLATGEOBUF that resolves to "application/flatgeobuf".

At least, I'm assuming that's the correct MIME Type — that's what's returned by:

curl https://flatgeobuf.septima.dk/population_areas.fgb --head

If all I have to do is just add a line here then I can submit a PR. But I'm not sure if there's something more involved in ensuring FlatGeobuf support.

[TomAugspurger]

Looking at flatgeobuf/flatgeobuf#112, I don't think "application/flatgeobuf" is "official" :/ We'd probably want to wait on that, but I'm not sure.

[m-mohr]

The COG media type for example is also not official yet, but I think we can follow what the community uses until it is official. Adding it to PySTAC may actually help to promote a single media type and not everyone has to search and find one (result might differ), so I'm +1 on adding it.

[gadomski]

@ashiklom if you're willing to make a PR, that would help force an up/down vote on the issue.

@m-mohr what's the skinny on profile=cloud-optimized? Should that be included in the flatgeobuf media type?

[m-mohr]

Is "cloud optimized" a variant of flatgeobuf like (Geo)Tiff vs COG? @gadomski

[gadomski]

I'm not sure, I'm just reading up on it myself. It is based on http://google.github.io/flatbuffers/, which appears to be "cloud optimized" (for some value of "cloud optimized") itself. So my guess is that it's a geospatial specialization of an already-cloud-optimized format. But @ashiklom (or others) should chime in with Actual Knowledge™.

[m-mohr]

Yeah, if it is already cloud-optimized you don't need the profile.