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.

Trouver plus de publications taguées avec

Accepted answers

All comments

ShayePalagi

Hi Melita,

Thank you for your reply, and for all the insight you've contributed to this thread. No, the data is not west of Palo, but more like 20 km north of Palo. I have reached out to the creator of the dataset to inquire about the potential use of local cadastral grids/projections. I'll reply with updates should that work as we figure it out, so others with similar issues might learn as well.

Thank you!

MelitaKennedy

Is the data approximately 10 km west of Palo, in the Philippines?

I looked at the other coordinate systems that we support for the Philippines, but none of them match the coordinates of your second dataset. The fact that it has negative and positive values implies that its center is in the area, so not a standard UTM or Philippines zone.

I have found some references to local cadastral grids/projections, so it's possible that is what the second data is using. You'd have to find out the parameters. I think the origin is usually the first point of the cadastral survey.

Melita

ShayePalagi

Hello all,

I've read through all past posts going back years, and unfortunately none of the prior fixes worked for me. This thread has been alive and well for years, hopefully someone is still out there to provide a little insight!

I have two polygon shapefiles with the same coordinate system:

WKID: 32651 Authority: EPSG

Data Type: Shapefile Feature Class

Geometry Type: Polygon

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

The two shapefiles should overlap, however their extents are different:

File 1 (the "correct" file):

Top: 1255609.389774 m

Left: 707424.654017 m

Right: 721689.696680 m

Bottom: 1237012.701112 m

File 2:

Top: 63404.759644 m

Left: -15831.190479 m

Right: 20830.738005 m

Bottom: -17715.538242 m

When I activate both layers, they are offset by thousands of meters. I can also tell that File 2 is sized incorrectly, it's scaled significantly larger than file 1. I received these files from a local city government, I wanted to use their shapefiles to recreate some maps for spatial analysis. It's a wonder to me that they created the maps they did when the extents are so different.

Any advice would be greatly appreciated!

Shaye

ulicheberli

Hi!

I am facing troubles re-projecting vector data from USGS HYRO1k for Africa to WGS84. The projection doesn’t match with correct WGS84 maps (about 3 miles east offset). Have tried all kinds of transformations and re-definitions of the original projection, though without success.

Shapefile 1:

Sphere_ARC_INFO_Lambert_Azimuthal_Equal_Area

Authority: Custom

Projection: Lambert_Azimuthal_Equal_Area

False_Easting: 0,0

False_Northing: 0,0

Central_Meridian: 20,0

Latitude_Of_Origin: 5,0

Linear Unit: Meter (1,0)

Geographic Coordinate System: GCS_Sphere_ARC_INFO

Angular Unit: Degree (0,0174532925199433)

Prime Meridian: Greenwich (0,0)

Datum: D_Sphere_ARC_INFO

Spheroid: Sphere_ARC_INFO

Semimajor Axis: 6370997,0

Semiminor Axis: 6370997,0

Inverse Flattening: 0,0

Data is from USGS Earthexplorer – Digital Evelation – GTOPO30 –HYDRO1k https://lta.cr.usgs.gov/HYDRO1KReadMe

Any ideas? Your help is highly appreciated.

Thanks a lot & best,

Uli

MelitaKennedy

Hello Helle,

Did you find this site: CM2.X model ocean and sea ice grids information

You might want to check whether they've exported the variable you want into a rectangular grid-based file.

Melita

NeilAyres

If those original coords are utm, then it is about 6 or 7 zones to the right of the zone you are using. Might be considerable distortion in your data.

HelleJørgensbye

Hi Neil

Thank you for taking time to reply.

Yes I agree with the weird numbers. It might be a problem with references missing in the net.cdf file (which is generated in Matlab after data has been assembled) nccreate and ncwrite were used in matlab to build the file. I am not sure excatly what is missing as ARCGIS plots the data but it is "to small" and totally off - so I think something must be added when building the net.cdf file.

The orginal data plots fine with a worldmap and should be ok.

Helle

NeilAyres

At first glance, I thought these were GCS (geographic) coordinates, but that doesn't look correct.

New netcdf file
extent :
Top : 188,5
Bottom: 0,5
Right: 177,5
Left: 0,5<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Bottom left is 0.5, 0.5. Top right is 177.5, 188.5

Doesn't look like anything to me. Are you sure this data is actually georeferenced to anything.

And, those numbers on your original data don't look anything like i would expect from UTM. Have you actually looked at this data with some other background info to confirm that it is where you think it is?

HelleJørgensbye

I have a similar problem.

I have one dataset with environmental data in a WGS 1984 UTM zone.

I am trying to add another environmental data layer from a netcdf file (works fine with the make netcdf raster layer) but the projection is off. Importing it "on the fly" into the existing dataset do not work. Projecting, reprojecting and exporting it do not work.

The information with the netcdf file states that it uses the "native tripolar grid (ORCA025) at ¼° resolution with 75 vertical levels" as the only info. What kind of projection is that?

Clearly someting is wrong with my projection

Old data set

extent :

Top : 9501969,24636

Bottom: -1831567,57809

Right: 3230932,42191

Left: 5176969,24636

New netcdf file

extent :

Top : 188,5

Bottom: 0,5

Right: 177,5

Left: 0,5

Helle

MelitaKennedy

Hello Pinelopi,

Follow Jayanta's steps below--use the Define Projection tool to reset/redefine the coordinate system to WGS84 or Amersfoort. Once that's done, you can use the Project tool to make a copy of the data that's georeferenced to RD_New.

Melita

JayantaPoddar

Define a new projection to the shapefile using Define Projection geoprocessing tool.

For the coordinate system, choose an appropriate Geographical Coordinate System (e.g. GCS_WGS_1984 or GCS_Amersfoort, whichever positions your map correctly).

PinelopiTrapezanlidou

Yes, it seems like that. Is there anything that I can do to convert it into RD_new?

NeilAyres

In your 2nd shapefile, those extent values look nothing like the extents in the first (very small numbers).

I would suggest the the second one is not in fact actually in a projected RD_New system, but has simply been defined like that.

It looks to me as if the actual coord sys is really GCS (geographic)

PinelopiTrapezanlidou

Hellow!

I am facing a problem like most of yours,

I have 2 shapefiles with the same coordinate system but I they don't seem to overlap.

The 1st is a point shapefile :

extent :

Top :612130,629897 m

Bottom: 606825,613838 m

Right: 192545,576475 m

Left: 167607,007256 m

Projected Coordinate System:   RD_New
Projection:   Double_Stereographic
False_Easting:   155000,00000000
False_Northing:   463000,00000000
Central_Meridian:   5,38763889
Scale_Factor:   0,99990790
Latitude_Of_Origin:   52,15616056
Linear Unit:    Meter

Geographic Coordinate System:   GCS_Amersfoort
Datum:    D_Amersfoort
Prime Meridian:    Greenwich
Angular Unit:    Degree

The 2nd is a polygon shapefile (map):

extent :

Top : 53,554459 m

Bottom: 50,755165 m

Right: 7,292710 m

Left: 3,361904 m

Geographic Coordinate System:   GCS_Amersfoort
Datum:    D_Amersfoort
Prime Meridian:    Greenwich
Angular Unit:    Degree

I hope you can help to find what is going wrong.

Peny

VickyNinjar

OMG! It's working!!! I've been trying to do this forever. So the only difference I can see is that I was importing from an excel file. Is that why? I don't get it really. But thank you so much

-Vicky

DarrenWiens2

The city's extent at least appears to be in the correct coordinate area. The Airbnb data seems to have been brought in incorrectly. I downloaded the listings csv and it has the correct coordinates (latitude ~45dd). Try bringing it in again from the csv, specifying WGS84 when you do so.

VickyNinjar

Hi! I have a similar issue and tried many of the proposed solutions but nothing seems to be working for me. Hope you'll be able to help.

I have 2 shapefiles, one polygons and the other points.

- The polygons are from city of Mtl open data portal (city's neighbourhoods): Limite administrative de l'agglomération de Montréal (Arrondissement et Ville liée) - LIMADMIN_shp - Portail données ouv…

- The points are insideairbnb data for the city: Get the Data - Inside Airbnb. Adding data to the debate.

For some reason, I can't get the data aligned. My latest try was to put all of them in GCS_WGS_1984.

The city's shape is returning:

Left: -73.996603 dd

Right:-73.473866 dd

Top: 45.707579 dd

Bottom:45.385402 dd

Airbnb data are returning:

Left: -142.428442 dd

Right:-142.428440 dd

Top: 16.275957 dd

Bottom:16.275954 dd

It's obvious they are not in the same range at all but I have no idea of how to solve this. Can you help please?

Thanks!!

-Vicky (not an GIS-expert!)

BTW. I've also tried using NAD83 with no success.

NeilAyres

Derek,
looking at that list of coordinates, it appears to be Lat / Long.
ie the first column is +30 odd deg , and the second column is -85 odd deg.
So when adding XY table, specify the X, Y the other way round and define the projection as GCS_WGS84 (plain geographic cords, not Web Aux). Having a quick look at my world map, these points are somewhere in Florida.
Good luck,
Neil

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!

deleted-user-ymUUSX5iRPbK

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

Best wishes,
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

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

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.!!!

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

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

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!

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

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

The TAZ layer (in Georgia statewide Lambert) appears to be around Macon, Bibb County, more or less. The other layers might be in state plane (Georgia East), but the Y values don't match up. I also checked UTM, but that didn't match either.

Melita

NathanBarnett

I'm having a mismatched projection problem as well. I have a TAZ layer, and 5 polyline files. The first polyline matches up with the TAZ layer fine. The other four come from a co-worker and I'm not sure how they were created.

The TAZ layer has the following coordinates:

NAD_1983_Georgia_Statewide_Lambert
WKID: 102604 Authority: ESRI

Projection: Lambert_Conformal_Conic
False_Easting: 0.0
False_Northing: 0.0
Central_Meridian: -83.5
Standard_Parallel_1: 31.41666666666667
Standard_Parallel_2: 34.28333333333333
Latitude_Of_Origin: 0.0
Linear Unit: Foot_US (0.3048006096012192)

Geographic Coordinate System: GCS_North_American_1983
Angular Unit: Degree (0.0174532925199433)
Prime Meridian: Greenwich (0.0)
Datum: D_North_American_1983
Spheroid: GRS_1980
    Semimajor Axis: 6378137.0
    Semiminor Axis: 6356752.314140356
    Inverse Flattening: 298.257222101

and these extents:
Y: 12503462.7160497 to 12694270.8447545 Foot_US
X: -120406.902007222 to 43657.1490820976

The first polyline that lines up well is in GCS NAD83 and has the following coordinates:
GCS_North_American_1983
WKID: 4269 Authority: EPSG

Angular Unit: Degree (0.0174532925199433)
Prime Meridian: Greenwich (0.0)
Datum: D_North_American_1983
Spheroid: GRS_1980
    Semimajor Axis: 6378137.0
    Semiminor Axis: 6356752.314140356
    Inverse Flattening: 298.257222101

and these extents:
Y: 32.8478994582219 to 32.6640322039645 Degree
X: -83.6616686449638 to -83.615816768027

The first of the other polylines (I believe) originally had no GCS but is now:
GCS_North_American_1983
WKID: 4269 Authority: EPSG

Angular Unit: Degree (0.0174532925199433)
Prime Meridian: Greenwich (0.0)
Datum: D_North_American_1983
Spheroid: GRS_1980
    Semimajor Axis: 6378137.0
    Semiminor Axis: 6356752.314140356
    Inverse Flattening: 298.257222101

(which is same as the first polyline that works).

The extents are wildly off from the working polyline:
Y: 3095050.23747941 to 3072264.87089158 Degree
X: 146084.714474299 to 157349.799715325

Usually, I receive files in GCS NAD83 (especially from the Census Bureau's TIGERline set), create polylines in the same set, and project all in a State Plane projection. I'm not sure in what GCS these polylines were created, and I can't seem to match them up. I tried changing the GCS to UTM 16 and 17 but were still too far south.

Any help lining these all on top of one another would be highly appreciated! Thank you in advance.

MelitaKennedy

I'm sorry about the delay in responding.

It looks like the first dataset has the wrong coordinate system definition. One thing I look for is what are the extent values? Are they similar to the false easting/false northing values? In this case, the false easting/northing values are 200000.0 and 300000.0, but the Y/northing values are 4.5 million. I think this dataset may be using a UTM zone instead, possibly 29N (N = north).

Melita

DianneOlson

Never mind - I figured out how to convert this!

DianneOlson

Oh my gosh I am having this same frustrating problem. I have points from our vendor and they lay just fine in Google Earth when I import them. Here are three sets of the Lat/Long.

38.7236133333 -104.6992050000
38.7238900000 -104.6989933333
38.7239366667 -104.6990150000

NAD_1983_StatePlane_Colorado_Central_FIPS_0502_Feet
Projection: Lambert_Conformal_Conic
False_Easting: 3000000.000316
False_Northing: 999999.999996
Central_Meridian: -105.500000
Standard_Parallel_1: 38.450000
Standard_Parallel_2: 39.750000
Latitude_Of_Origin: 37.833333
Linear Unit: Foot_US

GCS_North_American_1983
Datum: D_North_American_1983

When I dump the exact same lat longs into Arcmap, they do not come in correctly. I see from the extent that these points are
Top: 38.728807 ft
Left: -104.699205 ft
Right: -104.694992 ft
Bottom: 38.722677 ft

My pole point extents are the following:
Top: 29887959.6930 ft
Left: 0.0 Ft
Right 84146321.696 ft
Bottom: 0.0 ft

My light point extents are similar to my pole extents. In fact all of my data in my master map has similar extents.
Top: 1336807.832 ft
Left 0.0 ft
Right: 3239698.78800 ft
Bottom 0.0 ft.

What in the world is wrong? Looks like these points are about 658 miles away from one another!

Thanks for any help. I'm leaving for the bar now!

NeilAyres

Melita,
you must have the patience of Job!
Keep up the good work.

DuartePrata

Hello! I'm a novice in Arcgis and I´m also facing a similar problem... I cant align points created in excel to a map that I already had.
For anyone that can help, here is the info:

Points

Projection: Transverse_Mercator
False_Easting: 200000.000000
False_Northing: 300000.000000
Central_Meridian: -8.131906
Scale_Factor: 1.000000
Latitude_Of_Origin: 39.666667
Linear Unit: Meter (1.000000)

Geographic Coordinate System: GCS_Datum_Lisboa_Hayford
Angular Unit: Degree (0.017453292519943295)
Prime Meridian: Greenwich (0.000000000000000000)
Datum: D_Datum_Lisboa_Hayford
Spheroid: International_1924
    Semimajor Axis: 6378388.000000000000000000
    Semiminor Axis: 6356911.946127946500000000
    Inverse Flattening: 297.000000000000000000

Extent:
Top:4644500.000000 m
Left:654925.000000 m
Right:720825.000000 m
Bottom:4561986.000000 m

DEM

Projection: Transverse_Mercator
False_Easting: 200000.000000
False_Northing: 300000.000000
Central_Meridian: -8.131906
Scale_Factor: 1.000000
Latitude_Of_Origin: 39.666667
Linear Unit: Meter (1.000000)

Geographic Coordinate System: GCS_Datum_Lisboa_Hayford
Angular Unit: Degree (0.017453292519943295)
Prime Meridian: Greenwich (0.000000000000000000)
Datum: D_Datum_Lisboa_Hayford
Spheroid: International_1924
    Semimajor Axis: 6378388.000000000000000000
    Semiminor Axis: 6356911.946127946500000000
    Inverse Flattening: 297.000000000000000000

Extent:
Top:560000 m
Left:263999.999999999 m
Right:375999.999999999 m
Bottom:460000 m

It seems that is the extent that is wrong... How can I correct this?

Thanks in advance!

MelitaKennedy

Hi Rachael,

The points are in UTM zone 12 North, rather than 13 (very generally: Red Hill area of the county). Try defining the data as NAD 1983 UTM Zone 12N. At that point you can either let ArcMap project it on-the-fly to zone 13, or create a copy via ArcMap (right click in the table of contents, data, export data, choose to export in the data frame's coordinate system) or the Project Tool (once the points are in a shapefile or feature class).

Hope this helps,
Melita

MelitaKennedy

Hi,

We really need an example point from the CSV file, plus a general idea of what location the data represents (county, city, etc).

Melita

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

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

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

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, 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

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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