Add image to index

[abarciauskas-bgse]

In writing the COPC content, I thought to create a diagram which depicts how some formats are cloud-optimized versions of existing formats.

[wildintellect]

Could be a table, where we also list datatypes supported? Oh, your image is a table ...

Can you add geojson as a traditional format? or should it be non-cloud formats? ie gpkg Speaking of geojson we should probably mention topojson and row oriented geojson (I'm forgetting the name)

And how do we handle that Zarr/HDF can be points?

[abarciauskas-bgse]

@wildintellect great points.

1. We can add geojson as a traditional format, I assume geojson would be a format for both point and vector data?
2. Can geojson cover topojson and row-orented geojson? I'm just concerned about overloading the table.
3. We can HDF for points as well, but are we recommending Zarr for point clouds at this point (no pun intended)?

[kylebarron]

GeoJSON makes sense in the image table, but newline-delimited geojson and topojson I think are fine to only mention in text.

Are there many people using zarr/hdf for points?

[wildintellect]

• Agreed the variants of geojson should be in discussed in text somewhere.
• Can you change the "points to" to "references in the Raster section, should we label it Raster/Data Cube(s)
• Can you put HDF5 at the top of that section and move points to the middle so we can indicate HDF5 can store points (regardless if we recommend ICESat2 and GEDI come this way)
• How do we indicate overlap, flatgeo and geoparquet are good for points too
• COPC/las is really only for 3D points not 2D, not sure how to show that in the diagram