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.
The feed specification? Interesting. I'd thought it was one of the regular expressions. I'll take a look. > A long pattern which had an allow like (example, not actual) on the > upstream site: > > ALLOW ldm01.allisonhouse.com > IDS|DDPLUS|HRS|NEXRAD2|NEXRAD3|NIMAGE|FSL2|CONDUIT|ETC THAT EXCEEDED 256 > CHARACTERS|NOTHER > > Basically, it cut off the last feed, NOTHER, so we weren't allowed to get > it. Would putting that one on a second line solve that issue, like: > > ALLOW ldm01.allisonhouse.com > IDS|DDPLUS|HRS|NEXRAD2|NEXRAD3|NIMAGE|FSL2|CONDUIT|ETC > ALLOW ldm01.allisonhouse.com NOTHER Regards, Steve Emmerson Ticket Details =================== Ticket ID: WOM-274153 Department: Support LDM Priority: Normal Status: Open =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.