Page 1 of 1

Importing TDS file created on Nikon gun

PostPosted: Wed Jul 06, 2005 1:44 am
by Bruce Loth
My aging Nikon DTM-730 has onboard DC capabilities and can export field data
in "TDS" format. The test example below is from a 3-station, closed loop
traverse (measured in the office's parking lot). On the first setup
(station 10), I told the Nikon that my backsight was station 99 and
assigned it a back azimuth of 65°. The final setup was on station 12 where
I turned an angle back to station 10 (assigning 10 the foresight point
number 13). When I export from Nikon format into TDS (using the Nikon's
onboard DC software), this is the ascii file that I end up with:

JB,NMB:\W00_00\W00_00,DT06-01-2005,TM17:03:04
MO,AD0,UN0,SF1.000000,EC1,EO0.0000,AU1
--Description:
--Client:
--Comments:
--Tilt Correction: VA:ON HA:ON
-- W00_00 <JOB> Created 01-Jun-05 16:06:23
--Prism constant: 30
SP,PN10,N 5000.0000,E 10000.0000,EL500.0000,--TRAV
SP,PN99,N 0.0000,E 0.0000,EL0.0000,--
--DT06-01-2005,TM%02:%02:%02
OC,OP10,N 5000.0000,E 10000.0000,EL500.0000,--TRAV
BK,OP10,BP99,BS65.0000,BC0.0000
LS,HI5.2800,HR5.5000
--99,FD0.0000,ZD90.5139,SD108.7439
SS,OP10,FP11,AR45.1731,ZE90.5452,SD93.1878,--TRAV
SS,OP10,FP101,AR61.4726,ZE91.2303,SD64.2709,--WR FLAG
--DT06-01-2005,TM%02:%02:%02
OC,OP11,N 4967.6862,E 10087.3932,EL498.2930,--TRAV
BK,OP11,BP10,BS290.1731,BC0.0000
LS,HI5.1100,HR5.5000
--10,FD0.0000,ZD88.4132,SD93.1999
--BS IN TOLERANCE
--HDm=93.1757 BS Zm=500.0302 DELTAS: HD=-0.0003 Z=-0.0302
SS,OP11,FP12,AR77.4856,ZE89.4843,SD79.0579,--TRAV
--DT06-01-2005,TM%02:%02:%02
OC,OP12,N 5045.9536,E 10098.5428,EL498.1626,--TRAV
BK,OP12,BP11,BS188.0627,BC0.0000
LS,HI5.3500,HR5.5000
--11,FD0.0000,ZD89.4024,SD79.0599
--BS OUT OF TOLERANCE
--HDm=79.0586 BS Zm=498.4635 DELTAS: HD=0.0011 Z=-0.1705
SS,OP12,FP13,AR56.5324,ZE88.5112,SD108.7527,--TRAV

I designated every reading as a "sideshot" in the Nikon DC software (even
the control). When I import the above file into Carlson's "Raw Editor", it
seems to choke on the records that start with "OC".

If I strip the "OC" records out of the file (and the comments to improve
readability), I end up with this:

SP,PN10,N 5000.0000,E 10000.0000,EL500.0000,--TRAV
BK,OP10,BP99,BS65.0000,BC0.0000
LS,HI5.2800,HR5.5000
SS,OP10,FP11,AR45.1731,ZE90.5452,SD93.1878,--TRAV
SS,OP10,FP101,AR61.4726,ZE91.2303,SD64.2709,--WR FLAG
BK,OP11,BP10,BS290.1731,BC0.0000
LS,HI5.1100,HR5.5000
SS,OP11,FP12,AR77.4856,ZE89.4843,SD79.0579,--TRAV
BK,OP12,BP11,BS188.0627,BC0.0000
LS,HI5.3500,HR5.5000
SS,OP12,FP13,AR56.5324,ZE88.5112,SD108.7527,--TRAV

.. . . which imports nicely into Carlson's "Raw Editor". The traverse legs
and sideshots are drawn and I can process the data to adjust for misclosure.

Three questions:

1) Is the TDS file that my old Nikon gun creates using a an up-to-date "TDS"
format that Carslon understands?

2) What are the "OC" records? I googled for a specification on the "TDS"
file format but didn't find anything. I am assuming that the Nikon creates
the "OC" record during the "station setup" procedure required when the
instrument is powered on and told what point it is setup over.

3) Or, should I get used to editting these raw files before importing?

Btw ... Here's what the Nikon-format raw file looks like (as exported from
the the gun's DC software onto the datacard):

CO,B:\W00_00\W00_00
CO,Description:
CO,Client:
CO,Comments:
CO,Downloaded 01-Jun-05 17:02:29
CO,Software: AP700 version: 1.20
CO,Instrument: Nikon DTM730
CO,Dist Units: Feet US
CO,Angle Units: Degrees
CO,Zero azimuth: North
CO,Zero VA: Zenith
CO,Coord Order: NEZ
CO,Tilt Correction: VA:ON HA:ON
CO, W00_00 <JOB> Created 01-Jun-05 16:06:23
CO,Prism constant: 30
MC,10,T10,5000.0000,10000.0000,500.0000,CP
MC,99,,,,,
CO,01-Jun-05 16:15:50
CO,Temperature: 68 Fahrenheit Pressure: 29.9 inHg
ST,10,T10,99,,5.2800,65.0000
F1,99,108.7439,0.0000,90.5139,16:15:50
SS,11,5.5000,93.1878,45.1731,90.5452,16:17:46,CP
SS,101,5.5000,64.2709,61.4726,91.2303,16:20:08,WR FLAG
CO,01-Jun-05 16:31:04
CO,Temperature: 68 Fahrenheit Pressure: 29.9 inHg
ST,11,,10,T10,5.1100,290.1731
F1,10,93.1999,0.0000,88.4132,16:31:04
CO,BS IN TOLERANCE
CO,HDm=93.1757 BS Zm=500.0302 DELTAS: HD=-0.0003 Z=-0.0302
SS,12,5.5000,79.0579,77.4856,89.4843,16:32:42,CP
CO,01-Jun-05 16:43:38
CO,Temperature: 68 Fahrenheit Pressure: 29.9 inHg
ST,12,,11,,5.3500,188.0627
F1,11,79.0599,0.0000,89.4024,16:43:38
CO,BS OUT OF TOLERANCE
CO,HDm=79.0586 BS Zm=498.4635 DELTAS: HD=0.0011 Z=-0.1705
SS,13,5.5000,108.7527,56.5324,88.5112,16:45:48,CP

Re: Importing TDS file created on Nikon gun

PostPosted: Wed Jul 06, 2005 7:11 am
by Andrew Puller
We use TDS-95 and the format you are getting is the same as the native tds
files we have, except you have more comments in your raw file.

We have had no trouble importing the raw data file into raweditor on Survey
2004.

The OC line stands for Occupied, indicating you have occupied a new station
and is set as a comment when we import it.
Have you tried importing the Nikon format? Survey 2004 has a Nikon option on
the file menu, under import, which may work if Nikon have not changed their
file format too much.



"Bruce Loth" <rbloth_nospam_@yahoo.com> wrote in message
news:daeuva$d3q$1@update.carlsonsw.com...
My aging Nikon DTM-730 has onboard DC capabilities and can export field
data
in "TDS" format. The test example below is from a 3-station, closed loop
traverse (measured in the office's parking lot). On the first setup
(station 10), I told the Nikon that my backsight was station 99 and
assigned it a back azimuth of 65°. The final setup was on station 12
where
I turned an angle back to station 10 (assigning 10 the foresight point
number 13). When I export from Nikon format into TDS (using the Nikon's
onboard DC software), this is the ascii file that I end up with:

JB,NMB:\W00_00\W00_00,DT06-01-2005,TM17:03:04
MO,AD0,UN0,SF1.000000,EC1,EO0.0000,AU1
--Description:
--Client:
--Comments:
--Tilt Correction: VA:ON HA:ON
-- W00_00 <JOB> Created 01-Jun-05 16:06:23
--Prism constant: 30
SP,PN10,N 5000.0000,E 10000.0000,EL500.0000,--TRAV
SP,PN99,N 0.0000,E 0.0000,EL0.0000,--
--DT06-01-2005,TM%02:%02:%02
OC,OP10,N 5000.0000,E 10000.0000,EL500.0000,--TRAV
BK,OP10,BP99,BS65.0000,BC0.0000
LS,HI5.2800,HR5.5000
--99,FD0.0000,ZD90.5139,SD108.7439
SS,OP10,FP11,AR45.1731,ZE90.5452,SD93.1878,--TRAV
SS,OP10,FP101,AR61.4726,ZE91.2303,SD64.2709,--WR FLAG
--DT06-01-2005,TM%02:%02:%02
OC,OP11,N 4967.6862,E 10087.3932,EL498.2930,--TRAV
BK,OP11,BP10,BS290.1731,BC0.0000
LS,HI5.1100,HR5.5000
--10,FD0.0000,ZD88.4132,SD93.1999
--BS IN TOLERANCE
--HDm=93.1757 BS Zm=500.0302 DELTAS: HD=-0.0003 Z=-0.0302
SS,OP11,FP12,AR77.4856,ZE89.4843,SD79.0579,--TRAV
--DT06-01-2005,TM%02:%02:%02
OC,OP12,N 5045.9536,E 10098.5428,EL498.1626,--TRAV
BK,OP12,BP11,BS188.0627,BC0.0000
LS,HI5.3500,HR5.5000
--11,FD0.0000,ZD89.4024,SD79.0599
--BS OUT OF TOLERANCE
--HDm=79.0586 BS Zm=498.4635 DELTAS: HD=0.0011 Z=-0.1705
SS,OP12,FP13,AR56.5324,ZE88.5112,SD108.7527,--TRAV

I designated every reading as a "sideshot" in the Nikon DC software (even
the control). When I import the above file into Carlson's "Raw Editor",
it
seems to choke on the records that start with "OC".

<SNIP>

. . . which imports nicely into Carlson's "Raw Editor". The traverse legs
and sideshots are drawn and I can process the data to adjust for
misclosure.

Three questions:

1) Is the TDS file that my old Nikon gun creates using a an up-to-date
"TDS"
format that Carslon understands?

2) What are the "OC" records? I googled for a specification on the "TDS"
file format but didn't find anything. I am assuming that the Nikon
creates
the "OC" record during the "station setup" procedure required when the
instrument is powered on and told what point it is setup over.

3) Or, should I get used to editting these raw files before importing?


<SNIP>

Re: Importing TDS file created on Nikon gun

PostPosted: Wed Jul 06, 2005 4:55 pm
by Bruce Loth
Yeah, perhaps the "OC" records are not the source of the problem .... I
removed the line:

SP,PN99,N 0.0000,E 0.0000,EL0.0000,--

(and comments) from the file resulting in this:

SP,PN10,N 5000.0000,E 10000.0000,EL500.0000,--CP
OC,OP10,N 5000.0000,E 10000.0000,EL500.0000,--CP
BK,OP10,BP99,BS65.0000,BC0.0000
LS,HI5.2800,HR5.5000
SS,OP10,FP11,AR45.1731,ZE90.5452,SD93.1878,--CP
SS,OP10,FP101,AR61.4726,ZE91.2303,SD64.2709,--WR FLAG
OC,OP11,N 4967.6862,E 10087.3932,EL498.2930,--CP
BK,OP11,BP10,BS290.1731,BC0.0000
LS,HI5.1100,HR5.5000
SS,OP11,FP12,AR77.4856,ZE89.4843,SD79.0579,--CP
OC,OP12,N 5045.9536,E 10098.5428,EL498.1626,--CP
BK,OP12,BP11,BS188.0627,BC0.0000
LS,HI5.3500,HR5.5000
SS,OP12,FP13,AR56.5324,ZE88.5112,SD108.7527,--CP

.. . . which imports into the raw editor OK.




"Andrew Puller" <andrew@surveyor.net.au> wrote in message
news:dafhl2$j14$1@update.carlsonsw.com...
We use TDS-95 and the format you are getting is the same as the native tds
files we have, except you have more comments in your raw file.

We have had no trouble importing the raw data file into raweditor on
Survey
2004.

The OC line stands for Occupied, indicating you have occupied a new
station
and is set as a comment when we import it.
Have you tried importing the Nikon format? Survey 2004 has a Nikon option
on
the file menu, under import, which may work if Nikon have not changed
their
file format too much.