The map below uses the freely available sample data from Ordnance Survey. Including MasterMap, AddressBasePlus for
Royal Mail postal addresses, where matched to a UPRN. And Code-Point for Post Codes. OpenStreetMap provides extractable building polygons, although the building data has large gaps in some towns and as such can only be relied upon to produce higher level FTTH plans. Demand levels, which can be based on the building type or footprint, could not easily be assigned.

The study area lies to the west of the city of Exeter. OS Grid Square sx9091 was used as an example area, west of Exeter’s St. Thomas train station.

Notice the routeline for the network, uses the roadside curb line as a close approximation to a pavement laid cable duct. Curblines have a specific attibute value, as do the boundaries of houses on the nearside or inside of the pavement, where one exisits. The middle line of the pavement could be used as an even closer approximation to a suitable fibre routeline or network distribution line.

Work continues on detailing the drop lines, distribution lines, main feeder lines and distribution line terminations. Also on clustering demand using the K Mean, an attribute clustering tool, to group demand points. potential network node point positions will be calculated on routeline length and aggregated demand levels

The Voronoi polygons gather (fairly accurately) postcode groups, although some building TOIDs appear to mave mismatched postcodes. A GRASS GIS Convex Hull tool could be used to better group postcodes. Such anomalies have to be checked and corrected if necessary, individually. Postcodes were derived from AddressBase Plus data for Exeter. Retaining Postcodes will enable reporting of postcodes serviced across the network.

This plan uses the Sample OS MasterMap, Highways, Topographical and AddresBasePlus datasets, available free from the Ordnance Survey, all centered on Exeter City.

Note: There are over 1,000 features in this composition. Layer loading times will vary, and may take longer to load. Zooming in to the map speeds up the refresh times.

The data for these maps is transferred to the same webspace as this site using the QGIS plugin qgis2web. It is served using JavasScript. If it was served from an online database redrawing the map performance of this map would be greatly enhanced. An open source database such as PostgreSQL running with its spatial data enabling extension PostGIS, would serve this and maps displaying many layers with large amounts of data, considerably faster.