[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[netCDF #IGD-438207]: degrees minutes and seconds

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.

  • Subject: [netCDF #IGD-438207]: degrees minutes and seconds
  • Date: Tue, 10 Feb 2009 17:14:34 -0700
> Hello Ed
>
> thank you for getting back to me
>
> i appreciate the value of cf conventions and i'm not trying to sidestep
> them on a whim, i'd like to stick with them, but i am yet to find a
> solution to the problem i working on
>
> i am investigating an issue with importing netcdf files into some
> propriatory software, which requires that all the grid points have equal
> spacing along an axis
>
> however for some input files the latitude and longitude values suffer
> from floating point inaccuracies due to their base 10 nature and the
> small size of the spacing. although theses differences are tiny they are
> enough for the software to return errors rather than importing the data
>
> for example a grid point spacing of 0.1 degrees fails to import as the
> points are deemed unequally spaced
>
> i am investigating using deg/min/sec as a way to force the generated
> grids of data onto a controlled regular pattern.  for this to work the
> dimension data would need to be stored as degrees/minutes/seconds
>
> i have looked at conversion as you have suggested and this also exhibits
> the floating point inaccuracies that i have described. i am receiving
> data as decimal degrees and converting it to deg/min/sec to try and
> sidestep this issue, hence why i'd be interested in how to go about
> coding the values of the dimensions within the netcdf file
>
> i am continuing to investigate courses of action so it would be useful
> for me to either establish that a deg/min/sec approach is plausible or
> rule it out
>
> if you've any further advice for me i'd appreciate your thoughts
>
> much obliged
>
> mark
>
> Mark Hedley, Software Developer
> Met Office FitzRoy Road Exeter Devon EX1 3PB United Kingdom
> Tel: +44 (0)1392 884482
> Email: address@hidden Website: www.metoffice.gov.uk
>

Howdy Mark!

Have you had any luck coming up with degree/minute/second conventions? I have
not found any...

Thanks,

Ed

Ticket Details
===================
Ticket ID: IGD-438207
Department: Support netCDF
Priority: Critical
Status: Closed