WA_HYDRANT - verify new fields added

[rssidlowski]

Marian added the requested fields to the City's WA_HYDRANT table. Please verify the names, field definitions and update migration as needed. Fields that should have been added: LOCATION_TYPE Text(50) STREET_NUM Text(50) STREET_NAME Text(255) CAD_ADDR long text
CROSS_STREET text(255) CORNER_POSITION text(50) LOCATION_DESCRIPTION text(50)
DISTRICT text(6) HYDR_ZONE long integer

Please provide connection information for the latest Hydrant database so I can update the data model, including lookup fields.

[rssidlowski]

Here's what was added: ST_NAME C_ST_NAME LOCATION_DESCRIPTION ADDRESS

Please update any migration scripts and/or application code as needed.

[rssidlowski]

redo migration to wa_hydrant, sources include maint2water_hyd, journal, Baltimore county out of service.

[gerrykelly]

[I'd commented on the wrong issue before, should have been here]

So, to clarify where things stand and what I should do for followup: The following fields were added to PRODUCTION WA_HYDRANT (all null values): LOCATION_TYPE Text(50) STREET_NUM Text(50) STREET_NAME Text(255) CAD_ADDR long text !!!!(was added as Text(255)) CROSS_STREET text(255) CORNER_POSITION text(50) LOCATION_DESCRIPTION text(50) !!!! but why limit to 50char? DISTRICT text(6) HYDR_ZONE long integer The production WA_HYDRANT was not migrated to the DEV OPERATIONS (I should probably replace the whole dataset at some point), so these fields do not exist in DEV WA_HYDRANT The fields, ST_NAME, C_ST_NAME, LOCATION_DESCRIPTION, ADDRESS exist ONLY in the featureclass WA_HYDRANTdev that I created to be used during development. This is the featureclass that is used for the mapservice here and in City DEV. So, what to do? Assuming the fields that were added to PRODUCTION WA_HYDRANT are as desired (although I’d request lengthening the 2 fields I commented on) I think I should: 1) Copy the PRODUCTION WA_HYDRANTS to dev 2) Populate those fields as best I can 3) Deliver a script (to Marian?) that populates the fields in the WATER DB, so these values then are part of OPERATIONS and will then be maintained by normal workflow in WATER a. That would need to be an approved request that it would become the responsibility of whoever edits WA_HYDRANTS 4) Recreate the mapservice a. Joe would need to do this at the City 5) Revise the UI to use these new fields’ equivalent of what I’d had in WA_HYDRANTdev a. And now do we want to add other new fields to the UI? Please direct.

[rssidlowski]

I will attempt to get clarification today at the meeting.

[rssidlowski]

What would you recommend for the length for the fields: CAD_ADDR LOCATION_DESCRIPTION

[gerrykelly]

Actually CAD_ADDR is fine as is, but make LOCATION_DESCRIPTION 255 also