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

Landcover Classification #3947

Closed
ivanbusthomi opened this issue Feb 27, 2017 · 6 comments
Closed

Landcover Classification #3947

ivanbusthomi opened this issue Feb 27, 2017 · 6 comments

Comments

@ivanbusthomi
Copy link
Contributor

@ivanbusthomi ivanbusthomi commented Feb 27, 2017

Problem

We need to make the classification for landcover exposure match with the volcanic ash landcover classification. The landcover classification came from Badan Geologi.
lc
We might also need to automatically assign the value map from BIG landcover data to the classes because the value in BIG land cover data has already been standardised using either the Remark Field or the FCODE field.
image

Expected Behaviour

the landcover classification matches the Badan Geologi classification.

Environment

  • InaSAFE :
  • QGIS :
  • OS :
  • Data used (filenames and paths so as to reproduce, a project is better):
    • Exposure :
    • Hazard :
    • Aggregation :
    • Extent :

Proposed Solution

Maybe by adding new land cover classification. This is the volcanic ash landcover classification and the value map for BIG land cover data

Value Map Remark FCODE
Settlement Permukiman dan Tempat Kegiatan 50102
Rice Field Sawah 50306
Plantation Perkebunan / Kebun 50304
Water Supply Air Danau / Situ, Air Empang, Air Penggaraman, Air Tambak, Air Tawar Sungai, Air Waduk, Perairan Lainnya 50404, 50420, 50418, 50416, 50408, 50406, 50400
Forest Hutan Rimba 50202
@Gustry
Copy link
Contributor

@Gustry Gustry commented Mar 1, 2017

I put the label release blocker because I though it was. If it's not, you can remove it. Should we go with this classification ? Should we remove the old one ?

Loading

@ivanbusthomi
Copy link
Contributor Author

@ivanbusthomi ivanbusthomi commented Mar 2, 2017

Hi @Gustry,
I am thinking maybe we can just add another classification for BIG landcover, and make it automatically value mapped if using the remark or FCODE field based on the table above.
And I believe it is not a release blocker. What do you think @Charlotte-Morgan ?

Loading

@Gustry
Copy link
Contributor

@Gustry Gustry commented Mar 2, 2017

Yes, good.
Do you want to do it @ivanbusthomi ?
You need to add new classification here : https://github.com/inasafe/inasafe/blob/develop/safe/definitions/exposure_classifications.py
(CC @myarjunar )

Loading

@Gustry
Copy link
Contributor

@Gustry Gustry commented Mar 2, 2017

Check #3626

Loading

@myarjunar
Copy link
Collaborator

@myarjunar myarjunar commented Mar 3, 2017

is it ok if I named it badan_geologi_landcover_classes? @ivanbusthomi @Gustry

Loading

@ivanbusthomi
Copy link
Contributor Author

@ivanbusthomi ivanbusthomi commented Mar 3, 2017

@myarjunar yeah I think so.

Loading

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

Successfully merging a pull request may close this issue.

None yet
3 participants