LogoLogo
OS Docs HomeOS NGDOS APIsOS Download ProductsMore than MapsContact Us
  • More than Maps
  • Geographic Data Visualisation
    • Guide to cartography
      • Introduction to cartography
      • Types of maps
      • Symbology
      • Colour
      • Text on maps
      • Generalisation
      • Coordinate reference systems
      • Projections
      • Scale
      • Map legends
      • Map layout
      • Relief representation
      • North arrows
    • Guide to data visualisation
      • Introduction to data visualisation
      • GeoDataViz design principles
      • Types of visualisation
      • Thematic mapping techniques
      • Data visualisation critique
      • Accessible data visualisation
      • Ethical data visualisation
      • Software
      • Data
    • GeoDataViz assets
      • GeoDataViz basemaps
      • Stylesheets
      • GeoDataViz virtual gallery
      • Equal area cartograms
      • How did I make that?
        • Apollo 11 Landing
        • North York Moors National Park, 70 years
        • Snowdonia National Park, 70 years
        • Great Britain's National Parks
        • Great Britain's Islands
        • Great Britain's AONB's and National Scenic Areas
        • Famous shipwrecks of Pembrokeshire
        • Trig pillars today
        • Britain's most complex motorway junctions
      • #30DayMapChallenge
  • Data in Action
    • Examples
  • Demonstrators
    • 🆕Product Viewer
    • Addressing & location demonstrators
      • Address Portfolio overview
      • Which address product should you use?
      • AddressBase
      • AddressBase Core
      • AddressBase Plus
      • AddressBase Premium
      • Address Classifications
      • Addressing Lifecycle
      • OS Emergency Services Gazetteer
      • What are Vertical Streets?
      • Why are there differences in boundaries?
    • Contextual demonstrators
    • Customer best practice
      • Channel Shift
      • Data Management and OS Data Hub
      • End User Licence vs Contractor Licence
      • 🆕 IDs vs Spatial Relationships
      • Why we should capture good quality addresses at source
      • Why we Snap and Trace
    • Network Demonstrators
      • OS Detailed Path Network
      • OS Multi Modal Routing Network
        • OS Multi Modal Routing Network
      • Water Networks overview
      • OS MasterMap Highways Network and OS NGD Speeds
      • OS MasterMap® Highways Network and OS Open Roadsâ„¢
    • OS MasterMap Generation APIs
      • Using the OS Features API
      • Using the OS Features API Archive
      • Using the OS Downloads API
      • Using OS APIs in ESRI Software
    • 🆕OS NGD (National Geographic Database)
      • OS NGD Address
      • OS NGD Boundaries
      • 🆕OS NGD Buildings
        • 🆕Building and Building Access Feature Types
        • Building Part and Building Line Feature Types
      • 🆕OS NGD Geographical Names
      • OS NGD Land
      • OS NGD Land Cover enhancements
      • 🆕OS NGD Land Use
      • OS NGD Land Use enhancements
      • 🆕OS NGD Structures
        • 🆕OS NGD Structures
        • Field Boundaries
      • 🆕OS NGD Transport Features
      • 🆕OS NGD Transport Network
      • OS NGD Transport RAMI
      • OS NGD Water Features
      • OS NGD Water Network
      • OS NGD API - Features
      • Ordering OS NGD data
      • Change only updates
      • OS NGD Versioning
      • Creating a topographic map from OS NGD Data
      • Analytical styling for OS NGD data
    • OS MasterMap® demonstrators
    • 🆕Product & API Comparisons
      • 🆕Comparison of Water Network Products
  • Tutorials
    • GeoDataViz
      • Thematic Mapping Techniques
      • Downloading and using data from the OS Data Hub
      • How to download and use OS stylesheets
      • How to use the OS Maps API
      • Creating a bespoke style in Maputnik
    • GIS
      • Analysing pavement widths
      • Basic routing with OS Open Data and QGIS
      • Walktime analysis using OS Multi-modal Routing Network and QGIS
      • Creating 3D Symbols for GIS Applications
      • Constructing a Single Line Address using a Geographic Address
      • Creating a Digital Terrain Model (DTM)
      • Visualising a road gradient using a Digital Terrain Model
      • Visualising a road gradient using OSMM Highways
    • 🆕APIs
      • 🆕Using OS APIs with EPC API
      • 🆕OS APIs and ArcGIS
  • Deep Dive
    • Introduction to address matching
    • Guide to routing for the Public Sector
      • Part 1: Guide to routing
      • Part 2: Routing software and data options
      • Part 3: Building a routable network
    • Unlocking the Power of Geospatial Data
    • Using Blender for Geospatial Projects
    • A Guide to Coordinate Systems in Great Britain
      • Myths about coordinate systems
      • The shape of the Earth
      • What is position?
        • Types of coordinates
        • We need a datum
        • Position summary
      • Modern GNSS coordinate systems
        • Realising WGS84 with a TRF
        • The WGS84 broadcast TRF
        • The International Terrestrial Reference Frame (ITRF)
        • The International GNSS Service (IGS)
        • European Terrestrial Reference System 1989 (ETRS89)
      • Ordnance Survey coordinate systems
        • ETRS89 realised through OS Net
        • National Grid and the OSGB36 TRF
        • Ordnance Datum Newlyn
        • The future of British mapping coordinate systems
        • The future of British mapping coordinate systems
      • From one coordinate system to another: geodetic transformations
        • What is a geodetic transformation?
        • Helmert datum transformations
        • National Grid Transformation OSTN15 (ETRS89–OSGB36)
        • National Geoid Model OSGM15 (ETRS89-Orthometric height)
        • ETRS89 to and from ITRS
        • Approximate WGS84 to OSGB36/ODN transformation
        • Transformation between OS Net v2001 and v2009 realisations
      • Transverse Mercator map projections
        • The National Grid reference convention
      • Datum, ellipsoid and projection information
      • Converting between 3D Cartesian and ellipsoidal latitude, longitude and height coordinates
      • Converting between grid eastings and northings and ellipsoidal latitude and longitude
      • Helmert transformation worked example
      • Further information
  • Code
    • Ordnance Survey APIs
    • Mapping
    • Routing with pgRouting
      • Getting started with OS MasterMap Highways and pgRouting
      • Getting started with OS MasterMap Highways Network - Paths and pgRouting
      • Getting started with OS NGD Transport Theme and pgRouting
      • Getting started with OS NGD Transport Path features and pgRouting
  • RESOURCES
    • 🆕Data Visualisation External Resources
Powered by GitBook

Website

  • Ordnance Survey

Data

  • OS Data Hub
On this page
  • What are the Field Boundaries?
  • What formats does the OS NGD data come in?
  • What is the attribution?
  • How the data is created
  • Structure OSID
  • Field Boundaries Description
  • Field Boundary Height, Width and Length
  • Use Cases for Field Boundaries

Was this helpful?

  1. Demonstrators
  2. OS NGD (National Geographic Database)
  3. OS NGD Structures

Field Boundaries

A Lightning Talk

What are the Field Boundaries?

Field Boundary

These are line features in the Structures Collection with geometry matching with the obstructing features demarking field boundaries outside of urban areas, as found in Structure Line of the Structures Collection.

Identification of the nature of the field boundary feature when adjacent to agricultural land, forestry, rough grassland or heath, and whether the field boundary is vegetated or a wall.

What formats does the OS NGD data come in?

The OS NGD Field Boundary data comes in two formats, CSV and GeoPackage (GPKG)

  • The GeoPackage format comes ready to load into the GIS package of the users choice with different gpkg files for each layer.

  • The CSV format is more suited for loading into a database. It has all of the same layers in csv format and all the same attribution as the GeoPackage, however instead of storing the geometry in a GIS ready format, it is stored as a POLYGON, POINT or LINESTRING attribute with all of the vertices stored as co-ordinate pairs in the text file.

What is the attribution?

The attribution varies between the feature types, but there are some common features:

  • All OS NGD data has an OSID, version info and changetype

  • Link to the structure line features within the OS NGD structure theme using the Structureline OSID as the unique identifier.

  • The data now has geometry evidence and update dates so users can see when the information was updated

  • Information on the type of field boundaries, can be found in the description

  • Details of the size of the boundaries will be available for the vegetated boundaries.

  • A flag will be included indicating if the line segment represents part of a woodland boundary.

How the data is created

Field Boundary features are classified where there are existing ‘built obstruction’ structure lines adjacent to, or contained within, areas of Agricultural Land, Trees, Rough Grassland or Heath. Includes field boundary features adjacent to land in the Rural Payments Agency (RPA) Rural Land Register (RLR) where they are in urban areas in England

Structure OSID

The field boundary data segments the geometry of the built_obstruction lines.

However, each field boundary segment holds a Structure OSID that can be used to link back to the original OS NGD structure line.

Field Boundaries Description

The classification will follow the hierarchy from the previous image, resulting from using aerial imagery to determine it.

For example, a wall at the edge of a forested area will be classified as a tree canopy as it would not be possible to see the wall beneath the canopy in imagery

  • Tree Canopy is defined as instances of vegetation canopy

  • Wooded Strip is defined as a continuous row of trees.

  • Hedges are defined as a row of shrubs.

  • Wall made with stones that fit together firmly with or without mortar

  • Other is where a classification has not conclusively identified the Field Boundary as a hedge or tree or wall. Fences will fall under this classification.

  • Unknown is where a geometry edit to the OS NGD Obstructing Line has occurred outside of the cyclical revision process. This will be completed from the next cyclical revision epoch.

Field Boundary Height, Width and Length

Height, width and length, derived from imagery. sizes are to provide an indication of height & width, rather than an absolute value.

Classification
Height (min/max)
Width (min/max)
Length (min/max)

Tree Canopy

3.5m/no max

0.5m/20.0m

4.0m/49.9m

Wooded Strip

3.5m/no max

0.5m/20.0m

50.0m/no max

Hedge

0.5m/3.5m

0.5m/20.0m

4.0m/no max

Wall

n/a

n/a

4.0m/no max

Use Cases for Field Boundaries

Following Engagement with the community the following use cases for the data were captured

  • Flood risk assessment to understand where boundary features can hold back water.

  • Design and administration of agricultural farming payments.

  • Vegetated boundaries are an important habitat to map, monitor natural capital and to link to existing services and national statistics.

  • Understanding surface runoff into watercourses, assessing the impact of this and mitigating the effect

  • Hedges are a high priority habitat type which provide a pollinator network, so it is important to understand their location, habitat networks and connectivity.

  • Development of Environmental Land Management Schemes to achieve local based environmental outcomes.

  • Understand hedgerow decline over time and biodiversity loss as these are a priority habitat.


Links that may be useful:

PreviousOS NGD StructuresNextOS NGD Transport Features

Last updated 8 months ago

Was this helpful?

This content has been developed from what was originally a Lightning Talk PowerPoint slide set. These slides are available to PSGA members to view and download from the

PSGA members area of the OS website
🆕
🆕
OS NGD Documentation Platform | osngd
Logo
OS Data HubOrdnanceSurvey
Logo
OS Select+Build | OS productsOrdnance Survey
Page cover image
Logo