ANAM: Programs for Analysis of Magnetic Anomaly Data

Japanese

 1.   One file consists of 1 set of GRID data, or multiple sets of GRID data.
    The 2nd set or further behind of multiple sets of GRID data is restricted
    in usage, and is valid only for cases below.
      (1) 1st set GRID data indicates a distribution of any physical quantity
        on a curved surface, and the altitude distribution of the surface is
        given by 2nd set GRID data.
      (2) The file consists of a series of independent GRID data, and they are
        not used for other than illustrating each distribution.
 2.   The unit for the physical quantity (grid data) is, in principle,
    nT for magnetic field, m for altitude, 0.01 A/m for magnetization, mGal
    for gravity, or others as derived from them.  And it is recommended to use
    the value of positive 99999 in effective digits for representing null
    value (the lack of valid data).
 3.   Every data line in GRID data file may not exceed 80 bytes excluding LF
    code.  And it is recommended to be 79 bytes or less excluding LF.
 4.   Data in GRID data file may not include multi-byte characters, and
    control codes other than LF shall not be used.

Each set of GRID data is constructed as follows.
a) Comment: Before 1st Header, arbitrary lines of comment can be placed.
        Comment line has "#" on the 1st column and is 80 byte long at most.
b) 1st Header (Areaname and information of map projection)  [fixed format]
      FORMAT(a8, 4x,i4, 2i8, 2i8)
  area: 8 byte string representing Areaname or else, not starting with "#".
  nc:   coordinate number of map projection (usually UTM zone number)
            0 : Japanese transverse Mercator coordinates
         1-60 : UTM coordinates zone number
           61 : North pole UPS coordinates
           62 : South pole UPS coordinates
           65 : UTM coordinates with non-standard central meridian
           70 : Mercator projection
           71 : Lambert conformal conic projection (1 standard parallel)
           72 : Lambert conformal conic projection (2 standard parallels)
          100 : Lambert Azimuthal Equal-Area Projection
                (from the sphere with surface area equal to the earth)
          109 : Lambert Azimuthal Equal-Area Projection
                (from the sphere with equatorial radius equal to the earth)
          199 : Latitude/Longitude in minutes are regarded as distance in km
        These numbers above are for GRS ellipsoid (WGS-ITRF).
        For Bessel ellipsoid (Old Tokyo datum), add 800 to the corresponding
        projection.
  ig, kg : Latitude and Longitude (in minutes) of origin
            [neglected for nc = 1 to 62]
  i1, i2 : Latitudes (in minutes) of standard parallels
            [valid only when nc = 72]
    In general, coordinate values are X (Northing) = Y (Easting) = 0 at the
    origin.  However, in UTM (nc = 1 to 60, or 65) X = 0, Y = 500,000 (m), and
    in UPS (nc = 61 or 62) X = Y = 2,000,000 (m), at the origin.
c) 2nd Header (Grid information, null value and altitude)  [free format]
      FORMAT(2i12, 2i6, 2i6, 1x,f7.1, 1x,f7.0)   (as standard)
  ixs, iys : Northing and Easting (in m) of Southwest corner of GRID  [integer]
  mszx,mszy: mesh size (in m) towards North and East                  [integer]
  mxn, myn : mesh count (including both ends) towards North and East  [integer]
  vnul :     special value representing the lack of valid data        [real]
  alt :      observation altitude (in m)                              [real]
              (If the value = 0., the distribution of observation surface is
               given as 2nd set GRID data, and if negative (-1.), the altitude
               of observation is undefined.  For the 2nd set GRID data (i.e.,
               altitude data) this is filled with -1., though meaningless.)
d) GRID data body  [free format]
      FORMAT((f7.1, 9(1x,f7.1)))   (as standard)
  All grid data are listed out in the order that starts from Southwest corner
  toward North, and on arriving North end proceeds to next East row.
  Next expression is the equivalent FORTRAN statement reading this data.
        read(10,*) ((f(i,k),i=1,mxn),k=1,myn)
  However, for the output programming, line break operation between rows
        do k=1,myn
          write(10,'((f7.1,9(1x,f7.1)))') (f(i,k),i=1,mxn)
        enddo
  is recommended.

# Areaname: Kobe-Kyoto
# Survey Date: 1995.12.07-12.27
&A-01
  2079.02221N  8116.27649E   277.87m   -45.15nT
  2079.04052N  8116.31640E   278.58m   -44.66nT
  2079.05883N  8116.35641E   279.19m   -44.47nT
        .......
  2087.39584N  8134.25592E   275.40m   -48.38nT
  2087.41585N  8134.29643E   275.41m   -53.69nT
&    C-2r
  2088.27126N  8134.37994E   279.12m   -44.90nT
  2088.25637N  8134.33845E   279.33m   -40.81nT
  2088.24078N  8134.29646E   279.64m   -40.12nT
        .......

     Lines starting with '#' are comment information, usually placed only at
       the head of the file.  (Never be placed among series of line data.)
     Lines starting with '&' or '%' indicate the start of line data.
       Line name (number) is described in 2nd-9th columns, and the form of
       the rest is not restricted.  (Starting time and number of data points
       included are commonly described.)
       In some cases, a line with no data points is defined for explicit
       declaration of the end of file.
     All other lines are data of individual points, consisting of Latitude
       (in minutes), Longitude (in minutes), Altitude (in m), and Residual
       magnetic anomaly (in nT) data, with the format (47 columns) of
          format(1x, f11.5, 1hN,1x, f11.5, 1hE,1x, f8.2, 1hm,1x, f8.2, 2hnT)
       while number of columns of each data may be different for input data.