[DebianGIS-dev] r577 - in packages/postgis/upstream: .
autom4te.cache doc doc/html doc/man java java/ejb3
java/ejb3/src/org/postgis/ejb java/ejb3/src/org/postgis/ejb/mdb
java/ejb3/src/org/postgis/hibernate java/jdbc
java/jdbc/jtssrc/org/postgis/jts java/jdbc/src/examples
java/jdbc/src/org/postgis java/jdbc/src/org/postgis/binary
java/pljava java/pljava/src java/pljava/src/org
java/pljava/src/org/postgis
java/pljava/src/org/postgis/pljava loader lwgeom
Fabio Tranchitella
kobold at alioth.debian.org
Tue Oct 31 21:52:34 CET 2006
Author: kobold
Date: 2006-10-31 21:52:30 +0100 (Tue, 31 Oct 2006)
New Revision: 577
Added:
packages/postgis/upstream/HOWTO_RELEASE
packages/postgis/upstream/autom4te.cache/
packages/postgis/upstream/autom4te.cache/output.0
packages/postgis/upstream/autom4te.cache/requests
packages/postgis/upstream/autom4te.cache/traces.0
packages/postgis/upstream/java/ejb3/EJB3Spatial.odt
packages/postgis/upstream/java/pljava/
packages/postgis/upstream/java/pljava/README.txt
packages/postgis/upstream/java/pljava/build.xml
packages/postgis/upstream/java/pljava/functions.sql
packages/postgis/upstream/java/pljava/install.sh
packages/postgis/upstream/java/pljava/postgis_pljava.jar
packages/postgis/upstream/java/pljava/src/
packages/postgis/upstream/java/pljava/src/org/
packages/postgis/upstream/java/pljava/src/org/postgis/
packages/postgis/upstream/java/pljava/src/org/postgis/pljava/
packages/postgis/upstream/java/pljava/src/org/postgis/pljava/Aggregates.java
packages/postgis/upstream/java/pljava/src/org/postgis/pljava/HelloWorld.java
packages/postgis/upstream/java/pljava/src/org/postgis/pljava/PLJGeometry.java
packages/postgis/upstream/java/pljava/src/org/postgis/pljava/PLJtsParser.java
packages/postgis/upstream/java/pljava/src/org/postgis/pljava/PLJtsWriter.java
packages/postgis/upstream/java/pljava/update.sh
packages/postgis/upstream/loader/README.txt
packages/postgis/upstream/make_dist.sh
Removed:
packages/postgis/upstream/doc/html/postgis.html
packages/postgis/upstream/java/ejb3/lib/
Modified:
packages/postgis/upstream/CHANGES
packages/postgis/upstream/Version.config
packages/postgis/upstream/configure
packages/postgis/upstream/configure.in
packages/postgis/upstream/doc/man/pgsql2shp.1
packages/postgis/upstream/doc/man/shp2pgsql.1
packages/postgis/upstream/doc/postgis.xml
packages/postgis/upstream/java/ejb3/README.txt
packages/postgis/upstream/java/ejb3/build.xml
packages/postgis/upstream/java/ejb3/ejb3spatial.pdf
packages/postgis/upstream/java/ejb3/src/org/postgis/ejb/PersonEntity.java
packages/postgis/upstream/java/ejb3/src/org/postgis/ejb/UserBean.java
packages/postgis/upstream/java/ejb3/src/org/postgis/ejb/UserBeanRemote.java
packages/postgis/upstream/java/ejb3/src/org/postgis/ejb/mdb/IngestMDB.java
packages/postgis/upstream/java/ejb3/src/org/postgis/hibernate/GeometryType.java
packages/postgis/upstream/java/jdbc/jtssrc/org/postgis/jts/JtsBinaryParser.java
packages/postgis/upstream/java/jdbc/jtssrc/org/postgis/jts/JtsBinaryWriter.java
packages/postgis/upstream/java/jdbc/src/examples/TestAutoregister.java
packages/postgis/upstream/java/jdbc/src/org/postgis/Geometry.java
packages/postgis/upstream/java/jdbc/src/org/postgis/binary/BinaryWriter.java
packages/postgis/upstream/java/jdbc/todo.txt
packages/postgis/upstream/loader/README.pgsql2shp
packages/postgis/upstream/loader/README.shp2pgsql
packages/postgis/upstream/loader/pgsql2shp.c
packages/postgis/upstream/loader/shp2pgsql.c
packages/postgis/upstream/lwgeom/SERIALIZED_FORM
packages/postgis/upstream/lwgeom/lwgeom_geos_c.c
Log:
Imported postgis 1.1.5.
Modified: packages/postgis/upstream/CHANGES
===================================================================
--- packages/postgis/upstream/CHANGES 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/CHANGES 2006-10-31 20:52:30 UTC (rev 577)
@@ -1,5 +1,18 @@
+PostGIS 1.1.5
+2006/10/13
+ - Java:
+ - Removed obsolete synchronization from Jts code.
+ - fixed nullpointer Exception in Geometry.equals() method
+ - Added EJB3Spatial.odt to fulfill the GPL requirement of
+ distributing the "preferred form of modification"
+ - Added -S option for non-multi geometries to shp2pgsql
+ - Updated heavily outdated README files for shp2pgsql/pgsql2shp by
+ merging them with the manpages.
+ - Fixed MingW link error that was causing pgsql2shp to
+ segfault on Win32 when compiled for PostgreSQL 8.2
+
PostGIS 1.1.4
-
+2006/09/27
- Fixed support for PostgreSQL 8.2
- Fixed bug in collect() function discarding SRID of
input
Added: packages/postgis/upstream/HOWTO_RELEASE
===================================================================
--- packages/postgis/upstream/HOWTO_RELEASE 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/HOWTO_RELEASE 2006-10-31 20:52:30 UTC (rev 577)
@@ -0,0 +1,35 @@
+How to release
+~~~~~~~~~~~~~~
+ Date: 2006-09-27
+
+Versioning Scheme
+-----------------
+
+Release version is composed by REL_MAJOR_VERSION, REL_MINOR_VERSION
+and REL_MICRO_VERSION components. "REL" here matches SO for the server
+side of PostGIS, and JDBC for the java side.
+
+By default only [REL_MICRO_VERSION] increments between releases.
+
+[REL_MINOR_VERSION] is incremented (and MICRO set to 0) when minor
+additions have been introduced (one or two functions can be considered
+*micro* additions)
+
+[REL_MAJOR_VERSION] is incremented (and MICRO and MINOR set to 0) when
+a dump/reload of existing spatial databases is *REQUIRED* for things
+to work or rather *HIGHLY RECOMMENDED* to get new functionalities.
+
+Release procedure
+-----------------
+
+1) Update Version.config as specified in Versioning Scheme above.
+2) Edit CHANGES: set release date and check all notable changes are
+ been reported.
+3) Add release notes in doc/postgis.xml
+4) Tag the release:
+ $ base=http://svn.refractions.net/postgis/
+ $ rel=MAJ.MIN.MIC
+ $ svn copy -m "Tagged release $rel" $base/trunk $base/tags/$rel
+5) Run: sh make_dist.sh MAJ.MIN.MIC
+6) Publish
+7) Announce
Modified: packages/postgis/upstream/Version.config
===================================================================
--- packages/postgis/upstream/Version.config 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/Version.config 2006-10-31 20:52:30 UTC (rev 577)
@@ -4,9 +4,9 @@
# shared library / release version
SO_MAJOR_VERSION=1
SO_MINOR_VERSION=1
-SO_MICRO_VERSION=4
+SO_MICRO_VERSION=5
# JDBC code version
JDBC_MAJOR_VERSION=1
JDBC_MINOR_VERSION=1
-JDBC_MICRO_VERSION=3
+JDBC_MICRO_VERSION=5
Added: packages/postgis/upstream/autom4te.cache/output.0
===================================================================
--- packages/postgis/upstream/autom4te.cache/output.0 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/autom4te.cache/output.0 2006-10-31 20:52:30 UTC (rev 577)
@@ -0,0 +1,5845 @@
+@%:@! /bin/sh
+@%:@ Guess values for system-dependent variables and create Makefiles.
+@%:@ Generated by GNU Autoconf 2.59.
+@%:@
+@%:@ Copyright (C) 2003 Free Software Foundation, Inc.
+@%:@ This configure script is free software; the Free Software Foundation
+@%:@ gives unlimited permission to copy, distribute and modify it.
+## --------------------- ##
+## M4sh Initialization. ##
+## --------------------- ##
+
+# Be Bourne compatible
+if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then
+ emulate sh
+ NULLCMD=:
+ # Zsh 3.x and 4.x performs word splitting on ${1+"$@"}, which
+ # is contrary to our usage. Disable this feature.
+ alias -g '${1+"$@"}'='"$@"'
+elif test -n "${BASH_VERSION+set}" && (set -o posix) >/dev/null 2>&1; then
+ set -o posix
+fi
+DUALCASE=1; export DUALCASE # for MKS sh
+
+# Support unset when possible.
+if ( (MAIL=60; unset MAIL) || exit) >/dev/null 2>&1; then
+ as_unset=unset
+else
+ as_unset=false
+fi
+
+
+# Work around bugs in pre-3.0 UWIN ksh.
+$as_unset ENV MAIL MAILPATH
+PS1='$ '
+PS2='> '
+PS4='+ '
+
+# NLS nuisances.
+for as_var in \
+ LANG LANGUAGE LC_ADDRESS LC_ALL LC_COLLATE LC_CTYPE LC_IDENTIFICATION \
+ LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER \
+ LC_TELEPHONE LC_TIME
+do
+ if (set +x; test -z "`(eval $as_var=C; export $as_var) 2>&1`"); then
+ eval $as_var=C; export $as_var
+ else
+ $as_unset $as_var
+ fi
+done
+
+# Required to use basename.
+if expr a : '\(a\)' >/dev/null 2>&1; then
+ as_expr=expr
+else
+ as_expr=false
+fi
+
+if (basename /) >/dev/null 2>&1 && test "X`basename / 2>&1`" = "X/"; then
+ as_basename=basename
+else
+ as_basename=false
+fi
+
+
+# Name of the executable.
+as_me=`$as_basename "$0" ||
+$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
+ X"$0" : 'X\(//\)$' \| \
+ X"$0" : 'X\(/\)$' \| \
+ . : '\(.\)' 2>/dev/null ||
+echo X/"$0" |
+ sed '/^.*\/\([^/][^/]*\)\/*$/{ s//\1/; q; }
+ /^X\/\(\/\/\)$/{ s//\1/; q; }
+ /^X\/\(\/\).*/{ s//\1/; q; }
+ s/.*/./; q'`
+
+
+# PATH needs CR, and LINENO needs CR and PATH.
+# Avoid depending upon Character Ranges.
+as_cr_letters='abcdefghijklmnopqrstuvwxyz'
+as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
+as_cr_Letters=$as_cr_letters$as_cr_LETTERS
+as_cr_digits='0123456789'
+as_cr_alnum=$as_cr_Letters$as_cr_digits
+
+# The user is always right.
+if test "${PATH_SEPARATOR+set}" != set; then
+ echo "#! /bin/sh" >conf$$.sh
+ echo "exit 0" >>conf$$.sh
+ chmod +x conf$$.sh
+ if (PATH="/nonexistent;."; conf$$.sh) >/dev/null 2>&1; then
+ PATH_SEPARATOR=';'
+ else
+ PATH_SEPARATOR=:
+ fi
+ rm -f conf$$.sh
+fi
+
+
+ as_lineno_1=$LINENO
+ as_lineno_2=$LINENO
+ as_lineno_3=`(expr $as_lineno_1 + 1) 2>/dev/null`
+ test "x$as_lineno_1" != "x$as_lineno_2" &&
+ test "x$as_lineno_3" = "x$as_lineno_2" || {
+ # Find who we are. Look in the path if we contain no path at all
+ # relative or not.
+ case $0 in
+ *[\\/]* ) as_myself=$0 ;;
+ *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
+done
+
+ ;;
+ esac
+ # We did not find ourselves, most probably we were run as `sh COMMAND'
+ # in which case we are not to be found in the path.
+ if test "x$as_myself" = x; then
+ as_myself=$0
+ fi
+ if test ! -f "$as_myself"; then
+ { echo "$as_me: error: cannot find myself; rerun with an absolute path" >&2
+ { (exit 1); exit 1; }; }
+ fi
+ case $CONFIG_SHELL in
+ '')
+ as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in /bin$PATH_SEPARATOR/usr/bin$PATH_SEPARATOR$PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for as_base in sh bash ksh sh5; do
+ case $as_dir in
+ /*)
+ if ("$as_dir/$as_base" -c '
+ as_lineno_1=$LINENO
+ as_lineno_2=$LINENO
+ as_lineno_3=`(expr $as_lineno_1 + 1) 2>/dev/null`
+ test "x$as_lineno_1" != "x$as_lineno_2" &&
+ test "x$as_lineno_3" = "x$as_lineno_2" ') 2>/dev/null; then
+ $as_unset BASH_ENV || test "${BASH_ENV+set}" != set || { BASH_ENV=; export BASH_ENV; }
+ $as_unset ENV || test "${ENV+set}" != set || { ENV=; export ENV; }
+ CONFIG_SHELL=$as_dir/$as_base
+ export CONFIG_SHELL
+ exec "$CONFIG_SHELL" "$0" ${1+"$@"}
+ fi;;
+ esac
+ done
+done
+;;
+ esac
+
+ # Create $as_me.lineno as a copy of $as_myself, but with $LINENO
+ # uniformly replaced by the line number. The first 'sed' inserts a
+ # line-number line before each line; the second 'sed' does the real
+ # work. The second script uses 'N' to pair each line-number line
+ # with the numbered line, and appends trailing '-' during
+ # substitution so that $LINENO is not a special case at line end.
+ # (Raja R Harinath suggested sed '=', and Paul Eggert wrote the
+ # second 'sed' script. Blame Lee E. McMahon for sed's syntax. :-)
+ sed '=' <$as_myself |
+ sed '
+ N
+ s,$,-,
+ : loop
+ s,^\(['$as_cr_digits']*\)\(.*\)[$]LINENO\([^'$as_cr_alnum'_]\),\1\2\1\3,
+ t loop
+ s,-$,,
+ s,^['$as_cr_digits']*\n,,
+ ' >$as_me.lineno &&
+ chmod +x $as_me.lineno ||
+ { echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2
+ { (exit 1); exit 1; }; }
+
+ # Don't try to exec as it changes $[0], causing all sort of problems
+ # (the dirname of $[0] is not the place where we might find the
+ # original and so on. Autoconf is especially sensible to this).
+ . ./$as_me.lineno
+ # Exit status is that of the last command.
+ exit
+}
+
+
+case `echo "testing\c"; echo 1,2,3`,`echo -n testing; echo 1,2,3` in
+ *c*,-n*) ECHO_N= ECHO_C='
+' ECHO_T=' ' ;;
+ *c*,* ) ECHO_N=-n ECHO_C= ECHO_T= ;;
+ *) ECHO_N= ECHO_C='\c' ECHO_T= ;;
+esac
+
+if expr a : '\(a\)' >/dev/null 2>&1; then
+ as_expr=expr
+else
+ as_expr=false
+fi
+
+rm -f conf$$ conf$$.exe conf$$.file
+echo >conf$$.file
+if ln -s conf$$.file conf$$ 2>/dev/null; then
+ # We could just check for DJGPP; but this test a) works b) is more generic
+ # and c) will remain valid once DJGPP supports symlinks (DJGPP 2.04).
+ if test -f conf$$.exe; then
+ # Don't use ln at all; we don't have any links
+ as_ln_s='cp -p'
+ else
+ as_ln_s='ln -s'
+ fi
+elif ln conf$$.file conf$$ 2>/dev/null; then
+ as_ln_s=ln
+else
+ as_ln_s='cp -p'
+fi
+rm -f conf$$ conf$$.exe conf$$.file
+
+if mkdir -p . 2>/dev/null; then
+ as_mkdir_p=:
+else
+ test -d ./-p && rmdir ./-p
+ as_mkdir_p=false
+fi
+
+as_executable_p="test -f"
+
+# Sed expression to map a string onto a valid CPP name.
+as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'"
+
+# Sed expression to map a string onto a valid variable name.
+as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'"
+
+
+# IFS
+# We need space, tab and new line, in precisely that order.
+as_nl='
+'
+IFS=" $as_nl"
+
+# CDPATH.
+$as_unset CDPATH
+
+
+# Name of the host.
+# hostname on some systems (SVR3.2, Linux) returns a bogus exit status,
+# so uname gets run too.
+ac_hostname=`(hostname || uname -n) 2>/dev/null | sed 1q`
+
+exec 6>&1
+
+#
+# Initializations.
+#
+ac_default_prefix=/usr/local
+ac_config_libobj_dir=.
+cross_compiling=no
+subdirs=
+MFLAGS=
+MAKEFLAGS=
+SHELL=${CONFIG_SHELL-/bin/sh}
+
+# Maximum number of lines to put in a shell here document.
+# This variable seems obsolete. It should probably be removed, and
+# only ac_max_sed_lines should be used.
+: ${ac_max_here_lines=38}
+
+# Identity of this package.
+PACKAGE_NAME=
+PACKAGE_TARNAME=
+PACKAGE_VERSION=
+PACKAGE_STRING=
+PACKAGE_BUGREPORT=
+
+ac_unique_file="README.postgis"
+# Factoring default headers for most tests.
+ac_includes_default="\
+#include <stdio.h>
+#if HAVE_SYS_TYPES_H
+# include <sys/types.h>
+#endif
+#if HAVE_SYS_STAT_H
+# include <sys/stat.h>
+#endif
+#if STDC_HEADERS
+# include <stdlib.h>
+# include <stddef.h>
+#else
+# if HAVE_STDLIB_H
+# include <stdlib.h>
+# endif
+#endif
+#if HAVE_STRING_H
+# if !STDC_HEADERS && HAVE_MEMORY_H
+# include <memory.h>
+# endif
+# include <string.h>
+#endif
+#if HAVE_STRINGS_H
+# include <strings.h>
+#endif
+#if HAVE_INTTYPES_H
+# include <inttypes.h>
+#else
+# if HAVE_STDINT_H
+# include <stdint.h>
+# endif
+#endif
+#if HAVE_UNISTD_H
+# include <unistd.h>
+#endif"
+
+ac_subst_vars='SHELL PATH_SEPARATOR PACKAGE_NAME PACKAGE_TARNAME PACKAGE_VERSION PACKAGE_STRING PACKAGE_BUGREPORT exec_prefix prefix program_transform_name bindir sbindir libexecdir datadir sysconfdir sharedstatedir localstatedir libdir includedir oldincludedir infodir mandir build_alias host_alias target_alias DEFS ECHO_C ECHO_N ECHO_T LIBS CC CFLAGS LDFLAGS CPPFLAGS ac_ct_CC EXEEXT OBJEXT CXX CXXFLAGS ac_ct_CXX LN_S USE_ICONV ICONV_LDFLAGS CPP EGREP build build_cpu build_vendor build_os host host_cpu host_vendor host_os PGCONFIG PGFEINCLUDES PGBEINCLUDES PGFELIBS PGBELIBS PGBIN PGTEMPLATE LPATH PWDREGRESS USE_GEOS GEOS_DIR GEOS_LDFLAGS USE_GEOS_CAPI GEOSCONFIG USE_PROJ PROJ_DIR PROJ_LIBDIR PROJ USE_JTS JTS_INCLUDES JTS_LIBDIR JTSCONFIG FLEX DLLWRAP DLLTOOL YACC INSTALL PERL docdir XSLBASE XSLTPROC PDFXMLTEX DB2PDF JW DOC_RULE PORTNAME DLSUFFIX DLFLAGS EXE HOST_OS ELF_SYS LIB@&t at OBJS LTLIBOBJS'
+ac_subst_files=''
+
+# Initialize some variables set by options.
+ac_init_help=
+ac_init_version=false
+# The variables have the same names as the options, with
+# dashes changed to underlines.
+cache_file=/dev/null
+exec_prefix=NONE
+no_create=
+no_recursion=
+prefix=NONE
+program_prefix=NONE
+program_suffix=NONE
+program_transform_name=s,x,x,
+silent=
+site=
+srcdir=
+verbose=
+x_includes=NONE
+x_libraries=NONE
+
+# Installation directory options.
+# These are left unexpanded so users can "make install exec_prefix=/foo"
+# and all the variables that are supposed to be based on exec_prefix
+# by default will actually change.
+# Use braces instead of parens because sh, perl, etc. also accept them.
+bindir='${exec_prefix}/bin'
+sbindir='${exec_prefix}/sbin'
+libexecdir='${exec_prefix}/libexec'
+datadir='${prefix}/share'
+sysconfdir='${prefix}/etc'
+sharedstatedir='${prefix}/com'
+localstatedir='${prefix}/var'
+libdir='${exec_prefix}/lib'
+includedir='${prefix}/include'
+oldincludedir='/usr/include'
+infodir='${prefix}/info'
+mandir='${prefix}/man'
+
+ac_prev=
+for ac_option
+do
+ # If the previous option needs an argument, assign it.
+ if test -n "$ac_prev"; then
+ eval "$ac_prev=\$ac_option"
+ ac_prev=
+ continue
+ fi
+
+ ac_optarg=`expr "x$ac_option" : 'x[^=]*=\(.*\)'`
+
+ # Accept the important Cygnus configure options, so we can diagnose typos.
+
+ case $ac_option in
+
+ -bindir | --bindir | --bindi | --bind | --bin | --bi)
+ ac_prev=bindir ;;
+ -bindir=* | --bindir=* | --bindi=* | --bind=* | --bin=* | --bi=*)
+ bindir=$ac_optarg ;;
+
+ -build | --build | --buil | --bui | --bu)
+ ac_prev=build_alias ;;
+ -build=* | --build=* | --buil=* | --bui=* | --bu=*)
+ build_alias=$ac_optarg ;;
+
+ -cache-file | --cache-file | --cache-fil | --cache-fi \
+ | --cache-f | --cache- | --cache | --cach | --cac | --ca | --c)
+ ac_prev=cache_file ;;
+ -cache-file=* | --cache-file=* | --cache-fil=* | --cache-fi=* \
+ | --cache-f=* | --cache-=* | --cache=* | --cach=* | --cac=* | --ca=* | --c=*)
+ cache_file=$ac_optarg ;;
+
+ --config-cache | -C)
+ cache_file=config.cache ;;
+
+ -datadir | --datadir | --datadi | --datad | --data | --dat | --da)
+ ac_prev=datadir ;;
+ -datadir=* | --datadir=* | --datadi=* | --datad=* | --data=* | --dat=* \
+ | --da=*)
+ datadir=$ac_optarg ;;
+
+ -disable-* | --disable-*)
+ ac_feature=`expr "x$ac_option" : 'x-*disable-\(.*\)'`
+ # Reject names that are not valid shell variable names.
+ expr "x$ac_feature" : ".*[^-_$as_cr_alnum]" >/dev/null &&
+ { echo "$as_me: error: invalid feature name: $ac_feature" >&2
+ { (exit 1); exit 1; }; }
+ ac_feature=`echo $ac_feature | sed 's/-/_/g'`
+ eval "enable_$ac_feature=no" ;;
+
+ -enable-* | --enable-*)
+ ac_feature=`expr "x$ac_option" : 'x-*enable-\([^=]*\)'`
+ # Reject names that are not valid shell variable names.
+ expr "x$ac_feature" : ".*[^-_$as_cr_alnum]" >/dev/null &&
+ { echo "$as_me: error: invalid feature name: $ac_feature" >&2
+ { (exit 1); exit 1; }; }
+ ac_feature=`echo $ac_feature | sed 's/-/_/g'`
+ case $ac_option in
+ *=*) ac_optarg=`echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"`;;
+ *) ac_optarg=yes ;;
+ esac
+ eval "enable_$ac_feature='$ac_optarg'" ;;
+
+ -exec-prefix | --exec_prefix | --exec-prefix | --exec-prefi \
+ | --exec-pref | --exec-pre | --exec-pr | --exec-p | --exec- \
+ | --exec | --exe | --ex)
+ ac_prev=exec_prefix ;;
+ -exec-prefix=* | --exec_prefix=* | --exec-prefix=* | --exec-prefi=* \
+ | --exec-pref=* | --exec-pre=* | --exec-pr=* | --exec-p=* | --exec-=* \
+ | --exec=* | --exe=* | --ex=*)
+ exec_prefix=$ac_optarg ;;
+
+ -gas | --gas | --ga | --g)
+ # Obsolete; use --with-gas.
+ with_gas=yes ;;
+
+ -help | --help | --hel | --he | -h)
+ ac_init_help=long ;;
+ -help=r* | --help=r* | --hel=r* | --he=r* | -hr*)
+ ac_init_help=recursive ;;
+ -help=s* | --help=s* | --hel=s* | --he=s* | -hs*)
+ ac_init_help=short ;;
+
+ -host | --host | --hos | --ho)
+ ac_prev=host_alias ;;
+ -host=* | --host=* | --hos=* | --ho=*)
+ host_alias=$ac_optarg ;;
+
+ -includedir | --includedir | --includedi | --included | --include \
+ | --includ | --inclu | --incl | --inc)
+ ac_prev=includedir ;;
+ -includedir=* | --includedir=* | --includedi=* | --included=* | --include=* \
+ | --includ=* | --inclu=* | --incl=* | --inc=*)
+ includedir=$ac_optarg ;;
+
+ -infodir | --infodir | --infodi | --infod | --info | --inf)
+ ac_prev=infodir ;;
+ -infodir=* | --infodir=* | --infodi=* | --infod=* | --info=* | --inf=*)
+ infodir=$ac_optarg ;;
+
+ -libdir | --libdir | --libdi | --libd)
+ ac_prev=libdir ;;
+ -libdir=* | --libdir=* | --libdi=* | --libd=*)
+ libdir=$ac_optarg ;;
+
+ -libexecdir | --libexecdir | --libexecdi | --libexecd | --libexec \
+ | --libexe | --libex | --libe)
+ ac_prev=libexecdir ;;
+ -libexecdir=* | --libexecdir=* | --libexecdi=* | --libexecd=* | --libexec=* \
+ | --libexe=* | --libex=* | --libe=*)
+ libexecdir=$ac_optarg ;;
+
+ -localstatedir | --localstatedir | --localstatedi | --localstated \
+ | --localstate | --localstat | --localsta | --localst \
+ | --locals | --local | --loca | --loc | --lo)
+ ac_prev=localstatedir ;;
+ -localstatedir=* | --localstatedir=* | --localstatedi=* | --localstated=* \
+ | --localstate=* | --localstat=* | --localsta=* | --localst=* \
+ | --locals=* | --local=* | --loca=* | --loc=* | --lo=*)
+ localstatedir=$ac_optarg ;;
+
+ -mandir | --mandir | --mandi | --mand | --man | --ma | --m)
+ ac_prev=mandir ;;
+ -mandir=* | --mandir=* | --mandi=* | --mand=* | --man=* | --ma=* | --m=*)
+ mandir=$ac_optarg ;;
+
+ -nfp | --nfp | --nf)
+ # Obsolete; use --without-fp.
+ with_fp=no ;;
+
+ -no-create | --no-create | --no-creat | --no-crea | --no-cre \
+ | --no-cr | --no-c | -n)
+ no_create=yes ;;
+
+ -no-recursion | --no-recursion | --no-recursio | --no-recursi \
+ | --no-recurs | --no-recur | --no-recu | --no-rec | --no-re | --no-r)
+ no_recursion=yes ;;
+
+ -oldincludedir | --oldincludedir | --oldincludedi | --oldincluded \
+ | --oldinclude | --oldinclud | --oldinclu | --oldincl | --oldinc \
+ | --oldin | --oldi | --old | --ol | --o)
+ ac_prev=oldincludedir ;;
+ -oldincludedir=* | --oldincludedir=* | --oldincludedi=* | --oldincluded=* \
+ | --oldinclude=* | --oldinclud=* | --oldinclu=* | --oldincl=* | --oldinc=* \
+ | --oldin=* | --oldi=* | --old=* | --ol=* | --o=*)
+ oldincludedir=$ac_optarg ;;
+
+ -prefix | --prefix | --prefi | --pref | --pre | --pr | --p)
+ ac_prev=prefix ;;
+ -prefix=* | --prefix=* | --prefi=* | --pref=* | --pre=* | --pr=* | --p=*)
+ prefix=$ac_optarg ;;
+
+ -program-prefix | --program-prefix | --program-prefi | --program-pref \
+ | --program-pre | --program-pr | --program-p)
+ ac_prev=program_prefix ;;
+ -program-prefix=* | --program-prefix=* | --program-prefi=* \
+ | --program-pref=* | --program-pre=* | --program-pr=* | --program-p=*)
+ program_prefix=$ac_optarg ;;
+
+ -program-suffix | --program-suffix | --program-suffi | --program-suff \
+ | --program-suf | --program-su | --program-s)
+ ac_prev=program_suffix ;;
+ -program-suffix=* | --program-suffix=* | --program-suffi=* \
+ | --program-suff=* | --program-suf=* | --program-su=* | --program-s=*)
+ program_suffix=$ac_optarg ;;
+
+ -program-transform-name | --program-transform-name \
+ | --program-transform-nam | --program-transform-na \
+ | --program-transform-n | --program-transform- \
+ | --program-transform | --program-transfor \
+ | --program-transfo | --program-transf \
+ | --program-trans | --program-tran \
+ | --progr-tra | --program-tr | --program-t)
+ ac_prev=program_transform_name ;;
+ -program-transform-name=* | --program-transform-name=* \
+ | --program-transform-nam=* | --program-transform-na=* \
+ | --program-transform-n=* | --program-transform-=* \
+ | --program-transform=* | --program-transfor=* \
+ | --program-transfo=* | --program-transf=* \
+ | --program-trans=* | --program-tran=* \
+ | --progr-tra=* | --program-tr=* | --program-t=*)
+ program_transform_name=$ac_optarg ;;
+
+ -q | -quiet | --quiet | --quie | --qui | --qu | --q \
+ | -silent | --silent | --silen | --sile | --sil)
+ silent=yes ;;
+
+ -sbindir | --sbindir | --sbindi | --sbind | --sbin | --sbi | --sb)
+ ac_prev=sbindir ;;
+ -sbindir=* | --sbindir=* | --sbindi=* | --sbind=* | --sbin=* \
+ | --sbi=* | --sb=*)
+ sbindir=$ac_optarg ;;
+
+ -sharedstatedir | --sharedstatedir | --sharedstatedi \
+ | --sharedstated | --sharedstate | --sharedstat | --sharedsta \
+ | --sharedst | --shareds | --shared | --share | --shar \
+ | --sha | --sh)
+ ac_prev=sharedstatedir ;;
+ -sharedstatedir=* | --sharedstatedir=* | --sharedstatedi=* \
+ | --sharedstated=* | --sharedstate=* | --sharedstat=* | --sharedsta=* \
+ | --sharedst=* | --shareds=* | --shared=* | --share=* | --shar=* \
+ | --sha=* | --sh=*)
+ sharedstatedir=$ac_optarg ;;
+
+ -site | --site | --sit)
+ ac_prev=site ;;
+ -site=* | --site=* | --sit=*)
+ site=$ac_optarg ;;
+
+ -srcdir | --srcdir | --srcdi | --srcd | --src | --sr)
+ ac_prev=srcdir ;;
+ -srcdir=* | --srcdir=* | --srcdi=* | --srcd=* | --src=* | --sr=*)
+ srcdir=$ac_optarg ;;
+
+ -sysconfdir | --sysconfdir | --sysconfdi | --sysconfd | --sysconf \
+ | --syscon | --sysco | --sysc | --sys | --sy)
+ ac_prev=sysconfdir ;;
+ -sysconfdir=* | --sysconfdir=* | --sysconfdi=* | --sysconfd=* | --sysconf=* \
+ | --syscon=* | --sysco=* | --sysc=* | --sys=* | --sy=*)
+ sysconfdir=$ac_optarg ;;
+
+ -target | --target | --targe | --targ | --tar | --ta | --t)
+ ac_prev=target_alias ;;
+ -target=* | --target=* | --targe=* | --targ=* | --tar=* | --ta=* | --t=*)
+ target_alias=$ac_optarg ;;
+
+ -v | -verbose | --verbose | --verbos | --verbo | --verb)
+ verbose=yes ;;
+
+ -version | --version | --versio | --versi | --vers | -V)
+ ac_init_version=: ;;
+
+ -with-* | --with-*)
+ ac_package=`expr "x$ac_option" : 'x-*with-\([^=]*\)'`
+ # Reject names that are not valid shell variable names.
+ expr "x$ac_package" : ".*[^-_$as_cr_alnum]" >/dev/null &&
+ { echo "$as_me: error: invalid package name: $ac_package" >&2
+ { (exit 1); exit 1; }; }
+ ac_package=`echo $ac_package| sed 's/-/_/g'`
+ case $ac_option in
+ *=*) ac_optarg=`echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"`;;
+ *) ac_optarg=yes ;;
+ esac
+ eval "with_$ac_package='$ac_optarg'" ;;
+
+ -without-* | --without-*)
+ ac_package=`expr "x$ac_option" : 'x-*without-\(.*\)'`
+ # Reject names that are not valid shell variable names.
+ expr "x$ac_package" : ".*[^-_$as_cr_alnum]" >/dev/null &&
+ { echo "$as_me: error: invalid package name: $ac_package" >&2
+ { (exit 1); exit 1; }; }
+ ac_package=`echo $ac_package | sed 's/-/_/g'`
+ eval "with_$ac_package=no" ;;
+
+ --x)
+ # Obsolete; use --with-x.
+ with_x=yes ;;
+
+ -x-includes | --x-includes | --x-include | --x-includ | --x-inclu \
+ | --x-incl | --x-inc | --x-in | --x-i)
+ ac_prev=x_includes ;;
+ -x-includes=* | --x-includes=* | --x-include=* | --x-includ=* | --x-inclu=* \
+ | --x-incl=* | --x-inc=* | --x-in=* | --x-i=*)
+ x_includes=$ac_optarg ;;
+
+ -x-libraries | --x-libraries | --x-librarie | --x-librari \
+ | --x-librar | --x-libra | --x-libr | --x-lib | --x-li | --x-l)
+ ac_prev=x_libraries ;;
+ -x-libraries=* | --x-libraries=* | --x-librarie=* | --x-librari=* \
+ | --x-librar=* | --x-libra=* | --x-libr=* | --x-lib=* | --x-li=* | --x-l=*)
+ x_libraries=$ac_optarg ;;
+
+ -*) { echo "$as_me: error: unrecognized option: $ac_option
+Try \`$0 --help' for more information." >&2
+ { (exit 1); exit 1; }; }
+ ;;
+
+ *=*)
+ ac_envvar=`expr "x$ac_option" : 'x\([^=]*\)='`
+ # Reject names that are not valid shell variable names.
+ expr "x$ac_envvar" : ".*[^_$as_cr_alnum]" >/dev/null &&
+ { echo "$as_me: error: invalid variable name: $ac_envvar" >&2
+ { (exit 1); exit 1; }; }
+ ac_optarg=`echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"`
+ eval "$ac_envvar='$ac_optarg'"
+ export $ac_envvar ;;
+
+ *)
+ # FIXME: should be removed in autoconf 3.0.
+ echo "$as_me: WARNING: you should use --build, --host, --target" >&2
+ expr "x$ac_option" : ".*[^-._$as_cr_alnum]" >/dev/null &&
+ echo "$as_me: WARNING: invalid host type: $ac_option" >&2
+ : ${build_alias=$ac_option} ${host_alias=$ac_option} ${target_alias=$ac_option}
+ ;;
+
+ esac
+done
+
+if test -n "$ac_prev"; then
+ ac_option=--`echo $ac_prev | sed 's/_/-/g'`
+ { echo "$as_me: error: missing argument to $ac_option" >&2
+ { (exit 1); exit 1; }; }
+fi
+
+# Be sure to have absolute paths.
+for ac_var in exec_prefix prefix
+do
+ eval ac_val=$`echo $ac_var`
+ case $ac_val in
+ [\\/$]* | ?:[\\/]* | NONE | '' ) ;;
+ *) { echo "$as_me: error: expected an absolute directory name for --$ac_var: $ac_val" >&2
+ { (exit 1); exit 1; }; };;
+ esac
+done
+
+# Be sure to have absolute paths.
+for ac_var in bindir sbindir libexecdir datadir sysconfdir sharedstatedir \
+ localstatedir libdir includedir oldincludedir infodir mandir
+do
+ eval ac_val=$`echo $ac_var`
+ case $ac_val in
+ [\\/$]* | ?:[\\/]* ) ;;
+ *) { echo "$as_me: error: expected an absolute directory name for --$ac_var: $ac_val" >&2
+ { (exit 1); exit 1; }; };;
+ esac
+done
+
+# There might be people who depend on the old broken behavior: `$host'
+# used to hold the argument of --host etc.
+# FIXME: To remove some day.
+build=$build_alias
+host=$host_alias
+target=$target_alias
+
+# FIXME: To remove some day.
+if test "x$host_alias" != x; then
+ if test "x$build_alias" = x; then
+ cross_compiling=maybe
+ echo "$as_me: WARNING: If you wanted to set the --build type, don't use --host.
+ If a cross compiler is detected then cross compile mode will be used." >&2
+ elif test "x$build_alias" != "x$host_alias"; then
+ cross_compiling=yes
+ fi
+fi
+
+ac_tool_prefix=
+test -n "$host_alias" && ac_tool_prefix=$host_alias-
+
+test "$silent" = yes && exec 6>/dev/null
+
+
+# Find the source files, if location was not specified.
+if test -z "$srcdir"; then
+ ac_srcdir_defaulted=yes
+ # Try the directory containing this script, then its parent.
+ ac_confdir=`(dirname "$0") 2>/dev/null ||
+$as_expr X"$0" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
+ X"$0" : 'X\(//\)[^/]' \| \
+ X"$0" : 'X\(//\)$' \| \
+ X"$0" : 'X\(/\)' \| \
+ . : '\(.\)' 2>/dev/null ||
+echo X"$0" |
+ sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ s//\1/; q; }
+ /^X\(\/\/\)[^/].*/{ s//\1/; q; }
+ /^X\(\/\/\)$/{ s//\1/; q; }
+ /^X\(\/\).*/{ s//\1/; q; }
+ s/.*/./; q'`
+ srcdir=$ac_confdir
+ if test ! -r $srcdir/$ac_unique_file; then
+ srcdir=..
+ fi
+else
+ ac_srcdir_defaulted=no
+fi
+if test ! -r $srcdir/$ac_unique_file; then
+ if test "$ac_srcdir_defaulted" = yes; then
+ { echo "$as_me: error: cannot find sources ($ac_unique_file) in $ac_confdir or .." >&2
+ { (exit 1); exit 1; }; }
+ else
+ { echo "$as_me: error: cannot find sources ($ac_unique_file) in $srcdir" >&2
+ { (exit 1); exit 1; }; }
+ fi
+fi
+(cd $srcdir && test -r ./$ac_unique_file) 2>/dev/null ||
+ { echo "$as_me: error: sources are in $srcdir, but \`cd $srcdir' does not work" >&2
+ { (exit 1); exit 1; }; }
+srcdir=`echo "$srcdir" | sed 's%\([^\\/]\)[\\/]*$%\1%'`
+ac_env_build_alias_set=${build_alias+set}
+ac_env_build_alias_value=$build_alias
+ac_cv_env_build_alias_set=${build_alias+set}
+ac_cv_env_build_alias_value=$build_alias
+ac_env_host_alias_set=${host_alias+set}
+ac_env_host_alias_value=$host_alias
+ac_cv_env_host_alias_set=${host_alias+set}
+ac_cv_env_host_alias_value=$host_alias
+ac_env_target_alias_set=${target_alias+set}
+ac_env_target_alias_value=$target_alias
+ac_cv_env_target_alias_set=${target_alias+set}
+ac_cv_env_target_alias_value=$target_alias
+ac_env_CC_set=${CC+set}
+ac_env_CC_value=$CC
+ac_cv_env_CC_set=${CC+set}
+ac_cv_env_CC_value=$CC
+ac_env_CFLAGS_set=${CFLAGS+set}
+ac_env_CFLAGS_value=$CFLAGS
+ac_cv_env_CFLAGS_set=${CFLAGS+set}
+ac_cv_env_CFLAGS_value=$CFLAGS
+ac_env_LDFLAGS_set=${LDFLAGS+set}
+ac_env_LDFLAGS_value=$LDFLAGS
+ac_cv_env_LDFLAGS_set=${LDFLAGS+set}
+ac_cv_env_LDFLAGS_value=$LDFLAGS
+ac_env_CPPFLAGS_set=${CPPFLAGS+set}
+ac_env_CPPFLAGS_value=$CPPFLAGS
+ac_cv_env_CPPFLAGS_set=${CPPFLAGS+set}
+ac_cv_env_CPPFLAGS_value=$CPPFLAGS
+ac_env_CXX_set=${CXX+set}
+ac_env_CXX_value=$CXX
+ac_cv_env_CXX_set=${CXX+set}
+ac_cv_env_CXX_value=$CXX
+ac_env_CXXFLAGS_set=${CXXFLAGS+set}
+ac_env_CXXFLAGS_value=$CXXFLAGS
+ac_cv_env_CXXFLAGS_set=${CXXFLAGS+set}
+ac_cv_env_CXXFLAGS_value=$CXXFLAGS
+ac_env_CPP_set=${CPP+set}
+ac_env_CPP_value=$CPP
+ac_cv_env_CPP_set=${CPP+set}
+ac_cv_env_CPP_value=$CPP
+
+#
+# Report the --help message.
+#
+if test "$ac_init_help" = "long"; then
+ # Omit some internal or obsolete options to make the list less imposing.
+ # This message is too long to be a string in the A/UX 3.1 sh.
+ cat <<_ACEOF
+\`configure' configures this package to adapt to many kinds of systems.
+
+Usage: $0 [OPTION]... [VAR=VALUE]...
+
+To assign environment variables (e.g., CC, CFLAGS...), specify them as
+VAR=VALUE. See below for descriptions of some of the useful variables.
+
+Defaults for the options are specified in brackets.
+
+Configuration:
+ -h, --help display this help and exit
+ --help=short display options specific to this package
+ --help=recursive display the short help of all the included packages
+ -V, --version display version information and exit
+ -q, --quiet, --silent do not print \`checking...' messages
+ --cache-file=FILE cache test results in FILE [disabled]
+ -C, --config-cache alias for \`--cache-file=config.cache'
+ -n, --no-create do not create output files
+ --srcdir=DIR find the sources in DIR [configure dir or \`..']
+
+_ACEOF
+
+ cat <<_ACEOF
+Installation directories:
+ --prefix=PREFIX install architecture-independent files in PREFIX
+ [$ac_default_prefix]
+ --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
+ [PREFIX]
+
+By default, \`make install' will install all the files in
+\`$ac_default_prefix/bin', \`$ac_default_prefix/lib' etc. You can specify
+an installation prefix other than \`$ac_default_prefix' using \`--prefix',
+for instance \`--prefix=\$HOME'.
+
+For better control, use the options below.
+
+Fine tuning of the installation directories:
+ --bindir=DIR user executables [EPREFIX/bin]
+ --sbindir=DIR system admin executables [EPREFIX/sbin]
+ --libexecdir=DIR program executables [EPREFIX/libexec]
+ --datadir=DIR read-only architecture-independent data [PREFIX/share]
+ --sysconfdir=DIR read-only single-machine data [PREFIX/etc]
+ --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
+ --localstatedir=DIR modifiable single-machine data [PREFIX/var]
+ --libdir=DIR object code libraries [EPREFIX/lib]
+ --includedir=DIR C header files [PREFIX/include]
+ --oldincludedir=DIR C header files for non-gcc [/usr/include]
+ --infodir=DIR info documentation [PREFIX/info]
+ --mandir=DIR man documentation [PREFIX/man]
+_ACEOF
+
+ cat <<\_ACEOF
+
+System types:
+ --build=BUILD configure for building on BUILD [guessed]
+ --host=HOST cross-compile to build programs to run on HOST [BUILD]
+_ACEOF
+fi
+
+if test -n "$ac_init_help"; then
+
+ cat <<\_ACEOF
+
+Optional Packages:
+ --with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
+ --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
+ --without-iconv disable unicode support
+ --with-pgsql[=ARG] build for a specific pgsql version
+ [ARG=path to pg_config]
+ --with-geos[=ARG] enable spatial predicates and operators using GEOS
+ [ARG=path to geos-config]
+ --with-geos-libdir=PATH path to GEOS libdir
+ [taken from geos-config by default]
+ --with-proj[=DIR] enable reprojection support
+ --with-proj-libdir=PATH path to PROJ4 libdir
+ --with-jts[=ARG] use JTS for spatial predicates and operators
+ [ARG=path to jts-config]
+ --with-docdir=DIR install the documentation in DIR [PREFIX/share/doc]
+
+Some influential environment variables:
+ CC C compiler command
+ CFLAGS C compiler flags
+ LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
+ nonstandard directory <lib dir>
+ CPPFLAGS C/C++ preprocessor flags, e.g. -I<include dir> if you have
+ headers in a nonstandard directory <include dir>
+ CXX C++ compiler command
+ CXXFLAGS C++ compiler flags
+ CPP C preprocessor
+
+Use these variables to override the choices made by `configure' or to help
+it to find libraries and programs with nonstandard names/locations.
+
+_ACEOF
+fi
+
+if test "$ac_init_help" = "recursive"; then
+ # If there are subdirs, report their specific --help.
+ ac_popdir=`pwd`
+ for ac_dir in : $ac_subdirs_all; do test "x$ac_dir" = x: && continue
+ test -d $ac_dir || continue
+ ac_builddir=.
+
+if test "$ac_dir" != .; then
+ ac_dir_suffix=/`echo "$ac_dir" | sed 's,^\.[\\/],,'`
+ # A "../" for each directory in $ac_dir_suffix.
+ ac_top_builddir=`echo "$ac_dir_suffix" | sed 's,/[^\\/]*,../,g'`
+else
+ ac_dir_suffix= ac_top_builddir=
+fi
+
+case $srcdir in
+ .) # No --srcdir option. We are building in place.
+ ac_srcdir=.
+ if test -z "$ac_top_builddir"; then
+ ac_top_srcdir=.
+ else
+ ac_top_srcdir=`echo $ac_top_builddir | sed 's,/$,,'`
+ fi ;;
+ [\\/]* | ?:[\\/]* ) # Absolute path.
+ ac_srcdir=$srcdir$ac_dir_suffix;
+ ac_top_srcdir=$srcdir ;;
+ *) # Relative path.
+ ac_srcdir=$ac_top_builddir$srcdir$ac_dir_suffix
+ ac_top_srcdir=$ac_top_builddir$srcdir ;;
+esac
+
+# Do not use `cd foo && pwd` to compute absolute paths, because
+# the directories may not exist.
+case `pwd` in
+.) ac_abs_builddir="$ac_dir";;
+*)
+ case "$ac_dir" in
+ .) ac_abs_builddir=`pwd`;;
+ [\\/]* | ?:[\\/]* ) ac_abs_builddir="$ac_dir";;
+ *) ac_abs_builddir=`pwd`/"$ac_dir";;
+ esac;;
+esac
+case $ac_abs_builddir in
+.) ac_abs_top_builddir=${ac_top_builddir}.;;
+*)
+ case ${ac_top_builddir}. in
+ .) ac_abs_top_builddir=$ac_abs_builddir;;
+ [\\/]* | ?:[\\/]* ) ac_abs_top_builddir=${ac_top_builddir}.;;
+ *) ac_abs_top_builddir=$ac_abs_builddir/${ac_top_builddir}.;;
+ esac;;
+esac
+case $ac_abs_builddir in
+.) ac_abs_srcdir=$ac_srcdir;;
+*)
+ case $ac_srcdir in
+ .) ac_abs_srcdir=$ac_abs_builddir;;
+ [\\/]* | ?:[\\/]* ) ac_abs_srcdir=$ac_srcdir;;
+ *) ac_abs_srcdir=$ac_abs_builddir/$ac_srcdir;;
+ esac;;
+esac
+case $ac_abs_builddir in
+.) ac_abs_top_srcdir=$ac_top_srcdir;;
+*)
+ case $ac_top_srcdir in
+ .) ac_abs_top_srcdir=$ac_abs_builddir;;
+ [\\/]* | ?:[\\/]* ) ac_abs_top_srcdir=$ac_top_srcdir;;
+ *) ac_abs_top_srcdir=$ac_abs_builddir/$ac_top_srcdir;;
+ esac;;
+esac
+
+ cd $ac_dir
+ # Check for guested configure; otherwise get Cygnus style configure.
+ if test -f $ac_srcdir/configure.gnu; then
+ echo
+ $SHELL $ac_srcdir/configure.gnu --help=recursive
+ elif test -f $ac_srcdir/configure; then
+ echo
+ $SHELL $ac_srcdir/configure --help=recursive
+ elif test -f $ac_srcdir/configure.ac ||
+ test -f $ac_srcdir/configure.in; then
+ echo
+ $ac_configure --help
+ else
+ echo "$as_me: WARNING: no configuration information is in $ac_dir" >&2
+ fi
+ cd $ac_popdir
+ done
+fi
+
+test -n "$ac_init_help" && exit 0
+if $ac_init_version; then
+ cat <<\_ACEOF
+
+Copyright (C) 2003 Free Software Foundation, Inc.
+This configure script is free software; the Free Software Foundation
+gives unlimited permission to copy, distribute and modify it.
+_ACEOF
+ exit 0
+fi
+exec 5>config.log
+cat >&5 <<_ACEOF
+This file contains any messages produced by compilers while
+running configure, to aid debugging if configure makes a mistake.
+
+It was created by $as_me, which was
+generated by GNU Autoconf 2.59. Invocation command line was
+
+ $ $0 $@
+
+_ACEOF
+{
+cat <<_ASUNAME
+@%:@@%:@ --------- @%:@@%:@
+@%:@@%:@ Platform. @%:@@%:@
+@%:@@%:@ --------- @%:@@%:@
+
+hostname = `(hostname || uname -n) 2>/dev/null | sed 1q`
+uname -m = `(uname -m) 2>/dev/null || echo unknown`
+uname -r = `(uname -r) 2>/dev/null || echo unknown`
+uname -s = `(uname -s) 2>/dev/null || echo unknown`
+uname -v = `(uname -v) 2>/dev/null || echo unknown`
+
+/usr/bin/uname -p = `(/usr/bin/uname -p) 2>/dev/null || echo unknown`
+/bin/uname -X = `(/bin/uname -X) 2>/dev/null || echo unknown`
+
+/bin/arch = `(/bin/arch) 2>/dev/null || echo unknown`
+/usr/bin/arch -k = `(/usr/bin/arch -k) 2>/dev/null || echo unknown`
+/usr/convex/getsysinfo = `(/usr/convex/getsysinfo) 2>/dev/null || echo unknown`
+hostinfo = `(hostinfo) 2>/dev/null || echo unknown`
+/bin/machine = `(/bin/machine) 2>/dev/null || echo unknown`
+/usr/bin/oslevel = `(/usr/bin/oslevel) 2>/dev/null || echo unknown`
+/bin/universe = `(/bin/universe) 2>/dev/null || echo unknown`
+
+_ASUNAME
+
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ echo "PATH: $as_dir"
+done
+
+} >&5
+
+cat >&5 <<_ACEOF
+
+
+@%:@@%:@ ----------- @%:@@%:@
+@%:@@%:@ Core tests. @%:@@%:@
+@%:@@%:@ ----------- @%:@@%:@
+
+_ACEOF
+
+
+# Keep a trace of the command line.
+# Strip out --no-create and --no-recursion so they do not pile up.
+# Strip out --silent because we don't want to record it for future runs.
+# Also quote any args containing shell meta-characters.
+# Make two passes to allow for proper duplicate-argument suppression.
+ac_configure_args=
+ac_configure_args0=
+ac_configure_args1=
+ac_sep=
+ac_must_keep_next=false
+for ac_pass in 1 2
+do
+ for ac_arg
+ do
+ case $ac_arg in
+ -no-create | --no-c* | -n | -no-recursion | --no-r*) continue ;;
+ -q | -quiet | --quiet | --quie | --qui | --qu | --q \
+ | -silent | --silent | --silen | --sile | --sil)
+ continue ;;
+ *" "*|*" "*|*[\[\]\~\#\$\^\&\*\(\)\{\}\\\|\;\<\>\?\"\']*)
+ ac_arg=`echo "$ac_arg" | sed "s/'/'\\\\\\\\''/g"` ;;
+ esac
+ case $ac_pass in
+ 1) ac_configure_args0="$ac_configure_args0 '$ac_arg'" ;;
+ 2)
+ ac_configure_args1="$ac_configure_args1 '$ac_arg'"
+ if test $ac_must_keep_next = true; then
+ ac_must_keep_next=false # Got value, back to normal.
+ else
+ case $ac_arg in
+ *=* | --config-cache | -C | -disable-* | --disable-* \
+ | -enable-* | --enable-* | -gas | --g* | -nfp | --nf* \
+ | -q | -quiet | --q* | -silent | --sil* | -v | -verb* \
+ | -with-* | --with-* | -without-* | --without-* | --x)
+ case "$ac_configure_args0 " in
+ "$ac_configure_args1"*" '$ac_arg' "* ) continue ;;
+ esac
+ ;;
+ -* ) ac_must_keep_next=true ;;
+ esac
+ fi
+ ac_configure_args="$ac_configure_args$ac_sep'$ac_arg'"
+ # Get rid of the leading space.
+ ac_sep=" "
+ ;;
+ esac
+ done
+done
+$as_unset ac_configure_args0 || test "${ac_configure_args0+set}" != set || { ac_configure_args0=; export ac_configure_args0; }
+$as_unset ac_configure_args1 || test "${ac_configure_args1+set}" != set || { ac_configure_args1=; export ac_configure_args1; }
+
+# When interrupted or exit'd, cleanup temporary files, and complete
+# config.log. We remove comments because anyway the quotes in there
+# would cause problems or look ugly.
+# WARNING: Be sure not to use single quotes in there, as some shells,
+# such as our DU 5.0 friend, will then `close' the trap.
+trap 'exit_status=$?
+ # Save into config.log some information that might help in debugging.
+ {
+ echo
+
+ cat <<\_ASBOX
+@%:@@%:@ ---------------- @%:@@%:@
+@%:@@%:@ Cache variables. @%:@@%:@
+@%:@@%:@ ---------------- @%:@@%:@
+_ASBOX
+ echo
+ # The following way of writing the cache mishandles newlines in values,
+{
+ (set) 2>&1 |
+ case `(ac_space='"'"' '"'"'; set | grep ac_space) 2>&1` in
+ *ac_space=\ *)
+ sed -n \
+ "s/'"'"'/'"'"'\\\\'"'"''"'"'/g;
+ s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='"'"'\\2'"'"'/p"
+ ;;
+ *)
+ sed -n \
+ "s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1=\\2/p"
+ ;;
+ esac;
+}
+ echo
+
+ cat <<\_ASBOX
+@%:@@%:@ ----------------- @%:@@%:@
+@%:@@%:@ Output variables. @%:@@%:@
+@%:@@%:@ ----------------- @%:@@%:@
+_ASBOX
+ echo
+ for ac_var in $ac_subst_vars
+ do
+ eval ac_val=$`echo $ac_var`
+ echo "$ac_var='"'"'$ac_val'"'"'"
+ done | sort
+ echo
+
+ if test -n "$ac_subst_files"; then
+ cat <<\_ASBOX
+@%:@@%:@ ------------- @%:@@%:@
+@%:@@%:@ Output files. @%:@@%:@
+@%:@@%:@ ------------- @%:@@%:@
+_ASBOX
+ echo
+ for ac_var in $ac_subst_files
+ do
+ eval ac_val=$`echo $ac_var`
+ echo "$ac_var='"'"'$ac_val'"'"'"
+ done | sort
+ echo
+ fi
+
+ if test -s confdefs.h; then
+ cat <<\_ASBOX
+@%:@@%:@ ----------- @%:@@%:@
+@%:@@%:@ confdefs.h. @%:@@%:@
+@%:@@%:@ ----------- @%:@@%:@
+_ASBOX
+ echo
+ sed "/^$/d" confdefs.h | sort
+ echo
+ fi
+ test "$ac_signal" != 0 &&
+ echo "$as_me: caught signal $ac_signal"
+ echo "$as_me: exit $exit_status"
+ } >&5
+ rm -f core *.core &&
+ rm -rf conftest* confdefs* conf$$* $ac_clean_files &&
+ exit $exit_status
+ ' 0
+for ac_signal in 1 2 13 15; do
+ trap 'ac_signal='$ac_signal'; { (exit 1); exit 1; }' $ac_signal
+done
+ac_signal=0
+
+# confdefs.h avoids OS command line length limits that DEFS can exceed.
+rm -rf conftest* confdefs.h
+# AIX cpp loses on an empty file, so make sure it contains at least a newline.
+echo >confdefs.h
+
+# Predefined preprocessor variables.
+
+cat >>confdefs.h <<_ACEOF
+@%:@define PACKAGE_NAME "$PACKAGE_NAME"
+_ACEOF
+
+
+cat >>confdefs.h <<_ACEOF
+@%:@define PACKAGE_TARNAME "$PACKAGE_TARNAME"
+_ACEOF
+
+
+cat >>confdefs.h <<_ACEOF
+@%:@define PACKAGE_VERSION "$PACKAGE_VERSION"
+_ACEOF
+
+
+cat >>confdefs.h <<_ACEOF
+@%:@define PACKAGE_STRING "$PACKAGE_STRING"
+_ACEOF
+
+
+cat >>confdefs.h <<_ACEOF
+@%:@define PACKAGE_BUGREPORT "$PACKAGE_BUGREPORT"
+_ACEOF
+
+
+# Let the site file select an alternate cache file if it wants to.
+# Prefer explicitly selected file to automatically selected ones.
+if test -z "$CONFIG_SITE"; then
+ if test "x$prefix" != xNONE; then
+ CONFIG_SITE="$prefix/share/config.site $prefix/etc/config.site"
+ else
+ CONFIG_SITE="$ac_default_prefix/share/config.site $ac_default_prefix/etc/config.site"
+ fi
+fi
+for ac_site_file in $CONFIG_SITE; do
+ if test -r "$ac_site_file"; then
+ { echo "$as_me:$LINENO: loading site script $ac_site_file" >&5
+echo "$as_me: loading site script $ac_site_file" >&6;}
+ sed 's/^/| /' "$ac_site_file" >&5
+ . "$ac_site_file"
+ fi
+done
+
+if test -r "$cache_file"; then
+ # Some versions of bash will fail to source /dev/null (special
+ # files actually), so we avoid doing that.
+ if test -f "$cache_file"; then
+ { echo "$as_me:$LINENO: loading cache $cache_file" >&5
+echo "$as_me: loading cache $cache_file" >&6;}
+ case $cache_file in
+ [\\/]* | ?:[\\/]* ) . $cache_file;;
+ *) . ./$cache_file;;
+ esac
+ fi
+else
+ { echo "$as_me:$LINENO: creating cache $cache_file" >&5
+echo "$as_me: creating cache $cache_file" >&6;}
+ >$cache_file
+fi
+
+# Check that the precious variables saved in the cache have kept the same
+# value.
+ac_cache_corrupted=false
+for ac_var in `(set) 2>&1 |
+ sed -n 's/^ac_env_\([a-zA-Z_0-9]*\)_set=.*/\1/p'`; do
+ eval ac_old_set=\$ac_cv_env_${ac_var}_set
+ eval ac_new_set=\$ac_env_${ac_var}_set
+ eval ac_old_val="\$ac_cv_env_${ac_var}_value"
+ eval ac_new_val="\$ac_env_${ac_var}_value"
+ case $ac_old_set,$ac_new_set in
+ set,)
+ { echo "$as_me:$LINENO: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5
+echo "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;}
+ ac_cache_corrupted=: ;;
+ ,set)
+ { echo "$as_me:$LINENO: error: \`$ac_var' was not set in the previous run" >&5
+echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;}
+ ac_cache_corrupted=: ;;
+ ,);;
+ *)
+ if test "x$ac_old_val" != "x$ac_new_val"; then
+ { echo "$as_me:$LINENO: error: \`$ac_var' has changed since the previous run:" >&5
+echo "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;}
+ { echo "$as_me:$LINENO: former value: $ac_old_val" >&5
+echo "$as_me: former value: $ac_old_val" >&2;}
+ { echo "$as_me:$LINENO: current value: $ac_new_val" >&5
+echo "$as_me: current value: $ac_new_val" >&2;}
+ ac_cache_corrupted=:
+ fi;;
+ esac
+ # Pass precious variables to config.status.
+ if test "$ac_new_set" = set; then
+ case $ac_new_val in
+ *" "*|*" "*|*[\[\]\~\#\$\^\&\*\(\)\{\}\\\|\;\<\>\?\"\']*)
+ ac_arg=$ac_var=`echo "$ac_new_val" | sed "s/'/'\\\\\\\\''/g"` ;;
+ *) ac_arg=$ac_var=$ac_new_val ;;
+ esac
+ case " $ac_configure_args " in
+ *" '$ac_arg' "*) ;; # Avoid dups. Use of quotes ensures accuracy.
+ *) ac_configure_args="$ac_configure_args '$ac_arg'" ;;
+ esac
+ fi
+done
+if $ac_cache_corrupted; then
+ { echo "$as_me:$LINENO: error: changes in the environment can compromise the build" >&5
+echo "$as_me: error: changes in the environment can compromise the build" >&2;}
+ { { echo "$as_me:$LINENO: error: run \`make distclean' and/or \`rm $cache_file' and start over" >&5
+echo "$as_me: error: run \`make distclean' and/or \`rm $cache_file' and start over" >&2;}
+ { (exit 1); exit 1; }; }
+fi
+
+ac_ext=c
+ac_cpp='$CPP $CPPFLAGS'
+ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
+ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
+ac_compiler_gnu=$ac_cv_c_compiler_gnu
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ac_config_headers="$ac_config_headers config.h"
+
+
+
+ac_ext=c
+ac_cpp='$CPP $CPPFLAGS'
+ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
+ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
+ac_compiler_gnu=$ac_cv_c_compiler_gnu
+if test -n "$ac_tool_prefix"; then
+ # Extract the first word of "${ac_tool_prefix}gcc", so it can be a program name with args.
+set dummy ${ac_tool_prefix}gcc; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_prog_CC+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ if test -n "$CC"; then
+ ac_cv_prog_CC="$CC" # Let the user override the test.
+else
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_prog_CC="${ac_tool_prefix}gcc"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+fi
+fi
+CC=$ac_cv_prog_CC
+if test -n "$CC"; then
+ echo "$as_me:$LINENO: result: $CC" >&5
+echo "${ECHO_T}$CC" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+fi
+if test -z "$ac_cv_prog_CC"; then
+ ac_ct_CC=$CC
+ # Extract the first word of "gcc", so it can be a program name with args.
+set dummy gcc; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_prog_ac_ct_CC+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ if test -n "$ac_ct_CC"; then
+ ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test.
+else
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_prog_ac_ct_CC="gcc"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+fi
+fi
+ac_ct_CC=$ac_cv_prog_ac_ct_CC
+if test -n "$ac_ct_CC"; then
+ echo "$as_me:$LINENO: result: $ac_ct_CC" >&5
+echo "${ECHO_T}$ac_ct_CC" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+ CC=$ac_ct_CC
+else
+ CC="$ac_cv_prog_CC"
+fi
+
+if test -z "$CC"; then
+ if test -n "$ac_tool_prefix"; then
+ # Extract the first word of "${ac_tool_prefix}cc", so it can be a program name with args.
+set dummy ${ac_tool_prefix}cc; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_prog_CC+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ if test -n "$CC"; then
+ ac_cv_prog_CC="$CC" # Let the user override the test.
+else
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_prog_CC="${ac_tool_prefix}cc"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+fi
+fi
+CC=$ac_cv_prog_CC
+if test -n "$CC"; then
+ echo "$as_me:$LINENO: result: $CC" >&5
+echo "${ECHO_T}$CC" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+fi
+if test -z "$ac_cv_prog_CC"; then
+ ac_ct_CC=$CC
+ # Extract the first word of "cc", so it can be a program name with args.
+set dummy cc; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_prog_ac_ct_CC+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ if test -n "$ac_ct_CC"; then
+ ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test.
+else
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_prog_ac_ct_CC="cc"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+fi
+fi
+ac_ct_CC=$ac_cv_prog_ac_ct_CC
+if test -n "$ac_ct_CC"; then
+ echo "$as_me:$LINENO: result: $ac_ct_CC" >&5
+echo "${ECHO_T}$ac_ct_CC" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+ CC=$ac_ct_CC
+else
+ CC="$ac_cv_prog_CC"
+fi
+
+fi
+if test -z "$CC"; then
+ # Extract the first word of "cc", so it can be a program name with args.
+set dummy cc; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_prog_CC+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ if test -n "$CC"; then
+ ac_cv_prog_CC="$CC" # Let the user override the test.
+else
+ ac_prog_rejected=no
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ if test "$as_dir/$ac_word$ac_exec_ext" = "/usr/ucb/cc"; then
+ ac_prog_rejected=yes
+ continue
+ fi
+ ac_cv_prog_CC="cc"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+if test $ac_prog_rejected = yes; then
+ # We found a bogon in the path, so make sure we never use it.
+ set dummy $ac_cv_prog_CC
+ shift
+ if test $@%:@ != 0; then
+ # We chose a different compiler from the bogus one.
+ # However, it has the same basename, so the bogon will be chosen
+ # first if we set CC to just the basename; use the full file name.
+ shift
+ ac_cv_prog_CC="$as_dir/$ac_word${1+' '}$@"
+ fi
+fi
+fi
+fi
+CC=$ac_cv_prog_CC
+if test -n "$CC"; then
+ echo "$as_me:$LINENO: result: $CC" >&5
+echo "${ECHO_T}$CC" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+fi
+if test -z "$CC"; then
+ if test -n "$ac_tool_prefix"; then
+ for ac_prog in cl
+ do
+ # Extract the first word of "$ac_tool_prefix$ac_prog", so it can be a program name with args.
+set dummy $ac_tool_prefix$ac_prog; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_prog_CC+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ if test -n "$CC"; then
+ ac_cv_prog_CC="$CC" # Let the user override the test.
+else
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_prog_CC="$ac_tool_prefix$ac_prog"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+fi
+fi
+CC=$ac_cv_prog_CC
+if test -n "$CC"; then
+ echo "$as_me:$LINENO: result: $CC" >&5
+echo "${ECHO_T}$CC" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+ test -n "$CC" && break
+ done
+fi
+if test -z "$CC"; then
+ ac_ct_CC=$CC
+ for ac_prog in cl
+do
+ # Extract the first word of "$ac_prog", so it can be a program name with args.
+set dummy $ac_prog; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_prog_ac_ct_CC+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ if test -n "$ac_ct_CC"; then
+ ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test.
+else
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_prog_ac_ct_CC="$ac_prog"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+fi
+fi
+ac_ct_CC=$ac_cv_prog_ac_ct_CC
+if test -n "$ac_ct_CC"; then
+ echo "$as_me:$LINENO: result: $ac_ct_CC" >&5
+echo "${ECHO_T}$ac_ct_CC" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+ test -n "$ac_ct_CC" && break
+done
+
+ CC=$ac_ct_CC
+fi
+
+fi
+
+
+test -z "$CC" && { { echo "$as_me:$LINENO: error: no acceptable C compiler found in \$PATH
+See \`config.log' for more details." >&5
+echo "$as_me: error: no acceptable C compiler found in \$PATH
+See \`config.log' for more details." >&2;}
+ { (exit 1); exit 1; }; }
+
+# Provide some information about the compiler.
+echo "$as_me:$LINENO:" \
+ "checking for C compiler version" >&5
+ac_compiler=`set X $ac_compile; echo $2`
+{ (eval echo "$as_me:$LINENO: \"$ac_compiler --version </dev/null >&5\"") >&5
+ (eval $ac_compiler --version </dev/null >&5) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }
+{ (eval echo "$as_me:$LINENO: \"$ac_compiler -v </dev/null >&5\"") >&5
+ (eval $ac_compiler -v </dev/null >&5) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }
+{ (eval echo "$as_me:$LINENO: \"$ac_compiler -V </dev/null >&5\"") >&5
+ (eval $ac_compiler -V </dev/null >&5) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }
+
+cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+
+int
+main ()
+{
+
+ ;
+ return 0;
+}
+_ACEOF
+ac_clean_files_save=$ac_clean_files
+ac_clean_files="$ac_clean_files a.out a.exe b.out"
+# Try to create an executable without -o first, disregard a.out.
+# It will help us diagnose broken compilers, and finding out an intuition
+# of exeext.
+echo "$as_me:$LINENO: checking for C compiler default output file name" >&5
+echo $ECHO_N "checking for C compiler default output file name... $ECHO_C" >&6
+ac_link_default=`echo "$ac_link" | sed 's/ -o *conftest[^ ]*//'`
+if { (eval echo "$as_me:$LINENO: \"$ac_link_default\"") >&5
+ (eval $ac_link_default) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; then
+ # Find the output, starting from the most likely. This scheme is
+# not robust to junk in `.', hence go to wildcards (a.*) only as a last
+# resort.
+
+# Be careful to initialize this variable, since it used to be cached.
+# Otherwise an old cache value of `no' led to `EXEEXT = no' in a Makefile.
+ac_cv_exeext=
+# b.out is created by i960 compilers.
+for ac_file in a_out.exe a.exe conftest.exe a.out conftest a.* conftest.* b.out
+do
+ test -f "$ac_file" || continue
+ case $ac_file in
+ *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.o | *.obj )
+ ;;
+ conftest.$ac_ext )
+ # This is the source file.
+ ;;
+ [ab].out )
+ # We found the default executable, but exeext='' is most
+ # certainly right.
+ break;;
+ *.* )
+ ac_cv_exeext=`expr "$ac_file" : '[^.]*\(\..*\)'`
+ # FIXME: I believe we export ac_cv_exeext for Libtool,
+ # but it would be cool to find out if it's true. Does anybody
+ # maintain Libtool? --akim.
+ export ac_cv_exeext
+ break;;
+ * )
+ break;;
+ esac
+done
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+{ { echo "$as_me:$LINENO: error: C compiler cannot create executables
+See \`config.log' for more details." >&5
+echo "$as_me: error: C compiler cannot create executables
+See \`config.log' for more details." >&2;}
+ { (exit 77); exit 77; }; }
+fi
+
+ac_exeext=$ac_cv_exeext
+echo "$as_me:$LINENO: result: $ac_file" >&5
+echo "${ECHO_T}$ac_file" >&6
+
+# Check the compiler produces executables we can run. If not, either
+# the compiler is broken, or we cross compile.
+echo "$as_me:$LINENO: checking whether the C compiler works" >&5
+echo $ECHO_N "checking whether the C compiler works... $ECHO_C" >&6
+# FIXME: These cross compiler hacks should be removed for Autoconf 3.0
+# If not cross compiling, check that we can run a simple program.
+if test "$cross_compiling" != yes; then
+ if { ac_try='./$ac_file'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ cross_compiling=no
+ else
+ if test "$cross_compiling" = maybe; then
+ cross_compiling=yes
+ else
+ { { echo "$as_me:$LINENO: error: cannot run C compiled programs.
+If you meant to cross compile, use \`--host'.
+See \`config.log' for more details." >&5
+echo "$as_me: error: cannot run C compiled programs.
+If you meant to cross compile, use \`--host'.
+See \`config.log' for more details." >&2;}
+ { (exit 1); exit 1; }; }
+ fi
+ fi
+fi
+echo "$as_me:$LINENO: result: yes" >&5
+echo "${ECHO_T}yes" >&6
+
+rm -f a.out a.exe conftest$ac_cv_exeext b.out
+ac_clean_files=$ac_clean_files_save
+# Check the compiler produces executables we can run. If not, either
+# the compiler is broken, or we cross compile.
+echo "$as_me:$LINENO: checking whether we are cross compiling" >&5
+echo $ECHO_N "checking whether we are cross compiling... $ECHO_C" >&6
+echo "$as_me:$LINENO: result: $cross_compiling" >&5
+echo "${ECHO_T}$cross_compiling" >&6
+
+echo "$as_me:$LINENO: checking for suffix of executables" >&5
+echo $ECHO_N "checking for suffix of executables... $ECHO_C" >&6
+if { (eval echo "$as_me:$LINENO: \"$ac_link\"") >&5
+ (eval $ac_link) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; then
+ # If both `conftest.exe' and `conftest' are `present' (well, observable)
+# catch `conftest.exe'. For instance with Cygwin, `ls conftest' will
+# work properly (i.e., refer to `conftest.exe'), while it won't with
+# `rm'.
+for ac_file in conftest.exe conftest conftest.*; do
+ test -f "$ac_file" || continue
+ case $ac_file in
+ *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.o | *.obj ) ;;
+ *.* ) ac_cv_exeext=`expr "$ac_file" : '[^.]*\(\..*\)'`
+ export ac_cv_exeext
+ break;;
+ * ) break;;
+ esac
+done
+else
+ { { echo "$as_me:$LINENO: error: cannot compute suffix of executables: cannot compile and link
+See \`config.log' for more details." >&5
+echo "$as_me: error: cannot compute suffix of executables: cannot compile and link
+See \`config.log' for more details." >&2;}
+ { (exit 1); exit 1; }; }
+fi
+
+rm -f conftest$ac_cv_exeext
+echo "$as_me:$LINENO: result: $ac_cv_exeext" >&5
+echo "${ECHO_T}$ac_cv_exeext" >&6
+
+rm -f conftest.$ac_ext
+EXEEXT=$ac_cv_exeext
+ac_exeext=$EXEEXT
+echo "$as_me:$LINENO: checking for suffix of object files" >&5
+echo $ECHO_N "checking for suffix of object files... $ECHO_C" >&6
+if test "${ac_cv_objext+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+
+int
+main ()
+{
+
+ ;
+ return 0;
+}
+_ACEOF
+rm -f conftest.o conftest.obj
+if { (eval echo "$as_me:$LINENO: \"$ac_compile\"") >&5
+ (eval $ac_compile) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; then
+ for ac_file in `(ls conftest.o conftest.obj; ls conftest.*) 2>/dev/null`; do
+ case $ac_file in
+ *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg ) ;;
+ *) ac_cv_objext=`expr "$ac_file" : '.*\.\(.*\)'`
+ break;;
+ esac
+done
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+{ { echo "$as_me:$LINENO: error: cannot compute suffix of object files: cannot compile
+See \`config.log' for more details." >&5
+echo "$as_me: error: cannot compute suffix of object files: cannot compile
+See \`config.log' for more details." >&2;}
+ { (exit 1); exit 1; }; }
+fi
+
+rm -f conftest.$ac_cv_objext conftest.$ac_ext
+fi
+echo "$as_me:$LINENO: result: $ac_cv_objext" >&5
+echo "${ECHO_T}$ac_cv_objext" >&6
+OBJEXT=$ac_cv_objext
+ac_objext=$OBJEXT
+echo "$as_me:$LINENO: checking whether we are using the GNU C compiler" >&5
+echo $ECHO_N "checking whether we are using the GNU C compiler... $ECHO_C" >&6
+if test "${ac_cv_c_compiler_gnu+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+
+int
+main ()
+{
+#ifndef __GNUC__
+ choke me
+#endif
+
+ ;
+ return 0;
+}
+_ACEOF
+rm -f conftest.$ac_objext
+if { (eval echo "$as_me:$LINENO: \"$ac_compile\"") >&5
+ (eval $ac_compile) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_c_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest.$ac_objext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ ac_compiler_gnu=yes
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ac_compiler_gnu=no
+fi
+rm -f conftest.err conftest.$ac_objext conftest.$ac_ext
+ac_cv_c_compiler_gnu=$ac_compiler_gnu
+
+fi
+echo "$as_me:$LINENO: result: $ac_cv_c_compiler_gnu" >&5
+echo "${ECHO_T}$ac_cv_c_compiler_gnu" >&6
+GCC=`test $ac_compiler_gnu = yes && echo yes`
+ac_test_CFLAGS=${CFLAGS+set}
+ac_save_CFLAGS=$CFLAGS
+CFLAGS="-g"
+echo "$as_me:$LINENO: checking whether $CC accepts -g" >&5
+echo $ECHO_N "checking whether $CC accepts -g... $ECHO_C" >&6
+if test "${ac_cv_prog_cc_g+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+
+int
+main ()
+{
+
+ ;
+ return 0;
+}
+_ACEOF
+rm -f conftest.$ac_objext
+if { (eval echo "$as_me:$LINENO: \"$ac_compile\"") >&5
+ (eval $ac_compile) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_c_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest.$ac_objext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ ac_cv_prog_cc_g=yes
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ac_cv_prog_cc_g=no
+fi
+rm -f conftest.err conftest.$ac_objext conftest.$ac_ext
+fi
+echo "$as_me:$LINENO: result: $ac_cv_prog_cc_g" >&5
+echo "${ECHO_T}$ac_cv_prog_cc_g" >&6
+if test "$ac_test_CFLAGS" = set; then
+ CFLAGS=$ac_save_CFLAGS
+elif test $ac_cv_prog_cc_g = yes; then
+ if test "$GCC" = yes; then
+ CFLAGS="-g -O2"
+ else
+ CFLAGS="-g"
+ fi
+else
+ if test "$GCC" = yes; then
+ CFLAGS="-O2"
+ else
+ CFLAGS=
+ fi
+fi
+echo "$as_me:$LINENO: checking for $CC option to accept ANSI C" >&5
+echo $ECHO_N "checking for $CC option to accept ANSI C... $ECHO_C" >&6
+if test "${ac_cv_prog_cc_stdc+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ ac_cv_prog_cc_stdc=no
+ac_save_CC=$CC
+cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+#include <stdarg.h>
+#include <stdio.h>
+#include <sys/types.h>
+#include <sys/stat.h>
+/* Most of the following tests are stolen from RCS 5.7's src/conf.sh. */
+struct buf { int x; };
+FILE * (*rcsopen) (struct buf *, struct stat *, int);
+static char *e (p, i)
+ char **p;
+ int i;
+{
+ return p[i];
+}
+static char *f (char * (*g) (char **, int), char **p, ...)
+{
+ char *s;
+ va_list v;
+ va_start (v,p);
+ s = g (p, va_arg (v,int));
+ va_end (v);
+ return s;
+}
+
+/* OSF 4.0 Compaq cc is some sort of almost-ANSI by default. It has
+ function prototypes and stuff, but not '\xHH' hex character constants.
+ These don't provoke an error unfortunately, instead are silently treated
+ as 'x'. The following induces an error, until -std1 is added to get
+ proper ANSI mode. Curiously '\x00'!='x' always comes out true, for an
+ array size at least. It's necessary to write '\x00'==0 to get something
+ that's true only with -std1. */
+int osf4_cc_array ['\x00' == 0 ? 1 : -1];
+
+int test (int i, double x);
+struct s1 {int (*f) (int a);};
+struct s2 {int (*f) (double a);};
+int pairnames (int, char **, FILE *(*)(struct buf *, struct stat *, int), int, int);
+int argc;
+char **argv;
+int
+main ()
+{
+return f (e, argv, 0) != argv[0] || f (e, argv, 1) != argv[1];
+ ;
+ return 0;
+}
+_ACEOF
+# Don't try gcc -ansi; that turns off useful extensions and
+# breaks some systems' header files.
+# AIX -qlanglvl=ansi
+# Ultrix and OSF/1 -std1
+# HP-UX 10.20 and later -Ae
+# HP-UX older versions -Aa -D_HPUX_SOURCE
+# SVR4 -Xc -D__EXTENSIONS__
+for ac_arg in "" -qlanglvl=ansi -std1 -Ae "-Aa -D_HPUX_SOURCE" "-Xc -D__EXTENSIONS__"
+do
+ CC="$ac_save_CC $ac_arg"
+ rm -f conftest.$ac_objext
+if { (eval echo "$as_me:$LINENO: \"$ac_compile\"") >&5
+ (eval $ac_compile) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_c_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest.$ac_objext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ ac_cv_prog_cc_stdc=$ac_arg
+break
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+fi
+rm -f conftest.err conftest.$ac_objext
+done
+rm -f conftest.$ac_ext conftest.$ac_objext
+CC=$ac_save_CC
+
+fi
+
+case "x$ac_cv_prog_cc_stdc" in
+ x|xno)
+ echo "$as_me:$LINENO: result: none needed" >&5
+echo "${ECHO_T}none needed" >&6 ;;
+ *)
+ echo "$as_me:$LINENO: result: $ac_cv_prog_cc_stdc" >&5
+echo "${ECHO_T}$ac_cv_prog_cc_stdc" >&6
+ CC="$CC $ac_cv_prog_cc_stdc" ;;
+esac
+
+# Some people use a C++ compiler to compile C. Since we use `exit',
+# in C++ we need to declare it. In case someone uses the same compiler
+# for both compiling C and C++ we need to have the C++ compiler decide
+# the declaration of exit, since it's the most demanding environment.
+cat >conftest.$ac_ext <<_ACEOF
+@%:@ifndef __cplusplus
+ choke me
+@%:@endif
+_ACEOF
+rm -f conftest.$ac_objext
+if { (eval echo "$as_me:$LINENO: \"$ac_compile\"") >&5
+ (eval $ac_compile) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_c_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest.$ac_objext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ for ac_declaration in \
+ '' \
+ 'extern "C" void std::exit (int) throw (); using std::exit;' \
+ 'extern "C" void std::exit (int); using std::exit;' \
+ 'extern "C" void exit (int) throw ();' \
+ 'extern "C" void exit (int);' \
+ 'void exit (int);'
+do
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+$ac_declaration
+@%:@include <stdlib.h>
+int
+main ()
+{
+exit (42);
+ ;
+ return 0;
+}
+_ACEOF
+rm -f conftest.$ac_objext
+if { (eval echo "$as_me:$LINENO: \"$ac_compile\"") >&5
+ (eval $ac_compile) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_c_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest.$ac_objext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ :
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+continue
+fi
+rm -f conftest.err conftest.$ac_objext conftest.$ac_ext
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+$ac_declaration
+int
+main ()
+{
+exit (42);
+ ;
+ return 0;
+}
+_ACEOF
+rm -f conftest.$ac_objext
+if { (eval echo "$as_me:$LINENO: \"$ac_compile\"") >&5
+ (eval $ac_compile) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_c_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest.$ac_objext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ break
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+fi
+rm -f conftest.err conftest.$ac_objext conftest.$ac_ext
+done
+rm -f conftest*
+if test -n "$ac_declaration"; then
+ echo '#ifdef __cplusplus' >>confdefs.h
+ echo $ac_declaration >>confdefs.h
+ echo '#endif' >>confdefs.h
+fi
+
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+fi
+rm -f conftest.err conftest.$ac_objext conftest.$ac_ext
+ac_ext=c
+ac_cpp='$CPP $CPPFLAGS'
+ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
+ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
+ac_compiler_gnu=$ac_cv_c_compiler_gnu
+
+ac_ext=cc
+ac_cpp='$CXXCPP $CPPFLAGS'
+ac_compile='$CXX -c $CXXFLAGS $CPPFLAGS conftest.$ac_ext >&5'
+ac_link='$CXX -o conftest$ac_exeext $CXXFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
+ac_compiler_gnu=$ac_cv_cxx_compiler_gnu
+if test -n "$ac_tool_prefix"; then
+ for ac_prog in $CCC g++ c++ gpp aCC CC cxx cc++ cl FCC KCC RCC xlC_r xlC
+ do
+ # Extract the first word of "$ac_tool_prefix$ac_prog", so it can be a program name with args.
+set dummy $ac_tool_prefix$ac_prog; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_prog_CXX+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ if test -n "$CXX"; then
+ ac_cv_prog_CXX="$CXX" # Let the user override the test.
+else
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_prog_CXX="$ac_tool_prefix$ac_prog"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+fi
+fi
+CXX=$ac_cv_prog_CXX
+if test -n "$CXX"; then
+ echo "$as_me:$LINENO: result: $CXX" >&5
+echo "${ECHO_T}$CXX" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+ test -n "$CXX" && break
+ done
+fi
+if test -z "$CXX"; then
+ ac_ct_CXX=$CXX
+ for ac_prog in $CCC g++ c++ gpp aCC CC cxx cc++ cl FCC KCC RCC xlC_r xlC
+do
+ # Extract the first word of "$ac_prog", so it can be a program name with args.
+set dummy $ac_prog; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_prog_ac_ct_CXX+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ if test -n "$ac_ct_CXX"; then
+ ac_cv_prog_ac_ct_CXX="$ac_ct_CXX" # Let the user override the test.
+else
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_prog_ac_ct_CXX="$ac_prog"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+fi
+fi
+ac_ct_CXX=$ac_cv_prog_ac_ct_CXX
+if test -n "$ac_ct_CXX"; then
+ echo "$as_me:$LINENO: result: $ac_ct_CXX" >&5
+echo "${ECHO_T}$ac_ct_CXX" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+ test -n "$ac_ct_CXX" && break
+done
+test -n "$ac_ct_CXX" || ac_ct_CXX="g++"
+
+ CXX=$ac_ct_CXX
+fi
+
+
+# Provide some information about the compiler.
+echo "$as_me:$LINENO:" \
+ "checking for C++ compiler version" >&5
+ac_compiler=`set X $ac_compile; echo $2`
+{ (eval echo "$as_me:$LINENO: \"$ac_compiler --version </dev/null >&5\"") >&5
+ (eval $ac_compiler --version </dev/null >&5) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }
+{ (eval echo "$as_me:$LINENO: \"$ac_compiler -v </dev/null >&5\"") >&5
+ (eval $ac_compiler -v </dev/null >&5) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }
+{ (eval echo "$as_me:$LINENO: \"$ac_compiler -V </dev/null >&5\"") >&5
+ (eval $ac_compiler -V </dev/null >&5) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }
+
+echo "$as_me:$LINENO: checking whether we are using the GNU C++ compiler" >&5
+echo $ECHO_N "checking whether we are using the GNU C++ compiler... $ECHO_C" >&6
+if test "${ac_cv_cxx_compiler_gnu+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+
+int
+main ()
+{
+#ifndef __GNUC__
+ choke me
+#endif
+
+ ;
+ return 0;
+}
+_ACEOF
+rm -f conftest.$ac_objext
+if { (eval echo "$as_me:$LINENO: \"$ac_compile\"") >&5
+ (eval $ac_compile) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_cxx_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest.$ac_objext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ ac_compiler_gnu=yes
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ac_compiler_gnu=no
+fi
+rm -f conftest.err conftest.$ac_objext conftest.$ac_ext
+ac_cv_cxx_compiler_gnu=$ac_compiler_gnu
+
+fi
+echo "$as_me:$LINENO: result: $ac_cv_cxx_compiler_gnu" >&5
+echo "${ECHO_T}$ac_cv_cxx_compiler_gnu" >&6
+GXX=`test $ac_compiler_gnu = yes && echo yes`
+ac_test_CXXFLAGS=${CXXFLAGS+set}
+ac_save_CXXFLAGS=$CXXFLAGS
+CXXFLAGS="-g"
+echo "$as_me:$LINENO: checking whether $CXX accepts -g" >&5
+echo $ECHO_N "checking whether $CXX accepts -g... $ECHO_C" >&6
+if test "${ac_cv_prog_cxx_g+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+
+int
+main ()
+{
+
+ ;
+ return 0;
+}
+_ACEOF
+rm -f conftest.$ac_objext
+if { (eval echo "$as_me:$LINENO: \"$ac_compile\"") >&5
+ (eval $ac_compile) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_cxx_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest.$ac_objext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ ac_cv_prog_cxx_g=yes
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ac_cv_prog_cxx_g=no
+fi
+rm -f conftest.err conftest.$ac_objext conftest.$ac_ext
+fi
+echo "$as_me:$LINENO: result: $ac_cv_prog_cxx_g" >&5
+echo "${ECHO_T}$ac_cv_prog_cxx_g" >&6
+if test "$ac_test_CXXFLAGS" = set; then
+ CXXFLAGS=$ac_save_CXXFLAGS
+elif test $ac_cv_prog_cxx_g = yes; then
+ if test "$GXX" = yes; then
+ CXXFLAGS="-g -O2"
+ else
+ CXXFLAGS="-g"
+ fi
+else
+ if test "$GXX" = yes; then
+ CXXFLAGS="-O2"
+ else
+ CXXFLAGS=
+ fi
+fi
+for ac_declaration in \
+ '' \
+ 'extern "C" void std::exit (int) throw (); using std::exit;' \
+ 'extern "C" void std::exit (int); using std::exit;' \
+ 'extern "C" void exit (int) throw ();' \
+ 'extern "C" void exit (int);' \
+ 'void exit (int);'
+do
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+$ac_declaration
+@%:@include <stdlib.h>
+int
+main ()
+{
+exit (42);
+ ;
+ return 0;
+}
+_ACEOF
+rm -f conftest.$ac_objext
+if { (eval echo "$as_me:$LINENO: \"$ac_compile\"") >&5
+ (eval $ac_compile) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_cxx_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest.$ac_objext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ :
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+continue
+fi
+rm -f conftest.err conftest.$ac_objext conftest.$ac_ext
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+$ac_declaration
+int
+main ()
+{
+exit (42);
+ ;
+ return 0;
+}
+_ACEOF
+rm -f conftest.$ac_objext
+if { (eval echo "$as_me:$LINENO: \"$ac_compile\"") >&5
+ (eval $ac_compile) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_cxx_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest.$ac_objext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ break
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+fi
+rm -f conftest.err conftest.$ac_objext conftest.$ac_ext
+done
+rm -f conftest*
+if test -n "$ac_declaration"; then
+ echo '#ifdef __cplusplus' >>confdefs.h
+ echo $ac_declaration >>confdefs.h
+ echo '#endif' >>confdefs.h
+fi
+
+ac_ext=c
+ac_cpp='$CPP $CPPFLAGS'
+ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
+ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
+ac_compiler_gnu=$ac_cv_c_compiler_gnu
+
+echo "$as_me:$LINENO: checking whether ln -s works" >&5
+echo $ECHO_N "checking whether ln -s works... $ECHO_C" >&6
+LN_S=$as_ln_s
+if test "$LN_S" = "ln -s"; then
+ echo "$as_me:$LINENO: result: yes" >&5
+echo "${ECHO_T}yes" >&6
+else
+ echo "$as_me:$LINENO: result: no, using $LN_S" >&5
+echo "${ECHO_T}no, using $LN_S" >&6
+fi
+
+
+
+
+
+ICONV_LDFLAGS=
+USE_ICONV=1
+
+# Check whether --with-iconv or --without-iconv was given.
+if test "${with_iconv+set}" = set; then
+ withval="$with_iconv"
+ if test "$with_iconv" = "no"; then
+ USE_ICONV=0
+ fi
+
+fi;
+
+if test "$USE_ICONV" = 1; then
+ echo "$as_me:$LINENO: checking for iconv_open in -liconv" >&5
+echo $ECHO_N "checking for iconv_open in -liconv... $ECHO_C" >&6
+if test "${ac_cv_lib_iconv_iconv_open+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ ac_check_lib_save_LIBS=$LIBS
+LIBS="-liconv $LIBS"
+cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+
+/* Override any gcc2 internal prototype to avoid an error. */
+#ifdef __cplusplus
+extern "C"
+#endif
+/* We use char because int might match the return type of a gcc2
+ builtin and then its argument prototype would still apply. */
+char iconv_open ();
+int
+main ()
+{
+iconv_open ();
+ ;
+ return 0;
+}
+_ACEOF
+rm -f conftest.$ac_objext conftest$ac_exeext
+if { (eval echo "$as_me:$LINENO: \"$ac_link\"") >&5
+ (eval $ac_link) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_c_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest$ac_exeext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ ac_cv_lib_iconv_iconv_open=yes
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ac_cv_lib_iconv_iconv_open=no
+fi
+rm -f conftest.err conftest.$ac_objext \
+ conftest$ac_exeext conftest.$ac_ext
+LIBS=$ac_check_lib_save_LIBS
+fi
+echo "$as_me:$LINENO: result: $ac_cv_lib_iconv_iconv_open" >&5
+echo "${ECHO_T}$ac_cv_lib_iconv_iconv_open" >&6
+if test $ac_cv_lib_iconv_iconv_open = yes; then
+ USE_ICONV=1
+ ICONV_LDFLAGS=-liconv
+
+else
+ echo "$as_me:$LINENO: checking for libiconv_open in -liconv" >&5
+echo $ECHO_N "checking for libiconv_open in -liconv... $ECHO_C" >&6
+if test "${ac_cv_lib_iconv_libiconv_open+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ ac_check_lib_save_LIBS=$LIBS
+LIBS="-liconv $LIBS"
+cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+
+/* Override any gcc2 internal prototype to avoid an error. */
+#ifdef __cplusplus
+extern "C"
+#endif
+/* We use char because int might match the return type of a gcc2
+ builtin and then its argument prototype would still apply. */
+char libiconv_open ();
+int
+main ()
+{
+libiconv_open ();
+ ;
+ return 0;
+}
+_ACEOF
+rm -f conftest.$ac_objext conftest$ac_exeext
+if { (eval echo "$as_me:$LINENO: \"$ac_link\"") >&5
+ (eval $ac_link) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_c_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest$ac_exeext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ ac_cv_lib_iconv_libiconv_open=yes
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ac_cv_lib_iconv_libiconv_open=no
+fi
+rm -f conftest.err conftest.$ac_objext \
+ conftest$ac_exeext conftest.$ac_ext
+LIBS=$ac_check_lib_save_LIBS
+fi
+echo "$as_me:$LINENO: result: $ac_cv_lib_iconv_libiconv_open" >&5
+echo "${ECHO_T}$ac_cv_lib_iconv_libiconv_open" >&6
+if test $ac_cv_lib_iconv_libiconv_open = yes; then
+ USE_ICONV=1
+ ICONV_LDFLAGS=-liconv
+
+else
+ echo "$as_me:$LINENO: checking for iconv_open in -lc" >&5
+echo $ECHO_N "checking for iconv_open in -lc... $ECHO_C" >&6
+if test "${ac_cv_lib_c_iconv_open+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ ac_check_lib_save_LIBS=$LIBS
+LIBS="-lc $LIBS"
+
+cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+
+/* Override any gcc2 internal prototype to avoid an error. */
+#ifdef __cplusplus
+extern "C"
+#endif
+/* We use char because int might match the return type of a gcc2
+ builtin and then its argument prototype would still apply. */
+char iconv_open ();
+int
+main ()
+{
+iconv_open ();
+ ;
+ return 0;
+}
+_ACEOF
+rm -f conftest.$ac_objext conftest$ac_exeext
+if { (eval echo "$as_me:$LINENO: \"$ac_link\"") >&5
+ (eval $ac_link) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_c_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest$ac_exeext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ ac_cv_lib_c_iconv_open=yes
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ac_cv_lib_c_iconv_open=no
+fi
+rm -f conftest.err conftest.$ac_objext \
+ conftest$ac_exeext conftest.$ac_ext
+LIBS=$ac_check_lib_save_LIBS
+fi
+echo "$as_me:$LINENO: result: $ac_cv_lib_c_iconv_open" >&5
+echo "${ECHO_T}$ac_cv_lib_c_iconv_open" >&6
+if test $ac_cv_lib_c_iconv_open = yes; then
+ USE_ICONV=1
+
+else
+ USE_ICONV=0
+
+fi
+
+
+fi
+
+
+fi
+
+fi
+
+ac_ext=c
+ac_cpp='$CPP $CPPFLAGS'
+ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
+ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
+ac_compiler_gnu=$ac_cv_c_compiler_gnu
+echo "$as_me:$LINENO: checking how to run the C preprocessor" >&5
+echo $ECHO_N "checking how to run the C preprocessor... $ECHO_C" >&6
+# On Suns, sometimes $CPP names a directory.
+if test -n "$CPP" && test -d "$CPP"; then
+ CPP=
+fi
+if test -z "$CPP"; then
+ if test "${ac_cv_prog_CPP+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ # Double quotes because CPP needs to be expanded
+ for CPP in "$CC -E" "$CC -E -traditional-cpp" "/lib/cpp"
+ do
+ ac_preproc_ok=false
+for ac_c_preproc_warn_flag in '' yes
+do
+ # Use a header file that comes with gcc, so configuring glibc
+ # with a fresh cross-compiler works.
+ # Prefer <limits.h> to <assert.h> if __STDC__ is defined, since
+ # <limits.h> exists even on freestanding compilers.
+ # On the NeXT, cc -E runs the code through the compiler's parser,
+ # not just through cpp. "Syntax error" is here to catch this case.
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+@%:@ifdef __STDC__
+@%:@ include <limits.h>
+@%:@else
+@%:@ include <assert.h>
+@%:@endif
+ Syntax error
+_ACEOF
+if { (eval echo "$as_me:$LINENO: \"$ac_cpp conftest.$ac_ext\"") >&5
+ (eval $ac_cpp conftest.$ac_ext) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } >/dev/null; then
+ if test -s conftest.err; then
+ ac_cpp_err=$ac_c_preproc_warn_flag
+ ac_cpp_err=$ac_cpp_err$ac_c_werror_flag
+ else
+ ac_cpp_err=
+ fi
+else
+ ac_cpp_err=yes
+fi
+if test -z "$ac_cpp_err"; then
+ :
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ # Broken: fails on valid input.
+continue
+fi
+rm -f conftest.err conftest.$ac_ext
+
+ # OK, works on sane cases. Now check whether non-existent headers
+ # can be detected and how.
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+@%:@include <ac_nonexistent.h>
+_ACEOF
+if { (eval echo "$as_me:$LINENO: \"$ac_cpp conftest.$ac_ext\"") >&5
+ (eval $ac_cpp conftest.$ac_ext) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } >/dev/null; then
+ if test -s conftest.err; then
+ ac_cpp_err=$ac_c_preproc_warn_flag
+ ac_cpp_err=$ac_cpp_err$ac_c_werror_flag
+ else
+ ac_cpp_err=
+ fi
+else
+ ac_cpp_err=yes
+fi
+if test -z "$ac_cpp_err"; then
+ # Broken: success on invalid input.
+continue
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ # Passes both tests.
+ac_preproc_ok=:
+break
+fi
+rm -f conftest.err conftest.$ac_ext
+
+done
+# Because of `break', _AC_PREPROC_IFELSE's cleaning code was skipped.
+rm -f conftest.err conftest.$ac_ext
+if $ac_preproc_ok; then
+ break
+fi
+
+ done
+ ac_cv_prog_CPP=$CPP
+
+fi
+ CPP=$ac_cv_prog_CPP
+else
+ ac_cv_prog_CPP=$CPP
+fi
+echo "$as_me:$LINENO: result: $CPP" >&5
+echo "${ECHO_T}$CPP" >&6
+ac_preproc_ok=false
+for ac_c_preproc_warn_flag in '' yes
+do
+ # Use a header file that comes with gcc, so configuring glibc
+ # with a fresh cross-compiler works.
+ # Prefer <limits.h> to <assert.h> if __STDC__ is defined, since
+ # <limits.h> exists even on freestanding compilers.
+ # On the NeXT, cc -E runs the code through the compiler's parser,
+ # not just through cpp. "Syntax error" is here to catch this case.
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+@%:@ifdef __STDC__
+@%:@ include <limits.h>
+@%:@else
+@%:@ include <assert.h>
+@%:@endif
+ Syntax error
+_ACEOF
+if { (eval echo "$as_me:$LINENO: \"$ac_cpp conftest.$ac_ext\"") >&5
+ (eval $ac_cpp conftest.$ac_ext) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } >/dev/null; then
+ if test -s conftest.err; then
+ ac_cpp_err=$ac_c_preproc_warn_flag
+ ac_cpp_err=$ac_cpp_err$ac_c_werror_flag
+ else
+ ac_cpp_err=
+ fi
+else
+ ac_cpp_err=yes
+fi
+if test -z "$ac_cpp_err"; then
+ :
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ # Broken: fails on valid input.
+continue
+fi
+rm -f conftest.err conftest.$ac_ext
+
+ # OK, works on sane cases. Now check whether non-existent headers
+ # can be detected and how.
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+@%:@include <ac_nonexistent.h>
+_ACEOF
+if { (eval echo "$as_me:$LINENO: \"$ac_cpp conftest.$ac_ext\"") >&5
+ (eval $ac_cpp conftest.$ac_ext) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } >/dev/null; then
+ if test -s conftest.err; then
+ ac_cpp_err=$ac_c_preproc_warn_flag
+ ac_cpp_err=$ac_cpp_err$ac_c_werror_flag
+ else
+ ac_cpp_err=
+ fi
+else
+ ac_cpp_err=yes
+fi
+if test -z "$ac_cpp_err"; then
+ # Broken: success on invalid input.
+continue
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ # Passes both tests.
+ac_preproc_ok=:
+break
+fi
+rm -f conftest.err conftest.$ac_ext
+
+done
+# Because of `break', _AC_PREPROC_IFELSE's cleaning code was skipped.
+rm -f conftest.err conftest.$ac_ext
+if $ac_preproc_ok; then
+ :
+else
+ { { echo "$as_me:$LINENO: error: C preprocessor \"$CPP\" fails sanity check
+See \`config.log' for more details." >&5
+echo "$as_me: error: C preprocessor \"$CPP\" fails sanity check
+See \`config.log' for more details." >&2;}
+ { (exit 1); exit 1; }; }
+fi
+
+ac_ext=c
+ac_cpp='$CPP $CPPFLAGS'
+ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
+ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
+ac_compiler_gnu=$ac_cv_c_compiler_gnu
+
+
+echo "$as_me:$LINENO: checking for egrep" >&5
+echo $ECHO_N "checking for egrep... $ECHO_C" >&6
+if test "${ac_cv_prog_egrep+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ if echo a | (grep -E '(a|b)') >/dev/null 2>&1
+ then ac_cv_prog_egrep='grep -E'
+ else ac_cv_prog_egrep='egrep'
+ fi
+fi
+echo "$as_me:$LINENO: result: $ac_cv_prog_egrep" >&5
+echo "${ECHO_T}$ac_cv_prog_egrep" >&6
+ EGREP=$ac_cv_prog_egrep
+
+
+echo "$as_me:$LINENO: checking for ANSI C header files" >&5
+echo $ECHO_N "checking for ANSI C header files... $ECHO_C" >&6
+if test "${ac_cv_header_stdc+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+#include <stdlib.h>
+#include <stdarg.h>
+#include <string.h>
+#include <float.h>
+
+int
+main ()
+{
+
+ ;
+ return 0;
+}
+_ACEOF
+rm -f conftest.$ac_objext
+if { (eval echo "$as_me:$LINENO: \"$ac_compile\"") >&5
+ (eval $ac_compile) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_c_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest.$ac_objext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ ac_cv_header_stdc=yes
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ac_cv_header_stdc=no
+fi
+rm -f conftest.err conftest.$ac_objext conftest.$ac_ext
+
+if test $ac_cv_header_stdc = yes; then
+ # SunOS 4.x string.h does not declare mem*, contrary to ANSI.
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+#include <string.h>
+
+_ACEOF
+if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
+ $EGREP "memchr" >/dev/null 2>&1; then
+ :
+else
+ ac_cv_header_stdc=no
+fi
+rm -f conftest*
+
+fi
+
+if test $ac_cv_header_stdc = yes; then
+ # ISC 2.0.2 stdlib.h does not declare free, contrary to ANSI.
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+#include <stdlib.h>
+
+_ACEOF
+if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
+ $EGREP "free" >/dev/null 2>&1; then
+ :
+else
+ ac_cv_header_stdc=no
+fi
+rm -f conftest*
+
+fi
+
+if test $ac_cv_header_stdc = yes; then
+ # /bin/cc in Irix-4.0.5 gets non-ANSI ctype macros unless using -ansi.
+ if test "$cross_compiling" = yes; then
+ :
+else
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+#include <ctype.h>
+#if ((' ' & 0x0FF) == 0x020)
+# define ISLOWER(c) ('a' <= (c) && (c) <= 'z')
+# define TOUPPER(c) (ISLOWER(c) ? 'A' + ((c) - 'a') : (c))
+#else
+# define ISLOWER(c) \
+ (('a' <= (c) && (c) <= 'i') \
+ || ('j' <= (c) && (c) <= 'r') \
+ || ('s' <= (c) && (c) <= 'z'))
+# define TOUPPER(c) (ISLOWER(c) ? ((c) | 0x40) : (c))
+#endif
+
+#define XOR(e, f) (((e) && !(f)) || (!(e) && (f)))
+int
+main ()
+{
+ int i;
+ for (i = 0; i < 256; i++)
+ if (XOR (islower (i), ISLOWER (i))
+ || toupper (i) != TOUPPER (i))
+ exit(2);
+ exit (0);
+}
+_ACEOF
+rm -f conftest$ac_exeext
+if { (eval echo "$as_me:$LINENO: \"$ac_link\"") >&5
+ (eval $ac_link) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } && { ac_try='./conftest$ac_exeext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ :
+else
+ echo "$as_me: program exited with status $ac_status" >&5
+echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+( exit $ac_status )
+ac_cv_header_stdc=no
+fi
+rm -f core *.core gmon.out bb.out conftest$ac_exeext conftest.$ac_objext conftest.$ac_ext
+fi
+fi
+fi
+echo "$as_me:$LINENO: result: $ac_cv_header_stdc" >&5
+echo "${ECHO_T}$ac_cv_header_stdc" >&6
+if test $ac_cv_header_stdc = yes; then
+
+cat >>confdefs.h <<\_ACEOF
+@%:@define STDC_HEADERS 1
+_ACEOF
+
+fi
+
+# On IRIX 5.3, sys/types and inttypes.h are conflicting.
+
+
+
+
+
+
+
+
+
+for ac_header in sys/types.h sys/stat.h stdlib.h string.h memory.h strings.h \
+ inttypes.h stdint.h unistd.h
+do
+as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh`
+echo "$as_me:$LINENO: checking for $ac_header" >&5
+echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6
+if eval "test \"\${$as_ac_Header+set}\" = set"; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+$ac_includes_default
+
+@%:@include <$ac_header>
+_ACEOF
+rm -f conftest.$ac_objext
+if { (eval echo "$as_me:$LINENO: \"$ac_compile\"") >&5
+ (eval $ac_compile) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_c_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest.$ac_objext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ eval "$as_ac_Header=yes"
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+eval "$as_ac_Header=no"
+fi
+rm -f conftest.err conftest.$ac_objext conftest.$ac_ext
+fi
+echo "$as_me:$LINENO: result: `eval echo '${'$as_ac_Header'}'`" >&5
+echo "${ECHO_T}`eval echo '${'$as_ac_Header'}'`" >&6
+if test `eval echo '${'$as_ac_Header'}'` = yes; then
+ cat >>confdefs.h <<_ACEOF
+@%:@define `echo "HAVE_$ac_header" | $as_tr_cpp` 1
+_ACEOF
+
+fi
+
+done
+
+
+
+for ac_header in iconv.h
+do
+as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh`
+if eval "test \"\${$as_ac_Header+set}\" = set"; then
+ echo "$as_me:$LINENO: checking for $ac_header" >&5
+echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6
+if eval "test \"\${$as_ac_Header+set}\" = set"; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+fi
+echo "$as_me:$LINENO: result: `eval echo '${'$as_ac_Header'}'`" >&5
+echo "${ECHO_T}`eval echo '${'$as_ac_Header'}'`" >&6
+else
+ # Is the header compilable?
+echo "$as_me:$LINENO: checking $ac_header usability" >&5
+echo $ECHO_N "checking $ac_header usability... $ECHO_C" >&6
+cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+$ac_includes_default
+@%:@include <$ac_header>
+_ACEOF
+rm -f conftest.$ac_objext
+if { (eval echo "$as_me:$LINENO: \"$ac_compile\"") >&5
+ (eval $ac_compile) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_c_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest.$ac_objext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ ac_header_compiler=yes
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ac_header_compiler=no
+fi
+rm -f conftest.err conftest.$ac_objext conftest.$ac_ext
+echo "$as_me:$LINENO: result: $ac_header_compiler" >&5
+echo "${ECHO_T}$ac_header_compiler" >&6
+
+# Is the header present?
+echo "$as_me:$LINENO: checking $ac_header presence" >&5
+echo $ECHO_N "checking $ac_header presence... $ECHO_C" >&6
+cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+@%:@include <$ac_header>
+_ACEOF
+if { (eval echo "$as_me:$LINENO: \"$ac_cpp conftest.$ac_ext\"") >&5
+ (eval $ac_cpp conftest.$ac_ext) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } >/dev/null; then
+ if test -s conftest.err; then
+ ac_cpp_err=$ac_c_preproc_warn_flag
+ ac_cpp_err=$ac_cpp_err$ac_c_werror_flag
+ else
+ ac_cpp_err=
+ fi
+else
+ ac_cpp_err=yes
+fi
+if test -z "$ac_cpp_err"; then
+ ac_header_preproc=yes
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ ac_header_preproc=no
+fi
+rm -f conftest.err conftest.$ac_ext
+echo "$as_me:$LINENO: result: $ac_header_preproc" >&5
+echo "${ECHO_T}$ac_header_preproc" >&6
+
+# So? What about this header?
+case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in
+ yes:no: )
+ { echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&5
+echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected by the preprocessor!" >&2;}
+ { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the compiler's result" >&5
+echo "$as_me: WARNING: $ac_header: proceeding with the compiler's result" >&2;}
+ ac_header_preproc=yes
+ ;;
+ no:yes:* )
+ { echo "$as_me:$LINENO: WARNING: $ac_header: present but cannot be compiled" >&5
+echo "$as_me: WARNING: $ac_header: present but cannot be compiled" >&2;}
+ { echo "$as_me:$LINENO: WARNING: $ac_header: check for missing prerequisite headers?" >&5
+echo "$as_me: WARNING: $ac_header: check for missing prerequisite headers?" >&2;}
+ { echo "$as_me:$LINENO: WARNING: $ac_header: see the Autoconf documentation" >&5
+echo "$as_me: WARNING: $ac_header: see the Autoconf documentation" >&2;}
+ { echo "$as_me:$LINENO: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&5
+echo "$as_me: WARNING: $ac_header: section \"Present But Cannot Be Compiled\"" >&2;}
+ { echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the preprocessor's result" >&5
+echo "$as_me: WARNING: $ac_header: proceeding with the preprocessor's result" >&2;}
+ { echo "$as_me:$LINENO: WARNING: $ac_header: in the future, the compiler will take precedence" >&5
+echo "$as_me: WARNING: $ac_header: in the future, the compiler will take precedence" >&2;}
+ (
+ cat <<\_ASBOX
+@%:@@%:@ ------------------------------------------ @%:@@%:@
+@%:@@%:@ Report this to the AC_PACKAGE_NAME lists. @%:@@%:@
+@%:@@%:@ ------------------------------------------ @%:@@%:@
+_ASBOX
+ ) |
+ sed "s/^/$as_me: WARNING: /" >&2
+ ;;
+esac
+echo "$as_me:$LINENO: checking for $ac_header" >&5
+echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6
+if eval "test \"\${$as_ac_Header+set}\" = set"; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ eval "$as_ac_Header=\$ac_header_preproc"
+fi
+echo "$as_me:$LINENO: result: `eval echo '${'$as_ac_Header'}'`" >&5
+echo "${ECHO_T}`eval echo '${'$as_ac_Header'}'`" >&6
+
+fi
+if test `eval echo '${'$as_ac_Header'}'` = yes; then
+ cat >>confdefs.h <<_ACEOF
+@%:@define `echo "HAVE_$ac_header" | $as_tr_cpp` 1
+_ACEOF
+
+fi
+
+done
+
+
+
+
+ac_aux_dir=
+for ac_dir in $srcdir $srcdir/.. $srcdir/../..; do
+ if test -f $ac_dir/install-sh; then
+ ac_aux_dir=$ac_dir
+ ac_install_sh="$ac_aux_dir/install-sh -c"
+ break
+ elif test -f $ac_dir/install.sh; then
+ ac_aux_dir=$ac_dir
+ ac_install_sh="$ac_aux_dir/install.sh -c"
+ break
+ elif test -f $ac_dir/shtool; then
+ ac_aux_dir=$ac_dir
+ ac_install_sh="$ac_aux_dir/shtool install -c"
+ break
+ fi
+done
+if test -z "$ac_aux_dir"; then
+ { { echo "$as_me:$LINENO: error: cannot find install-sh or install.sh in $srcdir $srcdir/.. $srcdir/../.." >&5
+echo "$as_me: error: cannot find install-sh or install.sh in $srcdir $srcdir/.. $srcdir/../.." >&2;}
+ { (exit 1); exit 1; }; }
+fi
+ac_config_guess="$SHELL $ac_aux_dir/config.guess"
+ac_config_sub="$SHELL $ac_aux_dir/config.sub"
+ac_configure="$SHELL $ac_aux_dir/configure" # This should be Cygnus configure.
+
+# Make sure we can run config.sub.
+$ac_config_sub sun4 >/dev/null 2>&1 ||
+ { { echo "$as_me:$LINENO: error: cannot run $ac_config_sub" >&5
+echo "$as_me: error: cannot run $ac_config_sub" >&2;}
+ { (exit 1); exit 1; }; }
+
+echo "$as_me:$LINENO: checking build system type" >&5
+echo $ECHO_N "checking build system type... $ECHO_C" >&6
+if test "${ac_cv_build+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ ac_cv_build_alias=$build_alias
+test -z "$ac_cv_build_alias" &&
+ ac_cv_build_alias=`$ac_config_guess`
+test -z "$ac_cv_build_alias" &&
+ { { echo "$as_me:$LINENO: error: cannot guess build type; you must specify one" >&5
+echo "$as_me: error: cannot guess build type; you must specify one" >&2;}
+ { (exit 1); exit 1; }; }
+ac_cv_build=`$ac_config_sub $ac_cv_build_alias` ||
+ { { echo "$as_me:$LINENO: error: $ac_config_sub $ac_cv_build_alias failed" >&5
+echo "$as_me: error: $ac_config_sub $ac_cv_build_alias failed" >&2;}
+ { (exit 1); exit 1; }; }
+
+fi
+echo "$as_me:$LINENO: result: $ac_cv_build" >&5
+echo "${ECHO_T}$ac_cv_build" >&6
+build=$ac_cv_build
+build_cpu=`echo $ac_cv_build | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\1/'`
+build_vendor=`echo $ac_cv_build | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\2/'`
+build_os=`echo $ac_cv_build | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\3/'`
+
+
+echo "$as_me:$LINENO: checking host system type" >&5
+echo $ECHO_N "checking host system type... $ECHO_C" >&6
+if test "${ac_cv_host+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ ac_cv_host_alias=$host_alias
+test -z "$ac_cv_host_alias" &&
+ ac_cv_host_alias=$ac_cv_build_alias
+ac_cv_host=`$ac_config_sub $ac_cv_host_alias` ||
+ { { echo "$as_me:$LINENO: error: $ac_config_sub $ac_cv_host_alias failed" >&5
+echo "$as_me: error: $ac_config_sub $ac_cv_host_alias failed" >&2;}
+ { (exit 1); exit 1; }; }
+
+fi
+echo "$as_me:$LINENO: result: $ac_cv_host" >&5
+echo "${ECHO_T}$ac_cv_host" >&6
+host=$ac_cv_host
+host_cpu=`echo $ac_cv_host | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\1/'`
+host_vendor=`echo $ac_cv_host | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\2/'`
+host_os=`echo $ac_cv_host | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\3/'`
+
+
+
+
+PGCONFIG=
+
+# Check whether --with-pgsql or --without-pgsql was given.
+if test "${with_pgsql+set}" = set; then
+ withval="$with_pgsql"
+ if test "$with_pgsql" != "no" -a "$with_pgsql" != "yes"; then
+ if test ! -f "$with_pgsql"; then
+ { { echo "$as_me:$LINENO: error: Invalid argument to --with-pgsql" >&5
+echo "$as_me: error: Invalid argument to --with-pgsql" >&2;}
+ { (exit 1); exit 1; }; };
+ fi
+ PGCONFIG="$with_pgsql"
+ fi
+
+fi;
+if test -z "$PGCONFIG"; then
+ # Extract the first word of "pg_config", so it can be a program name with args.
+set dummy pg_config; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_path_PGCONFIG+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ case $PGCONFIG in
+ [\\/]* | ?:[\\/]*)
+ ac_cv_path_PGCONFIG="$PGCONFIG" # Let the user override the test with a path.
+ ;;
+ *)
+ as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_path_PGCONFIG="$as_dir/$ac_word$ac_exec_ext"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+ ;;
+esac
+fi
+PGCONFIG=$ac_cv_path_PGCONFIG
+
+if test -n "$PGCONFIG"; then
+ echo "$as_me:$LINENO: result: $PGCONFIG" >&5
+echo "${ECHO_T}$PGCONFIG" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+fi
+if test -z "$PGCONFIG"; then
+ { { echo "$as_me:$LINENO: error: PostgreSQL is required by PostGIS" >&5
+echo "$as_me: error: PostgreSQL is required by PostGIS" >&2;}
+ { (exit 1); exit 1; }; };
+fi
+
+
+
+
+
+
+
+PGFEINCLUDES="-I"`${PGCONFIG} --includedir`
+PGFELIBS="-L"`${PGCONFIG} --libdir`" -lpq " #(1)# `${PGCONFIG} --libs 2> /dev/null`
+#(1)#
+# We don't really want to link to more libs then required, see:
+# http://postgis.refractions.net/pipermail/postgis-devel/2006-May/002124.html
+PGBELIBS="-L"`${PGCONFIG} --libdir`" -lpostgres"
+PGBEINCLUDES="-I"`${PGCONFIG} --includedir-server`
+PGBIN=`${PGCONFIG} --bindir`
+
+case $host_os in
+ *mingw*)
+ PWDREGRESS="pwd -W"
+ ;;
+ *)
+ PWDREGRESS="pwd"
+ ;;
+esac
+
+
+
+
+
+
+
+USE_GEOS=0
+USE_GEOS_CAPI=0
+GEOS_DIR=
+GEOS_LDFLAGS=
+
+# Extract the first word of "geos-config", so it can be a program name with args.
+set dummy geos-config; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_path_GEOSCONFIG+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ case $GEOSCONFIG in
+ [\\/]* | ?:[\\/]*)
+ ac_cv_path_GEOSCONFIG="$GEOSCONFIG" # Let the user override the test with a path.
+ ;;
+ *)
+ as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_path_GEOSCONFIG="$as_dir/$ac_word$ac_exec_ext"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+ ;;
+esac
+fi
+GEOSCONFIG=$ac_cv_path_GEOSCONFIG
+
+if test -n "$GEOSCONFIG"; then
+ echo "$as_me:$LINENO: result: $GEOSCONFIG" >&5
+echo "${ECHO_T}$GEOSCONFIG" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+if test -n "$GEOSCONFIG"; then
+ USE_GEOS=1
+fi
+
+
+# Check whether --with-geos or --without-geos was given.
+if test "${with_geos+set}" = set; then
+ withval="$with_geos"
+ if test "$with_geos" = "no"; then
+ USE_GEOS=0
+ else
+ if test "$with_geos" != "yes"; then
+ if test ! -f "$with_geos"; then
+ { { echo "$as_me:$LINENO: error: Invalid argument to --with-geos" >&5
+echo "$as_me: error: Invalid argument to --with-geos" >&2;}
+ { (exit 1); exit 1; }; };
+ else
+ GEOSCONFIG="$with_geos"
+ USE_GEOS=1
+ fi
+ fi
+ fi
+
+fi;
+
+if test $USE_GEOS -gt 0; then
+ GEOS_DIR=`$GEOSCONFIG --prefix`
+ GEOS_LDFLAGS=`$GEOSCONFIG --ldflags`
+ GEOS_MAJOR=`$GEOSCONFIG --version | cut -d. -f1`
+ if test "$GEOS_MAJOR" = "@GEOS_VERSION@"; then
+ GEOS_MAJOR=1
+ GEOS_MINOR=0
+ else
+ GEOS_MINOR=`$GEOSCONFIG --version | cut -d. -f2`
+ fi
+ if test $GEOS_MAJOR -gt 2; then
+ USE_GEOS_CAPI=1
+ elif test $GEOS_MAJOR -eq 2 -a $GEOS_MINOR -ge 2; then
+ USE_GEOS_CAPI=1
+ fi
+fi
+
+
+# Check whether --with-geos-libdir or --without-geos-libdir was given.
+if test "${with_geos_libdir+set}" = set; then
+ withval="$with_geos_libdir"
+
+case "$with_geos_libdir" in
+ no|yes)
+ { { echo "$as_me:$LINENO: error: Invalid argument to --with-geos-libdir" >&5
+echo "$as_me: error: Invalid argument to --with-geos-libdir" >&2;}
+ { (exit 1); exit 1; }; }
+ ;;
+ *)
+ GEOS_LDFLAGS=-L${with_geos_libdir}
+ ;;
+esac
+
+else
+ with_geos_libdir=no
+fi;
+
+
+
+
+
+USE_PROJ=0
+PROJ_DIR=
+PROJ_LIBDIR=
+# Extract the first word of "proj", so it can be a program name with args.
+set dummy proj; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_path_PROJ+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ case $PROJ in
+ [\\/]* | ?:[\\/]*)
+ ac_cv_path_PROJ="$PROJ" # Let the user override the test with a path.
+ ;;
+ *)
+ as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_path_PROJ="$as_dir/$ac_word$ac_exec_ext"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+ ;;
+esac
+fi
+PROJ=$ac_cv_path_PROJ
+
+if test -n "$PROJ"; then
+ echo "$as_me:$LINENO: result: $PROJ" >&5
+echo "${ECHO_T}$PROJ" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+if test -n "$PROJ"; then
+ USE_PROJ=1
+ PROJ_DIR=`dirname ${PROJ}`/..
+ owd=`pwd`; cd ${PROJ_DIR}; PROJ_DIR=`pwd`; cd $owd;
+fi
+
+# Check whether --with-proj or --without-proj was given.
+if test "${with_proj+set}" = set; then
+ withval="$with_proj"
+ if test "$with_proj" = "no"; then
+ USE_PROJ=0
+ else
+ USE_PROJ=1
+ if test "$with_proj" != "yes"; then
+ PROJ_DIR=$with_proj
+ fi
+ fi
+
+fi;
+if test $USE_PROJ -gt 0; then
+ if test ! -f $PROJ_DIR/include/projects.h; then
+ { { echo "$as_me:$LINENO: error: Can't find proj dir." >&5
+echo "$as_me: error: Can't find proj dir." >&2;}
+ { (exit 1); exit 1; }; };
+ fi
+ PROJ_LIBDIR=${PROJ_DIR}/lib
+fi
+
+
+# Check whether --with-proj-libdir or --without-proj-libdir was given.
+if test "${with_proj_libdir+set}" = set; then
+ withval="$with_proj_libdir"
+
+case "$with_proj_libdir" in
+ no|yes)
+ { { echo "$as_me:$LINENO: error: Invalid argument to --with-proj-libdir" >&5
+echo "$as_me: error: Invalid argument to --with-proj-libdir" >&2;}
+ { (exit 1); exit 1; }; }
+ ;;
+ *)
+ PROJ_LIBDIR=${with_proj_libdir}
+ ;;
+esac
+
+else
+ with_proj_libdir=no
+fi;
+
+
+
+
+USE_JTS=0
+JTS_INCLUDES=
+JTS_INCLUDES=
+
+# Check whether --with-jts or --without-jts was given.
+if test "${with_jts+set}" = set; then
+ withval="$with_jts"
+ if test "$with_jts" != "no"; then
+ USE_JTS=1
+ if test "$with_jts" != "yes"; then
+ if test ! -f "$with_jts"; then
+ { { echo "$as_me:$LINENO: error: Invalid argument to --with-jts" >&5
+echo "$as_me: error: Invalid argument to --with-jts" >&2;}
+ { (exit 1); exit 1; }; };
+ else
+ JTSCONFIG=$with_jts
+ fi
+ fi
+ fi
+
+fi;
+if test $USE_JTS -gt 0; then
+ if test -z "$JTSCONFIG"; then
+ # Extract the first word of "jts-config", so it can be a program name with args.
+set dummy jts-config; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_path_JTSCONFIG+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ case $JTSCONFIG in
+ [\\/]* | ?:[\\/]*)
+ ac_cv_path_JTSCONFIG="$JTSCONFIG" # Let the user override the test with a path.
+ ;;
+ *)
+ as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_path_JTSCONFIG="$as_dir/$ac_word$ac_exec_ext"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+ ;;
+esac
+fi
+JTSCONFIG=$ac_cv_path_JTSCONFIG
+
+if test -n "$JTSCONFIG"; then
+ echo "$as_me:$LINENO: result: $JTSCONFIG" >&5
+echo "${ECHO_T}$JTSCONFIG" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+ if test -z "$JTSCONFIG"; then
+ { { echo "$as_me:$LINENO: error: Can't find jts-config" >&5
+echo "$as_me: error: Can't find jts-config" >&2;}
+ { (exit 1); exit 1; }; };
+ fi
+ fi
+ JTS_INCLUDES=`$JTSCONFIG --includedir`
+ JTS_LIBDIR=`$JTSCONFIG --libdir`
+fi
+
+
+# Extract the first word of "flex", so it can be a program name with args.
+set dummy flex; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_path_FLEX+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ case $FLEX in
+ [\\/]* | ?:[\\/]*)
+ ac_cv_path_FLEX="$FLEX" # Let the user override the test with a path.
+ ;;
+ *)
+ as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_path_FLEX="$as_dir/$ac_word$ac_exec_ext"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+ ;;
+esac
+fi
+FLEX=$ac_cv_path_FLEX
+
+if test -n "$FLEX"; then
+ echo "$as_me:$LINENO: result: $FLEX" >&5
+echo "${ECHO_T}$FLEX" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+if test -z "$FLEX"; then
+ { { echo "$as_me:$LINENO: error: Can't find 'flex'" >&5
+echo "$as_me: error: Can't find 'flex'" >&2;}
+ { (exit 1); exit 1; }; };
+fi
+
+
+# Extract the first word of "dllwrap", so it can be a program name with args.
+set dummy dllwrap; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_path_DLLWRAP+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ case $DLLWRAP in
+ [\\/]* | ?:[\\/]*)
+ ac_cv_path_DLLWRAP="$DLLWRAP" # Let the user override the test with a path.
+ ;;
+ *)
+ as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_path_DLLWRAP="$as_dir/$ac_word$ac_exec_ext"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+ ;;
+esac
+fi
+DLLWRAP=$ac_cv_path_DLLWRAP
+
+if test -n "$DLLWRAP"; then
+ echo "$as_me:$LINENO: result: $DLLWRAP" >&5
+echo "${ECHO_T}$DLLWRAP" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+
+# Extract the first word of "dlltool", so it can be a program name with args.
+set dummy dlltool; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_path_DLLTOOL+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ case $DLLTOOL in
+ [\\/]* | ?:[\\/]*)
+ ac_cv_path_DLLTOOL="$DLLTOOL" # Let the user override the test with a path.
+ ;;
+ *)
+ as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_path_DLLTOOL="$as_dir/$ac_word$ac_exec_ext"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+ ;;
+esac
+fi
+DLLTOOL=$ac_cv_path_DLLTOOL
+
+if test -n "$DLLTOOL"; then
+ echo "$as_me:$LINENO: result: $DLLTOOL" >&5
+echo "${ECHO_T}$DLLTOOL" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+
+for ac_prog in 'bison -y' byacc
+do
+ # Extract the first word of "$ac_prog", so it can be a program name with args.
+set dummy $ac_prog; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_prog_YACC+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ if test -n "$YACC"; then
+ ac_cv_prog_YACC="$YACC" # Let the user override the test.
+else
+as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_prog_YACC="$ac_prog"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+fi
+fi
+YACC=$ac_cv_prog_YACC
+if test -n "$YACC"; then
+ echo "$as_me:$LINENO: result: $YACC" >&5
+echo "${ECHO_T}$YACC" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+ test -n "$YACC" && break
+done
+test -n "$YACC" || YACC="yacc"
+
+if test -z "$YACC"; then
+ { { echo "$as_me:$LINENO: error: Can't find 'yacc'" >&5
+echo "$as_me: error: Can't find 'yacc'" >&2;}
+ { (exit 1); exit 1; }; };
+fi
+
+
+INSTALL=`pwd`"/install-sh"
+
+
+# Extract the first word of "perl", so it can be a program name with args.
+set dummy perl; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_path_PERL+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ case $PERL in
+ [\\/]* | ?:[\\/]*)
+ ac_cv_path_PERL="$PERL" # Let the user override the test with a path.
+ ;;
+ *)
+ as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_path_PERL="$as_dir/$ac_word$ac_exec_ext"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+ ;;
+esac
+fi
+PERL=$ac_cv_path_PERL
+
+if test -n "$PERL"; then
+ echo "$as_me:$LINENO: result: $PERL" >&5
+echo "${ECHO_T}$PERL" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+if test -z "$PERL"; then
+ { { echo "$as_me:$LINENO: error: Can't find 'perl'" >&5
+echo "$as_me: error: Can't find 'perl'" >&2;}
+ { (exit 1); exit 1; }; };
+fi
+
+
+docdir='${prefix}/share/doc'
+
+# Check whether --with-docdir or --without-docdir was given.
+if test "${with_docdir+set}" = set; then
+ withval="$with_docdir"
+ if test "$with_docdir" = "yes"; then
+ { { echo "$as_me:$LINENO: error: option --with-docdir requires an argument" >&5
+echo "$as_me: error: option --with-docdir requires an argument" >&2;}
+ { (exit 1); exit 1; }; }
+ fi
+ if test "$with_docdir" != "no"; then
+ docdir="$with_docdir"
+ fi
+
+fi;
+
+
+XSLBASE=
+SEARCHPATH="
+ /usr/share/sgml/docbook/xsl-stylesheets
+ /usr/share/xml/docbook/stylesheet/nwalsh
+ /usr/share/sgml/docbook/stylesheet/xsl/nwalsh
+"
+for p in ${SEARCHPATH}; do
+ if test -r ${p}/html/docbook.xsl; then
+ XSLBASE=${p}
+ break
+ fi
+done
+
+# Extract the first word of "xsltproc", so it can be a program name with args.
+set dummy xsltproc; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_path_XSLTPROC+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ case $XSLTPROC in
+ [\\/]* | ?:[\\/]*)
+ ac_cv_path_XSLTPROC="$XSLTPROC" # Let the user override the test with a path.
+ ;;
+ *)
+ as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_path_XSLTPROC="$as_dir/$ac_word$ac_exec_ext"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+ ;;
+esac
+fi
+XSLTPROC=$ac_cv_path_XSLTPROC
+
+if test -n "$XSLTPROC"; then
+ echo "$as_me:$LINENO: result: $XSLTPROC" >&5
+echo "${ECHO_T}$XSLTPROC" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+# Extract the first word of "pdfxmltex", so it can be a program name with args.
+set dummy pdfxmltex; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_path_PDFXMLTEX+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ case $PDFXMLTEX in
+ [\\/]* | ?:[\\/]*)
+ ac_cv_path_PDFXMLTEX="$PDFXMLTEX" # Let the user override the test with a path.
+ ;;
+ *)
+ as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_path_PDFXMLTEX="$as_dir/$ac_word$ac_exec_ext"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+ ;;
+esac
+fi
+PDFXMLTEX=$ac_cv_path_PDFXMLTEX
+
+if test -n "$PDFXMLTEX"; then
+ echo "$as_me:$LINENO: result: $PDFXMLTEX" >&5
+echo "${ECHO_T}$PDFXMLTEX" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+# Extract the first word of "db2pdf", so it can be a program name with args.
+set dummy db2pdf; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_path_DB2PDF+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ case $DB2PDF in
+ [\\/]* | ?:[\\/]*)
+ ac_cv_path_DB2PDF="$DB2PDF" # Let the user override the test with a path.
+ ;;
+ *)
+ as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_path_DB2PDF="$as_dir/$ac_word$ac_exec_ext"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+ ;;
+esac
+fi
+DB2PDF=$ac_cv_path_DB2PDF
+
+if test -n "$DB2PDF"; then
+ echo "$as_me:$LINENO: result: $DB2PDF" >&5
+echo "${ECHO_T}$DB2PDF" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+# Extract the first word of "jw", so it can be a program name with args.
+set dummy jw; ac_word=$2
+echo "$as_me:$LINENO: checking for $ac_word" >&5
+echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
+if test "${ac_cv_path_JW+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ case $JW in
+ [\\/]* | ?:[\\/]*)
+ ac_cv_path_JW="$JW" # Let the user override the test with a path.
+ ;;
+ *)
+ as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
+ ac_cv_path_JW="$as_dir/$ac_word$ac_exec_ext"
+ echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
+ break 2
+ fi
+done
+done
+
+ ;;
+esac
+fi
+JW=$ac_cv_path_JW
+
+if test -n "$JW"; then
+ echo "$as_me:$LINENO: result: $JW" >&5
+echo "${ECHO_T}$JW" >&6
+else
+ echo "$as_me:$LINENO: result: no" >&5
+echo "${ECHO_T}no" >&6
+fi
+
+
+
+
+
+DOC_RULE=requirements_not_met
+if test -n "${XSLBASE}"; then
+ if test -n "${XSLTPROC}"; then
+ DOC_RULE=html/postgis.html
+ else
+ if test -n "${JW}"; then
+ DOC_RULE=jw
+ fi
+ fi
+fi
+
+
+
+if test $USE_JTS -gt 0; then
+ USE_GEOS=0
+fi
+
+#
+# Extract PostgreSQL paths from pg_config
+##
+
+#
+# Prefix (pg_prefix)
+#
+pg_prefix=/usr/local/pgsql
+pg_eprefix=
+pg_docdir=
+pg_datadir=
+pg_mandir=
+pg_bindir="`${PGCONFIG} --bindir`"
+pg_pkglibdir="`${PGCONFIG} --pkglibdir`"
+for v in `${PGCONFIG} --configure`; do
+ strip=`echo $v | sed "s/'//g"`
+ var=`echo "$strip" | cut -d= -f1`
+ if test "$var" = "--prefix"; then
+ pg_prefix=`echo "$strip" | cut -d= -f2`
+ elif test "$var" = "--exec-prefix"; then
+ pg_eprefix=`echo "$strip" | cut -d= -f2`
+ elif test "$var" = "--docdir"; then
+ pg_docdir=`echo "$strip" | cut -d= -f2`
+ elif test "$var" = "--with-docdir"; then
+ pg_docdir=`echo "$strip" | cut -d= -f2`
+ elif test "$var" = "--datadir"; then
+ pg_datadir=`echo "$strip" | cut -d= -f2`
+ elif test "$var" = "--mandir"; then
+ pg_mandir=`echo "$strip" | cut -d= -f2`
+ elif test "$var" = "--with-template"; then
+ PGTEMPLATE=`echo "$strip" | cut -d= -f2`
+ fi
+done
+#
+# We set these defaults after scan of
+# pg_config --configure to safely expand pg_prefix
+# We need expansion for the 'postgresq' path component
+# addition below (default paths take from pg_config)
+#
+if test -z "$pg_eprefix"; then pg_eprefix=${pg_prefix}; fi
+if test -z "$pg_docdir"; then pg_docdir=${pg_prefix}'/doc'; fi
+if test -z "$pg_datadir"; then pg_datadir=${pg_prefix}'/share'; fi
+if test -z "$pg_mandir"; then pg_mandir=${pg_prefix}'/man'; fi
+
+# Use old layout by default
+use_new_layout=0
+
+if test "$prefix" != 'NONE'; then
+ use_new_layout=1
+fi
+
+if test "${use_new_layout}" = "1"; then
+ LPATH=$libdir
+else
+
+ #
+ # Use old layout: everything under PGSQL paths
+ # Note: still allow override by user, this is
+ # done checking each variable against its
+ # default value, if it has a different
+ # value do not use PGSQL versions
+ #
+
+ if test "$prefix" = 'NONE'; then
+ prefix=${pg_prefix}
+ fi
+
+ if test "$docdir" = '${prefix}/share/doc'; then
+ docdir=${pg_docdir}
+ #
+ # If docdir contains no 'pgsql' or 'postgres'
+ # add the suffix. This is derived from
+ # PGSQL_SRC/src/Makefile.global
+ #
+ if expr "${docdir}" : ".*/pgsql" > /dev/null ; then :; else
+ if expr "${docdir}" : ".*/postgres" > /dev/null ; then :; else
+ docdir=${docdir}"/postgresql"
+ fi
+ fi
+ # Add the "contrib" part
+ docdir=${docdir}"/contrib"
+ fi
+
+ if test "$datadir" = '${prefix}/share'; then
+ datadir=${pg_datadir}
+ #
+ # If datadir contains no 'pgsql' or 'postgres'
+ # add the suffix. This is derived from
+ # PGSQL_SRC/src/Makefile.global
+ #
+ if expr "${datadir}" : ".*/pgsql" > /dev/null ; then :; else
+ if expr "${datadir}" : ".*/postgres" > /dev/null ; then :; else
+ datadir=${datadir}"/postgresql"
+ fi
+ fi
+ # Add the "contrib" part
+ datadir=${datadir}"/contrib"
+ fi
+
+ if test "$mandir" = '${prefix}/man'; then
+ mandir=${pg_mandir}
+ fi
+
+ if test "$bindir" = '${exec_prefix}/bin'; then
+ bindir=${pg_bindir}
+ fi
+
+ if test "$libdir" = '${exec_prefix}/lib'; then
+ libdir=${pg_pkglibdir}
+ LPATH='\$$libdir'
+ else
+ LPATH=$libdir
+ fi
+fi
+
+# --with-template parsing is done in the single
+# pg_config --configure scan above
+echo "$as_me:$LINENO: checking which template to use" >&5
+echo $ECHO_N "checking which template to use... $ECHO_C" >&6
+template=$PGTEMPLATE
+
+case $host_os in
+ aix*) template=aix ;;
+ beos*) template=beos ;;
+ bsdi*) template=bsdi ;;
+ cygwin*) template=cygwin ;;
+ darwin*) template=darwin ;;
+ dgux*) template=dgux ;;
+ freebsd*) template=freebsd ;;
+ hpux*) template=hpux ;;
+ irix*) template=irix ;;
+ linux*|gnu*|k*bsd*-gnu)
+ template=linux ;;
+ mingw*) template=win32 ;;
+ netbsd*) template=netbsd ;;
+nextstep*) template=nextstep ;;
+ openbsd*) template=openbsd ;;
+ osf*) template=osf ;;
+ qnx*) template=qnx4 ;;
+ sco*) template=sco ;;
+ solaris*) template=solaris ;;
+ sunos*) template=sunos4 ;;
+ sysv4.2*)
+ case $host_vendor in
+ univel) template=univel ;;
+ esac ;;
+ sysv4*) template=svr4 ;;
+ sysv5*) template=unixware ;;
+ ultrix*) template=ultrix4 ;;
+esac
+
+ if test x"$template" = x"" ; then
+ { { echo "$as_me:$LINENO: error:
+*******************************************************************
+PostgreSQL has apparently not been ported to your platform yet.
+To try a manual configuration, look into the src/template directory
+for a similar platform and use the '--with-template=' option.
+
+Please also contact <pgsql-ports at postgresql.org> to see about
+rectifying this. Include the above 'checking host system type...'
+line.
+*******************************************************************
+" >&5
+echo "$as_me: error:
+*******************************************************************
+PostgreSQL has apparently not been ported to your platform yet.
+To try a manual configuration, look into the src/template directory
+for a similar platform and use the '--with-template=' option.
+
+Please also contact <pgsql-ports at postgresql.org> to see about
+rectifying this. Include the above 'checking host system type...'
+line.
+*******************************************************************
+" >&2;}
+ { (exit 1); exit 1; }; }
+ fi
+
+echo "$as_me:$LINENO: result: $template" >&5
+echo "${ECHO_T}$template" >&6
+
+PORTNAME=$template
+
+
+
+#
+# OS-specific settings
+#
+
+
+
+
+
+# host_os is defined by AC_CANONICAL_HOST
+HOST_OS=$host_os
+DLSUFFIX=.so
+DLFLAGS=-shared
+EXE=
+case $host_os in
+ *mingw*)
+ PGBEINCLUDES="$PGBEINCLUDES $PGBEINCLUDES/port/win32"
+ DLSUFFIX=.dll
+ DLFLAGS='${PGBELIBS}'
+ EXE=.exe
+ ;;
+ *darwin*)
+ DLFLAGS="-no-cpp-precomp -flat_namespace -undefined suppress -multiply_defined suppress"
+ ;;
+esac
+
+# Assume system is ELF if it predefines __ELF__ as 1,
+# otherwise believe host_os based default.
+case $host_os in
+ freebsd1*|freebsd2*) elf=no;;
+ freebsd3*|freebsd4*) elf=yes;;
+esac
+
+cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+#if __ELF__
+ yes
+#endif
+
+_ACEOF
+if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
+ $EGREP "yes" >/dev/null 2>&1; then
+ ELF_SYS=true
+else
+ if test "X$elf" = "Xyes" ; then
+ ELF_SYS=true
+else
+ ELF_SYS=
+fi
+fi
+rm -f conftest*
+
+
+
+
+
+ ac_config_files="$ac_config_files Makefile.config"
+cat >confcache <<\_ACEOF
+# This file is a shell script that caches the results of configure
+# tests run on this system so they can be shared between configure
+# scripts and configure runs, see configure's option --config-cache.
+# It is not useful on other systems. If it contains results you don't
+# want to keep, you may remove or edit it.
+#
+# config.status only pays attention to the cache file if you give it
+# the --recheck option to rerun configure.
+#
+# `ac_cv_env_foo' variables (set or unset) will be overridden when
+# loading this file, other *unset* `ac_cv_foo' will be assigned the
+# following values.
+
+_ACEOF
+
+# The following way of writing the cache mishandles newlines in values,
+# but we know of no workaround that is simple, portable, and efficient.
+# So, don't put newlines in cache variables' values.
+# Ultrix sh set writes to stderr and can't be redirected directly,
+# and sets the high bit in the cache file unless we assign to the vars.
+{
+ (set) 2>&1 |
+ case `(ac_space=' '; set | grep ac_space) 2>&1` in
+ *ac_space=\ *)
+ # `set' does not quote correctly, so add quotes (double-quote
+ # substitution turns \\\\ into \\, and sed turns \\ into \).
+ sed -n \
+ "s/'/'\\\\''/g;
+ s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\\2'/p"
+ ;;
+ *)
+ # `set' quotes correctly as required by POSIX, so do not add quotes.
+ sed -n \
+ "s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1=\\2/p"
+ ;;
+ esac;
+} |
+ sed '
+ t clear
+ : clear
+ s/^\([^=]*\)=\(.*[{}].*\)$/test "${\1+set}" = set || &/
+ t end
+ /^ac_cv_env/!s/^\([^=]*\)=\(.*\)$/\1=${\1=\2}/
+ : end' >>confcache
+if diff $cache_file confcache >/dev/null 2>&1; then :; else
+ if test -w $cache_file; then
+ test "x$cache_file" != "x/dev/null" && echo "updating cache $cache_file"
+ cat confcache >$cache_file
+ else
+ echo "not updating unwritable cache $cache_file"
+ fi
+fi
+rm -f confcache
+
+test "x$prefix" = xNONE && prefix=$ac_default_prefix
+# Let make expand exec_prefix.
+test "x$exec_prefix" = xNONE && exec_prefix='${prefix}'
+
+# VPATH may cause trouble with some makes, so we remove $(srcdir),
+# ${srcdir} and @srcdir@ from VPATH if srcdir is ".", strip leading and
+# trailing colons and then remove the whole line if VPATH becomes empty
+# (actually we leave an empty line to preserve line numbers).
+if test "x$srcdir" = x.; then
+ ac_vpsub='/^[ ]*VPATH[ ]*=/{
+s/:*\$(srcdir):*/:/;
+s/:*\${srcdir}:*/:/;
+s/:*@srcdir@:*/:/;
+s/^\([^=]*=[ ]*\):*/\1/;
+s/:*$//;
+s/^[^=]*=[ ]*$//;
+}'
+fi
+
+DEFS=-DHAVE_CONFIG_H
+
+ac_libobjs=
+ac_ltlibobjs=
+for ac_i in : $LIB@&t at OBJS; do test "x$ac_i" = x: && continue
+ # 1. Remove the extension, and $U if already installed.
+ ac_i=`echo "$ac_i" |
+ sed 's/\$U\././;s/\.o$//;s/\.obj$//'`
+ # 2. Add them.
+ ac_libobjs="$ac_libobjs $ac_i\$U.$ac_objext"
+ ac_ltlibobjs="$ac_ltlibobjs $ac_i"'$U.lo'
+done
+LIB@&t at OBJS=$ac_libobjs
+
+LTLIBOBJS=$ac_ltlibobjs
+
+
+
+: ${CONFIG_STATUS=./config.status}
+ac_clean_files_save=$ac_clean_files
+ac_clean_files="$ac_clean_files $CONFIG_STATUS"
+{ echo "$as_me:$LINENO: creating $CONFIG_STATUS" >&5
+echo "$as_me: creating $CONFIG_STATUS" >&6;}
+cat >$CONFIG_STATUS <<_ACEOF
+#! $SHELL
+# Generated by $as_me.
+# Run this file to recreate the current configuration.
+# Compiler output produced by configure, useful for debugging
+# configure, is in config.log if it exists.
+
+debug=false
+ac_cs_recheck=false
+ac_cs_silent=false
+SHELL=\${CONFIG_SHELL-$SHELL}
+_ACEOF
+
+cat >>$CONFIG_STATUS <<\_ACEOF
+## --------------------- ##
+## M4sh Initialization. ##
+## --------------------- ##
+
+# Be Bourne compatible
+if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then
+ emulate sh
+ NULLCMD=:
+ # Zsh 3.x and 4.x performs word splitting on ${1+"$@"}, which
+ # is contrary to our usage. Disable this feature.
+ alias -g '${1+"$@"}'='"$@"'
+elif test -n "${BASH_VERSION+set}" && (set -o posix) >/dev/null 2>&1; then
+ set -o posix
+fi
+DUALCASE=1; export DUALCASE # for MKS sh
+
+# Support unset when possible.
+if ( (MAIL=60; unset MAIL) || exit) >/dev/null 2>&1; then
+ as_unset=unset
+else
+ as_unset=false
+fi
+
+
+# Work around bugs in pre-3.0 UWIN ksh.
+$as_unset ENV MAIL MAILPATH
+PS1='$ '
+PS2='> '
+PS4='+ '
+
+# NLS nuisances.
+for as_var in \
+ LANG LANGUAGE LC_ADDRESS LC_ALL LC_COLLATE LC_CTYPE LC_IDENTIFICATION \
+ LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER \
+ LC_TELEPHONE LC_TIME
+do
+ if (set +x; test -z "`(eval $as_var=C; export $as_var) 2>&1`"); then
+ eval $as_var=C; export $as_var
+ else
+ $as_unset $as_var
+ fi
+done
+
+# Required to use basename.
+if expr a : '\(a\)' >/dev/null 2>&1; then
+ as_expr=expr
+else
+ as_expr=false
+fi
+
+if (basename /) >/dev/null 2>&1 && test "X`basename / 2>&1`" = "X/"; then
+ as_basename=basename
+else
+ as_basename=false
+fi
+
+
+# Name of the executable.
+as_me=`$as_basename "$0" ||
+$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
+ X"$0" : 'X\(//\)$' \| \
+ X"$0" : 'X\(/\)$' \| \
+ . : '\(.\)' 2>/dev/null ||
+echo X/"$0" |
+ sed '/^.*\/\([^/][^/]*\)\/*$/{ s//\1/; q; }
+ /^X\/\(\/\/\)$/{ s//\1/; q; }
+ /^X\/\(\/\).*/{ s//\1/; q; }
+ s/.*/./; q'`
+
+
+# PATH needs CR, and LINENO needs CR and PATH.
+# Avoid depending upon Character Ranges.
+as_cr_letters='abcdefghijklmnopqrstuvwxyz'
+as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
+as_cr_Letters=$as_cr_letters$as_cr_LETTERS
+as_cr_digits='0123456789'
+as_cr_alnum=$as_cr_Letters$as_cr_digits
+
+# The user is always right.
+if test "${PATH_SEPARATOR+set}" != set; then
+ echo "#! /bin/sh" >conf$$.sh
+ echo "exit 0" >>conf$$.sh
+ chmod +x conf$$.sh
+ if (PATH="/nonexistent;."; conf$$.sh) >/dev/null 2>&1; then
+ PATH_SEPARATOR=';'
+ else
+ PATH_SEPARATOR=:
+ fi
+ rm -f conf$$.sh
+fi
+
+
+ as_lineno_1=$LINENO
+ as_lineno_2=$LINENO
+ as_lineno_3=`(expr $as_lineno_1 + 1) 2>/dev/null`
+ test "x$as_lineno_1" != "x$as_lineno_2" &&
+ test "x$as_lineno_3" = "x$as_lineno_2" || {
+ # Find who we are. Look in the path if we contain no path at all
+ # relative or not.
+ case $0 in
+ *[\\/]* ) as_myself=$0 ;;
+ *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in $PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
+done
+
+ ;;
+ esac
+ # We did not find ourselves, most probably we were run as `sh COMMAND'
+ # in which case we are not to be found in the path.
+ if test "x$as_myself" = x; then
+ as_myself=$0
+ fi
+ if test ! -f "$as_myself"; then
+ { { echo "$as_me:$LINENO: error: cannot find myself; rerun with an absolute path" >&5
+echo "$as_me: error: cannot find myself; rerun with an absolute path" >&2;}
+ { (exit 1); exit 1; }; }
+ fi
+ case $CONFIG_SHELL in
+ '')
+ as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
+for as_dir in /bin$PATH_SEPARATOR/usr/bin$PATH_SEPARATOR$PATH
+do
+ IFS=$as_save_IFS
+ test -z "$as_dir" && as_dir=.
+ for as_base in sh bash ksh sh5; do
+ case $as_dir in
+ /*)
+ if ("$as_dir/$as_base" -c '
+ as_lineno_1=$LINENO
+ as_lineno_2=$LINENO
+ as_lineno_3=`(expr $as_lineno_1 + 1) 2>/dev/null`
+ test "x$as_lineno_1" != "x$as_lineno_2" &&
+ test "x$as_lineno_3" = "x$as_lineno_2" ') 2>/dev/null; then
+ $as_unset BASH_ENV || test "${BASH_ENV+set}" != set || { BASH_ENV=; export BASH_ENV; }
+ $as_unset ENV || test "${ENV+set}" != set || { ENV=; export ENV; }
+ CONFIG_SHELL=$as_dir/$as_base
+ export CONFIG_SHELL
+ exec "$CONFIG_SHELL" "$0" ${1+"$@"}
+ fi;;
+ esac
+ done
+done
+;;
+ esac
+
+ # Create $as_me.lineno as a copy of $as_myself, but with $LINENO
+ # uniformly replaced by the line number. The first 'sed' inserts a
+ # line-number line before each line; the second 'sed' does the real
+ # work. The second script uses 'N' to pair each line-number line
+ # with the numbered line, and appends trailing '-' during
+ # substitution so that $LINENO is not a special case at line end.
+ # (Raja R Harinath suggested sed '=', and Paul Eggert wrote the
+ # second 'sed' script. Blame Lee E. McMahon for sed's syntax. :-)
+ sed '=' <$as_myself |
+ sed '
+ N
+ s,$,-,
+ : loop
+ s,^\(['$as_cr_digits']*\)\(.*\)[$]LINENO\([^'$as_cr_alnum'_]\),\1\2\1\3,
+ t loop
+ s,-$,,
+ s,^['$as_cr_digits']*\n,,
+ ' >$as_me.lineno &&
+ chmod +x $as_me.lineno ||
+ { { echo "$as_me:$LINENO: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&5
+echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2;}
+ { (exit 1); exit 1; }; }
+
+ # Don't try to exec as it changes $[0], causing all sort of problems
+ # (the dirname of $[0] is not the place where we might find the
+ # original and so on. Autoconf is especially sensible to this).
+ . ./$as_me.lineno
+ # Exit status is that of the last command.
+ exit
+}
+
+
+case `echo "testing\c"; echo 1,2,3`,`echo -n testing; echo 1,2,3` in
+ *c*,-n*) ECHO_N= ECHO_C='
+' ECHO_T=' ' ;;
+ *c*,* ) ECHO_N=-n ECHO_C= ECHO_T= ;;
+ *) ECHO_N= ECHO_C='\c' ECHO_T= ;;
+esac
+
+if expr a : '\(a\)' >/dev/null 2>&1; then
+ as_expr=expr
+else
+ as_expr=false
+fi
+
+rm -f conf$$ conf$$.exe conf$$.file
+echo >conf$$.file
+if ln -s conf$$.file conf$$ 2>/dev/null; then
+ # We could just check for DJGPP; but this test a) works b) is more generic
+ # and c) will remain valid once DJGPP supports symlinks (DJGPP 2.04).
+ if test -f conf$$.exe; then
+ # Don't use ln at all; we don't have any links
+ as_ln_s='cp -p'
+ else
+ as_ln_s='ln -s'
+ fi
+elif ln conf$$.file conf$$ 2>/dev/null; then
+ as_ln_s=ln
+else
+ as_ln_s='cp -p'
+fi
+rm -f conf$$ conf$$.exe conf$$.file
+
+if mkdir -p . 2>/dev/null; then
+ as_mkdir_p=:
+else
+ test -d ./-p && rmdir ./-p
+ as_mkdir_p=false
+fi
+
+as_executable_p="test -f"
+
+# Sed expression to map a string onto a valid CPP name.
+as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'"
+
+# Sed expression to map a string onto a valid variable name.
+as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'"
+
+
+# IFS
+# We need space, tab and new line, in precisely that order.
+as_nl='
+'
+IFS=" $as_nl"
+
+# CDPATH.
+$as_unset CDPATH
+
+exec 6>&1
+
+# Open the log real soon, to keep \$[0] and so on meaningful, and to
+# report actual input values of CONFIG_FILES etc. instead of their
+# values after options handling. Logging --version etc. is OK.
+exec 5>>config.log
+{
+ echo
+ sed 'h;s/./-/g;s/^.../@%:@@%:@ /;s/...$/ @%:@@%:@/;p;x;p;x' <<_ASBOX
+@%:@@%:@ Running $as_me. @%:@@%:@
+_ASBOX
+} >&5
+cat >&5 <<_CSEOF
+
+This file was extended by $as_me, which was
+generated by GNU Autoconf 2.59. Invocation command line was
+
+ CONFIG_FILES = $CONFIG_FILES
+ CONFIG_HEADERS = $CONFIG_HEADERS
+ CONFIG_LINKS = $CONFIG_LINKS
+ CONFIG_COMMANDS = $CONFIG_COMMANDS
+ $ $0 $@
+
+_CSEOF
+echo "on `(hostname || uname -n) 2>/dev/null | sed 1q`" >&5
+echo >&5
+_ACEOF
+
+# Files that config.status was made for.
+if test -n "$ac_config_files"; then
+ echo "config_files=\"$ac_config_files\"" >>$CONFIG_STATUS
+fi
+
+if test -n "$ac_config_headers"; then
+ echo "config_headers=\"$ac_config_headers\"" >>$CONFIG_STATUS
+fi
+
+if test -n "$ac_config_links"; then
+ echo "config_links=\"$ac_config_links\"" >>$CONFIG_STATUS
+fi
+
+if test -n "$ac_config_commands"; then
+ echo "config_commands=\"$ac_config_commands\"" >>$CONFIG_STATUS
+fi
+
+cat >>$CONFIG_STATUS <<\_ACEOF
+
+ac_cs_usage="\
+\`$as_me' instantiates files from templates according to the
+current configuration.
+
+Usage: $0 [OPTIONS] [FILE]...
+
+ -h, --help print this help, then exit
+ -V, --version print version number, then exit
+ -q, --quiet do not print progress messages
+ -d, --debug don't remove temporary files
+ --recheck update $as_me by reconfiguring in the same conditions
+ --file=FILE[:TEMPLATE]
+ instantiate the configuration file FILE
+ --header=FILE[:TEMPLATE]
+ instantiate the configuration header FILE
+
+Configuration files:
+$config_files
+
+Configuration headers:
+$config_headers
+
+Report bugs to <bug-autoconf at gnu.org>."
+_ACEOF
+
+cat >>$CONFIG_STATUS <<_ACEOF
+ac_cs_version="\\
+config.status
+configured by $0, generated by GNU Autoconf 2.59,
+ with options \\"`echo "$ac_configure_args" | sed 's/[\\""\`\$]/\\\\&/g'`\\"
+
+Copyright (C) 2003 Free Software Foundation, Inc.
+This config.status script is free software; the Free Software Foundation
+gives unlimited permission to copy, distribute and modify it."
+srcdir=$srcdir
+_ACEOF
+
+cat >>$CONFIG_STATUS <<\_ACEOF
+# If no file are specified by the user, then we need to provide default
+# value. By we need to know if files were specified by the user.
+ac_need_defaults=:
+while test $# != 0
+do
+ case $1 in
+ --*=*)
+ ac_option=`expr "x$1" : 'x\([^=]*\)='`
+ ac_optarg=`expr "x$1" : 'x[^=]*=\(.*\)'`
+ ac_shift=:
+ ;;
+ -*)
+ ac_option=$1
+ ac_optarg=$2
+ ac_shift=shift
+ ;;
+ *) # This is not an option, so the user has probably given explicit
+ # arguments.
+ ac_option=$1
+ ac_need_defaults=false;;
+ esac
+
+ case $ac_option in
+ # Handling of the options.
+_ACEOF
+cat >>$CONFIG_STATUS <<\_ACEOF
+ -recheck | --recheck | --rechec | --reche | --rech | --rec | --re | --r)
+ ac_cs_recheck=: ;;
+ --version | --vers* | -V )
+ echo "$ac_cs_version"; exit 0 ;;
+ --he | --h)
+ # Conflict between --help and --header
+ { { echo "$as_me:$LINENO: error: ambiguous option: $1
+Try \`$0 --help' for more information." >&5
+echo "$as_me: error: ambiguous option: $1
+Try \`$0 --help' for more information." >&2;}
+ { (exit 1); exit 1; }; };;
+ --help | --hel | -h )
+ echo "$ac_cs_usage"; exit 0 ;;
+ --debug | --d* | -d )
+ debug=: ;;
+ --file | --fil | --fi | --f )
+ $ac_shift
+ CONFIG_FILES="$CONFIG_FILES $ac_optarg"
+ ac_need_defaults=false;;
+ --header | --heade | --head | --hea )
+ $ac_shift
+ CONFIG_HEADERS="$CONFIG_HEADERS $ac_optarg"
+ ac_need_defaults=false;;
+ -q | -quiet | --quiet | --quie | --qui | --qu | --q \
+ | -silent | --silent | --silen | --sile | --sil | --si | --s)
+ ac_cs_silent=: ;;
+
+ # This is an error.
+ -*) { { echo "$as_me:$LINENO: error: unrecognized option: $1
+Try \`$0 --help' for more information." >&5
+echo "$as_me: error: unrecognized option: $1
+Try \`$0 --help' for more information." >&2;}
+ { (exit 1); exit 1; }; } ;;
+
+ *) ac_config_targets="$ac_config_targets $1" ;;
+
+ esac
+ shift
+done
+
+ac_configure_extra_args=
+
+if $ac_cs_silent; then
+ exec 6>/dev/null
+ ac_configure_extra_args="$ac_configure_extra_args --silent"
+fi
+
+_ACEOF
+cat >>$CONFIG_STATUS <<_ACEOF
+if \$ac_cs_recheck; then
+ echo "running $SHELL $0 " $ac_configure_args \$ac_configure_extra_args " --no-create --no-recursion" >&6
+ exec $SHELL $0 $ac_configure_args \$ac_configure_extra_args --no-create --no-recursion
+fi
+
+_ACEOF
+
+
+
+
+
+cat >>$CONFIG_STATUS <<\_ACEOF
+for ac_config_target in $ac_config_targets
+do
+ case "$ac_config_target" in
+ # Handling of arguments.
+ "Makefile.config" ) CONFIG_FILES="$CONFIG_FILES Makefile.config" ;;
+ "config.h" ) CONFIG_HEADERS="$CONFIG_HEADERS config.h" ;;
+ *) { { echo "$as_me:$LINENO: error: invalid argument: $ac_config_target" >&5
+echo "$as_me: error: invalid argument: $ac_config_target" >&2;}
+ { (exit 1); exit 1; }; };;
+ esac
+done
+
+# If the user did not use the arguments to specify the items to instantiate,
+# then the envvar interface is used. Set only those that are not.
+# We use the long form for the default assignment because of an extremely
+# bizarre bug on SunOS 4.1.3.
+if $ac_need_defaults; then
+ test "${CONFIG_FILES+set}" = set || CONFIG_FILES=$config_files
+ test "${CONFIG_HEADERS+set}" = set || CONFIG_HEADERS=$config_headers
+fi
+
+# Have a temporary directory for convenience. Make it in the build tree
+# simply because there is no reason to put it here, and in addition,
+# creating and moving files from /tmp can sometimes cause problems.
+# Create a temporary directory, and hook for its removal unless debugging.
+$debug ||
+{
+ trap 'exit_status=$?; rm -rf $tmp && exit $exit_status' 0
+ trap '{ (exit 1); exit 1; }' 1 2 13 15
+}
+
+# Create a (secure) tmp directory for tmp files.
+
+{
+ tmp=`(umask 077 && mktemp -d -q "./confstatXXXXXX") 2>/dev/null` &&
+ test -n "$tmp" && test -d "$tmp"
+} ||
+{
+ tmp=./confstat$$-$RANDOM
+ (umask 077 && mkdir $tmp)
+} ||
+{
+ echo "$me: cannot create a temporary directory in ." >&2
+ { (exit 1); exit 1; }
+}
+
+_ACEOF
+
+cat >>$CONFIG_STATUS <<_ACEOF
+
+#
+# CONFIG_FILES section.
+#
+
+# No need to generate the scripts if there are no CONFIG_FILES.
+# This happens for instance when ./config.status config.h
+if test -n "\$CONFIG_FILES"; then
+ # Protect against being on the right side of a sed subst in config.status.
+ sed 's/,@/@@/; s/@,/@@/; s/,;t t\$/@;t t/; /@;t t\$/s/[\\\\&,]/\\\\&/g;
+ s/@@/,@/; s/@@/@,/; s/@;t t\$/,;t t/' >\$tmp/subs.sed <<\\CEOF
+s, at SHELL@,$SHELL,;t t
+s, at PATH_SEPARATOR@,$PATH_SEPARATOR,;t t
+s, at PACKAGE_NAME@,$PACKAGE_NAME,;t t
+s, at PACKAGE_TARNAME@,$PACKAGE_TARNAME,;t t
+s, at PACKAGE_VERSION@,$PACKAGE_VERSION,;t t
+s, at PACKAGE_STRING@,$PACKAGE_STRING,;t t
+s, at PACKAGE_BUGREPORT@,$PACKAGE_BUGREPORT,;t t
+s, at exec_prefix@,$exec_prefix,;t t
+s, at prefix@,$prefix,;t t
+s, at program_transform_name@,$program_transform_name,;t t
+s, at bindir@,$bindir,;t t
+s, at sbindir@,$sbindir,;t t
+s, at libexecdir@,$libexecdir,;t t
+s, at datadir@,$datadir,;t t
+s, at sysconfdir@,$sysconfdir,;t t
+s, at sharedstatedir@,$sharedstatedir,;t t
+s, at localstatedir@,$localstatedir,;t t
+s, at libdir@,$libdir,;t t
+s, at includedir@,$includedir,;t t
+s, at oldincludedir@,$oldincludedir,;t t
+s, at infodir@,$infodir,;t t
+s, at mandir@,$mandir,;t t
+s, at build_alias@,$build_alias,;t t
+s, at host_alias@,$host_alias,;t t
+s, at target_alias@,$target_alias,;t t
+s, at DEFS@,$DEFS,;t t
+s, at ECHO_C@,$ECHO_C,;t t
+s, at ECHO_N@,$ECHO_N,;t t
+s, at ECHO_T@,$ECHO_T,;t t
+s, at LIBS@,$LIBS,;t t
+s, at CC@,$CC,;t t
+s, at CFLAGS@,$CFLAGS,;t t
+s, at LDFLAGS@,$LDFLAGS,;t t
+s, at CPPFLAGS@,$CPPFLAGS,;t t
+s, at ac_ct_CC@,$ac_ct_CC,;t t
+s, at EXEEXT@,$EXEEXT,;t t
+s, at OBJEXT@,$OBJEXT,;t t
+s, at CXX@,$CXX,;t t
+s, at CXXFLAGS@,$CXXFLAGS,;t t
+s, at ac_ct_CXX@,$ac_ct_CXX,;t t
+s, at LN_S@,$LN_S,;t t
+s, at USE_ICONV@,$USE_ICONV,;t t
+s, at ICONV_LDFLAGS@,$ICONV_LDFLAGS,;t t
+s, at CPP@,$CPP,;t t
+s, at EGREP@,$EGREP,;t t
+s, at build@,$build,;t t
+s, at build_cpu@,$build_cpu,;t t
+s, at build_vendor@,$build_vendor,;t t
+s, at build_os@,$build_os,;t t
+s, at host@,$host,;t t
+s, at host_cpu@,$host_cpu,;t t
+s, at host_vendor@,$host_vendor,;t t
+s, at host_os@,$host_os,;t t
+s, at PGCONFIG@,$PGCONFIG,;t t
+s, at PGFEINCLUDES@,$PGFEINCLUDES,;t t
+s, at PGBEINCLUDES@,$PGBEINCLUDES,;t t
+s, at PGFELIBS@,$PGFELIBS,;t t
+s, at PGBELIBS@,$PGBELIBS,;t t
+s, at PGBIN@,$PGBIN,;t t
+s, at PGTEMPLATE@,$PGTEMPLATE,;t t
+s, at LPATH@,$LPATH,;t t
+s, at PWDREGRESS@,$PWDREGRESS,;t t
+s, at USE_GEOS@,$USE_GEOS,;t t
+s, at GEOS_DIR@,$GEOS_DIR,;t t
+s, at GEOS_LDFLAGS@,$GEOS_LDFLAGS,;t t
+s, at USE_GEOS_CAPI@,$USE_GEOS_CAPI,;t t
+s, at GEOSCONFIG@,$GEOSCONFIG,;t t
+s, at USE_PROJ@,$USE_PROJ,;t t
+s, at PROJ_DIR@,$PROJ_DIR,;t t
+s, at PROJ_LIBDIR@,$PROJ_LIBDIR,;t t
+s, at PROJ@,$PROJ,;t t
+s, at USE_JTS@,$USE_JTS,;t t
+s, at JTS_INCLUDES@,$JTS_INCLUDES,;t t
+s, at JTS_LIBDIR@,$JTS_LIBDIR,;t t
+s, at JTSCONFIG@,$JTSCONFIG,;t t
+s, at FLEX@,$FLEX,;t t
+s, at DLLWRAP@,$DLLWRAP,;t t
+s, at DLLTOOL@,$DLLTOOL,;t t
+s, at YACC@,$YACC,;t t
+s, at INSTALL@,$INSTALL,;t t
+s, at PERL@,$PERL,;t t
+s, at docdir@,$docdir,;t t
+s, at XSLBASE@,$XSLBASE,;t t
+s, at XSLTPROC@,$XSLTPROC,;t t
+s, at PDFXMLTEX@,$PDFXMLTEX,;t t
+s, at DB2PDF@,$DB2PDF,;t t
+s, at JW@,$JW,;t t
+s, at DOC_RULE@,$DOC_RULE,;t t
+s, at PORTNAME@,$PORTNAME,;t t
+s, at DLSUFFIX@,$DLSUFFIX,;t t
+s, at DLFLAGS@,$DLFLAGS,;t t
+s, at EXE@,$EXE,;t t
+s, at HOST_OS@,$HOST_OS,;t t
+s, at ELF_SYS@,$ELF_SYS,;t t
+s, at LIB@&t at OBJS@,$LIB@&t at OBJS,;t t
+s, at LTLIBOBJS@,$LTLIBOBJS,;t t
+CEOF
+
+_ACEOF
+
+ cat >>$CONFIG_STATUS <<\_ACEOF
+ # Split the substitutions into bite-sized pieces for seds with
+ # small command number limits, like on Digital OSF/1 and HP-UX.
+ ac_max_sed_lines=48
+ ac_sed_frag=1 # Number of current file.
+ ac_beg=1 # First line for current file.
+ ac_end=$ac_max_sed_lines # Line after last line for current file.
+ ac_more_lines=:
+ ac_sed_cmds=
+ while $ac_more_lines; do
+ if test $ac_beg -gt 1; then
+ sed "1,${ac_beg}d; ${ac_end}q" $tmp/subs.sed >$tmp/subs.frag
+ else
+ sed "${ac_end}q" $tmp/subs.sed >$tmp/subs.frag
+ fi
+ if test ! -s $tmp/subs.frag; then
+ ac_more_lines=false
+ else
+ # The purpose of the label and of the branching condition is to
+ # speed up the sed processing (if there are no `@' at all, there
+ # is no need to browse any of the substitutions).
+ # These are the two extra sed commands mentioned above.
+ (echo ':t
+ /@[a-zA-Z_][a-zA-Z_0-9]*@/!b' && cat $tmp/subs.frag) >$tmp/subs-$ac_sed_frag.sed
+ if test -z "$ac_sed_cmds"; then
+ ac_sed_cmds="sed -f $tmp/subs-$ac_sed_frag.sed"
+ else
+ ac_sed_cmds="$ac_sed_cmds | sed -f $tmp/subs-$ac_sed_frag.sed"
+ fi
+ ac_sed_frag=`expr $ac_sed_frag + 1`
+ ac_beg=$ac_end
+ ac_end=`expr $ac_end + $ac_max_sed_lines`
+ fi
+ done
+ if test -z "$ac_sed_cmds"; then
+ ac_sed_cmds=cat
+ fi
+fi # test -n "$CONFIG_FILES"
+
+_ACEOF
+cat >>$CONFIG_STATUS <<\_ACEOF
+for ac_file in : $CONFIG_FILES; do test "x$ac_file" = x: && continue
+ # Support "outfile[:infile[:infile...]]", defaulting infile="outfile.in".
+ case $ac_file in
+ - | *:- | *:-:* ) # input from stdin
+ cat >$tmp/stdin
+ ac_file_in=`echo "$ac_file" | sed 's,[^:]*:,,'`
+ ac_file=`echo "$ac_file" | sed 's,:.*,,'` ;;
+ *:* ) ac_file_in=`echo "$ac_file" | sed 's,[^:]*:,,'`
+ ac_file=`echo "$ac_file" | sed 's,:.*,,'` ;;
+ * ) ac_file_in=$ac_file.in ;;
+ esac
+
+ # Compute @srcdir@, @top_srcdir@, and @INSTALL@ for subdirectories.
+ ac_dir=`(dirname "$ac_file") 2>/dev/null ||
+$as_expr X"$ac_file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
+ X"$ac_file" : 'X\(//\)[^/]' \| \
+ X"$ac_file" : 'X\(//\)$' \| \
+ X"$ac_file" : 'X\(/\)' \| \
+ . : '\(.\)' 2>/dev/null ||
+echo X"$ac_file" |
+ sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ s//\1/; q; }
+ /^X\(\/\/\)[^/].*/{ s//\1/; q; }
+ /^X\(\/\/\)$/{ s//\1/; q; }
+ /^X\(\/\).*/{ s//\1/; q; }
+ s/.*/./; q'`
+ { if $as_mkdir_p; then
+ mkdir -p "$ac_dir"
+ else
+ as_dir="$ac_dir"
+ as_dirs=
+ while test ! -d "$as_dir"; do
+ as_dirs="$as_dir $as_dirs"
+ as_dir=`(dirname "$as_dir") 2>/dev/null ||
+$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
+ X"$as_dir" : 'X\(//\)[^/]' \| \
+ X"$as_dir" : 'X\(//\)$' \| \
+ X"$as_dir" : 'X\(/\)' \| \
+ . : '\(.\)' 2>/dev/null ||
+echo X"$as_dir" |
+ sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ s//\1/; q; }
+ /^X\(\/\/\)[^/].*/{ s//\1/; q; }
+ /^X\(\/\/\)$/{ s//\1/; q; }
+ /^X\(\/\).*/{ s//\1/; q; }
+ s/.*/./; q'`
+ done
+ test ! -n "$as_dirs" || mkdir $as_dirs
+ fi || { { echo "$as_me:$LINENO: error: cannot create directory \"$ac_dir\"" >&5
+echo "$as_me: error: cannot create directory \"$ac_dir\"" >&2;}
+ { (exit 1); exit 1; }; }; }
+
+ ac_builddir=.
+
+if test "$ac_dir" != .; then
+ ac_dir_suffix=/`echo "$ac_dir" | sed 's,^\.[\\/],,'`
+ # A "../" for each directory in $ac_dir_suffix.
+ ac_top_builddir=`echo "$ac_dir_suffix" | sed 's,/[^\\/]*,../,g'`
+else
+ ac_dir_suffix= ac_top_builddir=
+fi
+
+case $srcdir in
+ .) # No --srcdir option. We are building in place.
+ ac_srcdir=.
+ if test -z "$ac_top_builddir"; then
+ ac_top_srcdir=.
+ else
+ ac_top_srcdir=`echo $ac_top_builddir | sed 's,/$,,'`
+ fi ;;
+ [\\/]* | ?:[\\/]* ) # Absolute path.
+ ac_srcdir=$srcdir$ac_dir_suffix;
+ ac_top_srcdir=$srcdir ;;
+ *) # Relative path.
+ ac_srcdir=$ac_top_builddir$srcdir$ac_dir_suffix
+ ac_top_srcdir=$ac_top_builddir$srcdir ;;
+esac
+
+# Do not use `cd foo && pwd` to compute absolute paths, because
+# the directories may not exist.
+case `pwd` in
+.) ac_abs_builddir="$ac_dir";;
+*)
+ case "$ac_dir" in
+ .) ac_abs_builddir=`pwd`;;
+ [\\/]* | ?:[\\/]* ) ac_abs_builddir="$ac_dir";;
+ *) ac_abs_builddir=`pwd`/"$ac_dir";;
+ esac;;
+esac
+case $ac_abs_builddir in
+.) ac_abs_top_builddir=${ac_top_builddir}.;;
+*)
+ case ${ac_top_builddir}. in
+ .) ac_abs_top_builddir=$ac_abs_builddir;;
+ [\\/]* | ?:[\\/]* ) ac_abs_top_builddir=${ac_top_builddir}.;;
+ *) ac_abs_top_builddir=$ac_abs_builddir/${ac_top_builddir}.;;
+ esac;;
+esac
+case $ac_abs_builddir in
+.) ac_abs_srcdir=$ac_srcdir;;
+*)
+ case $ac_srcdir in
+ .) ac_abs_srcdir=$ac_abs_builddir;;
+ [\\/]* | ?:[\\/]* ) ac_abs_srcdir=$ac_srcdir;;
+ *) ac_abs_srcdir=$ac_abs_builddir/$ac_srcdir;;
+ esac;;
+esac
+case $ac_abs_builddir in
+.) ac_abs_top_srcdir=$ac_top_srcdir;;
+*)
+ case $ac_top_srcdir in
+ .) ac_abs_top_srcdir=$ac_abs_builddir;;
+ [\\/]* | ?:[\\/]* ) ac_abs_top_srcdir=$ac_top_srcdir;;
+ *) ac_abs_top_srcdir=$ac_abs_builddir/$ac_top_srcdir;;
+ esac;;
+esac
+
+
+
+ if test x"$ac_file" != x-; then
+ { echo "$as_me:$LINENO: creating $ac_file" >&5
+echo "$as_me: creating $ac_file" >&6;}
+ rm -f "$ac_file"
+ fi
+ # Let's still pretend it is `configure' which instantiates (i.e., don't
+ # use $as_me), people would be surprised to read:
+ # /* config.h. Generated by config.status. */
+ if test x"$ac_file" = x-; then
+ configure_input=
+ else
+ configure_input="$ac_file. "
+ fi
+ configure_input=$configure_input"Generated from `echo $ac_file_in |
+ sed 's,.*/,,'` by configure."
+
+ # First look for the input files in the build tree, otherwise in the
+ # src tree.
+ ac_file_inputs=`IFS=:
+ for f in $ac_file_in; do
+ case $f in
+ -) echo $tmp/stdin ;;
+ [\\/$]*)
+ # Absolute (can't be DOS-style, as IFS=:)
+ test -f "$f" || { { echo "$as_me:$LINENO: error: cannot find input file: $f" >&5
+echo "$as_me: error: cannot find input file: $f" >&2;}
+ { (exit 1); exit 1; }; }
+ echo "$f";;
+ *) # Relative
+ if test -f "$f"; then
+ # Build tree
+ echo "$f"
+ elif test -f "$srcdir/$f"; then
+ # Source tree
+ echo "$srcdir/$f"
+ else
+ # /dev/null tree
+ { { echo "$as_me:$LINENO: error: cannot find input file: $f" >&5
+echo "$as_me: error: cannot find input file: $f" >&2;}
+ { (exit 1); exit 1; }; }
+ fi;;
+ esac
+ done` || { (exit 1); exit 1; }
+_ACEOF
+cat >>$CONFIG_STATUS <<_ACEOF
+ sed "$ac_vpsub
+$extrasub
+_ACEOF
+cat >>$CONFIG_STATUS <<\_ACEOF
+:t
+/@[a-zA-Z_][a-zA-Z_0-9]*@/!b
+s, at configure_input@,$configure_input,;t t
+s, at srcdir@,$ac_srcdir,;t t
+s, at abs_srcdir@,$ac_abs_srcdir,;t t
+s, at top_srcdir@,$ac_top_srcdir,;t t
+s, at abs_top_srcdir@,$ac_abs_top_srcdir,;t t
+s, at builddir@,$ac_builddir,;t t
+s, at abs_builddir@,$ac_abs_builddir,;t t
+s, at top_builddir@,$ac_top_builddir,;t t
+s, at abs_top_builddir@,$ac_abs_top_builddir,;t t
+" $ac_file_inputs | (eval "$ac_sed_cmds") >$tmp/out
+ rm -f $tmp/stdin
+ if test x"$ac_file" != x-; then
+ mv $tmp/out $ac_file
+ else
+ cat $tmp/out
+ rm -f $tmp/out
+ fi
+
+done
+_ACEOF
+cat >>$CONFIG_STATUS <<\_ACEOF
+
+#
+# CONFIG_HEADER section.
+#
+
+# These sed commands are passed to sed as "A NAME B NAME C VALUE D", where
+# NAME is the cpp macro being defined and VALUE is the value it is being given.
+#
+# ac_d sets the value in "#define NAME VALUE" lines.
+ac_dA='s,^\([ ]*\)#\([ ]*define[ ][ ]*\)'
+ac_dB='[ ].*$,\1#\2'
+ac_dC=' '
+ac_dD=',;t'
+# ac_u turns "#undef NAME" without trailing blanks into "#define NAME VALUE".
+ac_uA='s,^\([ ]*\)#\([ ]*\)undef\([ ][ ]*\)'
+ac_uB='$,\1#\2define\3'
+ac_uC=' '
+ac_uD=',;t'
+
+for ac_file in : $CONFIG_HEADERS; do test "x$ac_file" = x: && continue
+ # Support "outfile[:infile[:infile...]]", defaulting infile="outfile.in".
+ case $ac_file in
+ - | *:- | *:-:* ) # input from stdin
+ cat >$tmp/stdin
+ ac_file_in=`echo "$ac_file" | sed 's,[^:]*:,,'`
+ ac_file=`echo "$ac_file" | sed 's,:.*,,'` ;;
+ *:* ) ac_file_in=`echo "$ac_file" | sed 's,[^:]*:,,'`
+ ac_file=`echo "$ac_file" | sed 's,:.*,,'` ;;
+ * ) ac_file_in=$ac_file.in ;;
+ esac
+
+ test x"$ac_file" != x- && { echo "$as_me:$LINENO: creating $ac_file" >&5
+echo "$as_me: creating $ac_file" >&6;}
+
+ # First look for the input files in the build tree, otherwise in the
+ # src tree.
+ ac_file_inputs=`IFS=:
+ for f in $ac_file_in; do
+ case $f in
+ -) echo $tmp/stdin ;;
+ [\\/$]*)
+ # Absolute (can't be DOS-style, as IFS=:)
+ test -f "$f" || { { echo "$as_me:$LINENO: error: cannot find input file: $f" >&5
+echo "$as_me: error: cannot find input file: $f" >&2;}
+ { (exit 1); exit 1; }; }
+ # Do quote $f, to prevent DOS paths from being IFS'd.
+ echo "$f";;
+ *) # Relative
+ if test -f "$f"; then
+ # Build tree
+ echo "$f"
+ elif test -f "$srcdir/$f"; then
+ # Source tree
+ echo "$srcdir/$f"
+ else
+ # /dev/null tree
+ { { echo "$as_me:$LINENO: error: cannot find input file: $f" >&5
+echo "$as_me: error: cannot find input file: $f" >&2;}
+ { (exit 1); exit 1; }; }
+ fi;;
+ esac
+ done` || { (exit 1); exit 1; }
+ # Remove the trailing spaces.
+ sed 's/[ ]*$//' $ac_file_inputs >$tmp/in
+
+_ACEOF
+
+# Transform confdefs.h into two sed scripts, `conftest.defines' and
+# `conftest.undefs', that substitutes the proper values into
+# config.h.in to produce config.h. The first handles `#define'
+# templates, and the second `#undef' templates.
+# And first: Protect against being on the right side of a sed subst in
+# config.status. Protect against being in an unquoted here document
+# in config.status.
+rm -f conftest.defines conftest.undefs
+# Using a here document instead of a string reduces the quoting nightmare.
+# Putting comments in sed scripts is not portable.
+#
+# `end' is used to avoid that the second main sed command (meant for
+# 0-ary CPP macros) applies to n-ary macro definitions.
+# See the Autoconf documentation for `clear'.
+cat >confdef2sed.sed <<\_ACEOF
+s/[\\&,]/\\&/g
+s,[\\$`],\\&,g
+t clear
+: clear
+s,^[ ]*#[ ]*define[ ][ ]*\([^ (][^ (]*\)\(([^)]*)\)[ ]*\(.*\)$,${ac_dA}\1${ac_dB}\1\2${ac_dC}\3${ac_dD},gp
+t end
+s,^[ ]*#[ ]*define[ ][ ]*\([^ ][^ ]*\)[ ]*\(.*\)$,${ac_dA}\1${ac_dB}\1${ac_dC}\2${ac_dD},gp
+: end
+_ACEOF
+# If some macros were called several times there might be several times
+# the same #defines, which is useless. Nevertheless, we may not want to
+# sort them, since we want the *last* AC-DEFINE to be honored.
+uniq confdefs.h | sed -n -f confdef2sed.sed >conftest.defines
+sed 's/ac_d/ac_u/g' conftest.defines >conftest.undefs
+rm -f confdef2sed.sed
+
+# This sed command replaces #undef with comments. This is necessary, for
+# example, in the case of _POSIX_SOURCE, which is predefined and required
+# on some systems where configure will not decide to define it.
+cat >>conftest.undefs <<\_ACEOF
+s,^[ ]*#[ ]*undef[ ][ ]*[a-zA-Z_][a-zA-Z_0-9]*,/* & */,
+_ACEOF
+
+# Break up conftest.defines because some shells have a limit on the size
+# of here documents, and old seds have small limits too (100 cmds).
+echo ' # Handle all the #define templates only if necessary.' >>$CONFIG_STATUS
+echo ' if grep "^[ ]*#[ ]*define" $tmp/in >/dev/null; then' >>$CONFIG_STATUS
+echo ' # If there are no defines, we may have an empty if/fi' >>$CONFIG_STATUS
+echo ' :' >>$CONFIG_STATUS
+rm -f conftest.tail
+while grep . conftest.defines >/dev/null
+do
+ # Write a limited-size here document to $tmp/defines.sed.
+ echo ' cat >$tmp/defines.sed <<CEOF' >>$CONFIG_STATUS
+ # Speed up: don't consider the non `#define' lines.
+ echo '/^[ ]*#[ ]*define/!b' >>$CONFIG_STATUS
+ # Work around the forget-to-reset-the-flag bug.
+ echo 't clr' >>$CONFIG_STATUS
+ echo ': clr' >>$CONFIG_STATUS
+ sed ${ac_max_here_lines}q conftest.defines >>$CONFIG_STATUS
+ echo 'CEOF
+ sed -f $tmp/defines.sed $tmp/in >$tmp/out
+ rm -f $tmp/in
+ mv $tmp/out $tmp/in
+' >>$CONFIG_STATUS
+ sed 1,${ac_max_here_lines}d conftest.defines >conftest.tail
+ rm -f conftest.defines
+ mv conftest.tail conftest.defines
+done
+rm -f conftest.defines
+echo ' fi # grep' >>$CONFIG_STATUS
+echo >>$CONFIG_STATUS
+
+# Break up conftest.undefs because some shells have a limit on the size
+# of here documents, and old seds have small limits too (100 cmds).
+echo ' # Handle all the #undef templates' >>$CONFIG_STATUS
+rm -f conftest.tail
+while grep . conftest.undefs >/dev/null
+do
+ # Write a limited-size here document to $tmp/undefs.sed.
+ echo ' cat >$tmp/undefs.sed <<CEOF' >>$CONFIG_STATUS
+ # Speed up: don't consider the non `#undef'
+ echo '/^[ ]*#[ ]*undef/!b' >>$CONFIG_STATUS
+ # Work around the forget-to-reset-the-flag bug.
+ echo 't clr' >>$CONFIG_STATUS
+ echo ': clr' >>$CONFIG_STATUS
+ sed ${ac_max_here_lines}q conftest.undefs >>$CONFIG_STATUS
+ echo 'CEOF
+ sed -f $tmp/undefs.sed $tmp/in >$tmp/out
+ rm -f $tmp/in
+ mv $tmp/out $tmp/in
+' >>$CONFIG_STATUS
+ sed 1,${ac_max_here_lines}d conftest.undefs >conftest.tail
+ rm -f conftest.undefs
+ mv conftest.tail conftest.undefs
+done
+rm -f conftest.undefs
+
+cat >>$CONFIG_STATUS <<\_ACEOF
+ # Let's still pretend it is `configure' which instantiates (i.e., don't
+ # use $as_me), people would be surprised to read:
+ # /* config.h. Generated by config.status. */
+ if test x"$ac_file" = x-; then
+ echo "/* Generated by configure. */" >$tmp/config.h
+ else
+ echo "/* $ac_file. Generated by configure. */" >$tmp/config.h
+ fi
+ cat $tmp/in >>$tmp/config.h
+ rm -f $tmp/in
+ if test x"$ac_file" != x-; then
+ if diff $ac_file $tmp/config.h >/dev/null 2>&1; then
+ { echo "$as_me:$LINENO: $ac_file is unchanged" >&5
+echo "$as_me: $ac_file is unchanged" >&6;}
+ else
+ ac_dir=`(dirname "$ac_file") 2>/dev/null ||
+$as_expr X"$ac_file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
+ X"$ac_file" : 'X\(//\)[^/]' \| \
+ X"$ac_file" : 'X\(//\)$' \| \
+ X"$ac_file" : 'X\(/\)' \| \
+ . : '\(.\)' 2>/dev/null ||
+echo X"$ac_file" |
+ sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ s//\1/; q; }
+ /^X\(\/\/\)[^/].*/{ s//\1/; q; }
+ /^X\(\/\/\)$/{ s//\1/; q; }
+ /^X\(\/\).*/{ s//\1/; q; }
+ s/.*/./; q'`
+ { if $as_mkdir_p; then
+ mkdir -p "$ac_dir"
+ else
+ as_dir="$ac_dir"
+ as_dirs=
+ while test ! -d "$as_dir"; do
+ as_dirs="$as_dir $as_dirs"
+ as_dir=`(dirname "$as_dir") 2>/dev/null ||
+$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
+ X"$as_dir" : 'X\(//\)[^/]' \| \
+ X"$as_dir" : 'X\(//\)$' \| \
+ X"$as_dir" : 'X\(/\)' \| \
+ . : '\(.\)' 2>/dev/null ||
+echo X"$as_dir" |
+ sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ s//\1/; q; }
+ /^X\(\/\/\)[^/].*/{ s//\1/; q; }
+ /^X\(\/\/\)$/{ s//\1/; q; }
+ /^X\(\/\).*/{ s//\1/; q; }
+ s/.*/./; q'`
+ done
+ test ! -n "$as_dirs" || mkdir $as_dirs
+ fi || { { echo "$as_me:$LINENO: error: cannot create directory \"$ac_dir\"" >&5
+echo "$as_me: error: cannot create directory \"$ac_dir\"" >&2;}
+ { (exit 1); exit 1; }; }; }
+
+ rm -f $ac_file
+ mv $tmp/config.h $ac_file
+ fi
+ else
+ cat $tmp/config.h
+ rm -f $tmp/config.h
+ fi
+done
+_ACEOF
+
+cat >>$CONFIG_STATUS <<\_ACEOF
+
+{ (exit 0); exit 0; }
+_ACEOF
+chmod +x $CONFIG_STATUS
+ac_clean_files=$ac_clean_files_save
+
+
+# configure is writing to config.log, and then calls config.status.
+# config.status does its own redirection, appending to config.log.
+# Unfortunately, on DOS this fails, as config.log is still kept open
+# by configure, so config.status won't be able to write to it; its
+# output is simply discarded. So we exec the FD to /dev/null,
+# effectively closing config.log, so it can be properly (re)opened and
+# appended to by config.status. When coming back to configure, we
+# need to make the FD available again.
+if test "$no_create" != yes; then
+ ac_cs_success=:
+ ac_config_status_args=
+ test "$silent" = yes &&
+ ac_config_status_args="$ac_config_status_args --quiet"
+ exec 5>/dev/null
+ $SHELL $CONFIG_STATUS $ac_config_status_args || ac_cs_success=false
+ exec 5>>config.log
+ # Use ||, not &&, to avoid exiting from the if with $? = 1, which
+ # would make configure fail if this is the last instruction.
+ $ac_cs_success || { (exit 1); exit 1; }
+fi
+
+
+echo "$as_me:$LINENO: result: " >&5
+echo "${ECHO_T} " >&6
+echo "$as_me:$LINENO: result: SUMMARY" >&5
+echo "${ECHO_T} SUMMARY" >&6
+echo "$as_me:$LINENO: result: -------------------------------------------------------" >&5
+echo "${ECHO_T} -------------------------------------------------------" >&6
+echo "$as_me:$LINENO: result: " >&5
+echo "${ECHO_T} " >&6
+echo "$as_me:$LINENO: result: HOST_OS: $host_os" >&5
+echo "${ECHO_T} HOST_OS: $host_os" >&6
+echo "$as_me:$LINENO: result: " >&5
+echo "${ECHO_T} " >&6
+echo "$as_me:$LINENO: result: PGSQL: $PGCONFIG" >&5
+echo "${ECHO_T} PGSQL: $PGCONFIG" >&6
+
+if test $USE_JTS -gt 0; then
+ echo "$as_me:$LINENO: result: JTS: includedir=$JTS_INCLUDES libdir=$JTS_LIBDIR" >&5
+echo "${ECHO_T} JTS: includedir=$JTS_INCLUDES libdir=$JTS_LIBDIR" >&6
+fi
+if test $USE_GEOS -gt 0; then
+ if test $USE_GEOS_CAPI -gt 0; then
+ echo "$as_me:$LINENO: result: GEOS: $GEOSCONFIG (with C-API)" >&5
+echo "${ECHO_T} GEOS: $GEOSCONFIG (with C-API)" >&6
+ else
+ echo "$as_me:$LINENO: result: GEOS: $GEOSCONFIG" >&5
+echo "${ECHO_T} GEOS: $GEOSCONFIG" >&6
+ fi
+ echo "$as_me:$LINENO: result: (ldflags: $GEOS_LDFLAGS)" >&5
+echo "${ECHO_T} (ldflags: $GEOS_LDFLAGS)" >&6
+fi
+if test $USE_PROJ -gt 0; then
+ echo "$as_me:$LINENO: result: PROJ: prefix=$PROJ_DIR libdir=$PROJ_LIBDIR" >&5
+echo "${ECHO_T} PROJ: prefix=$PROJ_DIR libdir=$PROJ_LIBDIR" >&6
+fi
+echo "$as_me:$LINENO: result: ICONV: $USE_ICONV $ICONV_LDFLAGS" >&5
+echo "${ECHO_T} ICONV: $USE_ICONV $ICONV_LDFLAGS" >&6
+
+echo "$as_me:$LINENO: result: " >&5
+echo "${ECHO_T} " >&6
+echo "$as_me:$LINENO: result: PORTNAME: $PORTNAME" >&5
+echo "${ECHO_T} PORTNAME: $PORTNAME" >&6
+echo "$as_me:$LINENO: result: PREFIX: $prefix" >&5
+echo "${ECHO_T} PREFIX: $prefix" >&6
+echo "$as_me:$LINENO: result: EPREFIX: $exec_prefix" >&5
+echo "${ECHO_T} EPREFIX: $exec_prefix" >&6
+echo "$as_me:$LINENO: result: DOC: $docdir" >&5
+echo "${ECHO_T} DOC: $docdir" >&6
+echo "$as_me:$LINENO: result: DATA: $datadir" >&5
+echo "${ECHO_T} DATA: $datadir" >&6
+echo "$as_me:$LINENO: result: MAN: $mandir" >&5
+echo "${ECHO_T} MAN: $mandir" >&6
+echo "$as_me:$LINENO: result: BIN: $bindir" >&5
+echo "${ECHO_T} BIN: $bindir" >&6
+if test "$MODULE_INSTALLDIR" = "$LPATH"; then
+ echo "$as_me:$LINENO: result: EXT: $libdir" >&5
+echo "${ECHO_T} EXT: $libdir" >&6
+else
+ echo "$as_me:$LINENO: result: EXT: $libdir ($LPATH)" >&5
+echo "${ECHO_T} EXT: $libdir ($LPATH)" >&6
+fi
+
+echo "$as_me:$LINENO: result: -------------------------------------------------------" >&5
+echo "${ECHO_T} -------------------------------------------------------" >&6
+echo "$as_me:$LINENO: result: " >&5
+echo "${ECHO_T} " >&6
+
Added: packages/postgis/upstream/autom4te.cache/requests
===================================================================
--- packages/postgis/upstream/autom4te.cache/requests 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/autom4te.cache/requests 2006-10-31 20:52:30 UTC (rev 577)
@@ -0,0 +1,115 @@
+# This file was generated.
+# It contains the lists of macros which have been traced.
+# It can be safely removed.
+
+ at request = (
+ bless( [
+ '0',
+ 1,
+ [
+ '/usr/share/autoconf'
+ ],
+ [
+ '/usr/share/autoconf/autoconf/autoconf.m4f',
+ 'configure.in'
+ ],
+ {
+ 'm4_pattern_forbid' => 1,
+ 'AC_CONFIG_LIBOBJ_DIR' => 1,
+ 'AC_TYPE_OFF_T' => 1,
+ 'AC_C_VOLATILE' => 1,
+ 'AC_FUNC_CLOSEDIR_VOID' => 1,
+ 'AC_REPLACE_FNMATCH' => 1,
+ 'AC_PROG_LIBTOOL' => 1,
+ 'AC_FUNC_STAT' => 1,
+ 'AC_HEADER_TIME' => 1,
+ 'AC_FUNC_WAIT3' => 1,
+ 'AM_AUTOMAKE_VERSION' => 1,
+ 'AC_STRUCT_TM' => 1,
+ 'AC_FUNC_LSTAT' => 1,
+ 'AC_TYPE_MODE_T' => 1,
+ 'AC_FUNC_GETMNTENT' => 1,
+ 'AC_FUNC_STRTOD' => 1,
+ 'AC_CHECK_HEADERS' => 1,
+ 'AC_FUNC_STRNLEN' => 1,
+ 'm4_sinclude' => 1,
+ 'AC_PROG_CXX' => 1,
+ 'AC_PATH_X' => 1,
+ 'AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK' => 1,
+ 'AC_PROG_AWK' => 1,
+ '_m4_warn' => 1,
+ 'AC_HEADER_STDC' => 1,
+ 'AC_HEADER_MAJOR' => 1,
+ 'AC_FUNC_ERROR_AT_LINE' => 1,
+ 'AC_PROG_GCC_TRADITIONAL' => 1,
+ 'AC_LIBSOURCE' => 1,
+ 'AC_FUNC_MBRTOWC' => 1,
+ 'AC_STRUCT_ST_BLOCKS' => 1,
+ 'AC_TYPE_SIGNAL' => 1,
+ 'AC_TYPE_UID_T' => 1,
+ 'AC_CONFIG_AUX_DIR' => 1,
+ 'AC_PROG_MAKE_SET' => 1,
+ 'sinclude' => 1,
+ 'm4_pattern_allow' => 1,
+ 'AC_DEFINE_TRACE_LITERAL' => 1,
+ 'AC_FUNC_STRERROR_R' => 1,
+ 'AC_PROG_CC' => 1,
+ 'AC_FUNC_FORK' => 1,
+ 'AC_DECL_SYS_SIGLIST' => 1,
+ 'AC_FUNC_VPRINTF' => 1,
+ 'AC_FUNC_STRCOLL' => 1,
+ 'AC_PROG_YACC' => 1,
+ 'AC_INIT' => 1,
+ 'AC_STRUCT_TIMEZONE' => 1,
+ 'AC_FUNC_CHOWN' => 1,
+ 'AC_SUBST' => 1,
+ 'AC_FUNC_ALLOCA' => 1,
+ 'AC_CANONICAL_HOST' => 1,
+ 'AC_FUNC_GETPGRP' => 1,
+ 'AC_PROG_RANLIB' => 1,
+ 'AM_INIT_AUTOMAKE' => 1,
+ 'AC_FUNC_SETPGRP' => 1,
+ 'AC_CONFIG_SUBDIRS' => 1,
+ 'AC_FUNC_MMAP' => 1,
+ 'AC_FUNC_REALLOC' => 1,
+ 'AC_TYPE_SIZE_T' => 1,
+ 'AC_CONFIG_LINKS' => 1,
+ 'AC_CHECK_TYPES' => 1,
+ 'AC_CHECK_MEMBERS' => 1,
+ 'AM_MAINTAINER_MODE' => 1,
+ 'AC_FUNC_UTIME_NULL' => 1,
+ 'AC_FUNC_SELECT_ARGTYPES' => 1,
+ 'AC_FUNC_STRFTIME' => 1,
+ 'AC_HEADER_STAT' => 1,
+ 'AC_C_INLINE' => 1,
+ 'AC_PROG_CPP' => 1,
+ 'AC_TYPE_PID_T' => 1,
+ 'AC_C_CONST' => 1,
+ 'AC_PROG_LEX' => 1,
+ 'AC_CONFIG_FILES' => 1,
+ 'include' => 1,
+ 'AC_FUNC_SETVBUF_REVERSED' => 1,
+ 'AC_PROG_INSTALL' => 1,
+ 'AM_GNU_GETTEXT' => 1,
+ 'AC_FUNC_OBSTACK' => 1,
+ 'AC_CHECK_LIB' => 1,
+ 'AC_FUNC_MALLOC' => 1,
+ 'AC_FUNC_GETGROUPS' => 1,
+ 'AC_FUNC_GETLOADAVG' => 1,
+ 'AH_OUTPUT' => 1,
+ 'AC_FUNC_FSEEKO' => 1,
+ 'AM_PROG_CC_C_O' => 1,
+ 'AM_CONDITIONAL' => 1,
+ 'AC_CANONICAL_SYSTEM' => 1,
+ 'AC_FUNC_MKTIME' => 1,
+ 'AC_CONFIG_HEADERS' => 1,
+ 'AC_HEADER_SYS_WAIT' => 1,
+ 'AC_FUNC_MEMCMP' => 1,
+ 'AC_PROG_LN_S' => 1,
+ 'm4_include' => 1,
+ 'AC_HEADER_DIRENT' => 1,
+ 'AC_CHECK_FUNCS' => 1
+ }
+ ], 'Autom4te::Request' )
+ );
+
Added: packages/postgis/upstream/autom4te.cache/traces.0
===================================================================
--- packages/postgis/upstream/autom4te.cache/traces.0 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/autom4te.cache/traces.0 2006-10-31 20:52:30 UTC (rev 577)
@@ -0,0 +1,402 @@
+m4trace:configure.in:1: -1- AC_INIT([README.postgis])
+m4trace:configure.in:1: -1- m4_pattern_forbid([^_?A[CHUM]_])
+m4trace:configure.in:1: -1- m4_pattern_forbid([_AC_])
+m4trace:configure.in:1: -1- m4_pattern_forbid([^LIBOBJS$], [do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs LIBOBJS'])
+m4trace:configure.in:1: -1- m4_pattern_allow([^AS_FLAGS$])
+m4trace:configure.in:1: -1- m4_pattern_forbid([^_?m4_])
+m4trace:configure.in:1: -1- m4_pattern_forbid([^dnl$])
+m4trace:configure.in:1: -1- m4_pattern_forbid([^_?AS_])
+m4trace:configure.in:1: -1- AC_SUBST([SHELL], [${CONFIG_SHELL-/bin/sh}])
+m4trace:configure.in:1: -1- AC_SUBST([PATH_SEPARATOR])
+m4trace:configure.in:1: -1- AC_SUBST([PACKAGE_NAME], [m4_ifdef([AC_PACKAGE_NAME], ['AC_PACKAGE_NAME'])])
+m4trace:configure.in:1: -1- AC_SUBST([PACKAGE_TARNAME], [m4_ifdef([AC_PACKAGE_TARNAME], ['AC_PACKAGE_TARNAME'])])
+m4trace:configure.in:1: -1- AC_SUBST([PACKAGE_VERSION], [m4_ifdef([AC_PACKAGE_VERSION], ['AC_PACKAGE_VERSION'])])
+m4trace:configure.in:1: -1- AC_SUBST([PACKAGE_STRING], [m4_ifdef([AC_PACKAGE_STRING], ['AC_PACKAGE_STRING'])])
+m4trace:configure.in:1: -1- AC_SUBST([PACKAGE_BUGREPORT], [m4_ifdef([AC_PACKAGE_BUGREPORT], ['AC_PACKAGE_BUGREPORT'])])
+m4trace:configure.in:1: -1- AC_SUBST([exec_prefix], [NONE])
+m4trace:configure.in:1: -1- AC_SUBST([prefix], [NONE])
+m4trace:configure.in:1: -1- AC_SUBST([program_transform_name], [s,x,x,])
+m4trace:configure.in:1: -1- AC_SUBST([bindir], ['${exec_prefix}/bin'])
+m4trace:configure.in:1: -1- AC_SUBST([sbindir], ['${exec_prefix}/sbin'])
+m4trace:configure.in:1: -1- AC_SUBST([libexecdir], ['${exec_prefix}/libexec'])
+m4trace:configure.in:1: -1- AC_SUBST([datadir], ['${prefix}/share'])
+m4trace:configure.in:1: -1- AC_SUBST([sysconfdir], ['${prefix}/etc'])
+m4trace:configure.in:1: -1- AC_SUBST([sharedstatedir], ['${prefix}/com'])
+m4trace:configure.in:1: -1- AC_SUBST([localstatedir], ['${prefix}/var'])
+m4trace:configure.in:1: -1- AC_SUBST([libdir], ['${exec_prefix}/lib'])
+m4trace:configure.in:1: -1- AC_SUBST([includedir], ['${prefix}/include'])
+m4trace:configure.in:1: -1- AC_SUBST([oldincludedir], ['/usr/include'])
+m4trace:configure.in:1: -1- AC_SUBST([infodir], ['${prefix}/info'])
+m4trace:configure.in:1: -1- AC_SUBST([mandir], ['${prefix}/man'])
+m4trace:configure.in:1: -1- AC_DEFINE_TRACE_LITERAL([PACKAGE_NAME])
+m4trace:configure.in:1: -1- AH_OUTPUT([PACKAGE_NAME], [/* Define to the full name of this package. */
+#undef PACKAGE_NAME])
+m4trace:configure.in:1: -1- AC_DEFINE_TRACE_LITERAL([PACKAGE_TARNAME])
+m4trace:configure.in:1: -1- AH_OUTPUT([PACKAGE_TARNAME], [/* Define to the one symbol short name of this package. */
+#undef PACKAGE_TARNAME])
+m4trace:configure.in:1: -1- AC_DEFINE_TRACE_LITERAL([PACKAGE_VERSION])
+m4trace:configure.in:1: -1- AH_OUTPUT([PACKAGE_VERSION], [/* Define to the version of this package. */
+#undef PACKAGE_VERSION])
+m4trace:configure.in:1: -1- AC_DEFINE_TRACE_LITERAL([PACKAGE_STRING])
+m4trace:configure.in:1: -1- AH_OUTPUT([PACKAGE_STRING], [/* Define to the full name and version of this package. */
+#undef PACKAGE_STRING])
+m4trace:configure.in:1: -1- AC_DEFINE_TRACE_LITERAL([PACKAGE_BUGREPORT])
+m4trace:configure.in:1: -1- AH_OUTPUT([PACKAGE_BUGREPORT], [/* Define to the address where bug reports for this package should be sent. */
+#undef PACKAGE_BUGREPORT])
+m4trace:configure.in:1: -1- AC_SUBST([build_alias])
+m4trace:configure.in:1: -1- AC_SUBST([host_alias])
+m4trace:configure.in:1: -1- AC_SUBST([target_alias])
+m4trace:configure.in:1: -1- AC_SUBST([DEFS])
+m4trace:configure.in:1: -1- AC_SUBST([ECHO_C])
+m4trace:configure.in:1: -1- AC_SUBST([ECHO_N])
+m4trace:configure.in:1: -1- AC_SUBST([ECHO_T])
+m4trace:configure.in:1: -1- AC_SUBST([LIBS])
+m4trace:configure.in:2: -1- AC_CONFIG_HEADERS([config.h])
+m4trace:configure.in:16: -1- AC_PROG_CC
+m4trace:configure.in:16: -1- AC_SUBST([CC])
+m4trace:configure.in:16: -1- AC_SUBST([CFLAGS])
+m4trace:configure.in:16: -1- AC_SUBST([LDFLAGS])
+m4trace:configure.in:16: -1- AC_SUBST([CPPFLAGS])
+m4trace:configure.in:16: -1- AC_SUBST([CC])
+m4trace:configure.in:16: -1- AC_SUBST([ac_ct_CC])
+m4trace:configure.in:16: -1- AC_SUBST([CC])
+m4trace:configure.in:16: -1- AC_SUBST([ac_ct_CC])
+m4trace:configure.in:16: -1- AC_SUBST([CC])
+m4trace:configure.in:16: -1- AC_SUBST([CC])
+m4trace:configure.in:16: -1- AC_SUBST([ac_ct_CC])
+m4trace:configure.in:16: -1- AC_SUBST([EXEEXT], [$ac_cv_exeext])
+m4trace:configure.in:16: -1- AC_SUBST([OBJEXT], [$ac_cv_objext])
+m4trace:configure.in:17: -1- AC_PROG_CXX
+m4trace:configure.in:17: -1- AC_SUBST([CXX])
+m4trace:configure.in:17: -1- AC_SUBST([CXXFLAGS])
+m4trace:configure.in:17: -1- AC_SUBST([LDFLAGS])
+m4trace:configure.in:17: -1- AC_SUBST([CPPFLAGS])
+m4trace:configure.in:17: -1- AC_SUBST([CXX])
+m4trace:configure.in:17: -1- AC_SUBST([ac_ct_CXX])
+m4trace:configure.in:18: -1- AC_PROG_LN_S
+m4trace:configure.in:18: -1- AC_SUBST([LN_S], [$as_ln_s])
+m4trace:configure.in:24: -1- AC_SUBST([USE_ICONV])
+m4trace:configure.in:25: -1- AC_SUBST([ICONV_LDFLAGS])
+m4trace:configure.in:48: -3- AC_CHECK_LIB([c], [iconv_open], [USE_ICONV=1
+ ], [USE_ICONV=0
+ ])
+m4trace:configure.in:49: -2- AC_CHECK_LIB([iconv], [libiconv_open], [USE_ICONV=1
+ ICONV_LDFLAGS=-liconv
+ ], [echo "$as_me:$LINENO: checking for iconv_open in -lc" >&5
+echo $ECHO_N "checking for iconv_open in -lc... $ECHO_C" >&6
+if test "${ac_cv_lib_c_iconv_open+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ ac_check_lib_save_LIBS=$LIBS
+LIBS="-lc $LIBS"
+
+cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+
+/* Override any gcc2 internal prototype to avoid an error. */
+#ifdef __cplusplus
+extern "C"
+#endif
+/* We use char because int might match the return type of a gcc2
+ builtin and then its argument prototype would still apply. */
+char iconv_open ();
+int
+main ()
+{
+iconv_open ();
+ ;
+ return 0;
+}
+_ACEOF
+rm -f conftest.$ac_objext conftest$ac_exeext
+if { (eval echo "$as_me:$LINENO: \"$ac_link\"") >&5
+ (eval $ac_link) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_c_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest$ac_exeext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ ac_cv_lib_c_iconv_open=yes
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ac_cv_lib_c_iconv_open=no
+fi
+rm -f conftest.err conftest.$ac_objext \
+ conftest$ac_exeext conftest.$ac_ext
+LIBS=$ac_check_lib_save_LIBS
+fi
+echo "$as_me:$LINENO: result: $ac_cv_lib_c_iconv_open" >&5
+echo "${ECHO_T}$ac_cv_lib_c_iconv_open" >&6
+if test $ac_cv_lib_c_iconv_open = yes; then
+ USE_ICONV=1
+
+else
+ USE_ICONV=0
+
+fi
+
+ ])
+m4trace:configure.in:50: -1- AC_CHECK_LIB([iconv], [iconv_open], [USE_ICONV=1
+ ICONV_LDFLAGS=-liconv
+ ], [echo "$as_me:$LINENO: checking for libiconv_open in -liconv" >&5
+echo $ECHO_N "checking for libiconv_open in -liconv... $ECHO_C" >&6
+if test "${ac_cv_lib_iconv_libiconv_open+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ ac_check_lib_save_LIBS=$LIBS
+LIBS="-liconv $LIBS"
+cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+
+/* Override any gcc2 internal prototype to avoid an error. */
+#ifdef __cplusplus
+extern "C"
+#endif
+/* We use char because int might match the return type of a gcc2
+ builtin and then its argument prototype would still apply. */
+char libiconv_open ();
+int
+main ()
+{
+libiconv_open ();
+ ;
+ return 0;
+}
+_ACEOF
+rm -f conftest.$ac_objext conftest$ac_exeext
+if { (eval echo "$as_me:$LINENO: \"$ac_link\"") >&5
+ (eval $ac_link) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_c_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest$ac_exeext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ ac_cv_lib_iconv_libiconv_open=yes
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ac_cv_lib_iconv_libiconv_open=no
+fi
+rm -f conftest.err conftest.$ac_objext \
+ conftest$ac_exeext conftest.$ac_ext
+LIBS=$ac_check_lib_save_LIBS
+fi
+echo "$as_me:$LINENO: result: $ac_cv_lib_iconv_libiconv_open" >&5
+echo "${ECHO_T}$ac_cv_lib_iconv_libiconv_open" >&6
+if test $ac_cv_lib_iconv_libiconv_open = yes; then
+ USE_ICONV=1
+ ICONV_LDFLAGS=-liconv
+
+else
+ echo "$as_me:$LINENO: checking for iconv_open in -lc" >&5
+echo $ECHO_N "checking for iconv_open in -lc... $ECHO_C" >&6
+if test "${ac_cv_lib_c_iconv_open+set}" = set; then
+ echo $ECHO_N "(cached) $ECHO_C" >&6
+else
+ ac_check_lib_save_LIBS=$LIBS
+LIBS="-lc $LIBS"
+
+cat >conftest.$ac_ext <<_ACEOF
+/* confdefs.h. */
+_ACEOF
+cat confdefs.h >>conftest.$ac_ext
+cat >>conftest.$ac_ext <<_ACEOF
+/* end confdefs.h. */
+
+/* Override any gcc2 internal prototype to avoid an error. */
+#ifdef __cplusplus
+extern "C"
+#endif
+/* We use char because int might match the return type of a gcc2
+ builtin and then its argument prototype would still apply. */
+char iconv_open ();
+int
+main ()
+{
+iconv_open ();
+ ;
+ return 0;
+}
+_ACEOF
+rm -f conftest.$ac_objext conftest$ac_exeext
+if { (eval echo "$as_me:$LINENO: \"$ac_link\"") >&5
+ (eval $ac_link) 2>conftest.er1
+ ac_status=$?
+ grep -v '^ *+' conftest.er1 >conftest.err
+ rm -f conftest.er1
+ cat conftest.err >&5
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); } &&
+ { ac_try='test -z "$ac_c_werror_flag"
+ || test ! -s conftest.err'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; } &&
+ { ac_try='test -s conftest$ac_exeext'
+ { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
+ (eval $ac_try) 2>&5
+ ac_status=$?
+ echo "$as_me:$LINENO: \$? = $ac_status" >&5
+ (exit $ac_status); }; }; then
+ ac_cv_lib_c_iconv_open=yes
+else
+ echo "$as_me: failed program was:" >&5
+sed 's/^/| /' conftest.$ac_ext >&5
+
+ac_cv_lib_c_iconv_open=no
+fi
+rm -f conftest.err conftest.$ac_objext \
+ conftest$ac_exeext conftest.$ac_ext
+LIBS=$ac_check_lib_save_LIBS
+fi
+echo "$as_me:$LINENO: result: $ac_cv_lib_c_iconv_open" >&5
+echo "${ECHO_T}$ac_cv_lib_c_iconv_open" >&6
+if test $ac_cv_lib_c_iconv_open = yes; then
+ USE_ICONV=1
+
+else
+ USE_ICONV=0
+
+fi
+
+
+fi
+
+ ])
+m4trace:configure.in:53: -1- AC_CHECK_HEADERS([iconv.h])
+m4trace:configure.in:53: -1- AH_OUTPUT([HAVE_ICONV_H], [/* Define to 1 if you have the <iconv.h> header file. */
+#undef HAVE_ICONV_H])
+m4trace:configure.in:53: -1- AC_HEADER_STDC
+m4trace:configure.in:53: -1- AC_PROG_CPP
+m4trace:configure.in:53: -1- AC_SUBST([CPP])
+m4trace:configure.in:53: -1- AC_SUBST([CPPFLAGS])
+m4trace:configure.in:53: -1- AC_SUBST([CPP])
+m4trace:configure.in:53: -1- AC_SUBST([EGREP])
+m4trace:configure.in:53: -1- AC_DEFINE_TRACE_LITERAL([STDC_HEADERS])
+m4trace:configure.in:53: -1- AH_OUTPUT([STDC_HEADERS], [/* Define to 1 if you have the ANSI C header files. */
+#undef STDC_HEADERS])
+m4trace:configure.in:53: -1- AC_CHECK_HEADERS([sys/types.h sys/stat.h stdlib.h string.h memory.h strings.h \
+ inttypes.h stdint.h unistd.h], [], [], [$ac_includes_default])
+m4trace:configure.in:53: -1- AH_OUTPUT([HAVE_SYS_TYPES_H], [/* Define to 1 if you have the <sys/types.h> header file. */
+#undef HAVE_SYS_TYPES_H])
+m4trace:configure.in:53: -1- AH_OUTPUT([HAVE_SYS_STAT_H], [/* Define to 1 if you have the <sys/stat.h> header file. */
+#undef HAVE_SYS_STAT_H])
+m4trace:configure.in:53: -1- AH_OUTPUT([HAVE_STDLIB_H], [/* Define to 1 if you have the <stdlib.h> header file. */
+#undef HAVE_STDLIB_H])
+m4trace:configure.in:53: -1- AH_OUTPUT([HAVE_STRING_H], [/* Define to 1 if you have the <string.h> header file. */
+#undef HAVE_STRING_H])
+m4trace:configure.in:53: -1- AH_OUTPUT([HAVE_MEMORY_H], [/* Define to 1 if you have the <memory.h> header file. */
+#undef HAVE_MEMORY_H])
+m4trace:configure.in:53: -1- AH_OUTPUT([HAVE_STRINGS_H], [/* Define to 1 if you have the <strings.h> header file. */
+#undef HAVE_STRINGS_H])
+m4trace:configure.in:53: -1- AH_OUTPUT([HAVE_INTTYPES_H], [/* Define to 1 if you have the <inttypes.h> header file. */
+#undef HAVE_INTTYPES_H])
+m4trace:configure.in:53: -1- AH_OUTPUT([HAVE_STDINT_H], [/* Define to 1 if you have the <stdint.h> header file. */
+#undef HAVE_STDINT_H])
+m4trace:configure.in:53: -1- AH_OUTPUT([HAVE_UNISTD_H], [/* Define to 1 if you have the <unistd.h> header file. */
+#undef HAVE_UNISTD_H])
+m4trace:configure.in:60: -1- AC_CANONICAL_HOST
+m4trace:configure.in:60: -1- AC_SUBST([build], [$ac_cv_build])
+m4trace:configure.in:60: -1- AC_SUBST([build_cpu], [`echo $ac_cv_build | sed 's/^\([[^-]]*\)-\([[^-]]*\)-\(.*\)$/\1/'`])
+m4trace:configure.in:60: -1- AC_SUBST([build_vendor], [`echo $ac_cv_build | sed 's/^\([[^-]]*\)-\([[^-]]*\)-\(.*\)$/\2/'`])
+m4trace:configure.in:60: -1- AC_SUBST([build_os], [`echo $ac_cv_build | sed 's/^\([[^-]]*\)-\([[^-]]*\)-\(.*\)$/\3/'`])
+m4trace:configure.in:60: -1- AC_SUBST([host], [$ac_cv_host])
+m4trace:configure.in:60: -1- AC_SUBST([host_cpu], [`echo $ac_cv_host | sed 's/^\([[^-]]*\)-\([[^-]]*\)-\(.*\)$/\1/'`])
+m4trace:configure.in:60: -1- AC_SUBST([host_vendor], [`echo $ac_cv_host | sed 's/^\([[^-]]*\)-\([[^-]]*\)-\(.*\)$/\2/'`])
+m4trace:configure.in:60: -1- AC_SUBST([host_os], [`echo $ac_cv_host | sed 's/^\([[^-]]*\)-\([[^-]]*\)-\(.*\)$/\3/'`])
+m4trace:configure.in:65: -1- AC_SUBST([PGCONFIG])
+m4trace:configure.in:78: -1- AC_SUBST([PGCONFIG], [$ac_cv_path_PGCONFIG])
+m4trace:configure.in:83: -1- AC_SUBST([PGFEINCLUDES])
+m4trace:configure.in:84: -1- AC_SUBST([PGBEINCLUDES])
+m4trace:configure.in:85: -1- AC_SUBST([PGFELIBS])
+m4trace:configure.in:86: -1- AC_SUBST([PGBELIBS])
+m4trace:configure.in:87: -1- AC_SUBST([PGBIN])
+m4trace:configure.in:88: -1- AC_SUBST([PGTEMPLATE])
+m4trace:configure.in:89: -1- AC_SUBST([LPATH])
+m4trace:configure.in:111: -1- AC_SUBST([PWDREGRESS])
+m4trace:configure.in:117: -1- AC_SUBST([USE_GEOS])
+m4trace:configure.in:118: -1- AC_SUBST([GEOS_DIR])
+m4trace:configure.in:119: -1- AC_SUBST([GEOS_LDFLAGS])
+m4trace:configure.in:120: -1- AC_SUBST([USE_GEOS_CAPI])
+m4trace:configure.in:126: -1- AC_SUBST([GEOSCONFIG], [$ac_cv_path_GEOSCONFIG])
+m4trace:configure.in:186: -1- AC_SUBST([USE_PROJ])
+m4trace:configure.in:187: -1- AC_SUBST([PROJ_DIR])
+m4trace:configure.in:188: -1- AC_SUBST([PROJ_LIBDIR])
+m4trace:configure.in:192: -1- AC_SUBST([PROJ], [$ac_cv_path_PROJ])
+m4trace:configure.in:229: -1- AC_SUBST([USE_JTS])
+m4trace:configure.in:230: -1- AC_SUBST([JTS_INCLUDES])
+m4trace:configure.in:231: -1- AC_SUBST([JTS_LIBDIR])
+m4trace:configure.in:251: -1- AC_SUBST([JTSCONFIG], [$ac_cv_path_JTSCONFIG])
+m4trace:configure.in:263: -1- AC_SUBST([FLEX])
+m4trace:configure.in:264: -1- AC_SUBST([FLEX], [$ac_cv_path_FLEX])
+m4trace:configure.in:269: -1- AC_SUBST([DLLWRAP])
+m4trace:configure.in:270: -1- AC_SUBST([DLLWRAP], [$ac_cv_path_DLLWRAP])
+m4trace:configure.in:271: -1- AC_SUBST([DLLTOOL])
+m4trace:configure.in:272: -1- AC_SUBST([DLLTOOL], [$ac_cv_path_DLLTOOL])
+m4trace:configure.in:276: -1- AC_PROG_YACC
+m4trace:configure.in:276: -1- AC_SUBST([YACC])
+m4trace:configure.in:288: -1- AC_SUBST([INSTALL])
+m4trace:configure.in:294: -1- AC_SUBST([PERL])
+m4trace:configure.in:295: -1- AC_SUBST([PERL], [$ac_cv_path_PERL])
+m4trace:configure.in:300: -1- AC_SUBST([docdir])
+m4trace:configure.in:315: -1- AC_SUBST([XSLBASE])
+m4trace:configure.in:332: -1- AC_SUBST([XSLTPROC], [$ac_cv_path_XSLTPROC])
+m4trace:configure.in:333: -1- AC_SUBST([PDFXMLTEX], [$ac_cv_path_PDFXMLTEX])
+m4trace:configure.in:334: -1- AC_SUBST([DB2PDF], [$ac_cv_path_DB2PDF])
+m4trace:configure.in:335: -1- AC_SUBST([JW], [$ac_cv_path_JW])
+m4trace:configure.in:336: -1- AC_SUBST([XSLTPROC])
+m4trace:configure.in:337: -1- AC_SUBST([PDFXMLTEX])
+m4trace:configure.in:338: -1- AC_SUBST([JW])
+m4trace:configure.in:350: -1- AC_SUBST([DOC_RULE])
+m4trace:configure.in:525: -1- AC_SUBST([PORTNAME])
+m4trace:configure.in:531: -1- AC_SUBST([DLSUFFIX])
+m4trace:configure.in:532: -1- AC_SUBST([DLFLAGS])
+m4trace:configure.in:533: -1- AC_SUBST([EXE])
+m4trace:configure.in:534: -1- AC_SUBST([HOST_OS])
+m4trace:configure.in:571: -1- AC_SUBST([ELF_SYS])
+m4trace:configure.in:575: -1- AC_CONFIG_FILES([Makefile.config])
+m4trace:configure.in:575: -1- _m4_warn([obsolete], [AC_OUTPUT should be used without arguments.
+You should run autoupdate.], [])
+m4trace:configure.in:575: -1- AC_SUBST([LIB@&t at OBJS], [$ac_libobjs])
+m4trace:configure.in:575: -1- AC_SUBST([LTLIBOBJS], [$ac_ltlibobjs])
Modified: packages/postgis/upstream/configure
===================================================================
--- packages/postgis/upstream/configure 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/configure 2006-10-31 20:52:30 UTC (rev 577)
@@ -4570,7 +4570,6 @@
case $host_os in
*mingw*)
PGBEINCLUDES="$PGBEINCLUDES $PGBEINCLUDES/port/win32"
- PGFELIBS=`${PGCONFIG} --libdir`"/libpq.dll"
DLSUFFIX=.dll
DLFLAGS='${PGBELIBS}'
EXE=.exe
Modified: packages/postgis/upstream/configure.in
===================================================================
--- packages/postgis/upstream/configure.in 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/configure.in 2006-10-31 20:52:30 UTC (rev 577)
@@ -541,7 +541,6 @@
case $host_os in
*mingw*)
PGBEINCLUDES="$PGBEINCLUDES $PGBEINCLUDES/port/win32"
- PGFELIBS=`${PGCONFIG} --libdir`"/libpq.dll"
DLSUFFIX=.dll
DLFLAGS='${PGBELIBS}'
EXE=.exe
Deleted: packages/postgis/upstream/doc/html/postgis.html
===================================================================
--- packages/postgis/upstream/doc/html/postgis.html 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/doc/html/postgis.html 2006-10-31 20:52:30 UTC (rev 577)
@@ -1,2092 +0,0 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>PostGIS Manual</title><link rel="stylesheet" href="style.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.65.1"><meta name="description" content="PostGIS is an extension to the PostgreSQL object-relational
- database system which allows GIS (Geographic Information Systems)
- objects to be stored in the database. PostGIS includes support for
- GiST-based R-Tree spatial indexes, and functions for analysis and
- processing of GIS objects. This is the manual for version 1.1.4"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="id2580166"></a>PostGIS Manual</h1></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>PostGIS is an extension to the PostgreSQL object-relational
- database system which allows GIS (Geographic Information Systems)
- objects to be stored in the database. PostGIS includes support for
- GiST-based R-Tree spatial indexes, and functions for analysis and
- processing of GIS objects.</p><p>This is the manual for version 1.1.4</p></div></div></div><div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#id2582151">1. Introduction</a></span></dt><dd><dl><dt><span class="sect1"><a href="#credits">1.1. Credits</a></span></dt><dt><span class="sect1"><a href="#id2581981">1.2. More Information</a></span></dt></dl></dd><dt><span class="chapter"><a href="#id2609268">2. Installation</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id2609274">2.1. Requirements</a></span></dt><dt><span class="sect1"><a href="#PGInstall">2.2. PostGIS</a></span></dt><dd><dl><dt><span class="sect2"><a href="#upgrading">2.2.1. Upgrading</a></span></dt><dt><span class="sect2"><a href="#id2581192">2.2.2. Common Problems</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2649517">2.3. JDBC</a></span></dt><dt><span class="sect1"><a href="#id2649594">2.4. Loader/Dumper</a></span></dt></dl></dd><dt><span class="chapter"><a href="#id2649632">3. Frequently Asked Questions</a></span></dt><dt><span class="chapter"><a href="#id2650088">4. Using PostGIS</a></span></dt><dd><dl><dt><span class="sect1"><a href="#RefObject">4.1. GIS Objects</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2650115">4.1.1. OpenGIS WKB and WKT</a></span></dt><dt><span class="sect2"><a href="#id2650222">4.1.2. PostGIS EWKB, EWKT and Canonical Forms</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2650378">4.2. Using OpenGIS Standards</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2650411">4.2.1. The SPATIAL_REF_SYS Table</a></span></dt><dt><span class="sect2"><a href="#id2650620">4.2.2. The GEOMETRY_COLUMNS Table</a></span></dt><dt><span class="sect2"><a href="#id2650754">4.2.3. Creating a Spatial Table</a></span></dt><dt><span class="sect2"><a href="#id2650861">4.2.4. Ensuring OpenGIS compliancy of geometries</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2650951">4.3. Loading GIS Data</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2650964">4.3.1. Using SQL</a></span></dt><dt><span class="sect2"><a href="#id2651020">4.3.2. Using the Loader</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2651250">4.4. Retrieving GIS Data</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2651263">4.4.1. Using SQL</a></span></dt><dt><span class="sect2"><a href="#id2651429">4.4.2. Using the Dumper</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2651607">4.5. Building Indexes</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2651660">4.5.1. GiST Indexes</a></span></dt><dt><span class="sect2"><a href="#id2651729">4.5.2. Using Indexes</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2651847">4.6. Complex Queries</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2651866">4.6.1. Taking Advantage of Indexes</a></span></dt><dt><span class="sect2"><a href="#id2651962">4.6.2. Examples of Spatial SQL</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2652277">4.7. Using Mapserver</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2652320">4.7.1. Basic Usage</a></span></dt><dt><span class="sect2"><a href="#id2652568">4.7.2. Frequently Asked Questions</a></span></dt><dt><span class="sect2"><a href="#id2652735">4.7.3. Advanced Usage</a></span></dt><dt><span class="sect2"><a href="#id2580495">4.7.4. Examples</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2580593">4.8. Java Clients (JDBC)</a></span></dt><dt><span class="sect1"><a href="#id2653210">4.9. C Clients (libpq)</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2653219">4.9.1. Text Cursors</a></span></dt><dt><span class="sect2"><a href="#id2653229">4.9.2. Binary Cursors</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#id2653241">5. Performance tips</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id2653247">5.1. Small tables of large geometries</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2653253">5.1.1. Problem description</a></span></dt><dt><span class="sect2"><a href="#id2653305">5.1.2. Workarounds</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2653365">5.2. CLUSTERing on geometry indices</a></span></dt><dt><span class="sect1"><a href="#id2653421">5.3. Avoiding dimension conversion</a></span></dt></dl></dd><dt><span class="chapter"><a href="#id2653471">6. PostGIS Reference</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id2653484">6.1. OpenGIS Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2653490">6.1.1. Management Functions</a></span></dt><dt><span class="sect2"><a href="#id2653580">6.1.2. Geometry Relationship Functions</a></span></dt><dt><span class="sect2"><a href="#id2653956">6.1.3. Geometry Processing Functions</a></span></dt><dt><span class="sect2"><a href="#id2654282">6.1.4. Geometry Accessors</a></span></dt><dt><span class="sect2"><a href="#id2654768">6.1.5. Geometry Constructors</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2655371">6.2. Postgis Extensions</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2655376">6.2.1. Management Functions</a></span></dt><dt><span class="sect2"><a href="#id2655701">6.2.2. Operators</a></span></dt><dt><span class="sect2"><a href="#id2655909">6.2.3. Measurement Functions</a></span></dt><dt><span class="sect2"><a href="#id2656192">6.2.4. Geometry Outputs</a></span></dt><dt><span class="sect2"><a href="#id2656300">6.2.5. Geometry Constructors</a></span></dt><dt><span class="sect2"><a href="#id2656633">6.2.6. Geometry Editors</a></span></dt><dt><span class="sect2"><a href="#id2657229">6.2.7. Linear Referencing</a></span></dt><dt><span class="sect2"><a href="#id2657449">6.2.8. Misc</a></span></dt><dt><span class="sect2"><a href="#id2658447">6.2.9. Long Transactions support</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#id2658031">7. Reporting Bugs</a></span></dt><dt><span class="appendix"><a href="#release_notes">A. Appendix</a></span></dt><dd><dl><dt><span class="sect1"><a href="#id2658101">A.1. Release Notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2658106">A.1.1. Release 1.1.4</a></span></dt><dt><span class="sect2"><a href="#id2658230">A.1.2. Release 1.1.3</a></span></dt><dt><span class="sect2"><a href="#id2658396">A.1.3. Release 1.1.2</a></span></dt><dt><span class="sect2"><a href="#id2658690">A.1.4. Release 1.1.1</a></span></dt><dt><span class="sect2"><a href="#id2658820">A.1.5. Release 1.1.0</a></span></dt><dt><span class="sect2"><a href="#id2659145">A.1.6. Release 1.0.6</a></span></dt><dt><span class="sect2"><a href="#id2659254">A.1.7. Release 1.0.5</a></span></dt><dt><span class="sect2"><a href="#id2659386">A.1.8. Release 1.0.4</a></span></dt><dt><span class="sect2"><a href="#rel_1.0.3_upgrading">A.1.9. Release 1.0.3</a></span></dt><dt><span class="sect2"><a href="#id2659632">A.1.10. Release 1.0.2</a></span></dt><dt><span class="sect2"><a href="#id2659711">A.1.11. Release 1.0.1</a></span></dt><dt><span class="sect2"><a href="#id2659811">A.1.12. Release 1.0.0</a></span></dt><dt><span class="sect2"><a href="#id2659910">A.1.13. Release 1.0.0RC6</a></span></dt><dt><span class="sect2"><a href="#id2659984">A.1.14. Release 1.0.0RC5</a></span></dt><dt><span class="sect2"><a href="#id2660056">A.1.15. Release 1.0.0RC4</a></span></dt><dt><span class="sect2"><a href="#id2660181">A.1.16. Release 1.0.0RC3</a></span></dt><dt><span class="sect2"><a href="#id2660352">A.1.17. Release 1.0.0RC2</a></span></dt><dt><span class="sect2"><a href="#id2660450">A.1.18. Release 1.0.0RC1</a></span></dt></dl></dd></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2582151"></a>Chapter 1. Introduction</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#credits">1.1. Credits</a></span></dt><dt><span class="sect1"><a href="#id2581981">1.2. More Information</a></span></dt></dl></div><p>PostGIS is developed by Refractions Research Inc, as a spatial
- database technology research project. Refractions is a GIS and database
- consulting company in Victoria, British Columbia, Canada, specializing in
- data integration and custom software development. We plan on supporting
- and developing PostGIS to support a range of important GIS functionality,
- including full OpenGIS support, advanced topological constructs
- (coverages, surfaces, networks), desktop user interface tools for viewing
- and editing GIS data, and web-based access tools.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="credits"></a>1.1. Credits</h2></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">Sandro Santilli <strk at refractions.net></span></dt><dd><p>Coordinates all bug fixing and maintenance effort,
- integration of new GEOS functionality, and new function
- enhancements.</p></dd><dt><span class="term">Chris Hodgson <chodgson at refractions.net></span></dt><dd><p>Maintains new functions and the 7.2 index bindings.</p></dd><dt><span class="term">Paul Ramsey <pramsey at refractions.net></span></dt><dd><p>Keeps track of the
- documentation and packaging.</p></dd><dt><span class="term">Jeff Lounsbury <jeffloun at refractions.net></span></dt><dd><p>Original development of the Shape file loader/dumper.</p></dd><dt><span class="term">Dave Blasby <dblasby at gmail.com></span></dt><dd><p>The original developer of PostGIS. Dave wrote the server
- side objects, index bindings, and many of the server side
- analytical functions.</p></dd><dt><span class="term">Other contributors</span></dt><dd><p>
- In alphabetical order:
- Alex Bodnaru, Alex Mayrhofer, Bruce Rindahl,
- Bernhard Reiter,
- Bruno Wolff III, Carl Anderson, Charlie Savage,
- David Skea, David Techer,
- IIDA Tetsushi, Geographic Data BC, Gerald Fenoy,
- Gino Lucrezi, Klaus Foerster, Kris Jurka, Mark Cave-Ayland,
- Mark Sondheim, Markus Schaber, Michael Fuhr, Nikita Shulga,
- Norman Vine, Olivier Courtin, Ralph Mason, Steffen Macke.
- </p></dd><dt><span class="term">Important Support Libraries</span></dt><dd><p>The <a href="http://geos.refractions.net" target="_top">GEOS</a>
- geometry operations library, and the algorithmic work of
- Martin Davis <mbdavis at vividsolutions.com> of Vivid Solutions
- in making it all work.</p><p>The <a href="http://proj4.maptools.org" target="_top">Proj4</a>
- cartographic projection library, and the work of Gerald Evenden
- and Frank Warmerdam in creating and maintaining it.</p></dd></dl></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2581981"></a>1.2. More Information</h2></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>The latest software, documentation and news items are
- available at the PostGIS web site, <a href="http://postgis.refractions.net" target="_top">http://postgis.refractions.net</a>.</p></li><li><p>More information about the GEOS geometry operations library is
- available at<a href="http://geos.refractions.net" target="_top">
- http://geos.refractions.net</a>.</p></li><li><p>More information about the Proj4 reprojection library is
- available at <a href="http://www.remotesensing.org/proj" target="_top">http://www.remotesensing.org/proj</a>.</p></li><li><p>More information about the PostgreSQL database server is
- available at the PostgreSQL main site <a href="http://www.postgresql.org" target="_top">http://www.postgresql.org</a>.</p></li><li><p>More information about GiST indexing is available at the
- PostgreSQL GiST development site, <a href="http://www.sai.msu.su/~megera/postgres/gist" target="_top">http://www.sai.msu.su/~megera/postgres/gist</a>.</p></li><li><p>More information about Mapserver internet map server is
- available at <a href="http://mapserver.gis.umn.edu/" target="_top">http://mapserver.gis.umn.edu</a>.</p></li><li><p>The "<a href="http://www.opengis.org/docs/99-049.pdf" target="_top">Simple Features
- for Specification for SQL</a>" is available at the OpenGIS
- Consortium web site: <a href="http://www.opengis.org" target="_top">http://www.opengis.org</a>.</p></li></ul></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2609268"></a>Chapter 2. Installation</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#id2609274">2.1. Requirements</a></span></dt><dt><span class="sect1"><a href="#PGInstall">2.2. PostGIS</a></span></dt><dd><dl><dt><span class="sect2"><a href="#upgrading">2.2.1. Upgrading</a></span></dt><dt><span class="sect2"><a href="#id2581192">2.2.2. Common Problems</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2649517">2.3. JDBC</a></span></dt><dt><span class="sect1"><a href="#id2649594">2.4. Loader/Dumper</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2609274"></a>2.1. Requirements</h2></div></div><div></div></div><p>PostGIS has the following requirements for building and
- usage:</p><div class="itemizedlist"><ul type="disc"><li><p>
- A complete installation of PostgreSQL (including server headers).
- PostgreSQL is available from <a href="http://www.postgresql.org" target="_top">http://www.postgresql.org</a>.
- Version 7.2 or higher is required.
- </p></li><li><p>GNU C compiler (<tt class="filename">gcc</tt>). Some other ANSI C
- compilers can be used to compile PostGIS, but we find far fewer
- problems when compiling with <tt class="filename">gcc</tt>.</p></li><li><p>GNU Make (<tt class="filename">gmake</tt> or
- <tt class="filename">make</tt>). For many systems, GNU
- <tt class="filename">make</tt> is the default version of make. Check the
- version by invoking <tt class="filename">make -v</tt>. Other versions of
- <tt class="filename">make</tt> may not process the PostGIS
- <tt class="filename">Makefile</tt> properly.</p></li><li><p>(Recommended) Proj4 reprojection library. The Proj4 library is
- used to provide coordinate reprojection support within PostGIS.
- Proj4 is available for download from <a href="http://www.remotesensing.org/proj" target="_top">http://www.remotesensing.org/proj</a>.</p></li><li><p>(Recommended) GEOS geometry library. The GEOS library is used
- to provide geometry tests (Touches(), Contains(), Intersects()) and
- operations (Buffer(), GeomUnion(), Difference()) within PostGIS.
- GEOS is available for download from <a href="http://geos.refractions.net" target="_top">http://geos.refractions.net</a>.</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="PGInstall"></a>2.2. PostGIS</h2></div></div><div></div></div><p>The PostGIS module is a extension to the PostgreSQL backend
- server. As such, PostGIS 1.1.4
- <span class="emphasis"><em>requires</em></span> full PostgreSQL server headers access
- in order to compile. The PostgreSQL source code is available at <a href="http://www.postgresql.org" target="_top">http://www.postgresql.org</a>.</p><p>PostGIS 1.1.4 can be built against PostgreSQL
- versions 7.2.0 or higher. Earlier versions of PostgreSQL are
- <span class="emphasis"><em>not</em></span> supported.</p><div class="orderedlist"><ol type="1"><li><p>Before you can compile the PostGIS server modules, you must
- compile and install the PostgreSQL package.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>If you plan to use GEOS functionality you might need to
- explicitly link PostgreSQL against the standard C++
- library:</p><pre class="programlisting">LDFLAGS=-lstdc++ ./configure [YOUR OPTIONS HERE]</pre><p>This is a workaround for bogus C++ exceptions interaction
- with older development tools. If you experience weird problems
- (backend unexpectedly closed or similar things) try this trick.
- This will require recompiling your PostgreSQL from scratch, of
- course.</p></div></li><li><p>Retrieve the PostGIS source archive from <a href="http://postgis.refractions.net/postgis-1.1.4.tar.gz" target="_top">http://postgis.refractions.net/postgis-1.1.4.tar.gz</a>.
- Uncompress and untar the archive.
- </p><pre class="programlisting"># gzip -d -c postgis-1.1.4.tar.gz | tar xvf -</pre></li><li><p>Enter the postgis-1.1.4 directory, and run:
-</p><pre class="programlisting"># ./configure</pre><p>
- </p><div class="itemizedlist"><ul type="disc"><li><p>
- If you want support for coordinate reprojection, you must have
- the Proj4 library installed. If ./configure didn't find
- it, try using <tt class="code">--with-proj=PATH</tt>
- switch specify a specific Proj4 installation directory.
- </p></li><li><p>
- If you want to use GEOS functionality, you must have the GEOS
- library installed. If ./configure didn't find it, try
- using <tt class="code">--with-geos=PATH</tt> to specify the full
- path to the geos-config program full path.
- </p></li></ul></div></li><li><p>Run the compile and install commands.</p><pre class="programlisting"># make
-# make install</pre><p>All files are installed using information provided
- by <tt class="filename">pg_config</tt></p><div class="itemizedlist"><ul type="disc"><li><p>Libraries are installed
- <tt class="filename">[pkglibdir]/lib/contrib</tt>.</p></li><li><p>Important support files such as
- <tt class="filename">lwpostgis.sql</tt> are installed in
- <tt class="filename">[prefix]/share/contrib</tt>.</p></li><li><p>Loader and dumper binaries are installed in
- <tt class="filename">[bindir]/</tt>.</p></li></ul></div></li><li><p>PostGIS requires the PL/pgSQL procedural language extension.
- Before loading the <tt class="filename">lwpostgis.sql</tt> file, you must
- first enable PL/pgSQL. You should use the
- <tt class="filename">createlang</tt> command. The PostgreSQL
- Programmer's Guide has the details if you want to this manually for
- some reason.</p><pre class="programlisting"># createlang plpgsql [yourdatabase]</pre></li><li><p>Now load the PostGIS object and function definitions into your
- database by loading the <tt class="filename">lwpostgis.sql</tt> definitions
- file.</p><pre class="programlisting"># psql -d [yourdatabase] -f lwpostgis.sql</pre><p>The PostGIS server extensions are now loaded and ready to
- use.</p></li><li><p>For a complete set of EPSG coordinate system definition
- identifiers, you can also load the
- <tt class="filename">spatial_ref_sys.sql</tt> definitions file and
- populate the <tt class="varname">SPATIAL_REF_SYS</tt> table.</p><pre class="programlisting"># psql -d [yourdatabase] -f spatial_ref_sys.sql</pre></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="upgrading"></a>2.2.1. Upgrading</h3></div></div><div></div></div><p>
-Upgrading existing spatial databases can be tricky as it requires
-replacement or introduction of new PostGIS object definitions.
-</p><p>
-Unfortunately not all definitions can be easily replaced in
-a live database, so sometimes your best bet is a dump/reload
-process.
-</p><p>
-PostGIS provides a SOFT UPGRADE procedure for minor or bugfix
-releases, and an HARD UPGRADE procedure for major releases.
-</p><p>
-Before attempting to upgrade postgis, it is always worth to backup
-your data. If you use the -Fc flag to pg_dump you will always be able
-to restore the dump with an HARD UPGRADE.
- </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="soft_upgrade"></a>2.2.1.1. Soft upgrade</h4></div></div><div></div></div><p>
-Soft upgrade consists of sourcing the lwpostgis_upgrade.sql
-script in your spatial database:
-</p><pre class="programlisting">psql -f lwpostgis_upgrade.sql -d your_spatial_database</pre><p>
-If a soft upgrade is not possible the script will abort and
-you will be warned about HARD UPGRADE being required,
-so do not hesitate to try a soft upgrade first.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-If you can't find the <tt class="filename">lwpostgis_upgrade.sql</tt> file
-you are probably using a version prior to 1.1 and must generate that
-file by yourself. This is done with the following command:
-</p><pre class="programlisting">utils/postgis_proc_upgrade.pl lwpostgis.sql > lwpostgis_upgrade.sql</pre></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="hard_upgrade"></a>2.2.1.2. Hard upgrade</h4></div></div><div></div></div><p>
-By HARD UPGRADE we intend full dump/reload of postgis-enabled databases.
-You need an HARD UPGRADE when postgis objects' internal storage
-changes or when SOFT UPGRADE is not possible.
-The <a href="#release_notes" title="Appendix A. Appendix">Release Notes</a> appendix reports for each version whether you need a
-dump/reload (HARD UPGRADE) to upgrade.
- </p><p>
-PostGIS provides an utility script to restore a dump
-produced with the pg_dump -Fc command. It is experimental so redirecting
-its output to a file will help in case of problems. The procedure is
-as follow:
- </p><pre class="programlisting">
- # Create a "custom-format" dump of the database you want
- # to upgrade (let's call it "olddb")
- $ pg_dump -Fc olddb > olddb.dump
-
- # Restore the dump contextually upgrading postgis into
- # a new database. The new database doesn't have to exist.
- # Let's call it "newdb"
- $ sh utils/postgis_restore.pl lwpostgis.sql newdb olddb.dump > restore.log
-
- # Check that all restored dump objects really had to be restored from dump
- # and do not conflict with the ones defined in lwpostgis.sql
- $ grep ^KEEPING restore.log | less
-
- # If upgrading from PostgreSQL < 8.0 to >= 8.0 you might want to
- # drop the attrelid, varattnum and stats columns in the geometry_columns
- # table, which are no-more needed. Keeping them won't hurt.
- # !!! DROPPING THEM WHEN REALLY NEEDED WILL DO HURT !!!!
- $ psql newdb -c "ALTER TABLE geometry_columns DROP attrelid"
- $ psql newdb -c "ALTER TABLE geometry_columns DROP varattnum"
- $ psql newdb -c "ALTER TABLE geometry_columns DROP stats"
-
- # spatial_ref_sys table is restore from the dump, to ensure your custom
- # additions are kept, but the distributed one might contain modification
- # so you should backup your entries, drop the table and source the new one.
- # If you did make additions we assume you know how to backup them before
- # upgrading the table. Replace of it with the new one is done like this:
- $ psql newdb
- newdb=> delete from spatial_ref_sys;
- DROP
- newdb=> \i spatial_ref_sys.sql
- </pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2581192"></a>2.2.2. Common Problems</h3></div></div><div></div></div><p>There are several things to check when your installation or
- upgrade doesn't go as you expected.</p><div class="orderedlist"><ol type="1"><li><p>It is easiest if you untar the PostGIS distribution into the
- contrib directory under the PostgreSQL source tree. However, if
- this is not possible for some reason, you can set the
- <tt class="varname">PGSQL_SRC</tt> environment variable to the path to
- the PostgreSQL source directory. This will allow you to compile
- PostGIS, but the <span><b class="command">make install</b></span> may not work, so
- be prepared to copy the PostGIS library and executable files to
- the appropriate locations yourself.</p></li><li><p>Check that you you have installed PostgreSQL 7.2 or newer,
- and that you are compiling against the same version of the
- PostgreSQL source as the version of PostgreSQL that is running.
- Mix-ups can occur when your (Linux) distribution has already
- installed PostgreSQL, or you have otherwise installed PostgreSQL
- before and forgotten about it. PostGIS will only work with
- PostgreSQL 7.2 or newer, and strange, unexpected error messages
- will result if you use an older version. To check the version of
- PostgreSQL which is running, connect to the database using psql
- and run this query:</p><pre class="programlisting">SELECT version();</pre><p>If you are running an RPM based distribution, you can check
- for the existence of pre-installed packages using the
- <span><b class="command">rpm</b></span> command as follows: <span><b class="command">rpm -qa | grep
- postgresql</b></span></p></li></ol></div><p>Also check that you have made any necessary changes to the top
- of the Makefile.config. This includes:</p><div class="orderedlist"><ol type="1"><li><p>If you want to be able to do coordinate reprojections, you
- must install the Proj4 library on your system, set the
- <tt class="varname">USE_PROJ</tt> variable to 1 and the
- <tt class="varname">PROJ_DIR</tt> to your installation prefix in the
- Makefile.config.</p></li><li><p>If you want to be able to use GEOS functions you must
- install the GEOS library on your system, and set the
- <tt class="varname">USE_GEOS</tt> to 1 and the
- <tt class="varname">GEOS_DIR</tt> to your installation prefix in the
- Makefile.config</p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2649517"></a>2.3. JDBC</h2></div></div><div></div></div><p>The JDBC extensions provide Java objects corresponding to the
- internal PostGIS types. These objects can be used to write Java clients
- which query the PostGIS database and draw or do calculations on the GIS
- data in PostGIS.</p><div class="orderedlist"><ol type="1"><li><p>Enter the <tt class="filename">jdbc</tt> sub-directory of the
- PostGIS distribution.</p></li><li><p>Edit the <tt class="filename">Makefile</tt> to provide the correct
- paths of your java compiler (<tt class="varname">JAVAC</tt>) and
- interpreter (<tt class="varname">JAVA</tt>).</p></li><li><p>Run the <tt class="filename">make</tt> command. Copy the
- <tt class="filename">postgis.jar</tt> file to wherever you keep your java
- libraries.</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2649594"></a>2.4. Loader/Dumper</h2></div></div><div></div></div><p>The data loader and dumper are built and installed automatically
- as part of the PostGIS build. To build and install them manually:</p><pre class="programlisting"># cd postgis-1.1.4/loader
-# make
-# make install</pre><p>The loader is called <tt class="filename">shp2pgsql</tt> and converts
- ESRI Shape files into SQL suitable for loading in PostGIS/PostgreSQL.
- The dumper is called <tt class="filename">pgsql2shp</tt> and converts PostGIS
- tables (or queries) into ESRI Shape files.</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2649632"></a>Chapter 3. Frequently Asked Questions</h2></div></div><div></div></div><div class="qandaset"><dl><dt>3.1. <a href="#id2649640">What kind of geometric objects can I store?</a></dt><dt>3.2. <a href="#id2649661">How do I insert a GIS object into the database?</a></dt><dt>3.3. <a href="#id2649756">How do I construct a spatial query?</a></dt><dt>3.4. <a href="#id2649822">How do I speed up spatial queries on large tables?</a></dt><dt>3.5. <a href="#id2649903">Why aren't PostgreSQL R-Tree indexes supported?</a></dt><dt>3.6. <a href="#id2649956">Why should I use the AddGeometryColumn()
- function and all the other OpenGIS stuff?</a></dt><dt>3.7. <a href="#id2650004">What is the best way to find all objects within a radius of
- another object?</a></dt><dt>3.8. <a href="#id2650056">How do I perform a coordinate reprojection as part of a
- query?</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2649640"></a><a name="id2649642"></a><b>3.1.</b></td><td align="left" valign="top"><p>What kind of geometric objects can I store?</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>You can store point, line, polygon, multipoint, multiline,
- multipolygon, and geometrycollections. These are specified in the
- Open GIS Well Known Text Format (with XYZ,XYM,XYZM extentions).</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2649661"></a><a name="id2649663"></a><b>3.2.</b></td><td align="left" valign="top"><p>How do I insert a GIS object into the database?</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>First, you need to create a table with a column of type
- "geometry" to hold your GIS data. Connect to your database with
- <tt class="filename">psql</tt> and try the following SQL:</p><pre class="programlisting">CREATE TABLE gtest ( ID int4, NAME varchar(20) );
-SELECT AddGeometryColumn('', 'gtest','geom',-1,'LINESTRING',2);</pre><p>If the geometry column addition fails, you probably have not
- loaded the PostGIS functions and objects into this database. See the
- <a href="#PGInstall" title="2.2. PostGIS">installation instructions</a>.</p><p>Then, you can insert a geometry into the table using a SQL
- insert statement. The GIS object itself is formatted using the
- OpenGIS Consortium "well-known text" format:</p><pre class="programlisting">INSERT INTO gtest (ID, NAME, GEOM) VALUES (1, 'First Geometry', GeomFromText('LINESTRING(2 3,4 5,6 5,7 8)', -1));</pre><p>For more information about other GIS objects, see the <a href="#RefObject" title="4.1. GIS Objects">object reference</a>.</p><p>To view your GIS data in the table:</p><pre class="programlisting">SELECT id, name, AsText(geom) AS geom FROM gtest;</pre><p>The return value should look something like this:</p><pre class="programlisting"> id | name | geom
-----+----------------+-----------------------------
- 1 | First Geometry | LINESTRING(2 3,4 5,6 5,7 8)
-(1 row)</pre></td></tr><tr class="question"><td align="left" valign="top"><a name="id2649756"></a><a name="id2649758"></a><b>3.3.</b></td><td align="left" valign="top"><p>How do I construct a spatial query?</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>The same way you construct any other database query, as an SQL
- combination of return values, functions, and boolean tests.</p><p>For spatial queries, there are two issues that are important
- to keep in mind while constructing your query: is there a spatial
- index you can make use of; and, are you doing expensive calculations
- on a large number of geometries.</p><p>In general, you will want to use the "intersects operator"
- (&&) which tests whether the bounding boxes of features
- intersect. The reason the && operator is useful is because
- if a spatial index is available to speed up the test, the &&
- operator will make use of this. This can make queries much much
- faster.</p><p>You will also make use of spatial functions, such as
- Distance(), Intersects(), Contains() and Within(), among others, to
- narrow down the results of your search. Most spatial queries include
- both an indexed test and a spatial function test. The index test
- serves to limit the number of return tuples to only tuples that
- <span class="emphasis"><em>might</em></span> meet the condition of interest. The
- spatial functions are then use to test the condition exactly.</p><pre class="programlisting">SELECT id, the_geom FROM thetable
-WHERE
- the_geom && 'POLYGON((0 0, 0 10, 10 10, 10 0, 0 0))'
-AND
- Contains(the_geom,'POLYGON((0 0, 0 10, 10 10, 10 0, 0 0))';</pre></td></tr><tr class="question"><td align="left" valign="top"><a name="id2649822"></a><a name="id2649824"></a><b>3.4.</b></td><td align="left" valign="top"><p>How do I speed up spatial queries on large tables?</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>Fast queries on large tables is the <span class="emphasis"><em>raison
- d'etre</em></span> of spatial databases (along with transaction
- support) so having a good index is important.</p><p>To build a spatial index on a table with a
- <tt class="varname">geometry</tt> column, use the "CREATE INDEX" function
- as follows:</p><pre class="programlisting">CREATE INDEX [indexname] ON [tablename]
- USING GIST ( [geometrycolumn] );</pre><p>The "USING GIST" option tells the server to use a GiST
- (Generalized Search Tree) index.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- GiST indexes are assumed to be lossy.
- Lossy indexes uses a proxy object (in the spatial case,
- a bounding box) for building the index.</p></div><p>You should also ensure that the PostgreSQL query planner has
- enough information about your index to make rational decisions about
- when to use it. To do this, you have to "gather statistics" on your
- geometry tables.</p><p>For PostgreSQL 8.0.x and greater, just run the <span><b class="command">VACUUM
- ANALYZE</b></span> command.</p><p>For PostgreSQL 7.4.x and below, run the <span><b class="command">SELECT
- UPDATE_GEOMETRY_STATS()</b></span> command.</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2649903"></a><a name="id2649906"></a><b>3.5.</b></td><td align="left" valign="top"><p>Why aren't PostgreSQL R-Tree indexes supported?</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>Early versions of PostGIS used the PostgreSQL R-Tree indexes.
- However, PostgreSQL R-Trees have been completely discarded since
- version 0.6, and spatial indexing is provided with an
- R-Tree-over-GiST scheme.</p><p>Our tests have shown search speed for native R-Tree and GiST
- to be comparable. Native PostgreSQL R-Trees have two limitations
- which make them undesirable for use with GIS features (note that
- these limitations are due to the current PostgreSQL native R-Tree
- implementation, not the R-Tree concept in general):</p><div class="itemizedlist"><ul type="disc"><li><p>R-Tree indexes in PostgreSQL cannot handle features which
- are larger than 8K in size. GiST indexes can, using the "lossy"
- trick of substituting the bounding box for the feature
- itself.</p></li><li><p>R-Tree indexes in PostgreSQL are not "null safe", so
- building an index on a geometry column which contains null
- geometries will fail.</p></li></ul></div></td></tr><tr class="question"><td align="left" valign="top"><a name="id2649956"></a><a name="id2649958"></a><b>3.6.</b></td><td align="left" valign="top"><p>Why should I use the <tt class="varname">AddGeometryColumn()</tt>
- function and all the other OpenGIS stuff?</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>If you do not want to use the OpenGIS support functions, you
- do not have to. Simply create tables as in older versions, defining
- your geometry columns in the CREATE statement. All your geometries
- will have SRIDs of -1, and the OpenGIS meta-data tables will
- <span class="emphasis"><em>not</em></span> be filled in properly. However, this will
- cause most applications based on PostGIS to fail, and it is
- generally suggested that you do use
- <tt class="varname">AddGeometryColumn()</tt> to create geometry
- tables.</p><p>Mapserver is one application which makes use of the
- <tt class="varname">geometry_columns</tt> meta-data. Specifically,
- Mapserver can use the SRID of the geometry column to do on-the-fly
- reprojection of features into the correct map projection.</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2650004"></a><a name="id2650006"></a><b>3.7.</b></td><td align="left" valign="top"><p>What is the best way to find all objects within a radius of
- another object?</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>To use the database most efficiently, it is best to do radius
- queries which combine the radius test with a bounding box test: the
- bounding box test uses the spatial index, giving fast access to a
- subset of data which the radius test is then applied to.</p><p>The <tt class="varname">Expand()</tt> function is a handy way of
- enlarging a bounding box to allow an index search of a region of
- interest. The combination of a fast access index clause and a slower
- accurate distance test provides the best combination of speed and
- precision for this query.</p><p>For example, to find all objects with 100 meters of POINT(1000
- 1000) the following query would work well:</p><pre class="programlisting">SELECT *
-FROM GEOTABLE
-WHERE
- GEOCOLUMN && Expand(GeomFromText('POINT(1000 1000)',-1),100)
-AND
- Distance(GeomFromText('POINT(1000 1000)',-1),GEOCOLUMN) < 100;</pre></td></tr><tr class="question"><td align="left" valign="top"><a name="id2650056"></a><a name="id2650058"></a><b>3.8.</b></td><td align="left" valign="top"><p>How do I perform a coordinate reprojection as part of a
- query?</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>To perform a reprojection, both the source and destination
- coordinate systems must be defined in the SPATIAL_REF_SYS table, and
- the geometries being reprojected must already have an SRID set on
- them. Once that is done, a reprojection is as simple as referring to
- the desired destination SRID.</p><pre class="programlisting">SELECT Transform(GEOM,4269) FROM GEOTABLE;</pre></td></tr></tbody></table></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2650088"></a>Chapter 4. Using PostGIS</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#RefObject">4.1. GIS Objects</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2650115">4.1.1. OpenGIS WKB and WKT</a></span></dt><dt><span class="sect2"><a href="#id2650222">4.1.2. PostGIS EWKB, EWKT and Canonical Forms</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2650378">4.2. Using OpenGIS Standards</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2650411">4.2.1. The SPATIAL_REF_SYS Table</a></span></dt><dt><span class="sect2"><a href="#id2650620">4.2.2. The GEOMETRY_COLUMNS Table</a></span></dt><dt><span class="sect2"><a href="#id2650754">4.2.3. Creating a Spatial Table</a></span></dt><dt><span class="sect2"><a href="#id2650861">4.2.4. Ensuring OpenGIS compliancy of geometries</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2650951">4.3. Loading GIS Data</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2650964">4.3.1. Using SQL</a></span></dt><dt><span class="sect2"><a href="#id2651020">4.3.2. Using the Loader</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2651250">4.4. Retrieving GIS Data</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2651263">4.4.1. Using SQL</a></span></dt><dt><span class="sect2"><a href="#id2651429">4.4.2. Using the Dumper</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2651607">4.5. Building Indexes</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2651660">4.5.1. GiST Indexes</a></span></dt><dt><span class="sect2"><a href="#id2651729">4.5.2. Using Indexes</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2651847">4.6. Complex Queries</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2651866">4.6.1. Taking Advantage of Indexes</a></span></dt><dt><span class="sect2"><a href="#id2651962">4.6.2. Examples of Spatial SQL</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2652277">4.7. Using Mapserver</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2652320">4.7.1. Basic Usage</a></span></dt><dt><span class="sect2"><a href="#id2652568">4.7.2. Frequently Asked Questions</a></span></dt><dt><span class="sect2"><a href="#id2652735">4.7.3. Advanced Usage</a></span></dt><dt><span class="sect2"><a href="#id2580495">4.7.4. Examples</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2580593">4.8. Java Clients (JDBC)</a></span></dt><dt><span class="sect1"><a href="#id2653210">4.9. C Clients (libpq)</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2653219">4.9.1. Text Cursors</a></span></dt><dt><span class="sect2"><a href="#id2653229">4.9.2. Binary Cursors</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="RefObject"></a>4.1. GIS Objects</h2></div></div><div></div></div><p>The GIS objects supported by PostGIS are a superset of
- the "Simple Features" defined by the OpenGIS Consortium (OGC).
- As of version 0.9, PostGIS supports all the objects and functions
- specified in the OGC "Simple Features for SQL" specification.</p><p>PostGIS extends the standard with support for 3DZ,3DM and 4D
- coordinates.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2650115"></a>4.1.1. OpenGIS WKB and WKT</h3></div></div><div></div></div><p>The OpenGIS specification defines two standard ways of
- expressing spatial objects: the Well-Known Text (WKT) form and
- the Well-Known Binary (WKB) form. Both WKT and WKB include
- information about the type of the object and the
- coordinates which form the object.</p><p>Examples of the text representations (WKT) of the spatial
- objects of the features are as follows:</p><div class="itemizedlist"><ul type="disc"><li><p>POINT(0 0)</p></li><li><p>LINESTRING(0 0,1 1,1 2)</p></li><li><p>POLYGON((0 0,4 0,4 4,0 4,0 0),(1 1, 2 1, 2 2, 1 2,1 1))</p></li><li><p>MULTIPOINT(0 0,1 2)</p></li><li><p>MULTILINESTRING((0 0,1 1,1 2),(2 3,3 2,5 4))</p></li><li><p>MULTIPOLYGON(((0 0,4 0,4 4,0 4,0 0),(1 1,2 1,2 2,1 2,1 1)),
- ((-1 -1,-1 -2,-2 -2,-2 -1,-1 -1)))</p></li><li><p>GEOMETRYCOLLECTION(POINT(2 3),LINESTRING((2 3,3 4)))</p></li></ul></div><p>The OpenGIS specification also requires that the
- internal storage format of spatial objects include a spatial
- referencing system identifier (SRID). The SRID is required when
- creating spatial objects for insertion into the database.</p><p>
-Input/Output of these formats are available using the following
-interfaces:
-</p><pre class="programlisting">
- bytea WKB = asBinary(geometry);
- text WKT = asText(geometry);
- geometry = GeomFromWKB(bytea WKB, SRID);
- geometry = GeometryFromText(text WKT, SRID);
- </pre><p> For example, a valid insert statement to create and insert an OGC spatial object would be:</p><pre class="programlisting">
- INSERT INTO SPATIALTABLE (
- THE_GEOM,
- THE_NAME
- )
- VALUES (
- GeomFromText('POINT(-126.4 45.32)', 312),
- 'A Place'
- )</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2650222"></a>4.1.2. PostGIS EWKB, EWKT and Canonical Forms</h3></div></div><div></div></div><p>
-OGC formats only support 2d geometries, and the associated SRID
-is *never* embedded in the input/output representations.
-</p><p>
-Postgis extended formats are currently superset of OGC one (every
-valid WKB/WKT is a valid EWKB/EWKT) but this might vary in the
-future, specifically if OGC comes out with a new format conflicting
-with our extensions. Thus you SHOULD NOT rely on this feature!
-</p><p>
-Postgis EWKB/EWKT add 3dm,3dz,4d coordinates support and embedded
-SRID information.
-</p><p>Examples of the text representations (EWKT) of the
- extended spatial objects of the features are as follows:</p><div class="itemizedlist"><ul type="disc"><li><p>POINT(0 0 0) -- XYZ</p></li><li><p>SRID=32632;POINT(0 0) -- XY with SRID</p></li><li><p>POINTM(0 0 0) -- XYM</p></li><li><p>POINT(0 0 0 0) -- XYZM</p></li><li><p>SRID=4326;MULTIPOINTM(0 0 0,1 2 1) -- XYM with SRID</p></li><li><p>MULTILINESTRING((0 0 0,1 1 0,1 2 1),(2 3 1,3 2 1,5 4
- 1))</p></li><li><p>POLYGON((0 0 0,4 0 0,4 4 0,0 4 0,0 0 0),(1 1 0,2 1 0,2 2 0,1 2
- 0,1 1 0))</p></li><li><p>MULTIPOLYGON(((0 0 0,4 0 0,4 4 0,0 4 0,0 0 0),(1 1 0,2 1 0,2 2
- 0,1 2 0,1 1 0)),((-1 -1 0,-1 -2 0,-2 -2 0,-2 -1 0,-1 -1 0)))</p></li><li><p>GEOMETRYCOLLECTIONM(POINTM(2 3 9),LINESTRINGM((2 3 4,3 4
- 5)))</p></li></ul></div><p>
-Input/Output of these formats are available using the following
-interfaces:
-</p><pre class="programlisting">
- bytea EWKB = asEWKB(geometry);
- text EWKT = asEWKT(geometry);
- geometry = GeomFromEWKB(bytea EWKB);
- geometry = GeomFromEWKT(text EWKT);
- </pre><p>
-For example, a valid insert statement to create and insert a PostGIS spatial object would be:
-</p><pre class="programlisting">
- INSERT INTO SPATIALTABLE (
- THE_GEOM,
- THE_NAME
- )
- VALUES (
- GeomFromEWKT('SRID=312;POINTM(-126.4 45.32 15)'),
- 'A Place'
- )</pre><p>
-The "canonical forms" of a PostgreSQL type are the representations
-you get with a simple query (without any function call) and the one
-which is guaranteed to be accepted with a simple insert, update or
-copy. For the postgis 'geometry' type these are:
-
- </p><pre class="programlisting">
- - Output -
- binary: EWKB
- ascii: HEXEWKB (EWKB in hex form)
-
- - Input -
- binary: EWKB
- ascii: HEXEWKB|EWKT
- </pre><p>
-</p><p>
-For example this statement reads EWKT and returns HEXEWKB in the
-process of canonical ascii input/output:
-</p><pre class="programlisting">
- =# SELECT 'SRID=4;POINT(0 0)'::geometry;
- geometry
- ----------------------------------------------------
- 01010000200400000000000000000000000000000000000000
- (1 row)
- </pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2650378"></a>4.2. Using OpenGIS Standards</h2></div></div><div></div></div><p>The OpenGIS "Simple Features Specification for SQL" defines
- standard GIS object types, the functions required to manipulate them,
- and a set of meta-data tables. In order to ensure that meta-data remain
- consistent, operations such as creating and removing a spatial column
- are carried out through special procedures defined by OpenGIS.</p><p>There are two OpenGIS meta-data tables:
- <tt class="varname">SPATIAL_REF_SYS</tt> and
- <tt class="varname">GEOMETRY_COLUMNS</tt>. The
- <tt class="varname">SPATIAL_REF_SYS</tt> table holds the numeric IDs and
- textual descriptions of coordinate systems used in the spatial
- database.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2650411"></a>4.2.1. The SPATIAL_REF_SYS Table</h3></div></div><div></div></div><p>The <tt class="varname">SPATIAL_REF_SYS</tt> table definition is as
- follows:</p><pre class="programlisting">CREATE TABLE SPATIAL_REF_SYS (
- SRID INTEGER NOT NULL PRIMARY KEY,
- AUTH_NAME VARCHAR(256),
- AUTH_SRID INTEGER,
- SRTEXT VARCHAR(2048),
- PROJ4TEXT VARCHAR(2048)
-)</pre><p>The <tt class="varname">SPATIAL_REF_SYS</tt> columns are as
- follows:</p><div class="variablelist"><dl><dt><span class="term">SRID</span></dt><dd><p>An integer value that uniquely identifies the Spatial
- Referencing System (SRS) within the database.</p></dd><dt><span class="term">AUTH_NAME</span></dt><dd><p>The name of the standard or standards body that is being
- cited for this reference system. For example, "EPSG" would be a
- valid <tt class="varname">AUTH_NAME</tt>.</p></dd><dt><span class="term">AUTH_SRID</span></dt><dd><p>The ID of the Spatial Reference System as defined by the
- Authority cited in the <tt class="varname">AUTH_NAME</tt>. In the case
- of EPSG, this is where the EPSG projection code would go.</p></dd><dt><span class="term">SRTEXT</span></dt><dd><p>The Well-Known Text representation of the Spatial
- Reference System. An example of a WKT SRS representation
- is:</p><pre class="programlisting">PROJCS["NAD83 / UTM Zone 10N",
- GEOGCS["NAD83",
- DATUM["North_American_Datum_1983",
- SPHEROID["GRS 1980",6378137,298.257222101]
- ],
- PRIMEM["Greenwich",0],
- UNIT["degree",0.0174532925199433]
- ],
- PROJECTION["Transverse_Mercator"],
- PARAMETER["latitude_of_origin",0],
- PARAMETER["central_meridian",-123],
- PARAMETER["scale_factor",0.9996],
- PARAMETER["false_easting",500000],
- PARAMETER["false_northing",0],
- UNIT["metre",1]
-]</pre><p>For a listing of EPSG projection codes and their
- corresponding WKT representations, see <a href="http://www.opengis.org/techno/interop/EPSG2WKT.TXT" target="_top">http://www.opengis.org/techno/interop/EPSG2WKT.TXT</a>.
- For a discussion of WKT in general, see the OpenGIS "Coordinate
- Transformation Services Implementation Specification" at <a href="http://www.opengis.org/techno/specs.htm" target="_top">http://www.opengis.org/techno/specs.htm</a>.
- For information on the European Petroleum Survey Group (EPSG)
- and their database of spatial reference systems, see <a href="http://epsg.org" target="_top">http://epsg.org</a>.</p></dd><dt><span class="term">PROJ4TEXT</span></dt><dd><p>PostGIS uses the Proj4 library to provide coordinate
- transformation capabilities. The <tt class="varname">PROJ4TEXT</tt>
- column contains the Proj4 coordinate definition string for a
- particular SRID. For example:</p><pre class="programlisting">+proj=utm +zone=10 +ellps=clrk66 +datum=NAD27 +units=m</pre><p>For more information about, see the Proj4 web site at
- <a href="http://www.remotesensing.org/proj" target="_top">http://www.remotesensing.org/proj</a>.
- The <tt class="filename">spatial_ref_sys.sql</tt> file contains both
- <tt class="varname">SRTEXT</tt> and <tt class="varname">PROJ4TEXT</tt>
- definitions for all EPSG projections.</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2650620"></a>4.2.2. The GEOMETRY_COLUMNS Table</h3></div></div><div></div></div><p>The <tt class="varname">GEOMETRY_COLUMNS</tt> table definition is as
- follows:</p><pre class="programlisting">CREATE TABLE GEOMETRY_COLUMNS (
- F_TABLE_CATALOG VARCHAR(256) NOT NULL,
- F_TABLE_SCHEMA VARCHAR(256) NOT NULL,
- F_TABLE_NAME VARCHAR(256) NOT NULL,
- F_GEOMETRY_COLUMN VARCHAR(256) NOT NULL,
- COORD_DIMENSION INTEGER NOT NULL,
- SRID INTEGER NOT NULL,
- TYPE VARCHAR(30) NOT NULL
-)</pre><p>The columns are as follows:</p><div class="variablelist"><dl><dt><span class="term">F_TABLE_CATALOG, F_TABLE_SCHEMA, F_TABLE_NAME</span></dt><dd><p>The fully qualified name of the feature table containing
- the geometry column. Note that the terms "catalog" and "schema"
- are Oracle-ish. There is not PostgreSQL analogue of "catalog" so
- that column is left blank -- for "schema" the PostgreSQL schema
- name is used (<tt class="varname">public</tt> is the default).</p></dd><dt><span class="term">F_GEOMETRY_COLUMN</span></dt><dd><p>The name of the geometry column in the feature
- table.</p></dd><dt><span class="term">COORD_DIMENSION</span></dt><dd><p>The spatial dimension (2, 3 or 4 dimensional) of the
- column.</p></dd><dt><span class="term">SRID</span></dt><dd><p>The ID of the spatial reference system used for the
- coordinate geometry in this table. It is a foreign key reference
- to the <tt class="varname">SPATIAL_REF_SYS</tt>.</p></dd><dt><span class="term">TYPE</span></dt><dd><p>The type of the spatial object. To restrict the spatial
- column to a single type, use one of: POINT, LINESTRING, POLYGON,
- MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, GEOMETRYCOLLECTION or
- corresponding XYM versions POINTM, LINESTRINGM, POLYGONM,
- MULTIPOINTM, MULTILINESTRINGM, MULTIPOLYGONM, GEOMETRYCOLLECTIONM.
- For heterogeneous (mixed-type) collections, you can use
- "GEOMETRY" as the type.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>This attribute is (probably) not part of the OpenGIS
- specification, but is required for ensuring type
- homogeneity.</p></div></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2650754"></a>4.2.3. Creating a Spatial Table</h3></div></div><div></div></div><p>Creating a table with spatial data is done in two stages:</p><div class="itemizedlist"><ul type="disc"><li><p>Create a normal non-spatial table.</p><p>For example: <span><b class="command">CREATE TABLE ROADS_GEOM ( ID int4,
- NAME varchar(25) )</b></span></p></li><li><p>Add a spatial column to the table using the OpenGIS
- "AddGeometryColumn" function.</p><p>The syntax is:
- </p><pre class="programlisting">AddGeometryColumn(<schema_name>, <table_name>,
- <column_name>, <srid>, <type>,
- <dimension>)</pre><p>
-
- Or, using current schema:
- </p><pre class="programlisting">AddGeometryColumn(<table_name>,
- <column_name>, <srid>, <type>,
- <dimension>)</pre><p>
- </p><p>Example1: <span><b class="command">SELECT AddGeometryColumn('public',
- 'roads_geom', 'geom', 423, 'LINESTRING', 2)</b></span></p><p>Example2: <span><b class="command">SELECT AddGeometryColumn(
- 'roads_geom', 'geom', 423, 'LINESTRING', 2)</b></span></p></li></ul></div><p>Here is an example of SQL used to create a table and add a
- spatial column (assuming that an SRID of 128
- exists already):</p><pre class="programlisting">CREATE TABLE parks ( PARK_ID int4, PARK_NAME varchar(128), PARK_DATE date, PARK_TYPE varchar(2) );
-SELECT AddGeometryColumn('parks', 'park_geom', 128, 'MULTIPOLYGON', 2 );</pre><p>Here is another example, using the generic "geometry" type and
- the undefined SRID value of -1:</p><pre class="programlisting">CREATE TABLE roads ( ROAD_ID int4, ROAD_NAME varchar(128) );
-SELECT AddGeometryColumn( 'roads', 'roads_geom', -1, 'GEOMETRY', 3 );</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2650861"></a>4.2.4. Ensuring OpenGIS compliancy of geometries</h3></div></div><div></div></div><p>Most of the functions implemented by the GEOS library
- rely on the assumption that your geometries are valid
- as specified by the OpenGIS Simple Feature Specification.
- To check validity of geometries you can use the
- <a href="#IsValid">IsValid()</a> function:</p><pre class="programlisting">gisdb=# select isvalid('LINESTRING(0 0, 1 1)'), isvalid('LINESTRING(0 0,0 0)');
- isvalid | isvalid
----------+---------
- t | f</pre><p>By default, PostGIS does not apply this validity check on geometry input, because
- testing for validity needs lots of CPU time for complex geometries, especially polygons.
- If you do not trust your data sources, you can manually enforce such a check to your tables
- by adding a check constraint:</p><pre class="programlisting">ALTER TABLE mytable ADD CONSTRAINT geometry_valid_check CHECK (isvalid(the_geom));</pre><p>If you encounter any strange error messages such as "GEOS Intersection() threw an
- error!" or "JTS Intersection() threw an error!" when calling PostGIS functions with valid
- input geometries, you likely found an error in either PostGIS or one of the libraries it
- uses, and you should contact the PostGIS developers. The same is true if a PostGIS function returns
- an invalid geometry for valid input.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- Strictly compliant OGC geometries cannot have Z or M values.
- The <a href="#IsValid">IsValid()</a> function won't
- consider higher dimensioned geometries invalid! Invocations
- of <a href="#AddGeometryColumn">AddGeometryColumn()</a>
- will add a constraint checking geometry dimensions, so it is
- enough to specify 2 there.
- </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2650951"></a>4.3. Loading GIS Data</h2></div></div><div></div></div><p>Once you have created a spatial table, you are ready to upload GIS
- data to the database. Currently, there are two ways to get data into a
- PostGIS/PostgreSQL database: using formatted SQL statements or using the
- Shape file loader/dumper.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2650964"></a>4.3.1. Using SQL</h3></div></div><div></div></div><p>If you can convert your data to a text representation, then
- using formatted SQL might be the easiest way to get your data into
- PostGIS. As with Oracle and other SQL databases, data can be bulk
- loaded by piping a large text file full of SQL "INSERT" statements
- into the SQL terminal monitor.</p><p>A data upload file (<tt class="filename">roads.sql</tt> for example)
- might look like this:</p><pre class="programlisting">BEGIN;
-INSERT INTO ROADS_GEOM (ID,GEOM,NAME ) VALUES (1,GeomFromText('LINESTRING(191232 243118,191108 243242)',-1),'Jeff Rd');
-INSERT INTO ROADS_GEOM (ID,GEOM,NAME ) VALUES (2,GeomFromText('LINESTRING(189141 244158,189265 244817)',-1),'Geordie Rd');
-INSERT INTO ROADS_GEOM (ID,GEOM,NAME ) VALUES (3,GeomFromText('LINESTRING(192783 228138,192612 229814)',-1),'Paul St');
-INSERT INTO ROADS_GEOM (ID,GEOM,NAME ) VALUES (4,GeomFromText('LINESTRING(189412 252431,189631 259122)',-1),'Graeme Ave');
-INSERT INTO ROADS_GEOM (ID,GEOM,NAME ) VALUES (5,GeomFromText('LINESTRING(190131 224148,190871 228134)',-1),'Phil Tce');
-INSERT INTO ROADS_GEOM (ID,GEOM,NAME ) VALUES (6,GeomFromText('LINESTRING(198231 263418,198213 268322)',-1),'Dave Cres');
-COMMIT;</pre><p>The data file can be piped into PostgreSQL very easily using the
- "psql" SQL terminal monitor:</p><pre class="programlisting">psql -d [database] -f roads.sql</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2651020"></a>4.3.2. Using the Loader</h3></div></div><div></div></div><p>The <tt class="filename">shp2pgsql</tt> data loader converts ESRI
- Shape files into SQL suitable for insertion into a PostGIS/PostgreSQL
- database. The loader has several operating modes distinguished by
- command line flags:</p><div class="variablelist"><dl><dt><span class="term">-d</span></dt><dd><p>Drops the database table before creating a new table with
- the data in the Shape file.</p></dd><dt><span class="term">-a</span></dt><dd><p>Appends data from the Shape file into the database table.
- Note that to use this option to load multiple files, the files
- must have the same attributes and same data types.</p></dd><dt><span class="term">-c</span></dt><dd><p>Creates a new table and populates it from the Shape file.
- <span class="emphasis"><em>This is the default mode.</em></span></p></dd><dt><span class="term">-p</span></dt><dd><p>Only produces the table creation SQL code, without adding
- any actual data. This can be used if you need to completely
- separate the table creation and data loading steps.</p></dd><dt><span class="term">-D</span></dt><dd><p>Use the PostgreSQL "dump" format for the output data. This
- can be combined with -a, -c and -d. It is much faster to load
- than the default "insert" SQL format. Use this for very large data
- sets.</p></dd><dt><span class="term">-s <SRID></span></dt><dd><p>Creates and populates the geometry tables with the
- specified SRID.</p></dd><dt><span class="term">-k</span></dt><dd><p>Keep identifiers' case (column, schema and attributes). Note that attributes in Shapefile are all UPPERCASE.</p></dd><dt><span class="term">-i</span></dt><dd><p>Coerce all integers to standard 32-bit integers, do not
- create 64-bit bigints, even if the DBF header signature appears
- to warrant it.</p></dd><dt><span class="term">-I</span></dt><dd><p>Create a GiST index on the geometry column.</p></dd><dt><span class="term">-w</span></dt><dd><p>
- Output WKT format, for use with older (0.x) versions of PostGIS.
- Note that this will introduce coordinate drifts and will drop M
- values from shapefiles.
- </p></dd><dt><span class="term">-W <encoding></span></dt><dd><p>
-Specify encoding of the input data (dbf file).
-When used, all attributes of the dbf are converted from the specified
-encoding to UTF8. The resulting SQL output will contain a <tt class="code">SET
-CLIENT_ENCODING to UTF8</tt> command, so that the backend will be able
-to reconvert from UTF8 to whatever encoding the database is configured
-to use internally.
- </p></dd></dl></div><p>Note that -a, -c, -d and -p are mutually exclusive.</p><p>An example session using the loader to create an input file and
- uploading it might look like this:</p><pre class="programlisting"># shp2pgsql shaperoads myschema.roadstable > roads.sql
-# psql -d roadsdb -f roads.sql</pre><p>A conversion and upload can be done all in one step using UNIX
- pipes:</p><pre class="programlisting"># shp2pgsql shaperoads myschema.roadstable | psql -d roadsdb</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2651250"></a>4.4. Retrieving GIS Data</h2></div></div><div></div></div><p>Data can be extracted from the database using either SQL or the
- Shape file loader/dumper. In the section on SQL we will discuss some of
- the operators available to do comparisons and queries on spatial
- tables.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2651263"></a>4.4.1. Using SQL</h3></div></div><div></div></div><p>The most straightforward means of pulling data out of the
- database is to use a SQL select query and dump the resulting columns
- into a parsable text file:</p><pre class="programlisting">db=# SELECT id, AsText(geom) AS geom, name FROM ROADS_GEOM;
-id | geom | name
----+-----------------------------------------+-----------
- 1 | LINESTRING(191232 243118,191108 243242) | Jeff Rd
- 2 | LINESTRING(189141 244158,189265 244817) | Geordie Rd
- 3 | LINESTRING(192783 228138,192612 229814) | Paul St
- 4 | LINESTRING(189412 252431,189631 259122) | Graeme Ave
- 5 | LINESTRING(190131 224148,190871 228134) | Phil Tce
- 6 | LINESTRING(198231 263418,198213 268322) | Dave Cres
- 7 | LINESTRING(218421 284121,224123 241231) | Chris Way
-(6 rows)</pre><p>However, there will be times when some kind of restriction is
- necessary to cut down the number of fields returned. In the case of
- attribute-based restrictions, just use the same SQL syntax as normal
- with a non-spatial table. In the case of spatial restrictions, the
- following operators are available/useful:</p><div class="variablelist"><dl><dt><span class="term">&&</span></dt><dd><p>This operator tells whether the bounding box of one
- geometry intersects the bounding box of another.</p></dd><dt><span class="term">~=</span></dt><dd><p>This operators tests whether two geometries are
- geometrically identical. For example, if 'POLYGON((0 0,1 1,1 0,0
- 0))' is the same as 'POLYGON((0 0,1 1,1 0,0 0))' (it is).</p></dd><dt><span class="term">=</span></dt><dd><p>This operator is a little more naive, it only tests
- whether the bounding boxes of to geometries are the same.</p></dd></dl></div><p>Next, you can use these operators in queries. Note that when
- specifying geometries and boxes on the SQL command line, you must
- explicitly turn the string representations into geometries by using
- the "GeomFromText()" function. So, for example:</p><pre class="programlisting">SELECT
- ID, NAME
-FROM ROADS_GEOM
-WHERE
- GEOM ~= GeomFromText('LINESTRING(191232 243118,191108 243242)',-1);</pre><p>The above query would return the single record from the
- "ROADS_GEOM" table in which the geometry was equal to that
- value.</p><p>When using the "&&" operator, you can specify either a
- BOX3D as the comparison feature or a GEOMETRY. When you specify a
- GEOMETRY, however, its bounding box will be used for the
- comparison.</p><pre class="programlisting">SELECT
- ID, NAME
-FROM ROADS_GEOM
-WHERE
- GEOM && GeomFromText('POLYGON((191232 243117,191232 243119,191234 243117,191232 243117))',-1);</pre><p>The above query will use the bounding box of the polygon for
- comparison purposes.</p><p>The most common spatial query will probably be a "frame-based"
- query, used by client software, like data browsers and web mappers, to
- grab a "map frame" worth of data for display. Using a "BOX3D" object
- for the frame, such a query looks like this:</p><pre class="programlisting">SELECT
- AsText(GEOM) AS GEOM
-FROM ROADS_GEOM
-WHERE
- GEOM && SetSRID('BOX3D(191232 243117,191232 243119)'::box3d,-1);</pre><p>Note the use of the SRID, to specify the projection of the
- BOX3D. The value -1 is used to indicate no specified SRID.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2651429"></a>4.4.2. Using the Dumper</h3></div></div><div></div></div><p>The <tt class="filename">pgsql2shp</tt> table dumper connects
- directly to the database and converts a table (possibly defined by
- a query) into a shape file. The
- basic syntax is:</p><pre class="programlisting">pgsql2shp [<options>] <database> [<schema>.]<table></pre><pre class="programlisting">pgsql2shp [<options>] <database> <query></pre><p>The commandline options are:</p><div class="variablelist"><dl><dt><span class="term">-f <filename></span></dt><dd><p>Write the output to a particular filename.</p></dd><dt><span class="term">-h <host></span></dt><dd><p>The database host to connect to.</p></dd><dt><span class="term">-p <port></span></dt><dd><p>The port to connect to on the database host.</p></dd><dt><span class="term">-P <password></span></dt><dd><p>The password to use when connecting to the
- database.</p></dd><dt><span class="term">-u <user></span></dt><dd><p>The username to use when connecting to the
- database.</p></dd><dt><span class="term">-g <geometry column></span></dt><dd><p>In the case of tables with multiple geometry columns, the
- geometry column to use when writing the shape file.</p></dd><dt><span class="term">-b</span></dt><dd><p>Use a binary cursor. This will make the operation faster,
- but will not work if any NON-geometry attribute in the table
- lacks a cast to text.</p></dd><dt><span class="term">-r</span></dt><dd><p>Raw mode. Do not drop the <tt class="varname">gid</tt> field, or
- escape column names.</p></dd><dt><span class="term">-d</span></dt><dd><p>For backward compatibility: write a 3-dimensional shape
- file when dumping from old (pre-1.0.0) postgis databases (the
- default is to write a 2-dimensional shape file in that case).
- Starting from postgis-1.0.0+, dimensions are fully encoded.
- </p></dd></dl></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2651607"></a>4.5. Building Indexes</h2></div></div><div></div></div><p>Indexes are what make using a spatial database for large data sets
- possible. Without indexing, any search for a feature would require a
- "sequential scan" of every record in the database. Indexing speeds up
- searching by organizing the data into a search tree which can be quickly
- traversed to find a particular record. PostgreSQL supports three kinds
- of indexes by default: B-Tree indexes, R-Tree indexes, and GiST
- indexes.</p><div class="itemizedlist"><ul type="disc"><li><p>B-Trees are used for data which can be sorted along one axis;
- for example, numbers, letters, dates. GIS data cannot be rationally
- sorted along one axis (which is greater, (0,0) or (0,1) or (1,0)?)
- so B-Tree indexing is of no use for us.</p></li><li><p>R-Trees break up data into rectangles, and sub-rectangles, and
- sub-sub rectangles, etc. R-Trees are used by some spatial databases
- to index GIS data, but the PostgreSQL R-Tree implementation is not
- as robust as the GiST implementation.</p></li><li><p>GiST (Generalized Search Trees) indexes break up data into
- "things to one side", "things which overlap", "things which are
- inside" and can be used on a wide range of data-types, including GIS
- data. PostGIS uses an R-Tree index implemented on top of GiST to
- index GIS data.</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2651660"></a>4.5.1. GiST Indexes</h3></div></div><div></div></div><p>GiST stands for "Generalized Search Tree" and is a generic form
- of indexing. In addition to GIS indexing, GiST is used to speed up
- searches on all kinds of irregular data structures (integer arrays,
- spectral data, etc) which are not amenable to normal B-Tree
- indexing.</p><p>Once a GIS data table exceeds a few thousand rows, you will want
- to build an index to speed up spatial searches of the data (unless all
- your searches are based on attributes, in which case you'll want to
- build a normal index on the attribute fields).</p><p>The syntax for building a GiST index on a "geometry" column is
- as follows:</p><pre class="programlisting">CREATE INDEX [indexname] ON [tablename]
- USING GIST ( [geometryfield] GIST_GEOMETRY_OPS ); </pre><p>Building a spatial index is a computationally intensive
- exercise: on tables of around 1 million rows, on a 300MHz Solaris
- machine, we have found building a GiST index takes about 1 hour. After
- building an index, it is important to force PostgreSQL to collect
- table statistics, which are used to optimize query plans:</p><pre class="programlisting">VACUUM ANALYZE [table_name] [column_name];
-
--- This is only needed for PostgreSQL 7.4 installations and below
-SELECT UPDATE_GEOMETRY_STATS([table_name], [column_name]);</pre><p>GiST indexes have two advantages over R-Tree indexes in
- PostgreSQL. Firstly, GiST indexes are "null safe", meaning they can
- index columns which include null values. Secondly, GiST indexes
- support the concept of "lossiness" which is important when dealing
- with GIS objects larger than the PostgreSQL 8K page size. Lossiness
- allows PostgreSQL to store only the "important" part of an object in
- an index -- in the case of GIS objects, just the bounding box. GIS
- objects larger than 8K will cause R-Tree indexes to fail in the
- process of being built.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2651729"></a>4.5.2. Using Indexes</h3></div></div><div></div></div><p>Ordinarily, indexes invisibly speed up data access: once the
- index is built, the query planner transparently decides when to use
- index information to speed up a query plan. Unfortunately, the
- PostgreSQL query planner does not optimize the use of GiST indexes
- well, so sometimes searches which should use a spatial index instead
- default to a sequence scan of the whole table.</p><p>If you find your spatial indexes are not being used (or your
- attribute indexes, for that matter) there are a couple things you can
- do:</p><div class="itemizedlist"><ul type="disc"><li><p>Firstly, make sure statistics are gathered about the number
- and distributions of values in a table, to provide the query
- planner with better information to make decisions around index
- usage. For PostgreSQL 7.4 installations and below this is done by
- running <span><b class="command">update_geometry_stats([table_name,
- column_name])</b></span> (compute distribution) and <span><b class="command">VACUUM
- ANALYZE [table_name] [column_name]</b></span> (compute number of
- values). Starting with PostgreSQL 8.0 running <span><b class="command">VACUUM
- ANALYZE</b></span> will do both operations. You should regularly
- vacuum your databases anyways -- many PostgreSQL DBAs have
- <span><b class="command">VACUUM</b></span> run as an off-peak cron job on a regular
- basis.</p></li><li><p>If vacuuming does not work, you can force the planner to use
- the index information by using the <span><b class="command">SET
- ENABLE_SEQSCAN=OFF</b></span> command. You should only use this
- command sparingly, and only on spatially indexed queries:
- generally speaking, the planner knows better than you do about
- when to use normal B-Tree indexes. Once you have run your query,
- you should consider setting <tt class="varname">ENABLE_SEQSCAN</tt> back
- on, so that other queries will utilize the planner as
- normal.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>As of version 0.6, it should not be necessary to force the
- planner to use the index with
- <tt class="varname">ENABLE_SEQSCAN</tt>.</p></div></li><li><p>If you find the planner wrong about the cost of sequential
- vs index scans try reducing the value of random_page_cost in
- postgresql.conf or using SET random_page_cost=#. Default value for
- the parameter is 4, try setting it to 1 or 2. Decrementing the
- value makes the planner more inclined of using Index scans.</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2651847"></a>4.6. Complex Queries</h2></div></div><div></div></div><p>The <span class="emphasis"><em>raison d'etre</em></span> of spatial database
- functionality is performing queries inside the database which would
- ordinarily require desktop GIS functionality. Using PostGIS effectively
- requires knowing what spatial functions are available, and ensuring that
- appropriate indexes are in place to provide good performance.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2651866"></a>4.6.1. Taking Advantage of Indexes</h3></div></div><div></div></div><p>When constructing a query it is important to remember that only
- the bounding-box-based operators such as && can take advantage
- of the GiST spatial index. Functions such as
- <tt class="varname">distance()</tt> cannot use the index to optimize their
- operation. For example, the following query would be quite slow on a
- large table:</p><pre class="programlisting">SELECT the_geom FROM geom_table
-WHERE distance( the_geom, GeomFromText( 'POINT(100000 200000)', -1 ) ) < 100</pre><p>This query is selecting all the geometries in geom_table which
- are within 100 units of the point (100000, 200000). It will be slow
- because it is calculating the distance between each point in the table
- and our specified point, ie. one <tt class="varname">distance()</tt>
- calculation for each row in the table. We can avoid this by using the
- && operator to reduce the number of distance calculations
- required:</p><pre class="programlisting">SELECT the_geom FROM geom_table
-WHERE the_geom && 'BOX3D(90900 190900, 100100 200100)'::box3d
- AND distance( the_geom, GeomFromText( 'POINT(100000 200000)', -1 ) ) < 100</pre><p>This query selects the same geometries, but it does it in a more
- efficient way. Assuming there is a GiST index on the_geom, the query
- planner will recognize that it can use the index to reduce the number
- of rows before calculating the result of the
- <tt class="varname">distance()</tt> function. Notice that the
- <tt class="varname">BOX3D</tt> geometry which is used in the &&
- operation is a 200 unit square box centered on the original point -
- this is our "query box". The && operator uses the index to
- quickly reduce the result set down to only those geometries which have
- bounding boxes that overlap the "query box". Assuming that our query
- box is much smaller than the extents of the entire geometry table,
- this will drastically reduce the number of distance calculations that
- need to be done.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2651962"></a>4.6.2. Examples of Spatial SQL</h3></div></div><div></div></div><p>The examples in this section will make use of two tables, a
- table of linear roads, and a table of polygonal municipality
- boundaries. The table definitions for the <tt class="varname">bc_roads</tt>
- table is:</p><pre class="programlisting"> Column | Type | Description
-------------+-------------------+-------------------
- gid | integer | Unique ID
- name | character varying | Road Name
- the_geom | geometry | Location Geometry (Linestring)</pre><p>The table definition for the <tt class="varname">bc_municipality</tt>
- table is:</p><pre class="programlisting"> Column | Type | Description
------------+-------------------+-------------------
- gid | integer | Unique ID
- code | integer | Unique ID
- name | character varying | City / Town Name
- the_geom | geometry | Location Geometry (Polygon)</pre><div class="qandaset"><dl><dt>4.6.2.1. <a href="#id2652008">What is the total length of all roads, expressed in
- kilometers?</a></dt><dt>4.6.2.2. <a href="#id2652035">How large is the city of Prince George, in
- hectares?</a></dt><dt>4.6.2.3. <a href="#id2652064">What is the largest municipality in the province, by
- area?</a></dt><dt>4.6.2.4. <a href="#id2652106">What is the length of roads fully contained within each
- municipality?</a></dt><dt>4.6.2.5. <a href="#id2652168">Create a new table with all the roads within the city of
- Prince George.</a></dt><dt>4.6.2.6. <a href="#id2652207">What is the length in kilometers of "Douglas St" in
- Victoria?</a></dt><dt>4.6.2.7. <a href="#id2652241">What is the largest municipality polygon that has a
- hole?</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2652008"></a><a name="id2652010"></a><b>4.6.2.1.</b></td><td align="left" valign="top"><p>What is the total length of all roads, expressed in
- kilometers?</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>You can answer this question with a very simple piece of
- SQL:</p><pre class="programlisting">postgis=# SELECT sum(length(the_geom))/1000 AS km_roads FROM bc_roads;
- km_roads
-------------------
- 70842.1243039643
-(1 row)</pre></td></tr><tr class="question"><td align="left" valign="top"><a name="id2652035"></a><a name="id2652038"></a><b>4.6.2.2.</b></td><td align="left" valign="top"><p>How large is the city of Prince George, in
- hectares?</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>This query combines an attribute condition (on the
- municipality name) with a spatial calculation (of the
- area):</p><pre class="programlisting">postgis=# SELECT area(the_geom)/10000 AS hectares FROM bc_municipality
- WHERE name = 'PRINCE GEORGE';
- hectares
-------------------
- 32657.9103824927
-(1 row) </pre></td></tr><tr class="question"><td align="left" valign="top"><a name="id2652064"></a><a name="id2652066"></a><b>4.6.2.3.</b></td><td align="left" valign="top"><p>What is the largest municipality in the province, by
- area?</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>This query brings a spatial measurement into the query
- condition. There are several ways of approaching this problem,
- but the most efficient is below:</p><pre class="programlisting">postgis=# SELECT name, area(the_geom)/10000 AS hectares
- FROM bc_municipality
- ORDER BY hectares DESC
- LIMIT 1;
- name | hectares
----------------+-----------------
- TUMBLER RIDGE | 155020.02556131
-(1 row)</pre><p>Note that in order to answer this query we have to
- calculate the area of every polygon. If we were doing this a
- lot it would make sense to add an area column to the table
- that we could separately index for performance. By ordering
- the results in a descending direction, and them using the
- PostgreSQL "LIMIT" command we can easily pick off the largest
- value without using an aggregate function like max().</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2652106"></a><a name="id2652108"></a><b>4.6.2.4.</b></td><td align="left" valign="top"><p>What is the length of roads fully contained within each
- municipality?</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>This is an example of a "spatial join", because we are
- bringing together data from two tables (doing a join) but
- using a spatial interaction condition ("contained") as the
- join condition rather than the usual relational approach of
- joining on a common key:</p><pre class="programlisting">postgis=# SELECT m.name, sum(length(r.the_geom))/1000 as roads_km
- FROM bc_roads AS r,bc_municipality AS m
- WHERE r.the_geom && m.the_geom
- AND contains(m.the_geom,r.the_geom)
- GROUP BY m.name
- ORDER BY roads_km;
-
- name | roads_km
-----------------------------+------------------
- SURREY | 1539.47553551242
- VANCOUVER | 1450.33093486576
- LANGLEY DISTRICT | 833.793392535662
- BURNABY | 773.769091404338
- PRINCE GEORGE | 694.37554369147
- ...</pre><p>This query takes a while, because every road in the
- table is summarized into the final result (about 250K roads
- for our particular example table). For smaller overlays
- (several thousand records on several hundred) the response can
- be very fast.</p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2652168"></a><a name="id2652170"></a><b>4.6.2.5.</b></td><td align="left" valign="top"><p>Create a new table with all the roads within the city of
- Prince George.</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>This is an example of an "overlay", which takes in two
- tables and outputs a new table that consists of spatially
- clipped or cut resultants. Unlike the "spatial join"
- demonstrated above, this query actually creates new
- geometries. An overlay is like a turbo-charged spatial join,
- and is useful for more exact analysis work:</p><pre class="programlisting">postgis=# CREATE TABLE pg_roads as
- SELECT intersection(r.the_geom, m.the_geom) AS intersection_geom,
- length(r.the_geom) AS rd_orig_length,
- r.*
- FROM bc_roads AS r, bc_municipality AS m
- WHERE r.the_geom && m.the_geom
- AND intersects(r.the_geom, m.the_geom)
- AND m.name = 'PRINCE GEORGE';</pre></td></tr><tr class="question"><td align="left" valign="top"><a name="id2652207"></a><a name="id2652209"></a><b>4.6.2.6.</b></td><td align="left" valign="top"><p>What is the length in kilometers of "Douglas St" in
- Victoria?</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><pre class="programlisting">postgis=# SELECT sum(length(r.the_geom))/1000 AS kilometers
- FROM bc_roads r, bc_municipality m
- WHERE r.the_geom && m.the_geom
- AND r.name = 'Douglas St'
- AND m.name = 'VICTORIA';
- kilometers
-------------------
- 4.89151904172838
-(1 row)</pre></td></tr><tr class="question"><td align="left" valign="top"><a name="id2652241"></a><a name="id2652243"></a><b>4.6.2.7.</b></td><td align="left" valign="top"><p>What is the largest municipality polygon that has a
- hole?</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><pre class="programlisting">postgis=# SELECT gid, name, area(the_geom) AS area
- FROM bc_municipality
- WHERE nrings(the_geom) > 1
- ORDER BY area DESC LIMIT 1;
- gid | name | area
------+--------------+------------------
- 12 | SPALLUMCHEEN | 257374619.430216
-(1 row)</pre></td></tr></tbody></table></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2652277"></a>4.7. Using Mapserver</h2></div></div><div></div></div><p>The Minnesota Mapserver is an internet web-mapping server which
- conforms to the OpenGIS Web Mapping Server specification.</p><div class="itemizedlist"><ul type="disc"><li><p>The Mapserver homepage is at <a href="http://mapserver.gis.umn.edu" target="_top">http://mapserver.gis.umn.edu</a>.</p></li><li><p>The OpenGIS Web Map Specification is at <a href="http://www.opengis.org/techno/specs/01-047r2.pdf" target="_top">http://www.opengis.org/techno/specs/01-047r2.pdf</a>.</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2652320"></a>4.7.1. Basic Usage</h3></div></div><div></div></div><p>To use PostGIS with Mapserver, you will need to know about how
- to configure Mapserver, which is beyond the scope of this
- documentation. This section will cover specific PostGIS issues and
- configuration details.</p><p>To use PostGIS with Mapserver, you will need:</p><div class="itemizedlist"><ul type="disc"><li><p>Version 0.6 or newer of PostGIS.</p></li><li><p>Version 3.5 or newer of Mapserver.</p></li></ul></div><p>Mapserver accesses PostGIS/PostgreSQL data like any other
- PostgreSQL client -- using <tt class="filename">libpq</tt>. This means that
- Mapserver can be installed on any machine with network access to the
- PostGIS server, as long as the system has the
- <tt class="filename">libpq</tt> PostgreSQL client libraries.</p><div class="orderedlist"><ol type="1"><li><p>Compile and install Mapserver, with whatever options you
- desire, including the "--with-postgis" configuration
- option.</p></li><li><p>In your Mapserver map file, add a PostGIS layer. For
- example:</p><pre class="programlisting">LAYER
- CONNECTIONTYPE postgis
- NAME "widehighways"
- # Connect to a remote spatial database
- CONNECTION "user=dbuser dbname=gisdatabase host=bigserver"
- # Get the lines from the 'geom' column of the 'roads' table
- DATA "geom from roads"
- STATUS ON
- TYPE LINE
- # Of the lines in the extents, only render the wide highways
- FILTER "type = 'highway' and numlanes >= 4"
- CLASS
- # Make the superhighways brighter and 2 pixels wide
- EXPRESSION ([numlanes] >= 6)
- COLOR 255 22 22
- SYMBOL "solid"
- SIZE 2
- END
- CLASS
- # All the rest are darker and only 1 pixel wide
- EXPRESSION ([numlanes] < 6)
- COLOR 205 92 82
- END
-END</pre><p>In the example above, the PostGIS-specific directives are as
- follows:</p><div class="variablelist"><dl><dt><span class="term">CONNECTIONTYPE</span></dt><dd><p>For PostGIS layers, this is always "postgis".</p></dd><dt><span class="term">CONNECTION</span></dt><dd><p>The database connection is governed by the a
- 'connection string' which is a standard set of keys and
- values like this (with the default values in
- <>):</p><p>user=<username> password=<password>
- dbname=<username> hostname=<server>
- port=<5432></p><p>An empty connection string is still valid, and any of
- the key/value pairs can be omitted. At a minimum you will
- generally supply the database name and username to connect
- with.</p></dd><dt><span class="term">DATA</span></dt><dd><p>The form of this parameter is "<column> from
- <tablename>" where the column is the spatial column to
- be rendered to the map.</p></dd><dt><span class="term">FILTER</span></dt><dd><p>The filter must be a valid SQL string corresponding to
- the logic normally following the "WHERE" keyword in a SQL
- query. So, for example, to render only roads with 6 or more
- lanes, use a filter of "num_lanes >= 6".</p></dd></dl></div></li><li><p>In your spatial database, ensure you have spatial (GiST)
- indexes built for any the layers you will be drawing.</p><pre class="programlisting">CREATE INDEX [indexname]
- ON [tablename]
- USING GIST ( [geometrycolumn] GIST_GEOMETRY_OPS );</pre></li><li><p>If you will be querying your layers using Mapserver you will
- also need an "oid index".</p><p>Mapserver requires unique identifiers for each spatial
- record when doing queries, and the PostGIS module of Mapserver
- uses the PostgreSQL <tt class="varname">oid</tt> value to provide these
- unique identifiers. A side-effect of this is that in order to do
- fast random access of records during queries, an index on the
- <tt class="varname">oid</tt> is needed.</p><p>To build an "oid index", use the following SQL:</p><pre class="programlisting">CREATE INDEX [indexname] ON [tablename] ( oid );</pre></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2652568"></a>4.7.2. Frequently Asked Questions</h3></div></div><div></div></div><div class="qandaset"><dl><dt>4.7.2.1. <a href="#id2652576">When I use an EXPRESSION in my map
- file, the condition never returns as true, even though I know
- the values exist in my table.</a></dt><dt>4.7.2.2. <a href="#id2652610">The FILTER I use for my Shape files is not working for
- my PostGIS table of the same data.</a></dt><dt>4.7.2.3. <a href="#id2652639">My PostGIS layer draws much slower than my Shape file
- layer, is this normal?</a></dt><dt>4.7.2.4. <a href="#id2652677">My PostGIS layer draws fine, but queries are really
- slow. What is wrong?</a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id2652576"></a><a name="id2652578"></a><b>4.7.2.1.</b></td><td align="left" valign="top"><p>When I use an <tt class="varname">EXPRESSION</tt> in my map
- file, the condition never returns as true, even though I know
- the values exist in my table.</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>Unlike shape files, PostGIS field names have to be
- referenced in EXPRESSIONS using <span class="emphasis"><em>lower
- case</em></span>.</p><pre class="programlisting">EXPRESSION ([numlanes] >= 6)</pre></td></tr><tr class="question"><td align="left" valign="top"><a name="id2652610"></a><a name="id2652612"></a><b>4.7.2.2.</b></td><td align="left" valign="top"><p>The FILTER I use for my Shape files is not working for
- my PostGIS table of the same data.</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>Unlike shape files, filters for PostGIS layers use SQL
- syntax (they are appended to the SQL statement the PostGIS
- connector generates for drawing layers in Mapserver).</p><pre class="programlisting">FILTER "type = 'highway' and numlanes >= 4"</pre></td></tr><tr class="question"><td align="left" valign="top"><a name="id2652639"></a><a name="id2652641"></a><b>4.7.2.3.</b></td><td align="left" valign="top"><p>My PostGIS layer draws much slower than my Shape file
- layer, is this normal?</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>In general, expect PostGIS layers to be 10% slower than
- equivalent Shape files layers, due to the extra overhead
- involved in database connections, data transformations and
- data transit between the database and Mapserver.</p><p>If you are finding substantial draw performance
- problems, it is likely that you have not build a spatial index
- on your table.</p><pre class="programlisting">postgis# CREATE INDEX geotable_gix ON geotable USING GIST ( geocolumn );
-postgis# SELECT update_geometry_stats(); -- For PGSQL < 8.0
-postgis# VACUUM ANALYZE; -- For PGSQL >= 8.0</pre></td></tr><tr class="question"><td align="left" valign="top"><a name="id2652677"></a><a name="id2652679"></a><b>4.7.2.4.</b></td><td align="left" valign="top"><p>My PostGIS layer draws fine, but queries are really
- slow. What is wrong?</p></td></tr><tr class="answer"><td align="left" valign="top"><b></b></td><td align="left" valign="top"><p>For queries to be fast, you must have a unique key for
- your spatial table and you must have an index on that unique
- key.</p><p>You can specify what unique key for mapserver to use
- with the <tt class="varname">USING UNIQUE</tt> clause in your
- <tt class="varname">DATA</tt> line:</p><pre class="programlisting">DATA "the_geom FROM geotable USING UNIQUE gid"</pre><p>If your table does not have an explicit unique column,
- you can "fake" a unique column by using the PostgreSQL row
- "oid" for your unique column. "oid" is the default unique
- column if you do not declare one, so enhancing your query
- speed is a matter of building an index on your spatial table
- oid value.</p><pre class="programlisting">postgis# CREATE INDEX geotable_oid_idx ON geotable (oid);</pre></td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2652735"></a>4.7.3. Advanced Usage</h3></div></div><div></div></div><p>The <tt class="varname">USING</tt> pseudo-SQL clause is used to add
- some information to help mapserver understand the results of more
- complex queries. More specifically, when either a view or a subselect
- is used as the source table (the thing to the right of "FROM" in a
- <tt class="varname">DATA</tt> definition) it is more difficult for mapserver
- to automatically determine a unique identifier for each row and also
- the SRID for the table. The <tt class="varname">USING</tt> clause can
- provide mapserver with these two pieces of information as
- follows:</p><pre class="programlisting">DATA "the_geom FROM (SELECT table1.the_geom AS the_geom, table1.oid AS oid, table2.data AS data
- FROM table1 LEFT JOIN table2 ON table1.id = table2.id) AS new_table USING UNIQUE oid USING SRID=-1"</pre><div class="variablelist"><dl><dt><span class="term">USING UNIQUE <uniqueid></span></dt><dd><p>Mapserver requires a unique id for each row in order to
- identify the row when doing map queries. Normally, it would use
- the oid as the unique identifier, but views and subselects don't
- automatically have an oid column. If you want to use Mapserver's
- query functionality, you need to add a unique column to your
- view or subselect, and declare it with <tt class="varname">USING
- UNIQUE</tt>. For example, you could explicitly select one
- of the table's oid values for this purpose, or any other column
- which is guaranteed to be unique for the result set.</p><p>The <tt class="varname">USING</tt> statement can also be useful
- even for simple <tt class="varname">DATA</tt> statements, if you are
- doing map queries. It was previously recommended to add an index
- on the oid column of tables used in query-able layers, in order
- to speed up the performance of map queries. However, with the
- <tt class="varname">USING</tt> clause, it is possible to tell
- mapserver to use your table's primary key as the identifier for
- map queries, and then it is no longer necessary to have an
- additional index.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>"Querying a Map" is the action of clicking on a map to
- ask for information about the map features in that location.
- Don't confuse "map queries" with the SQL query in a
- <tt class="varname">DATA</tt> definition.</p></div></dd><dt><span class="term">USING SRID=<srid></span></dt><dd><p>PostGIS needs to know which spatial referencing system is
- being used by the geometries in order to return the correct data
- back to mapserver. Normally it is possible to find this
- information in the "geometry_columns" table in the PostGIS
- database, however, this is not possible for tables which are
- created on the fly such as subselects and views. So the
- <tt class="varname">USING SRID=</tt> option allows the correct SRID to
- be specified in the <tt class="varname">DATA</tt> definition.</p></dd></dl></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>The parser for Mapserver PostGIS layers is fairly primitive,
- and is case sensitive in a few areas. Be careful to ensure that all
- SQL keywords and all your <tt class="varname">USING</tt> clauses are in
- upper case, and that your <tt class="varname">USING UNIQUE</tt> clause
- precedes your <tt class="varname">USING SRID</tt> clause.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2580495"></a>4.7.4. Examples</h3></div></div><div></div></div><p>Lets start with a simple example and work our way up. Consider
- the following Mapserver layer definition:</p><pre class="programlisting">LAYER
- CONNECTIONTYPE postgis
- NAME "roads"
- CONNECTION "user=theuser password=thepass dbname=thedb host=theserver"
- DATA "the_geom FROM roads"
- STATUS ON
- TYPE LINE
- CLASS
- COLOR 0 0 0
- END
-END</pre><p>This layer will display all the road geometries in the roads
- table as black lines.</p><p>Now lets say we want to show only the highways until we get
- zoomed in to at least a 1:100000 scale - the next two layers will
- achieve this effect:</p><pre class="programlisting">LAYER
- CONNECTION "user=theuser password=thepass dbname=thedb host=theserver"
- DATA "the_geom FROM roads"
- MINSCALE 100000
- STATUS ON
- TYPE LINE
- FILTER "road_type = 'highway'"
- CLASS
- COLOR 0 0 0
- END
-END
-
-LAYER
- CONNECTION "user=theuser password=thepass dbname=thedb host=theserver"
- DATA "the_geom FROM roads"
- MAXSCALE 100000
- STATUS ON
- TYPE LINE
- CLASSITEM road_type
- CLASS
- EXPRESSION "highway"
- SIZE 2
- COLOR 255 0 0
- END
- CLASS
- COLOR 0 0 0
- END
-END</pre><p>The first layer is used when the scale is greater than 1:100000,
- and displays only the roads of type "highway" as black lines. The
- <tt class="varname">FILTER</tt> option causes only roads of type "highway"
- to be displayed.</p><p>The second layer is used when the scale is less than 1:100000,
- and will display highways as double-thick red lines, and other roads
- as regular black lines.</p><p>So, we have done a couple of interesting things using only
- mapserver functionality, but our <tt class="varname">DATA</tt> SQL statement
- has remained simple. Suppose that the name of the road is stored in
- another table (for whatever reason) and we need to do a join to get it
- and label our roads.</p><pre class="programlisting">LAYER
- CONNECTION "user=theuser password=thepass dbname=thedb host=theserver"
- DATA "the_geom FROM (SELECT roads.oid AS oid, roads.the_geom AS the_geom, road_names.name as name
- FROM roads LEFT JOIN road_names ON roads.road_name_id = road_names.road_name_id) AS named_roads
- USING UNIQUE oid USING SRID=-1"
- MAXSCALE 20000
- STATUS ON
- TYPE ANNOTATION
- LABELITEM name
- CLASS
- LABEL
- ANGLE auto
- SIZE 8
- COLOR 0 192 0
- TYPE truetype
- FONT arial
- END
- END
-END</pre><p>This annotation layer adds green labels to all the roads when
- the scale gets down to 1:20000 or less. It also demonstrates how to
- use an SQL join in a <tt class="varname">DATA</tt> definition.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2580593"></a>4.8. Java Clients (JDBC)</h2></div></div><div></div></div><p>Java clients can access PostGIS "geometry" objects in the
- PostgreSQL database either directly as text representations or using the
- JDBC extension objects bundled with PostGIS. In order to use the
- extension objects, the "postgis.jar" file must be in your CLASSPATH
- along with the "postgresql.jar" JDBC driver package.</p><pre class="programlisting">import java.sql.*;
-import java.util.*;
-import java.lang.*;
-import org.postgis.*;
-
-public class JavaGIS {
- public static void main(String[] args)
- {
- java.sql.Connection conn;
- try
- {
- /*
- * Load the JDBC driver and establish a connection.
- */
- Class.forName("org.postgresql.Driver");
- String url = "jdbc:postgresql://localhost:5432/database";
- conn = DriverManager.getConnection(url, "postgres", "");
-
- /*
- * Add the geometry types to the connection. Note that you
- * must cast the connection to the pgsql-specific connection * implementation before calling the addDataType() method.
- */
- ((org.postgresql.Connection)conn).addDataType("geometry","org.postgis.PGgeometry");
- ((org.postgresql.Connection)conn).addDataType("box3d","org.postgis.PGbox3d");
-
- /*
- * Create a statement and execute a select query.
- */
- Statement s = conn.createStatement();
- ResultSet r = s.executeQuery("select AsText(geom) as geom,id from geomtable");
- while( r.next() )
- {
- /*
- * Retrieve the geometry as an object then cast it to the geometry type.
- * Print things out.
- */
- PGgeometry geom = (PGgeometry)r.getObject(1);
- int id = r.getInt(2);
- System.out.println("Row " + id + ":");
- System.out.println(geom.toString());
- }
- s.close();
- conn.close();
- }
- catch( Exception e )
- {
- e.printStackTrace();
- }
- }
-}</pre><p>The "PGgeometry" object is a wrapper object which contains a
- specific topological geometry object (subclasses of the abstract class
- "Geometry") depending on the type: Point, LineString, Polygon,
- MultiPoint, MultiLineString, MultiPolygon.</p><pre class="programlisting">PGgeometry geom = (PGgeometry)r.getObject(1);
-if( geom.getType() = Geometry.POLYGON )
-{
- Polygon pl = (Polygon)geom.getGeometry();
- for( int r = 0; r < pl.numRings(); r++ )
- {
- LinearRing rng = pl.getRing(r);
- System.out.println("Ring: " + r);
- for( int p = 0; p < rng.numPoints(); p++ )
- {
- Point pt = rng.getPoint(p);
- System.out.println("Point: " + p);
- System.out.println(pt.toString());
- }
- }
-}</pre><p>The JavaDoc for the extension objects provides a reference for the
- various data accessor functions in the geometric objects.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2653210"></a>4.9. C Clients (libpq)</h2></div></div><div></div></div><p>...</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653219"></a>4.9.1. Text Cursors</h3></div></div><div></div></div><p>...</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653229"></a>4.9.2. Binary Cursors</h3></div></div><div></div></div><p>...</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2653241"></a>Chapter 5. Performance tips</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#id2653247">5.1. Small tables of large geometries</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2653253">5.1.1. Problem description</a></span></dt><dt><span class="sect2"><a href="#id2653305">5.1.2. Workarounds</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2653365">5.2. CLUSTERing on geometry indices</a></span></dt><dt><span class="sect1"><a href="#id2653421">5.3. Avoiding dimension conversion</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2653247"></a>5.1. Small tables of large geometries</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653253"></a>5.1.1. Problem description</h3></div></div><div></div></div><p>
-Current PostgreSQL versions (including 8.0) suffer from a query
-optimizer weakness regarding TOAST tables. TOAST tables are a kind of
-"extension room" used to store large (in the sense of data size) values
-that do not fit into normal data pages (like long texts, images or
-complex geometries with lots of vertices), see
-http://www.postgresql.org/docs/8.0/static/storage-toast.html for more
-information).
-</p><p>
-The problem appears if you happen to have a table with rather large
-geometries, but not too much rows of them (like a table containing the
-boundaries of all European countries in high resolution). Then the table
-itself is small, but it uses lots of TOAST space. In our example case,
-the table itself had about 80 rows and used only 3 data pages, but the
-TOAST table used 8225 pages.
-</p><p>
-Now issue a query where you use the geometry operator && to search for a
-bounding box that matches only very few of those rows. Now the query
-optimizer sees that the table has only 3 pages and 80 rows. He estimates
-that a sequential scan on such a small table is much faster than using
-an index. And so he decides to ignore the GIST index. Usually, this
-estimation is correct. But in our case, the && operator has to fetch
-every geometry from disk to compare the bounding boxes, thus reading all
-TOAST pages, too.
-</p><p>
-To see whether your suffer from this bug, use the "EXPLAIN ANALYZE"
-postgresql command. For more information and the technical details, you
-can read the thread on the postgres performance mailing list:
-http://archives.postgresql.org/pgsql-performance/2005-02/msg00030.php
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653305"></a>5.1.2. Workarounds</h3></div></div><div></div></div><p>
-The PostgreSQL people are trying to solve this issue by making the query
-estimation TOAST-aware. For now, here are two workarounds:
-</p><p>
-The first workaround is to force the query planner to use the index.
-Send "SET enable_seqscan TO off;" to the server before issuing the
-query. This basically forces the query planner to avoid sequential scans
-whenever possible. So it uses the GIST index as usual. But this flag has
-to be set on every connection, and it causes the query planner to make
-misestimations in other cases, so you should "SET enable_seqscan TO on;"
-after the query.
-</p><p>
-The second workaround is to make the sequential scan as fast as the
-query planner thinks. This can be achieved by creating an additional
-column that "caches" the bbox, and matching against this. In our
-example, the commands are like:
-</p><pre class="programlisting">
-SELECT addGeometryColumn('myschema','mytable','bbox','4326','GEOMETRY','2');
-
-UPDATE mytable set bbox = Envelope(Force_2d(the_geom));
-</pre><p>
-Now change your query to use the && operator against bbox instead of
-geom_column, like:
-</p><pre class="programlisting">
-SELECT geom_column FROM mytable WHERE bbox && SetSrid('BOX3D(0 0,1 1)'::box3d,4326);
-</pre><p>
-Of course, if you change or add rows to mytable, you have to keep the
-bbox "in sync". The most transparent way to do this would be triggers,
-but you also can modify your application to keep the bbox column current
-or run the UPDATE query above after every modification.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2653365"></a>5.2. CLUSTERing on geometry indices</h2></div></div><div></div></div><p>
-For tables that are mostly read-only, and where a single index is used for the
-majority of queries, PostgreSQL offers the CLUSTER command. This command
-physically reorders all the data rows in the same order as the index criteria,
-yielding two performance advantages: First, for index range scans, the number of
-seeks on the data table is drastically reduced. Second, if your working set
-concentrates to some small intervals on the indices, you have a more efficient
-caching because the data rows are spread along fewer data pages. (Feel invited
-to read the CLUSTER command documentation from the PostgreSQL manual at this
-point.)
-</p><p>
-However, currently PostgreSQL does not allow clustering on PostGIS GIST indices
-because GIST indices simply ignores NULL values, you get an error message like:
-</p><pre class="programlisting">
-lwgeom=# CLUSTER my_geom_index ON my_table;
-ERROR: cannot cluster when index access method does not handle null values
-HINT: You may be able to work around this by marking column "the_geom" NOT NULL.
-</pre><p>
-As the HINT message tells you, one can work around this deficiency by adding a
-"not null" constraint to the table:
-</p><pre class="programlisting">
-lwgeom=# ALTER TABLE my_table ALTER COLUMN the_geom SET not null;
-ALTER TABLE
-</pre><p>
-Of course, this will not work if you in fact need NULL values in your geometry
-column. Additionally, you must use the above method to add the constraint, using
-a CHECK constraint like "ALTER TABLE blubb ADD CHECK (geometry is not null);" will
-not work.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2653421"></a>5.3. Avoiding dimension conversion</h2></div></div><div></div></div><p>
-Sometimes, you happen to have 3D or 4D data in your table, but always access
-it using OpenGIS compliant asText() or asBinary() functions that only output
-2D geometries. They do this by internally calling the force_2d() function,
-which introduces a significant overhead for large geometries. To avoid this
-overhead, it may be feasible to pre-drop those additional dimensions once and
-forever:
-</p><pre class="programlisting">
-UPDATE mytable SET the_geom = force_2d(the_geom);
-VACUUM FULL ANALYZE mytable;
-</pre><p>
-Note that if you added your geometry column using AddGeometryColumn()
-there'll be a constraint on geometry dimension.
-To bypass it you will need to drop the constraint.
-Remember to update the entry in the geometry_columns table and
-recreate the constraint afterwards.
-</p><p>
-In case of large tables, it may be wise to divide this UPDATE into smaller portions
-by constraining the UPDATE to a part of the table via a WHERE clause and your
-primary key or another feasible criteria, and running a simple "VACUUM;" between
-your UPDATEs. This drastically reduces the need for temporary disk space.
-Additionally, if you have mixed dimension geometries, restricting the UPDATE by "WHERE
-dimension(the_geom)>2" skips re-writing of geometries that already are in 2D.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2653471"></a>Chapter 6. PostGIS Reference</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#id2653484">6.1. OpenGIS Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2653490">6.1.1. Management Functions</a></span></dt><dt><span class="sect2"><a href="#id2653580">6.1.2. Geometry Relationship Functions</a></span></dt><dt><span class="sect2"><a href="#id2653956">6.1.3. Geometry Processing Functions</a></span></dt><dt><span class="sect2"><a href="#id2654282">6.1.4. Geometry Accessors</a></span></dt><dt><span class="sect2"><a href="#id2654768">6.1.5. Geometry Constructors</a></span></dt></dl></dd><dt><span class="sect1"><a href="#id2655371">6.2. Postgis Extensions</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2655376">6.2.1. Management Functions</a></span></dt><dt><span class="sect2"><a href="#id2655701">6.2.2. Operators</a></span></dt><dt><span class="sect2"><a href="#id2655909">6.2.3. Measurement Functions</a></span></dt><dt><span class="sect2"><a href="#id2656192">6.2.4. Geometry Outputs</a></span></dt><dt><span class="sect2"><a href="#id2656300">6.2.5. Geometry Constructors</a></span></dt><dt><span class="sect2"><a href="#id2656633">6.2.6. Geometry Editors</a></span></dt><dt><span class="sect2"><a href="#id2657229">6.2.7. Linear Referencing</a></span></dt><dt><span class="sect2"><a href="#id2657449">6.2.8. Misc</a></span></dt><dt><span class="sect2"><a href="#id2658447">6.2.9. Long Transactions support</a></span></dt></dl></dd></dl></div><p>The functions given below are the ones which a user of PostGIS is
- likely to need. There are other functions which are required support
- functions to the PostGIS objects which are not of use to a general
- user.</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2653484"></a>6.1. OpenGIS Functions</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653490"></a>6.1.1. Management Functions</h3></div></div><div></div></div><div class="variablelist"><dl><dt><a name="AddGeometryColumn"></a><span class="term">AddGeometryColumn(varchar, varchar, varchar, integer,
- varchar, integer)</span></dt><dd><p>Syntax: AddGeometryColumn(<schema_name>,
- <table_name>, <column_name>, <srid>,
- <type>, <dimension>). Adds a geometry column to an
- existing table of attributes. The <tt class="varname">schema_name</tt>
- is the name of the table schema (unused for pre-schema
- PostgreSQL installations). The <tt class="varname">srid</tt> must be
- an integer value reference to an entry in the SPATIAL_REF_SYS
- table. The <tt class="varname">type</tt> must be an uppercase string
- corresponding to the geometry type, eg, 'POLYGON' or
- 'MULTILINESTRING'.</p></dd><dt><span class="term">DropGeometryColumn(varchar, varchar, varchar)</span></dt><dd><p>Syntax: DropGeometryColumn(<schema_name>,
- <table_name>, <column_name>). Remove a geometry
- column from a spatial table. Note that schema_name will need to
- match the f_schema_name field of the table's row in the
- geometry_columns table.</p></dd><dt><span class="term">SetSRID(geometry, integer)</span></dt><dd><p>Set the SRID on a geometry to a particular integer value.
- Useful in constructing bounding boxes for queries.</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653580"></a>6.1.2. Geometry Relationship Functions</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">Distance(geometry, geometry)</span></dt><dd><p>Return the cartesian distance between two geometries in
- projected units.</p></dd><dt><span class="term">Equals(geometry, geometry)</span></dt><dd><p>Returns 1 (TRUE) if the given Geometries are
- "spatially equal". Use this for a 'better' answer than '='.
- equals('LINESTRING(0 0, 10 10)','LINESTRING(0 0, 5 5, 10 10)')
- is true.</p><p>Performed by the GEOS module</p><p>OGC SPEC s2.1.1.2</p></dd><dt><span class="term">Disjoint(geometry, geometry)</span></dt><dd><p>Returns 1 (TRUE) if the Geometries are "spatially disjoint".
- </p><p>Performed by the GEOS module</p><p>Do not call with a GeometryCollection as an
- argument</p><p>NOTE: this is the "allowable" version that returns a
- boolean, not an integer.</p><p>OGC SPEC s2.1.1.2 //s2.1.13.3 - a.Relate(b,
- 'FF*FF****')</p></dd><dt><span class="term">Intersects(geometry, geometry)</span></dt><dd><p>Returns 1 (TRUE) if the Geometries "spatially intersect".
- </p><p>Performed by the GEOS module</p><p>Do not call with a GeometryCollection as an
- argument</p><p>NOTE: this is the "allowable" version that returns a
- boolean, not an integer.</p><p>OGC SPEC s2.1.1.2 //s2.1.13.3 - Intersects(g1, g2 ) -->
- Not (Disjoint(g1, g2 ))</p></dd><dt><span class="term">Touches(geometry, geometry)</span></dt><dd><p>Returns 1 (TRUE) if the Geometries "spatially touch".
- </p><p>Performed by the GEOS module</p><p>Do not call with a GeometryCollection as an
- argument</p><p>NOTE: this is the "allowable" version that returns a
- boolean, not an integer.</p><p>OGC SPEC s2.1.1.2 // s2.1.13.3- a.Touches(b) -> (I(a)
- intersection I(b) = {empty set} ) and (a intersection b) not
- empty</p></dd><dt><span class="term">Crosses(geometry, geometry)</span></dt><dd><p>Returns 1 (TRUE) if the Geometries "spatially cross".
- </p><p>Performed by the GEOS module</p><p>Do not call with a GeometryCollection as an
- argument</p><p>NOTE: this is the "allowable" version that returns a
- boolean, not an integer.</p><p>OGC SPEC s2.1.1.2 // s2.1.13.3 - a.Relate(b,
- 'T*T******')</p></dd><dt><span class="term">Within(geometry A, geometry B)</span></dt><dd><p>Returns 1 (TRUE) if Geometry A is "spatially within"
- Geometry B.</p><p>Performed by the GEOS module</p><p>Do not call with a GeometryCollection as an
- argument</p><p>NOTE: this is the "allowable" version that returns a
- boolean, not an integer.</p><p>OGC SPEC s2.1.1.2 // s2.1.13.3 - a.Relate(b,
- 'T*F**F***')</p></dd><dt><span class="term">Overlaps(geometry, geometry)</span></dt><dd><p>Returns 1 (TRUE) if the Geometries "spatially
- overlap".</p><p>Performed by the GEOS module</p><p>Do not call with a GeometryCollection as an
- argument</p><p>NOTE: this is the "allowable" version that returns a
- boolean, not an integer.</p><p>OGC SPEC s2.1.1.2 // s2.1.13.3</p></dd><dt><span class="term">Contains(geometry A, geometry B)</span></dt><dd><p>Returns 1 (TRUE) if Geometry A "spatially contains"
- Geometry B.</p><p>Performed by the GEOS module</p><p>Do not call with a GeometryCollection as an
- argument</p><p>NOTE: this is the "allowable" version that returns a
- boolean, not an integer.</p><p>OGC SPEC s2.1.1.2 // s2.1.13.3 - same as
- within(geometry B, geometry A)</p></dd><dt><span class="term">Intersects(geometry, geometry)</span></dt><dd><p>Returns 1 (TRUE) if the Geometries "spatially
- intersect".</p><p>Performed by the GEOS module</p><p>Do not call with a GeometryCollection as an
- argument</p><p>NOTE: this is the "allowable" version that returns a
- boolean, not an integer.</p><p>OGC SPEC s2.1.1.2 // s2.1.13.3 - NOT
- disjoint(geometry, geometry)</p></dd><dt><span class="term">Relate(geometry, geometry, intersectionPatternMatrix)</span></dt><dd><p>Returns 1 (TRUE) if this Geometry is spatially related to
- anotherGeometry, by testing for intersections between the
- Interior, Boundary and Exterior of the two geometries as
- specified by the values in the intersectionPatternMatrix.</p><p>Performed by the GEOS module</p><p>Do not call with a GeometryCollection as an
- argument</p><p>NOTE: this is the "allowable" version that returns a
- boolean, not an integer.</p><p>OGC SPEC s2.1.1.2 // s2.1.13.3</p></dd><dt><span class="term">Relate(geometry, geometry)</span></dt><dd><p>returns the DE-9IM (dimensionally extended
- nine-intersection matrix)</p><p>Performed by the GEOS module</p><p>Do not call with a GeometryCollection as an
- argument</p><p>not in OGC spec, but implied. see s2.1.13.2</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653956"></a>6.1.3. Geometry Processing Functions</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">Centroid(geometry)</span></dt><dd><p>Returns the centroid of the geometry as a point.</p><p>Computation will be more accurate if performed by the GEOS
- module (enabled at compile time).</p></dd><dt><span class="term">Area(geometry)</span></dt><dd><p>Returns the area of the geometry if it is a polygon or
- multi-polygon. </p></dd><dt><span class="term">Length(geometry)</span></dt><dd><p>The length of this Curve in its associated spatial
- reference.</p><p>synonym for length2d()</p><p>OGC SPEC 2.1.5.1</p></dd><dt><span class="term">PointOnSurface(geometry)</span></dt><dd><p>Return a Point guaranteed to lie on the surface</p><p>Implemented using GEOS</p><p>OGC SPEC 3.2.14.2 and 3.2.18.2 -</p></dd><dt><span class="term">Boundary(geometry)</span></dt><dd><p>Returns the closure of the combinatorial boundary of this
- Geometry. The combinatorial boundary is defined as described in
- section 3.12.3.2 of the OGC SPEC. Because the result of this
- function is a closure, and hence topologically closed, the
- resulting boundary can be represented using representational
- geometry primitives as discussed in the OGC SPEC, section
- 3.12.2.</p><p>Performed by the GEOS module</p><p>OGC SPEC s2.1.1.1</p></dd><dt><span class="term">Buffer(geometry, double, [integer])</span></dt><dd><p>Returns a geometry that represents all points whose
- distance from this Geometry is less than or equal to distance.
- Calculations are in the Spatial Reference System of this
- Geometry. The optional third parameter sets the
- number of segment used to approximate a quarter circle
- (defaults to 8).</p><p>Performed by the GEOS module</p><p>Do not call with a GeometryCollection as an
- argument</p><p>OGC SPEC s2.1.1.3</p></dd><dt><span class="term">ConvexHull(geometry)</span></dt><dd><p>Returns a geometry that represents the convex hull of this
- Geometry.</p><p>Performed by the GEOS module</p><p>OGC SPEC s2.1.1.3</p></dd><dt><span class="term">Intersection(geometry, geometry)</span></dt><dd><p>Returns a geometry that represents the point set
- intersection of the Geometies.</p><p>Performed by the GEOS module</p><p>Do not call with a GeometryCollection as an
- argument</p><p>OGC SPEC s2.1.1.3</p></dd><dt><span class="term">SymDifference(geometry A, geometry B)</span></dt><dd><p>Returns a geometry that represents the point set symmetric
- difference of Geometry A with Geometry B.</p><p>Performed by the GEOS module</p><p>Do not call with a GeometryCollection as an
- argument</p><p>OGC SPEC s2.1.1.3</p></dd><dt><span class="term">Difference(geometry A, geometry B)</span></dt><dd><p>Returns a geometry that represents the point set difference
- of Geometry A with Geometry B.</p><p>Performed by the GEOS module</p><p>Do not call with a GeometryCollection as an
- argument</p><p>OGC SPEC s2.1.1.3</p></dd><dt><span class="term">GeomUnion(geometry, geometry)</span></dt><dd><p>Returns a geometry that represents the point set union of
- the Geometries.</p><p>Performed by the GEOS module</p><p>Do not call with a GeometryCollection as an
- argument</p><p>NOTE: this is renamed from "union" because union is an SQL
- reserved word</p><p>OGC SPEC s2.1.1.3</p></dd><dt><span class="term">GeomUnion(geometry set)</span></dt><dd><p>Returns a geometry that represents the point set union of
- this all Geometries in given set.</p><p>Performed by the GEOS module</p><p>Do not call with a GeometryCollection in the argument
- set</p><p>Not explicitly defined in OGC SPEC</p></dd><dt><span class="term">MemGeomUnion(geometry set)</span></dt><dd><p>Same as the above, only memory-friendly (uses less memory
- and more processor time).</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654282"></a>6.1.4. Geometry Accessors</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">AsText(geometry)</span></dt><dd><p>Return the Well-Known Text representation of the geometry.
- For example: POLYGON(0 0,0 1,1 1,1 0,0 0)</p><p>OGC SPEC s2.1.1.1</p></dd><dt><span class="term">AsBinary(geometry)</span></dt><dd><p>Returns the geometry in the OGC "well-known-binary"
- format, using the endian encoding of the server on which the
- database is running. This is useful in binary cursors to pull
- data out of the database without converting it to a string
- representation.</p><p>OGC SPEC s2.1.1.1 - also see
- asBinary(<geometry>,'XDR') and
- asBinary(<geometry>,'NDR')</p></dd><dt><span class="term">SRID(geometry)</span></dt><dd><p>Returns the integer SRID number of the spatial reference
- system of the geometry.</p><p>OGC SPEC s2.1.1.1</p></dd><dt><span class="term">Dimension(geometry)</span></dt><dd><p>The inherent dimension of this Geometry object, which must
- be less than or equal to the coordinate dimension. OGC SPEC
- s2.1.1.1 - returns 0 for points, 1 for lines, 2 for polygons,
- and the largest dimension of the components of a
- GEOMETRYCOLLECTION.</p><pre class="programlisting">select dimension('GEOMETRYCOLLECTION(LINESTRING(1 1,0 0),POINT(0 0)');
-dimension
------------
-1</pre></dd><dt><span class="term">Envelope(geometry)</span></dt><dd><p>Returns a POLYGON representing the bounding box of the
- geometry.</p><p>OGC SPEC s2.1.1.1 - The minimum bounding box for this
- Geometry, returned as a Geometry. The polygon is defined by the
- corner points of the bounding box ((MINX, MINY), (MAXX, MINY),
- (MAXX, MAXY), (MINX, MAXY), (MINX, MINY)).</p><p>NOTE:PostGIS will add a Zmin/Zmax coordinate as
- well.</p></dd><dt><span class="term">IsEmpty(geometry)</span></dt><dd><p>Returns 1 (TRUE) if this Geometry is the empty geometry .
- If true, then this Geometry represents the empty point set -
- i.e. GEOMETRYCOLLECTION(EMPTY).</p><p>OGC SPEC s2.1.1.1</p></dd><dt><a name="IsSimple"></a><span class="term">IsSimple(geometry)</span></dt><dd><p>Returns 1 (TRUE) if this Geometry has no anomalous
- geometric points, such as self intersection or self
- tangency.</p><p>Performed by the GEOS module</p><p>OGC SPEC s2.1.1.1</p></dd><dt><a name="IsClosed"></a><span class="term">IsClosed(geometry)</span></dt><dd><p>Returns true of the geometry start and end points are
- coincident.</p></dd><dt><span class="term">IsRing(geometry)</span></dt><dd><p>Returns 1 (TRUE) if this Curve is closed (StartPoint ( ) =
- EndPoint ( )) and this Curve is simple (does not pass through
- the same point more than once).</p><p>performed by GEOS</p><p>OGC spec 2.1.5.1</p></dd><dt><span class="term">NumGeometries(geometry)</span></dt><dd><p>If geometry is a GEOMETRYCOLLECTION (or MULTI*) return the
- number of geometries, otherwise return NULL.</p></dd><dt><span class="term">GeometryN(geometry,int)</span></dt><dd><p>Return the N'th geometry if the geometry is a
- GEOMETRYCOLLECTION, MULTIPOINT, MULTILINESTRING or MULTIPOLYGON.
- Otherwise, return NULL.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- Index is 1-based as for OGC specs since version 0.8.0.
- Previous versions implemented this as 0-based instead.
- </p></div></dd><dt><span class="term">NumPoints(geometry)</span></dt><dd><p>Find and return the number of points in the first
- linestring in the geometry. Return NULL if there is no
- linestring in the geometry.</p></dd><dt><span class="term">PointN(geometry,integer)</span></dt><dd><p>Return the N'th point in the first linestring in the
- geometry. Return NULL if there is no linestring in the
- geometry.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- Index is 1-based as for OGC specs since version 0.8.0.
- Previous versions implemented this as 0-based instead.
- </p></div></dd><dt><span class="term">ExteriorRing(geometry)</span></dt><dd><p>Return the exterior ring of the polygon geometry.
- Return NULL if the geometry is not a polygon.</p></dd><dt><span class="term">NumInteriorRings(geometry)</span></dt><dd><p>Return the number of interior rings of the first polygon
- in the geometry. Return NULL if there is no polygon in the
- geometry.</p></dd><dt><span class="term">NumInteriorRing(geometry)</span></dt><dd><p>Synonym to NumInteriorRings(geometry). The OpenGIS specs
- are ambiguous about the exact function naming, so we provide
- both spellings.</p></dd><dt><span class="term">InteriorRingN(geometry,integer)</span></dt><dd><p>Return the N'th interior ring of the polygon geometry.
- Return NULL if the geometry is not a polygon or the given
- N is out of range.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- Index is 1-based as for OGC specs since version 0.8.0.
- Previous versions implemented this as 0-based instead.
- </p></div></dd><dt><span class="term">EndPoint(geometry)</span></dt><dd><p>Returns the last point of the LineString geometry as a point.</p></dd><dt><a name="StartPoint"></a><span class="term">StartPoint(geometry)</span></dt><dd><p>Returns the first point of the LineString geometry as a point.</p></dd><dt><a name="GeometryType"></a><span class="term">GeometryType(geometry)</span></dt><dd><p>Returns the type of the geometry as a string. Eg:
- 'LINESTRING', 'POLYGON', 'MULTIPOINT', etc.</p><p>OGC SPEC s2.1.1.1 - Returns the name of the instantiable
- subtype of Geometry of which this Geometry instance is a member.
- The name of the instantiable subtype of Geometry is returned as
- a string.</p></dd><dt><span class="term">X(geometry)</span></dt><dd><p>Return the X coordinate of the point.
- Input must be a point.</p></dd><dt><span class="term">Y(geometry)</span></dt><dd><p>Return the Y coordinate of the point.
- Input must be a point.</p></dd><dt><span class="term">Z(geometry)</span></dt><dd><p>Return the Z coordinate of the point,
- or NULL if not available.
- Input must be a point.</p></dd><dt><span class="term">M(geometry)</span></dt><dd><p>Return the M coordinate of the point,
- or NULL if not available.
- Input must be a point.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>This is not (yet) part of the OGC spec,
- but is listed here to complete the point coordinate
- extractor function list.</p></div></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654768"></a>6.1.5. Geometry Constructors</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">GeomFromText(text,[<srid>])</span></dt><dd><p>Makes a Geometry from WKT with the given SRID.</p><p>OGC SPEC 3.2.6.2 - option SRID is from the conformance
- suite</p></dd><dt><span class="term">PointFromText(text,[<srid>])</span></dt><dd><p>Makes a Geometry from WKT with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>OGC SPEC 3.2.6.2 - option SRID is from the conformance
- suite</p><p>Throws an error if the WKT is not a Point</p></dd><dt><span class="term">LineFromText(text,[<srid>])</span></dt><dd><p>Makes a Geometry from WKT with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>OGC SPEC 3.2.6.2 - option SRID is from the conformance
- suite</p><p>Throws an error if the WKT is not a Line</p></dd><dt><span class="term">LinestringFromText(text,[<srid>])</span></dt><dd><p>Makes a Geometry from WKT with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>from the conformance suite</p><p>Throws an error if the WKT is not a Line</p></dd><dt><span class="term">PolyFromText(text,[<srid>])</span></dt><dd><p>Makes a Geometry from WKT with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>OGC SPEC 3.2.6.2 - option SRID is from the conformance
- suite</p><p>Throws an error if the WKT is not a Polygon</p></dd><dt><span class="term">PolygonFromText(text,[<srid>])</span></dt><dd><p>Makes a Geometry from WKT with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>from the conformance suite</p><p>Throws an error if the WKT is not a Polygon</p></dd><dt><span class="term">MPointFromText(text,[<srid>])</span></dt><dd><p>Makes a Geometry from WKT with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>OGC SPEC 3.2.6.2 - option SRID is from the conformance
- suite</p><p>Throws an error if the WKT is not a MULTIPOINT</p></dd><dt><span class="term">MLineFromText(text,[<srid>])</span></dt><dd><p>Makes a Geometry from WKT with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>OGC SPEC 3.2.6.2 - option SRID is from the conformance
- suite</p><p>Throws an error if the WKT is not a MULTILINESTRING</p></dd><dt><span class="term">MPolyFromText(text,[<srid>])</span></dt><dd><p>Makes a Geometry from WKT with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>OGC SPEC 3.2.6.2 - option SRID is from the conformance
- suite</p><p>Throws an error if the WKT is not a MULTIPOLYGON</p></dd><dt><span class="term">GeomCollFromText(text,[<srid>])</span></dt><dd><p>Makes a Geometry from WKT with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>OGC SPEC 3.2.6.2 - option SRID is from the conformance
- suite</p><p>Throws an error if the WKT is not a
- GEOMETRYCOLLECTION</p></dd><dt><span class="term">GeomFromWKB(bytea,[<srid>])</span></dt><dd><p>Makes a Geometry from WKB with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>OGC SPEC 3.2.6.2 - option SRID is from the conformance
- suite</p></dd><dt><span class="term">GeomFromWKB(bytea,[<srid>])</span></dt><dd><p>Makes a Geometry from WKB with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>OGC SPEC 3.2.7.2 - option SRID is from the conformance
- suite</p></dd><dt><span class="term">PointFromWKB(bytea,[<srid>])</span></dt><dd><p>Makes a Geometry from WKB with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>OGC SPEC 3.2.7.2 - option SRID is from the conformance
- suite</p><p>throws an error if WKB is not a POINT</p></dd><dt><span class="term">LineFromWKB(bytea,[<srid>])</span></dt><dd><p>Makes a Geometry from WKB with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>OGC SPEC 3.2.7.2 - option SRID is from the conformance
- suite</p><p>throws an error if WKB is not a LINESTRING</p></dd><dt><span class="term">LinestringFromWKB(bytea,[<srid>])</span></dt><dd><p>Makes a Geometry from WKB with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>from the conformance suite</p><p>throws an error if WKB is not a LINESTRING</p></dd><dt><span class="term">PolyFromWKB(bytea,[<srid>])</span></dt><dd><p>Makes a Geometry from WKB with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>OGC SPEC 3.2.7.2 - option SRID is from the conformance
- suite</p><p>throws an error if WKB is not a POLYGON</p></dd><dt><span class="term">PolygonFromWKB(bytea,[<srid>])</span></dt><dd><p>Makes a Geometry from WKB with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>from the conformance suite</p><p>throws an error if WKB is not a POLYGON</p></dd><dt><span class="term">MPointFromWKB(bytea,[<srid>])</span></dt><dd><p>Makes a Geometry from WKB with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>OGC SPEC 3.2.7.2 - option SRID is from the conformance
- suite</p><p>throws an error if WKB is not a MULTIPOINT</p></dd><dt><span class="term">MLineFromWKB(bytea,[<srid>])</span></dt><dd><p>Makes a Geometry from WKB with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>OGC SPEC 3.2.7.2 - option SRID is from the conformance
- suite</p><p>throws an error if WKB is not a MULTILINESTRING</p></dd><dt><span class="term">MPolyFromWKB(bytea,[<srid>])</span></dt><dd><p>Makes a Geometry from WKB with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>OGC SPEC 3.2.7.2 - option SRID is from the conformance
- suite</p><p>throws an error if WKB is not a MULTIPOLYGON</p></dd><dt><span class="term">GeomCollFromWKB(bytea,[<srid>])</span></dt><dd><p>Makes a Geometry from WKB with the given SRID. If SRID is
- not give, it defaults to -1.</p><p>OGC SPEC 3.2.7.2 - option SRID is from the conformance
- suite</p><p>throws an error if WKB is not a GEOMETRYCOLLECTION</p></dd><dt><a name="BdPolyFromText"></a><span class="term">BdPolyFromText(text WKT, integer SRID)</span></dt><dd><p>
- Construct a Polygon given an arbitrary
- collection of closed linestrings as a
- MultiLineString text representation.
- </p><p>
- Throws an error if WKT is not a MULTILINESTRING.
- Throws an error if output is a MULTIPOLYGON; use <a href="#BdMPolyFromText">BdMPolyFromText</a> in
- that case, or see
- <a href="#BuildArea">BuildArea()</a>
- for a postgis-specific approach.
- </p><p>OGC SFSQL 1.1 - 3.2.6.2</p><p>
- Availability: 1.1.0 - requires GEOS >= 2.1.0.
- </p></dd><dt><a name="BdMPolyFromText"></a><span class="term">BdMPolyFromText(text WKT, integer SRID)</span></dt><dd><p>
- Construct a MultiPolygon given an arbitrary
- collection of closed linestrings as a
- MultiLineString text representation.
- </p><p>
- Throws an error if WKT is not a MULTILINESTRING.
- Forces MULTIPOLYGON output even when result is really
- only composed by a single POLYGON; use <a href="#BdPolyFromText">BdPolyFromText</a> if you're sure
- a single POLYGON will result from
- operation, or see
- <a href="#BuildArea">BuildArea()</a>
- for a postgis-specific approach.
- </p><p>OGC SFSQL 1.1 - 3.2.6.2</p><p>
- Availability: 1.1.0 - requires GEOS >= 2.1.0.
- </p></dd></dl></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2655371"></a>6.2. Postgis Extensions</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2655376"></a>6.2.1. Management Functions</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">DropGeometryTable([<schema_name>],
- <table_name>)</span></dt><dd><p>Drops a table and all its references in geometry_columns.
- Note: uses current_schema() on schema-aware pgsql installations if
- schema is not provided.</p></dd><dt><span class="term">UpdateGeometrySRID([<schema_name>],
- <table_name>, <column_name>, <srid>)</span></dt><dd><p>Update the SRID of all features in a geometry column updating constraints and reference in geometry_columns.
- Note: uses current_schema() on schema-aware pgsql installations if schema is not provided.</p></dd><dt><span class="term">update_geometry_stats([<table_name>,
- <column_name>])</span></dt><dd><p>Update statistics about spatial tables for use by the query
- planner. You will also need to run "VACUUM ANALYZE [table_name]
- [column_name]" for the statistics gathering process to be
- complete. NOTE: starting with PostgreSQL 8.0 statistics gathering
- is automatically performed running "VACUUM ANALYZE".</p></dd><dt><span class="term">postgis_version()</span></dt><dd><p>Returns PostGIS version number and compile-time options</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- Prior to version 1.1.0 this was a procedural function, thus possibly
- returning inaccurate information (in case of incomplete database upgrades).
- </p></div></dd><dt><a name="postgis_lib_version"></a><span class="term">postgis_lib_version()</span></dt><dd><p>Returns the version number of the PostGIS library.</p><p>
- Availability: 0.9.0
- </p></dd><dt><span class="term">postgis_lib_build_date()</span></dt><dd><p>Returns build date of the PostGIS library.</p><p>
- Availability: 1.0.0RC1
- </p></dd><dt><span class="term">postgis_script_build_date()</span></dt><dd><p>Returns build date of the PostGIS scripts.</p><p>
- Availability: 1.0.0RC1
- </p></dd><dt><span class="term">postgis_scripts_installed()</span></dt><dd><p>
- Returns version of the postgis scripts
- installed in this database.
- </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- If the output of this function doesn't match the output of
- <a href="#postgis_scripts_released">postgis_scripts_released()</a>
- you probably missed to properly upgrade an existing database.
- See the <a href="#upgrading" title="2.2.1. Upgrading">Upgrading</a> section for more info.
- </p></div><p>
- Availability: 0.9.0
- </p></dd><dt><a name="postgis_scripts_released"></a><span class="term">postgis_scripts_released()</span></dt><dd><p>Returns the version number of the lwpostgis.sql script
- released with the installed postgis lib.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- Starting with version 1.1.0 this function returns the same
- value of <a href="#postgis_lib_version">postgis_lib_version()</a>.
- Kept for backward compatibility.
- </p></div><p>
- Availability: 0.9.0
- </p></dd><dt><span class="term">postgis_geos_version()</span></dt><dd><p>Returns the version number of the GEOS library, or NULL if
- GEOS support is not enabled.</p><p>
- Availability: 0.9.0
- </p></dd><dt><span class="term">postgis_jts_version()</span></dt><dd><p>Returns the version number of the JTS library, or NULL if
- JTS support is not enabled.</p><p>
- Availability: 1.1.0
- </p></dd><dt><span class="term">postgis_proj_version()</span></dt><dd><p>Returns the version number of the PROJ4 library, or NULL if
- PROJ4 support is not enabled.</p><p>
- Availability: 0.9.0
- </p></dd><dt><span class="term">postgis_uses_stats()</span></dt><dd><p>Returns true if STATS usage has been enabled, false
- otherwise.</p><p>
- Availability: 0.9.0
- </p></dd><dt><a name="postgis_full_version"></a><span class="term">postgis_full_version()</span></dt><dd><p>Reports full postgis version and build configuration
- infos.</p><p>Availability: 0.9.0</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2655701"></a>6.2.2. Operators</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">A &< B</span></dt><dd><p>The "&<" operator returns true if A's bounding box
- overlaps or is to the left of B's bounding box.</p></dd><dt><span class="term">A &> B</span></dt><dd><p>The "&>" operator returns true if A's bounding box
- overlaps or is to the right of B's bounding box.</p></dd><dt><span class="term">A << B</span></dt><dd><p>The "<<" operator returns true if A's bounding box is
- strictly to the left of B's bounding box.</p></dd><dt><span class="term">A >> B</span></dt><dd><p>The ">>" operator returns true if A's bounding box is
- strictly to the right of B's bounding box.</p></dd><dt><span class="term">A &<| B</span></dt><dd><p>The "&<|" operator returns true if A's bounding box
- overlaps or is below B's bounding box.</p></dd><dt><span class="term">A |&> B</span></dt><dd><p>The "|&>" operator returns true if A's bounding box
- overlaps or is above B's bounding box.</p></dd><dt><span class="term">A <<| B</span></dt><dd><p>The "<<|" operator returns true if A's bounding box is
- strictly below B's bounding box.</p></dd><dt><span class="term">A |>> B</span></dt><dd><p>The "|>>" operator returns true if A's bounding box is
- strictly above B's bounding box.</p></dd><dt><span class="term">A ~= B</span></dt><dd><p>The "~=" operator is the "same as" operator. It tests actual
- geometric equality of two features. So if A and B are the same
- feature, vertex-by-vertex, the operator returns true.</p></dd><dt><span class="term">A @ B</span></dt><dd><p>The "@" operator returns true if A's bounding box is
- completely contained by B's bounding box.</p></dd><dt><span class="term">A ~ B</span></dt><dd><p>The "~" operator returns true if A's bounding box completely
- contains B's bounding box.</p></dd><dt><span class="term">A && B</span></dt><dd><p>The "&&" operator is the "overlaps" operator. If A's
- bounding box overlaps B's bounding box the operator returns
- true.</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2655909"></a>6.2.3. Measurement Functions</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">area2d(geometry)</span></dt><dd><p>Returns the area of the geometry if it is a polygon or
- multi-polygon.</p></dd><dt><span class="term">distance_sphere(point, point)</span></dt><dd><p>Returns linear distance in meters between two lat/lon
- points. Uses a spherical earth and radius of 6370986 meters.
- Faster than <a href="#distance_spheroid">distance_spheroid()</a>, but
- less accurate.
- Only implemented for points.</p></dd><dt><a name="distance_spheroid"></a><span class="term">distance_spheroid(point, point, spheroid)</span></dt><dd><p>Returns linear distance between two lat/lon points given a
- particular spheroid. See the explanation of spheroids given for
- <a href="#length_spheroid">length_spheroid()</a>.
- Currently only implemented for points.</p></dd><dt><a name="length2d"></a><span class="term">length2d(geometry)</span></dt><dd><p>Returns the 2-dimensional length of the geometry if it is a
- linestring or multi-linestring.</p></dd><dt><span class="term">length3d(geometry)</span></dt><dd><p>Returns the 3-dimensional length of the geometry if it is a
- linestring or multi-linestring.</p></dd><dt><a name="length_spheroid"></a><span class="term">length_spheroid(geometry,spheroid)</span></dt><dd><p>Calculates the length of of a geometry on an ellipsoid. This
- is useful if the coordinates of the geometry are in
- latitude/longitude and a length is desired without reprojection.
- The ellipsoid is a separate database type and can be constructed as
- follows:</p><div class="literallayout"><p>SPHEROID[<NAME>,<SEMI-MAJOR AXIS>,<INVERSE FLATTENING>]</p></div><p>Eg:</p><div class="literallayout"><p>SPHEROID["GRS_1980",6378137,298.257222101]</p></div><p>An example calculation might look like this:</p><div class="literallayout"><p>SELECT<br>
- length_spheroid(<br>
- geometry_column,<br>
- 'SPHEROID["GRS_1980",6378137,298.257222101]'<br>
- )<br>
-FROM geometry_table;</p></div></dd><dt><span class="term">length3d_spheroid(geometry,spheroid)</span></dt><dd><p>Calculates the length of of a geometry on an ellipsoid,
- taking the elevation into account. This is just like
- length_spheroid except vertical coordinates (expressed in the same
- units as the spheroid axes) are used to calculate the extra
- distance vertical displacement adds.</p></dd><dt><span class="term">distance(geometry, geometry)</span></dt><dd><p>Returns the smaller distance between two geometries.</p></dd><dt><span class="term">max_distance(linestring,linestring)</span></dt><dd><p>Returns the largest distance between two line
- strings.</p></dd><dt><span class="term">perimeter(geometry)</span></dt><dd><p>Returns the 2-dimensional perimeter of the geometry, if it
- is a polygon or multi-polygon.</p></dd><dt><span class="term">perimeter2d(geometry)</span></dt><dd><p>Returns the 2-dimensional perimeter of the geometry, if it
- is a polygon or multi-polygon.</p></dd><dt><span class="term">perimeter3d(geometry)</span></dt><dd><p>Returns the 3-dimensional perimeter of the geometry, if it
- is a polygon or multi-polygon.</p></dd><dt><span class="term">azimuth(geometry, geometry)</span></dt><dd><p>
- Returns the azimuth of the segment defined by the given Point
- geometries, or NULL if the two points are coincident.
- Return value is in radians.
- </p><p>
- Availability: 1.1.0
- </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2656192"></a>6.2.4. Geometry Outputs</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">AsBinary(geometry,{'NDR'|'XDR'})</span></dt><dd><p>Returns the geometry in the OGC "well-known-binary" format as a bytea, using little-endian (NDR) or big-endian (XDR) encoding. This is useful in binary cursors to pull data out of the database without converting it to a string representation.</p></dd><dt><span class="term">AsEWKT(geometry)</span></dt><dd><p>Returns a Geometry in EWKT format (as text).</p></dd><dt><span class="term">AsEWKB(geometry, {'NDR'|'XDR'})</span></dt><dd><p>Returns a Geometry in EWKB format (as bytea) using either little-endian (NDR) or big-endian (XDR) encoding.</p></dd><dt><span class="term">AsHEXEWKB(geometry, {'NDR'|'XDR'})</span></dt><dd><p>Returns a Geometry in HEXEWKB format (as text) using either little-endian (NDR) or big-endian (XDR) encoding.</p></dd><dt><span class="term">AsSVG(geometry, [rel], [precision])</span></dt><dd><p>Return the geometry as an SVG path data. Use 1 as second argument to have the path data implemented in terms of relative moves, the default (or 0) uses absolute moves. Third argument may be used to reduce the maximum number of decimal digits used in output (defaults to 15). Point geometries will be rendered as cx/cy when 'rel' arg is 0, x/y when 'rel' is 1.</p></dd><dt><span class="term">AsGML(geometry, [precision])</span></dt><dd><p>Return the geometry as a GML element. Second argument may be used to reduce the maximum number of significant digits used in output (defaults to 15).</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2656300"></a>6.2.5. Geometry Constructors</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">GeomFromEWKT(text)</span></dt><dd><p>Makes a Geometry from EWKT.</p></dd><dt><span class="term">GeomFromEWKB(bytea)</span></dt><dd><p>Makes a Geometry from EWKB.</p></dd><dt><span class="term">MakePoint(<x>, <y>, [<z>], [<m>])</span></dt><dd><p>Creates a 2d,3dz or 4d point geometry.</p></dd><dt><span class="term">MakePointM(<x>, <y>, <m>)</span></dt><dd><p>Creates a 3dm point geometry.</p></dd><dt><span class="term">MakeBox2D(<LL>, <UR>)</span></dt><dd><p>Creates a BOX2D defined by the given point geometries.</p></dd><dt><span class="term">MakeBox3D(<LLB>, <URT>)</span></dt><dd><p>Creates a BOX3D defined by the given point geometries.</p></dd><dt><span class="term">MakeLine(geometry set)</span></dt><dd><p>Creates a Linestring from a set of point geometries.
- You might want to use a subselect to order points before
- feeding them to this aggregate.</p></dd><dt><span class="term">MakeLine(geometry, geometry)</span></dt><dd><p>Creates a Linestring from the two given point
- geometries.</p></dd><dt><span class="term">LineFromMultiPoint(multipoint)</span></dt><dd><p>Creates a LineString from a MultiPoint geometry.</p></dd><dt><span class="term">MakePolygon(linestring, [linestring[]])</span></dt><dd><p>Creates a Polygon formed by the given
- shell and array of holes. You can construct
- a geometry array using <a href="#Accum">Accum</a>.
- Input geometries must be closed LINESTRINGS (see <a href="#IsClosed">IsClosed</a> and <a href="#GeometryType">GeometryType</a>).
- </p></dd><dt><a name="BuildArea"></a><span class="term">BuildArea(geometry)</span></dt><dd><p>Creates an areal geometry formed by the constituent
- linework of given geometry. The return type can
- be a Polygon or MultiPolygon, depending on input.
- If the input lineworks do not form polygons NULL is
- returned.
- </p><p>
- See also <a href="#BdPolyFromText">BdPolyFromText</a> and <a href="#BdMPolyFromText">BdMPolyFromText</a> - wrappers to this function with standard OGC interface.
- </p><p>
- Availability: 1.1.0 - requires GEOS >= 2.1.0.
- </p></dd><dt><span class="term">Polygonize(geometry set)</span></dt><dd><p>
- Aggregate. Creates a GeometryCollection containing
- possible polygons formed from the constituent linework
- of a set of geometries.
- </p><p>
- Availability: 1.0.0RC1 - requires GEOS >= 2.1.0.
- </p></dd><dt><span class="term">Collect(geometry set)</span></dt><dd><p>This function returns a GEOMETRYCOLLECTION or a MULTI object from a set
- of geometries. The collect() function is an "aggregate" function
- in the terminology of PostgreSQL. That means that it operators on
- lists of data, in the same way the sum() and mean() functions do.
- For example, "SELECT COLLECT(GEOM) FROM GEOMTABLE GROUP BY
- ATTRCOLUMN" will return a separate GEOMETRYCOLLECTION for each
- distinct value of ATTRCOLUMN.</p></dd><dt><span class="term">Collect(geometry, geometry)</span></dt><dd><p>This function returns a geometry being a collection
- of two input geometries. Output type can be a MULTI* or
- a GEOMETRYCOLLECTION.</p></dd><dt><span class="term">Dump(geometry)</span></dt><dd><p>This is a set-returning function (SRF).
- It returns a set of geometry_dump rows, formed
- by a geometry (geom) and an array of integers (path).
- When the input geometry is a simple type
- (POINT,LINESTRING,POLYGON)
- a single record will be returned with an empty
- path array and the input geometry as geom.
- When the input geometry is a collection or multi
- it will return a record for each of the collection
- components, and the path will express the position
- of the component inside the collection.
- </p><p>
- Availability: PostGIS 1.0.0RC1.
- Requires PostgreSQL 7.3 or higher.
- </p></dd><dt><span class="term">DumpRings(geometry)</span></dt><dd><p>This is a set-returning function (SRF).
- It returns a set of geometry_dump rows, formed
- by a geometry (geom) and an array of integers (path).
- The 'path' field holds the polygon ring index, contains
- a single element: 0 for the shell, hole number for holes.
- The 'geom' field contains the corresponding ring
- as a polygon.
- </p><p>
- Availability: PostGIS 1.1.3.
- Requires PostgreSQL 7.3 or higher.
- </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2656633"></a>6.2.6. Geometry Editors</h3></div></div><div></div></div><div class="variablelist"><dl><dt><a name="addbbox"></a><span class="term">AddBBOX(geometry)</span></dt><dd><p>Add bounding box to the geometry. This would make bounding
- box based queries faster, but will increase the size of the
- geometry.</p></dd><dt><a name="dropbbox"></a><span class="term">DropBBOX(geometry)</span></dt><dd><p>Drop the bounding box cache from the geometry.
- This reduces geometry size, but makes bounding-box based
- queries slower.</p></dd><dt><span class="term">AddPoint(linestring, point, [<position>])</span></dt><dd><p>Adds a point to a LineString before point <pos>
- (0-based index).
- Third parameter can be omitted or set to -1 for appending.
- </p></dd><dt><span class="term">RemovePoint(linestring, offset)</span></dt><dd><p>
- Removes point from a linestring. Offset is 0-based.
- </p><p>
- Availability: 1.1.0
- </p></dd><dt><span class="term">SetPoint(linestring, N, point)</span></dt><dd><p>
- Replace point N of linestring with given point.
- Index is 0-based.
- </p><p>
- Availability: 1.1.0
- </p></dd><dt><span class="term">Force_collection(geometry)</span></dt><dd><p>Converts the geometry into a GEOMETRYCOLLECTION. This is
- useful for simplifying the WKB representation.</p></dd><dt><a name="force_2d"></a><span class="term">Force_2d(geometry)</span></dt><dd><p>Forces the geometries into a "2-dimensional mode" so that
- all output representations will only have the X and Y coordinates.
- This is useful for force OGC-compliant output (since OGC only
- specifies 2-D geometries).</p></dd><dt><a name="force_3dz"></a><span class="term">Force_3dz(geometry), </span><span class="term">Force_3d(geometry), </span></dt><dd><p>Forces the geometries into XYZ mode.</p></dd><dt><a name="force_3dm"></a><span class="term">Force_3dm(geometry)</span></dt><dd><p>Forces the geometries into XYM mode.</p></dd><dt><a name="force_4d"></a><span class="term">Force_4d(geometry)</span></dt><dd><p>Forces the geometries into XYZM mode.</p></dd><dt><span class="term">Multi(geometry)</span></dt><dd><p>Returns the geometry as a MULTI* geometry. If the geometry
- is already a MULTI*, it is returned unchanged.</p></dd><dt><span class="term">Transform(geometry,integer)</span></dt><dd><p>Returns a new geometry with its coordinates transformed to
- the SRID referenced by the integer parameter. The destination SRID
- must exist in the <tt class="varname">SPATIAL_REF_SYS</tt> table.</p></dd><dt><span class="term">Affine(geometry,float8,float8,float8,float8,float8,float8,float8,float8,float8,float8,float8,float8)</span></dt><dd><p>Applies an 3d affine transformation to the geometry. The call
- </p><pre class="programlisting">
- Affine(geom, a, b, c, d, e, f, g, h, i, xoff, yoff, zoff)
- </pre><p>
- represents the transformation matrix
- </p><pre class="programlisting">
- / a b c xoff \
- | d e f yoff |
- | g h i zoff |
- \ 0 0 0 1 /
- </pre><p>
- and the vertices are transformed as follows:
- </p><pre class="programlisting">
- x' = a*x + b*y + c*z + xoff
- y' = d*x + e*y + f*z + yoff
- z' = g*x + h*y + i*z + zoff
- </pre><p>
- All of the translate / scale functions below are expressed via such an affine transformation.
- </p><p>
- Availability: 1.1.2.
- </p></dd><dt><span class="term">Affine(geometry,float8,float8,float8,float8,float8,float8)</span></dt><dd><p>Applies an 2d affine transformation to the geometry. The call
- </p><pre class="programlisting">
- Affine(geom, a, b, d, e, xoff, yoff)
- </pre><p>
- represents the transformation matrix
- </p><pre class="programlisting">
- / a b 0 xoff \ / a b xoff \
- | d e 0 yoff | rsp. | d e yoff |
- | 0 0 1 0 | \ 0 0 1 /
- \ 0 0 0 1 /
- </pre><p>
- and the vertices are transformed as follows:
- </p><pre class="programlisting">
- x' = a*x + b*y + xoff
- y' = d*x + e*y + yoff
- z' = z
- </pre><p>
- This method is a subcase of the 3D method above.
- </p><p>
- Availability: 1.1.2.
- </p></dd><dt><span class="term">Translate(geometry,float8,float8,float8)</span></dt><dd><p>Translates the geometry to a new location using the numeric
- parameters as offsets. Ie: translate(geom, X, Y, Z).</p></dd><dt><span class="term">Scale(geometry,float8,float8,float8)</span></dt><dd><p>scales the geometry to a new size by multiplying the
- ordinates with the parameters. Ie: scale(geom, Xfactor, Yfactor, Zfactor).</p><p>
- Availability: 1.1.0
- </p></dd><dt><a name="Rotate"></a><span class="term">RotateZ(geometry,float8), </span><span class="term">RotateX(geometry,float8), </span><span class="term">RotateY(geometry,float8), </span></dt><dd><p>
- Rotate the geometry around the Z, X or Y axis by
- the given angle given in radians. Follows the
- right-hand rule. This is the same in
- PostScript but opposite of SVG.
- </p><p>
- Availability: 1.1.2.
- </p></dd><dt><span class="term">TransScale(geometry,float8,float8,float8,float8)</span></dt><dd><p>First, translates the geometry using the first two floats, then scales it
- using the second two floats, working in 2D only. Using
- <tt class="code">transscale(geom, X, Y, XFactor, YFactor)</tt> internally calls
- <tt class="code">affine(geom, XFactor, 0, 0, 0, YFactor, 0, 0, 0, 1, X*XFactor, Y*YFactor, 0)</tt>.
- </p><p>
- Availability: 1.1.0.
- </p></dd><dt><span class="term">Reverse(geometry)</span></dt><dd><p>Returns the geometry with vertex order reversed.</p></dd><dt><span class="term">ForceRHR(geometry)</span></dt><dd><p>Force polygons of the collection to obey Right-Hand-Rule.</p></dd><dt><span class="term">Simplify(geometry, tolerance)</span></dt><dd><p>Returns a "simplified" version of the given geometry using
- the Douglas-Peuker algorithm. Will actually do something only with
- (multi)lines and (multi)polygons but you can safely call it with
- any kind of geometry. Since simplification occurs on a
- object-by-object basis you can also feed a GeometryCollection to
- this function. Note that returned geometry might loose its
- simplicity (see <a href="#IsSimple">IsSimple</a>)</p></dd><dt><span class="term">SnapToGrid(geometry, originX, originY, sizeX, sizeY), </span><span class="term">SnapToGrid(geometry, sizeX, sizeY), </span><span class="term">SnapToGrid(geometry, size), </span></dt><dd><p>Snap all points of the input geometry to the grid
- defined by its origin and cell size.
- Remove consecutive points falling on the same cell,
- eventually returning NULL if output points are not
- enough to define a geometry of the given type.
- Collapsed geometries in a collection are stripped
- from it.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- The returned geometry might loose its
- simplicity (see <a href="#IsSimple">IsSimple</a>).
- </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- Before release 1.1.0 this function always returned
- a 2d geometry. Starting at 1.1.0 the returned geometry
- will have same dimensionality as the input one with higher
- dimension values untouched. Use the version taking a second
- geometry argument to define all grid dimensions.
- </p></div><p>
- Availability: 1.0.0RC1
- </p></dd><dt><span class="term">SnapToGrid(geometry, geometry, sizeX, sizeY, sizeZ, sizeM)</span></dt><dd><p>
- Snap all points of the input geometry to the grid
- defined by its origin (the second argument, must be a point)
- and cell sizes. Specify 0 as size for any dimension you don't
- want to snap to a grid.
- </p><p>
- Availability: 1.1.0
- </p></dd><dt><span class="term">Segmentize(geometry, maxlength)</span></dt><dd><p>Return a modified geometry having no segment
- longer then the given distance. Interpolated points will have Z
- and M values (if needed) set to 0. Distance computation is
- performed in 2d only.</p></dd><dt><span class="term">LineMerge(geometry)</span></dt><dd><p>
- Returns a (set of) LineString(s) formed by sewing
- together constituent linework of input.
- </p><p>
- Availability: 1.1.0 - requires GEOS >= 2.1.0
- </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657229"></a>6.2.7. Linear Referencing</h3></div></div><div></div></div><div class="variablelist"><dl><dt><a name="line_interpolate_point"></a><span class="term">line_interpolate_point(linestring, location)</span></dt><dd><p>
- Returns a point interpolated along a line.
- First argument must be a LINESTRING.
- Second argument is a float8 between 0 and 1
- representing fraction of total
- <a href="#length2d">2d length</a> the point has
- to be located.
- </p><p>
- See <a href="#line_locate_point">line_locate_point()</a>
- for computing the line location nearest to a Point.
- </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- Since release 1.1.1 this function also interpolates
- M and Z values (when present), while prior releases
- set them to 0.0.
- </p></div><p>
- Availability: 0.8.2
- </p></dd><dt><a name="line_substring"></a><span class="term">line_substring(linestring, start, end)</span></dt><dd><p>
- Return a linestring being a substring of the input one starting
- and ending at the given fractions of total 2d length. Second
- and third arguments are float8 values between 0 and 1.
- </p><p>
- If 'start' and 'end' have the same value this is equivalent
- to <a href="#line_interpolate_point">line_interpolate_point()</a>.
- </p><p>
- See <a href="#line_locate_point">line_locate_point()</a>
- for computing the line location nearest to a Point.
- </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- Since release 1.1.1 this function also interpolates
- M and Z values (when present), while prior releases
- set them to unspecified values.
- </p></div><p>
- Availability: 1.1.0
- </p></dd><dt><a name="line_locate_point"></a><span class="term">line_locate_point(LineString, Point)</span></dt><dd><p>
- Returns a float between 0 and 1 representing
- the location of the closest point on LineString
- to the given Point, as a fraction of
- total <a href="#length2d">2d line</a> length.
- </p><p>
- You can use the returned location to extract a Point (<a href="#line_interpolate_point">line_interpolate_point</a>) or a substring (<a href="#line_substring">line_substring</a>).
- </p><p>
- Availability: 1.1.0
- </p></dd><dt><span class="term">locate_along_measure(geometry, float8)</span></dt><dd><p>
- Return a derived geometry collection value with elements that
- match the specified measure.
- Polygonal elements are not supported.
- </p><p>
- Semantic is specified by: ISO/IEC CD 13249-3:200x(E) -
- Text for Continuation CD Editing Meeting
- </p><p>
- Availability: 1.1.0
- </p></dd><dt><span class="term">locate_between_measures(geometry, float8, float8)</span></dt><dd><p>
- Return a derived geometry collection value with elements that
- match the specified range of measures inclusively.
- Polygonal elements are not supported.
- </p><p>
- Semantic is specified by: ISO/IEC CD 13249-3:200x(E) -
- Text for Continuation CD Editing Meeting
- </p><p>
- Availability: 1.1.0
- </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657449"></a>6.2.8. Misc</h3></div></div><div></div></div><div class="variablelist"><dl><dt><span class="term">Summary(geometry)</span></dt><dd><p>Returns a text summary of the contents of the geometry.</p></dd><dt><span class="term">box2d(geometry)</span></dt><dd><p>Returns a BOX2D representing the maximum extents of the geometry.</p></dd><dt><span class="term">box3d(geometry)</span></dt><dd><p>Returns a BOX3D representing the maximum extents of the geometry.</p></dd><dt><span class="term">extent(geometry set)</span></dt><dd><p>The extent() function is an "aggregate" function in the terminology of PostgreSQL. That means that it operators on lists of data, in the same way the sum() and mean() functions do. For example, "SELECT EXTENT(GEOM) FROM GEOMTABLE" will return a BOX3D giving the maximum extend of all features in the table. Similarly, "SELECT EXTENT(GEOM) FROM GEOMTABLE GROUP BY CATEGORY" will return one extent result for each category.</p></dd><dt><a name="zmflag"></a><span class="term">zmflag(geometry)</span></dt><dd><p>Returns ZM (dimension semantic) flag of the geometries as a small int. Values are: 0=2d, 1=3dm, 2=3dz, 3=4d. </p></dd><dt><a name="hasbbox"></a><span class="term">HasBBOX(geometry)</span></dt><dd><p>Returns TRUE if the bbox of this geometry is cached, FALSE otherwise. Use <a href="#addbbox">addBBOX()</a> and <a href="#dropbbox">dropBBOX()</a> to control caching.</p></dd><dt><a name="ndims"></a><span class="term">ndims(geometry)</span></dt><dd><p>Returns number of dimensions of the geometry as a small int. Values are: 2,3 or 4.</p></dd><dt><span class="term">nrings(geometry)</span></dt><dd><p>If the geometry is a polygon or multi-polygon returns the number of rings.</p></dd><dt><span class="term">npoints(geometry)</span></dt><dd><p>Returns the number of points in the geometry.</p></dd><dt><a name="IsValid"></a><span class="term">isvalid(geometry)</span></dt><dd><p>returns true if this geometry is valid.</p></dd><dt><span class="term">expand(geometry, float)</span></dt><dd><p>This function returns a bounding box expanded in all
- directions from the bounding box of the input geometry, by an
- amount specified in the second argument. Very useful for
- distance() queries, to add an index filter to the query.</p></dd><dt><span class="term">estimated_extent([schema], table, geocolumn)</span></dt><dd><p> Return the 'estimated' extent of the given spatial table. The estimated is taken from the geometry column's statistics. The current schema will be used if not specified.</p><p>For PostgreSQL>=8.0.0 statistics are gathered by VACUUM ANALYZE and resulting extent will be about 95% of the real one.</p><p>For PostgreSQL<8.0.0 statistics are gathered by update_geometry_stats() and resulting extent will be exact.</p></dd><dt><span class="term">find_srid(varchar,varchar,varchar)</span></dt><dd><p>The syntax is find_srid(<db/schema>, <table>,
- <column>) and the function returns the integer SRID of the
- specified column by searching through the GEOMETRY_COLUMNS table.
- If the geometry column has not been properly added with the
- AddGeometryColumns() function, this function will not work
- either.</p></dd><dt><span class="term">mem_size(geometry)</span></dt><dd><p>Returns the amount of space (in bytes) the geometry
- takes.</p></dd><dt><span class="term">numb_sub_objects(geometry)</span></dt><dd><p>Returns the number of objects stored in the geometry. This
- is useful for MULTI-geometries and GEOMETRYCOLLECTIONs.</p></dd><dt><span class="term">point_inside_circle(geometry,float,float,float)</span></dt><dd><p>The syntax for this functions is
- point_inside_circle(<geometry>,<circle_center_x>,<circle_center_y>,<radius>).
- Returns the true if the geometry is a point and is inside the
- circle. Returns false otherwise.</p></dd><dt><span class="term">xmin(box3d) ymin(box3d) zmin(box3d)</span></dt><dd><p>Returns the requested minima of a bounding box.</p></dd><dt><span class="term">xmax(box3d) ymax(box3d) zmax(box3d)</span></dt><dd><p>Returns the requested maxima of a bounding box.</p></dd><dt><a name="Accum"></a><span class="term">Accum(geometry set)</span></dt><dd><p>Aggregate. Constructs an array of geometries.</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2658447"></a>6.2.9. Long Transactions support</h3></div></div><div></div></div><p>
-This module and associated pl/pgsql functions have been implemented
-to provide long locking support required by
-<a href="https://portal.opengeospatial.org/files/?artifact_id=7176" target="_top">Web Feature Service</a> specification.
- </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- Users must use <a href="http://www.postgresql.org/docs/7.4/static/transaction-iso.html" target="_top">serializable transaction level</a> otherwise locking mechanism would break.
- </p></div><div class="variablelist"><dl><dt><a name="EnableLongTransactions"></a><span class="term">EnableLongTransactions()</span></dt><dd><p>
- Enable long transaction support. This function creates the
- required metadata tables, needs to be called once before
- using the other functions in this section. Calling it twice
- is harmless.
- </p><p>
- Availability: 1.1.3
- </p></dd><dt><a name="DisableLongTransactions"></a><span class="term">DisableLongTransactions()</span></dt><dd><p>
- Disable long transaction support. This function removes the
- long transaction support metadata tables, and drops all
- triggers attached to lock-checked tables.
- </p><p>
- Availability: 1.1.3
- </p></dd><dt><a name="CheckAuth"></a><span class="term">CheckAuth([<schema>], <table>, <rowid_col>)</span></dt><dd><p>
- Check updates and deletes of rows in
- given table for being authorized.
- Identify rows using <rowid_col> column.
- </p><p>
- Availability: 1.1.3
- </p></dd><dt><a name="LockRow"></a><span class="term">LockRow([<schema>], <table>, <rowid>, <authid>, [<expires>])</span></dt><dd><p>
- Set lock/authorization for specific row in table
- <authid> is a text value, <expires> is a timestamp
- defaulting to now()+1hour.
- Returns 1 if lock has been assigned, 0 otherwise
- (already locked by other auth)
- </p><p>
- Availability: 1.1.3
- </p></dd><dt><a name="UnlockRows"></a><span class="term">UnlockRows(<authid>)</span></dt><dd><p>
- Remove all locks held by specified authorization id.
- Returns the number of locks released.
- </p><p>
- Availability: 1.1.3
- </p></dd><dt><a name="AddAuth"></a><span class="term">AddAuth(<authid>)</span></dt><dd><p>
- Add an authorization token to be used in current
- transaction.
- </p><p>
- Availability: 1.1.3
- </p></dd></dl></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2658031"></a>Chapter 7. Reporting Bugs</h2></div></div><div></div></div><p>
- Reporting bugs effectively is a fundamental way to help PostGIS
- development. The most effective bug report is that enabling
- PostGIS developers to reproduce it, so it would ideally contain
- a script triggering it and every information regarding the
- environment in which it was detected. Good enough info can
- be extracted running <tt class="code">SELECT postgis_full_version()</tt>
- [for postgis] and <tt class="code">SELECT version()</tt> [for postgresql].
- </p><p>
- If you aren't using latest release, it's worth taking a look
- at its <a href="http://postgis.refractions.net/CHANGES.txt" target="_top">release
- changelog</a> first, to find out if your bug has already been
- fixed.
- </p><p>
- Using the <a href="http://postgis.refractions.net/bugs/" target="_top">PostGIS
- bug tracker</a> will ensure your reports are not discarded, and
- will keep you informed on it's handling process. Before reporting
- a new bug please query the database to see if it is a known one, and
- if it is please add any new information you have about it.
- </p><p>
- You might want to read Simon Tatham's paper about <a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html" target="_top">How
- to Report Bugs Effectively</a> before filing a new report.
- </p></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="release_notes"></a>Appendix A. Appendix</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#id2658101">A.1. Release Notes</a></span></dt><dd><dl><dt><span class="sect2"><a href="#id2658106">A.1.1. Release 1.1.4</a></span></dt><dt><span class="sect2"><a href="#id2658230">A.1.2. Release 1.1.3</a></span></dt><dt><span class="sect2"><a href="#id2658396">A.1.3. Release 1.1.2</a></span></dt><dt><span class="sect2"><a href="#id2658690">A.1.4. Release 1.1.1</a></span></dt><dt><span class="sect2"><a href="#id2658820">A.1.5. Release 1.1.0</a></span></dt><dt><span class="sect2"><a href="#id2659145">A.1.6. Release 1.0.6</a></span></dt><dt><span class="sect2"><a href="#id2659254">A.1.7. Release 1.0.5</a></span></dt><dt><span class="sect2"><a href="#id2659386">A.1.8. Release 1.0.4</a></span></dt><dt><span class="sect2"><a href="#rel_1.0.3_upgrading">A.1.9. Release 1.0.3</a></span></dt><dt><span class="sect2"><a href="#id2659632">A.1.10. Release 1.0.2</a></span></dt><dt><span class="sect2"><a href="#id2659711">A.1.11. Release 1.0.1</a></span></dt><dt><span class="sect2"><a href="#id2659811">A.1.12. Release 1.0.0</a></span></dt><dt><span class="sect2"><a href="#id2659910">A.1.13. Release 1.0.0RC6</a></span></dt><dt><span class="sect2"><a href="#id2659984">A.1.14. Release 1.0.0RC5</a></span></dt><dt><span class="sect2"><a href="#id2660056">A.1.15. Release 1.0.0RC4</a></span></dt><dt><span class="sect2"><a href="#id2660181">A.1.16. Release 1.0.0RC3</a></span></dt><dt><span class="sect2"><a href="#id2660352">A.1.17. Release 1.0.0RC2</a></span></dt><dt><span class="sect2"><a href="#id2660450">A.1.18. Release 1.0.0RC1</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2658101"></a>A.1. Release Notes</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2658106"></a>A.1.1. Release 1.1.4</h3></div></div><div></div></div><p>Release date: 2006/09/27</p><p>
-This is an bugfix release including some improvements in the Java interface.
-Upgrade is <span class="emphasis"><em>encouraged</em></span>.
- </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658124"></a>A.1.1.1. Upgrading</h4></div></div><div></div></div><p>
-If you are upgrading from release 1.0.3 or later follow the
-<a href="#soft_upgrade" title="2.2.1.1. Soft upgrade">soft upgrade</a> procedure.
- </p><p>
-If you are upgrading from a release <span class="emphasis"><em>between 1.0.0RC6 and
-1.0.2</em></span> (inclusive) and really want a live upgrade read the
-<a href="#rel_1.0.3_upgrading" title="A.1.9. Release 1.0.3">upgrade section</a> of the 1.0.3
-release notes chapter.
- </p><p>
-Upgrade from any release prior to 1.0.0RC6 requires an
-<a href="#hard_upgrade" title="2.2.1.2. Hard upgrade">hard upgrade</a>.
- </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658173"></a>A.1.1.2. Bug fixes</h4></div></div><div></div></div><p>
- Fixed support for PostgreSQL 8.2
- </p><p>
- Fixed bug in collect() function discarding SRID of
- input
- </p><p>
- Added SRID match check in MakeBox2d and MakeBox3d
- </p><p>
- Fixed regress tests to pass with GEOS-3.0.0
- </p><p>
- Improved pgsql2shp run concurrency.
- </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658201"></a>A.1.1.3. Java changes</h4></div></div><div></div></div><p>
- reworked JTS support to reflect new upstream
- JTS developers' attitude to SRID handling.
- Simplifies code and drops build depend on GNU trove.
- </p><p>
- Added EJB2 support generously donated by the
- "Geodetix s.r.l. Company" http://www.geodetix.it/
- </p><p>
- Added EJB3 tutorial / examples donated by
- Norman Barker <nbarker at ittvis.com>
- </p><p>
- Reorganized java directory layout a little.
- </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2658230"></a>A.1.2. Release 1.1.3</h3></div></div><div></div></div><p>Release date: 2006/06/30</p><p>
-This is an bugfix release including also some new functionalities (most notably long transaction support) and portability enhancements.
-Upgrade is <span class="emphasis"><em>encouraged</em></span>.
- </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658249"></a>A.1.2.1. Upgrading</h4></div></div><div></div></div><p>
-If you are upgrading from release 1.0.3 or later follow the
-<a href="#soft_upgrade" title="2.2.1.1. Soft upgrade">soft upgrade</a> procedure.
- </p><p>
-If you are upgrading from a release <span class="emphasis"><em>between 1.0.0RC6 and
-1.0.2</em></span> (inclusive) and really want a live upgrade read the
-<a href="#rel_1.0.3_upgrading" title="A.1.9. Release 1.0.3">upgrade section</a> of the 1.0.3
-release notes chapter.
- </p><p>
-Upgrade from any release prior to 1.0.0RC6 requires an
-<a href="#hard_upgrade" title="2.2.1.2. Hard upgrade">hard upgrade</a>.
- </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658295"></a>A.1.2.2. Bug fixes / correctness</h4></div></div><div></div></div><p> BUGFIX in distance(poly,poly) giving wrong results. </p><p> BUGFIX in pgsql2shp successful return code. </p><p> BUGFIX in shp2pgsql handling of MultiLine WKT. </p><p> BUGFIX in affine() failing to update bounding box. </p><p> WKT parser: forbidden construction of multigeometries with
- EMPTY elements (still supported for GEOMETRYCOLLECTION). </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658324"></a>A.1.2.3. New functionalities</h4></div></div><div></div></div><p> NEW Long Transactions support. </p><p> NEW DumpRings() function. </p><p> NEW AsHEXEWKB(geom, XDR|NDR) function. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658343"></a>A.1.2.4. JDBC changes</h4></div></div><div></div></div><p> Improved regression tests: MultiPoint and scientific ordinates </p><p> Fixed some minor bugs in jdbc code </p><p>
-Added proper accessor functions for all fields in preparation of
-making those fields private later
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658363"></a>A.1.2.5. Other changes</h4></div></div><div></div></div><p> NEW regress test support for loader/dumper. </p><p> Added --with-proj-libdir and --with-geos-libdir configure switches. </p><p> Support for build Tru64 build. </p><p> Use Jade for generating documentation. </p><p> Don't link pgsql2shp to more libs then required. </p><p> Initial support for PostgreSQL 8.2. </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2658396"></a>A.1.3. Release 1.1.2</h3></div></div><div></div></div><p>Release date: 2006/03/30</p><p>
-This is an bugfix release including some new functions and portability enhancements.
-Upgrade is <span class="emphasis"><em>encouraged</em></span>.
- </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658414"></a>A.1.3.1. Upgrading</h4></div></div><div></div></div><p>
-If you are upgrading from release 1.0.3 or later follow the
-<a href="#soft_upgrade" title="2.2.1.1. Soft upgrade">soft upgrade</a> procedure.
- </p><p>
-If you are upgrading from a release <span class="emphasis"><em>between 1.0.0RC6 and
-1.0.2</em></span> (inclusive) and really want a live upgrade read the
-<a href="#rel_1.0.3_upgrading" title="A.1.9. Release 1.0.3">upgrade section</a> of the 1.0.3
-release notes chapter.
- </p><p>
-Upgrade from any release prior to 1.0.0RC6 requires an
-<a href="#hard_upgrade" title="2.2.1.2. Hard upgrade">hard upgrade</a>.
- </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658623"></a>A.1.3.2. Bug fixes</h4></div></div><div></div></div><p>BUGFIX in SnapToGrid() computation of output bounding box</p><p>BUGFIX in EnforceRHR() </p><p>jdbc2 SRID handling fixes in JTS code</p><p>Fixed support for 64bit archs</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658646"></a>A.1.3.3. New functionalities</h4></div></div><div></div></div><p>Regress tests can now be run *before* postgis installation</p><p>New affine() matrix transformation functions</p><p>New rotate{,X,Y,Z}() function </p><p>Old translating and scaling functions now use affine() internally</p><p>Embedded access control in estimated_extent() for builds against pgsql >= 8.0.0</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658674"></a>A.1.3.4. Other changes</h4></div></div><div></div></div><p>More portable ./configure script</p><p>Changed ./run_test script to have more sane default behaviour</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2658690"></a>A.1.4. Release 1.1.1</h3></div></div><div></div></div><p>Release date: 2006/01/23</p><p>
-This is an important Bugfix release, upgrade is <span class="emphasis"><em>highly
-recommended</em></span>.
-Previous version contained a bug in postgis_restore.pl preventing
-<a href="#hard_upgrade" title="2.2.1.2. Hard upgrade">hard upgrade</a> procedure to complete
-and a bug in GEOS-2.2+ connector preventing GeometryCollection objects
-to be used in topological operations.
- </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658718"></a>A.1.4.1. Upgrading</h4></div></div><div></div></div><p>
-If you are upgrading from release 1.0.3 or later follow the
-<a href="#soft_upgrade" title="2.2.1.1. Soft upgrade">soft upgrade</a> procedure.
- </p><p>
-If you are upgrading from a release <span class="emphasis"><em>between 1.0.0RC6 and
-1.0.2</em></span> (inclusive) and really want a live upgrade read the
-<a href="#rel_1.0.3_upgrading" title="A.1.9. Release 1.0.3">upgrade section</a> of the 1.0.3
-release notes chapter.
- </p><p>
-Upgrade from any release prior to 1.0.0RC6 requires an
-<a href="#hard_upgrade" title="2.2.1.2. Hard upgrade">hard upgrade</a>.
- </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658765"></a>A.1.4.2. Bug fixes</h4></div></div><div></div></div><p>Fixed a premature exit in postgis_restore.pl </p><p>BUGFIX in geometrycollection handling of GEOS-CAPI connector</p><p>Solaris 2.7 and MingW support improvements</p><p>BUGFIX in line_locate_point()</p><p>Fixed handling of postgresql paths</p><p>BUGFIX in line_substring()</p><p>Added support for localized cluster in regress tester</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658800"></a>A.1.4.3. New functionalities</h4></div></div><div></div></div><p>New Z and M interpolation in line_substring()</p><p>New Z and M interpolation in line_interpolate_point()</p><p>added NumInteriorRing() alias due to OpenGIS ambiguity</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2658820"></a>A.1.5. Release 1.1.0</h3></div></div><div></div></div><p>Release date: 2005/12/21</p><p>
-This is a Minor release, containing many improvements and new things.
-Most notably: build procedure greatly simplified; transform() performance
-drastically improved; more stable GEOS connectivity (CAPI support);
-lots of new functions; draft topology support.
- </p><p>
-It is <span class="emphasis"><em>highly recommended</em></span> that you upgrade to GEOS-2.2.x
-before installing PostGIS, this will ensure future GEOS upgrades won't
-require a rebuild of the PostGIS library.
- </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658847"></a>A.1.5.1. Credits</h4></div></div><div></div></div><p>
-This release includes code from Mark Cave Ayland for caching of proj4
-objects. Markus Schaber added many improvements in his JDBC2 code.
-Alex Bodnaru helped with PostgreSQL source dependency relief and
-provided Debian specfiles. Michael Fuhr tested new things on Solaris arch.
-David Techer and Gerald Fenoy helped testing GEOS C-API connector.
-Hartmut Tschauner provided code for the azimuth() function.
-Devrim GUNDUZ provided RPM specfiles. Carl Anderson helped with
-the new area building functions.
-See the <a href="#credits" title="1.1. Credits">credits</a> section for more names.
- </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658874"></a>A.1.5.2. Upgrading</h4></div></div><div></div></div><p>
-If you are upgrading from release 1.0.3 or later you <span class="emphasis"><em>DO
-NOT</em></span> need a dump/reload.
-Simply sourcing the new lwpostgis_upgrade.sql script in all your
-existing databases will work.
-See the <a href="#soft_upgrade" title="2.2.1.1. Soft upgrade">soft upgrade</a> chapter
-for more information.
- </p><p>
-If you are upgrading from a release <span class="emphasis"><em>between 1.0.0RC6 and
-1.0.2</em></span> (inclusive) and really want a live upgrade read the
-<a href="#rel_1.0.3_upgrading" title="A.1.9. Release 1.0.3">upgrade section</a> of the 1.0.3
-release notes chapter.
- </p><p>
-Upgrade from any release prior to 1.0.0RC6 requires an
-<a href="#hard_upgrade" title="2.2.1.2. Hard upgrade">hard upgrade</a>.
- </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658927"></a>A.1.5.3. New functions</h4></div></div><div></div></div><p>scale() and transscale() companion methods to translate()</p><p>line_substring() </p><p>line_locate_point()</p><p>M(point) </p><p>LineMerge(geometry) </p><p>shift_longitude(geometry) </p><p>azimuth(geometry) </p><p>locate_along_measure(geometry, float8) </p><p>locate_between_measures(geometry, float8, float8) </p><p>SnapToGrid by point offset (up to 4d support)</p><p>BuildArea(any_geometry) </p><p>OGC BdPolyFromText(linestring_wkt, srid) </p><p>OGC BdMPolyFromText(linestring_wkt, srid)</p><p>RemovePoint(linestring, offset)</p><p>ReplacePoint(linestring, offset, point)</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2658991"></a>A.1.5.4. Bug fixes</h4></div></div><div></div></div><p>Fixed memory leak in polygonize()</p><p>Fixed bug in lwgeom_as_anytype cast functions</p><p>
-Fixed USE_GEOS, USE_PROJ and USE_STATS elements of postgis_version()
-output to always reflect library state.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659011"></a>A.1.5.5. Function semantic changes</h4></div></div><div></div></div><p>SnapToGrid doesn't discard higher dimensions</p><p>Changed Z() function to return NULL if requested dimension is not available</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659027"></a>A.1.5.6. Performance improvements</h4></div></div><div></div></div><p>
-Much faster transform() function, caching proj4 objects
-</p><p>
-Removed automatic call to fix_geometry_columns() in
-AddGeometryColumns() and update_geometry_stats()
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659043"></a>A.1.5.7. JDBC2 works</h4></div></div><div></div></div><p>Makefile improvements</p><p>JTS support improvements</p><p>Improved regression test system</p><p>Basic consistency check method for geometry collections</p><p>Support for (Hex)(E)wkb</p><p>Autoprobing DriverWrapper for HexWKB / EWKT switching</p><p>fix compile problems in ValueSetter for ancient jdk releases.</p><p>fix EWKT constructors to accept SRID=4711; representation</p><p>added preliminary read-only support for java2d geometries</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659086"></a>A.1.5.8. Other new things</h4></div></div><div></div></div><p>
-Full autoconf-based configuration, with PostgreSQL source dependency relief
-</p><p>GEOS C-API support (2.2.0 and higher)</p><p>Initial support for topology modelling</p><p>Debian and RPM specfiles</p><p>New lwpostgis_upgrade.sql script</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659113"></a>A.1.5.9. Other changes</h4></div></div><div></div></div><p>JTS support improvements</p><p>Stricter mapping between DBF and SQL integer and string attributes</p><p>Wider and cleaner regression test suite</p><p>old jdbc code removed from release</p><p>obsoleted direct use of postgis_proc_upgrade.pl</p><p>scripts version unified with release version</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2659145"></a>A.1.6. Release 1.0.6</h3></div></div><div></div></div><p>Release date: 2005/12/06</p><p>
-Contains a few bug fixes and improvements.
- </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659159"></a>A.1.6.1. Upgrading</h4></div></div><div></div></div><p>If you are upgrading from
- release 1.0.3 or later you <span class="emphasis"><em>DO
- NOT</em></span> need a dump/reload.
- </p><p>If you are upgrading from
- a release <span class="emphasis"><em>between 1.0.0RC6 and
- 1.0.2</em></span> (inclusive) and really want
- a live upgrade read the <a href="#rel_1.0.3_upgrading" title="A.1.9. Release 1.0.3">upgrade
- section</a> of the 1.0.3 release notes
- chapter.
- </p><p>
- Upgrade from any release prior to 1.0.0RC6
- requires an <a href="#hard_upgrade" title="2.2.1.2. Hard upgrade">hard
- upgrade</a>.
- </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659203"></a>A.1.6.2. Bug fixes</h4></div></div><div></div></div><p>Fixed palloc(0) call in collection deserializer (only gives problem with --enable-cassert)</p><p>Fixed bbox cache handling bugs</p><p>Fixed geom_accum(NULL, NULL) segfault</p><p>Fixed segfault in addPoint()</p><p>Fixed short-allocation in lwcollection_clone()</p><p>Fixed bug in segmentize()</p><p>Fixed bbox computation of SnapToGrid output</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659238"></a>A.1.6.3. Improvements</h4></div></div><div></div></div><p>Initial support for postgresql 8.2</p><p>Added missing SRID mismatch checks in GEOS ops</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2659254"></a>A.1.7. Release 1.0.5</h3></div></div><div></div></div><p>Release date: 2005/11/25</p><p>
-Contains memory-alignment fixes in the library, a segfault fix in loader's
-handling of UTF8 attributes and a few improvements and cleanups.
- </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-Return code of shp2pgsql changed from previous releases to conform to unix
-standards (return 0 on success).
- </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659275"></a>A.1.7.1. Upgrading</h4></div></div><div></div></div><p>If you are upgrading from
- release 1.0.3 or later you <span class="emphasis"><em>DO
- NOT</em></span> need a dump/reload.
- </p><p>If you are upgrading from
- a release <span class="emphasis"><em>between 1.0.0RC6 and
- 1.0.2</em></span> (inclusive) and really want
- a live upgrade read the <a href="#rel_1.0.3_upgrading" title="A.1.9. Release 1.0.3">upgrade
- section</a> of the 1.0.3 release notes
- chapter.
- </p><p>
- Upgrade from any release prior to 1.0.0RC6
- requires an <a href="#hard_upgrade" title="2.2.1.2. Hard upgrade">hard
- upgrade</a>.
- </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659319"></a>A.1.7.2. Library changes</h4></div></div><div></div></div><p>Fixed memory alignment problems</p><p>Fixed computation of null values fraction in analyzer</p><p>Fixed a small bug in the getPoint4d_p() low-level function</p><p>Speedup of serializer functions</p><p>Fixed a bug in force_3dm(), force_3dz() and force_4d()</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659346"></a>A.1.7.3. Loader changes</h4></div></div><div></div></div><p>Fixed return code of shp2pgsql</p><p>Fixed back-compatibility issue in loader (load of null shapefiles)</p><p>Fixed handling of trailing dots in dbf numerical attributes</p><p>Segfault fix in shp2pgsql (utf8 encoding)</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659369"></a>A.1.7.4. Other changes</h4></div></div><div></div></div><p>Schema aware postgis_proc_upgrade.pl, support for pgsql 7.2+</p><p>New "Reporting Bugs" chapter in manual</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2659386"></a>A.1.8. Release 1.0.4</h3></div></div><div></div></div><p>Release date: 2005/09/09</p><p>
-Contains important bug fixes and a few improvements. In particular, it
-fixes a memory leak preventing successful build of GiST indexes
-for large spatial tables.
- </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659401"></a>A.1.8.1. Upgrading</h4></div></div><div></div></div><p>If you are upgrading from
- release 1.0.3 you <span class="emphasis"><em>DO
- NOT</em></span> need a dump/reload.
- </p><p>If you are upgrading from
- a release <span class="emphasis"><em>between 1.0.0RC6 and
- 1.0.2</em></span> (inclusive) and really want
- a live upgrade read the <a href="#rel_1.0.3_upgrading" title="A.1.9. Release 1.0.3">upgrade
- section</a> of the 1.0.3 release notes
- chapter.
- </p><p>
- Upgrade from any release prior to 1.0.0RC6
- requires an <a href="#hard_upgrade" title="2.2.1.2. Hard upgrade">hard
- upgrade</a>.
- </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659445"></a>A.1.8.2. Bug fixes</h4></div></div><div></div></div><p>Memory leak plugged in GiST indexing</p><p>Segfault fix in transform() handling of proj4 errors</p><p>Fixed some proj4 texts in spatial_ref_sys (missing +proj)</p><p>Loader: fixed string functions usage, reworked NULL objects check, fixed segfault on MULTILINESTRING input.</p><p>Fixed bug in MakeLine dimension handling</p><p>Fixed bug in translate() corrupting output bounding box</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659477"></a>A.1.8.3. Improvements</h4></div></div><div></div></div><p>Documentation improvements</p><p>More robust selectivity estimator </p><p>Minor speedup in distance()</p><p>Minor cleanups </p><p>GiST indexing cleanup</p><p>Looser syntax acceptance in box3d parser</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="rel_1.0.3_upgrading"></a>A.1.9. Release 1.0.3</h3></div></div><div></div></div><p>Release date: 2005/08/08</p><p>
-Contains some bug fixes - <span class="emphasis"><em>including a severe one affecting
-correctness of stored geometries</em></span> - and a few improvements.
- </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659530"></a>A.1.9.1. Upgrading</h4></div></div><div></div></div><p>
-Due to a bug in a bounding box computation routine, the upgrade procedure
-requires special attention, as bounding boxes cached in the database could
-be incorrect.
- </p><p>
-An <a href="#hard_upgrade" title="2.2.1.2. Hard upgrade">hard upgrade</a> procedure (dump/reload)
-will force recomputation of all bounding boxes (not included in dumps).
-This is <span class="emphasis"><em>required</em></span> if upgrading from releases prior
-to 1.0.0RC6.
- </p><p>
-If you are upgrading from versions 1.0.0RC6 or up, this release includes a
-perl script (utils/rebuild_bbox_caches.pl) to force recomputation of
-geometries' bounding boxes and invoke all operations required to propagate
-eventual changes in them (geometry statistics update, reindexing).
-Invoke the script after a make install (run with no args for syntax help).
-Optionally run utils/postgis_proc_upgrade.pl to refresh postgis procedures
-and functions signatures (see <a href="#soft_upgrade" title="2.2.1.1. Soft upgrade">Soft upgrade</a>).
- </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659578"></a>A.1.9.2. Bug fixes</h4></div></div><div></div></div><p>Severe bugfix in lwgeom's 2d bounding box computation</p><p>Bugfix in WKT (-w) POINT handling in loader</p><p>Bugfix in dumper on 64bit machines</p><p>Bugfix in dumper handling of user-defined queries </p><p>Bugfix in create_undef.pl script</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659604"></a>A.1.9.3. Improvements</h4></div></div><div></div></div><p>Small performance improvement in canonical input function</p><p>Minor cleanups in loader</p><p>Support for multibyte field names in loader</p><p>Improvement in the postgis_restore.pl script</p><p>New rebuild_bbox_caches.pl util script</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2659632"></a>A.1.10. Release 1.0.2</h3></div></div><div></div></div><p>Release date: 2005/07/04</p><p>
- Contains a few bug fixes and improvements.
- </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659646"></a>A.1.10.1. Upgrading</h4></div></div><div></div></div><p>If you are upgrading from
- release 1.0.0RC6 or up you <span class="emphasis"><em>DO
- NOT</em></span> need a dump/reload.</p><p>Upgrading from older releases
- requires a dump/reload.
- See the <a href="#upgrading" title="2.2.1. Upgrading">upgrading</a>
- chapter for more informations.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659673"></a>A.1.10.2. Bug fixes</h4></div></div><div></div></div><p>Fault tolerant btree ops</p><p>Memory leak plugged in pg_error</p><p>Rtree index fix</p><p>Cleaner build scripts (avoided mix of CFLAGS and CXXFLAGS)</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659695"></a>A.1.10.3. Improvements</h4></div></div><div></div></div><p>New index creation capabilities in loader (-I switch)</p><p>Initial support for postgresql 8.1dev</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2659711"></a>A.1.11. Release 1.0.1</h3></div></div><div></div></div><p>Release date: 2005/05/24</p><p>
- Contains a few bug fixes and some improvements.
- </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659725"></a>A.1.11.1. Upgrading</h4></div></div><div></div></div><p>If you are upgrading from
- release 1.0.0RC6 or up you <span class="emphasis"><em>DO
- NOT</em></span> need a dump/reload.</p><p>Upgrading from older releases
- requires a dump/reload.
- See the <a href="#upgrading" title="2.2.1. Upgrading">upgrading</a>
- chapter for more informations.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659752"></a>A.1.11.2. Library changes</h4></div></div><div></div></div><p>BUGFIX in 3d computation of length_spheroid()</p><p>BUGFIX in join selectivity estimator</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659767"></a>A.1.11.3. Other changes/additions</h4></div></div><div></div></div><p>BUGFIX in shp2pgsql escape functions</p><p>better support for concurrent postgis in multiple schemas</p><p>documentation fixes</p><p>jdbc2: compile with "-target 1.2 -source 1.2" by default</p><p>NEW -k switch for pgsql2shp</p><p>NEW support for custom createdb options in postgis_restore.pl</p><p>BUGFIX in pgsql2shp attribute names unicity enforcement</p><p>BUGFIX in Paris projections definitions</p><p>postgis_restore.pl cleanups</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2659811"></a>A.1.12. Release 1.0.0</h3></div></div><div></div></div><p>Release date: 2005/04/19</p><p>Final 1.0.0 release.
- Contains a few bug fixes, some improvements
- in the loader (most notably support for older
- postgis versions), and more docs.
- </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659826"></a>A.1.12.1. Upgrading</h4></div></div><div></div></div><p>If you are upgrading from
- release 1.0.0RC6 you <span class="emphasis"><em>DO
- NOT</em></span> need a dump/reload.</p><p>Upgrading from any other precedent
- release requires a dump/reload.
- See the <a href="#upgrading" title="2.2.1. Upgrading">upgrading</a>
- chapter for more informations.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659853"></a>A.1.12.2. Library changes</h4></div></div><div></div></div><p>BUGFIX in transform() releasing random memory address</p><p>BUGFIX in force_3dm() allocating less memory then required</p><p>BUGFIX in join selectivity estimator (defaults, leaks, tuplecount, sd)</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659873"></a>A.1.12.3. Other changes/additions</h4></div></div><div></div></div><p>BUGFIX in shp2pgsql escape of values starting with tab or single-quote</p><p>NEW manual pages for loader/dumper</p><p>NEW shp2pgsql support for old (HWGEOM) postgis versions</p><p>NEW -p (prepare) flag for shp2pgsql</p><p>NEW manual chapter about OGC compliancy enforcement</p><p>NEW autoconf support for JTS lib</p><p>BUGFIX in estimator testers (support for LWGEOM and schema parsing)</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2659910"></a>A.1.13. Release 1.0.0RC6</h3></div></div><div></div></div><p>Release date: 2005/03/30</p><p>Sixth release candidate for 1.0.0.
- Contains a few bug fixes and cleanups.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659924"></a>A.1.13.1. Upgrading</h4></div></div><div></div></div><p>You need a dump/reload to upgrade
- from precedent releases. See the <a href="#upgrading" title="2.2.1. Upgrading">upgrading</a>
- chapter for more informations.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659943"></a>A.1.13.2. Library changes</h4></div></div><div></div></div><p>BUGFIX in multi()</p><p>early return [when noop] from multi()</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659957"></a>A.1.13.3. Scripts changes</h4></div></div><div></div></div><p>dropped {x,y}{min,max}(box2d) functions</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659968"></a>A.1.13.4. Other changes</h4></div></div><div></div></div><p>BUGFIX in postgis_restore.pl scrip</p><p>BUGFIX in dumper's 64bit support</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2659984"></a>A.1.14. Release 1.0.0RC5</h3></div></div><div></div></div><p>Release date: 2005/03/25</p><p>Fifth release candidate for 1.0.0.
- Contains a few bug fixes and a improvements.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2659998"></a>A.1.14.1. Upgrading</h4></div></div><div></div></div><p>If you are upgrading from
- release 1.0.0RC4 you <span class="emphasis"><em>DO
- NOT</em></span> need a dump/reload.</p><p>Upgrading from any other precedent
- release requires a dump/reload.
- See the <a href="#upgrading" title="2.2.1. Upgrading">upgrading</a>
- chapter for more informations.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660025"></a>A.1.14.2. Library changes</h4></div></div><div></div></div><p>BUGFIX (segfaulting) in box3d computation (yes, another!).</p><p>BUGFIX (segfaulting) in estimated_extent().</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660040"></a>A.1.14.3. Other changes</h4></div></div><div></div></div><p>Small build scripts and utilities refinements.</p><p>Additional performance tips documented.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2660056"></a>A.1.15. Release 1.0.0RC4</h3></div></div><div></div></div><p>Release date: 2005/03/18</p><p>Fourth release candidate for 1.0.0.
- Contains bug fixes and a few improvements.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660070"></a>A.1.15.1. Upgrading</h4></div></div><div></div></div><p>You need a dump/reload to upgrade
- from precedent releases. See the <a href="#upgrading" title="2.2.1. Upgrading">upgrading</a>
- chapter for more informations.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660088"></a>A.1.15.2. Library changes</h4></div></div><div></div></div><p>BUGFIX (segfaulting) in geom_accum().</p><p>BUGFIX in 64bit architectures support.</p><p>BUGFIX in box3d computation function with collections.</p><p>NEW subselects support in selectivity estimator.</p><p>Early return from force_collection.</p><p>Consistency check fix in SnapToGrid().</p><p>Box2d output changed back to 15 significant digits.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660124"></a>A.1.15.3. Scripts changes</h4></div></div><div></div></div><p>NEW distance_sphere() function.</p><p>Changed get_proj4_from_srid implementation to use PL/PGSQL instead of SQL.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660139"></a>A.1.15.4. Other changes</h4></div></div><div></div></div><p>BUGFIX in loader and dumper handling of MultiLine shapes</p><p>BUGFIX in loader, skipping all but first hole of polygons.</p><p>jdbc2: code cleanups, Makefile improvements</p><p>FLEX and YACC variables set *after* pgsql Makefile.global is included and only if the pgsql *stripped* version evaluates to the empty string</p><p>Added already generated parser in release</p><p>Build scripts refinements</p><p>improved version handling, central Version.config</p><p>improvements in postgis_restore.pl</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2660181"></a>A.1.16. Release 1.0.0RC3</h3></div></div><div></div></div><p>Release date: 2005/02/24</p><p>Third release candidate for 1.0.0.
- Contains many bug fixes and improvements.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660195"></a>A.1.16.1. Upgrading</h4></div></div><div></div></div><p>You need a dump/reload to upgrade
- from precedent releases. See the <a href="#upgrading" title="2.2.1. Upgrading">upgrading</a>
- chapter for more informations.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660213"></a>A.1.16.2. Library changes</h4></div></div><div></div></div><p>BUGFIX in transform(): missing SRID, better error handling.</p><p>BUGFIX in memory alignment handling</p><p>BUGFIX in force_collection() causing mapserver connector failures on simple (single) geometry types.</p><p>BUGFIX in GeometryFromText() missing to add a bbox cache.</p><p>reduced precision of box2d output.</p><p>prefixed DEBUG macros with PGIS_ to avoid clash with pgsql one</p><p>plugged a leak in GEOS2POSTGIS converter</p><p>Reduced memory usage by early releasing query-context palloced one.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660254"></a>A.1.16.3. Scripts changes</h4></div></div><div></div></div><p>BUGFIX in 72 index bindings.</p><p>BUGFIX in probe_geometry_columns() to work with PG72 and support multiple geometry columns in a single table</p><p>NEW bool::text cast</p><p>Some functions made IMMUTABLE from STABLE, for performance
- improvement.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660278"></a>A.1.16.4. JDBC changes</h4></div></div><div></div></div><p>jdbc2: small patches, box2d/3d tests, revised docs and license.</p><p>jdbc2: bug fix and testcase in for pgjdbc 8.0 type autoregistration</p><p>jdbc2: Removed use of jdk1.4 only features to enable build with older jdk releases.</p><p>jdbc2: Added support for building against pg72jdbc2.jar</p><p>jdbc2: updated and cleaned makefile</p><p>jdbc2: added BETA support for jts geometry classes</p><p>jdbc2: Skip known-to-fail tests against older PostGIS servers.</p><p>jdbc2: Fixed handling of measured geometries in EWKT.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660319"></a>A.1.16.5. Other changes</h4></div></div><div></div></div><p>new performance tips chapter in manual</p><p>documentation updates: pgsql72 requirement, lwpostgis.sql</p><p>few changes in autoconf </p><p>BUILDDATE extraction made more portable</p><p>fixed spatial_ref_sys.sql to avoid vacuuming the whole
- database.</p><p>spatial_ref_sys: changed Paris entries to match the ones
- distributed with 0.x.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2660352"></a>A.1.17. Release 1.0.0RC2</h3></div></div><div></div></div><p>Release date: 2005/01/26</p><p>Second release candidate for 1.0.0
- containing bug fixes and a few improvements.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660366"></a>A.1.17.1. Upgrading</h4></div></div><div></div></div><p>You need a dump/reload to upgrade
- from precedent releases. See the <a href="#upgrading" title="2.2.1. Upgrading">upgrading</a>
- chapter for more informations.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660385"></a>A.1.17.2. Library changes</h4></div></div><div></div></div><p>BUGFIX in pointarray box3d computation</p><p>BUGFIX in distance_spheroid definition</p><p>BUGFIX in transform() missing to update bbox cache</p><p>NEW jdbc driver (jdbc2)</p><p>GEOMETRYCOLLECTION(EMPTY) syntax support for backward compatibility</p><p>Faster binary outputs</p><p>Stricter OGC WKB/WKT constructors</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660420"></a>A.1.17.3. Scripts changes</h4></div></div><div></div></div><p>More correct STABLE, IMMUTABLE, STRICT uses in lwpostgis.sql</p><p>stricter OGC WKB/WKT constructors</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660435"></a>A.1.17.4. Other changes</h4></div></div><div></div></div><p>Faster and more robust loader (both i18n and not)</p><p>Initial autoconf script</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2660450"></a>A.1.18. Release 1.0.0RC1</h3></div></div><div></div></div><p>Release date: 2005/01/13</p><p>This is the first candidate of a
- major postgis release, with internal
- storage of postgis types redesigned to be smaller
- and faster on indexed queries.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660466"></a>A.1.18.1. Upgrading</h4></div></div><div></div></div><p>You need a dump/reload to upgrade
- from precedent releases. See the <a href="#upgrading" title="2.2.1. Upgrading">upgrading</a>
- chapter for more informations.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2660484"></a>A.1.18.2. Changes</h4></div></div><div></div></div><p>
- Faster canonical input parsing.
- </p><p>
- Lossless canonical output.
- </p><p>
- EWKB Canonical binary IO with PG>73.
- </p><p>
- Support for up to 4d coordinates, providing
- lossless shapefile->postgis->shapefile
- conversion.
- </p><p>
- New function: UpdateGeometrySRID(), AsGML(),
- SnapToGrid(), ForceRHR(), estimated_extent(),
- accum().
- </p><p>
- Vertical positioning indexed operators.
- </p><p>
- JOIN selectivity function.
- </p><p>
- More geometry constructors / editors.
- </p><p>
- Postgis extension API.
- </p><p>
- UTF8 support in loader.
- </p></div></div></div></div></div></body></html>
Modified: packages/postgis/upstream/doc/man/pgsql2shp.1
===================================================================
--- packages/postgis/upstream/doc/man/pgsql2shp.1 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/doc/man/pgsql2shp.1 2006-10-31 20:52:30 UTC (rev 577)
@@ -2,72 +2,96 @@
.SH "NAME"
.LP
pgsql2shp - postgis to shapefile dumper
+
.SH "SYNTAX"
.LP
pgsql2shp [\fIoptions\fR] \fIdatabase\fR [\fIschema\fR\fB.\fR]\fItable\fR
.br
pgsql2shp [\fIoptions\fR] \fIdatabase\fR \fIquery\fR
+
.SH "DESCRIPTION"
.LP
-The pgsql2shp table dumper connects directly to the database and converts a table (possibly created by user query) into a shape file. It is compatible with
-all versions of PostGIS.
+The pgsql2shp table dumper connects directly to the database and converts a
+table (possibly created by user query) into a shape file. It is compatible
+with all versions of PostGIS.
+
+Version: 1.1.5 (2006/10/06)
+
+.SH "USAGE"
+.LP
+The <database> is the name of the database to connect to.
+
+The <table> is the (optionally schema-qualified) table to read spatial
+data from. Alternatively, you can specify a QUERY whose result will be
+written into the shapefile.
+
.SH "OPTIONS"
.LP
The commandline options are:
-
.TP
\fB\-f\fR <\fIfilename\fR>
Write the output to a particular filename.
-
.TP
\fB\-h\fR <\fIhost\fR>
The database host to connect to.
-
.TP
\fB\-p\fR <\fIport\fR>
The port to connect to on the database host.
-
-
.TP
\fB\-P\fR <\fIpassword\fR>
The password to use when connecting to the database.
-
-
.TP
\fB\-u\fR <\fIuser\fR>
The username to use when connecting to the database.
-
.TP
\fB\-g\fR <\fIgeometry column\fR>
-In the case of tables with multiple geometry columns, the geometry column to use when writing the shape file.
-
+In the case of tables with multiple geometry columns, the geometry column
+to use when writing the shape file.
.TP
\fB\-b\fR
-Use a binary cursor. When used on pre\-1.0.0 PostGIS versions this will reduce the likelihood of coordinate drift due to conversion to and from WKT format.
-Coordinate drifts will not occur with PostGIS 1.0.0 and newer versions.
-It will be slightly faster, but might fail if any NON\-gemetry column lacks
-a cast to text.
-
+Use a binary cursor. When used on pre\-1.0.0 PostGIS versions this will
+reduce the likelihood of coordinate drift due to conversion to and from
+WKT format. Coordinate drifts will not occur with PostGIS 1.0.0 and newer
+versions. It will be slightly faster, but might fail if any NON\-gemetry
+column lacks a cast to text.
.TP
\fB\-r\fR
Raw mode. Do not drop the gid field, or escape column names.
-
.TP
\fB\-d\fR
-For backward compatibility: write a 3\-dimensional shape file when dumping from old (pre\-1.0.0) postgis databases (the default is to write a 2\-dimensional shape file in that case). Starting from postgis\-1.0.0+, dimensions are fully encoded.
-
+For backward compatibility: write a 3\-dimensional shape file when dumping
+from old (pre\-1.0.0) postgis databases (the default is to write a
+2\-dimensional shape file in that case). Starting from postgis\-1.0.0+,
+dimensions are fully encoded.
.TP
\fB\-k\fR
Keep idendifiers case (don't uppercase field names).
+.SH "INSTALLATION"
+.LP
+To compile the program from source, simply run "make" in the source directory.
+Then copy the binary in your shell search path (or wherever you like). This
+text is also available as a man page in the ../doc/man/ directory, ready for
+copying it into the manual search path on unixoid systems.
+.SH "EXAMPLES"
+.LP
+An example session using the dumper to create shape file from a database might
+look like this:
+
+# \fBpgsql2shp -f myfile -p 5555 my_db roads_table\fR
+
.SH "AUTHORS"
.LP
Originally written by Jeff Lounsbury <jeffloun at refractions.net>.
Improved and maintained by Sandro Santilli <strk at refractions.net>.
+Includes small contributions and improvements by others.
This application uses functionality from shapelib 1.2.9
by Frank Warmerdam <warmerda at gdal.velocet.ca> to write to ESRI Shape files.
+
.SH "SEE ALSO"
.LP
shp2pgsql(1)
+
+More information is available at http://postgis.refractions.net
Modified: packages/postgis/upstream/doc/man/shp2pgsql.1
===================================================================
--- packages/postgis/upstream/doc/man/shp2pgsql.1 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/doc/man/shp2pgsql.1 2006-10-31 20:52:30 UTC (rev 577)
@@ -2,80 +2,104 @@
.SH "NAME"
.LP
shp2pgsql - shapefile to postgis loader
+
.SH "SYNTAX"
.LP
shp2pgsql [\fIoptions\fR] \fIshapefile\fR [\fIschema\fR\fB.\fR]\fItable\fR
+
.SH "DESCRIPTION"
.LP
-The shp2pgsql data loader converts ESRI Shape files into SQL suitable for insertion into a PostGIS/PostgreSQL database.
+The shp2pgsql data loader converts ESRI Shape files into SQL suitable
+for insertion into a PostGIS/PostgreSQL database.
+Version: 1.1.5 (2006/10/06)
+
+.SH "USAGE"
+.LP
+The <shapefile> is the name of the shape file, without any extension
+information. For example, 'roads' would be the name of the shapefile
+comprising the 'roads.shp', 'roads.shx', and 'roads.dbf' files.
+
+The <tablename> is the (optionally schema-qualified) name of the database
+table you want the data stored in in the database. Within that table,
+the geometry will be placed in the 'geo_value' column by default.
+
.SH "OPTIONS"
.LP
The loader has several operating modes distinguished by command line flags:
+(Note that -a, -c, -d and -p are mutually exclusive.)
.TP
\fB\-d\fR
-Drops the database table before creating a new table with the data in the Shape file.
-
+Drops the database table before creating a new table with the data in the
+Shape file.
.TP
\fB\-a\fR
-Appends data from the Shape file into the database table. Note that to use this option to load multiple files, the files must have the same attributes and same data types.
-
+Appends data from the Shape file into the database table. Note that to use
+this option to load multiple files, the files must have the same attributes
+and same data types.
.TP
\fB\-c\fR
-Creates a new table and populates it from the Shape file. This is the default mode.
-
+Creates a new table and populates it from the Shape file. This is the default
+mode.
.TP
\fB\-p\fR
-Only produces the table creation SQL code, without adding any actual data. This can
-be used if you need to completely separate the table creation and data loading steps.
-
+Only produces the table creation SQL code, without adding any actual data.
+This can be used if you need to completely separate the table creation and
+data loading steps.
.TP
\fB\-D\fR
-Use the PostgreSQL "dump" format for the output data. This can be combined with -a, -c and -d.
-It is much faster to load than the default "insert" SQL format. Use this for very large data sets.
-
+Use the PostgreSQL "dump" format for the output data. This can be combined
+with -a, -c and -d. It is much faster to load than the default "insert" SQL
+format. Use this for very large data sets.
.TP
\fB\-s\fR <\fISRID\fR>
Creates and populates the geometry tables with the specified SRID.
-
.TP
\fB\-g\fR <\fIgeometry_column\fR>
Specify the name of the geometry column (mostly useful in append mode).
-
.TP
\fB\-k\fR
-Keep idendifiers case (column, schema and attributes). Note that attributes in Shapefile are usually all UPPERCASE.
-
+Keep idendifiers case (column, schema and attributes). Note that attributes
+in Shapefile are usually all UPPERCASE.
.TP
\fB\-i\fR
-Coerce all integers to standard 32\-bit integers, do not create 64\-bit bigints, even if the DBF header signature appears to warrant it.
-
+Coerce all integers to standard 32\-bit integers, do not create 64\-bit
+bigints, even if the DBF header signature appears to warrant it.
.TP
+\fB\-S\fR
+Generate simple Geometries instead of MULTIgeometries. Shape files don't
+differ between LINESTRINGs and MULTILINESTRINGs, so shp2pgsql generates
+MULTILINESTRINGs by default. This switch will produce LINESTRINGs instead,
+but shp2pgsql will fail when it hits a real MULTILINESTRING. The same works
+for POLYGONs vs. MULTIPOLYGONs.
+.TP
\fB\-w\fR
Output WKT format, for use with older (0.x) versions of PostGIS.
Note that this will introduce coordinate drifts and will drop
M values from shapefiles.
-
.TP
\fB\-W\fR <\fIencoding\fR>
Specify the character \fIencoding\fR of Shapefile's attributes.
If this option is used the output will be encoded in UTF-8.
-
.TP
\fB\-I\fR
Create a GiST index on the geometry column.
-
.TP
\fB\-N\fR <\fIpolicy\fR>
Specify NULL geometries handling policy (insert,skip,abort).
+.SH "INSTALLATION"
.LP
-Note that -a, -c, -d and -p are mutually exclusive.
+To compile the program from source, simply run "make" in the source directory.
+Then copy the binary in your shell search path (or wherever you like). This
+text is also available as a man page in the ../doc/man/ directory, ready for
+copying it into the manual search path on unixoid systems.
.SH "EXAMPLES"
.LP
-An example session using the loader to create an input file and uploading it might look like this:
+An example session using the loader to create an input file and uploading it
+might look like this:
# \fBshp2pgsql shaperoads roadstable roadsdb > roads.sql\fR
.br
@@ -84,13 +108,18 @@
A conversion and upload can be done all in one step using UNIX pipes:
# \fBshp2pgsql shaperoads roadstable roadsdb | psql \-d roadsdb\fR
+
.SH "AUTHORS"
.LP
Originally written by Jeff Lounsbury <jeffloun at refractions.net>.
Improved and maintained by Sandro Santilli <strk at refractions.net>.
+Includes small contributions and improvements by others.
This application uses functionality from shapelib 1.2.9
by Frank Warmerdam <warmerda at gdal.velocet.ca> to read from ESRI Shape files.
+
.SH "SEE ALSO"
.LP
pgsql2shp(1)
+
+More information is available at http://postgis.refractions.net
Modified: packages/postgis/upstream/doc/postgis.xml
===================================================================
--- packages/postgis/upstream/doc/postgis.xml 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/doc/postgis.xml 2006-10-31 20:52:30 UTC (rev 577)
@@ -361,6 +361,19 @@
</listitem>
</orderedlist>
+ <sect2 id="templatepostgis">
+ <title>Creating PostGIS spatially-enabled databases from an in-built template</title>
+ <para>Some packaged distributions of PostGIS (in particular the Win32 installers for PostGIS >= 1.1.5) load the PostGIS functions into a template database called <varname>template_postgis</varname>. If the <varname>template_postgis</varname> database exists in your PostgreSQL installation then it is possible for users and/or applications to create spatially-enabled databases using a single command. Note that in both cases, the database user must have been granted the privilege to create new databases.</para>
+
+ <para>From the shell:</para>
+
+ <programlisting># createdb -T template_postgis my_spatial_db</programlisting>
+
+ <para>From SQL:</para>
+
+ <programlisting>postgres=# CREATE DATABASE my_spatial_db TEMPLATE=template_postgis</programlisting>
+ </sect2>
+
<sect2 id="upgrading">
<title>Upgrading</title>
@@ -574,7 +587,8 @@
<para>The loader is called <filename>shp2pgsql</filename> and converts
ESRI Shape files into SQL suitable for loading in PostGIS/PostgreSQL.
The dumper is called <filename>pgsql2shp</filename> and converts PostGIS
- tables (or queries) into ESRI Shape files.</para>
+ tables (or queries) into ESRI Shape files. For more verbose documentation,
+ see the online help, and the manual pages.</para>
</sect1>
</chapter>
@@ -5312,6 +5326,54 @@
<title>Release Notes</title>
+ <sect2>
+ <title>Release 1.1.5</title>
+ <para>Release date: 2006/10/13</para>
+ <para>This is an bugfix release, including a critical
+ segfault on win32. Upgrade is <emphasis>encouraged</emphasis>.
+ </para>
+
+ <sect3>
+ <title>Upgrading</title>
+
+ <para>
+If you are upgrading from release 1.0.3 or later follow the
+<link linkend="soft_upgrade">soft upgrade</link> procedure.
+ </para>
+
+ <para>
+If you are upgrading from a release <emphasis>between 1.0.0RC6 and
+1.0.2</emphasis> (inclusive) and really want a live upgrade read the
+<link linkend="rel_1.0.3_upgrading">upgrade section</link> of the 1.0.3
+release notes chapter.
+ </para>
+
+ <para>
+Upgrade from any release prior to 1.0.0RC6 requires an
+<link linkend="hard_upgrade">hard upgrade</link>.
+ </para>
+ </sect3>
+
+ <sect3>
+ <title>Bug fixes</title>
+ <para>Fixed MingW link error that was causing pgsql2shp to
+ segfault on Win32 when compiled for PostgreSQL 8.2</para>
+ <para>fixed nullpointer Exception in Geometry.equals() method
+ in Java</para>
+ <para>Added EJB3Spatial.odt to fulfill the GPL requirement of
+ distributing the "preferred form of modification"</para>
+ <para>Removed obsolete synchronization from JDBC Jts code.</para>
+ <para>Updated heavily outdated README files for shp2pgsql/pgsql2shp by
+ merging them with the manpages.</para>
+ <para>Fixed version tag in jdbc code that still said "1.1.3" in the
+ "1.1.4" release.</para>
+ </sect3>
+ <sect3>
+ <title>New Features</title>
+ <para>Added -S option for non-multi geometries to shp2pgsql</para>
+ </sect3>
+ </sect2>
+
<sect2>
<title>Release 1.1.4</title>
<para>Release date: 2006/09/27</para>
Added: packages/postgis/upstream/java/ejb3/EJB3Spatial.odt
===================================================================
(Binary files differ)
Property changes on: packages/postgis/upstream/java/ejb3/EJB3Spatial.odt
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: packages/postgis/upstream/java/ejb3/README.txt
===================================================================
--- packages/postgis/upstream/java/ejb3/README.txt 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/ejb3/README.txt 2006-10-31 20:52:30 UTC (rev 577)
@@ -1,5 +1,5 @@
-$Id: README.txt 2489 2006-09-27 08:47:10Z mschaber $
-(This code was contributed by Norman Barker <nbarker at ittvis.com>)
+$Id: README.txt 2505 2006-10-11 10:45:28Z mschaber $
+(This code was contributed by Norman Barker <norman.barker at gmail.com>)
Spatial EJB3
@@ -13,7 +13,8 @@
Services.
Since it is useful to display screenshots in a tutorial this has been written
-as a PDF and the document and source are available here.
+as an Openoffice Document. For easy viewing and printing, a PDF version is
+also available.
COMPILING:
Modified: packages/postgis/upstream/java/ejb3/build.xml
===================================================================
--- packages/postgis/upstream/java/ejb3/build.xml 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/ejb3/build.xml 2006-10-31 20:52:30 UTC (rev 577)
@@ -3,7 +3,7 @@
*
* PostGIS extension for PostgreSQL JDBC driver - EJB3 Support
*
- * (C) 2006 Noarman Barker <nbarker at ittvis.com>
+ * (C) 2006 Norman Barker <norman.barker at gmail.com>
*
* This library is free software; you can redistribute it and/or modify it under
* the terms of the GNU Lesser General Public License as published by the Free
@@ -19,7 +19,7 @@
* 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA or visit the web at
* http://www.gnu.org.
*
- * $Id: build.xml 2476 2006-09-20 09:03:12Z mschaber $
+ * $Id: build.xml 2500 2006-10-09 17:12:46Z mschaber $
-->
<project name="PostGIS EJB3 Tutorial" default="compile" basedir=".">
<property name="build.dir" value="bin"/>
Modified: packages/postgis/upstream/java/ejb3/ejb3spatial.pdf
===================================================================
(Binary files differ)
Modified: packages/postgis/upstream/java/ejb3/src/org/postgis/ejb/PersonEntity.java
===================================================================
--- packages/postgis/upstream/java/ejb3/src/org/postgis/ejb/PersonEntity.java 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/ejb3/src/org/postgis/ejb/PersonEntity.java 2006-10-31 20:52:30 UTC (rev 577)
@@ -3,7 +3,7 @@
*
* PostGIS extension for PostgreSQL JDBC driver - EJB3 Tutorial
*
- * (C) 2006 Noarman Barker <nbarker at ittvis.com>
+ * (C) 2006 Norman Barker <norman.barker at gmail.com>
*
* This library is free software; you can redistribute it and/or modify it under
* the terms of the GNU Lesser General Public License as published by the Free
@@ -19,7 +19,7 @@
* 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA or visit the web at
* http://www.gnu.org.
*
- * $Id: PersonEntity.java 2476 2006-09-20 09:03:12Z mschaber $
+ * $Id: PersonEntity.java 2500 2006-10-09 17:12:46Z mschaber $
*/
package org.postgis.ejb;
Modified: packages/postgis/upstream/java/ejb3/src/org/postgis/ejb/UserBean.java
===================================================================
--- packages/postgis/upstream/java/ejb3/src/org/postgis/ejb/UserBean.java 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/ejb3/src/org/postgis/ejb/UserBean.java 2006-10-31 20:52:30 UTC (rev 577)
@@ -3,7 +3,7 @@
*
* PostGIS extension for PostgreSQL JDBC driver - EJB3 Tutorial
*
- * (C) 2006 Noarman Barker <nbarker at ittvis.com>
+ * (C) 2006 Norman Barker <norman.barker at gmail.com>
*
* This library is free software; you can redistribute it and/or modify it under
* the terms of the GNU Lesser General Public License as published by the Free
@@ -19,7 +19,7 @@
* 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA or visit the web at
* http://www.gnu.org.
*
- * $Id: UserBean.java 2476 2006-09-20 09:03:12Z mschaber $
+ * $Id: UserBean.java 2500 2006-10-09 17:12:46Z mschaber $
*/
package org.postgis.ejb;
Modified: packages/postgis/upstream/java/ejb3/src/org/postgis/ejb/UserBeanRemote.java
===================================================================
--- packages/postgis/upstream/java/ejb3/src/org/postgis/ejb/UserBeanRemote.java 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/ejb3/src/org/postgis/ejb/UserBeanRemote.java 2006-10-31 20:52:30 UTC (rev 577)
@@ -3,7 +3,7 @@
*
* PostGIS extension for PostgreSQL JDBC driver - EJB3 Tutorial
*
- * (C) 2006 Noarman Barker <nbarker at ittvis.com>
+ * (C) 2006 Norman Barker <norman.barker at gmail.com>
*
* This library is free software; you can redistribute it and/or modify it under
* the terms of the GNU Lesser General Public License as published by the Free
@@ -19,7 +19,7 @@
* 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA or visit the web at
* http://www.gnu.org.
*
- * $Id: UserBeanRemote.java 2476 2006-09-20 09:03:12Z mschaber $
+ * $Id: UserBeanRemote.java 2500 2006-10-09 17:12:46Z mschaber $
*/
package org.postgis.ejb;
Modified: packages/postgis/upstream/java/ejb3/src/org/postgis/ejb/mdb/IngestMDB.java
===================================================================
--- packages/postgis/upstream/java/ejb3/src/org/postgis/ejb/mdb/IngestMDB.java 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/ejb3/src/org/postgis/ejb/mdb/IngestMDB.java 2006-10-31 20:52:30 UTC (rev 577)
@@ -3,7 +3,7 @@
*
* PostGIS extension for PostgreSQL JDBC driver - EJB3 Tutorial
*
- * (C) 2006 Noarman Barker <nbarker at ittvis.com>
+ * (C) 2006 Norman Barker <norman.barker at gmail.com>
*
* This library is free software; you can redistribute it and/or modify it under
* the terms of the GNU Lesser General Public License as published by the Free
@@ -19,7 +19,7 @@
* 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA or visit the web at
* http://www.gnu.org.
*
- * $Id: IngestMDB.java 2476 2006-09-20 09:03:12Z mschaber $
+ * $Id: IngestMDB.java 2500 2006-10-09 17:12:46Z mschaber $
*/
package org.postgis.ejb.mdb;
Modified: packages/postgis/upstream/java/ejb3/src/org/postgis/hibernate/GeometryType.java
===================================================================
--- packages/postgis/upstream/java/ejb3/src/org/postgis/hibernate/GeometryType.java 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/ejb3/src/org/postgis/hibernate/GeometryType.java 2006-10-31 20:52:30 UTC (rev 577)
@@ -3,7 +3,7 @@
*
* PostGIS extension for PostgreSQL JDBC driver - EJB3 Tutorial
*
- * (C) 2006 Noarman Barker <nbarker at ittvis.com>
+ * (C) 2006 Norman Barker <norman.barker at gmail.com>
*
* This library is free software; you can redistribute it and/or modify it under
* the terms of the GNU Lesser General Public License as published by the Free
@@ -19,7 +19,7 @@
* 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA or visit the web at
* http://www.gnu.org.
*
- * $Id: GeometryType.java 2476 2006-09-20 09:03:12Z mschaber $
+ * $Id: GeometryType.java 2501 2006-10-09 17:22:15Z mschaber $
*/
package org.postgis.hibernate;
@@ -111,9 +111,9 @@
/* (non-Javadoc)
* @see org.hibernate.usertype.UserType#replace(java.lang.Object, java.lang.Object, java.lang.Object)
*/
- public Object replace(Object arg0, Object arg1, Object arg2) throws HibernateException {
- // TODO Auto-generated method stub
- return null;
+ public Object replace(Object original, Object target,
+ Object owner) throws HibernateException {
+ return original;
}
/* (non-Javadoc)
Modified: packages/postgis/upstream/java/jdbc/jtssrc/org/postgis/jts/JtsBinaryParser.java
===================================================================
--- packages/postgis/upstream/java/jdbc/jtssrc/org/postgis/jts/JtsBinaryParser.java 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/jdbc/jtssrc/org/postgis/jts/JtsBinaryParser.java 2006-10-31 20:52:30 UTC (rev 577)
@@ -19,7 +19,7 @@
* 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA or visit the web at
* http://www.gnu.org.
*
- * $Id: JtsBinaryParser.java 2407 2006-07-18 18:13:31Z mschaber $
+ * $Id: JtsBinaryParser.java 2493 2006-10-02 14:30:47Z mschaber $
*/
package org.postgis.jts;
@@ -68,22 +68,16 @@
/**
* Parse a hex encoded geometry
- *
- * Is synchronized to protect offset counter. (Unfortunately, Java does not
- * have neither call by reference nor multiple return values.)
*/
- public synchronized Geometry parse(String value) {
+ public Geometry parse(String value) {
StringByteGetter bytes = new ByteGetter.StringByteGetter(value);
return parseGeometry(valueGetterForEndian(bytes));
}
/**
* Parse a binary encoded geometry.
- *
- * Is synchronized to protect offset counter. (Unfortunately, Java does not
- * have neither call by reference nor multiple return values.)
*/
- public synchronized Geometry parse(byte[] value) {
+ public Geometry parse(byte[] value) {
BinaryByteGetter bytes = new ByteGetter.BinaryByteGetter(value);
return parseGeometry(valueGetterForEndian(bytes));
}
Modified: packages/postgis/upstream/java/jdbc/jtssrc/org/postgis/jts/JtsBinaryWriter.java
===================================================================
--- packages/postgis/upstream/java/jdbc/jtssrc/org/postgis/jts/JtsBinaryWriter.java 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/jdbc/jtssrc/org/postgis/jts/JtsBinaryWriter.java 2006-10-31 20:52:30 UTC (rev 577)
@@ -19,7 +19,7 @@
* 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA or visit the web at
* http://www.gnu.org.
*
- * $Id: JtsBinaryWriter.java 2410 2006-07-19 13:31:18Z mschaber $
+ * $Id: JtsBinaryWriter.java 2497 2006-10-02 23:26:34Z mschaber $
*/
package org.postgis.jts;
@@ -74,42 +74,34 @@
/**
* Write a hex encoded geometry
*
- * Is synchronized to protect offset counter. (Unfortunately, Java does not
- * have neither call by reference nor multiple return values.) This is a
- * TODO item.
- *
* Currently, geometries with more than 2 dimensions and measures are not
* cleanly supported, but SRID is honored.
*/
- public synchronized String writeHexed(Geometry geom, byte REP) {
+ public String writeHexed(Geometry geom, byte REP) {
int length = estimateBytes(geom);
ByteSetter.StringByteSetter bytes = new ByteSetter.StringByteSetter(length);
writeGeometry(geom, valueSetterForEndian(bytes, REP));
return bytes.result();
}
- public synchronized String writeHexed(Geometry geom) {
+ public String writeHexed(Geometry geom) {
return writeHexed(geom, ValueSetter.NDR.NUMBER);
}
/**
* Write a binary encoded geometry.
*
- * Is synchronized to protect offset counter. (Unfortunately, Java does not
- * have neither call by reference nor multiple return values.) This is a
- * TODO item.
- *
* Currently, geometries with more than 2 dimensions and measures are not
* cleanly supported, but SRID is honored.
*/
- public synchronized byte[] writeBinary(Geometry geom, byte REP) {
+ public byte[] writeBinary(Geometry geom, byte REP) {
int length = estimateBytes(geom);
ByteSetter.BinaryByteSetter bytes = new ByteSetter.BinaryByteSetter(length);
writeGeometry(geom, valueSetterForEndian(bytes, REP));
return bytes.result();
}
- public synchronized byte[] writeBinary(Geometry geom) {
+ public byte[] writeBinary(Geometry geom) {
return writeBinary(geom, ValueSetter.NDR.NUMBER);
}
@@ -199,9 +191,6 @@
/**
* Write a Coordinatesequence, part of LinearRing and Linestring, but not
* MultiPoint!
- *
- * @param haveZ
- * @param haveM
*/
private void writeCoordinates(CoordinateSequence seq, int dims, ValueSetter dest) {
for (int i = 0; i < seq.size(); i++) {
@@ -314,9 +303,6 @@
/**
* Estimate an Array of "slim" Points (without endianness and type, part of
* LinearRing and Linestring, but not MultiPoint!
- *
- * @param haveZ
- * @param haveM
*/
private int estimatePointArray(int length, Point example) {
// number of points
Modified: packages/postgis/upstream/java/jdbc/src/examples/TestAutoregister.java
===================================================================
--- packages/postgis/upstream/java/jdbc/src/examples/TestAutoregister.java 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/jdbc/src/examples/TestAutoregister.java 2006-10-31 20:52:30 UTC (rev 577)
@@ -19,7 +19,7 @@
* Place, Suite 330, Boston, MA 02111-1307 USA or visit the web at
* http://www.gnu.org.
*
- * $Id: TestAutoregister.java 1622 2005-04-15 14:04:34Z mschaber $
+ * $Id: TestAutoregister.java 2497 2006-10-02 23:26:34Z mschaber $
*/
package examples;
@@ -88,6 +88,8 @@
System.err.println("Connection initialization failed, aborting.");
e.printStackTrace();
System.exit(1);
+ // signal the compiler that code flow ends here:
+ throw new AssertionError();
}
int postgisServerMajor = 0;
@@ -96,8 +98,9 @@
} catch (SQLException e) {
System.err.println("Error fetching PostGIS version: " + e.getMessage());
System.err.println("Is PostGIS really installed in the database?");
- // Signal the compiler that code flow ends here.
- System.exit(1);
+ System.exit(1);
+ // signal the compiler that code flow ends here:
+ throw new AssertionError();
}
System.out.println("PostGIS Version: " + postgisServerMajor);
Modified: packages/postgis/upstream/java/jdbc/src/org/postgis/Geometry.java
===================================================================
--- packages/postgis/upstream/java/jdbc/src/org/postgis/Geometry.java 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/jdbc/src/org/postgis/Geometry.java 2006-10-31 20:52:30 UTC (rev 577)
@@ -21,7 +21,7 @@
* 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA or visit the web at
* http://www.gnu.org.
*
- * $Id: Geometry.java 2343 2006-05-09 13:06:56Z mschaber $
+ * $Id: Geometry.java 2495 2006-10-02 15:58:43Z mschaber $
*/
package org.postgis;
@@ -145,15 +145,13 @@
* values
*/
public boolean equals(Geometry other) {
- boolean firstline = (other != null) && (this.dimension == other.dimension)
- && (this.type == other.type);
- boolean sridequals = (this.srid == other.srid);
- boolean measEquals = (this.haveMeasure == other.haveMeasure);
- boolean secondline = sridequals && measEquals;
- boolean classequals = other.getClass().equals(this.getClass());
- boolean equalsintern = this.equalsintern(other);
- boolean result = firstline && secondline && classequals && equalsintern;
- return result;
+ return (other != null)
+ && (this.dimension == other.dimension)
+ && (this.type == other.type)
+ && (this.srid == other.srid)
+ && (this.haveMeasure == other.haveMeasure)
+ && other.getClass().equals(this.getClass())
+ && this.equalsintern(other);
}
/**
Modified: packages/postgis/upstream/java/jdbc/src/org/postgis/binary/BinaryWriter.java
===================================================================
--- packages/postgis/upstream/java/jdbc/src/org/postgis/binary/BinaryWriter.java 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/jdbc/src/org/postgis/binary/BinaryWriter.java 2006-10-31 20:52:30 UTC (rev 577)
@@ -19,7 +19,7 @@
* 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA or visit the web at
* http://www.gnu.org.
*
- * $Id: BinaryWriter.java 1622 2005-04-15 14:04:34Z mschaber $
+ * $Id: BinaryWriter.java 2497 2006-10-02 23:26:34Z mschaber $
*/
package org.postgis.binary;
@@ -190,9 +190,6 @@
/**
* Write an Array of "slim" Points (without endianness, srid and type, part
* of LinearRing and Linestring, but not MultiPoint!
- *
- * @param haveZ
- * @param haveM
*/
private void writePointArray(Point[] geom, ValueSetter dest) {
// number of points
@@ -304,9 +301,6 @@
/**
* Write an Array of "slim" Points (without endianness and type, part of
* LinearRing and Linestring, but not MultiPoint!
- *
- * @param haveZ
- * @param haveM
*/
private int estimatePointArray(Point[] geom) {
// number of points
Modified: packages/postgis/upstream/java/jdbc/todo.txt
===================================================================
--- packages/postgis/upstream/java/jdbc/todo.txt 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/jdbc/todo.txt 2006-10-31 20:52:30 UTC (rev 577)
@@ -1,5 +1,5 @@
Todo for PostGIS 1.0 compatible JDBC classes
-$Id: todo.txt 1622 2005-04-15 14:04:34Z mschaber $
+$Id: todo.txt 2491 2006-09-27 15:50:33Z mschaber $
- even more Testing, especialy against different postgis,
pgjdbc and postgresql releases.
@@ -20,3 +20,7 @@
- Possibly adding server side code to support plJava
http://gborg.postgresql.org/project/pljava/projdisplay.php
+- Rework the BinaryParser/BinaryWriter to work on SQLInput/SQLOutput
+ instances, as well as reworking ValueGetter/ValueSetter to implment those interfaces.
+
+- Unify the build of app java projects
Added: packages/postgis/upstream/java/pljava/README.txt
===================================================================
--- packages/postgis/upstream/java/pljava/README.txt 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/pljava/README.txt 2006-10-31 20:52:30 UTC (rev 577)
@@ -0,0 +1,7 @@
+Pre-Alpha support for PLJava.
+
+!!! This code will not work against any released pljava version. See pljava developer list
+archive for discussion of the changes needed in pljava for this code to work. Let's hope all
+the fixes get into the next pljava release.
+
+Put pljava.jar and jts-1.7.1.jar into lib/ directory, then run ant.
Added: packages/postgis/upstream/java/pljava/build.xml
===================================================================
--- packages/postgis/upstream/java/pljava/build.xml 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/pljava/build.xml 2006-10-31 20:52:30 UTC (rev 577)
@@ -0,0 +1,69 @@
+<?xml version="1.0"?>
+<!-- PostGIS PLJava support
+ (C) 2006 Markus Schaber <schabi at logix-tt.com>
+
+This library is free software; you can redistribute it and/or modify it under
+the terms of the GNU Lesser General Public License as published by the Free
+Software Foundation, either version 2.1 of the License.
+
+This library is distributed in the hope that it will be useful, but WITHOUT
+ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more
+details.
+
+You should have received a copy of the GNU Lesser General Public License
+along with this library; if not, write to the Free Software Foundation, Inc.,
+59 Temple Place, Suite 330, Boston, MA 02111-1307 USA or visit the web at
+http://www.gnu.org.
+
+$Id: JtsBinaryParser.java 2407 2006-07-18 18:13:31Z mschaber $
+-->
+<project name="Postgis-PLJava" default="all">
+ <property file="build.properties" />
+ <description>
+ Build the api jar and JNI headers for the navi java api
+
+ $Id: build.xml 1329 2006-01-04 10:26:07Z schabi $
+ </description>
+
+ <property name="source.dir" value="src" />
+ <property name="class.dir" value="bin" />
+ <property name="jar.file" value="postgis_pljava.jar" />
+ <path id="buildcp"><fileset dir="lib" includes="*.jar"/></path>
+
+ <target name="all" depends="jar" description="build all">
+
+ </target>
+ <target name="clean" description="clean the whole mess up">
+ <delete dir="${class.dir}" includeemptydirs="true" />
+ <delete file="${jar.file}" />
+ </target>
+
+ <target name="prepare">
+ <mkdir dir="${class.dir}" />
+ </target>
+
+ <target name="compile" depends="prepare">
+ <javac srcdir="${source.dir}"
+ destdir="${class.dir}"
+ debug="${debug}"
+ deprecation="${deprecation}"
+ optimize="${optimize}"
+ source="1.4"
+ target="1.4" classpathref="buildcp"/>
+ </target>
+
+ <target name="jar"
+ depends="compile"
+ description="create the java api package">
+ <jar basedir="${class.dir}" destfile="${jar.file}">
+ </jar>
+ </target>
+
+ <target name="properties"
+ description="Output all properties to stdout - build file debugging help">
+ <echoproperties />
+ </target>
+
+</project>
+
Added: packages/postgis/upstream/java/pljava/functions.sql
===================================================================
--- packages/postgis/upstream/java/pljava/functions.sql 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/pljava/functions.sql 2006-10-31 20:52:30 UTC (rev 577)
@@ -0,0 +1,21 @@
+
+-- Create a function to call the java function
+CREATE OR REPLACE FUNCTION public.helloworld()
+ RETURNS "varchar" AS
+ 'org.postgis.pljava.HelloWorld.helloWorld'
+ LANGUAGE 'java' VOLATILE;
+
+SELECT sqlj.drop_type_mapping('public.geometry');
+
+SELECT sqlj.add_type_mapping('geometry', 'org.postgis.pljava.PLJGeometry');
+
+CREATE OR REPLACE FUNCTION public.getSize(geometry)
+ RETURNS "int4" AS
+ 'org.postgis.pljava.HelloWorld.getSize'
+ LANGUAGE 'java' IMMUTABLE STRICT;
+
+CREATE OR REPLACE FUNCTION public.getString(geometry)
+ RETURNS "text" AS
+ 'org.postgis.pljava.HelloWorld.getString'
+ LANGUAGE 'java' IMMUTABLE STRICT;
+
\ No newline at end of file
Added: packages/postgis/upstream/java/pljava/install.sh
===================================================================
--- packages/postgis/upstream/java/pljava/install.sh 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/pljava/install.sh 2006-10-31 20:52:30 UTC (rev 577)
@@ -0,0 +1,16 @@
+#!/bin/sh
+
+cat <<EOF
+
+set search_path to public;
+
+SELECT sqlj.install_jar('file://${PWD}/postgis_pljava.jar', 'postgis_pljava_jar', false);
+SELECT sqlj.install_jar('file://${PWD}/lib/jts-1.7.1.jar', 'jts_171_jar', false);
+
+
+-- Set the class path on the schema you are using.
+SELECT sqlj.set_classpath('public', 'postgis_pljava_jar:jts_171_jar');
+
+EOF
+
+cat functions.sql
Added: packages/postgis/upstream/java/pljava/postgis_pljava.jar
===================================================================
(Binary files differ)
Property changes on: packages/postgis/upstream/java/pljava/postgis_pljava.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: packages/postgis/upstream/java/pljava/src/org/postgis/pljava/Aggregates.java
===================================================================
--- packages/postgis/upstream/java/pljava/src/org/postgis/pljava/Aggregates.java 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/pljava/src/org/postgis/pljava/Aggregates.java 2006-10-31 20:52:30 UTC (rev 577)
@@ -0,0 +1,13 @@
+package org.postgis.pljava;
+
+import java.sql.SQLException;
+
+import org.postgresql.pljava.Session;
+
+public class Aggregates {
+ public static void test() throws SQLException {
+ Session a = org.postgresql.pljava.SessionManager.current();
+
+ a.hashCode();
+ }
+}
Added: packages/postgis/upstream/java/pljava/src/org/postgis/pljava/HelloWorld.java
===================================================================
--- packages/postgis/upstream/java/pljava/src/org/postgis/pljava/HelloWorld.java 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/pljava/src/org/postgis/pljava/HelloWorld.java 2006-10-31 20:52:30 UTC (rev 577)
@@ -0,0 +1,15 @@
+package org.postgis.pljava;
+
+public class HelloWorld {
+ public static String helloWorld() {
+ return "Hello Postgis-World";
+ }
+
+ public static int getSize(PLJGeometry geom) {
+ return geom.geom.getNumPoints();
+ }
+
+ public static String getString(PLJGeometry geom) {
+ return geom.toString();
+ }
+}
Added: packages/postgis/upstream/java/pljava/src/org/postgis/pljava/PLJGeometry.java
===================================================================
--- packages/postgis/upstream/java/pljava/src/org/postgis/pljava/PLJGeometry.java 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/pljava/src/org/postgis/pljava/PLJGeometry.java 2006-10-31 20:52:30 UTC (rev 577)
@@ -0,0 +1,80 @@
+/*
+ * PLJGeometry
+ *
+ * PostGIS datatype definition for PLJava
+ *
+ * (C) 2006 Markus Schaber, markus.schaber at logix-tt.com
+ *
+ * This library is free software; you can redistribute it and/or modify it under
+ * the terms of the GNU Lesser General Public License as published by the Free
+ * Software Foundation, either version 2.1 of the License.
+ *
+ * This library is distributed in the hope that it will be useful, but WITHOUT
+ * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+ * FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more
+ * details.
+ *
+ * You should have received a copy of the GNU Lesser General Public License
+ * along with this library; if not, write to the Free Software Foundation, Inc.,
+ * 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA or visit the web at
+ * http://www.gnu.org.
+ *
+ * $Id$
+ */
+package org.postgis.pljava;
+
+import java.sql.SQLData;
+import java.sql.SQLException;
+import java.sql.SQLInput;
+import java.sql.SQLOutput;
+
+import com.vividsolutions.jts.geom.CoordinateSequenceFactory;
+import com.vividsolutions.jts.geom.Geometry;
+import com.vividsolutions.jts.geom.GeometryFactory;
+import com.vividsolutions.jts.geom.PrecisionModel;
+import com.vividsolutions.jts.geom.impl.PackedCoordinateSequenceFactory;
+
+public class PLJGeometry implements SQLData {
+ final static PrecisionModel prec = new PrecisionModel();
+
+ final static CoordinateSequenceFactory csfac = PackedCoordinateSequenceFactory.DOUBLE_FACTORY;
+
+ final static GeometryFactory geofac = new GeometryFactory(prec, 0, csfac);
+
+ final static PLJtsParser parser = new PLJtsParser();
+ final static PLJtsWriter writer = new PLJtsWriter();
+
+ public static final String m_typeName="public.geometry";
+
+ public Geometry geom;
+
+ public String getSQLTypeName() {
+ return m_typeName;
+ }
+
+ public void readSQL(SQLInput stream, String typeName) throws SQLException {
+ checkType(typeName);
+
+ // skip length marker
+ stream.readInt();
+
+ // read the Geometry
+ this.geom = parser.parseGeometry(stream);
+ }
+
+ /** Check whether our given type is actually the one we can handle */
+ private static void checkType(String typeName) throws SQLException {
+ if (!m_typeName.equalsIgnoreCase(typeName)) {
+ throw new SQLException("parser for "+m_typeName+" cannot parse type "+typeName+"!");
+ }
+ }
+
+
+ public void writeSQL(SQLOutput stream) throws SQLException {
+ // write size marker
+ stream.writeInt(writer.estimateBytes(geom));
+
+ // write geometry
+ writer.writeGeometry(geom, stream);
+ }
+}
Added: packages/postgis/upstream/java/pljava/src/org/postgis/pljava/PLJtsParser.java
===================================================================
--- packages/postgis/upstream/java/pljava/src/org/postgis/pljava/PLJtsParser.java 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/pljava/src/org/postgis/pljava/PLJtsParser.java 2006-10-31 20:52:30 UTC (rev 577)
@@ -0,0 +1,225 @@
+/*
+ * JtsBinaryParser.java
+ *
+ * Binary Parser for JTS - relies on org.postgis V1.0.0+ package.
+ *
+ * (C) 2005 Markus Schaber, markus.schaber at logix-tt.com
+ *
+ * This library is free software; you can redistribute it and/or modify it under
+ * the terms of the GNU Lesser General Public License as published by the Free
+ * Software Foundation, either version 2.1 of the License.
+ *
+ * This library is distributed in the hope that it will be useful, but WITHOUT
+ * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+ * FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more
+ * details.
+ *
+ * You should have received a copy of the GNU Lesser General Public License
+ * along with this library; if not, write to the Free Software Foundation, Inc.,
+ * 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA or visit the web at
+ * http://www.gnu.org.
+ *
+ * $Id: JtsBinaryParser.java 2407 2006-07-18 18:13:31Z mschaber $
+ */
+package org.postgis.pljava;
+
+import java.sql.SQLException;
+import java.sql.SQLInput;
+
+
+import com.vividsolutions.jts.geom.Coordinate;
+import com.vividsolutions.jts.geom.CoordinateSequence;
+import com.vividsolutions.jts.geom.Geometry;
+import com.vividsolutions.jts.geom.GeometryCollection;
+import com.vividsolutions.jts.geom.LineString;
+import com.vividsolutions.jts.geom.LinearRing;
+import com.vividsolutions.jts.geom.MultiLineString;
+import com.vividsolutions.jts.geom.MultiPoint;
+import com.vividsolutions.jts.geom.MultiPolygon;
+import com.vividsolutions.jts.geom.Point;
+import com.vividsolutions.jts.geom.Polygon;
+import com.vividsolutions.jts.geom.impl.PackedCoordinateSequence;
+
+/**
+ * Parse binary representation of geometries. Currently, only text rep (hexed)
+ * implementation is tested.
+ *
+ * It should be easy to add char[] and CharSequence ByteGetter instances,
+ * although the latter one is not compatible with older jdks.
+ *
+ * I did not implement real unsigned 32-bit integers or emulate them with long,
+ * as both java Arrays and Strings currently can have only 2^31-1 elements
+ * (bytes), so we cannot even get or build Geometries with more than approx.
+ * 2^28 coordinates (8 bytes each).
+ *
+ * @author Markus Schaber, markus.schaber at logix-tt.com
+ *
+ */
+public class PLJtsParser {
+
+ /** Parse a geometry
+ * @throws SQLException */
+ public Geometry parseGeometry(SQLInput data) throws SQLException {
+ return parseGeometry(data, 0, false);
+ }
+
+ /** Parse with a known geometry factory
+ * @throws SQLException */
+ protected Geometry parseGeometry(SQLInput data, int srid, boolean inheritSrid) throws SQLException {
+ int typeword = data.readByte() & 0xFF;
+
+ int realtype = typeword & 0x0F; // cut off high flag bits
+
+ boolean haveBBox = (typeword & 0x80) != 0;
+ boolean haveS = (typeword & 0x40) != 0;
+ boolean haveZ = (typeword & 0x20) != 0;
+ boolean haveM = (typeword & 0x10) != 0;
+
+ if (haveBBox) {
+ // skip bbox, currently ignored
+ data.readFloat();
+ data.readFloat();
+ data.readFloat();
+ data.readFloat();
+ }
+
+ if (haveS) {
+ int newsrid = data.readInt();
+ if (inheritSrid && newsrid != srid) {
+ throw new IllegalArgumentException("Inconsistent srids in complex geometry: " + srid + ", " + newsrid);
+ } else {
+ srid = newsrid;
+ }
+ } else if (!inheritSrid) {
+ srid = -1;
+ }
+
+ Geometry result;
+ switch (realtype) {
+ case org.postgis.Geometry.POINT:
+ result = parsePoint(data, haveZ, haveM);
+ break;
+ case org.postgis.Geometry.LINESTRING:
+ result = parseLineString(data, haveZ, haveM);
+ break;
+ case org.postgis.Geometry.POLYGON:
+ result = parsePolygon(data, haveZ, haveM, srid);
+ break;
+ case org.postgis.Geometry.MULTIPOINT:
+ result = parseMultiPoint(data, srid);
+ break;
+ case org.postgis.Geometry.MULTILINESTRING:
+ result = parseMultiLineString(data, srid);
+ break;
+ case org.postgis.Geometry.MULTIPOLYGON:
+ result = parseMultiPolygon(data, srid);
+ break;
+ case org.postgis.Geometry.GEOMETRYCOLLECTION:
+ result = parseCollection(data, srid);
+ break;
+ default:
+ throw new IllegalArgumentException("Unknown Geometry Type!");
+ }
+
+ result.setSRID(srid);
+
+ return result;
+ }
+
+ private Point parsePoint(SQLInput data, boolean haveZ, boolean haveM) throws SQLException {
+ double X = data.readDouble();
+ double Y = data.readDouble();
+ Point result;
+ if (haveZ) {
+ double Z = data.readDouble();
+ result = PLJGeometry.geofac.createPoint(new Coordinate(X, Y, Z));
+ } else {
+ result = PLJGeometry.geofac.createPoint(new Coordinate(X, Y));
+ }
+
+ if (haveM) { // skip M value
+ data.readDouble();
+ }
+
+ return result;
+ }
+
+ /** Parse an Array of "full" Geometries
+ * @throws SQLException */
+ private void parseGeometryArray(SQLInput data, Geometry[] container, int srid) throws SQLException {
+ for (int i = 0; i < container.length; i++) {
+ container[i] = parseGeometry(data, srid, true);
+ }
+ }
+
+ /**
+ * Parse an Array of "slim" Points (without endianness and type, part of
+ * LinearRing and Linestring, but not MultiPoint!
+ *
+ * @param haveZ
+ * @param haveM
+ * @throws SQLException
+ */
+ private CoordinateSequence parseCS(SQLInput data, boolean haveZ, boolean haveM) throws SQLException {
+ int count = data.readInt();
+ int dims = haveZ ? 3 : 2;
+ CoordinateSequence cs = new PackedCoordinateSequence.Double(count, dims);
+
+ for (int i = 0; i < count; i++) {
+ for (int d = 0; d < dims; d++) {
+ cs.setOrdinate(i, d, data.readDouble());
+ }
+ if (haveM) { // skip M value
+ data.readDouble();
+ }
+ }
+ return cs;
+ }
+
+ private MultiPoint parseMultiPoint(SQLInput data, int srid) throws SQLException {
+ Point[] points = new Point[data.readInt()];
+ parseGeometryArray(data, points, srid);
+ return PLJGeometry.geofac.createMultiPoint(points);
+ }
+
+ private LineString parseLineString(SQLInput data, boolean haveZ, boolean haveM) throws SQLException {
+ return PLJGeometry.geofac.createLineString(parseCS(data, haveZ, haveM));
+ }
+
+ private LinearRing parseLinearRing(SQLInput data, boolean haveZ, boolean haveM) throws SQLException {
+ return PLJGeometry.geofac.createLinearRing(parseCS(data, haveZ, haveM));
+ }
+
+ private Polygon parsePolygon(SQLInput data, boolean haveZ, boolean haveM, int srid) throws SQLException {
+ int holecount = data.readInt() - 1;
+ LinearRing[] rings = new LinearRing[holecount];
+ LinearRing shell = parseLinearRing(data, haveZ, haveM);
+ shell.setSRID(srid);
+ for (int i = 0; i < holecount; i++) {
+ rings[i] = parseLinearRing(data, haveZ, haveM);
+ rings[i].setSRID(srid);
+ }
+ return PLJGeometry.geofac.createPolygon(shell, rings);
+ }
+
+ private MultiLineString parseMultiLineString(SQLInput data, int srid) throws SQLException {
+ int count = data.readInt();
+ LineString[] strings = new LineString[count];
+ parseGeometryArray(data, strings, srid);
+ return PLJGeometry.geofac.createMultiLineString(strings);
+ }
+
+ private MultiPolygon parseMultiPolygon(SQLInput data, int srid) throws SQLException {
+ int count = data.readInt();
+ Polygon[] polys = new Polygon[count];
+ parseGeometryArray(data, polys, srid);
+ return PLJGeometry.geofac.createMultiPolygon(polys);
+ }
+
+ private GeometryCollection parseCollection(SQLInput data, int srid) throws SQLException {
+ int count = data.readInt();
+ Geometry[] geoms = new Geometry[count];
+ parseGeometryArray(data, geoms, srid);
+ return PLJGeometry.geofac.createGeometryCollection(geoms);
+ }
+}
Added: packages/postgis/upstream/java/pljava/src/org/postgis/pljava/PLJtsWriter.java
===================================================================
--- packages/postgis/upstream/java/pljava/src/org/postgis/pljava/PLJtsWriter.java 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/pljava/src/org/postgis/pljava/PLJtsWriter.java 2006-10-31 20:52:30 UTC (rev 577)
@@ -0,0 +1,329 @@
+/*
+ * JtsBinaryWriter.java
+ *
+ * PostGIS extension for PostgreSQL JDBC driver - Binary Writer
+ *
+ * (C) 2005 Markus Schaber, markus.schaber at logix-tt.com
+ *
+ * This library is free software; you can redistribute it and/or modify it under
+ * the terms of the GNU Lesser General Public License as published by the Free
+ * Software Foundation, either version 2.1 of the License.
+ *
+ * This library is distributed in the hope that it will be useful, but WITHOUT
+ * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+ * FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more
+ * details.
+ *
+ * You should have received a copy of the GNU Lesser General Public License
+ * along with this library; if not, write to the Free Software Foundation, Inc.,
+ * 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA or visit the web at
+ * http://www.gnu.org.
+ *
+ * $Id: JtsBinaryWriter.java 2410 2006-07-19 13:31:18Z mschaber $
+ */
+package org.postgis.pljava;
+
+import java.sql.SQLException;
+import java.sql.SQLOutput;
+
+import com.vividsolutions.jts.geom.CoordinateSequence;
+import com.vividsolutions.jts.geom.Geometry;
+import com.vividsolutions.jts.geom.GeometryCollection;
+import com.vividsolutions.jts.geom.LineString;
+import com.vividsolutions.jts.geom.MultiLineString;
+import com.vividsolutions.jts.geom.MultiPoint;
+import com.vividsolutions.jts.geom.MultiPolygon;
+import com.vividsolutions.jts.geom.Point;
+import com.vividsolutions.jts.geom.Polygon;
+
+
+/**
+ * Create binary representation of geometries. Currently, only text rep (hexed)
+ * implementation is tested. Supports only 2 dimensional geometries.
+ *
+ * It should be easy to add char[] and CharSequence ByteGetter instances,
+ * although the latter one is not compatible with older jdks.
+ *
+ * I did not implement real unsigned 32-bit integers or emulate them with long,
+ * as both java Arrays and Strings currently can have only 2^31-1 elements
+ * (bytes), so we cannot even get or build Geometries with more than approx.
+ * 2^28 coordinates (8 bytes each).
+ *
+ * @author markus.schaber at logi-track.com
+ *
+ */
+public class PLJtsWriter {
+
+ public void writeBinary(Geometry geom, SQLOutput dest) throws SQLException {
+ writeGeometry(geom, dest);
+ }
+
+ /** Parse a geometry starting at offset.
+ * @throws SQLException */
+ protected void writeGeometry(Geometry geom, SQLOutput dest) throws SQLException {
+ // TODO: Add bbox
+ // TODO: Add proper handling of Measures
+
+
+ final int dimension = getCoordDim(geom);
+ if (dimension < 2 || dimension > 4) {
+ throw new IllegalArgumentException("Unsupported geometry dimensionality: " + dimension);
+ }
+
+ // write typeword
+ final int plaintype = getWKBType(geom);
+ byte typeword = (byte)plaintype;
+ if (dimension == 3 || dimension == 4) {
+ typeword |= 0x20;
+ }
+ if (dimension == 4) {
+ typeword |= 0x10;
+ }
+ if (checkSrid(geom)) {
+ typeword |= 0x40;
+ }
+
+ dest.writeByte(typeword);
+
+ if (checkSrid(geom)) {
+ dest.writeInt(geom.getSRID());
+ }
+
+ switch (plaintype) {
+ case org.postgis.Geometry.POINT:
+ writePoint((Point) geom, dest);
+ break;
+ case org.postgis.Geometry.LINESTRING:
+ writeLineString((LineString) geom, dest);
+ break;
+ case org.postgis.Geometry.POLYGON:
+ writePolygon((Polygon) geom, dest);
+ break;
+ case org.postgis.Geometry.MULTIPOINT:
+ writeMultiPoint((MultiPoint) geom, dest);
+ break;
+ case org.postgis.Geometry.MULTILINESTRING:
+ writeMultiLineString((MultiLineString) geom, dest);
+ break;
+ case org.postgis.Geometry.MULTIPOLYGON:
+ writeMultiPolygon((MultiPolygon) geom, dest);
+ break;
+ case org.postgis.Geometry.GEOMETRYCOLLECTION:
+ writeCollection((GeometryCollection) geom, dest);
+ break;
+ default:
+ throw new IllegalArgumentException("Unknown Geometry Type: " + plaintype);
+ }
+ }
+
+ public static int getWKBType(Geometry geom) {
+ if (geom instanceof Point) {
+ return org.postgis.Geometry.POINT;
+ } else if (geom instanceof com.vividsolutions.jts.geom.LineString) {
+ return org.postgis.Geometry.LINESTRING;
+ } else if (geom instanceof com.vividsolutions.jts.geom.Polygon) {
+ return org.postgis.Geometry.POLYGON;
+ } else if (geom instanceof MultiPoint) {
+ return org.postgis.Geometry.MULTIPOINT;
+ } else if (geom instanceof MultiLineString) {
+ return org.postgis.Geometry.MULTILINESTRING;
+ } else if (geom instanceof com.vividsolutions.jts.geom.MultiPolygon) {
+ return org.postgis.Geometry.MULTIPOLYGON;
+ } else if (geom instanceof com.vividsolutions.jts.geom.GeometryCollection) {
+ return org.postgis.Geometry.GEOMETRYCOLLECTION;
+ } else {
+ throw new IllegalArgumentException("Unknown Geometry Type: " + geom.getClass().getName());
+ }
+ }
+
+ /**
+ * Writes a "slim" Point (without endiannes, srid ant type, only the
+ * ordinates and measure. Used by writeGeometry.
+ * @throws SQLException
+ */
+ private void writePoint(Point geom, SQLOutput dest) throws SQLException {
+ writeCoordinates(geom.getCoordinateSequence(), getCoordDim(geom), dest);
+ }
+
+ /**
+ * Write a Coordinatesequence, part of LinearRing and Linestring, but not
+ * MultiPoint!
+ * @throws SQLException
+ */
+ private void writeCoordinates(CoordinateSequence seq, int dims, SQLOutput dest) throws SQLException {
+ for (int i = 0; i < seq.size(); i++) {
+ for (int d = 0; d < dims; d++) {
+ dest.writeDouble(seq.getOrdinate(i, d));
+ }
+ }
+ }
+
+ private void writeMultiPoint(MultiPoint geom, SQLOutput dest) throws SQLException {
+ dest.writeInt(geom.getNumPoints());
+ for (int i = 0; i < geom.getNumPoints(); i++) {
+ writeGeometry(geom.getGeometryN(i), dest);
+ }
+ }
+
+ private void writeLineString(LineString geom, SQLOutput dest) throws SQLException {
+ dest.writeInt(geom.getNumPoints());
+ writeCoordinates(geom.getCoordinateSequence(), getCoordDim(geom), dest);
+ }
+
+ private void writePolygon(Polygon geom, SQLOutput dest) throws SQLException {
+ dest.writeInt(geom.getNumInteriorRing() + 1);
+ writeLineString(geom.getExteriorRing(), dest);
+ for (int i = 0; i < geom.getNumInteriorRing(); i++) {
+ writeLineString(geom.getInteriorRingN(i), dest);
+ }
+ }
+
+ private void writeMultiLineString(MultiLineString geom, SQLOutput dest) throws SQLException {
+ writeGeometryArray(geom, dest);
+ }
+
+ private void writeMultiPolygon(MultiPolygon geom, SQLOutput dest) throws SQLException {
+ writeGeometryArray(geom, dest);
+ }
+
+ private void writeCollection(GeometryCollection geom, SQLOutput dest) throws SQLException {
+ writeGeometryArray(geom, dest);
+ }
+
+ private void writeGeometryArray(Geometry geom, SQLOutput dest) throws SQLException {
+ dest.writeInt(geom.getNumGeometries());
+ for (int i = 0; i < geom.getNumGeometries(); i++) {
+ writeGeometry(geom.getGeometryN(i), dest);
+ }
+ }
+
+ /** Estimate how much bytes a geometry will need in WKB. */
+ protected int estimateBytes(Geometry geom) {
+ // Todo: include bbox
+ int result = 0;
+
+ // write type byte
+ result += 1;
+
+ if (checkSrid(geom)) {
+ result += 4;
+ }
+
+ switch (getWKBType(geom)) {
+ case org.postgis.Geometry.POINT:
+ result += estimatePoint((Point) geom);
+ break;
+ case org.postgis.Geometry.LINESTRING:
+ result += estimateLineString((LineString) geom);
+ break;
+ case org.postgis.Geometry.POLYGON:
+ result += estimatePolygon((Polygon) geom);
+ break;
+ case org.postgis.Geometry.MULTIPOINT:
+ result += estimateMultiPoint((MultiPoint) geom);
+ break;
+ case org.postgis.Geometry.MULTILINESTRING:
+ result += estimateMultiLineString((MultiLineString) geom);
+ break;
+ case org.postgis.Geometry.MULTIPOLYGON:
+ result += estimateMultiPolygon((MultiPolygon) geom);
+ break;
+ case org.postgis.Geometry.GEOMETRYCOLLECTION:
+ result += estimateCollection((GeometryCollection) geom);
+ break;
+ default:
+ throw new IllegalArgumentException("Unknown Geometry Type: " + getWKBType(geom));
+ }
+ return result;
+ }
+
+ private boolean checkSrid(Geometry geom) {
+ final int srid = geom.getSRID();
+ // SRID is default 0 with jts geometries
+ return (srid != -1) && (srid != 0);
+ }
+
+ private int estimatePoint(Point geom) {
+ return 8 * getCoordDim(geom);
+ }
+
+ /** Write an Array of "full" Geometries */
+ private int estimateGeometryArray(Geometry container) {
+ int result = 0;
+ for (int i = 0; i < container.getNumGeometries(); i++) {
+ result += estimateBytes(container.getGeometryN(i));
+ }
+ return result;
+ }
+
+ /**
+ * Estimate an Array of "slim" Points (without endianness and type, part of
+ * LinearRing and Linestring, but not MultiPoint!
+ */
+ private int estimatePointArray(int length, Point example) {
+ // number of points
+ int result = 4;
+
+ // And the amount of the points itsself, in consistent geometries
+ // all points have equal size.
+ if (length > 0) {
+ result += length * estimatePoint(example);
+ }
+ return result;
+ }
+
+ /** Estimate an array of "fat" Points */
+ private int estimateMultiPoint(MultiPoint geom) {
+ // int size
+ int result = 4;
+ if (geom.getNumGeometries() > 0) {
+ // We can shortcut here, compared to estimateGeometryArray, as all
+ // subgeoms have the same fixed size
+ result += geom.getNumGeometries() * estimateBytes(geom.getGeometryN(0));
+ }
+ return result;
+ }
+
+ private int estimateLineString(LineString geom) {
+ if (geom == null || geom.getNumGeometries() == 0) {
+ return 0;
+ } else {
+ return estimatePointArray(geom.getNumPoints(), geom.getStartPoint());
+ }
+ }
+
+ private int estimatePolygon(Polygon geom) {
+ // int length
+ int result = 4;
+ result += estimateLineString(geom.getExteriorRing());
+ for (int i = 0; i < geom.getNumInteriorRing(); i++) {
+ result += estimateLineString(geom.getInteriorRingN(i));
+ }
+ return result;
+ }
+
+ private int estimateMultiLineString(MultiLineString geom) {
+ // 4-byte count + subgeometries
+ return 4 + estimateGeometryArray(geom);
+ }
+
+ private int estimateMultiPolygon(MultiPolygon geom) {
+ // 4-byte count + subgeometries
+ return 4 + estimateGeometryArray(geom);
+ }
+
+ private int estimateCollection(GeometryCollection geom) {
+ // 4-byte count + subgeometries
+ return 4 + estimateGeometryArray(geom);
+ }
+
+ public static final int getCoordDim(Geometry geom) {
+ // TODO: Fix geometries with more dimensions
+ // geom.getFactory().getCoordinateSequenceFactory()
+ if (geom == null) {
+ return 0;
+ } else {
+ return 2;
+ }
+ }
+}
Added: packages/postgis/upstream/java/pljava/update.sh
===================================================================
--- packages/postgis/upstream/java/pljava/update.sh 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/java/pljava/update.sh 2006-10-31 20:52:30 UTC (rev 577)
@@ -0,0 +1,13 @@
+#!/bin/sh
+
+ant 1>&2
+
+cat <<EOF
+
+set search_path to public;
+
+SELECT sqlj.replace_jar('file://${PWD}/postgis_pljava.jar', 'postgis_pljava_jar', false);
+
+EOF
+
+cat functions.sql
Modified: packages/postgis/upstream/loader/README.pgsql2shp
===================================================================
--- packages/postgis/upstream/loader/README.pgsql2shp 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/loader/README.pgsql2shp 2006-10-31 20:52:30 UTC (rev 577)
@@ -1,54 +1,100 @@
-pgsql2shp - Convert PostGIS Table to Shape
-~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+pgsql2shp(1) PostGIS pgsql2shp(1)
-VERSION: 0.7 (2002/05/04)
-MORE INFORMATION: http://postgis.refractions.net
-INTRODUCTION:
-This program takes PostGIS spatial tables and outputs ESRI
-shape files.
+NAME
+ pgsql2shp - postgis to shapefile dumper
-This application uses functionality from shapelib 1.2.9
-by Frank Warmerdam <warmerda at gdal.velocet.ca> to write to ESRI
-Shape files.
+SYNTAX
+ pgsql2shp [options] database [schema.]table
+ pgsql2shp [options] database query
-INSTALLATION:
-To build pgsql2shp just run 'make'.
-Copy the binary wherever you like. :)
+DESCRIPTION
+ The pgsql2shp table dumper connects directly to the database and con-
+ verts a table (possibly created by user query) into a shape file. It is
+ compatible with all versions of PostGIS.
+ Version: 1.1.5 (2006/10/06)
-USAGE:
-pgsql2shp [<options>] <database> <table>
+USAGE
+ The <database> is the name of the database to connect to.
-The <database> is the name of the database to connect to.
-The <table> is the table to read spatial data from.
+ The <table> is the (optionally schema-qualified) table to read spatial
+ data from. Alternatively, you can specify a QUERY whose result will be
+ written into the shapefile.
-Options:
- -d: set the dump file to be 3 dimensional, the default is 2d only.
- -f <filename>: Use this option to specify the specific name of the
- file to create. If not specified the file will be named after
- the table you dumped with shpafile extensions on it.
+OPTIONS
+ The commandline options are:
- -h <host>: allows you to specify what machine the database is on.
- The default machine if not specifid is the localhost.
+ -f <filename>
+ Write the output to a particular filename.
- -p <port>: allows you to specify a which database port to connect to.
- The default if not given is port 5432.
+ -h <host>
+ The database host to connect to.
- -P <password>: Connect to the database with the specified password.
+ -p <port>
+ The port to connect to on the database host.
- -u <user>: Connect to the database as the specified user.
+ -P <password>
+ The password to use when connecting to the database.
- -g <geometry_column> Specify the geometry column to be exported.
+ -u <user>
+ The username to use when connecting to the database.
+ -g <geometry column>
+ In the case of tables with multiple geometry columns, the geome-
+ try column to use when writing the shape file.
-EXAMPLES:
+ -b Use a binary cursor. When used on pre-1.0.0 PostGIS versions
+ this will reduce the likelihood of coordinate drift due to con-
+ version to and from WKT format. Coordinate drifts will not occur
+ with PostGIS 1.0.0 and newer versions. It will be slightly
+ faster, but might fail if any NON-gemetry column lacks a cast to
+ text.
- pgsql2shp -f myfile -p 5555 my_db roads_table
+ -r Raw mode. Do not drop the gid field, or escape column names.
+ -d For backward compatibility: write a 3-dimensional shape file
+ when dumping from old (pre-1.0.0) postgis databases (the default
+ is to write a 2-dimensional shape file in that case). Starting
+ from postgis-1.0.0+, dimensions are fully encoded.
+ -k Keep idendifiers case (don't uppercase field names).
+
+
+INSTALLATION
+ To compile the program from source, simply run "make" in the source
+ directory. Then copy the binary in your shell search path (or wherever
+ you like). This text is also available as a man page in the ../doc/man/
+ directory, ready for copying it into the manual search path on unixoid
+ systems.
+
+
+EXAMPLES
+ An example session using the dumper to create shape file from a
+ database might look like this:
+
+ # pgsql2shp -f myfile -p 5555 my_db roads_table
+
+
+AUTHORS
+ Originally written by Jeff Lounsbury <jeffloun at refractions.net>.
+ Improved and maintained by Sandro Santilli <strk at refractions.net>.
+ Includes small contributions and improvements by others.
+
+ This application uses functionality from shapelib 1.2.9 by Frank
+ Warmerdam <warmerda at gdal.velocet.ca> to write to ESRI Shape files.
+
+
+SEE ALSO
+ shp2pgsql(1)
+
+ More information is available at http://postgis.refractions.net
+
+
+
+ pgsql2shp(1)
Modified: packages/postgis/upstream/loader/README.shp2pgsql
===================================================================
--- packages/postgis/upstream/loader/README.shp2pgsql 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/loader/README.shp2pgsql 2006-10-31 20:52:30 UTC (rev 577)
@@ -1,76 +1,128 @@
-shp2pgsql - Convert Shape file to PostGIS
-~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+shp2pgsql(1) PostGIS shp2pgsql(1)
-VERSION: 0.7 (2002/05/04)
-MORE INFORMATION: http://postgis.refractions.net
-INTRODUCTION:
-This program takes in ESRI shape files and output formatted text suitable
-for uploading to the PostGIS/PostgreSQL spatial database using the psql
-terminal monitor.
+NAME
+ shp2pgsql - shapefile to postgis loader
-This application uses functionality from shapelib 1.2.9
-by Frank Warmerdam <warmerda at gdal.velocet.ca> to read from ESRI
-Shape files.
+SYNTAX
+ shp2pgsql [options] shapefile [schema.]table
-INSTALLATION:
-To build shp2pgsql just run 'make'.
-Copy the binary wherever you like. :)
+DESCRIPTION
+ The shp2pgsql data loader converts ESRI Shape files into SQL suitable
+ for insertion into a PostGIS/PostgreSQL database.
+ Version: 1.1.5 (2006/10/06)
-USAGE:
-shp2pgsql [<options>] <shapefile> <tablename> <database name>
+USAGE
+ The <shapefile> is the name of the shape file, without any extension
+ information. For example, 'roads' would be the name of the shapefile
+ comprising the 'roads.shp', 'roads.shx', and 'roads.dbf' files.
-The <shapefile> is the name of the shape file, without any extension
-information. For example, 'roads' would be the name of the shapefile
-comprising the 'roads.shp', 'roads.shx', and 'roads.dbf' files.
+ The <tablename> is the (optionally schema-qualified) name of the
+ database table you want the data stored in in the database. Within that
+ table, the geometry will be placed in the 'geo_value' column by
+ default.
-The <tablename> is the name of the database table you want the data stored
-in in the database. Within that table, the geometry will be placed in
-the 'geo_value' column by default.
-The <database name> is the name of the database you are going to put the
-the data into.
+OPTIONS
+ The loader has several operating modes distinguished by command line
+ flags:
-The options are as follows:
+ (Note that -a, -c, -d and -p are mutually exclusive.)
-(-a || -c || -d || -p) these options are mutually exclusive.
+ -d Drops the database table before creating a new table with the
+ data in the Shape file.
- -a Append mode. Do not delete the target table or try to create
- a new table, simple insert the data into the existing table.
- A table will have to exist for this to work, it is usually
- used after a create mode as been run once or after -p. (mutually
- exclusive with -c, -d and -p)
- -c Create mode. This is the default mode is no other is specified.
- Create a new table and upload the data into that table.
- (mutually eclusive with -a, -d and -p)
- -d Delete mode. Delete the database table named <tablename>, then
- create a new one with that name before uploading the data into
- the new empty database table. (mutually exclusive with -a, -c
- and -p)
- -p Prepare mode. Read the table schema from the shape file and
- create the new table, but do not insert any data. (mutually
- exclusive with -a, -c and -d)
+ -a Appends data from the Shape file into the database table. Note
+ that to use this option to load multiple files, the files must
+ have the same attributes and same data types.
- -D Dump. When inserting the data into the table use 'dump' format.
- Dump format is used by PostgreSQL for large data dumps and
- uploads. Use this mode if your upload dataset is very large.
- (you may still specify -a,-c or -d in conjunction with -D)
+ -c Creates a new table and populates it from the Shape file. This
+ is the default mode.
+ -p Only produces the table creation SQL code, without adding any
+ actual data. This can be used if you need to completely sepa-
+ rate the table creation and data loading steps.
-EXAMPLES:
+ -D Use the PostgreSQL "dump" format for the output data. This can
+ be combined with -a, -c and -d. It is much faster to load than
+ the default "insert" SQL format. Use this for very large data
+ sets.
-Loading directly:
+ -s <SRID>
+ Creates and populates the geometry tables with the specified
+ SRID.
- shp2pgsql -c roads1 roads_table my_db | psql -d my_db
- shp2pgsql -a roads2 roads_table my_db | psql -d my_db
+ -g <geometry_column>
+ Specify the name of the geometry column (mostly useful in append
+ mode).
-Saving to an intermiate file using the 'dump' format:
+ -k Keep idendifiers case (column, schema and attributes). Note that
+ attributes in Shapefile are usually all UPPERCASE.
- shp2pgsql -D roads1 roads_table my_db > roads.sql
- psql -d my_db -f roads.sql
+ -i Coerce all integers to standard 32-bit integers, do not create
+ 64-bit bigints, even if the DBF header signature appears to war-
+ rant it.
+ -S Generate simple Geometries instead of MULTIgeometries. Shape
+ files don't differ between LINESTRINGs and MULTILINESTRINGs, so
+ shp2pgsql generates MULTILINESTRINGs by default. This switch
+ will produce LINESTRINGs instead, but shp2pgsql will fail when
+ it hits a real MULTILINESTRING. The same works for POLYGONs vs.
+ MULTIPOLYGONs.
+
+ -w Output WKT format, for use with older (0.x) versions of PostGIS.
+ Note that this will introduce coordinate drifts and will drop M
+ values from shapefiles.
+
+ -W <encoding>
+ Specify the character encoding of Shapefile's attributes. If
+ this option is used the output will be encoded in UTF-8.
+
+ -I Create a GiST index on the geometry column.
+
+ -N <policy>
+ Specify NULL geometries handling policy (insert,skip,abort).
+
+
+INSTALLATION
+ To compile the program from source, simply run "make" in the source
+ directory. Then copy the binary in your shell search path (or wherever
+ you like). This text is also available as a man page in the ../doc/man/
+ directory, ready for copying it into the manual search path on unixoid
+ systems.
+
+
+EXAMPLES
+ An example session using the loader to create an input file and upload-
+ ing it might look like this:
+
+ # shp2pgsql shaperoads roadstable roadsdb > roads.sql
+ # psql -d roadsdb -f roads.sql
+
+ A conversion and upload can be done all in one step using UNIX pipes:
+
+ # shp2pgsql shaperoads roadstable roadsdb | psql -d roadsdb
+
+
+AUTHORS
+ Originally written by Jeff Lounsbury <jeffloun at refractions.net>.
+ Improved and maintained by Sandro Santilli <strk at refractions.net>.
+ Includes small contributions and improvements by others.
+
+ This application uses functionality from shapelib 1.2.9 by Frank
+ Warmerdam <warmerda at gdal.velocet.ca> to read from ESRI Shape files.
+
+
+SEE ALSO
+ pgsql2shp(1)
+
+ More information is available at http://postgis.refractions.net
+
+
+
+ shp2pgsql(1)
Added: packages/postgis/upstream/loader/README.txt
===================================================================
--- packages/postgis/upstream/loader/README.txt 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/loader/README.txt 2006-10-31 20:52:30 UTC (rev 577)
@@ -0,0 +1,12 @@
+This directory contains the loader and dumper utility programs.
+
+The loader can convert shape files to an SQL dump suitable for loading into a PostGIS enabled
+PostgreSQL database server. The dumper does the opposite, creates a shape file out of an PostGIS
+table or arbitrary query.
+
+To compile the program from source, simply run "make" in the source directory. Then copy the
+binary into your command search path (or wherever you like).
+
+For usage information, simply run the programs without any arguments, that will display a
+help screen, and look into the ../doc/man/ directory, there are manpages ready for copying
+into the manual search path on unixoid systems.
Modified: packages/postgis/upstream/loader/pgsql2shp.c
===================================================================
--- packages/postgis/upstream/loader/pgsql2shp.c 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/loader/pgsql2shp.c 2006-10-31 20:52:30 UTC (rev 577)
@@ -1,5 +1,5 @@
/**********************************************************************
- * $Id: pgsql2shp.c 2486 2006-09-27 08:24:08Z strk $
+ * $Id: pgsql2shp.c 2485 2006-09-27 08:23:40Z strk $
*
* PostGIS - Spatial Types for PostgreSQL
* http://postgis.refractions.net
@@ -19,7 +19,7 @@
**********************************************************************/
static char rcsid[] =
- "$Id: pgsql2shp.c 2486 2006-09-27 08:24:08Z strk $";
+ "$Id: pgsql2shp.c 2485 2006-09-27 08:23:40Z strk $";
#include <stdio.h>
#include <stdlib.h>
Modified: packages/postgis/upstream/loader/shp2pgsql.c
===================================================================
--- packages/postgis/upstream/loader/shp2pgsql.c 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/loader/shp2pgsql.c 2006-10-31 20:52:30 UTC (rev 577)
@@ -1,5 +1,5 @@
/**********************************************************************
- * $Id: shp2pgsql.c 2383 2006-06-16 14:12:17Z strk $
+ * $Id: shp2pgsql.c 2506 2006-10-11 11:19:54Z mschaber $
*
* PostGIS - Spatial Types for PostgreSQL
* http://postgis.refractions.net
@@ -69,6 +69,7 @@
/* globals */
int dump_format = 0; /* 0=insert statements, 1 = dump */
+int simple_geometries = 0; /* 0 = MULTILINESTRING/MULTIPOLYGON, 1 = LINESTRING/POLYGON */
int quoteidentifiers = 0;
int forceint4 = 0;
int createindex = 0;
@@ -137,7 +138,7 @@
static void print_wkb_double(double val);
static char rcsid[] =
- "$Id: shp2pgsql.c 2383 2006-06-16 14:12:17Z strk $";
+ "$Id: shp2pgsql.c 2506 2006-10-11 11:19:54Z mschaber $";
void *safe_malloc(size_t size)
{
@@ -739,7 +740,7 @@
fprintf(stderr, " -s <srid> Set the SRID field. If not specified it defaults to -1.\n");
fprintf(stderr, "\n");
fprintf(stderr, " (-d|a|c|p) These are mutually exclusive options:\n");
- fprintf(stderr, " -d Drops the table , then recreates it and populates\n");
+ fprintf(stderr, " -d Drops the table, then recreates it and populates\n");
fprintf(stderr, " it with current shape file data.\n");
fprintf(stderr, " -a Appends shape file into current table, must be\n");
fprintf(stderr, " exactly the same table schema.\n");
@@ -759,6 +760,8 @@
fprintf(stderr, "\n");
fprintf(stderr, " -I Create a GiST index on the geometry column.\n");
fprintf(stderr, "\n");
+ fprintf(stderr, " -S Generate simple geometries instead of MULTI geometries.\n");
+ fprintf(stderr, "\n");
fprintf(stderr, " -w Use wkt format (for postgis-0.x support - drops M - drifts coordinates).\n");
#ifdef USE_ICONV
fprintf(stderr, "\n");
@@ -792,9 +795,17 @@
if (!dump_format) printf("'");
if ( sr_id && sr_id != "-1" ) printf("SRID=%s;", sr_id);
- print_wkb_byte(getEndianByte());
- print_wkb_int(wkbtype);
- print_wkb_int(obj->nParts);
+ if (simple_geometries==0) // We write MULTI geometries, so generate Header
+ {
+ print_wkb_byte(getEndianByte());
+ print_wkb_int(wkbtype);
+ print_wkb_int(obj->nParts); /* npolys */
+ }
+ else if ((obj->nParts)!=1) // We write Non-MULTI geometries, but have several parts:
+ {
+ fprintf(stderr, "We have a MultiLineString with %d parts, can't use -S switch!\n", obj->nParts);
+ exit(1);
+ }
for (pi=0; pi<obj->nParts; pi++)
{
@@ -843,8 +854,22 @@
return;
}
- if (dump_format) printf("SRID=%s;MULTILINESTRING(",sr_id);
- else printf("GeometryFromText('MULTILINESTRING (");
+ if (dump_format) printf("SRID=%s;",sr_id );
+ else printf("GeometryFromText('");
+
+ if (simple_geometries==0) // We write MULTI geometries, so generate Header
+ {
+ printf("MULTILINESTRING(");
+ }
+ else if ((obj->nParts)==1)
+ {
+ printf("LINESTRING");
+ }
+ else // We write Non-MULTI geometries, but have several parts:
+ {
+ fprintf(stderr, "We have a Multilinestring with %d parts, can't use -S switch!\n", obj->nParts);
+ exit(1);
+ }
for (pi=0; pi<obj->nParts; pi++)
{
@@ -874,8 +899,10 @@
}
- if (dump_format) printf(")\n");
- else printf(")',%s) );\n",sr_id);
+ if (simple_geometries==0) printf(")");
+
+ if (dump_format) printf("\n");
+ else printf("',%s) );\n",sr_id);
}
int
@@ -1051,9 +1078,17 @@
if (!dump_format) printf("'");
if ( sr_id && sr_id != "-1" ) printf("SRID=%s;", sr_id);
- print_wkb_byte(getEndianByte());
- print_wkb_int(wkbtype);
- print_wkb_int(out_index); /* npolys */
+ if (simple_geometries==0) // We write MULTI geometries, so generate Header
+ {
+ print_wkb_byte(getEndianByte());
+ print_wkb_int(wkbtype);
+ print_wkb_int(out_index); /* npolys */
+ }
+ else if (out_index!=1) // We write Non-MULTI geometries, but have several parts:
+ {
+ fprintf(stderr, "We have a Multipolygon with %d parts, can't use -S switch!\n", out_index);
+ exit(1);
+ }
/* Write the coordinates */
for(pi=0; pi<out_index; pi++)
@@ -1112,8 +1147,22 @@
out_index = FindPolygons(obj, &Outer);
- if (dump_format) printf("SRID=%s;MULTIPOLYGON(",sr_id );
- else printf("GeometryFromText('MULTIPOLYGON(");
+ if (dump_format) printf("SRID=%s;",sr_id );
+ else printf("GeometryFromText('");
+
+ if (simple_geometries==0) // We write MULTI geometries, so generate Header
+ {
+ printf("MULTIPOLYGON(");
+ }
+ else if (out_index==1)
+ {
+ printf("POLYGON");
+ }
+ else
+ { // We write Non-MULTI geometries, but have several parts:
+ fprintf(stderr, "We have a Multipolygon with %d parts, can't use -S switch!\n", out_index);
+ exit(1);
+ }
/* Write the coordinates */
for(pi=0; pi<out_index; pi++)
@@ -1149,8 +1198,10 @@
}
- if (dump_format) printf(")\n");
- else printf(")',%s) );\n",sr_id);
+ if (simple_geometries==0) printf(")");
+
+ if (dump_format) printf("\n");
+ else printf("',%s) );\n",sr_id);
/* Release all memory */
ReleasePolygons(Outer, out_index);
@@ -1228,7 +1279,7 @@
extern char *optarg;
extern int optind;
- while ((c = getopt(ARGC, ARGV, "kcdapDs:g:iW:wIN:")) != EOF){
+ while ((c = getopt(ARGC, ARGV, "kcdapDs:Sg:iW:wIN:")) != EOF){
switch (c) {
case 'c':
if (opt == ' ')
@@ -1257,6 +1308,9 @@
case 'D':
dump_format =1;
break;
+ case 'S':
+ simple_geometries =1;
+ break;
case 's':
sr_id = optarg;
break;
@@ -1311,7 +1365,7 @@
if ( opt==' ' ) opt = 'c';
- for (; optind < ARGC; optind++){
+ for (; optind < ARGC; optind++){
if(curindex ==0){
shp_file = ARGV[optind];
}else if(curindex == 1){
@@ -1449,6 +1503,13 @@
shpfiletype);
break;
}
+
+ if (simple_geometries)
+ {
+ // adjust geometry name for CREATE TABLE by skipping MULTI
+ if ((wkbtype & 0x7) == MULTIPOLYGONTYPE) pgtype += 5;
+ if ((wkbtype & 0x7) == MULTILINETYPE) pgtype += 5;
+ }
}
char *
Modified: packages/postgis/upstream/lwgeom/SERIALIZED_FORM
===================================================================
--- packages/postgis/upstream/lwgeom/SERIALIZED_FORM 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/lwgeom/SERIALIZED_FORM 2006-10-31 20:52:30 UTC (rev 577)
@@ -64,9 +64,9 @@
If both objects are present the bounding box come first.
-Bounding box is composed by 4 16-bit float:
+Bounding box is composed by 4 32-bit float:
- [FLOAT16] [FLOAT16] [FLOAT16] [FLOAT16]
+ [FLOAT32] [FLOAT32] [FLOAT32] [FLOAT32]
xmin ymin xmax ymax
SRID is composed by a 32-bit integer:
@@ -78,24 +78,24 @@
==Ordinate Arrays==
-When it comes to ordinate values all geometries use arrays of 32-bit
+When it comes to ordinate values all geometries use arrays of 64-bit
floats. Number and semantic of values depend on the dimension flags
on the geometry type byte:
2D (ZM=0x00)
- [FLOAT32] [FLOAT32]
+ [FLOAT64] [FLOAT64]
x y
3DM (ZM=0x01)
- [FLOAT32] [FLOAT32] [FLOAT32]
+ [FLOAT64] [FLOAT64] [FLOAT64]
x y m
3DZ (ZM=0x10)
- [FLOAT32] [FLOAT32] [FLOAT32]
+ [FLOAT64] [FLOAT64] [FLOAT64]
x y z
4D (ZM=0x11)
- [FLOAT32] [FLOAT32] [FLOAT32] [FLOAT32]
+ [FLOAT64] [FLOAT64] [FLOAT64] [FLOAT64]
x y z m
Modified: packages/postgis/upstream/lwgeom/lwgeom_geos_c.c
===================================================================
--- packages/postgis/upstream/lwgeom/lwgeom_geos_c.c 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/lwgeom/lwgeom_geos_c.c 2006-10-31 20:52:30 UTC (rev 577)
@@ -2240,8 +2240,9 @@
POINTARRAY *
ptarray_from_GEOSCoordSeq(GEOSCoordSeq cs, char want3d)
{
- unsigned int dims=2;
- unsigned int size, i, ptsize;
+ size_t dims=2;
+ size_t size;
+ unsigned int i, ptsize;
uchar *points, *ptr;
POINTARRAY *ret;
Added: packages/postgis/upstream/make_dist.sh
===================================================================
--- packages/postgis/upstream/make_dist.sh 2006-10-25 18:33:48 UTC (rev 576)
+++ packages/postgis/upstream/make_dist.sh 2006-10-31 20:52:30 UTC (rev 577)
@@ -0,0 +1,88 @@
+#!/bin/sh
+
+#
+# USAGE:
+#
+# -- postgis-cvs.tar.gz
+# sh make_dist.sh
+#
+# -- postgis-1.1.0.tar.gz
+# sh make_dist.sh 1.1.0
+#
+# NOTE: will not work prior to 1.1.0
+#
+#
+
+tag=trunk
+version=cvs
+
+if [ -n "$1" ]; then
+ version="$1"
+ #version=`echo $version | sed 's/RC/-rc/'`
+ #tag=pgis_`echo "$version" | sed 's/\./_/g'`
+ tag="tags/$version"
+fi
+
+outdir="postgis-$version"
+package="postgis-$version.tar.gz"
+
+if [ -d "$outdir" ]; then
+ echo "Output directory $outdir already exist"
+ exit 1
+fi
+
+echo "Exporting tag $tag"
+#cvs export -r "$tag" -d "$outdir" postgis
+svn export "http://svn.refractions.net/postgis/$tag" "$outdir"
+if [ $? -gt 0 ]; then
+ exit 1
+fi
+
+# remove .cvsignore, make_dist.sh and HOWTO_RELEASE
+echo "Removing .cvsignore and make_dist.sh files"
+find "$outdir" -name .cvsignore -exec rm {} \;
+rm -f "$outdir"/make_dist.sh "$outdir"/HOWTO_RELEASE
+
+# generating configure script
+echo "Running autogen.sh; ./configure"
+owd="$PWD"
+cd "$outdir"
+./autogen.sh
+./configure
+cd "$owd"
+
+# generating documentation
+echo "Generating documentation"
+owd="$PWD"
+cd "$outdir"/doc
+sleep 2 # wait some time to have 'make' recognize it needs to build html
+make
+if [ $? -gt 0 ]; then
+ exit 1
+fi
+make clean # won't drop the html dir
+cd "$owd"
+
+## generating parser
+#echo "Generating parser"
+#owd="$PWD"
+#cd "$outdir"/lwgeom
+#make lex.yy.c
+#if [ $? -gt 0 ]; then
+# exit 1
+#fi
+#cd "$owd"
+
+# Run make distclean
+echo "Running make distclean"
+owd="$PWD"
+cd "$outdir"
+make distclean
+cd "$owd"
+
+echo "Generating $package file"
+tar czf "$package" "$outdir"
+
+#echo "Cleaning up"
+#rm -Rf "$outdir"
+
More information about the Pkg-grass-devel
mailing list