Skip to content

function: om_copy_property #592

@rburghol

Description

@rburghol
  • Use: Usage: om_copy_property src_entity_type src_featureid dest_entity_type dest_featureid propname[propname|newname] [include_children=1] [overwrite=0, 1(yes, unless custom=1), 2(force)] [debug=0]
  • Ex: om_copy_property dh_properties 7633694 dh_properties 4988636 pump_mgd 1 1 0

@COBrogan - I am focusing on property setting infrastructure from command line for doing large batches of updates. The main rationale, is that while we have good property setting tools in R, they are slow compared to command prompt, and I think we will benefit from these -- it'll probably take me a couple hours to work through it tho, so I wanted your opinion on it's merit. Updating 50+ facility models in the Shenandoah with 4-5 properties each won't require this more rapid command prompt script, so I certainly don't need to do it today, but later when we update all 1500 models I think it will be beneficial.

My main focus is simple, an add-on to the current om_copy_property function in bash to honor the custom sub-property setting which indicates that it is not to be over-written -- actually, the R tools don't yet support this, so either way we need to put this into play. Example:

  • The default for Qintake is Qintake = Qreach * intake_drainage_area / reach_area_sqmi,
  • For small side-stream intakes we want Qintake = Runit * intake_drainage_area
  • For others still we have something relative to the upstream flow Qriver_up * 512.3 / 327.05
  • And some are just tweaked custom, such as: Qriver_up * (277 / 210) + Qlinville + 1.0
  • Or even this Rappahannock intake which uses a regression: -31.645 + 0.795360 * Qreach

Complicating all of this is the need to insure that the custom setting has been applied properly, that is, has been applied in all cases where it is needed -- I'm not concerned about things marked custom that shouldn't be, as I just don't think that's happened. Oh, and finally, if you wanted to collaborate on this one, I'm nore than happy to do a Teams meeting, but I think you are on VPDES today?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions