Recent Development

Version  2.1.1 is stable.

Versions 2.2.0 and 2.2.1  are broken for VPF feature types containing variable width fields and non-point geometries.

Fixes were applied to 2.2.x and trunk so it should work. 

Module Status

The vpf module is believed to be stable for data reading.  There are no plans to implement writing at this time.

There are a number of reasons why there are no real tests.

• many data files are required to have a real VPF datastore.  Do we really want to add them to SVN?
• it takes a while to do a non-trivial amount of VPF processing
• it would take a significant amount of effort to write useful tests

IP Review

Please refer to:

• http://svn.geotools.org/geotools/trunk/gt/modules/unsupported/vpf/review.txt

Outstanding Issues

jira.codehaus.org (7 issues)
T	Key	Summary	Assignee	Reporter	Pr	Status	Res	Created	Updated	Due
	GEOT-498	VPF Keeps too many files open	Unassigned	John Meagher		Open	UNRESOLVED	Apr 12, 2005	Apr 12, 2005
	GEOT-456	OutOfMemoryError on VPF UVMap data DQAREA feature type	Unassigned	John Meagher		Open	UNRESOLVED	Mar 04, 2005	Mar 04, 2005
	GEOT-455	VPF not always setting default geometry	Unassigned	John Meagher		Open	UNRESOLVED	Mar 04, 2005	Mar 04, 2005
	GEOT-997	VPFFile/readFixedSizeData() missing case statement for date/time	Jeff Yutzler	Peter Borissow		Open	UNRESOLVED	Oct 26, 2006	Nov 13, 2006
	GEOT-497	VPFFeatures need better FIDs.	Jeff Yutzler	Chris Holmes		Open	UNRESOLVED	Apr 11, 2005	Nov 20, 2006
	GEOT-453	Use facc code to determine feature type name in VPF	John Meagher	John Meagher		Open	UNRESOLVED	Feb 28, 2005	Apr 12, 2005
	GEOT-1900	unsup/vpf has test classes with own copyright, test data of unkown origin	Unassigned	Adrian Custer		Open	UNRESOLVED	Jul 08, 2008	Jul 10, 2008