Opened 13 years ago
Last modified 12 years ago
#22 new defect
Albers projections don't output standard parallel parameters in proj string
| Reported by: | markhepburn | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | FUTURE |
| Component: | core library | Version: | |
| Keywords: | Cc: |
Description
Method org.osgeo.proj4j.proj.Projection#getPROJ4Description() is common to all instances (ie not over-ridden). In the current implementation, this ignores the standard parallels (instance variables projectionLatitude1 and projectionLatitude2). This breaks Albers (in our case), and of course any others using them.
I can create a patch if you'd like, but what's the preferred method? Something like
if ( projectionLatitude1 != 0)
sb.append(" +lat_1=" + projectionLatitude1);
etc?
Note:
See TracTickets
for help on using tickets.
Good question. At the moment it's not possible to tell whether a given Projection implementation should output particular parameters in the PROJ.4 string. One way around this would be to override the getPROJ4Description for each subclass that needed to. But a nicer way would be for each subclass to supply metadata about which parameters are required. Not sure of the best way to do that at the moment.