“No Projection” Coordinate System

[T.Guisewhite]

When I start a boundary project I usually have some sort of deed/plat calculated points that I’m importing. Is there a way to set up a coordinate system for a page that these points can be imported to so the values never change? I just want the LS to never scale them to another projection. Or even look at them relative to a coordinate system.

Scenario I keep running into is:
I Start a State Plane project
Import the points to a page
Then if I adjust the project to ground...
The points get projected...but they were always ground points from the deeds...

I tried setting up a no-projection coordinate system but as the underlying system I chose the state plane...and I’m still seeing the points move.

I just want the LS to look at the Northing and Easting of the design points and never move / scale etc.

Anyone got a good system for dealing with that? I don’t really want to have a bunch of different coordinate systems for the project. Just don’t want it to mess with design points.

Thanks to all!

 

[Adam]

I usually import the points into a state plane and then create a ground scaled system. Then after the ground system is made I just delete the points and reimport them on the proper ground system. I think we need a prompt when importing points that would allow the user to select the underlying system and the scale point from the list of points to be imported and then a system would be created upon import.

Edit...this applies to modified state plane coordinates, grid bearings and ground distances.

 

[Shawn Billings]

It already exists. Create a local system (house with + symbol). In Adam's case, select state plane as underlying system. In T's case select any system. Import points into page with the local coordinate system. Use localization to translate scale and rotate. Coordinate values will not change, only the relationship between the local grid and the underlying system.

 

[Nate The Surveyor]

Yeah! What Shawn said!

 

[T.Guisewhite]

So if the points are already psudo-state plane. Meaning search points overlaid on geo-referenced imagery. Does this mean I would have to do a localization to be able to use them? Or can I just stake to them from the get go?

I’ll have to play with this.

 

[Adam]

So if the points are already psudo-state plane. Meaning search points overlaid on geo-referenced imagery. Does this mean I would have to do a localization to be able to use them? Or can I just stake to them from the get go?

I’ll have to play with this.

Most of the time I download the Ortho photos from nconemap. Then plot the deeds and overlay them on the photos using centerlines, fencelines etc. That gives me grid bearings and ground distances.Then you have the option of setting up a ground scaled system or what I've been doing lately is scaling the deed to state plane in the office when I plot it. I've been keeping it all on state plane for a while now.i like it. I really like to scale the deed when I plot it and never worry about converting any survey data. Also, ground distances can be entered in cogo if your going to set one on the fly.

 

[Adam]

No localization needed for deed plots for search locations in my opinion, Tim. Here in NC we have the luxury of those nconemap orthos. Sometimes I will do a localization onna deed that I have on a "modified" state plane via the images just to see how it compares. I use localization as a geometry comparison tool a lot. But really only use localization to survey for construction or if it's a really good survey by someone I have seen good work from. Localization helps to find out what you've been given. If I'm handed control coordinates for construction staking you bet I do a localization.

 

[Matt Johnson]

Is there a way to set up a coordinate system for a page that these points can be imported to so the values never change?

I want to emphasize that the coordinate values of design points never change and their physical location is determined by their underlying coordinate system that was used when they were imported. If you modify the definition of the underlying coordinate system then the physical location of the points associated with it will be modified.

 

[Shawn Billings]

I want to emphasize that the coordinate values of design points never change and their physical location is determined by their underlying coordinate system that was used when they were imported. If you modify the definition of the underlying coordinate system then the physical location of the points associated with it will be modified.

This is true for localization. Design point coordinate values will change when using move, shift or rotate in cogo.

 

[Adam]

When a duplicate state plane system is created, then points are imported into that system, then a scale point is created from one of the points in the import, then the design coords are scaled. This is why I always delete the points and reimport after getting the scaled system set up. The other way is to only enter the scale point. Then create the system and then import the rest of the points.
This process bites a lot of our North Carolina users. It's how most of them prefer to work.
I made a rough pdf that I have given to some of them.