You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Note that the Overpass query passed to `get()` should not contain any `out` or other meta statements.** See `verbosity` below for how to control the output.
60
60
@@ -96,7 +96,12 @@ response = api.get('node["name"="Salt Lake City"]', responseformat="xml")
96
96
97
97
We will construct a valid Overpass QL query from the parameters you set by default. This means you don't have to include 'meta' statements like `[out:json]`, `[timeout:60]`, `[out body]`, etcetera. You just supply the meat of the query, the part that actually tells Overpass what to query for. If for whatever reason you want to override this and supply a full, valid Overpass QL query, you can set `build` to `False` to make the API not do any pre-processing.
98
98
99
-
### Pre-cooked Queries: `MapQuery`, `WayQuery`
99
+
#### `date`
100
+
101
+
You can query the data as it was on a given date. You can give either a standard ISO date alone (YYYY-MM-DD) or a full overpass date and time (YYYY-MM-DDTHH:MM:SSZ, i.e. 2020-04-28T00:00:00Z).
102
+
You can also directly pass a `date` or `datetime` object from the `datetime` library.
103
+
104
+
### Pre-cooked Queries: `MapQuery`, `WayQuery`
100
105
101
106
In addition to just sending your query and parse the result, `overpass`
102
107
provides shortcuts for often used map queries. To use them, just pass
0 commit comments