Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    ycespb
    @ycespb
    Thanks. we'll check and correct.
    ycespb
    @ycespb
    @lossyrob Hi Rob, the situation on our server has already improved (no intermediate certificate is missing any more), but there is still and issue we need to solve (an expired certificate remains in the chain). Could you check if the changes we made are already sufficient to unblock your problem ?
    ycespb
    @ycespb
    @lossyrob Hi Rob, I'm told that the certificates should now be OK on our server. Could you check if you still have an issue when accessing from outside ?
    Rob Emanuele
    @lossyrob
    I’m not seeing certificate errors anymore, so that seems to have worked. thanks!
    The javascript relative path logic is getting tripped up by the colin in the eo:platform URL of the subcatalogs currently, so that’s the next issue to contend with :-)
    ycespb
    @ycespb
    Perfect. thanks for the feedback. Let us know if you see any mistakes/problems in the current implementation... We are still working on it.
    Rob Emanuele
    @lossyrob
    will do
    ycespb
    @ycespb
    @lossyrob Do you know why certain pages have to be explicitly refreshed in the browser before they show a content ? I have this with the page https://stacindex.org/catalogs/fedeo-clearinghouse#/5nc6NjkK1CgBqG8HCgekPHXMn/4XwrsbGiKREPj6mQGr8Q2cajTYEGbSr9ax56?t=catalogs which should show 2 or 3 entries (PROBA-1 collections). I get 0 entries and after refreshing/reloading the page, they appear...
    Rob Emanuele
    @lossyrob
    Not sure - clicking that link showed me 2 items immediately. I can see if I can reproduce while exploring that catalog
    Rob Emanuele
    @lossyrob
    @ycespb that issue will be fixed as part of radiantearth/stac-browser#47. Also, I was working on the “next” and “prev” for catalogs, but it seems like those links were removed in the https://ergo.spacebel.be/ catalog? Did you all decide not to go with the catalog pagination? If so I’m happy to not code in that feature; I’m not a designer and it was tough guessing where those buttons should go :)
    ycespb
    @ycespb
    @lossyrob . Great that this problem will be solved. Regarding paging in collections/catalogs, they are still there once there are "item" links in a collection such as https://ergo.spacebel.be/series/eo:platform/PROBA-1/PROBA.CHRIS.1A. This will happen for all collections which have actual items as there are severla hundreds/thousands. When there are only "child" links (the top-level of the tree-structure), we managed to increase the page size by optimizing our implementation so we cna afford larger page sizes for obtaining the "child" links. Regarding the place for the buttons, we would have thought that thay would be before/after the numbered tabs, thus for instance <1> <2><3><next> which would go to for instance <prev><4><5><6>.<next>. instead of <1><2>..<8>. I got an email from github this morning about a change to the collection level assets which would be implemented. Is this a change which already exists and could we test it somewhere or is it already available for download?
    Rob Emanuele
    @lossyrob
    @ycespb You can checkout the branch that’s associated with the pull request linked above and test it - any testing would be appreciated! For the pagination, thanks for the clarification. As far as I can tell, the collection with child pagination doesn’t have enough information to make the page numbers update or set the page size for the control based on how many pages/children the collection has - there are ‘first, ‘next’ and ‘last’ links as far as I could tell, but no count, current page, or page size information that can be used to calculate the info required for the setup you mentioned. If that were available, we might be able to modify the settings of the current boostrap-vue pagination control to accomplish what you mentioned; otherwise it might take some customization of that control which would be a lot more involved. I was looking at a simple solution that placed the catalog pagination with buttons to route to the first, next and last links if they existed above the metadata in case those links were present. That wouldn’t be the ideal pagination control but may satisfy this specific use case based on the currently available information in the collection
    ycespb
    @ycespb
    @lossyrob Just having previous/next/first/last buttons if the links exist would be perfect. No need to show any page numbers... We are currently still busy on the server-side implementation. We'll give feedback on your client as soon as it is either accessible via Stacindex or when we install t ourselves. I'm curious about the display of the summaries and collection-level assets to see how we can even better exploit it. For instance displaying the "count" of child catalogs and/or items in the catalog would be very interesting (I have in mind something like summaries { "id": { "count": 2000 } }. Thanks for all the work. We will definitely give you feedback asap...
    Matthias Mohr
    @m-mohr
    I'm just testing the PR with STAC Index
    Anything specific I should look at, @ycespb ?
    ycespb
    @ycespb
    @m-mohr : if you navigate in FedEO via "platforms" and search for "Proba-1", it should show 3 entries. In the current implementation, there was a bug leaving the page empty until you explicitly refreshed. Also, when you arrive to these two collections for Proba-1, each of them should have colection-level assets which are links to metadata representations. This is new functionality high on our wish-list :-)
    @m-mohr , we do also display n the collection the summaries for platform and instruments. Hopefully these show up and we did encode them correctly also..
    Matthias Mohr
    @m-mohr
    @ycespb It shows me two entries (PROBA.CHRIS.1A (7144), PROBA.HRC.1A (18023)) - No refresh required
    ycespb
    @ycespb
    @m-mohr perfect (should be two indeed - the 3 is my mistake). In the current stacindex, you had to refresh the page to see them..
    Matthias Mohr
    @m-mohr
    And it shows a single Platform (PROBA-1) in summaries @ycespb
    ycespb
    @ycespb
    @m-mohr if you select one of these 2 proba collections, it should show in its summary also the "instruments"... We can check if at the level of "Proba-1", we could include the two instruments of the underlying collections...
    Chris Holmes
    @cholmes
    I was just thinking about the 'count' thing - I do like how your catalog shows that @ycespb But does feel like it should be something we have a proper field for. @m-mohr - is there a way it would fit in summaries? I feel like it's a bit different than the others.
    Matthias Mohr
    @m-mohr
    @ycespb Your Collections are missing extents, which is giving errors in STAC Browser. The summaries for the PROBA CHRIS Level 1A indeed shows the CHRIS instrument.
    ycespb
    @ycespb
    @cholmes the W3C VOID specification has "structural metadata" in https://www.w3.org/TR/void/#statistics Something allowing to show count the "item" and/or "child" links would be interesting..
    Matthias Mohr
    @m-mohr
    @cholmes Hmm... not directly. You could add a count to the Stats Object for a field... "id": { min: 0, max: 1000, count: 588 } or so, just an idea
    ycespb
    @ycespb
    @m-mohr , we will check the extents... I'm surprised that they are missing. Maybe the syntax is not correct? ...
    Matthias Mohr
    @m-mohr
    They are there for Proba CHRIS, but I looked at the eo:platform thingy
    Chris Holmes
    @cholmes
    @ycespb - interesting.
    @m-mohr - That could work, though seems a bit obscure. We could also just add an optional field in the catalog that's 'count'.
    Do we have a ticket to move summaries to catalog? We talked about it at the sprint and it seems like a good idea.
    Matthias Mohr
    @m-mohr
    @cholmes Yes, it's not the most intuitive way to do it, but would need no spec change. Why not re-use the context extension from the API?
    Chris Holmes
    @cholmes
    ah, that's a good idea. I could get behind that.
    Matthias Mohr
    @m-mohr
    @cholmes We had summaries in Catalog, but you pushed me to clean it up and remove it.
    Chris Holmes
    @cholmes
    Yeah, I know. I regret it.
    Matthias Mohr
    @m-mohr
    But no, no ticket.
    Chris Holmes
    @cholmes
    I'm going to make a 'count' issue, we can discuss approaches there.
    Cool, I"ll make one for that too.
    ycespb
    @ycespb
    @m-mohr For the "eo:platform" object we have no precise/meaningful "extent" information, but can include a dummy one (whole earth, any date)... Can't it be considered a "catalog object" still at this level which has no mandatory extent ?
    Matthias Mohr
    @m-mohr
    @ycespb As you have specified other Collection fields many tooling will detect it as collection and complain about the missing extent. Worldwide seems like the correct approach to me if the union of the collection data linked to covers the whole world. I know we discussed this in another issue recently, but I don't think a worldwide extent is really wrong here...
    ycespb
    @ycespb
    @m-mohr thanks, we'll add it tomorrow morning...
    ycespb
    @ycespb
    @m-mohr staclint.com seems to be happy with the "eo:platform" object....
    Matthias Mohr
    @m-mohr
    Then it likely validates it as Catalog. Not sure which rules are used exactly, but they may change (see the issue we discussed yesterday).
    ycespb
    @ycespb
    @m-mohr No problem. This is probably why we did not notice something was missing ...
    Matthias Mohr
    @m-mohr
    @ycespb The Node Validator complains about the missing extent ;-)
    ycespb
    @ycespb
    @m-mohr We added the extents.. Should be OK now.
    Matthias Mohr
    @m-mohr
    @ycespb Yes, they are now recocgnized as valid collections!
    ycespb
    @ycespb
    @lossyrob Hi Rob, we have this morning deployed the STAC-Browser with support for collection-level assets now at https://geo.spacebel.be/?t=catalogs. This is very interesting functionality for us, and we will see what additional assets we can make available through this mechanism. Thanks!. The only issue I noted so far is related to the "map" which seems to be absent on some of the collection pages and then come back... Also the "bug" which required a refresh/reload of the page to see all collections has now disappeared, which is good news as well.
    Matthias Mohr
    @m-mohr
    @ycespb I have the same issue with the map: radiantearth/stac-browser#49
    ycespb
    @ycespb
    @m-mohr Thanks, so this is a known issue already...
    Rob Emanuele
    @lossyrob
    Thanks for the notes! I’ll put the map bug on the priority backlog...