Anyone doing this?
Can you tell me the best way to achieve it.
I'm slightly familiar with using attribute 1 as a string number. Is this the best way to do it with Liscad?
Not using it myself , it's for a friend.
I'm on holiday for another week, but do have a format file I created years ago to do just what your talking about.?ÿ Basically, you need to create a GSI file that has one line for the point number and measurement data and one line for the code and attributes.?ÿ For the code you basically need to combine the code with attribute 1 (or what ever attribute you use for the string value).?ÿ Since switching over to Captivate several years ago I've pretty much abandoned LisCAD because the string values are not an attribute and I could never figure out how to capture the data.?ÿ Message me in a week or so and I will look for the format files.
We used to incorporate the string number directly into the code, so if 167 was the code for asphalt then "167" alone would be for a ground shot on asphalt "10167" would be for the first string, "20167" for the second "100167" for the tenth etc.?ÿ
Descriptive attribute coding was hyped in the manual back then but we only used the info lines for instructional codes like rectangles, offsets etc.?ÿ
This was back in the early aughts on the eleven hundred series instruments, I am sure things have changed but I hold fond memories of working with that approach.
Squowse,
If your still looking for info on outputting to liscad email me at jputnam'at'oriongeomatics'dot'com, I'm finally back in town.?ÿ The bottom line is that you extract a GSI file with the code and string not as an attributes but as a remark blocks. 71.. for the code and 72.. for the string.?ÿ I have a format file for the SmartWorks that I had used for years and I can send you a copy if you like.?ÿ You can also import the Leica database directly into LisCAD but I found that method a little limiting.