Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Motivation:Add support for ComplexFeatures. GeoTools should be able to parse a complex WFS response and construct a set of Feature objects from it.

Contact:

Adam Brown

Tracker:

Add ComplexFeatureSupport to GeoTools

Tagline:

complex features FTW

This page represents the current plan; for discussion please check the tracker link above.

Children:

Description

GeoTool's lack of support for parsing XML into complex features limits its effectiveness as a GIS toolkit. I propose to add this functionality by modifying currently existing Simple-feature-only type hierarchies and creating new classes to handle complex types, some of which follow:

  • WFSContentDataAccess
  • WFSDataAccessFactory
  • XmlComplexFeatureParser
  • AttributeBuilder
  • ComplexFeatureBuilder

**TODO: add diagrams of before and after type hierarchies.

The XmlComplexFeatureParser is one of the key components, it uses the AttributeBuilder and ComplexFeatureBuilder to create objects that reflect the content of the XML responses (to GetFeature requests).

The WFSContentDataAccess, WFSDataAccessFactory and their parent types have been created and modified respectively to reflect the current simple feature access API as much as possible. [See examples {link:below}]

 

Status

This proposal is under construction.

Voting has not started yet:

Tasks

This section is used to make sure your proposal is complete (did you remember documentation?) and has enough paid or volunteer time lined up to be a success

 

no progress

(tick)

done

(error)

impeded

(warning)

lack mandate/funds/time

(question)

volunteer needed

  1. API changed based on BEFORE / AFTER
  2. Update default implementation
  3. Update wiki (both module matrix and upgrade to to 2.5 pages) |
  4. Remove deprecated code from GeoTools project
  5. Update the user guide
  6. Update or provided sample code in demo
  7. review user documentation

API Changes

Filter

BEFORE:

AFTER:

Documentation Changes

list the pages effected by this proposal

  • No labels