Open Data Change Log

Coming Soon

Notification of scheduled breaking changes will be displayed in this section.

------

Register to receive advanced notice of breaking changes and alerts to updates

To receive email notifications relating to data and website enhancements, including advanced notice of schema changes, please register with the Active Places Power website (via the homepage).  

------------

Purpose July 2021

This is a notification to users of Active Places open data regarding changes that may impact use of the data, in particular where scripted or automated processes have been established. 

 

 Summary of the Changes

Changes to Site and Facilities are being introduced in order to enhance how data is represented. Details of these are outlined in the section below.

When these changes are implemented, anything that depends on previous values will no longer function. Please ensure you are ready to switch to the new changes based on the dates outlined under the “Timeline” section of this notification.

 

Explanation of the Changes

 

  1. 1. Rename existing Facility Type of ‘Athletic Tracks’

The existing Facility Type of “Athletic Tracks” to be renamed to ‘Athletics’ in all places and the ID of 1 will remain the same .

This will result in the following open data changes:

Item

CSV Download

JSON Download / API

SQL DB Export

Rename existing Facility Type of ‘Athletic Tracks’

 

'Athletic Tracks.csv' file to be renamed to 'Athletics.csv'

No change

No Chang

  1. 2. Remove the existing ‘Athletics’ Facility sub types

The Facility Sub Types of ‘Synthetic’, ‘Cinder’ and ‘Permanent Grass’ have been removed. 

There are no open data structure changes.

  

  1. 3. New ‘Athletics’ Facility Sub types

The following Facility Sub Types have been added: -

                  Name = ‘Compact Outdoor’; ID = 1006

                  Name = ‘Indoor Training’; ID = 1009

                  Name = ‘Mini Outdoor’; ID = 1005

                  Name = ‘Standalone Field’; ID = 1007

                  Name = ‘Standalone Oval Indoor’; ID = 1008

                  Name = ‘Standard Oval Outdoor’; ID = 1004

There are no open data structure changes.

 

  1. 4. Remove existing Facility Specifics for ‘Athletics’

The removal of Facility Specifics ‘Floodlit’ and ‘Lanes from the Facility Specifics area.

This will result in the following open data changes:

Item

CSV Download

JSON Download / API

SQL DB Export

Removal of the field of "Floodlit"

The column ‘Floodlit’ will be removed from “Athletics.csv”.

Removal of attribute “Floodlit’ from the JSON open data file - "FacilitySpecifics" section.

The removal of attribute "Floodlit" from the “dbo._FacilitySpecifics” table.

Removal of the field of "Lanes"

The column ‘Lanes will be removed from “Athletics.csv”.

Removal of attribute “Lanes from the JSON open data file - "FacilitySpecifics" section.

The removal of attribute "Lanes" from the “dbo._FacilitySpecifics” table.

 

 

  1. 5. New ‘Athletics’ Facility Specifics

New Facility Specifics have been added to each of the new Facility Sub types detailed in the table below.  For JSON file they will only be there if they are relevant to that sub type.

This will result in the following open data changes:

 

Item

CSV Download

JSON Download / API

SQL DB Export

Additional of the new field of "Discus Throw facility"

A new column will be added to “Athletics.csv” after "Facility ID".  The column is to have the heading of "Discus Throw facility" with value displayed as a 1, 0 or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Discus Throw facility". This field will be added to the "FacilitySpecifics" section with a true or false value.

The additional attribute of "Discus Throw facility" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Floodlit"

A new column will be added to “Athletics.csv” after "Discus Throw facility".  The column is to have the heading of "Floodlit" with value displayed as a 1, 0 or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Floodlit". This field will be added to the "FacilitySpecifics" section with a true or false value.

The additional attribute of "Floodlit" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Hammer Throw facility"

A new column will be added to “Athletics.csv” after "Floodlit".  The column is to have the heading of "Hammer Throw facility" with value displayed as a 1, 0 or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Hammer Throw facility". This field will be added to the "FacilitySpecifics" section with a true or false value.

The additional attribute of "Hammer Throw facility" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "High Jump facility"

A new column will be added to “Athletics.csv” after "Hammer Throw facility".  The column is to have the heading of "High Jump facility" with value displayed as a 1, 0 or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "High Jump facility". This field will be added to the "FacilitySpecifics" section with a true or false value.

The additional attribute of "High Jump facility" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Indoor Throws net for Javelin"

A new column will be added to “Athletics.csv” after "High Jump facility".  The column is to have the heading of "Indoor Throws net for Javelin" with value displayed as a 1, 0 or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Indoor Throws net for Javelin". This field will be added to the "FacilitySpecifics" section with a true or false value.

The additional attribute of "Indoor Throws net for Javelin" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Indoor Throws training - cage"

A new column will be added to “Athletics.csv” after "Indoor Throws net for Javelin".  The column is to have the heading of "Indoor Throws training - cage" with value displayed as a 1, 0 or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Indoor Throws training - cage". This field will be added to the "FacilitySpecifics" section with a true or false value.

The additional attribute of "Indoor Throws training - cage" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Infield Surface Type"

A new column will be added to “Athletics.csv” after "Indoor Throws training - cage".  The column is to have the heading of "Infield Surface Type" with value displayed as a string or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Infield Surface Type". This field will be added to the "FacilitySpecifics" section with an object value containing the id and name.

The additional attribute of "Infield Surface Type" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Javelin Throw facility"

A new column will be added to “Athletics.csv” after "Infield Surface Type".  The column is to have the heading of "Javelin Throw facility" with value displayed as a 1, 0 or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Javelin Throw facility". This field will be added to the "FacilitySpecifics" section with a true or false value.

The additional attribute of "Javelin Throw facility" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Long Jump facility"

A new column will be added to “Athletics.csv” after "Javelin Throw facility".  The column is to have the heading of "Long Jump facility" with value displayed as a 1, 0 or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Long Jump facility". This field will be added to the "FacilitySpecifics" section with a true or false value.

The additional attribute of "Long Jump facility" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Oval Track Lanes"

A new column will be added to “Athletics.csv” after "Long Jump facility".  The column is to have the heading of "Oval Track Lanes" with value displayed as a number or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Oval Track Lanes". This field will be added to the "FacilitySpecifics" section with a number value.

The additional attribute of "Oval Track Lanes" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Oval Track Length"

A new column will be added to “Athletics.csv” after "Oval Track Lanes".  The column is to have the heading of "Oval Track Length" with value displayed as a number or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Oval Track Length". This field will be added to the "FacilitySpecifics" section with a number value.

The additional attribute of "Oval Track Length" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Pole Vault facility"

A new column will be added to “Athletics.csv” after "Oval Track Length".  The column is to have the heading of "Pole Vault facility" with value displayed as a 1, 0 or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Pole Vault facility". This field will be added to the "FacilitySpecifics" section with a true or false value.

The additional attribute of "Pole Vault facility" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Shot Put facility"

A new column will be added to “Athletics.csv” after "Pole Vault facility".  The column is to have the heading of "Shot Put facility" with value displayed as a 1, 0 or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Shot Put facility". This field will be added to the "FacilitySpecifics" section with a true or false value.

The additional attribute of "Shot Put facility" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Sprint straight Length"

A new column will be added to “Athletics.csv” after "Shot Put facility".  The column is to have the heading of "Sprint straight Length" with value displayed as a number or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Sprint straight Length". This field will be added to the "FacilitySpecifics" section with a number value.

The additional attribute of "Sprint straight Length" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Steeplechase water jump"

A new column will be added to “Athletics.csv” after "Sprint straight Length".  The column is to have the heading of "Steeplechase water jump" with value displayed as a 1, 0 or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Steeplechase water jump". This field will be added to the "FacilitySpecifics" section with a true or false value.

The additional attribute of "Steeplechase water jump" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Straight Track Lanes"

A new column will be added to “Athletics.csv” after "Steeplechase water jump".  The column is to have the heading of "Straight Track Lanes" with value displayed as a number or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Straight Track Lanes". This field will be added to the "FacilitySpecifics" section with a number value.

The additional attribute of "Straight Track Lanes" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Track Lanes"

A new column will be added to “Athletics.csv” after "Straight Track Lanes".  The column is to have the heading of "Track Lanes" with value displayed as a number or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Track Lanes". This field will be added to the "FacilitySpecifics" section with a number value.

The additional attribute of "Track Lanes" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Track length"

A new column will be added to “Athletics.csv” after "Track Lanes".  The column is to have the heading of "Track length" with value displayed as a 1, 0 or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Track length". This field will be added to the "FacilitySpecifics" section with a number value.

The additional attribute of "Track length" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Track Surface Type"

A new column will be added to “Athletics.csv” after "Track length".  The column is to have the heading of "Track Surface Type" with value displayed as a string or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Track Surface Type". This field will be added to the "FacilitySpecifics" section with an object value containing the id and name.

The additional attribute of "Track Surface Type" will be included in the “dbo._FacilitySpecifics” table.

Additional of the new field of "Triple Jump facility"

A new column will be added to “Athletics.csv” after "Track Surface Type".  The column is to have the heading of "Triple Jump facility" with value displayed as a 1, 0 or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Triple Jump facility". This field will be added to the "FacilitySpecifics" section with a true or false value.

The additional attribute of "Triple Jump facility" will be included in the “dbo._FacilitySpecifics” table.

 

 

  1. 6. New ‘Sports Hall’ Facility Specific

A new Facility Specifics has been added called ‘Futsal courts’ to the ‘Sports Hall’ facility type.  For JSON file this new attribute will only be there for ‘Main’ and ‘Barn’.

This will result in the following open data changes:

Item

CSV Download

JSON Download / API

SQL DB Export

Additional of the new field of "Futsal courts"

A new column will be added to “SportsHall.csv” after "Five-a-side Pitches".  The column is to have the heading of "Futsal courts" with value displayed as a number value or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "Futsal courts". This field will be added to the "FacilitySpecifics" section with a number value.

The additional attribute of "Futsal courts" will be included in the “dbo._FacilitySpecifics” table.

 

 Timeline

The changes outlined above are planned to be released to the User Acceptance Testing (UAT) environment on 5th August-2021 to allow for testing of any changes to your processes prior to going live. Please contact Active Places Team (App.Enquiries@sportengland.org) for details on how to access the UAT environment.

The changes are planned to be released to the Live environment on 12th August-2021.

 

---------------

Known Issues

  • If you have any feedback please submit this to us via App.Enquiries@sportengland.org.
  • We will be reviewing feedback comments along with internal data additions on a continuous basis.   
  • Please keep in touch via this page for advance notification of the planned changes.

  

Changes

 The following breaking changes have been released.

July 2021

Summary of the Changes

During implementation of new API functionality, the decision was made to resolve some longstanding issues with the formatting of the JSON and to provide some additional data to reduce the need to consult the Sports Data Model for the meaning of some lookup values.  The following provides a summary of the Open Data JSON Download / API changes, with details of the previously notified approach and a revised version to clarify what is being implemented. This summary only covers differences and where there is no change to what has previously been communicated, then this is not included below.

 

Also included in this change is altering the facility type and sub type name from ‘Health and Fitness Suite’ to ‘Health and Fitness Gym’.

 

  1. 1. Represent Site and Facility categorisation data as an id and name object rather than just a name

 

This is to provide more flexibility when filtering a site or facility based on a characteristic of the site such as the operational status or ownership. This better represents how the data is stored and used within Active Places Power. The currently available values for the id field are listed in the Sports Data Model.

Site or Facility Attribute

Previous

Revised

Site - Management Type

"managementType""Sport Club"

"managementType": {

      "id"5,

      "name""Sport Club"

}

Site - Management Group

"managementGroup""Education"

"managementGroup": {

      "id"1,

      "name""Education"

}

Site - Owner Type

"ownerType""Academies"

"ownerType": {

      "id"16,

      "name""Academies"

}

Site - Owner Group

"ownerGroup""Education"

"ownerGroup": {

      "id"2,

      "name""Education"

}

Site - Education Phase

"educationPhase""Primary"

"educationPhase": {

      "id"3,

      "name""Primary"

}

Site Comment - Category and SubCategory

"comments": [{

"category""Community Use",

"subCategory""Community Use Agreement”

}]

"comments": [{

      "category": {

            "id"3,

            "name""Community Use"

      },

      "subCategory": {

            "id"8,

            "name""Community Use Agreement"

      }

}]

Site – Closure Code and Reason

"closureCode"999,

"closureReason""Unclassified"

"closureReason": {

      "id": 999,

      "name""Unclassified"

}

Site Contacts - Contact Type

"contacts": [{

      "contactType""Enquiries"

}]

"contacts": [{

      "contactType": {

            "id": 1,

            "name""Enquiries"

      }

}]

Facilities – Facility Type

"facilityType""Grass Pitches"

"facilityType": {

      "id": 5,

      "name""Grass Pitches"

}

Facilities – Facility SubType

"facilitySubType""Mini Soccer 5v5"

"facilitySubType": {

      "id": 5023,

      "name""Mini Soccer 5v5"

}

Facilities – Accessibility

"accessibility""Private Use"

"accessibility": {

      "id": 5,

      "name""Private Use"

}

Facilities – Status

"status""Operational"

"status": {

      "id": 3,

      "name""Operational"

}

Facilities - Management Type

"managementType""Sport Club"

"managementType": {

      "id"5,

      "name""Sport Club"

}

Facilities - Management Group

"managementGroup""Education"

"managementGroup": {

      "id"1,

      "name""Education"

}

Facilities – Accessibility Group

"accessibilityGroup""Private"

"accessibilityGroup": {

      "id": 2,

      "name""Private"

}

Facilities – Timings Type

"timingsType""Dawn to Dusk"

"timingsType": {

      "id"1,

      "name""Dawn to Dusk"

}

Facilities Comment - Category and SubCategory

"comments": [{

"category""Community Use",

"subCategory""Community Use Agreement”

}]

"comments": [{

      "category": {

            "id"3,

            "name""Community Use"

      },

      "subCategory": {

            "id"8,

            "name""Community Use Agreement"

      }

}]

Facilities – Closure Code and Reason

"closureCode"999,

"closureReason""Unclassified"

"closureReason": {

      "id": 999,

      "name""Unclassified"

}

Facility Opening Times - Access

"openingTimes": [{

"accessDescription""Pay and Play"

}]

"openingTimes": [{

      "accessDescription": {

            "id": 2,

            "name""Pay and Play"

      }

}]

Facility Opening Times – Period

"openingTimes": [{

      "periodOpenFor""Monday-Friday"

}]

"openingTimes": [{

      "periodOpenFor": {

            "id": 11,

            "name""Monday-Friday"

      }

}]

  

  1. 2. Store Facility Specifics in the correct format depending on their type

 

The facilitySpecifics section of the JSON currently stores data as strings rather than the correct data type. This means that the text “1” sometimes means 1 and sometimes means true depending on the type of information being stored. This makes the Json very difficult to parse into the correct format and could be considered to be invalid Json by some software tools. The facility specifics are now stored in the correct format according to the type of data they hold.

Site or Facility Attribute

Previous Examples

Revised

Facility Specifics with the values true or false

"floodlit""0"

"hybrid""1"

"floodlit"false

"hybrid"true

Facility Specifics with a numeric value

"pitches""1"

"length""12.5"

"pitches"1

"length"12.5

Facility Specifics with a single value based on a list of possible values

"surfaceType""Concrete"

 

"surfaceType": {

      "id": 4,

      "name""Concrete"

}

Facility Specifics with multiple values based on a list of possible values

"overmarkedSports""1,2,3"

"overmarkedSports": [{

      "id"1,

      "name""Tennis"

}, {

      "id"2,

      "name""Football"

}, {

      "id"3,

      "name""Basketball"

}]

Facility Specifics with a date value are not changing but are included here for completeness

"wR22Pitch:NextTestDue""2022-02-23"

"wR22Pitch:NextTestDue""2022-02-23"

 

  1. 3. Store all numerical values as numbers instead of strings

 

Some of the numerical values throughout the Json have been stored as strings instead of numbers. This has now been corrected.

Site or Facility Attribute

Previous

Revised

Site UPRN

"uprn""100051982475"

"uprn"100051982475

Site Equipment entries

"tableTennisTables": "4"

"tableTennisTables": 4

Site Activities

"activities": [{

      "id""11",

      "name""Badminton"

}]

"activities": [{

      "id"11,

      "name""Badminton"

}]

 

  1. 4. Move Changing Places Toilets data into the Disability section and correct its value

 

The changingPlacesToiletsExists field holds data on whether the site and/or facility has “Changing Places” toilets available for patrons. This is accessibility data so has been moved into the disability section along with the other accessibility entries. It has also had it’s value corrected from a number to a Boolean with a null entry if not known. This is for consistency with other accessibility entries.

Site or Facility Attribute

Previous

Revised

Site Changing Places Toilets

"changingPlacesToiletsExist""0"

"disability": {

      "changingPlacesToiletsExist"false

}

Facilities Changing Places Toilets

"changingPlacesToiletsExist""0"

"disability": {

      "changingPlacesToiletsExist"false

}

 

  1. 5. Rename of Facility type and sub type

 

The existing facility type and sub type of ‘Health and Fitness Suite’ is renamed to ‘Health and Fitness Gym’.

The table below outlines the impact of this to open data files:

CSV Download

JSON Download / API

SQL DB Export

The existing file “HealthandFitnessSuite” is renamed to “HealthandFitnessGym” open data CSV file.

No change

No change

 

-----------

December 2020

Changes to Site and Facilities have been introduced in order to enhance how data is represented. Details of these changes are outlined in the section below.

 

Following the release on Thursday 3rd December 2020, anything that depends on previous values will no longer function. 

 

Explanation of the Changes

  1. Including “Management Type” in the OpenData files

The existing field of “Management Type” to be included in the CSV download area. 

This will result in the following open data changes:

CSV Download

JSON Download / API

SQL DB Export

New columns will be added to “Sites.csv” after “OwnerOrgName”.  The columns will have the headings of: -

- “MgtTypeID”: an enumerated value of the Management Type ID

- “MgtType”: description for the ID.

No change

No change

 

  1. Addition of “Operator Name” field

A new field of “Operator Name” is being introduced to be able to identify the Operator of a Site and also at the Facility level. 

This will result in the following open data changes:

CSV Download

JSON Download / API

SQL DB Export

A new column will be added to “Sites.csv” after “MgtType”.  The column is to have the heading of “OperatorName” with value displayed as a string.

A new column will be added at the end of the "FacilityManagement.csv" file.  The column is to have the heading of "OperatorName” with value as a string

Additional attributes will be included in the JSON open data file to represent the field of "OperatorName". This field will be added to the "Site" section and "Facilities" section with a value of a string.

The additional column of “OperatorName” will be included in the “dbo._Facilities” table and “dbo._Sites” table.

 

  1. New “Operational Status”

A new Operational Status is being introduced called “Temporarily Closed COVID”.

There are no open data structure changes.

 

  1. Addition of “Expected Opening” field

A new field of “Expected Opening” is being introduced to be able to identify when a Facility is expected to reopen if the Operation Status is “Under Construction”, “Temporarily Closed” or “Temporarily Closed COVID”. 

This will result in the following open data changes:

CSV Download

JSON Download / API

SQL DB Export

A new column will be added to “Facilities.csv” after “FacStatusFlag”.  The column is to have the heading of “ExpectedOpening” with value displayed as a date or an empty field.

Additional attribute will be included in the JSON open data file to represent the field of "ExpectedOpening". This field will be added to the "Facilities" section with a value of a date or an empty field.

The additional column of “ExpectedOpening” will be included in the “dbo._Facilities” table.

----------

October 2020

Enhancements made to the way that geospatial data is stored and used within Active Places and to naming standards of Areas of Interests to follow Ordnance Survey conventions across all of Active Places.  The changes to structure mean that there will be changes to two tables included in the database export files.  

Following the release, anything that depends on previous values will no longer function. 

Explanation of the Changes

1.      Database Id changes to _Areas and _Addresses tables

There will be the following changes to database tables:

a)     _Addresses will no longer contain the “Area_Id” foreign key column

b)     _Areas will no longer contain the “Id” primary key column

c)      _Areas will have a new column “AddressId” which will be unique and will be the new link to the _Addresses table

As a result of this change, the _Areas table will only contain a row if there is a corresponding address that exists within the specific Area of Interest.

To link an Address to an Area, a join can be done on _Addresses.ID = _Areas.AddressId

Note: The _Areas.AddressId column will not be set as a primary key so it is recommended to set it before using the data, as this will improve performance.

Example - To identify the Areas information for Site Id 1206727:

·        Currently

o   The Address Id would need to be located in _Addresses table (21085) and then the Area Id located in the _Areas table (156897)

·        After change

o   The Address Id would need to be located in the Addresses table (21085) and this used to join on the AddressId in the _Areas table

2.      Changes to Area of Interest naming convention

Following the change, all Area of Interest names within the _Areas database table (and across all Active Places functionality) will follow the Ordnance Survey naming conventions. To note that these names are already used for map search functionality on Active Places Power.

Examples of the changes to names include:

 

AOI Type

Difference

Example before change

Example after change

Parliamentary Constituency

Suffixed with “Co Const” or “Boro Const”

Bournemouth East

Bournemouth East Boro Const

Ward

Suffixed with “Ward”

Shepton West

Shepton West Ward

Local Authority

Suffixed with “District” and sometimes with “(B)”

Eastbourne District

Eastbourne District (B)

County

Suffixed with “County”

Northamptonshire

Northamptonshire County

Region

Suffixed with “Euro Region”

East Midlands

East Midlands Euro Region

 

----------

July 2020

Changes to “Grass Pitches” and “Artificial Grass Pitch” facility types have been introduced on Thursday 16th July 2020.  In addition, a deprecated field has also been removed from the “Contacts” and “Facilities” database tables. Details of these are outlined in the section below.

Following the release on Thursday 16th July 2020, anything that depends on previous values will no longer function. 

    • Addition of “Hybrid” Facility Specific for Facility Type “Grass Pitches”

    The facility specific data collected for Grass Pitches facilities has been enhanced to indicate if the facility pitches are "Hybrid". The supported values are  “Yes” (Id 1) or “No” (Id 0).

    The table below outlines the impact of this to open data files:

    CSV Download

    JSON Download / API

    SQL DB Export

    The column "Hybrid" added to the right of "Floodlit" on the "GrassPitches" open data CSV file.

    The attribute "Hybrid" included within the "facilitySpecifics" of a Grass Pitch facility in the JSON open data.

    Note: the addition of the attribute will not be published in incremental files, so users would need to reinitialise to obtain the attribute.

    The table “dbo._FacilitySpecifics” includes an additional row for Grass Pitch facilities to represent the “Hybrid” attribute.

    • Changes to Facility Type “Artificial Grass Pitch” Sub Type "Rubber crumb pile (3G)"

    The name of the sub type has changed from "Rubber crumb pile (3G)" to "Long Pile Carpet".  There are also corresponding changes to the facility sub type description. The facility specific data for the facility sub type has been enhanced with the attribute of “Fill” to indicate the type of fill in use. The supported values for this attribute are: "None" (Id 0), "Yes - Rubber" (Id 1), "Yes - Other organic" (Id 2), or "Yes - Not known" (Id 3).

    The table below outlines the impact of this to open data files:

    CSV Download

    JSON Download / API

    SQL DB Export

    The column "Fill" added to the right of "Dimensions estimate" on the "ArtificialGrassPitch" open data CSV file.

    The attribute "Fill" included within the "facilitySpecifics" of a “Long Pile Carpet” facility in the JSON open data.

    Note: the addition of the attribute will not be published in incremental files, so users would need to reinitialise to obtain the attribute.

    The table “dbo._FacilitySpecifics” includes an additional row for “Long Pile Carpet” facilities to represent the "Fill" attribute.

    • Addition of "WR22 Compliant Pitch" and "WR22 Pitch: Next Test Due" Facility Specifics for Facility Type “Artificial Grass Pitch”

    The facility specific data collected for Artificial Grass Pitch facilities has been enhanced to indicate if the facility has a "WR22 Compliant Pitch" and, if so, to also collect "WR22 Pitch: Next Test Due". For the attribute of "WR22 Compliant Pitch" the supported values are Yes" (Id 1), "No" (Id 0) or "Don't know" (Id 2). Where provided, the attribute "WR22 Pitch: Next Test Due" will represent a date.

    The table below outlines the impact of this to open data files:

    CSV Download

    JSON Download / API

    SQL DB Export

    Columns added to the right of "Width" on the "ArtificialGrassPitch" open data CSV file of "WR22 Compliant Pitch" and "WR22 Pitch: Next Test Due".

    The attributes "WR22 Compliant Pitch" and "WR22 Pitch: Next Test Due" included within the "facilitySpecifics" of an Artifical Grass Pitch facility in the JSON open data.

    Note: the addition of the attributes will not be published in incremental files, so users would need to reinitialise to obtain the attributes.

    The table “dbo._FacilitySpecifics” includes additional rows for Artificial Grass Pitch facilities to represent the "WR22 Compliant Pitch" and "WR22 Pitch: Next Test Due" attributes.

    • Removal of “UpdatedOn” and “UpdatedBy” from “Contacts” and “Facilities”

    The attributes of “UpdatedOn” and “UpdatedBy” for “Contacts” and “Facilities” database tables have been superseded by the attributes of “CheckedOn” and “CheckedBy”, so they have been removed.

    CSV Download

    JSON Download / API

    SQL DB Export

    The column “UpdatedOn”  removed from the "Contacts" open data CSV file.

    No impact.

    The columns “UpdatedOn” and “UpdatedBy” and their associated data values have been removed from the database tables "dbo._Contacts" and “dbo._Facilities”.

     

    ----------

    June 2020

    Changes to the “Mini Rugby” Facility Sub Type have been introduced.  

    Following release on 18th June 2020, anything that depends on previous values will no longer function.  See below for details.  

     

    1. Changes to Mini Rugby Facility Sub Type

    The Facility Sub Type of "Mini Rugby" for the Facility Type of "Grass Pitches" is been re-categorised as two Facility Sub Type for "Mini Rugby Union" or "Mini Rugby League".

    The existing Facility Sub Type of “Mini Rugby” (Facility Sub Type Id 5021) has been renamed to “Mini Rugby Union” and a new Facility Sub Type of "Mini Rugby League" (Facility Sub Type Id 5024) has been created.   

    Facility Sub Type Id

    Facility Sub Type Name

    Facility Sub Type Description

    5021

    Mini Rugby Union

    RFU recommended dimensions pitch including in-goal:  (U7) 30m x 12m (36m x 18m with 3m run offs)
    (U8) 55m x 25m (61m x 31m with 3m run offs)
    (U9) 70m x 35m (76m x 41m with 3m run offs)
    (U10) 70m x 35m (80m x 45m with 5m run offs)
    (U11 & U12) 70m x 43m ( 80m x 53m with 5m run offs)

    RFU recommended dimensions: 
    (U7,U8,U9) 60m x40m (64m x 44m with 2m run offs
    (U10&U11) 80m x50m(84mx54m with 2m run offs)

    Reference: Sport England Comparative Sizes of Sports Pitches & Courts (OUTDOOR)-September 2015 Update.

    5024

    Mini Rugby League

    RFL recommended dimensions: 
    (U7,U8,U9) 60m x40m (64m x 44m with 2m run offs)
    (U10&U11) 80m x50m(84mx54m with 2m run offs)

    Reference: Sport England Comparative Sizes of Sports Pitches & Courts (OUTDOOR)-September 2015 Update

     

    Existing data has been audited and updated to reflect the appropriate Facility Sub Type. In some cases, where a current Facility represents Mini Rugby Union pitches, the existing facility has been updated to reflect the Mini Rugby Union details and a new facility created to represent the Mini Rugby League data.

    The updated data will be available through existing open data attributes (i.e. no breaking changes), but to note that the changes will not be published in incremental JSON files, so users would need to reinitialise with the full JSON download to update records.

    ----------

    May 2020

    Changes to the “Mini Soccer” Facility Sub Type have been introduced and the site level attribute of “Dedicated Football Facility” has been removed.  Out of date files in the CSV open data download have also been removed. 

    Following release on 21st May 2020, anything that depends on previous values will no longer function.  See below for details.  

    1. Removal of “Dedicated Football Facility” flag

    The site level attribute of “Dedicated Football Facility” and existing associated data has been removed, as this has been superseded by the “Small AGP” flag associated with the Facility Type of Artificial Grass Pitches. 

    CSV Download

    JSON Download / API

    SQL DB Export

    The column "DedicatedFootballFlag" will be removed from the “Sites.csv” file.

    The attribute "dedicatedFootballFacility" has been removed from the JSON open data.

    Note: the attribute removal will not be published in incremental files, so users need to reinitialise to remove the attribute.

    The column "DedicatedFootballFacilityFlag" and its associated data values has been removed from the database table "dbo._Sites"

     

    1. Changes to Mini Soccer Facility Sub Type

    The Facility Sub Type of "Mini Soccer" for the Facility Type of "Grass Pitches" is been re-categorised as two Facility Sub Type for "Mini Soccer 7v7" or "Mini Soccer 5v5".

    The existing Facility Sub Type of “Mini Soccer” (Facility Sub Type Id 5020) is being renamed to “Mini Soccer 7v7” and a new Facility Sub Type (Facility Sub Type Id 5023) is being created for “Mini Soccer 5v5”. 

    Facility Sub Type Id

    Facility Sub Type Name

    Facility Sub Type Description

    5020

    Mini Soccer 7v7

    FA recommended dimensions (U9 &U10):  55m x 37m (61m x 43m with 3m run offs).

    Reference: Sport England Comparative Sizes of Sports Pitches & Courts (OUTDOOR)-September 2015 Update.

    5023

    Mini Soccer 5v5

    FA recommended dimensions (U7 &U8): 37m x 27m (43m x 33m with 3m run offs).

    Reference: Sport England Comparative Sizes of Sports Pitches & Courts (OUTDOOR)-September 2015 Update.

     

    Existing data has been updated to reflect the appropriate Facility Sub Type. In some cases, where a current Facility represents Mini Soccer 7v7 and 5v5 pitches, the existing facility will be updated to reflect the Mini Soccer 7v7 details and a new facility created to represent the Mini Soccer 5v5 data.

    The updated data will be available through existing open data attributes (i.e. no breaking changes), but to note that the changes will not be published in incremental JSON files, so users would need to reinitialise with the full JSON download to update records.

    1. Removal of files in CSV open data download

    The following files have been removed from the CSV open data download as they are out of date:

    a) OpenDataColumnMapper.xlsx

    b) OpenDataCsvRelationships.pdf

    ----------

    April 2020

    Changes to Facility Type and Facility Type Specifics attributes introduced in order to enhance how data is represented. When these changes are implemented, anything that depends on previous values will no longer function.  

    1. Addition of “Meets Active Places Criteria” flag

    The new flag of “Meets Active Places Criteria” is being introduced to be able to identify Facilities with outlying values. This replaces the "Operational Status" option of “Does not appear to meet Active Places criteria” and results in the following open data changes:

    Item

    CSV Download

    JSON Download / API

    SQL DB Export

    Representation of the new field of "Meets Active Places Criteria" and exception criteria

    A new column added at the end of the "Facilities.csv" file. The column has the heading of "MeetsAPCriteria” with value displayed as Boolean (i.e. 1=Yes)

    A new file as part of the daily open data CSV zip file generation called "FacilityCriteriaExceptions.csv"  with the following columns with a row per exception reason:

    1. FacilityId: Id of the Facility
    2. FacilitySpecificHeader: Name of field which does not meet criteria
    3. FacilitySpecificValue: Value that does not meet criteria

    ExceptionReason: Reason why it does not meet criteria

    Additional attributes included in the JSON open data file representing fields of "Meets Active Places Criteria" and "Active Places Criteria Exceptions". These are added after the "facilitySpecifics" section as "meetsActivePlacesCriteria" with a value of "true" or "false" and "criteriaExceptions" with a list of "Name" and "Reason" per exception.

    The additional attribute of “MeetsAPCriteria” included in the “dbo._Facilities” table to represent the field of "Meets Active Places Criteria.”

    An additional table included in the DB export of “dbo._FacilityCriteriaExceptions”. This includes the columns:

    1. Id: Unique id
    2. FacilityId: Id of the Facility
    3. FacilitySpecificHeader: Name of field which does not meet criteria
    4. FacilitySpecificValue: Value that does not meet criteria

    ExceptionReason: Reason why it does not meet criteria

    Deprecation of Facility status of “Does not appear to meet Active Places criteria”

    Data changes in the “FacStatusFlag” column of the “Facilities.csv” file. The value “6” is no longer supported and is replaced with a different value from within the existing schema.

    Data changes in the “Status” attribute. The value “Does not appear to meet Active Places criteria” is no longer supported and is  replaced with a different value from within the existing schema.

    Data changes in the “FacilityStatus” column of the “dbo._Facilities” table. The value “Does not appear to meet Active Places criteria” is no longer supported and is replaced with a different value from within the existing schema.

     

    1. Changes to Facility Type “Ice Rinks”

    The Facility Type Specific of "Rinks" is removed as an attribute for Facility Type "Ice Rinks" (Facility Type Id 10), Facility Sub Type "Ice Rinks" (Facility SubType Id 10001). This is because the number of rinks is always expected to be one, so does not require a specific attribute.

    This will result in the following open data changes:

    CSV Download

    JSON Download / API

    SQL DB Export

    The column “Rinks” is removed from “IceRinks.csv” file

    The "facilitySpecifics" item of “rinks” is no longer provided

    A row for “Rinks” is no longer provided in the “dbo._FacilitySpecifics” table

     

    1. Changes to Facility Type “Tennis Courts”

    The Facility Type “Tennis Courts” (Facility Type Id 17) is renamed to “Outdoor Tennis Courts” and the Facility Type Specifics of “Overmarked” and “Overmarked Sports” are added in order to provide additional facility information. The supported look up attribute values for “Overmarked Sports” are included on the “Lookups” tab in an updated version of the Sports Data Model.

    This will result in the following open data changes:

    Item

    CSV Download

    JSON Download / API

    SQL DB Export

    Change of name to “Outdoor Tennis Courts”

    The file “TennisCourts.csv” is renamed to “OutdoorTennisCourts.csv”

    The “facilityType” value of “Tennis Courts” is changed to “Outdoor Tennis Courts”

    The “Name” column value for Id “17” in the table “dbo.FacilityTypes” is  updated

    Addition of Facility Type Specifics of “Overmarked” and “Overmarked Sports”

    The file “OutdoorTennisCourts.csv” has columns added at the end of the file of:

    1. "Overmarked" with Boolean value to indicate “Yes” or “No”
    2.  "Overmarked Sports" with comma separated list of look up ID values. If "Overmarked"=0, then will have value of "n/a"

    Example to illustrate:

    FacilityID, Courts, Floodlit, Surface Type, Overmarked, Overmarked Sports

    4099970,6,1,4,1,"1,3"

    The Facility Type specifics attributes of “overmarked” and “overmarkedSports” are included as the final items within the "facilitySpecifics" of an Outdoor Tennis Court facility.

    The “overmarked” attribute is denoted by “1” and “0” (rather than “true” and “false”) to be consistent with other boolean “facilitySpecifics” attributes.

     The “overmarkedSports” attribute is presented as a textual string, not as an array to be consistent with other Facility Specific attributes.

    The table “dbo._FacilitySpecifics” includes additional rows to represent the additional fields

     

    Below is an example snippet that illustrates the revised structure described above:

    "openingTimes": [],

    "facilitySpecifics": {

                    "courts": "5",

                    "floodlit": "0",

                    "overmarked": "1",

                    "overmarkedSports": "1,2,3",

                    "surfaceType": "Acrylic"

    },

    "meetsActivePlacesCriteria": false,

    "facilityCriteriaExceptions": [{

                                    "name": "Width",

                                    "reason": "Width Value should be between 3 and 30"

                    }, {

                                    "name": "Length",

                                    "reason": "Length Value should be between 4 and 50"

                    }

    ],

    "disability": {

     

    1. Facility Type Specific “Dimensions Estimate”

    The Facility Type Specific attribute value of “Area” is automatically calculated based on multiplying length and width values.  Associated to this change, the “Area Estimate” flag is renamed to “Dimensions Estimate” for the Facilities where this attribute is currently supported, and additional Facilities introduce the “Dimensions Estimate” flag.

    This results in the following open data changes:

    CSV Download

    JSON Download / API

    SQL DB Export

    The column header of “Area Estimate” is renamed to “Dimensions Estimate” in the following CSV files:

    1. SportsHall.csv
    2. Studio.csv

     The column header of “Dimensions Estimate” is added after the “Area” column in the following CSV files:

    1. IndoorBowls.csv
    2. SwimmingPool.csv
    3. ArtificalGrassPitch.csv
    4. IceRinks.csv

     

    The "facilitySpecifics" attribute of “areaEstimate” is renamed to “dimensionsEstimate”

    The table “dbo._FacilitySpecifics” no longer has any rows with “Name” value of “Area estimate”. Going forward the table will include rows with “Name” value of “Dimensions estimate”. 

     

    ----------

    February 2020

    • Active Places sport facility data can now be shared via simple links.  A shareable link can be generated within Active Places Power when viewing a sport facility details page using the new “Share” button.
    • The standard URL structure of https://www.activeplacespower.com/opendata/sites/ only requires the Site ID to be appended.  For example the direct link to K2 Crawley is https://www.activeplacespower.com/opendata/sites/1206727
    • There is no requirement to be logged in to Active Places Power to access the URL.  This means a local store of Active Places data can be enriched with a link to live Active Places information.

     

    ----------

    October 2019

    • ‘County Sport Partnerships’ (CSPs) have been rebranded to ‘Active Partnerships’ and the Active Places Power platform is being updated to reflect this. All existing references to ‘County Sport Partnership’ or ‘CSP’ will be changed to ‘Active Partnership’. (More information about Active Partnerships is available at: https://www.activepartnerships.org/about-us.)  Change details:
    1. Open Data – CSV Download

    In the file “Geographic.csv”, the following column headings will change:

    File

    Column Heading Before Change

    Column Heading After Change

    Geographic.csv

    CSP Code

    Active Partnership Code

    Geographic.csv

    CSP Name

    Active Partnership Name

     

    In the file “Sites.csv”, the column “Activities” will be removed. Data relating to which Activities are available at which Sites can be accessed via the “SiteActivities.csv” file within the CSV download zip file.

    1. Open Data – JSON Download

    In the JSON download file, the following column headings will change:

    File

    Column Heading Before Change

    Column Heading After Change

    JSON download

    cspCode

    activePartnershipCode

    JSON download

    cspName

    activePartnershipName

     

    To note that there will be no change to the values within the column ‘activePartnershipCode’, these will remain with the ‘CSP’ prefix (e.g. CSP031).

    1. SQL Database Export

    In the table dbo._Areas, the following column headings will change:

    Table

    Column Heading Before Change

    Column Heading After Change

    dbo._Areas

    CspId

    ActivePartnershipId

    dbo._Areas

    CspName

    ActivePartnershipName

    dbo._Areas

    CspCode

    ActivePartnershipCode

     

    To note that there will be no change to the values within the column ‘ActivePartnershipCode’, these will remain with the ‘CSP’ prefix (e.g. CSP031).

    ----------

    August 2019

    ----------

    September 2017

    • Sport England receive exemption from Ordnance Survey and Royal Mail to make Active Places open data available with derived data. 

    ----------

    March 2017

    • A daily JSON download of the Sport England data is available as a Data Download.
    • A real time API is available to provide change only data to maintain the Data Download as a self-maintained dataset.