Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 24 2020 15:18
    ghobona closed #1
  • Nov 24 2020 15:17
    ghobona transferred #15
  • Nov 24 2020 15:16
    ghobona transferred #14
  • Nov 24 2020 15:16
    ghobona transferred #12
  • Nov 24 2020 15:15
    ghobona transferred #11
  • Nov 24 2020 15:14
    ghobona transferred #10
  • Nov 24 2020 15:13
    ghobona transferred #9
  • Nov 24 2020 15:12
    ghobona labeled #9
  • Nov 03 2020 19:53
    jratike80 commented #2
  • Nov 03 2020 19:53
    pomakis commented #2
  • Nov 03 2020 19:51
    jratike80 commented #2
  • Oct 07 2020 13:59
    Schpidi transferred #6
  • Oct 07 2020 13:55
    Schpidi transferred #5
  • Oct 07 2020 13:54
    Schpidi commented #5
  • Oct 07 2020 13:47
    Schpidi transferred #3
  • Oct 07 2020 13:47
    Schpidi commented #3
  • Oct 07 2020 13:39
    Schpidi closed #2
  • Oct 07 2020 13:39
    Schpidi commented #2
  • Oct 07 2020 13:36
    Schpidi transferred #18
  • Aug 27 2020 08:45
    jratike80 commented #18
Panagiotis (Peter) A. Vretanos
@pvretano
Oops, cut-n-pasted the wrong output formats! tiff and wkb.
Tom Kralidis
@tomkralidis
@ghobona where are the OpenAPI schema in development again? Embarking on doing OpenAPI document support here
23 replies
Panagiotis (Peter) A. Vretanos
@pvretano
@jerstlouis nope. These are data tiles from a coverage, not features.
Jerome St-Louis
@jerstlouis
@pvretano can WKB encode coverage data?
Jerome St-Louis
@jerstlouis
I guess it's a multipoint feature with elevation...
Jeff Yutzler
@jyutzler
More threading more often, please. It is really difficult to track these conversations if you aren't actively participating in real-time.
1 reply
Panagiotis (Peter) A. Vretanos
@pvretano
@jerstlouis we have extended OGC's WKB to be able to encode coverage data ... in a backward compatible way I think.
1 reply
ghobona
@ghobona
We reconvene in 25 minutes for the final demos, discussion and wrap up.
Stephan Meißl
@Schpidi
@cmheazel I'm trying to figure out what is the right syntax for requirements and conformance classes. in common I see usage of: "http://www.opengis.net/spec/ogcapi-common/1.0/req/core", "http://www.opengis.net/spec/ogcapi-common-1/1.0/req/core", "http://www.opengis.net/spec/OAPI-Common-1/1.0/req/core", "http://www.opengis.net/spec/ogcapi-common/1.0/conf/core", ... and in coverages also as "http://www.opengis.net/spec/ogcapi_common-1/1.0/req/collections". What is the correct syntax (all lower case?, dash instead of underscore?, appended with -1?)? thanks
8 replies
ghobona
@ghobona
I think the spec needs to be clearer about what the difference between the expected responses of /collections/{coverageId}/coverage/metadata and /collections/{coverageId} is.
At the moment they both can return CIS-encoded metadata, although /collections/{coverageId}/coverage/metadata can also return domain specific metadata.
5 replies
ghobona
@ghobona
The Gotomeeting room is open.
Scott Simmons
@ogcscotts
Another superb Sprint - thanks for the dedication, all!
ghobona
@ghobona
Everyone, thanks for participating in the sprint. It's been a very productive event.
Tom Kralidis
@tomkralidis
@ghobona minor updates in PR: opengeospatial/OGC-API-Sprint-August-2020#16
ghobona
@ghobona
@tomkralidis Thanks!
Jerome St-Louis
@jerstlouis
We now have coverages and coverage tiles available as GeoTIFF on our server (e.g. https://maps.ecere.com/ogcapi/collections/Daraa:Daraa_DTED/coverage , https://maps.ecere.com/ogcapi/collections/Daraa:Daraa_DTED/tiles/CDBGlobalGrid/0/57/215 ). Did not yet implement DomainSet / RangeType links, and subset parameters, but planning to add these in the following weeks . Note that the /coverage end-points scales by default right now (it understands BBOX, WIDTH & HEIGHT).
ghobona
@ghobona
@jerstlouis Thanks for the update!
Stephan Meißl
@Schpidi
fyi I'm woring on having a complete and adjusted openapi yaml definition at https://github.com/Schpidi/ogcapi-coverages-1/. I found the swagger editor to work nicely with this split setup https://editor.swagger.io/?url=https://raw.githubusercontent.com/Schpidi/ogcapi-coverages-1/master/yaml-unresolved/ogcapi-coverages-1.yaml it is not yet finished but the paths up to /coverage should be aligned with the draft, rest to follow
Jerome St-Louis
@jerstlouis
CoverageClient.jpg
@pomakis wondering if a request using bbox extending beyond the dataset, alongside a scaleSize setting, is currently expected to be working from your service?
32 replies
Jerome St-Louis
@jerstlouis
@ghobona @pomakis I have added screenshots of our client accessing and rendering the CubeWerx elevation coverage (as well as our GNOSIS Map Server) at https://github.com/opengeospatial/OGC-API-Sprint-August-2020/tree/master/Screenshots
Jerome St-Louis
@jerstlouis
@pomakis @joanma747 One thing I noticed is that if a coverage is PointIsCorner, we might want coverage tiles to have the extra corner cell (e.g. 257x257 intead of 256x256). There is otherwise a gap when displaying in QGIS. We implemented this for e.g. https://maps.ecere.com/ogcapi/collections/SRTM_ViewFinderPanorama/tiles/GNOSISGlobalGrid/0/0/0 and https://maps.ecere.com/ogcapi/collections/SRTM_ViewFinderPanorama/tiles/GNOSISGlobalGrid/0/0/1 (GeoTIFF by default). In our GNOSIS Map Tiles format we also do this, plus include an extra cell around so that normals can be computed for hillshading without depending on adjacent tiles, so it's 259 x 259 (http://docs.opengeospatial.org/per/18-025.html#_binary_layout_for_gridded_coverage_tiles).
44 replies
ghobona
@ghobona
@jerstlouis Thanks for the screenshots!
@Schpidi Thanks for advancing the yaml files. Great work!
ghobona
@ghobona
All, registration for the next OGC Code Sprint has been opened. The OGC invites software developers to the May 2021 OGC API Virtual Code Sprint, to be held from May 26th to May 28th, 2021. The Code Sprint will focus on the following draft OGC API specifications: