-
Notifications
You must be signed in to change notification settings - Fork 7
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
[ISSUE 3] Inconsistencies with fractions and percentages #82
Comments
@phil-evans replies: i think this is also related to the changes to the rounding rules - this page was initially set up so that the returned data would follow the rounding rules that are created for the indicator in WP, but it seems to have lost that step after we added the new formatting logic. i’ll see if i can find where that’s going wrong |
@phil-evans asks: just to confirm - for all of the ‘probability’ indicators, i should remove the % symbols from the popup and legend? |
@plesueur explains: Follow the units displayed on the side panel. In other words:
|
@phil-evans replies: ok, i believe this is all right now: |
@phil-evans asks: one thing i noticed - the annual economic loss ratio in the sidebar is pulling |
If that's the case I believe we want it to match asset for all, so annual economic loss ratio should b e pointing to eAALm_Asset and not eAALm_Bldg, which in the case for North Vancouver above should be 0.044% @plesueur |
yep, @wkhchow has got it right. Use eAALm_Asset. Good catch @phil-evans |
From @tieganh:
Generally speaking, we need to be consistent with presenting things as fractions or as percentages, and not use the “%” on fractions. The example shown has a hover over value of “0.49%”, but the legend hover over for this shade of red is “44.44+ %“. If we are multiplying legend values by 100 and adding the “%”, then we should do the same for the hover over, detail box, and left hand table. Probably easier at this stage to omit the “%” and change legend values to fractions?
The text was updated successfully, but these errors were encountered: