210 likes | 362 Views
GPS Explorer: Overview and Extension to INDIGO http://geoapp.ucsd.edu. Paul Jamason | Scripps Orbit and Permanent Array Center (SOPAC ) IGS Analysis Center Workshop, Miami, 2008. GPS Explorer Background.
E N D
GPS Explorer: Overview and Extension to INDIGOhttp://geoapp.ucsd.edu Paul Jamason | Scripps Orbit and Permanent Array Center (SOPAC ) IGS Analysis Center Workshop, Miami, 2008
GPS Explorer Background • NASA REASoN project to provide GPS data products/services using new web technologies/standards • project overview: http://reason.scign.org • java-based web portal; web 2.0 (mapping, inter-portlet communication) • develop common formats (xml) and methods (web services) for improved metadata and data exchange • Geophysical Resource Web Services: http://reason.scign.org/scignDataPortal/grwsSummary.jsp • NASA MOSES project to allow users to perform modeling in a portal context • application of various time series models
GPS Explorer Framework • Uses the • JSR-168 compliant portlets (java-based windows in portal with user controls; distributable to other portals) • user logins; save data/results for future viewing • standard look/feel across pages; easy configuration • Employs a workflow/dashboard approach • users select and save groups of GPS sites via mapping portlet. Data queries, modeling operations are performed throughout portal on saved groups. • Inter-portlet communication • Dynamic content produced via calls to back-end web services
GPS Explorer Portal: Mapping • SOMI: Scripps Online Mapping Interface • University of Minnesota MapServer; input data layers stored at SOPAC (e.g., fault lines) • interactive velocity vectors • users can draw bounding boxes to select sites • recent performance optimization • Migrating to OpenLayers • open source API • user community • utilize non-google data layers • MapServer; tile caching
GPS Explorer Portal: Products • Processed GPS coordinates • millions of xyz coordinates from SOPAC/JPL/REASON combination/PBO • dynamically queryable and exportable to urls • GPS Time Series • layer time series from different sources/sites via Java Applet • display time series dynamically by clicking sites on map • Velocities • view/layer velocity vectors for various sources/reference frames • Strain Maps • under development
GPS Explorer Portal: Geophysical Resource Web Services • Standardized approach to data submission/retrieval • Inter-agency data exchange • Use XML standards • Geography Markup Language (GML): represent features/geometry/reference systems/time • observation collections; filter encoding • transfer XML via SOAP/web services • alternatives: JSON, REST • Advantages: • Independent server-side code. call web services from other web pages/sites, command-line utilities, etc. • Adaptable - e.g., REASoN -> INDIGO: new web services
XML and Geodesy at SOPAC: IGS Site Logs • Overview: http://sopac.ucsd.edu/projects/xml
<igsSiteLog xmlns="http://sopac.ucsd.edu/ns/geodesy/doc/igsSiteLog/2004" xmlns:mi="http://sopac.ucsd.edu/ns/geodesy/doc/igsSiteLog/monumentInfo/2004" xmlns:equip="http://sopac.ucsd.edu/ns/geodesy/doc/igsSiteLog/equipment/2004" xsi:schemaLocation="http://sopac.ucsd.edu/ns/geodesy/doc/igsSiteLog/2004 http://sopac.ucsd.edu/ns/geodesy/doc/igsSiteLog/2004/igsSiteLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <siteIdentification> <mi:siteName>Scripps 5 - Mt. Soledad</mi:siteName> <mi:fourCharacterID>SIO5</mi:fourCharacterID> <mi:monumentInscription>SIO5 ECCS</mi:monumentInscription> <mi:iersDOMESNumber>40460M006</mi:iersDOMESNumber> </siteIdentification> <siteLocation> <mi:city>La Jolla</mi:city> <mi:state>California</mi:state> <mi:country>USA</mi:country> <mi:approximatePositionITRF> <mi:xCoordinateInMeters>-2456115.13</mi:xCoordinateInMeters> <mi:yCoordinateInMeters>-4768905.79</mi:yCoordinateInMeters> <mi:zCoordinateInMeters>3439232.44</mi:zCoordinateInMeters> <mi:latitude-North>+325024.00</mi:latitude-North> <mi:longitude-East>-1171500.00</mi:longitude-East> <mi:elevation-m_ellips.>185.53</mi:elevation-m_ellips.> </mi:approximatePositionITRF> </siteLocation> <gnssReceiver> <equip:receiverType>ASHTECH Z-XII3</equip:receiverType> <equip:satelliteSystem>GPS</equip:satelliteSystem> <equip:serialNumber>LP02814</equip:serialNumber> <equip:firmwareVersion>CD00</equip:firmwareVersion> <equip:dateInstalled>2002-05-15T00:00Z</equip:dateInstalled> <equip:dateRemoved>2003-01-09T00:00Z</equip:dateRemoved> </gnssReceiver> <gnssAntenna> <equip:antennaType>ASH701945B_M</equip:antennaType> <equip:serialNumber>CR519991867</equip:serialNumber> <equip:antennaReferencePoint>BPA</equip:antennaReferencePoint> <equip:marker-arpUpEcc.>0.0083</equip:marker-arpUpEcc.> <equip:dateInstalled>2002-05-15T00:00Z</equip:dateInstalled> <equip:dateRemoved>2004-09-29T00:00Z</equip:dateRemoved> <equip:notes></equip:notes> </gnssAntenna> Sample XML IGS Site Log
GPS Explorer Portal: INDIGO • SOPAC and INDIGO • Inter-service Data Integration for Geodetic Operations • systems enabling the simultaneous use of multiple space geodetic techniques • Utilize IT resources and JPL collaboration in support of IGS • Potential development areas: • Include all GNSS sites at CDDIS/JPL/IGN (GSAC) • Extend GPS Explorer capabilities to include SLR/VLBI/DORIS • Site mapping • Common data exploration/visualization tools • Incorporate GPS products into (next-generation?) GSAC • Provide web services wrapper to GSAC
GPS Explorer Portal: Future • Focus on IGS support via INDIGO • How can GPSE serve as common interface for user access to data/metadata? • Add “Products” tab • Portal name change? • Evaluate/implement feedback from user survey, NASA website developers • Ingest/display new data sources • Cross-browser compatibility • Javascript development • Evaluate other portal frameworks (JBOSS) • Interactive Strain Maps