Help!

Hello, I am new to geopak, and have been working in some trainings and stuff...I am now trying to understand how to create vertical alignments, and i am able to get to the point of drawing my existing ground profile and adding new VPI in the profile generator dialog box, but when I try to save this new profile I get a message: A VALID NAME IS REQUIRED TO STORE PROFILE and I have tried overwriting the profiles that appear in the profile pull down and tried new names, and changing the input file name, and creating a new ex ground profiles, but I just keep getting this message, can someone please tell me what the problem might be???

~Thanks
N.Flores

Parents
  • when you click save profile as, Make sure that you use a name with no spaces and not longer than 8 characters.

    Also,

    in the save as dialog, it has a field for creating a cogo input file for this profile.

    use a name with this format

    NAME###.ioc

    The name is the name of the file (5 characters max)

    ### is your gpk job number (ie 444)

    .i means input and oc is your operator code. (the same operator code you use to log into cogo)

    Do not leave the input file name field blank and if it is not blank, write down the name of the file in the field and go delete it from your working directory and or your gpk directory.

    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

     



  • Thanks for the replies!  I had someone suggest to reset geopak through cad conform and it force me to close the profile generator tool.  So I lost the data and had to start over.  It wasn't a naming issue.  I used the same naming convention later on and it worked just fine.  Something must have been wrong in the resource files.

Reply
  • Thanks for the replies!  I had someone suggest to reset geopak through cad conform and it force me to close the profile generator tool.  So I lost the data and had to start over.  It wasn't a naming issue.  I used the same naming convention later on and it worked just fine.  Something must have been wrong in the resource files.

Children
No Data