search

twhiteaker / CFGeom

CF Convention for Representing Simple Geometry Types
MIT License
9 stars 4 forks source link

Document motivation in comparison to DSG. #33

Closed dblodgett-usgs closed 8 years ago

dblodgett-usgs commented 8 years ago

What does DSG do that's similar to what we want? What doesn't DSG do that we need? How does what we are proposing work with / build on DSGs?

BobSimons commented 8 years ago

DSG handles data from one or a collection of TimeSeries (point), Trajectory, Profile, TrajectoryProfile or TimeSeriesProfile. So measurements are from a point (TimeSeries and Profile) or points along a trajectory. DSG can be used for at least some of what you want to do here if you say, e.g., I have a TimeSeries which is stream flow measured (or modeled) at a given point on a stream. But DSG has no system to define a geometry (point, polyline, polygon, etc) and say e.g, The expected rainfall in this polygon for some period of time is 5304 liters, except to assign a nominal point (centroid?) or just use an ID (e.g., San Francisquito Catchment section 5A).

Separately: DSG has 3 systems for dealing with ragged arrays, but all of them are only to be used in the context of DSG and are not available for general use in CF. Our system takes one of those systems (contiguous ragged array) and generalizes it for use for any purpose in CF, including an encoding of WKT.

dblodgett-usgs commented 8 years ago

Thanks for the head start @BobSimons - @marqh and I took actions from the call today to flesh out this discussion in our wiki/readme content here. More to come.

bekozi commented 8 years ago

Thanks again for the comments @BobSimons. I am using them in the poster text.

dblodgett-usgs commented 8 years ago

I think we've done this issue justice in the readme and poster.