Further development of the GIS platform of the Swiss Federal Office of Energy (SFOE): Add price information to the charging stations and find the cheapest option around for electric car drivers.
What we needed was of course the list of the prices for every provider coherently compiled and available for comparison. At the very beginning we toyed a little with the idea of scraping the provider's websites to harvest the price information. This approach was quickly proved as unfeasible since for many providers the price structure is not even clearly published and, even when it is, each provider present it in its own way or only through their proprietary mobile app. Public APIs are not available and we had to scrap that approach too.
At the end, we resorted to manually look for and extract the pricing information from the various websites. For time reasons we limited ourselves to three of the biggest providers.
KWh, per minute, per hour, monthly abo, yearly abo, one-time fee per plug-in, flatrates, roaming... and many permutations of all that. The pricing landscape is obscure and confusing. We thus spent quite a lot of time looking for a way to model this variety and compile it in a single table.
We settled for the concept of "tariff plan" as our object. Discriminating parameters are the tariff provider, the roaming partner, time of the day, power type and KW at the plug. With such a structure we are able to filter for the chosen plug paramenters and present the user the tariff plans available for that particular plug. As far as pricing information goes, we could not really consolidate it to a single measurement unit (ex: chf per KWh) because of the diversity in the pricing structures. Therefore, for each tariff plan we show the price in the same measurement units given by the provider. Because of this, it was also not possible to give the final charge price to the user to fill the battery. In addition, this would require a lot of information about the vehicle that are here out of scope.
As already stated, we faced several problems during our data collection and consolidation process.
- The pricing data is not publicly available, or very hard to find.
- Some pricing information is available only to registered customers.
- There is no common denominator across the tariff plans across different providers. And even within the same provider we found often huge differences in price calculations. Comparing the various tariff plans is therefore almost impossible.
- We did not manage to harvest the price structures programmatically and had to resort to manual work.
- The price also depends on the car type (max. kW input, battery volume etc.)
To allow a user to compare the available tariff plans for a given charging station we combined the following elements:
- A leaflet webmap. The map uses the publicly available geoJSON from the Federal Spatial Data Infrastructure (FSDI) to visualize the charging stations.
- The freely accessible FSDI API at api.geo.admin.ch to retrieve the full station and plug informations
- Our static table (filled as a google sheet then transformed to JSON for the webapp) with the tariff plans information.
When the user picks a charging station, the application retrieves the ID from the geoJSON and then uses it to make an API call to api.geo.admin.ch. This retrieves all the needed information about the available plugs at the station. The user than chooses a certain plug. The app then filters the tariff table for this plug to present the valid plans and the pricing information.
Filter parameters are:
| API result attribute | Tariff table attribute | |
|---|---|---|
| Provider This looks for al the tariff plans valid for the selected station's operator |
OperatorName | tariff_provier |
| KW Some tariff plans depend on the available power at the plug. |
QueryChargingFacilities | valid_kw |
| Time of the day Some tariff plans depend on the time of the day. |
- | start end |
| Power time Some tariff plans depend on power type (AC or DC). |
QueryChargingFacilities | powertype |
You can find the table here
| Variable name | Description |
|---|---|
| tariff_provier | String Name of the provider offering this tariff |
| roaming_partner | String Name of the roaming partner for this tariff. Is the same as tariff_provider if not a roaming tariff |
| tariff_name | String Name of the tariff |
| valid_kw | String Comma-separated list of the plug powers using this tariff |
| start | hh:mm:ss Validity start for this tariff plan |
| end | hh:mm:ss Validity end for this tariff plan |
| powertype | String "AC", "DC" or "AC, DC" where the info is not available |
| flatrate | Boolaen Informs if the tariff is a flatrate one (pay once, charge unlimited without additional costs) |
| chf_plug-in | Float Base fee just to plug-in the car, in Swiss Francs for this tariff |
| chf_minute | Float Fee in Swiss Francs per minute plugged in |
| chf_kwh | Float Fee in Swiss Francs per KWh delivered by the plug |
| chf_month | Integer Cost in Swiss Francs of the monthly subscription |
| chf_year | Integer Cost in Swiss Francs of the yearly subscription |
Our solution is very rudimentary and must be considered as an early-stage POC.
- We have a static and still rudimentary tariff "database"
- Incomplete tariff data
- Data model has to be optimized
- Filter function optimization
- Not integrated with ich-tanke-strom.ch
- Impossible to calculate the total cost of a charge
- Still almost impossible for a user to make meaningful comparisons because of the different price calculations
- Car parking costs are not considered
- Include more operators
- Automatic fetching of updated tariff information
- Integration of the data into ich-tanke-strom.ch
- Integration user data such as car type, battery status, ...
- Integration of parking costs
- Develop a real webapp 😄
- Develop a price comparing site à la comparis, Djungelkompass
- The data needs to be open, easily and freely accessible in order to develop such an applications
- There is a need for a standard way to describe the costs to make a meaningful comparison possible
- It is a pleasure to work with the freely available DIEMO data (both the static JSON than via the FSDI API)
- Open Data is nice and saves a lot of nerves!