Using TGO or TBC to generate .prj for custom coordinate system

963
1
09-19-2012 07:51 AM
DanielReynolds1
New Contributor
Short Version:
Is there an easy way to take the Coordinate System Details output from TGO or TBC to define a custom coordinate system?

Long Version:
We have set up a control network to do some survey work in Wyoming.  Previously, while doing work in Utah and Colorado, we have used information generated in TGO to create a custom coordinate system that enables us to communicate with CAD and the surveyors.    While duplicating this process for our work in Wyoming, I noticed that when calculating latitude and longitude from a local x,y value I am not seeing the expected value.  This is not the case for our work in Colorado and Utah.  As far as I can see, the only difference between the projects is that the State Plane zones for Utah and Colorado use Lambert Conformal Conic whereas Wyoming uses a modified UTM. 

This was done by taking the origin of the State Plane zone in question and using the scale factor given by TGO along with the origin of our surveyors local coordinate system to come up with a new False Northing and Easting.  The new False Northing and Easting along with the Scale Factor are then used to modify the State Plane Zone to create a custom coordinate system.  This has given very satisfactory results.

Here's the math we're using:

New False Northing: Fn
State Plane Zone Origin Northing: SPn
Scale Factor (from TGO): SF
Local (ground) Northing of our local coordinate system): Ln
Northing offset (to differentiate local coordinates from State Plane Coordinates): On
State Plane Northing of our local origin: Gn

Fn = (SPn*SF)-((Gn*SF)-Ln)
Ln = Gn-On

The calculations for the False Easting are similar, simply replacing northing values with corresponding easting values.

On the CAD side, they input the local northing and easting, the corresponding State Plane northing and easting, and the inverse of the scale factor from TGO.  This process worked fine for our Wyoming data.

Is there anything different about the calculations needed to come up with the modified False Northing and False Easting given that we are trying to shift a UTM grid rather than a Lambert Grid?
Tags (2)
0 Kudos
1 Reply
MelitaKennedy
Esri Notable Contributor
The only thing I can think of it that there's already a scale factor in a tranverse Mercator definition, unlike a (US) Lambert conformal conic one. It's applied like this in the algorithm:

X (SPCS/UTM easting) = FE + sf*(x)
Y (SPCS/UTM northing) = FN + sf*(y)

where FE/FN is the SPCS/UTM false easting or false northing values
sf = scale factor (0.9996 for UTM, 0.9999375 for NAD83 SPCS WY)
x/y = the calculated values for the zone before the scale factor and false easting/northing are applied.

So when I create a custom local coordinate system, if the grid-to-ground is applied to the final SPCS/UTM coords, the modified TM-based coordinate system will have both new false easting/northing and scale factor parameters.

X (TM easting) = SF*(FE + sf*(x) )
Y (TM northing) = SF*(FN + sf*(y) )

SF = grid-to-ground
new scale factor = SF*sf


Melita
0 Kudos