30
Copyright © 2013 Open Geospatial Consortium.
and the ebRIM profile applies a flexible registry information model to supplement the common interface Get, Insert, Update, Delete Records, etc.
The OWS-9 Aviation Registry was used to host resources shared between multiple OGC services e.g. ISO metadata pertaining to datasets common to multiple WFS
implementations Snowflake, Comsoft, Styling information shared between multiple Feature Portrayal Services FPS implementations Envitia, Luciad, and ISO Service
metadata describing the Services deployed in OWS-9. The efficient retrieval of metadata task was also implemented using the Aviation Registry by designing queries to retrieve
only the relevant excerpts of the metadata desired by clients. The participants used InsertUpdateGet transactions to create User accounts, publish common resources, and
efficiently retrieve resources using complex filtered queries. No functional or performance issues were encountered during the OWS-9 initiative.
Unlike conventional geographic catalogues, INdicio™ is highly configurable and can be readily deployed to manage a wide variety of objects.
INdicio™ ships with a CSW-ebRIM Basic Extension Package which provides a variety of useful objects for geospatial applications including:
Service taxonomy and Dataset metadata model source: ISO 191151911919139 via the preloaded OGC Cataloging ISO Metadata CIM Registry Information
Model. Feature data dictionaries and catalogues source: ISO 191091911019126.
Coordinate Reference Systems source: ISO 19111. Country codes source: ISO 3166-1 “Codes for the representation of names of
countries and their subdivisions – Part 1: Country codes”. Geographical regions source: UN Statistics Division.
Property categories based on Dublin Core source: DCMI metadata terms.
6.2.4 IDS Event Service
IDS provided one of the two ES implementations of the broker component which is based on the Organization for the Advancement of Structured Information Standards OASIS
Web Services Brokered Notification 1.3 specification. Its main functionalities included finding a match between a notification sent by a producer and subscriptions subscribed
by a consumer, then disseminating those matching records to that consumer. The IDS ES has been used since OWS-8.
6.2.4.1 Interfaces
The IDS ES consists of five endpoints, and their descriptions can be found at: http:vpn.ubitech.com:9998IdsBrokerInterface
. Only the endpoints that would be used in this test bed are listed below.
Copyright © 2013 Open Geospatial Consortium.
31 Endpoint
Available Methods URL
NotificationBroker Notify, Subscribe,
CreateStoreFilter, ListStoredFilters,
DescribedStoreFilters and GetCurrentMessage
http:vpn.ubitech.com:9998IdsBrokerInt erfaceIdsBroker
PauseableSubscription Manager
Unsubscribe, PauseSubscription,
ResumeSubscription and Renew
http:vpn.ubitech.com:9998IdsBrokerInt erfaceIdsPausableSubscriptionManager
Users can access the service WSDL by concatenating the “?wsdl” at the end of the service endpoint e.g. http:vpn.ubitech.com:9998IdsBrokerInterfaceIdsBroker.
All available methods are defined by OASIS Web Services Notification WS-N, with the exception that all stored filter methods are extended and described in an experimental
schema http:test.schemas.opengis.netows-9aviationesstoredFilters.xsd. The methods used in this test bed are described in the following table.
Method Description
Notify Used by a producer to push a NotificationMessage to the ES. The
contents are Digital NOTAM Events or position update messages of an aircraft.
Subscribe Used by a consumer to define a subset of all incoming notifications. A
subset can be defined using topic filters, XPath expressions and FES 1.12.0 filters.. A Subscription can have an InitialTerminationTime
encoded as a period or a date time to define its lifetime.
Unsubscribe Used by a client to cancel a subscription.
CreateStoredFilter Used by a client to create a stored filter.
ListStoredFilters Used by a client to discover the availability of all stored filters have
been created.
DescribedStoredFilters Used by a client to retrieve stored filter descriptions.
6.2.4.2 Changes to the Event Service Implementation
In the previous test bed, the ES only supported spatial capabilities of OGC filter. For example, filtering based on geometry intersections of a bounding box wrapping the entire
route. Simulation was used to simulate the consumer and producer components. In this test bed, additional features were added:
FES 2.0 filters. Interactions with producer e.g. WFS and consumer.
32
Copyright © 2013 Open Geospatial Consortium.
Advanced Filtering functionality: Event Service Update Interval, Stored Filters, AIXM Features as Geometry Operands, Spatial Filtering of Non-spatial Features,
