Project

General

Profile

Bug #1250

qnet - editing ground points using a positive longitude direction=west

Added by Tammy Becker about 6 years ago. Updated 12 days ago.

Status:
Acknowledged
Priority:
Normal
Assignee:
-
Category:
Applications
Target version:
-
Impact:
Software Version:
Test Reviewer:

Description

Ella and I had to walk through a mystery and now we think we understand what is going on.

1) Cassini RADAR mosaic products are generated in longtiude_direction=west and longitude system=360

2) We are using these RADAR mosaics for the 'ground source' in qnet to tie Cassini ISS level1 images.

3) When creating a new ground point, once a point is selected as constrainted, and the Radar mosaic loaded as ground source; qnet seems to read the west longitude direction value of the map and converts to 'east'...the user can select the ground point, saves the point and network.

4)When this network with the ground source point is 'reloaded' into a new qnet session, with the same ground source loaded...qnet does not 're-convert' the saved converted west->east longitude back to west in order to find it on the original ground source. The user must separately remap the ground source file to positive longitude direction to 'east'...load this version of ground source into qnet in order to see/edit the existing ground points.

5) We haven't gone through the exercise to see if the incoming longitude domain gets converted from 180 to 360 and will cause the same editing problem (luckily the radar is in 360; consistent with isis3), ...it's worth looking into.

History

#1 Updated by Tammy Becker about 6 years ago

Triaged at moderate level for now; there is a work around with remapping ground to positive direction=east.

This should be considered an important detail for any new development in the control suite.

Improved documentation might suffice with the current qnet based on tight resources.

#3 Updated by Anonymous about 5 years ago

  • Target version deleted (150)

#7 Updated by Moses Milazzo over 3 years ago

Moving this from FY15Q1 to FY15Q3. Hopefully it can be addressed while also addressing other qnet issues.

#8 Updated by Stuart Sides over 3 years ago

  • Target version set to 3.4.10 (FY15 R3 2015-07-23 Jul)

#9 Updated by Stuart Sides about 1 year ago

  • Target version deleted (3.4.10 (FY15 R3 2015-07-23 Jul))

Also available in: Atom PDF