• Contact: hgryoo
• Tracker: <>
• TLDR: one line description
• Branch: <>

Description

Take a couple paragraphs to describe the change, motivations and link out to any design documents. It is especially important to highlight any customer requirements or deadlines.

// As a Java Library most proposals will include a code example

We expect proposals to be used to bounce ideas off the community before you have secured budget for the work. This is your chance to ask for a sanity check, confirm the technical approach and see if you forgot anything (such as documentation or QA requirements). Please present this proposal requirement to your management or customer as a way to reduce risk.

References:

• OGC documents
• design docs
• geotools-devel email discussion
• GeoTools change proposal

Status

Choose one of:

• Under Discussion
• In Progress
• Completed
• Rejected,
• Deferred

Voting:

• Andrea Aime
• Ben Caradoc-Davies
• Christian Mueller
• Ian Turton
• Justin Deoliveira
• Jody Garnett
• Simone Giannecchini

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. Use initials to indicate volunteer, or :warning: where volunteer is neededs. Proposals that lack resources to be successful are unlikely to be approved.

1. Update implementation
2. Verify with test case
3. Remove deprecated code
4. Documentation changes
   • API change make a note upgrading page.
   • Update the user guide with code example

API Change

Before:

import org.geotools.filter.Filter;
public void exampleMethod( DataStore store, Filter filter){
    FeatureCollection collection = store.getFeatures( filter )
     ...   
}

After:

import org.opengis.filter.Filter;
public void exampleMethod( Source source, Filter filter){
    Collection collection = source.content( filter )
    ...   
}