{"action":"opened","issue":{"url":"https://api.github.com/repos/opticks-org/opticks/issues/118","repository_url":"https://api.github.com/repos/opticks-org/opticks","labels_url":"https://api.github.com/repos/opticks-org/opticks/issues/118/labels{/name}","comments_url":"https://api.github.com/repos/opticks-org/opticks/issues/118/comments","events_url":"https://api.github.com/repos/opticks-org/opticks/issues/118/events","html_url":"https://github.com/opticks-org/opticks/issues/118","id":306017801,"number":118,"title":"OPTICKS-445 - Add capability to position layers in a view according to geocoordinates","user":{"login":"tclarke","id":8740,"avatar_url":"https://avatars0.githubusercontent.com/u/8740?v=4","gravatar_id":"","url":"https://api.github.com/users/tclarke","html_url":"https://github.com/tclarke","followers_url":"https://api.github.com/users/tclarke/followers","following_url":"https://api.github.com/users/tclarke/following{/other_user}","gists_url":"https://api.github.com/users/tclarke/gists{/gist_id}","starred_url":"https://api.github.com/users/tclarke/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tclarke/subscriptions","organizations_url":"https://api.github.com/users/tclarke/orgs","repos_url":"https://api.github.com/users/tclarke/repos","events_url":"https://api.github.com/users/tclarke/events{/privacy}","received_events_url":"https://api.github.com/users/tclarke/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-16T17:39:15Z","updated_at":"2018-03-16T17:39:15Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Layers in a view are currently positioned according to pixel coordinates referenced from a primary raster layer. Since multiple raster layers may be available, it would be helpful to position layers based on geocoordinates instead of pixel coordinates relative to another layer.\n\nOriginal Issue: [OPTICKS-445](https://issues.opticks.org/jira/browse/OPTICKS-445)\nStatus: Deferred\nFeature Interpretation:\nThis new feature will include the following capabilities:\n \n View\n - Allow users to import multiple data sets into a single view.\n - Allow a single view to be pixel-coordinate based where layers are positioned based on a common origin, or geocoordinate based where layers are positioned according to latitude/longitude (if available).\n - Enhance support for 3D elevation/terrain data such that layers have access to the data to draw in three dimensions. This does not include the capability to draw the layers in three dimensions.\n - Add support for multiple projections.\n - Add support for multiple ellipsoid models.\n \n Layer\n - Allow each raster layer to specify its own texture mode.\n\nSuggested Solution:\nTo allow for the creation of a view with a geo coordinate system, the concept of a dataset object will be introduced to contain multiple data elements and attributes that apply to all elements, such as elevation data. This allows multiple raster elements in a single file or multiple files to be contained within a single object, and thereby eliminates the previous concept of a primary raster element in a view. The dataset object will be the container to store and manage all objects that will be displayed in two new views that will replace the existing spatial data view.\n \n To display the contents of a dataset in a single view, the current spatial data view will be replaced with two separate views: a geo view and a spatial view. The geo view will have an underlying latitude/longitude coordinate system, where the data will be positioned based on geocoordinates. The spatial view will have an underlying pixel coordinate system, where the data will be positioned based on pixel coordinates relative to an origin. The geo view will also contain support for multiple projections and ellipsoid models.\n \n To position layers generically in a view, a new coordinate object will be added, containing x-y-z values along with height units. All layers will be updated to store coordinate locations with the new object independent of units, so that the layer can be displayed in either a geo view or spatial view without specialization in the layer.\n \n Elevation data will be supported through the use of a new terrain element, contained in a dataset, that stores elevation data for the entire dataset. Importing elevation data will then import the data into the terrain element instead of a separate raster element. The existing DTED importer will be updated to use the new terrain element.\n \n Capability will be added to the Data tab of the import options dialog to allow the user to specify a new or existing dataset to contain the imported data, which will allow users to import raster data and other data elements from multiple files into a single dataset and view. A new Datasets tab will be added to the Session Explorer that displays all loaded datasets along with the elements contained in the dataset.\n \n The smoothing capability currently in the spatial data view will be moved to the raster layer, allowing individual raster layers to set their own texture mode.\n\nActual Solution:\n\n\nSeverity: \nVersion Control: \nEnvironment: \nLinked: \n"}}
{"actor":{"display_login":"tclarke"}}