I am having some trouble keeping track of the different specs so please bear with me!
It looks like OGC API - Features - Part 9: Text Search specifies that spaces between terms in the q parameter indicate an AND clause and that commas between terms indicate an OR clause, while the examples in the README here suggest that spaces will be interpreted as OR clauses. Is this the difference between the basic and the advanced free-text search implementations?
Also, does anyone know of an implementation that parses a q parameter into a regex?
I am having some trouble keeping track of the different specs so please bear with me!
It looks like OGC API - Features - Part 9: Text Search specifies that spaces between terms in the
q
parameter indicate anAND
clause and that commas between terms indicate anOR
clause, while the examples in the README here suggest that spaces will be interpreted asOR
clauses. Is this the difference between the basic and the advanced free-text search implementations?Also, does anyone know of an implementation that parses a
q
parameter into a regex?