Queries
Writing Stream queries that find what you mean.
Writing Stream Queries
A query is a natural-language description of anything visually observable. Queries fall into useful categories:
| Type | Examples |
|---|---|
| Objects | fire hydrants, palm trees |
| Conditions | cracked sidewalks, flooded roads |
| Infrastructure | bike lanes, streetlights |
| Environment | dense tree canopy, rocky coastline |
| Construction | construction cranes, road work |
| Accessibility | curb ramps, tactile paving |
Recommended request structure
Keep the query for the thing, and pass location and time as structured fields instead of stuffing every constraint into natural language.
{
"query": "potholes",
"region": "New York",
"year": 2026
}Specific vs broad
red fire hydrant narrows the visual target — good when you want a precise object and can accept fewer results.
Singular vs plural
pothole and potholes both work — Stream matches observations of the object in either form. Use whichever reads naturally in your UI.
Conditions
State-based queries like damaged road or cracked sidewalk describe the condition of the environment rather than a discrete object. They work best paired with a location and year so you compare the same area through time.
Visual characteristics
Descriptions of visual traits work directly — buildings with balconies, graffiti-covered wall, leaf-strewn gutter. Phrase them the way a person would describe what they see.