I am an autocad and ESRI user who is trying to better intergrate the functions with Map 3d. I am having problems with drawing units when connecting to GIS data. I live in TN, so I have set the coorinate system to TN NAD 83, Feet. When I connect in a NAIP aerial, it displays properly. When I measure anything, however, the distances are off by a factor of about 1/3. That is, something that is supposed to be 18' is measuring 6'. I have played with the units, but can't seem to come up with an answer. Any help would be appreciated.
That thought did cross my mind. I have played with the different units coordinate systems, and nothing changes. Here is the only pertinent information from the USDA image metadata:
Grid_Coordinate_System_Name: Universal Transverse Mercator
Horizontal_Datum_Name: North American Datum of 1983 (NAD83)
I didn't see anything about units. Anyone know if the UDSA aerials are in metric, and if so, how to correct this? I have sucessfully connected to shapefiles and google earth images, so I am pretty sure it is something with the aerial itself.
. Anyone know if the UDSA aerials are in metric, and if so, how to correct this? I have sucessfully connected to shapefiles and google earth images, so I am pretty sure it is something with the aerial itself.
IIRC some of the images from USDA are in metric even when the metadata states otherwise. Where abouts in TN are ya?
USDA is metric. Are you using FDO or MapIINSERT? make sure you set the drawing coordinates to metric if using mapiinsert. fdo will transform, mapiinsert wont... you need to insert in metric and perform a drawing query to transform utm meters to nad feet if not using FDO...
I have tried using mapiinsert and connecting to the SID file via the task pane (connect to data) and get the same result. When I connect to shape files that weren't provided by USDA, everything comes in to scale and in the right location (even if i created the shape file in ArcGIS drawing on top of a USDA aerial). Both image and shape files directly from USDA come in scaled to metric and in the wrong location. I have never had these problems in ArcGIS. Any ideas?
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register