V1.0.0

[thomas-maschler]

Pull request checklist

Please check if your PR fulfills the following requirements:

• [ ] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
• [ ] Make sure you are making a pull request against the develop branch (left side). Also you should start your branch off our develop.
• [ ] Check the commit's or even all commits' message styles matches our requested structure.
• [ ] Check your code additions will fail neither code linting checks nor unit test.

Pull request type

Please check the type of change your PR introduces: - [ ] Bugfix - [x] Feature - [ ] Code style update (formatting, renaming) - [x] Refactoring (no functional changes, no api changes) - [ ] Build related changes - [ ] Documentation content changes - [ ] Other (please describe): ## What is the current behavior?

Issue Number: N/A

What is the new behavior?

• move analysis to subpackages
• rename columns using gfw naming convention
• add additional input feature types

Does this introduce a breaking change?

• [x] Yes
• [ ] No

Other information

[thomas-maschler]

Do not yet merge, still need to validate one more feature

[thomas-maschler]

@jterry64 This is ready for review

In the end I did not test the simple summary stats analysis which gets triggered via ArcPy client. This won't be an issue, since the client is currently pointing to an older version anyways. We can support the client in a later release and make sure, we upgrade the client at the same time.