geoq
geoq copied to clipboard
The TC (Tasking, Collection) in TCPED
Need to discuss creating a "new tab" in GEOQ to handle the Tasking and Collection planning, coordination and status of imagery collection for cap and other sources.
Should it be a new tab? Or just a different type of job that is handled differently?
On Fri, Jun 27, 2014 at 11:08 AM, Ray Bauer [email protected] wrote:
Need to discuss creating a "new tab" in GEOQ to handle the Tasking and Collection planning, coordination and status of imagery collection for cap and other sources.
Reply to this email directly or view it on GitHub: https://github.com/ngageoint/geoq/issues/176
That's the discussion. Need to bring in the smes to discuss at acme.
Ray
On Jun 27, 2014, at 11:10 AM, Jay Crossler [email protected] wrote:
Should it be a new tab? Or just a different type of job that is handled differently?
On Fri, Jun 27, 2014 at 11:08 AM, Ray Bauer [email protected] wrote:
Need to discuss creating a "new tab" in GEOQ to handle the Tasking and Collection planning, coordination and status of imagery collection for cap and other sources.
Reply to this email directly or view it on GitHub: https://github.com/ngageoint/geoq/issues/176 — Reply to this email directly or view it on GitHub.
I've worked closely with CAP on this and I would recommend not building that into GeoQ for now. I can help build that in the future but for now I think we should keep GeoQ strictly on Exploitation. That is where we need the man power. Tasking is a small job that can be handled by the on scene remote sensing coordinator.
During discussions today it was suggested that current system capabilities for creating a Job and Workcell, drawing polygons where more coverage is required, and exporting out this information as a Shapefile for ingestion by other applications would work well. What we would probably want to do in this case would be to look at ways of expediting this process and standardizing the naming so that the layer produced will be quickly accessible to other applications.