Danilo Bargen

> You could cache Overpass API results. Hm, that's actually not a bad idea, since it would avoid needing to download the full OSM planet file. However, this would require...

Actually, if the dataset is not too large, there's another alternative to the API which might even be way cooler: The server could preprocess the charging station data and host...

I downloaded the OSM planet file (60 GiB) and ran Osmosis on it to extract all nodes with `amenity=charging_station`. This results in 52'210 nodes exported. In an uncompressed "PostgreSQL dump"...

Hi @johan12345, quick status update! The Swiss OSM Community's "Project of the Month" in September was focussed on adding and improving charging stations in OSM: https://wiki.openstreetmap.org/wiki/DE:Project_of_the_month_Switzerland/Charging_Stations Right now, there are...

Here's my PoC: https://github.com/dbrgn/evmap-osm The script currently takes roughly 6 minutes to fetch all 57437 charging stations via Overpass query (27 MiB of raw JSON) and writes them to a...

> Can we assume that they always contain this type data and convert them into the correct JSON types, or is there no such validation in place on the OSM...

I started working on the parsing and conversion code: https://github.com/dbrgn/EVMap/tree/osm Right now I only handle a single JSON entry. However, the current data source JSON file contains a top-level object...

The evmap-osm script is updated: https://github.com/dbrgn/evmap-osm The output now looks like this: 

Very nice! I'll try to finish the parsing code this week.

An initial version of the parser is *almost* done, only power parsing is left which should be fairly straightforward. During the implementation I decided to make `Chargepoint.power` nullable instead of...