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
Why this feature is necessary:
Currently, the make-maps command allows the user to select from two technologies (wind and solar), which results in the use of hard-coded legend breaks for the various maps.
@ppinchuk raised the point that this is limiting for other technologies (e.g., geothermal) and, even for wind and solar, the hard-coded legend breaks may not always be suitable for every supply curve.
A possible solution is:
As discussed in PR 38, a possible solution would be to replace the existing --tech option with a --breaks-style option. The user could then choose from a set of options including wind and solar (which would use the existing hard-coded breaks for those technologies) or auto, which would use an automatic classification (e.g., Jenks-Fisher with 5 breaks).
I have considered the following alternatives:
An alternative solution would be to implement the new --breaks-style and enable the user to select any classification from https://pysal.org/mapclassify/api.html#classifiers. The user would have to specify the classifier name (and if applicable, a number of breaks), e.g., --breaks-style fisherjenks:5.
Additional context
NA
Charge code
NA. This is a nice to have at the moment.
Urgency / Timeframe
Not urgent at all.
The text was updated successfully, but these errors were encountered:
Why this feature is necessary:
Currently, the
make-maps
command allows the user to select from two technologies (wind
andsolar
), which results in the use of hard-coded legend breaks for the various maps.@ppinchuk raised the point that this is limiting for other technologies (e.g.,
geothermal
) and, even forwind
andsolar
, the hard-coded legend breaks may not always be suitable for every supply curve.A possible solution is:
As discussed in PR 38, a possible solution would be to replace the existing
--tech
option with a--breaks-style
option. The user could then choose from a set of options includingwind
andsolar
(which would use the existing hard-coded breaks for those technologies) orauto
, which would use an automatic classification (e.g., Jenks-Fisher with 5 breaks).I have considered the following alternatives:
An alternative solution would be to implement the new
--breaks-style
and enable the user to select any classification from https://pysal.org/mapclassify/api.html#classifiers. The user would have to specify the classifier name (and if applicable, a number of breaks), e.g.,--breaks-style fisherjenks:5
.Additional context
NA
Charge code
NA. This is a nice to have at the moment.
Urgency / Timeframe
Not urgent at all.
The text was updated successfully, but these errors were encountered: