1Ezmap(3NCARG) NCAR GRAPHICS Ezmap(3NCARG)
2
6 EZMAP - Allows one to plot maps of the earth according to any of ten
7 different projections, with parallels, meridians, and continental,
8 international, and/or U.S. state outlines.
9 EZMAPA is the name of a supplement to the EZMAP utility that allows
11 users to produce solid-filled maps of the earth. The EZMAPA routines
12 are discussed as part of the EZMAP utility.
13 EZMAPB is the name of a supplement to the EZMAP utility that provides
15 access to improved map databases (principally one called "Earth..1",
16 which contains a unified higher-resolution version of everything that
17 was in the old outline datasets). The EZMAPB routines are discussed as
18 part of the EZMAP utility.
19
21 Routines Used to Draw a Simple Map
22 To draw the simple map defined by the current values of EZMAP's
24 internal parameters (assuming no area fills and no access to the
25 new, improved, map database "Earth..1", which was created in
26 1998), one need only execute the single FORTRAN statement "CALL
27 MAPDRW":
28 · MAPDRW - Draws a complete simple map.
30 All that MAPDRW does is call four lower-level routines. In some
32 situations, the user may wish to call these routines directly;
33 they are as follows (in the order in which they are called by
34 MAPDRW):
35 · MAPINT - Initializes. MAPINT must be called at least once
37 before calling any routine that depends on mapping lat/lon
38 coordinates into u/v coordinates. After one or more of
39 MAPPOS, MAPROJ, and MAPSET has been called, MAPINT must be
40 called again. MAPINT does the call to the SPPS routine SET
41 that defines the mapping from the u/v (projection) plane to
42 the x/y (plotter) plane.
43 · MAPGRD - Draws selected parallels and meridians.
45 · MAPLBL - Labels the international date line, the equator,
47 the Greenwich meridian, and the poles, and draws the
48 perimeter.
49 · MAPLOT - Draws selected geographic outlines. Note that this
51 routine uses whichever old outline dataset is selected by
52 the value of the internal parameter 'OU'; to access the new
53 map database "Earth..1", which was created in 1998, one must
54 call instead the EZMAPB routine MPLNDR.
55 Routines Used to Change the Values of Internal Parameters
57 The following routines are called to change the values of
59 internal parameters of EZMAP, and thus change the behavior of
60 other EZMAP routines:
61 · MAPPOS - Determines what portion of the plotter frame is to
63 be used.
64 · MAPROJ - Determines the projection to be used.
66 · MAPSET - Determines what portion of the u/v plane is to be
68 viewed.
69 · MAPSTC - Sets a parameter value of type CHARACTER.
71 · MAPSTI - Sets a parameter value of type INTEGER.
73 · MAPSTL - Sets a parameter value of type LOGICAL.
75 · MAPSTR - Sets a parameter value of type REAL.
77 Routines Used to Retrieve the Values of Internal Parameters
79 The following routines are used to retrieve the current values
81 of EZMAP parameters:
82 · MAPGTC - Gets a parameter value of type CHARACTER.
84 · MAPGTI - Gets a parameter value of type INTEGER.
86 · MAPGTL - Gets a parameter value of type LOGICAL.
88 · MAPGTR - Gets a parameter value of type REAL.
90 Routines Used to Save and Restore Internal Parameters
92 To save/restore the current values of the internal parameters of
94 EZMAP, use the following:
95 · MAPSAV - Saves the values (by writing a record on a user-
97 specified unit).
98 · MAPRST - Restores saved values (by reading a record from a
100 user-specified unit).
101 Routines Used to Draw Objects on a Map
103 To draw objects on the map, use the following routines:
105 · MAPTRA - Computes the u/v coordinates of a point from its
107 latitude and longitude. If the point is unprojectable or its
108 projection lies outside the current perimeter, a special
109 value is returned to signal this.
110 · MAPTRN - Computes the u/v coordinates of a point from its
112 latitude and longitude. If the point is unprojectable, a
113 special value is returned to signal this, but no check is
114 made for the projected value being outside the perimeter.
115 · MAPFST - Does a "pen-up" move defining the start of a line
117 to be projected and drawn. The line is defined by a series
118 of lat/lon coordinates.
119 · MAPVEC - Does a "pen-down" move defining the continuation of
121 a line to be projected and drawn. The line is defined by a
122 series of lat/lon coordinates.
123 · MAPIT - Does "pen-up" or "pen-down" moves. This routine is
125 called by MAPFST and MAPVEC.
126 · MAPIQ - Signals the end of a string of calls to MAPIT and
128 causes its buffers to be flushed.
129 · MAPGCI - Given the latitudes and longitudes of two points on
131 the surface of the globe, this routine returns the latitudes
132 and longitudes of a specified number of points along the
133 great circle route joining them.
134 Routines Used to Do Inverse Transformations
136 The following routine was added to EZMAP early in 1992:
138 · MAPTRI - Computes the latitude and longitude of a point from
140 its u/v coordinates. If the point is outside the boundary of
141 the map, a special value is returned.
142 The example named "mpex10" shows one of the ways in which this
144 routine may be used; it draws what is essentially a colored
145 contour plot of a data field defined on the surface of the
146 globe, using an orthographic projection.
147 Routines Used to Draw Solid-Filled Maps (EZMAPA)
149 In late 1986 or early 1987, a package of routines was written
151 allowing a user to draw solid-filled maps of the globe. This
152 package was named EZMAPA and was first advertised in the NCAR
153 Graphics User's Guide (Version 2.00), published in August, 1987.
154 Conceptually, the routines in this package are really part of
155 EZMAP; they use the same common blocks and many of the same
156 underlying low-level routines and they are affected by the same
157 set of internal parameters as the routines in EZMAP proper. The
158 routines of EZMAPA will be described in this document; to use
159 them effectively, it will be necessary to understand also the
160 package AREAS, which is described in a separate document. The
161 EZMAPA routines are as follows:
162 · MAPBLA - Adds boundary lines to an existing area map.
164 Routines in the package AREAS may then be used to process
165 that area map in various ways. (Example: drawing a map of
166 Europe with each country in a different color.) Note that
167 this routine uses whichever old outline dataset is selected
168 by the value of the internal parameter 'OU'; to access the
169 new map database "Earth..1", which was created in 1998, one
170 must call instead the EZMAPB routine MPLNAM.
171 · MAPBLM - Draws boundary lines "masked" by an existing area
173 map. (Example: drawing these lines only where they do not
174 overlay CONPACK labels.) Note that this routine uses
175 whichever old outline dataset is selected by the value of
176 the internal parameter 'OU'; to access the new map database
177 "Earth..1", which was created in 1998, one must call instead
178 the EZMAPB routine MPLNDM.
179 · MAPGRM - Draws lines of latitude and longitude "masked" by
181 an existing area map. (Example: drawing these lines over
182 water, but not over land.)
183 · MAPITA and MAPIQA - Adds to an area map the projections of
185 arbitrary lines defined by lat/lon coordinates of points on
186 the surface of the globe. MAPBLA uses these routines to add
187 boundary lines to an area map; they may be called directly
188 by the user to add his/her own set of boundary lines to the
189 area map.
190 · MAPITM and MAPIQM - Draws, masked by an area map, the
192 projections of arbitrary lines defined by lat/lon
193 coordinates of points on the surface of the globe. MAPGRM
194 uses these routines to draw masked lines of latitude and
195 longitude; they may be called directly by the user to draw
196 other masked lines.
197 · MAPACI - A function which, given the "area identifier" for a
199 particular area defined by the boundaries in one of the old
200 EZMAP outline datasets, returns a suggested color index for
201 that area; it is guaranteed that, if the suggested color
202 indices are used, no two areas having a boundary in common
203 will have the same color. Note that this function should
204 not be used to select color indices for areas defined by the
205 new map database "Earth..1", which was created in 1998; for
206 that purpose, use EZMAPB functions instead (in particular,
207 MPISCI).
208 Routines Used to Access New Datasets (EZMAPB)
210 In early 1998, a new world map database, called "Earth..1", was
212 created for use with EZMAP; this database has higher-resolution
213 coastlines, it has been updated to reflect many of the political
214 changes that have taken place over the years since EZMAP came
215 into existence, and it is structured differently, allowing for
216 greater flexibility and ease of use and providing for easier
217 changes and extensions in the future.
218 Each area defined by the database has 1) a "area identifier" (an
220 integer uniquely identifying it), 2) an "area type" specifying
221 its level in a hierarchy of areas, 3) a suggested color index,
222 4) an area identifier specifying its "parent" area (the area of
223 which it is a part), and 5) a name. For example, there is an
224 area named "Madeline Island" which is of type 4 (used for a
225 state or a portion thereof) and has suggested color index 6.
226 Its parent is an area named "Wisconsin", which is also of type 4
227 and has suggested color index 6. The parent of "Wisconsin" is
228 "Conterminous US", which is of type 3 (used for a country or a
229 portion thereof) and has suggested color index 3. The parent of
230 "Conterminous US" is "United States", which is also of type 3
231 and has suggested color index 3. The parent of "United States"
232 is "North America", which is of type 2 and has suggested color
233 index 5. The parent of "North America" is "Land", which is of
234 type 1 and has suggested color index 2. The area named "Land"
235 is at the top of the hierarchy and therefore has no parent (when
236 you ask for the area identifier of its parent, you get a zero).
237 One may use the database at any of five specified hierarchical
239 levels: 1 => land/water, 2 => continents, 3 => countries, 4 =>
240 states, and 5 => counties (so far, no counties are included).
241 When the database is used at a particular level, entities that
242 exist only at lower levels (larger level numbers) effectively
243 disappear.
244 The new database was created from data available on the World
246 Wide Web, using a new interactive editor based on NCAR Graphics.
247 There are plans to make this editor available, so that a
248 knowledgeable user can create a database tailored to his or her
249 own needs: for example (assuming that one can obtain the
250 necessary outline data), it should now be relatively easy to
251 create and use a Pangaea database with EZMAP.
252 A new package of routines is used to access "Earth..1" and other
254 databases in the same format; this package is called EZMAPB.
255 Conceptually, the EZMAPB routines are just part of EZMAP; they
256 use the same common blocks and many of the same underlying low-
257 level routines and they are affected by the same set of internal
258 parameters as the routines in EZMAP proper.
259 The principal EZMAPB routines are as follows:
261 · MPLNAM (MaP LiNes, to Area Map) - A routine to extract
263 boundary lines from a specified database and send them to an
264 area map.
265 · MPLNDM (MaP LiNes, Draw Masked) - A routine to extract
267 boundary lines from a specified database and draw them,
268 masked by the contents of an area map.
269 · MPLNDR (MaP LiNes, Draw) - A routine to extract boundary
271 lines from a specified database and draw them.
272 · MPLNRI - A routine to force the reading of certain
274 information from a database into labelled COMMON blocks
275 inside EZMAP, so that subsequent references to some of the
276 functions described below will have that information to work
277 with. (Each of the routines MPLNAM, MPLNDM, and MPLNDR
278 reads this data as a side effect; MPLNRI is provided for use
279 in cases in which none of the other three routines has yet
280 been called.)
281 As each of the EZMAPB routines MPLNAM, MPLNDM, and MPLNDR
283 processes boundary lines from a specified database, it calls an
284 EZMAPB routine named MPCHLN (the default version of which does
285 nothing):
286 · MPCHLN - A user-replaceable routine that can be made to
288 change line style, color, line width, and so on as the
289 boundary lines from a database are being drawn; it can also
290 be made to delete particular lines or to change the area
291 identifiers associated with them. The arguments of MPCHLN
292 tell it which of the EZMAPB routines is calling it and
293 whether it's being called before or after the line is
294 processed; they also supply the "line type" of the line
295 being drawn, the area identifiers of the areas on either
296 side of it, and the actual coordinates defining the line.
297 Line types are similar to area types (1 => land/water, 2 =>
298 continents, 3 => countries, 4 => states, and 5 => counties).
299 Another EZMAPB routine, named MPGLTY, may be called by the user
301 from within the line-processing routine specified by the final
302 argument in a call to MPLNDM:
303 · MPGLTY - Retrieves the line type of the line being drawn.
305 There is a group of EZMAPB functions providing access to
307 information about the areas defined by a database being used;
308 these may be referenced at any time the appropriate information
309 has been loaded into EZMAPB's common blocks (that is, after
310 calling one of MPLNAM, MPLNDM, MPLNDR, or MPLNRI), but they are
311 normally to be referenced from within the area-processing
312 routine specified as the final argument in a call to the AREAS
313 routine ARSCAM, in which they may be used to obtain information
314 determining the manner in which the areas are to be rendered:
315 · MPIPAI - A function whose value is non-zero if and only if
317 the area with a specified area identifier is part of the
318 area having a second specified area identifier.
319 · MPIPAN - A function whose value is non-zero if and only if
321 the area with a specified area identifier is part of the
322 area having a specified name.
323 · MPIOAR - A function whose value is the area identifier of
325 the smallest area that is defined at or above a specified
326 level in the area hierarchy and of which the area having a
327 specified area identifier is a part.
328 · MPIATY - A function whose value is the type of the area
330 having a specified area identifier.
331 · MPIPAR - A function whose value is the area identifier of
333 the parent of the area having a specified area identifier.
334 · MPISCI - A function whose value is the suggested color index
336 for an area having a specified area identifier.
337 · MPNAME - A function whose value is the name of the area
339 having a particular area identifier.
340 · MPFNME - A function whose value is the full name of the area
342 having a specified area identifier, up to a specified level
343 in the hierarchy of areas; the full name of an area consists
344 of its own name, preceded by the name of its parent,
345 preceded by the name of its parent's parent, and so on; the
346 various components of the name are separated by the
347 3-character string ' - ' (a blank, a dash, and another
348 blank).
349 Two additional EZMAPB functions are provided; these have nothing
351 to do with mapping, really, but can be useful in dealing with
352 character strings:
353 · MPIFNB - A function whose value is the index of the first
355 non-blank character in a character string.
356 · MPILNB - A function whose value is the index of the last
358 non-blank character in a character string.
359 Miscellaneous Other Routines
361 The following EZMAP routines are used for the purposes stated:
363 · MAPRS - Re-executes the "CALL SET" done during the last call
365 to MAPINT. This is useful when there has been an
366 intervening call to a utility that calls SET. It is quite
367 common for a background drawn by EZMAP to be placed in a
368 flash buffer (as created by the package "GFLASH"). When the
369 contents of the flash buffer are copied to the metafile
370 being created, if it is desired to draw something on the
371 EZMAP background, MAPRS may first have to be called to
372 ensure that the correct SET call is in effect.
373 · MPRST - Resets the internal state of EZMAP/EZMAPA to the
375 default.
376 · SUPMAP - Draws a map with a single call. An implementation
378 of the routine from which EZMAP grew.
379
381 #include <ncarg/ncargC.h>
382 c_mapaci
384 c_mapbla
385 c_mapdrw
386 c_mapfst
387 c_mapgrd
388 c_mapgrm
389 c_mapgtc
390 c_mapgtc
391 c_mapgti
392 c_mapgtl
393 c_mapgtr
394 c_mapint
395 c_mapiq
396 c_mapiqa
397 c_mapiqm
398 c_mapit
399 c_mapita
400 c_mapitm
401 c_maplbl
402 c_maplot
403 c_mappos
404 c_maproj
405 c_maprs
406 c_maprst
407 c_mapsav
408 c_mapset
409 c_mapstc
410 c_mapsti
411 c_mapstl
412 c_mapstr
413 c_maptra
414 c_maptri
415 c_maptrn
416 c_mapvec
417 c_mpfnme
418 c_mpglty
419 c_mpiaty
420 c_mpifnb
421 c_mpilnb
422 c_mpiola
423 c_mpiosa
424 c_mpipai
425 c_mpipan
426 c_mpipar
427 c_mpisci
428 c_mplnam
429 c_mplndm
430 c_mplndr
431 c_mplnri
432 c_mpname
433 c_mprset
434 c_supmap
435
437 The following EZMAP routines are used for the purposes stated:
438 · MAPUSR - This routine is called by various EZMAP routines
440 just before and just after drawing parts of the map. By
441 default, grid lines are drawn using software dashed lines
442 and geographical outlines are drawn using either solid lines
443 or dotted lines. The dash pattern used for the grid lines,
444 the flag which says whether outlines are solid or dotted,
445 and the color indices of various parts of the map are all
446 user-settable parameters, but more complete control of color
447 indices, spot size, dash pattern, etc., may be achieved by
448 supplying one's own version of MAPUSR; a user version may be
449 as complicated as is required to achieve a desired effect.
450 Note that this routine is not called by any of the EZMAPB
451 routines; they call MPCHLN instead.
452 · MAPEOD - This routine is called by the EZMAP routine MAPLOT
454 and by the EZMAPA routines MAPBLA and MAPBLM; in each case,
455 it is called once for each segment in the outline dataset.
456 The user may supply a version which examines the segment to
457 see if it ought to be plotted and, if not, to delete it.
458 This can be used (for example) to reduce the clutter in
459 northern Canada. Note that this routine is not called by
460 any of the EZMAPB routines; they call MPCHLN instead.
461 · MPCHLN - This routine is called by the EZMAPB routines
463 MPLNAM, MPLNDM, and MPLNDR; in each case, it is called just
464 before and just after the processing of each segment in the
465 map database. The default version does nothing; a user-
466 supplied version can do for the new databases what MAPUSR
467 and MAPEOD did for the old ones.
468
470 To use EZMAP Fortran or C routines, load the NCAR Graphics libraries
471 ncarg, ncarg_gks, and ncarg_c, preferably in that order.
472
474 When error conditions are detected, the support routine SETER is
475 called. By default, SETER writes a message to the standard error file
476 (as defined by I1MACH(4)) and then terminates execution. It is
477 possible to put SETER into recovery mode and regain control after a
478 recoverable error (which includes all of the possible errors).
479 The possible error messages are listed below. All errors are
481 recoverable in the sense that a user program which has called ENTSR to
482 set recovery mode will get control back after one of these errors
483 occurs.
484 MAPBLA - UNCLEARED PRIOR ERROR
486 MAPCHI - ERROR EXIT FROM GQPLCI
487 MAPCHI - ERROR EXIT FROM GQPMCI
488 MAPCHI - ERROR EXIT FROM GQTXCI
489 MAPDRW - UNCLEARED PRIOR ERROR
490 MAPFST - UNCLEARED PRIOR ERROR
491 MAPGCI - UNCLEARED PRIOR ERROR
492 MAPGRD - UNCLEARED PRIOR ERROR
493 MAPGRM - UNCLEARED PRIOR ERROR
494 MAPGTC - UNCLEARED PRIOR ERROR
495 MAPGTC - UNKNOWN PARAMETER NAME
496 MAPGTI - UNCLEARED PRIOR ERROR
497 MAPGTI - UNKNOWN PARAMETER NAME
498 MAPGTL - UNCLEARED PRIOR ERROR
499 MAPGTL - UNKNOWN PARAMETER NAME
500 MAPGTR - UNCLEARED PRIOR ERROR
501 MAPGTR - UNKNOWN PARAMETER NAME
502 MAPINT - ANGULAR LIMITS TOO GREAT
503 MAPINT - ATTEMPT TO USE NON-EXISTENT PROJECTION
504 MAPINT - MAP HAS ZERO AREA
505 MAPINT - MAP LIMITS INAPPROPRIATE
506 MAPINT - UNCLEARED PRIOR ERROR
507 MAPIO - EOF ENCOUNTERED IN OUTLINE DATASET
508 MAPIO - ERROR ON READ OF OUTLINE DATASET
509 MAPIQ - UNCLEARED PRIOR ERROR
510 MAPIQA - UNCLEARED PRIOR ERROR
511 MAPIQM - UNCLEARED PRIOR ERROR
512 MAPIT - UNCLEARED PRIOR ERROR
513 MAPITA - UNCLEARED PRIOR ERROR
514 MAPITM - UNCLEARED PRIOR ERROR
515 MAPLBL - UNCLEARED PRIOR ERROR
516 MAPLMB - UNCLEARED PRIOR ERROR
517 MAPLOT - UNCLEARED PRIOR ERROR
518 MAPPOS - ARGUMENTS ARE INCORRECT
519 MAPPOS - UNCLEARED PRIOR ERROR
520 MAPROJ - UNCLEARED PRIOR ERROR
521 MAPROJ - UNKNOWN PROJECTION NAME
522 MAPRS - UNCLEARED PRIOR ERROR
523 MAPRST - EOF ON READ
524 MAPRST - ERROR ON READ
525 MAPRST - UNCLEARED PRIOR ERROR
526 MAPSAV - ERROR ON WRITE
527 MAPSAV - UNCLEARED PRIOR ERROR
528 MAPSET - UNCLEARED PRIOR ERROR
529 MAPSET - UNKNOWN MAP AREA SPECIFIER
530 MAPSTC - UNCLEARED PRIOR ERROR
531 MAPSTC - UNKNOWN OUTLINE NAME
532 MAPSTC - UNKNOWN PARAMETER NAME
533 MAPSTI - UNCLEARED PRIOR ERROR
534 MAPSTI - UNKNOWN PARAMETER NAME
535 MAPSTL - UNCLEARED PRIOR ERROR
536 MAPSTL - UNKNOWN PARAMETER NAME
537 MAPSTR - UNCLEARED PRIOR ERROR
538 MAPSTR - UNKNOWN PARAMETER NAME
539 MAPTRA - UNCLEARED PRIOR ERROR
540 MAPTRI - UNCLEARED PRIOR ERROR
541 MAPTRN - ATTEMPT TO USE NON-EXISTENT PROJECTION
542 MAPTRN - UNCLEARED PRIOR ERROR
543 MAPVEC - UNCLEARED PRIOR ERROR
544 MPGETC - UNCLEARED PRIOR ERROR
545 MPGETI - UNCLEARED PRIOR ERROR
546 MPGETL - UNCLEARED PRIOR ERROR
547 MPGETR - UNCLEARED PRIOR ERROR
548 MPLNAM - Can't form name of ".names" file
549 MPLNAM - Can't open the ".lines" file
550 MPLNAM - Can't open the ".names" file
551 MPLNAM - Read bad index from ".names" file
552 MPLNAM - Read error on ".lines" file
553 MPLNAM - Read error on ".names" file
554 MPLNAM - UNCLEARED PRIOR ERROR
555 MPLNDM - Can't form name of ".names" file
556 MPLNDM - Can't open the ".lines" file
557 MPLNDM - Can't open the ".names" file
558 MPLNDM - Read bad index from ".names" file
559 MPLNDM - Read error on ".lines" file
560 MPLNDM - Read error on ".names" file
561 MPLNDM - UNCLEARED PRIOR ERROR
562 MPLNDR - Can't form name of ".names" file
563 MPLNDR - Can't open the ".lines" file
564 MPLNDR - Can't open the ".names" file
565 MPLNDR - Read bad index from ".names" file
566 MPLNDR - Read error on ".lines" file
567 MPLNDR - Read error on ".names" file
568 MPLNDR - UNCLEARED PRIOR ERROR
569 MPLNRI - Can't form name of ".names" file
570 MPLNRI - Can't open the ".names" file
571 MPLNRI - Read bad index from ".names" file
572 MPLNRI - Read error on ".names" file
573 MPLNRI - UNCLEARED PRIOR ERROR
574 MPRSET - UNCLEARED PRIOR ERROR
575 MPSETC - UNCLEARED PRIOR ERROR
576 MPSETI - UNCLEARED PRIOR ERROR
577 MPSETL - UNCLEARED PRIOR ERROR
578 MPSETR - UNCLEARED PRIOR ERROR
579 SUPCON - UNCLEARED PRIOR ERROR
580 SUPMAP - UNCLEARED PRIOR ERROR
581
584 Online: ezmap_params, mapaci, mapbla, mapblm, mapdrw, mapeod, mapfst,
585 mapgci, mapgrd, mapgrm, mapgtc, mapgti, mapgtl, mapgtr, mapint, mapiq,
586 mapiqa, mapiqd, mapiqm, mapit, mapita, mapitd, mapitm, maplbl, maplmb,
587 maplot, mappos, maproj, maprs, maprst, mapsav, mapset, mapstc, mapsti,
588 mapstl, mapstr, maptra, maptri, maptrn, mapusr, mapvec, mpchln, mpfnme,
589 mpgetc, mpgeti, mpgetl, mpgetr, mpglty, mpiaty, mpifnb, mpilnb, mpiola,
590 mpiosa, mpipai, mpipan, mpipar, mpisci, mplnam, mplndm, mplndr, mplnri,
591 mpname, mprset, mpsetc, mpseti, mpsetl, mpsetr, supmap, supcon,
592 ncarg_cbind
593 Hardcopy: NCAR Graphics Contouring and Mapping Tutorial; NCAR Graphics
595 Fundamentals, UNIX Version
596
598 Copyright (C) 1987-2007
599 University Corporation for Atmospheric Research
600 This documentation is free software; you can redistribute it and/or
602 modify it under the terms of the GNU General Public License as
603 published by the Free Software Foundation; either version 2 of the
604 License, or (at your option) any later version.
605 This software is distributed in the hope that it will be useful, but
607 WITHOUT ANY WARRANTY; without even the implied warranty of
608 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
609 General Public License for more details.
610 You should have received a copy of the GNU General Public License along
612 with this software; if not, write to the Free Software Foundation,
613 Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
614UNIX March 1993 Ezmap(3NCARG)