iMMAP / DRR-datacenter

GNU General Public License v3.0
0 stars 3 forks source link

Couldn't download the Interactive Map to PDF #1

Closed rafinkanisa closed 2 years ago

rafinkanisa commented 2 years ago

When I try to to download the interactive map with the dashboard, it returns [Object Object]

Link : http://asdc.immap.org/maps/5568/view

Screen Shot 2021-12-10 at 10 54 04

Kindly identify the issue and fix

sud0su commented 2 years ago

hi @rafinkanisa , the map can't be downloaded, it happened not because of a code error but because there are two layers (Mean Sea Level Pressure (gfs-msl-pressure) & Surface Weather Observations (METAR)) from ogcie.iblsoft.com that don't have map legend graphics. i have been discussed with @dodiws , and we think the best option we can do is just two options :

  1. unselect the layers (Mean Sea Level Pressure (gfs-msl-pressure) & Surface Weather Observations (METAR)) before print
  2. make a contact with ogcie.iblsoft.com and ask why the layers (Mean Sea Level Pressure (gfs-msl-pressure) & Surface Weather Observations (METAR)) did not have a legend
rafinkanisa commented 2 years ago

Can't we show more useful error message like saying, please unselect the layer?

sud0su commented 2 years ago

Can't we show more useful error message like saying, please unselect the layer?

I will try to dev and do a test on my local machine first to make sure is it possible or not, because the update code will be affected to all interactive map

rafinkanisa commented 2 years ago

alright. I'll be waiting for the updates then

sud0su commented 2 years ago

alright. I'll be waiting for the updates then

still can't display the popup message to uncheck the specific layers(the error layer), this bug needs more time to debug and develop because these changes will have an impact on all print processes in the interactive map.

dodiws commented 2 years ago

this commit show error message with workaround suggestions when print fail on interactive map because of GetLegendGraphic error

error message with workaround suggestions