Time interval queries
To query data for a specific time interval, use atuple in the form (start, end) as the temporal_extent parameter. Both start and end must be TimeScalars, which can be datetime objects or strings in ISO 8601 format.
Output
The
show_progress parameter is optional and can be used to display a tqdm progress bar while loading data.Endpoint inclusivity
A time interval specified as a tuple is interpreted as a half-closed interval. This means the start time is inclusive, and the end time is exclusive. For instance, using an end time of2025-06-01 includes data points up to 2025-05-31 23:59:59.999, but excludes those from 2025-06-01 00:00:00.000.
This behavior mimics the Python range function and is useful for chaining time intervals.
Manual endpoint inclusivity
For greater control over inclusivity of start and end times, you can explicitly specify aTimeInterval. This way you can specify both the start and end times, as well as their inclusivity. Here’s an example of creating equivalent TimeInterval objects in two different ways.
Output
Time scalar queries
You can query all datapoints linked to a specific timestamp by specifying aTimeScalar as the time query argument. A TimeScalar can be a datetime object or a string in ISO 8601 format.
Here’s how to query a data point at a specific millisecond from a dataset or collection.
Output
Timezone handling
AllTimeScalars specified as a string are treated as UTC if they do not include a timezone suffix. If you want to query data for a specific time or time range
in another timezone, it’s recommended to a type that includes timezone information. Tilebox will automatically convert such objects to UTC in order to send the right query requests.
All outputs will always contain UTC timestamps, which will need to be converted again to a different timezone if required.