Grid to Geodetic

Using COGO and inversing between points, I see where you can change using ground distance, can you do this for geodetic bearings as well? Also how do you export to geodetic or is it better to rotate and translate in CADD? Also, by using spc, how do i view the convergence angle? Does DPOS show the convergence angle?

Garrett
 

Shawn Billings

Shawn Billings
5PLS
Garrett,
for convergence, go to CoGo, tools and factors. You can select a point and see the convergence, scale factor and combined factor there.

to switch the inverse direction from grid to geodetic, press the label "B, Grid" and it will scroll through B, Geo (which is geodetic) and B, Mag Geo (which would be the current magnetic bearing) and B, Mag Grid (which doesn't make a lot of sense to me, but it's the current grid bearing by compass unadjusted for declination).

To export geodetic... that's a can of geodetic worms. Technically, you can export geodetic coordinates. Those would be latitude and longitude. But there aren't any CAD systems that I'm aware of that work in a geodetic coordinate system. It must be grid, or rather a grid. This grid can be true State Plane, a modified State Plane, a Low Distortion Projection or a localized system. There are proponents of each and all have their merits and detractions.

True State Plane is exactly what it is - State Plane. Just a little metadata and you're set. The only problem is that inverses are not well related to measurements at the Earth surface in many places. Also, the bearings are not close to true geodetic North in many places. To get past the grid inverse mismatch to ground measurements, surveyors often use the next options...

Modified State Plane has the look and feel of State Plane, but it's not quite State Plane. You'll need to keep more metadata for yourself and others if you use this. The upside is that the manipulation is fairly simply, multiplying the coordinates by a project wide combined factor is the easiest, but it causes your coordinates to shift a significant amount. Many will scale around a project point. That keeps the coordinates close to true State Plane, but it means more metadata. You'll need to keep up with what you scaled around. In order to keep Modified State Plane coordinates from being confused with true State Plane Coordinates, many will subtract truncate the coordinates (which is more metadata). This is helpful, but as Matt Johnson would point out, importing orthorectified georeferenced images into your project won't match up with your points (which is a primary motive for scaling around a project point instead of 0,0)

Low Distortion Projections can be developed for an entire county (with some exceptions in mountainous terrain). These projections work exactly like State Plane was designed to work, except the area is smaller and tailored to the local elevation rather than the ellipsoid, as State Plane was. With a little careful planning a LDP system can be designed such that differences in grid inverse and ground measurements can simply be ignored (+/-10ppm).

The localized system has some other benefits. It's based on State Plane, but does the scaling and truncating for you. In the LS, the underlying positions can shift (such as from DPOS) but the grid values never change as the localization parameters change to accommodate.

You'll have to decide which is best for you. I've been working with a new version of Carlson Survey that allows me to keep true State Plane Coordinates and label distances with a scale factor. I can also label directions as mean geodetic. This makes it much more convenient to have true State Plane. Having said that, I'm a big proponent of Low Distortion Projections.
 
My father uses the modified state plane with his survey pro. While working together, we both collect in spc and when he gets back to the office he will rotate and scale based off of one point.

Garrett
 
The convergence angle. I think he keeps raw data in spc and copies to rotate to the convergence angle and uses the combined scale factor.
 
Top