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

Pycarto++ #119

Closed
wants to merge 31 commits into from
Closed

Pycarto++ #119

wants to merge 31 commits into from

Conversation

rhattersley
Copy link
Member

No description provided.

bblay and others added 27 commits September 27, 2012 13:58
…e shift due to the default centering of maps.
Factor out cartopy axes creation.
GRIB load sets `circular`
@rhattersley
Copy link
Member Author

Awaiting resolution of SciTools/cartopy#58 and SciTools/cartopy#60.

@esc24 esc24 mentioned this pull request Oct 2, 2012

def get_lat_lon_grids(cube):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This api change should be documented as a non-compatible change.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. Similarly for lat_lon_range() and get_lat_lon_contiguous_bounded_grids(). Will need to revisit if we move the "xy" equivalents to the plot module.

@pelson
Copy link
Member

pelson commented Oct 3, 2012

This is looking good. I've made a couple of comments, but I have no doubt that we can merge this in the next couple of hours.

@pelson
Copy link
Member

pelson commented Oct 3, 2012

Some other points:

  • It would be nice to have a rotated pole example not in its native coordinate system. (be it TEC, or one of the specific rotated pole examples)
  • The Cynthia Brewer notice is highly annoying, particularly on the GloSea example (which has 12 plots, each with their own notice that this is using the color scheme. Can we not just remove the notice?

@rhattersley
Copy link
Member Author

I've made a couple of comments...

A couple?! ;-) I'll do what I can with some of the issues, but it'd help if you could muster @esc24 & @bblay for some of the changes they were originally responsible for.

It would be nice to have a rotated pole example not in its native coordinate system.

Perhaps. Personally I like the way the data is now nice and square and the coastlines are distorted to fit. But if we do decide to have a BendyPlot(tm), it should be handled in a separate PR.

The Cynthia Brewer notice is highly annoying...

Yes. There are too many of them. And it'd be nicer to have them outside the axes. But that's a matter for a new PR too.

@pelson
Copy link
Member

pelson commented Oct 3, 2012

@rhattersley : What is your desired stratergy here? I'd be happy enough to merge and address some of my comments in a separate PR (which should be done before 1.0)?

@pelson pelson mentioned this pull request Oct 3, 2012
@rhattersley
Copy link
Member Author

Replaced by squashed PR #126.

@rhattersley rhattersley closed this Oct 3, 2012
@esc24 esc24 mentioned this pull request Oct 3, 2012
This was referenced Oct 3, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants