Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 2
    this is my method also. I utilize two different software to "prove" it. You might also peruse this question for some basic direction on projections. gis.stackexchange.com/questions/2769/…
    – Brad Nesom
    Commented Mar 28, 2011 at 20:16
  • 7
    You could simplify step 2 a little by just changing the dataframe (ArcMap) projection, and letting the known layer reproject on the fly. Commented Mar 28, 2011 at 20:50
  • 14
    Note that you shouldn't be projecting the data. You should be defining the projection. Projecting the data changes the coordinates. Defining the projection just assigns a projection to that data and tells that software what projection the data is already in. These are two different tools in ArcMap, "Define Projection" is the one you want to use.
    – Sean
    Commented Aug 31, 2011 at 12:36
  • 1
    I prefer read the coordinate values, I can usually tell if they are decimal degrees, meters or feet (harder t distinguish) and then move to the best system. Start with WGS 84 if it appears decimal, UTM if meters, State plane if feet. I once had one that nobody could fix (for gravitational anomalies). It was USA state plane with a linear unit of......kilometers. I could tell from the fact it was close I had the system right but the state was tiny, ahh kilometers was the linear unit. Commented Feb 24, 2019 at 2:44