Discussion: Times should be in 24 hour time UTC (ENH-000132015)

[mripp]

• [ ] Implement UK region on each device
• [ ] Remove 24 hour hints in Survey123 XLXS if workaround is confirmed working

During testing feedback it was discussed that the times should be in 24 hour time UTC. The following fields are impacted by this.

• LocationVisit.VisitDate
• LocationVisit.BatteryReplacementDate
• LocationVisit.DataLoggerRecordStart
• LocationVisit.DataLoggerRecordEnd
• LocationVisit.DataLoggerTime
• LocationVisit.DataLoggerTimeActual
• LocationVisit.ADVMBatteryReplacementDate
• LocationVisit.ADVMRecordStart
• LocationVisit.ADVMRecordEnd
• LocationVisit.ADVMDischargeRecordStart
• LocationVisit.ADVMDischargeRecordEnd
• LocationVisit.DischargeRecordStart
• LocationVisit.DischargeRecordEnd
• LocationVisit.WaterQualitySensorPullDate
• LocationVisit.WaterQualityPurgeStart
• LocationVisit.WaterQualitySamplingEnd
• LocationVisit.WaterQualitySensorReinstallDate
• RainfallTips.FalseTipDate
• StageMeasurement.MeasureDate
• StageMeasurement.SensorAdjustmentDate
• GroundwaterMeasurement.MeasureDate
• GroundwaterMeasurement.SensorAdjustmentDate
• ConductivityMeasurement.MeasureDate
• ConductivityMeasurement.SensorAdjustmentDate
• ConductivityMeasurement.VerificationDate
• TemperatureMeasurement.MeasureDate

After researching the options for the Field Form I found the following:

• During publication of the feature service we can set the TimeZone to UTC. When doing this the DateTime field in the Survey will still appear with an AM/PM option and the data will still be stored with AM/PM
• In this example, Survey123 has the user input the time in military time but the field is datatype TEXT.

@rkircher Ask Katie if we want to escalate this enhancement from low to high.

[mripp]

@kprice-TLH I am wondering if you have an example of how you need the date and time formatted in UTC time. Is it like so '12/17/2023 15:20:20'

[kprice-TLH]

mm/dd/yyyy HH:MM:SS is great

From: Morgan Ripp @.> Sent: Monday, March 20, 2023 03:55 PM To: NWFWMD-IT/Hydrologic-Monitoring-Project @.> Cc: Katie Price @.>; Mention @.> Subject: Re: [NWFWMD-IT/Hydrologic-Monitoring-Project] Discussion: Times should be in 24 hour time UTC (Issue #85)

@kprice-TLHhttps://github.com/kprice-TLH I am wondering if you have an example of how you need the date and time formatted in UTC time. Is it like so '12/17/2023 15:20:20'

— Reply to this email directly, view it on GitHubhttps://github.com/NWFWMD-IT/Hydrologic-Monitoring-Project/issues/85#issuecomment-1476845791, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AY7QGQGSPORFT5BMG6B3VULW5CY2RANCNFSM6AAAAAAWBRL3EQ. You are receiving this because you were mentioned.Message ID: @.***>

[mripp]

On 4/3 we discussed how the user should not be able to input AM/PM into the survey. As an alternative we talked about having the user input the Date and Time separately.

@mripp will implement this workflow for the VisitDate field.

• The user will input the Date, date will be inputted as Date and temporarily stored in the survey
• The user will input the Time, time will be inputted as Text in military format and temporarily stored in the survey.
• The survey will concat the Date and Time together and store it as a Text field in the format of mm/dd/yyyy HH:MM:SS

[mripp]

On 4/17 we discussed how we can use other lanaugaes such as French, German etc to use 24 hour clock

• [x] @mripp will look into using these languages that are 24 hours that appear in English

Mripp also demoed how you can have a note/text field translate the 12 hour clock into a 24 hour clock for display purposes

[mripp]

Based on email correspondence with James Tedrick there is an existing enhancement, ENH-000132015, to add a 24 hour English option to the clock.

• [x] @rkircher will add NFWMD as an additional customer to that enhancement

[mripp]

The ENH is currently "under consideration" and we would need to escalate it in order for it to be implemented in a timely fashion.

It was recommended by tech support to utilize the workaround mentioned here. This would mean the user would input the date/time with the calendar interface and the survey would automatically convert it to military time and store it as a string. This would mean the database would need to contain 26 new string fields

[mmannion]

@mripp will contact @rkircher to start escalation.

Escalation will yield survey to describe use case. Current enhancement request does not include use case (we think).

[SarahNWF]

Followup with Michael to make sure the database preserves 24-hour time from UTC Timezone, preserve through databases, dashboards, etc. with Survey123

[mripp]

Update: The enhancement request is in the works on the datetime issue. It's been pushed back to product team for escalation.

[mmannion]

Followup with Michael to make sure the database preserves 24-hour time from UTC Timezone, preserve through databases, dashboards, etc. with Survey123

Confirmed.

The database stores dates and times in an internal format that is independent from how they are displayed in clients. Client applications can display this information in 12/24 hours, different time zones, etc. by choosing their own formatting options when fetching date/time content from the database.

[mripp]

Implemented a note to show 24 hour times for all questions in the survey. This is a temporary work around until this is fixed in the product. If this enhancement is implemented in the Survey123 product all fields below can be removed. In addition, the hint that references these fields can also be removed.

Fields used to calculate 24 hour note:

• VisitDate24 in Location Visit section
• BatteryReplacementDate124 in Battery section
• DataLoggerTime24 in Logger Time section
• DataLoggerTimeActual24 in Logger Time section
• DataLoggerTimeAdjDate24 in Logger Time section
• FalseTipDate24 in Rainfall section
• StageMeasureDate24 in Stage section
• StageSensorAdjustmentDate24 in Stage section
• GroundwaterMeasureDate24 in Groundwater section
• GroundwaterSensorAdjustmentDate24 in Groundwater section
• WaterQualitySensorPullDate24 in Water Quality section
• WaterQualityPurgeStart24 in Water Quality section
• WaterQualitySamplingEnd24 in Water Quality section
• WaterQualitySensorReinstallDate24 in Water Quality section
• ConductivityMeasureDate24 in Specific Conductance section
• ConductivitySensorAdjustmentDate24 in Specific Conductance section
• VerificationDate24 in Specific Conductance section
• ADVMRecordStart24 in ADVM section
• ADVMRecordEnd24 in ADVM section
• TemperatureMeasureDate24 in Temperature section
• DischargeRecordStart24 in Discharge section
• DischargeRecordEnd24 in Discharge section
• ADVMDischarge_RecordStart24 in Discharge section
• ADVMDischarge_RecordEnd24 in Discharge section
• DataLoggerRecordStart24 in Logger File section
• DataLoggerRecordEnd24 in Logger File section
• BatteryReplacementDate224 in Logger File section
• DataLoggerTime224 in Logger File section
• DataLoggerTimeActual224 in Logger File section
• DataLoggerTimeAdjDate224 in Logger File section

[mmannion]

• Per team meeting discussion, cannot enter 24 hour format in Survey input box (tested)
• @rkircher talking again with Survey123 development team
  • May include meeting with @kprice-TLH

[mripp]

During meeting on 4/1 We confirmed that if the Windows 11 Region setting is set to a local that uses 24 hour time then the Survey123 field application automatically utilizes 24 time formatting.

Example of Setting

Survey123 Field Application Appearance

[mmannion]

Attaching summary email from @rkircher about causes > options for time format issue.

email.pdf

[mmannion]

@kprice-TLH @Bikechain will investigate Windows 11 locale settings. More options than Windows 10, and field laptops in the process of being updated.

[mmannion]

On Windows 11:

• Use UK locale
• Fixes 24-hour format in Survey123
• Dates remain as "Monday, 1 April 2024"
  • Don't anticipate problem because month is spelled out

This is sufficient to meet the business need.