Skip to content
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

Error in Metwork V1.0 with metpy.plots.SkewT #145

Closed
matthieusorel opened this issue Nov 9, 2020 · 3 comments
Closed

Error in Metwork V1.0 with metpy.plots.SkewT #145

matthieusorel opened this issue Nov 9, 2020 · 3 comments
Assignees

Comments

@matthieusorel
Copy link

Hello,

I have an error while trying to import metpy.plots.SkewT.

>>> from metpy.plots import SkewT
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/opt/metwork-mfext-1.0/opt/python3_scientific/lib/python3.7/site-packages/metpy/plots/__init__.py", line 12, in <module>
    from .declarative import *  # noqa: F403
  File "/opt/metwork-mfext-1.0/opt/python3_scientific/lib/python3.7/site-packages/metpy/plots/declarative.py", line 14, in <module>
    from . import cartopy_utils, ctables
  File "/opt/metwork-mfext-1.0/opt/python3_scientific/lib/python3.7/site-packages/metpy/plots/cartopy_utils.py", line 43, in <module>
    USCOUNTIES = MetPyMapFeature('us_counties', '20m', facecolor='None', edgecolor='black')
  File "/opt/metwork-mfext-1.0/opt/python3_scientific/lib/python3.7/site-packages/metpy/plots/cartopy_utils.py", line 17, in __init__
    super(MetPyMapFeature, self).__init__('', name, scale, **kwargs)
  File "/opt/metwork-mfext-1.0/opt/python3_scientific/lib/python3.7/site-packages/cartopy/feature/__init__.py", line 264, in __init__
    self._validate_scale()
  File "/opt/metwork-mfext-1.0/opt/python3_scientific/lib/python3.7/site-packages/cartopy/feature/__init__.py", line 274, in _validate_scale
    'Valid scales are "110m", "50m", and "10m".'
ValueError: 20m is not a valid Natural Earth scale. Valid scales are "110m", "50m", and "10m".

Seeems that we are not alone: Unidata/MetPy#1368

Cheers,
Matthieu

@thebaptiste thebaptiste self-assigned this Nov 10, 2020
@thefab
Copy link
Member

thefab commented Nov 12, 2020

as I understand it, it's an upstream bug (and not a metwork one)

we should update cartopy from 0.17 to 0.18?

@matthieusorel do you understand the same thing than me?

@matthieusorel
Copy link
Author

Yep !
We should give it a try !

@thebaptiste
Copy link
Contributor

Not that simple : we are already in Cartopy 0.18. May be it's MetPy we should upgrade...
I'm working on it (soon).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants