-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Misplaced urban areas #105
Comments
@flaviandribeiro, could you please also provide the original geo_em files? For sure |
Yes, for sure. |
I'm sending the others too |
didn't we fix something similar in #60? |
That is what I thought as well. I have to check the projection that is embedded in the files of @flaviandribeiro and see whether our implementation of #60 is buggy or not? |
So I just ran this example myself. And indeed, the LCZ pixels seems to be shifted north-west-ward. I do think this must be related to #60, even though in this case MAP_PROJ = 1 (the Lambert projection), which so far never caused issues? As I am not sure where to start, it might take a bit of time to figure this one out ... |
We have also problem with the misplacement of the urban areas, and also may be related to the issue #60. We are working with the rotated latlon projection, and it looks like the w2w tool does not read the projection correctly. In the code the standard equidistant latlon projection is defined (i.e. MAP_PROJ = 6), but the rotated latlon option is not, and therefore I guess the projection is not read correctly, and the LCZ data are not correctly interpolated and therefore misplaced. I tried to add the projection into the w2w.py code following the link given within the code, but I did not make it work. The changes I tested in the forked w2w repository that you can find on this link. We would appreciate any kind of help, as the most of the climate simulations that we are performing are on the rotated latlon projection. |
Hi @yoselita: I am sorry to hear you also have issues with the reprojection. @yoselita and @flaviandribeiro: I currently do not have much time to look into this. Not sure if one of you already found a solution to this problem? |
Thank you @matthiasdemuzere. Unfortunately, I haven't found yet the solution to the problem. You can download the files I was using to create the map shared above from this link. |
Hello!
I haven't found it either, but I haven't got the time to look into it in
detail. I wonder if the information givenin ref_lat, ref_lon, truelat1,
truelat2, and stand_lon in namelist.wps matters to the conversion of
projections.
Thank you!
Em qua., 25 de jan. de 2023 às 07:14, Josipa Milovac <
***@***.***> escreveu:
… Thank you @matthiasdemuzere <https://github.com/matthiasdemuzere>.
Unfortunately, I haven't found yet the solution to the problem. You can
download the files I was using to create the map shared above from this
link
<https://drive.google.com/u/0/uc?id=1JdS_gxTFrH2K0L9vtYdzsUQ5D3cKrYXR&export=download>
.
—
Reply to this email directly, view it on GitHub
<#105 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AT36VUEGU43MYMGMHS2V5ZLWUD4GRANCNFSM6AAAAAASOTPV6E>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Flávia Noronha Dutra Ribeiro
Environmental Management - School of Arts, Sciences and Humanities
University of São Paulo
Group of Micrometeorology - IAG-USP
|
Hello!
I think I solved it for my area. The problem was that I haven't been very
careful in determining Truelat1, Truelat2 and Stan_lon in WPS, and w2w uses
the values from the wrf file to pass on to Proj4 to convert the projections.
Thank you very much for the attention and hope that this information helps
other people!
Best regards!
Em qui., 26 de jan. de 2023 às 09:23, Flávia Noronha Dutra Ribeiro <
***@***.***> escreveu:
… Hello!
I haven't found it either, but I haven't got the time to look into it in
detail. I wonder if the information givenin ref_lat, ref_lon, truelat1,
truelat2, and stand_lon in namelist.wps matters to the conversion of
projections.
Thank you!
Em qua., 25 de jan. de 2023 às 07:14, Josipa Milovac <
***@***.***> escreveu:
> Thank you @matthiasdemuzere <https://github.com/matthiasdemuzere>.
> Unfortunately, I haven't found yet the solution to the problem. You can
> download the files I was using to create the map shared above from this
> link
> <https://drive.google.com/u/0/uc?id=1JdS_gxTFrH2K0L9vtYdzsUQ5D3cKrYXR&export=download>
> .
>
> —
> Reply to this email directly, view it on GitHub
> <#105 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AT36VUEGU43MYMGMHS2V5ZLWUD4GRANCNFSM6AAAAAASOTPV6E>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
--
Flávia Noronha Dutra Ribeiro
Environmental Management - School of Arts, Sciences and Humanities
University of São Paulo
Group of Micrometeorology - IAG-USP
--
Flávia Noronha Dutra Ribeiro
Environmental Management - School of Arts, Sciences and Humanities
University of São Paulo
Group of Micrometeorology - IAG-USP
|
Describe your issue
I'm trying to use LCZ classification for São Paulo state, Brazil. I was able to run the program successfully, but the resulting file shows a misplaced urban classification. Note that there are urban areas at the coastline in LCZSPInt.tif, but the geo_em.d03_LCZ_params.nc file places them outside (northwest from) the coast. It seems that the geographical projections are off, but it uses EPSG 4236. LCZSPInt.tif was extracted from the LCZ global map produced by Demuzere et al. (2022). If you could help me with any clues on how to solve this, it would be greatly appreciated.
LCZ-SP.zip
w2w --version
w2w.0.4.2
nc-config --all
Installed Packages
numpy==1.23.2
Traceback
No response
The text was updated successfully, but these errors were encountered: