...
For example, { "qt": [ "ftext": "barack obama" ] } will match on any documents containing either "barack" or "obama", with documents containing both scored more highly (TBD link to scoring params). { "qt": [ "ftext": "+barack +obama" ] } requires both be present (but not necessarily in the same phrase), and { "qt": [ "ftext": "'barack obama'" ] } is equivalent to the "etext" query described above.
Other examples:
- qt[0].ftext="+obama -palin": documents containing the word "Obama" but not containing the word "Palin"
- qt[0].ftext="title:\"palin\"": documents with the word "Palin" in the title.
Note when using dot notation and typing queries directly into the URL bar that characters like '+' must be double-URL-encoded, eg to %25%32%4B (ie via %2B from +).
...
The "dist" string is a distance in the format "<distance><unit>" where <distance> is an integer or floating point number, and unit is one of "m" (miles), "km" (kilometers), "nm" (nautical miles).
Examples:
- qt[0].geo.centerll="40.12,-71.34"&qt[0].geo.dist="100km": within 100km of the specified lat/long.
- { "qt": [ { "geo": { "centerll": "40.12,-71.34", "dist": "100" } } ] }: uses the default unit (km), ie is the same query as above.
- qt[0].geo.minll="(4.1,-171.34)"&qt[0].geo.maxll="40.12,-71.34": bounding box showing lat/long format with and without parantheses.
Temporal
The temporal query term has the following format:
| Code Block | ||||
|---|---|---|---|---|
| ||||
{
"time": {
"min": string,
"max": string
}
} |
One of "min" and "max" must be specified. If one of them is not specified, time is not bounded in that direction (eg if "min" is not specified then it means "all times before max"; if "max" is not specified then it means "all times after min").
The date fields are both strings and support a number of different formats:
- "now" which always resolves to the current time,
- any Unix time (ie milliseconds after "Jan 1 00:00:00 1970"),
- and the following date/date-time formats: "yyyy''DDD", "yyyy''MM'-'dd", "yyyyMMdd", "dd MMM yyyy", "dd MMM yy", "MM/dd/yy", "MM/dd/yyyy", "MM.dd.yy", "MM.dd.yyyy", "dd MMM yyyy hh:mm:ss", "yyyy-MM-dd" (ISO Date), "yyyy-MM-ddZZ" (ISO Date-Timezone", "yyyy-MM-dd'T'HH:mm:ssZZ" (ISO DateTime-Timezone), "EEE, dd MMM yyyy HH:mm:ss Z" (SMTP DateTime).
Examples:
- { "qt": [ { "time": { "min": "1284666757164", "max": "now" } } ] }: from 16 Sep 2010 until now.
- qt[0].time.min="now": any time in the future.
- qt[0].time.max="20100201": any time before 1 Feb 2010.
- { "qt": [ { "time": { "min": "02/10/2000", "max": "10 Feb 2001 13:00:00" } } ] }: from 10 Feb 2000 until 10 Feb 2001 at 1pm.
Events
The event query format is slightly more complex TBD
Combining query terms
Multiple query terms can be combined in 2 ways:
- Using the "logic" field as described under "Overview of querying". This is the standard way of combining separate queries.
- In addition, within a single query term multiple elements of different types can be merged into a single object - this has the effect of ANDing them together. For example:
- { "qt": [ { "entity": "barack obama/person", "time": { "min": "1284666757164", "max": "now" } } ] }: documents containing the entity Barack Obama, from 16 Sep 2010 until now.
- qt[0].etext="apple"&qt[0].ftext="pair": this is equivalent to qt[0].etext="apple"&qt[1].ftext="pair"&logic="1 and 2"
XXX