Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 10 07:48
    ghobona transferred #47
  • May 10 07:44
    ghobona closed #2
  • May 10 07:44
    ghobona closed #69
  • May 10 07:43
    ghobona closed #63
  • May 10 07:43
    ghobona closed #61
  • May 10 07:43
    ghobona closed #60
  • May 10 07:41
    ghobona closed #50
  • May 10 07:41
    ghobona closed #31
  • May 10 07:41
    ghobona closed #29
  • May 10 07:39
    ghobona transferred #26
  • Mar 03 11:04

    ghobona on master

    draft engineering report moved … (compare)

  • Mar 02 19:01

    ghobona on master

    geoserver discussion topics Merge pull request #85 from jod… (compare)

  • Mar 02 19:01
    ghobona closed #85
  • Mar 01 21:19
    jodygarnett opened #85
  • Mar 01 15:40

    ghobona on master

    Regenerated HTML and PDF versio… (compare)

  • Mar 01 15:36

    ghobona on master

    Update osgeo-pgrouting.adoc A … Merge pull request #84 from cvv… (compare)

  • Mar 01 15:36
    ghobona closed #84
  • Mar 01 15:36

    ghobona on master

    Update EcereGNOSIS.adoc Merge pull request #83 from jer… (compare)

  • Mar 01 15:36
    ghobona closed #83
  • Mar 01 14:11
    cvvergara opened #84
ghobona
@ghobona
The Issues / Concerns discussion has just ended. We will reconvene in the Gotomeeting room at 03:30pm EST / 08:30pm UTC for the final demonstration.
Vicky Vergara
@cvvergara
@ghobona I am looking for a location on the repository for posting a report on the work done on pgRouting.
Maybe it is somewhere else?
ghobona
@ghobona
@cvvergara The draft engineering report is at https://github.com/opengeospatial/joint-ogc-osgeo-asf-sprint-2021/tree/engineering-report
It's in the 'report' folder of the engineering-report branch. I will move it to the master branch later on today, after the sprint. All participants will then have 7 days to edit their relevant sections.
3 replies
Jerome St-Louis
@jerstlouis
@gardengeek99 if you have a few minutes I just joined Processes
Steve McDaniel
@gardengeek99
There now
@jerstlouis There now
Tom Kralidis
@tomkralidis
hey all: PSA: we released our new OGC API home today: https://twitter.com/tomkralidis/status/1362854920429441027
ghobona
@ghobona
Congrats @tomkralidis ! That's excellent news.
Jerome St-Louis
@jerstlouis
@gardengeek99 sorry I'm here now
ghobona
@ghobona
We will reconvene in the Gotomeeting room at 03:30pm EST for the final demonstration. https://global.gotomeeting.com/join/978960909
Tom Kralidis
@tomkralidis
@lucadelu see geopython/OWSLib#759 . Any chance you can test?
Jody Garnett
@jodygarnett
thanks everyone
ghobona
@ghobona
Excellent work everyone! Thank you for participating. Have a great weekend!
Angelos Tzotsos
@kalxas
thanks everyone!
Panagiotis (Peter) A. Vretanos
@pvretano
Thanks you everyone. Great code sprint. Lots of energy. Lots of innovation!
Peter Rushforth
@prushforth
Special thanks to you @ghobona ! Mischief managed.
Tom Kralidis
@tomkralidis
thanks all! Alot of cool technology, integrations, tinkering and collab. Looking forward to future events! Thanks @ghobona for keeping us calibrated.
Jerome St-Louis
@jerstlouis
So that exact request as geotiff is having that issue with gdalinfo? I'll try gdalinfo on it.
Jerome St-Louis
@jerstlouis
@lucadelu I just tried https://maps.ecere.com/ogcapi/collections/Daraa:Daraa_DTED/coverage?f=geotiff again, and the GeoTIFF looks fine in QGIS (3.16.3-Hannover). Here is the gdalinfo (3.0.4) output I get for it: https://gist.github.com/jerstlouis/26ff39a450cd347cf3f193b0f6f5b0f1
(though I noticed our WorldMercatorQuad coverage tiles are broken)
Jerome St-Louis
@jerstlouis
(And that is now fixed)
Luca Delucchi
@lucadelu
@jerstlouis I get same result that is different from cubewerx https://pads.ccc.de/BcNZXqEEYp
Jerome St-Louis
@jerstlouis
@lucadelu this is our different GeoTIFF output code that geo-references things a bit differently... But it seems to work fine in QGIS. We could potentially improve this to be more interoperable. It seems like the main difference is that we are using 4 GroundControlPoint that associates corners of the images with specific geospatial coordinates rather than an "origin". A related on-going discussion is here: https://github.com/opengeospatial/ogcapi-coverages/issues/95#issuecomment-768540429 .
ghobona
@ghobona
All, the draft engineering report is now in the 'report' folder of the master branch of the Sprint repo. Please feel free to edit the architecture and discussion sections that describe your project/group activities. I will finalise the engineering report on March 1st at 10:00am EST and submit it to the OGC Technical Committee.
Jody Garnett
@jodygarnett
ghobona
@ghobona
@jodygarnett Please have a look at the HTML or PDF documents. The PDF is currently 53 pages long.
Jody Garnett
@jodygarnett
Thanks, I am checking some of the OsGeo projects
Alex Kmoch
@allixender
Hi @ghobona , nicely put together. It's great to see such a substantial amount of activities summarised.
Will be looking forward to share it once you release it.
You suggest we can propose edits via pull request?
ghobona
@ghobona
Hi @allixender , yes, you may suggest edits by creating a fork of the repo and then creating a pull request. Final edits are due at 11:59pm EST on Tuesday 2 March this week. Please create the pull request by then.
Alex Kmoch
@allixender
Yes, thanks
Jody Garnett
@jodygarnett
@ghobona I note my PR is not yet merged opengeospatial/joint-ogc-osgeo-asf-sprint-2021#85
ghobona
@ghobona
@jodygarnett The PR has just been merged.
Jody Garnett
@jodygarnett
Thanks, hope I got the images and links right.
ghobona
@ghobona
Not to worry. I will fix the image referencing tomorrow morning when I review the document.
ghobona
@ghobona
The draft engineering report has now been submitted to the OGC Technical Committee (TC) for approval. The TC will vote on the engineering report on March 26th.
Alex Kmoch
@allixender
Great work. Thanks for the efforts.
ghobona
@ghobona
All, I am pleased to announce that the Summary Engineering Report has been published. We have also published an associated Blog Post.
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:
ghobona
@ghobona
The joint-ogc-osgeo-asf-sprint-2021 GitHub repository has now been archived. Thanks again for your participation in the code sprint.
Vicky Vergara
@cvvergara
@ghobona thanks to you
Jody Garnett
@jodygarnett
I guess the next spring is ogc specific, and will have a new channel.
ghobona
@ghobona
Thanks @cvvergara
@jodygarnett Yes, the next sprint is OGC API specific. However, all are welcome to register and participate. The May 2021 OGC API Code Sprint will take place May 26th to 28th, 2021. The Gitter room for the code sprint is https://gitter.im/ogc-developer/Sprints
Angelos Tzotsos
@kalxas
thanks for the link @ghobona
ghobona
@ghobona
Hi everyone, in the Community Track of ApacheCon tomorrow (Wednesday 22 September), I will present A Summary of the 2021 Joint OGC OSGeo ASF Code Sprint. The presentation is at 18:50 UTC. Register on the ApacheCon 2021 website.