I am exporting shape files for a GIS user. I am using the correct coordinate system and my untis are in feet and decimal degrees. I can export the lines and points with attributes and they import into GIS just fine. When I export a polygon with or without attributes, when i improt them into GIS i get the error "One or more of the added layers has an extent that is not consistent with the associated spatial refernce." Any ideas what I could do?
Thank you for posting to the Autodesk Discussion Groups.
I'd like to help you resolve this, but the first step really is to gather enough information about your situation.
Below I have posted a few questions, and have implied some suggestions within them. So please try the suggestions, and if you resolve this, let us know what you did, for the benefit of myself and the community. If you are still having trouble, please post your answers to the questions.
1. What specific action is triggering this error message, and in what program is the error occuring in? A screenshot would be helpful to demonstrate this too.
2. Can you FDO connect to the "problematic" polygon shapefile in AutoCAD Map 3D? Is there any trouble when doing so? If yes, specifically what happens?
3. Which coordinate system is associated with this problematic shapefile? Have you tried using a coordinate system with smaller extents (such as a State Plane CS instead of a World or Continental CS)?
1. When the GIS user try's to improt the shape file into arch gis they get the following error
2. When I try and FDO connect the polygon back into Civil 3D Map it doesn;t report an error and it brings in the layer but the polygon does not show up. Also this is not one specoific polygon that gives me trouble it is all polygons and the lines and points work just fine.
3. I am using the UT83-CF (Utah State Planes; NAD83 datum, Central Zone, US Foot) This was the coordinate system I was directed to use by the GIS user who works for a municipality but am willing to try something else but not sure which to try.
Thank you for your reply.
I don't have ArcGIS to test with here, but here are a few more considerations:
You could check the ESRI resources for more information on that error too.
I hope this helps!