RubyGems - shp - Versions diffs - 0.0.1 - Mend

shp 0.0.1

Files changed (78) hide show

checksums.yaml +15 -0
data/.gitignore +34 -0
data/.travis.yml +4 -0
data/Gemfile +3 -0
data/LICENSE +28 -0
data/README.md +30 -0
data/Rakefile +23 -0
data/ext/shp/base.hpp +113 -0
data/ext/shp/dbf.cpp +381 -0
data/ext/shp/dbf.hpp +44 -0
data/ext/shp/extconf.rb +13 -0
data/ext/shp/shape_object.cpp +58 -0
data/ext/shp/shape_object.hpp +27 -0
data/ext/shp/shapefile.cpp +299 -0
data/ext/shp/shapefile.hpp +35 -0
data/ext/shp/shapelib/.cvsignore +15 -0
data/ext/shp/shapelib/ChangeLog +450 -0
data/ext/shp/shapelib/HOWTO-RELEASE +16 -0
data/ext/shp/shapelib/LICENSE.LGPL +483 -0
data/ext/shp/shapelib/Makefile +113 -0
data/ext/shp/shapelib/README +41 -0
data/ext/shp/shapelib/README.tree +172 -0
data/ext/shp/shapelib/contrib/.cvsignore +12 -0
data/ext/shp/shapelib/contrib/Makefile +66 -0
data/ext/shp/shapelib/contrib/ShapeFileII.pas +234 -0
data/ext/shp/shapelib/contrib/Shape_PointInPoly.cpp +238 -0
data/ext/shp/shapelib/contrib/Shape_PointInPoly_README.txt +59 -0
data/ext/shp/shapelib/contrib/csv2shp.c +558 -0
data/ext/shp/shapelib/contrib/dbfcat.c +166 -0
data/ext/shp/shapelib/contrib/dbfinfo.c +106 -0
data/ext/shp/shapelib/contrib/makefile.vc +34 -0
data/ext/shp/shapelib/contrib/my_nan.h +46 -0
data/ext/shp/shapelib/contrib/shpcat.c +100 -0
data/ext/shp/shapelib/contrib/shpcentrd.c +159 -0
data/ext/shp/shapelib/contrib/shpdata.c +129 -0
data/ext/shp/shapelib/contrib/shpdxf.c +340 -0
data/ext/shp/shapelib/contrib/shpfix.c +110 -0
data/ext/shp/shapelib/contrib/shpgeo.c +1595 -0
data/ext/shp/shapelib/contrib/shpgeo.h +154 -0
data/ext/shp/shapelib/contrib/shpinfo.c +113 -0
data/ext/shp/shapelib/contrib/shpproj.c +260 -0
data/ext/shp/shapelib/contrib/shpsort.c +605 -0
data/ext/shp/shapelib/contrib/shpsort.txt +44 -0
data/ext/shp/shapelib/contrib/shpwkb.c +123 -0
data/ext/shp/shapelib/contrib/tests/shpproj.sh +38 -0
data/ext/shp/shapelib/dbfopen.c +2221 -0
data/ext/shp/shapelib/makefile.vc +86 -0
data/ext/shp/shapelib/makeshape.sh +21 -0
data/ext/shp/shapelib/mkdist.sh +37 -0
data/ext/shp/shapelib/mkinstalldirs +38 -0
data/ext/shp/shapelib/mkrelease.sh +55 -0
data/ext/shp/shapelib/safileio.c +286 -0
data/ext/shp/shapelib/shapefil.h +647 -0
data/ext/shp/shapelib/shapelib.def +46 -0
data/ext/shp/shapelib/shpopen.c +2388 -0
data/ext/shp/shapelib/shptree.c +1187 -0
data/ext/shp/shapelib/shputils.c +1072 -0
data/ext/shp/shapelib/stream1.out +1465 -0
data/ext/shp/shapelib/stream1.sh +28 -0
data/ext/shp/shapelib/stream2.out +530 -0
data/ext/shp/shapelib/stream2.sh +11 -0
data/ext/shp/shapelib/stream3.out +37 -0
data/ext/shp/shapelib/web/.cvsignore +2 -0
data/ext/shp/shapelib/web/codepage.html +403 -0
data/ext/shp/shapelib/web/dbf_api.html +436 -0
data/ext/shp/shapelib/web/index.html +235 -0
data/ext/shp/shapelib/web/license.html +78 -0
data/ext/shp/shapelib/web/manifest.html +87 -0
data/ext/shp/shapelib/web/release.html +80 -0
data/ext/shp/shapelib/web/shapelib-tools.html +352 -0
data/ext/shp/shapelib/web/shp_api.html +376 -0
data/ext/shp/shp.cpp +19 -0
data/ext/shp/shp.hpp +47 -0
data/lib/shp.rb +35 -0
data/lib/shp/version.rb +3 -0
data/shp.gemspec +23 -0
data/spec/shp_spec.rb +127 -0
metadata +176 -0

data/ext/shp/shapelib/web/dbf_api.html ADDED Viewed

@@ -0,0 +1,436 @@
+<html>
+<head>
+<title>Attribute (.DBF) API</title>
+</head>
+<body>
+<h1>Attribute (.DBF) API</h1>
+The Attribute (DBF) API uses DBFHandle to represent a handle for access
+to one .dbf file.  The contents of the DBFHandle are visible (see shapefil.h)
+but should be ignored by the application.  It is intended that all information
+be accessed by API functions.  Note that there should be exactly one record
+in the .dbf file for each shape in the .shp/.shx files.  This constraint
+must be maintained by the application.<p>
+<!-------------------------------------------------------------------------->
+<h2>DBFOpen()</h2>
+<pre>
+DBFHandle DBFOpen( const char * pszDBFFile, const char * pszAccess );
+  pszDBFFile:		The name of the xBase (.dbf) file to access.
+  pszAccess:		The fopen() style access string.  At this time only
+			"rb" (read-only binary) and "rb+" (read/write binary)
+		        should be used.
+</pre>
+  The DBFOpen() function should be used to establish access to an existing
+  xBase format table file.  The returned DBFHandle is passed to other
+  access functions, and DBFClose() should be invoked to recover resources, and
+  flush changes to disk when complete.  The DBFCreate() function should
+  called to create new xBase files.  As a convenience, DBFOpen() can be
+  called with the name of a .shp or .shx file, and it will figure out the
+  name of the related .dbf file.<p>
+<!-------------------------------------------------------------------------->
+<h2>DBFCreate()</h2>
+<pre>
+DBFHandle DBFCreate( const char * pszDBFFile );
+  pszDBFFile:		The name of the xBase (.dbf) file to create.
+</pre>
+  The DBFCreate() function creates a new xBase format file with the given
+  name, and returns an access handle that can be used with other DBF functions.
+  The newly created file will have no fields, and no records.  Fields should
+  be added with DBFAddField() before any records add written.
+<!-------------------------------------------------------------------------->
+<h2>DBFGetFieldCount()</h2>
+<pre>
+int DBFGetFieldCount( DBFHandle hDBF );
+  hDBF:		The access handle for the file to be queried, as returned
+                by DBFOpen(), or DBFCreate().
+</pre>
+  The DBFGetFieldCount() function returns the number of fields currently
+  defined for the indicated xBase file.
+<!-------------------------------------------------------------------------->
+<h2>DBFGetRecordCount()</h2>
+<pre>
+int DBFGetRecordCount( DBFHandle hDBF );
+  hDBF:		The access handle for the file to be queried, as returned by
+		DBFOpen(), or DBFCreate().
+</pre>
+  The DBFGetRecordCount() function returns the number of records that
+  exist on the xBase file currently.  Note that with shape files one xBase
+  record exists for each shape in the .shp/.shx files.<p>
+<!-------------------------------------------------------------------------->
+<h2>DBFGetFieldIndex()</h2>
+<pre>
+int DBFGetFieldIndex( DBFHandle hDBF, const char *pszFieldName );
+  hDBF:		The access handle for the file to be queried, as returned by
+		DBFOpen(), or DBFCreate().
+  pszFieldName: Name of the field to search for.
+</pre>
+  Returns the index of the field matching this name, or -1 on failure.  The
+  comparison is case insensitive.  However, lengths must match exactly.<p>
+<!-------------------------------------------------------------------------->
+<h2>DBFGetFieldInfo()</h2>
+<pre>
+DBFFieldType DBFGetFieldInfo( DBFHandle hDBF, int iField, char * pszFieldName,
+                              int * pnWidth, int * pnDecimals );
+  hDBF:		The access handle for the file to be queried, as returned by
+		DBFOpen(), or DBFCreate().
+  iField:	The field to be queried.  This should be a number between
+                0 and n-1, where n is the number fields on the file, as
+                returned by DBFGetFieldCount().
+  pszFieldName:	If this pointer is not NULL the name of the requested field
+		will be written to this location.  The pszFieldName buffer
+                should be at least 12 character is size in order to hold
+		the longest possible field name of 11 characters plus a
+                terminating zero character.
+  pnWidth:	If this pointer is not NULL, the width of the requested field
+		will be returned in the int pointed to by pnWidth.  This is
+                the width in characters.
+  pnDecimals:	If this pointer is not NULL, the number of decimal places
+                precision defined for the field will be returned.  This is
+                zero for integer fields, or non-numeric fields.
+</pre>
+  The DBFGetFieldInfo() returns the type of the requested field, which is
+  one of the DBFFieldType enumerated values.  As well, the field name, and
+  field width information can optionally be returned.  The field type returned
+  does not correspond one to one with the xBase field types.  For instance
+  the xBase field type for Date will just be returned as being FTInteger.  <p>
+<pre>
+    typedef enum {
+      FTString,			/* fixed length string field 		*/
+      FTInteger,		/* numeric field with no decimals 	*/
+      FTDouble,			/* numeric field with decimals 		*/
+      FTLogical,		/* logical field.                       */
+      FTInvalid                 /* not a recognised field type 		*/
+    } DBFFieldType;
+</pre>
+<!-------------------------------------------------------------------------->
+<h2>DBFAddField()</h2>
+<pre>
+int DBFAddField( DBFHandle hDBF, const char * pszFieldName,
+                 DBFFieldType eType, int nWidth, int nDecimals );
+  hDBF:		The access handle for the file to be updated, as returned by
+		DBFOpen(), or DBFCreate().
+  pszFieldName:	The name of the new field.  At most 11 character will be used.
+                In order to use the xBase file in some packages it may be
+                necessary to avoid some special characters in the field names
+                such as spaces, or arithmetic operators.
+  eType:	One of FTString, FTInteger or FTDouble in order to establish
+                the type of the new field.  Note that some valid xBase field
+                types cannot be created such as date fields.
+  nWidth:	The width of the field to be created.  For FTString fields this
+                establishes the maximum length of string that can be stored.
+                For FTInteger this establishes the number of digits of the
+                largest number that can
+                be represented.  For FTDouble fields this in combination
+                with the nDecimals value establish the size, and precision
+                of the created field.
+  nDecimals:    The number of decimal places to reserve for FTDouble fields.
+                For all other field types this should be zero.  For instance
+                with nWidth=7, and nDecimals=3 numbers would be formatted
+                similarly to `123.456'.
+</pre>
+  The DBFAddField() function is used to add new fields to an existing xBase
+  file opened with DBFOpen(), or created with DBFCreate().  Note that fields
+  can only be added to xBase files with no records, though this is limitation
+  of this API, not of the file format.<p>
+  The DBFAddField() return value is the field number of the new field, or
+  -1 if the addition of the field failed.<p>
+<!-------------------------------------------------------------------------->
+<h2>DBFReadIntegerAttribute()</h2>
+<pre>
+int DBFReadIntegerAttribute( DBFHandle hDBF, int iShape, int iField );
+  hDBF:		The access handle for the file to be queried, as returned by
+		DBFOpen(), or DBFCreate().
+  iShape:	The record number (shape number) from which the field value
+                should be read.
+  iField:	The field within the selected record that should be read.
+</pre>
+  The DBFReadIntegerAttribute() will read the value of one field and return
+  it as an integer.  This can be used even with FTString fields, though the
+  returned value will be zero if not interpretable as a number.<p>
+<!-------------------------------------------------------------------------->
+<h2>DBFReadDoubleAttribute()</h2>
+<pre>
+double DBFReadDoubleAttribute( DBFHandle hDBF, int iShape, int iField );
+  hDBF:		The access handle for the file to be queried, as returned by
+		DBFOpen(), or DBFCreate().
+  iShape:	The record number (shape number) from which the field value
+                should be read.
+  iField:	The field within the selected record that should be read.
+</pre>
+  The DBFReadDoubleAttribute() will read the value of one field and return
+  it as a double.  This can be used even with FTString fields, though the
+  returned value will be zero if not interpretable as a number.<p>
+<!-------------------------------------------------------------------------->
+<h2>DBFReadStringAttribute()</h2>
+<pre>
+const char *DBFReadStringAttribute( DBFHandle hDBF, int iShape, int iField );
+  hDBF:		The access handle for the file to be queried, as returned by
+		DBFOpen(), or DBFCreate().
+  iShape:	The record number (shape number) from which the field value
+                should be read.
+  iField:	The field within the selected record that should be read.
+</pre>
+  The DBFReadStringAttribute() will read the value of one field and return
+  it as a string.  This function may be used on any field type (including
+  FTInteger and FTDouble) and will return the string representation stored
+  in the .dbf file.  The returned pointer is to an internal buffer
+  which is only valid untill the next DBF function call.  It's contents may
+  be copied with normal string functions such as strcpy(), or strdup().  If
+  the TRIM_DBF_WHITESPACE macro is defined in shapefil.h (it is by default)
+  then all leading and trailing space (ASCII 32) characters will be stripped
+  before the string is returned.<p>
+<!-------------------------------------------------------------------------->
+<h2>DBFIsAttributeNULL()</h2>
+<pre>
+int DBFIsAttributeNULL( DBFHandle hDBF, int iShape, int iField );
+  hDBF:		The access handle for the file to be queried, as returned by
+		DBFOpen(), or DBFCreate().
+  iShape:	The record number (shape number) from which the field value
+                should be read.
+  iField:	The field within the selected record that should be read.
+</pre>
+  This function will return TRUE if the indicated field is NULL valued
+  otherwise FALSE.  Note that NULL fields are represented in the .dbf file
+  as having all spaces in the field.  Reading NULL fields will result in
+  a value of 0.0 or an empty string with the other DBFRead*Attribute()
+  functions.<p>
+<!-------------------------------------------------------------------------->
+<h2>DBFWriteIntegerAttribute</h2>
+<pre>
+int DBFWriteIntegerAttribute( DBFHandle hDBF, int iShape, int iField,
+                              int nFieldValue );
+  hDBF:		The access handle for the file to be written, as returned by
+		DBFOpen(), or DBFCreate().
+  iShape:	The record number (shape number) to which the field value
+                should be written.
+  iField:	The field within the selected record that should be written.
+  nFieldValue:	The integer value that should be written.
+</pre>
+The DBFWriteIntegerAttribute() function is used to write a value to a numeric
+field (FTInteger, or FTDouble).  If the write succeeds the value TRUE will
+be returned, otherwise FALSE will be returned.  If the value is too large to
+fit in the field, it will be truncated and FALSE returned.<p>
+<!-------------------------------------------------------------------------->
+<h2>DBFWriteDoubleAttribute()</h2>
+<pre>
+int DBFWriteDoubleAttribute( DBFHandle hDBF, int iShape, int iField,
+                             double dFieldValue );
+  hDBF:		The access handle for the file to be written, as returned by
+		DBFOpen(), or DBFCreate().
+  iShape:	The record number (shape number) to which the field value
+                should be written.
+  iField:	The field within the selected record that should be written.
+  dFieldValue:	The floating point value that should be written.
+</pre>
+The DBFWriteDoubleAttribute() function is used to write a value to a numeric
+field (FTInteger, or FTDouble).  If the write succeeds the value TRUE will
+be returned, otherwise FALSE will be returned.  If the value is too large to
+fit in the field, it will be truncated and FALSE returned.<p>
+<!-------------------------------------------------------------------------->
+<h2>DBFWriteStringAttribute()</h2>
+<pre>
+int DBFWriteStringAttribute( DBFHandle hDBF, int iShape, int iField,
+                             const char * pszFieldValue );
+  hDBF:		The access handle for the file to be written, as returned by
+		DBFOpen(), or DBFCreate().
+  iShape:	The record number (shape number) to which the field value
+                should be written.
+  iField:	The field within the selected record that should be written.
+  pszFieldValue: The string to be written to the field.
+</pre>
+The DBFWriteStringAttribute() function is used to write a value to a string
+field (FString).  If the write succeeds the value TRUE willbe returned,
+otherwise FALSE will be returned.  If the value is too large to
+fit in the field, it will be truncated and FALSE returned.<p>
+<!-------------------------------------------------------------------------->
+<h2>DBFWriteNULLAttribute()</h2>
+<pre>
+int DBFWriteNULLAttribute( DBFHandle hDBF, int iShape, int iField );
+  hDBF:		The access handle for the file to be written, as returned by
+		DBFOpen(), or DBFCreate().
+  iShape:	The record number (shape number) to which the field value
+                should be written.
+  iField:	The field within the selected record that should be written.
+</pre>
+The DBFWriteNULLAttribute() function is used to clear the indicated field
+to a NULL value.  In the .dbf file this is represented by setting the entire
+field to spaces.  If the write succeeds the value TRUE willbe returned,
+otherwise FALSE will be returned.<p>
+<!-------------------------------------------------------------------------->
+<h2>DBFClose()</h2>
+<pre>
+void DBFClose( DBFHandle hDBF );
+  hDBF:		The access handle for the file to be closed.
+</pre>
+  The DBFClose() function will close the indicated xBase file (opened with
+  DBFOpen(), or DBFCreate()), flushing out all information to the file on
+  disk, and recovering any resources associated with having the file open.
+  The file handle (hDBF) should not be used again with the DBF API after
+  calling DBFClose().<p>
+<!-------------------------------------------------------------------------->
+<h2>DBFIsRecordDeleted()</h2>
+<pre>
+int DBFIsRecordDeleted( DBFHandle hDBF, int iShape );
+  hDBF:		The access handle for the file to be checked.
+  iShape:       The record index to check.
+</pre>
+  Returns TRUE (non-zero) if the record is marked for deletion, otherwise
+  it returns FALSE.<p>
+<!-------------------------------------------------------------------------->
+<h2>DBFMarkRecordDeleted()</h2>
+<pre>
+int DBFMarkRecordDeleted( DBFHandle hDBF, int iShape, int bIsDeleted );
+  hDBF:		The access handle for the file.
+  iShape:       The record index to update.
+  bIsDeleted:   TRUE to mark record deleted, or FALSE to undelete it.
+</pre>
+  Returns TRUE on success, or FALSE on error.<p>
+<!-------------------------------------------------------------------------->
+<h2>DBFGetNativeFieldType()</h2>
+<pre>
+char DBFGetNativeFieldType( DBFHandle hDBF, int iField );
+  hDBF:		The access handle for the file.
+  iField:       The field index to query.
+</pre>
+  This function returns the DBF type code of the indicated field. It will
+  be one of:<p>
+<ul>
+<li> 'C' (String)
+<li> 'D' (Date)
+<li> 'F' (Float)
+<li> 'N' (Numeric, with or without decimal)
+<li> 'L' (Logical)
+<li> 'M' (Memo: 10 digits .DBT block ptr)
+<li> ' ' (field out of range)
+</ul>
+</body>
+</html>

data/ext/shp/shapelib/web/index.html ADDED Viewed

@@ -0,0 +1,235 @@
+<html>
+<head>
+<title>Shapefile C Library V1.2</title>
+<link href="http://www.maptools.org/maptools.css" rel="stylesheet" type="text/css">
+</head>
+<body>
+<h1>Shapefile C Library V1.2</h1>
+<h2>Purpose</h2>
+The Shapefile C Library provides the ability to write simple C programs
+for reading, writing and updating (to a limited extent) ESRI Shapefiles,
+and the associated attribute file (.dbf).<p>
+<h2>Supporting Information</h2>
+<ul>
+<li> <a href="shp_api.html">Shapefile API Docs</a>
+<li> <a href="dbf_api.html">DBF/xBase API Docs</a>
+<li> <a href="shapelib-tools.html">Shapefile Tools Docs</a>
+<li> <a href="release.html">Release Notes</a>
+<li> <a href="manifest.html">Shapelib File Manifest</a>
+<li> <a href="license.html">Shapelib Licensing Terms</a>
+</ul>
+<h2>What is a Shapefile?</h2>
+If you don't know, you probably don't need this library.  The Shapefile
+format is a working and interchange format promulagated by
+<a href="http://www.esri.com/">ESRI</a> for simple vector data with attributes.
+<p>
+An excellent <a href="dl/shapefile.pdf">white paper</a> on the shapefile format
+is available from ESRI,
+but it is .pdf format, so you will need Adobe Acrobat to browse it.<p>
+The file format actually consists of three files.<p>
+<pre>
+XXX.shp - holds the actual vertices.
+XXX.shx - hold index data pointing to the structures in the .shp file.
+XXX.dbf - holds the attributes in xBase (dBase) format.
+</pre>
+<h2>Download</h2>
+Source code, and some other odds and ends can be downloaded from
+<a href="http://download.osgeo.org/shapelib">http://download.osgeo.org/shapelib</a> or <a href="http://shapelib.maptools.org/dl">http://shapelib.maptools.org/dl</a>.<p>
+Shapelib is available for anonymous CVS access:
+<pre>
+  cvs -d :pserver:cvsanon@cvs.maptools.org:/cvs/maptools/cvsroot login
+  Password: (hit enter)
+  cvs -d :pserver:cvsanon@cvs.maptools.org:/cvs/maptools/cvsroot co shapelib
+</pre>
+<h2>Bugs, Maintainance and Support</h2>
+This library is maintained by <a href="http://pobox.com/~warmerdam">Frank
+Warmerdam</a>.  Please send me bug reports, patches and suggestions for the
+library via the <a href="http://bugzilla.maptools.org/enter_bug.cgi?product=Shapelib">maptools.org Bugzilla</a>.  Shapelib bugs can also be
+<a href="http://bugzilla.maptools.org/query.cgi?product=Shapelib">queried</a>.
+<p>
+Shapelib is hosted at
+<a href="http://shapelib.maptools.org">shapelib.maptools.org</a>.   A mailing
+list for discussion of how to use shapelib, and announcing new releases
+<a href="http://lists.maptools.org/mailman/listinfo/shapelib/">is
+available</a>.  To only find out about new releases of Shapelib select the
+"<i>Subscribe to new releases</i>" option from the link at
+<a href="http://freshmeat.net/projects/shapelib/">Freshmeat</a>.<p>
+<h2>Credits</h2>
+I didn't start this section anywhere near soon enough, so alot of earlier
+contributors to Shapelib are lost in pre-history.
+<ul>
+<li> Bill Miller (NY-DOT) for shputils.c
+<li> Carl Anderson for the contents of the contrib directory, and
+the "tuple" additions to dbfopen.c.
+<li> Andrea Giacomelli for patches for dbfopen.c.
+<li> Doug Matthews for portability improvements.
+<li> Jan-Oliver Wagner for convincing me to make it available under LGPL,
+shared library support, and various other patches.
+<li> Dennis Christopher (of Avenza) for testing and bug fixes.
+<li> Miko Syrj� (of 3D-system Oy) for a record size bug fix.
+<li> Steven Lime and Curtis Hill for help with NULL shapes.
+<li> Jim Matthews for support of NULL attributes in dbf files.
+<li> <a href="http://www.pcigeomatics.com/">PCI Geomatics</a> who let me
+release a modified version of their shapefile code in the beginning and
+who hosted shapelib for years.
+</ul>
+<h2>In Memorium</h2>
+I would like to dedicate Shapelib to the memory of Sol Katz.  While I never
+met him in person, his generous contributions to the GIS community took
+many forms, including free distribution of a variety of GIS translators
+with source.  The fact that he used this Shapelib in some of his utilities,
+and thanked me was a great encouragement to me.  I hope I can do his memory
+honour by trying to contribute in a similar fashion.<p>
+<h2>Portability</h2>
+The Shapefile C Library should port easily to 32bit systems with ANSI C
+compilers.  It should work on 64 bit architectures (such as the DEC AXP).<p>
+Care should also be taken to pass the binary access flag into SHPOpen()
+and DBFOpen() when operating on systems with special text file translation
+such as MSDOS.<p>
+The shputils.c module is contributed, and may not take the same approach
+to portability as the rest of the package.<p>
+On Linux, and most unix systems it should be possible to build and
+install shapefile support as a shared library using the "lib" and "lib_install"
+targets of the Makefile.  Note that this Makefile doesn't use autoconf
+mechanisms and will generally require some hand tailoring for your environment.
+<h2>Limitations</h2>
+<ul>
+<li> You can't modify the vertices of existing structures (though you
+   can update the attributes of existing structures, and create new
+   structures).<p>
+<li> Not written in such a way as to be particularly fast.  This is
+particularly true of the 1.2 API.  For applications more concerned with
+speed it may be worth using the V1.1 API.<p>
+<li> Doesn't set the last access time properly in the .dbf files.<p>
+<li> There is no way to synchronize information to the file except to close it.
+<p>
+<li> Poor error checking and reporting.<p>
+<li> Not professionally supported (well it can be, if you want to pay).<p>
+<li> Some aspects of xBase files not supported, though I believe they are
+not used by ESRI.<p>
+<li> The application must keep the .dbf file in sync with the .shp/.shx
+files through appropriate use of the DBF and SHP APIs.<p>
+<li> No support for the undocumented .sbn/.sbx spatial index files.<p>
+</ul>
+<h2>Other Shapefile Resources</h2>
+<ul>
+<li> <a href="dl/shapefile.pdf">Shapefile Format Specifications (pdf)</a><p>
+<li> <a href="http://www.clicketyclick.dk/databases/xbase/format/">Xbase (.dbf) File Format Description</a>. <p>
+<li> <a href="codepage.html">Language ID / Code Page mappings</a><p>
+<li> Shapelib is used within the multiformat
+<a href="http://ogr.maptools.org/">OGR</a> library.  If you are looking for a
+high level C++ library with support for many geospatial vector formats you
+might want to check it out.<p>
+<li> Ari Jolma has produced an initial <b>perl</b> binding on top of shapelib,
+which can be found at CPAN as Geo::ShapeFile under the
+<a href="http://www.cpan.org/modules/by-module/Geo/">Geo</a> module.
+<p>
+<li> Bernhard Herzog has produced <b>python</b> bindings for Shapelib with
+SWIG, available at <a href="http://ftp.intevation.de/users/bh/pyshapelib/">http://ftp.intevation.de/users/bh/pyshapelib</a>.  A new version not using swig is
+available as <a href="http://wald.intevation.org/plugins/scmsvn/viewcvs.php/trunk/thuban/libraries/pyshapelib/?root=thuban">part of Thuban</a>.<p>
+<li> <a href="http://www.triplexware.huckfinn.de/shpapi.html">Delphi</a>
+bindings for Shapelib courtesy of Alexander Weidauer.<p>
+<li> Miguel Filgueiras has implemented
+<a href="http://www.ncc.up.pt/gpsmanshp/">Tcl</a> bindings for Shapelib
+as part of <a href="http://www.ncc.up.pt/gpsman/">GPSMan</a>.<p>
+<li> David Gancarz has implemented a Microsoft
+<a href="dl/contrib/DotNetArchive.zip">.NET wrapper</a> for
+Shapelib.   An example of using shapelib with VB6 is also icluded in the .NET wrapper project file.<p>
+<li> Andrey Hristov (php at hristov dot com) has developed a PHP extension
+based on Shapelib.  It can be found in CVS at http://cvs.php.net/pecl/shp.<p>
+<li> Toyoda Eizi has developed Ruby bindings found at
+<a href="http://sourceforge.net/projects/ruby-shapelib">http://sourceforge.net/projects/ruby-shapelib</a>.<p>
+<li> Davide Cesari has developed FORTRAN bindings that can be found at
+<a href"http://www.webalice.it/o.drofa/davide/shapelib-fortran/">
+http://www.webalice.it/o.drofa/davide/shapelib-fortran</a>.
+<li> Jan-Oliver Wagner has implemented a commandline program
+(<b>gen2shp</b>) for producing shapefiles from Arc/Info Generate format ASCII
+files.  He maintains a <a href="http://intevation.de/~jan/gen2shp">web page</a> for his work. <p>
+<li> Tom Russo has implemented a shpcs2cs program, which reprojects shapefiles
+using arguments similar to the PROJ.4 cs2cs program including datum conversion.
+Use as an alternate to the contrib/shpproj which doesn't do datums.  It is
+available at the bottom of Tom's <a href="http://www.swcp.com/~russo/shape_web/">Xastir Shapefile Resources</a> page. <p>
+<li>
+Andrew Williamson's
+<a href="http://www.geocities.com/SiliconValley/Haven/2295/useful.html">Useful
+Scripts and Stuff</a> page for ArcView, which includes ShapeChecker.<p>
+<li> The University of Bonn <a href="http://katla.giub.uni-bonn.de/sfjava/">
+sf4java</a> project apparently includes Java classes for reading Shapefiles.<p>
+<li> The <a href="http://gis.esri.com/arcscripts/details.cfm?CFGRIDKEY=628102085">ShapeIO2</a> Visual Basic libraries may be of interest to those wanting
+VB access to Shapefiles.  Also available <a href="http://shapelib.maptools.org/dl/contrib/ShapeIO2.zip">locally</a>.<p>
+<li> The <a href="http://arcscripts.esri.com/details.asp?dbid=11810">ShapeFile Read/Write OCX</a> is another option for Visual Basic programmers.<p>
+<li> <a href="http://www.casa.ucl.ac.uk/sanjay/software_isovistanalyst.htm">Isovist Analyst</a> is a sort-of-free isovist generating extension for
+ArcView using shapelib.<p>
+<li> <a href="http://www.obviously.com/gis/shpdiff/">shpdiff</a> utility
+by Bryce Nesbitt.<p>
+<li> <a href="http://www.aequometer.de/">Aequometer</a>: a program for
+MS Excel to calculate the area of polygons and export as shapefiles.<p>
+</ul>
+</body>
+</html>