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.

[NathanBarnett]

Melita,

Yes, the TAZ layer covers Bibb County in Georgia and another county to the northeast.  I also tried UTM (16 and 17 I think?) projections to no avail.  I'm wondering if I could put their GCS into NAD83 and then pull them into correct alignment?  Since I wrote my last post my coworker told me she didn't think she had any coordinates in the data frame to begin with, so does that mean they were "floating" without any coordinates to pinpoint them in a correct place?

[MelitaKennedy]

Hi Nathan,

The problem with converting or defining the other layers as NAD83 is we don't know what they're in now. If we can't figure it out, you may have use the spatial adjustment toolbar to force them into a known coordinate system.

Did she have any base data underlaying these layers? If so, that may be the coordinate system. They're using. It almost looks like the x/easting values are in NAD83 Georgia East (USfeet), but the y/northing values were converted to feet twice. Hmmm.

Melita

[NathanBarnett]

I believe there was nothing in the data frame as she began creating the shapefiles but I'm not sure.  I believe they were created in a new mxd file with nothing else added in the data frame, sort of like a clean slate.  I'm not sure how the GCS NAD83 would have been adopted into the files unless it was done later.

Since there were only a few polylines I think we're scrapping the old mismatched ones, though I may experiment with the spatial adjustment toolbar to see if I can scale/resize them into place.

Thank you for your help!

[MartesSaha]

Hi everyone,
a question in the same general them of extents...
I have a shapefile for lakes in east africa that has a specified UTM projection of 37s while the area in reality spans at least 6 UTM zones, on both sides of the equator. Hence the extent box has negative numbers. I am also unable to display any other shapefile along with this one in Arcmap, even though all the shapefiles have UTM 37S. The other shapefiles all display together, an cover an arrea that is a subset of the lakes shapefile.

Details for the lakes shapefile:

Extent:
Top:  -24226.9 m
Left: 986139.84 m
Right: 2381343.9 m
Bottom: -1709541 m

Projected Coordinate System: WGS_1984_UTM_Zone_37S
Projection: Transverse_Mercator
false_easting: 500000.00000000
false_northing: 10000000.00000000
central_meridian: 39.00000000
scale_factor: 0.99960000
latitude_of_origin: 0.00000000
Linear Unit:  Meter
Geographic Coordinate System: GCS_WGS_1984
Datum:  D_WGS_1984
Prime Meridian:  Greenwich
Angular Unit:  Degree

How does ArcMAP figure out the extent of the shapefile ? From the underlying data, I imagine ? If so, where does one look for the actual coordinates ? The attribute table for this shapefile does not have any lat longs or UTMs.

thanks for any suggestions !
martes

[MelitaKennedy]

Hi Martes,

The top/bottom values are negative. That has nothing to do with how many zones (width) the data covers. You only get negative Y (northing) values if the data is in the southern hemisphere, and is using a northern UTM zone. Change the coordinate system (Define Projection or ArcCatalog data property page) to zone 37N. Or maybe not.

By the way, the east-west extents aren't that wide, but if the data covers eastern Democratic Republic of the Congo through Tanzania, I think it's in UTM 34N, not 37N.


Melita

[SHARONYIU]

Hi,
i have trouble to manage the truck route layer. once i added on my truck route layer, i found that there is no spatial reference, then i added the coordinate system and projection to it same as the other layer in the data frame. however, it didn't show on the data
frame with other layers.

this is my truck route layer:

Extent:
top: 1780880.911940 ft
bottom: 1744756.081303 ft
left: 6442678.163408 ft
right: 6467979.834917 ft

data source:
Data Type: Shapefile Feature Class
Shapefile: T:\Syiu\GIS Data\GIS Online Test\TruckRtect.shp
Geometry Type: Line
Coordinates have Z values: No
Coordinates have measures: No

Projected Coordinate System: NAD_1983_StatePlane_California_V_FIPS_0405_Feet
Projection: Lambert_Conformal_Conic
False_Easting: 6561666.66666667
False_Northing: 1640416.66666667
Central_Meridian: -118.00000000
Standard_Parallel_1: 34.03333333
Standard_Parallel_2: 35.46666667
Latitude_Of_Origin: 33.50000000
Linear Unit:  Foot_US

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

this is one of my other layer:

Extent:
top: 1781517.516966 ft
bottom: 1744796.245593 ft
left: 6442600.817762 ft
right: 6467866.135013 ft

data source:
Data Type: SDE Feature Class
Database Platform: SQL Server
Server: GISData10
Connection Properties: gisdata10
Authentication Type: Database authentication
User name: sdeuser
Database: SDEReplica
Version: sde.DEFAULT
Description: Instance default version.
Feature Dataset: SDEReplica.REPLICA.Planning
Feature Class: SDEReplica.REPLICA.BikeRoute
Feature Type: Simple
Geometry Type: Line
Coordinates have Z values: No
Coordinates have measures: No

Projected Coordinate System: NAD_1983_StatePlane_California_V_FIPS_0405_Feet
Projection: Lambert_Conformal_Conic
False_Easting: 6561666.66666667
False_Northing: 1640416.66666667
Central_Meridian: -118.00000000
Standard_Parallel_1: 34.03333333
Standard_Parallel_2: 35.46666667
Latitude_Of_Origin: 33.50000000
Linear Unit:  Foot_US

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

i don't what is wrong between those layers? would anyone help me, will be great appreciated.!!!

[deleted-user-ymUUSX5iRPbK]

Hello!
I'm facing a similar problem as my projection doesn't match up.
I have several shapefiles that don't re project correctly. Although the projections are similar the extent of the shapefiles isn't. I've tried everything....

Shapefile 1:
Projected Coordinate System: WGS_1984_UTM_Zone_51N
Projection: Transverse_Mercator
False_Easting: 500000,00000000
False_Northing: 0,00000000
Central_Meridian: 123,00000000
Scale_Factor: 0,99960000
Latitude_Of_Origin: 0,00000000
Linear Unit:  Meter

Geographic Coordinate System: GCS_WGS_1984
Datum:  D_WGS_1984
Prime Meridian:  Greenwich
Angular Unit:  Degree

Extent
Top: 2906261,349089 m
Right: 393210,496279 m
Left: 997,816934 m
Bottom:2428047,437101 m


Shapefile 2

Geometry Type: Point
Coordinates have Z values: No
Coordinates have measures: No

Projected Coordinate System: WGS_1984_UTM_Zone_51N
Projection: Transverse_Mercator
False_Easting: 500000,00000000
False_Northing: 0,00000000
Central_Meridian: 123,00000000
Scale_Factor: 0,99960000
Latitude_Of_Origin: 0,00000000
Linear Unit:  Meter

Geographic Coordinate System: GCS_WGS_1984
Datum:  D_WGS_1984
Prime Meridian:  Greenwich
Angular Unit:  Degree


Extent
Top: 29,624399 m
Right: 128,000000 m
Left: 115,760010 m
Bottom: 17,939501 m


I wonder if someone could please help me??

Best regards,
Inês Machado

[MelitaKennedy]

Inês,

Shapefile 2 is not in UTM, but in latitude-longitude. Try redefining its coordinate system to WGS84 using the Define Projection Tool or the data's property page in ArcCatalog. Then, if necessary, you can project it to UTM.

Melita

[deleted-user-ymUUSX5iRPbK]

Dear Melita,
thank you for your help. Its finally working.

Best wishes,
Inês Machado

[DerekCitino]

Hello,

I created an excel table with long/lat data using a web application called itouchmap.com.  It uses Google Map to allow the user to select a point and then it gives you the long/lat in decimal degrees.  The points are of locations in the US, approximately 300 in 28 states.

I did research on the type of coordinate system Google Maps uses and I believed using the WGS_1984 Mercator_Auxiliary_Sphere projection would work.

I wanted to use the ArcGIS online base map called "World Street Map."  I uploaded that map and then imported my excel table.  Here is an example of some of the point data:

28.553715 -81.342369
27.793012 -82.733665
34.765125 -77.380542
28.055292 -82.432103
39.426797 -87.418037
30.673329 -88.124370
32.508624 -84.943628
30.184601 -81.734793
31.619755 -84.217127
27.465947 -82.567592


I import the data and then select 'Display xy data.'  I set the longitude column to 'x' and latitude column 'y'.  The box below that is called the Coordinate system of input coordinates and it is set to WGS_1984_Web_Mercator_Auxiliary_Sphere and the GCS is set to GCS_WGS_1984.

When it displays the points, it puts them in the very center of the map, just below the ear of Africa.  Where have I gone wrong?  Thanks in advance!