Presentation on theme: "Introducing: PFPS Google Earth Tool Updated for Version 1.0"— Presentation transcript:
1 Introducing: PFPS Google Earth Tool Updated for Version 1.0 Capt Mark Jacobsen10th Airlift Squadron19 January 2008In Partnership with the USAFA Institute for InformationTechnology Applications (IITA) and Warfighter’s Edge (WEdge)
2 Introduction What the Software Is New Features Examples & Capabilities Possible UsesPros & ConsGoogle Earth in the Air ForceFuture CapabilitiesConclusion
3 What Is It?A utility that converts PFPS/FalconView data into a Google Earth .KML file for 3D visualizationVersion 0.5 released in August 2007Version 1.0 released 22 January 2008Rewritten from scratchBetter integration with FalconViewMany new features!
4 New Features in v1.0Direct conversion of .RTE files – no more .CRD conversionTwo new kinds of airspace: elliptical and rectangularNew Threat object: supports probability ellipses, detection rings & engagement ringsFalconView Drawing File importerFalconView Threat File importerFalconView Local Point File importerNew support for airspace floorsCustomizable icons for graphical stylesLibraries for FalconView, Google Earth, and NGA iconsAbility to nest objects in foldersSIPRNET compatibility/hosting
5 Another PFPS route was imported to show the IR 326 corridor Another PFPS route was imported to show the IR 326 corridor. It uses an extruded, shaded path set to 5000’ MSL to give the appearance of solid walls around the low level corridor.A PFPS route was imported to show IR326. It is shown at a constant 500’ AGL.This is a Google Earth screenshot, showing the capabilities of PFPS Google Earth Tool. It shows several types of objects that the user can create.Polygonal airspace volumes were defined by PFPS route files. These represent Restricted Area R6714 and the Hanford Nuclear Reservation.Cylindrical airspace volumes were defined with a 3NM radius and 1500’ AGL to encompass local airfields.
6 PFPS Google Earth Tool allows users to create wedge-shaped airspace regions defined by radials and DME from a known waypoint. Six of these regions were used to build an airfield pie.Note: to avoid compromising classified information, this picture does not accurately reflect the airspace around Baghdad. It contains deliberate misinformation and imaginary airspace regions.Here is another screenshot, showing other ways the PFPS Google Earth Tool can be used to represent airspace.A PFPS route was used to define a polygonal region of airspace, representing an imaginary firing range.
7 One of the most exciting new features in v1 One of the most exciting new features in v1.0 is the FalconView Drawing File importer.With a few clicks, a user can visualize a FalconView drawing file in 3D.This makes it easy for users—from individual pilots to CAOC Intelligence Officers—to view the same data set in both applications.
8 Version 1.0 now allows users to define both floors and ceilings for airspace. Due to a limitation in Google Earth, previous versions only supported SFC to ceilings.Version 1.0 also adds elliptical and rectangular airspace, allowing users to create virtually any airspace shape they wish.
9 The ZSU-23 on the left edge of the screen was loaded using the Threat Importer. For any given threat, users can specify probability ellipses (shown here in blue), detection rings (not shown), and engagement rings (shown in red).This screenshot demonstrates both. The icons on the right half of the screen are local points. Note that the importer actually uses the same FalconView icons in Google Earth.Version 1.0 has two new import functions. It now imports FalconView Threat (.thr) files and FalconView Local Point (.lpt) files.
10 Users can edit graphical properties for every object to determine how that object will appear in Google Earth. Version 1.0 supports customizable icons. Its use of Icon Libraries means that FalconView icons—such as those used for threats and local points—can be ported straight into Google Earth.This is what PFPS Google Earth Tool looks like. The user can create or import a variety of different objects using the buttons on the toolbar. These objects appear in the tree view on the left of the screen.Double-clicking any object opens a property form, such as the Airspace Properties form above. The user can customize each object as desired.
11 Possible Uses? Best determined by individual units or crews Some possibilities:Low-level fly-throughsVisualization of ACOs or other congested airspaceRepresentation of local airfields, restricted areas, wildlife areas, etc.Study of unfamiliar airfields, drop zones or targetsThreat/SAFIRE/IED plotting and animation
12 Pros & Cons Pros Cons: Easier to use than TaskView Another tool to enhance SA in unfamiliar territoryDepicts routes in relation to 3D airspaceCons:Not a sanctioned Air Force productGoogle Earth is still an emerging technologyLacks the precision of tools like FalconViewMay be subject to bugs—always check against professional tools like PFPS
13 GE in the Air Force NGA has a SIPRNET version running NGA map data running on GE client softwareNo standard NIPRNET solution yetInstalling the free version of GE on a government computer is a license violationFree version okay for personal/home useAF authorized version costs $400/yr per copyAF Combat Support office discussing possible acquisition of GE Enterprise Edition for NIPRNET
14 GE in the Air Force DoD is taking GE seriously Close look by: 951 ESG (Mission Planning software)AFCSO (FalconView acquisition)USAF Academy Institute for Information Technology ApplicationsNGA providing tower data in .KML formatMany commercial aviation companies providing .KML data for DAFIF, charts, airspace, etc.Extract from NGA Tower Database
15 GE in the Air ForcePFPS Google Earth Tool is being tried out around the Department of Defense4,300+ visits to product websites from:Air Force Active Duty & Reserve fighter & heavy unitsNavy fighter squadronCoast Guard and Civil Air Patrol SAR unitsMissile Defense testing contractorsC-17 Weapons Instructor CourseNational Geospatial Intelligence Agency
16 Future Capabilities I’m not done yet Future versions will hopefully include:Post-flight GPS tracksE-CHUM and DAFIF supportThreat terrain maskingACO importer (early prototype is functional)IITA / Warfighter’s Edge PartnershipPossible accreditation as part of WEdgePossible future development under IITA (link)
17 Future CapabilitiesVersion 1.0 was redesigned from the ground up to integrate with other software toolsPFPSGoogle Earth conversion code is kept separate from front-end user applicationConversion classes stored in .DLL accessible to all .NET languages (VB.NET, C#, C++ .NET)Other applications can access this class library to convert PFPS data to .KMLIf you are interested in acquiring or using the conversion library for your own project, please contact me
18 In ConclusionPFPS Google Earth Tool—a new resource to help crews visualize flights in 3DDownload for freeNIPRNET:SIPRNET: gis.geoint.nga.smil.mil/GoogleEarth/googleearthpilotJWICS: gis.geoint.nga.ic.gov/GoogleEarth/googleearthpilotIf you would like more information or would like to be included in future updates, please