grid not working in many cases
Grid will now print out a warning when this scenarios arises.
Grid is not writing adding lat/lon lines to particular files. I think we have nailed it down to files which have longitude domain and then min/max lon values (in the header) in a different lon domain system:
no grid is written if:
(1) lon domain of 180 and a max lon > 180
(2) lon domain of 360 and min lon < 0
These mixed labels are getting generated in map2map so I would recommend either fixing the min/max lons there or allowing grid to handle this case. In the label below, created by map2map, the min/max lons are technically correct but not really valid for the longitude domain. Which is why this might need to be updated in map2map and not necessarily only in grid...? This could also be corrected if grid did not read the min/max longitudes from the label but calculated them from the file (if that is too dangerous then as an optional parameter)?
See zip file for a shell script for example run. This issue is cropping up in Map-a-planet 2 jobs as an issue since folks are moving between lon domains.
Group = Mapping
ProjectionName = SimpleCylindrical
CenterLongitude = 0.0
TargetName = Mars
EquatorialRadius = 3396190.0
PolarRadius = 3376200.0
LatitudeType = Planetocentric
LongitudeDirection = PositiveEast
* LongitudeDomain = 180*
MinimumLatitude = -10
MaximumLatitude = 10
* MinimumLongitude = 160*
* MaximumLongitude = 200*
UpperLeftCornerX = 9483560.688
UpperLeftCornerY = 599663.088
PixelResolution = 7403.248
Scale = 8.0065800204594
I produced a test input image, located at "/work/projects/usertests/UserTestPlans/Apps/grid/m02185/Mars_Viking_MDIM21_Mosaic_TEST_SIMP.cub". The image has a lon. range of 160 to 200 and a lon domain of 180. when grid is run the grid is clipped at longitude > 180. I also tested an image with a similar range but had a lon domain of 360 and a complete grid was produced.