Electronic Parking System (EPS) Carpark Records
The Electronic Parking System (EPS) dataset contains information on the public carpark records managed by HDB, URA, SDC, JTC and NParks. It includes data from both EPS and Parking@HDB. These records contain details such as Carpark Name, Carpark Operator (CPO), Entry / Exit date and time, and the Parking Charge(s), which are obtained from 5 designated Single Source of Truth Agencies (SSOTs), namely, HDB, URA, SDC, JTC and NParks.
Currently, HDB, URA, and SDC have been onboarded to the Trusted Center for Sensor Data (TCS). JTC has been partially onboarded, with EPS carpark data currently available only for carparks within the Punggol Digital District (PDD), while NParks is in the process of onboarding.
Datasets Update Frequency and Date Ranges
The EPS Carpark Records dataset contains data as early as 1 October 2018 up till 2 days before the current date. i.e. for 3rd Jan 2024, the latest dataset is 1st Jan 2024. Since carpark consist of multiple data sources, there are different date ranges from every sources.
The following table shows the update frequency and start date of the records for each source.
| Source | Update Frequency | Start Date | End Date | Percentage of Records |
|---|---|---|---|---|
| HDB EPS | Daily | 01/10/2018 | T - 2days | >99% |
| HDB Parking@HDB | Daily | 01/01/2021 | T - 2days | <1% |
| URA EPS | Daily | 01/01/2021 | T - 2days | <1% |
| SDC EPS | Daily | 22/02/2023 | T - 2days | <1% |
| JTC EPS (Punggol Digital District only) | Daily | 31/01/2025 | T - 2days | <1% |
Data Collection
The EPS carpark records are collected by the SSOTs from individual CPOs and provided to TCS for normalisation before making it available for WOG sharing. Data is updated on a daily basis.
Fields
This segment covers a short description of each field and domain specific information. You can find the detailed metadata here
You can download a sample dataset from the Dataset preview section, available on the DataHive
Mandatory Fields
With effect from 1 Jan 2023, these fields will be mandatory for all new records, which are already present in the majority of historical records.
Carpark Operator
Name of CPO that operates the carpark.
- Reflected as null for records under Parking@HDB category which is currently operated by HDB
- All other records will have a CPO name
Carpark Code
A short code that uniquely identifies the carpark.
Carpark Name
The name of the carpark, assigned by the CPO/SSOT.
Reflected as null for a small % of the historical records for URA carparks. Carpark Name is not provided by URA directly and it is separately obtained from Geospace. TC has done the merging of the 2 datasets for the convenience of users, but some of the historical records are no longer available (<1% of the dataset).
Parking Type
Classifier for type of parking ticket. Refer to the code tables found here
Vehicle Type
Classifier for type of vehicle. Refer to the code tables found here
Optional Fields
The following fields are optional because CPOs are not required to provide such information under existing contracts.
However, SSOTs have been able to obtain the additional information for most of the fields.
SSOTs are progressively updating their contracts with CPOs to provide these additional fields.
Entry Timestamp
The recorded entry datetime stamp (in UTC +8) of vehicle by IU/Autopass card.
- Reflected as null for instances where vendors send multiple records for the same transaction
- Reflected as the same value in multiple carpark locations due to 2 carparks being close to each other
- Reflected as the same value as Exit Timestamp due to vendors rounding off the entry and exit timing.
Exit Timestamp
The recorded exit datetime stamp (in UTC +8) of vehicle by IU/Autopass card.
Reflected as null for instances where vendors send multiple records for the same transaction.
Entry Station ID
The entry gantry/station in which the vehicle entered the carpark from.
Reflected as null for Instances involving entry barrier malfunctions.
Exit Station ID
The exit gantry/station in which the vehicle exited the carpark from.
Reflected as null for Parking@HDB records where there are no exit gantries.
Vehicle Number
Masked vehicle plate number. This is a derived field obtained by matching the vehicle IU in this dataset to the vehicle IU in the Vehicle Registration Number dataset. Carpark gantries do not capture vehicle plate numbers.
Note: This is done on a best-effort basis, and a mapping may not be available for all records.
Vehicle IU
Masked vehicle IU number/ Autopass card number.
Reflected as null for Parking@HDB records where IU is optional.
Vehicle Card Number
Masked vehicle card number.
Reflected as null for Parking@HDB records which operates on a post-paid basis.
Parking Fee Payable
Parking fee payable in SGD.
Parking Fee Paid
Parking fee paid in SGD.
Reflected as 0 for Records where fees could be offset by credits using Shopperlink
Parked Duration
Time between Entry and Exit Timestamps for a parking record in minutes.
Transaction Type
Classifier for type of transaction. Refer to the code tables found here
FAQ
Does the dataset include private carparks (condo/commercial buildings/etc)?
- No, the dataset only contains parking records from public carparks managed by HDB, URA, SDC, JTC and NParks.
What is the difference between EPS and Parking@HDB?
-
EPS carparks utilise existing ERP technology and deduct parking charges from the CashCard in the In-Vehicle Unit (IU) when the vehicle leaves the car park. It is the most common carpark system found across Singapore, with barriers at the entrances and exit of the carpark.
-
Parking@HDB is HDB’s pilot trial on a new short term parking experience for motorists introduced in smart town, Punggol. The Northshore estate in Punggol has seen various smart solutions in the estate to improve and enhance the lives of residents. Parking@HDB is one of them.
Featuring a barrier-less car park access, the system captures the licence plate of vehicles via a suite of cameras. Without a barrier arm, motorists are able to enjoy seamless entries and exits when visiting a car park equipped with Parking@HDB. Within the car park, the system also controls coloured LED light indicators to enable motorists to determine if the lot has been occupied or not. This increases the accessibility when navigating through a Parking@HDB car park.
HDB is also able to send motorists real-time notifications via their mobile number and/or the means of the companion app, Parking@HDB, by the means of a dedicated backend processing system. Examples of these notifications are when a motorist has parked illegally at a location that they are not meant to be in, Parking@HDB sends them an alert, so that they may move their vehicle before HDB takes enforcement action and if the parking charges are not deducted successfully at the exit of the car park, the system will notify the motorist and allows him to pay via the companion app.
The companion app also enables digital payment, providing a conclusive and seamless parking experience for the motorists. There is no longer a need to remember to top up CashCards and CEPAS cards or experiencing difficulties with locked cards or damaged cards as well. The pilot of Parking@HDB has been successfully launched at 8 car parks across the Punggol estate and Old Airport Road.
Can I access the raw vehicle IU/card/plate number?
- No, these are de-identified (masked) by default for privacy reasons.