Dashboard > uDig > Home > Documents > Requirements
uDig
Requirements
Added by Jive , last edited by jive on Oct 02, 2004  (view change)
Labels: 
(None)

Functional and Non Functional Requiremens are recorded for each module.

Use Case

Standards and Interoperability

  • act as a Web Feature Server client
  • provide access to GML data sources via WMS
  • act as a Web Map Server client
  • prototype a Web Registry Server search capability
  • providing a WFS client data store for GeoServer
  • providing a test implementation of a WRS client and providing feedback to the standards body.

The recent standardization effort of GO-1 and GeoAPI will be tracked in co-operation with Geotools.

Risks

  • Defining a sufficiently flexible printing user interface without creating
    excessive development effort.
  • Creating large format print outputs using the Java printing API, which has
    been primary tested with letter sized text-rich output.
  • Creating a canvas that can edit dynamically reprojected inputs and pass the
    resultants back to the source databases without coordinate drift or
    transaction issues.

Powered by a free Atlassian Confluence Open Source Project License granted to uDig. Evaluate Confluence today.
Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators
User-friendly Desktop Internet GIS