ArcGIS REST Services Directory
JSON

Layer: MUDC_Wards (ID:0)

View In:   Map Viewer

Name: MUDC_Wards

Display Field: WARDNAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: This dataset is based upon the Boundary Commission (BC)2012 Wards and mered to LPS large scale features. Where it was obvious that the BC line work was meant to follow a feature, e.g. hedges, banks or centre of roads and rivers this became the new ward line.There were rules created to assist in this process. TownlandsWhere BC Wards 2012 are coincident with Townland use the Townland boundary line. Where BC Wards 2012 are within 6 metres of the Townland and there appears to be an intention to follow the Townland use the Townland boundary line. Where BC Wards 2012 are greater than 6 metres of the Townland and there appears to be an intention to follow the Townland use the Townland boundary line.1993 WardsWhere BC Wards 2012 are coincident with 1993 Wards use the 1993 Wards boundary line.Where BC Wards 2012 are within 6 metres of the 1993 Wards and there appears to be an intention to follow the 1993 Wards use the 1993 Wards boundary line. Where BC Wards 2012 is greater than 6 metres of the 1993 Wards and there appears to be an intention to follow the 1993 Wards use the 1993 Wards boundary line. Where BC Wards 2012 are coincident, within or greater than 6 metres of the 1993 Wards and the boundary is defaced or undefined then the 1993 Wards or nearest existing administrative boundary will be used.HWMMTWhere BC Wards 2012 are coincident with HWMMT use the HWMMT boundary line.Where BC Wards 2012 are within 6 metres of the HWMMT and there appears to be an intention to follow the HWMMT use the HWMMT boundary line.Where BC Wards 2012 are greater than 6 metres of the HWMMT and there appears to be an intention to follow the HWMMT use the HWMMT boundary line.Where BC Wards 2012 does not follow the HWMMT at the end of inlets (Strangford Lough) then the nearest existing administrative boundary will be used OR the BC Wards 2012 line will be used.Road and water centrelineWhere BC Wards 2012 are coincident with road or water centreline use the road or water centreline.Where BC Wards 2012 are within 6 metres of the road or water centreline and there appears to be an intention to follow the road or water centreline use the road or water centreline.Where BC Wards 2012 are greater than 6 metres of the road or water centreline and there appears to be an intention to follow the road or water centreline use the road or water centreline. If no centreline exists then a line will be created following the centre of the road or water feature.OSNI large scale featuresWhere BC Wards 2012 are coincident with OSNI large scale features i.e. fence, wall, bank, hedge or perimeter_other then use the OSNI large scale features.Where BC Wards 2012 are within 6 metres of OSNI large scale features i.e. fence, wall, bank, hedge or perimeter_other and there appears to be an intention to follow OSNI large scale features then use the OSNI large scale features.Where BC Wards 2012 are greater than 6 metres of OSNI large scale features i.e. fence, wall, bank, hedge or perimeter_other and there is no OSNI large scale feature that can be used then use the BC Wards 2012 boundary line.

Copyright Text: This dataset has been created by LPS – Spatial Data Enhancement section. Contact Jim Kelly at Jim.Kelly@dfpni.gov.uk for more information regarding the creation of this dataset. Your feedback and comments are also welcome.

Min. Scale: 0

Max. Scale: 0

Default Visibility: true

Max Record Count: 1000

Supported query Formats: JSON

Use Standardized Queries: True

Extent:

Drawing Info:

HasZ: false

HasM: false

Has Attachments: false

Has Geometry Properties: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Object ID Field: OBJECTID

Unique ID Field:

Global ID Field:

Type ID Field:

Fields:
Templates:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 2/7/2019 10:45:39 AM

Schema Last Edit Date: 2/7/2019 10:45:39 AM

Data Last Edit Date: 2/7/2019 10:45:39 AM

Supported Operations:   Query   Query Top Features   Query Analytic   Query Bins   Generate Renderer   Validate SQL   Get Estimates