I wasn't seeing that. For example, all of the SAUS70 products were coming
in under the NGRID feed type.
3712 20120315/205607.833 NGRID 15948025 SAUS70 KWBC 152100
RRJ
3646 20120315/205607.841 NGRID 15948028 SAUS70 KWBC
152100
163 20120315/205607.841 NGRID 15948029 SAUS70 KWBC
152056
3751 20120315/205809.863 NGRID 15948453 SAUS70 KWBC 152100
RRA
3739 20120315/205809.883 NGRID 15948456 SAUS70 KWBC 152100
RRE
3677 20120315/205809.886 NGRID 15948458 SAUS70 KWBC 152100
RRF
3756 20120315/205809.893 NGRID 15948461 SAUS70 KWBC 152100
RRH
3710 20120315/205809.902 NGRID 15948462 SAUS70 KWBC 152100
RRK
3747 20120315/205809.904 NGRID 15948464 SAUS70 KWBC 152100
RRC
3652 20120315/205809.906 NGRID 15948466 SAUS70 KWBC
152100
3704 20120315/205809.909 NGRID 15948469 SAUS70 KWBC 152100
RRJ
3223 20120315/205809.910 NGRID 15948470 SAUS70 KWBC 152100
RRP
3705 20120315/205809.913 NGRID 15948472 SAUS70 KWBC 152100
RRD
3752 20120315/205809.914 NGRID 15948473 SAUS70 KWBC 152100
RRO
3711 20120315/205809.915 NGRID 15948476 SAUS70 KWBC 152100
RRG
3750 20120315/205809.925 NGRID 15948481 SAUS70 KWBC 152100
RRI
I wasn't seeing a SAUS70 under IDD|DDPLUS.
This was true of a lot of other METARs:
1628 20120315/205721.842 NGRID 15948429 SANA14 KAWN 152100
RRA
96 20120315/205721.851 NGRID 15948430 SAUS51 KWBC 152000
RRE
831 20120315/205721.851 NGRID 15948431 SACN59 CWAO 152000
RRI
84 20120315/205721.851 NGRID 15948432 SAIY32 LIIB 152050
RRA
92 20120315/205721.851 NGRID 15948433 SAIY31 LIIB 152050
RRA
102 20120315/205721.851 NGRID 15948434 SABE31 TXKF
152055
95 20120315/205721.851 NGRID 15948435 SACN89 CWAO 152000
RRE
96 20120315/205721.851 NGRID 15948436 SACN93 CWAO 152000
RRF
125 20120315/205725.840 NGRID 15948437 SAUS41 KBGM 152055
/pMTRAVP
136 20120315/205725.841 NGRID 15948438 SAUS45 KABQ 152057
/pMTRCAO
90 20120315/205727.841 NGRID 15948439 SAAI41 FHAW
152050
97 20120315/205737.851 NGRID 15948440 SAMT20 GQNN
152100
1494 20120315/205737.852 NGRID 15948442 SAXN17 KAWN 152000
RRK
415 20120315/205737.852 NGRID 15948443 SASA00 KAWN
152100
127 20120315/205739.851 NGRID 15948446 SAUS46 KSGX 152057
/pMTRNJK
222 20120315/205739.851 NGRID 15948447 SAUS42 KRAH 152057
/pMTRGSO
1729 20120315/205743.864 NGRID 15948448 SAXX60 KAWN
152100
132 20120315/205751.852 NGRID 15948449 SAUS43 KABR 152057
/pMTR8D3
133 20120315/205755.861 NGRID 15948450 SAUS43 KUNR 152057
/pMTRD07
135 20120315/205757.861 NGRID 15948451 SAUS42 KMHX 152057
/pMTRNBT
1677 20120315/205807.872 NGRID 15948452 SAZZ40 KAWN 152100
RRI
3751 20120315/205809.863 NGRID 15948453 SAUS70 KWBC 152100
RRA
992 20120315/205809.882 NGRID 15948454 SACN59 KWBC
152058
108 20120315/205809.882 NGRID 15948455 SACN94 KWBC
152058
3739 20120315/205809.883 NGRID 15948456 SAUS70 KWBC 152100
RRE
3728 20120315/205809.884 NGRID 15948457 SAUS99 KWBC 152058
RRB
But I was getting enough METARs in that it wasn't triggering alarms.
I just think NWS inadvertently changed the SBN channel number in the
NOAAPort CCB for these WMO headers to NWSTG2 (channel 6) rather than NWSTG
(channel 5). Interestingly, they were still going out on the NWSTG channel.
-- Dan
On Fri, Mar 16, 2012 at 10:49 AM, Steve Emmerson <steve@xxxxxxxxxxxxxxxx>wrote:
> On 03/16/2012 09:28 AM, Daniel Vietor wrote:
>
>> The interesting part of this was that not all of the METAR products were
>> mislabeled. Only about 2/3rds of the headers. I'm not sure how that
>> could be accomplished??
>>
>
> The LDM product-queue will reject as a duplicate a data-product that has
> the same MD5 checksum as one that's already in the product-queue -- even if
> the feedtypes of the two products differ. I suspect this is what's
> happening between the IDD|DDPLUS tagged METARs and the NGRID tagged METARs.
>
> --Steve
>
>
> ______________________________**_________________
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/**mailing_lists/<http://www.unidata.ucar.edu/mailing_lists/>
>
--
*Dan Vietor*
*Senior Systems Engineer*
Contractor, LS Technologies
Aviation Weather Center
Kansas City, MO
816.584.7271
