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.
Brice, > I can't directly, but I can show you what I crafted for him and what I am > using to get the same data from another source. And I am pretty sure that I > can show you what we attempted to use from the workaround off the web page. > > His first server requests would have come from each of his clients this way - > > Request FT4 "^WT01.*|^LR01.*|^PT.*|^LR01.*|^HR01.*|^LW01.*" > 134.xxx.xxx.aaa > > Then I had him try changing one of his clients to - > > Request FT4 "(^WT01.*|^LR01.*|^PT.*|^LR01.*|^HR01.*|^LW01.*)" > 134.xxx.xxx.aaa > > Which is what I interpreted the workaround to say. Then we tried "(())", > partially because I will have 4-5 clients coming trying to get the same data > and all hidden behind the SSH tunnel. Just FYI, you can dispense with the ".*" suffixes in all the patterns because they add nothing: the patterns "^WT01.*" and "^WT01" will match exactly the same strings (all strings that begin with "WT01"). > Thanks for help, Steve. > > Brice > Regards, Steve Emmerson Ticket Details =================== Ticket ID: BIG-900661 Department: Support LDM Priority: Normal Status: Open