GPK Drainage - Show water and sewer crossings in profile?

Support is trying to resolve this issue.  They have my files and are able to get the water crossings to display on the drainage profiles, but then the sewer crossings that I was able to display disappear.  I have the opposite problem:  I can get the sewer crossings to plot, but not the water crossings.  I am anxiously awaiting their answer.

Josh

It sounds like the water and sewer plan view graphics are using the exact same symbology, or something similar, such that the water & sewer lines are displaying the same and alternately confusing the profiler.  Also check your DDB file, water and sewer pipes, and make sure they're not using the exact same value in the attribute field.

Dan,

Everything checks out.  My sewer and water lines are drawn using different library items, each with unique symbology and attributes (double checked).  I even deleted and recreated the offending water lines.  They are visible as a file referenced to my Drainage file.  I still have the same problem with Drainage only recognizing the sewer lines.  However, in Water and Sewer, the drainage crossings show up on the water profile.  This project happens to NOT have any sewer vs. water crossings, only sewer AND water crossings vs. drainage lines.

Thanks for you help,

Josh

Sounds to me like all is well.  Are you sure the water crossings are toggled ON and those levels are turned ON in the dgn file (see attached)?  If you're in a 3D file, is your display depth wide enough to display everything?  Also try running the Conflict Finder, Drainage vs. Water and see if it can find the crossings.  One way to isolate the problem is draw the water lines in the same dgn as the drainage lines; if that works, its probably a problem with reference file attachments (update sequence or models or... ).  That may be more trouble for you than its worth though, support should be able to locate the issue; be sure to let us know what they come back with too.

Josh

I have occasionally seen projects which defy explanation and will not show some of the crossings.  If you can call our support line and send your dataset will accomplish two goals:

1. If there is a slight issue in your settings that is causing them not to show then they can help find it.  Dan's instructions are very thorough so it seems increasingly unlikely that this is the case.
2. If there is a bug then the dataset will help us track it down.

Sorry Josh - Just noticed that you already have placed a support call.

Dan,

I think we might be getting somewhere.  When I open a water profile, GEOPAK thinks for a short while (presumably generating elevations along the plan view element), but then all the options in the profile box revert back to some sort of default state.  I then have to open an existing symbology settings file to apply to each profile every time I try to edit them.  This does not happen in Drainage.  The first time I try to File Open a settings file Water and Sewer looks for a .wsp file.  I cancel the File Open dialog.  Then if I do a File Save As it tries to save a .ppf file.  I then cancel out of the File Save As dialog and immediatley do a File Open again, and now it is looking for a .ppf file, which I then select and open in order to set all of my settings for my current profile.  I need to do this on each profile as I open them.  Could the problem be that I don't have a .wsp file?  Even without a wsp file, WatSew is not remembering any of my profile settings that were last stored with the profile.  Each profile could theoretically have different settings, right?  All of mine are the same, but each profile's settings can be stored independently and don't need to refer back to a "master" settings file, right?

Thanks for all the help,

Josh

Dan,

I think we might be getting somewhere.  When I open a water profile, GEOPAK thinks for a short while (presumably generating elevations along the plan view element), but then all the options in the profile box revert back to some sort of default state.  I then have to open an existing symbology settings file to apply to each profile every time I try to edit them.  This does not happen in Drainage.  The first time I try to File Open a settings file Water and Sewer looks for a .wsp file.  I cancel the File Open dialog.  Then if I do a File Save As it tries to save a .ppf file.  I then cancel out of the File Save As dialog and immediatley do a File Open again, and now it is looking for a .ppf file, which I then select and open in order to set all of my settings for my current profile.  I need to do this on each profile as I open them.  Could the problem be that I don't have a .wsp file?  Even without a wsp file, WatSew is not remembering any of my profile settings that were last stored with the profile.  Each profile could theoretically have different settings, right?  All of mine are the same, but each profile's settings can be stored independently and don't need to refer back to a "master" settings file, right?

Thanks for all the help,

Josh

I've nested some responses below (hope the formatting looks right)

The first time I try to File Open a settings file Water and Sewer looks for a .wsp file.
>> the wsp is (should) only be accessed from the Project > Preferences, this could be the problem

Then if I do a File Save As it tries to save a .ppf file.
>> That is the correct file type.

I then cancel out of the File Save As dialog and immediatley do a File Open again, and now it is looking for a .ppf file.
>> Thats the correct workaround, but it sounds bad regardless, somewhere along it got stuck looking at the wrong file type and could be the root cause of the problem I would (if it were easy enough) a) delete the water line and profile b) save and close the files c) delete the resource files (*.rsc from the bin directory) and d)remake the water line & profile. If its still looking for the *.wsp instead of *.ppf, support should probably debug it. As Robert says, it could be a myriad of things.

Could the problem be that I don't have a .wsp file?
>> nope, you can run the program fine without saving or needing the *.wsp

Each profile could theoretically have different settings, right?
>> yep, each one could be set differently

All of mine are the same, but each profile's settings can be stored independently and don't need to refer back to a "master" settings file, right?
>> right, you could use one or many *.ppf and each could display the same or differently

hth.

Dan,

I found the culprit.  There were some lines in my custom configuration that were pointing to wsp files when they should have been pointing to ppf files. 

GPKHYD_DEFAULT_PROFPREFWATER = f:/home/pw/cad/geopak_v8i/preference/mfld_wat.ppf

GPKHYD_DEFAULT_PROFPREFSEWER = f:/home/pw/cad/geopak_v8i/preference/mfld_sew.ppf

Changing these lines fixed my strange profile preference behavior.  However, this did not fix the problem of Drainage incorrectly reading my WatSew project.  I'm still missing my water crossings, and my sewer crossings are plotting way too low in elevation.

Thanks for your help,

Josh

 

Hi Josh - that's great news!   'Funny' how three little letters can make a world of difference, huh?

I think that any dialog that tried to open a WSP instead of the PPF, and any dialog that took information from the affected dialogs, would have its resource files corrupted; in turn causing the errant behavior on those dialogs & any resulting computations from those dialogs.

 Your safest bet would be to Line>Delete and Profile > Delete anything that was affected by the file type mismatch.  Then close MicroStation, delete the resource files again (*.rsc in the bin); then open and remake the previously affected components.  And it 'should' work again. 

Given all that, you may have to kick start some of the output, by issuing Lines&Profiles > Upddate All commands in watsew and Links&Profiles > Update All commands in drainage, just to play it safe...

 

Dan,

With many, many thanks to Michael Gilham, it was discovered that the water/sewer dgn must be referenced into slot 1 of the drainage file for the crossings to be plotted correclty on the drainage profiles.

Such a simple fix but certainly not an expected place to find it!

Josh