Project

General

Profile

Bug #2185

grid not working in many cases

Added by Trent Hare about 3 years ago. Updated 4 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Applications
Target version:
Impact:

Grid will now print out a warning when this scenarios arises.

Software Version:
Test Reviewer:

Description

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
or
(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
End_Group
End_Object

gridTest.zip - sample file and script to show issue (2.37 MB) Trent Hare, 2014-10-28 04:37 PM

grid.png View (51.4 KB) Trent Hare, 2014-10-28 04:37 PM

History

#1 Updated by Tammy Becker about 3 years ago

  • Status changed from New to Acknowledged

#3 Updated by Stuart Sides 7 months ago

  • Target version set to 3.5.1 (Sprint 1)

#4 Updated by Makayla Shepherd 7 months ago

  • Assignee set to Robert Sucharski

#5 Updated by Robert Sucharski 7 months ago

  • Status changed from Acknowledged to Testing

#6 Updated by Robert Sucharski 7 months ago

  • Assignee deleted (Robert Sucharski)
  • Test Reviewer set to Robert Sucharski

#7 Updated by Robert Sucharski 7 months ago

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.

#8 Updated by Ian Humphrey 7 months ago

  • Status changed from Testing to Acknowledged
  • Assignee set to Ian Humphrey

#9 Updated by Ian Humphrey 7 months ago

  • Assignee deleted (Ian Humphrey)

#10 Updated by Jesse Mapel 7 months ago

  • Assignee set to Jesse Mapel

#11 Updated by Jesse Mapel 7 months ago

  • Status changed from Acknowledged to In Progress

#12 Updated by Jesse Mapel 7 months ago

A warning message has been added to notify the user when this problem arises.

Available for testing at m02185

#13 Updated by Jesse Mapel 7 months ago

  • Status changed from In Progress to Resolved

An updated version is available for testing. A parameter has been added to extend the grid past the longitude domain boundary.

#14 Updated by Jesse Mapel 7 months ago

  • Impact updated (diff)

#15 Updated by Stuart Sides 5 months ago

  • Target version changed from 3.5.1 (Sprint 1) to 3.5.2 (2017-01-31 Jan)

#16 Updated by Jesse Mapel 5 months ago

The latest version is available for testing on astrovm4 in the latest area. An app test to exercise the new code needs to be added still.

#17 Updated by Jesse Mapel 4 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF