C3D/Map 3D UTM83 Zone 17 Coordinate System

[CivilFlow]

Hello,

We have a pipeline project where we are networking with another consultant who is using ESRI ArcGIS to export either .gdb or .shp files for our use.  Their mapping projection is set to:

NAD_1983_UTM_Zone_17N",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",1640416.666666667],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-81.0],PARAMETER["Scale_Factor",0.9996],PARAMETER["Latitude_Of_Origin",0.0],UNIT["Foot_US",0.3048006096012192]]

The problem we're having is that the C3D/Map3D 2018 coordinate system library doesn't have that option for "17N".  The only option I see that is remotely similar is "UTM with NAD83 datum, Zone 17, US Foot; Central Meridian 81d W", but that doesn't work...neither do the following: NAD83 / BLM 17N (ftUS) or NAD83(CSRS) / UTM zone 17N.  We just get a prompt at the command line that says "entities were skipped due to failed coordinate transformations".

Of course if we strip the mapping projection from the C3D drawing and keep it no datum no projection, everything comes in fine.  I am just wondering if anyone as the steps to add this coordinate system to our C3D/Map3D library?

I am attaching a few .shp files from ArcGIS.  The proposed pipeline centerline, work areas, and access roads. All have the same .prj file setup indicated above.

Many thanks.

[rl_jackson]

I'm not a coordinate projection wizard, but I would bet @Pointdump could point you in the right direction.

[Pointdump]

Hi Mike,

I was able to both _MAPCONNECT and _MAPIMPORT your Shapefiles. They are right on the eastern edge of 17, in West Virginia and North Carolina. Here's the projection I used:

You'll need to Edit the Coordinate System of the Shapefiles:

 

Dave

[CivilFlow]

Thanks for taking a look at this Dave.  Which version of C3D are you using? 

I am using C3D18.2 and get errors when trying MAPIMPORT or MAPCONNECT methods.  Please watch the attached short animated .gif showing my workflow steps that lead to nothing getting imported from the same .shp files I posted earlier.

I'm not sure what is going on.  

[rl_jackson]

Set your shortcut for C3D to "run as admin" that reduces map etc issue....

[Pointdump]

Mike,

I'm also running 2018.2.

When you _MAPIMPORT you need to edit the Coordinate System of the Shapefile, but for _MAPCONNECT I did exactly the same as you and have no idea why it didn't work.

Dave

[Pointdump]

Mike,

OK, I'm able to re-create the error when I _MAPIMPORT without editing the Shapefile's Coordinate System:

Dave

[Pointdump · Accepted solution]

Mike,

I can fully re-create the problem when I use Drawing Settings to set the Coordinate System. I normally use _MAPCSASSIGN. Try that.

Dave

[CivilFlow]

Thanks Dave.  I was able to get MAPIMPORT to work with the UTM with NAD83 datum, Zone 17, US Foot; Central Meridian 81d W projection assigned via MAPCSASSIGN command and then editing the Input Coordinate System again to be the same in the MAPIMPORT\.shp dialog.  Then it imported as expected.  

For the MAPCONNECT option I had to do the same.  Specify the coordinate system via MAPCSASSIGN first, then edit the incoming schema's coordinate system to be the same.  Then it worked as expected.

I have no idea why I have to double up these coordinate system assignment steps on my end, but I'm happy it is working now.

Thank you sir for your time.

[Pointdump]

Mike,

But wait, there's more! Something in the dim recesses of my old brain remembered <<<This Post>>> from @Alfred.NESWADBA.

Dave

[Pointdump]

Mike,

Deleting the IDX files allows you to use either Drawing Settings or _MAPCSASSIGN to assign a coordinate system, but you still need to edit the shapefile CS for both _MAPCONNECT and _MAPIMPORT.

And of curious note, QGIS, which normally gets things right every time, doesn't quite know what to do with those shapefiles, and places them somewhere on the other side of the world.

Dave

[CivilFlow]

Thanks Dave,

This is good info and I will confirm if this .idx deletion helps remove the "extra" coordinate system edit I had to do on my end to get it to work..  I checked the original .shp and .gdb files in ESRI ArcMap, and they have that UTM projection defined with a "17N", which could be the culprit...not sure.  I'm just happy I'm able to use these .shp files in C3D/Map3D with the workflow described above.  Thanks again for your help.