Add more output formats on CLI

[nuest]

• WKT (should be easy to read in from R, and to save to PostGIS)
• GeoJSON (same as above)
• WKB
• saving the bounding box as a shapefile with ogr2ogr, https://kevinmanion.com/2019-10-12/Command-Line-GIS-2/ shp is dead
• add examples to docs how to read the formats into other languages/databases; if possible, demonstrate with piping on the CLI, e.g. into a PostGIS DB
  • R
  • Python
  • PostGIS (STgeomfromtext ? Or via WKB, see https://postgis.net/docs/using_postgis_dbmanagement.html)
  • QGIS
  • GDAL CLI: showcase how you can continue to use the bounding boxes as data in a workflow, see e.g. https://trac.osgeo.org/gdal/wiki/ProjectingWktFromStdin
  • Can we insert all the individual bounding boxes into a GeoPackage with some bash scripting?

[nuest]

For GeoJSON, demonstrate how to quickly inspect the created output with https://github.com/mapbox/geojsonio-cli on CLI and https://pypi.org/project/geojsonio/ for Python and Jupyter Notebooks.

For R, it might be fun to call geoextent and then parse the output, e.g.

sf::st_as_sf(system2('geoextent --output WKT -b data/path/'))

or could be worth trying out reticulate.

[nuest]

Split up this issue before starting to implement it, then prioritize.

[nuest]

Could be worth taking a look at how STAC constructs temporal and spatial extent: https://github.com/radiantearth/stac-spec/blob/master/collection-spec/collection-spec.md#extent-object