Dear Thomas @TomLav In answer to the question, No, I don't think it's been discussed already. Cases like this can be described without DSGs and featureTypes by providing a scalar or auxiliary coordinate variable with a string value and `standard_name` of `region` to identify the region, as described in 6.1.1. The reason this is problematic for chapter 9 is that it lacks x and y coordinate variables. It seems to me that it would be fine to provide a string-valued region variable instead of x and y variables if you want to store the data as a DSG, and you don't want to sketch out the regions explicitly (as in geometries). I don't have a view on whether this should still be regarded as a `featureType="timeseries"` or some new type.
Cheers Jonathan -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/220#issuecomment-561159633 This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
