Creating a shape file

[Bkilen]

Hello,

I am attempting to create a simple shape file. When I type mapexport I see the .esri file but not the .proj file. I only see the .proj file when I convert the benchmark... Also when I import my shapefile into google earth it does not place proper placement. it is way off... Also the area I am in is not supported by epsg.... Attached is the file

Thanks,

Brad

[rl_jackson · Accepted solution]

Why are you trying to create a simple shape file with 2-point clouds + in different areas in the same file in Minnesota that is over 13mb, and don't even reflect the datum as simple BingMaps don't show anything in the area. Minn does have a ESPG code, and your strawberry patch isn't located in Minn.

When you move all those surfaces to separate files you'll get better support to have roughly a mile of point cloud data in one file in completely different sectional areas is just crazy at best.

Otherwise for your simple little strawberry batch, try EXPORTKML and select the objects you want to export, GE will take care of the rest.

[Pointdump]

Hi Bradley,
"I only see the .proj file when I convert the benchmark."
I'm not following you there. More details please.
Definitely something inexplicable going on with the drawing. I couldn't make MAPEXPORT work no way no how. I even tried converting the export to LL84.
Dave

[Bkilen]

Here is the .prj file created when converting from the coordinates to LL84

[Bkilen]

Here are screenshots showing the steps I took

[Pointdump]

Bradley,
I don't see the PRJ or screen shots attached to your posts.
Dave

[ChicagoLooper]

Thanks of uploading you dwg file.

Your issue is in your dwg's assigned coordinate system. Civil3D/Map3D is more than capable when TRANSFORMING from one coordinate system to another. 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. It will not only reproject your drawing, it reproject it on-the-fly.

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. Had you original CS been in State Plane MN83-NF or in UTM83-15N, then the transformation would've been easy.   

MN is one of two states (WI is the other) which has county-based projections in addition to SPCS/Zone projections. 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. 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.)

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. 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. The original data source, combined with an alternate workflow that avoids the use of a county based CS, will resolve your issue.