Inconsistent longitude range in main subroutine

[ibanos90]

I noted that the longitude range in IODAv1 output files for ABI and AHI is from 0 to 360, however, for AHI HSD data there is a check for this that converts to -180 to 180. Also, for the NetCDF AHI data and other L2 products I convert to -180 to 180.

After offline conversation with @byoung-joo, he showed me that the final latitude/longitude that goes into the files is from MPAS and there seems to be some inconsistency with this regard in the main.f90 subroutine.
We write out lat_mpas and lon_mpas:

      call output_iodav1_o2m(trim(out_fname), scan_time, nC, 10, l_got_latlon(:), &
                             lat_mpas(:), lon_mpas(:), gzen(:), solzen(:), &
                             transpose(field_mpas), transpose(field_mpas_std) )  ! field_mpas(nC,nfield)

But we read this variable before, put it in double precision arrays and convert to -180 to 180:

   call read_mpas_latlon (f_mpas_latlon, nC, lon_mpas, lat_mpas, bdymask_mpas)  ! unit [radian], single precision
   lon_mpas_dp=lon_mpas ! pass double precision for kd-tree
   lat_mpas_dp=lat_mpas
   do iC=1,nC
      ! convert lon range [0,360] --> [-180, 180] to match with lon_s
      if(lon_mpas_dp(iC).gt.pi) lon_mpas_dp(iC)=lon_mpas_dp(iC)-2.d0*pi
   end do

This issue is to highlight this and give it a thought as we may want some consistency on this procedure.