Home

1.6MB pdf: OSCAR family product user guide v4.2

1. NENNEN OSCAR family product user guide chapter 2 V4 2 03 2005 Crown copyright Page 18 Feature position The centrelines in the parent database are positioned during survey but are not guaranteed as being absolutely central The dataset is no more accurate than the source mapping Digital mapping is an abstract representation of the real world and the road centreline does not represent a physical feature on the ground therefore its shape is partly subjective The coordinates of the OSCAR Asset Manager data are quoted to a resolution of 1 m e OSCAR Traffic Manager is filtered with a 2 m lateral filter Links representing road centrelines in OSCAR Asset Manager and OSCAR Traffic Manager have sufficient accuracy to ensure they will fall within the road pecks edge of road as depicted on Ordnance Survey basic scale maps Feature codes The geometry of links and nodes within OSCAR data would be meaningless unless they are assigned some distinguishing property Each feature is classified by means of a feature code FC These feature codes are allocated when each feature is initially interpreted and captured from source Thus an A road is distinguished from a motorway by the feature code allocated to it The feature code will be changed if the road is reclassified Feature codes are listed in chapter 6 Feature attribute data An attribute is a descriptive characteristic of a f
2. ed 47 Database eco cl ota IU IE 47 NIseieaWieo e CON 5 nate paied dag saat chute betbaueaiedalndnsnied E E T 48 Soole NES Ere e ae ia at 48 Node feature Ems 49 SECHOMMOAY TEC ORAS nl o A cds aa 49 How the section body is arranged cece teeter tent een eem eene eren nennen R RR nennen nennen nne 50 Data SUP PIV SEUCTUTG CEDE 51 SUPPLY of data on formatted medja sictir upahi iaie CERA TIAMANA nE EE ERAS RARO ARANA Aten 51 Chapter 7 Record structures for the transfer of OSCAR IN INT sirios banned Ris vieatarandenceninaadeas 53 IN TFS CONCISE oy EP 53 Volume Fleader Record VOL D REC Of sites ccc sts ave snag Ete reet im t eie trito a E ca 54 Database Header Record DBFREG Dl viii oia las 55 Feature Classification Record FEAT CLASS 5 e eterne retten ras 57 section Header Record SEGHREG 07 crio been terr Reden tie ke sas ene ck tane dose dd dir ea mE ec Peu ine Ee Deko e ER eae d 58 Atmibute Record ATT REC VA wcectccstges 60 Attribute Record AIRE VA M rS 61 Point Record POINTREC TS iper EE 62 Node Record NODEREC oer 63 Geometry Record GEOMETRY T 2 5 1 a in detecte kde oda AERE VENAN AAE RE dd cain ae nrbe pu A dee cue c g 64 Line RECOFG LINE REC 23 PP 65 Attribute Description Record ATTDESC 4D sicut iit a dia 66 Comment Record COMMENT ESTO 68 Volume Termination Record VOLETERM 99 die iduesies b Ie neue neto tur
3. 38 Chapge ntormialiofl es e seus iens re ieccthes acteansccnesGevenapsas sey Rea Ea E E aE EE C E a a rA e V M EE M ENIM LU EE ETE 38 Attribute CONOS qr 39 A A RETE LL LL 39 Data classificationiand Meta cuc TE cp 40 deae camur E 40 ayy OSCAR family user user guide contents v4 2 03 2005 Crown copyright Page 5 Junction name CIN MM IT PEE 40 HTS TAU EO T 41 OSODR OB e oa ies acts ca cote ce se ce MEM MI AN 41 Proper name PN wens E m 41 A s sea teri e tasted eiua e ILE LI IP EI MEI ILE AA 41 SOUFCE Scale SO T T 42 Settlement name CON ssepe tesutes este aa aege a Ea E cae atau S aa aee eA ea a Ea a aA eR 42 Trunk roads Riran EE 42 Grade Serio 43 NTE AU ITS e CC c E 44 Attribute AO CATION aiccsiese c E 45 Feature code FC allocations and descriptiOliS ctl bida ds netus tagen fans ct cir 46 TransterSel Structure E E E 4T VOMUME TECOS cir
4. 25 jesse 26 B M DEM 26 Ness E m 26 ES A E E EE E E E E A A A E TE E A T 26 AttriD tes NOGES csccicsis sccavaaecotsuastes sduwexenesscis iaiaaeaia ai Aada EEEE AEA AAS ENAN A AAAS AEEA EOE e OTEO Aaaa 26 Ordnance Survey ROADS Database Reference OSODR iicet cevaekecutvacshedavaeh a ane ava tod redone 27 Accuracy and ME SONU OM E EE 29 COMPICION qe 29 Chapter 5 OSCAR tile numbering and the Natonal Gra ptos LA Aon sat arsed lease palito Et nee 30 Chapter 6 NTF explained viii Em 31 An overview Rose dB TEUER 31 eremitae REEIe aaepe LEE 32 Data ATO CLS hs EM 33 Jackson Struct e UEM 34 VEFSIONEIMANAG SIMON iss e 35 A EET 35 igote togae E E M P RE 35 DEDE EO E E E EE EAEI A A 35 OSCAR information relevant to INT Fernado en noh ex a renei AEA ep aE aE Ea EEEE LORA ia E EEE E eA a Oaa TEE EEEE 36 ella MIU S EET ELLE DL LEE 36 o Lxx M 37 COMES c ME
5. ATTREC line For completed tile follow by Node feature POINTREC GEOMETRY1 node ATTREC node NODEREC For completed tile o I y a YM M d H Jo n x Page 50 OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Data supply structure Supply of data on formatted media Data supplied on CD ROM or other logically formatted media is not blocked but is written directly to the output device The transfer set has one dataset and one section One or more transfer sets are put onto the medium If your order is larger than the capacity of the medium it is put onto two or more of that media Continuation volumes are only used if a transfer set is larger than the capacity of the medium Formatted media transfer set less than media capacity 01 VOLUME HEADER RECORD 01 02 DATABASE HEADER RECORD 40 ATTRIBUTE DESCRIPTION RECORD 07 SECTION HEADER RECORD Tile 1 data 99 VOLUME TERMINATION RECORD 01 VOLUME HEADER RECORD 01 02 DATABASE HEADER RECORD 40 ATTRIBUTE DESCRIPTION RECORD 07 SECTION HEADER RECORD Tile 2 data 99 VOLUME TERMINATION RECORD and so on Tile n data 99 VOLUME TERMINATION RECORD 99End Of Transfer Set0 OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 51 Formatted media transfer set greater than m
6. This chapter and chapter 2 provide an introduction to the OSCAR product family and illustrate potential applications Chapter 3 contains more detailed information about OSCAR Please refer to the glossary at appendix A if you are unfamiliar with any of the terms used All aspects of OSCAR discussed in this user guide relate to OSCAR in BS 7567 NTF v2 0 Level 3 Full technical information on OSCAR data format is contained in chapters 6 and 7 Example data graphics in this user guide have been manipulated to aid clarity Other data where added is fictitious OSCAR an introduction The OSCAR product family is an Ordnance Survey data product that provides a digital representation of the road network of Great Britain derived from a single source Ordnance Survey s ROADS database OSCAR Asset Manager has centrelines of all publicly accessible and maintained roads Private and pedestrianised roads have been included where possible Centrelines fall within road casings defined within Ordnance Survey Land Line e OSCAR Traffic Manager has a 2 m filter with road junctions restructured to mirror the positioning of vehicles passing through them OSCAR family product user guide chapter 1 V4 2 03 2005 Crown copyright Page 8 OSCAR features The OSCAR product family are supplied as vector data in a link and node structure where links are road centrelines and nodes are intersections of links with attributes attached to ea
7. defines the topological relationship between links and nodes 21 Two Dimensional Geometry Record defines the two dimensional geometry for a link or node 23 Line Record identifies the definition of a link 40 Attribute Description Record defines attribute descriptions and their fields 90 Comment Record transfers change information or information about empty tiles 99 Volume Termination Record defines the end of the transfer set NOTE REC DESC record descriptor See appendix B for information on NTF records for OSCAR Traffic Manager when supplied with Address Ranges HMM OSCAR family product user guide chapter 7 V4 2 03 2005 Crown copyright Record name VOLHDREC DBHREC FEATCLASS SECHREC ATTREC POINTREC NODEREC GEOMETRY1 LINEREC ATTDESC COMMENT VOLTERM Page 53 Volume Header Record VOLHDREC 01 Field REC DESC DONOR RECIPIENT TRANDATE SERIAL VOLNUM NTFLEVEL NTFVER NTFOR EOR DIVIDER CONT MARK EOR Position 01 02 03 22 23 42 43 50 51 54 55 56 57 57 58 61 62 62 63 63 64 64 65 65 66 66 Record example 01 ORDNANCE SURVEY Format A2 A20 A20 DATE l4 I2 11 R4 2 A1 A1 A1 I1 A1 Value example 01 ORDNANCE SURVEY lt 5S gt 208 YYYYMMDD 0000 01 3 0200 V lt S gt 0 Description Not used Date of processing Not used Incremented for each
8. 6 V4 2 03 2005 Crown copyright Page 33 Jackson structure Figure 6 1 depicts an example of an OSCAR file No fixed record sequence or relationship is implied Key TRANSFER one or more SET o selection VOLUME VOLHDREC 01 DATABASE VOLTERM 99 DBHREC 02 ATTDESC 40 FEATCLASS 05 aco te SECTION SECHREC 07 CHANGE SECTION INFORMATION BODY COMMENT 90 FEATURE o o LINE NODE POINT FEATURE FEATURE FEATURE OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 34 Version management Product version Each version of OSCAR is defined by a unique product specification The product version number can be found in OSCAR data in the FCNAME field of the Database Header Record DBHREC The product version number takes the form xx yy where xx is the major product number and yy is the minor change number Thus version 03 02 would indicate that this is major product version 3 and contains the second minor amendment to the product specification This user guide reflects the product specification current at the time of its production The effective date of this product specification is 1 January 1994 and is indicated by the FCDATE field of the Database Header Record DBHREC Product release Each release of OSCAR is defined by a unique reference number The product release number appears in the Database Header Record DBHREC in the field DBNAME The product release number takes
9. Name of settlement Whether a link is a trunk road OSCAR family product user guide chapter 6 Page 44 Attribute allocation Not all attributes are applicable to all features and therefore some attributes may not be present in certain attribute records OSCAR Asset Manager and OSCAR Traffic Manager use the following attributes These attributes are compulsory and will always be present Line attributes FC LL OD SC Node attributes FC OD These attributes are optional and may be present in any combination Line attributes FW PN RN TR Node attributes JN SN See appendix B for information on OSCAR Traffic Manager with Address Ranges o queue ww A OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 45 Feature code FC allocations and descriptions The feature code FC attribute defines the type of feature which the link point or node record represents The following feature codes are used in NTF for supply of OSCAR products to represent or depict FC 3000 FC 3001 FC 3002 FC 3004 FC 3007 FC 3008 FC 3009 FC 3010 FC 3500 FC 3501 Motorways Roads classified by the DfT as A roads Roads classified by the DfT as B roads Minor or other roads which form part of the highway network including C roads Non network roads These are roads which do not form part of the current highway network For example this could b
10. PN VALUE mt A Road name DIVIDER T A1 VAL_TYPE ROT A2 RN VALUE ES A Road number DIVIDER nm A1 VAL_TYPE m A2 TR VALUE us A1 Trunk road indicator VAL TYPE mE A2 FW VALUE A A1 Form of way VAL TYPE pis A2 PU VALUE ie A Postcode unit DIVIDER T A1 VAL_TYPE po A2 LR VALUE Ed A Left address range DIVIDER n A1 VAL_TYPE Lm A2 LX o ee OSCAR family product user guide appendix B V4 2 03 2005 Crown copyright Page 86 Field Position Format Value example Description VALUE xe A Left building text name DIVIDER Tm A VAL_TYPE n A2 LA VALUE T A Left single address DIVIDER Tn A VAL_TYPE A2 RG VALUE Tem A Right address range DIVIDER s A1 VAL_TYPE A2 RY VALUE a A Right building text name DIVIDER 2m A1 VAL_TYPE ES A2 RF VALUE me A Right single address DIVIDER s A CONT_MARK 32 32 I1 0 No further records EOR 33 33 A1 96 Record terminator Record example 140000180DO2ARX1Y42NBFVFC3004SCALL00369PNCALVERT ROAD LR21 121 0 1 LR00125 121 003 O 2NLA127 3 RG2 44 E 1 RY46A 2 RY46B 31RG48 52 E ANRG58 94 E 5NO amp 1 2 3 4 5 6 7 8 12345678901234567890123456789012345678901234567890123456789012345678901234567890 Template OSCAR family product user guide appendix B V4 2 03 2005 Crown copyright Page 87 Data classification and metadata NTF attributes The following NTF codes are used in the supply of Address Ranges Attribute co
11. data is supplied in the British Standard national format common to the majority of Ordnance Survey s digital map data products namely NTF and is transferred in Level 3 as variable length records An overview of the data structure of an OSCAR data file is shown on page 34 in diagrammatic form The convention used for this diagram is in the industry standard adopted for Jackson Structured Programming JSP The British Standard for BS 7567 NTF v2 0 stipulates the following for Level 3 This level supports a variety of data models that may include network data polygons semantic relationships and complex features for example a school consisting of its buildings and playing fields This level is designed for transferring basic geometry and simple features through the use of geometry and feature records e relating basic geometrical and topological elements to one or more features through the use of chain polygon and complex line records combining features to form complex features through the use of collection and complex polygon records using text records both to relate text strings to features and cartographic output and e referencing and positioning external features for example raster data The record structure at this level may also be defined to be compatible with data in Levels 1 and 2 The governing body for the industry standard NTF is now the British Standards Institution BSI Their adaress is 389 Chiswick Hi
12. format for Ordnance Survey digital map data node An object representation of a point which either does not form any part of a link isolated node or polygon seed point or is the representation of a point at the start or end of a link terminating node The position of a node is defined by a single coordinate pair which is repeated within all links logically connected at that node and or containing it A node is only deleted if the link containing it as a terminating node is deleted node and link structure See link and node structure data object A collection of entities which form a higher level entity within a specific data model For example a group of entities defining a drainage system point A zero dimensional spatial abstraction of an object represented as a coordinate pair point feature A zero dimensional spatial abstraction of an object with its position defined by a coordinate pair Points are represented by nodes which may be isolated or part of a link terminating Points may also be represented by symbols which may have attributes such as rotation and size positional accuracy The degree to which the coordinates define a point s true position in the world directly related to the spheroid and or projection on which the coordinate system is based precision The exactness with which a value is expressed whether the value be right or wrong ae uut Smau RC BN OUI RUNE REESE a t OSCAR family product user guide
13. integer Record example 99End Of Volume 01 Transfer Set Continues On Volume 02 1 1 2 3 4 5 6 7 8 12345678901234567890123456789012345678901234567890123456789012345678901234567890 Template Record example 99End Of Transfer Set0 1 2 3 4 5 6 7 8 12345678901234567890123456789012345678901234567890123456789012345678901234567890 Template Notes If there are further volume s to follow then the FREE TEXT field will comprise the following message End Of Volume n Transfer Set Continues On Volume n 1 If there are no further volumes then the FREE TEXT field will comprise the message End Of Transfer Set OSCAR family product user guide chapter 7 V4 2 03 2005 Crown copyright Page 69 Appendix A Glossary accuracy The closeness of the results of observations computations or estimates to the true values or the values accepted as being true Accuracy relates to the exactness of the result and is a measure of the exactness of the operation by which the result is obtained arcs See link ASCII American Standard Code for Information Interchange a standard binary coding system used to represent characters within a computer attribute An attribute is a property of an entity usually used to refer to a non spatial qualification of a spatially referenced entity For example a descriptive code indicating what an entity represents
14. link and node features are derived from primary sources collected by Ordnance Survey See chapter 4 for full information The database from which the OSCAR product family are derived is continually revised OSCAR data structure In each OSCAR product roads and the information associated with them are modelled into a network of links and nodes Links represent all public motorable roads and the majority of private motorable roads with public access in Great Britain Each link has a feature code defining its road classification type Nodes represent all intersections of links link ends and the position where a tile edge cuts the link Links do not stop at tile edges but will traverse those edges to make one contiguous line feature Each line feature will however be made up of a number of link segments contained wholly within their respective tiles and will be further identified by the tile and line reference records All links and nodes have a unique national reference number the Ordnance Survey ROADS Database Reference OSODR This will uniquely identify any link or node within any OSCAR product OSODRs are e acommon and consistent location reference for all of Great Britain and the basis for linking customer features to data Wherever possible the OSODR will remain unchanged on update unless there is a geographic change to the feature enabling consistent referencing to be created between successive releases of OSCAR
15. links link edge or arc Links are the representation of line features They are made up of one or more consecutive non intersecting link segments with common attributes between two terminating nodes Links have no connection with other links except at the start or end via common shared terminating nodes points All links contain their terminating coordinates Links may form the boundaries of polygons and may be shared between polygons See also edge map A holistic representation and intellectual abstraction of geographical reality intended to be communicated for a purpose or purposes transforming relevant geographical data into an end product which is visual digital or tactile megabyte Mb 1 048 576 bytes a measure of data storage capacity model See data model EE OSCAR family product user guide appendix A V4 2 03 2005 Crown copyright Page 74 National Grid A unique referencing system which can be applied to all Ordnance Survey maps of Great Britain GB at all scales It is based on 100 km squares covering the whole of GB based on a Transverse Mercator projection It is used by Ordnance Survey on all post war mapping to provide an unambiguous spatial reference in GB for any place or entity whatever the map scale National Transfer Format NTF A format designed in 1988 specifically for the transfer of spatial information it is administered by the British Standards Institution BSI It is now the standard transfer
16. or how it should be portrayed basic scale The scale at which the survey is undertaken For Ordnance Survey mapping three scales are used 1 1250 1 2500 1 10 000 Any area is only maintained at one basic scale basic scale map The largest scale of map published for a particular area of Great Britain This may be 1 1250 scale for urban areas 1 2500 scale for rural areas or 1 10 000 scale for mountain and moorland areas bit A unit of information the word being a blend of binary and digit byte A unit of computer storage of binary data usually comprising 8 bits equivalent to a character Hence megabyte Mb and gigabyte Gb chain A directed sequence of non intersecting line segments and or arcs with nodes at each end References to left and right area identifiers are optional E OSCAR family product user guide appendix A V4 2 03 2005 Crown copyright Page 70 character A distinctive mark an inscribed letter one of a set of writing symbols coordinate pair A coordinate pair is an easting and a northing coordinates Pairs of numbers expressing horizontal distances along orthogonal axes Alternatively triplets of numbers measuring horizontal and vertical distances Row and column numbers of pixels from raw imagery are not considered coordinates for the purpose of the standard compact disc read only memory CD ROM A data storage medium A 12 cm disc similar to an audio CD contiguous Literally adjacent touc
17. retained at each update e Compatibility with other Ordnance Survey digital products Unique reference points allow the means to coordinate services between different departments agencies and organisations Accurate and reliable routeing and planning information e A common and consistent base for the exchange of road information All attributes feature DfT numbers and names where applicable e All OSCAR products are quality assured and are regularly updated NENNEN OSCAR family product user guide chapter 1 V4 2 03 2005 Crown copyright Page 10 OSCAR applications The OSCAR product family provides a comprehensive topological base of road information for a wide range of applications Possible uses include OSCAR Asset Manager Y LETT E s 44 44 s OSCAR Traffic Manager Y Y Y s NS SS s NS Uses Accident analysis Asset recording and inventory management Catchment area analysis Command and control Defect surveys Derivation of street gazetteers GIS analysis indexing and mapping Highway planning and engineering In vehicle navigation and guidance Linking traffic and travel information Locational referencing Logistics management Real time traffic control Recording street works and other related features Road and highway maintenance Road design Route planning Routeing analysis Scheduling and delivery Site location S
18. service performance report form Ordnance Survey welcomes feedback from its customers about OSCAR Asset Manager and OSCAR Traffic Manager If you would like to share your thoughts with us please print a copy of the form and when completed post or fax it to the address below YOUPNaMES Serii aea UTE TII ITEMS PORE RTT TECTUM Organisation EE c EN do pe iecaes AGOIESS siii FREE TOt FEES a ETE Emaili M POSICOGG sacississiassesssodssndsanssosidsssdsabscacsarsitndeanacansasandssstsabacsasnatasadsasbacagseanicasiaaasaa Please record your comments or feedback in the space below We will acknowledge receipt of your form within 3 working days and provide you with a full reply or a status report within 21 working days If you are posting this form please send it to Customer Contact Centre Ordnance Survey Romsey Road SOUTHAMPTON SO16 4GU Fax 023 8079 2615 OSCAR family product user guide appendix C V4 2 03 2005 Crown copyright Page 90
19. the data are those which have been surveyed and put into road classifications by Ordnance Survey surveyors and updated within the Ordnance Survey data archive o OSCAR family product user guide chapter 4 V4 2 03 2005 Crown copyright Page 29 Chapter 5 OSCAR tile numbering and the National Grid The National Grid provides a unique reference system that can be applied to all Ordnance Survey maps of Great Britain at all scales Great Britain is covered by 100 kilometre grid squares with each square identified by two letters Figure 5 1 Each National Grid square of 100 km by 100 km contains 400 5 km by 5 km HP squares OSCAR Asset Manager and af OSCAR Traffic Manager are supplied to HT HU TO PONN f customers in 5 km by 5 km tiles These are referenced by National Grid letters followed by HW HX HY HZ the appropriate numbers and figures which g obey the 1 10 000 scale sheet numbering OTN convention NA 28 NC ND 5 km square PE NS emm NF NG NH NJNK NL NMZNN NO NW ME 4 N NR UNS NT NU roza NW NXjNY NZ OV mm x 2 Mw SC SD SE TA 10 km square SH SJ SK TF TG e 4 TS m SM SN SO SP TL TM ELL ol SR SS ST SU T TR SV SW sX sY SZ Tv amp CM lo 100 km square OSCAR family product user guide chapter 5 V4 2 03 2005 O Crown copyright Page 30 Chapter 6 NTF explained An overview of OSCAR in NTF OSCAR
20. volume Version 2 0 Variable length records On formatted media Terminates variable length text fields No further records Record terminator 1995110700000130200V 0 1 4 5 12345678901234567890123456789012345678901234567890123456789012345678901234567890 6 7 8 o yA OSCAR family product user guide chapter 7 Template V4 2 03 2005 O Crown copyright Page 54 Database Header Record DBHREC 02 Field REC DESC DBNAME DDNAME DDATE DDBASE DDBDATE CONT MARK EOR Position 01 02 03 22 23 42 43 50 51 70 71 78 79 79 80 80 Format A2 A20 A20 DATE A20 DATE 11 A1 Continuation of Database Header Record Field REC_DESC FCNAME FCDATE DQNAME DQDATE DATA MODEL CONT MARK EOR Record example Position 01 02 03 22 23 30 31 50 51 58 59 60 61 61 62 62 Format A2 A20 DATE A20 DATE 12 11 A1 Value example 02 DEFAULT 02 00 78 19920515 208 00000000 1 96 Value example 00 19940101 in OSCAR Asset Manager only see note 3 208 00000000 00 0 96 Description Database name see note 1 Release date of NTF version being use used Not used Not used Continuation record Record terminator Description Data specification see note 2 Date of data specification Not used Not used Not used No further records Record terminator 020SCAR ASSET 01 0
21. was released in November 1995 and had an attribute database Address Ranges made available in 2000 Currency OSCAR data is derived from the latest version of Land Line Any changes to road information within Land Line are incorporated in each update sweep of OSCAR The ROADS database is continuously revised and updated The currency of the Land Line data is controlled by the revision criteria for topography defined by Ordnance Survey for the various geographic areas Information on new and amended classified roads is obtained from the relevant highways authority through Ordnance Survey s Mapping Intelligence o A OSCAR family product user guide chapter 4 V4 2 03 2005 O Crown copyright Page 25 Specification Features Topology Motorways e links A roads nodes B roads minor roads private roads pedestrianised streets Attributes links Attributes nodes e OSODR e OSODR classification junction name motorways name logical or edge e DfT number e settlement name e trunk road grade separation e form of way Optional database for OSCAR Traffic Manager e multi carriageways Address Ranges roundabouts e slip roads source scale road length IHNEN OSCAR family product user guide chapter 4 V4 2 03 2005 Crown copyright Page 26 Ordnance Survey ROADS Database Reference OSODR Formerly known as Ordnance Survey OSCAR Dat
22. 073 741 824 bytes a measure of data storage capacity grid The planimetric frame of reference For example the National Grid information Intelligence resulting from the assembly analysis or summary of data into a meaningful form ARA ccc WX e crc A OSCAR family product user guide appendix A V4 2 03 2005 Crown copyright Page 73 intersection The intersection of a link segment with a construction segment shot or tape line or of two construction segments A construction point is created at the position of the intersection the internal angle between alignments should be gt 30 junction A connection between two or more links at a common node Junctions may be a crossroads or T junctions line A series of connected coordinated points forming a simple feature with homogeneous attribution line feature The spatial abstraction of an object in one dimension Lines may intersect with other lines They are defined as a series of two or more coordinates and may be curved or straight Curved lines consist of a series of very short straight line segments Lines may be concurrent with other lines under certain conditions As an object abstraction a line has no width link and node data A form of vector data in which linear features are represented as links Links are terminated where they intersect other links These intersection points and link ends may carry nodes whose feature records express the geometric relationships between
23. 1 DEFAULT 02 00 19920515 000000001 O0OSCAR ASSET 01 01 19940101 00000000000 1 4 5 6 7 8 12345678901234567890123456789012345678901234567890123456789012345678901234567890 Template OSCAR family product user guide chapter 7 V4 2 03 2005 Crown copyright Page 55 Note 1 DBNAME will indicate the release number For example it could be OSCAR ASSET followed by the release number in the format xx yy See Version management chapter 6 Note 2 FCNAME will indicate the product version number For example it could be OSCAR ASSET followed by the product version number in the format xx yy See Version management chapter 6 Example of valid contents of DBNAME and FCNAME fields Product DBname FCname OSCAR Asset Manager OSCAR ASSET 02 01 3S OSCAR ASSET 01 01 3S OSCAR Traffic Manager OSCAR TRAFFIC 01 01 S OSCAR TRAFFIC 01 01 S Note 3 In OSCAR Traffic Manager this date is 19990401 o pw ww a J drO rna s OSCAR family product user guide chapter 7 V4 2 03 2005 Crown copyright Page 56 Feature Classification Record FEATCLASS 05 Field Position Format Value example Description REC DESC 01 02 A2 05 FEAT CODE 03 06 A4 Feature classification code CODE_COM 07 16 A10 lt 10S gt Not used STCLAS 17 36 A20 lt 20S gt Not used FEATDES ar A Description of feature class DIVIDER ES Al CONT_MARK ag 11 0 No further records EOR EE A1 96 Record t
24. 23456789012345678901234567890 Template o OSCAR family product user guide chapter 7 V4 2 03 2005 Crown copyright Page 61 Point Record POINTREC 15 Field Position Format Value example Description REC DESC 01 02 A2 15 POINT ID 03 08 l6 Unique id GEOM ID 09 14 l6 Reference to point geometry NUM ATT 15 16 12 01 Number of ATTRECs ATT_ID 17 22 16 Reference to ATTREC CONT MARK 23 23 I1 0 No further records EOR 24 24 A1 96 Record terminator Record example 15000004000006010000010 1 2 3 4 5 6 7 8 12345678901234567890123456789012345678901234567890123456789012345678901234567890 Template o ee OSCAR family product user guide chapter 7 V4 2 03 2005 Crown copyright Page 62 Node Record NODEREC 16 Field Position Format Value example Description REC DESC 01 02 A2 16 NODE ID 03 08 16 Unique id GEOM_ID 09 14 16 Reference to point geometry NUM_LINKS 15 18 14 Number of links at node DIR 19 19 11 1 for start 2 for end GEOM_ID 20 25 16 Reference to link geometry ORIENT 26 29 R4 1 0000 Not used LEVEL 30 30 1 0 1 or2 Link level at node CONT_MARK uu 11 0 No further records or 1 or continuation record follows EOR pi A1 Record terminator variable integer Record example 1600000500000700031000008000002000009000001000012000000 1 2 3 4 5 6 7 8 123456789012345678
25. 4567890123456789012345678901234567890 Template NENNEN OSCAR family product user guide chapter 7 V4 2 03 2005 Crown copyright Page 65 Attribute Description Record ATTDESC 40 Field Position Format Value example Description REC DESC 01 02 A2 40 VAL TYPE 03 04 A2 See table below FWIDTH 05 07 A3 See table below FINTER 08 12 A5 See table below ATT_NAME 13 7 A See table below DIVIDER kal Al FDESC xm A See table below DIVIDER ae Al CONT_MARK ae I1 0 No further records EOR Tue A1 96 Record terminator variable integer Record example 40PN A PROPER NAME Street Name 0 1 2 3 12345678901234567890123456789012345678901234567890123456789012345678901234567890 4 5 6 7 8 Template OSCAR family product user guide chapter 7 V4 2 03 2005 Crown copyright Page 66 Valid contents of ATTDESC for OSCAR products VAL type FWIDTH FC 004 FW 001 JN lt 3S gt Li 005 OD 013 PN lt 35 gt RN 3S SC 001 SN lt 3S gt TR 001 variable integer FINTER ATT type FEAT_CODE FORM_OF_WAY JUNCTION_NAME LINE_LENGTH OSODR PROPER_NAME ROAD_NUM SOURCE SETTLE_NAME TRUNK_ROAD FDESC Feature code Form of way descriptor Name of road junction Length of line feature Unique link identifier Str
26. 90123456789012345678901234567890123456789012345678901234567890 Template o A OSCAR family product user guide chapter 7 V4 2 03 2005 O Crown copyright Page 63 Geometry Record GEOMETRY 1 21 Field Position Format Value example Description REC DESC 01 02 A2 21 GEOM ID 03 08 l6 Reference from NODE or LINE GTYPE 09 09 A1 1or2 1 for node 2 for link NUM COORD 10 13 14 Number of coordinate pairs COORD 14 17 Easting Y_COORD 18 21 Northing QPLAN 22 22 11 lt S gt Not used CONT_MARK s I1 0 No further records or 1 or continuation record EOR PES A1 96 Record terminator variable integer Record example 210045202000934501982 03672003 04562110 03982134 03882452 03852797 03993012 1 0004123642 06783548 0 1 2 3 4 5 6 7 8 12345678901234567890123456789012345678901234567890123456789012345678901234567890 Template o A OSCAR family product user guide chapter 7 V4 2 03 2005 O Crown copyright Page 64 Line Record LINEREC 23 Field Position Format Value example Description REC DESC 01 02 A2 23 LINE_ID 03 08 l6 Unique id GEOM ID 09 14 16 Reference to link geometry NUM_ATT 15 16 12 01 Number of ATTRECs ATT_ID 17 22 16 Reference to ATTREC CONT MARK 23 23 I1 0 No further records EOR 24 24 A1 96 Record terminator Record example 23000027000009010000060 1 2 3 4 5 6 7 8 1234567890123456789012345678901234567890123
27. CAR product family may be customised by viewing or plotting at different scales or with different colours line and text styles to suit your purpose Certain classes of features may be omitted from customised maps on the basis of selection by feature code The resolution of OSCAR supports plotted or displayed output at a range of scales around the nominal scale of the source mapping o O pw LL w A OSCAR family product user guide chapter 1 V4 2 03 2005 Crown copyright Page 14 Figure 1 1 Representation of OSCAR Asset Manager data showing some road name attributes and some DfT road number attributes The highlighted link has the following attributes PROPER NAME LONDON ROAD ROAD CLASS 3002 ROAD NUM B4140 LINE LENGTH 110 OSODR O198QYF5MF2FW SOURCE A OSCAR family product user guide chapter 1 V4 2 03 2005 Crown copyright Page 15 Figure 1 2 Representation of OSCAR Traffic Manager data showing some road name attributes and some DfT road number attributes The highlighted link has the following attributes PROPER NAME LONDON ROAD ROAD CLASS 3002 ROAD NUM B4140 LINE LENGTH 110 OSODR O298QYF5MF2FW SOURCE A NENNEN OSCAR family product user guide chapter 1 V4 2 03 2005 Crown copyright Page 16 Chapter 2 Data overview Basic principles The OSCAR product family is a range of highly specified dig
28. D LINE GEOMETRY1 ATTRIBUTE RECORD ATTREC Each line feature is in the data only once There is one Attribute Record to each line record o quu ww A A OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 48 Node feature Each node feature is represented by the use of the following records Description in NTF POINT RECORD POINTREC GEOMETRY RECORD NODE GEOMETRY1 ATTRIBUTE RECORD ATTREC NODE RECORD NODEREC Each node feature is in the data only once There is one Attribute Record to each Point Record There is one Geometry Record referenced by both the Point Record and the Node Record The Node Record references one or more Line Geometry Records Section body records The Geometry Record GEOMETRY contains the coordinate position s of the feature Node and point features contain one coordinate pair line features contain two or more pairs Geometry continuation records contain any further coordinates required to complete a line feature OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 49 How the section body is arranged NOTE NTF is designed to transfer any geographic data therefore there is no standard order of records This description of the order of records is specifically for the transfer of OSCAR data but cannot be guaranteed to be maintained Line feature LINEREC GEOMETRY1 line
29. FIC 01 99 1S8 Database name DDNAME 23 42 A20 DEFAULT 02 00 7S8 DDATE 43 50 DATE 19920515 Release date of NTF version being used DDBASE 51 70 A20 208 Not used DDBDATE 71 78 DATE 00000000 Not used CONT_MARK 79 79 11 1 Continuation record EOR 80 80 A1 96 Record terminator Continuation of Database Header Record Field Position Format Value example Description REC DESC 01 02 A2 00 FCNAME 03 22 A20 OSCAR TMAR 01 00 48 Data specification FCDATE 23 30 DATE 19990401 Date of data specification DQNAME 31 50 A20 208 Not used DQDATE 51 58 DATE 00000000 Not used DATA MODEL 59 60 12 00 Not used CONT_MARK 61 61 11 0 No further records EOR 62 62 A1 96 Record terminator Record example 020SCAR TRAFFIC 01 97 DEFAULT 02 00 OOOSCAR TMAR 01 00 19970401 23004251000009020000060042510 1 2 3 4 5 6 7 8 12345678901234567890123456789012345678901234567890123456789012345678901234567890 Template 19920515 00000000000 000000001 o OSCAR family product user guide appendix B V4 2 03 2005 Crown copyright Page 84 Attribute Description Record ATTDESC 40 The Attribute Description Record will take the following format The record examples shown are the additional Attribute Description Records that will be required to support Address Ranges over and above the standard OSCAR Traffic Manager Attribute Description Records Field Position Format Value ex
30. Figure B 1 example Attribute Record for a link of link In this example the Attribute Record ATTREC for the link will identify PUSO44 3PRIPUSO44 3PS LR1 13 O 1 RG2 14 E 1 This states that the Address Range features two postcodes PU which are listed in full On the left side of the road LR are numbers 1 13 and this sequence O is odd numbers On the right side of the road RG the Address Range is 2 14 and all numbers E are even The number 1 after O and E denotes that this is the first range for that side of the link HEN OSCAR family product user guide appendix B V4 2 03 2005 Crown copyright Page 80 Figure B 2 example Attribute Record for a link Belvedere Captains Cottage Longacre m Alderwood Heathlands S tart A Dene J of link Oldholme Coniston End of link In this example the Attribute Record ATTREC for the link will identify PUSO44 3PR PUSO44 3PS LxXBelvedere 1 LXCaptains Cottage 2 _LXLongacre 3 LXAlderwood 4 RYHeathlands 1 RYWest Dene 2 RYOldholme 3 RYConiston 4 This shows the postcodes PU the range of house names on the left LX and right RY side of the road and the sequence in which they run o yy OSCAR family product user guide appendix B V4 2 03 2005 Crown copyright Page 81 Figure B 3 example Attribute Record for a link Start of link In this example the Attribute Record ATTREC for t
31. ODR of O1CB3NCKOVTEG This identifier will be unique throughout the whole OSCAR dataset This link will be made up of three link segments with OSODRs of O1CB3NCKOVTEG Each of these segments will be wholly contained within tiles and will be further identified by the SECT REF and NTF ID of the constituent links Nodes in a seamless database Each node will have an OSODR identifier which will be unique within the whole OSCAR dataset and product family Standard nodes will be where one or more link starts and or ends Edge nodes will appear in the data as a consequence of downloading the data in a tile format MEE OSCAR family product user guide chapter 3 V4 2 03 2005 Crown copyright Page 22 Details of features and attributes A listing of all the features attributes and their codes can be found in chapter 6 Grade Separation The Grade Separation attribute indicates the relative height relationship between intersecting links at a node for example bridges It does not relate to ground surface level Junction Name The Junction Name JN attribute indicates the junction number of motorway junctions and the other classified roads at that junction If the junction has no junction number then that part of the junction name will not be supplied This information will be attached to a stand alone node in OSCAR Asset Manager However for OSCAR Traffic Manager this attribu
32. Ordnance Survey OSCAR User guide Preface This user guide contains the information you need to make effective use of the OSCAR Asset Manager and OSCAR Traffic Manager product and service and is designed to help you understand the information contained in the data as well as providing detailed technical information and the data format specification This user guide has been checked and validated before issue and every endeavour made to ensure that the contents are accurate If you find an error omission or otherwise wish to make a suggestion as to how this user guide can be improved please contact us at customerservicesQordnancesurvey co uk or the address shown under contact details or use the product and service performance report form at appendix C Contact details The Customer Contact Centre will be pleased to deal with your enquiries Phone 023 8030 5030 Fax 023 8079 2615 Email customerservices ordnancesurvey co uk Welsh Language HelpLine in Welsh phone 08456 05 05 04 or write to Customer Contact Centre Ordnance Survey Romsey Road SOUTHAMPTON United Kingdom S016 4GU Visit the Ordnance Survey web site at www ordnancesurvey co uk ees eS 8 SS OSCAR family product user guide preface V4 2 03 2005 Crown copyright Page 1 Product performance If you have any problems with or identify any errors in the data or user guide please complete the Product and servi
33. REE A PARETE AAEE EATE Ia A ae aE EEEE E 19 Teban E ere rece nee ar erie ec ie ee E MIL EM MILI ML E M ME 19 OSCAR application OVerVIBW e eerie prO O a ceo ETE iii 20 Typical User SCONM AMOS m 20 Chapter 3 OS Gy A Puree placed E em 21 OSCAR data Model E 21 RA O O AT 21 links inii seamless database 5 coi center ent tese Ri io a NE A AER O MX URARA ines aia eii 21 Nodes in a seamless database RRRRRRRRRRRR Rara rnne ne 22 Details of Teaturessand attribute S ias E 23 Grade SE AN P H 23 A 23 LO A 23 A OSCAR family user user guide contents v4 2 03 2005 O Crown copyright Page 4 Private ROMS ii ad 23 noi Elie toor o vis sees est sei EE E ECO mmm N 23 A A a RII MEM M Mix Ex EME 24 ROA NU moer c 24 A PH T 24 Settlement NaMe T 24 SOUE OCA O r E EE E E 24 Chapter 4 Quality statementand Specie atose EE a EU D de REI ad eects 25 Use 25 A Href Nistor OF OSCAR STRE gneve eatuasschtaisstecig tscleabh tease acsecenauteudendus Eea Eaa Daai E E EEAO T ANFIA Ea 25 eue
34. abase Reference hence the abbreviation the name has been changed in line with the renaming of the database The existing abbreviation has been retained to minimise confusion The OSODR OD attribute defines the Ordnance Survey ROADS Database Reference OSODR This will uniquely identify any link or node within the national OSCAR dataset The OSODR will be used as the unique identifier for each link and node rather than the NTF identifiers The NTF identifiers will be unique within each tile that is supplied but will not be maintained between supplies A road object is part of a road between nodes junctions uninterrupted by tile or map edges An OSODR refers not just to a single link but may refer to many links that make up a road object which may be chained together across tile edges Thus on adjoining tiles there may be two or more links with the same OSODRs This attribute applies to links and nodes It will be present for all features An OSODR has been assigned to all existing features links and nodes in the OSCAR database Any features which are new to ROADS after the initial allocation will be assigned an OSODR when they are loaded to the database The OSODR for a feature will never be modified only created and deleted However there may be many changes to a feature with a specific OSODR during the lifetime of that OSODR allocation There are two reasons for changes These are 1 The coordinates of the feature may move withi
35. ager has a 2 m lateral filter applied to the centreline which is supplied to 1 m resolution The 2 m filter does not affect the positional accuracy of node points but allows for the straightening of alignments between nodes The data will still fall within the road carriageway unless derived from a source of 1 10 000 scale or greater During the updating of OSCAR data there is a comparison buffer created around the existing OSCAR data to detect change This buffer is set to 3 m either side of a feature 5 m at each end and 10 of the length Any new features which touch or fall outside of the buffer will be considered as altered features The original reference for features will be maintained across updates if the features remain unaltered Completeness Throughout the whole OSCAR production process there are many checks and validation procedures carried out to ensure that the data supplied to customers provides a high standard of accuracy and completeness These checks take the form of e visual checks e computer validation e within the flowline and e using commercially available software As well as these checks each time a component part of a tile is compared for update discrepancies are flagged for investigation Whilst Ordnance Survey makes every effort to ensure that all roads features and attributes are complete it cannot guarantee that the latest release of OSCAR contains all roads in Great Britain The roads featured in
36. ample Description REC DESC 01 02 A2 40 VAL TYPE 03 04 A2 See table below FWIDTH 05 07 A3 See table below FINTER 08 12 Ab See table below ATT NAME 19 A See table below DIVIDER dex Al FDESC wur A See table below DIVIDER uk Al CONT_MARK E I1 0 No further records EOR Tor A1 96 Record terminator Record example 40PU 40LA 40LR 40LX 40RF 40RG 40RY A A A A A A A POST_CODE_UNIT Post Code Unit 0 LEFT SING ADDR Left Single Address 0 LEFT_ADDR_RANGE Left Address Range 0 LEFT BUILD TEXT NAME Left Building Text Name 0 RIGHT SING ADDR Right Single Address 0 RIGHT ADDR RANGENRight Address Range 0 RIGHT BUILD TEXT NAME Right Building Text Name 0 12345678901234567890123456789012345678901234567890123456789012345678901234567890 2 3 4 5 6 7 8 Template OSCAR family product user guide appendix B V4 2 03 2005 Crown copyright Page 85 Attribute Record ATTREC 14 These records will be defined as an attribute of a line A separate Attribute Record will be used for each link The Attribute Record will take the following format Field Position Format Value example Description REC DESC 01 02 A2 14 ATT ID 03 08 l6 Unique id for record VAL TYPE 09 10 A2 OD VALUE 11 23 A13 Unique id OSODR of link VAL TYPE 24 25 A2 FC VALUE 26 29 l4 Feature code VAL TYPE n A2 SC VALUE d A1 Source scale VAL_TYPE Es A2 LL VALUE mE I5 Length of link VAL TYPE s A2
37. ange information Change information will be supplied as part of the NTF dataset This information will be transferred in the Comment Records COMMENT The change information will define the NTF record type that has changed since the last release of the product using the REC DESC of the corresponding record Change information will be indicated for POINT 15 NODE 16 and LINE 23 records The RECORD ID will indicate the OSODR of the record that has changed The CHANGE TYPEj will indicate the type of change that has occurred to that feature This may be e D deleted inserted new record or e U updated changed o OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 38 Attribute codes Attribute codes provide supplementary information for a feature providing such qualifying information as feature code feature name and so on In NTF the structure of user defined attributes is described in the Attribute Description Record ATTDESC The actual attribute detail for a record is in the Attribute Record ATTREC Not all the defined attributes may be applicable to all features and thus not all possible attributes will necessarily be defined in an attribute record see Attribute allocation in this chapter Feature and record IDs The identifying fields for each record for example NODE ID for NODE records LINE ID for LINE records and so on are unique within each individ
38. appendix A V4 2 03 2005 Crown copyright Page 75 record A set of related data fields grouped for processing representation Depiction or description of an object using symbology road centreline An imaginary line depicting the centre of a road carriageway FC98 in OS93 specification rural All areas of mapping at the basic scale of 1 2500 which are not classified as urban section In NTF terminology a subdivision of a database In Ordnance Survey terms this equates to a single map sheet that is a digital map file or a tile segment A chord defined by two consecutive coordinates in a line string source scale The scale of the source information from which the map was digitised that is the scale of survey for a basic scale map or the scale of the source map for a derived map spatial data Data which includes a reference to a two or three dimensional position in space as one of its attributes It is used as a synonym for geometric data structure See data structure tile Broadly synonymous with digital map file it implies evenly sized map sheet units topography The study of the physical features of the Earth A topographic map s principal purpose is to portray and identify the features of the Earth a ee ne CE PRA CET OSCAR family product user guide appendix A V4 2 03 2005 Crown copyright Page 76 topology The study of the properties of a geometric figure which are not dependent on position such as co
39. ce performance report form at appendix C Liability Ordnance Survey provides OSCAR Asset Manager and OSCAR Traffic Manager on media or via FTP file transfer protocol server Any advice or explanation provided by Ordnance Survey is for guidance only and it is your responsibility to ensure that goods ordered are suitable for their intended purpose Terms and conditions of data use You are advised to copy the supplied data to a back up medium A full description of the terms and conditions of supply and use of OSCAR Asset Manager and OSCAR Traffic Manager is detailed in your customer contract User guide copyright This user guide is Crown Copyright 2005 All rights reserved It is supplied with OSCAR Asset Manager and OSCAR Traffic Manager to allow you to make effective use of the data Any part of the user guide may be copied for use internally in your business or organisation although you should check the Ordnance Survey web site from time to time for the latest version Printing this user guide If you wish to print this user guide it is suggested that it is bound on the left side WHEN OSCAR family product user guide preface V4 2 03 2005 Crown copyright Page 2 Trademarks Ordnance Survey the OS Symbol ADDRESS POINT Land Line Meridian OSCAR OSCAR Asset Manager and OSCAR Traffic Manager are registered trademarks of Ordnance Survey the national map
40. ch feature Each road is classified by means of a feature code with unique identifiers to enable you to create consistent references between releases of OSCAR The links within OSCAR Traffic Manager have all been filtered thereby reducing data quantities while retaining a realistic representation of the road network The retention of the nodes in true National Grid position ensures a high level of physical precision within the roadway The OSCAR product family includes the following features and attributes Features Node attributes motorways e unique identifier OSODR A roads e Settlement name e Broads e Junction name where applicable and minor roads e Grade separation road over road e pedestrianised roads and private roads Link attributes road name e Department for Transport DfT number link length unique link identifier ROADS Database Reference OSODR e trunk roads source scale and form of way MEN OSCAR family product user guide chapter 1 V4 2 03 2005 Crown copyright Page 9 OSCAR benefits The high specification of OSCAR offers a number of benefits National coverage The definitive road dataset for Great Britain suited to multiple applications using geographical information systems GIS and digital mapping systems e Length values for every road Unique link and node identifiers are
41. coordinates Defines vector data Redefines X_COORD Y_COORD Defines units as metres Multiplies coordinates by 1 000 Multiplies coordinates by 1 000 Eastings of origin Northings of origin Not used Continuation record Record terminator Description Minimum eastings Minimum northings Maximum eastings Maximum northings Not used Not used Date of extraction from database Default not used Same as SURV_DATE No further records Record terminator OSCAR family product user guide chapter 7 V4 2 03 2005 Crown copyright Page 58 Record example 07TO38SW 21000042000000100000000000000010000000530000000018000000000000001 00000000000000000000000000005000000000500000000000001994010700000000199401070 1 2 3 4 5 6 7 8 12345678901234567890123456789012345678901234567890123456789012345678901234567890 Template Valid section header values for OSCAR products Product Sect ref XYLEN XMAX amp YMAX OSCAR Asset Manager AAAAAA lt 4S gt 00004 0000005000 OSCAR Traffic Manager AAAAAA lt 4S gt 00004 0000005000 OSCAR family product user guide chapter 7 V4 2 03 2005 Crown copyright Page 59 Attribute Record ATTREC 14 Field REC DESC ATT ID VAL TYPE VALUE VAL TYPE VALUE VAL TYPE VALUE VAL TYPE VALUE VAL TYPE VALUE DIVIDER VAL TYPE VALUE DIVIDER VAL TYPE VALUE VAL TYPE VALUE CONT MARK EOR Position 01 02 03 08 09 10 11 23 24 25 26 29 Kak
42. d part of a named estate the estate name will be allocated to the road Road number RN This attribute defines the DfT road classification number which relates to a link If a road is not classified then this attribute will not be present J MEE OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 41 Source scale SC This attribute indicates the derivation of OSCAR data The following source scale attributes are used in the NTF attribute records Definition Value 1 1250 1 2500 or 1 10 000 scales digital A 1 10 000 scale graphic B 1 50 000 scale C 1 100 000 scales D Settlement name SN The settlement name SN attribute defines the name of a location or settlement This name will be attached to a stand alone node for OSCAR Asset Manager However for OSCAR Traffic Manager this name will be attached to the node which is closest to the position of the location or settlement There are about 30 000 settlement names derived from 1 250 000 scale data Trunk roads TR If a link forms part of a trunk road then it will have a trunk road attribute TR with a value of Y MEN OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 42 Grade separation The grade separation attribute indicates the relative height relationship between intersecting l
43. de Attribute Attribute name Description PU Postcode unit POST CODE UNIT The combination of postcode area district sector and unit codes applicable for all or part of a link LR Left address range LEFT ADDR RANGE Range of building numbers that occur on the left hand side of a link LX Left building text LEFT BUILD TEXT NAME The text details of an individual address that name appears on the left hand side of a link LA Left single address LEFT SING ADDR A single address which appears on the left hand side of a link RG Right address range RIGHT ADDR RANGE Range of building numbers that occur on the right hand side of a link RY Right building text RIGHT BUILD TEXT NAME The text details of an individual address that name appears on the right hand side of a link RF Right single address RIGHT SING ADDR A single address which appears on the right hand side of a link o pu Luc Ic ncc ns In a D nan OSCAR family product user guide appendix B V4 2 03 2005 Crown copyright Page 88 Address Ranges qualifiers The values listed below will be used to define the contents of a numeric address range E All numbers in the range are even for example 2 4 6 O All numbers in the range are oda for example 1 3 5 S Numbers in the range are sequential for example 7 8 9 OSCAR family product user guide appendix B V4 2 03 2005 Crown copyright Page 89 Appendix C Product and
44. e a physical obstruction in the road and do not include mini roundabouts which are painted on the road This attribute will not be included in gyratory systems which are interpreted as separate roads and not roundabouts S indicates a road junction link or slip road Junction name JN This attribute is used to indicate the junction number of motorway junctions and the other classified roads at that junction The junction name is variable length text and will be in the format M6 J10A where M6 is the DfT road number and J10A indicates that this is junction 10A of the M6 There could be any number of roads at a junction therefore each classified road at that junction may be repeated in the junction name attribute Each road number and junction will be separated by a forward slash character The following is an example of a junction name attribute M40 J1 A40 A413 A4020 This attribute only applies to nodes If the node does not have a junction name or number then this attribute will not be present This information is attached to a stand alone node in OSCAR Asset Manager For OSCAR Traffic Manager this information is attached to a node that forms part of the junction ay OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 40 Line length LL This attribute defines the length of the link in metres and will be present for all link record
45. e applied to roads on new estates which have not yet been connected to the main highway network Private roads which are not accessible by the public These roads will be on private land and will be metalled Examples of such roads are those used for access to military establishments farm and forestry roads Private roads which are publicly accessible These roads will be on private land and will be metalled Examples of such roads are those used for access to major industrial educational health or civic establishments where public access is the norm Pedestrianised roads This will relate mainly to roads or streets in city or town centres where traffic is banned where access is permitted to public transport emergency services or delivery vehicles A standard node These nodes will be located wherever two or more links meet that is at the junction of roads They also exist in OSCAR Asset Manager for motorway junction names and settlement names An edge node These nodes will be located wherever a road link crosses the edge of an NTF tile They are only supplied for completeness in NTF and are not part of the national OSCAR dataset An edge node will never be positioned at the junction of two roads OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 46 Transfer set structure OSCAR data is in one or more transfer sets A transfer set normally equates to a single file except where continuation volumes a
46. eature that is a non spatial element Attribute codes are fully described in chapter 6 Text There is no cartographic text in OSCAR All textual information is held as attributes HEN OSCAR family product user guide chapter 2 V4 2 03 2005 Crown copyright Page 19 OSCAR application overview Typical user scenarios The OSCAR product family provides a digital representation of the road network that can be used for a variety of applications including routeing systems to calculate the shortest fastest or minimum junction routes and give directions with street names and distances emergency services systems for police beats hospital locations calculation of distances and positioning of fire stations and other infrastructure To supply contacts telephone numbers and location of resources efficient traffic control with data including infrastructure accidents and traffic flow to provide accurate and timely traffic and travel information to create smoother traffic movement and less congestion utilising unique junction configuration for real time routeing for in car navigation applications creating transport planning networks to evaluate highway and public transport schemes routeing scheduling transport planning and site location analysis for extensive regional or national requirements displaying information about customers policy holders properties dev
47. edia capacity 01 VOLUME HEADER RECORD 01 02 DATABASE HEADER RECORD 40 ATTRIBUTE DESCRIPTION RECORD 05 FEATURE CLASSIFICATION RECORD 07 SECTION HEADER RECORD Part tile 1 07 VOLUME TERMINATION RECORD 99 End of Volume 01 Transfer Set Continues On Volume 02 1 01 VOLUME HEADER RECORD 02 Remainder tile 1 data 99 VOLUME TERMINATION RECORD 01 VOLUME HEADER RECORD 01 02 DATABASE HEADER RECORD 40 ATTRIBUTE DESCRIPTION RECORD 05 FEATURE CLASSIFICATION RECORD 07 SECTION HEADER RECORD Tile 2 data 99 VOLUME TERMINATION RECORD i 99End Of Transfer Set0 A OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 52 Chapter 7 Record structures for the transfer of OSCAR in NTF NTF record list This list comprises the valid record types used in the OSCAR product family NTF transfer set Descriptor Description 01 Volume Header Record defines the donor and data type 02 Database Header Record transfers data about the database 05 Feature Classification Record defines data classifications 07 Section Header Record defines coordinate and structure types unit scale factors and so on 14 Attribute Record defines the attributes for line and point records 15 Point Record identifies the definition of node points 16 Node Record
48. eet name DfT route number Source scale of data Settlement name Trunk road indicator V4 2 03 2005 Crown copyright OSCAR family product user guide chapter 7 Page 67 Comment Record COMMENT 90 Field Position Format Value example Description REC DESC 01 02 A2 90 RECORD TYPE 03 04 I2 Changed NTF record type RECORD D 05 17 A13 Unique id OSODR CHANGE TYPE 18 18 A1 D orlor U Type of change CONT MARK 19 19 I1 0 No further records EOR 20 20 A1 Record terminator Record example 902301J945LPCABAXUOS 1 2 3 4 5 6 7 8 12345678901234567890123456789012345678901234567890123456789012345678901234567890 Template Field Position Format Value example Description REC_DESC 01 02 A2 90 FREE_TEXT 03 A NO OSCAR DATA FOR THIS TILE CONT MARK Ed I1 0 No further records EOR A A1 96 Record terminator variable integer Record example 90NO OSCAR DATA FOR THIS TILEOS 1 2 3 4 5 6 7 8 12345678901234567890123456789012345678901234567890123456789012345678901234567890 Template o OSCAR family product user guide chapter 7 V4 2 03 2005 Crown copyright Page 68 Volume Termination Record VOLTERM 99 Field Position Format Value example Description REC DESC 01 02 A2 99 FREE TEXT 03 A See note below CONT VOL 2d I1 0 No further volumes or 1 Continuation volumes EOR ce A1 96 Record terminator variable
49. elopment sites patients traffic incidents and competitors against an accurate street map planning salt spreading snowploughing street cleaning refuse collection postal delivery and meter readings or managing of road assets street furniture positioning road maintenance programming and cost evaluation OSCAR family product user guide chapter 2 V4 2 03 2005 Crown copyright Page 20 Chapter 3 OSCAR explained OSCAR data model In the OSCAR database the data is held in a seamless environment However Ordnance Survey edit in a tile based environment and at present data is supplied to customers in 5 km by 5 km tiles Data structure Links in a seamless database Each link will relate to a distinct link within the OSCAR dataset This link will not stop at tile edges but will traverse those edges to make one contiguous line feature This link will however be made up of a number of link segments each of which will be contained wholly within an OSCAR product family tile o we X J J A e M Page 21 OSCAR family product user guide chapter 3 V4 2 03 2005 Crown copyright Figure 3 1 Link examples SECT REF TQ38SW SECT REF TQ38SE NTF ID 33 NTF ID 62 OSODR O1CB3NCKOVTEG SECT REF TQ37NE In the example of OSCAR Asset Manager shown above there will be one link with an Ordnance Survey ROADS Database Reference OS
50. erminator variable integer Record example 053000 Motorwayl0 053001 A Road 0 053002 B Road 0 053004 Minor Road 0 053007 Non Network Road 0 053008 Private Road 0 053009 Private Road Publicly Used 0 053010 Pedestrianised Road 0 053500 Standard Node 0 053501 Edge Node 0 1 2 3 4 5 6 7 8 12345678901234567890123456789012345678901234567890123456789012345678901234567890 HEN V4 2 03 2005 Crown copyright Template OSCAR family product user guide chapter 7 Page 57 Section Header Record SECHREC 07 Field Position Format REC DESC 01 02 A2 SECT REF 03 12 A10 COORD TYP 13 13 11 STRUC_TYP 14 14 11 XYLEN 15 19 15 XY_UNIT 20 20 11 XY_MULT 21 30 R10 3 ZLEN 31 35 I5 Z UNIT 36 36 11 Z_MULT 37 46 R10 3 X ORIG 47 56 110 Y_ORIG 57 66 110 Z_DATUM 67 76 110 CONT_MARK TOT 11 EOR 78 78 A1 Continuation of Section Header Record Field Position Format REC DESC 01 02 A2 XMIN 03 12 110 YMIN 13 22 110 XMAX 23 32 110 YMAX 33 42 110 XY_ACC 43 47 R5 2 Z_ACC 48 52 R5 2 SURV_DATE 53 60 DATE LAST_AMND 61 68 DATE COPYRIGHT 69 76 DATE CONT_MARK TOT I1 EOR 78 78 Al Value example 07 1 2 0000001000 00000 0 0000001000 0000000000 1 96 Value example 00 0000000000 0000000000 00000 00000 YYYYMMDD 00000000 0 Description Tile reference Defines rectangular
51. gh Road LONDON W4 4AL Phone 020 8996 9000 Fax 020 8996 7001 MEE OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 31 NOTE Full details of the British Standard can be accessed through the British Standards Institution s web site at http Awww bsi global com Any queries relating to the OSCAR products should be referred to Ordnance Survey at the address shown at the beginning of this user guide Conventions used in this user guide Certain conventions are adopted as an aid to interpretation In some cases the convention is dropped where the context is self evident Square brackets are placed around record names for example SECHREC G A pair of braces denote field names for example FEAT CODE is the feature classification code 90 Atwo digit number following square brackets denotes the record descriptor which uniquely identifies the record name between brackets S Thisis the space character ASCII code 32 3S This denotes three successive space characters 96 The percentage character ASCII code 37 This indicates a repeating field ASCII code 124 HEN OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 32 Data model NODE TOPOLOGY LINK SEGMENT LINK COORDS OSCAR family product user guide chapter
52. he link will identify PUSO44 3PRIPUSO44 3PS LR1 3 S 1 _LXLongacre 2 LR7 11 O 3 RG4 6 S 1 RYConiston 2 RG8 12 E 3 This shows the postcodes PU followed by the first range on the left side LR which is numbers 1 3 in sequence S followed by a single named house LX with odd numbered houses O between 7 11 finishing the range LR The right side has numbers RG 4 6 in sequence S followed by a single named house RY and ending with even numbered E houses RG between 8 12 0 ee OSCAR family product user guide appendix B V4 2 03 2005 Crown copyright Page 82 Currency Address Ranges are derived from the most current ADDRESS POINT dataset available at the time of the OSCAR Traffic Manager freeze Address Ranges in NTF We recommended that you read chapter 6 and chapter 7 of this user guide first to obtain a full understanding of OSCAR in NTF When OSCAR Traffic Manager is supplied with Address Ranges the format of the NTF records will be changed as shown on the following page OSCAR family product user guide appendix B V4 2 03 2005 Crown copyright Page 83 Database Header Record DBHREC 02 The Database Header Record will take the following format when Address Ranges is supplied with OSCAR Traffic Manager Note If Address Ranges is not being supplied then the Database Header Record will remain unchanged Field Position Format Value example Description REC DESC 01 02 A2 02 DBNAME 03 22 A20 OSCAR TRAF
53. hing In the context of digital mapping the word has a special meaning and implies a connected entity copyright The sole legal right to print or publish a work Crown copyright subsists in all Ordnance Survey publications including digital map data for a 50 year period from the end of the year in which they were first published by virtue of the Copyright Designs and Patents Act 1988 currency An expression of the up to dateness of data data A representation of facts concepts or instructions in a formalised manner suitable for communication interpretation or processing database An organised integrated collection of data stored so as to be capable of use in relevant applications with the data being accessed by different logical paths Theoretically it is application independent but in reality it is rarely so a en E OSCAR family product user guide appendix A V4 2 03 2005 Crown copyright Page 71 dataset An Ordnance Survey term for a named collection of logically related features arranged in a prescribed manner For example all water features A dataset has more internal structure than a layer and is related to another dataset only by position data format A specification that defines the order in which data is stored or a description of the way data is held in a file or record data model An abstraction of the real world which incorporates only those properties thought to be relevant to the application or appl
54. ications at hand The data model would normally define specific groups of entities and their attributes and the relationship between these entities A data model is independent of a computer system and its associated data structures A map is one example of an analogue data model data structure The defined logical arrangement of data as used by a system for data management a representation of a data model in computer form density A measure of the number of units of data held on a stated length of storage surface For example some magnetic tapes may be recorded at a density of 1600 bits per inch bpi Often referred to as packing density digital Data which is expressed as numbers digits in computer readable form is said to be digital digitising The process of converting analogue maps and other sources to a computer readable form This may be point digitising points are only recorded when a button is pressed on a cursor or stream digitising points are recorded automatically at preset intervals of either distance or time digital map Any map sold by Ordnance Survey or its Agents in any form that is on computer readable media or as hard copy on paper and or film or microfilm produced mainly or wholly using computerised means edge An edge is a curve joining two possibly identical nodes without intersecting an edge including itself Any sequence of edges either bounds a face and or represents a line feature See also l
55. ing format on the relevant links M T 6 The Junction Number JN format will remain the same with the T in brackets Trunk Road If a link forms part of a trunk road it will have the Trunk Road TR attribute attached Settlement Name The Settlement Name SN attribute defines the name of a location or settlement This name will be attached to a stand alone node for OSCAR Asset Manager However for OSCAR Traffic Manager this name will be attached to the node which is closest to the position of the location or settlement Source Scale The Source Scale SC attribute defines the derivation of OSCAR data This is the scale from which the individual link was derived for the OSCAR product This attribute only applies to links and is present for all link features NENNEN OSCAR family product user guide chapter 3 V4 2 03 2005 Crown copyright Page 24 Chapter 4 Quality statement and specification Source OSCAR data was created from the latest Land Line data where it was available In areas which had no digital cover the required data was captured by digitising centrelines from 1 10 000 scale derived or basic scale graphic sheets A brief history of OSCAR Initial data capture for OSCAR was completed in December 1993 n April 1994 OSCAR was launched as OSCAR Asset Manager e To meet the increasing demand in traffic and travel applications OSCAR Traffic Manager
56. ink AR A tct mt at RC UB A EN NUNC t OSCAR family product user guide appendix A V4 2 03 2005 Crown copyright Page 72 edit The process of validating and correcting errors in digital map data feature An item of detail within a map which can be either a point or symbol a line or text a geographical entity such as a building or stream either taken from a map or surveyed directly from the real world feature code FC An alphanumeric code describing or classifying a feature used in digital map data as an attribute code to describe each feature in terms of the object surveyed its representation on the map or both feature serial number FSN A number used as a feature identifier usually allocated on a sequential basis For example the order in which features are digitised format The specified arrangement of data For example the layout of a printed document the arrangement of the parts of a computer instruction the arrangement of data in a record generalisation The process of abstracting from the real world through selection aggregation simplification and symbolisation for the purpose of representation in spatial data geographical information system GIS A system for capturing storing checking integrating analysing and displaying data that is spatially referenced to the Earth This is normally considered to involve a spatially referenced computer database and appropriate applications software gigabyte Gb 1
57. inks at a node for example bridges It does not relate to ground surface level Figure 6 2 Example of a junction The example consists of a multi carriageway running north south crossed by a single carriageway running east west with four slip roads providing access between the two and the single carriageway carried on a bridge over the multi carriageway There are eight nodes numbered 1 to 8 in figure 6 2 Using the LEVEL field in the Node Record 16 nodes 7 and 8 will show a level 0 for the multi carriageway links and a level 1 for the single carriageway Nodes 1 to 6 will show a level 0 for all links a uu A m w X A J e M OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 43 NTF attributes The following attributes are used in the supply of OSCAR Asset Manager and OSCAR Traffic Manager data Mnemonic FC FW JN LL OD PN RN SC SN TR o wu ow A V4 2 03 2005 Crown copyright Name Feature code Form of way Junction name Line length OSODR Proper name Road number Source scale Settlement name Trunk road Description Feature code for the feature Form of way descriptor for a link Name of junction at node Length of a link in metres Unique id for a link or node Road name for a link DfT road number for a link Scale of data from which the OSCAR link was derived
58. intersect one another where attributes change or at tile edges The first and last coordinate pairs in a line will correspond exactly with the start or end coordinates of any adjoining line s A line cannot cross from one tile to the next but see OSODR definition in chapter 4 LINE FEATURE TT GEOMETRY 21 GEOMETRY BODY ATTREC 14 GEOMETRY CONTINUATION ATTREC BODY RECORDS 00 OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 37 Coordinates Coordinate values and the number of coordinate pairs in a feature are transferred in the Geometry Record GEOMETRY1 All coordinates within the data are expressed as strings of numeric characters for the eastings and the northings The size of these character strings for both eastings and northings is four characters Where appropriate leading zeros will be present to complete the length of the coordinate field The eastings X COORD and northings Y COORD are separate fields and therefore coordinate pairs can be split across records although the integrity of the fields themselves is not compromised All coordinates are measured from the local origin which is the south west corner of the tile To convert coordinate data to full National Grid coordinates add the coordinates of the feature to those of the SW corner of the tile The SW corner coordinates are contained within the X ORIG and Y ORIG fields of the Section Header Record SECHREC Ch
59. ital road centreline products derived from a single definitive Source It is a representation in computer readable form of the national public road network as spatially defined by Ordnance Survey large scale digital mapping GIS software provides the functionality to store manage and manipulate the digital map data The properties of OSCAR make it suitable as the basis for users wishing to develop such applications OSCAR is coordinated on the National Grid which allows for the easy superimposition of other similarly referenced datasets The OSCAR product family is derived from Ordnance Survey s ROADS database and supplied as vector data in a link and node structure where links are road centrelines and nodes are intersections of links with attributes attached to each feature Nodes are also supplied at the edge of each tile OSCAR Asset Manager provides around 3 5 million links nationally in 10 566 5 km by 5 km tiles OSCAR Traffic Manager provides over 3 million links in 10 566 5 km by 5 km tiles 0 I O a OSCAR family product user guide chapter 2 V4 2 03 2005 Crown copyright Page 17 OSCAR data source The source of the digital data in the ROADS database is the road centreline feature within our large scale digital mapping database Digital Database Management System DDMS Additional information was taken from 1 10 000 scale and other graphic mapping with an equivalent accuracy The attributes attached to the
60. n a specified tolerance currently 3 m either side of a link 10 of its length and 5 m movement of any node 2 The attributes associated with a feature may change Any changes to these attributes will not affect the OSODR allocated to that feature a OSCAR family product user guide chapter 4 V4 2 03 2005 Crown copyright Page 27 The following attributes may change for link features e feature code e length of link e road name road number e trunk road indicator source scale form of way The following attributes may change for node features e direction of links at node feature code e junction name number of links at node e level of link at node settlement name If a feature moves by more than the specified tolerance then the OSODR for the feature will be deleted and a new OSODR allocated to that feature If a feature is deleted from the OSCAR dataset then the OSODR allocated to that feature will cease to exist and will not be reallocated MEE OSCAR family product user guide chapter 4 V4 2 03 2005 Crown copyright Page 28 Accuracy and resolution e OSCAR Asset Manager is supplied to 1 m resolution this means that the data will fall within the road carriageway as defined in Land Line unless derived from a source of 1 10 000 scale or greater e OSCAR Traffic Man
61. nnectivity relationships between lines nodes and polygons transfer set A specific NTF term for the data together with its supporting information which the customer receives UNIX An operating system that supports multi tasking and is used by many workstations and mini computers OSCAR family product user guide appendix A V4 2 03 2005 Crown copyright Page 77 Appendix B OSCAR Address Ranges information The product Address Ranges is no longer available for new customer supply Address Ranges an introduction Address Ranges is a database of house numbers and names attached to the portions of a link to which they apply Address Ranges is an exclusive option for OSCAR Traffic Manager and updates will be released on an identical schedule Address Ranges version number The version numbering of Address Ranges will be identical to the OSCAR Traffic Manager data it is supplied with and can be found in the Database Header Record DBHREC Address Ranges features Address Ranges feature the range of address numbers and house names applied sequentially along each side of a link between junctions with left or right side of link identifier direction in which the addresses run highest and lowest building number for each side of the link house names and postcode OSCAR family product user guide appendix B V4 2 03 2005 Crown copyright Page 78 Address Ranges data source Address Ranges is derived from the la
62. ok variable integer Record example Format A2 16 A2 A13 A2 14 A2 A1 A2 15 A2 AF A1 A2 A A1 A2 A1 A2 A1 I1 A1 Value example 14 OD FC SC LL PN FW or 1 96 Description Unique id for record Unique id OSODR for link Feature code Source scale Length of link Road name Road number Trunk road indicator Form of way No further records or continuation record follows Record terminator 140000010DO138UHKOPLWAXFC3001SCALL00342PNCOMMERCIAL STREETNRNA315 T TRYFWDO0 1 4 12345678901234567890123456789012345678901234567890123456789012345678901234567890 5 6 7 8 Template OSCAR family product user guide chapter 7 V4 2 03 2005 Crown copyright Page 60 Attribute Record ATTREC 14 Field Position Format Value example Description REC DESC 01 02 A2 14 ATT ID 03 08 16 Unique id for record VAL_TYPE 09 10 A2 OD VALUE 11 23 A13 Unique id OSODR for node VAL_TYPE 24 25 A2 FC VALUE 26 29 14 Feature code VAL_TYPE 125 A2 JN VALUE EE A Junction name DIVIDER EN Al VAL_TYPE a A2 SN VALUE q A Settlement name DIVIDER as Al CONT_MARK 8 11 0 No further records or 1 or continuation record follows EOR a A1 96 Record terminator variable integer Record example 140000230DO1DF42CKOVTEGFC3500JNM27 J2NSNSOUTHAMPTONV 0 1 2 3 4 5 6 7 8 123456789012345678901234567890123456789012345678901
63. ping agency of Great Britain MS DOS is a registered trademark of Microsoft Corporation PAF is a registered trademark of Royal Mail Group plc UNIX is a registered trademark of X Open Company Ltd OSCAR family product user guide preface V4 2 03 2005 Crown copyright Page 3 Contents Chapter 1 IMEFOGMCHON PP EET TETERTOIL T r RUEDAS 8 ISIN OMMISHUSER epo 8 xir eE Insigeteim cc PEEL 8 OSCAR EIU EET 9 OSCAR DSM GUIS O AUI E 10 OSCAR applications E 11 Whatyou need To use OSCAR Sata a ubt euer sert ed astuce Age kn td a 12 Hardware eseme TEES 12 SITAE E E E Ea 12 OSCAR SUDDIVIODIIOFIS aia oct ML T LM AIDS D onu IND D M Miss METUS EA LAE 13 TEST OMA e EAE EASE 13 E O EHE 13 Update update OptiONS enei T T ET 13 OSCAR version numbering or SpecificatiON oononnnninininicicnnnonneccneccnnccr narran rara 13 NTE peleas 6 Sie teak do rta 14 OSCAR OULD UE OPUOMS cn Das 14 Chapter 2 TAR 17 eres sc 17 OSCAR A r 18 OSCAR data StUCIUTS eT HL MHeee EE 18 Feature Posio Misie E 19 Feature CodeS aa a A E e a e e a a O A a a A S 19 AE o naa aie ae aea EE EE A EEE a aaaea Aaaa A
64. pply of OSCAR Asset Manager and OSCAR Traffic Manager is the 5 km by 5 km tile which corresponds to 5 km by 5 km divisions of the National Grid NG See figure 5 1 on page 30 National cover consists of 10 566 tiles Transfer format s OSCAR is available in e BS 7567 NTF v2 0 Level 3 Media OSCAR data in NTF National Transfer Format is supplied on the standard Ordnance Survey media range Update update options Both OSCAR Asset Manager and OSCAR Traffic Manager are updated twice a year April and October Each update is accompanied by details of changes since the previous supply The last update is scheduled for April 2006 OSCAR version numbering or specification Each version and release of all OSCAR products is defined by a unique product version number and product release number which are reflected in this user guide The product version number relates to the specification of the OSCAR data that is being supplied and the product release number relates to the chronological data release See chapter 6 OSCAR family product user guide chapter 1 V4 2 03 2005 Crown copyright Page 13 NTF release The current version is NTF v2 0 OSCAR output options OSCAR is inert data It requires software not provided by Ordnance Survey to display it on a screen manipulate it or plot it out as hard copy The parameters defining colours line styles text styles symbols and so on should be built into your software The OS
65. re used when the transfer set exceeds the capacity of the media Volume records Each transfer set starts with a Volume Header Record VOLHDREC and terminates with a Volume Terminator Record VOLTERM Database records The beginning of each transfer set is structured with the following introductory or leading records 1 Database Header Record DBHREC this gives details of e the database name e NTF release date e feature classification table name and e the date of the data specification 2 Attribute Description Record ATTDESC this lists and gives a description of the attributes that are applied to features within the transfer set 3 Feature Classification Record FEATCLASS this lists and gives descriptions of all possible feature codes for the transfer set These introductory records are followed by the data MEN OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 47 Section records This section consists of two parts 1 Section Header Record SECHREC this gives the National Grid coordinates of the section and on unformatted media informs you that a new section is starting 2 Section body this comprises all the features within the section Section body data Line feature Each line feature is represented by the use of the following records Description in NTF LINE RECORD LINEREC GEOMETRY RECOR
66. res cn 69 Appendix A lOs de E 70 MEN OSCAR family user user guide contents v4 2 03 2005 Crown copyright Page 6 Appendix B OSCAR Address hengdes IntorteiatlODes ise pesa e UpEts utet Pon Ia ou ER paca at un dU rbd 78 Address Ranges an IMMTODUCHOM ecc 9 78 Address Ranges version NUMDED ccsceeeesceceseneeeeeeneeeeeeneeeeenaeeeeeeaeeeeeaeeeeeaeeeeeeseeeeeeaeeeeesaeeeeeeaaeeeseaeeseseaaeeeeeaeeesseaeeeeseaeeeeeaeeeees 78 Address RangesS TE AUTES ii aia eiia SaNa Aea EAA ECAA EA ETA AE AEA TRARA EE 78 Address Ra ges data SOUFIGB etario rh assed spandand R aa EELA Eaa Ea a eD eraio pia Aa AEAEE ATAS ERE A 79 Change Ino Mal aios tot ret 79 Det ilSof Address Range S at ii it ea Aei ea a e ra at ner ta td 79 CUS CY Reta a EE RE E E S a A caos 83 Address R nges in NIF meirin aaa oca 83 Database Header Record DBHREC Daiana de dd adenda arios 84 Attribute Description Record ATTDESC Oraci n e da id Aca 85 Attribute Record ATT REC TA soriana dica 86 Datarclassiticatiomsand metadata E ET 88 NTF Attn tS ui A O calcio 88 Address Ranges qualifiers seien RR RARE RR EEEO EENAA nnne 89 Appendix C Product and service performance epOLEt fOPETIx cara xta uten reno aa acad tea e Fax ER tai 90 OSCAR family user user guide contents v4 2 03 2005 Crown copyright Page 7 Chapter 1 Introduction Using this user guide
67. s It is calculated from the planimetric coordinates making up the link and does not take into account the effect of slope The link length in all products refers to the length as recorded in the ROADS database OSODR OD The OSODR OD attribute defines the Ordnance Survey ROADS Database Reference OSODR This will uniquely identify any link or node within the national OSCAR dataset The OSODR will be used as the unique identifier for each link and node rather than the NTF identifiers The NTF identifiers will be unique within each tile that is supplied but will not be maintained between supplies A road object is part of a road between nodes junctions uninterrupted by tile or map edges An OSODR refers not just to a single link but may refer to many links that make up a road object which may be chained together across tile edges Thus on adjoining tiles there may be two or more links with the same OSODRs This attribute applies to links and nodes It will be present for all features An OSODR has been assigned to all existing features links and nodes in the ROADS database Any features which are new to OSCAR after the initial allocation will be assigned an OSODR when they are loaded to the database Proper name PN The proper name PN attribute defines the road name associated with any link in the OSCAR dataset If a link does not have a proper name then the attribute will not be present Where the road is otherwise not named an
68. te will be attached to the node closest to the position of the junction This attribute only applies to nodes If the node does not have a junction name then this attribute will not be present Link Length The Link Length LL attribute defines the length of the link in metres Private Roads The Private Roads feature code defines publicly accessible private roads which are metalled and on private land They are depicted on major industrial educational health or civic establishments where public access is normal A separate feature code has been allocated to private roads which are not accessible to the public Pedestrianised Roads The Pedestrianised Roads feature code defines roads or streets in city or town centres where traffic is banned NENNEN OSCAR family product user guide chapter 3 V4 2 03 2005 Crown copyright Page 23 Proper Name The Proper Name PN attribute defines the road name associated with any link in the OSCAR dataset If a link does not have a proper name then the attribute will not be present Road Number The Road Number RN attribute defines the DfT road classification number which relates to a link In the April 2004 release of OSCAR the M6 Toll road has been included for the first time The data structure has remained the same to minimise the impact on customers The road which is officially known as the M6Toll has been named in the follow
69. test version of ADDRESS POINT an Ordnance Survey data product ADDRESS POINT is created from the Royal Mail Postal Address File PAF Land Line and OSCAR Other data is collected from trade directories building notifications and field visits Change information Change information on Address Ranges attribution is not available in the supplied data at the moment Details of Address Ranges An Address Range can be a range of address numbers for example 2 10 building text if there are no numbers a single number for example 2 or a combination depending upon the address layout of a road The data will also show whether house number ranges are odd even or sequential House names will be listed in the order they fall along their respective sides of the road Postcodes are shown for the range of addresses and not for each individual address or in any particular order Named paths and walkways are currently not available in Address Ranges Blocks of flats will be shown as a single text or numbered address Full details on Address Ranges NTF record layouts and attribution can be found at Address Ranges in NTF in this chapter Address Ranges information can be found in the Attribute Record ATTREC The direction of the address range will be shown as following the direction of the coordinates of the link as found in the Geometry Record GEOMETRY 1 OSCAR family product user guide appendix B V4 2 03 2005 Crown copyright Page 79
70. the form xx yy where xx is the is the sequential release within a year and yy is the year of the release Thus release 01 01 would indicate that this is the first data release in 2001 The copyright date of each release is the same as date of extraction from the database SURV DATE and is shown in each Section Header Record SECHREC in the COPYRIGHT field Six monthly releases do not usually also mean a change of product specification NTF version The current version is NTF v2 0 Level 3 and will be supplied until further notice The NTF version is indicated by the NTFVER field of the Volume Header Record VOLHDREC The effective date of the definition of NTF v2 0 in OSCAR is 15 May 1992 and is indicated by the DDATE field of the Database Header Record DBHREC MEE OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 35 OSCAR information relevant to NTF Point features Point features exist at the junction or end of links in OSCAR Asset Manager and OSCAR Traffic Manager they also exist for motorway junction names and settlement names The point feature gives a position and attribute to the corresponding node POINT FEATURE POINTREC 15 GEOMETRY 21 AN ATTREC CONTINUATION RECORD 00 OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 36 Line features All line features are broken when they
71. treet furniture Traffic and travel information management Vehicle tracking OSCAR family product user guide chapter 1 V4 2 03 2005 Crown copyright Page 11 What you need to use OSCAR Hardware Providing that sufficient memory and storage facilities are available there are no constraints on hardware platforms which can be used for the OSCAR product family The range of hardware which can typically be used varies from higher specification personal computers PCs to mainframe computers Software OSCAR data does not include software for analysis but can be used with a variety of programs To fully exploit OSCAR data it is necessary to use appropriate application software There are many proprietary systems available and we publish a list of GIS computer aided design CAD and digital mapping licensed system suppliers who have confirmed their software can import Ordnance Survey NTF data Contact us at the address at the beginning of this user guide for a copy of the list We cannot however accept any responsibility for any third party software you use in conjunction with the OSCAR data Although the data contains no executable codes and cannot be run as a program the NTF text can be read in an MS DOS environment OSCAR family product user guide chapter 1 V4 2 03 2005 Crown copyright Page 12 OSCAR supply options OSCAR is supplied in tiles which are referenced to the National Grid see chapter 5 The base unit for su
72. ual dataset They are not guaranteed to be maintained between supplies The OSODR attribute which is linked to each line and node record will be a unique reference within the entire national OSCAR dataset These references will be maintained between supplies except where there has been significant change to a feature see chapter 4 for a more detailed explanation of OSODR allocation The OSODR is used in the change information records to indicate what features have changed between supplies o wu LL H A a e OSCAR family product user guide chapter 6 V4 2 03 2005 Crown copyright Page 39 Data classification and metadata Form of way FW The FW attribute is used to define the type of road feature which the link represents This is in addition to the feature code and may be applied to any link record Only one form of way will apply to any link record The form of way values are utilised primarily as an aid to produce other lower resolution Ordnance Survey data sets The following are Ordnance Survey definitions and should not be confused with any other definitions of these features D indicates that the link forms part of a multi carriageway This means that as well as being used for dual carriageways it is also used for complex junctions where there are two carriageways separated by a physical barrier R indicates that the link forms part of a roundabout Roundabouts with this attribute hav

1.6MB pdf: OSCAR family product user guide v4.2

Contents

Download Pdf Manuals

Related Search

Related Contents