John,
On 07/11/2011 03:12 PM, John Caron wrote:
2) Allowing lat/lon to live in another file. Clearly this is needed to
support what gridspec is doing.
IMO the use case for 1) is using netcdf as an exchange format, esp
for subsetting large datasets, eg the netcdf subset service. The user
needs to have the option of leaving the lat/lon out. The use case for
2) is large archives of data - where you can rely on the files staying
together, and even being able to use absolute paths (BTW - did the
spec get changed to allow reletive paths?).
Yes relative path are ok. From the wiki...:
The listed file names may include a directory name (a path). The
standard does not specify the directory separator character to be used,
that is whether "/" (Unix) or "\" (Windows) should be used. The file
name must be a valid file name on the platform where the host file
resides. If the file name contains a directory base name then care
should be taken to convert the string to the appropriate directory
separator if the files are moved to another platform.
The location of files can be absolute or relative to the location of the
host file. In the former case, the host file can be moved without
breaking the aggregation. In the latter case, both host and other files
can be moved to a different system/location provided the relative path
of each file is preserved.
--Alex
_______________________________________________
CF-metadata mailing list
[email protected]
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
