If the data is read by the SeaDAS reader the geo-location is wrong if scene crosses dateline. This is caused by not constructing the longitude tie-point-grid with the DISCONT_AT_180 option
The geo-location of a subset is totally wrong in certain cases. This can be best seen when using as subset_region covering only the right part of the scene (full hight).
See definition of subset.See resulting geo-location (red shape is the subset)
Below is a list of questions to be addressed as a result of this requirements document: