First make sure that the code you are after is in the Description Key Set (DKS), if it is then do the steps below. If it isn't you will need to add a new code to the DKS so it can be used below as well.
If you want to create a new code in the Stringer Settings this is how you would do it below.
-Click on Stringer Settings (make sure you have your CSV file set as current) -Find a code that is going to be about the same as the one you are adding in - click on the new button bottom left
-This will make a copy of that code - double click in the code and change the code to what you require
-Then select what TYPE of line it is going to be (3d Breakline, 2d Join Only or 3d Polyline) -Select the 2d layer you want the string to go on -Select the 3d Layer you want the 3d layer to go on (3d layer is normally only 1 layer as it is only required to create the breaklines in the drawing) -Click OK
Once that has been created, go and click on Join All Codes again and now it will be strung in the drawing and also added as a breakline in the surface. That code will now always be in the Stringer Settings CSV file for the next time you use that code.
Creating a tree block at the right size for Replace Tree Symbol Function
For your trees, you need to make sure that the tree blocks that you are using are at a 1m radius
Draw a circle at 1m radius and make sure the tree is the same size as the circle and resave the block showing the correct sizes.
Once you have the tree created at the riht size you can then go to the Tree Block Definition and set the right block for the right parameters for the trees.
After setting these items you just need to run the replace Symbols function and all your trees will be replaced with the right tree block at the right radius size as measured in the field. e.g. 201 .2 5 8 or TR .25 6 etc.
If you Have Stringer Topo installed and you want to turn arcs into chords , Stringer Topo has a great function in Stringer Extras that will allow you to truncate the Arc/Lines into chords at a distance or evenly set amount of chords required. Good for Subdivisons where arcs aren't required and a set amount of chords are.
Below is how to get it to work
Type TRUN in the command line
Then select the 2 lines you want Then select T for Truncation in the command line What are the lengths on the Truncation you require - lets say 4m It will then do a radius of 4m between the 2 lines Then when it says Enter A to specify Chord Deflection - type 4 in the command line This has now added 4 chords for that arc in the drawing.
Leica have brought out a new Total Station called Leica Captivate which doesn't use Format files (.FRT) anymore.
If you were using a Leica 1200 or a Leica Vivia machine and you had Stringer Topo you had to add an FRT file to the handheld and when you went to export out the survey data from those jiggers you would get an RW5 file that was compatible with Stringer Topo to reduce your data straight into the platform you were on.
The new Leica Captivates use an XML file exported out of those Total Stations.
Stringer Survey have gone and written a new importer for the XML file so it can be read into the abovemmentioned packages with Strigner Topo.
We have made it so you don't have to do anything to the original XML file, just export it off the Total Station and then read it into Stringer Topo.
As Stringer Connect is having a make over, we haven't made a new icon for it at this stage
In the command line type in STR_IMPORT_SURVEY_XML
This will allow you to search for the XML file that you have saved on the PC for the XML file required. Once you have selected the file you will get a new form displaying the Co-ordinates as shown below
If you click on the Observations tab you can see the raw survey data if needed.
Once you click on the Insert Points button, it will save the XML as an RW5 just like the other formats in Stringer Topo. If you want to use the RW5 to do the same edits as before in Stringer Connect you can use that file format just saved.
When it is added to the drawing, you will get the Points along with the linework that was showing on the Leica Captivate before import. This linework will be on a layer called Survey_Linework_XML. I have only been using this lineowrk to make sure the Handheld is the same as the Strings when joined with Join All Codes by Stringer Topo. When Join All Codes is clicked on it will get the linework as per pick up as usual. Remember, if .Parameters have been added then it will look a little different but the majority of the survey should match.
Now we, as in C R Kennedy and Stringer Survey, can be confident that the new XML files from the Leica Captivate can be imported easily into our software.
If you need to know anything else, please don't heistate in contacting us by adding in a ticket through Tech Support
Trimble DC Files - Prism Constants are not Added in Raw File.
The Trimble TSC3 DC file that gets exported from the Jigger DOESN'T add the Prism Constant to the slope distances. This mean they are the RAW observations without the correct adjustment being done to those distance on the Total Station.
I also downloaded an SDR file of the same job and compared those 2 files and the SDR file DOES have the prism constant added showing in this case a 31mm difference between the 2 points. The DC is the raw file without any calculations being added to it, where the SDR file has calcualtions added to it therefore not the raw file.
I was taught very early on in the peace that you always had to have the Prism Constant set on your jigger so that you get the correct answer. The DC file now relies on the Survey Software to add this data to your slope distances which i think goes against everything i was shown in the beginning.
So just be very carefull when using a DC file and make sure you check to see if the software you are using automatically adds the Prism Contant to the slope distance or NOT.