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.
Glenn, I ran gdinfo on your file and find that the times look like: Number of grids in file: 37 Maximum number of grids in file: 1500 NUM TIME1 TIME2 LEVL1 LEVL2 VCORD PARM 1 010215/0015F000 010215/0015F000 0 NONE RDSP1 2 010215/0045F000 010215/0045F000 0 NONE RDSP1 3 010215/0115F000 010215/0115F000 0 NONE RDSP1 4 010215/0145F000 010215/0145F000 0 NONE RDSP1 5 010215/0215F000 010215/0215F000 0 NONE RDSP1 6 010215/0245F000 010215/0245F000 0 NONE RDSP1 etc. On the file that I decoded here with dcgrib2, I have: Number of grids in file: 41 Maximum number of grids in file: 100 NUM TIME1 TIME2 LEVL1 LEVL2 VCORD PARM 1 010215/0015F000 0 NONE RDSP1 2 010215/0045F000 0 NONE RDSP1 3 010215/0115F000 0 NONE RDSP1 4 010215/0145F000 0 NONE RDSP1 5 010215/0215F000 0 NONE RDSP1 6 010215/0245F000 0 NONE RDSP1 7 010215/0315F000 0 NONE RDSP1 etc. So, it appers that NMAP may be choking on the way the time1:time2 are in your file. Are you using dcgrib2? What is the platform you are decoding on so that I can double check the results. Thanks, Steve Chiswell