Free dbf software for linux

jdbfviewer allows you to display dbf files in a JTable view (and optionally delete rows). Not all versions of dbf are supported. The memo-field isnt tested. No future development is planned.

This is work in progress, without progress.

I created the viewer to view lots of dbf-Files, and did not add any functionality you would probably expect, but which I didnt need.

Later I was asked to add an option to delete rows, which I only started to implement, but without the convenience to select a filename for example.

Another missing feature is, to change values of fields, but I guess its not too much work, to get it done.

XBase is a Perl module for reading and writing the dbf files.

SYNOPSIS

use XBase;
my $table = new XBase "dbase.dbf" or die XBase->errstr;
for (0 .. $table->last_record) {
my ($deleted, $id, $msg)
= $table->get_record($_, "ID", "MSG");
print "$id:t$msgn" unless $deleted;
}

This module can read and write XBase database files, known as dbf in dBase and FoxPro world. It also reads memo fields from the dbt and fpt files, if needed. An alpha code of reading index support for ndx, ntx, mdx, idx and cdx is available for testing -- see the DBD::Index(3) man page. Module XBase provides simple native interface to XBase files. For DBI compliant database access, see the DBD::XBase and DBI modules and their man pages.
The following methods are supported by XBase module:

General methods

new

Creates the XBase object, loads the info about the table form the dbf file. The first parameter should be the name of existing dbf file (table, in fact) to read. A suffix .dbf will be appended if needed. This method creates and initializes new object, will also check for memo file, if needed.

The parameters can also be specified in the form of hash: value of name is then the name of the table, other flags supported are:

memofile specifies non standard name for the associated memo file. By default its the name of the dbf file, with extension dbt or fpt.

ignorememo ignore memo file at all. This is usefull if youve lost the dbt file and you do not need it. Default is false.

memosep separator of memo records in the dBase III dbt files. The standard says it should be "x1ax1a". There are however implamentations that only put in one "x1a". XBase.pm tries to guess which is valid for your dbt but if it fails, you can tell it yourself.

nolongchars prevents XBase to treat the decimal value of character fields as high byte of the length -- there are some broken products around producing character fields with decimal values set.

my $table = new XBase "table.dbf" or die XBase->errstr;

my $table = new XBase "name" => "table.dbf",
"ignorememo" => 1;

recompute_lastrecno forces XBase.pm to disbelieve the information about the number of records in the header of the dbf file and recompute the number of records. Use this only if you know that some other software of yours produces incorrect headers.

close

Closes the object/file, no arguments.

create

Creates new database file on disk and initializes it with 0 records. A dbt (memo) file will be also created if the table contains some memo fields. Parameters to create are passed as hash.

You can call this method as method of another XBase object and then you only need to pass name value of the hash; the structure (fields) of the new file will be the same as of the original object.

If you call create using class name (XBase), you have to (besides name) also specify another four values, each being a reference to list: field_names, field_types, field_lengths and field_decimals. The field types are specified by one letter strings (C, N, L, D, ...). If you set some value as undefined, create will make it into some reasonable default.

my $newtable = $table->create("name" => "copy.dbf");

my $newtable = XBase->create("name" => "copy.dbf",
"field_names" => [ "ID", "MSG" ],
"field_types" => [ "N", "C" ],
"field_lengths" => [ 6, 40 ],
"field_decimals" => [ 0, undef ]);

Other attributes are memofile for non standard memo file location, codepage to set the codepage flag in the dbf header (it does not affect how XBase.pm reads or writes the data though, just to make FoxPro happy), and version to force different version of the dbt (dbt) file. The default is the version of the object from which you create the new one, or 3 if you call this as class method (XBase->create).

The new file mustnt exist yet -- XBase will not allow you to overwrite existing table. Use drop (or unlink) to delete it first.

drop

This method closes the table and deletes it on disk (including associated memo file, if there is any).

last_record

Returns number of the last record in the file. The lines deleted but present in the file are included in this number.

last_field

Returns number of the last field in the file, number of fields minus 1.

field_names, field_types, field_lengths, field_decimals

Return list of field names and so on for the dbf file.

field_type, field_length, field_decimal

For a field name, returns the appropriate value. Returns undef if the field doesnt exist in the table.

Geo::ShapeFile is a Perl extension for handling ESRI GIS Shapefiles.

SYNOPSIS

use Geo::ShapeFile;

my $shapefile = new Geo::ShapeFile("roads");

for(1 .. $shapefile->shapes()) {
my $shape = $shapefile->get_shp_record($_);
# see Geo::ShapeFile::Shape docs for what to do with $shape

my %db = $shapefile->get_dbf_record($_);
}

ABSTRACT

The Geo::ShapeFile module reads ESRI ShapeFiles containing GIS mapping data, it has support for shp (shape), shx (shape index), and dbf (data base) formats.

The Geo::ShapeFile module reads ESRI ShapeFiles containing GIS mapping data, it has support for shp (shape), shx (shape index), and dbf (data base) formats.

METHODS

new($filename_base)

Creates a new shapefile object, the only argument it takes is the basename for your data (dont include the extension, the module will automatically find the extensions it supports). For example if you have data files called roads.shp, roads.shx, and roads.dbf, use new Geo::ShapeFile("roads"); to create a new object, and the module will load the data it needs from the files as it needs it.

type_is($numeric_type)

Returns true if the major type of this data file is the same as the type passed to type_is().

get_dbf_record($record_index)

Returns the data from the dbf file associated with the specified record index (shapefile indexes start at 1). If called in a list context, returns a hash, if called in a scalar context, returns a hashref.

x_min() x_max() y_min() y_max()

m_min() m_max() z_min() z_max()

Returns the minimum and maximum values for x, y, z, and m fields as indicated in the shp file header.

upper_left_corner() upper_right_corner()
lower_left_corner() lower_right_corner()

Returns a Geo::ShapeFile::Point object indicating the respective corners.

height() width()

Returns the height and width of the area contained in the shp file. Note that this likely does not return miles, kilometers, or any other useful measure, it simply returns x_max - x_min, or y_max - y_min. Whether this data is a useful measure or not depends on your data.

corners()

Returns a four element array consisting of the corners of the area contained in the shp file. The corners are listed clockwise starting with the upper left. (upper_left_corner, upper_right_corner, lower_right_corner, lower_left_corner)
area_contains_point($point,$x_min,$y_min,$x_max,$y_max)

Utility function that returns true if the Geo::ShapeFile::Point object in point falls within the bounds of the rectangle defined by the area indicated. See bounds_contains_point() if you want to check if a point falls within the bounds of the current shp file.

bounds_contains_point($point)

Returns true if the specified point falls within the bounds of the current shp file.

file_version()

Returns the ShapeFile version number of the current shp/shx file.

shape_type()

Returns the shape type contained in the current shp/shx file. The ESRI spec currently allows for a file to contain only a single type of shape (null shapes are the exception, they may appear in any data file). This returns the numeric value for the type, use type() to find the text name of this value.

shapes()

Returns the number of shapes contained in the current shp/shx file. This is the value that allows you to iterate through all the shapes using for(1 .. $obj->shapes()) {.

records()

Returns the number of records contained in the current data. This is similar to
shapes(), but can be used even if you dont have shp/shx files, so you can access data that is stored as dbf, but does not have shapes associated with it.

shape_type_text()

Returns the shape type of the current shp/shx file (see shape_type()), but as the human-readable string type, rather than an integer.

get_shx_record($record_index) =item get_shx_record_header($record_index)
Get the contents of an shx record or record header (for compatibility with the other get_* functions, both are provided, but in the case of shx data, they return the same information). The return value is a two element array consisting of the offset in the shp file where the indicated record begins, and the content length of that record.

get_shp_record_header($record_index)

Retrieve an shp record header for the specified index. Returns a two element array consisting of the record number and the content length of the record.

get_shp_record($record_index)

Retrieve an shp record for the specified index. Returns a Geo::ShapeFile::Shape object.

shapes_in_area($x_min,$y_min,$x_max,$y_max)

Returns an array of integers, consisting of the indices of the shapes that overlap with the area specified. Currently this is a very oversimplified function that actually finds shapes that have any point that falls within the specified bounding box. Currently it may miss some shapes that actually do overlap with the specified area, if there are two points outside the area that cause an edge to pass through the area, but neither of the end points of that edge actually fall within the area specified. Patches to make this function more useful would be welcome.

check_in_area($x1_min,$y1_min,$x1_max,$y1_max,$x2_min,$x2_max,$y2_min,$y2_max)

Returns true if the two specified areas overlap.

bounds()

Returns the bounds for the current shp file. (x_min, y_min, x_max, y_max)

shx_handle() shp_handle() dbf_handle()

Returns the file handles associated with the respective data files.

type($shape_type_number)

Returns the name of the type associated with the given type id number.

find_bounds(@shapes)

Takes an array of Geo::ShapeFile::Shape objects, and returns a hash, with keys of x_min,y_min,x_max,y_max, with the values for each of those ranges.

GNU Oleo is a lightweight spreadsheet application.
It has internationalization support, an ncurses interface, a Motif/LessTif interface, and an autoconf/automake-based compilation process.
Current enhancements include printing and plotting.
Main features:
- Motif/LessTif interface, based on the XbaeMatrix widget
- Access to the statistics functions of the GSL (GNU Scientific Library).
- Support for opening multiple spreadsheets, each in a Motif window, at the same time.
- device independent graphics through GNU plotutils, replacing the older gnuplot interface
- more portable build through autoconf and automake
- internationalised (i18n)
- updated documentation
- ANSI C code (removed K&R stuff)
- filter mode (read file from stdin, save to stdout)
- better SYLK support
- improved printing (PostScript and PCL)
- database access (MySQL and DBF files)
- SciPlot graphics (Motif/LessTif only)
- cleaned up internals
- runs in character mode as well as in a GUI
- interface to CUPS to browse available printers

CLIP is a Clipper/XBase compatible compiler with initial support other xBase dialects. CLIP project features support for international languages and character sets.
It also features OOP, a multiplatform GUI based on GTK/GTKextra, all SIX/Comix features (including hypertext indexing), SQL and ODBC drivers, a C-API for third-party developers, a few wrappers for popular libraries (such as BZIP, GZIP, GD, Crypto, and Fcgi), a multitasking client and application server based on TCP/IP sockets, object data base utilities, and a functions library.
Main features:
- Preprocessor
- Fully compatible CA-Clipper with with some new possibilities.
- Compiler
- slight incompability with CA-Clipper, which may be resolved easily, using the "search and replace" method. In addition it can compile to C program, byte-code, dynamic library and mixed C+byte-code.
- Very fast and efficient OO-model
- Difference from CA-Clipper reveals itself in part of descriptions and making an object, but in part of using the ready objects syntax and logic of functioning is completely the same.
- It is possible to write programs on CLIP, without using other syntax excepting OOP.
- Initial support syntax from FS,CAVO,FoxPro.
- C-API
- has much more possibilities than CA-Clipper.
- Full international support
- Including adjustment on any code page of any language on any keyboard (with stelnet emulator only or on consoles), substitution of string constants during execution and changing a logic of functioning with strings, given for functions alpha, digit, lower, upper, subscripted weight factors etc.
- Support two-bytes charsets BIG5,GB , may be Korean,Japan too.
- GUI, based on GTK
- Provides using of all widgets and processing the events
- Using of dynamic libraries,
- loading and execution of the byte-code from external files ( in run-time, too ).
- Compatibility
- up to Clipper 5.3 (support of objects menu, button, check and other get-objects), as well as standard classes tbrowse,get,error.
- Are implemented a lot of CA_Tools functions, including all functions for processing the lines, dates, files, mathematicians.
- support all SIX functions and features
- MEM,DBF,DBT,FPT,NTX,CTX,CDX,NSX...
- VFP data types: datetime,currency
- RDD allows to use your own drivers, as well as use a driver, combined from several different drivers.
- RDD also allows to use only OO-style, without using of aliases
- Multitask support
- CODB - CLIP Object Data Base
- SQL
- libraries and classes for direct access to SQL-servers (PG,MySql,Oracle,Interbase)
- ODBC and ODBC bridge to Windows drivers.
- SQL-interpreter and commands, compatible with FoxPro
- Other possibilities
- Overloading operators for objects.
- Support of regular expressions.
- function for TCP/IP sockets connections
- COM_() functions
- Rushmore like technology, but more fast and efficient.
- Support of very-large-scale numbers with unlimited accuracy.
- Support of graphic files PNG,GD,JPEG and primitives like lines, rectangles, firing ranges, circumferences etc.
- Several common classes for word processorses, html/cgi programms.
- Several utilities for interpreting the patterns of the documents, www_sql,clip_bl, clip_blank, clip_sql, clip_hindex, clip_hseek etc.
- multiwindows interactive debugger.
- Supported OSes
- linux, freebsd, openBsd, SPARC & x86 solaris, IBM mainframe with TurboLinux, Win32 ( with CYGWIN development tools)
- TODO list
- Windows support
- FiveWin compatiblies.
- FoxPro compatiblies.
Enhancements:
- This release added fixes to support UTF environments, GCC 4.x, and newer Linux distributions.
- Some new utilities, functions, and documentation were added.