This driver treats a directory as a dataset and attempts to merge all the .NTF files in the directory, producing a layer for each type of feature (but generally not for each source file). Thus a directory containing several Landline files will have three layers (LANDLINE_POINT, LANDLINE_LINE and LANDLINE_NAME) regardless of the number of landline files.
NTF features are always returned with the British National Grid coordinate system. This may be inappropriate for NTF files written by organizations other than the UK Ordnance Survey.
Landline (and Landline Plus): LANDLINE_POINT LANDLINE_LINE LANDLINE_NAME Panorama Contours: PANORAMA_POINT PANORAMA_CONTOUR HEIGHT attribute holds elevation. Strategi: STRATEGI_POINT STRATEGI_LINE STRATEGI_TEXT STRATEGI_NODE Meridian: MERIDIAN_POINT MERIDIAN_LINE MERIDIAN_TEXT MERIDIAN_NODE Boundaryline: BOUNDARYLINE_LINK BOUNDARYLINE_POLY BOUNDARYLINE_COLLECTIONS The _POLY layer has links to links allowing true polygons to be formed (otherwise the _POLY's only have a seed point for geometry. The collections are collections of polygons (also without geometry as read). This is the only product from which polygons can be constructed. BaseData.GB: BASEDATA_POINT BASEDATA_LINE BASEDATA_TEXT BASEDATA_NODE OSCAR Asset/Traffic: OSCAR_POINT OSCAR_LINE OSCAR_NODE OSCAR Network: OSCAR_NETWORK_POINT OSCAR_NETWORK_LINE OSCAR_NETWORK_NODE Address Point: ADDRESS_POINT Code Point: CODE_POINT Code Point Plus: CODE_POINT_PLUSThe dataset as a whole will also have a FEATURE_CLASSES layer containing a pure table relating FEAT_CODE numbers with feature class names (FC_NAME). This applies to all products in the dataset. A few layer types (such as the Code Point, and Address Point products) don't include feature classes. Some products use features classes that are not defined in the file, and so they will not appear in the FEATURE_CLASSES layer.
The layers are based on a low level feature type in the NTF file, but will generally contain features of many different feature codes (FEAT_CODE attribute). Different features within a given layer may have a variety of attributes in the file; however, the schema is established based on the union of all attributes possible within features of a particular type (ie. POINT) of that product family (ie. OSCAR Network).
If an NTF product is read that doesn't match one of the known schema's it will go through a different generic handler which has only layers of type GENERIC_POINT and GENERIC_LINE. The features only have a FEAT_CODE attribute.
Details of what layers of what products have what attributes can be found in the NTFFileReader::EstablishLayers() method at the end of ntf_estlayers.cpp. This file also contains all the product specific translation code.
FEAT_CODE: General feature code integer, can be used to lookup a name in the FEATURE_CLASSES layer/table. TEXT_ID/POINT_ID/LINE_ID/NAME_ID/COLL_ID/POLY_ID/GEOM_ID: Unique identifier for a feature of the appropriate type. TILE_REF: All layers (except FEATURE_CLASSES) contain a TILE_REF attribute which indicates which tile (file) the features came from. Generally speaking the id numbers are only unique within the tile and so the TILE_REF can be used restrict id links within features from the same file. FONT/TEXT_HT/DIG_POSTN/ORIENT: Detailed information on the font, text height, digitizing position, and orientation of text or name objects. Review the OS product manuals to understand the units, and meaning of these codes. GEOM_ID_OF_POINT: For _NODE features this defines the POINT_ID of the point layer object to which this node corresponds. Generally speaking the nodes don't carry a geometry of their own. The node must be related to a point to establish it's position. GEOM_ID_OF_LINK: A _list_ of _LINK or _LINE features to end/start at a node. Nodes, and this field are generally only of value when establishing connectivity of line features for network analysis. Note that this should be related to the target features GEOM_ID, not it's LINE_ID. On the BOUNDARYLINE_POLY layer this attribute contains the GEOM_IDs of the lines which form the edge of the polygon. POLY_ID: A list of POLY_ID's from the BOUNDARYLINE_POLY layer associated with a given collection in the BOUNDARYLINE_COLLECTIONS layer.
GENERIC_POINT GENERIC_LINE GENERIC_NAME GENERIC_TEXT GENERIC_POLY GENERIC_NODE GENERIC_COLLECTIONGeneric products are primarily handled by the ntf_generic.cpp module whereas specific products are handled in ntf_estlayers.cpp.
Because some data products (OSNI datasets) not from the Ordnance Survey were found to have record groups in unusual orders compared to what the UK Ordnance Survey does, it was found necessary to cache all the records of level 3 and higher generic products, and construct record groups by id reference from within this cache rather than depending on convenient record orderings. This is accomplished by the NTFFileReader "indexing" capability near the bottom of ntffilereader.cpp. Because of this in memory indexing accessing generic datasets can be much more memory intensive than accessing known data products, though it isn't necessary for generic level 1 and 2 products.
It is possible to force a known product to be treated as generic by setting the FORCE_GENERIC option to "ON" using OGRNTFDataSource::SetOptionsList() as is demonstrated in ntfdump.cpp. This may also be accomplished from outside OGR applications by setting the OGR_NTF_OPTIONS environment variable to "FORCE_GENERIC=ON".