RE: Status of the CO-OP Min/Max Temp Issue?

Forums

RSS (Opens New Window)

Joseph Moore, modified 4 Years ago.

Status of the CO-OP Min/Max Temp Issue?

Youngling Posts: 31 Join Date: 11/1/13 Recent Posts

There has been a longstanding issue with IRIS in the decoding of cooperative observation (COOP) min/max temps with many tickets opened over the years.

Problem: When it comes to temperature data from cooperative observations, only the current temp is recorded in the IRIS database; the min/max reports from the RR3 are not saved into the IRIS database.

Desired Solution: Cooperative Observer min/max temps are recorded in the IRIS database so that they appear when running a min or max temp query.

For example:

#5057 - Opened 2014; Closed (Resolved - reported fixed in 5.0.1)

#6501 - Opened 2015; Closed (Resolved - reported fixed in 5.0.2)

#6546 - Opened 2015; Closed (Resolved - reported fixed in 5.0.2)

#19123 - Open 2016; Closed (Resolved - reported fixed in 6.1.1)

#22158 - Opened 2016; In-Progress, last updated 9 months ago (Target: 7.0.0)

#22159 - Opened 2016; Closed (comment that it appeared to be working 4 years ago, so ticket was closed)

#35579 - Opened 2017; New/Open (Target: 7.0.0)

#50539 - Opened 2018; Marked Complete over 1 year ago

#86166 - Opened 10 days ago; New/Open

While these tickets vary, generally the root cause is that the min/max temps aren't being saved. From reading discussions over the years I believe processing this data is complicated because co-op obs can arrive at any time of day (i.e. there are some observers who report min/max temp ending at 00z, or some other local time - they do not all report at 12z, and this varies across timezones and DST). However, previous tickets certainly seem like this issue has previously been solved. Is there a solution in the works for 7.0.0. for this problem? We would really like to see our cooperative observers in a min temp listing because they're often the coldest spots in the area.

Matt Davis, modified 4 Years ago.

RE: Status of the CO-OP Min/Max Temp Issue?

Youngling Posts: 193 Join Date: 6/14/11 Recent Posts

Hi Joe,

Sometimes dealing with obs seems like a Clark Griswold Lighting fiasco, LOL. I have verified this and know why it's happening. It will be fixed in 6.7.0 in late January. Sorry for the hassle. I'll post side by side comparisons when done.

Thanks for letting us know,

Matt

On Tue, Dec 29, 2020 at 9:18 AM Joseph Moore <VLab.Notifications@noaa.gov> wrote:

There has been a longstanding issue with IRIS in the decoding of cooperative observation (COOP) min/max temps with many tickets opened over the years.

Problem: When it comes to temperature data from cooperative observations, only the current temp is recorded in the IRIS database; the min/max reports from the RR3 are not saved into the IRIS database.

Desired Solution: Cooperative Observer min/max temps are recorded in the IRIS database so that they appear when running a min or max temp query.

For example:

#5057 - Opened 2014; Closed (Resolved - reported fixed in 5.0.1)

#6501 - Opened 2015; Closed (Resolved - reported fixed in 5.0.2)

#6546 - Opened 2015; Closed (Resolved - reported fixed in 5.0.2)

#19123 - Open 2016; Closed (Resolved - reported fixed in 6.1.1)

#22158 - Opened 2016; In-Progress, last updated 9 months ago (Target: 7.0.0)

#22159 - Opened 2016; Closed (comment that it appeared to be working 4 years ago, so ticket was closed)

#35579 - Opened 2017; New/Open (Target: 7.0.0)

#50539 - Opened 2018; Marked Complete over 1 year ago

#86166 - Opened 10 days ago; New/Open

While these tickets vary, generally the root cause is that the min/max temps aren't being saved. From reading discussions over the years I believe processing this data is complicated because co-op obs can arrive at any time of day (i.e. there are some observers who report min/max temp ending at 00z, or some other local time - they do not all report at 12z, and this varies across timezones and DST). However, previous tickets certainly seem like this issue has previously been solved. Is there a solution in the works for 7.0.0. for this problem? We would really like to see our cooperative observers in a min temp listing because they're often the coldest spots in the area.

--
Joseph Moore IRIS Virtual Lab Forum https://vlab.noaa.gov/web/iris/iris-forum/-/message_boards/view_message/13138537 VLab.Notifications@noaa.gov

Project Manager for IRIS, iNWS, CAP Handler

and NWSChat Long Term Update

Meteorological Development Lab

Office of Science and Technology Integration

NOAA DSRC 3D131, Boulder, Colorado

(608) 406-0537

Joseph Moore, modified 4 Years ago.

RE: Status of the CO-OP Min/Max Temp Issue?

Youngling Posts: 31 Join Date: 11/1/13 Recent Posts

Ha! That's great to hear, thanks for the update - I can imagine this has been a difficult problem to solve, and with so many moving parts it can be complex to diagnose these little issues.

Thanks,

Joe

On Tue, Dec 29, 2020 at 6:24 PM Matt Davis <VLab.Notifications@noaa.gov> wrote:

Hi Joe,

Sometimes dealing with obs seems like a Clark Griswold Lighting fiasco, LOL. I have verified this and know why it's happening. It will be fixed in 6.7.0 in late January. Sorry for the hassle. I'll post side by side comparisons when done.

Thanks for letting us know,
Matt

On Tue, Dec 29, 2020 at 9:18 AM Joseph Moore <VLab.Notifications@noaa.gov> wrote:
There has been a longstanding issue with IRIS in the decoding of cooperative observation (COOP) min/max temps with many tickets opened over the years.

Problem: When it comes to temperature data from cooperative observations, only the current temp is recorded in the IRIS database; the min/max reports from the RR3 are not saved into the IRIS database.

Desired Solution: Cooperative Observer min/max temps are recorded in the IRIS database so that they appear when running a min or max temp query.

For example:

#5057 - Opened 2014; Closed (Resolved - reported fixed in 5.0.1)

#6501 - Opened 2015; Closed (Resolved - reported fixed in 5.0.2)

#6546 - Opened 2015; Closed (Resolved - reported fixed in 5.0.2)

#19123 - Open 2016; Closed (Resolved - reported fixed in 6.1.1)

#22158 - Opened 2016; In-Progress, last updated 9 months ago (Target: 7.0.0)

#22159 - Opened 2016; Closed (comment that it appeared to be working 4 years ago, so ticket was closed)

#35579 - Opened 2017; New/Open (Target: 7.0.0)

#50539 - Opened 2018; Marked Complete over 1 year ago

#86166 - Opened 10 days ago; New/Open

While these tickets vary, generally the root cause is that the min/max temps aren't being saved. From reading discussions over the years I believe processing this data is complicated because co-op obs can arrive at any time of day (i.e. there are some observers who report min/max temp ending at 00z, or some other local time - they do not all report at 12z, and this varies across timezones and DST). However, previous tickets certainly seem like this issue has previously been solved. Is there a solution in the works for 7.0.0. for this problem? We would really like to see our cooperative observers in a min temp listing because they're often the coldest spots in the area.

--
Joseph Moore IRIS Virtual Lab Forum https://vlab.noaa.gov/web/iris/iris-forum/-/message_boards/view_message/13138537 VLab.Notifications@noaa.gov

--
Project Manager for IRIS, iNWS, CAP Handler
and NWSChat Long Term Update
Meteorological Development Lab
Office of Science and Technology Integration
NOAA DSRC 3D131, Boulder, Colorado
(608) 406-0537

--
Matt Davis IRIS Virtual Lab Forum http://vlab.noaa.gov/web/iris/iris-forum/-/message_boards/view_message/13142613 VLab.Notifications@noaa.gov

Joseph J. Moore

Warning Coordination Meteorologist

NOAA/National Weather Service Duluth, MN

Office: 218-729-6483 x726 | Cell: 267-481-0341 | Operations: 218-729-0653

weather.gov/duluth

Matt Davis, modified 4 Years ago.

RE: Status of the CO-OP Min/Max Temp Issue?

Youngling Posts: 193 Join Date: 6/14/11 Recent Posts

Hi Joe,

Here are the artifacts of the fix, from our development system (this morning's data)

Thanks,

Matt

On Wed, Dec 30, 2020 at 7:01 AM Joseph Moore <VLab.Notifications@noaa.gov> wrote:

Ha! That's great to hear, thanks for the update - I can imagine this has been a difficult problem to solve, and with so many moving parts it can be complex to diagnose these little issues.

Thanks,

Joe

On Tue, Dec 29, 2020 at 6:24 PM Matt Davis <VLab.Notifications@noaa.gov> wrote:

Hi Joe,

Sometimes dealing with obs seems like a Clark Griswold Lighting fiasco, LOL. I have verified this and know why it's happening. It will be fixed in 6.7.0 in late January. Sorry for the hassle. I'll post side by side comparisons when done.

Thanks for letting us know,

Matt

On Tue, Dec 29, 2020 at 9:18 AM Joseph Moore <VLab.Notifications@noaa.gov> wrote:

There has been a longstanding issue with IRIS in the decoding of cooperative observation (COOP) min/max temps with many tickets opened over the years.

Problem: When it comes to temperature data from cooperative observations, only the current temp is recorded in the IRIS database; the min/max reports from the RR3 are not saved into the IRIS database.

Desired Solution: Cooperative Observer min/max temps are recorded in the IRIS database so that they appear when running a min or max temp query.

For example:

#5057 - Opened 2014; Closed (Resolved - reported fixed in 5.0.1)

#6501 - Opened 2015; Closed (Resolved - reported fixed in 5.0.2)

#6546 - Opened 2015; Closed (Resolved - reported fixed in 5.0.2)

#19123 - Open 2016; Closed (Resolved - reported fixed in 6.1.1)

#22158 - Opened 2016; In-Progress, last updated 9 months ago (Target: 7.0.0)

#22159 - Opened 2016; Closed (comment that it appeared to be working 4 years ago, so ticket was closed)

#35579 - Opened 2017; New/Open (Target: 7.0.0)

#50539 - Opened 2018; Marked Complete over 1 year ago

#86166 - Opened 10 days ago; New/Open

While these tickets vary, generally the root cause is that the min/max temps aren't being saved. From reading discussions over the years I believe processing this data is complicated because co-op obs can arrive at any time of day (i.e. there are some observers who report min/max temp ending at 00z, or some other local time - they do not all report at 12z, and this varies across timezones and DST). However, previous tickets certainly seem like this issue has previously been solved. Is there a solution in the works for 7.0.0. for this problem? We would really like to see our cooperative observers in a min temp listing because they're often the coldest spots in the area.

--
Joseph Moore IRIS Virtual Lab Forum https://vlab.noaa.gov/web/iris/iris-forum/-/message_boards/view_message/13138537 VLab.Notifications@noaa.gov

--

Project Manager for IRIS, iNWS, CAP Handler

and NWSChat Long Term Update

Meteorological Development Lab

Office of Science and Technology Integration

NOAA DSRC 3D131, Boulder, Colorado

(608) 406-0537

--
Matt Davis IRIS Virtual Lab Forum http://vlab.noaa.gov/web/iris/iris-forum/-/message_boards/view_message/13142613 VLab.Notifications@noaa.gov

--

Joseph J. Moore
Warning Coordination Meteorologist

NOAA/National Weather Service Duluth, MN

Office: 218-729-6483 x726 | Cell: 267-481-0341 | Operations: 218-729-0653

weather.gov/duluth

--
Joseph Moore IRIS Virtual Lab Forum http://vlab.noaa.gov/web/iris/iris-forum/-/message_boards/view_message/13148812 VLab.Notifications@noaa.gov

Project Manager for IRIS, iNWS, CAP Handler

and NWSChat Long Term Update

Meteorological Development Lab

Office of Science and Technology Integration

NOAA DSRC 3D131, Boulder, Colorado

(608) 406-0537

Joseph Moore, modified 4 Years ago.

RE: Status of the CO-OP Min/Max Temp Issue?

Youngling Posts: 31 Join Date: 11/1/13 Recent Posts

Excellent, Thanks Matt!

And yeah... the observation time will inherently need quality control (since the "low" might be yesterday's low at obs time) but I think it'll be worth having the obs in there since those are often our coldest sites.

Thanks,

Joe

On Wed, Dec 30, 2020 at 8:46 AM Matt Davis <VLab.Notifications@noaa.gov> wrote:

Hi Joe,

Here are the artifacts of the fix, from our development system (this morning's data)

Thanks,

Matt

On Wed, Dec 30, 2020 at 7:01 AM Joseph Moore <VLab.Notifications@noaa.gov> wrote:

Ha! That's great to hear, thanks for the update - I can imagine this has been a difficult problem to solve, and with so many moving parts it can be complex to diagnose these little issues.

Thanks,

Joe

On Tue, Dec 29, 2020 at 6:24 PM Matt Davis <VLab.Notifications@noaa.gov> wrote:

Hi Joe,

Sometimes dealing with obs seems like a Clark Griswold Lighting fiasco, LOL. I have verified this and know why it's happening. It will be fixed in 6.7.0 in late January. Sorry for the hassle. I'll post side by side comparisons when done.

Thanks for letting us know,

Matt

On Tue, Dec 29, 2020 at 9:18 AM Joseph Moore <VLab.Notifications@noaa.gov> wrote:

There has been a longstanding issue with IRIS in the decoding of cooperative observation (COOP) min/max temps with many tickets opened over the years.

Problem: When it comes to temperature data from cooperative observations, only the current temp is recorded in the IRIS database; the min/max reports from the RR3 are not saved into the IRIS database.

Desired Solution: Cooperative Observer min/max temps are recorded in the IRIS database so that they appear when running a min or max temp query.

For example:

#5057 - Opened 2014; Closed (Resolved - reported fixed in 5.0.1)

#6501 - Opened 2015; Closed (Resolved - reported fixed in 5.0.2)

#6546 - Opened 2015; Closed (Resolved - reported fixed in 5.0.2)

#19123 - Open 2016; Closed (Resolved - reported fixed in 6.1.1)

#22158 - Opened 2016; In-Progress, last updated 9 months ago (Target: 7.0.0)

#22159 - Opened 2016; Closed (comment that it appeared to be working 4 years ago, so ticket was closed)

#35579 - Opened 2017; New/Open (Target: 7.0.0)

#50539 - Opened 2018; Marked Complete over 1 year ago

#86166 - Opened 10 days ago; New/Open

While these tickets vary, generally the root cause is that the min/max temps aren't being saved. From reading discussions over the years I believe processing this data is complicated because co-op obs can arrive at any time of day (i.e. there are some observers who report min/max temp ending at 00z, or some other local time - they do not all report at 12z, and this varies across timezones and DST). However, previous tickets certainly seem like this issue has previously been solved. Is there a solution in the works for 7.0.0. for this problem? We would really like to see our cooperative observers in a min temp listing because they're often the coldest spots in the area.

--
Joseph Moore IRIS Virtual Lab Forum https://vlab.noaa.gov/web/iris/iris-forum/-/message_boards/view_message/13138537 VLab.Notifications@noaa.gov

--

Project Manager for IRIS, iNWS, CAP Handler

and NWSChat Long Term Update

Meteorological Development Lab

Office of Science and Technology Integration

NOAA DSRC 3D131, Boulder, Colorado

(608) 406-0537

--
Matt Davis IRIS Virtual Lab Forum http://vlab.noaa.gov/web/iris/iris-forum/-/message_boards/view_message/13142613 VLab.Notifications@noaa.gov

--

Joseph J. Moore
Warning Coordination Meteorologist

NOAA/National Weather Service Duluth, MN

Office: 218-729-6483 x726 | Cell: 267-481-0341 | Operations: 218-729-0653

weather.gov/duluth

--
Joseph Moore IRIS Virtual Lab Forum http://vlab.noaa.gov/web/iris/iris-forum/-/message_boards/view_message/13148812 VLab.Notifications@noaa.gov

--

Project Manager for IRIS, iNWS, CAP Handler

and NWSChat Long Term Update

Meteorological Development Lab

Office of Science and Technology Integration

NOAA DSRC 3D131, Boulder, Colorado

(608) 406-0537

--
Matt Davis IRIS Virtual Lab Forum http://vlab.noaa.gov/web/iris/iris-forum/-/message_boards/view_message/13149468 VLab.Notifications@noaa.gov

Joseph J. Moore

Warning Coordination Meteorologist

NOAA/National Weather Service Duluth, MN

Office: 218-729-6483 x726 | Cell: 267-481-0341 | Operations: 218-729-0653

weather.gov/duluth

RE: Status of the CO-OP Min/Max Temp Issue? - IRIS Forum - IRIS

Forums