-
Notifications
You must be signed in to change notification settings - Fork 2
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
Factor: Water Sanitation - Water points (OSM), catch basins, water valves and fire hydrants (Mapillary) #48
Comments
NOTE: I believe the original name of the factor was Access to Water and Sanitation; however, this should be changed to Water and Sanitation. As mentioned in the original instructions, the scores are assigned by dividing the country territory into 100x100m raster cells. If the cell contains point features such as water points, catch basins, water valves, or fire hydrants, scores are assigned as follows: Raster cell with no water points: score 0 |
Result: |
@osundwajeff @mvmaltitz @javaftw |
@dragosgontariu |
hi colleagues, as you know, we have processed all the PC factors manually for the conference this week, to ensure timely results. In this process we noticed that the current computation of this factor is not ideal. What we decided is to measure access using buffers, assuming that if a feature exists, more likely access exists in the area, even if the data is not recorded. Could you kindly make these adjustments to the factor computation, and the descriptive text? Thank you |
@ClaraIV |
Water process failed. The label next to Execute button appear with text
And trigger a Python error below
And the Processing log below
|
This indicator is composed by assessing the presence of any of these four factors in a raster cell. First, the territory needs to be divided into 100m x 100m rasters. The scoring for each cell is as follows:
Raster cell with no water points: score 0
Raster cell with 1 water point: score 3
Raster cell with 2 or more water points: score 5
If from OSM:
If from Mapilliary:
The text was updated successfully, but these errors were encountered: