Automatic number plate recognition (ANPR) project

Open data API in a single place

Provided by Leeds City Council

Get early access to Automatic number plate recognition (ANPR) project API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2017.02.23 11:54
Created
2017.02.02
Available languages
English
Keywords
DfT, HGV, capacity, emissions, engine, diesel, eurostandards, passenger, petrol, size, ring road, travel, vechilce
Quality scoring

Dataset description

A dataset providing information of the vehicle types and counts in several locations in Leeds.  Purpose of the project ---------------------- The aim of this work was to examine the profile of vehicle types in Leeds, in order to compare local emissions with national predictions. Traffic was monitored for a period of one week at two Inner Ring Road locations in April 2016 and at seven sites around the city in June 2016. The vehicle registration data was then sent to the Department for Transport (Dft), who combined it with their vehicle type data, replacing the registration number with an anonymised ‘Unique ID’. The data is provided in three folders:- * Raw Data – contains the data in the format it was received, and a sample of each format. * Processed Data – the data after processing by LCC, lookup tables, and sample data. * Outputs – Excel spreadsheets summarising the data for each site,  for various time/dates. Initially a dataset was received for the Inner Ring Road (see file “IRR ANPR matched to DFT vehicle type list.csv”), with vehicle details, but with missing / uncertain data on the vehicles emissions Eurostandard class. Of the 820,809 recorded journeys,  from the pseudo registration number field (UniqueID) it was determined that there were 229,891 unique vehicles, and 31,912 unique “vehicle types” based on the unique concatenated vehicle description fields. It was therefore decided to import the data into an MS Access database, create a table of vehicle types, and to add the necessary fields/data so that combined with the year of manufacture / vehicle registration, the appropriate Eurostandard could be determined for the particular vehicle. The criteria for the Eurostandards was derived mainly from www.dieselnet.com  and summarised in a spreadsheet (“EuroStandards.xlsx”).  Vehicle types were assigned to a “VehicleClass” (see “Lookup Tables.xlsx”) and “EU class” with additional fields being added for any modified data (Gross Vehicle Weight – “GVM\_Mod”; Engine capacity – “EngineCC\_mod”; No of passenger seats  –  “PassSeats”; and Kerb weight – “KerbWt”). Missing data was added from the internet lookups, extrapolation from known data, and by association – eg 99% of cars with an engine size Additional data was then received from the Inner Ring Road site, giving journey date/time and incorporating the Taxi data for licensed taxis in Leeds. Similar data for Sites 1-7 was also then received, and processed to determine the “VehicleClass” and “EU class”. A mixture of Update queries, and VBA processing was then used to provide the Level 1-6 breakdown of vehicle types (see “Lookup Tables.xlsx”). The data was then combined into one database, so that the required Excel spreadsheets could be exported for the required time/date periods (see “outputs” folder).
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks