Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Janne Heikkilä
    @jampukka
    is there an enum for the possible "type" values in a queryable
    Andrea Aime
    @aaime
    @jampukka I made one up based on the testbed 15 one, but think it's something up to discussion
    ycespb
    @ycespb
    @jjrom , The profile value should be an absolute URI (not a URL). I would expect something like https://radiantearth/stac/collection ? or https://...#collection.
    Andrea Aime
    @aaime
    @rouault checking the bbox thing
    Jerome Gasperi
    @jjrom
    @ycespb Ok that's sound much better - i prepare a PR
    Janne Heikkilä
    @jampukka
    @aaime in your OpenAPI document for queryable "name" is required but the actual property is "id"
    Alessandro Pasotti
    @elpaso
    About TRANSACTIONS and PATCH, I don't see an option to change the geometry, is that supposed to be done with PUT only?
    ycespb
    @ycespb
    @jjrom Maybe the "targetSchema" property defined here https://json-schema.org/latest/json-schema-hypermedia.html#rfc.section.6.5.4 is an alternative to the "profile" approach...
    Andrea Aime
    @aaime
    @rouault checked, other versions of the WFS protocol would behave the same I think... the issue is that we first test if the two envelopes intersect, and they do, and then do a full intersection test with JTS, polygon vs polygon, apparently the empty polygon coming out of the empty envelope is not topologically intersecting, according to JTS
    I guess I can try to expand the bbox a tiny bit, minimum delta that would make one of the ordinates different than the other in the floating point encoding
    Andrea Aime
    @aaime
    seems a bit of a gray area... @rouault are you doing the bbox like that to do a sort of "featureinfo"?
    Jerome Gasperi
    @jjrom
    @ycespb Hum...not sure from the example it looks quite cryptic. I would really have a simple stuff like what we have for COG i.e. "profile:cloud-optimized" in the mimeType. Would "profile:stac-collection" not valid ? It will not be an official mime-type but at least it's meaningful within the stac spec
    ycespb
    @ycespb
    @jjrom Not sure. Here are examples of profiles and their URI: https://tools.ietf.org/html/rfc7284.
    Even Rouault
    @rouault
    @aaime Yes, I generally like to try the "what is at my place" kind of test query. This is far from being critical. I remember having that kind of issue with ElasticSearch or MongoDB and changed the client to do a small rectangle
    Andrea Aime
    @aaime
    @rouault so are we good?
    Even Rouault
    @rouault
    on that bbox=point point of view ? I'd still like some clarification from the spec to know if servers are allowed to interpret this as an empty bbox or not
    I should probably create an issue regarding this
    Andrea Aime
    @aaime
    @rouault in general I mean, do you have what you need to run a demo?
    Even Rouault
    @rouault
    yes. let me know when the server has deployed your /api changes to check if i can work without my current workaround
    Andrea Aime
    @aaime
    right
    ] gets left behind in the clickable link
    Angelos Tzotsos
    @kalxas
    @cholmes I think the cisco remote link is down
    Nick Weir
    @nrweir
    @kalxas It's currently shut off as everyone's just doing group work/working on things, and no one else was on it. I can start it up again if desired
    Angelos Tzotsos
    @kalxas
    just wanted to report in case it was needed
    :+1:
    Even Rouault
    @rouault
    @kalxas It is a known issue. Chris sent an email with a link to zoom instead
    Angelos Tzotsos
    @kalxas
    oops, sorry I missed that
    Chris Holmes
    @cholmes
    @/all - everyone here is updating the progress page I just linked. Remotes, if you did anything productive at all (and I think many of you did), please put something in the progress page so we can keep track of all that happened.
    And I'm also going to use it to go through calling people to share what they worked on.
    https://planet.zoom.us/j/8171436529 is the zoom link. I'll start it up now, but we wont' start the session for another hour.
    (and we'll likely be testing audio on it soon)

    Dial by your location
    +1 929 436 2866 US (New York)
    +1 669 900 6833 US (San Jose)
    +49 69 7104 9922 Germany
    +49 30 3080 6188 Germany
    +49 30 5679 5800 Germany
    +1 647 558 0588 Canada
    +44 203 966 3809 United Kingdom
    +44 131 460 1196 United Kingdom
    +44 203 051 2874 United Kingdom
    +44 203 481 5237 United Kingdom
    Meeting ID: 817 143 6529
    Find your local number: https://planet.zoom.us/u/amztGaUVJ

    Join by SIP
    8171436529@10.142.1.27
    8171436529@10.142.1.28

    Francesco Bartoli
    @francbartoli
    @cholmes I can hear you but the connection is unstable sometime
    Alessandro Pasotti
    @elpaso
    Goodby everyone and thank you for the presentations and all the valuable information, my time is over, it has been a pleasure to participate, I hope next time I will be able to attend in person!
    Chris Holmes
    @cholmes
    Thanks @elpaso !
    Ok, starting up now. Join the zoom.
    Tim Schaub
    @tschaub
    @jampukka Awesome :point_up: November 7, 2019 9:15 AM - I've added a link to this in the readme for opengeospatial/ogcapi-features#283
    If anybody else is feeling like braving an implementation, I'd be happy to take feedback (nudge @rouault and @aaime)
    didn't I say that I didn't want to implement more than one filter language.. ? I have 2 now...
    Tim Schaub
    @tschaub
    maybe we need FLAG - Filter Language Abstraction Library!
    Thanks @rouault. I appreciate you giving it a try.
    Even Rouault
    @rouault
    once you have the expression tree, all filter languages are pretty much the same complexity on the generation side. The amount of URL escaping needed doesn't make it pretty though
    Tim Schaub
    @tschaub
    yes, URI component encoded JSON looks ugly
    I like hand-writing beautiful URLs as much as the next dev, but I also see the value in machine friendly syntax - and this JSON filter expression encoding is meant for both GET and POST, optimizing for ease of parsing/generation (rather than hand writing)
    Probably also fair to say that properly encoded CQL isn't going to look very pretty once the query gets non-trivial
    Even a simple WKT geometry is ugly: POLYGON%20((35%2010%2C%2045%2045%2C%2015%2040%2C%2010%2020%2C%2035%2010)%2C(20%2030%2C%2035%2035%2C%2030%2020%2C%2020%2030))