Wind vector rotation troubles (rotate_vector)
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 30/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- matplotlib, python
调研方向
首先复现提供的 Basemap 示例,并比较 m.rotate_vector 对单个点和切片后的网格数组的结果。调查该例程如何处理非标准的二维纬度网格和不规则的观测坐标;当旋转行为一致,或已明确确定支持的坐标约束时,即视为完成。
由索引模型根据 Issue 内容生成。
描述
I am currently working with a gridded data set that has its wind vectors already in an earth-relative frame. When looking to rotate the wind vectors appropriately for plotting on a Basemap projection I've run into a strange problem where the vectors, quite simply, look rather odd. I ran a few tests with simple test points to make sure the rotate_vector routine appeared to be working correctly, and it seemed fine. But when I run a whole model output grid through the rotate_vector routine, it seems to produce wind fields which don't look quite right (see below).

Here are some stats associated with the point that has the red star on the plot with the title 'Rotated vectors'
Lat and Lon: 39.11, -70.0144
Original U and V: 1.30, 7.14
Rotated U and V: -1.33 , 7.13
Now note how the rotated wind at this point is aligned along the -70 meridian, which would suggest that in earth relative terms we might expect the wind components to be more along the lines of u=0 and v=7. However, judging from above that's certainly not the case.
Now, if I rotate that same vector, by itself, I get the following rotated wind:
Rotated U and V: -0.03 7.26
And see the second plot for a visual:

It would seem desirable to have the same behavior for the single point that we have for the gridded set of winds.
The only thing special about the gridded data, that I have noticed, is that the latitudes can vary in a non-standard way with increasing x dimension, west to east (e.g. 35.5N, 34.2N, 33.1N, 36.2N, etc.). It wasn't clear if this was okay within rotate_vector. In some simple tests it didn't seem to be a problem.
It would be nice to be able to use this routine for not only a set of gridded data, but observations as well. It's worth noting that observations wouldn't necessarily be ordered in a nice, regular way given the nature that observations tend to be irregularly spaced (e.g. surface stations co-located with airports).
Unfortunately I don't have any suggestions for a solution, but am hopeful others may have an idea.
Below is the snippet of code used to generate the first plot above.
Thanks!
Jacob
import nemsio
import numpy as np
import matplotlib.pyplot as plt
from mpl_toolkits.basemap import Basemap
# Get the input file
f='restart_file'
nio=nemsio.nemsfile(f)
skip=25
u10=u[::skip,::skip,0]
v10=v[::skip,::skip,0]
lats=nio.lats[::skip,::skip]
lons=nio.lons[::skip,::skip]
# Create the figure
fig=plt.figure(figsize=(18, 6))
# Domain covers NE CONUS
llcrnrlon=-84.0
llcrnrlat=35.0
urcrnrlon=-60.0
urcrnrlat=49.0
res='l'
m = Basemap(llcrnrlon=llcrnrlon,llcrnrlat=llcrnrlat,urcrnrlon=urcrnrlon,urcrnrlat=urcrnrlat,\
rsphere=(6378137.00,6356752.3142),\
resolution=res,projection='lcc',\
lat_1=25.0,lon_0=-95.0)
#The vector rotation to the Basemap projection just specified
u10_rot, v10_rot, x, y = m.rotate_vector(u10, v10, lons, lats, returnxy=True)
parallels = np.arange(-80.,90,5.)
meridians = np.arange(0.,360.,5.)
# - First sublot is without rotation
ax = fig.add_subplot(121)
ax.set_title('Without rotation')
m.drawmapboundary(fill_color='aqua')
m.fillcontinents(color='#cc9955', lake_color='aqua', zorder = 0)
m.drawcoastlines(color = '0.15')
m.drawparallels(parallels)
m.drawmeridians(meridians)
m.barbs(x, y, u10, v10, pivot='middle', barbcolor='black',zorder=10)
# - Second subplot is with rotation
ax = fig.add_subplot(122)
ax.set_title('Rotated vectors')
m.drawmapboundary(fill_color='aqua')
m.fillcontinents(color='#cc9955', lake_color='aqua', zorder = 0)
m.drawcoastlines(color = '0.15')
m.drawparallels(parallels)
m.drawmeridians(meridians)
m.barbs(x, y, u10_rot, v10_rot,
pivot='middle', barbcolor='black',zorder=10)
m.scatter(-70.0144,39.11,s=175,color='red',marker='*',latlon=True)
- 主要语言
- Python
- 星标
- 817
- 派生
- 395
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
matplotlib/basemap 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
matplotlib/basemap#368 ·
-
难度 4/5 3-5 天 新手友好度 48/100
matplotlib/basemap#652 · 2 条评论 · 5 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 45/100
matplotlib/basemap#649 · 2 个 reaction ·
-
难度 5/5 一周以上 新手友好度 35/100
matplotlib/basemap#646 ·
-
难度 2/5 1-3 小时 新手友好度 48/100
matplotlib/basemap#645 · 2 条评论 ·
查看 matplotlib/basemap 的全部 Issue
相似的 Issue
-
essnmx good first issue
难度 1/5 1 小时以内 新手友好度 95/100
-
难度 2/5 1-3 小时 新手友好度 65/100
syfoud/Simulated_Scepter#174 ·
-
难度 2/5 1-3 小时 新手友好度 75/100
Giskard-AI/giskard-oss#2840 · 1 条评论 ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success 未关闭area: repo bug perceived difficulty: 2
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 2/5 1-3 小时 新手友好度 75/100
yeti-platform/yeti#1380 ·