Skip to content

Conversation

@rhattersley
Copy link
Member

No description provided.

@esc24
Copy link
Member

esc24 commented Sep 28, 2012

Looks good to me. I assume this will let me remove the astype(numpy.float64) from my coordinate arrays or is there a significant benefit to using the extra precision?

@rhattersley
Copy link
Member Author

The underlying proj.4 routine always works with float64, so whatever values you supply to CRS.transform_points() they are cast to float64, transformed, and then returned as float64. So yes... where it's targeting CRS.transform_points() you'll be able to remove the calls to astype().

Copy link
Member

Choose a reason for hiding this comment

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

Will these end up being used? If not, would you mind removing?

Copy link
Member Author

Choose a reason for hiding this comment

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

Sorry - not sure what you mean. I've already deleted those lines.

@pelson
Copy link
Member

pelson commented Sep 28, 2012

Looks good to me. Just a couple of questions (commented inline).

@rhattersley
Copy link
Member Author

I think this is ready to merge.

pelson added a commit that referenced this pull request Oct 1, 2012
Allow CRS.transform_points() to work with float32.
@pelson pelson merged commit c02109a into SciTools:master Oct 1, 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.

3 participants