Skip to content
This repository has been archived by the owner on May 18, 2022. It is now read-only.

Improving the GUI #67

Open
kvos opened this issue Feb 6, 2018 · 3 comments
Open

Improving the GUI #67

kvos opened this issue Feb 6, 2018 · 3 comments
Assignees

Comments

@kvos
Copy link
Contributor

kvos commented Feb 6, 2018

Hi all,

As discussed with @KateBrodie @SRHarrison and Brittany last week, I will be helping to improve the GUI in view of the CIRN bootcamp.

Here are the first 2 improvements that were suggested:

  1. Intrinsic camera parameters
    1a. Populating the popup menu with the different cameras from the script makeLCPP3.m
    1b. Being able to set a custom camera and input the intrinsic camera parameters directly on the GUI, without having to edit makeLCPP3.m.

  2. Coordinate conversion: the GUI uses SuperTrans (from OpenEarth tools) to convert GPS coordinates (WGS84) from the image metadata into a user-defined coordinate system (the one used to survey the GCPs). SuperTrans uses the EPSG Geodetic Parameter Registry, which contains most coordinate systems but misses a few (for example NAD83 / North Carolina). It was therefore decided to give the user the option to enter all the inputs (GCPs and camera extrinsic parameters) in his local Argus coordinates
    2a. Add an option where the user can enter the inputs in local Argus coordinates.

This channel is here to discuss the changes and propose further improvements.

@SRHarrison
Copy link

Thanks @kvos.
Can you clarify: did you already make those additions to your branch or is this note just for discussion at this point?

@kvos
Copy link
Contributor Author

kvos commented Feb 6, 2018

it's just for discussion.

but I've done changes 1a and 1b.
In the intrinsic camera parameters panel (tab 2), there is an option for "custom" camera. The user can then input the lens calib parameters and proceed to the next step.
In case the user wants to save the custom camera, the button "save" allows to save the camera intrinsic parameters in a mat file. In a successive run, the saved custom camera can be loaded with the "load" button.

change1

@kvos
Copy link
Contributor Author

kvos commented Feb 9, 2018

I also made change 2a.
I added in the inputs structure a field inputs.localCoords that can be activated (0 or 1) on the GUI by ticking the checkbox Local in the rectification settings (see screenshot below).
When inputs.localCoords = 1, the user has to provide:

  • the GCPs in local Argus coordinates
  • the camera extrinsic parameters also in local Argus coordinates (hard!)

capture

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants