Released: July, 2013
TPC Desktop 2013 R1 – Released October 2013

Curved Text

Curved Text Example
Curved Text Example

Now you can choose from Stacked Curve or Aligned Curve.

Stacked Curve is the traditional curve/spiral label TPC has used forever. It creates a left or right aligned paragraph of text you can drag-n-drop anywhere on the drawing. Many of you turn on the leader which connects the stacked label back to the curve/spiral itself.

Aligned Curve works more like a tangent line label. The text is drawn parallel to the curve/spiral using the offset distance you specify from the line. In the example shown here, we’ve labeled the curve with some basic information.

In addition to telling TPC which style you want to use (Stacked vs. Aligned), you can also tell TPC how you want to label each style. We call this a Label Format.

You’ll now see both style options in the format dialog. Remember that you can include extra characters like LC= and R= to identify the individual data items in the label. This works for both stacked and aligned labels.

Curved Text Format Dialog
Curved Text Format Dialog

Traverse aPriori

 

Prior to the release of TPC Desktop 2013, TPC used one set of standard estimates for all observations it generated for Least Squares Adjustment. You could save and recall sets of standard estimates called A Priori values.

Now with TPC Desktop 2013, you can select standard estimates for individual traverses. Select one set of estimates for the GLO notes you entered or imported from a GMM Township Record file. Select another set of values for a total station traverse. And still another set for your GPS inputs.

Std Est By Traverse
Std Est By Traverse

From any Traverse View, just choose Tools | Least Squares Standard Error Estimates. TPC will display the A Priori values for that traverse.

Recall existing estimates or create unique estimates just for this traverse. When TPC pulls an observation from this traverse for the Least Squares network, it will automatically assign these estimates to the observation.

If you want observations from this traverse to revert back to the default estimates for the network, just choose the Remove Traverse Estimates button.

It’s a pretty simple way to provide additional flexibility to a Least Squares network.

Least Squares Angle Units

The LS report now use the angle units selected in Program Settings, Units. The report tells you which units you are using (DMS, Degrees, Grads, Rads, Mils, etc) and then reports all stanadard errors and observations in those units. For individual data items, abbreviations are appended to the value (i.e. 0.002g) where d=Degrees, g=Grads, r=Rads, and m=Mils).

Observations displayed in the Edit Observations dialog, also display angles and azimuths in the selected angle units.

Automatic Closure

You can now specify the closing point and closing angle in a traverse by including =[point label] in the point descriptions of the closing point and closing angle. See Automatic Closure Settings.

TPC uses this information to guess the closure type, closing point and closing angle when you open the Closure View to check your closure or apply an adjustment. You can still edit this information in the closure view and overwrite TPC’s guess, but most of the time, you won’t have to.

Redundant Observation Dlg
Redundant Observation Dlg

You can choose the character to use in the User Definitions dialog. TPC calls this the Redundant Observation character.

Here, we’ve used the equal sign.

You will see the Redundant Observation character in the Least Squares dialogs.

Using the Redundant Observation character for automatic closure is completely optional. If you don’t want to use it, then don’t. It’s that simple.

GMM Townships

GMM Township Settings Dlg
GMM Township Settings Dlg

TPC can import GMM Township Record files. These generally have a .RAW extension, and contain record data for a township. TPC creates a traverse named ‘Record T[township] R[range] [principal meridian] ‘ by reading the township, range and meridian values from the file. This traverse contains the record data from the file.

Choose the options you want from the Settings dialog.

As TPC imports the GCDB township records, it creates a traverse that can be used to plot the township. TPC inserts a Gap between each tier imported.

GMM Township Record Drawing
GMM Township Record Drawing

To plot the township, tag the imported traverse in the Traverses Manager.

GMM Township Traverse
GMM Township Traverse

And of course, all the township data is ready to use in it’s own traverse.

Because the traverse name includes the word ‘Record’, TPC knows that it holds record data and will use the data in the traverse to provide record data to lost corner routines like the Single and Double proportion dialogs.

Geodetics

We’ve formalized quite a number of improvements you requested in TPC Desktop 2011. Here are few of them.

  1. Added ability to edit geodetic positions in Point View (was available only in the Traverse View).
  2. Added warning message to Transform Coordinates command stating that points with fixed geodetic positions can not be transformed if the entire survey is not being transformed.
  3. When importing/exporting an ASCII file with geodetic positions, you can now precede the letter G with a minus (-G) to convert +longitude to -longitude (negative are West in TPC).
  4. Added support for Trimble Business Center .ASC files, where lat/long are specified as 42d15’30.12345″, using a ‘d’ for degrees.
  5. Added support for ASCII import of geodetic positions represented as ,42° 30′ 30.12345″. TPC now removes the spaces automatically.
  6. Entering bearing and distance equations (point .. point) in dialogs that specify the Distance and Direction types now recalls distance and direction in those types instead of grid (i.e. Distance Offset, Offset Interval, Compute Coordinates).
  7. Picking drawing objects to recall bearings / distances in dialogs that specify the Distance and Direction types now recalls distance and direction in those types instead of grid (i.e. Distance Offset, Offset Interval, Compute Coordinates).
  8. Added information to the Intersect dialog’s Summary report. Now includes information entered into the dialog.
  9. If [x] Latitude Arc is selected in the Intersect dialog, the Summary now includes the computed latitude for the computation and reports distances and directions as ground distance and true bearing (PLSS).
  10. When a survey’s distance type is set to either Geodetic or Ground at project elevation, new survey points are set to that elevation by default. Routines that interpolate an elevation for the new point will continue to override the default project elevation. See Survey Factors .

PLSS

We’ve formalized quite a number of improvements you requested in TPC Desktop 2011. Here are few of them.

  1. See just the PLSS symbols and line types. You can now edit the UserSymbols.dat and UserLineTypes.dat files to hide the symbols and line types you don’t use. Just begin any line with a minus sign ‘-‘ and TPC will hide that symbol or line type. Now when you pull down the symbol or line type list, you’ll see just the ones you want.
  2. Added ‘Justified’ alignment option to Text Box properties, producing fully justified text . Can be exported to DWG and DGN files.
  3. When survey units are Chains, scales are now displayed as ‘chs/in’ (chains per inch). Also see Scaling a Drawing
  4. Added ability to edit geodetic positions in Point View (was available only in the Traverse View).
  5. The Least Squares adjustment reports can now include adjusted coordinates and residuals even if a solution is not obtained. This allows for ‘post mortem’ investigation for non-converging solutions.
  6. When selecting points in a traverse for a Single or Double Proportion, you can now select just the existing corners without a temporary point.
  7. When computing lost corners with Single and Double proportion, you can now create a ‘Retrace’ and a ‘Record’ traverse to batch the computations. See help topic ‘Single Proportion’ and ‘Double Proportion’.
  8. Added geodetic position, convergence and scale factor to Double and Single proportion reports (existing corner and computed position of lost corner).
  9. Added computation of geodetic center section per 2009 Manual of Survey Instruction PLSS.
  10. Entering bearing and distance equations (point .. point) in dialogs that specify the Distance and Direction types now recalls distance and direction in those types instead of grid (i.e. Distance Offset, Offset Interval, Compute Coordinates).
  11. Picking drawing objects to recall bearings / distances in dialogs that specify the Distance and Direction types now recalls distance and direction in those types instead of grid (i.e. Distance Offset, Offset Interval, Compute Coordinates).
  12. If [x] Latitude Arc is selected in the Intersect dialog, the Summary now includes the computed latitude for the computation and reports distances and directions as ground distance and true bearing (PLSS).
  13. When a survey’s distance type is set to either Geodetic or Ground at project elevation, new survey points are set to that elevation by default. Routines that interpolate an elevation for the new point will continue to override the default project elevation. See Survey Factors .
  14. Traverse precision is now based on the units selected for a traverse. You can select “0.01 chns” per the PLSS.

Reports

We’ve formalized quite a number of improvements you requested in TPC Desktop 2011. Here are few of them.

Adds Date and Time to Report Sections

Section headings in the Report View now include the date and time. This provides you with an excellent record of what you did and when.

Here’s the Survey Report with date and time added.

[[ Survey Information ]] Friday, June 28, 2013 9:46:36

Date: 6-6-2013

Feet

147 Points

1 Traverses

0 Surfacess

MinX = 2691457.072 MinY = 0.000 MinZ = 0.00

MaxX = 2723097.113 MaxY = 31677.360 MaxZ = 0.00

1 Drawings

Adds Distance Type, Distance Units and Direction Types to Reports

TPC now includes this information for the Summary button available in many of the COGO dialogs and reports. Many of you have asked that TPC be as explicit as possible in reporting this information as you move from basic grid computations to geodetic.

Notice the Geo Dist and True Bearing in the following Random Inverse summary.

[[ Random Inverse (True Bearing, Geo Dist, Feet) ]] Saturday, June 29, 2013 19:48:50

Geo Dist (at project elevation 0.00 PLSS) True Bearing (mean course convergence PLSS)

From: 700100R

Y=0.000 X=2723097.113 Z=0.00

Lat=31°00’00.000″N Lng=107°50’00.000″W Conv=-0°00’00” Factor=0.9999167

To: 700140R SID:01645

Y=2639.780 X=2723097.113 Z=0.00

Lat=31°00’26.128″N Lng=107°50’00.000″W Conv=-0°00’00” Factor=0.9999167

Forward N0°00’00″E Backward S0°00’00″E

True Bearing=N0°00’00″W Geo Dist=2640.00 Slope Dist=2640.00

V Dist=0.00 V Angle=0°00’00” Percent=0.00

Files

TPC continues to improve it’s interface with files used in our industry. We’ve added some new ones in TPC Desktop 2013 and improved some others.

Import Trimble Business Center

TPC now imports geodetic and coordinate ASCII files exported from Trimble Business Center . We hope to release an extensive TBC interface with TPC Desktop 2013, Release 1.

Import GMM Township Record Files

TPC now imports GMM Township Record files. These are the R-Files or .RAW files used by the BLM and others to record PLSS data for an entire township. TPC reads this data into a traverse that can be used to automatically plot the record township points, populate the record data fields in the lost corner dialogs and reference GCDB point labels.

AutoCAD 2013 Support

AutoCAD has made lots of changes in their DWG file format as they moved from LDD to Civil 3D. The new AutoCAD 2013 drivers help you stay on top of exchanging drawings with clients and cohorts.

TPC is part of the Open Alliance, a consortium of CAD developers that support DWG and DGN files directly.

Others

  1. TPC now imports both alpha and numeric descriptions from Leica GSI files.
  2. Added ‘Combine BS, OP, FS’ option to SMI import. Many of the other import filters have this option. It cleans up the points in the Traverse View.
  3. Added ‘Overwrite Imported CooOctober 15, 2013htm”>TDS RAW/RW5 import. This causes imported points to assume the coordinates of existing points if ONLY their point labels match.
  4. ASCII import of latitude / longitude now reads more variations on degrees, minutes, seconds.
  5. Added support for DP record in TDS RAW import. This allows temporary points created in the data collector to be re-used as side shots or foresights.
  6. When opening an auto-saved survey file, TPC now checks to make sure the file was written in it’s entirety. If not, the autosave file is discarded and the last saved survey file is opened instead. See Using Autosave .
  7. Added ENZ coordinated order support to Trimble DC10.70 files.
  8. Added ability to determine description length in C&G binary CRD files. 18, 20 & 24 seem to be common lengths.
  9. TPC now handles survey path names with periods (1.e. \Docments\FirstName.LastName\Surveys\Job1.trv.

Sticky Adjustments

Beginning with TPC Desktop 2011, TPC refers to Precision, Curvature & Refraction and Scale Factor as ‘sticky’ adjustments. You can apply sticky adjustments before balancing angles and coordinates. Sticky adjustments also remain in effect when you choose Tools | Recompute from the Traverse View. To turn them off, go to the Closure View and choose Tools | Undo Adjustments.

With Sticky Adjustments, TPC can compute a traverse using any precision you want. This is critical for the PLSS were computations may be specified to the nearest link and minute.

 

Scalability and Stability

Scalability

With the recent release of the C++11/x ANSII standard, TPC can now rely more heavily on industry proven memory and data management. Where possible, we’ve replaced existing code with standard libraries from industry leaders. The result is something many of you have asked for – the absolute most reliable software experience possible.

In some ways, it’s like putting new tires on your vehicle. It may not look like a huge change, but it puts you on the road for another 40,000 miles. That’s what this new release does for Traverse PC.

Improved Testing

Microsoft has just released improved testing tools which move bug detection closer to the developer (that’s us) and farther from the user (that’s you). With tools like regression and automated UI testing, we can make the changes you want without introducing the bugs you don’t. We’ll be enhancing all the tests as we prepare for the agile release of TPC Desktop 2014.

 

Editions

  1. We’ve added Volumes and Point Codes to the Premium Edition.
  2. Added Generic Raw Data (CSV) import/export to Personal Edition.

Help