1
|
GTOPO30 Documentation
|
2
|
|
3
|
Table of Contents:
|
4
|
|
5
|
1.0 Introduction
|
6
|
2.0 Data Set Characteristics
|
7
|
3.0 Data Format
|
8
|
3.1 DEM File
|
9
|
3.2 Header File
|
10
|
3.3 World File
|
11
|
3.4 Statistics File
|
12
|
3.5 Projection File
|
13
|
3.6 Shaded Relief Image
|
14
|
3.7 Source Map
|
15
|
3.8 Source Map Header File
|
16
|
4.0 Data Distribution
|
17
|
4.1 Procedures for Obtaining Data
|
18
|
4.2 File Sizes
|
19
|
5.0 Notes and Hints for GTOPO30 Users
|
20
|
6.0 Data Set Development
|
21
|
6.1 Data Sources
|
22
|
6.1.1 Digital Terrain Elevation Data
|
23
|
6.1.2 Digital Chart of the World
|
24
|
6.1.3 USGS Digital Elevation Models
|
25
|
6.1.4 Army Map Service Maps
|
26
|
6.1.5 International Map of the World
|
27
|
6.1.6 Peru Map
|
28
|
6.1.7 New Zealand DEM
|
29
|
6.1.8 Antarctic Digital Database
|
30
|
6.2 Data Processing
|
31
|
6.2.1 Raster Source Processing
|
32
|
6.2.2 Vector Source Processing
|
33
|
6.2.3 DEM Merging
|
34
|
6.2.4 Global Product Assembly
|
35
|
7.0 Accuracy
|
36
|
8.0 GTOPO30 Caveats
|
37
|
8.1 Grid Spacing and Resolution
|
38
|
8.2 Topographic Detail and Accuracy
|
39
|
8.3 Production Artifacts
|
40
|
9.0 Summary
|
41
|
10.0 References
|
42
|
11.0 Disclaimers
|
43
|
|
44
|
|
45
|
1.0 Introduction
|
46
|
|
47
|
GTOPO30 is a global digital elevation model (DEM) resulting from a
|
48
|
collaborative effort led by the staff at the U.S. Geological Survey's
|
49
|
EROS Data Center in Sioux Falls, South Dakota. Elevations in GTOPO30 are
|
50
|
regularly spaced at 30-arc seconds (approximately 1 kilometer). GTOPO30
|
51
|
was developed to meet the needs of the geospatial data user community for
|
52
|
regional and continental scale topographic data. This release represents
|
53
|
the completion of global coverage of 30-arc second elevation data that
|
54
|
have been available from the EROS Data Center beginning in 1993. Several
|
55
|
areas have been updated and the entire global data set has been repackaged,
|
56
|
so these data supersede the previously released continental data sets.
|
57
|
Comments from users of GTOPO30 are welcomed and encouraged. Please send
|
58
|
your comments to Dean Gesch at gesch@edcmail.cr.usgs.gov or to Sue Greenlee
|
59
|
at sgreenlee@edcmail.cr.usgs.gov.
|
60
|
|
61
|
2.0 Data Set Characteristics
|
62
|
|
63
|
GTOPO30 is a global data set covering the full extent of latitude from 90
|
64
|
degrees south to 90 degrees north, and the full extent of longitude from
|
65
|
180 degrees west to 180 degrees east. The horizontal grid spacing is
|
66
|
30-arc seconds (0.008333333333333 degrees), resulting in a DEM having
|
67
|
dimensions of 21,600 rows and 43,200 columns. The horizontal coordinate
|
68
|
system is decimal degrees of latitude and longitude referenced to WGS84.
|
69
|
The vertical units represent elevation in meters above mean sea level.
|
70
|
The elevation values range from -407 to 8,752 meters. In the DEM, ocean
|
71
|
areas have been masked as "no data" and have been assigned a value of -9999.
|
72
|
Lowland coastal areas have an elevation of at least 1 meter, so in the
|
73
|
event that a user reassigns the ocean value from -9999 to 0 the land
|
74
|
boundary portrayal will be maintained. Due to the nature of the raster
|
75
|
structure of the DEM, small islands in the ocean less than approximately
|
76
|
1 square kilometer will not be represented.
|
77
|
|
78
|
3.0 Data Format
|
79
|
|
80
|
To facilitate electronic distribution, GTOPO30 has been divided into 33
|
81
|
smaller pieces, or tiles. The area from 60 degrees south latitude to
|
82
|
90 degrees north latitude and from 180 degrees west longitude to 180
|
83
|
degrees east longitude is covered by 27 tiles, with each tile covering 50
|
84
|
degrees of latitude and 40 degrees of longitude. Antarctica (90 degrees
|
85
|
south latitude to 60 degrees south latitude and 180 degrees west longitude
|
86
|
to 180 degrees east longitude) is covered by 6 tiles, with each tile covering
|
87
|
30 degrees of latitude and 60 degrees of longitude. The tiles names refer
|
88
|
to the longitude and latitude of the upper-left (northwest) corner of the
|
89
|
tile. For example, the coordinates of the upper-left corner of tile
|
90
|
E020N40 are 20 degrees east longitude and 40 degrees north latitude.
|
91
|
There is one additional tile that covers all of Antarctica with data in
|
92
|
a polar stereographic projection. The following table lists the name,
|
93
|
latitude and longitude extent, and elevation statistics for each tile.
|
94
|
|
95
|
Latitude Longitude Elevation
|
96
|
Tile Minimum Maximum Minimum Maximum Minimum Maximum Mean Std.Dev.
|
97
|
------- ---------------- ---------------- --------------------------------
|
98
|
|
99
|
W180N90 40 90 -180 -140 1 6098 448 482
|
100
|
W140N90 40 90 -140 -100 1 4635 730 596
|
101
|
W100N90 40 90 -100 -60 1 2416 333 280
|
102
|
W060N90 40 90 -60 -20 1 3940 1624 933
|
103
|
W020N90 40 90 -20 20 -30 4536 399 425
|
104
|
E020N90 40 90 20 60 -137 5483 213 312
|
105
|
E060N90 40 90 60 100 -152 7169 509 698
|
106
|
E100N90 40 90 100 140 1 3877 597 455
|
107
|
E140N90 40 90 140 180 1 4588 414 401
|
108
|
W180N40 -10 40 -180 -140 1 4148 827 862
|
109
|
W140N40 -10 40 -140 -100 -79 4328 1321 744
|
110
|
W100N40 -10 40 -100 -60 1 6710 375 610
|
111
|
W060N40 -10 40 -60 -20 1 2843 212 168
|
112
|
W020N40 -10 40 -20 20 -103 4059 445 298
|
113
|
E020N40 -10 40 20 60 -407 5825 727 561
|
114
|
E060N40 -10 40 60 100 1 8752 1804 1892
|
115
|
E100N40 -10 40 100 140 -40 7213 692 910
|
116
|
E140N40 -10 40 140 180 1 4628 549 715
|
117
|
W180S10 -60 -10 -180 -140 1 2732 188 297
|
118
|
W140S10 -60 -10 -140 -100 1 910 65 124
|
119
|
W100S10 -60 -10 -100 -60 1 6795 1076 1356
|
120
|
W060S10 -60 -10 -60 -20 1 2863 412 292
|
121
|
W020S10 -60 -10 -20 20 1 2590 1085 403
|
122
|
E020S10 -60 -10 20 60 1 3484 893 450
|
123
|
E060S10 -60 -10 60 100 1 2687 246 303
|
124
|
E100S10 -60 -10 100 140 1 1499 313 182
|
125
|
E140S10 -60 -10 140 180 1 3405 282 252
|
126
|
W180S60 -90 -60 -180 -120 1 4009 1616 1043
|
127
|
W120S60 -90 -60 -120 -60 1 4743 1616 774
|
128
|
W060S60 -90 -60 -60 0 1 2916 1866 732
|
129
|
W000S60 -90 -60 0 60 1 3839 2867 689
|
130
|
E060S60 -90 -60 60 120 1 4039 2951 781
|
131
|
E120S60 -90 -60 120 180 1 4363 2450 665
|
132
|
ANTARCPS -90 -60 -180 180 1 4748 2198 1016
|
133
|
|
134
|
The 27 tiles that individually cover 50 degrees of latitude and 40 degrees
|
135
|
of longitude each have 6,000 rows and 4,800 columns. The 6 Antarctica tiles
|
136
|
that individually cover 30 degrees of latitude and 60 degrees of longitude
|
137
|
each have 3,600 rows and 7,200 columns. There is no overlap among the tiles
|
138
|
so the global data set may be assembled by simply abutting the adjacent
|
139
|
tiles.
|
140
|
|
141
|
The tile named ANTARCPS includes the same data as the 6 geographic tiles
|
142
|
covering Antarctica, but is presented in a polar stereographic projection.
|
143
|
The horizontal grid spacing is 1,000 meters, and the tile has 5,400 rows
|
144
|
and 5,400 columns. The projection parameters used for the polar
|
145
|
stereographic projection are: 0 degrees for the longitude of the central
|
146
|
meridian, 71 degrees south for the latitude of true scale, and 0 for the
|
147
|
false easting and false northing.
|
148
|
|
149
|
Data for each tile are provided in a set of 8 files. The files are named
|
150
|
with the tile name and a file name extension indicating the contents of the
|
151
|
file. The following extensions are used:
|
152
|
|
153
|
Extension Contents
|
154
|
--------- --------
|
155
|
|
156
|
DEM digital elevation model data
|
157
|
HDR header file for DEM
|
158
|
DMW world file
|
159
|
STX statistics file
|
160
|
PRJ projection information file
|
161
|
GIF shaded relief image
|
162
|
SRC source map
|
163
|
SCH header file for source map
|
164
|
|
165
|
The simple format should allow for easy ingest into most popular image
|
166
|
processing and geographic information systems packages. Further information
|
167
|
on the contents of the files is provided below.
|
168
|
|
169
|
3.1 DEM File (.DEM)
|
170
|
|
171
|
The DEM is provided as 16-bit signed integer data in a simple binary raster.
|
172
|
There are no header or trailer bytes imbedded in the image. The data are
|
173
|
stored in row major order (all the data for row 1, followed by all the data
|
174
|
for row 2, etc.).
|
175
|
|
176
|
3.2 Header File (.HDR)
|
177
|
|
178
|
The DEM header file is an ASCII text file containing size and coordinate
|
179
|
information for the DEM. The following keywords are used in the header file:
|
180
|
|
181
|
BYTEORDER byte order in which image pixel values are stored
|
182
|
M = Motorola byte order (most significant byte first)
|
183
|
LAYOUT organization of the bands in the file
|
184
|
BIL = band interleaved by line (note: the DEM is a single
|
185
|
band image)
|
186
|
NROWS number of rows in the image
|
187
|
NCOLS number of columns in the image
|
188
|
NBANDS number of spectral bands in the image (1 for a DEM)
|
189
|
NBITS number of bits per pixel (16 for a DEM)
|
190
|
BANDROWBYTES number of bytes per band per row (twice the number of columns
|
191
|
for a 16-bit DEM)
|
192
|
TOTALROWBYTES total number of bytes of data per row (twice the number of
|
193
|
columns for a single band 16-bit DEM)
|
194
|
BANDGAPBYTES the number of bytes between bands in a BSQ format image
|
195
|
(0 for a DEM)
|
196
|
NODATA value used for masking purposes
|
197
|
ULXMAP longitude of the center of the upper-left pixel (decimal degrees)
|
198
|
ULYMAP latitude of the center of the upper-left pixel (decimal degrees)
|
199
|
XDIM x dimension of a pixel in geographic units (decimal degrees)
|
200
|
YDIM y dimension of a pixel in geographic units (decimal degrees)
|
201
|
|
202
|
Example header file (W100N40.HDR):
|
203
|
|
204
|
BYTEORDER M
|
205
|
LAYOUT BIL
|
206
|
NROWS 6000
|
207
|
NCOLS 4800
|
208
|
NBANDS 1
|
209
|
NBITS 16
|
210
|
BANDROWBYTES 9600
|
211
|
TOTALROWBYTES 9600
|
212
|
BANDGAPBYTES 0
|
213
|
NODATA -9999
|
214
|
ULXMAP -99.99583333333334
|
215
|
ULYMAP 39.99583333333333
|
216
|
XDIM 0.00833333333333
|
217
|
YDIM 0.00833333333333
|
218
|
|
219
|
3.3 World File (.DMW)
|
220
|
|
221
|
The world file is an ASCII text file containing coordinate information. It
|
222
|
is used by some packages for georeferencing of image data. The following is
|
223
|
an example world file (W100N40.DMW) with a description of each record:
|
224
|
|
225
|
0.00833333333333 x dimension of a pixel (decimal degrees)
|
226
|
0.00000000000000 rotation term (will always be zero)
|
227
|
0.00000000000000 rotation term (will always be zero)
|
228
|
-0.00833333333333 negative y dimension of a pixel (decimal degrees)
|
229
|
-99.99583333333334 longitude of the center of the upper-left pixel
|
230
|
39.99583333333333 latitude of the center of the upper-left pixel
|
231
|
|
232
|
3.4 Statistics File (.STX)
|
233
|
|
234
|
The statistics file is an ASCII text file which lists the band number,
|
235
|
minimum value, maximum value, mean value, and standard deviation of the
|
236
|
values in the DEM data file.
|
237
|
|
238
|
Example statistics file (W100N40.STX):
|
239
|
|
240
|
1 -9999 6710 -6078.8 5044.2
|
241
|
|
242
|
3.5 Projection File (.PRJ)
|
243
|
|
244
|
The projection information file is an ASCII text file which describes the
|
245
|
projection of the DEM and source map image.
|
246
|
|
247
|
Example projection file (W100N40.PRJ):
|
248
|
|
249
|
Projection GEOGRAPHIC
|
250
|
Datum WGS84
|
251
|
Zunits METERS
|
252
|
Units DD
|
253
|
Spheroid WGS84
|
254
|
Xshift 0.0000000000
|
255
|
Yshift 0.0000000000
|
256
|
Parameters
|
257
|
|
258
|
3.6 Shaded Relief Image (.GIF)
|
259
|
|
260
|
A shaded relief image is provided as an overview of the data in each tile.
|
261
|
The images were derived from a generalized version of GTOPO30 with a
|
262
|
horizontal grid spacing of 240-arc seconds (approximately 8 kilometers), so
|
263
|
many small islands and features will not be visible. The images are meant
|
264
|
to provide a convenient way for users to view the general topographic
|
265
|
features portrayed in each tile. The shaded relief images are provided as
|
266
|
GIF images which can be displayed by many popular image display programs and
|
267
|
World Wide Web browsers. An image size of 750 rows by 600 columns is used
|
268
|
for the tiles covering 50 degrees of latitude by 40 degrees of longitude.
|
269
|
An image size of 450 rows by 900 columns is used for the Antarctica tiles
|
270
|
which cover 30 degrees of latitude by 60 degrees of longitude each. The
|
271
|
Antarctica polar stereographic tile is portrayed by a shaded relief image
|
272
|
having 675 rows by 675 columns.
|
273
|
|
274
|
3.7 Source Map (.SRC)
|
275
|
|
276
|
The source map is a simple 8-bit binary image which has values that indicate
|
277
|
the source used to derive the elevation for every cell in the DEM. The
|
278
|
source map is the same resolution and has the same dimensions and coordinate
|
279
|
system as the DEM. Like the DEM, it has no header or trailer bytes and is
|
280
|
stored in row major order. These codes are used in the source map image:
|
281
|
|
282
|
Value Source
|
283
|
----- ------
|
284
|
|
285
|
0 Ocean
|
286
|
1 Digital Terrain Elevation Data
|
287
|
2 Digital Chart of the World
|
288
|
3 USGS 1-degree DEM's
|
289
|
4 Army Map Service 1:1,000,000-scale maps
|
290
|
5 International Map of the World 1:1,000,000-scale maps
|
291
|
6 Peru 1:1,000,000-scale map
|
292
|
7 New Zealand DEM
|
293
|
8 Antarctic Digital Database
|
294
|
|
295
|
More information on each of these sources is provided in section 6.1
|
296
|
(Data Sources). The cells with value 0 (ocean) in the source map can
|
297
|
be used as an ocean mask (the ocean cells match exactly all the cells
|
298
|
masked as "no data" in the DEM with a value of -9999). Likewise, the cells
|
299
|
with values 1-8 together constitute a global land mask. Every cell in the
|
300
|
DEM with an elevation has a corresponding cell in the source map with a
|
301
|
value in the range 1-8.
|
302
|
|
303
|
3.8 Source Map Header File (.SCH)
|
304
|
|
305
|
The source map header file is an ASCII text file containing size and
|
306
|
coordinate information, similar to the DEM header file. The following
|
307
|
keywords are used in the source map header file:
|
308
|
|
309
|
BYTEORDER byte order in which image pixel values are stored
|
310
|
M = Motorola byte order (most significant byte first)
|
311
|
LAYOUT organization of the bands in the file
|
312
|
BIL = band interleaved by line (note: the source map is
|
313
|
a single band image)
|
314
|
NROWS number of rows in the image
|
315
|
NCOLS number of columns in the image
|
316
|
NBANDS number of spectral bands in the image (1 for the source map)
|
317
|
NBITS number of bits per pixel (8 for the source map)
|
318
|
BANDROWBYTES number of bytes per band per row (the number of columns for
|
319
|
an 8-bit source map)
|
320
|
TOTALROWBYTES total number of bytes of data per row (the number of columns
|
321
|
for a single band 8-bit source map)
|
322
|
BANDGAPBYTES the number of bytes between bands in a BSQ format image
|
323
|
(0 for the source map)
|
324
|
NODATA value used for masking purposes
|
325
|
ULXMAP longitude of the center of the upper-left pixel (decimal degrees)
|
326
|
ULYMAP latitude of the center of the upper-left pixel (decimal degrees)
|
327
|
XDIM x dimension of a pixel in geographic units (decimal degrees)
|
328
|
YDIM y dimension of a pixel in geographic units (decimal degrees)
|
329
|
|
330
|
Example source map header file (W100N40.SCH):
|
331
|
|
332
|
BYTEORDER M
|
333
|
LAYOUT BIL
|
334
|
NROWS 6000
|
335
|
NCOLS 4800
|
336
|
NBANDS 1
|
337
|
NBITS 8
|
338
|
BANDROWBYTES 4800
|
339
|
TOTALROWBYTES 4800
|
340
|
BANDGAPBYTES 0
|
341
|
NODATA -9999
|
342
|
ULXMAP -99.99583333333334
|
343
|
ULYMAP 39.99583333333333
|
344
|
XDIM 0.00833333333333
|
345
|
YDIM 0.00833333333333
|
346
|
|
347
|
4.0 Data Distribution
|
348
|
|
349
|
Data for each GTOPO30 tile are distributed electronically as a compressed tar
|
350
|
file. The 8 files for each tile have been combined into one file with the
|
351
|
Unix "tar" command, and the tar file has been compressed with GNU "gzip"
|
352
|
utility. To use the GTOPO30 data files, the tar file must first be
|
353
|
decompressed and then the individual data files extracted from the tar file.
|
354
|
For example, the following Unix command could be used:
|
355
|
|
356
|
gunzip < w100n40.tar.gz | tar xvf -
|
357
|
|
358
|
If you do not have access to gzip, you can leave off the .gz extension and
|
359
|
the FTP server will decompress the tar file as it is downloaded. However,
|
360
|
you will still have to run the tar command to extract separate files.
|
361
|
Please note that a decompressed file is typically many times larger than
|
362
|
the compressed version and therefore will take much longer to transmit. If
|
363
|
you would like to obtain the gzip or tar programs they are available via
|
364
|
anonymous FTP from the following sites:
|
365
|
|
366
|
Unix gzip:
|
367
|
ftp://prep.ai.mit.edu/pub/gnu
|
368
|
ftp://wuarchive.wustl.edu/systems/gnu
|
369
|
Macintosh gzip and tar:
|
370
|
ftp://mirrors.aol.com/pub/mac/util/compression
|
371
|
macgzip0.3b2.sit.hqx
|
372
|
suntar2.03.cpt.hqx
|
373
|
DOS gzip and tar:
|
374
|
ftp://prep.ai.mit.edu/pub/gnu
|
375
|
gzip-1.2.4.tar
|
376
|
ftp://ftp.uu.net/systems/ibmpc/msdos/pcroute
|
377
|
tar.exe
|
378
|
|
379
|
4.1 Procedures for Obtaining Data
|
380
|
|
381
|
GTOPO30 is available electronically through an Internet anonymous File
|
382
|
Transfer Protocol (FTP) account at the EROS Data Center (at no cost).
|
383
|
|
384
|
To access this account:
|
385
|
|
386
|
1. FTP to edcftp.cr.usgs.gov
|
387
|
2. Enter "anonymous" at the Name prompt.
|
388
|
3. Enter your email address at the Password prompt.
|
389
|
4. Change ("cd") to the "/pub/data/gtopo30/global" subdirectory.
|
390
|
5. Files are named according to the longitude and latitude coordinates
|
391
|
of the upper-left corner of the tile, followed by the extension
|
392
|
".tar.gz".
|
393
|
6. Enter "binary" to set the transfer type.
|
394
|
7. Use "get" or "mget" to retrieve the desired files.
|
395
|
8. For the Antarctica polar stereographic data, change ("cd") to the
|
396
|
"/pub/data/gtopo30/antarctica" subdirectory and use "get" to
|
397
|
retrieve the file antarcps.tar.gz.
|
398
|
|
399
|
Click here to place an order for the data on CD-ROM or 8 mm high density
|
400
|
tar tape.
|
401
|
|
402
|
For assistance and information contact:
|
403
|
|
404
|
EDC DAAC User Services
|
405
|
EROS Data Center
|
406
|
Sioux Falls, SD 57198 USA
|
407
|
Tel: 605-594-6116 (7:30 am to 4:00 pm CT)
|
408
|
Fax: 605-594-6963 (24 hours)
|
409
|
Internet: edc@eos.nasa.gov (24 hours)
|
410
|
|
411
|
Data distributed on CD-ROM and 8 mm tape are provided as sets of files for
|
412
|
each tile as described above in section 3.0 (Data Format). They are not
|
413
|
combined into one tar file or compressed as they are for electronic
|
414
|
distribution.
|
415
|
|
416
|
4.2 File Sizes
|
417
|
|
418
|
After decompression and extraction from the tar files, the following file
|
419
|
sizes are present for each of the 3 sizes of tiles:
|
420
|
|
421
|
Tile size File Size (bytes)
|
422
|
--------- ---- ------------
|
423
|
|
424
|
50 degrees latitude DEM 57600000
|
425
|
by
|
426
|
40 degrees longitude Source map 28800000
|
427
|
|
428
|
30 degrees latitude DEM 51840000
|
429
|
by
|
430
|
60 degrees longitude Source map 25920000
|
431
|
|
432
|
Antarctica polar DEM 58320000
|
433
|
stereographic data
|
434
|
(5,400 km x 5,400 km) Source map 29160000
|
435
|
|
436
|
For each tile, the total for all the other file types (HDR, DMW, STX, PRJ,
|
437
|
GIF, and SCH) is well under 1 megabyte.
|
438
|
|
439
|
The global 16-bit DEM (21,600 rows by 43,200 columns) has a size of 1.74
|
440
|
gigabytes. The global 8-bit source map of the same dimensions has a size of
|
441
|
889.9 megabytes.
|
442
|
|
443
|
Through the use of the gzip compression utility the total size of the global
|
444
|
data set is reduced about 90% from almost 2.72 gigabytes to under 290
|
445
|
megabytes. The list below shows the compressed size for each tile. The
|
446
|
sizes range from less than 1 megabyte to about 25 megabytes, with the average
|
447
|
at about 8 megabytes. Decompressed, the tar file for each tile can be as
|
448
|
large as 84 megabytes.
|
449
|
|
450
|
File Size (bytes)
|
451
|
---- ------------
|
452
|
|
453
|
antarcps.tar.gz 10538463
|
454
|
e020n40.tar.gz 26124072
|
455
|
e020n90.tar.gz 16992230
|
456
|
e020s10.tar.gz 8262946
|
457
|
e060n40.tar.gz 17935016
|
458
|
e060n90.tar.gz 22402428
|
459
|
e060s10.tar.gz 113591
|
460
|
e060s60.tar.gz 5308336
|
461
|
e100n40.tar.gz 14175303
|
462
|
e100n90.tar.gz 24994154
|
463
|
e100s10.tar.gz 4361555
|
464
|
e120s60.tar.gz 6131365
|
465
|
e140n40.tar.gz 1140685
|
466
|
e140n90.tar.gz 9222752
|
467
|
e140s10.tar.gz 4059027
|
468
|
w000s60.tar.gz 5080091
|
469
|
w020n40.tar.gz 16938044
|
470
|
w020n90.tar.gz 8844434
|
471
|
w020s10.tar.gz 2927056
|
472
|
w060n40.tar.gz 3721100
|
473
|
w060n90.tar.gz 6820815
|
474
|
w060s10.tar.gz 6738966
|
475
|
w060s60.tar.gz 3558292
|
476
|
w100n40.tar.gz 11330238
|
477
|
w100n90.tar.gz 15656539
|
478
|
w100s10.tar.gz 9575882
|
479
|
w120s60.tar.gz 5677801
|
480
|
w140n40.tar.gz 6497682
|
481
|
w140n90.tar.gz 17031379
|
482
|
w140s10.tar.gz 89706
|
483
|
w180n40.tar.gz 131975
|
484
|
w180n90.tar.gz 5477564
|
485
|
w180s10.tar.gz 116231
|
486
|
w180s60.tar.gz 3500153
|
487
|
|
488
|
5.0 Notes and Hints for GTOPO30 Users
|
489
|
|
490
|
Because the DEM data are stored in a 16-bit binary format, users must be
|
491
|
aware of how the bytes are addressed on their computers. The DEM data are
|
492
|
provided in Motorola byte order, which stores the most significant byte
|
493
|
first ("big endian"). Systems such as Sun SPARC and Silicon Graphics
|
494
|
workstations use the Motorola byte order. The Intel byte order, which
|
495
|
stores the least significant byte first ("little endian"), is used on DEC
|
496
|
Alpha systems and most PCs. Users with systems that address bytes in the
|
497
|
Intel byte order may have to "swap bytes" of the DEM data unless their
|
498
|
application software performs the conversion during ingest. The statistics
|
499
|
file (.STX) provided for each tile gives the range of values in the DEM
|
500
|
file, so users can check if they have the correct DEM values stored on
|
501
|
their system.
|
502
|
|
503
|
Users of ARC/INFO or ArcView can display the DEM data directly after simply
|
504
|
renaming the file extension from .DEM to .BIL. However, if a user needs
|
505
|
access to the actual elevation values for analysis in ARC/INFO the DEM must
|
506
|
be converted to an ARC/INFO grid with the command IMAGEGRID. IMAGEGRID does
|
507
|
not support conversion of signed image data, therefore the negative 16-bit
|
508
|
DEM values will not be interpreted correctly. After running IMAGEGRID, an
|
509
|
easy fix can be accomplished using the following formula in Grid:
|
510
|
|
511
|
out_grid = con(in_grid >= 32768, in_grid - 65536, in_grid)
|
512
|
|
513
|
The converted grid will then have the negative values properly represented,
|
514
|
and the statistics of the grid should match those listed in the .STX file.
|
515
|
If desired, the -9999 ocean mask values in the grid could then be set to
|
516
|
NODATA with the SETNULL function.
|
517
|
|
518
|
6.0 Data Set Development
|
519
|
|
520
|
GTOPO30, completed in late 1996, was developed over a 3 year period through
|
521
|
a collaborative effort led by staff at the U.S. Geological Survey's EROS Data
|
522
|
Center (EDC). The following organizations participated by contributing
|
523
|
funding or source data: the National Aeronautics and Space Administration
|
524
|
(NASA), the United Nations Environment Programme/Global Resource Information
|
525
|
Database (UNEP/GRID), the U.S. Agency for International Development (USAID),
|
526
|
the Instituto Nacional de Estadistica Geografica e Informatica (INEGI) of
|
527
|
Mexico, the Geographical Survey Institute (GSI) of Japan, Manaaki Whenua
|
528
|
Landcare Research of New Zealand, and the Scientific Committee on Antarctic
|
529
|
Research (SCAR).
|
530
|
|
531
|
6.1 Data Sources
|
532
|
|
533
|
GTOPO30 is based on data derived from 8 sources of elevation information,
|
534
|
including vector and raster data sets. The following table lists the
|
535
|
percentage of the global land surface area derived from each source (a full
|
536
|
description of each source is provided below):
|
537
|
|
538
|
Source % of global land area
|
539
|
------ ---------------------
|
540
|
|
541
|
Digital Terrain Elevation Data 50.0
|
542
|
Digital Chart of the World 29.9
|
543
|
USGS 1-degree DEM's 6.7
|
544
|
Army Map Service 1:1,000,000-scale maps 1.1
|
545
|
International Map of the World 1:1,000,000-scale maps 3.7
|
546
|
Peru 1:1,000,000-scale map 0.1
|
547
|
New Zealand DEM 0.2
|
548
|
Antarctic Digital Database 8.3
|
549
|
|
550
|
6.1.1 Digital Terrain Elevation Data
|
551
|
|
552
|
Digital Terrain Elevation Data (DTED) is a raster topographic data base with
|
553
|
a horizontal grid spacing of 3-arc seconds (approximately 90 meters) produced
|
554
|
by the National Imagery and Mapping Agency (NIMA) (formerly the Defense
|
555
|
Mapping Agency). DTED was used as the source for most of Eurasia and large
|
556
|
parts of Africa, South America, Mexico, Canada, and Central America. DTED
|
557
|
coverage for Mexico was provided by INEGI.
|
558
|
|
559
|
6.1.2 Digital Chart of the World
|
560
|
|
561
|
Digital Chart of the World (DCW) is a vector cartographic data set based on
|
562
|
the 1:1,000,000-scale Operational Navigation Chart (ONC) series, which is the
|
563
|
largest scale base map source with global coverage (Danko, 1992). The DCW
|
564
|
and the ONC series are products of NIMA.
|
565
|
|
566
|
The topographic information of interest for generating DEM's is contained in
|
567
|
several DCW hypsography layers. The primary contour interval on the source
|
568
|
ONC's is 1,000 feet (305 meters), and supplemental contours at an interval of
|
569
|
250 feet (76 meters) are shown in areas below 1,000 feet in elevation. In
|
570
|
limited areas of higher elevation there supplemental contours at 500-foot
|
571
|
(152-meter) intervals. The DCW drainage layers were also used as input to
|
572
|
the DEM generation process; this information included stream networks, lake
|
573
|
shorelines, lake elevations, and ocean coastlines. The DCW was used as the
|
574
|
primary source for filling gaps in the DTED coverage, including all of
|
575
|
Australia, most of Greenland, and large areas of Africa, South America, and
|
576
|
Canada.
|
577
|
|
578
|
6.1.3 USGS Digital Elevation Models
|
579
|
|
580
|
USGS 1-degree DEM's with a horizontal grid spacing of 3-arc seconds
|
581
|
(approximately 90 meters) were used as the source data for the continental
|
582
|
United States, Alaska, and Hawaii. The topographic information content is
|
583
|
similar to that of DTED. The "1-degree" designation refers to the unit of
|
584
|
data distribution.
|
585
|
|
586
|
6.1.4 Army Map Service Maps
|
587
|
|
588
|
Paper maps at a scale of 1:1,000,000 produced by the Army Map Service (AMS),
|
589
|
a predecessor of DMA and NIMA, were acquired and digitized by GSI of Japan.
|
590
|
Contours (with intervals of 100, 150, 300, and 500 meters), spot heights,
|
591
|
drainage lines , and coastlines for some islands of southeast Asia and some
|
592
|
small areas in South America were delivered to EDC as digital vector
|
593
|
cartographic data sets.
|
594
|
|
595
|
6.1.5 International Map of the World
|
596
|
|
597
|
Paper maps from the 1:1,000,000-scale International Map of the World (IMW)
|
598
|
series were digitized by GSI to provide source data for the Amazon basin.
|
599
|
The International Map of the World includes national maps produced to a
|
600
|
United Nations specified standard for 1:1,000,000-scale mapping. The maps
|
601
|
used for this project had a 100-meter contour interval.
|
602
|
|
603
|
6.1.6 Peru Map
|
604
|
|
605
|
Small areas of a 1:1,000,000-scale map from the Peruvian government were
|
606
|
digitized to fill gaps in source data for South America. The map had a
|
607
|
contour interval of 1,000 meters.
|
608
|
|
609
|
6.1.7 New Zealand DEM
|
610
|
|
611
|
Manaaki Whenua Landcare Research contributed a DEM with a 500-meter
|
612
|
horizontal grid spacing for New Zealand. The DEM was derived from elevation
|
613
|
information on 1:63,360-scale maps with a 100-foot (30-meter) contour
|
614
|
interval.
|
615
|
|
616
|
6.1.8 Antarctic Digital Database
|
617
|
|
618
|
The Antarctic Digital Database (ADD) was produced under the auspices of the
|
619
|
Scientific Committee on Antarctic Research. Digital contours and coastlines
|
620
|
from the ADD were used as source material for Antarctica. The ADD vector
|
621
|
data were compiled from maps ranging in scale from 1:200,000 to 1:5,000,000.
|
622
|
The detail, density, and interval of the contours in the ADD vary widely,
|
623
|
with the more detailed data near the coastline and very generalized data in
|
624
|
the interior of the continent. Detailed metadata provided in the ADD
|
625
|
identifies the map scale from which each contour line was extracted.
|
626
|
|
627
|
6.2 Data Processing
|
628
|
|
629
|
GTOPO30 was developed over a 3 year period during which continental and
|
630
|
regional areas were produced individually. As such, processing techniques
|
631
|
were developed and refined throughout the duration of the project. Although
|
632
|
the techniques used for the various continental areas are very similar,
|
633
|
there were some differences in approach due to varying source material.
|
634
|
More details about data development for several of the continental areas are
|
635
|
reported by Verdin and Greenlee (1996), Bliss and Olsen (1996), and Gesch and
|
636
|
Larson (1996).
|
637
|
|
638
|
Data processing was accomplished using commercially available geographic
|
639
|
information system software, public domain image processing software,
|
640
|
vector-to-raster gridding software, and utilities developed specifically for
|
641
|
this project. To more efficiently handle the numerous input data sets and to
|
642
|
standardize the proper sequence of processing steps, the production
|
643
|
procedures were automated to a great extent by employing preset parameter
|
644
|
values, scripted command files, and consistent naming schemes for input and
|
645
|
output data files.
|
646
|
|
647
|
6.2.1 Raster Source Processing
|
648
|
|
649
|
Processing of the raster source data, including DTED, USGS DEM's, and the New
|
650
|
Zealand DEM, involved generalizing the higher resolution data to the 30-arc
|
651
|
second horizontal grid spacing. Because the DTED and USGS DEM's were already
|
652
|
in a geographic "projection" they only required a sampling of the full
|
653
|
resolution 3-arc second data. One representative elevation value was selected
|
654
|
to represent the area covered by 100 full resolution cells (a 10 by 10
|
655
|
matrix). As the project progressed, several methods of generalization were
|
656
|
used. Selection of the representative 30-arc second value was accomplished
|
657
|
by systematic subsampling for North and South America, by calculation of the
|
658
|
median value for Eurasia, and by the breakline emphasis approach (Gesch and
|
659
|
Larson, 1996) for Africa. The 500-meter New Zealand DEM was generalized to
|
660
|
30-arc seconds by reprojecting it from the New Zealand National Grid
|
661
|
projection to geographic coordinates using bilinear resampling.
|
662
|
|
663
|
6.2.2 Vector Source Processing
|
664
|
|
665
|
The topographic information from the vector cartographic sources, including
|
666
|
the DCW, the ADD, and the Army Map Service, International Map of the World,
|
667
|
and Peru 1:1,000,000-scale maps, was converted into elevation grids through
|
668
|
a vector-to-raster gridding approach. Contours, spot heights, stream lines,
|
669
|
lake shorelines, and ocean coastlines were input to the ANUDEM surface
|
670
|
gridding program developed at the Australian National University (Hutchinson,
|
671
|
1989). ANUDEM, specifically designed for creating DEM's from digital contour,
|
672
|
spot height, and stream line data, employs an approach known as drainage
|
673
|
enforcement to produce raster elevation models that represent more closely
|
674
|
the actual terrain surface and contain fewer artifacts than those produced
|
675
|
with more general purpose surface interpolation routines. Drainage
|
676
|
enforcement was performed for all areas covered by vector source data except
|
677
|
Antarctica and Greenland.
|
678
|
|
679
|
A significant amount of preprocessing was required to prepare and format the
|
680
|
vector source data for input to ANUDEM. This processing included editing and
|
681
|
updating the vector stream lines so that the direction of each was oriented
|
682
|
downstream (a requirement of ANUDEM). Further preprocessing involved
|
683
|
detection and correction of erroneous contour and point elevations (Larson,
|
684
|
1996). Ocean coastlines were assigned an elevation of zero for input as
|
685
|
contours. Also, shorelines of lakes for which the DCW included elevations
|
686
|
were tagged and used as contour input. The output from ANUDEM was an
|
687
|
elevation model grid referenced in the same horizontal coordinate system as
|
688
|
the generalized raster source data. The output grid spacing of 30-arc
|
689
|
seconds has been shown to be appropriate for the information content present
|
690
|
in the DCW hypsography layers (Hutchinson, 1996; Shih and Chiu, 1996).
|
691
|
|
692
|
6.2.3 DEM Merging
|
693
|
|
694
|
Prior to merging with the generalized raster data, lakes for which the DCW
|
695
|
did not indicate an elevation were updated on the DCW grid with the lowest
|
696
|
grid cell elevation found along the shoreline. When each of the vector
|
697
|
sources was gridded, an overlap area with the adjacent raster sources was
|
698
|
included so that smoothing could be performed to minimize the elevation
|
699
|
discrepancies among the sources. Also, additional point control was input
|
700
|
into the ANUDEM gridding process so interpolated elevations in the overlap
|
701
|
region would more closely match the raster source elevations. The additional
|
702
|
control was derived from the generalized raster sources within a 1-degree
|
703
|
buffer surrounding the vector source areas.
|
704
|
|
705
|
Merging of the generalized raster sources and the gridded vector sources was
|
706
|
accomplished by mosaicking the data sets. The generalized raster sources
|
707
|
had the highest priority so coverage of the data with the greater
|
708
|
topographic detail and accuracy was maximized. The grid derived from DCW
|
709
|
data had the highest priority among the vector sources, and the other
|
710
|
digitized map data was used when DCW hypsography was unavailable. The
|
711
|
merging procedure including blending of the generalized raster sources and
|
712
|
the vector-derived grids within an approximate 1-degree overlap area along
|
713
|
the irregular boundaries. The blending algorithm computes a weighted average
|
714
|
with the weights for each data source determined on a cell-by-cell basis
|
715
|
according to the cell's proximity to the edges of the overlap area (Franke,
|
716
|
1982).
|
717
|
|
718
|
A final processing step performed on the mosaicked and blended product
|
719
|
involved "clipping out" the land (as defined by vector coastline data) and
|
720
|
setting the ocean areas to a constant background value. Use of vector
|
721
|
coastline data resulted in a more consistent portrayal of the land/ocean
|
722
|
interface, especially in areas where raster source data (which had an implied
|
723
|
coastline) met with vector source data. The DCW coastline was used to clip
|
724
|
the following areas: Africa, Eurasia, South America, Australia, New Zealand,
|
725
|
Greenland, and isolated ocean islands. The World Vector Shoreline (WVS), a
|
726
|
vector shoreline data set from NIMA, was used for North America, including
|
727
|
Hawaii, the Caribbean islands, and Central America. The islands of Borneo
|
728
|
and Sulawesi in southeast Asia were clipped with the coastline digitized
|
729
|
from the 1:1,000,000-scale map source. Antarctica was defined by the
|
730
|
coastline as portrayed in the ADD.
|
731
|
|
732
|
6.2.4 Global Product Assembly
|
733
|
|
734
|
The global product was assembled from the continental and regional DEM's.
|
735
|
Several areas of overlap due to different production stages of the project
|
736
|
were addressed and eliminated, most notably between the Africa and Eurasia
|
737
|
data sets. The global source map was generated from masks of source data
|
738
|
coverage, and was verified to register with the DEM precisely. Finally, the
|
739
|
entire data set was packaged into tiles for easier electronic distribution.
|
740
|
|
741
|
7.0 Accuracy
|
742
|
|
743
|
The absolute vertical accuracy of GTOPO30 varies by location according to
|
744
|
the source data. Generally, the areas derived from the raster source data
|
745
|
have higher accuracy than those derived from the vector source data. The
|
746
|
full resolution 3-arc second DTED and USGS DEM's have a vertical accuracy
|
747
|
of + or - 30 meters linear error at the 90 percent confidence level (Defense
|
748
|
Mapping Agency, 1986; U.S. Geological Survey, 1993). If the error
|
749
|
distribution is assumed to be Gaussian with a mean of zero, the statistical
|
750
|
standard deviation of the errors is equivalent to the root mean square error
|
751
|
(RMSE). Under those assumptions, vertical accuracy expressed as + or - 30
|
752
|
meters linear error at 90 percent can also be described as a RMSE of 18
|
753
|
meters. The areas of GTOPO30 derived from DTED and USGS DEM's retain that
|
754
|
same level of accuracy because through generalization a representative
|
755
|
elevation value derived from the full resolution cells is chosen to represent
|
756
|
the area of the reduced resolution cell (although the area on the ground
|
757
|
represented by that one elevation value is now much larger than the area
|
758
|
covered by one full resolution cell).
|
759
|
|
760
|
The absolute vertical accuracy of the DCW, the vector source with the largest
|
761
|
area of coverage, is stated in its product specification as + or - 650 meters
|
762
|
linear error at the 90% confidence level (Defense Mapping Agency, 1990).
|
763
|
Experience has shown that the grids derived from DCW data should in many
|
764
|
areas be much more accurate than the 650-meter specification. To better
|
765
|
characterize the accuracy of the areas of GTOPO30 derived from DCW vector
|
766
|
hypsography, the DCW grid was compared to 30-arc second DTED, which had been
|
767
|
aggregated by averaging. By aggregating, the comparison could be done at the
|
768
|
30-arc second cell size of the DCW grid. The comparison was done for
|
769
|
portions of southern Europe and the Mideast, and all of Africa. Eliminated
|
770
|
from the comparison were those areas of the DCW grid for which supplemental
|
771
|
DTED point control had been included in the gridding process. If the
|
772
|
averaged DTED are thought of as the reference data set, the RMSE of the DCW
|
773
|
grid is 95 meters. To get an idea of the overall absolute accuracy of the
|
774
|
DCW grid, the relative error between the DCW and DTED can be combined with
|
775
|
the known error of the DTED itself in a sum of squares. The root of that sum
|
776
|
of squares is 97 meters. Using the assumptions about the error distribution
|
777
|
cited above, a RMSE of 97 meters can be expressed as + or - 160 meters linear
|
778
|
error at 90 percent confidence. This number compares favorably with an
|
779
|
expected vertical accuracy (linear error at 90 percent) of one-half of the
|
780
|
primary contour interval of 1,000 feet (305 meters) for the topographic maps
|
781
|
on which the DCW is based.
|
782
|
|
783
|
The accuracy of the areas of GTOPO30 based on the other sources can only be
|
784
|
estimated based on that which is known about each source. Using certain
|
785
|
assumptions, the vertical accuracy of each source (and the derived 30-arc
|
786
|
second grid) can be estimated from the contour interval. One assumption is
|
787
|
that the original map sources meet the commonly used accuracy standard which
|
788
|
states that 90% of the map elevations are within + or - one-half of the
|
789
|
contour interval. It is unknown if any of these maps actually meet this
|
790
|
standard. Also, map digitizing and elevation surface interpolation errors
|
791
|
are unknown and therefore not included. The table below lists the estimated
|
792
|
absolute vertical accuracy for the areas of GTOPO30 derived from each
|
793
|
source, with the method of estimating the accuracy also identified. The
|
794
|
RMSE numbers were calculated using the assumptions about the error
|
795
|
distribution cited above (a Gaussian distribution with a mean of zero).
|
796
|
|
797
|
Vertical accuracy (meters)
|
798
|
Source L.E. at 90% RMSE Estimation method
|
799
|
------ -------------------------- -----------------
|
800
|
|
801
|
DTED 30 18 product specification
|
802
|
DCW 160 97 calculated vs. DTED
|
803
|
USGS DEM 30 18 product specification
|
804
|
AMS maps 250 152 estimated from 500-meter interval
|
805
|
IMW maps 50 30 estimated from 100-meter interval
|
806
|
Peru map 500 304 estimated from 1,000-meter interval
|
807
|
N.Z. DEM 15 9 estimated from 100-foot interval
|
808
|
ADD highly variable wide range of scales and intervals
|
809
|
|
810
|
Local differences among DEM grid cells are often analyzed to calculate slope
|
811
|
and other land surface parameters. The relative vertical accuracy (or
|
812
|
point-to-point accuracy on the surface of the elevation model), rather than
|
813
|
the absolute accuracy, determines the quality of such parameters derived from
|
814
|
local differencing operations. Although not specified for this data set,
|
815
|
for many areas the relative accuracy is probably better than the estimated
|
816
|
absolute accuracy.
|
817
|
|
818
|
8.0 GTOPO30 Caveats
|
819
|
|
820
|
As with all digital geospatial data sets, users of GTOPO30 must be aware of
|
821
|
certain characteristics of the data set (resolution, accuracy, methods of
|
822
|
production and any resulting artifacts, etc.) in order to better judge its
|
823
|
suitability for a specific application. A characteristic of GTOPO30 that
|
824
|
renders it unsuitable for one application may have no relevance as a
|
825
|
limiting factor for its use in a different application. Because only the end
|
826
|
user can judge the applicability of the data set, it is the responsibility
|
827
|
of the data producer to describe the characteristics of the data as fully as
|
828
|
possible, so that an informed decision can be made by the user.
|
829
|
|
830
|
8.1 Grid Spacing and Resolution
|
831
|
|
832
|
For any application, the horizontal grid spacing (which limits the
|
833
|
resolution) and the vertical accuracy of GTOPO30 must be considered. The
|
834
|
30-arc second grid spacing equates to about 1 kilometer, although that
|
835
|
number decreases in the east/west (longitudinal) direction as latitude
|
836
|
increases, The table below lists the approximate distance covered by 30-arc
|
837
|
seconds at different latitudes. Thus, at high latitudes there is an
|
838
|
unavoidable redundancy of data in order to keep the 30-arc second spacing
|
839
|
consistent for the global data set. This is particularly true for the
|
840
|
geographic version of Antarctica where the ground distance for 30-arc seconds
|
841
|
of longitude converges to zero at the South Pole.
|
842
|
|
843
|
Latitude Ground distance (meters)
|
844
|
(degrees) E/W N/S
|
845
|
--------- ------------------------
|
846
|
|
847
|
Equator 928 921
|
848
|
10 914 922
|
849
|
20 872 923
|
850
|
30 804 924
|
851
|
40 712 925
|
852
|
50 598 927
|
853
|
60 465 929
|
854
|
70 318 930
|
855
|
73 272 930
|
856
|
78 193 930
|
857
|
82 130 931
|
858
|
|
859
|
The variation in ground dimensions for one 30-arc second cell should be
|
860
|
especially considered for any application that measures area of or distance
|
861
|
across a group of cells. Derivative products, such as slope maps, drainage
|
862
|
basin areas, and stream channel length, will be more reliable if they are
|
863
|
calculated from a DEM that has been first projected from geographic
|
864
|
coordinates to an equal area projection, so that each cell, regardless of
|
865
|
latitude, represents the same ground dimensions and area as every other cell.
|
866
|
|
867
|
Users should maintain the distinction between grid spacing and resolution.
|
868
|
Even though the global data set has a consistent 30-arc second grid spacing,
|
869
|
not all topographic features that one would expect to be resolved at that
|
870
|
spacing will be represented. The level of detail of the source data
|
871
|
determines whether the 30-arc second sampling interval is truly appropriate
|
872
|
for resolving the important topographic features represented in the source.
|
873
|
Certainly, a 30-arc second grid spacing is appropriate for the areas derived
|
874
|
from higher resolution DEM's (DTED, USGS DEM's, and the New Zealand DEM), and
|
875
|
30-arc seconds has been shown to be suitable as the cell spacing for grids
|
876
|
derived from DCW hypsography (Hutchinson, 1996; Shih and Chiu, 1996).
|
877
|
However, coverage of DCW contours is not complete, and there are areas for
|
878
|
which elevations were interpolated based only on very sparse DCW point data
|
879
|
and/or distant contours. Small areas of this nature are located in Africa,
|
880
|
South America, and islands of southeast Asia, while Australia and Greenland
|
881
|
contain larger such areas. Also, the quality of the contours from the ADD
|
882
|
for the interior of Antarctica does not realistically support a 30-arc second
|
883
|
(or even 1-kilometer) grid spacing, although such data are provided for
|
884
|
completeness and consistency of the global product.
|
885
|
|
886
|
8.2 Topographic Detail and Accuracy
|
887
|
|
888
|
Differences in topographic detail among the sources are evident in GTOPO30.
|
889
|
This change in level of topographic information is especially evident at the
|
890
|
boundary between areas derived from DTED and DCW in regions of higher relief.
|
891
|
The mosaicking techniques that were used resulted in a smoothing of the
|
892
|
transition areas, but the change in detail between the two sources remains
|
893
|
very noticeable. Even if the same topographic feature (ridge, stream valley,
|
894
|
lake, etc.) is represented in the data derived from the two sources, the
|
895
|
elevations across the feature may change somewhat abruptly due to the varying
|
896
|
accuracy of the sources. Derived products, such as slope maps, for the
|
897
|
source transition areas also emphasize the differences in topographic
|
898
|
information derived from the varying sources.
|
899
|
|
900
|
Users are reminded that the accuracy levels described above are estimates,
|
901
|
and that the accuracy for specific locations within the overall area derived
|
902
|
from any one source can vary from the estimate. For instance, approximately
|
903
|
30% of the DTED 1-degree by 1-degree tiles (the production and distribution
|
904
|
unit for full resolution DTED) have an absolute vertical accuracy worse than
|
905
|
the product specification of + or - 30 meters at 90% confidence. Also, the
|
906
|
actual accuracy for some areas derived from the vector contour sources may
|
907
|
be better or worse than the estimate. When the map source had multiple
|
908
|
contour intervals, the largest interval was used for a conservative estimate.
|
909
|
In contrast, some areas may be worse than the estimate because no contour
|
910
|
coverage was available for those specific locations.
|
911
|
|
912
|
8.3 Production Artifacts
|
913
|
|
914
|
Artifacts due to the production method are apparent in some areas of
|
915
|
GTOPO30. While the magnitude of the artifacts in a local area are usually
|
916
|
well within the estimated accuracy for the source, users are nonetheless
|
917
|
made aware because the effects are plainly visible and they may affect some
|
918
|
applications of the DEM. Some areas derived from DTED, especially in Africa
|
919
|
and the Mideast, exhibit a striping artifact, most likely due to the
|
920
|
production method of the DTED. The artifact is very evident in the full
|
921
|
resolution data, but remains noticeable even in the generalized 30-arc
|
922
|
second version. Generally, the pattern is more noticeable in low relief
|
923
|
areas, while in higher relief areas it is masked by the actual terrain
|
924
|
variation. Another pattern seen in some areas derived from DTED is a blocky
|
925
|
appearance, which is reflection of the 1-degree tiling structure of the full
|
926
|
resolution DTED. These areas derived from contiguous DTED 1-degree tiles
|
927
|
appear blocky because of vertical offsets among the tiles in the original
|
928
|
full resolution DTED. The artifacts in the DTED areas may or may not be
|
929
|
visible, depending on the method used to display the data. For instance,
|
930
|
when viewing the DEM data as an image either in shades of gray or color, the
|
931
|
artifacts may be hidden, depending on the number of shades or colors used.
|
932
|
If the data are displayed as a shaded relief image the appearance of the
|
933
|
artifacts will vary depending on the direction of illumination, vertical
|
934
|
exaggeration applied, and the scale of the display. Generally, none of the
|
935
|
artifacts will be visible on a small scale portrayal of the global data set.
|
936
|
|
937
|
Some production artifacts are also present in the areas derived from the
|
938
|
vector sources. Small artificial mounds and depressions may be present in
|
939
|
localized areas, particularly where steep topography is adjacent to
|
940
|
relatively level areas, and the hypsography data were sparse. Additionally,
|
941
|
a "stair step" (or terracing) effect may be seen in profiles of some areas,
|
942
|
where the transition between contour line elevations does not slope
|
943
|
constantly across the area but instead is covered by a flat area with
|
944
|
sharper changes in slope at the locations of the contour lines. When a
|
945
|
histogram of elevations is presented there are sharp peaks at elevations
|
946
|
that are multiples of the contour interval of the source. This effect is
|
947
|
common in DEM's produced by gridding of contour data in which the
|
948
|
interpolation process favors elevations at or near the contour values, thus
|
949
|
leading to a greater frequency of those elevations. Every effort to reduce
|
950
|
these effects has been made by careful selection of parameters for the
|
951
|
interpolation process, but some level of these conditions inevitably remain
|
952
|
due to the nature of vector-to-raster surface generation.
|
953
|
|
954
|
9.0 Summary
|
955
|
|
956
|
GTOPO30 provides a new level of detail in global topographic data.
|
957
|
Previously, the best available global DEM was the ETOPO5 data set, and its
|
958
|
successor TerrainBase, with a horizontal grid spacing of 5-arc minutes
|
959
|
(approximately 10 kilometers) (Row, Hastings, and Dunbar, 1995). GTOPO30
|
960
|
data are suitable for many regional and continental applications, such as
|
961
|
climate modeling, continental-scale land cover mapping, extraction of
|
962
|
drainage features for hydrologic modeling (Danielson, 1996; Verdin and
|
963
|
Greenlee, 1996), and geometric and atmospheric correction of medium and coarse
|
964
|
resolution satellite image data (Gesch, 1994; Jet Propulsion Laboratory,
|
965
|
1997).
|
966
|
|
967
|
10.0 References
|
968
|
|
969
|
Bliss, N.B., and Olsen, L.M., 1996. Development of a 30-arc-second digital
|
970
|
elevation model of South America. In: Pecora Thirteen, Human Interactions
|
971
|
with the Environment - Perspectives from Space, Sioux Falls, South Dakota,
|
972
|
August 20-22, 1996.
|
973
|
|
974
|
Danielson, J.J., 1996. Delineation of drainage basins from 1 km African
|
975
|
digital elevation data. In: Pecora Thirteen, Human Interactions with the
|
976
|
Environment - Perspectives from Space, Sioux Falls, South Dakota, August
|
977
|
20-22, 1996.
|
978
|
|
979
|
Danko, D.M., 1992. The digital chart of the world. GeoInfo Systems, 2:29-36.
|
980
|
|
981
|
Defense Mapping Agency, 1986. Defense Mapping Agency product specifications
|
982
|
for digital terrain elevation data (DTED) (2d ed.). Defense Mapping Agency
|
983
|
Aerospace Center, St. Louis, Missouri, 26 p.
|
984
|
|
985
|
Defense Mapping Agency, 1990. Digitizing the future (3d ed.). Defense
|
986
|
Mapping Agency, Washington, D.C., 105 p.
|
987
|
|
988
|
Franke, R., 1982. Smooth interpolation of scattered data by local thin plate
|
989
|
splines. Computing & Mathematics with Applications, 8:273-281.
|
990
|
|
991
|
Gesch, D.B., 1994. Topographic data requirements for EOS global change
|
992
|
research. U.S. Geological Survey Open-File Report 94-626, 60 p.
|
993
|
|
994
|
Gesch, D.B., and Larson, K.S., 1996. Techniques for development of global
|
995
|
1-kilometer digital elevation models. In: Pecora Thirteen, Human Interactions
|
996
|
with the Environment - Perspectives from Space, Sioux Falls, South Dakota,
|
997
|
August 20-22, 1996.
|
998
|
|
999
|
Hutchinson, M.F., 1989. A new procedure for gridding elevation and stream
|
1000
|
line data with automatic removal of spurious pits. Journal of Hydrology,
|
1001
|
106:211-232.
|
1002
|
|
1003
|
Hutchinson, M.F., 1996. A locally adaptive approach to the interpolation
|
1004
|
of digital elevation models. In: Proceedings, Third International
|
1005
|
Conference/Workshop on Integrating GIS and Environmental Modeling, Santa
|
1006
|
Fe, New Mexico, January 21-26, 1996. National Center for Geographic
|
1007
|
Information and Analysis, Santa Barbara, California.
|
1008
|
|
1009
|
Jet Propulsion Laboratory, 1997. DEM auxiliary datasets preparation plan:
|
1010
|
digital elevation mapping support to the EOS/AM1 platform - JPL D13508,
|
1011
|
Release 2. Jet Propulsion Laboratory, California Institute of Technology,
|
1012
|
Pasadena, California, 65 p.
|
1013
|
|
1014
|
Larson, K.S., 1996. Error detection and correction of hypsography layers.
|
1015
|
In: Proceedings, Sixteenth Annual ESRI User Conference, May 20-24, 1996.
|
1016
|
Environmental Systems Research Institute, Inc., Redlands, California.
|
1017
|
|
1018
|
Row, L.W., Hastings, D.A., and Dunbar, P.K., 1995. TerrainBase Worldwide
|
1019
|
Digital Terrain Data - Documentation Manual, CD-ROM Release 1.0. National
|
1020
|
Geophysical Data Center, Boulder, Colorado.
|
1021
|
|
1022
|
Shih, T.Y., and Chiu, Y.C., 1996. On the quality of DCW hypsographic data,
|
1023
|
a study for Taiwan. In: Technical Papers, ASPRS/ACSM Annual Convention and
|
1024
|
Exhibition, April 22-25, 1996, Baltimore, Maryland. American Society for
|
1025
|
Photogrammetry and Remote Sensing, Bethesda, Maryland, Volume III, p. 248-257.
|
1026
|
|
1027
|
U.S. Geological Survey, 1993. Digital elevation models, data user guide 5.
|
1028
|
Reston, Virginia, 50 p.
|
1029
|
|
1030
|
Verdin, K.L., and Greenlee, S.K., 1996. Development of continental scale
|
1031
|
digital elevation models and extraction of hydrographic features. In:
|
1032
|
Proceedings, Third International Conference/Workshop on Integrating GIS and
|
1033
|
Environmental Modeling, Santa Fe, New Mexico, January 21-26, 1996. National
|
1034
|
Center for Geographic Information and Analysis, Santa Barbara, California.
|
1035
|
|
1036
|
11.0 Disclaimers
|
1037
|
|
1038
|
Any use of trade, product, or firm names is for descriptive purposes only
|
1039
|
and does not imply endorsement by the U.S. Government.
|
1040
|
|
1041
|
Please note that some U.S. Geological Survey (USGS) information contained
|
1042
|
in this data set and documentation may be preliminary in nature and
|
1043
|
presented prior to final review and approval by the Director of the USGS.
|
1044
|
This information is provided with the understanding that it is not guaranteed
|
1045
|
to be correct or complete and conclusions drawn from such information are the
|
1046
|
sole responsibility of the user.
|
1047
|
|
1048
|
|