Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install latest stable QGIS/Python/PyCharm on Linux VM #18

Open
smalers opened this issue Mar 31, 2021 · 0 comments
Open

Install latest stable QGIS/Python/PyCharm on Linux VM #18

smalers opened this issue Mar 31, 2021 · 0 comments
Assignees
Labels
critical Priority: highest priority enhancement S Size: day or less

Comments

@smalers
Copy link
Contributor

smalers commented Mar 31, 2021

The SNODAS linux server needs to run QGIS to do processing. The original work used QGIS 2.17 (I think?) and QGIS is now up to version 3.x. The OWF Learn QGIS documentation describe how to install QGIS on Windows. I'm not sure what the process is for Linux. It would probably be useful to install directly from QGIS download rather than apt-get so that we can rely on QGIS documentation. Below are technical considerations:

  1. For all of this, it would be great to take Markdown notes and screen shots so that we can update README and MkDocs documentation for the current environment. This is really helpful for OWF staff. See the MkDocs developer documentation in this repository.
  2. It may be helpful to archive the old software by creating a top-level folder and creating a new copy. For example, maybe there should be a top-level folder indicating the QGIS version so that it is easy to see the old code parallel to new code. Or, keep the old folder, which we know works as is, and create a new folder for the new work.
  3. Installing the versioned QGIS (meaning the install folder has version number in it - at least that is how it works on WIndows) is desirable rather than the OSGeo version that does not have version in the folder. The documentation mentioned above explains this. That way we can test and deploy different versions and transition easier without clobbering something that is working. We may need to improve how the previous configuration was done.
  4. The GeoProcessor also has installation instructions that get into setup.
  5. We used PyCharm before but OWF staff may not have set up as cleanly as it should be. GeoProcessor uses the same tools so look at that. Basically, we don't want to commit anything to the repo that is dynamic for developers and causes flip-flopping (similar issue to Java workspace/project and Angular). The free community addition can be used. Previous work focused on Windows so need to make sure it installs on Linux.
  6. I can help with TSTool Linux install - the old version should work for this project but there are some changes that need to be done.
  7. Any changes to the environment should ideally be minimal and can use existing scripts. However, if changes are needed, we can discuss.
  8. A part of the update is figuring out how to spin up a new VM, transition everything to that, and shut down the old VM. That way the State only has to pay for one VM. This type of update is going to increasingly be part of what we have to deal with.
@smalers smalers added enhancement critical Priority: highest priority S Size: day or less labels Mar 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
critical Priority: highest priority enhancement S Size: day or less
Projects
None yet
Development

No branches or pull requests

2 participants