fix for issue #6, hopefully it doesnt affect the expected behavior in other cases, now we assume that the lat/lon coords are definitive coords if both x/y and lat/lon are recognized in the file, which fixes this case because netcdf-java doesn't have the appropriate information to project x/y to lat/lon like it is expected to