Results 1 to 2 of 2

Thread: Required Fields in Feature Classes

  1. #1

    Question Required Fields in Feature Classes

    It has been a few years since I last configured Feature Classes in a Geodatabase for a model in InfoWater.

    I am looking to identify only the required fields.

    From the GIS side, here is what I have:

    4 Feature Classes are necessary to use a model in InfoWater -
    • Junctions
    • Pumps
    • Reservoirs
    • Valves
    • Pipes



    Please tell me what required fields I am missing or is not required:

    JUNCTIONS Feature Class

    • JunctionID, Text, 20
    • Description, Text, 200
    • PressureZone, Text, 20
    • YearInstall, Short
    • YearRetire, Short
    • Elevation, Double


    PUMPS Feature Class

    • PumpID, Text, 20
    • Description, Text, 200
    • PressureZone, Text, 20
    • YearInstall, Short
    • YearRetire, Short
    • Elevation, Double
    • Diameter, Double
    • DesignHead, Double
    • DesignFlow, Double
    • ShutHead, Double
    • HighHead, Double
    • HighFlow, Double
    • Curve, Text, 20
    • NPSHCurve, Text, 20
    • RatedPower, Double
    • CostID, Text, 20



    RESERVOIRS Feature Class

    • ReservoirID, Text, 20
    • Description, Text, 200
    • PressureZone, Text, 20
    • YearInstall, Short
    • YearRetire, Short
    • BottomElev, Double
    • Capacity, Text, 20
    • Head, Double
    • Pattern, Text, 20
    • CostID, Text, 20


    VALVES Feature Class

    • ValveID, Text, 20
    • Description, Text, 200
    • PressureZone, Text, 20
    • Phase, Short
    • YearInstall, Short
    • YearRetire, Short
    • Elevation, Double
    • Diameter, Double
    • Setting, Double
    • Curve, Text, 20
    • MinorLoss, Double
    • CostID, Text, 20


    PIPES Feature Class

    • PipeID, Text, 20
    • Description, Text, 200
    • PressureZone, Text, 20
    • YearInstall, Short
    • YearRetire, Short
    • Diameter, Double
    • Roughness, Double
    • CheckValve, Short
    • FromJunction, Text, 20
    • ToJunction, Text, 20
    • Material, Text, 40
    • MinorLoss, Double
    • Totalizer, Short
    • CostID, Text, 20
    Tim Hayes
    GIS Manager
    City of San Jose Municipal Water System
    San Jose-Santa Clara Regional Wastewater Facility

  2. #2
    Forum Moderator

    Innovyze Employee



    Innovyze Employee



    Join Date
    May 2015
    Posts
    434
    Tim,

    Please see the comments added to your text Innovyze comments are in bold italicized Red Text


    I am looking to identify only the required fields.

    From the GIS side, here is what I have:

    4 Feature Classes are necessary to use a model in InfoWater (Innovyze Note: There are 6 model elements types (Junctions, Tanks, Reservoirs, Pumps, Valves, Pipes)
    • Junctions
    • Pumps
    • Reservoirs
    • Valves
    • Pipes



    Please tell me what required fields I am missing or is not required: (Innovyze comments in bold Red -These are the built in FIXED fields even though not all are technically required to be populated)

    JUNCTIONS Feature Class

    • JunctionID, Text, 20 (ID -> length 32)
    • Description, Text, 200 (length 60)
    • PressureZone, Text, 20 (ZONE -> Length 32)
    • YearInstall, Short (Integer Length 4)
    • YearRetire, Short (Integer Length 4)
    • Elevation, Double (Length 20, Decimal 9)
    • Phase (integer length 4)


    PUMPS Feature Class

    • PumpID, Text, 20 (ID -> length 32)
    • Description, Text, 200 (length 60)
    • TYPE: Integer Length 4
    • PressureZone, Text, 20 (ZONE -> Length 32)
    • YearInstall, Short (Integer Length 4)
    • YearRetire, Short (Integer Length 4)
    • Elevation, Double (Length 20, Decimal 9)
    • Diameter, Double (Length 20, Decimal 9)
    • HP , Double (Length 20, Decimal 9)
    • DesignHead, Double ( DSGN_HEAD, Length 20, Decimal 9)
    • DesignFlow, Double (DSGN_FLOW, Length 20, Decimal 9)
    • ShutHead, Double (Length 20, Decimal 9)
    • HighHead, Double (HIGH_HEAD, Length 20, Decimal 9)
    • HighFlow, Double (HIGH_FLOW, Length 20, Decimal 9)
    • Curve, Text, 20 ( text, length 32)
    • NPSHCurve, Text, 20 ( text, length 32)
    • RatedPower, Double (Length 20, Decimal 9)
    • CostID, Text, 20 ( text, length 32)
    • Phase (integer length 4)


    Tanks Feature Class

    • TankID, Text, 20 (ID -> length 32)
    • Description, Text, 200 (length 60)
    • PressureZone, Text, 20 (ZONE -> Length 32)
    • YearInstall, Short (Integer Length 4)
    • YearRetire, Short (Integer Length 4)
    • TYPE: Integer Length 4
    • Elevation, Double (Length 20, Decimal 9)
    • Minimum Level, Double (Length 20, Decimal 9)
    • Maximum Level, Double (Length 20, Decimal 9)
    • Initial Level, Double (Length 20, Decimal 9)
    • Minimum Volume, Double (Length 20, Decimal 9)
    • Curve text length 32
    • Allow Overflow (Boolean) ​(Boolean) In the raw data base Boolean fields appear as "True" or "false" but are listed as a length of 1 With an apparent value of 1 for Yes and a zero for No , but in the viewable model database editor these are "YES" and "NO",
    • CostID, Text, 20 ( text, length 32)
    • Phase (integer length 4)



    RESERVOIRS Feature Class

    • ReservoirID, Text, 20 (ID -> length 32)
    • Description, Text, 200 (length 60)
    • TYPE: Integer Length 4
    • PressureZone, Text, 20 (ZONE -> Length 32)
    • YearInstall, Short (Integer Length 4)
    • YearRetire, Short (Integer Length 4)
    • BottomElev, Double
    • Head, Double (Length 20, Decimal 9)
    • Pattern, Text, 20 text length 32
    • CostID, Text, 20 ( text, length 32)
    • Phase (integer length 4)


    VALVES Feature Class

    • ValveID, Text, 20 (ID -> length 32)
    • Description, Text, 200 (length 60)
    • PressureZone, Text, 20 (ZONE -> Length 32)
    • Phase (integer length 4)
    • YearInstall, Short (Integer Length 4)
    • YearRetire, Short (Integer Length 4)
    • Elevation, Double (Length 20, Decimal 9)
    • Diameter, Double (Length 20, Decimal 9)
    • Setting, Double (Length 20, Decimal 9)
    • Curve, Text, 20 ( text, length 32)
    • PID (Control ID used for Float Valves - text, length 32)
    • UCL Double (Upper control Limit used for Float Valves - Length 20, Decimal 9)
    • LCL Double (Lower control Limit used for Float Valves -Length 20, Decimal 9)
    • MinorLoss, Double (Length 20, Decimal 9)
    • CostID, Text, 20 ( text, length 32)


    PIPES Feature Class

    • PipeID, Text, 20 (ID -> length 32)
    • Description, Text, 200 (length 60)
    • PressureZone, Text, 20 (ZONE -> Length 32)
    • YearInstall, Short (Integer Length 4)
    • YearRetire, Short (Integer Length 4)
    • Diameter, Double (Length 20, Decimal 9)
    • Roughness, Double (Length 20, Decimal 9)
    • MinorLoss, Double (Length 20, Decimal 9)
    • CheckValve, Short (Boolean) In the raw data base Boolean fields appear as "True" or "false" but are listed as a length of 1 With an apparent value of 1 for Yes and a zero for No , but in the viewable model database editor these are "YES" and "NO",
    • Totalizer, (Boolean) In the raw data base Boolean fields appear as "True" or "false" but are listed as a length of 1 With an apparent value of 1 for Yes and a zero for No , but in the viewable model database editor these are "YES" and "NO",
    • FromJunction, Text, 20 (Same as element ID field Length 32, text)
    • ToJunction, Text, 20 (Same as element ID field Length 32, text)
    • Material, Text, 40 ( text Length 40)
    • Phase (integer length 4)
    • CostID, Text, 20 ( text, length 32)



    Patrick Moore

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •