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 again, Regarding modifying the station database, the authority on such things has supplied the following information: ---- STNDB.CORE - primary station database; binary; not user modifiable STNDB.SITE - secondary station database; text; managed by site administrator STNDB.USER - tertiary station database; text; managed by individual user The hierarchy for use of these files is STNDB.USER followed by STNDB.SITE then STNDB.CORE. Entries in the site or user modifiable files supersede the entries in STNDB.CORE. ---- So there is no need to modify the binary STNDB.CORE, that's easier then. For your use cases it shouldn't matter if you use a .SITE or .USER file for this, so long as you understand the hierarchy shown above. There should be an existing ~/data/STNDB.SITE file, which is textual and includes plenty of examples to go off of. Again, since your original issue turned out to be for Gempak, the above will not address that particular problem. Best, -Mike Cheers, Tom -- Ticket Details =================== Ticket ID: UKN-727350 Department: Support McIDAS 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.