I see "EO series" in the GUI while the 2 others are not shown (we have 3 in /collections)... Do these "collection" metadata look OK to you ? Are you trying to retrieve all content before listing the 3 collections ? Only the one with "id" is series will typcially have a geometry..
Brad Hards
@bradh
So I'm getting the collection OK, but only the first is getting added.
There should be three child nodes in the SpaceBel EO-Catalog tree, but only Resources is showing up
ycespb
@ycespb
Does it matter that the link to the JSON schema will not resolve ? We could remove these links if that helps..
Brad Hards
@bradh
It shouldn't.
ycespb
@ycespb
Maybe the fact that the URI has a query parameter in these collection metadata ? We have /resources?type=xxx for the moment...
@bradh , I am compiling a Technology Integration Experiment (TIE) matrix identifying which clients and services were bound together during the hackathon. Which services does the OpenSphere demo link to?
Brad Hards
@bradh
@ghobona: pygeoapi, geoserver and spacebel
I'll have to send you some company details too, or just PR them.
I'm just rebuilding (tests take a while) and will push an update
@ghobona Are there any other features servers?
ycespb
@ycespb
@bradh In the GUI, I see "Resources" under Spacebel EO-Catalog which is the id of the 1st collection, while the Layer Name shown right is "EO Series" which is the name of one of the other collections ?
ghobona
@ghobona
@bradh , what are the API types used to access pygeoapi, geoserver and spacebel services from OpenSphere?
_
Brad Hards
@bradh
WFS 3
OK, OGC API for Features.
ghobona
@ghobona
OK, thanks.
Brad Hards
@bradh
@ycespb Looks like a bug on my side.
@ghobona You still owe me answer on the tile server.
ghobona
@ghobona
@bradh , I'm waiting for the answer from one of the participants here. Please stand by.
ycespb
@ycespb
@bradh Yes. We just added one more "collection" with (landsat) products (and some nice metadata hopefully) and now this title is used (uses last collection title for the first collection id)
Brad Hards
@bradh
And last description.
Which is definitely wrong. Debugging.
ycespb
@ycespb
Now I see the landsat image footprints and their metadata (FeatureInfo) appear on the globe. Nice..... Should there eventually 4 separate layers appearing under "Feature Layers" ?
Brad Hards
@bradh
Yep. Looks like I'm ending up with the same layer ID, although its obviously distinct.
OK. I'm using the name attribute which isn't included.
Wonder if that is required.
ycespb
@ycespb
Didnet see this in the OGC Common API specification ...
ycespb
@ycespb
Looks like "id" in the current OGC API common (see the buildings example) is called "name" in the OGC API for Features...
both specs use the same "buildings" example with id/name changed.
Brad Hards
@bradh
Concur, although I think its been changed in the WFS_FES spec too.
Less spec lawyering, more coding.
ycespb
@ycespb
You want us to add also "name" in the collection metadata ?