DPAM: Programs for Aeromagnetic Survey
Observation Data Processing
Japanese
| Program Name | Function |
|---|
| alog2asc |
Convert AIRLOGS airborne binary raw data into
Common ASCII obs.data Format, with correcting
PC's Time data by GPS and converting GPS-time (UTC) into Localtime.
| |
Parameters: |
log filename
input binary data filename
output ASCII data filename
Localtime zone ([+/-]HHMM) |
|
| daq2asc |
Convert AMDAQ raw data into
Common ASCII obs.data Format, with correcting
PC's Time data by GPS and converting GPS-time (UTC) into Localtime.
| |
Parameters: |
log filename
input AMDAQ obs.data filename
output ASCII data filename
Localtime zone ([+/-]HHMM) |
|
| bdaq2asc |
Convert AMBDAQ raw data into
Common ASCII obs.data Format, with correcting
PC's Time data by GPS and converting GPS-time (UTC) into Localtime.
| |
Parameters: |
log filename
input AMBDAQ obs.data filename
output ASCII data filename
Localtime zone ([+/-]HHMM) |
|
| dmaq2asc |
Convert G858+GPS downloaded raw data into
Common ASCII obs.data Format, with correcting
G858 Time data by GPS and converting GPS-time (UTC) into Localtime.
| |
Parameters: |
log filename
input G858+GPS obs.data filename
output ASCII data filename
Localtime zone ([+/-]HHMM) |
|
| filtadasc |
Filter out high-frequency noise component from the ADC 8ch data in
Common ASCII obs.data, with a boxcar averaging
of [2n+1] data.
| |
Parameters: |
log filename
input Common ASCII obs.data filename
output Common ASCII obs.data filename
half-width of filter window (n) |
|
| xldam |
Generate DPAM line data file from airborne
Common ASCII obs.data making use of
Real-time GPS position data included, with calculation of IGRF residuals.
Also, the correction of Mag.Sensor offset from GPS can be done.
| |
Parameters: |
log filename
filename of survey line information data
output DPAM line data filename
survey year
IGRF generation number
thin-out ratio N (crop 1 out of N data)
Mag.Sensor offset [forward, starboard, downward] (m) or a blank line
(In case all 3 values equal 0. or a blank line, no correction
shall be done.) |
Filename of input Common ASCII obs.data is specified in the
survey line information data. |
| xldpn |
Generate DPAM line data file from airborne
Common ASCII obs.data and PostNav
GPS position data, with calculation of
IGRF residuals.
Also, the correction of Mag.Sensor offset from GPS can be done.
| |
Parameters: |
log filename
filename of survey line information data
Time spec of Pos. data (Localtime(0) or UTC(1))
[if UTC(1)] Localtime Time-zone string
output DPAM line data filename
survey year
IGRF generation number
thin-out ratio N (crop 1 out of N data)
Mag.Sensor offset [forward, starboard, downward] (m) or a blank line
(In case all 3 values equal 0. or a blank line, no correction
shall be done.) |
Filenames of input Common ASCII obs.data and PostNav GPS position data
are specified in the survey line information data.
|
| xldhg |
Generate HGAM line data file (similar to DPAM line
data) from helicopter-borne gradiometer AM (HGAM) data, making use of
HGAM bird-mag data and Real-time or PostNav
GPS position data, with diurnal correction by
GSmag data and calculation of IGRF residuals.
| |
Parameters: |
log filename
filename of survey line information data
Pos. data spec.: 0(PNAV-DGPS) or 1(Real-time)
Time spec of Pos. data (UTC(1) or Localtime(0))
[if UTC(1)] Localtime Time-zone string
input GSmag data filename
output DPAM line data filename
survey year
IGRF generation number
magnetic sensors vertical separation (m)
thin-out ratio N (crop 1 out of N data) |
Filenames of input HGAM bird-mag data and Real-time/PostNav GPS position
data are specified in the survey line information
data. |
| despike |
Eliminate magnetic field spike noise in
DPAM line data.
| |
Parameters: |
log filename
input DPAM line data filename
output DPAM line data filename |
|
| dvcorr |
Correct for magnetic field diurnal variation in
DPAM line data, making use of
GSmag data.
| |
Parameters: |
log filename
input DPAM line data filename
input GSmag data filename
output DPAM line data filename |
|
| ecomp |
Execute compensation of aircraft magnetic effect for CompBox
DPAM line data, using line data of CompBox flight
itself. (Test purpose)
| |
Parameters: |
log filename
filename of DPAM CompBox data
output DPAM line data filename |
|
| fcomp |
Execute compensation of aircraft magnetic effect for Survey
DPAM line data,
using DPAM line data of CompBox flight.
| |
Parameters: |
log filename
filename of DPAM CompBox data
filename of input DPAM survey line data
filename of output DPAM survey line data |
|
| ggrid |
Generate magnetic field grid data from DPAM line
data or equivalent, by the method developed by Smith and Wessel [1990].
| |
Parameters: |
log filename
input AM line data file-type (*1)
input AM line data filename
Geodetic system of input data [WGS(1) or TYO(2)]
[if random file] data formatting parameter (*2)
effecting radius (km)
areaname label
map projection coordinate number
grid location parameters (*3)
output grid filename |
|
| ggrids |
Generate grid data of magnetic field and observation altitude from
DPAM line data or equivalent, by the method
developed by Smith and Wessel [1990].
| |
Parameters: |
log filename
input AM line data file-type (*1)
input AM line data filename
Geodetic system of input data [WGS(1) or TYO(2)]
[if WGS(1)] Altitude Reference [GRS(1) or Geoid(2)] (*4)
[if Geoid(2)] Geoid model [0:NGA or Model name] (*4)
[if random file] data formatting parameter (*2)
effecting radius (km)
areaname label
map projection coordinate number (NC)
[if NC < 200] Alt.Reference of output [GRS(1) or Geoid(2)] (*4)
[if Geoid(2)] Geoid model [0:NGA or Model name] (*4)
grid location parameters (*3)
output grid filename |
|
| pframe |
Draw map of coordinates framework of survey area.
(For easier setting of grid location parameters.)
| |
Parameters: |
log filename
output PS filename
areaname
map projection coordinate number
Latitude/Longitude range
drawing parameter |
|
| pltrk |
Draw trackline paths from DPAM line data or
equivalent.
| |
Parameters: |
log filename
input AM line data file-type (*1)
input AM line data filename
Geodetic system of input data [WGS(1) or TYO(2)]
[if random file] data formatting parameter (*2)
output PS filename
areaname
map projection coordinate number
location parameters
drawing parameters |
|
| pchkdv |
Plot Ground station magnetic field data.
| |
Parameters: |
log filename
input GSmag data filename
output PS filename |
|
| pchkmag |
Plot magnetic total field data of DPAM line data,
HGAM line data, HGAM bird mag. data
or Common ASCII obs. data (in black).
| |
Parameters: |
log filename
data type (1:DPAM, 1/2:HGAM(1st/2nd), 3/4: HeliBird(1st/2nd)
or 0:CommonASCIIobs.)
input filename (DPAM/HGAM line / HGAM bird mag.
or Common ASCII obs. data)
output PS filename |
|
| pchkres |
Plot IGRF residual (or difference) magnetic field data of
DPAM line data or HGAM line data
(in blue).
| |
Parameters: |
log filename
data type (1:DPAM, or 1/2/3:HGAM(1st/2nd/diff))
input DPAM/HGAM line data filename
output PS filename |
|
| pchkcomp |
Plot IGRF residual magnetic field data before and after the compensation
of aircraft magnetic effect, for the output DPAM file from the process
ecomp/fcomp.
| |
Parameters: |
log filename
input DPAM line data filename
output PS filename |
|
| xslin |
Convert various format line data
into StdLIN standard line data.
| |
Parameters: |
log filename
input AM line data file-type (*1)
input AM line data filename
Geodetic system of input data [WGS(1) or TYO(2)]
[if WGS(1)] Altitude Reference [GRS(1) or Geoid(2)] (*4)
[if Geoid(2)] Geoid model [0:NGA or Model name] (*4)
[if generic random file] data formatting parameter (*2)
output StdLIN data filename
Geodetic system of output data [WGS(1) or TYO(2)]
[if WGS(1)] Altitude Reference [GRS(1) or Geoid(2)] (*4)
[if Geoid(2)] Geoid model [0:NGA or Model name] (*4) |
|
| xslina |
Extract StdLIN line data with averaged re-sampling
from DPAM line data.
| |
Parameters: |
log filename
input DPAM line data filename
Geodetic system of input data [WGS(1) or TYO(2)]
[if WGS(1)] Altitude Reference [GRS(1) or Geoid(2)] (*4)
[if Geoid(2)] Geoid model [0:NGA or Model name] (*4)
time interval of averaged re-sampling (sec.)
output StdLIN data filename
Geodetic system of output data [WGS(1) or TYO(2)]
[if WGS(1)] Altitude Reference [GRS(1) or Geoid(2)] (*4)
[if Geoid(2)] Geoid model [0:NGA or Model name] (*4) |
|
| (*1) |
There are variations of file types of AM line data as follows:
1: DPAM survey line data, 2: AMDB-GSJ located line data,
3: AMDB-NEDO integrated located data, 4: StdLIN standard line data,
0: generic random point data.
The detail of generic random point data file is specified by the data
formatting parameter (*2). |
| (*2) |
Data formatting parameter includes the unit [minute(1),
degree(2) or Deg:Min(3)] of latitudes/longitudes, and the sequence numbers
for latitude, longitude, altitude (in m) and magnetic field (in nT) data
in the free-format data string (when ':' delimiter has been replaced with
space). |
| (*3) |
"grid location parameters" include Northing and Easting of
Southwest corner, mesh interval and number of mesh to the North, and
to the East. |
| (*4) |
If Geodetic system is TYO(2) [Tokyo-Datum], altutude reference
must be Geoid, while it may be selectable from ITRF-GRS(1) and Geoid(2)
if Geoditic system is WGS(1), and the Geoid model is selectable from 0:NGA
and another name (if geoid data is prepared) when Geoid(2) is selected.
Here the altitude in Tokyo-Datum is assumed to be equal to the elevation
from Geiod. When the altitude reference is different between input and
output data, conversion of ellipsoidal heights to/from elevations from
Geoid (or height translation between different Geoid models) is performed,
using 'libgm' function "hgeoid/sgeoid". |
AM raw obs.data file Format
- AIRLOGS binary data
♦ After the 232 bytes Header, data blocks are placed.
♦ Header (232 bytes) consists of 29 8-byte real binary values, i.e.,
Version#, Date(Windows style), Julian day, Year, Month, Day,
Hour, Minute, Second, Sub-second, Sensor-typw(0/1), Flight#,
Cycle intv.(sec.), and 16 coeff values of ADC 8ch calibration.
♦ The length of data block is 68 bytes or 98 byte depending on the
condition that the 4th byte of the block is 0 (: 68 bytes) or else.
♦ The contents of 5th to 68th byte are 4 8-byte real values (Fiducial#,
System time, t200 value, Mag. intensity [nT]) and 8 4-byte real values
(8ch ADC data corresponding to Fluxgate data [3 components], Radio Alt.,
Baro-alt., and Auxiliary analog input [3 components]).
"t200" value seems a kind of fiducial number only unknown.
♦ The contents of 69th to 98th byte are 3 8-byte real values of UTC
[hhmmss.sss], Latitude[dddmmss.ss], Longitude[dddmmss.ssss] and 1 4-byte
real value of Altitude, 2 1-byte integer values of Pos. method code and
Number of Sats used.
- AMDAQ acqisition raw data (Stinger type AM survey)
/AMDAQ ver.2014-09-19 by T.Nakatsuka (GSJ)
/DateTime: 2014-11-26 14:53:44 (Logging start)
/CyclingInterval: 100 mSec (60 mSec Gate-time)
/GyromagneticRatioUsed: 3.498577 Hz/nT (Scintrex)
M 53624.35 00027.11 45451.232 -3.657+2.026+1.548+0.010+4.243+0.010+0.005+0.005
M 53624.45 00027.21 45451.061 -3.652+2.036+1.548+0.000+4.238+0.010+0.005+0.005
M 53624.55 00027.31 45451.150 -3.652+2.031+1.548+0.005+4.248-0.005+0.005+0.005
M 53624.65 00027.41 45450.871 -3.657+2.026+1.548+0.000+4.248+0.005+0.005+0.005
S 53624.59 00027.35$GPGGA,055345.00,3515.0110,N,13655.3893,E,1,16,0.8,15.38,M,37.80,M,,*55^M
M 53624.74 00027.51 45451.003 -3.652+2.036+1.543+0.010+4.248+0.010+0.005+0.005
M 53624.85 00027.61 45450.811 -3.657+2.031+1.543+0.005+4.258+0.005+0.005+0.005
M 53624.95 00027.71 45451.083 -3.657+2.031+1.548+0.005+4.238+0.010+0.005+0.005
M 53625.05 00027.81 45451.211 -3.657+2.031+1.543-0.005+4.243-0.005+0.005+0.005
:
:
Preceding 4 lines are Header Comments.
M record consists of 'M', ReceiveTime(sec.), Fiducial number, Mag.Intensity, and 8 values of ADC.
S record consists of 'S', ReceiveTime(sec.), Fiducial number, and $GPGGA record from GPS.
($GPGGA record includes: '$GPGGA', UTC time[hhmmss.ss], Latitude[ddmm.mmmm], 'N', Longitude
[dddmm.mmmm], 'E', Pos. method code, Number of Sats used, Hor. accuracy index (HDOP),
Antenna height, 'M', Geoid height, 'M', , '*' check-sum '^M'.)
- AMBDAQ acqisition raw data (Bird type AM or other mobile survey)
/AMBDAQ by T.Nakatsuka (GSJ) ver.2007NOV22
/DateTime: 2007-11-23 09:12:04 (Logging start)
:
:
36411.16,0, 46741.827, 0.000,10:06:52.45,11/23/07, 0
36411.26,0, 46743.765, 0.000,10:06:52.55,11/23/07, 0
36411.36,0, 46745.239, 0.000,10:06:52.65,11/23/07, 0
36411.46,0, 46746.836, 0.000,10:06:52.75,11/23/07, 0
36411.56,0, 46748.750, 0.000,10:06:52.85,11/23/07, 0
36411.66,0, 46750.397, 0.000,10:06:52.95,11/23/07, 0,36411.54,$GPGGA,010653.00,3526.0033,N,13850.1248,E,1,08,1.2,1206.08,M,38.12,M,,*51
36411.76,0, 46751.727, 0.000,10:06:53.05,11/23/07, 0
36411.86,0, 46753.094, 0.000,10:06:53.15,11/23/07, 0
36411.96,0, 46754.179, 0.000,10:06:53.25,11/23/07, 0
36412.06,0, 46755.981, 0.000,10:06:53.35,11/23/07, 0
36412.16,0, 46757.653, 0.000,10:06:53.45,11/23/07, 0
:
:
Preceding 2 lines are Header Comments.
Each of the rest records consists of 7 items separated by comma
(ReceiveTime(sec.), 0, Mag.Intensity-1, Mag.Intensity-2, Time(hh:mm:ss.tt),
Date(MM/DD/YY), and 0), and a set of ReceiveTime(sec.) and GPS $GPGGA record
might follow if received at that timing. (See the "AMDAQ acqisition raw data"
above for the contents of $GPGGA record.)
- G858+GPS acqisition raw data (Small multicopter magnetic survey)
6 0.000 0.000 14:50:47.500 11/30/16 7599 1 1 5 0
0 46214.218 0.000 14:50:47.500 11/30/16 0
21 $GPGGA,055047.00,3533.4110,N,14023.9125,E,1,15,0.7,3.28,M,33.30,M,,*6F 14:50:47.400 11/30/16 65 0
0 46214.335 0.000 14:50:47.400 11/30/16 0
0 46214.455 0.000 14:50:47.300 11/30/16 0
0 46214.646 0.000 14:50:47.200 11/30/16 0
0 46214.663 0.000 14:50:47.100 11/30/16 0
0 46214.932 0.000 14:50:47.00 11/30/16 0
0 46215.002 0.000 14:50:46.900 11/30/16 0
0 46215.400 0.000 14:50:46.800 11/30/16 0
0 46215.644 0.000 14:50:46.700 11/30/16 0
0 46215.778 0.000 14:50:46.600 11/30/16 0
0 46216.190 0.000 14:50:46.500 11/30/16 0
21 $GPGGA,055046.00,3533.4110,N,14023.9126,E,1,15,0.7,3.40,M,33.30,M,,*63 14:50:46.400 11/30/16 66 0
0 46216.671 0.000 14:50:46.400 11/30/16 0
0 46217.048 0.000 14:50:46.300 11/30/16 0
0 46217.265 0.000 14:50:46.200 11/30/16 0
:
:
0 45980.890 0.000 14:20:37.800 11/30/16 0
0 45980.962 0.000 14:20:37.700 11/30/16 0
0 45980.293 0.000 14:20:37.600 11/30/16 0
0 45979.364 0.000 14:20:37.500 11/30/16 0
21 $GPGGA,052037.00,3533.4097,N,14023.9110,E,1,13,0.8,7.46,M,33.30,M,,*62 14:20:37.500 11/30/16 208 0
0 45978.507 0.000 14:20:37.400 11/30/16 0
0 45977.638 0.000 14:20:37.300 11/30/16 0
0 45974.065 0.000 14:20:37.200 11/30/16 0
6 0.000 0.000 14:20:36.900 11/30/16 0 0 0 36 0
Common ASCII obs.data Format (Example of "daq2asc" output)
//daq2asc v.2017-10-16 by T. Nakatsuka
//InputDataFilename: /home/nktk/data/Tfield/20150622_085808.daq
//PC-Time data were Shifted by +0.47 sec.
/AMDAQ ver.2014-09-19 by T.Nakatsuka (GSJ)
/DateTime: 20150622 08:58:08 (Logging start)
/CyclingInterval: 100 mSec (60 mSec Gate-time)
/GyromagneticRatioUsed: 3.498577 Hz/nT (Scintrex)
/ FID SYSTIME t200 MAG FGx FGy FGz Ralt Balt AD6 AD7 AD8 LTsec LAT LON ALT Q N
:
:
134.9 08:59:40.85 134.910 44022.322 -3.965 -0.605 2.588 0.010 0.233 0.024 0.005 0.000 * * * * * *
135.0 08:59:40.94 135.010 44021.805 -3.901 -0.630 2.559 0.005 0.238 0.000 0.010 0.005 * * * * * *
135.1 08:59:41.05 135.110 44024.093 -3.901 -0.601 2.549 0.005 0.238 -0.005 0.005 0.005 32381.00 34.5741050 135.8166467 265.24 1 17
135.2 08:59:41.14 135.210 44020.111 -3.887 -0.645 2.520 0.005 0.238 0.020 0.005 0.005 * * * * * *
135.3 08:59:41.25 135.310 44018.997 -3.955 -0.605 2.573 0.000 0.233 -0.015 0.005 0.005 * * * * * *
135.4 08:59:41.35 135.410 44022.616 -3.970 -0.654 2.578 0.010 0.243 -0.015 0.005 0.005 * * * * * *
135.5 08:59:41.44 135.510 44025.231 -3.960 -0.615 2.593 0.010 0.233 -0.015 0.005 0.005 * * * * * *
135.6 08:59:41.55 135.610 44018.321 -3.950 -0.571 2.603 -0.005 0.238 0.015 0.005 0.000 32381.50 34.5741050 135.8166467 265.23 1 17
135.7 08:59:41.64 135.710 44020.228 -3.950 -0.576 2.520 0.000 0.233 -0.010 0.005 0.005 * * * * * *
135.8 08:59:41.75 135.810 44019.916 -3.950 -0.649 2.515 0.000 0.233 -0.010 0.005 0.000 * * * * * *
:
:
153.5 08:59:59.44 153.510 44394.005 -3.975 -0.591 2.588 0.000 0.224 0.010 0.005 0.005 * * * * * *
153.6 08:59:59.55 153.610 44933.933 -3.960 -0.645 2.510 0.005 0.243 -0.005 0.005 0.000 32399.50 34.5741050 135.8166483 265.30 1 17
153.7 08:59:59.64 153.710 45287.924 -3.940 -0.625 2.559 0.000 0.194 -0.010 0.010 0.005 * * * * * *
153.8 08:59:59.75 153.810 44750.706 -3.970 -0.610 2.603 0.005 0.258 0.005 0.005 0.000 * * * * * *
153.9 08:59:59.85 153.910 44848.155 -3.901 -0.605 2.515 0.005 0.263 -0.010 0.005 0.005 * * * * * *
154.0 08:59:59.94 154.010 44516.191 -3.916 -0.635 2.529 0.005 0.248 0.024 0.005 0.005 * * * * * *
154.1 09:00:00.05 154.110 44512.921 -3.970 -0.625 2.607 0.000 0.248 -0.010 0.005 0.005 32400.00 34.5741050 135.8166483 265.31 1 17
154.2 09:00:00.14 154.210 44779.757 -3.901 -0.552 2.612 0.005 0.175 0.034 0.005 0.005 * * * * * *
:
:
156.5 09:00:02.44 156.510 43976.703 -3.882 -0.566 2.529 0.005 0.277 -0.015 0.005 0.005 * * * * * *
156.6 09:00:02.55 156.610 43987.158 -3.887 -0.615 2.515 0.010 0.121 0.034 0.005 0.005 32402.50 34.5741017 135.8166417 264.79 1 16
156.7 09:00:02.64 156.710 43995.208 -3.906 -0.649 2.622 0.000 0.302 0.020 0.005 0.005 * * * * * *
156.8 09:00:02.75 156.810 44004.666 -3.979 -0.562 2.627 -0.005 0.297 -0.010 0.005 0.000 * * * * * *
156.9 09:00:02.85 156.910 44007.559 -3.950 -0.571 2.593 0.000 0.346 0.015 0.005 0.005 * * * * * *
157.0 09:00:02.94 157.010 43997.328 -3.892 -0.664 2.515 0.005 0.341 0.005 0.005 0.005 * * * * * *
157.1 09:00:03.05 157.110 44007.911 -3.916 -0.654 2.578 0.000 0.414 0.010 0.005 0.005 32403.00 34.5741017 135.8166417 264.79 1 16
157.2 09:00:03.14 157.210 44012.890 -3.945 -0.654 2.520 0.000 0.331 0.010 0.005 0.005 * * * * * *
:
:
Ground station magnetic field data (example)
/Base: 46490 <-- Baseline value (nighttime value of quiet day) (*)
/Date: 20030215 <-- Date (8 columns of "yyyymmdd") (*)
130008 464795
130023 46480
130038 464795
130053 4648030 <-- Acquired data from ground station magnetometer
130108 46480.5 <-- 6 cols Time "HHMMSS", 1 col (or more) space,
130123 46480.71 <-- and magnetic field (in 1nT, 0.1nT or 0.01nT unit)
130138 464806.1
130153 4648052.
.......
(*) If Baseline value and/or Date is specified in the midst of file,
it is effective rearward.
PostNav DGPS / Real-time GPS position data
(example)
12:51:11.000 35.0960951 137.6353737 983.83
12:51:12.000 35.0963192 137.6353688 985.57
12:51:13.000 35.0965443 137.6353639 987.19
.......
14:14:46.00 36.4404884 138.5358380 1408.51
14:14:47.00 36.4404885 138.5358380 1408.50
14:14:48.00 36.4404886 138.5358380 1408.47
.......
All lines are GPS position data in free format consisting of Localtime,
latitude (in degrees), longitude (in degrees) and altitude (in m).
Time data must be in the form of "HH:MM:SS.tt".
Survey line information data (example)
=030217f1.asc 030217f1.pnav
220 095250 100100 0
210 100330 101000 180
200 101210 101950 0
.......
140 111210 112050 0
130 112340 113120 180
=030217f2.asc 030217f2.pnav
120 121300 122010 0
110 122235 122840 180
100 123105 123850 0
.......
Lines starting with '=' on the 1st column specify data files,
giving filenames of Common ASCII obs.data and GPS position data.
(Prog. xldam does not require filename of GPS position data.)
All other lines are individual survey line information, i.e.,
Line name, Start time, End time, and Flying direction (azimuth in
degrees) separated by space.
(The time format is "hhmmss.tt", where ".tt" can be omitted.)
Flying direction data may be omitted if the correction of
Mag.Sensor offset is not executed.
Various Line data File Format
There is variations of AM line data file formats, as follows.
1) DPAM line data file
2) AMDB-GSJ located line data file
3) AMDB-NEDO integrated located data file
4) StdLIN standard line data file
0) Generic random point data file
In the file format of 2 and 3, latitude and longitude values are referred to
WGS (World Geodetic System), and altitude values are elevation from the Geoid.
However, there is no such rule in other types of format, and the user has to
specify the sort of geodetic system, etc.
The format type 0 is one for manipulating general versatile data, and the
unit of latitude and longitude values and the sequence of each data are to be
specified. In this case, the data line must consist of mumeric data only, with
an exception that ":" is treated as a data seperator sama as a space.
Commonly, individual point data consists 1 line data, the 1st column of
which is a blank or the 1st digit of a value. To indicate the start of new
line with any attribute information, there is a header line starting with
"&", "#" or "%" at the 1st column. Also, there may exist some comment
lines starting with "#".
(Accordingly, the omission of lines starting with "&", "%" and "#" gives
the series of valid point data.)
StdLIN line data format (example)
# 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.
DPAM line data format (example)
# Areaname: Ootoge
# Survey Date: 2003.02.17
&220 20030217 95250.00 100100.00
418860 20030217 95250.02 3 35.0885765 137.7122326 1033.28 46445.27 -50.13 -3.535 2.783 1.099 35570.02
418870 20030217 95250.09 3 35.0885932 137.7122356 1033.31 46445.02 -50.39 -3.525 2.783 1.108 35570.09
418880 20030217 95250.17 3 35.0886091 137.7122389 1033.34 46445.90 -49.51 -3.545 2.781 1.084 35570.17
.......
494660 20030217 100059.89 3 35.2059824 137.7122510 1258.37 46440.41 -115.48 -3.560 2.891 0.713 36059.89
494670 20030217 100059.95 3 35.2059986 137.7122531 1258.30 46439.93 -115.95 -3.555 2.874 0.708 36059.95
&210 20030217 100330.00 101000.00
517780 20030217 100330.09 3 35.2047662 137.7067634 1247.53 46418.68 -138.34 -3.281 -3.225 -0.249 36210.09
517790 20030217 100330.19 3 35.2047375 137.7067660 1247.46 46418.48 -138.52 -3.296 -3.230 -0.273 36210.19
517800 20030217 100330.29 3 35.2047093 137.7067705 1247.39 46418.52 -138.47 -3.286 -3.210 -0.288 36210.29
.......
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,
describing Line name (number), Date "yyyymmdd" and Start/End time.
Time data is double precision value in the form of "HHMMSS.tt".
All other lines are data of individual points (115 columns + LF).
format(i8, 1x,i8, 1x,f9.2, 1x,i2, 1x,f11.7, 1x,f12.7, 1x,f7.2,
* 2(1x,f8.2), 3(1x,f7.3), 1x,f9.2)
1) Fiducial number, 2) Date (yyyymmdd), 3) Time (HHMMSS.tt),
4) Data spec.(*), 5) Latitude (Deg.), 6) Longitude (Deg.),
7) Altitude (m), 8) Magnetic field (nT), 9) IGRF residual (nT),
10-12) Fluxgate 3 components values (V),
13) Localtime seconds (number of seconds from 00:00)
In case of output from ecomp/fcomp, following data related to the
aircraft magnetic field compensation are added with format (4(1x,f8.2)).
14) residual before compensation (tres),
15) correction for aircraft magnetic field (corr),
16) random variation component (rand),
17) linear trend component (trend),
[tres = corr + rand + trend]
(*) Meaning of Data spec.(k) :
k = 4,5,6,7 : 5) Lat., 6) Long., 7) Alt. are from Real-time GPS
k = 0,1,2,3 : 5) Lat., 6) Long., 7) Alt. are from PostNav DGPS
k = 2,3,6,7 : 8) Mag.F, 9) IGRFres. are not diurnal corrected yet
k = 0,1,4,5 : 8) Mag.F, 9) IGRFres. are diurnal corrected already
k = 1,3,5,7 : 8) Mag.F, 9) IGRFres. are not AMF compensated yet
k = 0,2,4,6 : 8) Mag.F, 9) IGRFres. are AMF compensated already
Bird-mag data and Line data in Helicopter-borne gradiometer AM (HGAM)
[ HGAM bird-mag data format ] (example)
.......
20051012 09:14:51.10 99999.99 46949.90
20051012 09:14:51.20 99999.99 46949.89
20051012 09:14:51.30 99999.99 46949.85
20051012 09:14:51.40 46781.33 46949.85
20051012 09:14:51.50 99999.99 46949.79
20051012 09:14:51.60 99999.99 46949.77
20051012 09:14:51.70 46795.16 46949.70
20051012 09:14:51.80 46850.40 46949.78
20051012 09:14:51.90 46851.73 46949.73
20051012 09:14:52.00 46851.76 46949.70
.......
Each data consists of Date (yyyymmdd), Time (HH:MM:SS.tt),
Total force magnetic field at 1st sensor (nT), and
Total force magnetic field at 2nd sensor (nT),
with the form (41 columns + LF) as follows.
format(1x, i8, 1x, i2,1h:,i2,1h:,f5.2, 1x, f9.2, 1x, f9.2)
[ HGAM line data format ] (example)
&F13 20051012 142618.00 152530.00
1893030 20051012 142618.00 80 36.4324162 138.4260987 2285.58 46934.03 -58.27 46936.09 -56.09 -2.06
1893040 20051012 142618.10 80 36.4323834 138.4261012 2285.41 46934.69 -57.58 46936.12 -56.03 -1.43
1893050 20051012 142618.20 80 36.4323596 138.4261236 2285.44 46935.28 -56.97 46936.75 -55.38 -1.47
.......
2248210 20051012 152529.80 80 36.4200127 138.5840531 2700.97 47043.23 112.45 47048.76 118.09 -5.53
2248220 20051012 152529.90 80 36.4200489 138.5840760 2700.40 47043.27 112.47 47048.77 118.09 -5.50
2248230 20051012 152530.00 80 36.4200661 138.5840904 2699.93 47042.84 112.02 47048.52 117.81 -5.67
&F23a 20051013 125215.00 130130.00
1388080 20051013 125215.00 80 36.4079470 138.5286123 2771.76 47531.58 593.48 47536.52 598.54 -4.94
1388090 20051013 125215.10 80 36.4079393 138.5285881 2772.09 47531.73 593.64 47536.70 598.73 -4.98
1388100 20051013 125215.20 80 36.4079166 138.5285668 2772.32 47531.83 593.75 47536.73 598.77 -4.90
1388110 20051013 125215.30 80 36.4079055 138.5285373 2772.65 47531.95 593.87 47536.86 598.90 -4.91
.......
Lines starting with '&' indicate the start of line data,
describing Line name (number), Date "yyyymmdd" and Start/End time.
Time data is double precision value in the form of "HHMMSS.tt".
All other lines are data of individual points (108 columns + LF).
format(i8, 1x,i8, 1x,f9.2, 1x,i2, 1x,f11.7, 1x,f12.7, 1x,f7.2,
* 5(1x,f8.2))
1) Fiducial number, 2) Date (yyyymmdd), 3) Time (HHMMSS.tt),
4) Data spec.(*), 5) Latitude (Deg.), 6) Longitude (Deg.),
7) Altitude (m), 8) MagneticField-1(nT), 9) IGRFresidual-1 (nT),
10) MagneticField-2 (nT), 11) IGRFresidual-2 (nT),
12) Magnetic field difference (nT),
(*) Data spec.(k) :
k = 80 if position data is recovered by PostNav DGPS
k = 84 if position data is recovered by Real-time GPS
(Both, diurnal already corrected, no need of AMF compensation.)
This data has the form of a variation of DPAM line data.
It can be processed much the same as DPAM line, as far as dealing
with MagneticField-1 value.
When dealing with MagneticField-2 value, the file shall be processed
as a generic random point data file.
AMDB-GSJ line data format
Located line data file from GSJ digital data processing consists of
1 row of areaname
header and a repetition of line data blocks, and the line data block is
composed of 1 row
line header and repeated point data. The format of each data row is as
follows.
| name | offset | cols | format |
Contents |
|---|
| (Areaname Header) | |
|---|
- | 0 | 2 |
A2 | fixed string ‘##’ |
- | 2 | 2 |
2X | (space) |
area | 4 | 8 |
A8 | Area name |
year | 12 | 8 |
F8.2 | Year of survey (as used for DGRF calculation) |
high | 20 | 6 |
F6.0 | Altitude in ft |
- | 26 | 2 |
A2 | fixed string ‘ft’ |
| (Line Header) | |
|---|
- | 0 | 2 |
A2 | fixed string ‘# ’ |
lnam | 2 | 8 |
A8 | Line name (aligned left) |
npt | 10 | 6 |
I6 | Number of point data included |
| (Point data) |
(repeat npt times) |
|---|
isec | 0 | 8 |
I8 | Time in seconds (converted from DDHHMMSS string) |
alat | 8 | 9 |
F9.3 | Latitude in minutes (ITRF) |
alon | 17 | 9 |
F9.3 | Longitude in minutes (ITRF) |
tres | 26 | 8 |
F8.1 | DGRF residual magnetic value in nT after all corrections
|
AMDB-NEDO line data format
Integrated located data file of NEDO survey consists of 1 row of
areaname header and
a repetition of line data blocks, and the line data block is composed of
1 row line header
and repeated point data. The format of each data row is as follows.
| name | offset | cols | format |
Contents |
|---|
| (Areaname Header) | |
|---|
- | 0 | 2 |
A2 | fixed string ‘##’ |
- | 2 | 8 |
A8 | fixed string ‘ NEDO
’ |
area | 10 | 8 |
A8 | Area name
(kyushu / tohoku / hokkaido / chubu / kanto / chugoku)
|
| (Line Header) | |
|---|
- | 0 | 2 |
A2 | fixed string ‘# ’ |
lnam | 2 | 8 |
A8 | Line name (aligned right) |
npt | 10 | 6 |
I6 | Number of point data included |
| (Point data) |
(repeat npt times) |
|---|
ifid | 0 | 8 |
I8 | Fiducial number |
isec | 8 | 6 |
I6 | Time of a day in seconds |
alat | 14 | 9 |
F9.3 | Latitude in minutes (ITRF) |
alon | 23 | 9 |
F9.3 | Longitude in minutes (ITRF) |
tair | 32 | 8 |
F8.1 | Magnetic field in the air in nT |
tmdv | 40 | 8 |
F8.1 | Magnetic diurnal variation in nT |
tcor | 48 | 8 |
F8.1 | Magnetic field in nT after diurnal correction
and level adjustment |
tres | 56 | 8 |
F8.1 | DGRF residual in nT after correction and adjustment |
irad | 64 | 5 |
I5 | Radio altimeter value in ft |
ibar | 69 | 5 |
I5 | Barometric altimeter value in ft |