Filters
Filters define which stations are included in the Tile Service response. While all filters perform exclusion, EVSE-level filters also transform the station’s data fields to ensure the output is contextually relevant to the specific search criteria.
Filters are categorized into two types based on their impact on the response payload:
Implementation
Filter parameters can be appended to the request URL as query strings to any of the Tile Service endpoints (MVT or JSON or Count). When no filters are applied, the API returns the full set of available charging stations in their raw, non-transformed state.
Filters / URL Example
- 01
https://api.chargetrip.io/v2/station/..../?{filter_1}&{filter_2}&{filter_n}
Parameters
An overview of possible filter parameters can be found below.
Station-level filters
Filters that evaluate the station's global attributes. These filters are exclusion-only: exclude non-matching stations but never modify the returned data fields.
amenities
Filter to include only stations that provide the specified amenities near or at the station.
preferred_operators
Filter to include only stations operated by pre-defined preferred operators. Preferred operators can be set in project settings within the dashboard.
hide_excluded_operators
Filter to exclude stations operated by excluded operators. Excluded operators can be set in project settings within the dashboard.
operator_ids
Filter that configures the operators that will be included in the tiles.
truck_dedicated
Filter to include only stations dedicated or primarily intended for truck charging. Only applicable if the Eco-Movement station database is used; otherwise, it is ignored.
vehicle_types
Filter to include only stations supporting the specified OCPI Vehicle Types. Only applicable if the Eco-Movement station database is used; otherwise, it is ignored.
EVSE-Level Filters
Filters that evaluate the station’s specific charging capabilities. These filters perform exclusion and transformation: non-matching stations are excluded, and matching stations have their dynamic fields recalculated.
minimum_power
Filter to include only stations where at least one connector meets or exceeds the specified power value (in kW).
maximum_power
Filter to include only stations where the maximum charging power of any connector does not exceed the specified power value (in kW).
connectors
Filter to include only stations that have EVSEs with the specified connector types. Accepts an array of strings with any OCPI 2.2.1 connector values.
evse_statuses
Filter to include only stations with EVSEs that have the specified statuses.
Filter combinations & logic
Filters can be combined in two ways.
Data transformations
When EVSE-Level filters are applied the stations properties connector_maximum_power and evse_status_* are re-calculated to reflect only the connectors that match filtering criteria.
This station serves as reference point for how data transformations occur based on different filter parameters.
| Station A |
|---|
| 1x Combo Type 1 (IEC_62196_T1_COMBO), Available, 150 kW |
| 1x Combo Type 1 (IEC_62196_T1_COMBO), Out of Order, 150 kW |
| 1x CHAdeMO, Available, 100 kW |
| Belongs to a prefered operator |
Request without filters
When no filters are applied, all stations are returned and the response reflects the aggregate data of all the stations evses.
Data transformations / Without filters response
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
- 09
- 10
- 11
{ "id": "station_a",// Static: The station's absolute maximum power "station_maximum_power": 150, // Dynamic: Reflects the maximum power available across all connectors since no filters are applied "connector_maximum_power": 150, // Dynamic: Counts all available connectors "evse_status_available": 2, // Dynamic: Counts all out-of-order connectors "evse_status_out_of_order":1 }
Request with Station-Level filters
Filter: ?preferred_operator=true
In this example the station is returned because matches the operator criteria and no re-calculations are done.
Data transformations / Filters response
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
- 09
- 10
- 11
{ "id": "station_a",// Static: The station's absolute maximum power "station_maximum_power": 150, // Dynamic: Reflects the maximum power available across all connectors since no filters are applied "connector_maximum_power": 150, // Dynamic: Counts all available connectors "evse_status_available": 2, // Dynamic: Counts all out-of-order connectors "evse_status_out_of_order":1 }
Request with EVSE-Level filters
Filter: ?preferred_operator=true & connectors[]=CHADEMO
In this example, the station is returned because it matches operator criteria and the EVSE-Level filter (connector_type CHAdeMO is present). The dynamic fields are recalculated to "mask" any hardware that isn't a CHAdeMO connector.
Data transformations / Filters response
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
- 09
- 10
- 11
{ "id": "station_a", // Static: Remains 150 kW (This represents the station maximum power across all conectors) "station_maximum_power": 150, // Dynamic: Adjusted to 100 kW (Max power of the CHADEMO connector) "connector_maximum_power": 100, // Dynamic: Counts the 1 CHADEMO chargers "evse_status_available": 1, // Dynamic: 0, because the charging Type 1 plugs are filtered out "evse_status_out_of_order": 0 }