Ryan, Well...the default selection on the page you are viewing *should* be NetCDF-3. The place you would choose is a selection window at the bottom of the box on the right side of this page: http://thredds.ucar.edu/thredds/ncss/grid/grib/NCEP/NAM/CONUS_12km/files/NAM_CONUS_12km_20130614_1200.grib2/dataset.html You can switch between "netcdf" and "netcdf4" Perhaps you could try downloading the same data in both formats, to see if one of them works with arcgis10.1. I'm going to ask around and see if anyone here at Unidata has any familiarity with arcgis. While I gather you are not running your own TDS, you may find the information on these two pages useful: http://www.unidata.ucar.edu/projects/THREDDS/tech/tds4.3/UpgradingTo4.3.html http://www.unidata.ucar.edu/projects/THREDDS/tech/tds4.3/AccessChangesTds4.3.html > hi, > > thnx4reply. > > where would i select 'netcdf4' vs 'netcdf3'? i don't seem to see any > option on thredds wwweb pages. > > if there's more compression of netcdf4 vs netcdf3, does that result in > file naming convention change? see attached screen capture for shorter > new name of .nc file vs longer old (pre june 7) name. this change > appears to be on the ucar side, not the arcgis (end-user) side. > > also thredds page for selecting nam variable has a changed 'look' as > well. (wish i had screen capture of 'old' nam variable selection page > (for netcdf format data) to send for comparison w/ new nam variable > selection page (for netcdf format data). > > in the end, it may be that arcgis10.1 does not recognize netcdf4 format. > as i said at the top of this message, i don't see where i have option > to specify netcdf3 vs netcdf4 file format. > > also, documentation for arcgis10.1 does not specify which version netcdf > format (-3 or -4) their translation routine (from netcdf to raster) > works with. > > perhaps if there's a way i can specify grib2 to netcdf3 (rather than > netcdf4) format, i could try narrowing down where the problem lies > (other than w/ the end user, of course). > > thnx, > ryan rudnicki > san marcos, texas > > > > > On 6/14/2013 11:23 AM, Unidata THREDDS Support wrote: > > Hi Ryan, > > > > I think you are looking at the same file. A possible difference between > > 4.2 and 4.3 versions of the TDS (the transition a couple of weeks ago) that > > might trip you up would be a migration from NetCDF-3 to NetCDF-4, which > > have more compression. However, you can still download files in NetCDF-3 > > format, and this is actually the default. Do you know if you have been > > selecting "netcdf4" for an output format? I really don't know much about > > arcgis, so I can't comment on how it reads NetCDF, but NetCDF-3 hasn't > > changed. > > > > -Lansing Madry > > Unidata > > Boulder, Colorado > > > >> sent follow-up info, but have not heard back. > >> > >> que paso? > >> > >> ryan rudnicki > >> san marcos, texas > >> > >> > >> On 6/6/2013 5:14 PM, Unidata THREDDS Support wrote: > >>> > >>> ryanr, > >>> > >>> Your Ticket has been received, and a Unidata staff member will review it > >>> and reply accordingly. Listed below are details of this new Ticket. > >>> Please make sure the Ticket ID remains in the Subject: line on all > >>> correspondence related to this Ticket. > >>> > >>> Ticket ID: AZL-675809 > >>> Subject: what happened?... motherlode...ncep... nam...netCDF data? > >>> Department: Support THREDDS > >>> Priority: Normal > >>> Status: Open > >>> > >>> > >>> > >>> Please let us know how we can assist you further. > >>> > >>> Unidata User Support > >>> > >>> > >>> > >> > >> > > > > -Lansing Madry > > Unidata > > Boulder, Colorado > > > > Ticket Details > > =================== > > Ticket ID: AZL-675809 > > Department: Support THREDDS > > Priority: High > > Status: Open > > > > > > > > -Lansing Madry Unidata Boulder, Colorado Ticket Details =================== Ticket ID: AZL-675809 Department: Support THREDDS Priority: High 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.