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.
Hi Mary, re: > My name is Mary Tyree and with your help I try to keep the ldm feed > running through our workstation aeolus. Good to hear from you again! re: > I most recently contacted you to update the information about the > contact person for aeolus. Larry Riddle retired quite a while ago (5 > years I think). Yes, I did the update. re: > Since then I've kept an eye on the ldm feed and with > some incredible luck the workstation continues to run. aeolus must be getting pretty "long in the tooth" ... re: > This morning I had a request from John Graham - about a feed for ldm. > Could you please guide me as to how to properly allow the site requested > access to lightning data: > > # Larry Riddle address@hidden > ALLOW NLDN ^aeolus\.ucsd\.edu$ Three things: - the agreement with the providers of both sources of LIGHTNING data prohibit the re-distribution of the data beyond one's campus So, if the "site" in "site requested access" is something other than UCSD, you cannot add an ALLOW to relay the data. If the "site" is another department/group in UCSD, then you can relay the data if you already have it, BUT you need to remind the LDM/IDD administrator in that department/group that they are not allowed to re-distribute the data. - there is already a blanket ALLOW for UCSD machines in place on aeolus: # UCSD machines allow ANY ^[a-zA-Z].*\.ucsd\.edu$ This ALLOW will work if the name of the REQUESTing ucsd.edu machine begins with an alphabetical character (i.e., it will not work if the machine name begins with a number, etc.). - aeolus is not REQUESTing LIGHTNING data, so it will not be able to relay it But, there is already an ALLOW for LIGHTNING data on the source for the NLDN data, striker2.atmos.albany.edu. So, if you add the following line to the ~ldm/etc/ldmd.conf file, aeolus will start receiving the data: request LIGHTNING ".*" striker2.atmos.albany.edu And, if the ucsd.edu machine to which aeolus will relay LIGHTNING data to has added an appropriate REQUEST to aeolus, LIGHTNING data will start flowing to it: <in ~ldm/etc/ldmd.conf on the other ucsd.edu machine> request LIGHTNING ".*" aeolus.ucsd.edu Please let us know if the above helps! Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: KZT-246763 Department: Support IDD Priority: Normal Status: Closed