Customer Meter Data

Open data API in a single place

Provided by Calderdale Metropolitan Borough Council

Get early access to Customer Meter Data API!

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

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
Quality scoring

Dataset description

<p style="box-sizing: border-box; margin: 0px 0px 10px; color: #333333; font-family: Roboto, sans-serif; font-size: 16px; line-height: 22.8571px;">This dataset comprises of Yorkshire Water Customer Meter data both actual and estimated readings for domestic properties in the Yorkshire Water operational area.</p> <p style="box-sizing: border-box; margin: 0px 0px 10px; color: #333333; font-family: Roboto, sans-serif; font-size: 16px; line-height: 22.8571px;">The dataset has been anonymised to remove personal data and make it Data Protection Act compliant. There is 5 years worth of data for 2010 - 2015. </p> <h2 style="box-sizing: border-box; font-family: Roboto, sans-serif; font-weight: 400; line-height: 1.1; margin-top: 20px; margin-bottom: 10px; font-size: 1.57143rem;">Dataset guidance</h2> <ul style="box-sizing: border-box; margin-top: 0px; margin-bottom: 10px; padding: 0px 0px 0px 1em; margin-left: 0px; color: #333333; font-family: Roboto, sans-serif; font-size: 16px; line-height: 22.8571px;"> <li style="box-sizing: border-box; margin-left: 20px;">POSTAL_TOWN - Name of postal town (e.g. Bradford).</li> <li style="box-sizing: border-box; margin-left: 20px;">POSTCODE_OUTCODE - First part of post code (e.g. BD10).</li> <li style="box-sizing: border-box; margin-left: 20px;">PROPERTY_CLASS - "House" measured by Ratable Value (RV) or "All New Domestic Property"</li> <li style="box-sizing: border-box; margin-left: 20px;">METER_KEY - Common reference to link meter readings together over time.</li> <li style="box-sizing: border-box; margin-left: 20px;">READING_START_DATE - Start of metered period.</li> <li style="box-sizing: border-box; margin-left: 20px;">READING_END_DATE - End of metered period.</li> <li style="box-sizing: border-box; margin-left: 20px;">READING_START_READING - Start reading at start of metered period.</li> <li style="box-sizing: border-box; margin-left: 20px;">READING_END_READING - End reading at end of metered period.</li> <li style="box-sizing: border-box; margin-left: 20px;">GROSS_COMSUMPTION - (READING_END_READING)-(READING_START_READING).  One unit = 1m3 (1000 litres)</li> <li style="box-sizing: border-box; margin-left: 20px;">DAILY_AVERAGE_CONSUMPTION - GROSS_CONSUMPTION/(READING_END_DATE-READING_START_DATE)</li> <li style="box-sizing: border-box; margin-left: 20px;">READING_SOURCE - Source of meter reading (customer, YW meter reader etc)</li> <li style="box-sizing: border-box; margin-left: 20px;">CUSTOMER_TYPE - determines who is responsible for paying the bill - the occupier (space) or the landlord (A or L). Where this is an I, it means that the meter reading isn't being used to create the bill - these are what are called 'check meters' and exist on domestic properties so we still read them, and are valid water use readings, but the customer has reverted to being billed using rateable value. This usually happens when they request a meter on the basis that they think it will be cheaper, but then find it isn't so are allowed to revert back.</li> <li style="box-sizing: border-box; margin-left: 20px;">BILLPAYER_AGE - is the average age of the billpayers in the household where their dates of birth are known. For some, we don't know their dates of birth. For those households where there are multiple bill payers (Mr & Mrs usually, or students), then it is the average age. (As of June 2015 for that Meter Key.  Will not be true for previous years).  This has been further anonymised into age ranges in case people can be identified.</li> <li style="box-sizing: border-box; margin-left: 20px;">CURRENT_OCCUPANCY_AGE - Time current occupier has been at property (As of June 2015 for that Meter Key.  Will not be true for previous years)</li> </ul>
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