Skip to content
This repository was archived by the owner on Sep 19, 2024. It is now read-only.

Architecture (WFS)

Jump to bottom
Henning Bredel edited this page Aug 15, 2014 · 5 revisions

The following gives an overview about the WFS connector's design and how it is integrated and coupled to the Ilwis framework. The connector module integrates to the Ilwis Framework with the classes WfsCatalogExplorer, WfsFeatureConnector, WfsObjectFactory, and WfsModule.

The WfsModule is being scanned by Ilwis' plugin mechanism and provides certain metadata of the connector itself and registers creation factories to the kernel. The integration layer maps the Ilwis workflow onto the WFS remote request/response communication. The actual domain level parsers do the conversation from WFS features and its metadata to an IFeatureCoverage.

The different domain-level parsers can choose to use either the XPath parser or the streaming parser. While XPath parsing is convenient when only certain parts of an XML document are of interesting, the streaming parser makes sense when huge XML documents are returned and have to be parsed almost completely (e.g. feature collection).

The XML parsers have been moved to the IlwisCore.

Clone this wiki locally