Projection Issue: Two Layers not matching up

[AprilTaylor]

Here is what I did and am trying to figure out: I took a table with coordinates and added XY then exported to a shapefile (which is attached in the Everylocation shapefile). Then I added this shapefile into a Arcmap project with a layer called PublicNotices (which is attached). When I added the Everylocation shapefile, some of the points are displayed out in the ocean. I began to think that those points out in the ocean were the wrong coordinates and I was going to delete them. Then I wanted to compare them to the publicnotice shapefile.  The PublicNotice file has some of the same points as the Everylocation file and the two should overlap. How do I determine if this is a projection issue and fix it or to determine which file has the wrong coordinates?

[MelitaKennedy]

You definitely have a few bad points in BankPermits. One is FID = 349. The latitude value is the same at the longitude value, just the sign changed. That's why it shows up so far north compared to rest of the data. FID = 303 has the wrong Northing value (it's currently equal to the Easting value).

I don't know what's wrong with point FID = 387, if all the points are supposed to fall within South Carolina. The latitude value is 30.3114 when all other points have latitude values over 31 degrees.

For the other points in BankPermits that fall offshore, I don't have a ready answer for you. It's possible that the latitude-longitude values for some points that they may be in DMS rather than decimal degrees. For example, FID = 115 has:

latitude = 32.4507
longitude = -80.0103

If we treat these as DD.MMSS and convert to decimal degrees, they become

latitude = 32.751944
longitude = -80.0175

Or they could be DD.MMmm which converts to

latitude = 32.751167
longitude = -80.017167

Without knowing where the point's supposed to be, I can't tell if either of these is correct.

Melita