point creation stops comma delimited file if there is a space in the data

[lpugliani]

I tried to insert points using "create points - alignments - from file" using a text file that was hand generated. The file had a space after the elevation, right before the comma that precedes the  description. I used option 5 (station, offset, elevation, description). All the data came in except the elevations of the few points that had a space after the elevation. Why does this happened in a comma delimited file? Is there a fix for this?

[wfberry]

I went back and looked at my comma delimited points.  It appears that all of my points do not have a space.  So I guess you need to eliminate the spaces.  So it is either space delimited or comma delimited.

Bill

[cwr-pae]

I think its dependent on the data format of the column (property classification) in the point file format. We use spaces in almost every description for survey points and have no issues. But that column is formatted as a string, not an elevation. I would suggest not using spaces or other text in the elevation column. Creating a user defined property classification for elevations formatted as string would be possible but I think I would advise against that. You can not change the column's format in 'standard' classifications only in user defined ones.

Find and Replace in Excel or Notepad could be used to remove undesired spaces from the files before import if necessary.

[lynn_zhang]

Hello @lpugliani ,

Just checking to see if your problem has been solved. Have you tried the suggestions from our experts above and did they help? If yes, please click on the "Accept as Solution" button in their reply or let us know if you still need help. Thanks!

[Civil3DReminders · Accepted solution]

This issue should be logged as a bug in the program. At AU Autodesk bragged about AI, this appears to be a perfect situation for AI to be applied to make the import process smarter to provide an awesome user experience instead of the horrible one described by the original poster. An expert giving a workaround should never be taken as an acceptable solution when Autodesk should be providing a programming fix to prevent this common point import issue from happening. For the non-AI solution, Autodesk should be running the common string's Trim() method to remove any leading or trailing spaces on an expected number field.

Feel free to post the issue number after logging it as defect so all the community members can track Autodesk's progress in addressing this issue. 

[Christopher.Fugitt]

 @lynn_zhang While @lpugliani has marked my post as the solution, you'll notice that I called on Autodesk to provide the programming solution to resolve the issue. Hopefully, you'll provide the link between the Forums and the Developers to resolve this issue in update 2020.3, which should be totally doable based on the lack of complexity of solving the issue.

[rl_jackson]

The solution to this is to go to your "file" and remove the space or put an elevation of 0.00' or -9999999. or something. I think if you remove the space the data will import and that point will be at 0 or the old default -9999#.

I don't see any bug or error short of the error in your data that is being provided.

[Civil3DReminders_com]

As a person who supports thousands of potential users of Civil 3D, I don't want to have to answer this questions a hundred times or have to look at text files to determine whether or not the an extra space is after a number in a text file. This task has wastes hundreds of hours of me having to look at text files to find out what pattern a person has violated when it could have been easily solved via programming with a more robust text parser. You might be happy with this time wasting activity, I find it abhorrent.

[lpugliani]

This also happens when you have spaces in text descriptions in data collectors. It can be solved with a few lines of code. If I remove the spaces, the point descriptions are combined into one "word"

[rl_jackson]

I did a little testing an created a data file in Excel by hand and left the elevation cell empty for one of the stations. Exported/saved as a cab file and got no space for that cell. It was comma comma as it should be. Could there be a workflow error can you provide your data?  Is this space human error? How was the handmade data created?

Spaces in the description are used for other things. And are a very powerful source of transferring information into the model including providing the ability to insert blocks, draw linework form field survey data, and much more. You should look into the help for description keys and the survey database automatic linework capabilities.