Relax schema from required to optional

stac-extensions / pointcloud

Provides a way to describe point cloud datasets. The point clouds can come from either active or passive sensors, and data is frequently acquired using tools such as LiDAR or coincidence-matched imagery.

Apache License 2.0

12 stars 3 forks source link

Relax schema from required to optional #3

Closed hobu closed 1 year ago

hobu commented 2 years ago

When used in practice, the schema object doesn't add a ton of value, and more importantly, I don't know that anyone is going to be using such a complex object to be filtering data. It's either a point cloud with XYZ position values or it's not.

I think we should relax the schema object to optional.

cc @kylemann16

raelwaed commented 1 year ago

I agree with you @hobu in terms of the way I and my client want to search for information.

pc:count - fair enough
pc:type - also good
pc:encoding - isn't this covered by the type field in the Asset Object already?

I think getting stats on the classification is largely a waste of time, but getting actual classifications has more value.

wonder-sk commented 1 year ago

I would suggest to change schema to just a list of attributes: ["X", "Y", "Z", "Intensity", "Classification", ...]

I don't see much use of type and size in a catalog, it's a technical detail that is only making the definition more verbose.