Hi, Well, one option that might make a parser easier to write is to use the XML view of the catalog rather than HTML: https://thredds.ucar.edu/thredds/catalog/satellite/goes16/GOES16/CONUS/Channel02/current/catalog.xml Then you can parse the XML and look at the "urlPath" attributes in the "dataset" elements. The spec for the XML is here: https://www.unidata.ucar.edu/software/thredds/current/tds/catalog/InvCatalogSpec.html If you're a Python user, an alternative is to use our Siphon library which can parse catalogs: from siphon.catalog import TDSCatalog cat = TDSCatalog('http://thredds.ucar.edu/thredds/catalog/satellite/goes16/GOES16/CONUS/Channel02/current/catalog.xml') latest = cat.datasets latest.download() That code above will download the latest file. Siphon also provides functionality to access in Python using other methods. Documentation for Siphon is available here: https://unidata.github.io/siphon/ Hope this helps, Ryan > Hi all, > > I'm trying to understand the various options in the "catalog" page > for obtaining near-real time GOES imagery from your Thredds server. > It looks like if I set up a script to run every 5 minutes, I would point > it to (for example) > > https://thredds.ucar.edu/thredds/catalog/satellite/goes16/GOES16/CONUS/Channel02/current/catalog.html > > read the name of the most recent file (or maybe just guess it from the > time, since the schedule is quite regular), and then grab it from > > "https://thredds.ucar.edu/thredds/fileServer/satellite/goes16/GOES16/CONUS/Channel02/current/" > + filename. > > Is that the best way to do this, or is one of the other "Access" options > a better way to go? Ticket Details =================== Ticket ID: KXN-592759 Department: Support THREDDS Priority: Normal Status: Closed =================== 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.
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.