Skip navigation.
Home
OGC Network
 OGC® Home | OGC Network™ | OGC User™ | OGC Forum
networks | domains | services | infomodels | learn | servicelist | help
Home

Use Case search results

titlesort iconUse Case IDDescriptionNormal FlowPriorityBusiness RulesAssumptionsNotes and Issues
Aggregate and geoserve multiple 3rd-party data setsWFS.GEOCODE.2.RSS

Without changing operational databases in any way, implement a software component that can harvest information from those databases, geocode them, and respond to geographic information requests, preferably as a Web Feature Service. This may involve creating a lookup table matching addresses with point locations. 3rd-party databases should maintain synchronization.

Make an information request to the service, constrained by geographic area and/or attributes.
Response compliant with Web Feature Service interface.
Create a geospatial service from a database table with an address fieldWFS.GEOCODE.1.RSS

Without changing the operational database in any way, implement a software component that can respond to geographic information requests, preferably as a Web Feature Service. This may involve creating a lookup table matching addresses with point locations.

Make an information request to the service, constrained by geographic area and/or attributes.
Response compliant with Web Feature Service interface.
Give a system user access to data that was restricted prior to receiving an emergency alertDRM.CAP.WMS.1.RRS

Service: Implement a WMS service restricted by a digital rights management (DRM) system.
Service: Implement an alert receiving system that can change the state of the DRM system.
Client: Implement a client application that supports WMS and the service's DRM system.

Data user attempts to access a WMS and fails.
Alert is broadcast to a network.
Data repository gets the alert and changes data access restrictions appropriately (should be limited in time and geography).
Data user now attempts to access a WMS and succeeds.