Fix WANTLIB after kerb/gdal update, new MASTER_SITES. Actually install
the README by adding it to PLIST.. and use enough XXXX's in mktemp call
during regress tests.
See http://mapserver.org/development/announce/6-2.html for a list of new
features in the 6.2 branch.
- Uses its own local copy of agg (as mapnik..)
- now uses libtool and installs a library. Adapt chroot setups as needed.
- provides an install target, so install perl examples and mapscript.ini
in post-install.
- dont install php examples, they're badly outdated
gimgtools is a set of command-line tools to examine and manipulate
Garmin IMG (the map format) files. The included tools are:
* gimgunlock: Unlock a locked map so that it can be used on ALL devices.
* gimgxor: Unscramble XOR'd map files.
* gimginfo: Print information of the map.
* gimgextract: Extract the IMG sections.
* gimgch: Hexdump and compare section header of two or more IMGs.
ok sebastia@
SpatiaLite is an open source library intended to extend the SQLite core
to support fully fledged Spatial SQL capabilities. It provides a
complete and powerful Spatial DBMS (mostly OGC-SFS compliant).
It is to sqlite what postgis is to postgresql.
freexl-1.0.0e: extract valid data from within an Excel spreadsheet
readosm-1.0.0b: library to extract data from OSM files
libspatialite-4.0.0: sqlite extented with spatial SQL capabilities
libgaiagraphics-0.5: common-utility raster handling methods, used by spatialite_gui
librasterlite-1.1f: store rasters coverages within spatialite, used byspatialite_gis
spatialite-tools-4.0.0: CLI tools for spatialite
spatialite_gis-1.0.0c: minimalistic GIS on top of spatialite and rasterlite
spatialige_gui-1.6.0: GUI for spatialite
ok/tweaks ajacoutot@
The purpose of this library is to provide:
* An extensible framework that will support robust spatial indexing
methods.
* Support for sophisticated spatial queries. Range, point location,
nearest neighbor and k-nearest neighbor as well as parametric queries
(defined by spatial constraints) should be easy to deploy and run.
* Easy to use interfaces for inserting, deleting and updating
information.
* Wide variety of customization capabilities. Basic index and storage
characteristics like the page size, node capacity, minimum fan-out,
splitting algorithm, etc. should be easy to customize.
* Index persistence. Internal memory and external memory structures
should be supported. Clustered and non-clustered indices should be
easy to be persisted.
ok ajacoutot@
