Changes between Version 3 and Version 4 of FdoWMSSLDSupport
- Timestamp:
- 10/29/07 10:05:38 (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FdoWMSSLDSupport
v3 v4 14 14 If a WMS is to symbolize features using a user-defined symbolization, it is necessary to identify the source of the feature data. The WMS-SLD specification is designed to permit a wide variety of implementations of WMS that support user-defined symbolization. For example a WMS might symbolize feature or coverage data stored in a remote Web Feature Server (WFS) or Web Coverage Server (WCS), or it might only be able to symbolize data from a specific default feature/coverage store. 15 15 16 To support this option, a !RemoteOwsType enumeration will be added to the FDO WMS Overrides API and exposed as a property on the Raster Definition class. By setting the enumeration value, clients will be able to specify the source of the feature/coverage data. The presently allowed values are WFS and W MS though more may be allowed in the future.16 To support this option, a !RemoteOwsType enumeration will be added to the FDO WMS Overrides API and exposed as a property on the Raster Definition class. By setting the enumeration value, clients will be able to specify the source of the feature/coverage data. The presently allowed values are WFS and WCS though more may be allowed in the future. 17 17 18 18 The !RemoteOwsType is to be used in conjunction with the Raster Definition’s !RemoteOwsUrl property which specifies the URL of the OWS service.