Replies: 1 comment
-
|
I found out that it depends on the providers source type. It does not work with Geojson, but once I use PostgreSQL, it does work for INTERSECTS. It would be nice if Pygeoapi gives a warning once you use a filter that does not work for the providers source type in stead of just giving all the features. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have setup a localhost server with Pygeoapi (0.21.0) with a geojson file as source.
The API works fine, but it does not seem to react on any of my spatial filters according to Part 3 of the filtering standard.
In all the cases, it returns all the records (567), instead of the 2 or 3 that I expected.
http://localhost:5000/collections/Aandachtsgebied_EV/items?filter-crs=http://www.opengis.net/def/crs/EPSG/0/28992&filter=INTERSECTS(foo_geom,%20LINESTRING(138000%20523000,%20138000%20525000))
http://localhost:5000/collections/Aandachtsgebied_EV/items?filter-crs=http://www.opengis.net/def/crs/EPSG/0/28992&filter=CROSSES(foo_geom,%20LINESTRING(138000%20523000,%20138000%20525000))
http://localhost:5000/collections/Aandachtsgebied_EV/items?filter-crs=http://www.opengis.net/def/crs/EPSG/0/28992&filter=DWITHIN(geometry,POINT(138000%20524000),1000,meters)
I have also tried it with WGS-84 coordinates, without filter crs, but that does not make a difference.
Does anyone have suggestions what could be wrong?
Are there any preconditions, I should take care off?
Thank you for looking into it,
Pieter
Beta Was this translation helpful? Give feedback.
All reactions