GEOSS ADC Architecture Workshop: Portals
Post on 30-Dec-2015
35 Views
Preview:
DESCRIPTION
Transcript
GEOSS ADC Architecture Workshop: Portals
Ingo Simonis
iGSI
ingo.simonis@igsi.eu
GEOSSComponent,
Service registry
Standards,Special
ArrangementsRegistries
references
Web Portal
searches
contributeregister
CommunityResourcesaccesses
GEOSSClearinghouse
Catalogues
Services
User
accesses
get list ofcatalogueservices
accesses
searches
invokes
referenceOfferors
Slide by Jay Pearlman
Web PortalCommunityResourcesaccesses
User
accesses
searches
GEONetCast FenYunCast
links links
GEOSecretariatResources
links
GEOSSClearinghouse
- Best practices- Training material- Capacity Building- ...
Web Portal Information Services
- Access/Security- Customization- Management- ...
GEO Web Portal
- Maps- Graphs- Diagrams- Coverages- ...
Portrayal Services
- Features- Gazetteers- Coverages- ...
Data Services
- Chats- Newsrooms- Wikis- ...
Communication/Collaboration
- Catalogs- Registries
Discovery Services
Explore Societal Benefit Areas
SearchClearing-
house
CollaborationCommuni-
cationtools
CustomizationNews
Map & Data Viewer
Training
Capacity building
GEONetcast
FenyuncastAuthorization / Authentication / Security
Web Portal
Portal Requirements - Draft
• Functional Requirements– Portrayal Services– Access to Catalogue Services– Access to Data Services– Access to web pages at GEO Secretariat– Portal management functions
• Design Requirements– Free to install at GEO member sites– Minimum dynamic performance to be defined– GEOSS identity reflected in portal design
GEO Portal Current Status
• Pilot-level portals, provided by:– Compusult (http://www.geowebportal.org)– ESA-FAO (http://www.geoportal.org) – ESRI (http://keel.esri.com/Portal)
• Videos have been produced:
http://www.ogcnetwork.net/pub/ogcnetwork/GEOSS/AI_Pilot_Demo/index.html
Potential Future Activities
• Present portals at GEOSS workshops and meetings• Develop portal presentation feedback
form/questionnaire• Capture feedback from audience• Harmonize new requirements with GEOSS Registry
(additional entries)• Develop GEO Web Portal Architecture and
Requirements report
Community Portals and Applications
• Registered at registry:– Mapufacture (Africa wild fire scenario)– SEDAC Map Client (Polar E&B scenario)– GEO Connections Discovery Portal (Polar E&B scenario)– ESA Service Support Environment (Oil Spill scenario)– SERVIR data portal (Hurricane scenario)– DataFed GEOSS Registry– Earth Observation Grid Processing on Demand GEOSS Registry– GEO-UA GEOSS Registry– GeoConnections Discovery Portal GEOSS Registry– Global Biodiversity Information Facility Data Portal GEOSS Registry– INSPIRE geo-portal GEOSS Registry– Incorporated Research Institutiions for Seismology Data Management Center GEOSS Registry– GI-go GeoBrowser GEOSS Registry– Information System and Data Center GEOSS Registry– International Directory Network: A Portal for Group on Earth Observations GEOSS Registry– NASA Earth Science Gateway GEOSS Registry– NASA Socioeconomic Data and Applications Center GEOSS Registry– U.S. Geospatial One-Stop Portal GEOSS Registry
Integrated Clients
• Frameworks• Best practices
ContextDocument
IntegratedWMS
ComponentWMS (FPS)
WMS
WFS
Catalogof SEs
Catalog ofSymbols(PNG,SVG)
GeoDSSClient
Status Quo and Ahead?
• Compusult, ESA-FAO, ESRI• Other candidates/options?• Further testing/development/evaluation• Cross-thread activities (e.g. with clearinghouse)
Some ideas
• Dictionaries• Registries• URN-resolver• Ontologies• see Sensor Web Requirements• how to deal with ebRIM profiles?
Discussion
• GEOSec to provide advice about status of portal solutions (prototypes, IOC?)
• Feedback is key: announce existence of portals to make users exploring the portals and to provide feedback
• testing with clearinghouses should be continued/completed
• Consider to run future portal activities as part of the scenario/SBA developments rather than a separate activity (define user requirements through scenario participation)
• What is the relation with application clients? Integration of various resources
top related