Polar Stereographic Projection #1339
Replies: 3 comments
-
I guess several of the classes have non-public vars. Given a Grib2Gds of the stereo and lambert types, and a need to persist their specific fields based on their tables (referenced in the Grib2Gds.java file above each class), what is the recommended way of accessing that data?
And for Lambert only:
|
Beta Was this translation helpful? Give feedback.
-
I am not very familiar with the code or why some members were made public. In general, we prefer to have private members to limit unneeded access. If you just need read access to these members, I would suggest adding getter methods and keeping the members themselves package private as they are now. |
Beta Was this translation helpful? Give feedback.
-
Thanks @tdrwenski — I went with a Horizontal System created from the projections which provided everything I needed (right now) to create a coverage. If I need access to the other values, I agree that a getter would be great! Thanks again—I'll close this. |
Beta Was this translation helpful? Give feedback.
-
Hello! I am an engineer working on a NWS project and using this library. I am currently migrating some old python code into java persistence code, and using the 5.x branch of this library. I am wondering why in Grib2Gds, the Polar Stereographic - as opposed to the Lambert, Mercator, and Lat/Lon classes—does not have public fields? For example, LA/LO 1.
In the others:
In Polar:
I am new to this weather code world. I am wondering why this was done, or if it is oversight. I am persisting a lot of different GDS based coverages to my db, and need to be able to access these fields. An easy change—but I want to see why this is the way it is before any attempt at change.
Beta Was this translation helpful? Give feedback.
All reactions