4 Ways Water Companies Can Get More Value From Their OS Data
🎧 Audio summary
Get up to speed in less than 2 minutes
A speedy listen, generated using Google NotebookLM.
You already make extensive use of Ordnance Survey data across asset management, network planning and modelling. You’ve most likely started moving to the OS National Geographic Database (OS NGD) or are thinking about when to.
This move can be treated as a simple migration or as an opportunity to rethink how your data is accessed, selected and used. The latter unlocks far more value from what you’re already paying for.
So, here are 4 ways that OS NGD data can work harder for you…
1. Ditch the “download everything, store locally” habit
While OS NGD lets you download data, it’s built to be accessed through APIs. This means you have the most up-to-date information from OS without having to manually refresh or store a tonne of data. The two most popular APIs are…
- Features API: live, queryable geographic data on demand
- Tiles API: instant, ready-to-use basemaps for dashboards and applications
đź’ˇ example – Remove the quarterly manual refresh
Your asset management team may manually refresh a full regional OS dataset every quarter to keep its GIS in sync. By switching to the OS Features API, its systems could query the data directly, removing that repetitive manual work.
2. Draw a smaller box
Rather than pulling a full national or regional supply, Custom Areas let you take data only for the area that matters to you and your workflows.
đź’ˇ example – Take only the data the project needs
A team assessing a proposed pipeline could define a Custom Area around the route with an appropriate buffer. The resulting data supply would include the buildings, roads, structures, water features and land information needed for early feasibility work, without including anything beyond the project area.
3. Get specific
OS NGD is organised into themes, collections and individual Feature Types, so you can select exactly what Features a workflow needs rather than loading everything into every system.
đź’ˇ example – Choose specific Features, not the entire Theme
The Water Theme contains Features covering watercourse connectivity, flow direction, inland or tidal classification, subterranean passages, catchment names, gradients, widths and watercourse names. Previously, you would have had to license the entire Theme to access a specific Feature. Now, you can select only the Features you need.
4. Build, Use, Repeat
A Recipe is a reusable selection of OS NGD data built for a specific purpose. They pull together a set of defined Feature Types and attributes. This means more consistency across teams, and less mismatched datasets and schemas.
đź’ˇExample – Create a repeatable recipe for flood analysis
A water company could create a flood-consequence Recipe covering water features, buildings, structures, roads and access routes, land use and relevant address information. Whenever a team assesses a new location or refreshes an existing analysis, it can use the same agreed selection for faster, more consistent results.
Get more with OS NGD
Getting more from OS NGD isn’t about accessing more data. It’s about accessing the right data, for the right workflow, in the right way.
Some workflows will still need a downloaded dataset. Others may be better served by an API, a smaller geographic area, a reusable Recipe or a more focused selection of Feature Types.
For water companies, reviewing those choices can reduce unnecessary data handling and make OS data more valuable across planning, modelling and operational decisions.
Going to the Water, Wastewater and Environmental Management Expo?
Simon will be at WWEM Expo, talking to water companies about connecting complex data, improving established models and getting more value from technologies such as FME and OS NGD. If you are attending, arrange a time to meet him.
Arrange a chat with Simon View event details