You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that the data available in the map has only two digits of precision, instead of the usual three. I feel this is quite irritating as it makes visualizing tiny differences more difficult, especially around numbers near the boundary, such as in this
example:
We can see that they are different values because the percentage of capacity they represent is different.
Was this change on purpose? If so, why was this change implemented? In the case I've posted the difference between possible values is of up to 8% (13.5/12.5), quite significant.
It is possible this was introduced with the change from power to energy units.
Hope all this makes sense, and this issue hasn't been raised before.
The text was updated successfully, but these errors were encountered:
jarek
changed the title
Reduced data precision
Reduced data precision - significant digits on generation by source
Sep 20, 2023
Hi,
Does this issue need to be done? I'm new to this repository and would like to help. I've just had a quick look at the codebase and I think the precision can be easily changed in BreakdownChartTooltip.tsx.
Regards
Does this issue need to be done? I'm new to this repository and would like to help. I've just had a quick look at the codebase and I think the precision can be easily changed in BreakdownChartTooltip.tsx.
Regards
Feel free to take a look at it and open a PR, it's easier to review the suggested changes directly in the code.
Thanks for taking an interest in the repo and project!
Description
I've noticed that the data available in the map has only two digits of precision, instead of the usual three. I feel this is quite irritating as it makes visualizing tiny differences more difficult, especially around numbers near the boundary, such as in this
![Screenshot_20230920_014826](https://private-user-images.githubusercontent.com/84802276/269120406-046d22b4-d84e-44f8-b6b2-afdc71a677c4.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE5NzcxNTgsIm5iZiI6MTcyMTk3Njg1OCwicGF0aCI6Ii84NDgwMjI3Ni8yNjkxMjA0MDYtMDQ2ZDIyYjQtZDg0ZS00NGY4LWI2YjItYWZkYzcxYTY3N2M0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzI2VDA2NTQxOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWVlNjlhODk5NjgwYmYyN2RmZjVmNTQ5ZDBmNzgzM2ZkOTExYzAxNGY4OTU0MzYzYTNmOWVmMzcyOTQwOGRjMGUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.OyqvJhsLaEgydm3xWdDtl2ItW4w0K9JMCO6GYPiNLE0)
![Screenshot_20230920_014845](https://private-user-images.githubusercontent.com/84802276/269120450-e47048ac-b20c-4a43-89ed-2957b71ab087.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE5NzcxNTgsIm5iZiI6MTcyMTk3Njg1OCwicGF0aCI6Ii84NDgwMjI3Ni8yNjkxMjA0NTAtZTQ3MDQ4YWMtYjIwYy00YTQzLTg5ZWQtMjk1N2I3MWFiMDg3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzI2VDA2NTQxOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPThhYjM0NzZlZGFjODVlMjFlYzY3YWY1MjNmY2NkMzNlYmNmOGI5ZjQxMmY5YWE0MzcyM2U0N2UwZTljZjY5NDEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.eRbP0mfHaT3P5hhQqMK9PhWJ25eiQVwoxnSxg4YLBRU)
example:
We can see that they are different values because the percentage of capacity they represent is different.
Was this change on purpose? If so, why was this change implemented? In the case I've posted the difference between possible values is of up to 8% (13.5/12.5), quite significant.
It is possible this was introduced with the change from power to energy units.
Hope all this makes sense, and this issue hasn't been raised before.
The text was updated successfully, but these errors were encountered: