Map the Behrmann projection to cae when converting ESRI CRSes #1986
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Adds the capability to force a fixed value for a non-specified CRS component while mapping ESRI projections, and maps the Behrman projection to cae with lat_ts=30, lon_0=0
I had to add the new "is_fixed_value" property for ESRIParamMapping in order to differentiate parameters which are specified in the ESRI WKT definition and have an expected value Vs parameters which are NOT included in the ESRI WKT definition and have to have a fixed value (such as the Standard_Parallel_1 parameter for Behrman, which is not part of the CRS definition but has to have the value of 30 so that the proj string gets the required +lat_ts=30 parameter)