Veolcity MID/MIF

[parkesa 0]

Not sure if this is a TuFlow bug or just a user error. I have a large number of TuFlow results for which the Max/Min results option was not enabled, I used the "Dat to Dat" utility to extract maximum V, H, D and ZUK0 results for each (faster than re-running) and then used the "TuFlow to GIS" utility to generate ASC (V,H,D and ZUKO) and MID/MIF (V only) data.

All of the ASC output was fine but the MID/MIF velocity data wouldn't import into MapInfo (10) bouncing back with an "unsupported data type for column(s) v" error.

After a bit of digging I noticed that the data type row in the MIF file was "v(maxmax) Float" rather than "v Float" as appeared in results which hadn't had the "dat to dat" utility run over them. Manually removing the (maxmax) text from the MIF allowed MapInfo to import the MID/MIF file as normal.

Basically I'm trying to work out if the above is a "feature"/bug of the "Dat to Dat" tool or (more likely) if I messed up somewhere.

Cheers

Adam

[Michael Turnley 0]

Hi Adam,

It's a quirk/bug. MapInfo doesn't like the brackets in the automatically assigned fieldname, so renaming the fieldname to V_maxmax in the MIF file would have also worked. I understand the issue is being fixed in the utility, and an updated version will be released. I'm not sure of the timeframe.

Cheers,

Mick

[RhysHJ 0]

Hi Adam,

I'm not sure about this, but I think without storing maximums dat_to_dat will only give you the peak for the timesteps of your map output. So if your catchment response is quite fast compared to your output interval you might miss the peak in some spots. So you might want to make sure that your map data output interval is short enough to have captured the peak values.

Please someone correct me if I'm wrong about this.

Cheers

Rhys

[Bill Syme 0]

Hi Adam

No, you haven't messed up and is a bug in TUFLOW_to_GIS that has been fixed (in Build 2010-02-AA or later).

Cheers

Bill

[dannyduong 0]

I'm trying to do a similar thing by converting the Velocity (V) data from .dat to mid/mif. However, I've stumbled across a problem where an error is given as:

"ERROR - Reading .2dm file - may not be generated by TUFLOW"

This is for a catchment model, and as far as I can tell, they were indeed generated by TUFLOW. This model was most likely run on older versions of TUFLOW, but I don't see why this error would be generated.

I've compared it to other .2dm files, that work, and they appear very similar.

Here is an extract of the first few lines of the .2dm file:

MESH2D 301834.970 1242683.130 25.817712 708 791 5.000 5.000 10.000

NO_MOVE_EQ9_CENTER_NODE

ND 1 303981.482 1243860.473 6.900 2 0. 0. 0.

ND 2 303983.659 1243855.973 6.646 2 0. 0. 0.

ND 3 303979.158 1243853.795 6.586 2 0. 0. 0.

ND 4 303976.981 1243858.296 6.655 2 0. 0. 0.

E4Q 1 1 4 3 2 3 25 489 2

ND 5 303985.983 1243862.651 6.912 2 0. 0. 0.

ND 6 303988.160 1243858.150 6.697 2 0. 0. 0.

E4Q 2 5 1 2 6 3 25 490 2

ND 7 303990.484 1243864.829 6.937 2 0. 0. 0.

ND 8 303992.661 1243860.328 6.757 2 0. 0. 0.

EDIT: I've used the utility on the D, H and Q .dat files and it appears to work fine wit the same .2dm file. I'm not sure if the problem lies in the .2dm, V.dat or utility.

Any ideas regarding this?

Thanks.

Danny

[Bill Syme 0]

Sorry for the slow response Danny, but if you're still having problems can you please zip up and email the .2dm file to support@tuflow.com. I assume you're using TUFLOW_to_GIS?

Cheers

Bill