insarmaps2.0 suggestions summary

[falkamelung]

1. switch form button "Actual pixel size" to slider allowing changing the pixel size (forget abut "actual pixel size". It does not make

2. Button to show the latest ingest and/or window showing the latest 5 ingests. Clicking should activate/show this data set (this is because insarmaps is a research tool to explore data. Originally I thought data, once ingested will not change, but that turned out not to be true. You look at them and then decide whether and how to process differently and/or share with others.)

3. I never used the "Search for ...." tool. It probably can be removed, which frees up screen real estate.

4. A recurrent problem is that we run out of disk space and then things fail without meaningful error message. It would be good to set a limit of e.g 100GB and when 90% is reached to automatically remove the oldest files. Maybe call a function at the beginning of the ingest script that makes sure that after ingestion we don't exceed 90%.

5. when one data set is displayed, there should appear a window with all data sets covering the same bounding box and shown period. Alternatively, draw a box and show all data sets covering this box and period (I am not sure what to do with the current dataset window)

6. the window should have two buttons: (1) to replace the current dataset with the selected datasets (and an easy way to switch back), (2) to open a new browser window showing exactly the same zoom area/period. This needs some logic given that the dates are different: Use the dates following the dates of the first dataset. When for the end date there is no later data use the previous one.

7. Support to display vertical and east-west time periods as the European Ground Motion Service (EGMS). Falk first needs to develop the products first modify save_hdf5eos.py, which will take a while.

8. Show supplementary data for each point as text (elevation, RMSE) similar to EGMS (Later: Falk needs in to include layers in S1*.he5 file.

9. We may want to revisit the blue/red boxes. I have the impress the boxes shown are not always consistent. Why in this case the shown area is different from the box?

   

10. Revisit dataset technical information window (it currently shows unnecessary fields. Remove: CENTER_LINE_UTC, first_frame, last_frame, change order: show last_date after first_date). Remove frame number from title (for Hawaii it dies not need to show 527:)

    

11. Shall we merge insarmaps_scripts and insarmaps into one repo?

12. Let's try to have a defaults/insarmaps_defaults.cfg file to set all parameters instead of hardwiring them in. There should be an option to adjust the defaults without modifying the repo. E.g. parameters found in ~/.insarmapsrc (or ~/.insarmaps.cfg) will be used as found. Somewhere in the codebase we get credentials using import password_config as password, while the password_config.py script contains e.g.

    #For insarmaps and caltech SVN
    insaruser="insaradmin"
    insarpass="insaradmin"

    and is then available in the the script as https://github.com/geodesymiami/rsmas_insar/blob/ec1d421d6e04e7563f9f7cf4bc7d4842cf485761/minsar/create_insarmaps_jobfile.py#L99C61-L100C1

Does it need to be a *py file for this to work? Maybe an insarmaps_defaults.cfg would work?

[falkamelung]

Some more info to provide on the README.md

• for the containers please add something on troubleshooting. E.g. which services/demons need to be running, what commands to check the status and how to solve issues. In particular how can I find out whether to re-run init.sh and run_docker.sh. Use commands like systemctl status docker and sudo docker container ls, sudo service docker restart when appropriate. (systemctl status postgresql should show something only when docker is not used)

• Also say something on whether it should be always running or just when you need it (personally I will use the local version when the internet versions are down, which happened a lot lately).

• What happens to the data when you restart docker? Will they stay or be gone? What is an easy way to remove all data? Remove the insar_website_data dir/file?

• Also for init.sh and run_docker.sh it will be good to have a --help option explaining what the scripts are doing including examples, when running locally and over the internet

• Can data be removed only using the json_mbtiles2insarmaps.py --remove option or also by just removing files in the directories?

• For all insarmaps related files/dirs we better use insarmaps to not confuse with regular Insar data. So insamaps_website_data instead on insar_website_data.

• If you run out of space on the instance, run sudo docker system prune -a to clean out old docker images