UTM/UPS Standardized Raster Product (USRP)

UTM/UPS STANDARDIZED RASTERPRODUCT SPECIFICATION

(USRP)DI

GIT

AL

INFORMATI

GEGR

APHIC

O

ON WORKING

GROU

P

BE

CADA FR GE IT NL NO SP UK

US

BIS TRE R UMARSPECULUM OR

Produced and issued under the direction of the Centre Géographique Interarmées,France on behalf of the Digital Geographic Information Working Group.

Edition 1.2 May 1993

THIS PAGE ISINTENTIONALLY

BLANK

USRP Edition 1.2May 1993

i

TABLE OF CONTENTS

PageTable of Contents ....................................................................................................... iList of Annexes ...........................................................................................................iiList of Enclosures ...................................................................................................... iiiList of Figures ............................................................................................................ivRecord of Amendments ..............................................................................................vNotice to Users ..........................................................................................................viForeword................................................................................................................... vii

Authority ......................................................................................................... viiPurpose and Scope........................................................................................ viiApplication...................................................................................................... viiDistribution ..................................................................................................... viiProposed Changes ........................................................................................ viiAmendements ............................................................................................... viiiTechnical Queries ......................................................................................... viiiSecurity ......................................................................................................... viiiCustodian ...................................................................................................... viiiNational Representatives / Points of Contact................................................ viii

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

1.0 Scope ............................................................................................................ 1 - 1

2.0 References ................................................................................................... 2 - 1

3.0 General Information..................................................................................... 3 - 13.1 Description of UTM/UPS Standardized Raster Products .................... 3 - 1

3.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 - 1

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

3.4.1 Horizontal and Vertical Accuracy........................................... 3 - 43.4.2 Color Representation............................................................. 3 - 5

3.5 Source Material ................................................................................... 3 - 63.5.1 Color Bars.............................................................................. 3 - 63.5.2 Insets ..................................................................................... 3 - 6

3.6 Marginalia............................................................................................ 3 - 63.6.1 Legend Images...................................................................... 3 - 63.6.2 Supplementary Text Data ...................................................... 3 - 8

USRP Edition 1.2May 19934.0 Exchange Specification ..............................................................................4 - 1

4.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 - 5

4.4 Documentation Conventions ...............................................................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 Source File ............................................................................5 - 95.2.4 Quality File...........................................................................5 - 195.2.5 Geo Data File ......................................................................5 - 22

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 - 4

6.4 File naming conventions...................................................................... 6 - 4

LIST OF ANNEXES

A ISO 8211 Encapsulation Specifications.

B UTM/UPS Coordinate Transformations.


iii

LIST OF ENCLOSURES

The following Enclosures are extracts from DIGEST (see section 2.0, Reference 1) :

USRPENCLOSURE

DIGEST PART DESCRIPTION

1 4 FACC: Attribute Codes and Associated Values.[Note: Only those FACC codes which are used in this USRPspecification are included (i.e. DAT, NST, VDC). This istherefore an incomplete copy of the DIGEST Annex B]

2 3 Projection Names and Codes.[Note this is a copy of Reference 1 PART 3, Clause 6]

3 3 Grid names and Codes.[Note this is a copy of Reference 1 PART 3, Clause 7]

4 3 Ellipsoid Names and Codes.[Note this is a copy of Reference 1 PART 3, Clause 8]

5 3 Geodetic Datum Names and Codes.[Note this is a copy of Reference 1 PART 3, Clause 9]

6 3 Country Names and Codes.[Note this is a copy of Reference 1 PART 3, Clause 11]

7 3 Media Recording Standards Codes.[Note this is a copy of Reference 1 PART 3, Clause 12]

8 3 Use of CIE Values.[Note this is a copy of Reference 1 PART 3, Clause 13]

9 3 Unit of Measure Codes.[Note this is a copy of Reference 1 PART 3, Clause 10]

10 2 Data Exchange Form.[Note this is a copy of Reference 1 PART 2, Annex D]

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

USRP AMDT 1.2May 1993

LIST OF FIGURES

Figure Page3 - 1 UTM/UPS Zone Tiling Organisation........................................................... 3 - 23 - 4 An example Elevation/Depth (Bathymetric)Tint Diagram............................. 3 - 73 - 5 An example Glossary ................................................................................. 3 - 83 - 6 An example Feature Symbol table............................................................... 3 - 8

4 - 1 Sub Block and Pixel Organization................................................................ 4 - 24 - 2 USRP image tile structure ........................................................................... 4 - 34 - 3 Tile index map example with null tiles.......................................................... 4 - 4

5 - 1 Logical Data Set .......................................................................................... 5 - 15 - 2 A seamless four-map Main Raster Image (MRI)........................................5 - 235 - 3 MRI for source graphics with outsets.........................................................5 - 235 - 4 MRI for source graphics with inset.............................................................5 - 245 - 5 MRI for source graphics on different datums ............................................5 - 24


i

RECORD OF AMENDMENTS

NO DATE ENTERED BY REMARKS


ii

NOTICE TO USERS

This international specification for UTM/UPS Standardized Raster Products(USRP) has been designed to state the content and format of DGIWG’s standardraster product. This specification now forms the baseline from which both systemdevelopers and National Survey organisations can plan their development andproduction 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.


iii

FOREWORD

AUTHORITY

1. This document is issued under the authority of the Digital GeographicInformation Working Group. DGIWG comprises a group of international defencemapping agencies which is charged with encouraging the use of its standards inboth the civil and defence worlds. Current members of DGIWG are Belgium,Canada, Denmark, France, Germany, Italy, Netherlands, Norway, Spain, the UKand 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 providesthe necessary data structure, file organization, format and capture specifications toenable the production of seamless raster data sets, UTM/UPS Standardized RasterProducts, on a common world-wide datum. Other forms of this same basic fileorganization and format have been created to enable the exchange of other types ofMC&G raster data not explicitly 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,captured or displayed onto a plan and allows for the easy computation of ranges,angles and bearings. Annex B deals with those formulae and algorithms, adaptedfor electronic computing, necessary to handle the USRP datums, geographiccoordinates and grid coordinates.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.The formulae and algorithms of Annex B can be usedevery time UTM/UPS coordinates have to be handled concurrently with geographiccoordinates in a Geographic Information System.

DISTRIBUTION

5. 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.

PROPOSED CHANGES

6. 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 toensure understanding and complete evaluation. Comments should be addressed


iv

to the original Point of Contact who will then forward the details to the custodiannation. DGIWG will ensure that all such comments are processed through formalchange control procedures.

AMENDMENTS

7. Amendments to this specification will be the responsibility of the custodian, onbehalf of and in agreement with DGIWG, and will be issued as necessary.

TECHNICAL QUERIES

8. Any queries with regard to the content or application of this specificationshould be 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

NATIONAL REPRESENTATIVES / POINTS OF CONTACT

11. The national representatives are:

Belgium IGNAbbaye de la Cambre 13B 1050 BrusselsBelgium

Canada Director of Geographic OperationsNational Defence HeadquartersMGen G Pearkes BuildingOttawa K1A 0K2Canada

Denmark Chief of Defence Attn: Geographic Officer Army Engineer School

Farum KaserneDK-3520 FarumDenmark


v

France Ministère de la DéfenseEtat-Major des ArméesCentre Géographique InterarméesF-00450 ArméesFrance

Germany AMT FUER MILITAERISCHES GEOWESENFrauenberger Str 250Mercator KaserneW 5350 EuskirchenGermany

Italy IGMI Via C Battisti 1050100 FirenzeItaly

Netherlands Topographic ServicePO Box 1157800 AC EmmenThe Netherlands

Norway Forsvarets KarttjenesteBygn-64AkershusOslo Mil/Akershus0015 Oslo 1Norway

SHAPE Chief Geographic OfficerOperations Division (OME)SHAPEBFPO 26 or APO 09055or 7010 SHAPE, Belgium

Spain Servicio Geografico del EjercitoDario Gazapo Num 828024 MadridSpain

UK Ministry of DefenceMilitary Survey(Geo Commitments Group)Elmwood AvenueFelthamMiddlesex TW13 7AHUnited Kingdom

US HQ Defense Mapping Agency (PRS/A-13)8613 Lee HighwayFairfax, VA 22031-2137USA


vi

ACRONYMS AND ABBREVIATIONS.

ANSI American National Standards Institute

ASCII American National Standard Code for Information Interchange

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

SRG Standard Raster Graphics

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 and mostessential elements of many information system applications both for the Mapping,Charting and Geodesy (MC&G) Community and for other, diverse users. Thisdocument provides the necessary data structure, file organization, format andcapture specifications to enable the exchange of seamless raster data sets,UTM/UPS Standardized Raster Products (USRP), on a common world-wide datum.Other forms of this same basic file organization and format have been created toenable the exchange of other types of MC&G raster data not explicitly for use in aseamless data sets.

USRP Edition 1.2May 1993Section 1 -- Scope

1 - 2


BLANK


Section 2 -- References

2 - 1

2.0 REFERENCES.

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

• Part 1: General Description; Edition 1.1, October 1992,

• Part 2: Theoretical Model, Exchange Structure, and EncapsulationSpecifications; Edition 1.1, October 1992,

• Part 3: Codes, Parameters and Tags; Edition 1.1, October 1992,

• Part 4: Feature and Attribute Coding Catalogue; Edition 1.1, October 1992.

2. DMA Technical Report (DMATR) 8350.2, "DoD World Geodetic System 1984: ItsDefinition and Relationship with Local Geodetic Systems," 2nd Edition;1 September 1991.

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

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

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

6. ISO 1001 - "Information Processing -- File Structure and Labelling of MagneticTapes for Information Interchange Ed.2", 1986.

7. ISO 2022: - "Information Processing -- ISO7 Bit and 8 Bit Coded Character Sets-- Code Extension Techniques Ed. 3", 1986.

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

9. ISO 5652 - "Information processing -- 9 track 12.7 mm (0.5 in.) wide magnetictape for information interchange formats and recording, using group coding 246cpmm (6,250 cpi)".

10. ISO 8211 - "Information processing - Specification for a data descriptive file forinformation interchange", 1985.

11. ISO 9660 - "Information Processing -- Volume and File Structure of CD-ROM forInformation Interchange. Ed. 1", 1988.

12. STANAG 2211- Geodetic Datums, Ellipsoids, Grids and Grid References, Dated15-July-91.

USRP Edition 1.2May 1993Section 2 -- References

2 - 2

13. STANAG 2215- Edition 4 - Evaluation of Land Maps. Dated 19 December, 1983

14. STANAG 3671 Edition Designation System for Land Maps, Aeronautical Chartsand Military Geographic Documentation, Edition 2.

15. STANAG 3716 Map Series Numbering, Edition 1.

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


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 colors present on many graphicproducts, each multicolor graphic is scanned and digitally separated into red,green, and blue components or color-coded layers. The result can be severalimage bands that when combined, provide a multicolor digital replica of the originalgraphic product. The total format of a graphic including margin, border, and legendareas 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. The USRPconsists not only of the transformed graphic data but also a record that containsdatum shift and projection parameters with which users can transform USRP backto the source graphic's datum or projection; a graphic information record thatcontains 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 color-coded images with 100 microns (254 lines perinch) sample size, trimmed at the graphic's neat line and transformed to either theUTM or UPS frame of reference. Data on the UTM/UPS system will be maintainedas a world-wide seamless data base of scanned graphic data on World GeodeticSystem 1984 (WGS 84). UTM/UPS data are divided into zones as defined inSTANAG 2211. Each zone is subdivided into an array of tiles, every UTM zone isisometric to every other UTM zone.

3.2.2 The tiling system is structured such that for each UTM zone, the equator andcentral meridian are always on the edges of whole tiles. In the same manner, foreach UPS zone, the meridians 90°W-90°E and 0°-180° are always on the edges ofwhole tiles (See figure 3 - 1). Transmission of a dataset will always be in multiplesof complete and adjacent tiles. Each tile represents 12.8 mm square (approximately.5 by .5 inch) of a hardcopy graphic image for all scales and geographic locations.Each pixel nominally represents 100 microns square of hardcopy 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. Within each(non-legend image) geo data file, data will be on the same zone reference systemwhich 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.2May 1993Section 3--General Information

3 - 2

NB: Sizes and shapes are exaggerated for illustration purposes.

Figure 3 - 1 UTM/UPS Zone Tiling Organisation



3 - 3

��

��

��

��

��

��

��

��

��

��

��

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

��

��

(Zone N)��

Overlap

Overlap

Overlap

Overlap

GEO DATA FILE 2

(Zone N -1 ) GEO DATA FILE 1��

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

��

A

B

C

D

EF

A

B

C

D

EF

Zone N (including overlaps)

Zone N -1 (including overlap)

Zone N +1 (including overlap)

ZDI (Zone Data Image)

ZDI ZDI

MAIN RASTER IMAGE

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


3 - 4

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 geodetic system.These parameters are derived from Reference 2 The constants for the WGS 84ellipsoid (extracted from Reference 2) are:

a = 6378137.0 meters

b = 6356752.3142 meters

e2 = 0.00669437999013

3.4 ACCURACY REQUIREMENTS.

USRP data will be captured and processed in a way which satisfies the followingaccuracy requirements.

3.4.1 Horizontal accuracy for USRP data may be determined using the methoddetailed in Section 3.4.1.1. Vertical accuracy will remain unchanged from thesource graphic.

3.4.1.1 Coordinates of control points obtained from raw scanned data will notdeviate from the cartometrically derived coordinates of those points on the sourcegraphics by more than 200 microns at scale (this includes only that error introducedby scanning). Example: Locations of points in an USRP at a scale of 1:50,000,(sampled at a nominal 100 micron interval in both X and Y), will differ from thelocations of those points on the source map by no more than 2 x 100 microns x50,000 = 10 meters in both X and Y. The USRP Horizontal Accuracy Value (HAV) isthe square root of the sums of the squares of the source graphic's HorizontalAccuracy Value (AAH) and the error in X and Y (i.e., Xerror and Yerror). Inmathematical notation,

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

In the example given for the 1:50,000 scale map, if the source graphic's HorizontalAccuracy Value (AAH) = 50 meters, the USRP Horizontal Accuracy Value (HAV) =(502 + 102+102)1/2 = 52 meters.

Note: Transformation to UTM/UPS is considered error free.

3.4.1.2 90% of the points per graphic will fulfill the condition required underSection 3.4.1.1 above. Reference 13 gives information on representative pointselection.

3.4.1.3 If exact control point data are not available, the following simplified checkmay be used. The graphic will be scanned. It will then be plotted and the plotscanned again. A computer run of the first scan (from graphic) against the second



3 - 5

scan (from plot) will identify the correctness of the scanning (and plotting)procedure if 99% of the sampled data shows no significant deviation.

3.4.1.4 If the plotting process is excluded from the checking, the graphic will bescanned in two consecutive runs and these compared against each other.

3.4.2 Color representation is in the form of color-code. Each color-code is stored ina color look-up table together with its CIE (x, y, Y) reference (see Enclosure 8) andnominal RGB intensity values. Where a color-code represents a transition colorwhich is a known additive of two or more other coded colors then an equationdefining the mixture will be given in the Quality Record subfield FRM (Annex A 2.4).Where given, the equation will be of the following form :

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

Where P is the proportion

CC is the color-code (i,e label CCD) nand ∑ Pi = 1 i = 1

Example :

If the color that is coded 5 (CC5) is an additive mixture of 0.25 of CC3 and 0.75 ofCC6 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 colors for displaypurposes. For example, if it is necessary to alter the displayed color for colors 3and for 6 then the changes to the related color 5 can be directly computed asfollows:

Where R3, G3, B3 and R6, G6, B6 are the desired signalstrengths/luminosities of the colors 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 above equationsgiving.

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


3 - 6

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

x*YX = ------

y

Y = Y

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

3.5 SOURCE MATERIAL.

3.5.1 Normally, Standardized Raster Graphics (SRG) serve as the source forUSRP. The color bars printed onto each hardcopy multi-color graphic should bescanned if untrimmed litho copies are available. This provides some informationfor conversion of RGB data to color-coded data. If repromat is used, each layer(band) will be assigned a standard color-code which matches the printing color forwhich this repromat stands.

3.5.2 Any internal insets which appear on the source graphic will be described inthe Source Graphic Data File. Providing the information described inSection 5.2.3 will allow user manipulation of the inset separate from the remainderof the zone image.

3.6 MARGINALIA.

3.6.1 Legend Images.

Legend Images, which provide valuable information on the source graphic but areoutside the neat lines, will be provided in separate data files (Section 5.2.3. and5.2.5). Legend images are typically a minimum size to encompass the type ofimages described below. The intention is that legend images are capable of beingdisplayed in less than a display screen full of data, and therefore the image on thesource may be subdivided for display convenience.A legend image has no direct relationship to geographic location.Each legend image is contained in its own file and is related to the source graphicby the LEGEND_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 graphicand its relationship to other graphics in the region.

Figure 3 - 3 An example Index Diagram

(b) Elevation/Depth (Bathymetric)Tint Diagram

The elevation/depth tint diagram is a multi-color graphic depicting the colorsand/or tints used to represent different elevation or depth bands on the printedmap/chart.

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


3 - 8

(c) Glossaries

Glossaries are brief lists of foreign geographical terms appearing on thegraphic with their translated or transliterated equivalents.

Figure 3 - 5 An example Glossary

(d) Feature Symbols

Landmark feature symbols are used to indicate navigationally-prominent entities.

Figure 3 - 6 An example Feature Symbol table

3.6.2 Supplementary Text Data.

Supplementary text appears on many maps and charts, most often to providetextual data associated with special annotations. These may appear in the marginor on the back of the chart and will be provided in a separate record on the USRPvolume (Section 5.2.3). In addition, supplementary text is used to capture itemssuch as convergence tables, extended copyrights, etc.



3 - 9

SUPPLEMENTARY_TEXT_FIELD subfield descriptions.

TRY subfield. This subfield will contain a code identifying the supplementary texttype. The following types have been defined :

Type Description

CONV Convergence table informationCPYZ Extended copyright noticeDATM Datum subregion identifier (the subfield DCD in the

SOURCE _FIELD of the SOURCE_RECORD in the SOURCE_FILE contains the first three characters of the datum code)

MISC MiscellaneousNOTE Textual CHUM notesXXXX Other codes (when mutually agreed upon).

TRI subfield. Used to index several entries of the same type.

TXT subfield. This variable length subfield will contain the actual supplementarytextual information as described above.


3 - 10


BLANK


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 nations andhas 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

By reference to the DGIWG Digital Geographic Information Exchange Standard(DIGEST), this specification identifies and details those criteria that are necessaryto permit the exchange of data in a form that is direct, informative, and above allelse, complete. Some flexibility has been allowed in the areas of data field sizes,color representation, and the ordering of the data to enable full benefit to be gainedin data density and in run length encoding as required. Alternatively, some ruleshave been fixed to insure conformity of product and hence, ease of data receiptand 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.2May 1993Section 4--Exchange Specification

4 - 2

Image Bands

Q

P

{.

��

��

��

��

12

Rows 1 to M

Columns 1 to N

3 2 1

N+ 1

N x M

��

��

��

Pixel (N Bits )

��

SCAN LINE

SUB BLOCK AND PIXEL ORGANIZATION

WITHIN AN IMAGE

Record

N

2N

Figure 4 - 1 Sub Block and Pixel Organization

4.2.3 Zero fill is defined as the color-code zero. Zero fill may be used within a SubBlock at the beginning or end of each line. If the actual number of samples perimage line is not an integer multiple of 128, zero fill will be added to produce thenext integer multiple of 128 samples. Zero fill may be used preceding the first lineor following the last line of actual image data in a Sub Block. If the actual number oflines is not an integer multiple of 128, zero fill will be added to produce the nextinteger multiple of 128 lines. Therefore, zero fill for a zone image may be on any orall 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 the DATA_SET_PARAMETERS_FIELD, SPR.

The subfield values LSO and PSO are image origin coordinates given in the GENERAL_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 is presentin the image file, and for a tile which is present, tells the tiles sequence position orstarting 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 address ofeach tile is the byte number within the image data (SCN field) numbering from one(the first byte). If the image is uncompressed (i.e., not Run Length Encoded) then itis 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 be skipped


4 - 4

to access the tile in column c, row r of the image (See figure 4 - 3). The Tile IndexMap is present only when tiles have been omitted from the image file or optionallythe data is Run Length Encoded. A flag is provided to indicate if the tile map ispresent.-

��

��

��

��

��

��

��

��

��

��

��

��

Tile

��

Tile

��

Tile

��

Tile

��

Tile

��

Tile

��

Tile

��

Tile

��

Tile��(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.Thisannex also 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 separators betweenthem. Each scan line starts on a byte boundary, any remaining bits in the final byteare ignored (i.e., padding with any combinations of 0's and 1's). The implicitelements of the PIX Subfield have the logical form as depicted below, where eachrun of pixels is composed of two elements:

- Pixel count- Pixel value

Pixel Count Value 1 1

Pixel Count Value 2 2

* * * PixelCount Value 'n' 'n'



4 - 5

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 = 1where 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.2 If PCB is set to 0 then there is no count subfield and the value of the count isassumed 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 color coded images separated into bands, each containing onlytwo colors (e.g. black and white, or brown and transparent), then attribute PVB canbe set to 0 (zero) and the scan line reduces to a string of count elements as follows:

Count1

Count2

* * * Count'n'

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


4 - 6

4.4 DOCUMENTATION CONVENTIONS.

4.4.1 FIELD USE

When a field is present, all subfields are mandatory. Where information is notavailable, or not applicable:

- fixed fields will be filled with ASCII spaces, i.e. ISO 646 (2/0),- delimited subfields will be filled with null values.

4.4.2 DECIMAL MARK.

The decimal mark in all numeric representation shall be the FULL STOP ,i.e., ISO646 (2/14).

4.4.3 DIGEST SPECIFIC DATA SYNTAX.

Data items having DIGEST specific syntax, e.g., dates, shall be encoded accordingto the applicable Section, Annex or Appendix to that document - RelevantEnclosures from that document are included 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 thehighest order bit and b1 is the lowest order bit. For binary fields representingscanlines, the bits are to be sequenced highest order to lowest order. Thus whenPCB = 4 and PVB = 0 then bits b8 to b5 will be valued first, followed by bits b4 to b1.Note that when PCB = 4 and PVB = 8, pixel values will span alternate byteboundaries subject to the restrictions in paragraph 4.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, number ofdata sets on the volume (optional), and the volume number will be present in the ISOmedia label, in accordance with the standards described in section 6. The logicalview of these two data subsets is explained below. The THF will be described insection 5.2.1 below. (see Figure 5-1).

HEADER DATA

SUBSET

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 set2. A Source File Occurrence: Once per source (several sources

may occur per data set)3. 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 (a) physical and cultural characteristics of the earth'ssurface (which is called the main raster image); or (b) legend information which iscalled the raster legend image). The Geo Data Subset is composed of the following:

A Geo Data File Occurrence: - Once per UTM zone of theMain Raster Image

- Once per Raster Legend Image

USRP Edition 1.2May 1993Section 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 as shownbelow.

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 DESCRIPTIONRECORD

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 7 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



5 - 3

Date Creation date for this transmittal. (seeEnclosure 1 DAT)

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 Color Coded

Product Type Product type and map series designation(eg,USRP,1501G) This entity is mandatoryunless product type is unknown orunspecified.

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 wil l be-648000.00 seconds (i.e.,-180 degrees).

Latitude of SW Corner of MBR(Minimum Bounding Rectangle)

Southernmost Latitude of the extent of theunpaddedcartographic 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).


5 - 4

SECURITY AND UPDATERECORD

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 (Yes or 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 Edition 1.1)

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

DIGEST Amendment Number Latest DIGEST amendment number.



5 - 5

5.2.2 GENERAL INFORMATION FILE

The GENERAL INFORMATION FILE contains information pertaining to formatting,sequencing and file organization which is helpful for the user and machine reading ofthe file. The file also includes other general information about the actual content ofthe 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 in the Data Set

DATA SET IDENTIFICATION Gives information about the Geo DataSubset identification.

Product Type Product type and map series designation.This entity is mandatory unless product typeis unknown or unspecified.

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)

GENERAL INFORMATION Gives information about the Geo DataSubset content.

Data Structure Structure of Data (4 for Raster ColorCoding)

Data Density E/W Data Interval of a pixel (E-W) ground scalein meters

Data Density N/S Data Interval of a pixel (N-S) ground scalein meters


5 - 6

Data Density Units Unit of measure used for Data Density inE/W and N/S directions. This entity mustbe present if Data Density E/W and N/S arepresent (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).

(Note: The above four values must be a latitude and longitude reference 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 during scanning. (Yes orNo)

Longitude/Easting of Origin Easting of upper left pixel of the paddedZone Data Image

Latitude/Northing of Origin Northing of upper left pixel of the paddedZone Data Image



5 - 7

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

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

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

Row number, upper right corner of the MBRof the unpadded Zone Data Image in pixels.Max. value = (max. number of subblocks *number of pix. per scan line) -1 i.e. (999 *128) -1 =127871.

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

Column number,upper right corner of theMBR of the unpadded Zone Data Image inpixels. Max. value = (max. number ofsubblocks * number of pix. per scan line) -1i.e. (999 * 128) -1 =127871.

Row number of MBR (MinimumBounding Rectangle) S/WCorner

Row number, lower left corner of the MBRof the unpadded Zone Data Image in pixels.Max. value = (max. number of subblocks *number of pix. per scan line) -1 i.e. (999 *128) -1 = 127871.

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

Column number, lower left corner of theMBR of the unpadded Zone Data Image inpixels. Max. value = (max. number ofsubblocks * number of pix. per scan line) -1i.e. (999 * 128) -1 = 127871.

Number of Sub-blocks Vertically(Bottom to Top)

Number of Sub Blocks North to South (M)

Number of Sub-blocksHorizontally (Left to Right)

Number of Sub Blocks West to East (N)

Number of Pixels Left to Right Number of Pixels/Sub-block Line (Q)

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

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 (e.g., for RunLength Encoding)

Pixel Value Length Size of pixel value in bits


5 - 8

Image File Name Image File Name (ISO Media file labelname). See section 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.

BAND IDENTIFICATION Gives information about each individualband in a raster image. The order in whichthe color bands are recorded in this field isthe order they must appear in the Geo DataFile

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

"ON" color code value "ON" color code value- . (see section 4.3.4)

"OFF" color code value "OFF" color code value (see section 4.3.4)

TILE INDEX MAP Contains information regardingSubblocks/tiles (see section 4.2.4.forusage criteria)

Tile Index Values Values of Tile Index Map (a zero or nullvalue corresponds to an omitted sub-block).This entity is required only if the Tile IndexMap Flag = "y"(see Section 4.2.4.)

DATA SET DESCRIPTIONRECORD

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 SOURCE FILE

The SOURCE FILE provides information about source documents* only to which thedata set file refers. A source document is usually a single map or chart from whichthe image or part of an image was derived. If this file is repeated the sources willnormally be from the same map series.

(*Note : The SOURCE FILE repeats once per source document).

The logical entities of the SOURCE FILE are as follows :

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

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

• METRIC SUPPORT RECORD• DATUM CHANGE CONSTANTS (1)

• SOURCE DATUM COEFFICIENTS COUNTER (1)

• SOURCE DATUM LONGITUDE COEFFICIENTS (1)

• SOURCE DATUM LATITUDE COEFFICIENTS (1)

• GRID ROTATION COEFFICIENTS (1)

• SUPPLEMENTARY TEXT RECORD• SUPPLEMENTARY TEXT

(1) These fields are in the METRIC SUPPORT DATA RECORD which givescoefficients and datum change constants which are utilized in the math modelequations of the projections (UTM and UPS) contained in the Annex B.


FILE TITLE Source File.

SOURCE RECORD

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


5 - 10

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(s) usedor referenced to create the data containedin the 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).

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 datecodes (DAT))

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

Perishable Date Perishable information date

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

Cartographic Grid Code Cartographic Grid Code: An identification ofthe cartographic grid(s) used on theproduct(Format nA2). (see Enclosure 3Grid Codes)



5 - 11

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. (SeeEnclosure 9 )

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

Contour Unit of Measurement Contour Unit of Measurement: Identifies theunit of 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.

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

Ellipsoid Name Ellipsoid Name: This component containsthe name of the ellipsoid on which theproduct was produced. (Free Text)

Ellipsoid Code Ellipsoid Code: This Component contains acode of the name of the ellipsoid on whichthe product was produced. (See Enclosure4).

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)

Vertical Reference Code Datum of Vertical Reference Code. (SeeEnclosure 1 VDC).

Sounding Datum Name Sounding Datum Name (See Enclosure 1,VDC)

Sounding Datum Code Sounding Datum Code: Code used torepresent the Sounding Datum. (SeeEnclosure 1, VDC).

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


5 - 12

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

Source Reference Number Library/Source (or history) ReferenceNumber.

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

Units of the elevation value Units of the elevation value

Longitude of Highest Elevation Eastings of the highest known elevation

Latitude of Highest Elevation Northings of the highest known elevation

MAGNETIC RATE Provides information on the magnetic rate ofchange on a given source. The field may berepeated if more than one magnetic rate ofchange applies for a source.

Date (magnetic) Date of magnetic information

Rate of Change Magnetic rate of change

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

G-M Angle Grid north - Magnetic north (G-M) Angle(Grivation)

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

Longitude of the G-M anglereference point

Longitude of the G-M angle reference point

Latitude of the G-M anglereference point

Latitude of the G-M angle reference point

Convergence Angle Grid convergence angle

Unit gca Units of grid convergence angle

BOUNDING POLYGONCOORDINATES

Lists the coordinates of the source polygon.

Eastings coordinate Eastings coordinate

Northings coordinate Northings coordinate



5 - 13

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

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

Projection Code Code of the projection if any. Null ifgeographic coordinates. Must be present ifprojection name is present.Projection mayhave up to 4 parameters, as follows. (SeeEnclosure 2)

Parameter 1 Projection Parameter 1. May be present ifprojection name is present.(See Enclosure 2)




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. (Yes or No)



5 - 14

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.

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

Inset Identification Unique ID for the Inset.Dependent on presence of inset.

Reciprocal cartographic scale ofinset

Reciprocal of cartographic scale of Inset(e.g., 50,000 for 1:50,000).Mandatory if inset is present.

Inset Name Name of Inset.Mandatory if inset is present.(free text)

Image File Name ISO Media file name of the Zone DataImage containing this Inset (See section 6.4for naming conventions)

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.Mandatory if inset is present.

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).Mandatory if inset is present.

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.



5 - 15

The following set of entities is repeated for each legend image related to thissource.

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 legend Image).Free Text: See Section 3.6.1

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

LEGEND PARAMETERS Provides parameters to interpret the LegendImage Data.

Longitude of MBR (MinimumBounding Rectangle) N/E corner

Row number, upper right corner of the MBRin pixels.

Latitude of MBR (MinimumBounding Rectangle) N/E corner

Column number,upper right corner of theMBR in pixels.

Longitude of MBR (MinimumBounding Rectangle) S/Wcorner

Row number, lower left corner of the MBRin pixels.

Latitude of MBR (MinimumBounding Rectangle) S/Wcorner

Column number, lower left corner of theMBR in pixels.

Number of Sub-blocks Vertically(Bottom to Top)

For the legend, number of Sub Blocks Northto South (M)

Number of Sub-blocksHorizontally (Left to Right)

For the legend, number of Sub Blocks Westto East (N)

Number of Pixels Left to Right Number of Pixels/Sub-block Line (Q)

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

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 (e.g., for RunLength Encoding)


5 - 16

Pixel Value Length Size of pixel value in bits (e.g., for RunLength Encoding)

Image File Name Image File Name (ISO Media file labelname). See section 6.4

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

TILE INDEX MAP Contains information regardingSubblocks/tiles (see section 4.2.4. forusage criteria).

Tile Index Value Values of Tile Index Map (a zero or nullvalue corresponds to an omitted sub-block).This entity is required only if the Tile IndexMap Flag = "y"(see Section 4.2.4.)

METRIC SUPPORT RECORD

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.

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).



5 - 17

SOURCE DATUMCOEFFICIENTS COUNTER

Provides the numbers of longitude/latitudecoefficients contained in the SLG/SLT fields.

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 .

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 Eastings shift Normalized Eastings shift


5 - 18

Normalized Northings shift Normalized Northings shift

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

SUPPLEMENTARY TEXTRECORD

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

Text Field Reference ID Supplementary Text Record Type , (seeSection 3.6.2), and Supplementary TextField Reference Identifier

Textual information. Free Text



5 - 19

5.2.4 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

• ACCURACY RECORD• POSITIONAL 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 (Yes or No)


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

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


5 - 20

Creation Date Date of creation of data set.(See Enclosure 1 DAT)

Revision Date Date of revision of data set.(See Enclosure 1 DAT)

Recompilation Count Self explanatory.

Revision Count Self explanatory.

Specification ID Specification ID for USRP (free text)

Date of specification Date of specification. (See Enclosure 1 DAT)

Specification amendment USRP Specification amendment identifier(free text)

Date of earliest source Date of earliest source.(See Enclosure 1 DAT)

Date of latest source Date of latest source.(See Enclosure 1 DAT)

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

Name Name and/or Description for ColorCode(graphic color)(free text)

Color Code Color code assigned in the data set.

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

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

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



5 - 21

Color Intensity (GREENnominal)

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

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

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

Comments Miscellaneous comments - Free text.

ACCURACY RECORD

POSITIONAL ACCURACY Provides information about positionalaccuracy of Geo Data Subset - Repeat asnecessary depending on the number ofsources and 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)

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)

Point to Point HorizontalAccuracy

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)

Point to Point 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)


5 - 22

BOUNDING POLYGONCOORDINATES

Provides the geographic coordinates(northings and eastings) of the polygonwhich delineates the accuracy region of theGeo Data Subset.

Longitude Eastings coordinate

Latitude Northings coordinate

5.2.5 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 so thatthe following PIXEL FIELD can start at the beginning of a physical block on thetransfer media. The field contains sufficient characters including the field terminatorto 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 - 23

NEA

SWA

SW

O

NEO

Map 1 Map 2

Map 3 Map 4

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

��

NEA

SWA

SW

O

NEO

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


5 - 24

��

��

An MRI formed by a map and its inset. The inset is an external inset at the same scale as the main map. The inset is placed at the correct geographic area in the USRP image, and the inset area on the main graphic filled with zero (null) pixels.

NEA

SWA

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

SW

O

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 exchanginginformation between different users and different computing systems. Use of thestandards in the following paragraphs will facilitate the exchange of digital data.

6.2 CHARACTER REPRESENTATION. All information which is represented ascharacters will use the character set and method of encoding defined in FIPS PUB1-1, which adopts ANSI X3.4-1977 (ISO 646 IRU). For names and the Raster GeoData File only, other character sets may be used as defined by ISO 2022. This doesnot exclude formats which incorporate numeric data represented in binary formwhere this has significant advantages.

6.3 FORMS OF MEDIA.

6.3.1 MAGNETIC TAPE.

Magnetic tape volumes containing data interchange files shall conform to ISO 1001,level 3, with one fixed length media record per physical block.

PHYSICAL BLOCK SIZE. The block size for this product is 8,192 (8bit) Bytes. Thecompletion of a block, if necessary, from the end of specified recorded informationshould be by use of (5/E) characters.

RECORD STRUCTURE. Only fixed length records may be used, and these shall beequal to the physical block size or a whole subdivision of it. The ISO 8211 file ofDDR and DR records shall be treated as a continuous string of bytes spanning,without separators or padding, the fixed length records and blocks of the magnetictape. Any unused bytes in the last magnetic tape record of the file shall be filled with5/E characters.

PHYSICAL RECORDING ALTERNATIVES. There are two physical recordingalternatives: 6,250 characters per inch (cpi), group-coded recording (6,250 GCR),and 1,600 cpi, phase encoded (1,600 PE). The preferred density is 6,250 GCR.

- 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).

RECORDED LABELS. Magnetic tapes will have labels recorded as defined in FIPSPUB 79 which 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:

USRP Edition 1.2May 1993Section 6 -- Exchange Media

6 - 2

First Volume Header Label (Vol 1)

Entity Name Definition ISO 1001 Byte Position (BP) and field name

Volume ID ID for this specific volume 5 to 10 -Volumeidentifier

Security Classification Security Classification 11 -Volume Accessibilityof this volume

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

User Volume Label One (UVL1)

Sequence Number Sequential number of 5 to 7 Reserved forthis volume within the implementa-volume set (transmittal) tion use

Transmittal ID Unique ID for the 8 to 37 Reserved fortransmittal (volume set) implementa-to which this volume tion usebelongs

Number of Data Sets Number of Data Sets on, 38 to 40 Reserved foror starting on, this volume implementa-

(may be left blank) tion use

Notes:

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

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 space onthe magnetic tape to ensure that completion of a known number of Data Sets beforethe End of 'Tape Mark'.

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

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



6 - 3

6.3.2 OPTICAL DISK.

CD-ROM INTERCHANGE. CD-ROM volumes shall conform to ISO 9660 and mayuse an 'Extended Attribute Record' in any of the files in which case the 'Recordformat' (BP 79) shall be = 0. The ISO 8211 records shall span the media recordswithout further demarcation. The unused portion of the last block shall be paddedwith characters (5/E). Supplementary labels defined in this standard may be usedby particular implementations as desired, but must only contain data that may beignored by the receiver. The information is defined as follows:

Primary Volume Descriptor

Entity Name Definition ISO 9660 Byte Position(BP) and field name

Volume 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 Use


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


6 - 4

CLASSIFICATION AT THE FILE LEVEL

Where present the classification of a file shall be defined by the first character in thesystem user area at the end of the directory record.


ISO 9660. 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 TypeGENGeneral Information FileSOUSource 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 uniquely identifiedwith NOAMER. If the data set contains more than one source file, the file name willbe the same except that at least one of the characters , "0" or "1", must be changed.


6 - 6


BLANK

Annex A -- ISO 8211 ImplementationTo USRP Edition 1.2

May 1993

A - 1

ANNEX A –– ISO 8211 ENCAPSULATION SPECIFICATIONS

TABLE OF CONTENTS

PageTable of Contents .................................................................................................A - 1

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 - 4

A.2 ISO 8211 Encapsulation..............................................................................A - 6A.2.1 Transmittal Header File....................................................................A - 6A.2.2 General Information File ..................................................................A - 8A.2.3 Source File.....................................................................................A - 10A.2.4 Quality File .................................................................................... A - 15A.2.5 Geo Data File................................................................................ A - 17

Annex A -- ISO 8211 ImplementationTo USRP Edition 1.2May 1993

A - 2

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 explicit statementof the required or permitted subtrees. The third item is specified as the fielddescriptions of the component files. The details of the specification format aregiven in the next section.

A.1 SPECIFICATION OF ISO 8211 EXCHANGE FILE SETS.

An ISO 8211 exchange set is usually a large data structure which must be specifiedin great detail. The following manner of specification is intended to enable aspecification in a concise yet detailed manner.

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 offurther subtrees. The complete specification of an exchange set comprises thefollowing generic 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


May 1993

A - 3

= null means r = 1= R, meaning indefinite repetition

<file type>, <record type> and <field type> level may have an instance of thesame 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 the maximumvalues of the contents of the field. These may be less if optional subfields areomitted.

<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 order of

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>

NOTA BENE: In these representations, the preorder traversal sequence rule is: topdown, right hand branch first. The parent of any subtree is readily apparent and theparent tags for fields must coincide with the field description. The traversal of thetree encounters the repetition factor, perhaps the default of one, of a subtree as thesubtree is entered. Further repetition may be indicated in the field descriptions.


A - 4

Spaces may be introduced into the text for readability and for large exchange setsthe description may be compartmentalized into subtrees for reasons of clarity. Theroot 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 four record types: a control record, tag definition records, subfielddefinition records and interspersed comment records.

Control record:

_00000vL dd00000 np0t_ 0_F_kk

"_" is a skipped byte, usually a SPACE,v is the ISO 8211 interchange level = 1|2|3,dd is "06" for level 2|3 files without character set extension,n is the width of the entry map field length subfield,p is the width of the entry map field position subfield,t is the width of the entry map field tag subfield,kk is the maximum length of the label field <=30.Note: One extra byte is allowed for the Cartesian label delimiters.

Tag definition record (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

Subfield definition (one per subfield):

_nsi_label_dwwwwD_subfield comment

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 structured,e1,e2, in label 1 is a numeric array descriptor** is an in-field numeric array descriptor


May 1993

A - 5

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

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

D is a user subfield delimiter, A1SPACE = default delimiter = (1/15)

comment is a subfield comment string, A35; is used in thedocument draft

Comment records:

Comment records must start with five SPACEs or a "-" and may be locatedanywhere.

Fields are defined at their first occurrence in the data set and are included by tagreference i.e., tag ==) at other locations.Unique values of fields and subfields are specified in { }s, e.g.

{RTY = THF} the RTY subfield must contain the value THF

{RID = 1} the RID subfield must contain the value 1

{NOF = 001-999} the NOF subfield must contain one value in therange 001 through 999 inclusive

{QSS = T |S |C |R |U} the QSS subfield must contain one of the valuesT or S or C or R or U}

Some comments are specified in ( ) e.g.

(LSO = ±m...m) the LSO subfield must contain a positive ornegative value expressed in meters

(SWO = ±SSSSSS.SS) the SWO subfield must contain a positive ornegative value expressed in seconds

(DAT = 007,YYYYMMDD) the DAT subfield must contain the threecharacter code 007 followed by a ',' followed bythe relevant date e.g. '007,19921223


A - 6

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) Record Id {RTY = THF}| |- VDR (8) Transmittal Header| |-R FDR (7) Data Set Description||- Record: SECURITY AND UPDATE|- 001 (2) Record Id {RTY = LCF}|- QSR (4) Security and Release|- QUV (3) Up to Dateness

Field Data Descriptions:

Control == 000002L 0600000 2203 0 F 7 *

*Note: The values shown are minimum and should be modified based upon thedataset sizes. (see section A.1.2, control record)

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

999


May 1993

A - 7

Record: TRANSMITTAL DESCRIPTION

The following record identification field occurs in each record with a differentvalue of the RTY subfield.

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

999

0 VDR 001 ;& TRANSMITTAL_HEADER1 MSD A 3 Media Standard2 VOO A Originator 3 ADR A Addressee4 NOV I 1 Number of Volumes {NOV = 1-9}5 NOF I 3 Number of Data Sets {NOF = 001-999}6 URF A Transmittal ID7 EDN I 3 Edition Number {EDN = 001-999}8 DAT A 12 Creation date (DAT = 007,YYYYMMDD)

999

0 FDR 001 ;& DATA SET DESCRIPTION1 NAM A 6 Data Set ID (NAM = ZZZZZZ)2 STR I 1 Data Structure Code {STR = 4}3 PRT A Product Type (PRT = USRP, Serie )4 SWO R 10.2 Longitude.

of SW Corner of MBR (SWO = ±SSSSSS.SS)5 SWA R 10.2 Latitude

of SW Corner of MBR (SWA = ±SSSSSS.SS)6 NEO R 10.2 Longitude

of NE Corner of MBR (NEO = ±SSSSSS.SS)7 NEA R 10.2 Latitude

of NE Corner of MBR (NEA = ±SSSSSS.SS)999

Record: SECURITY AND UPDATE

001 == {RTY = LCF, RID = 1}

0 QSR 001 ;& SECURITY_AND_RELEASE1 QSS A 1 Highest Security Classification {QSS = T |S |C |R |U}2 QOD A 1 Downgrading instructions {QOD = Y | N}3 DAT A 12 Date of downgrading (DAT = 010,YYYYMMDD)4 QLE A Releasability statement (Free text)

999

0 QUV 001 ;& UP_TO_DATENESS1 SRC A USRP Edition number2 DAT A 12 USRP Edition Date (DAT = 012,YYYYMMDD)3 SPA A USRP Amendment number

999


A - 8

A.2.2 GENERAL_INFORMATION_FILE.


File: GENERAL INFORMATION|-R Record: GENERAL INFORMATION - repeat for each zone of a dataset| |- 001 (2) Record Id {RTY = GIN}| |- DSI (2) Data Set Id| |- GEN (15) General Information| |- SPR (15) Data Set Parameters| |- BDF (*3:O) Band Id| |- TIM (*1) Tile Index Map

||- Record: DATASET DESCRIPTION

|- 001 (2) Record Id {RTY = DSS}|- DRF (4) Dataset Description


control ==

000 == {=GENERAL_INFORMATION_FILE}

Record: GENERAL INFORMATION

001 == {RTY = GIN}

0 DSI 001 ;& DATA_SET_ID1 PRT A Product Type {PRT = USRP,Series}2 NAM A 6 Data Set Name (NAM = ZZZZZZ)

999

0 GEN 001 ;& GENERAL_INFORMATION1 STR I 1 Data Structure {STR = 4}2 LOD R 6 Data Density E/W (LOD = mmmmmm)3 LAD R 6 Data Density N/S (LAD = mmmmmm)4 UNIloa A 3 Data Density Units for LOD and LAD 5 ZNA I 3 Zone Number {ZNA = ±01-61}6 SWO R 10.2 Longitude.

of SW Corner of MBR (SWO = ±SSSSSS.SS)7 SWA R 10.2 Latitude

of SW Corner of MBR (SWA = ±SSSSSS.SS)8 NEO R 10.2 Longitude

of NE Corner of MBR (NEO = ±SSSSSS.SS)9 NEA R 10.2 Latitude

of NE Corner of MBR (NEA = ±SSSSSS.SS)10 SCA I 9 Source graphic scale reciprocal

{SCA = 000000000-999999999}11 PSP R 5.1 Pixel Spacing (in microns) {PSP = 000.0-100.0}12 IMR A 1 Rectified Image {IMR = Y | N}


May 1993

A - 9

13 LSO R 10 Easting of Origin (LSO = ±m...m)14 PSO R 10 Northing of Origin (PSO = ±m...m)15 TXT A Free Text

999

0 SPR 001 ;& DATA_SET_PARAMETERS1 NUL I 6 Row Number; upper right corner of MBR

{NUL = 000000-127871}2 NUS I 6 Column Number; upper right corner of MBR

{NUS = 000000-127871}3 NLL I 6 Row Number; lower left corner of MBR

{NLL = 000000-127871}4 NLS I 6 Column Number; lower left corner of MBR

{NLS = 000000-127871}5 NFL I 3 Number of Sub-blocks (Bottom to Top)

{NFL = 001-999}6 NFC I 3 Number of Sub-blocks (Left to Right)

{NFC = 001-999}7 PNC I 3 Number of Pixels Left to Right {PNC = 128}8 PNL I 3 Number of Pixels Top to Bottom {PNL = 128}9 COD I 1 Column Sequence {COD = 0}10 ROD I 1 Row Sequence {ROD = 1}11 POR I 1 Pixel Order {POR = 0}12 PCB I 1 Pixel Count Length {PCB = 0 |4 |8}13 PVB I 1 Pixel Value Length {PVB = 0 |8}14 BAD A 12 Image File Name (BAD = ZZZZZZDD.IMG)15 TIF A 1 Tile Index Map Flag {TIF = Y |N}

999

0 BDF 001 ;& BAND_ID1 *BID A 5 Band Identification 2 WS1 I 5 "ON" color code value {WS1 = 00000-00255}3 WS2 I 5 "OFF" color code value {WS2 = 00000-00255}

999

0 TIM 001 ;& TILE_INDEX_MAP1 *TSI I 11 Tile Index Map values

{TSI = 00000000000-99999999999}999

Record: DATASET DESCRIPTION

001 == {RTY = DSS, RID = 1}

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

{NSH = 01-99}2 NSV I 2 Number of vertical accuracy sub-regions {NSV = 01-99}3 NOZ I 2 Number of zone image files {NOZ = 01-99}4 NOS I 2 Number of source graphics {NOS = 01-99}

999


A - 10

A.2.3 SOURCE FILE.


File: SOURCE|- Record: SOURCE| |- 001 (2) Record Id {RTY = SOU}| |- SGF (3) Source Summary| |- SOR (28) Source| |- MAG (*9) Magnetic Rate| |- RCI (*2) Bounding Polygon Coordinates| |- PRR (8) Projection| |- QSR (4) Security and Release| |- INS (*19) Inset| |- CPY (1) Copyright||-R Record: LEGEND| |- 001 (2) Record Id {RTY = LEG}| |- LGI (2) Legend| |- SPR (15) Data Set Parameters| |- TIM (*1) Tile Index Map||- Record: METRIC SUPPORT| |-001 (2) Record Id {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||-R Record: SUPPLEMENTARY TEXT

|- 001 (2) Record Id {RTY = SPT}|- SUP (*3) Supplementary Text


control ==000 == {= SOURCE_FILE}

Record: SOURCE

001 == {RTY = SOU, RID = 1}

0 SGF 001 ;& SOURCE_SUMMARY1 NST I 4 Number of supplementary text records

{NST = 0000-9999}2 NLI I 2 Number of legend images {NLI = 00-99}3 NIN I 2 Number of insets {NIN = 00-99}

999


May 1993

A - 11

0 SOR 001 ;& SOURCE1 PRT A 10 Series Designator2 URF A 20 Unique Source Identification3 EDN A 7 Source Edition Number4 NAM A Full Name5 DAT1 A 12 Significant Date (DAT1 = code,YYYYMMDD)6 COU A 2 Country Code7 DAT2 A 12 Perishable Date (DAT2 = 027,YYYYMMDD)8 SCA I 9 Reciprocal Scale {SCA = 000000000-999999999}9 GRD A Cartographic Grid (GRD = GRD1-GRDn)10 SQU I Area Coverage at ground level11 UNIsqu A 3 Unit of measure for area coverage. 12 PCI I 4 Predominant Contour Interval {PCI = 0000-9999}13 UNIpci A 3 Contour Unit of Measurement14 WPC I 3 Water Coverage {WPC = 000-100}15 NST I 3 Navigation System Type 16 ELL A Ellipsoid Name17 ELC A 3 Ellipsoid Code (ELC = nnn)18 DVR A Vertical Reference Name19 VDCdvr A 3 Vertical Reference Code (VDCdvr = nnn)20 SDA A 20 Sounding Datum Name21 VDCsda A 4 Sounding Datum Code22 DAG A Geodetic Datum Name23 DCD A 3 Geodetic Datum Code24 SRN A Source Reference Number25 HKE I 6 Highest Elevation {HKE = 000000-999999}26 UNIhke A 3 Units of the elevation value27 LON R 10 Eastings of Highest Elevation (LON = ±m...m)28 LAT R 10 Northings of Highest Elevation (LAT = ±m...m)

999

0 MAG 001 ;& MAGNETIC-_RATE1 *DAT A 12 Date (magnetic) (DAT = code,YYYYMMDD)2 RAT R 8 Magnetic rate of change3 UNIrat A 3 Units magnetic rate of change4 GMA R 8 G-M Angle5 UNIgma A 3 Units of G-M Angle6 LON R 10.2 Longitude of the G-M angle reference point

(LON = ±SSSSSS.SS)7 LAT R 10.2 Latitude of the G-M angle reference point

(LAT = ±SSSSSS.SS)8 GCA R 8 Grid convergence angle9 UNIgca A 3 Units of grid convergence angle

999

0 RCI 001 ;& BOUNDING_POLYGON_COORDINATES1 *LON R 10 Eastings coordinate (LON = +m...m)2 LAT R 10 Northings coordinate (LAT = +m...m)

999


A - 12

0 PRR 001 ;& PROJECTION1 PRN A Projection Name2 PCO A 2 Projection Code3 PAA R 10.2 Projection Parameter 1. (PAA = ±SSSSSS.SS)4 PAB R 10.2 Projection Parameter 2. (PAB = ±SSSSSS.SS)5 PAC R 10.2 Projection Parameter 3. (PAC = ±SSSSSS.SS)6 PAE R 10.2 Projection Parameter 4. (PAE = ±SSSSSS.SS)7 XOR R 8 X Projection false origin (XOR =+mmmmmmm)8 YOR R 8 Y Projection false origin (YOR =+mmmmmmm)

999

0 QSR 001 ;& SECURITY_AND_RELEASE1 QSS A 1 Security Classification {QSS = T |S |C |R |U}2 QOD A 1 Downgrading {QOD = Y |N}3 DAT A 12 Date of downgrading (DAT = 010,YYYYMMDD)4 QLE A Releasability statement

999

0 INS 001 ;& INSET1 *INT A 2 Inset Identification2 SCA I 9 Reciprocal cartographic scale of inset

{SCA = 000000000-999999999}3 NAM A Inset Name 4 BAD A 12 Image File Name (BAD = ZZZZZZDD.IMG)5 NTL R 10 Absolute Easting of Lower Left Corner

(NTL = +m...m)6 TTL R 10 Absolute Northing of Lower Left Corner

(TTL = +m...m)7 NVL R 10 Absolute Easting of Upper Left Corner

(NVL = +m...m)8 TVL R 10 Absolute Northing of Upper Left Corner

(TVL = +m...m)9 NTR R 10 Absolute Easting of Upper Right Corner

(NTR = +m...m)10 TTR R 10 Absolute Northing of Upper Right Corner

(TTR = +m...m)11 NVR R 10 Absolute Easting of Lower Right Corner

(NVR = +m...m)12 TVR R 10 Absolute Northing of Lower Right Corner

(TVR = +m...m)13 NRL R 10 Relative Easting of Lower Left Corner

(NRL = +m...m)14 TRL R 10 Relative Northing of Lower Left Corner

(TRL = +m...m)15 NSL R 10 Relative Easting of Upper Left Corner

(NSL = +m...m)16 TSL R 10 Relative Northing of Upper Left Corner

(TSL = +m...m)17 NRR R 10 Relative Eastings of Upper Right Corne

(NRR = +m...m)18 TRR R 10 Relative Northing of Upper Right Corner


May 1993

A - 13

(TRR = +m...m)19 NSR R 10 Relative Easting of Lower Right Corner

(NSR = +m...m)20 TSR R 10 Relative Northing of Lower Right Corner

(TSR = +m...m)999

0 CPY 001 ;& COPYRIGHT1 CPZ A Copyright statement

999

Record: LEGEND

001 == {RTY = LEG}

0 LGI 001 ;& LEGEND1 NAM A Legend name2 STR I 1 Data Structure Code {STR = 4}

999

SPR == (see General Information Record) (BAD = ZZZZZZDD.Lcc)TIM == (see General Information Record)

Record: METRIC SUPPORT

001 == {RTY = MSD, RID = 1}

0 DCC 001 ;& DATUM_CHANGE_CONSTANTS1 TOF R 22 Latitude normalizing offset.2 GOF R 22 Longitude normalizing offset.3 NZT R 22 Normalizing factor.4 ELV R 22 Eastern limit of validity.5 WLV R 22 Western limit of validity.6 NLV R 22 Northern limit of validity.7 SLV R 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 indice of the coefficient of MRE b i,j.2 CBJ I 2 j indice of the coefficient of MRE b i,j.3 LGC R 12 Coefficient of MRE b i,j.

999


A - 14

0 SLT 001 ;& SOURCE_DATUM_LATITUDE_COEFFICIENTS1 *CAI I 2 i indice of the coefficient of MRE a i,j.2 CAJ I 2 j indice of the coefficient of MRE a i,j.3 LTC R 12 Coefficient of MRE a i,j.

999

0 GRC 001 ;& GRID_ROTATION_COEFFICIENTS1 NES R 22 Normalized Eastings shift2 NNS R 22 Normalized Northings shift3 AOR R 22 Angle of orientation.

999

Record: SUPPLEMENTARY TEXT

001 == {RTY = SPT, RID = 1}

0 SUP 001 ;& SUPPLEMENTARY_TEXT1 *TRY A 4 Supplementary Text Record Type 2 TRI A 4 Text Field Reference ID {TRI = 0001-9999}3 TXT A Textual information

999


May 1993

A - 15

A.2.4 QUALITY FILE.


File: QUALITY|- Record: QUALITY| |- 001 (2) Record Id {RTY = QAL}| |- QSR (4) Security and Release| |- QUV (10) Up_to_Dateness| |- COL (*9) Color Code Id| |- QOI (1) Other Quality InformationI|-R Record: HORIZONTAL ACCURACY| |- 001 (2) Record Id {RTY = HOR}| |- ASH (4) Horizontal Accuracy| |- RCI (*2) Bounding Polygon Coordinates||-R Record: VERTICAL ACCURACY

|- 001 (2) Record Id {RTY = VER}|- ASV (4) Vertical Accuracy|- RCI (*2) Bounding Polygon Coordinates


control ==000 == {=QUALITY_FILE}

Record: QUALITY

001 == {RTY = QAL, RID = 1}

0 QSR 001 ;& SECURITY_AND_RELEASE1 QSS A 1 Security Classification {QSS = T |S |C |R |U}2 QOD A 1 Downgrading {QOD = Y |N}3 DAT A 12 Date of downgrading (DAT = 010,YYYYMMDD)4 QLE A Releasability Statement (Free text)

999

0 QUV 001 ;& UP_TO_DATENESS1 EDN A 20 Edition Number2 DAT1 A 12 Date of Creation (DAT1 = 007,YYYYMMDD)3 DAT2 A 12 Date of Revision or Update (DAT2 = 024,YYYYMMDD)4 REC I 3 Recompilation Count {REC = 000-999}5 REV I 3 Revision Count {REV = 000-999}6 SRC A Specification ID7 DAT3 A 12 Date of specification (DAT3 = 022,YYYYMMDD)8 SPA A Specification amendment9 DAT4 A 12 Date of earliest source (DAT4 = 020,YYYYMMDD)10 DAT5 A 12 Date of latest source (DAT5 = 021,YYYYMMDD)

999


A - 16

0 COL 001 ;& COLOR_CODE_ID1 *CBD A Name2 CCD I 3 Color Code Assigned in Data Set. {CCD = 000-255}3 CR1 I 6 CIEx (real values scaled by 1000 000)4 CR2 I 6 CIEy (real values scaled by 1000 000)5 CR3 I 6 CIE Reflectivity (Y) (real values scaled by 1000 000)6 FRM A Mathematical Relation to other color-codes (free text). .7 NSR I 3 Color Intensity (RED nominal) {NSR = 000-255}8 NSG I 3 Color Intensity (GREEN nominal) {NSG = 000-255}9 NSB I 3 Color Intensity (BLUE nominal) {NSB = 000-255}

999

0 QOI 001 ;& OTHER_QUALITY_INFORMATION1 OQI A Comments

999

Record: HORIZONTAL ACCURACY

001 == {RTY = HOR}

0 ASH 001 ;& HORIZONTAL_ACCURACY1 AAH I 5 Absolute Horizontal Accuracy {AAH = 00000-99999}2 UNIaah A 3 Unit of measure (meters) {UNIaah = M}3 APH I 5 Relative Horizontal Accuracy {APH = 00000-99999}4 UNIaph A 3 Unit of measure (meters) {UNIaph = M}

999

RCI == (see Source Record)

Record: VERTICAL ACCURACY

001 == {RTY = VER}

0 ASV 001 ;& VERTICAL_ACCURACY1 AAV I 5 Absolute Vertical Accuracy {AAV= 00000-99999}2 UNIaav A 3 Unit of measure (meters) {UNIaav = M}3 APV I 5 Relative Vertical Accuracy {APV = 00000-99999}4 UNIapv A 3 Unit of measure (meters) {UNIapv = M}

999

RCI == (see Source Record)


May 1993

A - 17

A.2.5 GEO DATA FILE.


File: RASTER GEO DATA|-R Record: IMAGE

|- 001 (2) Record Id {RTY = IMG}|- PAD (1) Padding|- SCN (*1) Pixel Field


control ==000 == {=RASTER_GEO_DATA_FILE}

Record: IMAGE

001 == {RTY = IMG}

0 PAD 001 ;& PADDING FIELD1 PAD A Padding Characters to Fill Block (PAD = spaces)

999

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

999


A - 18


BLANK

Annex B -- UTM/UPS Coordinate TansformationTo USRP Edition 1.2

May 1993

B - 1

ANNEX B UTM/UPS COORDINATE TRANSFORMATION.

TABLE OF CONTENTS

Page

Table of Contents. ..........................................................................................B - 1B 1 - UTM-UPS parameters. .........................................................................B - 3

B 1-A - Summary of symbols used ......................................................B - 3B 1 -B - Pixels numbering principle . ....................................................B - 5

B 2 - Easting and Northing (E1 ,N1 ) of the upper-left cornerof a pixel coordinates (c,r) of which are given : .....................................B - 7

B 3 - Coordinates (c,r) of the upper-left corner of thepixel inside which is the image of a point with gridcoordinates (E,N) given..........................................................................B - 9

B 4 - Computation (formula) of £ (isometric latitude) given φ . .....................B - 11B 5 - Algorithm of inversion of £ (Computation of φ given £0 ) .....................B - 11

B 6 - Computation (formula) of β (true distance along ameridian from the Equator) to the latitude φ : given φ (UTM only) .......B - 13

B 7 - Algorithm of inversion of β (Newton-Raphson).Computation of φgiven β0 . (UTM only)...........................................................................B - 15

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

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

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

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

B 12 - Maximum stretch (scale factor). .........................................................B - 25B 13 - Source Datum Geographic coordinates from WGS84

Geographic Coordinates. .....................................................................B - 27B 14 - Map projection data field : To derive source datum UTM grid

coordinates from WGS84 UTM grid coordinates : ...............................B - 31

Annex B -- UTM/UPS Coordinate TansformationTo USRP Edition 1.2May 1993

B - 2


BLANK


May 1993

B - 3

B 1 - UTM-UPS parameters.

B 1-A - 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 point;E1 ,N1 = Easting and Northing of the upper-left corner of a pixel;a = semi-major axis;f = flattening ;e2 = 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.

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


B - 4


BLANK


May 1993

B - 5

B 1 -B - Pixels numbering principle .

The coordinates of the origin are: - in UTM: Easting = E0 (metres) Northing = N0 (metres) - in file : c = 0 r = 0

r

The coordinates of the upper-left corner of the shadowed pixel are: - in UTM / UPS: E1 (metres) N1 (metres) - in image: c = 2 r = 1

��

��

c 0

0

21 3

3

1

2

Origin of the image

UTM / UPS: increasing Eastings (E) rightwards

In image : increasing columns (c) rightwards

��

The side of the pixel has a dimension of: - in image: 100 µm - on the ground: S/10 000 metres (at the scale 1/S)

��

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


B - 6


BLANK


May 1993

B - 7

B 2 - Easting and Northing (E1 ,N1 ) of the upper-left corner of a pixelcoordinates (c,r) of which are given :

Parameters used(c,r) = row and column and row of the image pixel;(E0 ,N0 ) = grid co-ordinates of the (0,0) image pixel;S = reciprocal scale;1/S = scale;S/10 000 = actual side dimension on ground in metres of apixel with 100 µm side at the reciprocal scale S (e.g : 5 mwith a 1/50.000 map)10 000 000 metres = value of the false origin in N specific

to UTM for south case.

ThenE1 ← 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;N.B : The pixel with the upper-left integer coordinates (c,r)!(E1 ,N1 )

coordinates is the representative of all the points with real (floating)coordinates (E,N) located inside this pixel (surjection but no injectionfrom ground to pixel). The best approximation (< E , N >) for all these points will be obtained byadding ½ pixel to c and r respectively i.e. :

< 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 andwhich the minimum bounding rectangle has its southern edge South of Equator.


B - 8


BLANK


May 1993

B - 9

B 3 - Coordinates (c,r) of the upper-left corner of the pixel inside which isthe image of a point with grid coordinates (E,N) given.

Parameters used :(E,N) = grid co-ordinates of the current point;(E0 ,N0 ) = grid co-ordinates of the (0,0) ZDR pixel;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 a

1/50.000 map)Then

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

UTM case : if N and N0 are astride the Equator, then N ← N - 10 000 000;

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


B - 10


BLANK


May 1993

B - 11

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

ALL ANGLES IN RADIANS.

£ = ln [ tan(2

2/πϕ + )*()sin(*1)sin(*1

ϕϕ

ee

+− )e/2 ]

approaches infinity as φ approaches 2/π ;undefined for φ = 2/π .

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 - 12


BLANK


May 1993

B - 13

B 6 - Computation (formula) of β (true distance along a meridian from theEquator) to the latitude φ : given φ (UTM only)

ALL ANGLES IN RADIANSput

y ← sin(2*φ);x ← cos(2*φ);

thenβ←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.


B - 14


BLANK


May 1993

B - 15

B 7 - Algorithm of inversion of β (Newton-Raphson).Computation of φgiven β0 . (UTM only)


Quick convergency for every value of β0 .

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

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

REPEATφ0 ←φ;

φ ←φ-)1(*))(sin*1(

2

2/322

eae

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

(see para B-6 to compute β(φ))UNTIL ABS(φ0 -φ)<ε;IM ←φ;]]


B - 16


BLANK


May 1993

B - 17

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

ALL ANGLES IN RADIANS.N.B.

500 000 metres = value of the false origin in E specific to UTM.10 000 000 metres = value of the false origin in N specific to UTM for

south case.

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

ε ← e2

1-e2 *cos )(2 ϕ ;

R ← )(sin*1 22 ϕe

a−

;

ζ ← (λ - λ0 )*cos(φ);thenE← k0 *R* ζ *( ζ 2 *(A5 * ζ 2 /20+A3 )/6+1)+500 000;

N← k )2/)112/)30/*(*(***)(( 42

622

0 +++ AAµR ζζζϕβ +10 000 000*(1-sign(φ))/2;withA3 = ε – t + 1;A4 = ε * (4 * ε + 9) + 5 - t;A5 = 2 * ε * (7 – 29 * t) + t * (t - 18) + 5;A6 = 30 * ε * (9 – 11 * t) + t * (t - 58) + 61;


B - 18


BLANK


May 1993

B - 19

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


500 000 metres = value of the false origin in E specific to UTM.10 000 000 metres = value of the false origin in N specific to UTM for

south case.

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 )( 02 ϕ ;

R0 ← )(sin*1 0

22 ϕea

−;

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;

1 - North or South case is determined in ZNA subfield ( see GENERAL_INFORMATION_FILE,GENERAL_INFORMATION_RECORD, GEN TAG) with respect to the sign of the UTM zone.


B - 20

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 ;


May 1993

B - 21

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


2 000 000 metres = value of the false origins in E and N specific to UPS.

Put

C ← 2*a

1-e2 *(1-e1+e )

e/2 ; (Constant of the projection);

thenR ← if ABS(φ) = π/2 then R ← 0;

elseR ← k0 *C*exp(-£(φ)); (see para B 4 to compute £)

E ← 2 000 000 + R*sin(λ):N ← 2 000 000 - sign(φ)*R*cos(φ);


B - 22


BLANK


May 1993

B - 23

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


2 000 000 metres = value of the false origins in E and N specific to UPS.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;ELSE

north case

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

south case

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

ENDIF.

R ← x2+y2 ;

φ← ILSD(a,e2 ,ln(R

Ck *0 )) ; north case : φ>0; south case : φ<0;

(see para B 5-A to compute ILSD)


B - 24


BLANK


May 1993

B - 25

B 12 - Maximum stretch (scale factor).

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

UTM (k0 = 0.9996)

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

22

1)(sin*1

ee

−− ϕ ] ;

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 = aRk )(*0 ϕ * )(sin*1 22 ϕe− ; (see para B 10 to compute ”).

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


B - 26


BLANK


May 1993

B - 27

B 13 - Source Datum Geographic coordinates from WGS84 GeographicCoordinates.

CAUTION :- FORMULAE HEREAFTER MUST BE USED DIRECTLY WITH

PARAMETERS AND COEFFICIENTS PROVIDED BY US DEFENSEMAPPING AGENCY- SO ANGLES ARE ASSUMED TO BE IN VARIOUSUNITS.

- USE THESE PARAMETERS AND COEFFICIENTSEXCLUSIVELY INSIDE 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;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 *U

i *Vj ;

Δλ (in seconds) = ∑i=0

i=n ∑

j=0

j=n, (i+j)≤n bi,j *U

i *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 adegree.


B - 28


BLANK


May 1993

B - 29

COEFFICIENTS FROM ED50 TO WGS84(WESTERN EUROPE ONLY)

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

ai,j bi,j

a0,0 -2,65261 b0,0 -4,13447a0,1 0,77921 b0,1 1,94075

0 b0,2 0,300680 b0,5 -1,97974

a0,8 -0,05401 00 b0,9 0,16438

a1,0 2,06392 b1,0 -1,50572a1,1 0,10706 b1,1 1,98425

0 b1,3 -5,487110 b1,4 5,929230 b1,5 -1,79701

a1,9 0,05283 0a2,0 0,26743 b2,0 -1,37600a2,1 -0,95430 0

0 b2,3 -1,613510 b2,4 16,85976

a2,7 -0,10572 b2,7 -2,26917a3,0 0,76407 b3,0 -2,31939

0 b3,3 -6,52522a3,9 0,02445 0a4,0 0,17197 b4,0 -1,70401a4,1 1,04974 0

0 b4,4 4,490960 b4,6 -17,454280 b4,9 0,710410 b5,0 7,41956

a5,2 -0,22899 00 b5,7 8,871410 b6,0 1,577010 b6,1 -14,325160 b7,0 -3,083440 b7,2 7,802150 b8,1 9,987500 b8,3 5,28734

a9,0 -0,78909 00 b9,2 -8,258440 b9,4 -3,48015

ACT 15 BCT 30 All coefficients not above mentioned are equal to zero.


B - 30


BLANK


May 1993

B - 31

B 14 - Map projection data field : To derive source datum UTM gridcoordinates from WGS84 UTM grid coordinates :

Parameters used :E84 = UTM Eastings on WGS84 UTM grid;N84 = UTM Northings on WGS84 UTM grid;Esdc = UTM Eastings on source datum UTM grid;Nsdc = UTM Northings on source datum UTM grid;Θ = angle of rotation from source datum UTM grid to WGS84 UTM

grid;ΔE = normalized Eastings shift ;ΔN = normalized Northings shift;

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


B - 32


BLANK

DIGEST Enclosure 1 toEdition 1.1 USRP Edition 1.2October 1992 May 1993PART 4 - Annex B -- Attributes and Associated Values (PART OF)

Encl 1- 1

PART 4 - Annex B

NOTE. The following is only that subset of DIGEST Edition 1.1 PART 4 Annex Bwhich is applicable to the USRP specification.

Attributes and Associated Values

DAT Date

Date of report or activity.

DAT 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 Date999 Other

Enclosure 1 to DIGESTUSRP Edition 1.2 Edition 1.1May 1993 October 1992PART 4 - Annex B – Attributes and Associated Values (PART OF)

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 LORAN (Long Range Air Navigation)008 OMEGA009 NDB/DME010 RACON (Radar Responder Beacon)011 Radar012 Radio013 R/T (Radio Telephone)014 All DME but excluding ILS/DME015 Television016 Microwave017 NDB (Non-directional beacon)018 EUREKA019 RNG (Radio Range)020 VOR021 VOR/DME022 VORTAC023 TACAN024 ILS025 Multiple Radio Facilities026 LOC (Localizer)027 Broadcast Stations028 SDF (Simplified Directional Facility)029 LDA (Landing Distance Available)030 MLS (Microwave Landing System)031 Fan Marker032 Bone Marker033 Radio Telegraph034 GCA (Ground Control Approach)035 Radar Antenna036 A/Bn (Aerodrome Beacon)037 PAR038 Aeronautical Radio039 I/Bn (Identification Beacon)040 Radio Beacon041 Rotating Loop Radio Beacon042 VFR Test Signal Marker

DIGEST Enclosure 1 toEdition 1.1 USRP Edition 1.2October 1992 May 1993PART 4 - Annex B -- Attributes and Associated Values (PART OF)

Encl 1- 3

043 Marine NDB's044 Aeronautical Radio Range045 Radar Station046 Hifix047 Hyperfix048 Tricolor Panel049 LOC/DME050 Ocean Weather Ship (OWS)999 Other

VDC Vertical Datum Category

The reference line (0 elevation) from which heights and depths are measured.

VDC 000 Unknown001 VALUE INTENTIONALLY LEFT BLANK002 High Water003 Higher High Water004 Indian Spring Low Water005 Low Water006 Lower Low Water007 Mean High Water008 Mean High Water Neaps009 Mean High Water Springs010 Mean Higher High Water011 Mean Low Water012 Mean Low Water Neaps013 Mean Low Water Springs014 Mean Lower Low Water015 Mean Sea Level016 Mean Tide Level017 Neap Tide018 Spring Tide019 Mean Lower Low Water Springs020 Lowest Astronomical Tide021 Chart Datum (Unspecified)022 Highest Astronomical Tide999 Other

Enclosure 1 to DIGESTUSRP Edition 1.2 Edition 1.1May 1993 October 1992PART 4 - Annex B – Attributes and Associated Values (PART OF)

Encl 1- 4


BLANK

DIGEST Enclosure 2 toEdition 1.1 USRP Edition 1.2October 1992 May 1993PART 3 - 6 – Projection Codes

Encl 2- 1

PART 3 - 6 PROJECTION CODES AND PARAMETERS

Table 6-1 defines the allowable codes and parameters for the Dataset MapProjection Group. The projection code and parameters are necessary forconversion of digitized map coordinates to geographic coordinates. All longitudesand latitudes are expressed as seconds of arc (±SSSSSS.SS).

Table 6-1 Projection Codes and Parameters

NAME CODE PARAMETERS1 2 3 4

Albers EqualArea

AC CentralMeridian

Std. ParallelNearest toEquator

Farthest fromEquator

Std. Parallel-

Azimuthal EqualArea

AK Longitude ofTangency

Latitude ofTangency

- -

Azimuthal EqualDistant

AL Longitude ofTangency

Latitude ofTangency

- -

Gnomonic GN Longitude ofTangency

Latitude ofTangency

- -

Hotine ObliqueMercator

RB Longitude ofGreat Circle

Latitude ofGreat Circle

Azimuth ofGreat Circle

-

Lambert ParallelConformal conic

LE CentralMeridian

Std. ParallelNearest toEquator

Farthest fromEquator

Std. Parallel-

Lambert EqualArea

LJ CentralMeridian

- - -

Mercator MC CentralMeridian

Latitude ofTrue Scale

- -

Oblique Mercator OC Longitude ofGreat Circle

Latitude ofGreat Circle

Azimuth ofGreat Circle

-

Orthographic OD Longitude ofTangency

Latitude ofTangency

- -

Polar Stereo-graphic

PG CentralMeridian

Latitude ofTrue Scale

- -

Polyconic PH CentralMeridian

- - -

TransverseMercator

TC CentralMeridian

*Meridian ofTrue North

- -

ObliqueStereographic

* *CentralMeridian

* * *

RelativeCoordinates

RC X-ScaleFactor

Y-ScaleFactor

*To Be Resolved

Enclosure 2 to DIGESTUSRP Edition 1.2 Edition 1.1May 1993 October 1992

PART 3 - 6 – Projection Codes

Encl 2- 2


BLANK

DIGEST Enclosure 3 toEdition 1.1 USRP Edition 1.2October 1992 May 1993PART 3-7 -- Grid Codes

Encl 3 - 1

PART 3 - 7 GRID CODES

Table 7-1 provides the grids which may be used, and their code (abbreviations) inthe Grid System field:

Note: This list is not all-inclusive.

Table 7-1 Grid Codes

Grid Code1. National Grid of Great Britain ND2. Irish Transverse Mercator Grid IK3. French Lambert Grid FL4. India Zone IN5. Ceylon Belt (Transverse Mercator) CE6. Madagascar Grid (Laborde) MO7. Orthomorphic Grid MG8. Netherlands East Indies Equatorial

Zone British Metric Grid (Lambert)NM

9. New Zealand Belt NZ10. Universal Transverse Mercator UT11. Gauss-Kruger Grid (Transverse

Mercator)GK

12. Gauss-Boaga Grid (TransverseMercator)

GB


PART 3-7 -- Grid Codes

Encl 3 - 2


BLANK

DIGEST Enclosure 4 toEdition 1.1 USRP Edition 1.2October 1992 May 1993PART 3-8 -- Ellipsoid Codes

Encl 4 - 1

PART 3 - 8 ELLIPSOID CODES

Table 8-1 lists the ellipsoids which may be used, and their codes (abbreviations) inthe Ellipsoid field.

Table 8-1 Ellipsoid Codes

Ellipsoid Code1. Airy AAY2. Australian National AUN3. Bessel BES4. Clarke 1866 CLK5. Clarke 1880 CLJ6. Everest EVE7. Fisher FIS8. Geodetic Reference System 1980 GRS9. International INT10. Modified Airy AAM11. Modified Everest EVM12. Walbeck WAL13. World Geodetic System 1960 WGA14. World Geodetic System 1966 WGB15. World Geodetic System 1972 WGC16. World Geodetic System 1984 WGE17. Clark 1858 CLE18. Krasovsky KRA


PART 3-8 -- Ellipsoid Codes

Encl 4 - 2


BLANK

DIGEST Enclosure 5 toEdition 1.1 USRP Edition 1.2October 1992 May 1993PART 3-9 -- Datum Codes

Encl 5 - 1

PART 3 - 9 DATUM CODES

Table 9-1 lists the datums which may be used, and the codes (abbreviations) whichmay appear in the Geodetic Datum fields. Sounding Datum and the VerticalReference System field usage are covered in the Feature and Attribute CodingCatalogue (Part 4).

Note: This list is not all-inclusive.

Table 9-1 Datum Codes

Geodetic Datums Code1. Adindan ADI2. Arc 1950 ARF3. Australian Geodetic AUA4. Bukit Rimpah BUR5. Camp Area Astro. CAZ6. Campo Inchauspe CAI7. Chua Astro CHU8. Corrego Alegre COA9. Djakarta BAT10. European 50 EUR11. G. Segara GSE12. G. Serindung GSF13. Geodetic 1949 GEO14. Ghana GHA15. Guam 1963 GUA16. Herat North HEN17. Hjorsey HJO18. Hu-tzu-shan HTN19. Indian IND20. Ireland 1965 IRE21. Kertau KEA22. Liberia 1964 LIB23. Local Astro. LOC24. Luzon LUZ


PART 3-9 -- Datum Codes

Encl 5 - 2

25. Merchich MER26. Montjong Lowe MOL27. Nigeria NIG28. North American 1927 NAS29. North American 1983 NAX30. Old Hawaiian OHA31. Ordnance Survey of Great Britain OGB32. Provisional South American 1956 PRP33. Qornoq QUO34. Sierra Leone 1960 SIB35. Tananarive Obsv. 1925 TAN36. Timbalai TIL37. Tokyo TOK38. Voirol VOI39. World Geodetic System 1960 WGA40. World Geodetic System 1966 WGB41. World Geodetic System 1972 WGC42. World Geodetic System 1984 WGE43. Yacare YAC44. Hermannskogel HER45. European 79 ENB46. German GDA47. Italian IDA

DIGEST Enclosure 6 toEdition 1.1 USRP Edition 1.2October 1992 May 1993PART 3-11 -- Country Codes

Encl 6 - 1

PART 3 - 11 COUNTRY CODES

Use US FIPS PUB 10-3 for country codes.


PART 3-11 -- Country Codes

Encl 6 - 2


BLANK

DIGEST Enclosure 7 toEdition 1.1 USRP Edition 1.2October 1992 May 1993PART 3-7 -- : Media Recording Standards

Encl 7 - 1

PART 3-12 -- Media Recording Standards, Codes

Media Recording Standard Code

Magnetic Tape

ISO 3788 (1600 PE) 001

ISO 5652 (6250 GCR) 002

CD-ROMISO 9660 003


PART 3-12 -- : Media Recording Standards

Encl 7 - 2


BLANK

DIGEST Enclosure 8 toEdition 1.1 USRP Edition 1.2October 1992 May 1993PART 3-13 -- Use of CIE Values

Encl 8 - 1

PART 3 - 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 Tristimulous 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 cromacity chart (see Figure 13-1). Thisis also the method used in the DoD Standard Printing Color Catalog (Reference27). Of the other two systems, the CIELUV system is more applicable to the TVindustry, and the CIELAB system, while providing finer discrimination betweensimilar colours, is unnecessarily complex for the requirements of raster images. Itis only necessary to uniquely identify what a colour should be; any difference inhue 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 is Reference27, which as well as printing sample colours also gives the CIE Values for thatcolour. Where the standard colour catalogue referenced by a map specificationdoes not give the CIE Values, then these may be obtained by:

• identifying the CIE Values for the catalogue in accordance withReference 28 which defines the standard white to be used and themethod to be adopted; or

• identifying the closest approximation to each colour in Reference 27 andassigning those CIE Values to the local standard colour catalogue. Thismethod should only be used where the precise definition of a colour isnot critical (i.e. the map series is only produced and/or scanned by oneagency).

Defining what a map colour should be according to a recognized standard willensure that:

• the colour can be readily identified by the receiving agency or user;

• precise consistency of colour can be achieved between samples of thesame raster product produced not only by the same agency, but bydifferent agencies; and

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


PART 3-13 -- Use of CIE Values

Encl 8 - 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

co-efficients of x

co-e

ffici

ents

of y

600

700

400

550

500

450

CIE CROMACITY CHART

WHITE

Nonspectral

colours

Figure 13-1 CIE Cromacity Chart

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 Enclosure 9 toEdition 1.1 USRP Edition 1.2October 1992 May 1993PART 3-10 -- Units of Measure

Encl 9 - 1

PART 3 - 10 UNITS OF MEASURE CODES

Table 10-1 lists the allowable units of measure which can be used, and their codes(abbreviations) in the various Units of Measure fields.

Table 10-1 Units of Measure Codes

Unit Code1. Centimetres CM2. Decimetres DM3. Degrees of Arc DEG4. Fathoms FM5. Feet FT6. Fathoms and Feet FF7. Inches IN8. Kilometres KM9. Metres M10. Micrometres UM11. Millimetres MM12. Mils ML13. Minutes of Arc MA14. Nautical Miles NM15. Seconds of Arc SEC16. Statute Miles MI17. Yards YD


PART 3-10 -- Units of Measure

Encl 9 - 2

THIS PAGEINTENTIONALLY

BLANK

DIGEST Enclosure 10 toEdition 1.1 USRP Edition 1.2October 1992 May 1993PART 2-Annex D -- Volume Transmittal Form

Encl 10 - 1

PART 2 - Annex D. DIGITAL GEOGRAPHIC DATA VOLUME TRANSMITTALFORM

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: __________________________________________________


PART 2-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: _________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Documents

UTM/UPS Standardized Raster Product (USRP)