Latest Contributions by MelitaKennedy

I don't know what is happening, but you might use the Check and Repair Geometry tools to see if anything is reported. Possibly also check whether you have have multipart polygons. That could cause labels to show up in odd places. ... View more

Hi, in NAD27, Texas North Central uses US survey feet and has: false easting: 2000000.0 USft false northing: 0.0 USft In NAD83, it can use meters or US survey feet. The meter version uses: false easting: 600000.0 m = 19685000.0 USft false northing: 2000000.0 m = 6561666.66667 USft I am wondering if there's some confusion in the georeferencing. Once you georeference the rasters, is the coordinate system listed as NAD27- or NAD83-based? And is that information correct? If the coordinate system is set to NAD83-based, but you georeferenced with the NAD27-based coords, that would case the raster to show up south of where it should be. I think you should georeference in a NAD27-based workspace (set ArcMap to use NAD27 TX NC), define the coordinate system, then use the Project Tool, or set the data frame to NAD83 TX NC and use data, export data. Hope this helps, Melita ... View more

Are you using ArcMap or something else? There is possibly some information here: http://forums.arcgis.com/threads/13386-Changing-ArcGISTiledMapServiceLayer-(in-a-different-spatial-reference)-at-runtime And here: http://forums.esri.com/Thread.asp?c=158&f=2396&t=294947 Basically, I don't think tiled map services can be reprojected. Melita ... View more

Unfortunately, this data is very unlikely to be in Esri geodatabase format. A file geodatabase is a folder of files and a personal geodatabase has an .mdb (Microsoft Access) extension. It look like it's a Garmin format. The Data Interoperability extension may support it, but I don't think it's natively supported in ArcGIS. Melita ... View more

I've been given a new shapefile that is not posting correctly with my other raster and vector data. I've noted that this new shapefile's geographic (decimal degree) Bounding Coordinates (as viewed in ArcCatalog) appear to be corrupted; my project is over southern Chile in Patagonia. Can bounding coordinates be edited? I've been trying a number of methods to no avail. Here is what the Bounding Coordinates look like in ArcCatalog: Horizontal In decimal degrees West: -69.000667 East: -69.000648 North: -0.000420 South: -0.000465 In projected or local coordinates Left: -74.270841 Right: -72.133334 Top: -46.438227 Bottom: -51.448022 Kind regards, gleonard Hi, I'm sorry that I've taken so long to respond. I was out of the office. I did write up a response on my phone a few days ago, but it didn't get saved and published. The data has a projected coordinate system assigned to it. When calculating the decimal degree extents, the software takes the projected/local values and unprojects them to the PCS's geographic coordinate system. If you look at the projected/local values, you should see that these are already in decimal degrees. Redefine the data in the appropriate geographic coordinate system, and it will display correctly. If you want to make a copy that uses a projected coordinate system, use the Project Tool, not the Define Projection Tool or the data's property page in ArcCatalog. Melita ... View more

Hi All, I was hoping that someone else has run across this problem OR that someone out there can test it and see if they come across the same issue. I have a 1000mx1000m grid in GDA94, MGA zone 56. I wanted to re-project it into AGD66 AMG Zone 56 so that I could georeference an old topographic map. Using the Project tool in Arcmap, using any of the provided AGD66 to GDA94 transformations, produced a grid that was shifted the correct distance, but south west instead of North east! Any comments or similar findings would be welcome. (If this is a real bug I will report it to ESRI) Hi Lauren, That's generally what I would expect for the change in direction. Don't forget the the older map grid  has "even" values--you're not going to match that grid by using "even" values in GDA94 and transforming it back to AGD66. Can you tell me more specifically where the data's located? I may then be able to check against the appropriate state transformation program. Melita ... View more

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 ... View more

I'm just glad you've got it working! Melita ... View more

OIDs are maintained by ArcGIS to ensure an unique identifier per feature. So a field marked as esriFieldTypeOID won't be editable. Fundamentals of ObjectID Fields Melita ... View more

Please see response on gis.SE. And here's another answer on the archived forums: http://forums.esri.com/Thread.asp?c=93&f=993&t=136245&mc=3#msgid394974 Please try to not post the same question on multiple forums until there's a chance for a response from one of them. Melita ... View more

Hi, You certainly seem to have done all the right steps! When you looked at the point info in the output shapefile, did you look at the attribute table? The attribute table isn't updated when a dataset is projected because we don't know if you want those values updated. The actual values are stored internally. Add the output shapefile to a new ArcMap session. What is the data frame's coordinate system set to? You may want to also check the map units (data frame properties, general tab) as the map units reflect the data frame's coordinate system. If you then change the display units to degrees, you can check that the points are in the right location. How far off is this data relative to the photos? A few feet or meters? Hundreds of meters? Or Kilometers away? Can you post a sample lat/lon point, plus its corresponding state plane coordinates? Thanks, Melita ... View more

I haven't used the geocoder, so I can speculate only on what's happening. I believe the shapefile itself, as you said, is using NAD 1983 StatePlane Maryland FIPS 1900 (feet). Is it officially defined? When you use Calculate Geometry, try these steps. 1. Add the data to ArcMap. 2. Set the data frame's coordinate system to NAD 1983. 3. Calculate Geometry and use the data frame's coordinate system. That should enable the unit pull-down and it should default to decimal degrees. Another option is to project (not define projection) the data to a new shapefile using NAD 1983 and then calculate geometry using this data's coordinate system. Melita ... View more

Thanks! That was very useful. The relevant bit was here: S t a t e P l a n e _ 1 9 8 3 _ L A S o u t h _ S u r v e y F o o t   F F N A D 8 3 - L A S o u t h - 1 S u r v e y F o o t That tells me that it's NAD 1983 State Plane Louisiana South using US survey foot. Ah, but when I look at the coordinates for LA South (US feet), I'm seeing values in the 3million, 300thousand. If the shapefiles represent somewhere in Livingston county, the data itself is NAD 1983 State Plane Louisiana South (meters). Try defining them using that coordinate system. If the shapefile is really using NAD 1983 State Plane Louisiana South (US feet), the data shows up in Atacosa county, Texas. Melita ... View more

Oh, I see. Can you get any useful information out of the .csf files? If you want, you can send me one and I can see if I can figure out anything. mkennedy AT esri DOT com. You can also take a look at one of the new shapefiles, on its own, in a new ArcMap session. That will at tell you if the coordinates are using a geographic or projected coordinate system. Melita ... View more

Hi, My first question is which tool, Define Projection or Project? The first only updates the metadata and doesn't change the coordinate values to the new coordinate system. If you are using the Project tool, it may be that 1) the input data's coordinate system is incorrect (projecting it just makes it worse) or 2) there's something else wrong with the data so it's not projecting correctly to UTM 15North. Can you post some sample coordinates before and after? Melita ... View more