lrolola2isis
Imports LIDAR data from LRO LOLA instrument.
Imports LIDAR data from LRO LOLA instrument.
Categories
History
Makayla Shepherd and Tyler Wilson | 2017-01-29 | Original version |
Debbie Cook | 2018-03-19 | Added items that will be needed to bundle adjust: new point keyword simultaneousImages that is an array of serial numbers of the measures on images taken simultaneously with the Lidar data, a threshold to screen measures that are off the image, and both point (lat/lon/radius) and range constraints. Also added point type and set it to Constrained. |
Debbie Cook | 2018-04-16 | Fixed the case where a Lidar point has no simultaneous measures on any images in the input list. In this case do not write out the point because it has no constraints. In the future, the functionality may change to include points without simultaneous measures in the bundle adjustment. References #5343. |
Ken Edmundson | 2018-06-20 | Changed call to Camera::SetGround to use the SurfacePoint with the input lidar point coordinates. Ensures use of lidar point radius instead of the local radius. |
Ken Edmundson | 2018-06-25 | Changed internal default for lidar coordinate a priori uncertainties to "none", allowing FREE lidar points. |
Debbie A Cook | 2019-02-23 | Added new file OUTPUTTYPE=TEST, to be used strictly for testing. This option does a SLOW sort on the output data. The resulting output file is sorted by pointID, which allows testing software to compare output with truth data. References #5343. |
Debbie A Cook | 2019-03-11 | Added new input parameter FROMLIST to allow entering multiple input Lidar CSV files. All input points are written out into a single Lidar data file. References #5343. |
Parameters
Files
Type | filename |
---|---|
File Mode | input |
Exclusions |
|
Filter | *.csv |
Type | filename |
---|---|
File Mode | input |
Internal Default | None |
Exclusions |
|
Filter | *.lis |
Type | filename |
---|---|
File Mode | input |
Filter | *.lis |
Type | filename |
---|---|
File Mode | output |
Type | string | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Default | BINARY | ||||||||||||
Option List: |
|
Processing Parameters
This string will be used to create unique IDs for each control point created by this program. The string must contain a single series of question marks ("?"). For example: "VallesMarineris????"
The question marks will be replaced with a number beginning with zero and incremented by one each time a new control point is created. The example above would cause the first control point to have an ID of "VallesMarineris0000", the second ID would be "VallesMarineris0001" and so on. The maximum number of new control points for this example would be 10000 with the final ID being "VallesMarineris9999".
Note: Make sure there are enough "?"s for all the control points that might be created during this run. If all the possible point IDs are exhausted the program will exit with an error, and will not produce an output control network file.
Examples of POINTID:
- POINTID="JohnDoe?????"
- POINTID="Quad1_????>
- POINTID="JD_???_test1"
Type | string |
---|
This value is used to screen measures during back projection. If a Lidar point maps into an image with coordinates outside of the valid pixel range extended by the threshold value, it will be rejected as a measure for that point.
Type | double |
---|---|
Default | 0.0 |
Minimum | 0 (inclusive) |
Point Uncertainties
Type | double |
---|---|
Internal Default | none |
Minimum | 0 (inclusive) |
Type | double |
---|---|
Internal Default | none |
Minimum | 0 (inclusive) |
Type | double |
---|---|
Internal Default | none |
Minimum | 0 (inclusive) |
Type | double |
---|---|
Internal Default | none |
Minimum | 0 (inclusive) |