-
Notifications
You must be signed in to change notification settings - Fork 392
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
Wrong Shapefiles over South America #387
Comments
@beneduzi the data shipped with basemap is dangerously outdated outside USA and Europe. I do not recommend you to use that. You can download updated shapefiles and plot them yourself, like this example, or you can use cartopy and the natural Earth dataset. |
The data was updated in the v1.1.0 release, which is available through
conda-forge (as opposed to the standard conda channel). Which version are
you using?
…On Thu, Jan 18, 2018 at 1:22 PM, Filipe ***@***.***> wrote:
@beneduzi <https://github.com/beneduzi> the data shipped with basemap is
dangerously outdated outside USA and Europe. I do not recommend you to use
that. You can download updated shapefiles and plot them yourself, like this
examples
<https://ocefpaf.github.io/python4oceanographers/blog/2013/08/12/brazil-states-map/>,
or you can use cartopy and the natural Earth dataset
<https://ocefpaf.github.io/python4oceanographers/blog/2013/09/30/natural_earth/>
.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#387 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARy-GcXGjMzOggXLGbaWc8gPrOqDLUeks5tL4wDgaJpZM4RjUu4>
.
|
@WeatherGod v1.1.0 still uses GSHHG 2.3.6, no? As far as I can tell that still does not correctly represent South America. See http://nbviewer.jupyter.org/gist/ocefpaf/93dbaf0fce23ed5c6d4e37fc34a07142 |
Yes, it is using GSHHG 2.3.6. v2.3.7 was released back in June, and its
changenotes is:
"""
Updates the Northern Mariana Islands with CUPS data from NOAA, adds
two missing islands to northern Norway, and adds in the missing
Kosovo-Serbia boundary.
"""
So, it doesn't look like it fixed anything in South America. I would
suggest contacting Paul Wessel to let him know of the problem (feel free to
CC me on the email). He can fix the data and put out a new release, and I
can update it for basemap as well (getting about time for a new release
anyway).
…On Thu, Jan 18, 2018 at 1:50 PM, Filipe ***@***.***> wrote:
@WeatherGod <https://github.com/weathergod> v1.1.0 still uses GSHHG
2.3.6, no? As far as I can tell that still does not correctly represent
South America. See http://nbviewer.jupyter.org/gist/ocefpaf/
93dbaf0fce23ed5c6d4e37fc34a07142
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#387 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARy-Lq9RAKJztMxz8FYt4YLgL6Xj93jks5tL5KTgaJpZM4RjUu4>
.
|
Yep. Just tested v2.3.7 and it still has the same issue.
GTM devs are on GitHub 😉 Pinging @leouieda and @PaulWessel. |
@ocefpaf I use a correct shapefile, but I think a lot of people out of Brazil (and I don't know about the rest of South America), will never notice this kind of error and will use a wrong map. The Political divisions used in this are dated from early 1940's. Thanks @WeatherGod, it would be perfect, I'll contact @PaulWessel. |
@beneduzi you have greater chances of success if you include a source for the correct data. Even better if you're willing to try to fix it yourself. The main difficulty is that GSHHG has many different resolutions, all auto generated. So you need to make sure the downscaled versions aren't intersection or crazy in any way. Paul is a busy guy and this will probably not be a huge priority. |
I see numerous differences between GSHHG and DWC (Digital Chart of the World; also in GMT) for the state divisions of Brazil. If the DCW are more correct I might be able to replace the GSHHG version with those, unless better data magically arrives. |
The shapefiles have the wrong state divisions over Brazil.
Using the function mpl_toolkits.basemap.drawstates() in any resolution the state lines are wrong.
The text was updated successfully, but these errors were encountered: