It is assumed that the user will have already set the default co-ordinate reference system in QGIS to British National Grid (EPSG 27700). Instructions of how to do this can be found in the QGIS Getting Started Guide;

Loading and Displaying GeoTIFF supply

1. Open QGIS. Select ‘open raster layer’ from the left hand toolbar.

1. In the next window, click ‘browse’ and navigate to the folder where the OS OpenMap-Local GeoTIFF files are located.

1. Select one or several GeoTIFF files as required. Once selected, click ‘open’.

• The files will then appear in the QGIS map window.

• Zoom to the desired map scale using the zoom buttons or set the scale using the drop-down option at the bottom of the window. It is recommended to set the viewing scale to 1:5000 or slightly less.

As an alternative to loading the GeoTIFF files one at a time or in groups, it can be quicker and easier to create a virtual raster table (VRT) to load the data.

1. In the QGIS main menu, select ‘Raster’ and then in the drop-down menu select ‘build virtual raster (catalog)’. In the resulting window, the user has the option of selecting a folder containing all the raster GeoTIFF files, or the user can simply select several files with which to build the virtual raster table.

• It is highly recommended, for OS OpenMap-Local, to keep the maximum size of the VRT file to a 100km2 grid square, for example, SU. In some cases, the maximum number of tiles will be smaller than this.

1. The user also has the option of loading the virtual raster table when finished. Once the choice is made click ‘select’ and then navigate to the selected folder.

• It is then necessary to specify the name and location of an output VRT file. It is normal procedure to place the VRT file in the same folders as the GeoTIFF files.

1. Once the user is happy with the name of the VRT file and its location, click ‘Save’.

• The dialog box is now populated with the data required to construct the VRT file.

1. When satisfied, click ‘OK’. The process should now start and run to completion. It is important to note that in testing with the beta release data, the actual maximum number of OML raster tiles that could be included in a VRT file was considerably less than a 100km2 grid tile, as indicated previously in this guide. This is because there are 400 separate GeoTIFF files within a 100km2 tile and the actual size of the GeoTIFF file does vary according to the density of detail in the area which it covers. The user must experiment with their own system to find the optimal number of tiles for a VRT table.

• The user can now click ‘OK’ twice and then close the Build Virtual Raster catalog dialog box.

1. The OS OpenMap-Local raster data should display in a similar fashion to the example below, if the ‘load data into canvass when finished’ option was ticked in the building dialog window. If this option was not selected, the VRT file will have to be loaded manually by selecting the load raster data button as described previously and then selecting the .VRT file just constructed. For best viewing results, set the viewing scale to 1:5000 or slightly less.

For the purposes of this guide, it is assumed that the user is familiar with the procedure of creating a file geodatabase within ESRI ArcGIS. A file geodatabase is used to contain a raster catalog. The procedure for creating a raster catalog will be described later. The construction of a file geodatabase is described in the loading of the vector version of OS OpenMap-Local section of this guide.

Loading and Displaying GeoTIFF supply

1. Open ArcMap. To load the GeoTIFF file on an individual basis, or in small groups, click ‘Add Data’.

1. In the dialog box, browse to the folder where the GeoTIFF files are to be found. If the folder is not in the list of connected folders, the user will have to create a new folder connection to it in the usual way. Select the GeoTIFF files required and click ‘Add’.

1. In the next dialog box, the user should consider whether or not pyramids should be created before loading the raster data. In this case we are not going to create pyramids with the data.

1. Click ‘no’ on this dialog box. This must be repeated for all the raster files selected to be loaded. The data loaded should appear in a similar fashion to what is displayed in the next example. Select a suitable scale for viewing the data, probably around 1:5000 or less.

1. The best way of loading multiple raster files in ESRI ArcMap is to use a raster catalog to store the data. This method works from within a file geodatabase, which can also be used to store the vector version of OS OpenMap-Local if required. Details of how to create a file geodatabase in ArcCatalog are described in the loading of the vector version section later in this guide.

• Assuming the user has a file geodatabase already created to hold the data, the following procedure can be used to create a raster catalog to hold the raster files.

1. Open ArcCatalog. Right-click on the file geodatabase that has been created to fold the data and select ‘New’ ‘Raster Catalog’.

1. In the resulting dialog box, the user must give the raster catalog a name. In this box one can also specify a co-ordinate reference system and if the catalog will be managed or unmanaged. A managed catalog will physically contain all the raster tiles, and will take longer to create. However, if the file geodatabase is to be shared, the data will be available with the database and can be shared more easily with other users. In the example we have created a managed catalog with the British National Grid co-ordinate reference system. Click ‘OK’ when finished.

1. Once the catalog has been created it will appear as an entity within the file geodatabase. Refresh in ArcCatalog to see if it has been created. To load the raster files into the catalog, right-click the raster catalog and select ‘load raster datasets’.

1. Browse, in the next dialog box, to the folder where the raster datasets are stored and select the ones required for use. Click ‘OK’ when finished. The list of selected raster will now appear in the dialog box.

1. The output geodatabase will normally be the correct one where the raster catalog is located, so the user can then click ‘OK’. This process may take some time if there are many files to be loaded to the catalog, and the catalog which is being used is of the managed type. Once completed, the user will see the list of files in the catalog listed in the view pane of the main ArcCatalog window.

1. In ArcMap, select ‘Add Data’ and then browse to the file geodatabase where the raster catalog is stored. Select the raster catalog and then click ‘Add’. The data will now appear in the ArcMap main map window.

1. Select the raster catalog and then click ‘Add’. The data will now appear in the ArcMap main map window.

1. If a grid similar to what is shown in the example below is seen, it means that the catalog contains over the maximum number of raster tiles set to be displayed in ArcMap, which then defaults to a wireframe grid.

1. If this happens, the wireframe mode should be turned off. Right-click on the raster catalog in the table of contents window, select ‘Properties’ and then select the ‘Display’ tab. Click on the ‘Never show Wireframe’ radio button. Then click ‘OK’ or ‘Apply’. The raster data should now display correctly.

For the purposes of this guide, it is assumed that the user is familiar with using MapInfo Professional and knows how to perform certain functions required to handle raster data. MapInfo Professional 64bit version 15.2.4 is being used in these examples. Users of the 32-bit version of MapInfo or those using earlier releases will see different screens to those shown here.

1. To open the GeoTIFF raster files, select Open Table either from the ribbon button list at the top of the screen or select the ‘Home’ tab and select the table option.

1. In the next window, navigate to the folder in which the raster files are found. Initially, on a first load, the user will need to change the files of type to raster image from the default ‘tab’ type.

1. Select the number of raster tiles required and then click ‘open’. The raster data is now displayed in the map window.

1. MapInfo has loaded each of the raster tiles individually. Although this is normally OK for a small number of tiles, when working with large numbers of raster tiles and/or multiple layers of data, it is more efficient to create a seamless table in MapInfo to hold the data.

• The user will need to load the seamless table manager under the Tools button in the Home tab of MapInfo Professional.

1. The user must load at least one raster tile into the map window to start the process of creating a seamless table. Once this is done, double click seamless manager in the tools drop-down as shown above. The following window will appear.

1. Click ‘New Seamless Table’. Then select a folder in which to store the seamless table and give the table a name. Then click ‘Save’

1. MapInfo has now created a seamless table containing the one table that was loaded in the map window. The user can now add additional tables to the seamless table by appending additional tables to the one just created. This procedure works differently to the process used in earlier 32-bit versions of MapInfo. In MapInfo 64-bit, all the tables to be appended need to be loaded into the map window first.

1. This time click the ‘Append to Seamless Table’ Option. The browse window will appear.

1. Select the seamless table to be appended. In the example above it is ‘OML.TAB’. Click ‘open’. The following message will appear depending on the number of tables loaded into the map window.

1. From now on, the user can load all eight tables (in this example) at once simply by loading the seamless table. It is also important to note that the seamless manager will only work on tables created by MapInfo when loading in the original raster files. It will not work with GeoTIFF files directly.

Loading and Displaying GeoTIFF supply

1. Open CadCorp Map Modeller. In the ribbon menu bar, select ‘Add overlay’.

1. In the next window, select ‘File’ as the type of overlay to be opened.

1. Navigate to the folder where the data resides and select however many GeoTIFF files that are required to be loaded.

• Click ‘Finish’.

1. The GeoTIFF files will load into the map window.

Alternatively, the user can drag and drop the GeoTIFF files directly into the CadCorp Map window.

It is assumed that the user will have already set the default co-ordinate reference system in QGIS to British National Grid (EPSG 27700).

Loading and Displaying Shapefile Supply

1. Open QGIS. Select ‘open vector layer’ from the left hand toolbar.

1. In the next window, click ‘browse’ and navigate to the folder in which the OS OpenMap-Local shapefiles are located.

1. OS OpenMap-Local data is comprised of a number of shapefiles containing different elements of the whole dataset. It is up to the user as to which elements are loaded depending upon requirements. In this example, all of the main elements will be loaded into QGIS. After selecting the files required and clicking ‘open’ twice, the user will be presented with the data loaded.

• In the example below, the SU 100km grid tile has been loaded.

1. It will be noted that some features extend beyond the tile edge. This is indicative of the ‘hairy tile’ supply. The layers will need to be ordered correctly in order to display correctly, so that the polygon data does not cover the line and point data. A suggested layer order is shown below, but the user may wish to change this as per requirements.

1. It should be noted that initially, it is easier to turn off the functional site layer whilst styling is applied to the other layers. The functional site layer is an attribution layer which highlights various important sites and does not form part of the map base itself. Performance will be improved by adding a spatial index to each of the layers. Right click each layer in turn. In the context menu, select ‘properties’ and then click the ‘general’ tab. The ‘create spatial index’ button will be seen just below the co-ordinate reference system box. Each layer can be styled to appear as per user requirements. In QGIS, style files are identified by having the extension .QML. To add a style to a layer, right-click on the layer in the layer window and select ’properties’. Click the ‘style’ tab. The user can now either style the data using the various tools available or by loading a predefined style from a .QML file. For more information, please see the Getting Started with QGIS guide referred to at the beginning of this section. Ordnance Survey has released a set of style files for OS Open Map for QGIS. These will be available on the Ordnance Survery GitHub repo here. Instructions for layer ordering and loading of these styles are provided in the Quick Start Guide which is included with the style files.

The example above is styled using the published OS OpenMap-Local style files and layered according to the instructions included in the Quick Start guide available with those files.

Merging the Shapefile Supply

The user may have a requirement to load more than one 100km2 grid square to cover the area that is required. The user will need to extract the relevant shapefiles from each tile into a folder. In the final release of data, the individual shapefiles will be prefixed with their National Grid 100km grid square reference letters as shown below.

Each shapefile element of OS OpenMap-Local will need to be merged separately in order that the user obtains a shapefile, for example, buildings, covering the whole area of interest. It is recommended that the user copies each of these elements into a new empty folder before merging is carried out. In the case shown above, the buildings shapefiles for SU and TQ have been copied to an empty folder. To merge the shapefiles together in QGIS, from the main menu, select ‘vector’ then ‘data management tools’. The ‘merge shapefiles to one’ option is towards the bottom of the list of options.

In the next window, the user will need to define if the shapefiles to be merged are either points lines or polygons, and also the folder where the files to be merged will reside. In this example, all of the files in the folder specified will be merged, which is easier than defining individual files. Finally, an output folder and filename for the merged shapefile needs to be selected. The user can also specify if they want the newly merged file to be automatically added to the map canvass.

Once ‘OK’ is clicked, QGIS will create a merged shapefile covering the element of the grid tiles required. In this example, the building shapefiles for SU and TQ are being merged. This procedure will need to be repeated for all of the other layer shapefiles for OS OpenMap-Local which the user requires.

When working with merged shapefiles of any kind, it is highly recommended that a spatial index be applied to each element of the data, particularly if the user is loading national sets of data. The performance improvement in rendering the data will be very noticeable. In the case above, styling can now be applied to the data as described previously in this guide.

Removing Duplicate Features from Merged data

As has already been stated, OS OpenMap-Local data is supplied as ‘hairy tiles’ with features which cross a 100km2 tile edge being supplied in both tiles in which the feature appears. In many instances, the user will simply wish to use the merged OS OpenMap-Local data as a contextual backdrop map. In this case, there will be no need to remove duplicate features along the tile edges as the features will display perfectly clearly with one duplicate feature overlying the other.

There may however, be instances where the user wishes to carry out some form of analysis using feature counts contained within the data. In this case, the data will need to have the duplicate features removed. There are several ways within QGIS to achieve this. There are also several plugins for QGIS which can be installed to carry out this function, in particular one called ‘MMQGIS’. However methods using these options are not described here.

The ‘Dissolve’ function in QGIS which is part of standard functionality will effectively carry out this procedure. In the example described below, we are going to de-duplicate the merged SU_TQ Buildings file that we created in section 2.1.2. We have the file loaded into the map window.

From the main menu, select ‘vector’ then ‘geoprocessing tools’ followed by ‘dissolve’. Another window will then appear.

The user will need to select the input vector layer to be de-duplicated; in this case, the SU_TQ Buildings file is already selected. The dissolve field is set to ‘ID’ which will be the field in the data which will be searched for duplicate features. Finally, the user will need to specify an output folder and filename for the

de-duplicated data. Once this is done, the user can specify whether or not the newly created file can be added to the current map canvass. Click ‘OK’ to start the process.

A message appears once the process is complete. The new shapefile containing the de-duplicated data can now be loaded into QGIS. Once again, it is highly recommended that the de-duplicated file be given a spatial index using the method previously described to improve rendering performance

The data can now be styled with a suitable style as per user requirements using the procedures as described earlier in this guide.

Loading and Displaying GML Supply

Open QGIS. Select ‘open vector layer’ from the left hand toolbar.

In the resulting window, click ‘browse’ to open the window, which will allow the user to select the .GML file to be loaded.

The user will need to specify that a .GML (geography mark-up language) file needs to be opened from the drop-down menu at the bottom of the window. Select the file and then click ‘open’ twice.

Another window will appear which will allow the user to select which layers of the data to load. If all of them are required, click ‘select all’.

The data will now load into the map window.

In the example below, just the roads and buildings from the SU tile were selected.

The data can now be styled using a predefined style file (.QML file) as described previously or using the tools within QGIS. Please note that style files created for shapefile supply of the data will not work with GML supply without modifications. It is highly recommended that style files created specifically for the GML supply be used.

It should be noted that rendering performance of the data within QGIS will be much poorer than in the case of the shapefile format as GML data cannot be spatially indexed. It should also be noted that multiple 100km² tiles of OpenMap .GML data cannot easily be merged together as with the shapefile option and as a consequence, rendering performance will also be much slower. In addition, it is not easy to de-duplicate features along tile edges using common spatial geoprocessing tools within QGIS. As a result, the GML data itself will have to be queried using code scripts to highlight and remove duplicate features within a text editor. This is not covered in this guide.

Loading and Displaying Shapefile Supply

There are two possible ways of loading and displaying the shapefile data in ESRI ArcGIS. The shapefile data can be loaded straight into ArcGIS. However, if more than one 100km2 tile is being loaded, the rendering performance can become an issue. The recommended way of loading the data is to use a file geodatabase to house the data. This is the method which will be described in this guide.

1. Open ArcCatalog. Choose a folder where the file geodatabase is to be created.

1. Right click on the folder and in the context menu select ‘new’ and then ‘File Geodatabase’. Give the new file geodatabase a suitable name for ease of reference by highlighting the geodatabase and typing a new name.

1. Once created, right click on the file geodatabase and select ‘import’ and then ‘feature class (multiple)’.

1. In the next window, browse to the location where the data resides which is to be imported. Because the individual shape files begin with the 100km prefix, it is possible to import more than one OS OpenMap-Local tile into the geodatabase as per user requirements.

1. Click on the button to the right of the blank window under ‘input features’ and navigate to the folder where the OS OpenMap-Local shapefile data resides.

1. Select all of the shapefiles that are required in the window and click ‘add’.

1. The shapefiles selected will now appear as a list in the import feature class window. The output file geodatabase should default to the one which has been previously selected. Click ‘OK’. The window will close and now ArcCatalog will import the features classes into the file geodatabase. A dialog box will appear when the process is complete.

1. If the file geodatabase is now highlighted, a list of the imported features classes should be visible. In this example, both SU and TQ shapefiles have been imported.

A useful point to note is that loading the shapefiles into a file geodatabase will automatically add spatial indexes to the data in the import process. There is therefore no requirement to manually add one once the data has been loaded, which would be the case if shapefiles had been loaded into ArcGIS without using the file geodatabase option. As has been previously mentioned, the addition of a spatial index greatly improves rendering performance.

1. Start ArcMap. Click on the ‘import data’ button in the top toolbar.

1. In the window that appears, navigate to the location of the file geodatabase just created. Select the feature classes that are required and click ‘add’.

The data will load into ArcMap. Although ArcMap does put the shapefiles into a more logical sequence, the user can move the layers according to the desired preferences. The data will, of course load in as un-styled data. ArcMap will assign a random style to the data.

The user can manually style each of the layer files by right-clicking on each of the loaded layers, selecting ‘properties’ and then ‘symbology’. ArcMap contains an extensive range of tools to allow the user to apply various styles to each layer of the data and then save the work as an ArcGIS layer file. This procedure is not covered in this guide.

A set of ESRI layer files for OS OpenMap-Local will be available for download from the GitHub web site at product launch. Follow the instructions in the Quick Start Guide which accompanies these files to apply the styling to the data. These style files will work with either a direct shapefile load in ArcMap or using the file geodatabase methodology described here.

The user should see something like the screenshot above when the process is complete.

Alternate procedure for adding layer files into ArcMap

If using a different set of layer files, the procedure for adding a style in ArcMap is as follows – this method can be used for many other data types. To add a style to a layer, simply right-click on a layer, select ‘properties’ and then ‘symbology’

1. In the layer properties window, select ‘import’ (the button below the tabs at the top). A list of available styles, drawn from the imported layer file will appear. Simply select the required style and click ‘OK’. The symbol in the box will now change to the predefined style.

Click ‘OK’ again and the style will then be applied in ArcMap. Repeat this procedure for all of the layers until the OS OpenMap-Local data is styled to requirements. Labels for certain features can also be applied as required.

Loading multiple shapefiles

If there is a requirement to load a larger area of interest, it is recommended that the user merge the shapefiles together before loading into the file geodatabase. This procedure is described under point 2.2.3. below. Doing this will also mean that the supplied layer files for styling will only need to be applied once to the data and all the styles will work properly.

If however, the user simply wants to load multiple areas using the file geodatabase option, there is no mandatory requirement to merge shapefiles together.

To add another 100km2 tile of data in ArcMap previously loaded into the file geodatabase created earlier, simply click ‘add data’ and repeat the procedure described above for loading the individual layers for the subsequent tile(s). The user may wish to group the layers for each 100km tile loaded in the table of contents window to avoid confusion.

1. Select all of the layers within the new 100km tile added, right-click and then select ‘group’. The additional layers can be styled as previously using a predefined layer file or manually as required.

This example shows that all of the layers for SU and TQ have been loaded into ArcMap from within the file geodatabase. The file geodatabase option in ArcGIS is also useful in that if the user wishes to add another tile of data at a later date, the shapefiles can be simply imported into the same file geodatabase using ArcCatalog and then displayed in ArcMap.

Merging shapefiles and removing duplicate features from the data

As has already been stated, OS OpenMap-Local data is supplied as ‘hairy tiles’ with features which cross a 100km tile edge being supplied in both tiles in which the feature appears. These duplicate features will occur if more than one 100km2 tile is loaded into a file geodatabase. In many instances, the user will simply wish to use the OS OpenMap-Local data as a contextual backdrop map. In this case, there will be no need to remove duplicate features along the tile edges as the features will display perfectly clearly with one duplicate feature overlying the other.

There may however, be instances where the user wishes to carry out some form of analysis using feature counts contained within the data. In this case, the data will need to have the duplicate features removed.

To remove duplicate features in ArcMap, it is necessary firstly to merge the elements of the tiles together before removing the duplicate features. This procedure can take some time, so the user should consider if this requirement is really needed.

1. The elements of the data first need to be merged together to create new features classes within the file geodatabase containing the original data (or to a completely new file geodatabase or shapefile if required).

1. Using either ArcMap or ArcCatalog, from the main menu, select ‘Geoprocessing’ followed by ‘merge’.

1. In the next window, select the layers to be merged. In this example the SU_Roads and TQ_Roads are being merged together. All of the attribution is being copied into the new shapefile though the user can specify what attributes need to be copied. The user can also specify the output required. This can be a new feature class within a file geodatabase or a shapefile. In this example a new shapefile containing the merged data will be created.

1. Click ‘OK’ when all of the elements to be merged have been selected. It can be seen using this method, the roads element of a number of 100km tiles could be merged together, although only two are shown in this example. ArcGIS will then merge the files and load the newly created shapefile into the map window. Depending upon the sizes and number of of the data layers being merged, this could take some time. A dialog box will appear when the process is finished.

1. In the example shown below, a new file geodatabase has been created to hold a set of merged shapefiles covering the SU and TQ grid squares. These have been styled using the style files for OS OpenMap-Local available from Github. As stated above, it is important that the instructions provided in the Quick Start guide, that accompanies these files, be followed to obtain the intended end result.

1. The ‘Dissolve’ function in ArcGIS will remove the duplicated features along the tile boundaries. This procedure can be carried out in either ArcCatalog or ArcMap. Firstly, select ‘Geoprocessing’ and then ‘Dissolve’ from the main menu.

1. The user will then need to specify which merged file from which duplicate features are to be removed. In this example we are looking at the SU_TQ_Merged road file.

We are going to save the new feature class as a new shapefile called ‘Dissolve_SU_TQ_Roads’. All of the dissolve fields in the box need to be ticked except the FID field as otherwise the attribution will not be carried over to the new dissolved file. Once complete, the dissolved layer will be loaded into ArcMap. This merged file will contain no duplicate features. It can now be styled as previously described. A count using the attribute table on both the original merged file and the dissolved file will confirm that the dissolved shapefile contains fewer features