Imagery button / deployment workflow improvement

[bzeeb]

Just thought of another helpful administrator change, could we make a new folder called _imagery as a standard folder created along with project.

When the Imagery button is hit it will load/unload any files in this folder (rasters).

Simplifies deployment as that folder will just be completely ignored by the project update, and we no longer have to copy aerials in to the server folders. Also allows site IT staff to easily swap out to the latest aerial without having to jump in to QGIS to update.

[NathanW2]

How should we handle common images between projects? Should we also have a top level _imagery folder?

[NathanW2]

Auto loading these layers is a good idea and really like that.

[Emma-D]

I have created a “shared data” folder which contains the likes of imagery, address, property and roading layers which I use to create the base for all my projects.

From: Nathan Woodrow [mailto:notifications@github.com] Sent: Thursday, 21 January 2016 12:16 p.m. To: DMS-Aus/Roam Roam@noreply.github.com Subject: Re: [Roam] Imagery button / deployment workflow improvement (#316)

How should we handle common images between projects? Should we also have a top level _imagery folder?

— Reply to this email directly or view it on GitHubhttps://github.com/DMS-Aus/Roam/issues/316#issuecomment-173396049.

[NathanW2]

Yeah that is what we normally do too. I guess having something a bit more formal is good so the application knows about it.

[NathanW2]

That does make me wonder if the Roam install folder is the best place for the projects folder. Should it be moved to some place else? as well as roam.config if it's now being used for user settings.

Would allow for this:

• roam --profile {config folder}
• roam --profile {config folder 2}

Config folder:

- roam.config
- _imagery
- _vector_data
- projects
---- etc
---- etc