Just a heads up here. If you've got a drawing set to State Plane and you set the Project Scale Factor in the drawing setup screen to anything except 1.0, the Label Lat/Long command will give you way wrong values. I've alerted tech support to this, but they don't seem to understand that a given set of state plane coordinates equate to only one set of lat/long. The Report Distance Scale value in the drawing setup screen has no effect on the lat/long labels. Good idea to check your labels with another app such as Corpscon. This bug is new in 2015. I loaded the drawing with Carlson 2014 and the lat/long labels are correct regardless of what Project Scale Factor is used, as they should be.
>If you've got a drawing set to State Plane and you set the Project Scale Factor in the drawing setup screen to anything except 1.0, the Label Lat/Long command will give you way wrong values.
I don't believe this is a bug per se. Our documentation on the Project Scale Factor setting states:
>Project Scale Factor is multiplied by the x,y coordinates when converting between drawing and geodetic coordinates.
I believe the Project Scale Factor setting was hooked up in Carlson 2015 to more easily accommodate modified State Plane coordinates as described as the "GLOBAL modification" method in this State Plane Coordinates thread.
Semantics aside, I've seen digital plans that appeared to look a lot like State Plane coordinates but had associated with them a project scale factor (a value other than 1). When the coordinates were used as-is with established State Plane Coordinate System projection information, the data wouldn't line up with the data in other mapping applications. When superimposing these drawings into other mapping applications, it seemed the only way to get them to fit was by applying the specified project scale factor. If your coordinates are true State Plane, then your Project Scale Factor would (should?) be left at 1.
I often set my report distance scale factor as .36 so I can annotate in varas. Will this setting change my coordinate labels too? I definitely don't want it to do that.
Thanks, Ladd. It appears that release 2014 has the bug which was fixed in 2015, and I had just assumed I needed to put the same scale factor in both boxes (user error). Luckily no matter what value I had put in the Project Scale Factor box, the lat/long labels were always correct in 2014. In my thinking, if I check the state plane grid box in setup, the entities are in state plane, and the lat/long labels should always correspond. If I wasn't in state plane and working with ground distances, I would check the local box. I mainly wanted to give folks a heads up on the change in behavior that I was seeing so it wouldn't bite them too.
Thanks again! Carry on...