@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
seems a bit of a gray area... @rouault are you doing the bbox like that to do a sort of "featureinfo"?
@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
@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
@rouault so are we good?
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
@rouault in general I mean, do you have what you need to run a demo?
yes. let me know when the server has deployed your /api changes to check if i can work without my current workaround
@/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.