I have noticed that matplotlib.toolkits.basemap.Basemap supports a smaller set of projection arguments than the underlying function matplotlib.toolkits.basemap.pyproj.Proj and was wondering if there is a fundamental limitation on the functionality of Basemap that prevents it from handling proj arguments such as x_0, y_0, ellps, datum, and init?
I would like to be able to use all of the very nice functionality built into Basemap on standard projections such as Oregon State Plane Coordinate System-North NAD27 (which can be generated using pyproj.Proj with the following proj arguments: orspcs_m = matplotlib.toolkits.basemap.pyproj.Proj(\ proj='lcc',lat_1=44.33333333333334,lat_2=46,lat_0=43.66666666666666,\ lon_0=-120.5,x_0=609601.2192024384, y_0=0,ellps='clrk66',datum='NAD27') or even more simply by orspcs_m = matplotlib.toolkits.basemap.pyproj.Proj(init='epsg:32026') or orspcs_m = matplotlib.toolkits.basemap.pyproj.Proj(init='nad27:3601') but Basemap() won't accept the necessary arguments Would this be a matter of modifying the Basemap __init__ function to recognize a longer list of possible arguments or is there a larger issue I'm not seeing, or a bunch more code that would require modification? thanks, Charles Seaton Research Associate OHSU/ STC-CMOP -- View this message in context: http://www.nabble.com/projections-in-matplotlib.toolkits.basemap-Basemap-vs.-pyproj.Proj-tf4617163.html#a13186371 Sent from the matplotlib - users mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
