Please update all ZAMG hazard resources #41
Comments
|
Yesterday, @RobAndGo found a bug in cloning of the resources. I was able to fix this by allowing the reuse of references. References rarely (never?) need to be reused, but it's possible to do so now. |
|
All the hazard indices that were uploaded to /clarityftp/europe/hazard_indices/heat/ (ATOS FTP) were included in our geoserver back in July. For more information check issue #19 They can be accessed at https://clarity.meteogrid.com/geoserver and follow a naming convention containing europe (europe:HI_HotDays_rcp26_20110101-20401231_ensmean). The indices related to floods are still pending of some lingering questions that are already stated in the issue already mentioned. |
|
I have uploaded datasets for the hazard indices to the clarity-ftp. Speficially, I have done the following: - updated the following indices to remove the incorrect data around some of the coastlines: - updated the Tx75p index stored in - added the new indices |
|
Status of the layers: updated the following indices to remove the incorrect data around some of the coastlines:
updated the Tx75p index stored in
added the new indices
|
|
Regarding the layers available at /clarityftp/europe/hazard_indices/heat/hotdays-75thpercentile. I've removed the old ones from geoserver to avoid confusion with the new ones. The new layers can be found in the Layer Preview: https://clarity.meteogrid.com/geoserver/web/wicket/bookmarkable/org.geoserver.web.demo.MapPreviewPage?229 HI_Tx75p_consecutive_max_rcp26_20110101-20401231_ensstd / @RobAndGo let me know if there's something missing/wrong |
|
Thank you @ghilbrae!! The datasets all look good! I have spotted one problem with the consecutive-frostdays historical dataset, but that problem is from me and not from you. I will upload the new version of this file sometime today. In the meantime, I have uploaded the following new datasets: /clarityftp/europe/hazard_indices/cold/Tn10p /clarityftp/europe/hazard_indices/precipitation/consecutive-wetdays Here is another index which I forgot to include originally: |
|
Done with the previous batch of layers. New datasets progress:
|
|
In the directory: /clarityftp/europe/hazard_indices/cold/consecutive-frostdays I have updated the consecutive-frostdays historical dataset files: ConsecutiveFrostDays_historical_19710101-20001231_ensmean.nc They now show the correct data. As mentioned earlier, the other data files showing the future RCP scenarios were correct and do not need to be changed. In the directory: /clarityftp/europe/hazard_indices/cold/frostdays I have also updated the historical dataset files: FrostDays_historical_19710101-20001231_ensmean.nc |
|
@RobAndGo I've updated the four historical files. From the new files you updated I've only had time to add one set, as you can see above. I'll let everything prepared, in case one of my colleagues can add them later. @luis-meteogrid @LauraMTG are the ones that will continue with this task. |
|
ATM none of the HC Resources in the European Data Packages is working in the Map Component.
You can test the layers here: Note: You have to be logged-in in CSIS in the same browser. |
|
The URL is not correct, check this one: There are "-" where there should be "_". |
|
Urls in the data package are correct, as we defined them when we met at METEOGRID office and this has been like that for weeks (before leaving for vacations it worked). As it is shown in the original link in the data package resource: https://clarity.meteogrid.com/geoserver/wms?service=WMS&version=1.1.0&request=GetMap&layers=europe:HI_Tx75p-consecutive-max_historical_19710101-20001231&bbox=2145500,982500,6606000,57065000&width=725&height=768&srs=EPSG:3035&format=image/png Did the layers name in Geoserver changed when you updated the sources with Robert's new datasets? |
|
These are new layers and I simply reused the names from the files adding the prefix (HI), as I've done for all the layers to save time. So that might be the problem. Also that specific layer (europe:HI_Tx75p-consecutive-max_historical_19710101-20001231) no longer exists. The latest update from Robert changed that to: europe:Tx75p_consecutive_max_historical_19710101-20001231_ensmean and europe:Tx75p_consecutive_max_historical_19710101-20001231_ensstd |
|
Yes, as @ghilbrae mentioned, in the original names I used "_" to separate the variables and "-" within the names to make them more readable or to separate the time periods. However, if a better naming convention would be preferred, just tell me how I should name the files. |
|
I will update the resources to have into consideration the ensmean and ensstd (so we will basically have twice the amount of resources), but I would prefer that we stick to the naming convention we agreed (I also detected this other resource which is not compliant: HI_SummerDays_historical_19710101-20001231 (should it be summer-days?). |
|
@maesbri you are correct. This inconsistency appears for the other indices as well. I will rename them to follow this pattern: @maesbri - regarding the ensmean and ensstd files, would it make things easier if I combine them into 1 file? It wasn't clear to me which method would be easier for the post-processing in CSIS, so I left them as 2 separate files. |
No, it is fine like that. I am updating/renaming the Tx75 resources with the "_ensmean" at the end and then duplicate and update each of them with the sstd so I don't have to repeat again all the information. You can do then the same with the new hazard indexes. |
|
I have already made the changes to the filenames here: |
|
Done for the Tx75 hazard indexes. The wms links are not yet working as it is pending for meteogrid to update the layer names. |
@ghilbrae Can you please update the layer names so that we have working layers in the data package again? |
|
OK, I think this problem is because the consecutive days (historical) is an older dataset which used a different mask to cut out the pixels over water. The tropical nights is the newer dataset. So, a solution to this is for me to use the mask that I used for the older dataset, and this should solve the problem. |
|
That could be a solution.
…On Thu, 10 Oct 2019 at 10:28, RobAndGo ***@***.***> wrote:
OK, I think this problem is because the consecutive days (historical) is
an older dataset which used a different mask to cut out the pixels over
water. The tropical nights is the newer dataset.
So, a solution to this is for me to use the mask that I used for the older
dataset, and this should solve the problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#41?email_source=notifications&email_token=AAWTC7QAUH4TUUSVZ2LXNV3QN3RRJA5CNFSM4ILLSB3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA3MF7A#issuecomment-540459772>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAWTC7U4NFE2BBYRYY4W6SDQN3RRJANCNFSM4ILLSB3A>
.
|
|
Hi @RobAndGo Well, I'm pending |
|
Hi @LauraMTG If you want, we can try the second option that you suggest. I have uploaded the complete dataset for summer days here: /clarityftp/europe/hazard_indices/heat/summer-days The mask that I use is provided in the separate file: |
|
Ok @RobAndGo , I'll try and see if this solution is good. |
|
@RobAndGo @p-a-s-c-a-l as pointed out in today's meeting, there seems to be a layer having some issues. Can you please let us know which layer(s) is having display issues to check if there's a problem on our side? |
|
Hi @ghilbrae, /clarityftp/europe/hazard_indices/heat/hotdays-75thpercentile It is for all of Europe. I have included the mask of land-water here: |
|
On today's telco we noticed that the "Maximum consecutive days (summer) 75th percentile" standard deviation layers are suddenly the same as the "ensemble mean" layers. |
|
Both resources were using the same service path. I have changed this. |
|
Hi @RobAndGo I have published in geoserver a sample of the result obtained from applying a new mask to the final layers of HI in TIF format. It seems that now there are no land zones without data. The name of the layer is: New_Mask_HI_summer-days_historical_19710101-20001231_ensmean It is important to verify that this result is valid. If so, we must perform this procedure and automate it for the rest of the original NC layers |
|
Thank you for this @LauraMTG! The data looks good, and of course there is a lot more coastline and island regions included. At this stage only: |
|
You're welcome @RobAndGo ¡ |
|
nice
…On Tue, 15 Oct 2019, 16:10 LauraMTG, ***@***.***> wrote:
You're welcome @RobAndGo <https://github.com/RobAndGo> ¡
Tomorrow then I will launch the process with all available layers.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#41?email_source=notifications&email_token=AAWTC7QZ7XHBZ7AOOSRUYETQOXFO3A5CNFSM4ILLSB3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBI446Y#issuecomment-542232187>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAWTC7R3OOS2HRES4A4YFNLQOXFO3ANCNFSM4ILLSB3A>
.
|
|
Hi @LauraMTG /clarityftp/europe/hazard_indices/heat/consecutive-summer-days /clarityftp/europe/hazard_indices/cold/consecutive-frost-days /clarityftp/europe/hazard_indices/thermal-stress/extreme-temperature-range /clarityftp/europe/hazard_indices/precipitation/consecutive-wet-days /clarityftp/europe/hazard_indices/drought/consecutive-dry-days |
|
Ok, thanks @RobAndGo |
p-a-s-c-a-l
added
the
BB: Data Package Tool
|
Can this be considered done? |
|
I think so. As I understand it from @DenoBeno, that, until we get the option to use variables in the resource names for the RCP scenarios and time periods, it does not make sense to overwhelm the data package with 20 resources per index. What I could do is just upload a few resources per index (e.g. RCP45 or RCP85 for the periods 2041-2070, 2071-2100) concerning precipitation or drought. These are indices which @LauraMTG is/has already converted to GEOTIFF. However, I don't think we need this github issue open as a reminder to do that, so from my side you can close this issue @p-a-s-c-a-l. |
|
I'll process the data. For now, in order not to stop the publication of the final data, I will use the MTG geoserver. However, please note that the process of migrating data to ATOS FTP is pending, so its location will have to be changed later. |
|
Thank you! |
|
The migration process is being discussed here: |
This causes now more trouble than benefits. |
On todays telco, we realised that the existing hazard resources from ZAMG (heath indices) aren't the latest ones. Threfore, these ressources all need to be updated.
Alternatively, the new ones could be defined and the old ones deleted and then the new ones introduced in al lthe data packages as necessary. I suppose the first option is easier to achieve.
@RobAndGo : I understand that you will update the resources.
@ghilbrae: you need to assure that all the data we need is available on the map server.
Probably related to: #18
The text was updated successfully, but these errors were encountered: