Request: Use REVE data for EV chargers of Spain

[jmontane]

REVE map is where the Spanish Goverment compiles all EV chargers (>25kW) provided by charger operators.

REVA API is documented here and an API key can be requested here.

So, I request using REVE date for Spanish EV chargers.

Thanks

[GeiserX]

Requested! Thank you @jmontane
I should probably add this info it in the deployment guide for self-hosting too

[GeiserX]

API key: Validity until 21/8/2027

[GeiserX]

Shipped in #122 — thank you @jmontane, this was a good call and a clear improvement. Spain now gets its EV chargers from Mapa REVE instead of Open Charge Map.

Two things I found along the way that are worth recording here:

The API allows 5 requests per hour, 100 locations per page, and there is no bulk export. With ~14,500 locations that puts a complete pass at roughly 37 hours. So the scraper does not attempt a full sync — each hourly run fetches a few pages and the database fills in the background. The page window is derived from the wall clock rather than a stored cursor, so a redeploy resumes in place instead of restarting the crawl from page 1.

REVE and Open Charge Map overlap almost completely. I measured it: 92 of 100 sampled REVE locations sit within 50 m of an existing Open Charge Map row. Running both would double-pin about 13,000 Spanish chargers. So Open Charge Map stops being scraped for Spain immediately, its existing rows stay on the map while REVE backfills — otherwise Spain would look empty for a day and a half — and they are removed once REVE reaches 95% coverage. If you look at Spain over the next couple of days and see duplicate pins, that is the handover in progress, not a bug.

The data is noticeably better, as you said: real operator names, connector power, and INE province codes that map cleanly onto the province names the Spanish fuel scraper already uses.

Also added a workflow that opens a reminder issue a week before the key expires, since the failure mode is silent — the data would just quietly stop refreshing.

You were also right that this belongs in the self-hosting docs: PUMPERLY_REVE_API_KEY is now documented in both the README and .env.example, including the 30-plus-hour first load so nobody thinks it is broken.