以為飲水地圖計畫已經停止了? slayer

so true…

Dear Andy and Community,

We know it’s very important about the data quality on OSM. We’ve done the following fixes. Due to the field drill that we currently working in Bangladesh, GeoThings will publish this update to Play Market next Monday.

1. Added geoMapTool and its version into changeset created_by tag
2. Fixed the timeout issue during OSM data submission in low-network scenario
3. Disabled the new objects creating bar in UI

Will have further discussion with international consultant team for the data clean up event.

Have a good day! slayer

Dear Andy,

Thank you so much for listing the issues with details, we mark all of those as issue as our to-do and response in detail below:

(1) for the created_by, yes we know it should be geoMapTool. We missed this part in training material so the local mappers filled the tag according to the understanding of “created_by”. We will make geoMapTool to auto-complete this tag, and later clean it up on OSM with users.

(2) After several field mapping, we found that it’s not easy for unexperienced mapper to leverage polygon drawing. As we mentioned that we will have the data clean up event, we also thinking about to dismiss the polygon drawing feature in geoMapTool (or make it as the advance feature that need to be ON in menu/setting). And update the training material to focus on mapping with iD, and use geoMapTool only for updating detail tags.

(3) About the name of addr:housename is/are tagged as “house”, we will sync with our consultant and update the training material. Also will/should be clean up during the later event.

(4) We discussed with the disaster experts to know about what information should be provided for the disaster response and the evacuation planning. So we of course followed the tags that OSM community already had, then came up with the tags that are needed for the disaster scenario. After the drills with local community/government, we will know better about the work flow of response to disaster in those countries, and certainly will file/issue these tag as proposal to the OSM community.

Have a good day! slayer

Dear Andy, indeed we appreciated your efforts and comments very much.

We are currently working in a capacity building project with local community. The idea is to start from mapping with iD, validation with geoMapTool in the field, collect environment capacity & vulnerability with crowdsource tool (geoBingAn), then perform the drill with local community/government. I am the one who should be responsible for this mess, my apologize for not planned well in advance and the bugs of our tool that generated duplications and mess up the OSM data.

Since it’s a capacity building project, we work with international disaster experts to train the local community as seed trainers for disaster resilience. Instead of the data clean up by experienced mappers, we are now arranging the data clean up event/webinar, so the local community (mappers) will know why it’s no good for OSM, and know how to clean it up. This might be the fundamental idea that we can share with local community, and prevent further mess up in that area.

For the geoMapTool, we’ve done the quick fix for the app. We see some of the local mappers didn’t update yet, that might cause the duplication issue again, yet we will still keep the conversation with them, to prevent the further issue, and will together do the data clean up asap.

My sincere apologize for the inconvenience we made, because the coming national level drill in Bangladesh, we can’t response and arrange well to this issue in the short time. We will certainly clean it up, and we thank you for your time and efforts on this.

Have a good day! slayer

ICT stands for Information and Communication Technology. I think the most known case will be our smart phone, which handles information (via app) and provides the voice/data communication with the technology that available to people. To build something that make this technology better leveraged for humanitarian activity, we call it “Humanitarian ICT” :-)