So, here I am working for this crazy lunatic guy that requires the point numbers to be prefaced with letters.
I am using TDS Pro on a Lecia TCR 1103. Does anyone know how to make my raw file add a prefix of alpha characters?
Or is that only done during the raw file processing?
I am required to produce just the raw data and I want to make sure to get the client what he wants....
thanks,
Dtp
PS That crazy guy already sent my total station into a blackhole by assigning me point numbers 10,000 up...the Leica didn't want to expand a file that large while in the field. I had to bring it back to the office and create a few points in that range then export that CR5 file back to the card. Now it's fine!
Oh, and if that lunatic starts posting here, just ignore him 🙂
We've used stricly alphanumeric with TDS Survey Pro for years. Powerful tool. If you need to add a prefix later, the text editor is your friend. 🙂
RB
> We've used stricly alphanumeric with TDS Survey Pro for years. Powerful tool. If you need to add a prefix later, the text editor is your friend. 🙂
>
> RB
But can I add prior?
Alpha Numeric point numbers in TDS-leica>Road Burner
How do I set up the on board Data collector to allow me to input a prefix to the point number prior to shooting ?
Alpha Numeric point numbers in TDS-leica>Road Burner
> How do I set up the on board Data collector to allow me to input a prefix to the point number prior to shooting ?
Not familiar with anything Leica, but I would expect TDS to be the same as on the Ranger. As I recall, a .CR5 file doesn't allow alphanumeric point numbers. Our SOP is to store the first point of the day like W183001 and let it incremement from there. Separate tasks are stored in separate daily jobs, and the next task would start with, for example, W183301. The W is the last initial of the operator, and the 183 is the day of the year. Very useful info later on.
RB
Foggyidea,
I used the version of TDS on-baord with the TPS1100 and I do not remember the ability to use alpha numeric point ID's. TDS probably added this later but the TDS on board for the TPS1100 was last updated in June 2004.
Also on the file size issue starting at a large number.... are you creating a sequential or non-sequential job file. You can started a sequential job at 10000 with no issues but you cannot have a point number less than 10000. If you have control points at say Point number 10 and then create a non-sequential job and enter point number 10000 then the memory created space between point 10 all the way to point 10000 so you can input any number between 10 and 10000 and higher than 10000. I garuntee the system ill puke trying to make that large of a file. If you want to do this and actually start locating points at say 9900 make a sequential file starting at 10000 and then rename your point 10 to point 9910 to have some logic behind it. Yes you will need to edit the RW5 file later but that is easy.
It is just a memory issue between the sequential and non-sequential job formats. Memory was not as large, of course, on the TPS1100 memory cards and the programming has come a long way also.
Alpha Numeric point numbers in TDS-leica>STM
STM,
Thanks for confirming my suspicions. What I finally did was to upload alpha numeric point numbers (converted from the CRD to a CR5 file) and then try and find them in the Leica. The gun would NOT recognize the points.
So what I then did was to create dummy points in my drawing and the export those (without Alpha characters) but ranging the points from 1-20,000. It seems to work out ok so far.
Two contributing factors that eat up the DC space, the size of the point number and that fact that they are State Plane Coords. Those big number eat it up.........
Alpha Numeric point numbers in TDS-leica>STM
I was on a job about a decade ago where a carpenter claimed that he had a Microsoft buddy who had helped him hack his 1100 in order to put alpha in the point numbers so the point number could be the grid intx.
I am sure this little nugget of questionable information will serve you well 🙂
