Closed kellpossible closed 6 months ago
We're planning to move to using our own hazard map #39, and in the interim the manually generated hazard map is not being used, so this change is no longer required.
I was actually wondering the other day if we should bring back the interim map I had?
On 2024-01-27 12:31, Luke Frisken wrote:
We're planning to move to using our own hazard map #39 [1], and in the interim the manually generated hazard map is not being used, so this change is no longer required.
-- Reply to this email directly, view it on GitHub [2], or unsubscribe [3]. You are receiving this because you were assigned.Message ID: @.***>
[1] https://github.com/kellpossible/avalanche-report/issues/39 [2] https://github.com/kellpossible/avalanche-report/issues/19#issuecomment-1913142993 [3] https://github.com/notifications/unsubscribe-auth/AH7NZQDCAUNKIWCV7WSHA5LYQTXRDAVCNFSM6AAAAAAU5PT5GGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJTGE2DEOJZGM
@PSAvalancheConsulting if you'd like to continue doing so, let me know. I think a simpler solution than this could be to only display the hazard map for the current forecast so we could continue doing it how we were before.
Although that may involve rendering multiple maps, which I'd like to avoid and just have them all combined in one interface with a layer selection dialog. Perhaps we could instead host the hazard layer separately and insert it into the current map, that may also not be too much work.
Would it not be possible to just insert a window that links to the website where the hazard map lives? That link is permanent.
On 2024-01-28 11:51, Luke Frisken wrote:
Although that may involve rendering multiple maps, which I'd like to avoid and just have them all combined in one interface with a layer selection dialog. Perhaps we could instead host the hazard layer separately and insert it into the current map, that may also not be too much work.
-- Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. You are receiving this because you were mentioned.Message ID: @.***>
[1] https://github.com/kellpossible/avalanche-report/issues/19#issuecomment-1913569786 [2] https://github.com/notifications/unsubscribe-auth/AH7NZQBQYEB7INBNBB7UUNDYQY3VDAVCNFSM6AAAAAAU5PT5GGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJTGU3DSNZYGY
@PSAvalancheConsulting we can do that on the home page I guess similar to what we did last season if you're happy to update it for every forecast, I can work on that tonight. Doing it on the forecast pages means that it won't remain in sync with the forecast on the page if someone goes back and looks in the archive.
Currently hazard map has a fixed name, so it can fall out of sync with the current forecast. I propose we use a naming scheme like:
https://psavalancheconsulting.github.io/hazard-map/Gudauri_2023-02-12T20:00_LS.html
. We may need to use url encoding for the:
, so it would look likeGudauri_2023-02-12T20%3A00_LS.html
Using this scheme will allow us to quickly/easily hook into the existing scheme for representing forecast files.