Locations Module

Introduction

The Location objects live in the CPO back-end system. They describe the charging locations of an operator.

8.1. Flow and Lifecycle

The Locations module has the Location as base object. Each Location can have multiple EVSEs (1:n) and each EVSE can have multiple Connectors (1:n). With the methods in the Receiver interface, Location data and status information can be shared with for example an eMSP and NSP. Updates can be made to a whole Location, but also only to an EVSE or a single Connector.

8.1.1. No Public Charging or Roaming

When a Location is not available for either Public Charging or Roaming, it is RECOMMENDED to NOT send that Location via OCPI to receiving parties.

8.1.2. Group of Charge Points

OCPP 2.0 supports a 3-tier model: Charge Point → EVSE → Connector. OCPI does not have this exact model — OCPI has Location at the highest level, each Location can have multiple EVSEs, and every EVSE can have one or more Connectors.

When mapping OCPP Charge Points to OCPI, there are 2 options:

• One Location for a group of Charge Points at the same location. (preferred)
• One Location per Charge Point at the same location.

OCPI prefers the first method. An EV driver does not care if a Location consists of one Charge Point with a very large amount of EVSEs, or a large amount of Charge Points with only one EVSE. The EV driver wants to know how many EVSEs are available. Grouping Charge Points in the same location into one OCPI Location will show better on a map that shows Charging Locations.

8.1.3. OCPP 1.x Charge Points with Multiple Connectors per EVSE

OCPP 1.x was not designed to support the 3-tier model. It had no notion of EVSEs. The Open Charge Alliance has written an Application Note: "Multiple Connectors per EVSE in a OCPP 1.x implementation".

The workaround:

• Define one 'virtual' EVSE per Connector.
• When a connector of a hardware EVSE becomes unavailable, set all 'virtual' EVSEs for all the connectors of the hardware EVSE to unavailable, etc.

8.2.1. Sender Interface

Typically implemented by market roles like: CPO.

8.2.1.1. GET Method

Depending on the URL Segments provided, the GET request can either be used to retrieve information about a list of available Locations (with EVSEs and Connectors) at a CPO (GET List) or it can be used to retrieve information about one specific Location, EVSE or Connector (GET Object).

{locations_endpoint_url}?[date_from={date_from}]&[date_to={date_to}]&[offset={offset}]&[limit={limit}]

https://www.server.com/ocpi/cpo/2.2.1/locations/?date_from=2019-01-28T12:00:00&date_to=2019-01-29T12:00:00
https://ocpi.server.com/2.2.1/locations/?offset=50
https://www.server.com/ocpi/2.2.1/locations/?date_from=2019-01-29T12:00:00&limit=100
https://www.server.com/ocpi/cpo/2.2.1/locations/?offset=50&limit=100

{locations_endpoint_url}/{location_id}[/{evse_uid}][/{connector_id}]

https://www.server.com/ocpi/cpo/2.2.1/locations/LOC1
https://www.server.com/ocpi/cpo/2.2.1/locations/LOC1/3256
https://www.server.com/ocpi/cpo/2.2.1/locations/LOC1/3256/1

8.2.2. Receiver Interface

Typically implemented by market roles like: eMSP and NSP.

Locations are Client Owned Objects, so the end-points need to contain the required extra fields: country_code and party_id.

{locations_endpoint_url}/{country_code}/{party_id}/{location_id}[/{evse_uid}][/{connector_id}]

https://www.server.com/ocpi/emsp/2.2.1/locations/BE/BEC/LOC1
https://server.com/ocpi/2.2.1/locations/BE/BEC/LOC1/3256
https://ocpi.server.com/ocpi/2.2.1/locations/BE/BEC/LOC1/3256/1

8.2.2.1. GET Method

If the CPO wants to check the status of a Location, EVSE or Connector object in the eMSP system, it might GET the object from the eMSP system for validation purposes. The CPO is the owner of the objects, so it would be illogical if the eMSP system had a different status or was missing an object. If a discrepancy is found, the CPO might push an update to the eMSP via a PUT or PATCH call.

Request Parameters

Response Data

The response contains the requested object.

8.2.2.2. PUT Method

The CPO pushes available Location, EVSE or Connector objects to the eMSP. PUT can be used to send new Location objects to the eMSP but also to replace existing Locations.

Request Parameters

This is an information Push message, the objects pushed will not be owned by the eMSP. To make distinctions between objects being pushed to an eMSP from different CPOs, the party_id and country_code have to be included in the URL.

Request Body

The request body contains the new/updated object.

Example: Add an EVSE

To add an EVSE, simply put the full object in an update message, including all its required fields. Since the id will be new to the eMSP's system, the receiving party will know that it is a new object. When not all required fields are specified, the object may be discarded.

{
  "uid": "3256",
  "evse_id": "BE*BEC*E041503003",
  "status": "AVAILABLE",
  "capabilities": ["RESERVABLE"],
  "connectors": [
    {
      "id": "1",
      "standard": "IEC_62196_T2",
      "format": "SOCKET",
      "tariff_ids": ["14"]
    }
  ],
  "floor": -1,
  "physical_reference": 3,
  "last_updated": "2019-06-24T12:39:09Z"
}

8.2.2.3. PATCH Method

Same as the PUT method, but only the fields/objects that have to be updated have to be present. Other fields/objects that are not specified as part of the request are considered unchanged. Therefore, this method is not suitable to remove information shared earlier.

Example: A Simple Status Update

This is the most common type of update message. It is used to notify eMSPs that the status of an EVSE changed.

{
  "status": "CHARGING",
  "last_updated": "2019-06-24T12:39:09Z"
}

Example: Change the Location Name

{
  "name": "Interparking Gent Zuid",
  "last_updated": "2019-06-24T12:39:09Z"
}

Example: Set Tariff Update

Connector 2 of EVSE 1 of Location 1012 receives a new pricing scheme.

{
  "tariff_ids": ["15"],
  "last_updated": "2019-06-24T12:39:09Z"
}

Example: Delete an EVSE

An EVSE can be deleted by updating its status property.

{
  "status": "REMOVED",
  "last_updated": "2019-06-24T12:39:09Z"
}

8.3.1. Location Object

The Location object describes the location and its properties where a group of EVSEs that belong together are installed. Typically, the Location object is the exact location of the group of EVSEs, but it can also be the entrance of a parking garage which contains these EVSEs. The exact way to reach each EVSE can be further specified by its own properties.

Locations may be shown in apps or on websites etc. when the flag: publish is set to true. Locations that have this flag set to false SHALL not be shown in an app or on a website etc. unless it is to the owner of a Token in the publish_allowed_to list. Even parties like NSP or eMSP that do not 'own' this Token MAY show this location on an app or website, but only to the owner of that Token.

If the user of their app/website has provided information about his/her Token, and that information matches all the fields of one of the PublishToken tokens in the list, then they are allowed to show this location to their user. It is not allowed in OCPI to use a Token that is not 'owned' by the eMSP itself to start a charging session.

Private Charge Points, home or business that do not need to be published on apps, and do not require remote control via OCPI, SHOULD not be PUT via the OCPI Locations module.

8.3.2. EVSE Object

The EVSE object describes the part that controls the power supply to a single EV in a single session. It always belongs to a Location object. The object only contains directions to get from the location itself to the EVSE (i.e. floor, physical_reference or directions).

When the directional properties of an EVSE are insufficient to reach the EVSE from the Location point, then it typically indicates that the EVSE should be put in a different Location object (sometimes with the same address but with different coordinates/directions).

An EVSE object has a list of Connectors which can not be used simultaneously: only one connector per EVSE can be used at the time.

8.3.3. Connector Object

A Connector is the socket or cable and plug available for the EV to use. A single EVSE may provide multiple Connectors but only one of them can be in use at the same time. A Connector always belongs to an EVSE object.

8.3.4. Parking Object

Describes a parking space that a vehicle can be parked in while charging. For EVSEs around which no identifiable delineated parking spaces are available, a Parking object may describe the limitations that apply for parking near the EVSE without describing a specific space. This occurs a lot with streetside parking, for example.

This is an example of a public charging location. Can be used by any EV Driver as long as his eMSP has a roaming agreement with the CPO. Or the Charge Point has an ad-hoc payment possibility.

• publish = true
• parking_type = ON_STREET but could also be another value
• EVSE.parking_restrictions not used

{
  "country_code": "BE",
  "party_id": "BEC",
  "id": "LOC1",
  "publish": true,
  "name": "Gent Zuid",
  "address": "F.Rooseveltlaan 3A",
  "city": "Gent",
  "postal_code": "9000",
  "country": "BEL",
  "coordinates": {
    "latitude": "51.047599",
    "longitude": "3.729944"
  },
  "parking_type": "PARKING_GARAGE",
  "evses": [{
    "uid": "3256",
    "evse_id": "BE*BEC*E041503001",
    "status": "AVAILABLE",
    "capabilities": ["RESERVABLE"],
    "connectors": [{
      "id": "1",
      "standard": "IEC_62196_T2",
      "format": "CABLE",
      "power_type": "AC_3_PHASE",
      "max_voltage": 220,
      "max_amperage": 16,
      "tariff_ids": ["11"],
      "last_updated": "2015-03-16T10:10:02Z"
    }, {
      "id": "2",
      "standard": "IEC_62196_T2",
      "format": "SOCKET",
      "power_type": "AC_3_PHASE",
      "max_voltage": 220,
      "max_amperage": 16,
      "tariff_ids": ["13"],
      "last_updated": "2015-03-18T08:12:01Z"
    }],
    "parking": [
      {"parking_id": "1", "evse_position": "LEFT"},
      {"parking_id": "2", "evse_position": "RIGHT"}
    ],
    "physical_reference": "1",
    "floor_level": "-1",
    "last_updated": "2015-06-28T08:12:01Z"
  }, {
    "uid": "3257",
    "evse_id": "BE*BEC*E041503002",
    "status": "RESERVED",
    "capabilities": ["RESERVABLE"],
    "connectors": [{
      "id": "1",
      "standard": "IEC_62196_T2",
      "format": "SOCKET",
      "power_type": "AC_3_PHASE",
      "max_voltage": 220,
      "max_amperage": 16,
      "tariff_ids": ["12"],
      "last_updated": "2015-06-29T20:39:09Z"
    }],
    "parking": [
      {"parking_id": "2", "evse_position": "LEFT"},
      {"parking_id": "3", "evse_position": "RIGHT"}
    ],
    "physical_reference": "2",
    "floor_level": "-2",
    "last_updated": "2015-06-29T20:39:09Z"
  }],
  "parking_places": [{
    "id": "1",
    "physical_reference": "B1",
    "vehicle_types": ["PERSONAL_VEHICLE"],
    "reservation_required": false,
    "restricted_to_type": true
  }, {
    "id": "2",
    "physical_reference": "B2",
    "vehicle_types": ["PERSONAL_VEHICLE"],
    "reservation_required": false,
    "restricted_to_type": true
  }, {
    "id": "3",
    "physical_reference": "B3",
    "vehicle_types": ["PERSONAL_VEHICLE"],
    "reservation_required": false,
    "restricted_to_type": true
  }],
  "operator": {
    "name": "BeCharged"
  },
  "time_zone": "Europe/Brussels",
  "last_updated": "2015-06-29T20:39:09Z"
}

This is an example of a destination charging location. This is a Location where only guests, employees or customers can charge. For an EV driver, it can be useful to know if he/she can charge at his destination.

For example at a restaurant, only customers of the restaurant can charge their EV. Or at an office building where employees and guests of the office can charge their EV. Locations you can think of where this is useful: restaurants, bars, clubs, theme parks, stores, supermarkets, company buildings, office buildings, etc.

• publish = true
• parking_type = PARKING_LOT (but could also be PARKING_GARAGE, ON_DRIVEWAY or UNDERGROUND_GARAGE)
• EVSE.parking_restrictions = CUSTOMERS

{
  "country_code": "NL",
  "party_id": "ALF",
  "id": "3e7b39c2-10d0-4138-a8b3-8509a25f9920",
  "publish": true,
  "name": "ihomer",
  "address": "Tamboerijn 7",
  "city": "Etten-Leur",
  "postal_code": "4876 BS",
  "country": "NLD",
  "coordinates": {
    "latitude": "51.562787",
    "longitude": "4.638975"
  },
  "parking_type": "PARKING_LOT",
  "evses": [{
    "uid": "fd855359-bc81-47bb-bb89-849ae3dac89e",
    "evse_id": "NL*ALF*E000000001",
    "status": "AVAILABLE",
    "connectors": [{
      "id": "1",
      "standard": "IEC_62196_T2",
      "format": "SOCKET",
      "power_type": "AC_3_PHASE",
      "max_voltage": 220,
      "max_amperage": 16,
      "last_updated": "2019-07-01T12:12:11Z"
    }],
    "parking_restrictions": ["CUSTOMERS"],
    "last_updated": "2019-07-01T12:12:11Z"
  }],
  "time_zone": "Europe/Amsterdam",
  "last_updated": "2019-07-01T12:12:11Z"
}

This is an example of a destination charging location. But the owner of the location has requested not to publish the location in Apps or on websites.

Charging is still possible: EV drivers of an eMSP with a roaming agreement can still charge their EV. The eMSP helpdesk can use the information from the Location module to help the driver, maybe even start a session for a driver. Starting a session from an App is not possible, because the driver will not be able to select the Charge Point on a map.

In case the EV driver is not billed for charging, there is, in such a case, no reason to publish the location via OCPI.

• publish = false
• publish_allowed_to not used
• parking_type = not used
• EVSE.parking_restrictions = CUSTOMERS may still be useful so a support desk can also tell this to a customer

{
  "country_code": "NL",
  "party_id": "ALF",
  "id": "3e7b39c2-10d0-4138-a8b3-8509a25f9920",
  "publish": false,
  "name": "ihomer",
  "address": "Tamboerijn 7",
  "city": "Etten-Leur",
  "postal_code": "4876 BS",
  "country": "NLD",
  "coordinates": {
    "latitude": "51.562787",
    "longitude": "4.638975"
  },
  "evses": [{
    "uid": "fd855359-bc81-47bb-bb89-849ae3dac89e",
    "evse_id": "NL*ALF*E000000001",
    "status": "AVAILABLE",
    "connectors": [{
      "id": "1",
      "standard": "IEC_62196_T2",
      "format": "SOCKET",
      "power_type": "AC_3_PHASE",
      "max_voltage": 220,
      "max_amperage": 16,
      "last_updated": "2019-07-01T12:12:11Z"
    }],
    "parking_restrictions": ["CUSTOMERS"],
    "last_updated": "2019-07-01T12:12:11Z"
  }],
  "time_zone": "Europe/Amsterdam",
  "last_updated": "2019-07-01T12:12:11Z"
}

This is an example of a charging location that only a limited group can see (and use) via an App or website.

Typical examples where this is useful:

• Charge Points in the parking garage of an apartment building. Only owners can see/control the Charge Points.
• Charge Points at an office, for employees only. Only employees can see/control the Charge Points.
• Charge Points at vehicle depot. Any employee can see/control a charge point, even transactions they did not start. Use group_id for this.

The locations SHALL NOT be published to the general public. Only selected Tokens can see (and control) the Charge Points via eMSP app.

• publish = false
• publish_allowed_to contains list with information of Tokens that are allowed to be shown the Location
• parking_type = UNDERGROUND_GARAGE (but could also be PARKING_GARAGE, ON_DRIVEWAY or PARKING_LOT)

{
  "country_code": "NL",
  "party_id": "ALL",
  "id": "f76c2e0c-a6ef-4f67-bf23-6a187e5ca0e0",
  "publish": false,
  "publish_allowed_to": [{
    "visual_number": "12345-67",
    "issuer": "NewMotion"
  }, {
    "visual_number": "0055375624",
    "issuer": "ANWB"
  }, {
    "uid": "12345678905880",
    "type": "RFID"
  }],
  "name": "Water State",
  "address": "Taco van der Veenplein 12",
  "city": "Leeuwarden",
  "postal_code": "8923 EM",
  "country": "NLD",
  "coordinates": {
    "latitude": "53.213763",
    "longitude": "5.804638"
  },
  "parking_type": "UNDERGROUND_GARAGE",
  "evses": [{
    "uid": "8c1b3487-61ac-40a7-a367-21eee99dbd90",
    "evse_id": "NL*ALL*EG00000013",
    "status": "AVAILABLE",
    "connectors": [{
      "id": "1",
      "standard": "IEC_62196_T2",
      "format": "SOCKET",
      "power_type": "AC_3_PHASE",
      "max_voltage": 230,
      "max_amperage": 16,
      "last_updated": "2019-09-27T00:19:45Z"
    }],
    "last_updated": "2019-09-27T00:19:45Z"
  }],
  "time_zone": "Europe/Amsterdam",
  "last_updated": "2019-09-27T00:19:45Z"
}

This is an example of a private/home charge point that needs to be controlled via an eMSP App. The locations SHALL NOT be published to the general public. Only the owner, identified by his/her Token can see (and control) the Charge Points via an eMSP app.

• publish = false
• publish_allowed_to contains the information of the Tokens of the owner
• parking_type = not used, not relevant, owner knows where his Charge Point is

{
  "country_code": "DE",
  "party_id": "ALL",
  "id": "a5295927-09b9-4a71-b4b9-a5fffdfa0b77",
  "publish": false,
  "publish_allowed_to": [{
    "visual_number": "0123456-99",
    "issuer": "MoveMove"
  }],
  "address": "Krautwigstrasse 283A",
  "city": "Koln",
  "postal_code": "50931",
  "country": "DEU",
  "coordinates": {
    "latitude": "50.931826",
    "longitude": "6.964043"
  },
  "parking_type": "ON_DRIVEWAY",
  "evses": [{
    "uid": "4534ad5f-45be-428b-bfd0-fa489dda932d",
    "evse_id": "DE*ALL*EG00000001",
    "status": "AVAILABLE",
    "connectors": [{
      "id": "1",
      "standard": "IEC_62196_T2",
      "format": "SOCKET",
      "power_type": "AC_1_PHASE",
      "max_voltage": 230,
      "max_amperage": 8,
      "last_updated": "2019-04-05T17:17:56Z"
    }],
    "last_updated": "2019-04-05T17:17:56Z"
  }],
  "time_zone": "Europe/Berlin",
  "last_updated": "2019-04-05T17:17:56Z"
}

This is an example of a charge point, located in a parking garage with limited opening hours: 7:00 - 18:00. If the EV is left in the parking garage overnight, the car will still be charged.

• publish = true
• parking_type = PARKING_GARAGE but could also be another value
• EVSE.parking_restrictions not used
• opening_times is used
• charging_when_closed = true

{
  "country_code": "SE",
  "party_id": "EVC",
  "id": "cbb0df21-d17d-40ba-a4aa-dc588c8f98cb",
  "publish": true,
  "name": "P-Huset Leonard",
  "address": "Claesgatan 6",
  "city": "Malmo",
  "postal_code": "214 26",
  "country": "SWE",
  "coordinates": {
    "latitude": "55.590325",
    "longitude": "13.008307"
  },
  "parking_type": "PARKING_GARAGE",
  "evses": [{
    "uid": "eccb8dd9-4189-433e-b100-cc0945dd17dc",
    "evse_id": "SE*EVC*E000000123",
    "status": "AVAILABLE",
    "connectors": [{
      "id": "1",
      "standard": "IEC_62196_T2",
      "format": "SOCKET",
      "power_type": "AC_3_PHASE",
      "max_voltage": 230,
      "max_amperage": 32,
      "last_updated": "2017-03-07T02:21:22Z"
    }],
    "parking": [{
      "parking_id": "000e3877-87bf-473e-8e71-70d3aa6d64ea",
      "evse_position": "CENTER"
    }],
    "last_updated": "2017-03-07T02:21:22Z"
  }],
  "parking_places": [{
    "id": "000e3877-87bf-473e-8e71-70d3aa6d64ea",
    "physical_reference": "A0",
    "vehicle_types": ["PERSONAL_VEHICLE"],
    "reservation_required": false,
    "restricted_to_type": true
  }],
  "time_zone": "Europe/Stockholm",
  "opening_times": {
    "twentyfourseven": false,
    "regular_hours": [
      {"weekday": 1, "period_begin": "07:00", "period_end": "18:00"},
      {"weekday": 2, "period_begin": "07:00", "period_end": "18:00"},
      {"weekday": 3, "period_begin": "07:00", "period_end": "18:00"},
      {"weekday": 4, "period_begin": "07:00", "period_end": "18:00"},
      {"weekday": 5, "period_begin": "07:00", "period_end": "18:00"},
      {"weekday": 6, "period_begin": "07:00", "period_end": "18:00"},
      {"weekday": 7, "period_begin": "07:00", "period_end": "18:00"}
    ]
  },
  "charging_when_closed": true,
  "last_updated": "2017-03-07T02:21:22Z"
}

8.4.1. AdditionalGeoLocation class

This class defines an additional geo location that is relevant for the Charge Point. The geodetic system to be used is WGS 84.

8.4.2. BusinessDetails class

8.4.3. Capability OpenEnum

The capabilities of an EVSE.

When a Charge Point supports ad-hoc payments with a payment terminal, please use a combination of the following values to explain the possibilities of the terminal: CHIP_CARD_SUPPORT, CONTACTLESS_CARD_SUPPORT, CREDIT_CARD_PAYABLE, DEBIT_CARD_PAYABLE, PED_TERMINAL.

There are Charge Points in the field that do not yet support OCPP 2.x. If these Charge Points have multiple connectors per EVSE, the CPO needs to know which connector to start when receiving a StartSession for the given EVSE. If this is the case, the CPO should set the START_SESSION_CONNECTOR_REQUIRED capability on the given EVSE.

8.4.4. ConnectorCapability OpenEnum

Functionalities that a Connector may or may not support. These capabilities are meant to signal to eMSPs and their Drivers that a Driver can indeed use these functionalities at a Connector. Mere support for a standard by the charging hardware is not enough to warrant the presence of these capabilities.

8.4.5. ConnectorFormat enum

The format of the connector, whether it is a socket or a plug.

8.4.6. ConnectorType OpenEnum

The socket or plug standard of the charging point.

8.4.7. EnergyMix class

This type is used to specify the energy mix and environmental impact of the supplied energy at a location or in a tariff.

The supplier_name and energy_product_name fields can be used to look up energy qualification or to show it directly to the customer (for well-known brands like Greenpeace Energy, etc.)

Examples

"energy_mix": {
  "is_green_energy": true
}

"energy_mix": {
  "is_green_energy": true,
  "supplier_name": "Greenpeace Energy e6",
  "energy_product_name": "eco-power"
}

"energy_mix": {
  "is_green_energy": false,
  "energy_sources": [
    { "source": "GENERAL_GREEN",  "percentage": 35.9 },
    { "source": "GAS",            "percentage": 6.3  },
    { "source": "COAL",           "percentage": 33.2 },
    { "source": "GENERAL_FOSSIL", "percentage": 2.9  },
    { "source": "NUCLEAR",        "percentage": 21.7 }
  ],
  "environ_impact": [
    { "category": "NUCLEAR_WASTE",  "amount": 0.0006 },
    { "category": "CARBON_DIOXIDE", "amount": 372    }
  ],
  "supplier_name":       "E.ON Energy Deutschland",
  "energy_product_name": "E.ON DirektStrom eco"
}

8.4.8. EnergySource class

Key-value pairs (enum + percentage) of energy sources. All given values of all categories should add up to 100 percent.

8.4.9. EnergySourceCategory enum

Categories of energy sources.

8.4.10. EnvironmentalImpact class

Amount of waste produced/emitted per kWh.

8.4.11. EnvironmentalImpactCategory OpenEnum

Categories of environmental impact values.

8.4.12. EVSEParking class

A link between an EVSE and a Parking object. The presence of an EVSEParking object in an EVSE indicates that a certain parking space can be used when charging at that EVSE.

8.4.13. EVSEPosition enum

The position of an EVSE relative to the EVSE's parking space.

8.4.14. ExceptionalPeriod class

Specifies one exceptional period for opening or access hours.

8.4.15. Facility OpenEnum

8.4.16. GeoLocation class

This class defines the geo location of the Charge Point. The geodetic system to be used is WGS 84.

8.4.17. Hours class

Opening and access hours of the location.

Example: 24/7 Open with Exceptional Closing

Open 24 hours per day, 7 days a week, except for 25th of December 2018 between 03:00 and 05:00.

{
  "twentyfourseven": true,
  "exceptional_closings": [{
    "period_begin": "2018-12-25T03:00:00Z",
    "period_end": "2018-12-25T05:00:00Z"
  }]
}

Example: Opening Hours with Exceptional Closing

Regular opening hours between 01:00 and 06:00. With exceptional closing on 25th of December 2018 between 03:00 and 05:00.

{
  "twentyfourseven": false,
  "regular_hours": [{
    "weekday": 1,
    "period_begin": "01:00",
    "period_end": "06:00"
  }, {
    "weekday": 2,
    "period_begin": "01:00",
    "period_end": "06:00"
  }],
  "exceptional_closings": [{
    "period_begin": "2018-12-25T03:00:00Z",
    "period_end": "2018-12-25T05:00:00Z"
  }]
}

Example: Opening Hours with Exceptional Opening

Regular opening hours between 00:00 and 04:00. With exceptional opening on 25th of December 2018 between 05:00 and 07:00.

{
  "twentyfourseven": false,
  "regular_hours": [{
    "weekday": 1,
    "period_begin": "00:00",
    "period_end": "04:00"
  }, {
    "weekday": 2,
    "period_begin": "00:00",
    "period_end": "04:00"
  }],
  "exceptional_openings": [{
    "period_begin": "2018-12-25T05:00:00Z",
    "period_end": "2018-12-25T06:00:00Z"
  }]
}

8.4.18. Image class

This class references an image related to an EVSE in terms of a file name or url. The recommended setup is a public available web server hosted and updated by the EVSE Operator. Per charge point an unlimited number of images of each type is allowed. Recommended are at least two images where one is a network or provider logo and the second is a station photo.

8.4.19. ImageCategory OpenEnum

The category of an image to obtain the correct usage in a user presentation.

8.4.20. ParkingDirection enum

Indicates the direction in which parking occurs relative to the roadway on which vehicles approach the EVSE.

8.4.21. ParkingRestriction OpenEnum

This value, if provided, represents the restriction to the parking spot for different purposes.

8.4.22. ParkingType OpenEnum

Reflects the general type of the charge point's location. May be used for user information.

8.4.23. PowerType enum

8.4.24. PublishTokenType class

Defines the set of values that identify a token to which a Location might be published.

8.4.25. RegularHours class

Regular recurring operation or access hours.

Example

Operating on weekdays from 8am till 8pm with one exceptional opening on 22/6/2014 and one exceptional closing the Monday after:

"opening_times": {
  "regular_hours": [
    {"weekday": 1, "period_begin": "08:00", "period_end": "20:00"},
    {"weekday": 2, "period_begin": "08:00", "period_end": "20:00"},
    {"weekday": 3, "period_begin": "08:00", "period_end": "20:00"},
    {"weekday": 4, "period_begin": "08:00", "period_end": "20:00"},
    {"weekday": 5, "period_begin": "08:00", "period_end": "20:00"}
  ],
  "twentyfourseven": false,
  "exceptional_openings": [
    {"period_begin": "2014-06-21T09:00:00Z", "period_end": "2014-06-21T12:00:00Z"}
  ],
  "exceptional_closings": [
    {"period_begin": "2014-06-24T00:00:00Z", "period_end": "2014-06-25T00:00:00Z"}
  ]
}

8.4.26. Status enum

The status of an EVSE.

8.4.27. StatusSchedule class

This type is used to schedule status periods in the future. The eMSP can provide this information to the EV user for trip planning purposes. A period MAY have no end. Example: "This station will be running as of tomorrow. Today it is still planned and under construction."

8.4.28. VehicleType OpenEnum

A categorization of vehicles to indicate which type of vehicles can use a certain EVSE. Approximate UNECE codes corresponding to our categories are given in the third column.