Source
https://evroam.co.nz/ — original source (opens in a new tab; the file is not redistributed)
Summary
EVRoam (evroam.co.nz) is the live data feed for Aotearoa New Zealand’s public EV charging infrastructure, led by EECA (Energy Efficiency and Conservation Authority). Collects information from monitored public charge points around NZ and freely distributes it via API to downstream apps and websites — notably EECA’s Public EV Charger Dashboard and NZTA’s Journey Planner. EECA describes EVRoam as a “world-first collaboration with [NZ’s] energy industry that accelerates New Zealand’s transition to zero-carbon transport.” Operator/technical support: Seamless Data.
Key thesis / methodology insights
- EVRoam is the upstream live source for NZ’s public EV charging open data — fed by Charge Point Operators (CPOs) via API + bulk CSV upload, then redistributed via EECA’s Public EV Charger Dashboard, NZTA’s Journey Planner, and consumer apps. The 4 sibling EV CSVs (RD_009, RD_010, RD_011, RD_012) are all exports of EVRoam-fed EECA dashboards. URL_006 closes the data-lineage citation graph for the EV datasets. URL_006
- Critical NI / methodology constraint: NO historic data is available via the EVRoam API — only the current-state charging infrastructure. Means time-series analysis (e.g. RT_146 monitoring district-level EV trajectory) cannot be reconstructed from EVRoam alone; requires preserved snapshots like RD_011 (~Jan 2026) + RD_012 (~Q3/Q4 2025) that EECA happened to export at different vintages. Long-term NI calc design must capture and preserve EECA snapshots locally rather than relying on EVRoam API to backfill history. URL_006
- OCPI standard NOT yet supported (Open Charge Point Interface, the European interoperability standard). On EVRoam’s “heavily requested” product roadmap but no commit date. NZ’s public charger network is currently NOT OCPI-interoperable with European/global roaming aggregators. Constraint for any NI community-charger interoperability scenario — a Lower Moutere community charger would need EVRoam upload (CPO API or bulk CSV) to appear in NZ-wide app aggregators, not OCPI. URL_006
- EVRoam soft-delete model: when CPOs remove a charger, it’s flagged
IsProviderDelete=Yesrather than physically removed, so downstream apps that cache extracts can detect removals. Methodology implication: snapshot exports like RD_010 may include soft-deleted units if filter not applied — minor data-quality consideration for NI cross-checks. URL_006 - Data quality is CPO-self-reported — “EVRoam itself doesn’t do anything to change or validate the information - so we are dependent on [CPOs] to give us up to date information.” Explains the Z Waiouru / Z Turangi geocoding errors flagged in RD_010 (RT_144) and the Region taxonomy double-coding in RD_009 (RT_136) — these are upstream CPO data-entry artifacts that EECA does not normalise. URL_006
Connections
Links to
Referenced by