Historical Data Versioning
<p>We have added a new field to most historical data API's to indicate revision versions. </p><p>"revision_version"</p><p>To ensure our service always returns the best possible data for every location - on rare occasions - it is necessary to make changes to either calculated fields, or the underlying data (even when in a "final" state). In this case the "revision_version" field will indicate an updated version number. </p><p>revision_version: "MAJOR_VERSION.MINOR_VERSION" - Example: "1.0"</p><p>The minor version will update when:</p><ul><li>Improvements have been made to calculations of derived fields. </li><li>Bug fixes or minor improvements have been made that may only impact specific locations or time frames.</li></ul><p>The major version will update when:</p><ul><li>There are new historical dataset(s) added. </li><li>Major updates to station/data source selection have been made. </li><li>Changes or fixes have been made that impact all data returned by the API.</li></ul><p>As a general practice we recommend querying again for past data to obtain these revisions using both "revision_status" field, AND "revision_version" to determine whether or not to replace data in any locally hosted database. </p><p>More information on this can be found on the following page: https://help.weatherbit.io/why-does-the-historical-data-change/</p><h3 id="historical-revision-version-api">Historical Revision Version API</h3><p>To make it easier to detect when a major or minor data revision has occurred, we have added an API that returns this version. As such there is no need to query a historical API directly. </p><p>https://api.weatherbit.io/v2.0/history/revision_version?key=YOUR_API_KEY </p>{
"revision_version": "1.0"
}</pre><figcaption><p>This new API returns a simple JSON response with the current revision version</p></figcaption>