jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
Signup
GeoTools
  • GeoTools
  • GEOT-3921

WFS 2.0 ResourceID

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 8.0-M3
  • Fix Version/s: 8.0-M2, 8.0-M3
  • Component/s: opengis
  • Labels:
    None

Description

The WFS 2.0 specification defines the concept of ResourceID:

  • ResouceId: Implements the ResourceId operator with the rid parameter to allow predicates to be written that allow a specific resource to be queried.
  • Version Navigation: Implements ResourceId operator with the parameters that allow versions of resources to be queried (version, startTime, endTime)

The WFS 2.0 specification allows you to only "select" one of Filter, ResourceID or BBox at a time. This restriction is lifted for the GeoTools implementation of Filter.

The addition of ResourceId is the subject of the following change proposal:

http://docs.codehaus.org/display/GEOTOOLS/ResourceId

  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. Text File
    resource_and_query.patch
    23/Oct/11 11:02 AM
    59 kB
    Jody Garnett
  2. Text File
    resourceid_test.patch
    26/Oct/11 7:09 PM
    10 kB
    Mark Leslie
  3. Text File
    resourceid.patch
    18/Oct/11 3:40 AM
    36 kB
    Jody Garnett

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • History
  • Activity
Jody Garnett made changes - 18/Oct/11 3:40 AM
Field Original Value New Value
Attachment resourceid.patch [ 57369 ]
Hide
Permalink
Jody Garnett added a comment - 23/Oct/11 12:31 AM - edited
There has been a lively email discussion; with some good input from Gabriel to the effect of:
interface FeatureId{
   String getD();
   String getVersion();
   /**
    * @return <ID>[@<version>]
    */
   String rid();
}

This would be used to identifie features returned (as is the case now). On the other side the Filter expression Id<ResourceId> would be used to stage Queries:

interface FeatureId extends Identifier {
  String getID();
  boolean matches(Object feature);
  Version getVersion();
  Date getStartTime();
  Date getEndTime();
  public interface Version {
   VersionAction getVersionAction();
   Long getIndex();
   Date getTimeStamp();
  }
  public enum VersionAction {
   FIRST,
   LAST,
   ALL,
   NEXT,
   PREVIOUS
  }
}
Show
Jody Garnett added a comment - 23/Oct/11 12:31 AM - edited There has been a lively email discussion; with some good input from Gabriel to the effect of: interface FeatureId{    String getD();    String getVersion();    /**     * @return <ID>[@<version>]     */    String rid(); } This would be used to identifie features returned (as is the case now). On the other side the Filter expression Id<ResourceId> would be used to stage Queries: interface FeatureId extends Identifier {   String getID();   boolean matches(Object feature);   Version getVersion();   Date getStartTime();   Date getEndTime();   public interface Version {    VersionAction getVersionAction();    Long getIndex();    Date getTimeStamp();   }   public enum VersionAction {    FIRST,    LAST,    ALL,    NEXT,    PREVIOUS   } }
Jody Garnett made changes - 23/Oct/11 11:02 AM
Attachment resource_and_query.patch [ 57434 ]
Hide
Permalink
Jody Garnett added a comment - 23/Oct/11 11:04 AM
Okay I implemented everything and update the proposal. Clear FeatureId and ResourceId split. This is based on Justin's earlier patch and includes the updated bindings.

Some of the test cases for XML bindings hinged around the creation of invalid ResourceId information (ie containing both a relative version search and and a conflicting date range search). I have fixed these by making use of the implementation classed directly.
Show
Jody Garnett added a comment - 23/Oct/11 11:04 AM Okay I implemented everything and update the proposal. Clear FeatureId and ResourceId split. This is based on Justin's earlier patch and includes the updated bindings. Some of the test cases for XML bindings hinged around the creation of invalid ResourceId information (ie containing both a relative version search and and a conflicting date range search). I have fixed these by making use of the implementation classed directly.
Hide
Permalink
Mark Leslie added a comment - 26/Oct/11 7:09 PM
Attaching additional patch file (apply after resource_and_query.patch) to fix tests.
Show
Mark Leslie added a comment - 26/Oct/11 7:09 PM Attaching additional patch file (apply after resource_and_query.patch) to fix tests.
Mark Leslie made changes - 26/Oct/11 7:09 PM
Attachment resourceid_test.patch [ 57480 ]
Hide
Permalink
Jody Garnett added a comment - 27/Oct/11 1:39 AM
Thanks mark; I will go through and apply that now.
Show
Jody Garnett added a comment - 27/Oct/11 1:39 AM Thanks mark; I will go through and apply that now.
Jody Garnett made changes - 27/Oct/11 1:39 AM
Status Open [ 1 ] In Progress [ 3 ]
Jody Garnett made changes - 27/Oct/11 1:42 AM
Description The WFS 2.0 specification defines the concept of ResourceID:

* ResouceId: Implements the ResourceId operator with the rid parameter to allow predicates to be written that allow a specific resource to be queried.
* Version Navigation: Implements ResourceId operator with the parameters that allow versions of resources to be queried (version, startTime, endTime)

The WFS 2.0 specification allows you to only "select" one of Filter, ResourceID or BBox at a time. This restriction is lifted for the GeoTools implementation of Filter.

The addition of ResourceId is the subject of the following change proposal:

http://docs.codehaus.org/display/GEOTOOLS/ResouceId
The WFS 2.0 specification defines the concept of ResourceID:

* ResouceId: Implements the ResourceId operator with the rid parameter to allow predicates to be written that allow a specific resource to be queried.
* Version Navigation: Implements ResourceId operator with the parameters that allow versions of resources to be queried (version, startTime, endTime)

The WFS 2.0 specification allows you to only "select" one of Filter, ResourceID or BBox at a time. This restriction is lifted for the GeoTools implementation of Filter.

The addition of ResourceId is the subject of the following change proposal:

http://docs.codehaus.org/display/GEOTOOLS/ResourceId
Hide
Permalink
Jody Garnett added a comment - 27/Oct/11 4:43 AM
Thanks for the patch mark (check your whitespace settings though).
Show
Jody Garnett added a comment - 27/Oct/11 4:43 AM Thanks for the patch mark (check your whitespace settings though).
Jody Garnett made changes - 27/Oct/11 4:43 AM
Status In Progress [ 3 ] Resolved [ 5 ]
Fix Version/s 8.0-M3 [ 17864 ]
Fix Version/s 8.0-M2 [ 17480 ]
Resolution Fixed [ 1 ]

People

  • Assignee:
    Jody Garnett
    Reporter:
    Jody Garnett
Vote (0)
Watch (1)

Dates

  • Created:
    18/Oct/11 1:00 AM
    Updated:
    27/Oct/11 4:43 AM
    Resolved:
    27/Oct/11 4:43 AM
  • Atlassian JIRA (v5.2.7#850-sha1:b2af0c8)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.