search

opengeospatial / ogcapi-coverages

OGC API - Coverages draft specification
https://ogcapi.ogc.org/coverages
Apache License 2.0
22 stars 13 forks source link

Not only gridded coverages #7

Closed chris-little closed 4 years ago

chris-little commented 5 years ago

I am unhappy with the statement: "Only gridded coverages" in the first draft document, as it is feasible to retrieve MultiPoint point cloud based coverages. The UK Met Office and partners are implementing 3/4D curve based coverages, admittedly on underlying gridded data initially. We should at least consider whether the generic coverage API could tackle these approaches to avoid being locked into a 'gridded only or image coverage' mindset.

pebau commented 5 years ago

George pointed out that this is about a first focused approach, not yet full generality. BTW, subsetting as defined in the draft uploaded (and as per WCS Core, just read there) would work on point clouds, but I would not put emphasis on this at the current stage.

-Peter

On 28.03.19 11:46, Chris Little wrote:

I am unhappy with the statement: "Only gridded coverages" in the first draft document, as it is feasible to retrieve MultiPoint point cloud based coverages. The UK Met Office and partners are implementing 3/4D curve based coverages, admittedly on underlying gridded data initially. We should at least consider whether the generic coverage API could tackle these approaches to avoid being locked into a 'gridded only or image coverage' mindset.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/opengeospatial/ogc_api_coverages/issues/7, or mute the thread https://github.com/notifications/unsubscribe-auth/AF0ejoBaW74VDlGz4vwCH3X3Iyzy2h3Tks5vbJ2NgaJpZM4cP2fd.

-- Dr. Peter Baumann

  • Executive Director, rasdaman GmbH Bremen (HRB 26793) www.rasdaman.com, mail: baumann@rasdaman.com tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
  • Professor of Computer Science, Jacobs University Bremen www.faculty.jacobs-university.de/pbaumann mail: p.baumann@jacobs-university.de tel: +49-421-200-3178, fax: +49-421-200-493178 "A brilliant idea is a job halfdone."
percivall commented 5 years ago

Can we get weather data in uniform grid for now? Model outputs for precip and windfield would be relevant to a scenario on urban flooding.

pebau commented 5 years ago

yes, we have ERA-interim timeseries data available in WGS-84, with several variables including wind speed and precipitation. But I am sure our weather/climate colleagues have almost infinitely more :)

percivall commented 5 years ago

@chris-little what might UK Met Office supply on weather?

chris-little commented 5 years ago

Easiest at present is our DataPoint service but this is not gridded. Currently, our operational gridded data services are rather file-format orientated and the newer data-tile orientated services are not free at the point of use.

chris-little commented 5 years ago

@percivall Update to above, you can get some 24 hours out-of-date info in S3 buckets at Registry of Open Data on AWS. The Met Office data is Open Weather Data. Do you think this meets your need?

dblodgett-usgs commented 5 years ago

@chris-little -- I'm also not happy with the strength of this statement. There are aspects of the spec that are specific to gridded datasets, but it shouldn't be stated as strongly. 

Only gridded coverages are addressed, not MultiPoint/Curve/Surface/SolidCoverages. Reason is that gridded coverages receive most attention today.

Gridded coverages are the primary data type considered but other kinds of datasets are not meant to be excluded.
chris-little commented 4 years ago

How about this wording: "Only gridded or multi-point coverages are addressed, not Curve/Surface/SolidCoverages. The reason is that these are common use cases that receive the most attention today.

Gridded coverages or 'point-cloud' multi-point coverages are the primary data types considered but other kinds of datasets are not excluded."

pebau commented 4 years ago

+1 Peter

dblodgett-usgs commented 4 years ago

Looks good to me too.

percivall commented 4 years ago

The terminology suggested by Chris is now the title of Use Case #2 for the Coverge Processing Sprint https://github.com/opengeospatial/CoverageProcessAnalytics/blob/master/UseCases_Specs.adoc

Chris - any chance you can make data available for the Sprint in January at ESIP?

George

On Mon, Dec 9, 2019 at 5:10 AM David Blodgett notifications@github.com wrote:

Looks good to me too.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/opengeospatial/ogc_api_coverages/issues/7?email_source=notifications&email_token=AA5EV7COACYRRFUHANAUA53QXY7U7A5CNFSM4HB7M7O2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGJDTKQ#issuecomment-563231146, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA5EV7EVSULCFYM644DPYWDQXY7U7ANCNFSM4HB7M7OQ .

-- George Percivall CTO, Chief Engineer Open Geospatial Consortium (OGC) gpercivall@opengeospatial.org @Percivall

www.opengeospatial.org

Keep up with all the OGC news by signing up to our quarterly newsletter at http://newsletter.opengeospatial.org Interested in attending the next OGC Technical and Planning Committee Meeting? Find out more at http://www.ogcmeet.org

cmheazel commented 4 years ago

The working draft will be updated to include this wording. I suggest we explore non-gridded coverages in the January sprint.