Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

ECQL for greater GeoServer compatibility #86

Open
jodygarnett opened this issue Feb 8, 2020 · 2 comments
Open

ECQL for greater GeoServer compatibility #86

jodygarnett opened this issue Feb 8, 2020 · 2 comments
Assignees

Comments

@jodygarnett
Copy link

jodygarnett commented Feb 8, 2020

Discussion topic: For ECQL the key improvements is to go from "<PropertyName> <op> <Expression>" to "<Expression> <Op> <Expression>".

References:

@hwbllmnn
Copy link
Contributor

I agree that this would be very nice to have. Unfortunately I'd guess that it's not easy to implement with the current state of the parser (it was originally just ported from OpenLayers 2). The best way forward would probably be a (partial) rewrite of the parser.

@jodygarnett
Copy link
Author

I wonder if openlayers has any new code we can borrow.

As for ease of implementation, the code to parse an expression must already be present, it may be a manageable change to allow it to parse both the left and right hand side of an operation.

That said additional WFS 2.0 operations and filters have been defined (since any openlayers 2 parser was written), for example "between" to support temporal queries.

@KaiVolland KaiVolland removed their assignment May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants