Add option to import a fire perimeter and write with output products

[nwagenbrenner]

This feature was requested so that a fire perimeter could be viewed in the same output product (e.g., KMZ, GeoPDF) as the winds without post-processing.

[ksshannon]

Should this be hidden, like a config option, or exposed via the GUI/CLI. If exposed, does the use have to specify the dataset/layer/feature, or just the dataset, or just the dataset/layer?

[nwagenbrenner]

I think it should probably be exposed. Seems like if we can just require that the dataset be specified that would be simplest for the user? Where will this fit in the GUI layout? If a perimeter is supplied is it included in both the KMZ and PDF if they're both written as output?

[ksshannon]

I think that is a good place to start. We can refine as needed.

…

On Wed, Oct 25, 2017 at 10:24 AM, Natalie Wagenbrenner < ***@***.***> wrote: I think it should probably be exposed. Seems like if we can just require that the dataset be specified that would be simplest for the user? Where will this fit in the GUI layout? If a perimeter is supplied is it included in both the KMZ and PDF if they're both written as output? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#170 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAwVDaIdwDJJywjoJCUX-PhaHsOLz3naks5sv2DHgaJpZM4JJcGl> .

-- Kyle