Changes between Version 3 and Version 4 of rfc4_geolocate


Ignore:
Timestamp:
May 29, 2014, 3:50:18 PM (10 years ago)
Author:
etourigny
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • rfc4_geolocate

    v3 v4  
    7777 3. AVHRR: Has 11/51 known locations per-scanline.  These are currently substantially downsampled and returned as GCPs, but this format would be an excellent candidate for treating as geolocation arrays.  Planned in near future.
    7878 4. Envisat: Envisat raw products use geolocation information currently subsampled as GCPs, good candidate for upgrade.   No timetable for update.
    79  5. netCDF: NetCDF files can have differently varying maps in x and y directions (CF conventions two-dimensional coordinate variables) which are represented as geolocation arrays when they are irregular.  See the netcdf driver page for details.
     79 5. netCDF: NetCDF files can have differently varying maps in x and y directions, which are represented as geolocation arrays when they are encoded as CF conventions "two-dimensional coordinate variables".  See the netcdf driver page for details.
    8080 6. OPeNDAP: Can have differently varying maps in x and y directions which could be represented as geolocation arrays when they are irregular.   No timetable for update.
    8181