The following options are commonly available import options for many of the data filters TPC supports.
Many data filters include coordinates or geodetic positions for the points being imported. Use this option to protect these imported coordinates and geodetic positions.
When turned on, protects the imported coordinates or geodetic position. See Protecting Points.
When this option is off (default), they may be recomputed by the raw data that was imported.
Imported comment records are converted into traverse Notes. TPC inserts a Note point for each comment and places the comment in the Description column of the Traverse Views.
Many data filters include stored point and their coordinates or geodetic positions. These points are typically then used elsewhere in the imported data as occupied points or backsights. If you started the job on the data collector by exporting points from Traverse PC or some other surveying software and transferring those points to the data collector, the data collector will probably export them back out as these stored points.
Use this option to create a traverse point for each stored point being imported.
If this option is off (default), stored points are added to the survey and therefore can be accessed through the Points Manager, but are not added to the traverse created by the import.
Creates a detailed report in the Message View, showing how the file was converted. You will also see the following:
Turn this option on to show unsupported records. TPC does not read the individual observations in a horizontal angle set for this format. If you don't want these to show up as unsupported records, turn this option off.
Turn this option on to create a drawing showing the imported data. Once you've looked at the drawing to confirm the data you imported, you can always delete the drawing.
Turn this option on to include =[exsiting point label] in the descriptions of import points that get relabeled because TPC found an existing survey point with their original label.
For example, if point 1 is imported, but TPC finds an existing survey point labeled 1, the imported point must be relabled to something like 1:1. If this option is turned on, TPC places =1 in the description of imported point 1:1.
When an imported point matches an existing survey point, you can tell TPC to 1) create new (imported) points with a unique point labels, 2) use the matching existing survey point without updating it or 3) use the existing matching point and updated it from the imported data.
You control this with the option you select from a pulldown list. See Importing Matching Points.
Use this option to convert imported coordinates (y,x,z) from one type to another. This can be metric to imperial, imperial to metric, grid to ground, ground to grid, etc..
TPC imports the coordinates from the file, converts them based on the conversion type selected, then compares them with existing survey points when determining if a matching survey point already exists. If the imported coordinates end up creating a new survey point, that new point will have those coordinates.
You generally want the imported points to end up with the same coordinate type as the survey. For example, if you are using a state plane projection, like NAD83, your survey coordindates are on that state plane grid. As a rule, you want any imported coordinates to be state plane grid coordinates. If they are not, you will want to convert them to state plane coordinates on import.
If your survey has a CRS, you genearlly want the imported points to end up with the same coordinate type as the survey. So you will need to determine if the coordinates beimg imported are ground our grid (TPC's CRS grid) and convert them accordingly.
If your survey does not have a CRS, you are working in a local grid for that site. These local grids often use starting coordinates of 10000, 10000 or 0,0. In this case, you do not want to convert imported coordinates. Instead, you are making the assumption that the coordinates being imported are local or ground coordinates.
We used the word generally above, because you can have a survey in TPC that uses a CRS to relate a few GNSS control points to your ground survey, but otherwise uses ground coordinates for all the points. This is typical of boundary surveys or small subdivisions that do not cover a lot of area and have few geodetic constraints.
Use this field to modify imported point labels. You will generally do this to create unique points from the inported data.
Let's say that you have multiple crews collecting data on the same project. You could assign the prefix 'A' to all the data imported by crew A and the prefix 'B' to all data imported by crews B. Both crews could use the same point numbers like 1000, but one would be imported as A1000 and the other as B1000.
Enter a prefix you would like to begin each import point with. For example, if your point label modifier is 'TOPO-' and your imported point labels are 1,2,3,... the resulting points in TPC will be TOPO-1, TOPO-2, etc.
Use an asterisk (*) to embed the imported point labels inside the point label modifier . For example, if your point label modifier is 'GS*ORG ' and your imported point labels are 1,2,3,... the resulting points in TPC will be GS1ORG, GS2ORG, etc.
Use + or - to add or subtract a value to each point label. For example, if your point label modifier is +1000 and your imported point labels are 1,2,3... the resulting points in TPC will be 1001, 1002, 1003.
TPC will also split any incoming label into a prefix, value and suffix. So if your point label modifier is +1000 an imported point label of GPS1 will be modified to GPS1001, 120A will be modified to 1120A, EAC1A will be modified to EAC1001A and so on.
Many data collectors include a backsight record (TDS uses a BK records) for each instrument setup. However, if your data collector does not, or if a backsight record is omitted, TPC can treat the first observation as the backsight observation and create a backsight record for it in the traverse.
Use this option to treat the first observation after a station record as a backsight observation.
Use this option to eliminate redundant points in the traverse created from the import.
The TDS file format, for example, includes the following records for each foresight (OC-station, BK-backsight and TR-foresight). This results in the following traverse point sequence.
3 OP, etc.
This option reduces this sequence to the following
3 FS, etc.
This format is much cleaner to work with and is typical of how the traverse would look if you had entered the data manually.
Most total station data formats provide the horizontal circle reading. Internally, TPC stores the circle readings, allowing you to have a non-zero backsight reading. Inside the Traverse View, the raw data mode displays these circle readings, while the inverse move displays the resulting horizontal angles that were turned from the repsective backsights.
Use this option to convert horizontal circle readings to angles. TPC does this by subtracting the BS circle reading from any observations and setting the BS circle reading to zero.
Some surveyors set the BS circle to the reference azimuth of the BS. Any angles turned can be read as a direct azimuth if desired. TPC computes these observations just fine, but if you then copy data to another traverse and include raw data you can loose the association of the circle reading and its original backsight. Converting from a circle reading to the resulting angle can eliminate the side effects of these actions.
Turn this option on to have TPC automatically rotate and translate the imported data to the positions of existing survey points.
Both the initial occupied point OP and backsight point BS must include the point labels of the points to translate and rotate to in the point descriptions of the imported points.
For example, if TPC imports 1 OP = 100 followed by 2 BS = 101, and finds existing points 100 and 101, it will