Hi @TomLav -- thanks for reaching out. That discussion was partly taken up in the development of: http://cfconventions.org/cf-conventions/cf-conventions.html#geometries but as you can see in Example 7.15, the point coordinates are still more or less required to use the timeSeries feature type.
>From my perspective you have two options: 1) use (a) fake or (b) highly >idealized point coordinates so client code will read the `timeSeries` data >with maybe unfortunate handling of spatial data, or 2) leave out the spatial >coordinates and use the rest of the `timeSeries` feature type and suggest some >edits to the spec that allow that encoding to be valid. In 2, I would want to see a mechanism to reference some external description of the region -- possibly including a polygon geometry. Which could then circle back to putting a geometry (maybe just a convex hull) in the NetCDF file and using the centroid of the polygon as an idealized point location. This ends up looking an awful lot like 1b described above. and would put the onus on you to create .bounding polygons and idealized point locations. Hopefully that's helpful. - Dave -- 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-561157807 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].
