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.

Sign up for GitHub

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

Jump to bottom

Write few dev notes on how to write impact functions using QGIS native layers #151

Open
assefay opened this issue Feb 25, 2014 · 4 comments
Open

Write few dev notes on how to write impact functions using QGIS native layers #151

assefay opened this issue Feb 25, 2014 · 4 comments

Comments

@assefay
Copy link
Contributor

assefay commented Feb 25, 2014

This is the same idea of the doc we already have on writing impact functions, but geared toward using the qgis native layers instead of safe layers.
assefay added a commit to assefay/inasafe-doc that referenced this issue Feb 28, 2014
@assefay
writing impact functions using qgis api inasafe#151
eb12407
@assefay
Copy link
Contributor Author

assefay commented Feb 28, 2014

@mach0 @timlinux Is it possible to have a quick view on this. The main goal is to give a starting points for people starting as developer in inasafe.

Thx.

@mach0 mach0 self-assigned this Jun 9, 2014
@mach0
Copy link
Contributor

mach0 commented Jun 9, 2014

@assefay
technically it looks ok to me - as this is an old issuer - what about merging it into develop branch and close this issue? -> create a pull request

@mach0
Copy link
Contributor

mach0 commented Jun 23, 2014

@assefay is it ok to close this issue?

@mach0
Copy link
Contributor

mach0 commented Sep 29, 2014

@assefay still open for a pull request .. if @timlinux or @akbargumbira are ok with the content - just create a pull request and I take it into documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mach0 @assefay