Trouble Converting .raw file into .fbk file

[Anonymous]

Hello,

We are using spectra precision data collector and usually just export pnezd files to create our surveys.

We need to start applying a least squares analysis and the point files currently don't have the meta data to run the analysis.

So I have had our surveyor export a RAW. file in order to try and utilize the autocad survey data collector link.

The problem is when I try to convert the RAW. file into any other format I get this message.

(The input file has alphanumeric point names and cannot be converted)

An FBK. file is still created it is just blank.

Does anyone have any advice on this issue? Our surveyors code their points but the numbers arent really associated with any lettering. I tried running through and replacing names in the text file that appeared to have lettering but this is very uncertain and not something I want to replicate in my workflow.

Thanks for any response and your time!

[Dan_Donovan · Accepted solution]

Some conversions may be best if conversions are used within the software of the manufacturer. A .rw5 raw file for that data collector may give better results if using Carlson X-port and using the Direct-Reverse report, then reduce Direct-Reverse and then export to a Fieldbook. This method will give you the ability to see what the raw values of the doubled angles and an editable .fbk to be used within Survey Link.

[tcorey]

Does the Spectra Precision data recorder not allow export to point number only, without alpha-numeric "Names"?

[Anonymous]

Unfortunately we currently only have Survey pro for uploading and exporting our data.

Spectra doesn't offer a Carlson x port or fbk export of data.

[wfberry]

A raw file is only a .txt file.  I would think that a quick find and replace would work.

(Find "name", replace with nothing.)

Bill

[Anonymous]

This is something I have been messing around with, I would like a better workflow than having to always find and replace text files which I feel will increase the possibility of errors! Although the idea is good and I appreciate the input from all!

[Anonymous]

I will have too look into the settings on the data collector, currently though we don't assign any letters to point numbers. They do however have codes associated with them, but I wouldn't think this would be a problem?

[tcorey]

Even though you are using Point Numbers, there may be a setting in the data recorder/transfer software that lets that be considered a Name. A Name is alphanumeric, even if it has only numbers. I would like to see the .raw file.

[Anonymous]

Yes, when my surveyor is free today I plan on seeing the options within the export on the data collector, the raw file is associating letters in front of the point numbers within the raw file it seems to me.

thanks for input, I don't think I can post the entire file online due to confidentiality in the contract although here is a snippet of the RAW file for reference purposes.

thanks for input,

Cole

[wfberry]

I was looking for a PNEZD file but I guess not.

Bill

[Anonymous]

PNEZD text files don't contain enough data to perform a least squares analysis, Those are easy to bring in with our code set.

[tcorey]

It looks like the point number field indeed has alpha characters: FP5001, FP5002, etc. Please follow-up to this thread if you find a solution.

[Anonymous]

After much trial and error with converting the RAW file I decided to look deeper into survey pro software which is what comes with spectra precision. Within the software it appears there is a way to export FBK files through generating reports. I was not fully aware of survey pros capabilities because I have used other software in the past at other organizations.

Thanks all for time and help!

[rl_jackson]

From your snippet I didn't see anything out of the ordinary. The FP is fine that just means Foresight Point which is the point number. What you have to watch for is if the field crew uses the stakeout functions within the software it will by default add STK to the beginning of a shot being staked and stored. So that very well may be your issue somewhere within the raw file. I'd look for something like that within the raw file