I have noticed, that the albers equal area conic projection, fails when both parameters are set to 0. Unfortunately, the error is not checked in SetMakeParams(), so hugin can't see that something is wrong. Currently, this then leads to a crash in hugin (I have to investigate why that happens..).
On the other hand, if I understand correctly, the albers equal area conic projection with phi1=phi2=0, is equivalent to the lambert equal area cylindrical projection. Would it make sense to either fix the albers code so that it can handle phi1=phi2=0, or make the albers functions automatically switch to the lambert equal area cylindrical mapping internally.
This would avoid adding hacks for specific projections to hugin, since I assumed that all parameters inside the min and max range reported by panoProjectionFeaturesQuery() are valid parameters.
XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club!
Jetzt gratis testen! http://freemail.web.de/home/landingpad/?mc=021130