The following text describes the issue that we are running into when trying to import a new ASCII text file into a survey basemap drawing.
PROGRAM BEING USED::::: ODOT cadd Power GEOPAK SS4 - Version 08.11.09.878
Using the Survey Menu; create a new dataset, specify the text file to import, once import has started a box pops up warning us we are about to overwrite a point (ie: CALC1002), this point did not exist in the GPK prior to importing this new text file.
We select the option to add a prefix to the point number that is being overwritten (ie: ARCALC1002) and hit apply
After applying, it continues to warn us that we are overwriting more points that did not exist in the GPK prior to this import (ie: CALC1004, CALC1005….) and it keeps wanting to overwrite the same CALC point over and over again (2 or 3 times per point), adding 1% to the total import every time.
SUMMARY: it keeps wanting to overwrite points that are being created from the same DATASET that I am trying to import, even though these CALC points did not exist before selecting the new text file.
what are solutions to fix this? We cant import any other text files without it trying to overwrite points that didnt exist until this import
the issue is we already have files imported into the GPK, if we start from scratch we will have to re-do all of our linework and changes to the data. is there a way to set the CALC point range of what numbers to use?
You may want to edit the data set first before you import into the GPK file. You can multi point select and add a value so as to move to a new point range for the CALC points. So go from CALC1000 to CALC2000
For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki
i tried this and my microstation would crash every time while importing. i just uploaded all of my program files to the FTP site
Delete the CALC10000 to CALC10010 from the GPK using the COGO Navigator. Then process the ASCII file again. It should then start at CALC250.
Answer Verified By: Adam Ryan
that was it... any idea why those calc points were causing it to freak out?