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
It'd be awesome if one could use multiple addresses in the same simulation.
A lot of larger buildings in bigger cities have multiple entrances and thus different house numbers while being still organized by the same entity.
If we could use some special syntax (e.g. [ address1 ; address2 ; address3 ] or even something like Somestreet 3a-9, Somecity or Somestreet {3a, 3b, 5, 7, 9}, Somecity) those Buildings could be simulated all at once which would remove a lot of work for combining reports for separate simulations.
EDIT: Just found out you can double click select multiple buildings and create separate solar panels on each of them. But the calculated report seems to only include the most recent polygon.
The text was updated successfully, but these errors were encountered:
Hi @heeplr, thanks for your issue. You can also double click PV systems to select another system and then generate the report for this system. However by doing so #332 is very annoying and we haven't fixed that yet. And the general UX is a problem as well, since you are definetly not the only person that does not know about the possibility to double klick buildings.
Thanks everyone for this cool project!
It'd be awesome if one could use multiple addresses in the same simulation.
A lot of larger buildings in bigger cities have multiple entrances and thus different house numbers while being still organized by the same entity.
If we could use some special syntax (e.g.
[ address1 ; address2 ; address3 ]
or even something likeSomestreet 3a-9, Somecity
orSomestreet {3a, 3b, 5, 7, 9}, Somecity
) those Buildings could be simulated all at once which would remove a lot of work for combining reports for separate simulations.EDIT: Just found out you can double click select multiple buildings and create separate solar panels on each of them. But the calculated report seems to only include the most recent polygon.
The text was updated successfully, but these errors were encountered: