You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Coming from a question that was e-mailed to me: the TimML API reference currently does not mention what the units or quantities are. Not having units is a feature, just like MODFLOW, as some people want to compute in m/d, ft/d, m/s, etc.
This is worth adding to TimML (and TTim), but also to the QGIS-Tim Docs (that admittedly need a lot of other work too...).
It would be worthwhile to add the quantities like MODFLOW does in the documentation, e.g. L/T for length over time, L^3 for volumes, etc.
The text was updated successfully, but these errors were encountered:
More explanation on quantities is good, e.g. whether a parameters is in L^3/T or L/T, but for QGIS-Tim you can already reduce L^3/T to: m^3/T or feet^3/T
Good point. The time unit is also implicitly defined when writing TTim output: the float-based time is interpreted as (decimal) days since the reference date.
Coming from a question that was e-mailed to me: the TimML API reference currently does not mention what the units or quantities are. Not having units is a feature, just like MODFLOW, as some people want to compute in m/d, ft/d, m/s, etc.
This is worth adding to TimML (and TTim), but also to the QGIS-Tim Docs (that admittedly need a lot of other work too...).
It would be worthwhile to add the quantities like MODFLOW does in the documentation, e.g. L/T for length over time, L^3 for volumes, etc.
The text was updated successfully, but these errors were encountered: