Civil 3D - Importing Lat-Long Format Points

[cturlington]

Hello,

I am using Civil 3D 2017.

Have been trying to import a text point file.  The message I keep getting is "No points were transferred from the source".  The file is shown below for your reference.  The point file format I am using is also attached as a screen capture.  It has been some time that I have had issues importing a lat-long file, but do remember my first day with these same issues, seems like it is back to haunt me.  It has been my experience that the process is very temperamental.  I tried csv file format, then changed to text, remembering someone commenting that text files worked better, except now of course.  Any advice is appreciated.

200, 33.32705278, -79.36267500, 24.17, WGS-12
201, 33.32662778, -79.35984722, 24.16, WGS-11
202, 33.32626944, -79.35686389, 24.29, WGS-10
203, 33.32548611, -79.35293889, 26.91, WGS-9
204, 33.32048333, -79.35176111, 26.16, WGS-8
205, 33.31741111, -79.35153333, 24.63, WGS-7
206, 33.33166389, -79.35921667, 25.36, WGS-3
207, 33.33124167, -79.35591389, 26.8, WGS-4
208, 33.32997500, -79.34913611, 30.88, WGS-5
209, 33.32951944, -79.34460833, 24.65, WGS-6
210, 33.33660000, -79.36967778, 12.46, WGS-1
211, 33.33810556, -79.36779167, 10.85, WGS-2

[Pointdump]

Chuck,

Check the "Coordinate Zone Transform" box and select LL84. Then it'll work.

Dave

[Pointdump]

Chuck,

Like this:

 

Dave

[cturlington]

Dave,

It looks like the only difference is the "#" symbol in the comments field and a single space after the comma, instead of a tab.  Is that correct or were there other format issues ?

[cturlington]

Dave,

I update my point file format to match exactly the one you had in your file.  I am attaching the screen shots of those settings and error message below.  The changes I made are this:  The text file I changed by deleting the tab separation between the comma and text, using a comma and space between text instead.  I also changed the point file format to have the "#" symbol in the field adjacent to txt format field and added -999999 to the elevation Invalid Indicator field.  I also checked the transformation tab in the point file format to LL84 and checked to perform "transformation if possible" in the point import dialog.  However, not sure why this would be necessary since the points are a result of performing a query of the autocad point and transforming the file from a NAD83 State Plane Harn Int'l Feet to LL84.  The error message below does not make sense if the drawing file is an LL84 coordinate system format, why would it not be set that way ?  What else could I be missing that these points will not import.

[cturlington]

Dave,

I update my point file format to match exactly the one you had in your file.  I am attaching the screen shots of those settings.  The warning/error message I get is this: "A non-LL coordinate zone must be set for this drawing when latitude, longitude, or grid coordinates are used in a format.  No points were transferred from the source."  The changes I made are this:  The text file I changed by deleting the tab separation between the comma and text, using a comma and space between text instead.  I also changed the point file format to have the "#" symbol in the field adjacent to txt format field and added -999999 to the elevation Invalid Indicator field.  I also checked the transformation tab in the point file format to LL84 and checked to perform "transformation if possible" in the point import dialog.  However, not sure why this would be necessary since the points are a result of performing a query of the autocad point and transforming the file from a NAD83 State Plane Harn Int'l Feet to LL84 already, I am just importing a text or csv file to convert the AutoCAD points to civil 3d points.  I could just use the convert points inside the drawing but then I do not get the elevation.  The warning / error message in quotes above does not make sense if the drawing file is an LL84 coordinate system format, why would it not be set that way ?  What else could I be missing that these points will not import or how am I to interpret the error message to correct my import format.

[Pointdump]

Chuck,

That dialogue box is just telling you that you don't need to tell C3D what coordinate system your imported points are in if they are not going to be transformed. If your drawing is in State Plane and points are LL, then you definitely need to check that "Coordinate Zone Transform" button.

The comment tag is used to "hide" the first row of your point file. If you use "#", then your first row can read "#Durn these durn point file formats!" and C3D will ignore that and still import your points.

Not sure why your point import is failing. Can you post your point file? Sometimes it's some small detail, like a letter in one of your point numbers.

Dave

[cturlington]

Dave,

The text file I am is attached.  I have also attached the drawing file for your reference.  The point file format in the drawing that I am using is called: "PLATLONGZD"

Thanks again for all your help.

[Pointdump · Accepted solution]

Chuck,

OK, I get the same thing. Interesting. I learned something. The points will import into your LL84 drawing if you choose PNEZD, but of course the drawing wouldn't be very useful.

But if you change the drawing's coordinate system to SC83F, then your point file imports with no problem using the PLATLONGZD format.

Dave

[Pointdump · Accepted solution]

Chuck,

Oh, and if you've noticed the Bing Live Maps degradation in the last week, it's time to add <<<ArcGIS for AutoCAD>>> to take advantage of ESRI's sharp World Imagery:

Dave

[cturlington]

Dave,

Both approaches allow the points to import, but they do not appear to land at the correct location.  I guess this demonstrates the limits of the software to attempt interpretation of  geographical coordinates in a "flat" environment.  It seems like the bottom line is; if I need to work with true geographical coordinates, I have to use software that interprets the 3d coordinate systems and not just grid based ones.  I think that is interesting, was not aware.  However, if I am incorrect with my assessment, please do not hesitate to let me know.

BTW:  The ArcGIS connection with CAD is pretty cool.  It will be nice to see if it lasts for awhile.  Thanks again for all your help.

[Pointdump · Accepted solution]

Chuck,

"...limits of the software to attempt interpretation of geographical coordinates in a 'flat' environment."

"...they do not appear to land at the correct location."

Fair enough assessment. But consider that EVERY Projected Coordinate System is based on a Geographical Coordinate System and a Datum to tie that GCS to the round world. C3D does a pretty good job of converting Lats and Longs to whatever Projected Coordinate System you use, and since all work in this world is done with length units, I think it's best to stay in Projected Coordinate Systems.

Dave