Add New Operator in Romania

OCM
1

Hello,

Please add a new operator in Romania when you have some time. We will also be sharing network data via the datasharing link in the near future. Below the info:
This is an extension of the EVConnect network and we will be transitioning the site to Voltrelli.

Name: Voltrelli
Website: https://evconnect.ro/
Phone number: +40374421800

If there is anything else you need, let me know

Thank you!

2

Thanks, that’s added now.

3

Hello. We have just submitted a request to share our network data with you via the form. API endpoint and request key are in the link provided. Let us know if there are any issues or what next steps there are.

Thanks.

4

@Voltrelli thanks, I’ve had an initial look, do you know which version of OCPI your API is using?

It seems like it might be quite an old version of OCPI with som non-standard values, as it:

  • specifies Country as a 2 character ISO code instead of Country_code as a 3 character ISO code etc.
  • It has EVSE status as ACTIVE and INACTIVE but these don’t appear to be valid OCPI status codes.
  • It has connector type of CCS2 and Type etc but these are no valid OCPI values.

It would also be useful to know if your API accepts the Key as an HTTP header instead of being part of the URL query string.

5

Hello @Christopher,

I believe we are using 2.2.1.
We looked partly at the OCPI 2.2.1-d3-pre1 document dated 2023-09-07 from ocpi · GitHub as well as the examples from github:

Specifically the ocpi_2_2_1_locations-itcharge.json that was updated 3 weeks ago. Country_Code is listed as a 2 character ISO Code in both.

I see there is a newer 2.3.0-rc2 documentation available, which is from january of this year, and just quickly going through it, country_code examples are 2 character ISO. Is there another source of data we need to look at?

The API key can be accepted as an HTTP header, just need to know what header are you going to use.

Thanks

6

@Voltrelli thanks, conventionally for OCPI the header is:

Authorization: Token <key>

Regarding country data field, it should be “country_code” : “ROU”

I would not advise closely copying the example data from the test assets because each organization makes their own set of mistakes (very few implement OCPI exactly to the current spec, so we are a little flexible). Look at the Locations specification of the OCPI documents and for each field review the field name and accepted values.

We can definitely get your data to work and it is good compared to some other data sources, but now is a good time to implement the OCPI feed correctly especially if you might provide it to others in the future who might expect it to also follow the OCPI spec.

7

Thanks for the reply. We are working on the changes. Will submit a new to share in a couple of days.

8

Hello,

We have submitted a new data feed URL that contains the changes. The authentication is now via an Authentication header with a value. Let us know if that is ok.

Thank you!

1 Like
9

@Voltrelli thanks, these have been published now.

10

Thank you @Christopher !
Is there a way to refresh the data?
Some informations were wrong and we fixed the problems.

11

@Voltrelli thanks, yes this import has been refresh now.

12

Hey @Christopher !

Could you please tell us if there are more steps to be done in order to have the charging stations visible on google maps application ?
Why our stations have grey marker on your maps? Is there something wrong in our data ?

Thanks

13

@Voltrelli sorry for the delayed reply. The power in kW is used to determine the charging icon colour.

Your data has fields for voltage and amperage but in OCPI the fields should be called max_voltage and max_amperage. ocpi/mod_locations.asciidoc at master · ocpi/ocpi · GitHub

Ideally you should also provide your own value for max_electric_power otherwise we will approximately calculate that value.