GIS intelligence

A spatial database brings related project information into one organised, location-aware structure. It can store survey features, assets, boundaries, observations and supporting attributes while preserving their relationships and coordinate reference. GeoPackage offers a portable single-file option, while a File Geodatabase supports established Esri workflows. Both reduce scattered files and give teams a maintainable foundation for mapping, analysis and future updates.

Project layers separate spatial information into practical themes such as access, parcels, utilities, survey observations, constraints or design context. Each layer is prepared with clear geometry and useful attributes for its intended users. SHP, KML and DXF options allow the information to move between GIS, browser-based mapping and CAD workflows, helping different teams work from the same mapped evidence without unnecessary manual conversion.

A map series presents the project's spatial information as a coordinated set of readable views. Each map uses consistent symbols, scale, labels and context to explain a particular theme or area. PDF and PNG versions work well for reports and meetings, while a web map supports interactive navigation and layer control. Together they make complex GIS information understandable to both technical specialists and wider project stakeholders.

The asset register connects each mapped asset to a structured record containing its identifier, type, location and agreed project attributes. It may also link observations, photographs or status information where these form part of the scope. Delivering the register as a spatial table or spreadsheet makes it useful for mapping and everyday management, and provides a consistent starting point for maintenance, inspection or future data updates.

A data dictionary explains what the fields, codes and values in the GIS delivery mean. It records expected formats, permitted categories, identifiers and responsibility for important information, helping users enter and interpret data consistently. This small reference prevents a spatial database from becoming confusing over time and supports a reliable handover to teams who were not involved in the original survey or data preparation.

Change layers organise comparable information from different survey dates so teams can see where mapped conditions have altered. Depending on the available data, they may show additions, removals, movement, land-cover differences or updated asset status. The comparison basis and dates are clearly recorded. This supports progress review and targeted investigation while keeping the original observations available for context instead of replacing them with an unexplained result.