- Make a "default" useful parser available as a utility class
- Spatial.parseWKT (should be method compatible with JTS utility class)
- Hide details in a parser package (that casual users do not need to import)
- Be consistent with package names (not sure how to handle version differences)
- org.geotools.filter.text.cql2 - parser code for CQL
- org.geotools.geometry.text.wkt - parser code for WKT
- org.geotools.filter.xml.filter1_0 - filter 1.0 bindings (requires gml2)
- org.geotools.filter.xml.filter1_1 - Filter 1.1 bindings (requires gml3)
- org.geotools.geometry.xml.gml2 - geometry bindings for latest GML2
- org.geotools.geometry.xml.gml3 - geometry bindings for latest GML3
Of the format org.geotools.SUBJECT.PARSER.SPECIFICATION:
Please note this is for the gory details only; your users should not have to import anything from these packages. You may be stuck making some of the content public (especially for XML callbacks) - but none of your example/user code should be forced into an import.
- Update Upgrade to 2.4 instructions (if xml parsing packages are changed)
- Update description package convention to describe how additional parsers can be added.
- CQL examples look great!
- CRS examples needed
- Spatial examples needed
- Check with Acuster to see if demo can be updated
- Close jira when completed