Why not just put a “single” definition for the spatial reference frame within the Image Library itself?
Putting the spatial reference frame parameters in as fields of Image Library would require all producers to fill in spatial reference frame parameters for the Image Library (even though many or most producers will not be generating global textures, and spatial reference frame parameters are not applicable in those cases).
Related Questions
- Why does a Property Grid have its own spatial reference frame, independent of that of its Environment Root?
- Why not just put a "single" definition for the spatial reference frame within the Image Library itself?
- Why does a Property Grid have its own spatial reference frame, independent of the Environment Root?