Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OGC API - Coverage versions #81

Open
KathiSchleidt opened this issue Oct 8, 2024 · 8 comments
Open

OGC API - Coverage versions #81

KathiSchleidt opened this issue Oct 8, 2024 · 8 comments
Assignees

Comments

@KathiSchleidt
Copy link
Member

When comparing the approaches taken by rasdaman vs. AD4GD on implementing OGC API - Coverage, one sees very different approaches:

When I discussed this with Joan Maso (author of the AD4GD API running on ODC), he stated that what he sees in the rasdaman version looks like the initial discussions under OGC API - Coverage versions, what he implemented is aligned with the latest version.

I'd like to compare these approaches, see which is closer to where OGC API - Coverage versions is currently going.

@misev
Copy link

misev commented Oct 8, 2024

I get "The connection has timed out" on the AD4GD URL, does it work for you?

@pebau
Copy link

pebau commented Oct 8, 2024

for sure there are version differences, given the continuous changes in OAPI-Coverages (AFAIK SensorThings has not even bothered adopting OAPI). As there are no resources for changing back-and-forth we would wait until adoption and a stable version (if ever).

But talking about comparison, we might start into a comparison of the two pillars in Fairicube, otherwise why do we have two.

@KathiSchleidt
Copy link
Member Author

No idea why you're mentioning STA here, not being used in the project. Background of that accepted standard goes way before the current OGC APIs, but based on our latest analysis during the STA 2.0 update, not fit for purpose. Has been accepted by OAB, STA is formally an OGC API.

That said, the focus here is services for gridded data, where we don't have the level of development as we have for terrestrial point based data with STA (standardized well-deployed API), due to the lack of outlook for WCS we're refocusing on APIs. Based with discussions with EOX, they are at present not capable of providing standardized APIs, so no way to compare these 2 pillars.

However, based on our sibling collaboration with AD4GD we do have access to an OGC API - Coverage endpoint based on the latest version of the OAPI-Coverages - the topic in this thread is the comparison of these 2 approaches

@misev
Copy link

misev commented Oct 8, 2024

@KathiSchleidt if you're in contact with AD4GD you could let them know their service is down.

@misev
Copy link

misev commented Oct 9, 2024

For reference: rasdaman implemented OGC API - Coverages - Part 1: Core (0.0.2) a year ago which I think corresponds to the current draft version; generally all parts are supported except metadata filters (queryables) and coverage tiles.

Within Testbed-19: Jerome, the main editor of the draft standard, tested and used the rasdaman service at the end of 2023 with his own Ecere GNOSIS client and it all worked very well; Benjamin Pross from 52north also developed a testing suite which rasdaman passed.

@KathiSchleidt
Copy link
Member Author

Just checked, AD4GD OAPI-C is up again.

From what I can see, there were major changes between V0.0.2 and 0.0.7, I'll get in touch with Jerome to better understand the differences.

Is there an outlook for updating the rasdaman OAPI-C or are we stuck with the status-quo?

@misev
Copy link

misev commented Oct 9, 2024

Rasdaman is compliant with the 0.0.7 draft as far as I know: it has not changed since we did the implementation last year.

@misev
Copy link

misev commented Oct 9, 2024

The Testbed-19 GeoDataCubes Engineering Report lists OGC API - Coverages 0.0.6, although the link points to the 0.0.7 draft. I think there's no difference, but you could clarify with Jerome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants