Re: [Opengrads-devel] grads vs gradsdap in v2

[Arlindo da S. <da...@al...>]

On Feb 4, 2008 12:08 PM, Jennifer Adams <jm...@co...> wrote:

> In a couple of years the Unidate netcdf library will have swallowed up
> libnc-dap (see below),
>

That would be fantastic!


> so gradsdap is the one that will eventually be phased out. Until then, I
> feel it's better to link grads with the Unidata library and gradsdap with
> OPeNDAP version. Then when nc4 is ready (it's waiting for hdf5 to come out
> of beta status), we can link grads with nc4 library and leave gradsdap
> alone.
>

I have been experimenting with the current beta of netcdf4 in the context of
v1.9 (binary name: gradsnc4) and I'd say that, pending low level hdf-5
issues which are not visible at the API level, netcdf-4 is pretty ready;
gradsnc4 already passes 100% of our tests. I have both netcdf4 beta and the
hdf-5  version it requires in the supplibs. These will be replaced with the
final versions as they become available.  We have all the m4 discovery
macros for it already.

(The gradsnc4 binary is just as huge as gradsdap, as both libdap and hdf5
are bloated. Put these 2 together we will have a very heavy load, indeed. It
may be time to bring old gradsc back :-)


> I am trying to keep the data formats and their supplibs and their code
> paths in GrADS untangled. The HDF Group is also thinking about developing an
> OPeNDAP client library for HDF5, so that may be another complicating
> factor.
>

Speaking as a user, once an OPeNDAP enabled NetCDF-4 is available I see no
compeling reason for using HDF-5. I am trying to articulate this point
within NASA.

  Thank you for the info!

       Arlindo




> On Feb 4, 2008, at 11:40 AM, Arlindo da Silva wrote:
>
> Jennifer,
>
>   Does the executable "grads" have any feature not covered in "gradsdap"?
> If not, is "grads" really necessary? Sure, nc-dap is bloated, but nc-dap
> should be considered robust enough by now. You could have gone all the way
> and have a single executable called "grads", and only on those platforms
> where OPeNDAP cannot be build we build it with NetCDF. What were your
> thoughts for not having a single executable at this point?
>
>         Arlindo
>
> --
> Arlindo da Silva
> da...@al...
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
>
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
> Opengrads-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opengrads-devel
>
> --===============1190338742==--
>
>
> --
> Jennifer M. Adams
> IGES/COLA
> 4041 Powder Mill Road, Suite 302
> Calverton, MD 20705
> jm...@co...
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Opengrads-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opengrads-devel
>
>


-- 
Arlindo da Silva
da...@al...