Changes between Version 1 and Version 2 of rfc4_geolocate


Ignore:
Timestamp:
May 31, 2013, 3:09:52 AM (11 years ago)
Author:
Markus Neteler
Comment:

note added: more recent NOAA AVHRR datasets have 51 points

Legend:

Unmodified
Added
Removed
Modified

  • rfc4_geolocate

    v1 v2  
    1515geolocation for raw or projected data in this manner, and current approaches
    1616to representing this as very large numbers of GCPs, or greatly subsampling
    17 the geolocation information to provide more reasonable numbres of GCPs are
     17the geolocation information to provide more reasonable numbers of GCPs are
    1818inadequate for many applications.
    1919
    … …  
    5151}}}
    5252
    53 For AVHRR datasets, there are only 11 points, but for every line.  So
     53For AVHRR datasets, there are only 11 points (note, the more recent NOAA AVHRR
     54datasets have 51 points), but for every line.  So
    5455the result for a LAC dataset might look like:
    5556
    … …  
    7273
    7374
    74  1. HDF4: Client needs mandate immediate incorporation of geolocation array support in the HDF4 driver (specifially for swath products).  (complete)
     75 1. HDF4: Client needs mandate immediate incorporation of geolocation array support in the HDF4 driver (specifically for swath products).  (complete)
    7576 2. HDF5: Some HDF5 products include geolocation information that should be handled as arrays.  No timetable for update.
    76  3. AVHRR: Has 11 known location per-scanline.  These are currently substantially downsampled and returned as GCPs, but this format would be an excellent canidate for treating as geolocation arrays.  Planned in near future.
     77 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.
    7778 4. Envisat: Envisat raw products use geolocation information currently subsampled as GCPs, good candidate for upgrade.   No timetable for update.
    7879 5. netCDF: NetCDF files 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.