Forums

Back

Upcoming widespread flagging of CWOP & AWS wind speed observations

RSS (Opens New Window)(Opens New Window)
MM
Matthew Morris, modified 4 Years ago.

Upcoming widespread flagging of CWOP & AWS wind speed observations

Youngling Posts: 169 Join Date: 12/6/17 Recent Posts
Hi All,

Due to the persistent low wind speed bias that has continued to impact RTMA/URMA and the NBM, we are proposing a mass flagging of all CWOP and AWS wind speed observations throughout the CONUS and Alaska domains.  Recall that the SDM QC flags do not apply to wind gust observations.  The relevant updates to the SDM reject list are expected to take place on Friday, April 16th depending on CWD.

For the CONUS domain, CWOP and AWS wind speed/gust observations are rejected by default, unless the station is on the mesonet station uselist.  Thus, any new CWOP or AWS wind speed/gust observations will not be assimilated in the current 2D-RTMA/URMA suite.

For Alaska, however, mesonet wind speed observations are not rejected by default due to reduced observation counts over the domain.  CWOP and AWS stations reporting recently have been identified and will be flagged for wind speed only.  Thus, any CWOP or AWS stations that begin or resume reporting following this request will be considered for assimilation.  Should the Alaska region offices wish to flag any of these new stations, we ask that the offices submit the requests through the existing RTMA/URMA QC form.

The attached KML file shows the location of the stations that will be flagged for wind (in red), as well as those that are already flagged for wind on the SDM list (in yellow).  Many of the stations on the CONUS use list are not currently reporting and, thus, not displayed in the KML file; these stations will, however, still be included in the bulk flagging request.

 CWOP/AWS Stations to Flag - Wind Speed Only

We ask that forecast offices note in the attached spreadsheet (column C) any stations (with red or orange shading) that should be excluded from this request and continue to be used in RTMA/URMA.  We ask for this feedback by Tuesday, April 13th.

Note that many stations in the Northwest, particularly in Washington and Oregon, fall within both the CONUS and Alaska domains.  The spreadsheet includes a column noting the primary flagging domain.  If a station falling within CONUS is listed with the domain “Alaska”, this means that the station is not currently being used for CONUS (i.e., not on the station use list), but is being used for Alaska.  In other words, flagging these stations will not impact the CONUS domain.

Please let us know if you have any questions.

Thanks,
-Matt

Attachments:

MM
Matthew Morris, modified 4 Years ago.

RE: Upcoming widespread flagging of CWOP & AWS wind speed observations

Youngling Posts: 169 Join Date: 12/6/17 Recent Posts
Hi All,

There has been some confusion regarding the increased density of CWOP and AWS stations in Washington and Oregon.  Many of these stations are only being assimilated in Alaska-RTMA as they are not on the station use list for CONUS.  The Alaska domain encompasses western Washington and Oregon, as shown below.  To simplify this process, I have attached two new KML files that separate the stations by domain (CONUS and Alaska).

domains.png

Please let us know if you have any further questions.

Thanks,
-Matt

On Wed, Mar 31, 2021 at 8:56 AM VLab Notifications <VLab.Notifications@noaa.gov> wrote:
Hi All,

Due to the persistent low wind speed bias that has continued to impact RTMA/URMA and the NBM, we are proposing a mass flagging of all CWOP and AWS wind speed observations throughout the CONUS and Alaska domains.  Recall that the SDM QC flags do not apply to wind gust observations.  The relevant updates to the SDM reject list are expected to take place on Friday, April 16th depending on CWD.

For the CONUS domain, CWOP and AWS wind speed/gust observations are rejected by default, unless the station is on the mesonet station uselist.  Thus, any new CWOP or AWS wind speed/gust observations will not be assimilated in the current 2D-RTMA/URMA suite.

For Alaska, however, mesonet wind speed observations are not rejected by default due to reduced observation counts over the domain.  CWOP and AWS stations reporting recently have been identified and will be flagged for wind speed only.  Thus, any CWOP or AWS stations that begin or resume reporting following this request will be considered for assimilation.  Should the Alaska region offices wish to flag any of these new stations, we ask that the offices submit the requests through the existing RTMA/URMA QC form.

The attached KML file shows the location of the stations that will be flagged for wind (in red), as well as those that are already flagged for wind on the SDM list (in yellow).  Many of the stations on the CONUS use list are not currently reporting and, thus, not displayed in the KML file; these stations will, however, still be included in the bulk flagging request.

 CWOP/AWS Stations to Flag - Wind Speed Only

We ask that forecast offices note in the attached spreadsheet (column C) any stations (with red or orange shading) that should be excluded from this request and continue to be used in RTMA/URMA.  We ask for this feedback by Tuesday, April 13th.

Note that many stations in the Northwest, particularly in Washington and Oregon, fall within both the CONUS and Alaska domains.  The spreadsheet includes a column noting the primary flagging domain.  If a station falling within CONUS is listed with the domain “Alaska”, this means that the station is not currently being used for CONUS (i.e., not on the station use list), but is being used for Alaska.  In other words, flagging these stations will not impact the CONUS domain.

Please let us know if you have any questions.

Thanks,
-Matt

--
Matthew Morris RTMA/URMA Discussion Group Virtual Lab Forum http://vlab.noaa.gov/web/715073/home/-/message_boards/view_message/14297953VLab.Notifications@noaa.gov

Attachments:

Attachment

MM
Matthew Morris, modified 4 Years ago.

RE: Upcoming widespread flagging of CWOP & AWS wind speed observations

Youngling Posts: 169 Join Date: 12/6/17 Recent Posts
Hi All,

It was recently discovered that a significant number of CWOP and AWS stations throughout CONUS were inadvertently excluded from the initial spreadsheet and KML file.  These missed stations are partially whitelisted based on the wind direction, in order to account for obstructions (e.g., buildings).

These newly-identified stations are plotted in the attached KML file: stations with red placemarks will be added to the SDM reject list, while stations with yellow placemarks are already flagged as a result of earlier QC requests.  The spreadsheet lists the provider for all stations, as well as the latitude/longitude for the stations that have recently reported.  The stations in the earlier spreadsheet and KML file are not duplicated in the new spreadsheet and KML file.

 Part II: CWOP/AWS Stations to Flag - Wind Speed...

The impact is limited to the CONUS domain only.  Given this new information, the widespread flagging of CWOP and AWS wind speed observations will need to be delayed.  We ask that forecast offices note any additional stations that should be excluded from flagging in the attached spreadsheet by Tuesday, April 27th.  The updates to the SDM reject list will take place on or around Friday, April 30th, depending on CWD.

Please let us know if you have any questions.

Thanks,
Matt

On Wed, Mar 31, 2021 at 8:56 AM VLab Notifications <VLab.Notifications@noaa.gov> wrote:
Hi All,

Due to the persistent low wind speed bias that has continued to impact RTMA/URMA and the NBM, we are proposing a mass flagging of all CWOP and AWS wind speed observations throughout the CONUS and Alaska domains.  Recall that the SDM QC flags do not apply to wind gust observations.  The relevant updates to the SDM reject list are expected to take place on Friday, April 16th depending on CWD.

For the CONUS domain, CWOP and AWS wind speed/gust observations are rejected by default, unless the station is on the mesonet station uselist.  Thus, any new CWOP or AWS wind speed/gust observations will not be assimilated in the current 2D-RTMA/URMA suite.

For Alaska, however, mesonet wind speed observations are not rejected by default due to reduced observation counts over the domain.  CWOP and AWS stations reporting recently have been identified and will be flagged for wind speed only.  Thus, any CWOP or AWS stations that begin or resume reporting following this request will be considered for assimilation.  Should the Alaska region offices wish to flag any of these new stations, we ask that the offices submit the requests through the existing RTMA/URMA QC form.

The attached KML file shows the location of the stations that will be flagged for wind (in red), as well as those that are already flagged for wind on the SDM list (in yellow).  Many of the stations on the CONUS use list are not currently reporting and, thus, not displayed in the KML file; these stations will, however, still be included in the bulk flagging request.

 CWOP/AWS Stations to Flag - Wind Speed Only

We ask that forecast offices note in the attached spreadsheet (column C) any stations (with red or orange shading) that should be excluded from this request and continue to be used in RTMA/URMA.  We ask for this feedback by Tuesday, April 13th.

Note that many stations in the Northwest, particularly in Washington and Oregon, fall within both the CONUS and Alaska domains.  The spreadsheet includes a column noting the primary flagging domain.  If a station falling within CONUS is listed with the domain “Alaska”, this means that the station is not currently being used for CONUS (i.e., not on the station use list), but is being used for Alaska.  In other words, flagging these stations will not impact the CONUS domain.

Please let us know if you have any questions.

Thanks,
-Matt

--
Matthew Morris RTMA/URMA Discussion Group Virtual Lab Forum http://vlab.noaa.gov/web/715073/home/-/message_boards/view_message/14297953VLab.Notifications@noaa.gov

Attachments:

MM
Matthew Morris, modified 4 Years ago.

RE: Upcoming widespread flagging of CWOP & AWS wind speed observations

Youngling Posts: 169 Join Date: 12/6/17 Recent Posts
Hi All,

As a reminder, we are proposing a mass flagging of all CWOP and AWS wind speed observations throughout the CONUS and Alaska domains due to a persistent low wind speed bias.  This update is expected to take place on Friday, April 30th depending upon CWD.  If you haven't already done so, please note any stations that you wish to have excluded from this flagging request by tomorrow evening (Wednesday, April 28th).
Thanks,
Matt

On Wed, Apr 14, 2021 at 1:23 PM VLab Notifications <VLab.Notifications@noaa.gov> wrote:
Hi All,

It was recently discovered that a significant number of CWOP and AWS stations throughout CONUS were inadvertently excluded from the initial spreadsheet and KML file.  These missed stations are partially whitelisted based on the wind direction, in order to account for obstructions (e.g., buildings).

These newly-identified stations are plotted in the attached KML file: stations with red placemarks will be added to the SDM reject list, while stations with yellow placemarks are already flagged as a result of earlier QC requests.  The spreadsheet lists the provider for all stations, as well as the latitude/longitude for the stations that have recently reported.  The stations in the earlier spreadsheet and KML file are not duplicated in the new spreadsheet and KML file.

 Part II: CWOP/AWS Stations to Flag - Wind Speed...

The impact is limited to the CONUS domain only.  Given this new information, the widespread flagging of CWOP and AWS wind speed observations will need to be delayed.  We ask that forecast offices note any additional stations that should be excluded from flagging in the attached spreadsheet by Tuesday, April 27th.  The updates to the SDM reject list will take place on or around Friday, April 30th, depending on CWD.

Please let us know if you have any questions.

Thanks,
Matt

On Wed, Mar 31, 2021 at 8:56 AM VLab Notifications <VLab.Notifications@noaa.gov> wrote:
Hi All,

Due to the persistent low wind speed bias that has continued to impact RTMA/URMA and the NBM, we are proposing a mass flagging of all CWOP and AWS wind speed observations throughout the CONUS and Alaska domains.  Recall that the SDM QC flags do not apply to wind gust observations.  The relevant updates to the SDM reject list are expected to take place on Friday, April 16th depending on CWD.

For the CONUS domain, CWOP and AWS wind speed/gust observations are rejected by default, unless the station is on the mesonet station uselist.  Thus, any new CWOP or AWS wind speed/gust observations will not be assimilated in the current 2D-RTMA/URMA suite.

For Alaska, however, mesonet wind speed observations are not rejected by default due to reduced observation counts over the domain.  CWOP and AWS stations reporting recently have been identified and will be flagged for wind speed only.  Thus, any CWOP or AWS stations that begin or resume reporting following this request will be considered for assimilation.  Should the Alaska region offices wish to flag any of these new stations, we ask that the offices submit the requests through the existing RTMA/URMA QC form.

The attached KML file shows the location of the stations that will be flagged for wind (in red), as well as those that are already flagged for wind on the SDM list (in yellow).  Many of the stations on the CONUS use list are not currently reporting and, thus, not displayed in the KML file; these stations will, however, still be included in the bulk flagging request.

 CWOP/AWS Stations to Flag - Wind Speed Only

We ask that forecast offices note in the attached spreadsheet (column C) any stations (with red or orange shading) that should be excluded from this request and continue to be used in RTMA/URMA.  We ask for this feedback by Tuesday, April 13th.

Note that many stations in the Northwest, particularly in Washington and Oregon, fall within both the CONUS and Alaska domains.  The spreadsheet includes a column noting the primary flagging domain.  If a station falling within CONUS is listed with the domain “Alaska”, this means that the station is not currently being used for CONUS (i.e., not on the station use list), but is being used for Alaska.  In other words, flagging these stations will not impact the CONUS domain.

Please let us know if you have any questions.

Thanks,
-Matt

--
Matthew Morris RTMA/URMA Discussion Group Virtual Lab Forum http://vlab.noaa.gov/web/715073/home/-/message_boards/view_message/14297953VLab.Notifications@noaa.gov

--
Matthew Morris RTMA/URMA Discussion Group Virtual Lab Forum http://vlab.noaa.gov/web/715073/home/-/message_boards/view_message/14500858 VLab.Notifications@noaa.gov