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

proj4 support #1

Closed
adeckmyn opened this issue Jan 20, 2016 · 3 comments
Closed

proj4 support #1

adeckmyn opened this issue Jan 20, 2016 · 3 comments

Comments

@adeckmyn
Copy link
Owner

Having proj4 support in 'maps' would be useful. But it probably can only exist besides the old projection library, which for compatibility reasons can not be removed easily. So I will probably just add new options map(..., proj4="", proj4inv=FALSE)
The second allows for inverse projections of your data (which mapproj doesn't even implement)

@mdsumner
Copy link

You might use reproj which wraps `proj4' and handles the unit scaling

@adeckmyn
Copy link
Owner Author

Indeed. But my reason for closing the issue is that I decided taht, for now, there are already so many arguments to map() that adding more for proj4 is not very helpful. It is probably better to just call reproj (or proj4) separately with the output of map(). That is more or less what is happening anyway with packages that call map() for the basic lat/lon data only.

@mdsumner
Copy link

Sure, it should be that the plot device know its crs and modifies incoming data for it, that's how we wrap things 🙏

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

No branches or pull requests

2 participants