search

copcio / copcio.github.io

Geospatial, compressed, range-readable, LAZ-compatible point cloud format.
https://copc.io
MIT License
114 stars 15 forks source link

Mime/Content Type? #53

Open rcoup opened 2 years ago

rcoup commented 2 years ago

Are there any thoughts/conventions for MIME/Content-Type values for COPC files?

Maybe application/vnd.laszip; profile=copc ?

Related issues for COGTIFF: https://github.com/cogeotiff/cog-spec/issues/13 https://github.com/opengeospatial/CloudOptimizedGeoTIFF/issues/1

hobu commented 2 years ago

For planetary computer, we went with

application/vnd.laszip+copc

The rationale was to follow GeoJSON's registration. Profile certainly makes sense too though.

I didn't have a strong opinion on the topic. If someone does, please put forward the rationale for one form or another. I don't understand the intricacies of IANA registrations, as they've always seemed a bit arbitrary to me.

rcoup commented 2 years ago

application/vnd.laszip+copc seems sane enough to me 👍

I don't understand the intricacies of IANA registrations, as they've always seemed a bit arbitrary to me.

Agreed!

m-mohr commented 2 years ago

As it has the vnd. prefix, it is fine as it is, I think and I'll also use it in STAC Browser now.

But just a short remark here if that is meant to go through IANA at any time: Usually they do <sub-format>+<format>, so e.g. geo+json or in this case copc+(vnd.)laszip. So if you try to parse such things, you'd look for the primary format in the part after the +, which would now be copy instead of laszip. So it might be worth thinking about switching the order. Although I'm also not 100% sure whether this would then result in application/copc+vnd.laszip or application/vnd.copc+laszip. I hope it would be application/copc+vnd.laszip.