• Re: How to use scenario manager

    I'm using the scenario manager if I change the network geometry, say add pipes or tanks. If the only purpose is to change the demands, I prefer using custom fields in mw_MDemand. This has the benefit that I can quickly compare the content of the "scenarios", because they are side by side. And activating a "scenario" is just a field calculation (or a saved SQL expression).

    See [url=http://wiki.mikebydhi.com/mikeurban:szenarios-managen-lastfaelle-verwalten]http://wiki.mikebydhi.com/mikeurban:szenarios-managen-lastfaelle-verwalten[/url]

    The page is in German. Please use [url=http://translate.google.com]http://translate.google.com[/url] or whatever tool you like.
  • Re: Edit Mike Urban

    Concerning the original question how to merge two consecutive pipes: This is possible, but only for Water Distribution, and the tool is well hidden.

    [b](1)[/b] Select two pipes

    [b](2)[/b] Go to Edit > Feature Edit > Merge Selected Pipes

    That's it.

    The node in between the two pipes will disappear, and with the node any demand associated to it.

    Concerning the pipe attributes, I think MIKE URBAN preserves the values of the record higher up in the natural order of the database table. But you have to check and be cautious.
  • Tip: How to summarise impervious area and inhabitants per subcatchment

    As part of a general drainage master plan, very often we need the following key figures per combined server overflow (CSO):
    [li] total area and total impervious area of all catchments connected to each CSO, and[/li]
    [li] total number of inhabitants within the same subcatchments.[/li]

    [img width=200 height=178]http://wiki.mikebydhi.com/_media/mikeurban:anleitungen:gebietseinteilung:lageplan-kategorisiert.png?cache=[/img]

    The article [url=http://wiki.mikebydhi.com/mikeurban:anleitungen:ermitteln_von_kennwerten_in_teileinzugsgebieten]Ermitteln von Kennwerten in Teileinzugsgebieten[/url] describes step by step how to derive those key figures. The text is in German, but with Google translate or similar you should be able to get the message. On the way you'll get familiar with the following techniques:
    [li]adding user defined fields to the database[/li]
    [li]using SQL commands in order to copy values between tables[/li]
    [li]backward flow tracing[/li]
    [li]creating tables with summarised values[/li]
    I hope the tip is helpful!
  • Re: Error 79

    Sounds like a license issue. Do you have the necessary module licensed in you current version of MIKE URBAN? Check in the DHI License Administration.
  • Re: File Error 305: cannot open hydraulics file

    Sometimes this error is due to special characters in the path to the database (to the inp-file to be more precise, because the error message comes from the engine). If your path looks like

    C:\Users\anton.bruckner\Desktop\Anton\Calcul-Hydraulique\MIKE URBAN\BA_AW.mdb



    instead. Perhaps this solves your problem.
  • Re: HystemExtran Import

    I was involved in developing the import from Hystem-Extran 6 to MIKE URBAN, and I would be interested in learning more about HE version 7 and it's Firebird database. I suppose it should be possible to adapt the existing import, unless itwh has competely changed the data structure.

    If you like, send me an e-mail directly, using the small e-mail icon below my name on the left.