This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Qingping, Only US NWS bulletins have PILs. Only those products with a PIL on the line following the WMO identifier will have the /p tag added to the LDM identifier. Steve Chiswell Unidata User Support >From: Qingping Xu <address@hidden> >Organization: UCAR/Unidata >Keywords: 200104262005.f3QK5HL19697 >Stupid me. I compile and installed the new pqing with ldm >still running... cannot write to pqing, so still the old >pqing. Now it is OK. I noticed that not all the IDS/HDS stuff >have an /p ID. Is that normal? > >Thanks > >-Qingping > > >Apr 26 20:03:14 pqutil: 507 20010426200313.872 IDS|DDPLUS 636 SXUS70 >KWAL 262001 >Apr 26 20:03:14 pqutil: 2645 20010426200313.873 IDS|DDPLUS 637 FXUS39 >KMWI 262000 >Apr 26 20:03:14 pqutil: 500 20010426200313.874 IDS|DDPLUS 638 SXUS70 >KWAL 262001 >Apr 26 20:03:14 pqutil: 556 20010426200313.969 NNEXRAD 009 SDUS55 >KPIH 262002 /pN0RSFX >Apr 26 20:03:14 pqutil: 58 20010426200314.091 NNEXRAD 012 SDUS42 >KRAH 261704 /pRCMRAX >Apr 26 20:03:14 pqutil: 58 20010426200314.159 NNEXRAD 013 SDUS43 >KSGF 261710 /pRCMSGF >Apr 26 20:03:14 pqutil: 228 20010426200314.163 NNEXRAD 014 SDUS54 >KOUN 261716 /pNTPTLX >Apr 26 20:03:14 pqutil: 109 20010426200314.248 NNEXRAD 016 SDUS53 >KLMK 261726 /pN0SLVX >Apr 26 20:03:14 pqutil: 3263 20010426200314.366 HDS 552 ZVIV92 >KWBC 261200 /mAVN >Apr 26 20:03:14 pqutil: 2093 20010426200314.369 HDS 553 ZVJV92 >KWBC 261200 /mAVN >Apr 26 20:03:15 pqutil: 183 20010426200314.866 IDS|DDPLUS 639 FTEG31 >HECA 261700 >Apr 26 20:03:15 pqutil: 252 20010426200314.868 IDS|DDPLUS 640 UDEU40 >ESWI 261722 >Apr 26 20:03:15 pqutil: 74 20010426200314.869 IDS|DDPLUS 641 SRUS73 >KMQT 262002 /pRR7P75 >Apr 26 20:03:15 pqutil: 689 20010426200314.870 IDS|DDPLUS 642 FCFR32 >LFPW 261700 >Apr 26 20:03:15 pqutil: 212 20010426200314.871 IDS|DDPLUS 643 FTUS46 >KHNX 261725 /pTAFBFL >Apr 26 20:03:15 pqutil: 245 20010426200314.872 IDS|DDPLUS 644 FTUS46 >KHNX 261725 /pTAFFAT >Apr 26 20:03:15 pqutil: 74 20010426200314.872 IDS|DDPLUS 645 SRUS74 >KEWX 262003 /pRR7DRT >Apr 26 20:03:15 pqutil: 74 20010426200314.873 IDS|DDPLUS 646 SRUS71 >KILN 262003 /pRR7CVG >Apr 26 20:03:15 pqutil: 195 20010426200314.873 IDS|DDPLUS 647 FTUS41 >KPBZ 261725 /pTAFPIT >Apr 26 20:03:15 pqutil: 74 20010426200314.873 IDS|DDPLUS 648 SRUS74 >KLIX 262003 /pRR7BTR >Apr 26 20:03:15 pqutil: 80 20010426200314.874 IDS|DDPLUS 649 FTUS45 >KGJT 261725 /pTAFGUC >Apr 26 20:03:15 pqutil: 109 20010426200314.874 IDS|DDPLUS 650 SAUS45 >KCYS 261725 /pMTRIDV >Apr 26 20:03:15 pqutil: 130 20010426200314.875 IDS|DDPLUS 651 SXPA50 >KWAL 261724 >Apr 26 20:03:15 pqutil: 104 20010426200314.875 IDS|DDPLUS 652 SAUS70 >KWBC 261700 RRM >Apr 26 20:03:15 pqutil: 717 20010426200314.875 IDS|DDPLUS 653 SRUS27 >KZAU 262001 >Apr 26 20:03:15 pqutil: 184 20010426200314.876 IDS|DDPLUS 654 CDUS27 >KZDC 262001 >Apr 26 20:03:15 pqutil: 469 20010426200314.876 IDS|DDPLUS 655 SRUS27 >KZDC 262001 >Apr 26 20:03:15 pqutil: 779 20010426200314.877 IDS|DDPLUS 656 SRUS27 >KZTL 262001 >Apr 26 20:03:15 pqutil: 655 20010426200314.877 IDS|DDPLUS 657 SRUS27 >KZME 262001 >Apr 26 20:03:15 pqutil: 624 20010426200314.878 IDS|DDPLUS 658 SRUS27 >KZJX 262001 >Apr 26 20:03:15 pqutil: 866 20010426200314.878 IDS|DDPLUS 659 SRUS27 >KZNY 262001 >Apr 26 20:03:15 pqutil: 1350 20010426200314.878 IDS|DDPLUS 660 SOPA46 >KWBC 261959 >Apr 26 20:03:15 pqutil: 1109 20010426200314.879 IDS|DDPLUS 661 SOUS50 >KWBC 261959 >Apr 26 20:03:16 pqutil: 1223 20010426200315.865 IDS|DDPLUS 662 SAUS70 >KWBC 261724 > > > > >On Thu, 26 Apr 2001, Michael W Dross wrote: > >> >> Still looks like its not appending the PIL id. I have not used 5.1.3, so >> I can't say. But there should be a >> portion of code similar to the following that deals with PIL such as: >> >> if(usePil == 1) >> { >> if ((feedtype & DDS)||(feedtype & PPS)||(feedtype & IDS)|| >> (feedtype & HRS)||(feedtype & NEXRAD)) >> { >> usePil = 1; >> uinfo("Creating AFOS-like pil tags\0"); >> } >> else >> { >> usePil = 0; >> } >> } >> >> >> I just added the "||(feedtype & NEXRAD))" >> >> Also upon recollection I added the scan_binary, around line 626 >> >> if (feedtype & HDS) >> { >> if(chkflag == CHK_CHECK >> || (isatty(ifd) && chkflag != CHK_DONT)) >> setTheScanner(scan_wmo_binary_crc); >> else >> setTheScanner(scan_wmo_binary); >> } >> >> else if (feedtype & NEXRAD) << >> { >> setTheScanner(scan_wmo_binary); >> } >> >> >> >> >> >> I suspect the code in 5.1.3 is fairly similar.. >> >> Let me know.. >> >> >> Mike >> >> >> >> >> >> > >> Qingping Xu > >> <qxu@operations.o To: Michael W Dross <mwdros > address@hidden> >> cs.ou.edu> cc: > >> bcc: > >> 04/26/2001 03:46 Subject: Re: Asking LDM hel > p From Qingping >> PM > >> > >> > >> >> >> >> >> I have changed and recompiled the source for pqing. Now my feed looks >> like the following, looks like an int is appended for every NNEXRAD >> product. Since I was using LDM 5.1.3. I noticed some changes >> in the pqing source as shown in diff below. >> >> -Qingping >> >> >> > diff pqing.c pqing512.c >> 58,60c58,59 >> < int useNex=1; /* 1/0 flag to retype nexrad products as NEXRAD */ >> < /* skipLeadingCtlString: used in computing checksum, default is to skip >> */ >> < static int skipLeadingCtlString = 1; >> --- >> > /* skipLeadingCtlString: used in computing checksum, default is to not >> skip */ >> > static int skipLeadingCtlString = 0; >> 236,237d234 >> < "\t-N Do not place NEXRAD products in feedtype >> NEXRAD\n"); >> < (void)fprintf(stderr, >> 323c320 >> < * If user has not disabled skipLeadingCtlString with -5 option, >> --- >> > * If user has enabled skipLeadingCtlString with -5 option, >> 351,355d347 >> < if((strncmp(prod.info.ident,"SDUS5",5) == 0)&&(useNex == 1)) >> < { >> < prod.info.feedtype = NEXRAD; >> < } >> 464d455 >> < useNex = 1; >> 466c457 >> < while ((ch = getopt(ac, av, "vxcni5Nl:b:p:P:T:q:r:f:")) != EOF) >> --- >> > while ((ch = getopt(ac, av, "vxcni5l:b:p:P:T:q:r:f:")) != EOF) >> 483,485d473 >> < case 'N': >> < useNex = 0; >> < break; >> 487c475 >> < skipLeadingCtlString = 0; >> --- >> > skipLeadingCtlString = 1; >> 635c623 >> < else if (feedtype & (NMC2 || NMC3)) >> --- >> > else if (feedtype & NEXRAD) >> >> >> >> >> >> >> ======================================================================= >> Apr 26 19:20:13 pqutil: 19325 20010426192013.073 HDS 198 YVWB85 >> KWBG 261600 /mRUC2 >> Apr 26 19:20:14 pqutil: 56 20010426192013.352 NNEXRAD 597 SDUS55 >> KPSR 261910 >> Apr 26 19:20:14 pqutil: 98 20010426192013.476 NNEXRAD 598 SDUS56 >> KMTR 261916 >> Apr 26 19:20:14 pqutil: 102 20010426192013.673 NNEXRAD 599 SDUS55 >> KABQ 261913 >> Apr 26 19:20:14 pqutil: 221 20010426192013.681 NNEXRAD 600 SDUS52 >> KMHX 261914 >> Apr 26 19:20:14 pqutil: 369 20010426192013.686 NNEXRAD 601 SDUS51 >> KBTV 261639 >> Apr 26 19:20:14 pqutil: 128 20010426192013.955 NNEXRAD 604 SDUS51 >> KLWX 261910 >> Apr 26 19:20:14 pqutil: 36387 20010426192013.956 HDS 199 YRWB85 >> KWBG 261600 /mRUC2 >> Apr 26 19:20:14 pqutil: 391 20010426192014.234 NNEXRAD 605 SDUS56 >> KEKA 261911 >> Apr 26 19:20:15 pqutil: 334 20010426192014.954 NNEXRAD 607 SDUS54 >> KEWX 261916 >> Apr 26 19:20:15 pqutil: 4576 20010426192014.958 HDS 200 HTNJ99 >> EGRR 261200 /mUKM_45 >> >> >> >> On Thu, 26 Apr 2001, Michael W Dross wrote: >> >> > >> > Hi, >> > >> > Yes I modified pqing.c to have it create PIL ID's like it does with the >> > DDPLUS or HDS feeds for the NNEXRAD feed type. >> > I have attached the pqing.c I modified for ldm version ldm-5.1.2. >> > >> > At line 604 I changed to: >> > >> > >> > if ((feedtype & DDS)||(feedtype & PPS)||(feedtype & IDS)|| >> > (feedtype & HRS)||(feedtype & NEXRAD)) >> > >> > I believe that was it. >> > >> > Hopefully you can compile it.(See attached file: pqing.c). >> > >> > >> > Your pqing syntax is the same as mine. >> > >> > Let me know if you can compile pqing ok.. >> > >> > * I am going to copy Unidata, to see if they might be able to incorporate >> > the changes I made into a future relase of LDM. * >> > >> > Mike >> > >> > >> > >> > >> > >> >> > Qingping Xu >> >> > <qxu@operations.o To: >> address@hidden >> > cs.ou.edu> cc: >> >> > bcc: >> >> > 04/26/2001 02:08 Subject: Asking LDM help >> >From Qingping >> > PM >> >> > >> >> > >> >> > >> > >> > >> > >> > Mike, >> > >> > I have set up our system similar to yours. Both the DDPLUS|IDD and HDS >> > works fine. However, our downstream tester (who used to get data from >> > unidata) complains about the NIDS feed (They can see the feed but cannot >> > save or decode). >> > >> > The way I configure our system on noaaport box is same as yours. >> > On our BSD box, I set up pqing to insert all products (HDS, IDD and NIDS) >> > into the same queue, which then feed downstream LDMs. >> > >> > The syntax I used for NIDS is >> > >> > pqing -f NNEXRAD -P 5003 noaaport1 >> > >> > I am not sure it is the right feedtype. Also I remembered that you >> > mentioned before that you have to modify LDM source to insert >> > AFOS style information. Does that have something to do with complying >> > with the FOS feed? If it is, can you point to us how/where to modify >> > the ldm source? >> > >> > Thanks >> > >> > -Qingping >> > >> > >> > >> > >> >> >> >> >> >> >