Profiles for common spatial transformations used in geolocation

[GoogleCodeExporter]

Describe the Desired Feature that you would like to see:

Create ProcessChains or ProcessModels to support common components within 
a geolocation process chain (e.g. MountingTransform, PitchRollYaw, etc.) 
in addition to the Community Sensor models already being created for 
different sensor types (e.g. frame sensor, scanner,SAR, etc). 

Describe why this feature would be useful and how you envision it being 
utilized:
Having common components would prevent one from having to re-create all of 
the spatial transforms for geolocating from scratch and would result in 
simpler process chains(i.e. easier to understand and debug). 

Biggest challenge will be in establishing conventions for coordinate axes. 
Implmentation should consider whether such processes, say PitchRollYaw, 
should be implemented as ProcessModels with accompanying executable code, 
or as ProcessChains built on simpler process models.

Original issue reported on code.google.com by [email protected] on 21 Oct 2008 at 10:56