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

Zurich #3

Open
matthewberryman opened this issue Nov 23, 2016 · 1 comment
Open

Zurich #3

matthewberryman opened this issue Nov 23, 2016 · 1 comment
Assignees

Comments

@matthewberryman
Copy link

As per
urbanriskmap/riskmap#32
I would suggest we go straight to a scheduled lambda function rather than putting it in as part of reports, however. I guess for that, and for transforming qlue, etc. down the track, have them still as submodules of this reports master repo, and then this repo can package them (ala https://github.com/urbanriskmap/aws-lambda-image/blob/master/Makefile ) and document them? Leaving the powertrack as the odd one out.

@tomasholderness
Copy link

Agreed. I will start work on this soon -> NB. this is lower priority data source at the current time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants