GeoServer is now linking resource providing all possible representations... I was thinking, if the current resource is a JSON, maybe the client is just interested in that format, and we could link just that. And then, eventually provide the other representations as alternate links in the target resource
I think I've also seen links without the format, and just let content negotiation handle the target format... however, how does one discover the available formats?
5 replies
I haven't seen an answer to this in commons, but maybe I've just overlooked it
All, the discussion on Hierarchical Collections is continuing on the GitHub Issue opengeospatial/ogcapi-code-sprint-2021-10#5.
The stand-up session starts at 09:00am EDT.
anyone else?
Data query elevation in RHEALPIX and H3 in a Leaflet/Jupyter Notebook.
with an advanced client you would somehow want to see the uncertainties as well (e.g. std from the higher resolutions aggregation)
"almost" managed to show in the stand-up
And in our demo web client. Shall we upload those already to the screenshots folder?
All issues logged during the October 2021 Code Sprint have now been moved to the relevant SWG repositories i.e. OGC API - Common repository and OGC API - DGGS repository.
The Open Geospatial Consortium (OGC) and ISO/TC 211 invite software developers to the November 2021 Geospatial API Virtual Code Sprint, to be held from November 15-17, 2021, with a pre-event orientation webinar on November 9. Registration is available here, and is open to the general public.
This is a gentle reminder that today, the 9th of November, we will run the pre-event welcome webinar, for the November 2021 Geospatial API Code Sprint. The webinar will run from 9am-10am EST, and it will set the context for the upcoming code sprint, next week. The webinar will take place at the #Main Stage of the OGC Discord server. You can install Discord for Windows/Mac or Linux at this link, or run the web version. You will need to register in Discord, if you have not done so already.
Approximately one hour before the event, we will open the self-registration for the OGC Discord Server. When you connect to the OGC Discord server, you will land in the #Registration channel. These are the instructions for self check-in:
- Type in the channel: "!email YOUR EMAIL ADDRESS", replacing YOUR EMAIL ADDRESS by your email address. For instance: "!email ghobona@example.org". This email needs to be the same email you provided during the registration for the code sprint. It does not matter if it does not match the one you are using in Discord - the email is only used for the purpose of self registration.
- After you type in the command, you should receive a verification code on that email. Type in the channel: "!verify VERIFICATION CODE", where VERIFICATION CODE is the code you received by email. For instance: "!verify #$"%!&//##()". After you are verified, you should gain access to the rest of the channels, and you can proceed to the #Main Stage.
If you encounter any issues, you can send @doublebyte1 a direct message.
Day 1 has just ended. It was a very productive day. We had discussions on queryables and geometry simplification opengeospatial/ogcapi-features#654. We also had Mentor Stream sessions on Sharing data through OGC API - Features, as well as another session on Introduction to SpatioTemporal Asset Catalogs (STAC) and its use of OGC API features.
Day 2 has ended. It was another excellent day of coding, tutorials, and discussions. We had Mentor Stream sessions on Load feature data into your frontend application and Testing implementations of OGC API - Features for Compliance to the Standard. There were preliminary demos of geometry simplification through OGC API - Features.
Tomorrow (Day 3) at 13:00 EST there will be a Features and Geometry JSON Lightning Talk.