---
Hi user_5359,

Thank you for pointing this out.

`sumber` is Indonesian for "source" which our volunteer intended it as attribution note, mean that this is a sub-village (dusun/RT-RW level) boundary from participatory mapping result, delineated together by SIBAT (Indonesian Red Cross village volunteer) as part of EVCA study by PMI Bojonegoro in Mulyorejo village. This is not standard OSM key, should be `source=*` instead.

We will fix this to use the correct standard key. Thank you for the correction.

Halo Mas Fajr, terima kasih banyak atas saran dan masukannya.

Update: kami sudah menghapus seluruh tag non-standar (description:kerentanan dan description:kapasitas) dari semua objek terkait. Data VCA-nya sudah kami pindahkan ke pengelolaan internal terpisah.

Saran soal rekrut GIS specialist dan pakai QGIS/QField untuk data internal sangat kami apresiasi so far masih bisa dihandle internal, Kami juga sudah bergabung di grup Telegram OSM Indonesia.

Terima kasih atas waktu dan masukannya.

Hi user_5359,

Thank you for checking our changeset.

This changeset is from real community mapping activity by our village volunteers from Indonesian Red Cross (PMI SIBAT), using OsmAnd and iD edior in the field to digitize building footprint, land use, public facility, and neighborhood (RT/RW) boundary, as part of Vulnerability and Capacity Assessment (VCA) for disaster risk reduction.

For the two key you mentioned, 'description:kerentanan' (vulnerability) and 'description:kapasitas' (capacity), our volunteer use it to note condition within the location, such as elderly, disability, infant present (kerentanan), and available community resource like midwife, teacher, RT leader (kapasitas).

After we think again, this key is not suitable to be public OSM tag, because it can show personal information of vulnerable people connected to specific household location.

We will not remove it immediately, but change it step by step: first replace to something more neutral and less identifiable, then gradually remove it entirely, while the detail VCA data will be moved to our internal tool (not public, combined per RT/RW level). The other data (building, land use, boundary, facility) will stay, since that part is meant to be permanent.

If you or other mapper have advice how to prevent this in our next field activity, we will appreciate it.

you're right bud! fixed ya...

on special project for mapping Bengkulu?