Site Address details

[colmjude]

A discussion thread for information about the Site Address details section

See all open issues for the Site Address details section

[stevenbrandwood]

Definitive address and Unique Property Reference Numbers (UPRNs) can be obtained from OS AddressBase , NGD products and OS Places API. A limited address search can be performed at www.findmyaddress.co.uk

We are working with local authorities to capture site information at the planning stages and give the site a UPRN.

Definitive addresses are linked back to a definitive street index (the National Street Gazetteer) via a Unique Street Reference Number (USRN). USRNs can be searched at www.findmystreet.co.uk This is matched to the OS street network in OS Highways and made available via OS This enables users to see what street an address or site is access from.

[colmjude]

It has been suggested that this section should be renamed because Site Address Details can be a misleading name. This is because the site may not have an address and may not ever have one.

Suggestions

• Site location
• Site details

[colmjude]

Suggestion: Give the site a name, this can help communities identify sites. This is particularly important for sites that span multiple addresses. For example, a large development on Finchley Road is known as the O2 site.

[colmjude]

Information model

👉 See the latest version of the information model

[addhow]

In the absence of geometry/coordinates/UPRN if capturing an address then structured data would surely be preferable wouldn't it?

[James-Planningportal]

This component is listed for householder and many other types, but the information model only refers to the two tree works applciation types.
Need some clarity on how this is intended to work for 'single' location sites for all other types.

[James-Planningportal]

Do we need easting/northing AND latitude/longitude? Can one be inferred from the other?

[emilyhadleyMHCLG]

I came here to comment something similar - I've assumed EITHER 'easting' AND 'northing' OR 'latitude' AND 'longitude' are required, not sure if both pairs are needed.

[colmjude]

Converted into an issue

Responses added to the issues

[James-Planningportal]

Has postcode been omitted intentionally? In other components both 'address-text' and 'postcode' are listed as separate fields, e.g. in the 'person' object here: #78

For consistency, I'd say that postcode should either be separate or part of 'address-text' across the board

[colmjude]

Good spot. Missed unintentionally.
Fixed 684e948

[addhow]

What will be the standard coordinate reference system to be used for the site-boundary geometry?

[colmjude]

Hi @addhow

For lat and long it will be WGS84.
WGS84 is the UK governments' preferred CRS for the exchange of point data

field	name	description	required	notes
latitude	Latitude	Latitude coordinate in WGS84 (EPSG:4326)	MAY
longitude	Longitude	Longitude coordinate in WGS84 (EPSG:4326)	MAY

[addhow]

Thanks, what about the polygon data submitted i.e the redline area presumably that will be in OSGB36?

[pixeltrix]

@addhow my assumption is that it will be WGS84 - it's meant to be in GeoJSON format and that doesn't support anything other than WGS84 officially. We've just hit this issue on BOPS/Planning Portal integration where they are sending us OSGB36 but it needs transformation via OSTN15 to get the correct latitude/longitude. The standard projections you can use in an interactive online map show the boundary in the incorrect place on an basemap using EPSG:3857 - you need to switch to a EPSG:27700 basemap to place the boundary correctly.

[James-Planningportal]

@addhow my assumption is that it will be WGS84 - it's meant to be in GeoJSON format and that doesn't support anything other than WGS84 officially. We've just hit this issue on BOPS/Planning Portal integration where they are sending us OSGB36 but it needs transformation via OSTN15 to get the correct latitude/longitude. The standard projections you can use in an interactive online map show the boundary in the incorrect place on an basemap using EPSG:3857 - you need to switch to a EPSG:27700 basemap to place the boundary correctly.

I guess one way or another, we need to know 'how far' the MHCLG data standards will go in enforcing standards for the site boundary data (i.e. will it specify/validate a specific CRS).

GDS guidance ( https://www.gov.uk/guidance/uk-geospatial-data-standards-coordinate-reference-systems ) says that "The CRS that should be used in Great Britain is the British National Grid." so we're compliant with that, but as per above, this is not in line with the latest geoJSON spec: https://datatracker.ietf.org/doc/html/rfc7946#section-4

OS itself identifies there is some flexibility in the spec: https://labs.os.uk/public/blog/using-geojson-in-web-applications so its more a case of Government confirming if the GDS stated standard takes precedence here (or not).

[addhow]

Yes definitely be good to know what they're going for. I know the esri stuff is pretty good at transforming on the fly these days but it's not ideal and from talking to our GIS mgr not always the most accurate transformation.