nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Layer's don't match / Wrong Projection?

AnjaWietholter

I have a table with geocoded Lat/Long Values that I want to add as point features to my map. However when I add the table and add X/Y data (Tools-Add X/Y data) the data is added to the map but the projection doesn't match up. I did compare the coordinate systems and they appear to be the same whoever the extent doesn't match up.

My Shapefile with the Lat/Long Points has similar values in projected coordinates compared to the decimal degrees which leads me to believe it doesn't project?

Here is an example. My Zip Code layer in decimal degrees:
West: -117.597982
East: -116.080157
North: 33.511553
South: 32.530161

In projected or local coordinates:
Left: 6150765.000000
Right: 6613436.500000
Top: 2129760.000000
Bottom: 1775304.125000
NAD_1983_StatePlane_California_VI_FIPS_0406_Feet

And my XY layer that doesn't match:

Decimal:
West: -136.179977
East: -136.179964
North: 25.945595
South: 25.945576

In projected or local coordinates:
Left: -117.388904
Right: -116.371055
Top: 34.517990
Bottom: 32.543795

NAD_1983_StatePlane_California_VI_FIPS_0406 also

I tried about everything. If somebody could help me with this it would be GREATLY appreciated.

Vind meer berichten getagd met

Accepted answers

All comments

MelitaKennedy

I have a table with geocoded Lat/Long Values that I want to add as point features to my map. However when I add the table and add X/Y data (Tools-Add X/Y data) the data is added to the map but the projection doesn't match up. I did compare the coordinate systems and they appear to be the same whoever the extent doesn't match up.

My Shapefile with the Lat/Long Points has similar values in projected coordinates compared to the decimal degrees which leads me to believe it doesn't project?

Here is an example. My Zip Code layer in decimal degrees:
West: -117.597982
East: -116.080157
North: 33.511553
South: 32.530161

In projected or local coordinates:
Left: 6150765.000000
Right: 6613436.500000
Top: 2129760.000000
Bottom: 1775304.125000
NAD_1983_StatePlane_California_VI_FIPS_0406_Feet

And my XY layer that doesn't match:

Decimal:
West: -136.179977
East: -136.179964
North: 25.945595
South: 25.945576

In projected or local coordinates:
Left: -117.388904
Right: -116.371055
Top: 34.517990
Bottom: 32.543795

NAD_1983_StatePlane_California_VI_FIPS_0406 also

I tried about everything. If somebody could help me with this it would be GREATLY appreciated.

Thank you for posting the reported data extents! The XY layer should be using a geographic coordinate system like NAD 1983, not California VI. You need to tag it with its current coordinate system. ArcMap can project it on the fly to match your other data. If you want to convert it permanently to State Plane, right click the layer in the table of contents and select Data, Export Data. In the export dialog, set it to use the data frame's coordinate system.

Melita

AnjaWietholter

Melita,

thank you for your help! This solved the problem! You're the best!

-Anja:)

Hello!
I'm facing a similar problem as my projection doesn't match up.

Layer 1
Projected coordinate system name: WGS_1984_UTM_Zone_33N
Geographic coordinate system name: GCS_WGS_1984

Bounding coordinates
Horizontal
In decimal degrees
West: 10.511349
East: 10.511368
North: 0.000425
South: 0.000412
In projected or local coordinates
Left: 10.385948
Right: 12.477436
Top: 47.091793
Bottom: 45.673069

Layer 2
Projected coordinate system name: WGS_1984_UTM_Zone_33N
Geographic coordinate system name: GCS_WGS_1984

Bounding coordinates
Horizontal
In decimal degrees
West: 16.362326
East: 18.504936
North: 47.129382
South: 45.640333
In projected or local coordinates
Left: 606088.187500
Right: 766033.625000
Top: 5220491.203121
Bottom: 5059756.878740

What can I do? I tried to export data setting the data frame's coordinate system, but it didn't work.
Your help would be highly appreciated.
Giorgia

MelitaKennedy

Hello!
I'm facing a similar problem as my projection doesn't match up.

Layer 1
Projected coordinate system name: WGS_1984_UTM_Zone_33N
Geographic coordinate system name: GCS_WGS_1984

Bounding coordinates
Horizontal
In decimal degrees
West: 10.511349
East: 10.511368
North: 0.000425
South: 0.000412
In projected or local coordinates
Left: 10.385948
Right: 12.477436
Top: 47.091793
Bottom: 45.673069

Layer 2
Projected coordinate system name: WGS_1984_UTM_Zone_33N
Geographic coordinate system name: GCS_WGS_1984

Bounding coordinates
Horizontal
In decimal degrees
West: 16.362326
East: 18.504936
North: 47.129382
South: 45.640333
In projected or local coordinates
Left: 606088.187500
Right: 766033.625000
Top: 5220491.203121
Bottom: 5059756.878740

What can I do? I tried to export data setting the data frame's coordinate system, but it didn't work.
Your help would be highly appreciated.
Giorgia

Hi Giorgia,

Your data has a similar issue to Anja's. Layer 1 should be defined with a geographic coordinate system. See how similar its projected/local extents are compared to layer 2's decimal degree extents? Anyway, try defining it as WGS 1984.

Now, about layer 2. As it is, these two layers will not overlay. The longitude values are different. Layer 1 is between 10E and 12E, while Layer 2 is between 16E and 18E. However, are you sure that Layer 2 shouldn't be using WGS 1984 UTM Zone 32N rather than Zone 33N? I think that would place the data in the same location as Layer 1 and put the data in northern Italy, rather than closer to Hungary.

Melita

Thank you very much for your advice and information. I modified the coordinates, but I have still some problems.

1) layer 1
Horizontal coordinate system
Geographic coordinate system name: GCS_WGS_1984
Details
Geographic Coordinate System
Latitude Resolution: 0.000000
Longitude Resolution: 0.000000
Geographic Coordinate Units: Decimal degrees

Geodetic Model
Horizontal Datum Name: D_WGS_1984
Ellipsoid Name: WGS_1984
Semi-major Axis: 6378137.000000
Denominator of Flattening Ratio: 298.257224
_________________

Bounding coordinates
Horizontal
In decimal degrees
West: 10.385948
East: 12.477436
North: 47.091793
South: 45.673069
In projected or local coordinates
Left: 10.385948
Right: 12.477436
Top: 47.091793
Bottom: 45.673069

2) layer 2
Horizontal coordinate system
Projected coordinate system name: WGS_1984_UTM_Zone_32N
Geographic coordinate system name: GCS_WGS_1984
Details
Grid Coordinate System Name: Universal Transverse Mercator
UTM Zone Number: 32
Transverse Mercator Projection
Scale Factor at Central Meridian: 0.999600
Longitude of Central Meridian: 9.000000
Latitude of Projection Origin: 0.000000
False Easting: 500000.000000
False Northing: 0.000000

Planar Coordinate Information
Planar Distance Units: meters
Coordinate Encoding Method: coordinate pair
Coordinate Representation
Abscissa Resolution: 0.000000
Ordinate Resolution: 0.000000

Geodetic Model
Horizontal Datum Name: D_WGS_1984
Ellipsoid Name: WGS_1984
Semi-major Axis: 6378137.000000
Denominator of Flattening Ratio: 298.257224
_________________

Bounding coordinates
Horizontal
In decimal degrees
West: 10.362326
East: 12.504936
North: 47.129382
South: 45.640333
In projected or local coordinates
Left: 606088.187500
Right: 766033.625000
Top: 5220491.203121
Bottom: 5059756.878740

I can see the map with the two layers, but the borders don't coincide. (layer 1 represents municipalities, layers 2 represents the provinces where those municipalities are located)

I also changed layer 2 in GCS_WGS_1984 but I have still the same problem, that is, borders don't overlap.

2bis) layer 2

Horizontal coordinate system
Geographic coordinate system name: GCS_WGS_1984
Details
Geographic Coordinate System
Latitude Resolution: 0.000000
Longitude Resolution: 0.000000
Geographic Coordinate Units: Decimal degrees

Geodetic Model
Horizontal Datum Name: D_WGS_1984
Ellipsoid Name: WGS_1984
Semi-major Axis: 6378137.000000
Denominator of Flattening Ratio: 298.257224
_________________

Bounding coordinates
Horizontal
In decimal degrees
West: 10.387225
East: 12.478793
North: 47.093540
South: 45.674821
In projected or local coordinates
Left: 10.387225
Right: 12.478793
Top: 47.093540
Bottom: 45.674821

Is there anything else I can possibly do?
Thank you.
Giorgia

MelitaKennedy

Thank you very much for your advice and information. I modified the coordinates, but I have still some problems.

1) layer 1
Horizontal coordinate system
Geographic coordinate system name: GCS_WGS_1984
Details
Geographic Coordinate System
Latitude Resolution: 0.000000
Longitude Resolution: 0.000000
Geographic Coordinate Units: Decimal degrees

Geodetic Model
Horizontal Datum Name: D_WGS_1984
Ellipsoid Name: WGS_1984
Semi-major Axis: 6378137.000000
Denominator of Flattening Ratio: 298.257224
_________________

Bounding coordinates
Horizontal
In decimal degrees
West: 10.385948
East: 12.477436
North: 47.091793
South: 45.673069
In projected or local coordinates
Left: 10.385948
Right: 12.477436
Top: 47.091793
Bottom: 45.673069

2) layer 2
Horizontal coordinate system
Projected coordinate system name: WGS_1984_UTM_Zone_32N
Geographic coordinate system name: GCS_WGS_1984
Details
Grid Coordinate System Name: Universal Transverse Mercator
UTM Zone Number: 32
Transverse Mercator Projection
Scale Factor at Central Meridian: 0.999600
Longitude of Central Meridian: 9.000000
Latitude of Projection Origin: 0.000000
False Easting: 500000.000000
False Northing: 0.000000

Planar Coordinate Information
Planar Distance Units: meters
Coordinate Encoding Method: coordinate pair
Coordinate Representation
Abscissa Resolution: 0.000000
Ordinate Resolution: 0.000000

Geodetic Model
Horizontal Datum Name: D_WGS_1984
Ellipsoid Name: WGS_1984
Semi-major Axis: 6378137.000000
Denominator of Flattening Ratio: 298.257224
_________________

Bounding coordinates
Horizontal
In decimal degrees
West: 10.362326
East: 12.504936
North: 47.129382
South: 45.640333
In projected or local coordinates
Left: 606088.187500
Right: 766033.625000
Top: 5220491.203121
Bottom: 5059756.878740

I can see the map with the two layers, but the borders don't coincide. (layer 1 represents municipalities, layers 2 represents the provinces where those municipalities are located)

I also changed layer 2 in GCS_WGS_1984 but I have still the same problem, that is, borders don't overlap.

2bis) layer 2

Horizontal coordinate system
Geographic coordinate system name: GCS_WGS_1984
Details
Geographic Coordinate System
Latitude Resolution: 0.000000
Longitude Resolution: 0.000000
Geographic Coordinate Units: Decimal degrees

Geodetic Model
Horizontal Datum Name: D_WGS_1984
Ellipsoid Name: WGS_1984
Semi-major Axis: 6378137.000000
Denominator of Flattening Ratio: 298.257224
_________________

Bounding coordinates
Horizontal
In decimal degrees
West: 10.387225
East: 12.478793
North: 47.093540
South: 45.674821
In projected or local coordinates
Left: 10.387225
Right: 12.478793
Top: 47.093540
Bottom: 45.674821

Is there anything else I can possibly do?
Thank you.
Giorgia

Hi Giorgia,

Approximately how far apart are the two datasets?

Melita

Do you mean what the distance is between the two borders (of the two dataset) in the map? The length is approximately 220 Meters.
Thank you for your help.

Giorgia

MelitaKennedy

Do you mean what the distance is between the two borders (of the two dataset) in the map? The length is approximately 220 Meters.
Thank you for your help.

Giorgia

Hmmm, that could be a datum (geographic coordinate system) issue. However, the Monte Mario or Roma 1940-based zones for Italy have very different xy extents from a UTM zone. It could also be that the two datasets are at different accuracies. Can you find a 3rd dataset that you can use for a 'control'? That is, which dataset appears to be offset?

Melita

Thank you very much for all your suggestions.

I used Roma_1940_Gauss_Boaga_Est and they don't overlap again.

a) 1nd layer (municipalities)

Horizontal coordinate system
Projected coordinate system name: Roma_1940_Gauss_Boaga_Est
Geographic coordinate system name: GCS_Roma_1940
Details
Map Projection Name: Transverse Mercator
Scale Factor at Central Meridian: 0.999600
Longitude of Central Meridian: 15.000000
Latitude of Projection Origin: 0.000000
False Easting: 2520000.000000
False Northing: 0.000000

Planar Coordinate Information
Planar Distance Units: meters
Coordinate Encoding Method: coordinate pair
Coordinate Representation
Abscissa Resolution: 0.000000
Ordinate Resolution: 0.000000

Geodetic Model
Horizontal Datum Name: D_Roma_1940
Ellipsoid Name: International_1924
Semi-major Axis: 6378388.000000
Denominator of Flattening Ratio: 297.000000
_________________

Bounding coordinates
Horizontal
In decimal degrees
West: -7.074194
East: -7.074177
North: 0.000395
South: 0.000383
In projected or local coordinates
Left: 10.385948
Right: 12.477436
Top: 47.091793
Bottom: 45.673069

b) 2nd layer (provinces)

Horizontal coordinate system
Projected coordinate system name: Roma_1940_Gauss_Boaga_Est
Geographic coordinate system name: GCS_Roma_1940
Details
Map Projection Name: Transverse Mercator
Scale Factor at Central Meridian: 0.999600
Longitude of Central Meridian: 15.000000
Latitude of Projection Origin: 0.000000
False Easting: 2520000.000000
False Northing: 0.000000

Planar Coordinate Information
Planar Distance Units: meters
Coordinate Encoding Method: coordinate pair
Coordinate Representation
Abscissa Resolution: 0.000000
Ordinate Resolution: 0.000000

Geodetic Model
Horizontal Datum Name: D_Roma_1940
Ellipsoid Name: International_1924
Semi-major Axis: 6378388.000000
Denominator of Flattening Ratio: 297.000000
_________________

Bounding coordinates
Horizontal
In decimal degrees
West: -7.074194
East: -7.074177
North: 0.000395
South: 0.000383
In projected or local coordinates
Left: 10.387225
Right: 12.478793
Top: 47.093540
Bottom: 45.674821

I decide to give up to these shapefile (dated 2006) and I tried the new version of these and Municipalites', Provinces' and Regions' borders coincide. Is there no way to modify the datum of the old shapefile, right?
Thank you.
Giorgia

DianeMcConnaughey

I have a similar problem. Four datasets created the same way, but two of them are slightly different from the other two. They cannot all be loaded into the same Feature dataset. ArcGIS 9.3.1. The difference is in the Abscissa resolution and Ordinate resolution. In one pair the values are 0.000000, 0.000000; and in the other pair they are 0.000100, and 0.000100.
1) data brought in as XY event from excel table, UTM 11 NAD27, then exported as a FC into a FGDB, using the Data Frame properties: NAD_1983_Albers, Projection Albers, False Easting 0.000000, false northing 0.000000, Central Meridian -96.000000, Standard_Parallel_1 29.500000, Standard_Parallel_2 42.500000, Latitude_of_Origin 23.000000, Linear Unit Meter, GSC_North_American_1983, Datum - D_North_American_1983.
2. I tried importing the Coordinate system of one to the other, but it did not fix the problem. I also tried projecting one data set and importing the projection information of one of the others. This did not work either. Both times the Abscissa resolution and Ordinate resolution remained 0.000000, 0.000000.

JamesFetzner

I have a problem similar to the original poster. The points from my georeferenced file are not plotting on the map properly. The coordinate systems seem to be the same (see below) but the extents are different. It looks to me like the point file has set the extent to meters, when it should be decimal degrees (DD), or the DD need to be converted to meters to get the layers to overlap properly . I think the problem lies here, but I can't figure out how to edit/modify the extents on individual layers? Is this even possible? Or am I barking up the worng tree here? Using ArcGIS v10 by the way.

Point Layer:

Extent:
   Top: 31.177874 m
   Bottom: 31.087096 m
   Left: -89.028088 m
   Right: -88.981114 m

Projected Coordinate System:
Name: NAD_1983_Transverse_Mercator
Projection: Transverse_Mercator
False_Easting: 500000.000000
False_Northing: 1300000.000000
Central_Meridian: -89.750000
Scale_Factor: 0.999830
Latitude_Of_Origin: 32.500000
Linear Unit: Meter (1.000000)

Geographic Coordinate System: GCS_North_American_1983
Angular Unit: Degree (0.017453292519943295)
Prime Meridian: Greenwich (0.000000000000000000)
Datum: D_North_American_1983
    Spheroid: GRS_1980
      Semimajor Axis: 6378137.000000000000000000
      Semiminor Axis: 6356752.314140356100000000
      Inverse Flattening: 298.257222101000020000

Map Layer:

Extent:
    Top: 1574817.604125 m
    Bottom: 1078727.964133 m
    Left: 355913.259109 m
    Right: 609060.498911 m

Projected Coordinate System: NAD_1983_Transverse_Mercator
Projection: Transverse_Mercator
False_Easting: 500000.00000000
False_Northing: 1300000.00000000
Central_Meridian: -89.75000000
Scale_Factor: 0.99983000
Latitude_Of_Origin: 32.50000000
Linear Unit: Meter

Geographic Coordinate System: GCS_North_American_1983
Datum: D_North_American_1983
Prime Meridian: Greenwich
Angular Unit: Degree

Thanks for any help you might offer.

Cheers,
FetznerJ

MelitaKennedy

Hello FetznerJ,

It looks like the first layer should be using a geographic coordinate system, rather than a projected coordinate system. The extent values look like decimal degrees, particularly if the data is in southern Mississippi.

Redefine it as NAD 1983 (don't reproject it) using the Define Projection tool or the data's property page in ArcCatalog.

Melita

JamesFetzner

mkennedy,

Many thanks! I found the option in ArcMap to set the coordinate system to NAD-83, rather than projecting it. The points are now plotting where they should. Appreciate the help!!

Cheers,
FetznerJ

PearlDaniel

I am having a problem similar to the previous posts here. I created a shapefile from an Excel file of latitude/longitude values, but they are not appearing in the place they should be in ArcMap with the other shapefiles I have.

Here is the information on the point shapefile I created:
Extent
Top: 35.984250 m
Bottom: 34.367333 m
Left: 90.817589 m
Right: 93.998444 m

Projected Coordinate System: NAD_1983_UTM_Zone_15N
Projection: Transverse_Mercator
False_Easting: 500000.00000000
False_Northing: 0.00000000
Central_Meridian: -93.00000000
Scale_Factor: 0.99960000
Latitude_Of_Origin: 0.00000000
Linear Unit: Meter

Geographic Coordinate System: GCS_North_American_1983
Datum: D_North_American_1983
Prime Meridian: Greenwich
Angular Unit: Degree

The previously downloaded map shapefile:
Extent
Top: 3925437.166877 m
Bottom: 3891226.247671 m
Left: 677974.783259 m
Right: 727471.671950 m

Projected Coordinate System: NAD_1983_UTM_Zone_15N
Projection: Transverse_Mercator
False_Easting: 500000.00000000
False_Northing: 0.00000000
Central_Meridian: -93.00000000
Scale_Factor: 0.99960000
Latitude_Of_Origin: 0.00000000
Linear Unit: Meter

Geographic Coordinate System: GCS_North_American_1983
Datum: D_North_American_1983
Prime Meridian: Greenwich
Angular Unit: Degree

I am using ArcGIS v. 10. I have tried to use the Define Projection tool to define the Geographic Coordinate System to NAD 1983.prj and many others. I have tried to define the Projected Coordinate System to NAD 1983 Zone 15N. I have also tried using the Properties in ArcCatalog instead of the Define Projection tool. Sometimes with a different projection the point shapefile changes location but it is always far away from where it should be. Any help would be greatly appreciated.
Thanks!

MelitaKennedy

Hi,

The point shapefile has two problems with it that I can see. Given this extent:

Top: 35.984250 m
Bottom: 34.367333 m
Left: 90.817589 m
Right: 93.998444 m

The coordinate system should be NAD 1983 (geographic coordinate system), not a UTM zone. Once the data is defined correctly, you can use the Project Tool to convert to NAD 1983 UTM 15N. But before you can do any of this, the longitude values need to be made negative. ArcGIS expects that longitude values in the western hemisphere will be negative.

Melita

nathanruckinger

I am having much of a similar problem here. I created a point file using XY coordinates but I can't get the created file to line up with a County Shapefile for PA. I'm unsure what I am doing wrong. Can you maybe point me in the direction of my mistake.

This is the original County Shapefile information:

Extent:

Top: 772527.246046 ft
Bottom: -162711.412584 ft
Left: 1189338.551241 ft
Right: 2815149.596144 ft

Data Type: Shapefile Feature Class
Shapefile: F:\Marcellus Shale\New folder\PACountyRepro.shp
Geometry Type: Polygon

Projected Coordinate System: NAD_1983_StatePlane_Pennsylvania_North_FIPS_3701_Feet
Projection: Lambert_Conformal_Conic
False_Easting: 1968500.00000000
False_Northing: 0.00000000
Central_Meridian: -77.75000000
Standard_Parallel_1: 40.88333333
Standard_Parallel_2: 41.95000000
Latitude_Of_Origin: 40.16666667
Linear Unit: Foot_US

Geographic Coordinate System: GCS_North_American_1983
Datum: D_North_American_1983
Prime Meridian: Greenwich
Angular Unit: Degree

This is my created point file:

Extent:

Top: 4672116.459650 ft
Bottom: 4569259.197331 ft
Left: 50933.504070 ft
Right: 459885.954358 ft

Data Type: Shapefile Feature Class
Shapefile: F:\Marcellus Shale\HomeLocations.shp
Geometry Type: Point

Projected Coordinate System: NAD_1983_StatePlane_Pennsylvania_North_FIPS_3701_Feet
Projection: Lambert_Conformal_Conic
False_Easting: 1968500.00000000
False_Northing: 0.00000000
Central_Meridian: -77.75000000
Standard_Parallel_1: 40.88333333
Standard_Parallel_2: 41.95000000
Latitude_Of_Origin: 40.16666667
Linear Unit: Foot_US

Geographic Coordinate System: GCS_North_American_1983
Datum: D_North_American_1983
Prime Meridian: Greenwich
Angular Unit: Degree

This is the Data Frame Properties:

NAD_1983_StatePlane_Pennsylvania_North_FIPS_3701_Feet
Projection: Lambert_Conformal_Conic
False_Easting: 1968500.000000
False_Northing: 0.000000
Central_Meridian: -77.750000
Standard_Parallel_1: 40.883333
Standard_Parallel_2: 41.950000
Latitude_Of_Origin: 40.166667
Linear Unit: Foot_US

GCS_North_American_1983
Datum: D_North_American_1983

They match so I don't understand what it is that I am missing here.

Nate

MelitaKennedy

Hi Nate,

Just going by the coordinates, I would guess a UTM zone, either 17North or 18North. Because the easting values get pretty small, I think it's 18N.

Melita

nathanruckinger

Does this infer I should change it from 18N to something else? or vice versa?

Nate

MelitaKennedy

Hi Nate,

I'm sorry that I wasn't clearer in the earlier message. Use the Define Projection tool or the data's property page in ArcCatalog to change the coordinate system NAD83 UTM Zone 18N. Or you could just clear the coordinate system--make it unknown first. Add it and the other layer to ArcMap. Set the data frame to use NAD83 UTM 18N. If the State Plane data lines up with the point layer (with an unknown coordinate system), you've confirmed that the point layer is using UTM 18N.

If a layer has no coordinate system, ArcMap can't do anything to it except display it. ArcMap can't project it to a new coordinate system. It can project layers with a known coordinate system. So you try setting the data frame's coordinate system to what you think the unknown data is in.

Melita

PearlDaniel

Hi,

The point shapefile has two problems with it that I can see. Given this extent:

Top: 35.984250 m
Bottom: 34.367333 m
Left: 90.817589 m
Right: 93.998444 m

The coordinate system should be NAD 1983 (geographic coordinate system), not a UTM zone. Once the data is defined correctly, you can use the Project Tool to convert to NAD 1983 UTM 15N. But before you can do any of this, the longitude values need to be made negative. ArcGIS expects that longitude values in the western hemisphere will be negative.

Melita

Doh. I changed the longitude to negative, then defined the coordinate system as NAD 1983 in ArcCatalog. Then the points displayed correctly! What a relief to have this issue resolved. I was overlooking the positive longitude and would probably have never spotted that. Thank you very much!!

HelenJenkins

Hi, I have a similar problem with layers not matching. I have a shapefile and a file which simply contains a list of latitudes and longitudes providing points and I want to plot the points over the shapefile map. The details of the projections are the same for each one:
Projected Coordinate System: MOLDREF 99 TMM 2824
Projection: Transverse_Mercator
False_Easting: 200000.00000000
False_Northing: -5000000.00000000
Central_Meridian: 28.40000000
Scale_Factor: 0.99994000
Latitude_Of_Origin: 0.00000000
Linear Unit: Meter

Geographic Coordinate System: MOLDREF 99
Datum: D_GRS_1980
Prime Meridian: Greenwich
Angular Unit: Degree

But the "extent" is different (and it may be wrong for at least one).
For the points, the extent is
Top: 48.467222m
Bottom: 45.544444m
Left: 26.803889m
Right: 30.042500m

(Although these look to me like the boundaries of the lat and long coordinates)

For the shapefile, the extent is:
Top: 372942.186016 m
Bottom: 36636.565397 m
Left: 67754.832657 m
Right: 335481.716789 m

Any thoughts on how I can fix this?

Thank you!
Helen

MelitaKennedy

Helen,

You're so close! The shapefile's extents exactly fit the projected coordinate system definition so as long as it's assigned the MOLDREF99 definition, it's fine. The file with lat/lon coordinates needs to be defined with a geographic coordinate system--to match the values. The coordinate system definition must always match what the coordinates currently are using. Once that's set, then ArcMap can project the values on-the-fly to a different coordinate system, or you can use the Project Tool to create a copy in a different coordinate system.

Melita

MikeZaske

Hi, I am also having similar issues with getting an imported excel spreadsheet to align with my existing data set. After creating the shapefile, in Catalog I have selected and set the Geographic coordinate to NAD 83 as data is supposedly set to. When I add the data to my existing data set nothing shows up, I can not even zoom to layer to find it. I have tried various Geographic Coordinates and various projections. Other coordinates have the same results, nothing shows in the map unless it is the first data added. With projections the data does appear in my map but in the wrong locations, depending upon which projection is used depends on where the data appears.

Here is the info for my map data
Top: 728023.312475 ft
Bottom: 590417.499994
Left: 831501.000015
Right: 958965.124998

Projected Coordinate System: NAD_1983_HARN_StatePlane_Florida_East_FIPS_0901_Feet
Projection: Transverse_Mercator
False Easting: 656166.66666667
False Northing: 0.00000000
Central_Meridian: -81.00000000
Scale_Factor: 0.99994118
Latitude_Of_Origin: 24.33333333
Linear Unit: Foot_US

Here is the info for the imported point feature
Top: -80.114722 dd
Bottom: -80.183333 dd
Left: 25.985000 dd
Right: 26.063333 dd

Geographic Coordinate System: GCS_North_American_1983
Datum: D_North_American_1983
Prime Meridian: Greenwich
Angular Unit: Degree

I know I am probably overlooking something just not sure what at this point. Any assistance you can give would be greatly appreciated.
Mike

DianeMcConnaughey

Check the Excel spreadsheet in Excel for bogus or out of range values. Put filters or sort the XY columns. If there are too many values, you might try searching for values < or > valid range. Null values might also cause problems. If you do find out of range or null values, filter them, and save filtered values to a new worksheet, save the out of range or suspicious values to a different worksheet. You reference StatePlane, but the coordinates seem to be in Antarica Top: -80.114722 dd Bottom: -80.183333 dd Left: 25.985000 dd Right: 26.063333 dd

MelitaKennedy

Diana has the answer. When you import the point data, switch the columns that you're using for 'x' and 'y'. The -80 values are longitude and correspond to 'x' (easting) while the +25 values are latitude and correspond to 'y' (northing).

Melita

AnneBarth

Hi, I think I have a similiar problem to these posted problems here.
The Data Frame of my ArcMap Document has the Coordinate System UTM Adindan 37N, due to the fact that the initial shapefiles of teh area were set to this Coordiante System. I wanted to add some GPS points. The GPS was set to WGS 1984. I add the GPS points as an excel file (and calculated them into Decimal Degrees) and used the button addxy data. I turned the Coordinate System of the Input Coordinates to WGS 1984. The points appear, and they are broadly in the right area, but there are not correct. They are also not shifted to one sight, but seem to be distributed totally wrong.

I made a screenshot, the green points are where the points should be located, and the brown points are the points which I got.

I hope, sombody can help me with this. Thanks in advance!

screeenshot_1.jpg

MelitaKennedy

Hi Anne,

First, try setting a transformation to convert between Adindan and WGS84. There are several possibilities. If the data's in Ethiopia, try Adindan_To_WGS_1984_4. You're correct that the transformation will likely move most of the points into the area of interest, but not all of them. Perhaps check the original values again to confirm that the conversion to decimal degrees worked correctly? Were the original values in degrees-minutes or degrees-minutes-seconds?

Melita

AnneBarth

Hi Melita,
thank you for your hint with the conversion to decimal degrees. In fact, the original data was in Degrees Decimal Minutes and not in Degrees, Minutes, Seconds. Now as I converted them again to Decimal Degrees, the points are very close to where they should be, but there are still about 150 m south-east of the real location. I tried the Conversion between Adindan and WGS 1984, but it seems to be no difference.
Thank you for your help
Anne

Pier_PaoloComida

Hello, I seems to have a similar problem as listed above.
When I try to open a shapefile made of a series of waypoints (called "map31") on arcmap this error window appears and waypoints don't match up with the map and others waypoints (called "waypoints") took in the same area but with a different tool.

So I opened arc catalog and then I checked the spatial attributes founding some strong differences between Map31 (wrong) and waypoints (correct) as listed below:

Map31 Shapefile metadata spatial data:

Horizontal coordinate system
Projected coordinate system name: PSAD_1956_UTM_Zone_17S
Geographic coordinate system name: GCS_Provisional_S_American_1956
Details
Grid Coordinate System Name: Universal Transverse Mercator
UTM Zone Number: -17
Transverse Mercator Projection
Scale Factor at Central Meridian: 0.999600
Longitude of Central Meridian: -81.000000
Latitude of Projection Origin: 0.000000
False Easting: 500000.000000
False Northing: 10000000.000000

Planar Coordinate Information
Planar Distance Units: meters
Coordinate Encoding Method: coordinate pair
Coordinate Representation
Abscissa Resolution: 0.000000
Ordinate Resolution: 0.000000

Geodetic Model
Horizontal Datum Name: D_Provisional_S_American_1956
Ellipsoid Name: International_1924
Semi-major Axis: 6378388.000000
Denominator of Flattening Ratio: 297.000000
_________________

Bounding coordinates
Horizontal
In decimal degrees
West: -78.274169
East: -78.185368
North: 0.466100
South: 0.411639
In projected or local coordinates
Left: -78.286671
Right: -78.191760
Top: 0.474426
Bottom: 0.413234
_________________

Lineage
ESRI geoprocessing history

1. Process
2. Process
3. Process

_________________

Spatial data description
Vector data information
ESRI description
Map31
ESRI feature type: Simple
Geometry type: Point
Topology: FALSE
Feature count: 80
Spatial Index: FALSE
Linear referencing: FALSE

-------------------------------------------------------------

Waypoints shapefile spatial metadata:

Horizontal coordinate system
Projected coordinate system name: PSAD_1956_UTM_Zone_17S
Geographic coordinate system name: GCS_Provisional_S_American_1956
Details
Grid Coordinate System Name: Universal Transverse Mercator
UTM Zone Number: -17
Transverse Mercator Projection
Scale Factor at Central Meridian: 0.999600
Longitude of Central Meridian: -81.000000
Latitude of Projection Origin: 0.000000
False Easting: 500000.000000
False Northing: 10000000.000000

Planar Coordinate Information
Planar Distance Units: meters
Coordinate Encoding Method: coordinate pair
Coordinate Representation
Abscissa Resolution: 0.000000
Ordinate Resolution: 0.000000

Geodetic Model
Horizontal Datum Name: D_Provisional_S_American_1956
Ellipsoid Name: International_1924
Semi-major Axis: 6378388.000000
Denominator of Flattening Ratio: 297.000000
_________________

Bounding coordinates
Horizontal
In decimal degrees
West: -78.274169
East: -78.185368
North: 0.466100
South: 0.411639
In projected or local coordinates
Left: 803436.152327
Right: 813326.941221
Top: 10051577.353089
Bottom: 10045554.316746
_________________

Spatial data description
Vector data information
ESRI description
waypoints
ESRI feature type: Simple
Geometry type: Point
Topology: FALSE
Feature count: 33
Spatial Index: FALSE
Linear referencing: FALSE

SDTS description
Feature class: SDTS feature type, feature count
waypoints: Entity point, 33

----------------------------------------------

Now, the first try I did was to apply the same sets of bounding coordinates from the correct file to the wrong one but I can find anywhere "In projected or local coordinates" tab to change the values. Now I don't know if what I do it's correct anyway an help should be very appreciated.

Please write the solution step by step because I'm not practical using arcgis.

Thank you very much in advance for all your help you will give to me

Pier Paolo

Parallels Desktop.png

MelitaKennedy

The map31 data is in decimal degrees. Use the Define Projection Tool to define the data with the appropriate geographic coordinate system. Then you can use the Project Tool (or ArcMap) to convert it to PSAD56 UTM 17South. It might be in PSAD56 or WGS84.

Melita

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.