Closed olafveerman closed 6 years ago
This seems like a very reasonable proposition, however this could be tricky to do for the criticality indicator where the score is calculated from the unroutable pairs and time. Any idea how we'd solve for that one?
We should only add the value if it makes sense, and if it carries any meaning to the user.
The data pipeline currently outputs a scaled score (0-100) for each indicator. This makes it easier to prioritize and generate the final ranking, but a score in itself does not provide meaningful information to the user. I think we should, in addition to the scaled score, provide the option to store the raw value as well. In the case of the poverty indicator for example, the raw value would be the poverty rate of adjacent districts. We're not exposing these values just yet, but including them now in the Vector Tiles will make it easier to do so in the future.
Proposal
The CSV files for each indicator have the following schema:
way_id
- id of the road segmentscore
- scaled score for the indicator (0-100)value
- [OPTIONAL] the raw value for the indicatorThese would be stored on the Vector Tiles as
fishPotentialScore
andfishPotentialValue
.cc @danielfdsilva