THE UTM/UPS STANDARD RASTER PRODUCT SPECIFICATION (USRP) · USRP Edition 1.3 August 1997 v NOTICE TO USERS This international specification for UTM/UPS Standard Raster Product (USRP)

THEUTM/UPS STANDARD RASTER PRODUCT

SPECIFICATION

(USRP)

Produced and issued under the direction of theCentre Géographique Interarmées, France on behalf of theDigital Geographic Information Working Group (DGIWG).

Edition 1.3 August 1997

USRP Edition 1.3August 1997

i

TABLE OF CONTENTS

Page No

Table of Contents .................................................................................................... iList of Figures .........................................................................................................iiiList of Annexes .......................................................................................................iiiList of Enclosures ...................................................................................................ivNotice to Users ....................................................................................................... vRecord of Amendments .......................................................................................... vForeword.................................................................................................................vi

Authority .........................................................................................................viPurpose and Scope........................................................................................viApplication......................................................................................................viAmendements................................................................................................viDistribution .....................................................................................................viProposed Changes .......................................................................................viiTechnical Queries .........................................................................................viiSecurity .........................................................................................................viiCustodian ......................................................................................................viiNational Representatives / Points of Contact............................................... viii

Acronyms and Abbreviations .................................................................................. x

Page No

1.0 Scope........................................................................................................1 - 12.0 References................................................................................................2 - 13.0 General Information ..................................................................................3 - 1

3.1 Description of UTM/UPS Standardized Raster Products ..................3 - 13.1.1 Standard Raster Graphics....................................................3 - 13.1.2 UTM/UPS Projection ...........................................................3 - 1

3.2 The UTM/UPS System......................................................................3 - 13.2.1 General ................................................................................3 - 13.2.2 Zones ...................................................................................3 - 13.2.3 Polar Zones..........................................................................3 - 13.2.4 Storage.................................................................................3 - 13.2.5 Overlap.................................................................................3 - 2

3.3 Datums..............................................................................................3 - 43.4 Accuracy Requirements ....................................................................3 - 4

3.4.1 Source graphics at scales of 1:100,000 or smaller ..............3 - 43.4.2 Source graphics at scales larger than 1:100,000 .................3 - 4

3.5 Colour Definition and Coding ............................................................3 - 53.5.1 Colour Representation .........................................................3 - 53.5.2 Use of Repromat ..................................................................3 - 6


ii

3.6 Insets and Outsets ............................................................................3 - 63.6.1 Insets....................................................................................3 - 63.6.2 Outsets.................................................................................3 - 7

3.7 Marginalia..........................................................................................3 - 73.7.1 Legend Images.....................................................................3 - 73.7.2 Supplementary Text Data.....................................................3 - 9

4.0 Exchange Specification.............................................................................4 - 14.1 Overview ...........................................................................................4 - 14.2 Overview of Raster Data Structure....................................................4 - 1

4.2.1 Image Description ................................................................4 - 14.2.2 Subblock Ordering................................................................4 - 14.2.3 Subblock Zero Fill.................................................................4 - 24.2.4 Tile Index Map Description...................................................4 - 34.2.5 ISO 8211 Conformance .......................................................4 - 4

4.3 Scan Lines .......................................................................................4 - 44.3.1 Pixel Count Subfield .............................................................4 - 54.3.2 Subfield Length ....................................................................4 - 54.3.3 Zero Pixel Count...................................................................4 - 54.3.4 Color Coded Image ..............................................................4 - 6

4.4 General requirement .........................................................................4 - 64.4.1 Field Use ..............................................................................4 - 64.4.2 Decimal Mark .......................................................................4 - 64.4.3 Digest Specific Data Syntax .................................................4 - 64.4.4 Interpretation of Binary Fields ..............................................4 - 6

5.0 Logical Structure .......................................................................................5 - 15.1 Logical Description of Data Subsets .................................................5 - 1

5.1.1 Header Data Subset.............................................................5 - 15.1.2 Geo Data Subset..................................................................5 - 1

5.2 File Structures ...................................................................................5 - 25.2.1 Transmittal Header File ........................................................5 - 25.2.2 General Information File.......................................................5 - 55.2.3 Geo Reference File ............................................................5 - 105.2.4 Source File .........................................................................5 - 115.2.5 Quality File .........................................................................5 - 225.2.6 Geo Data File .....................................................................5 - 26

6.0 Exchange Media .......................................................................................6 - 16.1 Purpose.............................................................................................6 - 16.2 Character Representation .................................................................6 - 16.3 Forms of Media .................................................................................6 - 1

6.3.1 Magnetic tape.......................................................................6 - 16.3.2 Optical disk...........................................................................6 - 36.3.3 Other media .........................................................................6 - 5

6.4 File naming conventions ...................................................................6 - 5


iii

LIST OF FIGURES

Figure Page No

3 - 1 UTM/UPS Zone Tiling Organisation ........................................................3 - 23 - 2 Overlap Areas ..........................................................................................3 - 33 - 3 An example Index Diagram.......................................................................3 - 73 - 4 An example Elevation/Depth (Bathymetric)Tint Diagram ..........................3 - 83 - 5 An example Glossary ..............................................................................3 - 83 - 6 An example Feature Symbol table ............................................................3 - 94 - 1 Sub Block and Pixel Organization .............................................................4 - 24 - 2 USRP image tile structure .........................................................................4 - 34 - 3 Tile index map example with null tiles .......................................................4 - 45 - 1 Logical Data Set........................................................................................5 - 15 - 2 A seamless four-map Main Raster Image (MRI) .....................................5 - 275 - 3 MRI for source graphics with outsets. .....................................................5 - 275 - 4 MRI for source graphics with inset. .........................................................5 - 285 - 5 MRI for source graphics on different datums ..........................................5 - 28

LIST OF ANNEXES

A ISO 8211 Encapsulation Specifications.

B UTM/UPS Coordinate Transformations.


iv

LIST OF ENCLOSURES

The following Enclosures are extracts from DIGEST (Reference 1) :

USRPENCLOSURE

DIGESTREFERENCE DESCRIPTION

1 Part 4 Annex B Attribute and Value Codes.Note: Only those FACC codes which areused in this USRP specification areincluded (i.e. CDP, NST). This istherefore an incomplete copy of theDIGEST Annex.

2 PART 3 Clause 7 Grid Codes.

3 PART 3 Clause 8 Ellipsoid Codes.

4 PART 3 Clause 9 Datum Codes.

5 PART 3 Clause 6 Projection Codes and Parameters.

6 PART 3 Clause 13 Use of CIE Values.

7 PART 3 Clause 11 Country Names and Codes.

8 PART 3 Clause 12 Media Recording Standards Codes.

9 PART 3 Clause 10 Unit of Measure Codes.

10 PART 2, Annex D Data Exchange Form.

NOTE. These Enclosures are included for "completeness of documentation" purposes.Responsibility for their maintenance lies with the relevant DIGEST custodian nation.


v

NOTICE TO USERS

This international specification for UTM/UPS Standard Raster Product (USRP) has beendesigned to state the content and format of DGIWG’s standard raster product. Thisspecification now forms the baseline from which both system developers and NationalSurvey organisations can plan their development and production activities.

Research with all aspects of DGI is continuing within the DGIWG forum and anysubsequent potential changes will be subject to formal change control procedures.

RECORD OF AMENDMENTS

No. Date Entered By Remarks


vi

FOREWORD

AUTHORITY

1. This document is issued under the authority of the Digital Geographic InformationWorking Group. DGIWG comprises a group of international defence mapping agencieswhich is charged with encouraging the use of its standards in both the civil and defenceworlds. Current members of DGIWG are Belgium, Canada, Denmark, France,Germany, Italy, Netherlands, Norway, Spain, the UK and the USA.

PURPOSE AND SCOPE

2. Digital Geographic Information has evolved into one of the primary and mostessential elements of many system applications both for the Mapping, Charting andGeodesy (MC&G) Community and for many other users. This document provides thenecessary data structure, file organization, format and capture specifications to enablethe production of seamless raster data sets, UTM/UPS Standard Raster Product, on acommon world-wide datum. Other forms of this same basic file organization and formathave been created to enable the exchange of other types of MC&G raster data notexplicitly for use in seamless data sets.

3. USRP is based upon orthomorphic projections like topographic maps. Thisenables the immediate registration of every geographic data that was drawn, capturedor displayed onto a plan and allows for the easy computation of ranges, angles andbearings. Annex B deals with those formulae and algorithms, adapted for electroniccomputing, necessary to handle the USRP datums, geographic coordinates and gridcoordinates.

The data will be available on a common world wide reference datum of WorldGeodetic System (WGS ) 84.

APPLICATION

4. This specification applies to all activities involved in the capture, processing anddissemination of USRP data.

AMENDMENTS

5. Amendments to this specification will be the responsibility of the custodian, onbehalf of and in agreement with DGIWG, and will be issued as necessary, throughNational Point of Contact, to known document holders.

DISTRIBUTION

6. International distribution of this specification will be the responsibility of DGIWG.Within each DGIWG country this will be through the relevant national representative(point of contact). National points of contact can distribute freely outside DGIWGnations.


vii

PROPOSED CHANGES

7. Any proposed changes or comments should be keyed to the specific page,paragraph and line of the text. Reasons should be provided for each comment to ensureunderstanding and complete evaluation. Comments should be addressed to the originalPoint of Contact who will then forward the details to the custodian nation. DGIWG willensure that all such comments are processed through formal change controlprocedures.

TECHNICAL QUERIES

8. Any queries with regard to the content or application of this specification shouldbe addressed to the original Point of Contact.

SECURITY

9. This product specification is unclassified but the copying of this document isprohibited without the authority of the original Point of Contact.

CUSTODIAN

10. Ministère de la Défense Tel: (33) 1 42318953Etat-Major des ArméesCentre Géographique Interarmées Fax: (33) 1 42318950F-00450 ArméesFrance


viii

NATIONAL REPRESENTATIVES / POINTS OF CONTACT

The national representatives / Points of Contact are:

Belgium:Institut Géographique NationalAbbaye de la Cambre 13B 1050 BrusselsBelgium

Canada:Director of Geographic OperationsNational Defence HeadquartersMGen G. Pearkes BuildingOttawa, CanadaK1A 0K2

Denmark:Chief of Defence DenmarkLog Plans BranchPO Box 202DK-2950 VedvækDenmark

France:Centre Géographique InterarméesF-00450 ArméesFrance

Germany:Amt für Militärisches GeowesenFrauenberger Str 250Mercator Kaserne53879 EuskirchenGermany

Italy:IGMI — Via C. Battisti 1050100 FirenzeItaly


ix

The Netherlands:Directie Operatiën Koninklijke LandmachtSectie Militaire GeografiePostbus 907012509 LS Den HaagThe Netherlands

Norway:Norwegian Military Geographic Service (FMGT)Oslo Mil/AkershusN-0015 OsloNorway

Spain:Servicio Geografico del EjercitoDario Gazapo Num 828024 MadridSpain

UK:Requirements DivisionGeo Commitments GroupDG Military SurveyFeltham, Middlesex TW13 7AHUK

US:National Imagery and Mapping AgencyNIMA/SEIIMail Stop D-864600 Sangamore RoadBethesda, MD 20816-5003,USA


x

ACRONYMS AND ABBREVIATIONS

ANSI American National Standards Institute

ASCII American National Standard Code for Information Interchange

CHUM CHart Update Manual

CIE Commission Internationale de l'Eclairage(International Commission on Illumination)

CPI Characters Per Inch

DGI Digital Geographic Information

DGIWG Digital Geographic Information Working Group

DIGEST Digital Geographic Information Exchange Standard

FIPS Federal Information Processing Standards

FIPS PUB Federal Information Processing Standards Publication

GCR Group-Coded Recording

ISO International Organization for Standards

MC&G Mapping, Charting and Geodesy

PE Phase-Encoded

UPS Universal Polar Steographic Projection

USRP UTM/UPS Standard Raster Graphics

UTM Universal Transverse Mercator Projection

WGS 84 World Geodetic System 1984


Section 1 – Scope

1 - 1

1.0 SCOPE.

Digital Geographic Information (DGI) has evolved into one of the primary andmost essential elements of many information system applications both for theMapping, Charting and Geodesy (MC&G) Community and for other, diverseusers. This document provides the necessary data structure, file organization,format and capture specifications to enable the exchange of seamless raster datasets, UTM/UPS Standardized Raster Products (USRP), on a common world-widedatum. Other forms of this same basic file organization and format have beencreated to enable the exchange of other types of MC&G raster data not explicitlyfor use in a seamless data sets.

USRP Edition 1.3August 1997Section 1 – Scope

1 - 2

– This page is intentionally blank –


Section 2 – References

2 - 1

2.0 REFERENCES.

1. Digital Geographic Information Working Group, " Digital GeographicInformation Exchange Standards (DIGEST)":

• Part 1: General Description; Edition 1.2a, June 1995,

• Part 2: Theoretical Model, Exchange Structure, and EncapsulationSpecifications; Edition 1.2a, June 1995,

• Part 3: Codes, Parameters and Tags; Edition 1.2a, June 1995,

• Part 4: Feature and Attribute Coding Catalogue Edition 1.2a;June 1995.

2. Digital Geographic Information Working Group, "DIGEST Raster Profile",Edition 1.0, January 1995.

3. DMA Technical Report (DMATR) 8350.2, "DoD World Geodetic System1984: Its Definition and Relationship with Local Geodetic Systems," 2ndEdition; 1 September 1991.

4. Defense Mapping Agency Standard Printing Color Catalog for Mapping,Charting, Geodetic Data and Related Products, January 1987.

5. European Computer Manufacturer's Association (ECMA), "Standard forData Interchange on Read-Only 120 mm Optical Data Disks (CD-ROM)ECMA/TTC31/87/47, September 1987. (DRAFT)

6. ISO 646 – "Information processing – ISO 7-bit coded character set forinformation interchange", Second Edition, 1983.

7. ISO 1001 – "Information Processing – File Structure and Labelling ofMagnetic Tapes for Information Interchange Ed.2", 1986.

8. ISO 2022 – "Information Processing – ISO7 Bit and 8 Bit Coded CharacterSets -- Code Extension Techniques Ed. 3", 1986.

9. ISO 3788 – "Information Processing – 9 Track. 12,7 mm (0.5 in) WideMagnetic Tape for Information Interchange recorded at 63 cpmm (1600cpi), Phase Encoded. Ed. 1", 1976.

10. ISO 5652 – "Information processing – 9 track 12.7 mm (0.5 in.) widemagnetic tape for information interchange formats and recording, usinggroup coding 246 cpmm (6,250 cpi)".

11. ISO 8211 – "Information processing – Specification for a data descriptivefile for information interchange", 1985.

12. ISO 9660 – "Information Processing – Volume and File Structure of CD-ROM for Information Interchange. Ed. 1", 1988.

USRP Edition 1.3August 1997Section 2 – References

2 - 2

13. STANAG 2211 – Edition 5 amendment 2 – Geodetic Datums, Ellipsoids,Grids and Grid References, Dated 15-June-92.

14. STANAG 2215 – Edition 4 – Evaluation of Land Maps. Dated 19December, 1983.

15. STANAG 3671 Edition Designation System for Land Maps, AeronauticalCharts and Military Geographic Documentation, Edition 2.

16. STANAG 3716 Map Series Numbering, Edition.

17. DLMS Accuracy Working Group. (Accuracy Determination Method).

18. ISO 8859-1 – Information processing – 8-bits single byte coded graphiccharacter sets – Part1: Latin alphabet N°1, First Edition 1987-02-15.

19. ISO 6937 – Information processing – coded character sets for textcommunication, Ed. 1, 1983.

20. ISO/IEC/10646-1 – Information technology – Universal Multiple-Octetcoded character set (UCS), Part 1 : architecture and Basic MultilingualPlane, First Edition 1993-05-01.


Section 3 – General Information

3 - 1

3.0 GENERAL INFORMATION.

3.1 Description of UTM/UPS Standardized Raster Products (USRP).

3.1.1 Standardized Raster Graphics (SRGs) are digital replicas of graphicproducts. To digitally replicate the multiple colours present on many graphicproducts, each multicolour graphic is scanned and digitally separated into red,green, and blue components or colour-coded layers. The result can be severalimage bands that when combined, provide a multicolour digital replica of theoriginal graphic product. The total format of a graphic including margin, border,and legend areas are normally scanned at a resolution of 100 microns or less.

3.1.2 The UTM/UPS system is the projection and coordinate system for all USRPdata. The design objective of UTM/UPS is to provide graphic data in a virtuallyseamless manner and permit direct display in a conformal presentation. TheUSRP consists not only of the transformed graphic data but also a record thatcontains datum shift and projection parameters with which users can transformUSRP back to the source graphic's datum or projection; a graphic informationrecord that contains textual information about the source graphics; and an optionalsupplementary text field that contains textual descriptions of items depicted on theoriginal graphic.

3.2 THE UTM/UPS SYSTEM.

3.2.1 USRP data consists of colour-coded images with 100 microns (254 linesper inch) sample size, trimmed at the graphic's neat line and transformed to eitherthe UTM or UPS frame of reference. Data on the UTM/UPS system will bemaintained as a world-wide seamless data base of scanned graphic data onWorld Geodetic System 1984 (WGS 84). UTM/UPS data are divided into zonesas defined in STANAG 2211. Each zone is subdivided into an array of tiles, everyUTM zone is isometric to every other UTM zone.

3.2.2 The tiling system is structured such that for each UTM zone, the equatorand central meridian are always on the edges of whole tiles. In the same manner,for each UPS zone, the meridians 90°W-90°E and 0°-180° are always on theedges of whole tiles (See figure 3 - 1). Transmission of a dataset will always bein multiples of complete and adjacent tiles. Each tile represents 12.8 mm square(approximately .5 by .5 inch) of a hardcopy graphic image for all scales andgeographic locations. Each pixel nominally represents 100 microns square ofhardcopy graphic data.

3.2.3 Polar zones are square arrays of tiles overlaid mathematically on a polarstereographic (PST) projection. The use of the PST projection is to simplify theformulae to compute ranges, bearings and orthodromes.

3.2.4 A USRP geo data subset will contain one or more geo data files. Withineach (non-legend image) geo data file, data will be on the same zone referencesystem which includes overlap areas into the adjoining zone (See figure 3 - 2).

3.2.5 Each Zone contains a minimum 1024 pixel overlap into adjacent zones.

USRP Edition 1.3August 1997Section 3 – General Information

3 - 2

3.3 DATUMS.

The vertical datum for USRP data is the same as the vertical datum of the sourcegraphic. The horizontal datum is the World Geodetic System 1984. A set ofparameters is provided so that a user may shift back to the original geodeticsystem. These parameters are derived from Reference 2 The constants for theWGS 84 ellipsoid (extracted from Reference 2) are:

a = 6378137.0 metersb = 6356752.3142 meterse2 = 0.00669437999013

84°30'N84°30'N

80°30'S

180°

0°

90°W 90°E

84°N

180°

0°

90°W 90°E

80°S

UTM Zone UPS ZoneNB: Sizes and shapes are exaggerated for illustration purposes.

Figure 3 - 1 UTM/UPS Zone Tiling Organisation



3 - 3

Overlap Overlap

(Zone N -1 )GEO DATA FILE 1 (Zone N+1)GEO DATA FILE 3

ZDI ZDI

(Zone N)

Overlap Overlap

GEO DATA FILE 2

ZDI (Zone Data Image)

UTM Zone N - 1 UTM Zone N + 1UTM Zone N

A

B

C

D

EF

A

B

C

D

EF

Zone N (including overlaps)

MAIN RASTER IMAGE

Zone N -1 (including overlap)

Zone N +1 (including overlap)

Figure 3 - 2 Overlap AreasA multi-zoned USRP divided into component Zone Data Images (ZDI)


3 - 4

3.4 ACCURACY REQUIREMENTS.

Raster data will be captured and processed in a way which satisfies the followinghorizontal accuracy requirements. Vertical accuracy will remain unchanged fromthe source graphic.

3.4.1 Raster data collected from source graphics at scales of 1:100,000 orsmaller may retain the horizontal accuracy of the original source graphic, since theinaccuracy added as a result of digitization is generally less than the errortolerances built into the original source graphics’ horizontal accuracy figure.

3.4.2 Horizontal accuracy for Raster data collected from source graphics atscales larger than 1:100,000 may be determined after the image has beenrectified (if needed) using the method detailed below.

3.4.2.1 Coordinates of control points are determined in terms of the nominalsampling interval times the reciprocal scale of the graphic (i.e. the ground distancedefined by the number of pixels from the origin of the cartographic image). TheStandard Error (at 90% confidence limit) of their deviations, from thecartometrically derived coordinates, is calculated for both X and Y. These arecompounded with “Source Graphic’s Horizontal Accuracy Value” (AAH) to formthe total “Raster Horizontal Accuracy Value” (HAV) as follows:

HAV = (AAH2 + Xerror2+ Yerror2)1/2 .

An example is for a 1: 50,000 scale map where:

• AAH = 50 metres

• The sampling interval is 100 microns

• The Standard Error at 90% confidence limit is 200 microns (i.e. 2 pixels)which gives 2 x 100 x 50,000 = 10 meters in both X and Y.

This would give a total HAV = (502 + 102 + 102)1/2 = 52 metres

Ninety per cent of the points per graphic will fulfil the above condition.

3.5 COLOUR DEFINITION AND CODING.

3.5.1 Colour representation is in the form of colour-code. Each colour-code isstored in a colour look-up table together with its CIE (x, y, Y) reference (seeEnclosure 8) and nominal RGB intensity values. Where a colour-code representsa transition colour which is a known additive of two or more other coded coloursthen an equation defining the mixture will be given in the Quality Record subfieldFRM (Annex A 2.4).



3 - 5

Where given, the equation will be of the following form :

P1 * (CC1) + P2 * (CC2) +. . . Pn * (CCn)

Where P is the proportionCC is the colour-code (i,e label CCD) nand Σ Pi = 1 i = 1

Example :

If the colour that is coded 5 (CC5) is an additive mixture of 0.25 of CC3 and 0.75of CC6 then the equation for CC5 will be :

0.25* (3) + 0.75* (6)or 0.75* (6) + 0.25* (3)

The use of the equation is to allow easy modification of the colours for displaypurposes. For example, if it is necessary to alter the displayed colour for colours 3and for 6 then the changes to the related colour 5 can be directly computed asfollows:

Where R3, G3, B3 and R6, G6, B6 are the desired signal strengths/luminosities ofthe colours 3 and 6 respectively then :

R5 = 0.25* R3 + 0.75* R6G5 = 0.25* G3 + 0.75* G6B5 = 0.25* B3 + 0.75* B6

Note : The CIE stimuli (X,Y,Z) may be substituted for R,G,B in the aboveequations giving.

X5 = 0.25* X3 + 0.75 * X6Y5 = 0.25* Y3 + 0.75 * Y6Z5 = 0.25* Z3 + 0.75 * Z6

Where given the CIE reference (x,y,Y) then :

x * YX = ------

y

Y = Y

Y Z = ----- * (1 - x - y) y

3.5.2 If repromat is used, each layer (band) will be assigned a standard colour-code which matches the printing colour for which this repromat stands.


3 - 6

3.6 INSETS AND OUTSETS.

3.6.1 An inset is a separate map positioned within the neatline of a larger map.There are two types:

a. External Inset. This is an area geographically outside a sheet butincluded therein for convenience of publication, usually at the same scale.

b. Internal Inset. This is a portion of a map or chart, usually representing ahighly congested area, in which a decongested version of the area isdepicted in the same sheet, but in a different area of the sheet from thecongested version. Internal insets may be at a different scale from the scaleof the host graphic.

3.6.1.1 Any internal insets which appear on the source graphic will be describedin the Source File (described in Section 5.2.4). The INSET field provides thenecessary information to define a local transformation of the row and columnnumber into geographic or cartographic coordinates. This method can only applyto internal insets displayed in the same coordinate system as the main map.

3.6.1.2 Any external insets which occur on the source graphic will not bedescribed in the Source File. The inset is shifted to its correct geographic locationin the zone image and replaced in the main map by null pixels (see Figure 5-4).This method can only apply to external insets displayed in the same coordinatesystem as the main map.

3.6.1.3 An alternative may be the use of additional Geo Data Layers. The inset isextracted and held as another geo data layer within the same dataset. Thismethod can only apply to data sets displayed in the same coordinate system asthe main map. These could be either internal or external insets.

3.6.2 An outset occurs where part of a map protrudes beyond the neatline,causing a break in the neatline. Every such protruding part is called an outset.

3.6.2.1 When the detail contained in the outset is duplicated on the adjacent mapsheet, then it is trimmed to the neatline. If it does not appear on the adjacent mapsheet, it is included as an extension of the main image and the bounding polygonis adjusted to enclose the outset (see Figure 5-3).

3.7 MARGINALIA.

3.7.1 Legend Images, which provide valuable information on the source graphicbut are outside the neat lines, will be provided in separate data files (Section 5.2.3. and 5.2.5). Legend images are typically a minimum size to encompassthe type of images described below. The intention is that legend images arecapable of being displayed in less than a display screen full of data, and thereforethe image on the source may be subdivided for display convenience.

A legend image has no direct relationship to geographic location. Each legendimage is contained in its own file and is related to the source graphic by theLEGEND_IMAGE_RECORD in the SOURCE_FILE.



3 - 7

Some examples of legend images are provided below.

(a) Index Diagram

The index diagram shows the approximate geographic position of the graphic andits relationship to other graphics in the region (Figure 3 - 3)

Figure 3 - 3 An example Index Diagram

(b) Elevation/Depth (Bathymetric)Tint Diagram

The elevation/depth tint diagram is a multi-colour graphic depicting the coloursand/or tints used to represent different elevation or depth bands on the printedmap/chart (Figure 3 - 4)

Figure 3 - 4 An example Elevation/Depth (Bathymetric)Tint Diagram


3 - 8

(c) Glossaries

Glossaries are brief lists of foreign geographical terms appearing on the graphicwith their translated or transliterated equivalents (Figure 3 - 5).

Figure 3 - 5 An example Glossary

(d) Feature Symbols

Landmark feature symbols are used to indicate navigationally-prominent entities(Figure 3 - 6).

Figure 3 - 6 An example Feature Symbol table

3.7.2 Supplementary text appears on many maps and charts, most often toprovide textual data associated with special annotations. These may appear inthe margin or on the back of the chart and will be provided in a separate record onthe USRP volume (Section # 5.2.3). In addition, supplementary text is used tocapture items such as convergence tables, extended copyrights, etc.


Section 4 – Exchange Specification

4 - 1

4.0 EXCHANGE SPECIFICATION.

4.1 OVERVIEW OF THE SPECIFICATION.

This specification is designed to enable the exchange of USRP among nationsand has been structured to include:

a) Volume contentsb) Header Data Subsetc) Specific graphic details

i) Identification/descriptive detailsii) Data Set coverage and organizationiii) Source informationiv) Security aspects/classificationv) Data accuracy statementsvi) Graphic data content

d) Exchange media

Derived by reference to the DGIWG Digital Geographic Information ExchangeStandard (DIGEST, Reference 1), this specification identifies and details thosecriteria that are necessary to permit the exchange of data in a form that is direct,informative, and above all else, complete. Some flexibility has been allowed in theareas of data field sizes, colour representation, and the ordering of the data toenable full benefit to be gained in data density and in run length encoding asrequired. Alternatively, some rules have been fixed to insure conformity ofproduct and hence, ease of data receipt and handling by the recipient.

4.2 OVERVIEW OF THE RASTER DATA STRUCTURE.

4.2.1 An image may be separated into one or more image bands as depicted infigure 4-1. The image bands will be formatted into Sub Blocks. Each pixel valueis represented by a maximum of eight bits. The upper left corner of each SubBlock is the origin of the numbering sequence of lines and pixels (samples). EachSub Block consists of 128 pixels (square).

4.2.2 The ordering of Sub Blocks has the first Sub Block appearing in the verymost northwest corner and the last Sub Block in the very most southeast corner.An example is as follows: From west to east, there will be N number of SubBlocks. From north to south , there will be M number of Sub Blocks. Begin eachsequence from the upper left corner of a graphic. That position will be (1), andSub Block numbers are incremented by 1 along the row to N. Therefore the SubBlock to the east will be (2). The Sub Block to the south of Sub Block (1) will beSub Block (N+1). The Sub Block in the southeast corner will be Sub Block(N x M). Pixel values within a Sub Block are recorded in the same order.

USRP Edition 1.3August 1997Section 4 – Exchange Specification

4 - 2

ImageBands {

12

321

N+ 1

N x M

Pixel (N Bits )

SCAN LINE

SUB BLOCK AND PIXELORGANIZATION WITHIN AN IMAGE

Record

N

2N

Rows 1 to M

Columns 1 to N

P

Q

P = Q = 128 pixels

Figure 4 - 1 Sub Block and Pixel Organization

4.2.3 Zero fill is defined as the colour-code zero. Zero fill may be used within aSub Block at the beginning or end of each line. If the actual number of samplesper image line is not an integer multiple of 128, zero fill will be added to producethe next integer multiple of 128 samples. Zero fill may be used preceding the firstline or following the last line of actual image data in a Sub Block. If the actualnumber of lines is not an integer multiple of 128, zero fill will be added to producethe next integer multiple of 128 lines. Therefore, zero fill for a zone image may beon any or all edges. (See Figure 4-2)



4 - 3

Image dataLSO,PSO(c,r) = (0,0)

(c,r) = (NLS,NLL)

(c,r) = (NUS,NUL)

TILE(128X128 pixels)

MBR

Pad(black)

pixels ZONE DATA IMAGE

Note : The subfield values NUS, NUL, NLS and NLL are image coordinates given in theDATA_SET_PARAMETERS_FIELD, SPR.The subfield values LSO and PSO are image origin coordinates given in theGENERAL_INFORMATION_FIELD, GEN, for each Zone Data Image (ZDI).

Sizes and shapes are exaggerated for illustration purposes.

Figure 4 - 2 USRP Zone Data Image tile structure.

4.2.4 Full tiles of zero (null) pixels may be omitted from an image. Tiles(subblocks) containing non-zero (non-null) pixels are placed into the image file insequential order but without leaving space for omitted tiles. A rectangular array ofintegers, the Tile Index Map (M (c,r)), is used to indicate which tiles are present.There is one row of integers in the tile map for each row of tiles in the image, andeach integer in the row corresponds with a tile in the row of tiles in the image. Thevalue of each entry M (c,r) indicates whether or not tile (c,r) of the image ispresent in the image file, and for a tile which is present, tells the tiles sequenceposition or starting byte address, in the image file. M (c,r) is defined by:

M (c,r) = 0 or null if tile (c,r) is omittedM (c,r) = (sequence number >0 if tile (c,r) is present or start byte address)

If the image is compressed (i.e., Run Length Encoded) then the start byte addressof each tile is the byte number within the image data (SCN field) numbering fromone (the first byte). If the image is uncompressed (i.e., not Run Length Encoded)then it is the tile sequence position in the image file and when M (c,r) > 0 the value(M-(c,r)-1) indicates how many tiles of stored data in the image file must beskipped to access the tile in column c, row r of the image (See figure 4 - 3).


4 - 4

The Tile Index Map is present only when tiles have been omitted from the imagefile or optionally the data is Run Length Encoded. A flag is provided to indicate ifthe tile map is present.

TileTileTileTileTileTileTileTileTile(2,2)(1,2)(3,1)(2,1)(1,1)(0,1)(3,0)(2,0)(1,0)

0 1 2 3

0

1

2

0 1 2 3

4 5 6 7

8 9 00

null (1,0) (2,0)

(0,1) (1,1) (2,1) (3,1)

(1,2) (2,2) nullnull

Tile Index Map showing the tile sequence on Storage Media

Zone Image Tiles

Image File on Storage Media

RC

(3,0)

Figure 4 - 3 Tile index map example with null tiles.

4.2.5 The files of a USRP data exchange must conform to the specifications ofISO 8211. Annex A specifies files, records, fields and their contents. This annexalso specifies the field tags and subfield labels to be utilized. Under allcircumstances data types must agree with the data and conform to ISO 8211.

4.3 SCAN LINES

Each SCAN LINE contains the pixel data for a line of pixels in a Subblock.Because of the repetitive nature of pixel/raster data, the PIX subfield contains twoimplicit elements which are fixed length binary integers with no separatorsbetween them. Each scan line starts on a byte boundary, any remaining bits inthe final byte are ignored (i.e., padding with any combinations of 0's and 1's). Theimplicit elements of the PIX Subfield have the logical form as depicted below,where each run of pixels is composed of two elements:

- Pixel count- Pixel value



4 - 5

Pixel Count Value 1 1

Pixel Count Value 2 2

* * * Pixel Count Value 'n' 'n'

run 1 run 2 run "n"

4.3.1 The Pixel Count subfield defines the number of pixels with the value of thefollowing Pixel Value. The sum of all the Pixel Counts in a scan line of a subblock(tile) will be equal to 128 pixels (i.e., Wraparound of pixel runs to following scanlines is not allowed since pixels would not be physically adjacent).

n PNC = Σ (pixel count)i = 128

i = 1

where PNC represents the number of pixels per scan line.

4.3.2 The length of the binary integer subfields are defined (in bits) in the GeneralInformation Record (GEN) of the General Information File (GIN) by the followingattributes:

PCB = Size of Pixel Count element in Bits.PVB = Size of Pixel Value element in Bits.

4.3.3 If PCB is set to 0 then there is no count subfield and the value of the countis assumed to be one in all cases and the scan line structure reduces to anuncompressed form as follows:

Value1

Value2

* * * Value128

PNC

4.3.4 In the case of colour coded images separated into bands, each containingonly two colours (e.g. black and white, or brown and transparent), then attributePVB can be set to 0 (zero) and the scan line reduces to a string of count elementsas follows:

Count1

Count2

* * * Count'n'

The convention used is that the first count in this scan line refers to the colourdefined for the 'off' state, which is the subfield "WS2" in the GENERALINFORMATION_FILE. This count element may therefore be zero. Subsequentcount elements alternate in the colour they apply to. As before, the sum of thePixel Counts will be equal to 128 pixels.


4 - 6

4.4 GENERAL REQUIREMENT.

4.4.1 Field Use. When a field is present, all subfields are mandatory. Whereinformation is not available, or not applicable:

– fixed-format subfields will be filled with ASCII spaces (i.e. ISO 646 (2/0)).– variable-width subfields will be filled with null values (i.e. .consist solely of

the delimiter).

4.4.2 Decimal Mark. The decimal mark in all numeric representation shall be theFULL STOP ,i.e., ISO 646 (2/14).

4.4.3 Digest Specific Data Syntax. Data items having DIGEST specific syntax,e.g., dates, shall be encoded according to the applicable Section, Annex orAppendix to that document - Relevant Enclosures from that document areincluded at the end of this specification.

4.4.4 Interpretation of Binary Fields. The bits in a byte are identified by b8, b7, b6,b5, b4, b3, b2, b1, where b8 is the highest order bit and b1 is the lowest order bit.For binary fields representing scanlines, the bits are to be sequenced highestorder to lowest order. Thus when PCB = 4 and PVB = 0 then bits b8 to b5 will bevalued first, followed by bits b4 to b1. Note that when PCB = 4 and PVB = 8, pixelvalues will span alternate byte boundaries subject to the restrictions in paragraph4.3.


Section 5 – Logical Structure

5 - 1

5.0 LOGICAL STRUCTURE.

USRP data transfers are composed of the Transmittal Header File (THF) whichoccurs once and one or more data sets, each of which consist of the Header DataSubset and the Geo Data Subset. Information about the volume security, numberof data sets on the volume (optional), and the volume number will be present inthe ISO media label, in accordance with the standards described in section 6.The logical view of these two data subsets is explained below. The THF will bedescribed in section 5.2.1 below. (see Figure 5-1).

HEADER DATASUBSET

GEO DATA SUBSET

DATA SET

Figure 5-1 Logical Data Set

5.1 LOGICAL DESCRIPTION OF DATA SUBSETS.

5.1.1 HEADER DATA SUBSET.

The Header Data Subset is a logical construct composed of the following:

1. A General Information File Occurrence: Once per data set

2. A Geo Reference File Occurrence: Once per data set

3. A Source File Occurrence: Once per source (several sourcesmay occur per data set)

4. A Quality File Occurrence: Once per data set

5.1.2 GEO DATA SUBSET.

The Geo Data Subset is a logical construct defined as a collection of digitalinformation representing either physical and cultural characteristics of the earth'ssurface (which is called the main raster image); or legend information which iscalled the raster legend image). The Geo Data Subset is composed of thefollowing:

A Geo Data File Occurrence: - Once per UTM zone of the Main Raster Image - Once per Raster Legend Image

USRP Edition 1.3August 1997Section 5 – Logical Structure

5 - 2

5.2 FILE STRUCTURES.

5.2.1 TRANSMITTAL HEADER FILE.

The TRANSMITTAL HEADER FILE occurs only once on each transmittal and forserial media is located at the beginning immediately following the volume label. Itcontains a general description of the contents of the Transmittal.

The TRANSMITTAL HEADER FILE consists of two records with the fields asshown below.

TRANSMITTAL DESCRIPTION RECORD• TRANSMITTAL HEADER• DATA SET DESCRIPTION

SECURITY AND UPDATE RECORD• SECURITY AND RELEASE• UP-TO-DATENESS

Entity Name Description or Contents

FILE TITLE Transmittal Header File

TRANSMITTAL DESCRIPTION RECORD

TRANSMITTAL HEADER Provides information about the originator ofthe transfer, media standard, and otherinformation pertinent to the transfer.

Media Standard Media recording standard used for thistransmittal (see Enclosure 8 for Codes ofapplicable media standards)

Originator Free text, title and address of originator(\ used as a line separator)

Addressee Free text, title and address of addressee(\ used as a line separator)(null for CD-ROM)

Number of Volumes Number of media volumes in this transmittal(may be null or zero for magnetic tape)

Number of Data Sets Number of Data Sets in this transmittal

Transmittal ID Unique ID for this transmittal (Free Text)

Edition Number Transmittal Edition Number

Date Creation date for this transmittal.



5 - 3

The following set of entities is repeated for each data set of the transmittal

DATA SET DESCRIPTION Contains information about the geographicextent, identification, and structure of eachdata set in the transfer.

Data Set ID Name of this Data set: six alphanumericcharacters which uniquely identify thedataset to which the file belongs,(e.g. Unique dataset reference number).See section 6.4.for naming conventions)

Data Structure Code Data structure code 4 = Raster ColourCoded

Product Type Composed of two parts separated by acomma ",": {<Product type>, <series or leveldesignator >} (eg,USRP,1501G).The first part is mandatory. The second partis optional.

Longitude of SW Corner of MBR(Minimum Bounding Rectangle)

Westernmost longitude of the extent of theunpadded cartographic image. If either thenorth or south pole lies inside thecartographic image, the value will be -648000.00 seconds (i.e.,-180 degrees).

Latitude of SW Corner of MBR(Minimum Bounding Rectangle)

Southernmost Latitude of the extent of theunpadded cartographic image . If the southpole lies inside the cartographic image, thevalue will be-324000.00 seconds (i.e., -90 degrees).

Longitude of NE Corner of MBR(Minimum Bounding Rectangle)

Easternmost longitude of the extent of theunpadded cartographic image . If either thenorth or south pole lies inside thecartographic image, the value will be+648000.00 seconds (i.e., +180 degrees).

Latitude of NE Corner of MBR(Minimum Bounding Rectangle)

Northernmost Latitude of the extent of theunpadded cartographic image. If the southpole lies inside the cartographic image, thevalue will be +324000.00 seconds (i.e., +90degrees).

Note: The above four values must be a latitude and longitude in WGS 84


5 - 4

SECURITY AND UPDATE RECORD

SECURITY AND RELEASE Provides information about the securityclassification of the transfer as a whole.

Highest Security Classification Highest security classification of thetransmittal

T= TOP SECRETS= SECRETC= CONFIDENTIALR= RESTRICTED (or alternatively "FOR OFFICIAL USE ONLY" (Administrative classification only))U= UNCLASSIFIED

Downgrading instructions Originating agency's determination isrequired for downgrading: Y (Yes) or N (No)

Date of downgrading Date of downgrading (blank if answer toprevious entity is YES or if securityclassification is equal to "U")

Releasability statement Releasability restrictions for this transmittal.If no release restriction exists,"UNRESTRICTED" shall be entered in thisentity.

UP TO DATENESS Provides information regarding the USRPspecification edition to which this transferconforms.

DIGEST Edition Number Free text -Identifier of DIGEST editionnumber used for all datasets of thistransmittal. (e.g. DIGEST 1.2a)

DIGEST Edition Date Publication date of DIGEST. (e.g.19950630)

DIGEST Amendment Number Latest DIGEST amendment number.(e.g.1)

USRP Edition Number Free text -Identifier of USRP edition numberused for all datasets of this transmittal. (e.g.USRP 1.3)

USRP Edition Date Publication date of USRP. (e.g. 19970831)

USRP Amendment Number Latest USRP amendment number.(e.g.0)



5 - 5

5.2.2 GENERAL INFORMATION FILE

The GENERAL INFORMATION FILE contains information pertaining toformatting, sequencing and file organization which is helpful for the user andmachine reading of the file. The file also includes other general information aboutthe actual content of the Data Set File.

The possible logical entities of the General Information File are as follows:

GENERAL INFORMATION RECORD• DATA SET IDENTIFICATION• GENERAL INFORMATION• DATA SET PARAMETERS• BAND IDENTIFICATION• TILE INDEX MAP

DATASET DESCRIPTION RECORD• DATA SET DESCRIPTION


FILE TITLE General Information File

GENERAL INFORMATIONRECORD

Repeated for each Zone or Layer in theData Set

DATA SET IDENTIFICATION Gives information about the Geo DataSubset identification.

Product Type Composed of two parts separated by acomma ",": {<Product type>, <series or leveldesignator >} (eg,USRP,1501G).The first part is mandatory. The second partis optional.

Data Set ID Name of this Data set: six alphanumericcharacters which uniquely identify thedataset to which the file belongs,(See section 6.4.for naming conventions)

GENERAL INFORMATION Gives information about the Geo DataSubset content.

Data Structure Structure of Data (4 for Raster ColourCoding)

Data Density E/W Data density (E-W) or pixel size at groundscale

Data Density N/S Data density (N-S) or pixel size at groundscale


5 - 6

Data Density Units Unit of measure used for Data Density inE/W and N/S directions. (See Enclosure 9)

Zone Number UTM /UPS Zone number ("-" indicatesNorth Origin (PSO) is in the Southernhemisphere 01-60 indicates UTM Zonenumber , 61 indicates UPS Zone number )

Longitude of SW Corner of MBR(Minimum Bounding Rectangle)

Westernmost longitude of the extent withinthe zone (including overlap) of theunpadded cartographic image.(i.e. NOT including margin and legendinformation and bleeding edges).

Latitude of SW Corner of MBR(Minimum Bounding Rectangle)

Southernmost Latitude of the extent withinthe zone (including overlap) of theunpadded cartographic image .(i.e. NOT including margin and legendinformation and bleeding edges).

Longitude of NE Corner of MBR(Minimum Bounding Rectangle)

Easternmost longitude of the extent withinthe zone (including overlap) of theunpadded cartographic image .(i.e. NOT including margin and legendinformation and bleeding edges).

Latitude of NE Corner of MBR(Minimum Bounding Rectangle)

Northernmost Latitude of the extent withinthe zone (including overlap) of theunpadded cartographic image.(i.e. NOT including margin and legendinformation and bleeding edges).

(The above four values must be a latitude and longitude in WGS 84.)

Reciprocal Scale Reciprocal scale of data set. (e.g., 50000for 1:50,000). This is usually the scale ofthe source material.

Pixel Spacing Sample (pixel) spacing at which the datawas originally captured (in microns)

Rectified Image Image rectified. (Yes or No)

Easting of Origin Easting of upper left pixel of the paddedImage within the Zone

Northing of Origin Northing of upper left pixel of the paddedImage within the Zone

Text Free text. (e.g. Description of Digitizingequipment)



5 - 7

DATA SET PARAMETERS Gives information which providesparameters to interpret the Geo DataSubset.

Row number of MBR (MinimumBounding Rectangle) N/E corner

Row number of the upper right corner of theMBR of the unpadded Zone Data Image.(see figure 4-2)

Column number of MBR(Minimum Bounding Rectangle)N/E Corner

Column number of the upper right corner ofthe MBR of the unpadded Zone DataImage. (see figure 4-2)

Row number of MBR (MinimumBounding Rectangle) S/WCorner

Row number of the lower left corner of theMBR of the unpadded Zone Data Image.(see figure 4-2)

Column number of MBR(Minimum Bounding Rectangle)S/W Corner

Column number of the lower left corner ofthe MBR of the unpadded Zone DataImage. (see figure 4-2)

Number of Sub-blocks Vertically(Bottom to Top)

Number of Sub Blocks North to South (seefigure 4-1 : M)

Number of Sub-blocksHorizontally (Left to Right)

Number of Sub Blocks West to East (seefigure 4-1 : N)

Number of Pixels Left to Right Number of Pixels/Sub-block Line (see figure4-1 : Q = 128)

Number of Pixels Top to Bottom Number of Scan Lines/Sub-block (seefigure 4-1 : P = 128)

Column Sequence Column Sequence (0 for left to right)

Row Sequence Row Sequence (1 for top to bottom)

Pixel Order Pixel order (0 for column in row, in band, insubblock)

Pixel Count Length Size of pixel count in bits

Pixel Value Length Size of pixel value in bits

Image File Name Image File Name (ZZZZZZDD.IMG, Seesection 6.4)

Tile Index Map Flag Tile Index Map flag (see section 4.2.4.). "Y" indicates there is an index, "N" indicates there is none.


5 - 8

BAND IDENTIFICATION Gives information about each individualband in a raster image. The three entitiesare repeated for each colour band withinthe Geo Data File The order in which thecolour bands are recorded in this field is theorder they must appear in the Geo DataFile

Band ID Identification of the band. (e.g. RED)Repeat as necessary

The two following entities are omitted or null except when the Geo Data File iscomposed of multiple bi-colour bands (see section 4.3.4)

"ON" colour code value "ON" colour code value

"OFF" colour code value "OFF" colour code value

TILE INDEX MAP Contains information regardingSubblocks/tiles (see section 4.2.4. forusage criteria). This entity is required only ifthe Tile Index Map Flag = "Y"

Tile Index Value Values of Tile Index Map (a zero or nullvalue corresponds to an omitted sub-block,see Section 4.2.4.).

DATA SET DESCRIPTION RECORD

DATA SET DESCRIPTION Contains information on the number ofaccuracy subregions, zone images, andsource graphics in the dataset

Number of Horizontal AccuracySub-Regions

Identifies the number of HorizontalAccuracy Sub-Regions appearing in thedataset

Number of Vertical AccuracySub-Regions

Identifies the number of Vertical AccuracySub-Regions appearing in the dataset

Number of Zone Images Identifies the number of Zone Imagesappearing in the dataset

Number of Source Graphics Identifies the number of Source Graphicsappearing in the dataset



5 - 9

5.2.3 GEO REFERENCE FILE

The GEO REFERENCE FILE refers to the whole Geo Data Subset and containsparametric information used to transform and/or integrate the data into existingdata bases by evaluation of the given geodetic parameters. Each HDS contains asingle GEO REFERENCE FILE.

The logical entities of the GEO REFERENCE FILE are as follows :

GEO REFERENCE RECORD• GEO PARAMETERS• PROJECTION


FILE TITLE Geo Reference File

GEO REFERENCE RECORD

GEO PARAMETERS Identifies the following group of entities thatdescribe and aid the interpretation of thegeodetic system of the data.

Data Type Type of data comprising the Dataset (MAP)

Units Units of measure for this Dataset. (M, seeEnclosure 9)

Ellipsoid Name of the ellipsoid to which the Datasetrefers (World Geodetic system 1984)

Ellipsoid Code Code of the ellipsoid to which the Datasetrefers. (WGE , see enclosure 3)

Datum Geodetic Name Name of the Geodetic Datum. (WorldGeodetic system 1984)

Datum Geodetic Code Code of the Geodetic Datum. (WGE , seeenclosure 4)


5 - 10

PROJECTION Identifies the following group of entities thatdescribe the projection of the data. (seeenclosure 5)

Projection Name Name of the projection used in the Dataset.(Universal Transverse Mercator orUniversal Polar Stereographic)

Projection Code Code of the projection (TC or PG).

Parameter 1 Projection Parameter 1.


Projection False OriginX (easting ) false origin of the projection.Y (northing) false origin of the projection.

5.2.4 SOURCE FILE

The SOURCE FILE provides information about source documents only to whichthe data set file refers. A source document is usually a single map or chart fromwhich the image or part of an image was derived. If this file is repeated thesources will normally be from the same map series.

The SOURCE FILE repeats once per source document.

The logical entities of the SOURCE FILE are as follows :

SOURCE RECORD• SOURCE SUMMARY• SOURCE• MAGNETIC INFORMATION• BOUNDING POLYGON COORDINATES• PROJECTION• SECURITY AND RELEASE• INSET• COPYRIGHT

LEGEND RECORD• LEGEND DATA• LEGEND PARAMETERS• TILE INDEX MAP



5 - 11

METRIC SUPPORT RECORD• DATUM CHANGE CONSTANTS• SOURCE DATUM COEFFICIENTS COUNTER• SOURCE DATUM LONGITUDE COEFFICIENTS• SOURCE DATUM LATITUDE COEFFICIENTS• GRID ROTATION COEFFICIENTS

SUPPLEMENTARY TEXT RECORD• SUPPLEMENTARY TEXT


FILE TITLE Source File.

SOURCE RECORD

SOURCE SUMMARY Identifies the number of supplementary textrecords, legend images and insets fromeach source graphic

Number of supplementary textrecords

Provides number of supplementary textrecords in the file derived from the source

Number of Legend Images Provides number of legend images in thefile derived from the source

Number of Insets Provides number of insets in the file derivedfrom the source

SOURCE Provides information on the source used orreferenced to create the data contained inthe data set file.

Series Series Designator. : Will be used inconformance with STANAG 3716 (e.g.1501)

Unique Source Identification Source ID - Number or name which whenused in conjunction with the Series andEdition will identify a unique source.

Source Edition Number Source Edition Number Will be used inconformance with STANAG 3671

Full Name of source document Full Name: The complete name of agraphic (Free Text).


5 - 12

Type of Significant Date A significant date is a designated date thatmost accurately describes the basic date ofproduct for computation of the probableobsolescence date. It can be thecompilation date, revision date, or otherdepending on the product andcircumstances. (See Enclosure 1 for Typeof date codes (CDP))

Significant Date Value The actual date that most accuratelydescribes the basic date of product forcomputation of the probable obsolescencedate.

Country Code Country Code: used to identify the primarygeopolitical area associated with theproduct. (See Enclosure 7 for countrycodes )

Perishable Date Perishable information date value

Reciprocal Scale Reciprocal of cartographic scale (e.g.50,000 for 1/50,000 scale)

Cartographic Grid Code Cartographic Grid Code: An identificationof the cartographic grid(s) used on theproduct. (see Enclosure 2 Grid Codes)

Area Coverage Area Coverage. A number, with unit below,specifying how many square units of areacoverage (e.g., 43,000 km2)

Unit of measure for areacoverage.

Unit of measure for area coverage.(See Enclosure 9 )

Predominant Contour Interval Contour Interval: Value of the primary/basicinterval between contour lines on the mapor chart.

Contour Unit of Measure Contour Unit of Measure: Identifies the unitof measure of the interval betweenconsecutive contour lines on the product.(See Enclosure 9).

Water Coverage Percent Water: The percentage of theproduct that is covered by water. (999 = Unknown)

Navigational System Type Navigational system type (e.g. LORAN)(see Enclosure 1 NST)



5 - 13

Ellipsoid Name Ellipsoid Name: This component containsthe name of the ellipsoid on which thesource product was produced.

Ellipsoid Code Ellipsoid Code: This Component contains acode of the name of the ellipsoid on whichthe source product was produced. (SeeEnclosure 3).

Vertical Reference Name Datum of Vertical Reference Name: Nameused to describe the vertical referencesystem on which the product was produced.Usually the name of the port or city wherethe datum is located (Example: MSL atCagliari 1955-57)May be null if no elevation informationis present on the source.

Vertical Reference Code Datum of Vertical Reference Code. (SeeEnclosure 4).May be null if no elevation informationis present on the source.

Sounding Datum Name Sounding Datum Name (See Enclosure 4)May be null if no sounding information ispresent on the source.

Sounding Datum Code Sounding Datum Code: Code used torepresent the Sounding Datum. (SeeEnclosure 4). May be null if no soundinginformation is present on the source.

Geodetic Datum Name Geodetic Datum Name: Represents theproduct's geodetic control datum. (seeEnclosure 4).

Geodetic Datum Code Geodetic Datum Code: Code used torepresent the Geodetic Datum.( See Enclosure 4).

Highest Elevation Highest Known Elevation (of the source-ASCII spaces if unknown)

Units of the elevation value Units of the elevation value (ASCII spaces ifHighest elevation is unknown)(See Enclosure 9).

Easting of Highest Elevation Easting of the highest known elevation( null if Highest elevation is unknown)

Northing of Highest Elevation Northing of the highest known elevation(null if Highest elevation is unknown)


5 - 14

MAGNETIC RATE Provides information on the magnetic rateof change on a given source. The field maybe repeated if more than one magnetic rateof change applies for a source.

Type of Date (magnetic) Type of Date of magnetic information ( seeenclosure 1 CDP)

Date (magnetic) Date of magnetic information

Rate of Change Annual Magnetic rate of change

Units of change Units magnetic rate of change (SeeEnclosure 9)

Grid-Magnetic Angle Grid north to Magnetic north (G-M) Angle(Clockwise regarded as positive)

Units of G-M Angle Units of G-M Angle (See Enclosure 9)

Easting of the G-M anglereference point

Easting of the G-M angle reference point

Northing of the G-M anglereference point

Northing of the G-M angle reference point

Convergence Angle Grid convergence angle

Unit of Convergence Angle Units of grid convergence angle

BOUNDING POLYGONCOORDINATES

Lists the coordinates of the source polygon.There may be several bounding polygonsfor the source.

Easting coordinate Easting coordinate

Northing coordinate Northing coordinate

PROJECTION Provides information about the mapprojection used in the Source Data. (SeeEnclosure 5)

Projection Name Projection Name: Name given to thecartographic projection of the sourcegraphic. (free text)

Projection Code Code of the projection. Projection may haveup to 4 parameters, as follows. (SeeEnclosure 5)




5 - 15

Parameter 2 Projection Parameter 2. May be nulldepending on the Projection Code value.(See Enclosure 5)



Projection False Origin X and Y (Easting and Northing) false originof the map grid (0's if not applicable)

SECURITY and RELEASE Provides information about the security andreleasibility of the source to which it refers.

Security Classification Security classification of the Source:T = TOP SECRETS = SECRETC = CONFIDENTIALR = RESTRICTED (or alternatively "FOR OFFICIAL USE ONLY" (Administrative classification only))U=UNCLASSIFIED

Downgrading Originator's permission for downgradingrequired. Y(Yes) or N(No)


Releasability Releasability restrictions for data from thissource. If no release restrictions exist,"UNRESTRICTED" shall be entered in thisentity.(Free text)

The following set of entities is repeated for each inset in the data set orabsent of no inset exists.

INSET Provides information about the relative andabsolute coordinates of the inset.

Inset Identification Unique ID for the Inset.

Reciprocal cartographic scale ofinset

Reciprocal of cartographic scale of Inset(e.g., 50,000 for 1:50,000).

Inset Name Name of Inset.


5 - 16

Absolute Coordinates Absolute Easting and Northing coordinatesof lower and upper left corners and lowerand upper right corners of the inset asstated in the inset coordinates.

Relative Coordinates Relative Easting and Northing coordinatesof lower and upper left corners and lowerand upper right corners of the inset asstated in the host graphic coordinates (thevalue of these Easting and Northing arestated in terms of host graphic, as if theinset did not appear on the host graphic).

COPYRIGHT Is a free text field which contains applicablecopyright information for the source graphic.

Copyright statement Free text for the copyright statement. If nocopyrights exist, "UNCOPYRIGHTED'" shallbe placed in this entity.

The following set of entities is repeated for each legend image related to thissource and is omitted if no legend is transmitted.

LEGEND RECORD

LEGEND DATA Provides information on the legendinformation captured to permit an easierinterpretation of the source to which itrelates.

Legend name Legend name (i. e., TYPE of legendImage). Free Text: See Section 3.7.1

Data Structure Code Data Structure code (4 for Raster ColourCoded)

LEGEND PARAMETERS Provides parameters to interpret theLegend Image Data.

Row number of MBR (MinimumBounding Rectangle) UR corner

Row number of the upper right corner of theLegend Image.

Column number of MBR(Minimum Bounding Rectangle)UR Corner

Column number of the upper right corner ofthe Legend Image.

Row number of MBR (MinimumBounding Rectangle) LL Corner

Row number of the lower left corner of theLegend Image.

Column number of MBR(Minimum Bounding Rectangle)LL Corner

Column number of the lower left corner ofthe Legend Image.



5 - 17

Number of Sub-blocks Vertically(Bottom to Top)

For the legend, number of Sub BlocksNorth to South

Number of Sub-blocksHorizontally (Left to Right)

For the legend, number of Sub Blocks Westto East

Number of Pixels Left to Right Number of Pixels/Sub-block Line

Number of Pixels Top to Bottom Number of Scan Lines/Sub-block

Column Sequence Column Sequence (0 for left to right)

Row Sequence Row Sequence (1 for top to bottom)

Pixel Order Pixel order (0 for column in row, in band, insubblock)

Pixel Count Length Size of pixel count in bits

Pixel Value Length Size of pixel value in bits

Legend File Name Legend File Name (ZZZZZZDD.Lcc, Seesection 6.4)

Tile Index Map Flag Tile Index Map flag (see section 4.2.4.). "Y" indicates there is an index, "N" indicates there is none.

TILE INDEX MAP Contains information regardingSubblocks/tiles (see section 4.2.4. forusage criteria). This entity is required only ifthe Tile Index Map Flag = "Y"

Tile Index Value Values of Tile Index Map (a zero or nullvalue corresponds to an omitted sub-block,see Section 4.2.4.).

METRIC SUPPORT RECORD (see annex B)

DATUM CHANGE CONSTANTS Provides constants that are used inapplying the coefficients in the SourceDatum Coefficients Data Field to computegeographic coordinates relative to thesource datum geographics from WGS 84geographic coordinates.

Latitude normalizing offset Latitude normalizing offset in degrees anddecimal part of a degree.

Longitude normalizing offset Longitude normalizing offset in degrees anddecimal part of a degree.


5 - 18

Normalizing factor Normalizing factor

Eastern limit of validity Eastern limit of validity to use multipleregression equations (in degrees anddecimal part of degree).

Western limit of validity Western limit of validity to use multipleregression equations (in degrees anddecimal part of degree).

Northern limit of validity Northern limit of validity to use multipleregression equations (in degrees anddecimal part of degree)

Southern limit of validity Southern limit of validity to use multipleregression equations (in degrees anddecimal part of degree).

SOURCE DATUMCOEFFICIENTS COUNTER

Provides the numbers of longitude/latitudecoefficients contained in the SLG/SLTfields.

Number of longitude coefficients. Number of longitude coefficients.

Number of latitude coefficients. Number of latitude coefficients.

SOURCE DATUM LONGITUDECOEFFICIENTS

Provides longitude coefficients to be usedconcurrently with normalizing factors andparameters in order to derive source datumgeographic coordinates from WGS84geographic coordinates by means ofMultiple Regression Equations (MRE).

i long indice i indice of the coefficient of MRE b i,j.

j long indice j indice of the coefficient of MRE b i,j.

Coefficient of MRE b i,j. Coefficient of MRE b i,j. (b i,j. coefficientsare ordered with respect to increasing ithen j -See Annex B .



5 - 19

SOURCE DATUM LATITUDECOEFFICIENTS

Provides latitude coefficients to be usedconcurrently with normalizing factors andparameters in order to derive source datumgeographic coordinates from WGS84geographic coordinates by means ofMultiple Regression Equations (MRE).

i lat indice i indice of the coefficient of MRE a i,j.

j lat indice j indice of the coefficient of MRE a i,j.

Coefficient of MRE a i,j. Coefficient of MRE a i,j. (a i,j. coefficientsare ordered with respect to increasing ithen j -See Annex B .

GRID ROTATIONCOEFFICIENTS

Provides coefficients that are used to derivesource datum grid coordinates from WGS84 UTM and UPS grid coordinates.

Normalized Easting shift Normalized Easting shift

Normalized Northing shift Normalized Northing shift

Angle of orientation Angle of orientation from source datum gridto WGS UTM grid


5 - 20

SUPPLEMENTARY TEXT RECORD

SUPPLEMENTARY TEXT Provides free format text for a variety ofpurposes including alternative for mediadescriptions.

Text Record Type Supplementary Text Record Type Thissubfield will contain a code identifying thesupplementary text type. The followingtypes have been defined :

CONV Convergence table informationCPYZ Extended copyright noticeDATM Datum subregion identifierMISC MiscellaneousNOTE Textual CHUM notesXXXX Other codes

(when mutually agreed upon).

Text Reference ID Supplementary Text Field ReferenceIdentifier . Used to index several entries ofthe same type

Textual information. Free Text



5 - 21

5.2.5 QUALITY FILE

The QUALITY FILE gives information about the whole Geo Data Subset quality.

The logical entities of the QUALITY FILE are as follows:

QUALITY RECORD• SECURITY AND RELEASE• UP-TO-DATENESS• COLOR CODE IDENTIFIER• OTHER QUALITY INFO

HORIZONTAL ACCURACY RECORD• HORIZONTAL ACCURACY• BOUNDING POLYGON COORDINATES

VERTICAL ACCURACY RECORD• VERTICAL ACCURACY• BOUNDING POLYGON COORDINATES


FILE TITLE Quality File.

QUALITY RECORD

SECURITY AND RELEASE Provides security classification, handlingand release information.

Security Classification Highest security classification within thedata set.T = TOP SECRETS = SECRETC = CONFIDENTIALR = RESTRICTED (or alternatively "FOR OFFICIAL USE ONLY" (Administrative classification only))U = UNCLASSIFIED

Downgrading Originating agency's determination isrequired for downgrading. Y(Yes) or N(No)


Releasability Releasability restrictions for this data set. Ifno release restrictions exist,"UNRESTRICTED" shall be entered in thisentity.


5 - 22

UP TO DATENESS Provides information about currency ofthe data set file.

Edition Number Edition Identifier of this dataset: Will beused in conformance with STANAG 3671

Creation Date Date of creation of data set.

Revision Date Date of revision of data set.

Recompilation Count Self explanatory.

Revision Count Self explanatory.

Specification ID Specification ID

Date of specification Date of specification

Specification amendment Specification amendment identifier

Date of earliest source Date of earliest source.

Date of latest source Date of latest source

COLOR CODE IDENTIFIER Gives red, green, blue values eachaveraged over pixels scanned from uniformintensity colour reference samples intendedfor colour coded processing.

Name Name and/or Description for ColourCode(graphic colour)(free text)

Colour Code Colour code assigned in the data set.

CIEx CIE value for "x". )CIEy CIE value for "y". ) (see Encl 6)CIEY CIE reflectivity value "Y" )

Mathematical Relation Mathematical Relation to other colour-codes (free text). See section 3.4.2.

Colour Intensity (RED nominal) Actual Red intensity value recorded for thiscolour code where a single source suppliesthe image, or a Nominal Red intensity valuefor this colour code where more than onesource supplies the image.

Colour Intensity (GREENnominal)

Actual Green intensity value recorded forthis colour code where a single sourcesupplies the image, or a Nominal Greenintensity value for this colour code wheremore than one source supplies the image.



5 - 23

Colour Intensity (BLUE nominal) Actual Blue intensity value recorded for thiscolour code where a single source suppliesthe image, or a Nominal Blue intensity valuefor this colour code where more than onesource supplies the image.

OTHER QUALITY INFO Provides information defining specificdescriptors related to data quality.

Comments Miscellaneous comments - Free text.

HORIZONTAL ACCURACY RECORD

POSITIONAL ACCURACY Provides information about Horizontalaccuracy of Geo Data Subset - Repeat asnecessary depending on the number ofhorizontal accuracy subregions.

Absolute Horizontal Accuracy Absolute horizontal accuracy of Source fileRegion / Subregion.

Unit of Measure Unit of measure for absolute horizontalaccuracy.(See Enclosure 9, M for meters)

Relative Horizontal Accuracy Point to point horizontal accuracy of Sourcefile / Region / Subregion.

Unit of Measure Unit of measure for point to point horizontalaccuracy. (See Enclosure 9, M for meters)


Provides the coordinates (Northing andEasting) of the polygon which delineatesthe horizontal accuracy region.

Easting Easting coordinate

Northing Northing coordinate

VERTICAL ACCURACY RECORD

VERTICAL ACCURACY Provides information about verticalaccuracy of Geo Data Subset - Repeat asnecessary depending on the number ofvertical accuracy subregions.

Absolute Vertical Accuracy Absolute vertical accuracy of Source file /Region / Subregion .

Unit of Measure Unit of measure for absolute verticalaccuracy.(See Enclosure 9, M for meters)


5 - 24

Relative Vertical Accuracy Point to point vertical accuracy of Sourcefile/ Region / Subregion.

Unit of Measure Unit of measure for point to point verticalaccuracy. (See Enclosure 9, M for meters)


Provides the coordinates (Northing andEasting) of the polygon which delineatesthe vertical accuracy region.

Easting Easting coordinate

Northing Northing coordinate

5.2.6 GEO DATA FILE.

A GEO DATA FILE of the Geo Data Subset provides the actual data (pixels) of araster image , and contains one or more records as follows :

IMAGE RECORD• PADDING FIELD• PIXEL FIELD

The PADDING FIELD is optional, and is used to pad the IMAGE RECORD sothat the following PIXEL FIELD can start at the beginning of a physical block onthe transfer media. The field contains sufficient characters including the fieldterminator to achieve this result.

The PIXEL FIELD which consists of a string of bytes should be considered to besubdivided into logical subfields (i.e., not ISO 8211 subfields) in the mannerdescribed in Section 4.3.

Note : There is one Geo Data File per zone for the main raster image (includinginsets within the same zone) and possibly several GEO DATA FILES for legendimages. (Figures 5-2, 5-3, 5-4 and 5-5 are examples of Main Raster Images).



5 - 25

NEA

SWA

SWO

NEO

Map 1 Map 2

Map 3 Map 4

Figure 5-2. A seamless four-map Main Raster Image (MRI).

NEA

SWA

SWO

NEO

Figure 5-3. MRI for source graphics with outsets.


5 - 26

An MRI formed by a map andits inset. The inset is anexternal inset at the same scaleas the main map. The inset isplaced at the correctgeographic area in the USRPimage, and the inset area onthe main graphic filled with zero(null) pixels.

NEA

SWA

SWO

NEO

Figure 5-4. MRI for source graphic with inset.

Four maps in a Main Raster Image (MRI). Maps 1,2, and 3 are on the same datum, while map 4 is on a different datum.The difference between the two datums causes a gap in the MRI. The size of the gap depends on the datums and scale involved. The larger the scale, the larger the gap (in pixels).

Map 1 Map 2

Map 3 Map 4

NEA

SWA

SWO

NEO

Figure 5-5. MRI for source graphics on different datums.


Section 6 – Exchange Media

6 - 1

6.0 EXCHANGE MEDIA.

6.1 PURPOSE.

The aim of these standards is to reduce the difficulty of exchanging informationbetween different users and different computing systems. Use of the standardsin the following paragraphs will facilitate the exchange of digital data.

6.2 CHARACTER REPRESENTATION.

Two types of character encoding are defined in this standard. Basic Text is usedfor all text subfields which are alphanumeric identifiers, labels etc. or must be inASCII only. It makes use of the ISO 646 International Reference Version standardwhich corresponds to ASCII. A General Text format is used for all text fields thatmay contain descriptions or names expressed in any language. Four lexical levelsof alphabbetic repertoire of General Text characters are defined (Lexical Level 0corresponds to Basic Text).

0 - Primary ASCII text (ISO 646)

1 - Extended ASCII (including accents for Western European Latin alphabetbased languages ISO 8859 Part 1 (Latin Alphabet 1))

2 - Full Latin alphabet text ASCII (all accents, diacritical marks and specialcharacters for Latin alphabet based languages (ISO 6937 repertoire))

3 - Universal Character Set (Base Multilingual plane of ISO 10646) (note: 2bytes per character)

6.3 FORMS OF MEDIA.

6.3.1 MAGNETIC TAPE.

6.3.1.1 Magnetic tape volumes containing data interchange files shall conform toISO 1001, level 3, with one fixed length media record per physical block. Exceptby bilateral agreement between exchanging parties, the ISO 1001 definition of an8 bit/byte will be adopted.

6.3.1.2 The block size for this product is 8,192 (8bit) Bytes. The completion of ablock, if necessary, from the end of specified recorded information should be byuse of (5/E) characters.

6.3.1.3 Only fixed length records may be used, and these shall be equal to thephysical block size or a whole subdivision of it. The ISO 8211 file of DDR and DRrecords shall be treated as a continuous string of bytes spanning, withoutseparators or padding, the fixed length records and blocks of the magnetic tape.Any unused bytes in the last magnetic tape record of the file shall be filled with 5/Echaracters.

USRP Edition 1.3August 1997Section 6 – Exchange Media

6 - 2

6.3.1.4 There are three physical recording alternatives:

• 6,250 GCR — Defined in FIPS PUB 50 which adopts ANSI X3.54-1976 (ISO 5652).

• 1,600 PE — Defined in FIPS PUB 25 which adopts ANSI X3.39-1973 (ISO 3788).

• 8 Millimetre — Defined in ANSI X3.202-1978.

The preferred density is 6250 cpi for 9 track tape and 2.3 Gigabytes for 8 mmtapes. Other densities are permitted as required (e.g., 1,600 PE ).

6.3.1.5 Magnetic tapes will have labels recorded as defined in FIPS PUB 79which adopts ANSI X3.27-1978 (ISO 1001). Option labels defined in thisstandard may be used by particular implementations as desired, but must onlycontain data that may be ignored by the receiver, with the exception of the uservolume label (UVL1). Volume Header Label one (VOL 1) and User Volume Labelone (UVL1) will be present and will contain the information as follows:

Entity Name Definition ISO1001Byte Position(BP) and field name

First Volume Header Label (Vol 1)

Volume ID ID for this specific volume 5 to 10 Volume identifier

SecurityClassification

Security Classification ofthis volume

11 Volume Accessibility

T = TOP SECRETS = SECRETC = CONFIDENTIALR = RESTRICTEDU = UNCLASSIFIED

User Volume Label One (UVL1)

Sequence Number Sequential number of thisvolume within the volumeset (transmittal)

5 to 7 Reserved forimplementation use

Transmittal ID Unique ID for thetransmittal (volume set) towhich this volume belongs


Number of Data Sets Number of Data Sets on,or starting on, this volume(may be left blank)




6 - 3

Notes:

1. All fields shall be a-characters, even the numeric fields are numericcharacter fields.

2. The 'Number of Data Sets' field may be left blank. It is suggested that forClassified data that this field can be completed by leaving sufficient empty spaceon the magnetic tape to ensure that completion of a known number of Data Setsbefore the End of 'Tape Mark'.

3. The 'Security Classification' of individual files may be defined by settingbyte position (BP) 54 of the 'First File Header Label' to T, S, C, R or U as definedabove for the Volume Label.

6.3.2 OPTICAL DISK.

6.3.2.1 CD-ROM volumes shall conform to ISO 9660 and may use an 'ExtendedAttribute Record' in any of the files in which case the 'Record format' (BP 79) shallbe = 0. The ISO 8211 records shall span the media records without furtherdemarcation. The unused portion of the last block shall be padded withcharacters (5/E). Supplementary labels defined in this standard may be used byparticular implementations as desired, but must only contain data that may beignored by the receiver. The information is defined as follows:

Entity Name Definition ISO9660 Byte Position(BP) and field name

Primary VolumeDescriptorVolume ID ID for this specific volume 41-72 Volume identifier

Sequence Number Sequential number of 125-128 Volumethis volume within the sequencevolume set (transmittal) number

Transmittal ID Unique ID for the 191-318 Volume settransmittal (volume set) identifierto which this volumebelongs

Number of Data Sets Number of Data Sets on, 884-887 Applicationor starting on, this volume Use

Security Classification Security Classification of 888 Applicationthis volume UseT = TOP SECRETS = SECRETC = CONFIDENTIALR = RESTRICTEDU = UNCLASSIFIED


6 - 4

Note: The first three fields shall be recorded according to ISO 9660. The'Number of Data Sets' shall be recorded according to paragraph 7.2.3 of ISO 9660and the 'Security Classification' shall be a d-character (Annex A of ISO 9660).

6.3.2.2 Where present the classification of a file shall be defined by the firstcharacter in the system user area at the end of the directory record.

T = TOP SECRETS = SECRETC = CONFIDENTIALR = RESTRICTEDU = UNCLASSIFIED

6.3.2.3 Except by bilateral agreement between exchanging parties, the ISO 9660definition of an 8 bit/byte will be adopted.

6.3.3 OTHER MEDIA.

Other media will be addressed as the need arises.

6.4 FILE NAMING CONVENTIONS; FOR USE WITH MEDIA LABELS.

The TRANSMITTAL HEADER FILE name is always

"TRANSH01.THF"

All other file names conform to the following rules :

The purpose of this set of rules is to provide a mechanism to identify those files,which together comprise a single data set. Each file label will be of the form:

ZZZZZZDD.XXX, where:

"ZZZZZZ" are six alphanumeric characters which uniquely identify the data set to which the file belongs

"DD" are two alphanumeric characters which identify the occurrence of the file type within the data set

"XXX" are three characters which must be selected from the sets below.

For Header Data Subset files, the following are defined :

XXX File TypeGEN General Information FileGER Geo Reference FileSOU Source FileQAL Quality File



6 - 5

For the Geo Data Subset files, use:

IMG Main Raster ImageLcc Raster Legend Image (where 'cc' is the number

assigned to the image's source graphic)

An example of the use of this structure is depicted below:

NOAMER01.SOU

This example defines a SOURCE_FILE which is part of a data set uniquelyidentified with NOAMER. If the data set contains more than one source file, thefile name will be the same except that at least one of the characters , "0" or "1",must be changed.


6 - 6


Annexe A — ISO 8211 Implementation toUSRP Edition 1.3

August 1997

A - 1

ANNEX A –– ISO 8211 ENCAPSULATION SPECIFICATIONS

TABLE OF CONTENTS

Page

A.1 Specification of ISO 8211 Exchange File Sets .....................................A - 2A.1.1 The Spec. of Exchange Set Content..............................................A - 2A.1.2 ISO 8211 Data Field Description....................................................A - 4A.1.3 Presence, absence and repetition requirements............................A - 6

A.2 ISO 8211 Encapsulation.........................................................................A - 6A.2.1 Transmittal Header File..................................................................A - 6A.2.2 General Information File.................................................................A - 8A.2.3 Geo Reference File ........................................................................A - 11A.2.4 Source File .....................................................................................A - 12A.2.5 Quality File .....................................................................................A - 17A.2.6 Geo Data File .................................................................................A - 19

A.3 Backward Compatibility.........................................................................A - 20A.3.1 Transformation Functions and their C Implementation ..................A - 20A.3.2 Transformation from USRP 1.2......................................................A - 22

A.3.2.1 Transmittal Header File .......................................................A - 22A.3.2.2 Source File...........................................................................A - 22A.3.2.3 Quality File...........................................................................A - 23

Annexe A — ISO 8211 Implementation toUSRP Edition 1.3August 1997

A - 2

A.1 SPECIFICATION OF ISO 8211 EXCHANGE FILE SETS.

An ISO 8211 exchange set is usually a large data structure which must bespecified in great detail. The following manner of specification is intended toenable a specification in a concise yet detailed manner.

This Annex contains specifications for the implementation of USRP as ISO 8211interchange files. The specifications include the data structures and datadescriptions for the following:

1. the files of the USRP transmittal file set,2. the records and fields of each file,3. the subfields of each field.

The first two items are specified as ordered, rooted fields with an explicitstatement of the required or permitted subtrees. The third item is specified as thefield descriptions of the component files. The details of the specification formatare given in the next section.

A.1.1 THE SPECIFICATION OF EXCHANGE SET CONTENT.

Note: The following notation is in Backus Naur Form (BNF)

The structural model for a ISO 8211 exchange set is an ordered rooted tree. Thegeneral notation for the model is:

<tree root><r>-<subtree>

where <tree root> is the root of the tree structure<r> is the repetition factor of the subtree, <subtree>.

In the usual manner of trees, each subtree type may comprise the root of furthersubtrees. The complete specification of an exchange set comprises the followinggeneric subtrees:

<exchange set><r>-<file type>

<r>-<record type>|<file type><r>-<field type>|<record type>

<r>-<field type><field description>

where

<exchange set> is the exchange set name

<r> is a specified repetition factor for a subtree,= integer, meaning a specific repetition factor= null means r = 1= R, meaning indefinite repetition


August 1997

A - 3

<file type>, <record type> and <field type> level may have an instance ofthe same type as a subtree (i.e. a file can be the subtree of a file, etc.)

<file type> ::= File: external file titlei.e., contents of ISO 8211 DDR; tag = 0...0

<record type> ::= Record: record name

<field type> ::= <tag>(<structure>:<order>)-<field name>

<tag> ::= an ISO 8211 field tag (which associates thisfield uniquely to its data description).

<structure> ::= a succinct description of the structurewhere (n) is an n-tuple (with n = integer)(m*n) is a 2-D array of m rows and n columns(*n) is a repeating 2-D table with n columns(i*j*k) is a 3-D array with extents i, j and k.

Note: The intent of <field structure> is to provide the user with a clue to therepetition pattern of the subfields within the field. "n,m,i,j,k" represent themaximum values of the contents of the field. These may be less if optionalsubfields are omitted.

<order> ::= a succinct statement of any intra- or inter-field ordering requirements.

whereO implies the order of the subfields is significant.O,<tag>, implies the order of the subfields is correlated with the orderof the subfields in the field bearing the tag(s), <tag>.

<field name> ::= the ISO 8211 field name corresponding to <tag>.

<field description> is the ISO 8211 data description for a field.The details of field description are given in the next section.

The presentation diagram for ordered, rooted trees is:

<tree root>||-<r><subtree 1>*-<r><subtree 2> <subtree 2> or <sub tree 3> but not both.*-<r><subtree 3>


A - 4

NOTA BENE: In these representations, the preorder traversal sequence rule is:top down, right hand branch first. The parent of any subtree is readily apparentand the parent tags for fields must coincide with the field description. Thetraversal of the tree encounters the repetition factor, perhaps the default of one, ofa subtree as the subtree is entered. Further repetition may be indicated in thefield descriptions.

Spaces may be introduced into the text for readability and for large exchange setsthe description may be compartmentalized into subtrees for reasons of clarity.The root of each subtree identifies its nodal position in its parent tree.

The above tree structures for each file define the order and structure of the datadescriptive records (DDRs) and the order and structure of the data records (DRs).

A.1.2 ISO 8211 DATA FIELD DESCRIPTION.

The format of the machine- and human-readable field description is describedbelow. The format comprises a series of one-line records easily maintained by aneditor. There are five one-line record types: a control line, record title lines, tagdefinition lines, subfield definition lines and interspersed comment lines.

Control line:

The control line is the first line of the Field Data Description sectionControl_==_(see DDR Header in ISO 8211)

Record title line:

Record: _ Record name

Tag definition line (one per field):0_tag _ptag _pg_field name

wheretag is an ISO 8211 field tag, A7ptag is a parent tag, A7pg are the printable graphics, A2, (usually ';&')name is an ISO 8211 field name, A48


August 1997

A - 5

Subfield definition line(one per subfield):

nsi_label_dw_(r)_subfield comment_{syntax}

wherensi is a sequence number(1 = first, 999 = end of field description)

label is an ISO 8211 label component, Akk*label initiates a vector label in a Cartesian label describing a

2-d data structure

d,e1,e2, in label 1 is a numeric array descriptor** is an in-field numeric array descriptor

d is the subfield data type, A1 (d = A|I|R|B)where

A signifies character data;I signifies implicit-point representation;R signifies explicit-point unscaled representation;B signifies bit field data.

@ implies skip this format term in arrays

w is a fixed subfield width, I4(0|SPACE = delimited, variable width)

(r) is, when present, a qualifier on the subfield type:- a fixed number of decimal places for R types- when L it indicates lexical alphnumeric type for A types

comment is a descriptive subfield comment

syntax indicates, when present, how the subfield must be fillesit may be:- a single value (e.g. {THF}, {0})- a list of value (e.g. {0 | 4 | 8 } )- a range of value (e.g. {1-9} )- a pattern (e.g. {YYYYMMDD}, {ZZZZZZ},

{USRP,<serie>}, {±SSSSSS.SS})- an indication (e.g. {may be null})

Comment lines:

Comment records start with SPACEs or TABs andmay be located anywhere.


A - 6

A.1.3 PRESENCE, ABSENCE AND REPETITION REQUIREMENTS

Except when explicitly stated in bold and between square brackets, all therecords, fields and subfields listed in the following specification must be present ina USRP transmittal.

Rules for repetition are also stated in bold and between square brackets.

Except when explicitly stated in the syntax part of the subfield description line.(e.g.{may be null}), all the present subfields must be filled with a valid value.

A.2 ISO 8211 ENCAPSULATION.

The following specifies the content of a USRP transmittal file set at the file level byan ordered, rooted tree structure.

NOTE - See the section A.1. for format interpretation.

Exchange set: USRP||-File: TRANSMITTAL HEADER|-R File: GENERAL INFORMATION

|-R File: SOURCE|-File: QUALITY|-R File: RASTER GEO DATA

The following sections specify the content and structure of each USRP file at therecord and field level. The specification for each file is given as an ordered rootedtree specifying the file contents by record and field followed by the ISO 8211 datadescription for each field.

NOTE - See the section A.1 for format interpretation.

A.2.1 TRANSMITTAL_HEADER_FILE.

File Content by Record and Field:

File: TRANSMITTAL HEADER|- Record: TRANSMITTAL DESCRIPTION| |- 001 (2) {RTY = THF, RID = 01}| |- VDR (8) Transmittal Header| |-R FDR (7) Dataset Description||- Record: SECURITY AND UPDATE| |- 001 (2) {RTY = LCF}| |- QSR (4) Security and Release| |-R QUV (6) Up-to-Dateness


August 1997

A - 7

Note: The Dataset description field and up-to-dateness field will be repeatedonce for each dataset present in the transmittal. They will be repeated in the sameorder; there will be a one-to-one mapping between them. A single up-to-datenessfield will be used when the information applies to all the datasets.

Field Data Descriptions:

Control == (see DDR Header in ISO 8211)

0 000 {=TRANSMITTAL_HEADER_FILE}1 File title field, present only in DDR999

Record: TRANSMITTAL DESCRIPTION0 001 ;& RECORD_ID1 RTY A 3 Record type {THF}2 RID I Record id number {1}999

0 VDR 001 ;& TRANSMITTAL_HEADER1 MSD A 3 Media Volume / File Structure Standard {000-004}2 VOO A Originator3 ADR A Addressee {may be null}4 NOV I 1 Number of volumes {1-9}5 NOF I 3 Number of datasets {001-999}6 URF A Transmittal ID7 EDN I 3 Edition number {001-999}8 CDV07 A 8 Creation date value {YYYYMMDD}999

*0 FDR 001 ;& DATA_SET_DESCRIPTION [once per dataset]1 NAM A 6 Dataset ID {ZZZZZZ}2 STR I 1 Data structure code {4}3 PRT A Dataset type {USRP,<serie>}4 SWO R 10 (2) Westernmost longitude {±SSSSSS.SS}5 SWA R 10 (2) Southernmost latitude {±SSSSSS.SS}6 NEO R 10 (2) Easternmost longitude {±SSSSSS.SS}7 NEA R 10 (2) Northernmost latitude {±SSSSSS.SS}999

Record: SECURITY AND UPDATE0 001 ;& RECORD_ID1 RTY A 3 Record type {LCF}2 RID I Record id number {1}999

0 QSR 001 ;& SECURITY_AND_RELEASE1 QSS A 1 Highest security classification {T | S | C | R | U}2 QOD A 1 Downgrading instructions { Y | N }3 CDV10 A 8 Date of downgrading value {YYYYMMDD or null}4 QLE A Releasability999


A - 8

*0 QUV 001 ;& UP_TO_DATENESS [once, or once per dataset]1 SRC1 A DIGEST Edition ID { DIGEST 1.2a}2 CDV12 A 8 DIGEST Edition date value {19950630}3 SPA1 A DIGEST Amendment number {1}4 SRC2 A USRP Edition ID {USRP 1.3}5 CDV22 A 8 USRP Edition date value {19970831 }6 SPA2 A USRP Amendment number { 0}999

A.2.2 GENERAL_INFORMATION_FILE.


File: GENERAL INFORMATION|-R Record: GENERAL INFORMATION| |- 001 (2) Record Id {RTY = GIN}| |- DSI (2) Data Set Id| |- GEN (17) General Information| |- SPR (15) Data Set Parameters| |- BDF (*3:O) Band Id| |- TIM (*1) Tile Index Map| [TIM is omitted if Tile Index Map Flag contains "N"]||- Record: DATASET DESCRIPTION| |- 001 (2) {RTY = DSS}| |- DRF (4) Dataset Description



0 000 {=GENERAL_INFORMATION_FILE}1 File title field, present only in DDR999

Record: GENERAL INFORMATION [repeats for each zone of a dataset]

0 001 ;& RECORD_ID1 RTY A 3 Record type {GIN}2 RID I Record id number {1,n}999

0 DSI 001 ;& DATA_SET_ID1 PRT A Dataset type {<Product code>,serie}2 NAM A 6 Dataset ID {ZZZZZZ}999


August 1997

A - 9

0 GEN 001 ;& GENERAL_INFORMATION1 STR I 1 Data structure code {4}2 LOD R 6 Data density E-W direction {mmmmmm}3 LAD R 6 Data density N-S direction {mmmmmm}4 UNIloa A 3 Unit of measurement for LOD/LAD {UNlloa = M}5 ZNA I 3 Zone number {-61 to +61}6 SWO R 10 (2) Westernmost longitude {±SSSSSS.SS}7 SWA R 10 (2) Southernmost latitude {±SSSSSS.SS}8 NEO R 10 (2) Easternmost longitude {±SSSSSS.SS}9 NEA R 10 (2) Northernmost latitude {±SSSSSS.SS}10 SCA I 9 Source graphic scale reciprocal {000000000-999999999}11 PSP R 5 (1) Pixel Spacing, Microns at capture stage {000.0-100.0}12 IMR A 1 Image Rectified {Y | N}13 LSO R 10 Easting of origin {mmmmmmmmmm}14 PSO R 10 Northing of origin {mmmmmmmmmm}15 TXT A (L) Free Text {may be null}999

0 SPR 001 ;& DATA_SET_PARAMETERS1 NUL I 6 Row Number of the U-R corner of MBR {000000-127871}2 NUS I 6 Column Number of the U-R corner of MBR{000000-127871}3 NLL I 6 Row Number of the L-L corner of MBR {000000-127871}4 NLS I 6 Column Number of the L-L corner of MBR {000000-127871}5 NFL I 3 Number of Subblocks, vertically {001-999}6 NFC I 3 Number of Subblocks, horizontally {001-999}7 PNC I 3 Number of Pixels/Subblock Line {128}8 PNL I 3 Number of Scan Lines/Subblock {128}9 COD I 1 Column Sequence {0}10 ROD I 1 Row sequence {1}11 POR I 1 Pixel order {0}12 PCB I 1 Size of Pixel/Element Count in bits {0 | 4 | 8}13 PVB I 1 Size of Pixel/Element Value in bits {0 | 8}14 BAD A 12 Image file name {ZZZZZZDD.IMG}15 TIF A 1 Tile index map flag (“Y” or “N”) {Y | N}999

0 BDF 001 ;& BAND_ID1 *BID A 5 Band identification [once per band in the image file]

(band description)[WS1 and WS2 must be present if PVB = 0,they may be omitted or null otherwise]

2 WS1 I 5 ON color code value {00000-00255}3 WS2 I 5 OFF color code value {00000-00255}999

0 TIM 001 ;& TILE_INDEX_MAP[TIM must be present if TIF = Y,it is omitted otherwise.]

1 *TSI I 11 Tile index map value [once per block in the image file](N = 1-tuple) {nnnnnnnnnnn}

999


A - 10

Record: DATASET DESCRIPTION

0 001 ;& RECORD_ID1 RTY A 3 Record type {DSS}2 RID I Record id number {1}999

0 DRF 001 ;& DATASET_DESCRIPTION1 NSH I 2 Total number of horizontal accuracy sub-regions

{01-99}2 NSV I 2 Total number of vertical accuracy sub-regions

{01-99}3 NOZ I 2 Total number of zone image files {01-99}4 NOS I 2 Total number of source graphics {01-99}999

A.2.3 GEO REFERENCE FILE.


File: GEO REFERENCE|- Record: GEO REFERENCE| |- 001 (2) {RTY = GEO}| |- GEP (6) Geo Parameters| |- PRR (6) Projection



0 000 {=GEO_REFERENCE_FILE}1 File title field, present only in DDR999

Record: GEO REFERENCE

0 001 ;& RECORD_ID1 RTY A 3 Record type {GEO}2 RID I Record id number {1}999

0 GEP 001 ;& GEO_PARAMETERS1 TYP A 3 Data Type {MAP}2 UNI A 3 Unit of measurement for coordinates {M}3 ELL A Ellipsoid Name {World Geodetic System 1984}4 ELC A 3 Ellipsoid Code {WGE}5 DAG A Datum Geodetic Name {World Geodetic System 1984}6 DCD A 4 Datum Geodetic Code {WGE}999


August 1997

A - 11

0 PRR 001 ;& PROJECTION1 PRN A Projection Name {Universal Transverse Mercator |

Universal Polar Stereographic}2 PCO A 2 Projection Codes {TC | PG }3 PAA R 10 Projection Parameter 14 PAB R 10 Projection Parameter 25 XOR R 8 Easting false Origin {mmmmmmmm }6 YOR R 8 Northing false Origin {mmmmmmmm }999

A.2.4 SOURCE FILE.


File: SOURCE|- Record: SOURCE| |- 001 (2) {RTY = SOU}| |- SGF (3) Source Summary| |- SOR (28) Source| |- MAG (*10) Magnetic Rate| |-R RCI (*2) Bounding Polygon Coordinates| |- PRR (8) Projection| |- QSR (4) Security and Release| |- INS (*19) Inset| | [INS is omitted if no Inset is transmitted]| |- CPY (1) Copyright||-R Record: LEGEND [omitted if no Legend File is transmitted]| |- 001 (2) {RTY = LEG}| |- LGI (2) Legend| |- SPR (15) Dataset Parameters| |- TIM (*1) Tile Index Map| [TIM is omitted if Tile Index Map Flag contains "N"]||- Record: METRIC SUPPORT| |- 001 (2) {RTY = MSD}| |- DCC (7) Datum Change Constants| |- SCC (2) Source Datum Coefficient Counters| |- SLG (*3) Source Datum Longitude Coefficients| |- SLT (*3) Source Datum Latitude Coefficients| |- GRC (3) Grid Rotation Coefficients||- Record: SUPPLEMENTARY TEXT [omitted if no Text is| |- 001 (2) {RTY = SPT} transmitted]| |- SUP (*3) Supplementary Text


A - 12



0 000 {=SOURCE_FILE}1 File title field, present only in DDR999

Record: SOURCE

0 001 ;& RECORD_ID1 RTY A 3 Record type {SOU}2 RID I Record id number {1}999

0 SGF 001 ;& SOURCE_SUMMARY1 NST I 4 Number of supplementary text records {0000-9999}2 NLI I 2 Number of legend images {00-99}3 NIN I 2 Number of insets {00-99}999

0 SOR 001 ;& SOURCE1 PRT A 10 Series Designator for the Series2 URF A 20 Unique Source ID3 EDN A 7 Source Edition Number4 NAM A Full Name of Source Document5 CDP I Type of significant date6 CDV A 8 Significant Date value {YYYYMMDD}7 COU A 2 Country Code8 CDV27 A 8 Perishable information date value { YYYYMMDD}9 SCA I 9 Cartographic Scale {000000000-999999999}10 GRD A Cartographic Grid Code {GRD1,.,GRDn (may be null)}11 SQU I Area Coverage12 UNIsqu A 3 Unit of Measure for Area Coverage13 PCI I 4 Predominant Contour Interval {0000-9999}14 UNIpci A 3 Unit of Measure for Contour Interval15 WPC I 3 Percentage Covered by Water {000-100,999}16 NST I 3 Navigational System Type17 ELL A Ellipsoid Name18 ELC A 3 Ellipsoid Code19 DVR A Datum Vertical Reference {may be null}20 VDCdvr A 4 Code for Datum of Vertical Reference {may be null}21 SDA A Sounding Datum Name {may be null}22 VDCsda A 4 Code for Sounding Datum {may be null}23 DAG A Geodetic Datum Name24 DCD A 4 Geodetic Datum Code25 HKE I 6 Highest known elevation of source {000000-999999, or null}26 UNIhke A 3 Units of elevation value {may be null}27 LON R 10 Easting of HKE {mmmmmmmmmm, or null}28 LAT R 10 Northing of HKE {mmmmmmmmmm, or null}999


August 1997

A - 13

0 MAG 001 ;& MAGNETIC_RATE1 *CDP I Type of magnetic date rate [once per magnetic rate

for the source graphic]2 CDV A 8 Magnetic rate Date value {YYYYMMDD}3 RAT R 8 Annual magnetic rate of change4 UNIrat A 3 Units of annual rate of change5 GMA R 8 Grid north - magnetic north angle6 UNIgma A 3 Units of G-M Angle7 LON R 10 Easting of GMA reference point {mmmmmmmmmm}8 LAT R 10 Northing of GMA reference point {mmmmmmmmmm}9 GCA R 8 Grid convergence angle10 UNIgca A 3 Units of grid convergence angle999

0 RCI 001 ;& BOUNDING_POLYGON_COORDINATES[once per bounding polygon]

[once per vertex along the bounding polygon]1 *LON R 10 Easting coordinate {mmmmmmmmmm}2 LAT R 10 Northing coordinate {mmmmmmmmmm}999

0 PRR 001 ;& PROJECTION1 PRN A Projection Name2 PCO A 2 Projection Codes3 PAA R 10 Projection Parameter 14 PAB R 10 Projection Parameter 2 {may be null}5 PAC R 10 Projection Parameter 3 {may be null}6 PAE R 10 Projection Parameter 4 {may be null}7 XOR R 8 Easting false Origin {may be null}8 YOR R 8 Northing false Origin {may be null}999

0 QSR 001 ;& SECURITY_AND_RELEASE1 QSS A 1 Highest security classification {T | S | C | R | U}2 QOD A 1 Downgrading instructions {Y | N }3 CDV10 A 8 Date of downgrading value {YYYYMMDD, may be null}4 QLE A Releasability }999

0 INS 001 ;& INSET[INS may be omitted if no inset is present.]

1 *INT A 2 Unique ID of an Inset2 SCA I 9 Cartographic Scale of Inset3 NAM A Name of Inset4 NTL R 10 Absolute Easting lower-left corner5 TTL R 10 Absolute Northing lower-left corner6 NVL R 10 Absolute Easting upper left corner7 TVL R 10 Absolute Northing upper left corner8 NTR R 10 Absolute Easting upper-right corner9 TTR R 10 Absolute Northing upper-right corner10 NVR R 10 Absolute Easting lower right corner11 TVR R 10 Absolute Northing lower right corner


A - 14

12 NRL R 10 Relative Easting lower-left corner13 TRL R 10 Relative Northing lower-left corner14 NSL R 10 Relative Easting upper left corner15 TSL R 10 Relative Northing upper left corner16 NRR R 10 Relative Easting upper-right corner17 TRR R 10 Relative Northing upper-right corner18 NSR R 10 Relative Easting lower right corner19 TSR R 10 Relative Northing lower right corner999

0 CPY 001 ;& COPYRIGHT1 CPZ A (L) Copyright statement999

Record: LEGEND[omitted if no legend is transmitted, repeats for each legend file]

0 001 ;& RECORD_ID1 RTY A 3 Record type {LEG}2 RID I Record id number {1,n}999

0 LGI 001 ;& LEGEND1 NAM A Legend name2 STR I 1 Structure class code {4}999

0 SPR 001 ;& DATA_SET_PARAMETERS1 NUL I 6 Row Number of the U-R corner of MBR {000000-999999}2 NUS I 6 Column Number of the U-R corner of MBR{000000-999999}3 NLL I 6 Row Number of the L-L corner of MBR {000000-999999}4 NLS I 6 Column Number of the L-L corner of MBR {000000-999999}5 NFL I 3 Number of Subblocks, vertically {001-999}6 NFC I 3 Number of Subblocks, horizontally {001-999}7 PNC I 3 Number of Pixels/Subblock Line {001-999}8 PNL I 3 Number of Scan Lines/Subblock {001-999}9 COD I 1 Column Sequence {0}10 ROD I 1 Row sequence {1}11 POR I 1 Pixel order {0}12 PCB I 1 Size of Pixel/Element Count in bits {0 | 4 | 8}13 PVB I 1 Size of Pixel/Element Value in bits {0 | 8}14 BAD A 12 Image file name {ZZZZZZDD.Lcc}15 TIF A 1 Tile index map flag (“Y” or “N”) {Y | N}999

0 TIM 001 ;& TILE_INDEX_MAP[TIM must be present if TIF = Y,it is omitted otherwise.]

1 *TSI I 11 Tile index map value [once per block in the legend file](N = 1-tuple) {nnnnnnnnnnn}

999


August 1997

A - 15

Record: METRIC SUPPORT

0 001 ;& RECORD_ID1 RTY A 3 Record type {MSD}2 RID I Record id number {1}999

0 DCC 001 ;&DATUM_CHANGE_CONSTANTS(Note: units for all datum change constants are n degreesand decimal part of a degree.)

1 TOF S 22 Latitude normalizing offset.2 GOF S 22 Longitude normalizing offset.3 NZT S 22 Normalizing factor.4 ELV S 22 Eastern limit of validity.5 WLV S 22 Western limit of validity.6 NLV S 22 Northern limit of validity.7 SLV S 22 Southern limit of validity.999

0 SCC 001 ;&SOURCE_DATUM_COEFFICIENTS_COUNTER1 BCT I 2 Number of longitude coefficients.2 ACT I 2 Number of latitude coefficients.999

0 SLG 001 ;&SOURCE_DATUM_LONGITUDE_COEFFICIENTS1 *CBI I 2 i index of the coefficient of MRE b i,j.2 CBJ I 2 j index of the coefficient of MRE b i,j.3 LGC S 12 Coefficient of MRE bi,j (bi,j coefficients are ordered with

respect to increasing i then j.)999

0 SLT 001 ;&SOURCE_DATUM_LATITUDE_COEFFICIENTS1 *CAI I 2 i index of the coefficient of MRE ai,j.2 CAJ I 2 j index of the coefficient of MRE ai,j.3 LTC S 12 Coefficient of MRE ai,j (ai,j coefficients are ordered with

respect to increasing i then j.)999

0 GRC 001 ;&GRID_ROTATION_COEFFICIENTS1 NES S 22 Normalized Eastings shift2 NNS S 22 Normalized Northings shift3 AOR S 22 Angle of orientation from source datum grid to WGS UTM

grid999


A - 16

Record: SUPPLEMENTARY TEXT

0 001 ;& RECORD_ID1 RTY A 3 Record type {SPT}2 RID I Record id number {1}999

0 SUP 001 ;& SUPPLEMENTARY_TEXT1 *TRY A 4 Supplementary text record type [once per text]2 TRI A 4 Supplementary text field reference identifier3 TXT A (L) Supplementary text999

A.2.5 QUALITY FILE.


1 [M] File: QUALITY2 [M] |- Record: QUALITY

| |- 001 (2) {RTY = QAL}| |- QSR (4) Security and Release| |- QUV (10) Up-to-Dateness| |- COL (*9) Colour Code ID| |- QOI (1) Other Quality Information| |

2 [D] |-R Record: HORIZONTAL ACCURACY ††| |- 001 (2) {RTY = HOR}| |- ASH (5) Horizontal Accuracy| |- RCI (*2) Bounding Polygon Coordinates|

2 [D] |-R Record: VERTICAL ACCURACY ††|- 001 (2) {RTY = VER}|- ASV (5) Vertical Accuracy|- RCI (*2) Bounding Polygon Coordinates



0 000 {=QUALITY_FILE}1 File title field, present only in DDR999

Record: QUALITY

0 001 ;& RECORD_ID1 RTY A 3 Record type {QAL}2 RID I Record id number {1}999


August 1997

A - 17

0 QSR 001 ;& SECURITY_AND_RELEASE1 QSS A 1 Highest security classification {T | S | C | R | U }2 QOD A 1 Downgrading instructions {Y | N}3 CDV10 A 8 Date of downgrading value {CDV10 = YYYYMMDD}4 QLE A Releasability {may be null}999

0 QUV 001 ;& UP_TO_DATENESS1 EDN I 3 Edition Number of dataset2 CDV07 A 8 Creation of dataset date value {YYYYMMDD}3 CDV24 A 8 Revision or Update date value {YYYYMMDD}4 REC I 3 Recompilation Count {000-999}5 REV I 3 Revision Count {000-999}6 SRC A Specification ID7 CDV22 A 8 Specification date value {YYYYMMDD}8 SPA A Specification amendment9 CDV20 A 8 Earliest source date value {YYYYMMDD}10 CDV21 A 8 Latest source date value {YYYYMMDD}999

0 COL 001 ;& COLOUR_CODE_ID1 *CBD A Name of Colour Code [once per colour code]2 CCD I 3 Colour Code Assigned in Dataset {000-255}

(CIE color description)3 CR1 I 6 CIEx {000000-999999, or null}4 CR2 I 6 CIEy {000000-999999, or null}5 CR3 I 6 CIE Reflectivity (Y) {000000-999999, or null}6 FRM A Mathematical Relation to other colour {may be null}

(RGB color description)7 NSR I 3 Colour Intensity - Red actual {000-255}8 NSG I 3 Colour Intensity - Green actual {000-255}9 NSB I 3 Colour Intensity - Blue actual {000-255}999

0 QOI 001 ;& OTHER_QUALITY_INFORMATION1 OQI A (L) Free text {may be null}999

Record: HORIZONTAL ACCURACY[repeats for each horizontal accuracy subregion]

0 001 ;& RECORD_ID1 RTY A 3 Record type {HOR}2 RID I Record id number {1,n}999

0 ASH 001 ;& HORIZONTAL_ACCURACY1 AAH I 5 Absolute Horizontal Accuracy {00000-99999}2 UNIaah A 3 Unit of measure3 APH I 5 Relative Horizontal Accuracy {00000-99999}4 UNIaph A 3 Unit of measure999


A - 18

0 RCI 001 ;& BOUNDING_POLYGON_COORDINATES[once per vertex along the bounding polygon]

1 *LON R 10 Easting coordinate {mmmmmmmmmm}2 LAT R 10 Northing coordinate {mmmmmmmmmm}999

Record: VERTICAL ACCURACY[repeats for each vertical accuracy subregion]

0 001 ;& RECORD_ID1 RTY A 3 Record type {VER}2 RID I Record id number {1,n}999

0 ASV 001 ;& VERTICAL_ACCURACY1 AAV I 5 Absolute Vertical Accuracy {00000-99999}2 UNIaav A 3 Unit of measure3 APV I 5 Relative Vertical Accuracy {00000-99999}4 UNIapv A 3 Unit of measure999

0 RCI 001 ;& BOUNDING_POLYGON_COORDINATES[once per vertex along the bounding polygon]

1 *LON R 10 Easting coordinate {mmmmmmmmmm}2 LAT R 10 Northing coordinate {mmmmmmmmmm}999

A.2.6 RASTER GEO DATA FILE.


File: RASTER GEO DATA| -R Record: IMAGE| |- 001 (2) {RTY = IMG}| |- PAD (1) Padding| [PAD may be omitted]| |- SCN (*1) Pixel Field



0 000 {=RASTER_GEO_DATA_FILE}1 File title field, present only in DDR999


August 1997

A - 19

Record: IMAGE

0 001 ;& RECORD_ID1 RTY A 3 Record type {IMG}2 RID I Record id number {1 to n}999

0 PAD 001 ;& PADDING [may be omitted]1 PAD A Padding Characters to Fill Block999

0 SCN 001 ;& PIXEL1 *PIX B 8 Pixel Values - edit to B(8)999

A.3 BACKWARD COMPATIBILITY

Existing Interchange files conforming with USRP 1.2 may be imported as orconverted into conforming files using the alternate sub-field definitions.

Where changes have occurred, sub-fields are given an alternate subfield definitionwhich describes the way the information will be transmitted in these existingDIGEST interchange files. The alternate subfield definition contains:

- an alternate name (possibly the same)- an alternate sub-field type (possibly the same)- the transformation to be applied to the alternate subfield value.

Notation:

subfield subfield alternate alternate transformationlabel type label type

"— " = same name or type

ex:3[M] 2 RID I Record ID number — A2 A_TO_I

A.3.1 TRANSFORMATION FUNCTIONS AND THEIR C IMPLEMENTATION

There are five types of transformation required for defining the alternate sub-fields:

SAME_R may only apply when the alternate type and the subfield type is R, thelength of the field is the only change, the value will be the same, rightjustified, padded on the left with "0"s if required.

SAME_A may only apply when the alternate type and the subfield type is A, thelength of the field is the only change, the value will be the same, left


A - 20

justified, padded on the right with blank spaces, or truncated, ifrequired.

A_TO_I may only apply when the alternate type is A and the subfield type is I,the value, a character string representing an integer number, will beconverted in an integer value.

DATE_V may only apply when the alternate type is A 12 and the subfield type isA 8, only the last 8 characters representing a date value will be kept.

DATE_P may only apply when the alternate type is A 12 and the subfield type is I3, only the first 3 characters representing a date type code will beconverted to an integer value.

The C implementation of the functions is as follows:

#define ERROR (-1)#define NORMAL 0typedef enum {ADRG, ASRP} Product;

int SAME_R (double *new, double old, double minr, double maxr){

if (old < minr || old > maxr) {*new = 0;return ERROR;

}*new = old;return NORMAL;

}

int A_TO_I (int *new, char *old, int mini, int maxi){

int i;i = atoi(old);if (i < mini || i > maxi) {

*new = 0;return ERROR;

}*new = i;return NORMAL;

}

int DATE_V ( char *new, char *old){

int y,m,d;strncpy(new,old+4,8);new[8] = '\0';if (sscanf(new, "%4d%2d%2d", &y, &m, &d) != 3) return ERROR;if (m < 1 || m > 12 || d < 1 || d > 31) return ERROR;return NORMAL;

}

int DATE_P (int *new, char *old){

*new = atoi(old);if (*new < 0 || *new > 999) return ERROR;return NORMAL;

}

int SAME_A (char *new, char *old, int new_width)/* new width is the width of the new field, excluding NULL terminator */{


August 1997

A - 21

int i;for (i=0; i < new_width && *old; i++) *new++ = *old++ ;while (i++ < new_width) *new++ = ' ';*new = '\0';return NORMAL;

}

A.3.2 TRANSFORMATION FROM USRP 1.2

A.3.2.1 TRANSMITTAL HEADER FILE

Record: TRANSMITTAL DESCRIPTION

0 VDR 001 ;& TRANSMITTAL_HEADER8 CDV07 A 8 Creation date value DAT A12 DATE_V

Record: SECURITY AND UPDATE

0 QSR 001 ;& SECURITY_AND_RELEASE3 CDV10 A 8 Date of downgrading DAT A12 DATE_V

0 QUV 001 ;& UP_TO_DATENESSThe following three alternate sub-fields definition is only valid when importingthe data.It would not apply when converting to new edition:

4 SRC2 A Specification Edition ID SRC A SAME_A5 CDV22 A 8 Specification Ed. date value DAT A12 DATE_V6 SPA2 A Specification amend. number SPA A SAME_A

A.3.2.2 SOURCE FILE

Record: SOURCE

0 SOR 001 ;& SOURCE5 CDP I Type of significant date DAT1 A12 DATE_P6 CDV A 8 Significant Date value DAT1 A12 DATE_V8 CDV27 A 8 Perishable info date value DAT2 A12 DATE_V

20 VDCdvr A 4 Code for Datum — A 3 SAME_A21 SDA A Sounding Datum Name — A 20 SAME_A24 DCD A 4 Geodetic Datum Code — A 3 SAME_A

0 MAG 001 ;& MAGNETIC_RATE1 *CDP I Type of date DAT A12 DATE_P2 CDV A 8 Magnetic rate Date value DAT A12 DATE_V



A - 22

Record: METRIC SUPPORT

0 DCC 001 ;&DATUM_CHANGE_CONSTANTS1 TOF S 22 Latitude normalizing offset. — R 22 SAME_R2 GOF S 22 Longitude normalizing offset. — R 22 SAME_R3 NZT S 22 Normalizing factor — R 22 SAME_R4 ELV S 22 Eastern limit of validity — R 22 SAME_R5 WLV S 22 Western limit of validity — R 22 SAME_R6 NLV S 22 Northern limit of validity — R 22 SAME_R7 SLV S 22 Southern limit of validity — R 22 SAME_R

0 SLG 001 ;&SOURCE_DATUM_LONGITUDE_COEFFICIENTS3 LGC S 12 Coefficient of MRE bi,j — R 12 SAME_R

0 SLT 001 ;&SOURCE_DATUM_LATITUDE_COEFFICIENTS3 LTC S 12 Coefficient of MRE ai,j — R 12 SAME_R

0 GRC 001 ;&GRID_ROTATION_COEFFICIENTS1 NES S 22 Normalized Eastings Shift — R 22 SAME_R2 NNS S 22 Normalized Northings shift — R 22 SAME_R3 AOR S 22 Angle from source grid to

WGS UTM grid — R 22 SAME_R

A.3.2.3 QUALITY FILE

Record: QUALITY


0 QUV 001 ;& UP_TO_DATENESS1 EDN I 3 Edition Number of Dataset — A 20 A_TO_I2 CDV07 A 8 Creation of dataset date value DAT1 A12 DATE_V3 CDV24 A 8 Revision or Update date value DAT2 A12 DATE_V7 CDV22 A 8 Specification date value DAT3 A12 DATE_V9 CDV20 A 8 Earliest source date value DAT4 A12 DATE_V

10 CDV21 A 8 Latest source date value DAT5 A12 DATE_V

Annexe B — UTM/UPS Coordinate Transformation toUSRP Edition 1.3

August 1997

B - 1

ANNEX B UTM/UPS COORDINATE TRANSFORMATION.

TABLE OF CONTENTS

Page

B.1 UTM-UPS Parameters ............................................................................B - 2B.1.1 Summary Of Symbols Used ..........................................................B - 2B.1.2 Pixels numbering principle ............................................................B - 3

B.2 Easting and Northing of a pixel.............................................................B - 4

B.3 Image coordinates (c,r) of a point (E,N) ..............................................B - 5

B.4 Computation (formula) of £ (isometric latitude)given ϕϕϕϕ ....................................................................................................B - 5

B.5 Algorithm of inversion of £ (Computation of ϕϕϕϕ given£0 ) ..........................................................................................................B - 6

B.6 Computation (formula) of ββββ (true distance along ameridian from the Equator) to the latitude ϕϕϕϕ ........................................B - 6

B.7 Algorithm of inversion of ββββ (Newton-Raphson).Computation of ϕϕϕϕ given ββββ0 ..................................................B - 8

B.8 UTM projection (k0 =0.9996) - Computation of (E,N)given (λλλλ,ϕϕϕϕ)................................................................................................B - 9

B.9 UTM projection (k0 =0.9996) - Computation of (λλλλ,ϕϕϕϕ)given (E,N)...............................................................................................B - 10

B.10 UPS projection (k0 =0.994) - Computation of (E,N)given (λλλλ,ϕϕϕϕ)................................................................................................B - 11

B.11 UPS projection (k0 =0.994) - Computation of (λλλλ,ϕϕϕϕ)given (E,N)...............................................................................................B - 12

B.12 Maximum stretch (scale factor).............................................................B - 13

B.13 Source Datum Geographic coordinates fromWGS84 Geographic Coordinates ..........................................................B - 13

B.14 Source Datum UTM Grid Coordinates from WGS84UTM Grid Coordinates............................................................................B - 15

Annexe B — UTM/UPS Coordinate Transformation toUSRP Edition 1.3August 1997

B - 2

B.1 UTM-UPS PARAMETERS.

B.1.1 SUMMARY OF SYMBOLS USED.

E0 = Easting of the (0,0) (upper left) pixel of the Zone Image N0 = Northing of the (0,0) (upper left) pixel of the Zone Image E,N = Easting and Northing of a pointE1,N1 = Easting and Northing of the upper-left corner of a pixela = semi-major axisf = flatteninge2 = squared first eccentricity [e2 = f * (2 - f)]k0 = scale factor along the central meridian (UTM) or

at the Pole (UPS)λ0 = longitude of the central meridian (UTM);λ = geodetic longitude - positive towards east;ϕ = geodetic latitude - north positive; south negative;£ = isometric latitude at the geodetic latitude ϕ;β = true distance along a meridian from the equator to the

geodetic latitude ϕ;ln(a) = neperian logarithm of a;cosh(a) = hyperbolic cosine of a;sign(a) = sign of a (+1 if a ≥ 0 ; -1 if a < 0);round(a) = truncature of a to the nearest inferior whole integer

(function : INT in Pascal, FLOOR in C or DINT in FORTRAN).exp(a) = ea exponential of a.Atan(a) = inverse tangent of x.ε = 1*10-6 radians. (about 0.2 sexagesimal seconds)

recommended stop value for angles in iterative algorithms;← = affectation symbol inside an algorithm;= = mathematical equality inside a formula.ℜ = set of real numbers

ALL EASTINGS AND NORTHINGS ARE ASSUMED TO BE IN METRES;ALL ANGLES ARE ASSUMED TO BE IN RADIANS, EXCEPT IN B-13.


August 1997

B - 3

B.1.2 PIXELS NUMBERING PRINCIPLE.

The coordinates of the origin are E0 (Easting in metres), N0 (Northing in metres)in UTM, and 0 (column number), 0 (row number) in the image. The coordinates ofthe upper-left corner of a pixel are E (Easting in metres), N (Northing in metres)in UTM, and c (column number), r (row number) in the image. Each side of a pixelhas a dimension of 100 µm in the image, and S / 10,000 on the ground, where Sis the reciprocal scale of the scanned graphic. Figure B-1 illustrates the pixelnumbering principle.

r

c 0

0

21 3

3

1

2

Origin of the image(E0, N0)(c = 0, r = 0)

UTM / UPS: increasing Eastings (E) rightwards

In image : increasing columns (c)

100 µm

Location of a point withUTM / UPS coordinates(E, N)

(E1, N1) (c = 2, r = 1)

Figure B-1: Pixel numbering principles


B - 4

B.2 EASTING AND NORTHING OF A PIXEL.

Parameters used(c,r) = row and column and row of the image pixel;(E1,N1) = grid co-ordinates of the upper-left corner of the pixel;(E0,N0) = grid co-ordinates of the origin of the image;S = reciprocal scale;1/S = scale;S/10 000 = actual side dimension on ground in metres of a pixel with 100µm side at the reciprocal scale S (e.g : 5 m with a 1/50.000 map)Then

E1 ← E0 + c*S/10 000;N1 ← N0 - r*S/10 000;

UTM case : if N1< 0 (i.e. image astride the Equator)1

then N1 ← N1 + 10 000 000;

The best approximation (< E , N >) for all the points represented by the pixel willbe:

< E > ← E0,+ (c+0.5)*S/10 000;

< N > ← N0,- (r+0.5)*S/10 000;

1 - Image astride the Equator, i.e. for which the (0,0) image pixel is North of the Equator and whichthe minimum bounding rectangle has its southern edge South of Equator.


August 1997

B - 5

B.3 IMAGE COORDINATES (c,r) OF A POINT (E,N) .

Parameters used :(E,N) = grid co-ordinates of the current point;(E0,N0) = grid co-ordinates of the origin of the image;S = reciprocal scale;S/10 000 = actual side dimension on ground in metres of a pixel with 100µm side at the reciprocal scale S (e.g : 5 m with a1/50.000 map)Then

c ← round [10 000S *(E - E0)];

UTM case : if N and N0are astride the Equator,

then N ← N - 10 000 000;

r ← round [10 000S *(N0- N)];

B.4 COMPUTATION (FORMULA) OF £ (ISOMETRIC LATITUDE) GIVEN ϕϕϕϕ .

ALL ANGLES IN RADIANS.

£ = ln [ tan( + / 2

2

ϕ π )*( 1 - e * sin( )1 + e * sin( )

ϕϕ

)e/2 ]approaches infinity as ϕ approaches π/2;undefined for ϕ = π/2.


B - 6

B.5 ALGORITHM OF INVERSION OF £ (COMPUTATION OF ϕϕϕϕ GIVEN £0 ).


Quick convergency for every value of £0 .FUNCTION ILSD(in : a,e2 ,£0 ) out : ϕ in radians.

local : e,T,t,ϕm ,ε

ε ←1*10-6

[[ e ← e2 ; T ← exp(£0 ); ϕ ← 0;REPEAT

ϕm ← ϕ ; t ← e*sin(ϕ); ϕ ← 2*Atan[T*(1 + t1 -t )

e/2 ] -

2

π;

UNTIL ABS(ϕ-ϕm )<ε;]]

B.6 COMPUTATION (FORMULA) OF ββββ (TRUE DISTANCE ALONG A

MERIDIAN FROM THE EQUATOR) TO THE LATITUDE ϕ.ϕ.ϕ.ϕ.

ALL ANGLES IN RADIANSy ← sin(2*ϕ);x ← cos(2*ϕ);β ← a*(1-e2 )[b0 *ϕ-y*((((b10 *x-b8 )*x+b6 )*x-b4 )*x+b2 )];

with

b0 = 1 + 34 *e2 +4564 *e4 +175

256 *e6 + 1102516384 *e8 +43659

65536 *e10 ;

b2 = 38 *e2 +1532 *e4 +385

768 *e6 + 5251024 *e8 + 42273

81920 *e10 ;

b4 = 15128 *e4 +105

512 *e6 + 850532768 *e8 + 38115

131072 *e10 ;

b6 = 35768 *e6 + 105

1024 *e8 + 623740960 *e10 ;

b8 = 31516384 *e8 + 3465

65536 *e10

b10 = 69381920 *e10 ;

The set of bi has to be computed just one time for one ellipsoid.


August 1997

B - 7

B.7 ALGORITHM OF INVERSION OF ββββ (Newton-Raphson).

COMPUTATION OF ϕϕϕϕ GIVEN ββββ0 .


Quick convergency for every value of β0 .

FUNCTION IM(a,e2 ,β0 ) out ϕ in radians.local : ϕ0 ,ε

ε ← 1*10-6 [[ ϕ ← 0;

REPEAT

ϕ0 ← ϕ; ϕ ← ϕ - (1- e2 * sin2( ))3/2

a * (1- e2)

ϕ*(β(ϕ)-β0 );

UNTIL ABS(ϕ0 -ϕ)<ε;IM ← ϕ ;]]

(see para B-6 to compute β(ϕ))


B - 8

B 8 UTM PROJECTION (k0 =0.9996) -

COMPUTATION OF (E,N) GIVEN (λλλλ,ϕϕϕϕ).


Values of the false origin for UTM:

Easting = 500 000 metresNorthing = 0 metres (North hemisphere)

10 000 000 metres (South hemisphere)

Putµ ← tan(ϕ);t ← µ2 ;

ε ← e2

1-e2 *cos 2( ) ϕ ;

R ← a

1- e2 * sin2( )

ϕ;

ζ ← (λ-λ0 )*cos(ϕ);then

E ← k0 *R*ζ*(ζ2 *(A5 *ζ2 /20+A3 )/6+1)+500 000;

N ← k0 *( ( ) +R * * 2 * ( 2 * (A6 * 2 / 30 + A4) / 12 +1) / 2) β ϕ µ ζ ζ ζ +10 000 000 * (1- sign(ϕ))/2;

withA3 = ε-t+1;A4 =ε*(4*ε+9)+5-t;A5 =2*ε*(7-29*t)+t*(t-18)+5;A 6 =30*ε*(9-11*t)+t*(t-58)+61;


August 1997

B - 9

B 9 UTM PROJECTION (k0 =0.9996) -

COMPUTATION OF (λλλλ,ϕϕϕϕ) GIVEN (E,N).


Values of the false origin for UTM:

Easting = 500 000 metresNorthing = 0 metres (North hemisphere)

10 000 000 metres (South hemisphere)

Put :

E ← E-500 000k0

;

N ← North case : Nk0

; South case 1 : N-10 000 000k0

;

assuming that ϕ0 is the footpoint latitude.

ϕ0 ← IM(a,e2 ,N ) ; (see function IM para B 7 ; note N actual in-parameter);

Put :µ ← tan(ϕ0 )

t ← µ2 ;

ε ← e2

1-e2 *cos 2( 0 ) ϕ ;

R0 ← a

1- e2 * sin2( 0)

ϕ;

u ← ER0

;

thenλ ← u*(u2 *(B5 *u2 /20-B3 )/6+1)/cos(ϕ0 )+λ0 ;(where λ0 is the longitude of the central meridian);

ϕ ← ϕ0 -µ*u2 *((B6 *u2 /30+B4 )*u2 /12+B2 )/2;


B - 10

withB2 = 1+ε;B3 = ε+2*t+1;B4 = (3*ε*(1 +3*t)+6*(1+t))*ε-3*µ*t-5;B5 = 2*ε*(3+4*t)+4*(6*t+7)*t+5 ;B6 = ε*(107-9*t*(5*t+18))+45*t*(t+2)+61 ;

B.10 UPS PROJECTION (k0 = 0.994) -

COMPUTATION OF (E,N) GIVEN (λλλλ,ϕϕϕϕ).

ALL ANGLES IN RADIANS.Values of the false origin for UPS:

Easting = 2 000 000 metresNorthing = 2 000 000 metres

Put

C ← 2*a

1-e2 *(1-e1+e )

e/2 ; (Constant of the projection);

thenℜ ← if ABS(ϕ) = π/2 then ℜ ← 0;elseℜ ← k0 *C*exp(-£(ϕ)); (see para B 4 to compute £)E ← 2 000 000 + ℜ *sin(λ):N ← 2 000 000 - sign(ϕ)* ℜ *cos(ϕ);


August 1997

B - 11

B 11 UPS PROJECTION (k0 = 0.994) -

COMPUTATION OF (λλλλ,ϕϕϕϕ) GIVEN (E,N).

ALL ANGLES IN RADIANS.Values of the false origin for UPS:

Easting = 2 000 000 metresNorthing = 2 000 000 metres

Put

C ← 2*a

1-e2 *(1-e1+e )

e/2 ; (Constant of the projection);

IF (E = 2 000 000) AND (N = 2 000 000)THEN north case ϕ ← + π/2;

south case ϕ ← - π/2;λ ← 0;exit of procedure;

ENDIF

Putx ← E - 2 000 000;y ← N - 2 000 000;IF y = 0 THEN ¬←sign(x)*π/2;

ELSEnorth case

λ←π*sign(x)*(1+sign(y)2 )- Atan(xy );

south case

λ←π*sign(x)*(1-sign(y)2 ) +Atan(xy );

ENDIF.

ℜ ← x2+y2 ;

ϕ ← ILSD(a,e2 ,ln( k0 * C

ℜ

)) ; north case : ϕ>0; south case : ϕ<0;

(see para B 5-A to compute ILSD)


B - 12

B.12 MAXIMUM STRETCH (SCALE FACTOR).

In UTM and UPS, the scale factor k does not depend upon the bearings and, ifnecessary , can be computed with the following formulae :

UTM (k0 = 0.9996)

k ≈ k0 *cosh [(E-500 000)k0*a *

1- e2 * sin2( )

1- e2 ϕ

] ;

where cosh is the hyperbolic cosine.The scale distortion in UTM is always inferior to 0,04% and can be neglected for most uses.

UPS (k0 = 0.994)

k = k0 * ( )

a

ℜ ϕ* 1- e2 * sin2( ) ϕ ; (see para B 10 to compute ℜ ).

The scale distortion in UPS can reach 0,6% and has to be taken in accounts for some uses.

B.13 SOURCE DATUM GEOGRAPHIC COORDINATES

FROM WGS84 GEOGRAPHIC COORDINATES.

CAUTION :

- FORMULAE HEREAFTER MUST BE USED DIRECTLY WITH PARAMETERSAND COEFFICIENTS PROVIDED BY US DEFENSE MAPPING AGENCY- SOANGLES ARE ASSUMED TO BE IN VARIOUS UNITS.- USE THESE PARAMETERS AND COEFFICIENTS EXCLUSIVELYINSIDE THEIR DOMAIN OF VALIDITY.

Parameters used :ϕ84 = geodetic latitude on WGS84 datum;λ84 = geodetic longitude on WGS84 datum;ϕsdc = geodetic latitude on source datum;λsdc = geodetic longitude on source datum;ϕoff ; λoff = normalizing offset;


August 1997

B - 13

Parameters used (continued) :U = reduced parameter in latitude;V = reduced parameter in longitude;S = normalizing factor (DO NOT CONFUSE WITH RECIPROCAL

SCALE USED ABOVE )ai,j ; bi,j = coefficients of Multiple Regression Equations.n = degree of the MRE expansion.

Then :

ϕsdc ← ϕ84 - ∆ϕ or ϕ84 ← ϕsdc + ∆ϕ ;λsdc ← λ84 - ∆λ or λ84 ← λsdc + ∆λ ;

where :

∆ϕ (in seconds) = i=0

i=n

j = 0

j=n,(i+ j) n

∑ ∑≤

ai,j *Ui *Vj ;

∆λ (in seconds) = i=0

i=n

j = 0

j=n,(i+ j) n

∑ ∑≤

bi,j *Ui *Vj ;

with :U = S*(ϕsdc -ϕoff ) ; (ϕsdc -ϕoff ) in degrees and decimal part of a degree;V = S*(λsdc -λoff ) ; (λsdc -λoff ) in degrees and decimal part of a degree.

COEFFICIENTS FROM ED50 TO WGS84(WESTERN EUROPE ONLY)

ϕϕϕϕoff = 52° ; λoff = 10 ° ; n = 13 ; S = 0.05235988

ai,j (ACT = 15)

a0,0 -2,65261 a2,7 -0,10572a0,1 0,77921 a3,0 0,76407a0,8 -0,05401 a3,9 0,02445a1,0 2,06392 a4,0 0,17197a1,1 0,10706 a4,1 1,04974a1,9 0,05283 a5,2 -0,22899a2,0 0,26743 a9,0 -0,78909a2,1 -0,95430


B - 14

bi,j (BCT = 30)

b0,0 -4,13447 b3,3 -6,52522b0,1 1,94075 b4,0 -1,70401b0,2 0,30068 b4,4 4,49096b0,5 -1,97974 b4,6 -17,45428b0,9 0,16438 b4,9 0,71041b1,0 -1,50572 b5,0 7,41956b1,1 1,98425 b5,7 8,87141b1,3 -5,48711 b6,0 1,57701b1,4 5,92923 b6,1 -14,32516b1,5 -1,79701 b7,0 -3,08344b2,0 -1,37600 b7,2 7,80215b2,3 -1,61351 b8,1 9,98750b2,4 16,85976 b8,3 5,28734b2,7 -2,26917 b9,2 -8,25844b3,0 -2,31939 b9,4 -3,48015 All coefficients not above mentioned are equal to zero.

B.14 SOURCE DATUM UTM GRID COORDINATES

FROM WGS84 UTM GRID COORDINATES.

Parameters used :E84 = UTM Easting on WGS84 UTM grid;N84 = UTM Northing on WGS84 UTM grid;Esdc = UTM Easting on source datum UTM grid;Nsdc = UTM Northing on source datum UTM grid;Θ = angle of rotation from source datum UTM grid to WGS84 UTM grid;∆E = normalized Easting shift ;∆N = normalized Northing shift;

then :Esdc ← ∆E + E84 *cos(Θ) - N84 *sin(Θ);Nsdc ← ∆N + E84 *sin(Θ) + N84 *cos(Θ);

DIGEST Part 4 Enclosure 1 toEdition 1.2 USRP Edition 1.3January 1994 August 1997Annex B - Attribute and Value Codes

Encl 1 - 1

Annex B. ATTRIBUTE AND VALUE CODES

NOTE. The following is ONLY that subset of DIGEST Edition 1.2Part 4 Annex B attributes which is applicable to the USRP specification.

CDP — Calendar Date Type

The type of report or activity.

CDP 000 Unknown001 Aerial Photography002 Air Information003 Approximate004 Field Classification005 Compilation006 Copyright007 Creation008 Digitizing009 Distribution/Dispatching010 Downgrading011 Drafting/Scribing/Drawing012 Edition013 Field Examination014 Intelligence015 Date Interpretable016 Processing017 Print/Publication018 Receipt019 Source020 Earliest Date of Source021 Latest Date of Source022 Specifications023 Survey024 Up-to-dateness/revision025 Map Edit026 Information as of ---027 Perishable Information Date028 Cycle Date029 Significant Date030 Date of Magnetic Information999 Other

Enclosure 1 to DIGEST Part 4USRP Edition 1.3 Edition 1.2August 1997 January 1994

Annex B - Attribute and Value Codes

Encl 1 - 2

NST — Navigation System Types

Type of equipment or system used in electronic navigation

NST 000 Unknown001 Circular Radio Beacon002 CONSOL003 DECCA004 Radio Direction Finding005 Directional Radio Beacon006 Distance Finding007 Long Range Navigation System (LORAN)008 OMEGA009 VALUE INTENTIONALLY LEFT BLANK010 Radar Responder Beacon (RACON)011 Radar012 Radio013 Radio Telephone014 VALUE INTENTIONALLY LEFT BLANK015 TV016 Microwave017 Non-Directional Radio Beacon (NDB)018 VALUE INTENTIONALLY LEFT BLANK019 Radio Range (RNG)020 VHF Omni Directional Radio Range (VOR)021 VHF Omni Directional (VOR/DME)022 VHF Omni Directional (VORTAC)023 Tactical Air Navigation Equipment (TACAN)024 Instrument Landing System (ILS)025 VALUE INTENTIONALLY LEFT BLANK026 Localizer (LOC)027 VALUE INTENTIONALLY LEFT BLANK028 Simplified Directional Facility (SDF)029 Landing Distance Available (LDA)030 Microwave Landing System (MLS)031 Fan Marker032 Bone Marker033 Radio Telegraph034 Ground Controlled Approach (GCA)035 Radar Antenna037 Precision Approach Radar (PAR)038 Aeronautical Radio039 VALUE INTENTIONALLY LEFT BLANK

DIGEST Part 4 Enclosure 1 toEdition 1.2 USRP Edition 1.3January 1994 August 1997Annex B - Attribute and Value Codes

Encl 1 - 3

040 Radio Beacon041 Rotating Loop Radio Beacon042 Visual Flight Rules (VFR) Test Signal Maker043 VALUE INTENTIONALLY LEFT BLANK044 Consol Radio Beacon045 Aeronautical Radio Range046 Radar Station047 Hifix048 Hyperfix049 Tricolor Panel999 Other

Enclosure 1 to DIGEST Part 4USRP Edition 1.3 Edition 1.2August 1997 January 1994

Annex B - Attribute and Value Codes

Encl 1 - 4


DIGEST Part 3 Enclosure 2 toEdition 1.2a USRP Edition 1.3June 1995 August 19977 — Grid Codes

Encl 2 - 1

7 GRID CODES

Table 7-1 provides the allowable grids and their codes for the Grid System field.

Table 7-1 Grid Codes

Grid Description Code1 Aden Zone AD2 Afghanistan Gauss-Kruger Grid AF3 Air Defense Grid AG4 Air Support Grid AI5 Alabama Coordinate System AJ6 Alaska Coordinate System AK7 Algeria Zone AL8 Albania Bonne Grid AM9 Alpha-Numeric (Atlas) Grid AN

10 Arbitrary Grid AO11 American Samoa Coordinate System AP12 Argentine Gauss-Kruger Conformal Grid AQ13 Artillery Referencing System AR14 Arizona Coordinate System AS15 Australia Belt AU16 Arkansas Coordinate System AV17 Australian Map Grid AW18 Azores Gauss Conformal Grid AX19 Azores Zone AZ20 Baku 1927 Coordinate System BA21 Bavaria Solder Coordinate System BB22 Belgium Lambert Grid BC23 Belgium Bonne Grid BE24 Brazil Gauss Conformal Grid BF25 Borneo Rectified Skew Orthomorphic Grid BO26 British West Indies Grid BW27 California Coordinate System CB28 Canada British Modified Grid CD29 Ceylon Belt (Transverse Mercator) CE30 Canary Islands (Spanish~ Lambert Grid) CF31 Chile Gauss Conformal Grid CG32 China Belt CH33 Canary Islands Zone CI34 China Lambert Zone CJ35 Colorado Coordinate Zone CK36 Connecticut Coordinate System CM37 Caspian Zone CN38 Costa Rica Lambert Grid CO39 Crimea Grid CQ

Enclosure 2 to DIGEST Part 3USRP Edition 1.3 Edition 1.2aAugust 1997 June 1995

7 — Grid Codes

Encl 2 - 2

40 Crete Zone CR41 Cuba Lambert Grid CT42 Caucasus Zone CU43 Cape Verde Islands Zone CV44 British Cassini Grid CW45 Czechoslovak Uniform Cadastral Coordinate System CX46 Cyprus Grid CY47 Czechoslovak Military Grid CZ48 Danube Zone DA49 Dahomey Belt DB50 Denmark General Staff Grid DC51 Delaware Coordinate System DD52 Dominican Lambert Grid DE53 Denmark Geodetic Institute System 1924 DJ54 Cape Verde Peninsula Grid DK55 East Africa Belt EA56 English Belt EB57 Eqypt Gauss Conformal Grid ED58 El Salvador Lambert Grid EE59 Estonian Grid EF60 Egypt Purple Belt EP61 Egypt Red Belt ER62 Egypt 35 Degree Belt ET63 Fernando Poo Gauss Grid FA64 Fiji Grid FB65 Florida Coordinate System FC66 French Bonne Grid FD67 French Guiana Gauss Grid FE68 French Somaliland Gauss-LaBorde Grid FF69 French Indochina Grid FI70 Franz Josef Land Zone FJ71 French Lambert Grid FL72 Formosa (Taiwan) Gauss-Schreiber Coordinate System FO73 French Equatorial Africa Grid FS74 Gabon Belt GA75 Gauss-Boaga Grid (Transverse Mercator) GB76 Gabon Gauss Conformal Grid GC77 Geodetic GD78 Guadeloupe Gauss-LaBorde Grid GF79 Colombia Gause Conformal Grid GG80 Sweden Gauss-Hannover Grid GH81 Georgia Coordinate System GI82 Gauss-Kruger Grid (Transverse Mercator) GK83 Greece Azimuthal Grid GL84 German Army Grid (DHG) GN85 Ghana National Grid GO


Encl 2 - 3

86 Greece Bonne Grid GP87 Greece Conical Mecklenburg Coordinates GQ88 Geographic Reference System (GEOREF) GR89 Greece Conical Mecklenburg Coordinate (New Numbering) GM90 Greenland Lambert Grid GT91 Guinea Zone GU92 Guam Coordinate System GV93 Guatemala Lambert Grid GW94 Guyana Transverse Mercator Grid GY95 Haiti Lambert Grid HB96 Hawaii Coordinate System HC97 Hawaii Grid HD98 Honduras Lambert Grid HE99 Hong Kong New System Cassini Grid HF

100 Hungary Stereographic Grid HG101 Hong Kong Colony Grid HR102 Idaho Coordinate System IA103 Illinois Coordinate System IB104 Indiana Coordinate System IC105 Indonesia Mercator Grid ID106 Indonesia Polyhedric Grid IE107 Iowa Coordinate System IF108 Ivory Coast Azimuthal Grid IG109 Irish Cassini Grid IH110 Ivory Coast Belt IJ111 Irish Transverse Mercator Grid IK112 Iceland New Lambert Zone IL113 India Zone IN114 Iberian Peninsula Zone IP115 Iraq Zone IQ116 Iraq National Grid IR117 Italy Zone IT118 Ivy - Found on an HA in Marshall Islands IY119 Iceland Zone IZ120 Jamaica Foot Grid JA121 Japan Plane-Rectangular Coordinate System JB122 Japan Gauss-Schreiber Grid JC123 Johore Grid JO124 Austria Gauss-Kruger Grid KA125 Bulgaria Gauss-Kruger Grid KB126 Katanga Grid KC127 Kansas Coordinate System KD128 Kentucky Coordinate System KE129 Finland Gauss-Kruger Grid KF130 German Gauss-Kruger Grid KG131 Kenya Colony Grid KH


7 — Grid Codes

Encl 2 - 4

132 Korea Gauss-Schreiber Coordinate System KJ133 Louisiana Coordinate System KK134 Lithuania Gauss-Kruger Grid KL135 Kwantung Province Grid KN136 Turkey Gauss-Kruger Grid KT137 Kwangsi Province Grid KW138 Luxembourg Gauss-Kruger Grid KX139 Lambert Conformal Conic Grid LC140 Latvia Coordinate System LD141 Levant Zone LE142 Levant Stereographic Grid LF143 Liberia Rectified Skew Orthomorphic Grid LG144 Libya Zone LI145 Sirte (Libya) Lambert Grid LL146 Malaya Grid MA147 Malta Belt MB148 Maldive-Chagos Belt MC149 Madiera Zone MD150 Mediterranean Zone ME151 Maine Coordinate System MF152 Malaya Rectified Skew Orthomorphic Grid MG153 Military Grid Referense System MGRS154 Martinique Gauss Grid MH155 Maryland Coordinate System MI156 Mexican Lambert Grid MK157 Michigan Coordinate System ML158 Mecca-Muscat Zone MM159 Minnesota Coordinate System MN160 Madagascar Grid (Laborde) MO161 Mississippi Coordinate System MP162 Morocco Zone MQ163 Missouri Coordinate System MT164 Mauritius Zone MU165 Montana Coordinate System MV166 Mozambique Lambert Grid MW167 Mozambique Polyconic Grid MX168 Massachusetts Coordinate System MJ169 Northwest Africa Zone NA170 Nigeria Colony Belt NC171 National Grid of Great Britain ND172 Northern European Zone NE173 Nebraska Coordinate System NF174 Numeric Grid NG175 Niger Zone NI176 Netherlands Stereographic Grid (Old Numbering) NJ177 North Korea Gauss-Kruger Grid NK


Encl 2 - 5

178 Netherlands Stereographic Grid (New Numbering) NL179 Netherlands East Indies Equatorial Zone British Metric Grid

(Lambert)NM

180 Nord de Guerre Zone NO181 Nevada Coordinate System NP182 New Sierra Leone Colony Grid NQ183 New York Coordinate System NR184 Netherlands East Indies Southern Zone NS185 New Zealand National Grid NT186 Nicaragua Lambert Grid NU187 Niger Belt NV188 North Carolina Coordinate System NW189 North Dakota Coordinate System NX190 Netherlands East Indies Equatorial Zone U.S. Yard Grid NY191 New Zealand Belt NZ192 Northern Malaya Grid OA193 Norway Gauss-Kruger Grid OB194 Ohio Coordinate System OD195 Oklahoma Coordinate System OE196 Orange Report Net OR197 Oregon Coordinate System OS198 Palestine Belt PA199 Panama Lambert Grid PB200 Palestine Civil Grid (Cassini) PC201 Paraguay Gauss-Kruger Grid PD202 Peiping Coordinate System of 1954 PE203 Pennsylvania Coordinate System PF204 Peru Polyconic Grid PI205 Philippine Plane Coordinate System PJ206 Poland Gauss-Kruger Grid PK207 Poland Quasi-Stereographic Grid PL208 Philippine Polyconic Grid PP209 Portugal Bonne Grid, Old PQ210 Portugal Bonne Grid, New PR211 Portugal Gauss Grid PS212 Puerto Rico Coordinate System PT213 Puerto Rico Lambert Grid PU214 Qatar Grid QA215 Qatar Peninsula Grid QU216 Russian Belt RB217 Reunion Gauss Grid RC218 Rhode Island Coordinate System RD219 Rumania Bonne Grid RE220 Soviet Coordinate System of 1942 RF221 Rumania Lambert-Cholesky Grid RH


7 — Grid Codes

Encl 2 - 6

222 Rumania Stereographic Grid RI223 Pulkovo Coordinate System of 1932 RT224 South Africa Belt SA225 Senegal Gauss Conformal Grid (Belt) SB226 South Africa Coordinate System (Republic of South Africa) SD227 Senegal Belt SE228 South Carolina Coordinate System SF229 Sahara Zone SH230 South Dakota Coordinate System SI231 South Libya Zone SJ232 Sarawak Grid SK233 Spain Lambert Grid SL234 Southern New Guinea Grid SN235 South Georgia Lambert Grid SQ236 South Syria Lambert Grid SR237 Spanish North-Morocco Lambert Grid SS238 Svalbard Gauss-Kruger Grid SV239 Svobodny 1935 Coordinate System SX240 Seychelles Belt SY241 Spitzbergen Zone SZ242 Tanganyika Territorial Grid TA243 Tashkent 1875 Coordinate System TB244 Tennessee Coordinate System TC245 Texas Coordinate System TD246 Tobago Grid TE247 Trinidad Grid TF248 Trucial Coast Cassini Grid TG249 Trucial Coast Transverse Mercator Grid TH250 Turkey Bonne Grid TI251 Tunisia Zone TN252 Uganda Cassini Coordinate System UA253 Unidentified Grid UB254 Uruguay Gauss-Kruger Grid UC255 Utah Coordinate System UD256 Universal Polar Stereographic System UP257 U.S. Polyconic Grid System US258 Universal Transverse Mercator UT259 Vermont Coordinate System VA260 Virginia Coordinate System VB261 Venezuela Modified Lambert Grid VE262 Viet Nam Azimuthal Grid VI263 West Malaysia Rectified Skew Orthomorphic(Metric)Grid WA264 Switzerland Bonne Grid WB265 Switzerland Conformal Oblique Cylindrical Grid WC266 West Virginia Coordinate System WD267 Wisconsin Coordinate System WE


Encl 2 - 7

268 Wyoming Coordinate System WF269 World Polyconic System WP270 Yugoslavia Gauss-Kruger Grid (Not Reduced) YA271 Yugoslavia Reduced Gauss-Kruger Grid YG272 Yunnan Province Grid YU


7 — Grid Codes

Encl 2 - 8


DIGEST Part 3 Enclosure 3 toEdition 1.2a USRP Edition 1.3June 1995 August 19978 — Ellipsoid Codes

Encl 3 - 1

8 ELLIPSOID CODES

Table 8-1 provides the allowable ellipsoids and their codes for the Ellipsoid field.

Table 8-1 Ellipsoid Codes

Ellipsoid Code1 Modified Airy AAM2 Airy AAY3 Australian National AUN4 Bessel 1841 BES5 Clarke 1858 CLE6 Clarke 1880 CLJ7 Clarke 1866 CLK8 Everest EVE9 Modified Everest EVM

10 Modified Fischer 1960 FAM11 Fischer FIS12 Geodetic Reference System 1967 GRE13 Geodetic Reference System 1980 GRS14 Helmert 1906 HEL15 Hough HOU16 Indonesian 1974 IDN17 International INT18 Krassovsky KRA19 South American 1969 SAM20 Walbeck WAL21 World Geodetic System 1960 WGA22 World Geodetic System 1966 WGB23 World Geodetic System 1972 WGC24 World Geodetic System 1984 WGE


8 — Ellipsoid Codes

Encl 3 - 2


DIGEST Part 3 Enclosure 4 toEdition 1.2a USRP Edition 1.3June 1995 August 19979 — Datum Codes

Encl 4 - 1

9 DATUM CODES

Table 9-1 provides the allowable datums and their codes for the GeodeticDatum fields. Sounding Datum and the Vertical Reference System fieldusage are also covered in the Feature and Attribute Coding Catalogue(Part 4).

Table 9-1 Datum Codes

Geodetic Datums Code1 Adindan ADI2 Adindan (Ethiopia) ADIA3 Adindan (Sudan) ADIB4 Adindan (Mali) ADIC5 Adindan (Senegal) ADID6 Adindan (Mean value: Ethiopia and Sudan) ADIM7 Afgooye (Somalia) AFG8 Ain el Abd 1970 (Bahrain Island) AIN9 Anna 1 Astro (Cocos Islands) ANO

10 Arc 1950 ARF11 Arc 1950 (Botswana) ARFA12 Arc 1950 (Lesotho) ARFB13 Arc 1950 (Malawi) ARFC14 Arc 1950 (Swaziland) ARFD15 Arc 1950 (Zaire) ARFE16 Arc 1950 (Zambia) ARFF17 Arc 1950 (Zimbabwe) ARFG18 Arc 1950 (Mean value: Botswana, Lesotho, Malawi,

Swaziland, Zaire, Zambia, and Zimbabwe)ARFM

19 Arc 1960 (Kenya) ARSA20 Arc 1960 (Tanzania) ARSB21 Arc 1960 (Mean value: Kenya, Tanzania) ARSM22 Ascension Island 1958 (Ascension Island) ASC23 Astro Station 1952 (Marcus Island) ASQ24 Astro Beacon "E" (Iwo Jima Island) ATF25 Average Terrestrial System (Atlantic Datum) 1997 ATS26 Australian Geod. 1966 (Australia and Tasmania Is.) AUA27 Australian Geod. 1984 (Australia and Tasmania Is.) AUG28 Djakarta (Batavia) (Sumatra Island, Indonesia) BAT29 Bermuda 1957 (Bermuda Islands) BER30 Bogota Observatory (Colombia) BOO31 Bukit Rimpah (Bangka & Belitum Islands, Indonesia) BOR32 Bukit Rimpah BUR33 Canton Astro 1966 (Phoenix Islands) CA0


9 — Datum Codes

Encl 4 - 2

34 Cape Canaveral (Mean value: Florida and BahamaIslands)

CAC

35 Campo Inchauspe (Argentina) CAI36 Cape (South Africa) CAP37 Camp Area Astro (Camp McMurdo Area, Antartica) CAZ38 Carthage (Tunisia) CGE39 Chua Astro (Paraguay) CHG40 Chatham 1971 (Chatham Island, New Zealand) CHI41 Chua Astro CHU42 Corrego Alegre (Brazil) COA43 Guyana CSG67 CSG44 GUX 1 Astro (Guadacanal Island) DOB45 Easter Island 1967 (Easter Island) EAS46 European 79 ENB47 Wake-Eniwetok 1960 (Marshall Islands) ENW48 European 1979 (Mean value: Austria, Finland,

Netherlands, Norway, Spain, Sweden, andSwitzerland)

EUQ

49 European 1950 (Mean value) EUR50 European 1950 (Western Europe: Austria,

Denmark, France, Federal Republic of Germany ,Netherlands, and Switzerland)

EURA

51 European 1950 (Greece) EURB52 European 1950 (Norway and Finland) EURC53 European 1950 (Portugal and Spain) EURD54 European 1950 (Cyprus) EURE55 European 1950 (Egypt) EURF56 European 1950 (Iran) EURH57 European 1950 (Sardinia) EURI58 European 1950 (Sicily) EURJ59 European 1950 (England, Channel Islands, Ireland,

Northern Ireland, Scotland, Shetland Islands, andWales)

EURK

60 European 1950 (Mean value: Austria, Belgium,Denmark, Finland, France, Federal Republic ofGermany, Gibraltar, Greece, Italy, Luxembourg,Netherlands, Norway, Portugal, Spain, Sweden, &Switzerland)

EURM

61 Oman (Oman) FAH61a French NTF FDA62 Observatorio 1966 (Corvo and Flores Islands,

Azores)FLO

63 GAN Datum (Addu Atoll, Republic of Maldives) GAA64 German GDA65 Geodetic Datum 1949 (New Zealand) GEO66 Ghana GHA


Encl 4 - 3

67 DOS 1968 0230 (Gizo Island, New Georgia Islands) GIZ68 SW Base (Faial, Graciosa, Pico, Sao Jorge, and

Terceira Island, Azores)GRA

69 Genung Segara (Kalimantan Island, Indonesia) GSE70 G. Serindung GSF71 Guam 1963 GUA72 Guadeloupe Ste. Anne GUD73 Herat North (Afganistan) HEN74 Hermannskogel HER75 Prov. S. Chilea.i (S. Chile, 53 S.) HIT76 Hjorsey 1955 (Iceland) HJO77 Hong Kong 1963 (Hong Kong) HKD78 Hu-tzu-shan HTN79 Bellevue (IGN) (Efate and Erromango Islands) IBE80 Italian IDA81 Indian IND82 Indian (Thailand and Vietnam) INDA83 Indian (Bangladesh, India, and Nepal) INDB84 Ireland 1965 IRE85 Ireland 1965 (Ireland and Northern Ireland) IRL86 ISTS 073 Astro 1969 (Diego Garcia) IST87 Johnston Island 1961 (Johnston Island) JOH88 Kandawala (Sri Lanka) KAN89 Kertau 1948 (West Malaysia and Singapore) KEA90 Kerguelen Island 1949 (Kerguelen Island) KEG91 L.C. 5 Astro 1961 (Cayman Brac Island) LCF92 Liberia 1964 (Liberia) LIB93 Local Astro. LOC94 Luzon LUZ95 Luzon (Philipines except Mindanao Island) LUZA96 Luzon (Mindanao Island) LUZB97 Martinique Fort-Desaix MAR98 Marco Astro (Salvage Islands) MAA99 Massawa (Eritrea, Ethiopia) MAS

100 Mayotte Combani MAY101 Merchich MER102 Merchich (Morocco) MER103 Midway Astro 1961 (Midway Island) MID104 Mahe 1971 (Mahe Island) MIK105 Minna (Nigeria) MIN106 Rome 1940 (Sardinia Island) MOD107 Montjong Lowe MOL


9 — Datum Codes

Encl 4 - 4

108 Viti Levu 1916 (Viti Levu Island, Fiji Islands) MVS109 Nahrwan (Masirah Island, Oman) NAHA110 Nahrwan (United Arab Emirates) NAHB111 Nahrwan (Saudi Arabia) NAHC112 Naparima (BWI Trinidad and Tobago) NAP113 North American 1983 (Mean Value: Alaska,

Canada, CONUS, Mexico, and Central America)NAR

114 North American 1927 (Mean value) NAS115 North American 1927 (Eastern US) NASA116 North American 1927 (Western US) NASB117 North American 1927 (Mean value: CONUS) NASC118 North American 1927 (Alaska) NASD119 North American 1927 (Mean value: Canada) NASE120 North American 1927 (Alberta and British Columbia) NASF121 North American 1927 (Newfoundland, New

Brunswick, Nova Scotia and Quebec)NASG

122 North American 1927 (Manitoba and Ontario) NASH123 North American 1927 (Northwest Territories and

Saskatchewan)NASI

124 North American 1927 (Yukon) NASJ125 North American 1927 (Mexico) NASL126 North American 1927 (Central America - Belize,

Costa Rica, El Salvador, Guatemala, Honduras, andNicaragua)

NASN

127 North American 1927 (Canal Zone) NASO128 North American 1927 (Caribbean, Barbados, Caicos

Islands, Cuba, Dominican Republic, Grand Cayman,Jamaica, Leeward Islands, and Turks Islands)

NASP

129 North American 1927 (Bahamas, except SanSalvador Island)

NASQ

130 North American 1927 (San Salvador Island) NASR131 North American 1927 (Cuba) NAST132 North American 1927 (Hayes Peninsula, Greenland) NASU133 North American 1983 NAX134 Nigeria NIG135 Old Egyptian (Egypt) OEG136 Ordnance Survey of Great Britain OGB137 Ord. Survey G.B. 1936 (England) OGBA138 Ord. Survey G.B. 1936 (England, Isle of Man, and

Wales)OGBB

139 Ord. Survey G.B. 1936 (Scotland and ShetlandIslands)

OGBC

140 Ord. Survey G.B. 1936 (Wales) OGBD141 Ord. Survey G.B. 1936 (Mean value: England, Isle

of Man, Scotland, Shetland, and Wales)OGBM


Encl 4 - 5

142 Old Hawaiian OHA143 Old Hawaiian (Hawaii) OHAA144 Old Hawaiian (Kauai) OHAB145 Old Hawaiian (Maui) OHAC146 Old Hawaiian (Oahu) OHAD147 Old Hawaiian (Mean value) OHAM148 Pitcairn Astro 1967 (Pitcairn Island) PIT149 Pico de las Nieves (Canary Islands) PLN150 SE Base (Porto Santo) (Porto Santo & Madeira

Islands)POS

151 Provisional South American 1956 PRP152 Prov. S. Amer. 1956 (Northern Chile near 19

degrees south)PRPA

153 Prov. S. Amer. 1956 (Southern Chile near 43degrees south)

PRPC

154 Prov. S. Amer. 1956 (Columbia) PRPD155 Prov. S. Amer. 1956 (Ecuador) PRPE156 Prov. S. Amer. 1956 (Guyana) PRPF157 Prov. S. Amer. 1956 (Peru) PRPG158 Prov. S. Amer. 1956 (Venezuela) PRPH159 Prov. S. Amer. 1956 (Mean value: Bolivia, Chile,

Colombia, Ecuador, Guyana, Peru, & Venezuela)PRPM

160 Puerto Rico (Puerto Rico and Virgin Islands) PUR161 Qatar National (Qatar) QAT162 Qornoq (South Greenland) QUO163 Reunion 1947 REU164 Santo (DOS) 1965 (Espirito Santo Island) SAE165 South American 1969 (Argentina) SANA166 South American 1969 (Bolivia) SANB167 South American 1969 (Brazil) SANC168 South American 1969 (Chile) SAND169 South American 1969 (Columbia) SANE170 South American 1969 (Ecuador) SANF171 South American 1969 (Guyana) SANG172 South American 1969 (Paraguay) SANH173 South American 1969 (Peru) SANI174 South American 1969 (Trinidad and Tobago) SANK175 South American 1969 (Venezuela) SANL176 South American 1969 (Mean value: Argentina,

Bolivia, Brazil, Chile, Columbia, Ecuador, Guyana,Paraguay, Peru, Trinidad and Tobago, andVenezuela)

SANM

177 Sao Braz (Sao Miguel, Santa Maria Islands, Azores) SAO178 Sapper Hill 1943 (East Falkland Islands) SAP179 Schwarzeck (Namibia) SCK


9 — Datum Codes

Encl 4 - 6

180 Astro Dos 71/4 (St. Helena Island) SHB181 Sierra Leone 1960 SIB182 South Asia (Southeast Asia, Singapore) SOA183 St. Pierre et Miquelon 50 STP184 Tananarive Obsv. 1925 TAN185 Tristan Astro 1968 (Tristan da Cunha) TDC186 Timbali 1948 (Brunei and East Malaysia - Sarawak

and Sabah)TIL

187 Tokyo (Mean value) TOK188 Tokyo (Japan) TOYA189 Tokyo (Korea) TOYB190 Tokyo (Okinawa) TOYC191 Tokyo (Mean value: Japan, Korea, and Okinawa) TOYM192 Astro Tern Is. 1961 (Tern Island, Hawaii) TRN193 Undetermined (processed as if WGS 84) UND194 Voirol VOI195 World Geodetic System 1960 WGA196 World Geodetic System 1966 WGB197 World Geodetic System 1972 WGC198 World Geodetic System 1984 WGE199 Yacare (Uruguay) YAC200 Zanderij (Surinam) ZAN

Sounding Datum Code1 Mean Higher High Water MHHW2 Mean High Water MHW3 Mean High Water Neaps MHWN4 Mean High Water Springs MHWS5 Mean Lower Low Water MLLW6 Mean Low Water MLW7 Mean Low Water Neaps MLWN8 Mean Low Water Springs MLWS

Vertical Reference Code1 Geodetic (All elevations in the data set are

referenced to the ellipsoid of the specified datum.)GEOD

2 Mean Sea Level (All elevations in the data set arereferenced to the geoid of the specified datum.)

MSL

DIGEST Part 3 Enclosure 5 toEdition 1.2a USRP Edition 1.3June 1995 August 19976 — Projection Codes

Encl 5 - 1

6 PROJECTION CODES AND PARAMETERS

Table 6-1 provides the allowable projections and their codes and parameters forthe Dataset Map Projection Group. These codes and parameters are necessaryfor conversion of digitized map coordinates to geographic coordinates.

Table 6-1 Projection Codes and Parameters

NAME CODE PARAMETERS1 2 3 4

Albers EqualArea

AC CentralMeridian

Std. ParallelNearer toEquator

Std. ParallelFarther fromEquator

Parallel ofOrigin

Azimuthal EqualArea

AK Longitude ofTangency

Latitude ofTangency

- -

Azimuthal EqualDistant

AL Longitude ofTangency

Latitude ofTangency

- -

Gnomonic GN Longitude ofTangency

Latitude ofTangency

- -

Hotine ObliqueMercator(Rectified SkewOrthomorphic)

RB Longitude ofProj. Origin

Latitude ofProj. Origin

Azimuth ofSkew X-Axisat Proj. Origin

ScaleFactorat Proj. Origin

LambertConformal Conic

LE CentralMeridian

Std. ParallelNearer toEquator

Std ParallelFarther fromEquator

Parallel ofOrigin

Lambert EqualArea

LJ CentralMeridian

- - -

Mercator MC CentralMeridian

Latitude ofTrue Scale

Parallel ofOrigin

-

Oblique Mercator OC Longitude ofReferencePoint onGreat Circle

Latitude ofReferencePoint onGreat Circle

Azimuth ofGreat Circleat ReferencePoint

-

Orthographic OD Longitude ofTangency

Latitude ofTangency

- -

Polar Stereo-graphic

PG CentralMeridian

Latitude ofTrue Scale

- -

Polyconic PH CentralMeridian

- - -

TransverseMercator

TC CentralMeridian

Central ScaleFactor

Parallel ofOrigin

-

ObliqueStereographic

SD Longitude ofOrigin

Latitude ofOrigin

Scale factorat Origin

-

RelativeCoordinates

RC X-ScaleFactor

Y-ScaleFactor


6 — Projection Codes

Encl 5 - 2


DIGEST Part 3 Enclosure 6 toEdition 1.2a USRP Edition 1.3June 1995 August 199713 — Use of CIE Values

Encl 6 - 1

13 USE OF CIE VALUES

CIE is an international colour system for defining colour produced by the"Commission Internationale de l'Eclairage". A number of systems for identifyingcolours, and the difference between colours, have been promulgated by the CIE.These are all based on measuring the Tristimulus values (Red, Green and Blueintensities) of a colour relative to a standard white. The method chosen by theDGIWG is to use the coordinates to the CIE chromaticity chart (see Figure 13-1).This is also the method used in the DoD Standard Printing Color Catalog(Reference 29). Of the other two systems, the CIELUV system is more applicableto the TV industry, and the CIELAB system, while providing finer discriminationbetween similar colours, is unnecessarily complex for the requirements of rasterimages. It is only necessary to uniquely identify what a colour should be; anydifference in hue from the colour printed or captured by the scanner is irrelevant.

Defining accurately and consistently the colours that should appear in the rasterimage of a map, irrespective of any changes in colour introduced by both theprinting and scanning processes, should not be difficult. In most cases the mapspecification defines what the various colours used in its production should be byreference to a standard colour chart or catalogue. An example of this isReference 29, which as well as printing sample colours also gives the CIE Valuesfor that colour. Where the standard colour catalogue referenced by a mapspecification does not give the CIE Values, then these may be obtained by:

• identifying the CIE Values for the catalogue in accordance withReference 30 which defines the standard white to be used andthe method to be adopted; or

• identifying the closest approximation to each colour in Reference29 and assigning those CIE Values to the local standard colourcatalogue. This method should only be used where the precisedefinition of a colour is not critical (i.e. the map series is onlyproduced and/or scanned by one agency).

Defining what a map colour should be according to a recognized standardwill ensure that:

• the colour can be readily identified by the receiving agency oruser;

• precise consistency of colour can be achieved between samplesof the same raster product produced not only by the sameagency, but by different agencies; and

• users of applications will not be distracted by changes in colourand luminosity (which is worse) when traversing map boundaries.


13 — Use of CIE Values

Encl 6 - 2

0.9

0.8

0.7

0.6

0.5

0.4

0.3

0.2

0.1

0

0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8

coefficients of x

coef

ficie

nts

of y

600

700

400

550

500

450

CIE CHROMATICITY CHART

WHITE

Nonspectral

colours

Figure 13-1 CIE ChromaticityChart

Notes: 1. The colour coordinates are given as x,y,Y where Y is the reflectance.2. The numbers round the rim of the graph are the dominant

wavelength in nanometres.

DIGEST Part 3 Enclosure 7 toEdition 1.2a USRP Edition 1.3June 1995 August 199711 — Country Codes

Encl 7 - 1

11 COUNTRY CODES

Refer to US FIPS PUB 10-3/4 for country codes.


11 — Country Codes

Encl 7 - 2


DIGEST Part 3 Enclosure 8 toEdition 1.2a USRP Edition 1.3June 1995 August 199712 — Media Recording Standards

Encl 8 - 1

12 CODES FOR MEDIA RECORDING STANDARDS

Table 12-1 lists the codes for the various media recording standards.

Table 12-1 Codes for Media Recording Standards

Media Recording Standard Code

Non-standard/Bilateral agreement 0

Magnetic Tape

• ISO 3788 (1600 PE) 1

• ISO 5652 (6250 GCR) 2

• ANSI X3.202 (8mm tape) 4

CD-ROM• ISO 9660 3


12 — Media Recording Standards

Encl 8 - 2


DIGEST Part 3 Enclosure 9 toEdition 1.2a USRP Edition 1.3June 1995 August 199710 — Units of Measure

Encl 9 - 1

10 UNITS OF MEASURE CODES

DIGEST defines units of measurement as referenced by ISO 1000 “SI units andrecommendations for the use of their multiples and of certain other units.”However, there are certain units outside the SI (Système internationale), some ofwhich are recognized by International Committee for Weights and Measures(CIPM), which need to be included in DIGEST because of their practicalimportance, i.e. occurrence in DGI datasets. These units have their codesenclosed by parentheses ( ).

When a compound unit is formed by multiplication of two or more units, it can beindicated in one of the following ways:

N · m or N m

DIGEST preference is “N · m” to avoid misinterpretation of the blank space.

When a compound unit is formed by dividing one unit by another, it can beindicated in one of the following ways:

m or m/s or m s-1

s

DIGEST preference is “m/s”.

Table 10-1 lists the SI, and commonly recognized (shown in parentheses), units ofmeasure which are most likely to occur within a DIGEST dataset, and their codes(abbreviations) for the various Units of Measure fields of the Data Set ParameterGroup. They also are referenced in Part 4 — Annex B (Attribute and ValueCodes).


10 — Units of Measure

Encl 9 - 2

Table 10-1 Units of Measure Codes

Unit CodeLENGTH

1. Micrometres UM2. Millimetres MM3. Centimetres CM4. Decimetres DM5. Metres M6. Kilometres KM7. Inches (IN)8. Feet (FT)9. Yards (YD)10. Fathoms (FM)11. Fathoms and Feet (FF)12. Statute Miles (MI)13. Nautical miles (NM)

TIME14. Seconds S15. Minutes MIN16. Hours H17. Days D

SPEED18. Metres per Second M/S19. Kilometres per Hour KM/H20. Miles per Hour (MPH)21. Knots (KNOT)

AREA22. Square metres (M2)23. Square kilometres (KM2)24. Hectares (HA)

ANGULAR MEASUREMENT25. Mils ML26. Seconds (of arc) (SEC)27. Minutes (of arc) (MA)28. Degrees (of arc) (DEG)

DIGEST Part 3 Enclosure 9 toEdition 1.2a USRP Edition 1.3June 1995 August 199710 — Units of Measure

Encl 9 - 3

WEIGHT (MASS)29. Kilograms KG30. Kips (KIP)

PRESSURE31. Millibars MBAR32. Hectopascals HPA

ELECTRICITY33. Volts V34. Kilovolts KV35. Watts W36. Megawatts MW37. Gigawatts GW38. Amperes A39. Hertz HZ40. Kilohertz KHZ41. Megahertz MHZ

MISCELLANEOUS42. Beds (BED)43. Features (FEATURE)44. Lanes/Tracks (LANE/TRACK)45. Levels (LEVEL)46 Lines (LINE)47. Occults (OCCULT)48. Percent (%)49. Persons (PERSON)50. Qualifiers (QUALIFIER)51. Structures (STRUCTURE)52. Vehicles (VEHICLE)

Note: Codes enclosed in parentheses indicate non-ISO 1000 units.The parentheses themselves do not form part of the code.


10 — Units of Measure

Encl 9 - 4


DIGEST Part 2 Enclosure 10 toEdition 1.2a USRP Edition 1.3June 1995 August 1997Annex D — Volume Transmittal Form

Encl 10 - 1

D. DIGITAL GEOGRAPHIC DATA VOLUME TRANSMITTAL FORM

DATA EXCHANGE FORM

Part 1. — National Organizations

1. SENDER: ___________________ 2. ADDRESSEE: _________________________________________ __________________________________________ __________________________________________ __________________________________________ ______________________

3. SECURITY CLASSIFICATION: T S C R U

4. SPECIAL HANDLING:Date & Level of Downgrading:____________________________________________________Bi or Multilateral agreement(s): _______________________________________________________________________________________________________________________________Agreement between Country(s): ______________________________________________________________________________________________________________________________Name / Signature: _____________________________________________________________Creation Date: ________________________________________________________________

Part 2. — Data Exchange Specifications

5.a. EXCHANGE MEDIA:Type: Mag. Tape: ________________ Spec: Density: ________________________

CD-ROM: _________________ 1.4 MB: ________________________3.5" Floppy:________________ 1.2 MB: ________________________5.25" Floppy: 720 K: _________________________

Other: _________________________4 mm: ________________________8 mm: ________________________

Cartridge__________________ Other: _________________________

5.b. FORMATTING / COMPRESSION:Number of Cylinders: ______________________________________________________Number of Sectors: _______________________________________________________Compression: Yes: ___________ No: ________________

Technique Used: __________________________________________________


Annex D — Volume Transmittal Form

Encl 10 - 2

6. EXCHANGE SPECIFICATION:DIGEST Edition:____________ Date: ________________________Annex A ISO 8211: _________________Annex B ISO 8824: _________________Annex C VRF: _____________________Comments:_________________________________________________

7. OPERATING SYSTEM:Unix: ______ System: _____ Version: ______________________PC / MS - DOS Version: ______________________VAX / VMS Version: ______________________Mac O/S Version: ______________________Other: ____________________ Version: ______________________

8. READ / WRITE STATEMENT:_________________________________________Load __________________________________________________________

9. VOLUME CONTENTS:

File File Area of Data Product Remarks Size No. Name Coverage Structure Type

Part 3. - Additional Information

10. REMARKS: ____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

11. ADDITIONAL INFORMATION:______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

THE UTM/UPS STANDARD RASTER PRODUCT SPECIFICATION (USRP) · USRP Edition 1.3 August 1997 v NOTICE TO USERS This international specification for UTM/UPS Standard Raster Product (USRP)

Documents