OCPI / transport.data.gouv.fr "Statique" data corresponding table

[jmaupetit]

Purpose

To connect to QualiCharge API, operators (that mostly use OCPI) must convert their data from OCPI to the official schema used in the API. To ease its integration, we should document an official corresponding table between those two formats.

Proposal

Statique data

Official schema	OCPI module	OCPI attribute (v2.2.1)
accessibilite_pmr	locations	parking_reservation
adresse_station	locations	address
cable_t2_attache	locations	evses.connectors.standard
code_insee_commune	NA	NA
condition_acces	locations	access_type
contact_amenageur	locations	owner
contact_operateur	locations	operator
coordonneesXY	locations	coordinates
date_maj	locations	last_updated
date_mise_en_service	NA	NA
gratuit	tariffs	tarrifs
horaires	locations	opening_times
id_pdc_itinerance	locations	evses.evse_id
id_pdc_local	locations	evses.evse_id
id_station_itinerance	locations	id
id_station_local	locations	id
implantation_station	locations	parking_type
nbre_pdc	locations	evses.evse_count
nom_amenageur	locations	owner.name
nom_enseigne	locations	name
nom_operateur	locations	operator.name
nom_station	locations	name
num_pdl	NA	NA
observations	NA	NA
paiement_acte	locations	capabilities
paiement_autre	locations	capabilities
paiement_cb	locations	capabilities
prise_type_2	locations	capabilities
prise_type_autre	locations	capabilities
prise_type_chademo	locations	capabilities
prise_type_combo_ccs	locations	capabilities
prise_type_ef	locations	capabilities
puissance_nominale	locations	evses.connectors.max_power
raccordement	NA	NA
reservation	tariffs	evses.reservation
restriction_gabarit	locations	locations.access_rule
siren_amenageur	NA	NA
station_deux_roues	locations	parking_restrictions
tarification	tariffs	price_components.price
telephone_operateur	locations	number

Dynamique data

Status

Official Schema	OCPI module	OCPI attribute (v2.2.1)
id_pdc_itinerance	locations	evses.evse_id
etat_pdc	locations	evses.connectors.status
occupation_pdc	locations	evses.connectors.status
horodatage	locations	evses.connectors.last_updated
etat_prise_type_2	locations	evses.connectors.status
etat_prise_type_combo_ccs	locations	evses.connectors.status
etat_prise_type_chademo	locations	evses.connectors.status
etat_prise_type_ef	locations	evses.connectors.status

Session

Official Schema	OCPI module	OCPI attribute (v2.2.1)
id_pdc_itinerance	locations	evses.evse_id
start	cdrs	start_date_time
end	cdrs	stop_date_time
energy	cdrs	total_energy

---

📢 This proposal intends to be collaborative. Do not hesitate to propose alternatives (if any).

[monforte-laura]

Hi Julien, very useful, thanks. For everything OCPI related that have a 'Valeurs autorisées' here https://schema.data.gouv.fr/etalab/schema-irve-statique/2.3.1/documentation.html#propriete-accessibilite-pmr
would it possibile to have the corresponding mapping (i.e. fiedl accessibilite_pmr, condition_acces, implantation_station...)?

[jmaupetit]

Hi Julien, very useful, thanks. For everything OCPI related that have a 'Valeurs autorisées' here https://schema.data.gouv.fr/etalab/schema-irve-statique/2.3.1/documentation.html#propriete-accessibilite-pmr would it possibile to have the corresponding mapping (i.e. fiedl accessibilite_pmr, condition_acces, implantation_station...)?

Yes, we'll work on it!

I'll write here one of your suggestion:

parking_type

OCPI ParkingType enum	implantation_station
ALONG_MOTORWAY	Station dédiée à la recharge rapide
ON_STREET	Parking public
ON_DRIVEWAY	Parking public
PARKING_LOT	Parking privé à usage public
default	Parking privé à usage public

[monforte-laura]

Also, restriction_gabarit | locations | locations.access_rule. I can't find the field in the OCPI data, can it be?

[jmaupetit]

Maybe to also clarify what a pdc_id_itinerance corresponds to, we should document the mapping between EVSE (as defined by OCPI 2.2.1) and pdc_id_itinerance, i.e. 1 EVSE == 1 pdc_id_itinerance

[loco-philippe]

Here are some comments and alternative regarding the correspondence table (I didn't find the access_rule attribute either).

Official schema	OCPI module	OCPI attribute (v2.2.1)	note
gratuit	locations	connector.tariff_ids	"free of charge" tariff
station_deux_roues	locations	parking_restrictions	MOTORCYCLES
nbre_pdc	locations	??evse.evse_count??	evses (list of evse)
puissance_nominale	locations	evse.connector.max_power	(4)
accessibilite_pmr	locations	evse.parking_restrictions	DISABLED
condition_acces	locations	evse.parking_restrictions	(3)
restriction_gabarit	locations	??locations.access_rule ??
id_pdc_itinerance	locations	evse.evse_id
id_pdc_local	locations	??evse.evse_id ??	NA
code_insee_commune	locations	postal_code
paiement_acte	locations	evse.capabilities	(1)
paiement_autre	locations	evse.capabilities	(1)
paiement_cb	locations	evse.capabilities	(1)
reservation	locations	evse.capabilities	RESERVABLE
prise_type_2	locations	connector.standard	(2)
prise_type_autre	locations	connector.standard	(2)
prise_type_chademo	locations	connector.standard	(2)
prise_type_combo_ccs	locations	connector.standard	(2)
prise_type_ef	locations	connector.standard	(2)
cable_t2_attache	locations	connector.format	SOCKET CABLE

(1) values : DEBIT_CARD_PAYABLE, CREDIT_CARD_PAYABLE, PED_TERMINAL, CHIP_CARD_SUPPORT, CONTACTLESS_CARD_SUPPORT
(2) values : CHADEMO, CHAOJI, DOMESTIC_x, GBT_xx, IEC_xxxxx_x, NEMA_x_x, PANTOGRAPH_xx, TESLA_x
(3) values : EV_ONLY, PLUGGED, CUSTOMERS
(4) max_poweris not used if max_voltage and max_amperage are used