Home

SANY Sensors Anywhere

About SANY | News | Results | Downloads | Contact | Login

Search

SANY concrete results

  • Sensor Service Architecture
  • SANY Software Components
    • OGC SWE Services
    • Map and Diagram Service
    • SensorSA Catalogue Service
      • Supported Search Criteria
      • Harvesting and Semantic Annotation
    • SensorSA Security Framework
    • Time Series Toolbox
    • Cascading SOS
    • Georeferenced Timeseries Viewer
  • Sensor Integration
  • Data Fusion and Modelling Services
  • Decision Support Infrastructure
  • SANY Applications

Upcoming events

  • no upcoming events available
Add to iCalendar
more
Home » Results » SANY Software Components » SensorSA Catalogue Service

Supported Search Criteria

Following illustration shows the resource types of the so called SANY Application Schema for Meta-information. Each resource type supports mandatory meta-information sections (table of contents and core elements) containing common meta-information elements like ‘title’, ‘keywords’ or ‘source url’. Further meta-information can be provided by specifying optional sections. This has been used for the description of the new resource types. Additionally the ‘Procedure’ resource type supports a SensorML section for a detailed description of sensors.
SensorSA Resource Types
To support the possibilities of the SANY meta-information schema for the discovery process, the SensorSA Catalogue supports following search criteria ("queryables"):

  • ‘FeatureOfInterest’ allows search for specific feature of interests, like a specific test region.
  • ‘ObservedProperty’ allowa search for general phenomena, like ‘urn:ogc:phenomenon:temperature’.
  • ‘Procedure’ supporting the possibility to search for general sensor types (e.g. accelerometer) and sensor instances.
  • ‘DatasetType’ allows search for specific resource types like ‘Feature of Interest’, ‘Observed Property’ or ‘Procedure’.
‹ SensorSA Catalogue ServiceupHarvesting and Semantic Annotation ›
By Denis Havlik at 2009-11-06 12:30 | printer-friendly version | login to post comments