I have an issue where my files stop recognizing the new survey point that I import.
The issue is some times will bring in the points but I will not create the linework, I can't create the linework since changing the link code does nothing. Also, I have had this happen more than once where certain codes are not recognized so the points will not come in all together no error shown since the codes are valid codes just not processed. none of the times is the surface updated or created.
I have spent three days trying to troubleshoot this issue to no avail. Does anyone have similar problems that they have been able to fix?
I have tried recreating the drawing with a clean seed file, which worked for a while, and then it stopped altogether so I am back to the beginning. any help would be nice. I have made sure the feature definitions are all set up correctly.
A few questions come to my mind:
I had an issue a year or more ago that my ascii files would not import to ORD, no matter the size or format. It shut me down for almost a month. We made a few changes to Windows10 memory settings and it started working again. I dealt directly with a Bentley account manager as this was a serious problem. I'm personally not so sure it wasn't a combination of memory settings and Windows updates that caused the issue. Long story short we never nailed down the source of the issue.
I am importing .csv files with Point names, Northing, Easting, and Elevation
No, the Points show up but the linework is not drawn and it can't be manipulated once its process
Yes the data is going into the same fieldbook
I have compress the file
yes I am working on UDOT's Workspace
ORD Version 10.09.00.91
.csv files i will add in later post
It's hard to show really the issue but technically I can't edit any of the points to change their code, example if it's a start point I can't switch to a start pc or an endpoint so whatever comes in that it's it.
Another example is where it brings in the points but nothing is drawn out
Here the points are in but the line won't be drawn out and can't be manipulated to do so unless I draw a line manually which defeats the point.
let me know if you have any other questions
GPS_SAL_031621.csvGPS_SAL_031021.csv
Here are the .csv
Did I see in another post you were having issues with Project Wise? Is this issue related to that?
Project settings in ORD are critical the survey workflow. I sent over the default settings for FDOT. Are you familiar with these settings?
I downloaded and looked at the data. Nothing looks out of the ordinary for ascii data format. I assume you have you project configured to use your linking codes. I highlighted what I think are linking codes in your sample data.
Everything in the file seems fine. I really don't understand the issue and is driving me insane I am way over the hours for this task so now is all on my own time. which would be fine if I had a path forward but I don't yet. So I guess ill just keep dealing with this disaster.
Was the software working before? I did notice a setting in your prefs different than what I use. The other options for this setting do directly impact how the data is edited post import.