h4h5tools

When check_field_existence() checks whether or not the field is reachable with HDF-EOS2 API, it didn't search Geo-location fields. So, if "Longitude" that resides in Geo-location fields was inquired, this function wrongly said that "Longitude" doesn't exists.

This problem resulted in saying "_FV_Latitude" is neither HDF-EOS2 attribute nor HDF-EOS2 field. "_FV_Latitude" is not reachable by HDF-EOS2 API, but this does not always mean a failure because inserting "_FV_" is the way HDF-EOS2 puts an attribute for "Latitude". In this case, h4toh5 checks whether or not "Latitude" exists to distinguish the convention from the accidental match.

Because of the bug, h4toh5 couldn't find "Latitude", and "_FV_Latitude" is not an attribute attached to "Latitude", which gave the false alarm. This changelist will let h4toh5 recognize "_FV_Latitude" as an attribute attached to "Latitude".