Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Part 3: Filtering using Spatial dimension #969

Open
Karyme-Nava opened this issue Nov 22, 2024 · 1 comment
Open

Part 3: Filtering using Spatial dimension #969

Karyme-Nava opened this issue Nov 22, 2024 · 1 comment
Labels

Comments

@Karyme-Nava
Copy link

If I need to use Spatial dimension as a spatialOperand using the expressions for filtering (as overlaps, contains, touches, etc) in the CQL filter param, how should I specify the Spatial dimension? If I use "property":"geometry" is confusing since a Feature's Spatial dimension is not included in the properties of a Feature's item response.
see: Example 8. Examples of a NULL predicate
{ "not": { "isNull" : { "property": "geometry" } } }

Example 9. Example spatial predicate
{ "intersects": [ { "property": "geometry" }, { "type": "Polygon", "coordinates": [ [ [36.319836, 32.288087], [36.320041, 32.288032], [36.320210, 32.288402], [36.320008, 32.288458], [36.319836, 32.288087] ] ] } ] }

@cportele
Copy link
Member

There is no build-in function that returns the spatial dimension, so you have to extend CQL2 with a custom function. For example:

{
  "op": "spatialDim",
  "args": [ { "property": "geometry" } ]
}

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Development

No branches or pull requests

2 participants