Proceed to GeoCommunity Home Page


SpatialNewsGIS Data DepotGeoImaging ChannelGIS and MappingSoftwareGIS JobsGeoBids-RFPsGeoCommunity MarketplaceGIS Event Listings
HomeLoginAccountsAboutContactAdvertiseSearchFAQsForumsCartFree Newsletter

Sponsored by:


TOPICS
Today's News

Submit News

Feature Articles

Product Reviews

Education

News Affiliates

Discussions

Newsletters

Email Lists

Polls

Editor's Corner


SpatialNews Daily Newswire!
Subscribe now!

Latest Industry Headlines
SiteVision GIS Partnership With City of Roanoke VA Goes Live
Garmin® Introduces Delta™ Upland Remote Trainer with Beeper
Caliper Offers Updated Chile Data for Use with Maptitude 2013
Southampton’s Go! Rhinos Trail Mapped by Ordnance Survey
New Approach to Measuring Coral Growth Offers Valuable Tool for Reef Managers
Topo ly - Tailor-Fit for Companies' Online Mapping Needs

Latest GeoBids-RFPs
Nautical Charts*Poland
Software & Telemetry GPS
Spatial Data Management-DC
Geospatial and Mapping-DC
Next-Gen 911-MO

Recent Job Opportunities
Planner/GIS Specialist
Team Leader- Grape Supply Systems
Geospatial Developer

Recent Discussions
Raster images
cartographic symbology
Telephone Exchange areas in Europe
Problem showcasing Vector map on Windows CE device
Base map

GeoCommunity Mailing List
 
Mailing List Archives

Subject: Re: [gislist] Shapefile DBF Specification
Date:  10/27/2005 12:25:03 PM
From:  Quantitative Decisions



At 12:40 PM 10/27/2005 -0400, Frank Warmerdam wrote:
>But in my mind it is unclear what variations of .dbf file are legal with
>shapefiles.

The behavior of ArcView 3.x has been the de facto enforcer of the shapefile
standard, because in the majority of cases shapefiles are produced for use
with AV 3.

dBase III and IV files created by most, but not all, software, will
work. Some software does not exactly conform to the .dbf specs in
apparently harmless ways (such as writing bytes in reserved portions of the
header) and ArcView 3.x usually chokes on their .dbf output--it seems
pretty finicky--, so you have to test. (It's interesting, though, that AV
will happily read and write dBase III/IV files that contain duplicate field
names, something which I believe is invalid according to the spec.) The
dBase III and IV files produced by any recent version of Excel (going back
to '95) are ok. I recall AV does not read dBase V files. I have not
tested with dBase II files but don't expect those to work, either. AV does
not read dBase memo (.dbt) files nor does it read the various index files
(such as those developed for FoxBase/FoxPro, Clipper, or the original dBase).

It's useful to know that AV ignores the deletion bytes in the dBase file
records: it reads them all, whether they're marked as deleted or not.

--Bill Huber

_______________________________________________
gislist mailing list
gislist@lists.geocomm.com
http://lists.geocomm.com/mailman/listinfo/gislist

_________________________________
This list is brought to you by
The GeoCommunity
http://www.geocomm.com/

Sponsored by:

For information
regarding
advertising rates
Click Here!

Copyright© 1995-2012 MindSites Group / Privacy Policy

GeoCommunity™, Wireless Developer Network™, GIS Data Depot®, and Spatial News™
including all logos and other service marks
are registered trademarks and trade communities of
MindSites Group