"Seegrid will be due for a migration to confluence on the 1st of August. Any update on or after the 1st of August will NOT be migrated"

GeoServer Development Plan

  • Test cases are detailed in TestBed3UseCases
  • Test cases 4 and 5 are outside the scope of GeoServer
  • Development is broken into three week iterations, each comprising approximately 12-14 working days
  • Deliverables (builds, configurations) are made available as soon as they are ready, and are not tied to iterations.

Iterations

Use case matrix

  • Keys are used for convenience.
  • Some Jira tasks (i.e. AUS-*) are on an internal Jira instance and are only accessible from within CSIRO.

Key Use case References Task Estimate/Status
{wfs.shape.gml} User queries feature service and receives shapes encoded in GML (not WKT). GeoserverFeedback, AUS-262 Fix this bug. DONE
{wfs.response.validation} User tests feature service with a validation tool and response is validated. GeoserverFeedback, AUS-253 Establish validation methodology and write tool to automate. DONE: See XmlServiceTester
{wfs.test.automation} Users runs a tool that makes many feature service requests and automatically tests the correctness of the responses. AUS-253 Write test tool DONE: See XmlServiceTester
{use.case.1} User queries map service for portrayal of complex features TestBed3UseCase1 Implement WMS with complex feature support 10 days
{use.case.2.a} User queries feature service for all features TestBed3UseCase2 A, AUS-353   DONE
{use.case.2.b} User queries feature service for all features expecting EarthMaterial composition links TestBed3UseCase2 B, AUS-354   DONE
{use.case.2.c} User queries feature service for MappedFeatures TestBed3UseCase2 C, AUS-355    
{use.case.2.d} User queries feature service for SamplingFeatures within a bounding box TestBed3UseCase2 D    
{use.case.2.e}   TestBed3UseCase2 E    
{use.case.3.a} User queries feature service for all features with a particular lithology property TestBed3UseCase3ALithQuery    
{use.case.3.b} User queries feature service for all features with a particular geologic age TestBed3UseCase3BAgeQuery    
{use.case.3.c}   TestBed3UseCase3CStructureQuery    
{use.case.3.d} User maps Borehole with multiple gml:name elements with different codeSpace attributes TestBed3UseCase3DBoreholeQuery    
{bgs.borehole.mapping:11} User maps Borehole with coverage element (mapping:11 in BGS Borehole) TestBed3UseCase3DBoreholeQuery Fix ClassCastException failure  
{bgs.borehole.mapping:13} User maps Borehole with coverage position (mapping:13 in BGS Borehole) TestBed3UseCase3DBoreholeQuery Fix ClassCastException failure  
  ... many more of these ...      
{wfs.filter.function} User queries feature service with filter containing (CQL?) function TestBed3UseCase3AProfile AUS-203 Implement test harness. Implement function support and handlers for each database backend 10-20 days
{wfs.shapefile} User configures feature service to obtain its data from a shapefile   Implement test harness to compare response from shapefile to response from property file. DONE
Topic revision: r17 - 15 Oct 2010, UnknownUser
 

Current license: All material on this collaboration platform is licensed under a Creative Commons Attribution 3.0 Australia Licence (CC BY 3.0).