<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>
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.