The original data source, combined with an alternate workflow that avoids the use of a county based CS, will resolve your issue. ![]() If you can't or are unable to re-create the drawing, then upload your source files in their original format with their original projections so a workable procedure can be explained. If you can re-create the drawing in State Plane-North Zone-NAD83-feet (or UTM83-15N meters) then it'll be easy to transform and view your objects in Google Earth Pro. I suspect this is due to a scale factor applied to the ellipsoidal models MN uses in their county projections. (Of course, that's pure speculation.) ![]() Your MN County's CS can be transformed but it results in an error and places your linework in Canada which is too far north. MN is one of two states (WI is the other) which has county-based projections in addition to SPCS/Zone projections. Had you original CS been in State Plane MN83-NF or in UTM83-15N, then the transformation would've been easy. Your chosen coordinate system, however, is a MN County based coordinate system, and those systems are not very friendly with other coordinate systems during transformations. It’s also a good idea to assign the coordinate system to your new shapefile. Name the new polygon Poly1 and define the feature type as a polygon. the folder where you want to create your new shapfile), then select New > Shapefile. ![]() It will not only reproject your drawing, it reproject it on-the-fly. In ArcCatalog, right-click on your project folder (i.e. ![]() For example, if you want create a drawing in the State Plane Coordinate System (SPCS), your original drawing can be using UTM, WGS84PseudoMercator, LL84 or LL83, and Civil3D/Map3D will perform the transformation for you. Civil3D/Map3D is more than capable when TRANSFORMING from one coordinate system to another. Your issue is in your dwg's assigned coordinate system.
0 Comments
Leave a Reply. |