-
Notifications
You must be signed in to change notification settings - Fork 32
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
cql-text #22
Comments
Yes, the CQL Text branch is not yet production ready and needs additional care to be operational. Also, many changes in the OGC API Features spec will also affect CQL Text, so waiting until it has stabilized might be the bes course in order to avoid too many changes. |
we would also like to support cql-text in our project. so I also tried to use the pygeofilter branch, and alo ran into various issues. such as: certain lark syntax not accepted by lark (don't know with which lark version it was made?), no support for qualified identifiers (such as: 'eo:cover') and finally some lark errors I could not get around.. what we've done for now is extend the pygeofilter ecql parser to support qualified identifiers and only advertise support for 'basic CQL', which seems the same between ecql and cql-text.. not really sure what the further differences are between ecql and cql-text? note that the stac filter fragment documentation currently states: "This extension references behavior defined in the OGC API - Features - Part 3: Filtering and the Common Query Language (CQL2) specification. As of August 2021, this specification is in draft status. Several behaviors have changed since the last published draft, so this spec references the latest revision in the spec's GitHub repo. There are no major anticipated changes, so implementers are encouraged to move ahead with implementation, and to simply be aware that minor changes may need to be made in the future." I'd be more than happy to test after any changes you might make. |
i runned in to the same issue as described by @srepmub If i use constraint with dublin core notation
This is caused by the attribute definition inside the grammer. There is no definition for If i change the attribute definition to attribute: NAME
| DOUBLE_QUOTED
| NAME ":" NAME it produces the following exception:
|
i opend a pullrequest which fixes the issue for ecql |
I see that there is a branch with a base implementation for cql-text.
When I try to use it, I get import errors.
What is the road map for this branch? Do you have a timeline? Is it actively being developed?
The text was updated successfully, but these errors were encountered: