Hi Kevin, Just a quick update. We've found a few bugs in the CFPointWriter code (or maybe the Gempak IOSP code), but we are working on getting things going. We hope to have this fixed soon. Cheers, Sean > Hi Kevin, > > If you have any questions about THREDDS, please let me know - I'd be > happy to help out over the phone, video conferencing, logging into your > system to check things out, or even make some screencasts! > > There isn't a graphical method that I know of, but the pieces of code are > there to do it in a java program. We plan on making a main method in > ucar.nc2.ft.point.writer.CFPointWriter that accepts command line args, > similar to what is done in NetcdfDataset, and then you will be able to use > it on the command line. > > Cheers! > > Sean > > > Thanks Sean! Since you say that there is not a command-line option just yet > > ... do I take it that there maybe is a graphical method that might work > > (e.g. ToolsUI or IDV)? > > > > Hope the workshop goes well ... I am actually just starting to dive into > > the world of THREDDS so maybe next year I'll attend! > > > > --Kevin > > > > _____________________________________________ > > Kevin Tyle, Systems Administrator > > Dept. of Atmospheric & Environmental Sciences > > University at Albany > > Earth Science 235, 1400 Washington Avenue > > Albany, NY 12222 > > Email: address@hidden > > Phone: 518-442-4578 > > _____________________________________________ > > > > > > -----Original Message----- > > From: Unidata netCDF Java Support [mailto:address@hidden > > Sent: Wednesday, October 15, 2014 1:55 PM > > To: Tyle, Kevin R > > Cc: address@hidden; Berman, Jeremy D > > Subject: [netCDFJava #TOX-206476]: Problems converting GEMPAK point (METAR) > > data to a usable NetCDF file > > > > Hi Kevin, > > > > netcdf-java can read the example file you sent without any issues. > > Unfortunately, we do not yet have a write method that can be used from the > > command line yet for point data, but it is on our todo list soon - we'll > > take a look after our THREDDS workshop is finished (the workshop is next > > week). > > > > I'll let you know when we have something ready to go. > > > > Sean > > > > > Hi, > > > > > > We are using the netcdf-java library to convert GEMPAK METAR data into > > > NetCDF. While the conversion program runs without error, the resulting > > > NetCDF file is very small and basically does not have any of the various > > > station parameters in there. > > > > > > I've attached a sample GEMPAK surface data file, which only has US > > > stations in there for brevity. > > > > > > The command line we use is this: > > > > > > > > > > > > java -Xmx1G -classpath netcdfAll-4.5.jar > > > ucar.nc2.dataset.NetcdfDataset -in 141002_mtr_us.gem -out > > > 141002_mtr_us.nc > > > > > > > > > > > > I've also tried it with the 4.3 version of netcdf-java. > > > > > > > > > > > > I've attached the input GEMPAK file and the resulting output NetCDF file. > > > > > > > > > > > > Is there anything different we have to do for point data, versus gridded > > > data when converting GEMPAK files? Since IDV can display GEMPAK METAR > > > files, it would seem that the capability for netcdf-java to understand > > > and convert this type of data exists. > > > > > > > > > > > > Thanks for any insight ... > > > > > > > > > > > > --Kevin > > > > > > > > > _____________________________________________ > > > Kevin Tyle, Systems Administrator > > > Dept. of Atmospheric & Environmental Sciences University at Albany > > > Earth Science 235, 1400 Washington Avenue Albany, NY 12222 > > > Email: address@hidden<mailto:address@hidden> > > > Phone: 518-442-4578 > > > _____________________________________________ > > > > > > > > > > > > > Ticket Details > > =================== > > Ticket ID: TOX-206476 > > Department: Support netCDF Java > > Priority: Urgent > > Status: Open > > > > Ticket Details =================== Ticket ID: TOX-206476 Department: Support netCDF Java Priority: Urgent 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.