interpose userguide digimap a4

InterpOSe for Digimap® Interpreting and processing OS MasterMap effectively

User Guide Version 4.6 Febuary 08

Hanbury Court, Harris Business Park, Stoke Prior, Bromsgrove, B60 4JJ, UK.

E-mail: [email protected]

Licensed Partner

®

This document is copyright and remains the property of Dotted Eyes Ltd. It may not be reproduced or disclosed to any third parties without express written permission.

mailto:[email protected]

InterpOSe DIGIMAP User Guide Version 4.6

Ferry .................................................................... 18 ContentsRoad_Node .......................................................... 19 Road_Node_Info.................................................. 19 Link_TopoArea_Xref .......................................... 19 1. Introduction ......................................................... 1 Road_Link ........................................................... 19 Standards and implementation............................... 1 Road_Link_Info................................................... 19 Benefits of processing data.................................... 2 Road_Link_Info_Pt ............................................. 19 Process a full supply.............................................. 2 DirectedLink_Xref............................................... 20 Licence arrangements............................................ 2 Road_Route_Info................................................. 20 Installing the software ........................................... 3 Road_Route_Info_Pt ........................................... 20 Running one of the wizards................................... 3 Upper_Level_Bridge ........................................... 21

2. Processing the data.............................................. 3 Upper_Level_Road_Link .................................... 21 Identifying the order summary .............................. 4

5. Data holding validation ..................................... 21 Displaying the order summary .............................. 4 Selecting the FVDS files ..................................... 22 Selecting the input files ......................................... 5 Specifying the data format................................... 22 Specifying the output format ................................. 5 Identifying the parameter file .............................. 22 Setting the AutoCAD options................................ 6 Validation progress and report............................. 23 Selecting the output tables..................................... 7 Checking causes of defects .................................. 23 Specifying the output folders................................. 8

Metadata files ........................................................ 8 Appendix I Copy of licence agreement............... 25 ITN reference database.......................................... 8

Appendix II Topography Layer vs Land-Line.... 26 ITN cross reference and bridges............................ 9 Processing of chunks ........................................... 10 Appendix III ITN Layer vs OSCAR Asset-Mgr ... 28 Discarding duplicate features .............................. 10

Appendix IV Address vs ADDRESS-POINT........ 29 Choosing output file options ............................... 11 Catalogue settings................................................ 11 Appendix V Address Layer 2 vs Address ............ 30 Processing progress and log ................................ 12

Appendix VI Comparative glossary of terms ....... 30 3. Understanding the data..................................... 13

Appendix VII Styles in the feature catalogue......... 31 TOID and flat file feature types........................... 13 Feature routing to output tables ........................... 13 Themes and feature codes ................................... 14 ITN normalised feature types .............................. 15

Classification by categories................................. 15 AutopOSe, InterpOSe, ResponseMX, ShiftWiz, SuperpOSe and TranspOSe are trade marks of Dotted Eyes Limited and Dotted Eyes is a registered service mark. Ordnance Survey, the OS Symbol, ADDRESS-POINT, Land-Line, Land-Line.Plus, OS MasterMap, OSCAR and TOID are registered trade marks and Boundary-Line is a trade mark of Ordnance Survey, the national mapping agency of Great Britain. Royal Mail and PAF are registered trademarks of Royal Mail. MapInfo Professional is a trade mark of Pitney Bowes Software Inc. ArcCatalog, ArcGIS and ArcView are trade marks of Environmental Systems Research Institute. AutoCAD and DXF are trade marks of Autodesk Inc. FME is a trade mark of Safe Software Inc. Oracle is a trademark of Oracle Corporation. Acrobat is a trade mark of Adobe Systems.Incorporated.

Rules-based classification ................................... 16 Columns of attribute data .................................... 16 Change history data ............................................. 17 Values of numeric attributes................................ 17

4. Default ITN output tables ................................. 17 NetworkMember_Xref ........................................ 18 Road_Box............................................................ 18 Road_Line ........................................................... 18

© Dotted Eyes Ltd August 2007 Page ii


1. Introduction

InterpOSe for Digimap® is an application for Windows 2000 or above that interprets and processes the OS MasterMap product, in the schema as supplied by EDINA for use within Academic Institutions. It is a reduced functionality version of the commercial product, with a limited function set. It reads .gz (compressed .gml) input files and writes a local holding of output tables in a choice of formats: MapInfo .tab (table), .mif/.mid (MapInfo interchange format), ESRI .shp (shape), AutoCAD .dwg (drawing) or .dxf (drawing exchange format).

The role of this software product is much more than merely to translate from one format to another. It automatically performs sophisticated feature-based data processing tasks. The processing may take a significant time to run, and is designed to be left unattended – for example overnight.

Each .gz input file contains a chunk of the OS MasterMap product, consisting of vector map features – i.e. points, lines, polygon regions and text – or in some cases features with no geometry.

Every feature has a TOID attribute (a term originally abbreviated from TOpographic IDentifier, but now applying to all types of feature), which is a 16-digit number.

In the .gz file, any leading zeroes at the start of the TOID are not included, so the processing wizard inserts them and stores the result in a character column to ensure that all TOID values are presented in a consistent 16-digit format.

For a detailed comparison of OS MasterMap features against Land-Line, see Appendix II.

© Crown Copyright 2002-7

Symbols resembling DfT road signs are used in the ITN output tables by default, though they do not necessarily indicate that there is a road sign at the same location in the real world.

For a key to the graphic styles specified in the output, see Appendix VII.

Standards and implementation The data format of OS MasterMap is based on the Geography Markup Language (GML) version 2.1.2 specification – OGC (Open GIS Consortium) document number 02-069 dated 17th September 2002. GML is an implementation of XML (eXtensible Mark-up Language).

© Dotted Eyes Ltd August 2007 Page 1 of 36


InterpOSe for Digimap® is different from the standard commercial product in that it is designed to work solely with the supply schema of OS MasterMap as supplied by EDINA for use within UK academic institutions.

The software takes full advantage of the fast memory in your computer, and performs most efficiently when a large amount of free RAM is available. If the Windows virtual memory manager has to page data to disk, processing will take much longer.

Benefits of processing data Some GIS and mapping systems, including MapInfo Professional v7.0 or above, include a generic means of translating a single .gml file.

In contrast, InterpOSe is specifically designed for interpreting all the information in the OS MasterMap product. For example, duplicate features in geographic chunks may be discarded automatically as part of the translation process.

Text features can be filtered and indexed to form a gazetteer, enabling you to centre the map on the name of a feature.

Process a full supply InterpOSe processes one or more input files of OS MasterMap data into your chosen format. It creates a set of output tables, containing the Layers you specify.

The attribute data is analysed to determine which output tables (or layers) should contain each feature.

When you process a full supply of data, these output tables will make up your current data holding.

For a full supply there are two optional metadata tables. These do not themselves contain any feature geometry, but rather information about the features that have been processed:

• Change history database, containing a list of Change Date and Reason For Change attributes of the feature edits made by Ordnance Survey.

• Validation vault, containing a list of features that have not been routed to any output table, as defined by the parameter file. This is required for use with the Feature Validation Data Set.

Licence arrangements For a copy of the licence agreement, see Appendix I in the User Guide.

The software is provided free of charge for use with data supplied by EDINA to academic institutions. This free edition will not process OS MasterMap data supplied by Ordnance Survey; a Standard Licence is required for that use.

To upgrade to the Standard Licence, please contact [email protected].

The use of output files is limited to within your institution.

InterpOSe includes a single-user licence to a font called Heledd, which uses the Latin-8 character encoding, including accent marks on the Welsh vowels w and y. This font is installed onto the same computer as IntepOSe, and is specified in the default.itp parameter file for the Cartographic Text features routed to the Carto_Text output table.

If you want to use the Heledd font on any other computers that access output files, contact the font creator for a multi-user licence, then install it onto those machines.

Mr Meurig Williams, MEU Cymru, 57 Beulah Road, Rhiwbina, CARDIFF, CF14 6LU

Tel/fax 02920 626386 http://www.meucymru.co.uk

Dotted Eyes Ltd accepts no responsibility for your use of the Heledd font, which is distributed ‘as is’.


http://www.meucymru.co.uk/


Installing the software To install the software, download the setup package and run the installation program.

To remove an existing installation,, use Control Panel > Add/Remove Programs.

Follow the steps in the setup wizard to install the software.

After installing the software, install the sample data input and output tables of your choice.

• If you plan to use ESRI ArcGIS software, choose also the separate installation option for ArcGIS 8.x/9.x style file. Be careful to set the correct folder as the target (e.g. ArcGIS\Styles for ArcGIS v9.0 and above). This installation must be done for every client machine.

• If you plan to use the ITN Layer in MapInfo software, choose also the separate installation option for MapInfo custom symbols. Be careful to set the correct folder as the target, corresponding to your version of MapInfo Professional (e.g. Professional\900 for v9.0). This installation must be done for every client machine.

Running one of the wizards To use the software, launch one of the application wizards under MS Windows 2000 or XP.

Use the task bar commands Start > Programs > Dotted Eyes to launch one of the applications:

• InterpOSe for Digimap® Process; or • InterpOSe for Digimap® Validate If you try and launch another instance of an application wizard on the same system, the existing one will simply appear in front of any other application windows.

2. Processing the data

Make sure there is plenty of space on your hard disk(s) for the output tables and any temporary files that the software may create during processing. The attribute data may require a lot of storage space.

Remember that your operating system may have a limit on the maximum size of any individual file. Your GIS or mapping system may also impose a limit on the size of each output table, as it will generally need to maintain a set of pointers to associate map features with attribute data.

To run the InterpOSe processing wizard, start by closing all applications in Windows to free up resources. Use the task bar command Start > Programs > Dotted Eyes > InterpOSe for Digimap® Processing or use a desktop shortcut if there is one.

The wizards make it easy for you to change a number of settings. If InterpOSe has already been used on your system, the wizard will remember the most recently used settings.

The first step of the wizard confirms which of the InterpOSe licence options you have. It includes a hyperlink to the Dotted Eyes web



site, which includes up to date information about InterpOSe and various companion products.

If you try and launch another instance of the wizard on the same system, the existing one will simply appear in front of any other application windows.

From any step of the wizard click the Cancel button, or press the Esc key, to close InterpOSe without starting the processing.

Identifying the order summary

Enter the name of the contents order .txt file or click the folder button and pick the required file. The order file contains details of the files supplied as part of your EDINA supply, and parses these to InterpOSe for processing.

While the cursor is over the box, a tool tip displays the complete name, even where it is too long to appear within the box.

Displaying the order summary This step displays the specification of the order, as read from the contents file.



Selecting the input files

From the list of files taken from the contents file, either select to process all files, or select a subset of files. To adjust the selection of multiple files, hold the Shift or Ctrl key as you click a file name.

While the cursor is over the box, a tool tip displays the complete name, even where it is too long to appear within the box.

InterpOSe will process the selected input files from each folder in alphabetical order of their file names.

Any selected input files that do not contain the appropriate 'header' information for OS MasterMap will be ignored.

Specifying the output format This step specifies the format of the output tables.

For many formats you can also choose between the Standard or Short names specified for the attribute columns in the parameter wizard. For the ESRI Shape format, the Short name will always be used.



For .dwg or .dxf output, InterpOSe will create a separate set of drawings containing the features from the ITN Layer, with _ITN appended to each file name.

The two MapInfo formats use graphic styling for each feature according to the parameter file specified in a later step.

The two CAD formats use editable graphic styles inherited from a template drawing that is specified in the next step.

The ESRI shape format cannot store graphic styling, but you can adopt the default styling by installing the ArcGIS v8.x/9.x style file option. The style settings for layers will be saved in the current Map document .mxd file. You can also create layer .lyr files that refer to the data files on your system and automatically apply the styles each time they are loaded into a map.

InterpOSe can write ESRI shape files for the equivalent of the Leeds City Council area, but the file format is not suitable for any larger area.

After writing the output files you are recommended to build the optional spatial index for each .shp file.

• In ArcView v3.x, display the Theme Table for each file in turn and select the Shape column, then use the menu command Field > Create Index.

• In ArcCatalog v8.x or 9.x, select each file in turn and use the menu command File > Properties, then choose the Index tab and click the Add button.

If you choose .dwg or .dxf output, InterpOSe will only be able to process the OS MasterMap data as a full supply. The following paragraphs describe how to maintain an updated holding and extract it in any format, including .dwg or .dxf.

Setting the AutoCAD options This step will appear only if you have picked the AutoCAD Drawing (.dwg) or the Drawing eXchange Format (.dxf) option in the Output format step. It controls format-specific options.

Enter the required name or click the folder button beside the Template file box and pick the required file. This file contains layer styles, blocks and text fonts that define the graphic styles inherited by features in the output files.

Each layer specified in the parameter file must have a corresponding layer in the template file: names need to be identical also when it comes to upper and lower case used.

The line style required for each layer should be set in the template file.

Template files can be created and edited in AutoCAD and saved as template drawings. All layers in the template drawing are included in the output files, even if some of them contain no features.



However, any drawings that would contain no features in any of the layers will not be output.

Different versions of AutoCAD have provided various ways of storing attribute data within drawings. Pick the required Attribute storage option.

Selecting the output tables This step will appear in the processing wizard only if you have chosen an output format other than Fast feature store (.ffs).

This step enables you to check or uncheck the various output tables to be written during processing.

To tick all the checkboxes in the top group, click the Select All button. To clear all the checkboxes in the top group, click the Clear All button.

InterpOSe does not remember any previous settings of the checkboxes in the list of output tables.

The tables in the lower list are metadata tables in the specified output format. These are not available if you have chosen either .dwg or .dxf format.

• The Change History table is a cross-reference of all the Change Date and Reason For Change attributes for every feature that has been output.

• Scroll down to see the Validation Vault checkbox, which must be ticked if you intend to use the validation wizard. This table contains the TOID, Version and Version Date attributes of all processed features that have not been written to any other output tables.



Specifying the output folders This step specifies the output folders.

CAUTION – InterpOSe will over-write without warning any existing files with the same names as those it is creating in the output folders.

The default folder for temporary files is determined by the TEMP environment variable in your system.

Processing will generally be faster if the temporary files and the output tables are on a local disk drive, preferably not the same one as the input files so the disk head does not have to skip between them continually.

Enter the appropriate folder name or click the Folder button and pick the required folder. To create a new folder, pick its parent folder and click the Make New Folder… button.

Metadata files This step specifies the path of the log file and, if you have requested them, the order summary (in the same format you have specified for the output tables) and audit report.

Enter the appropriate file name or click the folder button and pick the required file.

When using a parameter file you have edited, you can obtain additional information on how it is operating by putting a tick in the Include statistics on how many features match each rule checkbox.

If a file with the same path as the log file already exists, you will be asked when the processing starts whether to overwrite it.

ITN reference database This step specifies the folder for storing the reference database containing ITN data, which is made up of a set of feature feeder



(.ff2) files, used to internally construct the ITN output tables. This is automatically deleted once processing is complete.

InterpOSe extracts the ITN data into ‘flat files’ in your selected output format, ready to use in GIS or mapping software. This enables ITN data to be visualised and queried effectively, though it does involve some duplication of information and requires more storage space.

• If you are processing input files that do not include the ITN Layer, or you do not wish to output any ITN features, choose the option to Ignore any ITN features in input files and process only the other Layers.

• In the processing wizard the option to Load features into reference database but and continue extraction into output tables will extract the ITN data into the final output tables.

Processing will generally be faster if the reference database is on a local disk drive, preferably not the same one as either the input or the output files. InterpOSe continually checks the reference database, using a number of indexed tables, so fast access to this information is particularly important in achieving good performance.

ITN cross reference and bridges If you are using the Load ITN features into reference database and continue extraction into output tables option, this step specifies which (optional) cross-reference and cartographic bridge tables are to be output for ITN data.

Cross-reference tables can be created to define the joins between various objects in the ITN relational data model, unless you are using .dwg or .dxf output format. InterpOSe uses many of these relationships to create ‘flat file’ output tables.

The Road Network theme of the ITN Layer does not specifically define bridges where one road crosses over another. InterpOSe can create two output tables to portray bridges cartographically:

• Locations of upper level bridges, either using fixed-size symbols or drawn so as to scale with the map – according to a setting in the parameter file; and

• Copies of short sections of the upper level road links either side of a bridge, intended to be drawn as a separate layer immediately on top of other road links, to achieve correct cartographic portrayal.



W Se u

here roads cross each other at three or more levels, InterpOses only the top-most level for the bridge output tables.

Processing of chunks This step will appear only if you are using the processing wizard and

ut files step.

either the .dwg

selected more than one file in the Inp

It determines whether to merge all the input files into one set of output tables, or create a set of sub-folders and divide the output between them. It will not appear if you have selectedor .dxf output format, which never merge input files.

Use the checkbox to choose whether to retain copies of any features that are duplicated in two or more geographic chunks whose edges they cross.

l tables, though the Gazetteer table is never divided because it

, one for each It will create within each folders, named after the middle

T e an ne set of tables

semble each

When processing only one input file, the processing wizard does not check for duplicate features – and this step is not displayed.

For modest volumes of data (total size of input files less than, say, 100MB for .gz or 2GB for .gml) choose the first option: One set of

tables, stored in each folder for output files. These tables will be written directly to the output folder(s) specified in the Output foldersstep.

The other option divides the output for larger volumes of data into severais intended for searching.

The following option is available:

• Divide into sub-foldersof the output folders a set of sub-part of the input file names (e.g. TQ1234-5). Where two or more chunks have the same middle part in their file names, InterpOSe merges together the contents of those input files.

o merge or split geographic chunks into different sizes, or to mergd split non-geographic chunks into tiles, choose O

and use one of the Tile options in the Output files step.

If you process a full supply into .tab format and divide the output tables, InterpOSe builds MapInfo seamless tables that asset of divided output into a single layer in a mapper window. You can achieve a similar effect in ArcGIS v8.x or above by creating a group layer for each set of themes stored in the various sub-folders.

Discarding duplicate features Different techniques are used to detect duplicate f

When using the option for One set of tables, d

eatures:

• uplicate features more

ly process a very large number of input files on a

• which the centre of the feature’s

ent

are considered only where they cross the edges of two orinput files. The method used to decide which feature to retain is arbitrary.

This mode requires a large amount of memory and may not successfulsystem with limited resources.

When using one of the Divide options, each sub-folder will contain only those features for bounding box lies within the bounding box of the Query Extdefined by the sub-folder.



As a result, if you use one of these options to process an area smaller than national coverage of Great Britain, a few features near the edge of your area will be omitted from the output tables.

Choosing output file options This step determines whether the area being processed will be output

ons. You can use es directly.

as One set of files…, suitable for GIS applicatithese output tables to apply change-only updat

The alternative is to use Tiles, in which features may optionally be clipped at tile edges.

Tiles are a convenient way of using OS MasterMap data in CAD drawings, because they can be loaded into memory one by one. Producing them requires substantial system resources and may take

into tiles.

IS v8.x or above by creating a group layer

some time.

In Autodesk formats, ITN features will be in separate drawings fromfeatures in the other OS MasterMap Layers. Road_Box features will not be sliced

If you process a supply into .tab format and slice the output into tiles, InterpOSe builds MapInfo seamless tables that assemble each set of tiles into a single layer in a mapper window. You can achieve a similar effect in ArcGfor each set of themes stored as tiles.

When you choose to Slice into tiles… or Extract a single tile…, each output file name will relate to the South West corner of the tile – as in Land-Line – with the one at the bottom left being based on the name of the input chunk.

You can choose Extract a single tile… only if you are processing just one input file. Specify the tile origin (South West corner) either as Easting and Northing coordinates in metres or as an alphanumeric grid reference.

By default the tile origin is the South West corner of the input file.

Catalogue settings This step controls the optional catalogue file. That is a metadata table in the specified output format. For geographic chunks the

ion corresponding to the Query been processed.

catalogue contains a polygon regExtent of each chunk that has

Each chunk will have attribute information, as specified in the parameter wizard, such as its Change Since Date.



While the cursor is over the Catalogue File name, a tool tip displays the complete name, even where it is too long to appear within the box. Enter the file name or click the folder button beside the Catalogue file box and pick the required file.

If you are using the processing wizard, you can include a set of columns recording the number of features of each type that were supplied in the various input chunks. To do so, tick the Include counts of each type of feature checkbox.

The feature types are listed in Section 4: Understanding the data. The catalogue feature counts may not be the same as the number of features in the output tables because, for example, duplicate features may have been discarded.

If a catalogue file already exists in the specified folder, you can either Replace the existing file or Add to the existing file.

Click the Finish button to display the Import Progress dialog box and start the processing.

Processing progress and log Information on the progress is updated every few seconds. The number of features processed in that time will vary from one feature to thousands of features, depending not only on the speed of your system but also on the complexity of the features.

If the progress display appears to have stalled, InterpOSe may be processing an unusually complex feature. This may also be a broken polygon – which means that the same geometry will be supplied for many different features that have ‘bled’ into each other.

To abort the process, click the Abandon button.

If you chose in an earlier step to slice the output into tiles, each input file is first written to a temporary file with a spatial index. For each of the tiled output files in turn, all intersecting features are selected and clipped to the edge of the tile. The progress indicator will display the name of each output file as it is being written.

If you are writing to MapInfo .tab format, InterpOSe will display a warning message when any of the files are approaching the maximum size limit of 2GB, as files above this size will not be usable in MapInfo Professional.



There are three options: click Yes to abandon the run to get a file that contains the data processed up to the point of the warning message. Click No to continue the processing with the risk of ending up with an unusable file or click No to All to achieve the same as when clicking No as well as suppressing any further messages.

At the end of the process, the Import Progress dialog box will display the message Completing output files… while InterpOSe finishes the processing and closes down. This may take a considerable time, particularly when writing a large number of output tables.

When the process has finished, if you want to review the InterpOSe log, click the View Log button in the message box. Otherwise, click the Exit button.

You may use a text editor such as Notepad at any time to open the log file.

3. Understanding the data

TOID and flat file feature types Each feature can be uniquely identified by its TOID and Version attributes.

Some OS MasterMap Layers (including Topography and Address) consist of a ‘flat file’ structure containing the following feature types:

• Topographic Point; and Topographic Line; and • Topographic Area; and • Cartographic Symbol; and•

• Cartographic Text; and • Boundary Line; and • Address Point; and • Departed Feature (just in change-only updates).

cluding the

and attribute

objects in the real world – such as bench marks, culverts and

Feature routing to output tables

Departed features consist only of certain attributes, inTOID – with bounding box geometry, where that is supplied – because their sole purpose is to enable the corresponding features (previously supplied) to be identified and removed.

All the other feature types consist of both geometrydata.

Sometide lines – are represented by two or more features, each with their own TOID attributes, which may belong to different feature types.

In general Topographic Area features (other than pylon, cliff and

bes this as a topological complex and calls it a structuring layer with the name Topography.

slope regions) form a complete blanket covering the extent of your data holding, with no regions overlapping each other.

Chapter 2.3 of the OS MasterMap User Guide descri



Where the Broken attribute is set to “True” for a line or polygon, tfeature was in the course of being edited by Ordnance Survey whethe .gz or .gml input file was created. This may result in a set of identical polygo

he n

n region features (on top of each other) or a polyline

to an output table

n regions of the

u rent

r wizard.

•

he Topo_Line

•

tative s part of Land-Line but are not

•

tion to place rotated text on the (invisible)

•

ofessional or ESRI ArcView or ArcGIS to search for

T

feature with gaps between two or more sections.

For an explanation of the reasons for these inconsistent features, see Chapter 2.3 of the OS MasterMap User Guide.

The default.itp parameter file routes each feature whose name is similar to the feature type, with these exceptions:

• The Carto_Area output table contains polygoTopographic Area feature type that have the Descriptive Term “Pylon”, “Cliff” or “Slope”, and should always be displayed above the Topo_Area output table.

The default styles for Landform features (Cliff and Slope) use transparent hatch patterns to avoid obscuring Pylon features. Yocan configure the software to separate these features into diffeoutput tables by using the paramete

The Carto_Line output table (set to be omitted in the default.itp parameter file) contains tide lines of the Topographic Line feature type that have the Physical Presence “Edge / Limit”, as these are equivalent to a very similar set of features in toutput table that have a valid Height Above Datum but no Physical Presence attribute.

The Area_Centroid output table (set to be omitted in the default.itp parameter file) contains symbols derived from the Topographic Area feature type which simulate the represensymbols that were supplied aincluded in OS MasterMap data.

The Area_Mosaic output table contains symbols derived from the Topographic Area feature type which fill the areas with a mosaic of drawn symbols.

• The Text_Centreline output table (set to be omitted for some output formats in the default.itp parameter file) contains lines derived from the Cartographic Text feature type, suitable for use with the Autolabel funccentre-line.

The Gazetteer output table contains (invisible) symbols derived from the Cartographic Text feature type, including only the Index Name attribute. You can use the Ctrl + F shortcut in either MapInfo Prnames in this table and centre the map accordingly.

hemes and feature codes Each feature belongs to one or more themes, as recorded in the Theme attribute. Themes provide a convenient means of marketing,

h since April 2004 there the Topography Layer

ation.

fining the edges of roads, tracks e

mapping and overlay analysis.

eats le

at contain no category.

In case you have any applications that rely on the four-digit feature code used in Land-Line, the default.itp parameter file inserts that

pricing and supplying OS MasterMap, thoughas been a single price to cover all themes inof OS MasterMap.

The Theme attribute has limited value in the resulting .gz or .gml files. A feature’s theme(s) can generally be deduced from its Descriptive Group attribute, though in some circumstances they do add further inform

The Topographic Line features that form the boundary of a Topographic Area feature belong to the same theme(s) as the area feature, in addition to their own theme(s). This means, for example, that you can select all the lines deand paths by selecting Topographic Line features whose Themattribute includes the category “Roads Tracks And Paths” as part of the list.

Traditionally in data products, feature codes are generally used to categorise features. This categorisation is necessary for such purposes as routing features to layers, applying graphic styles, thematic

The Feature Code in OS MasterMap takes no account of some significant attributes such as Make or Physical Presence, and trvalues of attributes such as Descriptive Term that contain multipcategories as being equivalent to those th

The Feature Code attribute is not recommended for classifying features in OS MasterMap, as it does not allow sufficient discrimination.



code as the first four characters of the Legend attribute for featurin the Topography Layer. Two dummy feature codes are also use9999 means that the feature’s attributes do not match any ofspecified rules,

es d:

the and 0000 means that its attributes had no equivalent

in Land-Line.

ITN normalised feature types There are two themes in the first stage of the ITN Layer of OS MasterMap.

You cannot place an order for the Road Routing Information theme

ng feature types:

with point geometry.

consists of the following

ry. tional point. th two points.

an optional point.

ute is omitted from the ITN output tables by ed in other

without also having the Road Network theme.

The Road Network theme consists of the followi

• Road with bounding box geometry. • Road Node• Road Link with polyline geometry. • Information Point with point geometry. • Ferry Terminal with no geometry. • Ferry Node with point geometry. • Ferry Link with no geometry.

The Road Routing Information theme feature types:

• Road Node Information with no gep

omet• Road Link Information with an o

n wi• Road Partial Link Informatio Road Route Information with •• Road Partial Route Information with two points.

The Theme attribdefault, as the information it contains is duplicatattributes.

Classification by categories The feature type identifies features in the Address Layer and Address Layer 2, and up to seven attributes classify those fe

• Structure Type. • Physical Status.

atures:

(Address Layer 2 only). yCount (Address Layer 2 only).

Layer, and various tributes are used to classify those features,

e feature type:

the software). .

oncatenated by the software). ransferred by the software).

ansferred by the software).

tures in the

bly belongs to one feature type and may tegory value for the Make and Physical dnance Survey describes these attributes as

ality.

have multiple cardinality. Descriptive Group re values and Descriptive Term may have zero

s for with a

es, the categories in the list appear in a

• PQAccuracy (Positional Quality indicator). • Postcode Type. • Match Status. • Land Use Group• MulitOccuopanc

The feature type identifies features in the ITNcombinations of atdepending on th

• Geometry Rendering. • Descriptive Group. • Descriptive Term. • Nature of Road. • Number of Links (counted by • Environment Qualifier

Vehicle Qualifier (c• Primary Indicator (t•

• Trunk Indicator (tr

The feature type and four attributes classify feaTopography Layer:

• Descriptive Group. • Descriptive Term. • Make. • Physical Presence.

Each feature invariaoptionally have one caPresence attributes. Orhaving single cardin

Some other attributes may have one or moor more values. These multiple values form a list of categorieeach attribute. The software separates the categories in the list semi-colon followed by a space (; ).

In the .gz or .gml input filrandom order. For example, one feature’s list of Descriptive Term categories might be “Boulders; Nonconiferous Trees” and another’s “Nonconiferous Trees; Boulders”. These two lists are intended to



have the same meaning, as no significance is attached to the order of the categories.

You would expect both these features to have a consistent description and appearance in your GIS or mapping system. The software facilitates this by enabling you to specify a category precedence order for Descriptive Group, Descriptive Term and Theme. All the categories in an attribute list are sorted according to the precedence order specified in the parameter file.

Rules-based classification The software uses a set of rules to process each feature according toits permutation of categories. The actions taken by these rules are:

Routing the feature to one or more output table(s)

• .

Determining how the feature is rendered in each of those output

he following ing”,

P “Obstructing”.

e in scriptive Group (and optionally

ameter the data. For example, if your primary

ory precedence

a given e.

rder

r

e.g. Descriptive Group •

tables.

• Defining the graphic style of the rendered feature in each table, where the output format permits.

For example, a Topographic Line feature may have tpermutation of categories: Descriptive Group “BuildDescriptive Term “Outline”, Make “Manmade” and Physical

resence

The feature classification rules take into account only the first valu the sorted list of categories for De

also for Descriptive Term). The first of any semi-colons, and everything after it, will then be ignored by the rules.

The order of categories in the sorted list is specified in the parwizard to suit your use ofinterest is in vegetation you may assign a higher precedence to “Nonconiferous Trees” than to “Boulders”. If you are more concerned with geology, you may wish to reverse that order.

If any categories other than those defined in the categorder are encountered during processing, they will be added at the end of the sorted list for that attribute. They will also be recorded in the log file, so you can consider whether to edit the category precedence order for future processing.

If any categories occur more than once in an attribute list forfeature, the repeats will be removed and recorded in the log fil

As each feature is processed, its feature type is identified and its categories are compared against the rules for that feature type, following the sequence of rules in the parameter file. The first rule that matches the appropriate permutation of attributes determines the actions which will be taken for that feature.

The national TOID density model for pricing defines a precedence order for Theme categories. These are reflected in the default parameter files. Ordnance Survey has not defined a precedence ofor Descriptive Term.

The default.itp parameter file uses an optimised precedence order foDescriptive Group categories. For any other order of Descriptive Group categories, you will generally need additional feature processing rules that may appear illogical (“Inland Water” with Descriptive Term “Scrub”).

Columns of attribute data The software can transfer the attribute data from the input files to the output tables, according to the settings in the parameter wizard.

The attributes in OS MasterMap that are described as ‘complex’ byOrdnance Survey are all presented by the software as

a set of simple

attributes.

tables may be arranged in valid for the output table

of Ordnance Survey’s current editing methods, the

The columns of attribute data in the outputany order, using any column names that are format.

The Version attribute of a feature is incremented every time the feature is changed within the Ordnance Survey Mercury editing database (the Geospatial Object Server).

As a resultVersion may increase by two or more when a single logical change is implemented. This means you cannot rely on sequential Version numbers in OS MasterMap to check for all published changes to a feature.



The Version Date attribute defines when the current version of thfeature was loaded into the Mercury database. This is generally lthan the Latest Change Date.

e ater

eason

Change history data

The software can include the Latest Change Date and Latest Rfor Change attributes for each feature in the output tables, and it ensures that these values relate to the most recent change event.

OS MasterMap includes a record of Change Date and Reason for Change, which together form a complex attribute called Change

The history of changes may become very extensive for some e contains its entire record of

de since the previous version.

g session, and checked to ensure that each Change History ins some

.dwg

History.

Ordnance Survey plans to supply a full history of changes throughout the life of every feature.

features. Every version of a featurchanges, not just the changes ma

The software can store all the changes for each feature in a changehistory table, without any geometry. This is updated at every processinevent is stored only once, even where OS MasterMap contaduplicate Change History events.

The change history table is not available if you have specifiedor .dxf output format.

The Version column in the change history database contains the feature’s Version when the processing wizard first encountered that Change History event in your data holding. This may not be the same as the Version at the time the change event was first recorded by Ordnance Survey.

Values of numeric attributes The Font attribute in the Cartographic Text feature type containsnumerical values in the range 0 to 3, though their meaning for OS MasterMap has not been defined.

InterpOSe and SuperpOSe use the same concept of feature classification rules for Cartographic Text as for all other feature types.

The software defines the attributes Height Above Datum and Height enables you to sort that include them

guish between a known value of d for a

is limitation could lead to confusion if zero were used to represent

es other than the Multiple Occupancy Count Type

used for assigning Height Above Datum in OS

Above Ground Level as numeric data types. Thisthe values correctly and use algebraic expressionsin calculations.

MapInfo Professional uses as its native format a version of the dBase .dbf file. This does not distinzero and an unknown value or blank – no standard is define‘null’ value.

Tha null value, as it could not then be differentiated from a true value of zero. Where the input file has no value the software uses a negative value in the form -9,999 to represent a null value in all numeric attributfor Address Point which uses the value 1.

For bench marks and spot heights, where a value is given for the Height Above Datum attribute, the value may not be reliable.

The process MasterMap was to identify the appropriate text annotation closest to the feature and associate its value. Occasionally, the wrong annotation may have been identified, resulting in a valid but incorrect value for Height Above Datum.

4.

s must world

The output tables defined in the default parameter file are described below. It is important to understand the data structure before making any configuration changes to a parameter file that will affect the output tables.

Default ITN output tables

Unlike the Topography and Address Layers of OS MasterMap, the ITN Layer uses a normalised database structure in which joinbe made between a number of features in order to model realobjects.



In MapInfo software, if the ITN Info symbols are coloured squares rather than as ‘road signs’, see th

rendered as e section entitled

Installing the software for details of how to install the custom

orkMember_Xref

symbols into the correct folder.

NetwA Road feature is supplied with no geometry. It has a Road Name – which may be a DfT Number, or a name, or a list of names in multiple languages if they are recorded by Ordnance Survey.

Each Road feature consists of a collection of Network Membervalues that are references by TOID to the set of Road Link features.

A road in the real world may be represented by no Road feature no Road Name or DfT Number i

(if s known to Ordnance Survey), or

one Road feature, or multiple Road features (if the road has at least one name and a DfT Number or the Descriptive Term “Trunk Road” and/or “Primary Route”).

Ordnance Survey has not reconciled the Road Name attribute either with Cartographic Text features in the Topography Layer or with the Thoroughfare or Dependent Thoroughfare attributes in the Address Layer.

The NetworkMember_Xref output table is a lookup table, without any geometry, that consists of one row for each combination of Road TOID and Road Link TOID.

Road_Box The geometry supplied in the .gz or .gml input files for each named Road feature is a bounding box enclosing the polylines of all the associated Road Link features. That bounding box is included in thoutput table.

is

world that does not have either a name or a DfT ded in this output table, as it is not represented

There may be several bounding boxes on top of each other for the same road in the real world, if it has at least one name and a DfT Number or is a Trunk Road and/or Primary Route.

Any road in the real Number is not incluby a Road feature in the ITN data.

References to a set of Network Member values are included in theNetworkMember_Xref output table.

Road_Line For each named Road feature, the software renders a polyline

top of each other for the same

ute.

Any road or path in the real world that does not have either a name s not included in this output table, as it is not oad feature in the ITN data.

put table is ideally suited for finding a named road/path or -

ibute is set to be indexed

consisting of the combined polylines of all the associated Road Link features.

There will be multiple polylines onroad in the real world if it has at least one name and a DfT Numberor is a Trunk Road and/or Primary Ro

or a DfT Number irepresented by a R

References to a set of Network Member values are included in theNetworkMember_Xref output table.

This outthe junction of two named roads – for example by using the doubleampersand (&&) operator in the Find command of MapInfo Professional. For this reason the Name attrin the default.itp parameter file.

Ferry A Ferry Node feature consists of a point at the start or end of one or

Ferry

more Ferry Link features.

A Ferry Link feature is supplied with no geometry, and the softwarerenders a straight-line topological connection between two Node points.



Road_Node A Road Node feature consists of a point at the start or end of one or more Road Link features.

Each Road Node includes a reference by TOID to a Topographic Area feature in the Topography Layer of OS MasterMap.

Road_Node_Info A Road Node Information feature is supplied with no geometry. It

features using the point geometry from

Link_TopoArea_Xref

consists of a reference by TOID to a Road Node feature.

The software renders thesethe associated Road Node feature.

A Road Link feature includes a collection of Reference to

etween junctions) or multiple

Road Link features (if it is part of a junction).

able is a lookup table, without one row for each combination of

Topographic Area values that are references by TOID to a set of Topographic Area features in the Topography Layer of OS MasterMap.

A section of road in the real world may be represented by one RoadLink feature (if it is part of a link b

The Link_TopoArea_Xref output tany geometry, that consists of Road Link TOID and Topographic Area TOID.

Road_Link A Road Link feature consists of a polyline that joins two Road Node points.

The software adds DfT Number and Road Name attributes to the Road Link feature, with values taken from the associated Road features.

Any Road Name vletter A, B or M ar

alues that contain a numeral and start with the e transferred to a separate DfT Number column in

TOID to a set of Topographic Area features in the

the Link output table.

References byTopography Layer of OS MasterMap are included in the Link_TopoArea_Xref output table.

Road_Link_Info Road Link Information and Road Partial Link Information

ature types.

supplied with either no geometry or a point at a vertex on the associated Road Link polyline

rmation feature is supplied with two .

es,

nders

at the same location, the software does not render any

ame

e

features include a reference by TOID to a Road Link feature.

The direction of traffic flow is not significant for these fe

A Road Link Information feature is

feature.

A Road Partial Link Infopoints at vertices on the associated Road Link polyline feature

The software renders Road Link Information features as polylinif they do not contain point geometry in the .gz or .gml input files.

For Road Partial Link Information features, the software rethe part of the polyline between the two points. If these two points coincidepolyline.

There will be multiple polylines on top of each other where the ssection of road or path in the real world has more than one type of restriction in the ITN data.

There may be multiple values for the Date Time Qualifier, Vehicle Qualifier and Environment Qualifier. The software concatenates thappropriate values into lists separated by semi-colons.

Road_Link_Info_Pt The software renders Road Link Information features as points, if they contain point geometry in the .gz or .gml input files.



Road Partial Link Information features are supplied with two points. If these two points coincide at the same location, the software renders only one symbol at that location.

All other Road Link Information and Road Partial Link Information features can also be rendered as points at the start and

k polyline feature – or whichever part

y both a

where two or rictions in

end of the associated Road Linof it is defined in the input files.

This means, for example, that a section of road in the real world that is subject to a Traffic Calming restriction may be marked bsymbol at each end and a polyline tracing the approximate road centre-line.

There will be multiple points on top of each other more sections of road in the real world meet, and have restthe ITN data.

DirectedLink_Xref Road Route Information features include references by TOID to an ordered set of directed Road Link features.

Road Partial Route Information features include a reference by TOID to a Road Link feature.

The direction of traffic flow is significant for these feature types, and is defined as either + or – with respect to the digitised direction.

table is a lookup table, without any row for each combination of Road

The DirectedLink_Xref outputgeometry, that consists of one Route Information TOID and directed Road Link TOID.

Road_Route_Info A Road Route Information feature is supplied with either no geometry or a point at a vertex on one of the associated Road Link polyline features.

A Road Partial Route Information feature is supplied with two points at vertices on the associated Road Link polyline feature. If

these two points coincide at trender any polyline.

he same location, the software does not

e same

TN data.

, where required. This means that directional

Vehicle t Qualifier. The software concatenates the

There will be multiple polylines on top of each other where thsection of road in the real world has more than one type of restriction in the I

The software renders these features as polylines using geometry from the associated Road Link feature(s).

The digitised direction of a Road Route Information feature is automatically reversedline styles can be used to portray One Way streets and similar items.

There may be multiple values for the Date Time Qualifier,Qualifier and Environmenappropriate values into lists separated by semi-colons.

Road_Route_Info_Pt The software renders Road Route Information features as points, if they contain point geometry in the .gz or .gml input files.

Road Partial Route Information features contain two points. If these two points coincide at the same location, the software renders only one symbol at that location.

an also be rendered as points, nd of the first associated Road

rld that

Link features.

in the real world.

Other Road Route Information cwhich the software creates at the eLink polyline feature in the specified direction.

This means, for example, that a road junction in the real wois subject to a “No U Turn” restriction may be marked by both a symbol at the junction and a polyline tracing the prohibited route defined by a directed set of Road

There will be multiple points on top of each other where two or more restrictions in the ITN data coincide, for example if there areseveral restricted turns at the same road junction



Upper_Level_Bridge The software checks the Start Grade Separation and End Grade Separation attributes of every Road Link feature to identify bridges over other roads, including grade-separated interchanges.

evated Road Link features (with paration attribute) meet, the

ation

Upper_Level_Road_Link

At each Road Node where two elnon-zero values of the Grade Sesoftware renders a cartographic bridge symbol, rotated to the appropriate angle.

The Upper_Level_Bridge output table includes the Orientattribute calculated by the software.

Where the software identifies a bridge carrying one road over another, it can also create a copy of a short road link either side of the bridge.

raphic portrayal of roads at g their relative levels.

ps on cased lines, and you can select all the features

These features are suitable for the cartoga grade-separated interchange, showin

The style of each link feature is inherited from the Road Link features adjacent to the bridge. In MapInfo Professional this may include end-cain this output table and edit their line styles without altering the colours.

5.

After using InterpOSe to load an initial supply, you can check and report on the correctness and completeness of the output tables in your data holding.

This requires the appropriate TOID List file from EDINA. Each file is supplied as a set of files in compressed .gz format (up to 10MB in size) which contain a comma-separated list of the TOID, Version and Version Date attributes of features which should be present.

was supplied as part itial supply or change-

only update. It is not possible to obtain a FVDS except as part of a

ata file, which in the default.itp parameter file is

terpOSe Validate or use a desktop shortcut if

e Dotted Eyes web site, which includes up

Data holding validation

The only FVDS you should use is the one thatof the most recently processed order for an in

particular order.

Any features that were not routed to an output table must be recorded in a metadcalled Validation_Vault.

Validation will take a significant amount of time and computer resources, particularly for a large data holding, as it checks every individual feature.

To run the validation wizard, if you have already processed OS MasterMap data, start by closing all applications in Windows to freeup resources. Use the task bar command Start > Programs > Dotted Eyes > Inthere is one.

The first step confirms which of the licence options you have. It also provides a hyperlink to thto date information about the software and various companion products.



Selecting the FVDS files This step specifies the folder containing the FVDS files anand filename of the text file that will contain a report on tcompleteness of your data holding.

d the path he

S files. Tick the Process the FVDS files in any sub-folders within this folder checkbox to read every sub-folder and check for FVD

Specifying the data format This step defines the file format of your data holdingcontaining your data holding.

Tick the Process data files in any sub-folders within this focheckbox to read every sub-folder and check all the files ispecified format. If those include an archive of supersedethe wizard may report discrepancies in the Version attribute o

lder n the

d features, f

features.

Identifying the parameter file This step identifies the parameter file that was used to process the data holding and the folder for storing temporary files used during the validation process.

and the folder



Click the Finish button to create the report on your current data holding.

Validation progress and report The process of checking runs through the following steps:

• Read all the FVDS files • Create a TOID index to speed the search • Read all output tables and check their contents • Check for features in FVDS not in output tables • Display summary of correctness and completeness • Produce report file listing details of discrepancies.

To abort the process, click the Abandon button.

The validation wizard tests for Correctness and Completeness. Information on the progress is updated every few seconds while the checking takes place.

When each test is complete, there is a visual indication of the rate of defects in parts per million (ppm):

• Green tick: zero defects; or

• Yellow query: defects up to 1 ppm; or

• Red cross: defects of more than 1 ppm.

Checking causes of defects Defects reported in your current data holding may be due to various reasons:

• Was your FVDS supplied by Ordnance Survey as part of the most recent order you have processed? If not, validation would not be appropriate.



• Did you process the full supply with a version of InterpOSe earlier than v4.0? Alternatively, have you cleared the checkbox for the Metadata output table whose name in the default.itp parameter file is Validation_Vault? If so, your data holding may be correct, but features which were not routed to any ‘normal’ output tables will not be listed in the metadata table, so validation may not produce the correct result. You should either process your full supply again and apply all the change-only updates, or order a new full supply and start again, ensuring that the Validation_Vault checkbox is ticked.

• Was the processing abandoned, either by clicking the Abandon button or automatically as the size of any output table approached the MapInfo limit of 2GB or the hard disk became almost full? If so, it is likely that some features were not written to the output files. You should repeat the processing, using one of the options to Divide the output between folders, clearing the Discard duplicate features checkbox if you are processing geographic chunks for an area less than the whole of GB.

• Had any of the input files become corrupted before processing? If so, some features may not have been read by the processing wizard, and they will be reported in the log file. You should order a new supply from Ordnance Survey.

• Were any features rejected by the processing wizard? If so, those features will be reported in the log file. This is unlikely if you have used the default.itp parameter file. You should contact [email protected] sending the validation report and the log file from the processing wizard.

• Have you edited or deleted any output tables since processing? If so, some features that were written to the output tables may no longer be present. You should either process your full supply again and apply all the change-only updates, or order a new full supply and start again.

• Did you fail to specify the same Output folder and Parameter file in the validation wizard as in the processing wizard? If so, the validation wizard may not have read all the relevant output tables. You should check the log file from the processing wizard, and use the information it contains to run the validation wizard again with the correct settings.

• When ordering change-only updates, did you fail to specify the Query Change Since Date to be the same as or earlier than the Extraction Date of your previous order? If so, there is a temporal gap in the changes you have applied. You should either apply a change-only update with a Query Change Since Date that is early enough, or alternatively order a new full supply and start again.

• When ordering change-only updates, did you leave a very long gap (more than, say, six months) between consecutive orders? Alternatively, have you ever processed a change-only update without following the correct chronological order? If so, features which should have been added to your holding, and then later removed, may still be present. You should order a new full supply and start again.

• Have you ever processed an area less than the whole of GB, using the topological polygon format, and applied a change-only update? If so, some Topographic Line features outside the area you ordered (which were required to close Topographic Area features crossing the edge of the area you ordered) may not have been removed. You should order a new full supply using the independent polygon format and start again.

• Have you processed geographical chunks for an area less than the whole of GB, ticking one of the options to Divide the output between folders, and also ticked the checkbox to Discard duplicate features? If so, features whose centroids did not lie within any of the chunk extents will not be included in any of the output tables, nor in the Validation_Vault metadata table. You should process your full supply again and apply all the change-only updates, clearing the Discard duplicate features checkbox in each case.

• Have you processed different types of order (e.g. covering different areas or distinct Layers of OS MasterMap data) into the same database using SupepOSe, or the same output folders using InterpOSe? If so, the most recent FVDS file for every type of order must be read at the same time. You should copy those FVDS files into sub-folders and tick the Process FVDS files in any sub-folders within this folder checkbox when running the validation wizard.


mailto:[email protected]


Appendix I Copy of licence agreement

By running the Setup program you indicate that you accept the terms of this licence agreement.

1. Licence. This Software is licensed on condition that you, the Customer, agree to the terms set out in this agreement. These terms supersede and replace any other terms and conditions, including any that may be supplied with the Customer’s order form. If you do not agree to the terms of this agreement you may return the package, with a signed declaration that the Setup program has not been run and no copies of the Software have been taken, within thirty days for a full refund. In consideration of payment of the licence fee, Dotted Eyes Limited agrees to grant and the Customer agrees to accept on the following terms and conditions a non-transferable and non-exclusive licence to use the Software installed by the Setup program.

2. Restrictions on use. Staff and students of the Customer are licensed to make internal use of the Software on any number of computers exclusively for the benefit of the teaching and research activities of the Customer and not to provide a bureau service for others, or for the benefit of or on behalf of any others whether by way of commercial projects or otherwise. The Software is licensed solely for the purpose of processing OS MasterMap data supplied by the Digimap service operated by EDINA and may not be used for processing data obtained direct from Ordnance Survey nor from any other source. Neither the licence granted under this agreement nor the Software to which it applies may be assigned, sub-licensed, rented, leased, lent or otherwise transferred by the Customer to any others without the prior written consent of Dotted Eyes Limited.

3. Back-up copies. The Customer may make up to four copies of the Software for operational security and back-up purposes but shall make no other copies of the Software.

4. Copies of printed material. The Customer may not copy, in whole or in part, any Software documentation or related materials in printed form. Additional copies of such materials may be purchased from Dotted Eyes Limited at the charges current at the time.

5. Modifications. The Customer may not modify, adapt, translate, reverse engineer, decompile, disassemble or merge within another programme any portion of the Software or create derivative works based on the Software.

6. Copyright. The Software and explanatory materials are copyright of Dotted Eyes Limited, and may not be published or transferred to any other party, in whole or in part, without the prior written permission of Dotted Eyes Limited. The Customer agrees not to remove any copyright notices or any confidential or proprietary legends from the Software or the output tables

and the Customer agrees to reproduce such notices and legends on any copy of the Software made by the Customer as permitted herein. Copyright is not transferred to the Customer by this Agreement.

7. Nondisclosure. The Customer agrees not to provide, disclose or otherwise make available in whole or in part, the Software to any person or organisation other than the Customer, its staff, students or its professional advisors, for the purposes necessary to the Customer’s business. The Customer further agrees that all copies of the Software will be strictly safeguarded against disclosure to or use by persons not authorised by Dotted Eyes Limited to use such software and that the Customer will take steps as are necessary to ensure that the provisions of this agreement are not violated by any member of staff or students of the Customer or its professional advisors.

8. Duration and termination. The licence under this agreement is effective from the date on which the Customer receives the Software and shall remain in force until terminated by either party. Dotted Eyes Limited may terminate this licence at any time if the Customer fails to comply with any of the terms of this agreement, if the Customer fails to pay on time any fees due under this agreement, or if the Customer becomes insolvent or has a bankruptcy order made against him, or if he shall pass a resolution for winding-up or have a petition for winding-up presented or have a receiver or manager appointed of his undertaking or any part thereof. If the Customer transfers possession of any copy, partial copy, modification or merged portion of the Software to another party, this licence is automatically terminated.

9. Consequences of termination. Upon termination of this agreement the Customer shall immediately cease use of the Software and shall destroy or deliver to Dotted Eyes Limited the original and all full or partial copies of the Software. Termination shall not relieve the Customer of the obligation under this Licence agreement, including, without limitation, its obligations regarding the confidentiality of Software.

10. Limitations of warranty and liability. Dotted Eyes Limited makes no warranties, either express or implied, with respect to the Software, its quality, performance, merchantability or fitness for any particular use. The Software is licensed ‘as is’ and with all faults. In no event will Dotted Eyes Limited be liable for indirect, incidental or consequential damages resulting from any defect in the software even if Dotted Eyes Limited has been advised of the possibility of such damages. Dotted Eyes Limited does not warrant that the Software will meet the Customer’s requirements or that the Software will be error free.



Appendix II Topography Layer vs Land-Line

For users familiar with Land-Line, the large-scale topographic product derived from the Ordnance Survey TOPO dataset, this Appendix highlights some comparisons with the OS MasterMap Topography Layer.

This was created from the TOPO dataset by largely automatic methods. A substantial amount of manual checking and editing was undertaken as part of the Quality Improvement Flowline (QIF) both before and after the initial release of OS MasterMap in November 2001.

However, the very large size of the database – around 434 million features, derived from some 230,000 TOPO tiles each containing a Digital Map Unit (DMU) – means that the QIF could only address a proportion of the inevitable limitations arising from automated production.

The new characteristics of the OS MasterMap Topography Layer that are most immediately apparent are:

• The geographical extent of an order may be any polygon, rather than a group of preset tiles.

• There are options as to which data structure is used to express polygons and which size is used for the geographic chunks.

• Polygon region features form a key part of OS MasterMap, whereas the TOPO dataset (and therefore the Land-Line product) does not include any regions.

• Arbitrary polygon closing links have been inferred to create regions from the linework in the TOPO dataset. In future versions of OS MasterMap, network closing links will also be created, for similar reasons.

• The national data set is stored without tiles and therefore without varying nominal scales, and the data is supplied in arbitrary chunks defined for a specific customer order.

Features are not clipped at the edges of geogra• same feature may be supplied in two or more chunks.

• In the verbose .gml format the files would be very large (perhaps 20 times the size of Land-Line in .ntf format) so Ordnance Survey actually supplies compressed .gz files or data streams.

• After the initial full supply Ordnance Survey does not publish updates, though customers with maintenance agreements may collect updates by downloading files as often as they wish.

• Downloaded files contain change-only updates that have to be applied to the current data holding in order to create an updated holding. If you need to re-create a base map as it was at some past date, the options are to keep a back-up copy of all the processed data, to assemble an archive of superseded features, or to adopt a geospatial database including archive tables.

• Each feature has many more attributes and its classification is determined by a permutation of categories held as descriptive attributes, rather than by means of its numeric Feature code (which provides less information in OS MasterMap than in Land-Line).

phic chunks, so the

tation text in OS MasterMap is defined in ground

feature depicted in Land-Line are not present in the

been omitted. An optional

es

• secondary (FC0035) are generally

• The five-digit Feature code in OS MasterMap is not sufficient for classifying features. The default.itp parameter file in InterpOSe and SuperpOSe adds the four-digit feature code that was supplied with Land-Line.

The size of anno• units, as there is no specified nominal scale. In Land-Line, the text height is assigned varying plot sizes at the three nominal scales (1:1 250, 1:2 500 or 1:10 000) and these sizes are reflected in OSMasterMap.

Some kinds of OS MasterMap Topography Layer:

Road centre-lines (FC0098) have • Integrated Transport Network (ITN) Layer has recently been added to OS MasterMap. TranspOSe software from Dotted Eymay be used to process OSCAR Asset-Manager road centre-lines, or the ITN (Integrated Transport Network) Layer of OS MasterMap may be used.

Vegetation/landform limits –depicted as landform.



• Marginal text has been omitted, and this was the only means by which administrative area names (included in FC1005) were recorded. In due course a further OS MasterMap Layer is expected to provide a set of boundary polygons to supplement or replace the current boundary lines. Meanwhile, TranspOSe software from Dotted Eyes may be used to process Boundary-Line for use with OS MasterMap.

• Building, glasshouse and upper level of communication seeds (FC0321, FC0323 & FC0395) have been omitted, as they may be inferred from the attributes of polygon areas. InterpOSe and SuperpOSe can create a set of symbols to simulate the seed points. To add further value, TranspOSe software from Dotted Eyes may be used to process ADDRESS-POINT, or the OS MasterMap Address Layer or Address Layer 2 may be used.

• Archway cross lines (included in FC0052) have been omitted, as they may be inferred from the attributes of areas. InterpOSe and SuperpOSe can create symbols and use a hatch pattern to simulate the cross lines.

• Seed points and symbols indicating a number of types of land cover (e.g. Water seed FC0400 & Orchard FC0386) have been omitted, as they may be inferred from the attributes of areas. InterpOSe and SuperpOSe can create symbols and use fill patterns to simulate the seed points and symbols.

• Land parcel numbers have been omitted. They have not been maintained in the TOPO dataset for some years, but are still supplied in Land-Line. Ordnance Survey recommends that users should associate data with map features by using the TOID and Version attributes rather than land parcel numbers.

Some new features have been constructed from information of a

ptive Term “Pylon” in Descriptive

with Descriptive Term “Switch” in Descriptive Group

different type in Land-Line:

The area feature with Descri• Group “Structure” replaces the symbol in Land-Line that has a defined size.

The symbol• “Rail” replaces the short line perpendicular to the rails in Land-Line (though in some cases the line remains unchanged).

• The symbol with Descriptive Term “Culvert” in Descriptive Group “Inland Water” replaces the short line perpendicular to the watercourse in Land-Line.



Appendix III ITN Layer vs OSCAR Asset-Mgr

For users familiar with OSCAR Asset-Manager, the Ordnance Survey Centre-line Alignment of Roads taken from the large-scale ROADS dataset, this Appendix highlights some comparisons with the first phase of the OS MasterMap ITN (Integrated Transport Network) Layer.

The new characteristics of the OS MasterMap ITN Layer that are most immediately apparent are:

• The geographical extent of an order may be any polygon, rather than a group of preset tiles.

• There is a new option of the Road Routing Information theme, containing information on driving restrictions.

• The data is supplied in arbitrary chunks defined for a specific customer order, and the chunk size may be varied.

• Features are not clipped at the edges of geographic chunks, so the same feature may be supplied in two or more chunks.

In the verbose .gml format the files would be very large• Ordnance Survey actually supplies compressed .gz files or data streams.

After the i

so

nitial full supply Ordnance Survey does not publish

be st

• ITN Layer of OS

s only at a specific vertex or

data.

tended to include

• updates, though customers with maintenance agreements may collect updates by downloading files as often as they wish.

Downloaded files contain change-only updates that have to • applied to the current data holding in order to create an updatedholding. If you need to re-create a base map as it was at some padate, the options are to keep a back-up copy of all the processed data, to assemble an archive of superseded features, or to adopt a geospatial database including an archive table.

Defined life cycle rules apply to features in the MasterMap. These ensure that the same TOID attribute will persist where possible, with the Version number being incremented when the feature is edited.

• Minor roads are distinguishable from local streets, both of which have the same feature code in OSCAR.

• Each feature has many more attributes and its classification is determined by a permutation of categories held as descriptive attributes, rather than by means of its numeric feature code.

• A normalised database structure is used to model the road network and restrictions information in ITN data. This means, for example, that Road Link features do not have a Road Name or DfT Number attribute, though InterpOSe can re-create such attributes.

• The Level attribute defining grade separation was supplied as part of the Road Node feature in OSCAR, but has been transferred to the Road Link feature in ITN data.

Some restriction information applie• for a specific part within a polyline feature.

Information on ferries is included in ITN •

In subsequent releases the ITN Layer will be ex• such features as railways, pedestrian routes and navigable inland waterways.



Appendix IV Address vs ADDRESS-POINT

For users familiar with ADDRESS-POINT, the large-scale data product derived from the Ordnance Survey ADDRESS dataset, this Appendix highlights some comparisons with the OS MasterMap Address Layer.

The Address information in OS MasterMap was created from the ADDRESS dataset and the NBDS (National Buildings Data Set) by largely automatic methods.

The new characteristics of the OS MasterMap Address Layer that are most immediately apparent are:

• The geographical extent of an order may be any polygon, rather than a group of preset tiles or postcode districts.

• Names of buildings, streets and localities in OS MasterMap now come from more than one source – Cartographic Text features recorded by Ordnance Survey, Road features recorded independently by Ordnance Survey, largely from observed signs, and Address Point features derived from the PAF (Postcode Address File) maintained by Royal Mail. There are numerous differences between these sources that have not been reconciled, even though OS MasterMap is described as a definitive data product.

• The Delivery Point Suffix (added to the postcode to create a unique key for each address in the PAF) is included in OS MasterMap.

• A Positional Quality Text attribute is included, with values of either “Provisional” or “Final”. This does not add any additional information, because its value depends only on the Positional Quality Type.

The Refere• nce To Feature TOIDTopographic Area feature that corresponds to a building associated with each address. This link was previously avfree of charge as part of the NBDS.

• Amended addresses are available as part of the OS MasterMap change-only update regime, without waiting for the next ‘frozen’ product release.

attribute contains the of a

ailable



Appendix V Address Layer 2 vs Address

For users familiar with the original Address Layer of OSMM, this Appendix highlights some comparisons with Address Layer 2.

• Change metadata is included for Address Layer 2, bringing it into line with all the other Layers of OS MasterMap.

• Valuation Office Agency unique IDs – a cross-reference for users interested either in contacting Valuation Office Agency directly about Council Tax and Non-Domestic Rates information, or in contacting Local Authorities via Intelligent Addressing, the custodian of the National Land & Property Gazetteer which also contains these IDs.

• Ordnance Survey BS7666 Part 3:2000 address – a geographical alternative address for BS7666 users, with the street derived from the OS MasterMap ITN Layer and the locality, town and administrative area derived from versions of Boundary-Line.

• Classification - what the address is addressing.

The Address and MOWPA themes have the following additions:

• Current Royal Mail unique IDs – the address key and organisation key attributes currently present in the ADDRESS-POINT PEX (PAF Extension) product.

New Royal Mail unique • Point Reference Number) in the Address themes and the UMRRN (Unique Multi-Residence Reference Number) in the MOWPA theme; the intended replacements for the current Royal Mail IDs

The Address theme also has the following additions:

IDs – the UDPRN (Unique Delivery

.

ve thoroughfare

• – any alternative premises details which

• and locality details approved by Welsh Local Authorities for some delivery points in Wales.

Royal Mail Alias address

Royal Mail Welsh Delivery Point address – alternati

are known by Royal Mail.

• Royal Mail True PO Box Address – the true address of the PO Box owner, where this is known by Royal Mail (rather than the address of the sorting office containing the actual PO Box).

• Ordnance Survey Alternative address – any variant premises or thoroughfare details collected by the Ordnance Survey field surveyor in the process of positioning Royal Mail addresses.

Appendix VI Comparative glossary of terms

This glossary compares some terms that may have slightly different meanings when used in different GIS software packages.

MapInfo ESRI AutoCAD Oracle

Output table

Layer or table

Theme or layer

Layer Table

Feature Object Feature Entity Row

Attribute/property

Column Field Field Column

Bounding box

Minimum bounding rectangle

Extent Extents Minimum bounding rectangle

Vertex (pl Vertices)

Node Vertex or node

Vertex or node

Ordinate

Point Point Point Point Point

Symbol Point Point Block Point

Drawn symbol

Polyline Polyline Block Line or multiline

Mosaic Polyline Polyline Blocks Multiline

Polyline Line or polyline

Polyline Line or polyline

Line or multiline

Region Region Polygon Closed polyline

Polygon

Text Text N/A Text N/A



Appendix VII Styles in the feature catalogue



Integrated Transport Network Layer


interpose userguide digimap a4

Documents

tool tip displays

south west

integrated

largely automatic

local disk

normalised

itp parameter

drawing exchange