self-hosted/postgis
self-hosted/postgis
1
0
Fork 0
mirror of https://git.osgeo.org/gitea/postgis/postgis synced 2024-10-23 16:42:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

Initial support for documentatin translation

Browse source 
Adds "update-po" Makefile target under doc/
Adds "local-html" Makefile target under doc/po/<lang>

git-svn-id: http://svn.osgeo.org/postgis/trunk@10299 b70326c6-7e19-0410-871a-916f4a2858ee
This commit is contained in:
Sandro Santilli 2012-09-17 12:31:54 +00:00
parent 977cbf66c3
commit 0be4223e97
97 changed files with 161713 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
.gitignore vendored
View file

@ -16,6 +16,11 @@ doc/html/image_src/Makefile
doc/html/*.html
doc/Makefile
doc/Makefile.comments
doc/po/*/*.xml
doc/po/*/*.po~
doc/po/*/html
doc/po/*/xsl
doc/po/*/*_comments.sql
doc/postgis_aggs_mm.xml
doc/postgis_comments.sql
doc/postgis-out.xml

43
doc/Makefile.in
View file

@ -21,6 +21,7 @@
# that we could produce a large number of files (think chunked HTML)
#
translations = it_IT pt_BR
POSTGIS_MAJOR_VERSION=@POSTGIS_MAJOR_VERSION@
POSTGIS_MINOR_VERSION=@POSTGIS_MINOR_VERSION@
@ -68,6 +69,12 @@ DBLATEX=@DBLATEX@
# Imagemagick's convert utility program for generated images used in the documentation
IMAGEMAGICK=@IMAGEMAGICK@
# Gettext for translated documentation
MSGMERGE=msgmerge
# XML gettext tools
XML2POT=xml2pot
# Directories for postgresql subdirectories
PGSQL_DOCDIR=@PGSQL_DOCDIR@
PGSQL_MANDIR=@PGSQL_MANDIR@
@ -127,6 +134,26 @@ XML_GENERATED_SOURCES = \
XML_INPUTS = $(XML_SOURCES) $(XML_GENERATED_SOURCES)
XML_INPUTS_POT = $(XML_SOURCES:%.xml=po/templates/%.xml.pot)
$(XML_INPUTS_POT): po/templates/%.xml.pot: %.xml
$(XML2POT) $< > $@
# Creates or updates translation files
update-po: $(XML_INPUTS_POT)
@for lang in $(translations); do \
echo "Creating po files for language $$lang..." ; \
for pot in $(XML_INPUTS_POT); do \
mkdir -p po/$$lang; \
po=po/$$lang/`basename $$pot .pot`.po; \
if test -f $$po; then \
$(MSGMERGE) --update $$po $$pot; \
else \
cp $$pot $$po; \
fi; \
done; \
done
ifeq ($(XSLTPROC),)
postgis_aggs_mm.xml: requirements_not_met_xsltproc
else
@ -169,16 +196,22 @@ chunked-html: postgis-out.xml Makefile images $(XML_INPUTS)
$(CHUNK_HTML_DOCBOOK_XSL) \
$<
html: html/postgis.html
html: html/postgis$(DOCSUFFIX).html
html/postgis.html: postgis-out.xml Makefile images $(XML_INPUTS)
html-localized:
@for lang in $(translations); do \
echo "Creating html for language $$lang..."; \
$(MAKE) -C po/$$lang local-html; \
done
html/postgis$(DOCSUFFIX).html: postgis-out.xml Makefile images $(XML_INPUTS)
$(XSLTPROC) $(XSLTPROC_COMMONOPTS) $(XSLTPROC_HTMLOPTS) \
--output html/postgis.html \
--output html/postgis$(DOCSUFFIX).html \
$(HTML_DOCBOOK_XSL) \
$<
postgis-${POSTGIS_MAJOR_VERSION}.${POSTGIS_MINOR_VERSION}.${POSTGIS_MICRO_VERSION}.pdf: postgis-out.xml images $(XML_INPUTS)
postgis-${POSTGIS_MAJOR_VERSION}.${POSTGIS_MINOR_VERSION}.${POSTGIS_MICRO_VERSION}$(DOCSUFFIX).pdf: postgis-out.xml images $(XML_INPUTS)
if test x"$(DBLATEX)" = x; then \
echo "Error: dblatex not found, can't build pdf"; \
echo " try installing dblatex and then re-run configure"; \
@ -196,7 +229,7 @@ postgis-${POSTGIS_MAJOR_VERSION}.${POSTGIS_MINOR_VERSION}.${POSTGIS_MICRO_VERSIO
-o postgis-${POSTGIS_MAJOR_VERSION}.${POSTGIS_MINOR_VERSION}.${POSTGIS_MICRO_VERSION}.pdf $<; \
fi
pdf: postgis-${POSTGIS_MAJOR_VERSION}.${POSTGIS_MINOR_VERSION}.${POSTGIS_MICRO_VERSION}.pdf
pdf: postgis-${POSTGIS_MAJOR_VERSION}.${POSTGIS_MINOR_VERSION}.${POSTGIS_MICRO_VERSION}$(DOCSUFFIX).pdf
doxygen.cfg: doxygen.cfg.in
$(PERL) -lpe "s'@@LAST_RELEASE_VERSION@@'${POSTGIS_MAJOR_VERSION}.${POSTGIS_MINOR_VERSION}.${POSTGIS_MICRO_VERSION}'g" $< > $@

24
doc/po/Makefile.local Normal file
View file

@ -0,0 +1,24 @@
# This file should be included by the Makefile
# in each language directory
local-all: local-html comments
local-html: symlinks
$(MAKE) html
local-pdf: symlinks
$(MAKE) pdf
symlinks:
rm -f html; ln -s ../../html html
rm -f xsl; ln -s ../../xsl xsl
# for XML_SOURCES
include ../../Makefile
# XML gettext tools
PO2XML=po2xml
$(XML_SOURCES): %.xml: %.xml.po
$(PO2XML) ../../$@ $< > $@

11
doc/po/README Normal file
View file

@ -0,0 +1,11 @@
Translation files for the PostGIS manual.
Compilation of the files require the ``poxml`` package,
part of the KDE development kit.
Run ``make`` in language directories to generate the
localized manual.
Run ``make update-po`` from the parent directory to
update the translation files to be in sync with the
official documentation.

2
doc/po/it_IT/Makefile Normal file
View file

@ -0,0 +1,2 @@
DOCSUFFIX=-it
include ../Makefile.local

16
doc/po/it_IT/extras.xml.po Normal file
View file

@ -0,0 +1,16 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

260
doc/po/it_IT/extras_historytable.xml.po Normal file
View file

@ -0,0 +1,260 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: extras_historytable.xml:3
#, no-c-format
msgid "History Tracking"
msgstr ""
#. Tag: para
#: extras_historytable.xml:6
#, no-c-format
msgid ""
"Suppose you have a table of data that represents the current state of a "
"particular geographic feature. A parcels table, or a roads table, or a fruit "
"trees table, whatever. Generally, GIS tools understand a table as a single "
"entity into which they can update, insert and delete rows from. How you do "
"allow common GIS tools to work against your data, while maintaining an audit "
"trail of what changes have been made, by whom, and what the past state of "
"the data is?"
msgstr ""
#. Tag: para
#: extras_historytable.xml:10
#, no-c-format
msgid ""
"This <varname>history_table</varname> extra module provides some utility "
"functions for creating and maintaining history."
msgstr ""
#. Tag: para
#: extras_historytable.xml:14
#, no-c-format
msgid ""
"The <varname>history_table</varname> was also packaged in PostGIS 1.5, but "
"added to the documentation in PostGIS 2.0. This package is written in "
"plpgsql and located in the <varname>extras/history_table</varname> of "
"PostGIS source tar balls and source repository."
msgstr ""
#. Tag: para
#: extras_historytable.xml:15
#, no-c-format
msgid ""
"If you have a table 'roads', this module will maintain a 'roads_history' "
"side table, which contains all the columns of the parent table, and the "
"following additional columns:"
msgstr ""
#. Tag: programlisting
#: extras_historytable.xml:16
#, no-c-format
msgid ""
"history_id | integer | not null default \n"
" date_added | timestamp without time zone | not null default now()\n"
" date_deleted | timestamp without time zone | \n"
" last_operation | character varying(30) | not null\n"
" active_user | character varying(90) | not null default "
"\"current_user\"()\n"
" current_version | text | not null"
msgstr ""
#. Tag: para
#: extras_historytable.xml:20
#, no-c-format
msgid ""
"When you insert a new record into 'roads' a record is automatically inserted "
"into 'roads_history', with the 'date_added' filled in the 'date_deleted' set "
"to NULL, a unique 'history_id', a 'last_operation' of 'INSERT' and "
"'active_user' set."
msgstr ""
#. Tag: para
#: extras_historytable.xml:23
#, no-c-format
msgid ""
"When you delete a record in 'roads', the record in the history table is "
"*not* deleted, but the 'date_deleted' is set to the current date."
msgstr ""
#. Tag: para
#: extras_historytable.xml:26
#, no-c-format
msgid ""
"When you update a record in 'roads', the current record has 'date_deleted' "
"filled in and a new record is created with the 'date_added' set and "
"'date_deleted' NULL."
msgstr ""
#. Tag: para
#: extras_historytable.xml:30
#, no-c-format
msgid ""
"With this information maintained, it is possible to retrieve the history of "
"any record in the roads table:"
msgstr ""
#. Tag: programlisting
#: extras_historytable.xml:31
#, no-c-format
msgid "SELECT * FROM roads_history WHERE roads_pk = 111;"
msgstr ""
#. Tag: para
#: extras_historytable.xml:33
#, no-c-format
msgid "Or, to retrieve a view of the roads table at any point in the past:"
msgstr ""
#. Tag: programlisting
#: extras_historytable.xml:34
#, no-c-format
msgid ""
"SELECT * FROM roads_history \n"
" WHERE date_added &lt; 'January 1, 2001' AND \n"
" ( date_deleted &gt;= 'January 1, 2001' OR date_deleted IS NULL );"
msgstr ""
#. Tag: refname
#: extras_historytable.xml:38
#, no-c-format
msgid "Postgis_Install_History"
msgstr ""
#. Tag: refpurpose
#: extras_historytable.xml:39
#, no-c-format
msgid ""
"Creates a table that will hold some interesting values for managing history "
"tables."
msgstr ""
#. Tag: funcprototype
#: extras_historytable.xml:44
#, no-c-format
msgid ""
"<funcdef>void <function>Postgis_Install_History</function></funcdef> "
"<paramdef></paramdef>"
msgstr ""
#. Tag: title
#: extras_historytable.xml:52 extras_historytable.xml:92
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: extras_historytable.xml:54
#, no-c-format
msgid ""
"Creates a table that will hold some interesting values for managing history "
"tables. Creates a table called <varname>historic_information</varname>"
msgstr ""
#. Tag: para
#: extras_historytable.xml:58 extras_historytable.xml:100
#, no-c-format
msgid "Availability: 1.5.0"
msgstr ""
#. Tag: title
#: extras_historytable.xml:63 extras_historytable.xml:105
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: programlisting
#: extras_historytable.xml:65
#, no-c-format
msgid "SELECT postgis_install_history();"
msgstr ""
#. Tag: title
#: extras_historytable.xml:71 extras_historytable.xml:113
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: refname
#: extras_historytable.xml:77
#, no-c-format
msgid "Postgis_Enable_History"
msgstr ""
#. Tag: refpurpose
#: extras_historytable.xml:78
#, no-c-format
msgid ""
"Registers a tablein the history_information table for tracking and also adds "
"in side line history table and insert, update, delete rules on the table."
msgstr ""
#. Tag: funcprototype
#: extras_historytable.xml:83
#, no-c-format
msgid ""
"<funcdef>boolean <function>Postgis_Enable_History</function></funcdef> "
"<paramdef><type>text </type> <parameter>p_schema</parameter></paramdef> "
"<paramdef><type>text </type> <parameter>p_table</parameter></paramdef>"
msgstr ""
#. Tag: para
#: extras_historytable.xml:94
#, no-c-format
msgid ""
"Registers a table in the history_information table for tracking and also "
"adds in side line history table with same name as table but prefixed with "
"<varname>history</varname> in the same schema as the original table. Puts in "
"insert, update, delete rules on the table. Any inserts,updates,deletes of "
"the geometry are recorded in the history table."
msgstr ""
#. Tag: para
#: extras_historytable.xml:97
#, no-c-format
msgid ""
"This function currently relies on a geometry column being registered in "
"<varname>geometry_columns</varname> and fails if the geometry column is not "
"present in <varname>geometry_columns</varname> table."
msgstr ""
#. Tag: programlisting
#: extras_historytable.xml:107
#, no-c-format
msgid ""
"CREATE TABLE roads(gid SERIAL PRIMARY KEY, road_name varchar(150));\n"
"SELECT AddGeometryColumn('roads', 'geom', 26986, 'LINESTRING', 2);\n"
" \n"
"SELECT postgis_enable_history('public', 'roads', 'geom') As register_table;\n"
"register_table\n"
"--------------\n"
"t\n"
"\n"
"INSERT INTO roads(road_name, geom) \n"
" VALUES('Test Street', ST_GeomFromText('LINESTRING(231660.5 832170,231647 "
"832202,231627.5 832250.5)',26986));\n"
"\n"
"-- check transaction detail --\n"
"SELECT date_added, last_operation, current_version \n"
"FROM roads_history \n"
"WHERE road_name = 'Test Street' ORDER BY date_added DESC;\n"
"\n"
" date_added | last_operation | current_version\n"
"------------------------+----------------+-----------------\n"
" 2011-02-07 12:44:36.92 | INSERT | 2"
msgstr ""

2161
doc/po/it_IT/extras_tigergeocoder.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

3792
doc/po/it_IT/extras_topology.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

667
doc/po/it_IT/faq.xml.po Normal file
View file

@ -0,0 +1,667 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: faq.xml:3
#, no-c-format
msgid "PostGIS Frequently Asked Questions"
msgstr ""
#. Tag: para
#: faq.xml:8
#, no-c-format
msgid ""
"My applications and desktop tools worked with PostGIS 1.5,but they don't "
"work with PostGIS 2.0. How do I fix this?"
msgstr ""
#. Tag: para
#: faq.xml:12
#, no-c-format
msgid ""
"A lot of deprecated functions were removed from the PostGIS code base in "
"PostGIS 2.0. This has affected applications in addition to third-party tools "
"such as Geoserver, MapServer, QuantumGIS, and OpenJump to name a few. There "
"are a couple of ways to resolve this. For the third-party apps, you can try "
"to upgrade to the latest versions of these which have many of these issues "
"fixed. For your own code, you can change your code to not use the functions "
"removed. Most of these functions are non ST_ aliases of ST_Union, ST_Length "
"etc. and as a last resort, install the whole of <varname>legacy.sql</"
"varname> or just the portions of <varname>legacy.sql</varname> you need."
msgstr ""
#. Tag: para
#: faq.xml:18
#, no-c-format
msgid ""
"The <varname>legacy.sql</varname> file is located in the same folder as "
"postgis.sql. You can install this file after you have installed postgis.sql "
"and spatial_ref_sys.sql to get back all the 200 some-odd old functions we "
"removed."
msgstr ""
#. Tag: para
#: faq.xml:24
#, no-c-format
msgid ""
"I'm running PostgreSQL 9.0 and I can no longer read/view geometries in "
"OpenJump, Safe FME, and some other tools?"
msgstr ""
#. Tag: para
#: faq.xml:28
#, no-c-format
msgid ""
"In PostgreSQL 9.0+, the default encoding for bytea data has been changed to "
"hex and older JDBC drivers still assume escape format. This has affected "
"some applications such as Java applications using older JDBC drivers or .NET "
"applications that use the older npgsql driver that expect the old behavior "
"of ST_AsBinary. There are two approaches to getting this to work again."
msgstr ""
#. Tag: para
#: faq.xml:32
#, no-c-format
msgid ""
"You can upgrade your JDBC driver to the latest PostgreSQL 9.0 version which "
"you can get from <ulink url=\"http://jdbc.postgresql.org/download.html"
"\">http://jdbc.postgresql.org/download.html</ulink>"
msgstr ""
#. Tag: para
#: faq.xml:34
#, no-c-format
msgid ""
"If you are running a .NET app, you can use Npgsql 2.0.11 or higher which you "
"can download from <ulink url=\"http://pgfoundry.org/frs/?"
"group_id=1000140\">http://pgfoundry.org/frs/?group_id=1000140</ulink> and as "
"described on <ulink url=\"http://fxjr.blogspot.com/2010/11/npgsql-2011-"
"released.html\">Francisco Figueiredo's NpgSQL 2.0.11 released blog entry</"
"ulink>"
msgstr ""
#. Tag: para
#: faq.xml:38
#, no-c-format
msgid ""
"If upgrading your PostgreSQL driver is not an option, then you can set the "
"default back to the old behavior with the following change:"
msgstr ""
#. Tag: programlisting
#: faq.xml:39
#, no-c-format
msgid "ALTER DATABASE mypostgisdb SET bytea_output='escape';"
msgstr ""
#. Tag: para
#: faq.xml:46
#, no-c-format
msgid ""
"I tried to use PgAdmin to view my geometry column and it is blank, what "
"gives?"
msgstr ""
#. Tag: para
#: faq.xml:50
#, no-c-format
msgid ""
"PgAdmin doesn't show anything for large geometries. The best ways to verify "
"you do have data in your geometry columns are?"
msgstr ""
#. Tag: programlisting
#: faq.xml:53
#, no-c-format
msgid ""
"-- this should return no records if all your geom fields are filled "
"in \n"
"SELECT somefield FROM mytable WHERE geom IS NULL;"
msgstr ""
#. Tag: programlisting
#: faq.xml:55
#, no-c-format
msgid ""
"-- To tell just how large your geometry is do a query of the form\n"
"--which will tell you the most number of points you have in any of your "
"geometry columns\n"
"SELECT MAX(ST_NPoints(geom)) FROM sometable;"
msgstr ""
#. Tag: para
#: faq.xml:61
#, no-c-format
msgid "What kind of geometric objects can I store?"
msgstr ""
#. Tag: para
#: faq.xml:65
#, no-c-format
msgid ""
"You can store point, line, polygon, multipoint, multiline, multipolygon, and "
"geometrycollections. In PostGIS 2.0 and above you can also store TINS and "
"Polyhedral Surfaces in the basic geometry type. These are specified in the "
"Open GIS Well Known Text Format (with XYZ,XYM,XYZM extensions). There are "
"three data types currently supported. The standard OGC geometry data type "
"which uses a planar coordinate system for measurement, the geography data "
"type which uses a geodetic coordinate system (not OGC, but you'll find a "
"similar type in Microsoft SQL Server 2008+). Only WGS 84 long lat "
"(SRID:4326) is supported by the geography data type. The newest family "
"member of the PostGIS spatial type family is raster for storing and "
"analyzing raster data. Raster has its very own FAQ. Refer to <xref linkend="
"\"RT_FAQ\"/> and <xref linkend=\"RT_reference\"/> for more details."
msgstr ""
#. Tag: para
#: faq.xml:78
#, no-c-format
msgid "I'm all confused. Which data store should I use geometry or geography?"
msgstr ""
#. Tag: para
#: faq.xml:82
#, no-c-format
msgid ""
"Short Answer: geography is a new data type that supports long range "
"distances measurements, but most computations on it are currently slower "
"than they are on geometry. If you use geography -- you don't need to learn "
"much about planar coordinate systems. Geography is generally best if all you "
"care about is measuring distances and lengths and you have data from all "
"over the world. Geometry data type is an older data type that has many more "
"functions supporting it, enjoys greater support from third party tools, and "
"operations on it are generally faster -- sometimes as much as 10 fold faster "
"for larger geometries. Geometry is best if you are pretty comfortable with "
"spatial reference systems or you are dealing with localized data where all "
"your data fits in a single <link linkend=\"spatial_ref_sys\">spatial "
"reference system (SRID)</link>, or you need to do a lot of spatial "
"processing. Note: It is fairly easy to do one-off conversions between the "
"two types to gain the benefits of each. Refer to <xref linkend="
"\"PostGIS_TypeFunctionMatrix\"/> to see what is currently supported and what "
"is not."
msgstr ""
#. Tag: para
#: faq.xml:93
#, no-c-format
msgid ""
"Long Answer: Refer to our more lengthy discussion in the <xref linkend="
"\"PostGIS_GeographyVSGeometry\"/> and <link linkend="
"\"PostGIS_TypeFunctionMatrix\">function type matrix</link>."
msgstr ""
#. Tag: para
#: faq.xml:101
#, no-c-format
msgid ""
"I have more intense questions about geography, such as how big of a "
"geographic region can I stuff in a geography column and still get reasonable "
"answers. Are there limitations such as poles, everything in the field must "
"fit in a hemisphere (like SQL Server 2008 has), speed etc?"
msgstr ""
#. Tag: para
#: faq.xml:105
#, no-c-format
msgid ""
"Your questions are too deep and complex to be adequately answered in this "
"section. Please refer to our <xref linkend=\"PostGIS_Geography_AdvancedFAQ\"/"
">."
msgstr ""
#. Tag: para
#: faq.xml:112
#, no-c-format
msgid "How do I insert a GIS object into the database?"
msgstr ""
#. Tag: para
#: faq.xml:116
#, no-c-format
msgid ""
"First, you need to create a table with a column of type \"geometry\" or "
"\"geography\" to hold your GIS data. Storing geography type data is a little "
"different than storing geometry. Refer to <xref linkend=\"Geography_Basics\"/"
"> for details on storing geography."
msgstr ""
#. Tag: para
#: faq.xml:120
#, no-c-format
msgid ""
"For geometry: Connect to your database with <filename>psql</filename> and "
"try the following SQL:"
msgstr ""
#. Tag: programlisting
#: faq.xml:124
#, no-c-format
msgid ""
"CREATE TABLE gtest ( ID int4, NAME varchar(20) );\n"
"SELECT AddGeometryColumn('', 'gtest','geom',-1,'LINESTRING',2);"
msgstr ""
#. Tag: para
#: faq.xml:126
#, no-c-format
msgid ""
"If the geometry column addition fails, you probably have not loaded the "
"PostGIS functions and objects into this database. See the <xref linkend="
"\"PGInstall\"/>."
msgstr ""
#. Tag: para
#: faq.xml:130
#, no-c-format
msgid ""
"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:"
msgstr ""
#. Tag: programlisting
#: faq.xml:134
#, no-c-format
msgid ""
"INSERT INTO gtest (ID, NAME, GEOM) \n"
"VALUES (\n"
" 1, \n"
" 'First Geometry', \n"
" ST_GeomFromText('LINESTRING(2 3,4 5,6 5,7 8)', -1)\n"
");"
msgstr ""
#. Tag: para
#: faq.xml:136
#, no-c-format
msgid ""
"For more information about other GIS objects, see the <link linkend="
"\"RefObject\">object reference</link>."
msgstr ""
#. Tag: para
#: faq.xml:139
#, no-c-format
msgid "To view your GIS data in the table:"
msgstr ""
#. Tag: programlisting
#: faq.xml:141
#, no-c-format
msgid "SELECT id, name, ST_AsText(geom) AS geom FROM gtest;"
msgstr ""
#. Tag: para
#: faq.xml:143
#, no-c-format
msgid "The return value should look something like this:"
msgstr ""
#. Tag: programlisting
#: faq.xml:145
#, no-c-format
msgid ""
"id | name | geom\n"
"----+----------------+-----------------------------\n"
" 1 | First Geometry | LINESTRING(2 3,4 5,6 5,7 8) \n"
"(1 row)"
msgstr ""
#. Tag: para
#: faq.xml:151
#, no-c-format
msgid "How do I construct a spatial query?"
msgstr ""
#. Tag: para
#: faq.xml:155
#, no-c-format
msgid ""
"The same way you construct any other database query, as an SQL combination "
"of return values, functions, and boolean tests."
msgstr ""
#. Tag: para
#: faq.xml:158
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: faq.xml:163
#, no-c-format
msgid ""
"In general, you will want to use the \"intersects operator\" (&amp;&amp;) "
"which tests whether the bounding boxes of features intersect. The reason the "
"&amp;&amp; operator is useful is because if a spatial index is available to "
"speed up the test, the &amp;&amp; operator will make use of this. This can "
"make queries much much faster."
msgstr ""
#. Tag: para
#: faq.xml:170
#, no-c-format
msgid ""
"You will also make use of spatial functions, such as Distance(), "
"ST_Intersects(), ST_Contains() and ST_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 <emphasis>might</emphasis> meet the "
"condition of interest. The spatial functions are then use to test the "
"condition exactly."
msgstr ""
#. Tag: programlisting
#: faq.xml:178
#, no-c-format
msgid ""
"SELECT id, the_geom \n"
"FROM thetable \n"
"WHERE \n"
" ST_Contains(the_geom,'POLYGON((0 0, 0 10, 10 10, 10 0, 0 0))');"
msgstr ""
#. Tag: para
#: faq.xml:184
#, no-c-format
msgid "How do I speed up spatial queries on large tables?"
msgstr ""
#. Tag: para
#: faq.xml:188
#, no-c-format
msgid ""
"Fast queries on large tables is the <emphasis>raison d'etre</emphasis> of "
"spatial databases (along with transaction support) so having a good index is "
"important."
msgstr ""
#. Tag: para
#: faq.xml:192
#, no-c-format
msgid ""
"To build a spatial index on a table with a <varname>geometry</varname> "
"column, use the \"CREATE INDEX\" function as follows:"
msgstr ""
#. Tag: programlisting
#: faq.xml:196
#, no-c-format
msgid ""
"CREATE INDEX [indexname] ON [tablename] USING GIST ( [geometrycolumn] );"
msgstr ""
#. Tag: para
#: faq.xml:198
#, no-c-format
msgid ""
"The \"USING GIST\" option tells the server to use a GiST (Generalized Search "
"Tree) index."
msgstr ""
#. Tag: para
#: faq.xml:202
#, no-c-format
msgid ""
"GiST indexes are assumed to be lossy. Lossy indexes uses a proxy object (in "
"the spatial case, a bounding box) for building the index."
msgstr ""
#. Tag: para
#: faq.xml:207
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: faq.xml:212
#, no-c-format
msgid ""
"For PostgreSQL 8.0.x and greater, just run the <command>VACUUM ANALYZE</"
"command> command."
msgstr ""
#. Tag: para
#: faq.xml:215
#, no-c-format
msgid ""
"For PostgreSQL 7.4.x and below, run the <command>SELECT UPDATE_GEOMETRY_STATS"
"()</command> command."
msgstr ""
#. Tag: para
#: faq.xml:222
#, no-c-format
msgid "Why aren't PostgreSQL R-Tree indexes supported?"
msgstr ""
#. Tag: para
#: faq.xml:226
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: faq.xml:231
#, no-c-format
msgid ""
"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):"
msgstr ""
#. Tag: para
#: faq.xml:239
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: faq.xml:246
#, no-c-format
msgid ""
"R-Tree indexes in PostgreSQL are not \"null safe\", so building an index on "
"a geometry column which contains null geometries will fail."
msgstr ""
#. Tag: para
#: faq.xml:256
#, no-c-format
msgid ""
"Why should I use the <varname>AddGeometryColumn()</varname> function and all "
"the other OpenGIS stuff?"
msgstr ""
#. Tag: para
#: faq.xml:261
#, no-c-format
msgid ""
"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 <emphasis>not</emphasis> be filled in "
"properly. However, this will cause most applications based on PostGIS to "
"fail, and it is generally suggested that you do use "
"<varname>AddGeometryColumn()</varname> to create geometry tables."
msgstr ""
#. Tag: para
#: faq.xml:270
#, no-c-format
msgid ""
"MapServer is one application which makes use of the "
"<varname>geometry_columns</varname> 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."
msgstr ""
#. Tag: para
#: faq.xml:279
#, no-c-format
msgid ""
"What is the best way to find all objects within a radius of another object?"
msgstr ""
#. Tag: para
#: faq.xml:284
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: faq.xml:289
#, no-c-format
msgid ""
"The <varname>ST_DWithin(geometry, geometry, distance)</varname> function is "
"a handy way of performing an indexed distance search. It works by creating a "
"search rectangle large enough to enclose the distance radius, then "
"performing an exact distance search on the indexed subset of results."
msgstr ""
#. Tag: para
#: faq.xml:295
#, no-c-format
msgid ""
"For example, to find all objects with 100 meters of POINT(1000 1000) the "
"following query would work well:"
msgstr ""
#. Tag: programlisting
#: faq.xml:298
#, no-c-format
msgid ""
"SELECT * FROM geotable \n"
"WHERE ST_DWithin(geocolumn, 'POINT(1000 1000)', 100.0);"
msgstr ""
#. Tag: para
#: faq.xml:304
#, no-c-format
msgid "How do I perform a coordinate reprojection as part of a query?"
msgstr ""
#. Tag: para
#: faq.xml:309
#, no-c-format
msgid ""
"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. "
"The below projects a geometry to NAD 83 long lat. The below will only work "
"if the srid of the_geom is not -1 (not undefined spatial ref)"
msgstr ""
#. Tag: programlisting
#: faq.xml:316
#, no-c-format
msgid "SELECT ST_Transform(the_geom,4269) FROM geotable;"
msgstr ""
#. Tag: para
#: faq.xml:322
#, no-c-format
msgid ""
"I did an ST_AsEWKT and ST_AsText on my rather large geometry and it returned "
"blank field. What gives?"
msgstr ""
#. Tag: para
#: faq.xml:326
#, no-c-format
msgid ""
"You are probably using PgAdmin or some other tool that doesn't output large "
"text. If your geometry is big enough, it will appear blank in these tools. "
"Use PSQL if you really need to see it or output it in WKT."
msgstr ""
#. Tag: programlisting
#: faq.xml:329
#, no-c-format
msgid ""
"--To check number of geometries are really blank\n"
" SELECT count(gid) FROM geotable WHERE "
"the_geom IS NULL;"
msgstr ""
#. Tag: para
#: faq.xml:335
#, no-c-format
msgid ""
"When I do an ST_Intersects, it says my two geometries don't intersect when I "
"KNOW THEY DO. What gives?"
msgstr ""
#. Tag: para
#: faq.xml:339
#, no-c-format
msgid ""
"This generally happens in two common cases. Your geometry is invalid -- "
"check <xref linkend=\"ST_IsValid\"/> or you are assuming they intersect "
"because ST_AsText truncates the numbers and you have lots of decimals after "
"it is not showing you."
msgstr ""
#. Tag: para
#: faq.xml:347
#, no-c-format
msgid ""
"I am releasing software that uses PostGIS, does that mean my software has to "
"be licensed using the GPL like PostGIS? Will I have to publish all my code "
"if I use PostGIS?"
msgstr ""
#. Tag: para
#: faq.xml:351
#, no-c-format
msgid ""
"Almost certainly not. As an example, consider Oracle database running on "
"Linux. Linux is GPL, Oracle is not, does Oracle running on Linux have to be "
"distributed using the GPL? No. So your software can use a PostgreSQL/PostGIS "
"database as much as it wants and be under any license you like."
msgstr ""
#. Tag: para
#: faq.xml:352
#, no-c-format
msgid ""
"The only exception would be if you made changes to the PostGIS source code, "
"and distributed your changed version of PostGIS. In that case you would have "
"to share the code of your changed PostGIS (but not the code of applications "
"running on top of it). Even in this limited case, you would still only have "
"to distribute source code to people you distributed binaries to. The GPL "
"does not require that you <emphasis>publish</emphasis> your source code, "
"only that you share it with people you give binaries to."
msgstr ""

658
doc/po/it_IT/faq_raster.xml.po Normal file
View file

@ -0,0 +1,658 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: faq_raster.xml:3
#, no-c-format
msgid "PostGIS Raster Frequently Asked Questions"
msgstr ""
#. Tag: para
#: faq_raster.xml:9
#, no-c-format
msgid "Where can I find out more about the PostGIS Raster Project?"
msgstr ""
#. Tag: para
#: faq_raster.xml:13
#, no-c-format
msgid ""
"Refer to the <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster"
"\">PostGIS Raster home page</ulink>."
msgstr ""
#. Tag: para
#: faq_raster.xml:19
#, no-c-format
msgid ""
"Are there any books or tutorials to get me started with this wonderful "
"invention?"
msgstr ""
#. Tag: para
#: faq_raster.xml:23
#, no-c-format
msgid ""
"There is a full length beginner tutorial <ulink url=\"http://trac.osgeo.org/"
"postgis/wiki/WKTRasterTutorial01\"> Intersecting vector buffers with large "
"raster coverage using PostGIS Raster</ulink>. Jorge has a series of blog "
"articles on PostGIS Raster that demonstrate how to load raster data as well "
"as cross compare to same tasks in Oracle GeoRaster. Check out <ulink url="
"\"http://gis4free.wordpress.com/category/postgis-raster/\">Jorge's PostGIS "
"Raster / Oracle GeoRaster Series</ulink>. There is a whole chapter (more "
"than 35 pages of content) dedicated to PostGIS Raster with free code and "
"data downloads at <ulink url=\"http://www.postgis.us/chapter_13\">PostGIS in "
"Action - Raster chapter</ulink>. You can <ulink url=\"http://www.postgis.us/"
"page_buy_book\">buy PostGIS in Action</ulink> now from Manning in hard-copy "
"(significant discounts for bulk purchases) or just the E-book format. You "
"can also buy from Amazon and various other book distributors. All hard-copy "
"books come with a free coupon to download the E-book version."
msgstr ""
#. Tag: para
#: faq_raster.xml:30
#, no-c-format
msgid ""
"Here is a review from a PostGIS Raster user <ulink url=\"http://"
"fuzzytolerance.info/code/postgis-raster-ftw/\">PostGIS raster applied to "
"land classification urban forestry</ulink>"
msgstr ""
#. Tag: para
#: faq_raster.xml:37
#, no-c-format
msgid "How do I install Raster support in my PostGIS database?"
msgstr ""
#. Tag: para
#: faq_raster.xml:41
#, no-c-format
msgid ""
"The easiest is to download binaries for PostGIS and Raster which are "
"currently available for windows and latest versions of Mac OSX. First you "
"need a working PostGIS 2.0.0 or above and be running PostgreSQL 8.4, 9.0, or "
"9.1. Note in PostGIS 2.0 PostGIS Raster is fully integrated, so it will be "
"compiled when you compile PostGIS."
msgstr ""
#. Tag: para
#: faq_raster.xml:43
#, no-c-format
msgid ""
"Instructions for installing and running under windows are available at "
"<ulink url=\"http://gis4free.wordpress.com/2011/03/10/how-to-install-and-"
"configure-postgis-raster-on-windows/\">How to Install and Configure PostGIS "
"raster on windows</ulink>"
msgstr ""
#. Tag: para
#: faq_raster.xml:44
#, no-c-format
msgid ""
"If you are on windows, you can compile yourself, or use the <ulink url="
"\"http://www.postgis.org/download/windows/experimental.php#wktraster\">pre-"
"compiled PostGIS Raster windows binaries</ulink>. If you are on Mac OSX "
"Leopard or Snow Leopard, there are binaries available at <ulink url=\"http://"
"www.kyngchaos.com/software/postgres\">Kyng Chaos Mac OSX PostgreSQL/GIS "
"binaries</ulink>."
msgstr ""
#. Tag: para
#: faq_raster.xml:50
#, no-c-format
msgid ""
"Then to enable raster support in your database, run the rtpostgis.sql file "
"in your database. To upgrade an existing install use "
"rtpostgis_upgrade_minor..sql instead of rtpostgis.sql"
msgstr ""
#. Tag: para
#: faq_raster.xml:51
#, no-c-format
msgid ""
"For other platforms, you generally need to compile yourself. Dependencies "
"are PostGIS and GDAL. For more details about compiling from source, please "
"refer to <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/"
"Documentation01#a2.3-CompilingandInstallingfromSources\">Installing PostGIS "
"Raster from source (in prior versions of PostGIS)</ulink>"
msgstr ""
#. Tag: para
#: faq_raster.xml:57
#, no-c-format
msgid ""
"I get error could not load library \"C:/Program Files/PostgreSQL/8.4/lib/"
"rtpostgis.dll\": The specified module could not be found. or could not load "
"library on Linux when trying to run rtpostgis.sql"
msgstr ""
#. Tag: para
#: faq_raster.xml:62
#, no-c-format
msgid ""
"rtpostgis.so/dll is built with dependency on libgdal.dll/so. Make sure for "
"Windows you have libgdal-1.dll in the bin folder of your PostgreSQL install. "
"For Linux libgdal has to be in your path or bin folder."
msgstr ""
#. Tag: para
#: faq_raster.xml:64
#, no-c-format
msgid ""
"You may also run into different errors if you don't have PostGIS installed "
"in your database. Make sure to install PostGIS first in your database before "
"trying to install the raster support."
msgstr ""
#. Tag: para
#: faq_raster.xml:71
#, no-c-format
msgid "How do I load Raster data into PostGIS?"
msgstr ""
#. Tag: para
#: faq_raster.xml:75
#, no-c-format
msgid ""
"The latest version of PostGIS comes packaged with a <varname>raster2pgsql</"
"varname> raster loader executable capable of loading many kinds of rasters "
"and also generating lower resolution overviews without any additional "
"software. Please refer to <xref linkend=\"RT_Raster_Loader\"/> for more "
"details. Pre-2.0 versions came with a <varname>raster2pgsql.py</varname> "
"that required python with numpy and GDAL. This is no longer needed."
msgstr ""
#. Tag: para
#: faq_raster.xml:81
#, no-c-format
msgid "What kind of raster file formats can I load into my database?"
msgstr ""
#. Tag: para
#: faq_raster.xml:85
#, no-c-format
msgid ""
"Any that your GDAL library supports. GDAL supported formats are documented "
"<ulink url=\"http://www.gdal.org/formats_list.html\">GDAL File Formats</"
"ulink>."
msgstr ""
#. Tag: para
#: faq_raster.xml:86
#, no-c-format
msgid ""
"Your particular GDAL install may not support all formats. To verify the ones "
"supported by your particular GDAL install, you can use"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:87
#, no-c-format
msgid "raster2pgsql -G"
msgstr ""
#. Tag: para
#: faq_raster.xml:93
#, no-c-format
msgid "Can I export my PostGIS raster data to other raster formats?"
msgstr ""
#. Tag: para
#: faq_raster.xml:97
#, no-c-format
msgid "<para>Yes</para>"
msgstr ""
#. Tag: para
#: faq_raster.xml:98
#, no-c-format
msgid ""
"GDAL 1.7+ has a PostGIS raster driver, but is only compiled in if you choose "
"to compile with PostgreSQL support."
msgstr ""
#. Tag: para
#: faq_raster.xml:99
#, no-c-format
msgid ""
"The driver currently doesn't support irregularly blocked rasters, although "
"you can store irregularly blocked rasters in PostGIS raster data type."
msgstr ""
#. Tag: para
#: faq_raster.xml:101
#, no-c-format
msgid ""
"If you are compiling from source, you need to include in your configure "
"<programlisting>--with-pg=path/to/pg_config</programlisting> to enable the "
"driver. Refer to <ulink url=\"http://trac.osgeo.org/gdal/wiki/BuildHints"
"\">GDAL Build Hints</ulink> for tips on building GDAL against in various OS "
"platforms."
msgstr ""
#. Tag: para
#: faq_raster.xml:106
#, no-c-format
msgid ""
"If your version of GDAL is compiled with the PostGIS Raster driver you "
"should see PostGIS Raster in list when you do"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:108
#, no-c-format
msgid "gdalinfo --formats"
msgstr ""
#. Tag: para
#: faq_raster.xml:110
#, no-c-format
msgid "To get a summary about your raster via GDAL use gdalinfo:"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:111
#, no-c-format
msgid ""
"gdalinfo \"PG:host=localhost port=5432 dbname='mygisdb' user='postgres' "
"password='whatever' schema='someschema' table=sometable\""
msgstr ""
#. Tag: para
#: faq_raster.xml:114
#, no-c-format
msgid ""
"To export data to other raster formats, use gdal_translate the below will "
"export all data from a table to a PNG file at 10% size."
msgstr ""
#. Tag: para
#: faq_raster.xml:116
#, no-c-format
msgid ""
"Depending on your pixel band types, some translations may not work if the "
"export format does not support that Pixel type. For example floating point "
"band types and 32 bit unsigned ints will not translate easily to JPG or some "
"others."
msgstr ""
#. Tag: para
#: faq_raster.xml:119
#, no-c-format
msgid "Here is an example simple translation"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:120
#, no-c-format
msgid ""
"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' "
"user='postgres' password=whatever' schema='someschema' table=sometable\" C:"
"\\somefile.png"
msgstr ""
#. Tag: para
#: faq_raster.xml:121
#, no-c-format
msgid ""
"You can also use SQL where clauses in your export using the where=... in "
"your driver connection string. Below are some using a where clause"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:123
#, no-c-format
msgid ""
"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' "
"user='postgres' password=whatever' schema='someschema' table=sometable where="
"\"owner='jimmy'\" \" C:\\somefile.png"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:124
#, no-c-format
msgid ""
"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' "
"user='postgres' password=whatever' schema='someschema' table=sometable "
"where='ST_Intersects(rast, ST_SetSRID(ST_Point(-71.032,42.3793),4326) )' \" "
"C:\\intersectregion.png"
msgstr ""
#. Tag: para
#: faq_raster.xml:125
#, no-c-format
msgid ""
"To see more examples and syntax refer to <ulink url=\"http://trac.osgeo.org/"
"gdal/wiki/frmts_wtkraster.html#a3.2-Readingrasterdatafromthedatabase"
"\">Reading Raster Data of PostGIS Raster section</ulink>"
msgstr ""
#. Tag: para
#: faq_raster.xml:130
#, no-c-format
msgid ""
"Are their binaries of GDAL available already compiled with PostGIS Raster "
"suppport?"
msgstr ""
#. Tag: para
#: faq_raster.xml:132
#, no-c-format
msgid ""
"Yes. Check out the page <ulink url=\"http://trac.osgeo.org/gdal/wiki/"
"DownloadingGdalBinaries\">GDAL Binaries</ulink> page. Any compiled with "
"PostgreSQL support should have PostGIS Raster in them."
msgstr ""
#. Tag: para
#: faq_raster.xml:134
#, no-c-format
msgid ""
"We know for sure the following windows binaries have PostGIS Raster built in."
msgstr ""
#. Tag: para
#: faq_raster.xml:135
#, no-c-format
msgid ""
"<ulink url=\"http://fwtools.maptools.org/\">FWTools latest stable version "
"for Windows is compiled with Raster support</ulink>."
msgstr ""
#. Tag: para
#: faq_raster.xml:136
#, no-c-format
msgid ""
"PostGIS Raster is undergoing many changes. If you want to get the latest "
"nightly build for Windows -- then check out the Tamas Szekeres nightly "
"builds built with Visual Studio which contain GDAL trunk, Python Bindings "
"and MapServer executables and PostGIS Raster driver built-in. Just click the "
"SDK bat and run your commands from there. <ulink url=\"http://vbkto.dyndns."
"org/sdk/\">http://vbkto.dyndns.org/sdk/</ulink>. Also available are VS "
"project files."
msgstr ""
#. Tag: para
#: faq_raster.xml:145
#, no-c-format
msgid "What tools can I use to view PostGIS raster data?"
msgstr ""
#. Tag: para
#: faq_raster.xml:149
#, no-c-format
msgid ""
"You can use MapServer compiled with GDAL 1.7+ and PostGIS Raster driver "
"support to view Raster data. QuantumGIS (QGIS) now supports viewing of "
"PostGIS Raster if you have PostGIS raster driver installed."
msgstr ""
#. Tag: para
#: faq_raster.xml:151
#, no-c-format
msgid ""
"In theory any tool that renders data using GDAL can support PostGIS raster "
"data or support it with fairly minimal effort. Again for Windows, Tamas' "
"binaries <ulink url=\"http://vbkto.dyndns.org/sdk/\">http://vbkto.dyndns.org/"
"sdk/</ulink> are a good choice if you don't want the hassle of having to "
"setup to compile your own."
msgstr ""
#. Tag: para
#: faq_raster.xml:158
#, no-c-format
msgid "How can I add a PostGIS raster layer to my MapServer map?"
msgstr ""
#. Tag: para
#: faq_raster.xml:162
#, no-c-format
msgid ""
"First you need GDAL 1.7 or higher compiled with PostGIS raster support. GDAL "
"1.8 or above is preferred since many issues have been fixed in 1.8 and more "
"PostGIS raster issues fixed in trunk version."
msgstr ""
#. Tag: para
#: faq_raster.xml:164
#, no-c-format
msgid ""
"You can much like you can with any other raster. Refer to <ulink url="
"\"http://mapserver.org/input/raster.html\">MapServer Raster processing "
"options</ulink> for list of various processing functions you can use with "
"MapServer raster layers."
msgstr ""
#. Tag: para
#: faq_raster.xml:167
#, no-c-format
msgid ""
"What makes PostGIS raster data particularly interesting, is that since each "
"tile can have various standard database columns, you can segment it in your "
"data source"
msgstr ""
#. Tag: para
#: faq_raster.xml:169
#, no-c-format
msgid ""
"Below is an example of how you would define a PostGIS raster layer in "
"MapServer."
msgstr ""
#. Tag: para
#: faq_raster.xml:170
#, no-c-format
msgid ""
"The mode=2 is required for tiled rasters and was added in PostGIS 2.0 and "
"GDAL 1.8 drivers. This does not exist in GDAL 1.7 drivers."
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:171
#, no-c-format
msgid ""
"-- displaying raster with standard raster options\n"
"LAYER\n"
" NAME coolwktraster\n"
" TYPE raster\n"
" STATUS ON\n"
" DATA \"PG:host=localhost port=5432 dbname='somedb' user='someuser' "
"password='whatever' \n"
" schema='someschema' table='cooltable' mode='2'\" \n"
" PROCESSING \"NODATA=0\"\n"
" PROCESSING \"SCALE=AUTO\"\n"
" #... other standard raster processing functions here\n"
" #... classes are optional but useful for 1 band data\n"
" CLASS\n"
" NAME \"boring\"\n"
" EXPRESSION ([pixel] &lt; 20)\n"
" COLOR 250 250 250\n"
" END\n"
" CLASS\n"
" NAME \"mildly interesting\"\n"
" EXPRESSION ([pixel] &gt; 20 AND [pixel] &lt; 1000)\n"
" COLOR 255 0 0\n"
" END\n"
" CLASS\n"
" NAME \"very interesting\"\n"
" EXPRESSION ([pixel] &gt;= 1000)\n"
" COLOR 0 255 0\n"
" END\n"
"END"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:173
#, no-c-format
msgid ""
"-- displaying raster with standard raster options and a where clause\n"
"LAYER\n"
" NAME soil_survey2009\n"
" TYPE raster\n"
" STATUS ON\n"
" DATA \"PG:host=localhost port=5432 dbname='somedb' user='someuser' "
"password='whatever' \n"
" schema='someschema' table='cooltable' "
"where='survey_year=2009' mode='2'\" \n"
" PROCESSING \"NODATA=0\"\n"
" #... other standard raster processing functions here\n"
" #... classes are optional but useful for 1 band data\n"
"END"
msgstr ""
#. Tag: para
#: faq_raster.xml:181
#, no-c-format
msgid "What functions can I currently use with my raster data?"
msgstr ""
#. Tag: para
#: faq_raster.xml:185
#, no-c-format
msgid ""
"Refer to the list of <xref linkend=\"RT_reference\"/>. There are more, but "
"this is still a work in progress."
msgstr ""
#. Tag: para
#: faq_raster.xml:187
#, no-c-format
msgid ""
"Refer to the <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/"
"PlanningAndFunding\">PostGIS Raster roadmap page</ulink> for details of what "
"you can expect in the future."
msgstr ""
#. Tag: para
#: faq_raster.xml:195
#, no-c-format
msgid ""
"I am getting error ERROR: function st_intersects(raster, unknown) is not "
"unique or st_union(geometry,text) is not unique. How do I fix?"
msgstr ""
#. Tag: para
#: faq_raster.xml:199
#, no-c-format
msgid ""
"The function is not unique error happens if one of your arguments is a "
"textual representation of a geometry instead of a geometry. In these cases, "
"PostgreSQL marks the textual representation as an unknown type, which means "
"it can fall into the st_intersects(raster, geometry) or st_intersects(raster,"
"raster) thus resulting in a non-unique case since both functions can in "
"theory support your request. To prevent this, you need to cast the geometry "
"to a geometry."
msgstr ""
#. Tag: para
#: faq_raster.xml:200
#, no-c-format
msgid "For example if your code looks like this:"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:201
#, no-c-format
msgid ""
"SELECT rast\n"
" FROM my_raster\n"
" WHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)');"
msgstr ""
#. Tag: para
#: faq_raster.xml:202
#, no-c-format
msgid ""
"Cast the textual geometry representation to a geometry by changing your code "
"to this:"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:203
#, no-c-format
msgid ""
"SELECT rast\n"
" FROM my_raster\n"
" WHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)'::geometry);"
msgstr ""
#. Tag: para
#: faq_raster.xml:211
#, no-c-format
msgid ""
"How is PostGIS Raster different from Oracle GeoRaster (SDO_GEORASTER) and "
"SDO_RASTER types?"
msgstr ""
#. Tag: para
#: faq_raster.xml:215
#, no-c-format
msgid ""
"For a more extensive discussion on this topic, check out Jorge Arévalo "
"<ulink url=\"http://gis4free.wordpress.com/2010/07/19/oracle-georaster-part-"
"i/\">Oracle GeoRaster and PostGIS Raster: First impressions </ulink>"
msgstr ""
#. Tag: para
#: faq_raster.xml:216
#, no-c-format
msgid ""
"The major advantage of one-georeference-by-raster over one-georeference-by-"
"layer is to allow:"
msgstr ""
#. Tag: para
#: faq_raster.xml:217
#, no-c-format
msgid ""
"* coverages to be not necessarily rectangular (which is often the case of "
"raster coverage covering large extents. See the possible raster arrangements "
"in the documentation)"
msgstr ""
#. Tag: para
#: faq_raster.xml:218
#, no-c-format
msgid ""
"* rasters to overlaps (which is necessary to implement lossless vector to "
"raster conversion)"
msgstr ""
#. Tag: para
#: faq_raster.xml:219
#, no-c-format
msgid ""
"These arrangements are possible in Oracle as well, but they imply the "
"storage of multiple SDO_GEORASTER objects linked to as many SDO_RASTER "
"tables. A complex coverage can lead to hundreds of tables in the database. "
"With PostGIS Raster you can store a similar raster arrangement into a unique "
"table."
msgstr ""
#. Tag: para
#: faq_raster.xml:224
#, no-c-format
msgid ""
"It's a bit like if PostGIS would force you to store only full rectangular "
"vector coverage without gaps or overlaps (a perfect rectangular topological "
"layer). This is very practical in some applications but practice has shown "
"that it is not realistic or desirable for most geographical coverages. "
"Vector structures needs the flexibility to store discontinuous and non-"
"rectangular coverages. We think it is a big advantage that raster structure "
"should benefit as well."
msgstr ""

1680
doc/po/it_IT/installation.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

509
doc/po/it_IT/introduction.xml.po Normal file
View file

@ -0,0 +1,509 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: introduction.xml:3
#, no-c-format
msgid "Introduction"
msgstr ""
#. Tag: para
#: introduction.xml:5
#, no-c-format
msgid ""
"PostGIS was 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."
msgstr ""
#. Tag: para
#: introduction.xml:15
#, no-c-format
msgid ""
"PostGIS is an incubation project of the OSGeo Foundation. PostGIS is being "
"continually improved and funded by many FOSS4G Developers as well as "
"corporations all over the world that gain great benefit from its "
"functionality and versatility."
msgstr ""
#. Tag: title
#: introduction.xml:21
#, no-c-format
msgid "Project Steering Committee"
msgstr ""
#. Tag: para
#: introduction.xml:22
#, no-c-format
msgid ""
"The PostGIS Project Steering Committee (PSC) coordinates the general "
"direction, release cycles, documentation, and outreach efforts for the "
"PostGIS project. In addition the PSC provides general user support, accepts "
"and approves patches from the general PostGIS community and votes on "
"miscellaneous issues involving PostGIS such as developer commit access, new "
"PSC members or significant API changes."
msgstr ""
#. Tag: term
#: introduction.xml:31
#, no-c-format
msgid "Mark Cave-Ayland"
msgstr ""
#. Tag: para
#: introduction.xml:33
#, no-c-format
msgid ""
"Coordinates bug fixing and maintenance effort, alignment of PostGIS with "
"PostgreSQL releases, spatial index selectivity and binding, loader/dumper, "
"and Shapefile GUI Loader, integration of new and new function enhancements."
msgstr ""
#. Tag: term
#: introduction.xml:40
#, no-c-format
msgid "Regina Obe"
msgstr ""
#. Tag: para
#: introduction.xml:42
#, no-c-format
msgid ""
"Buildbot Maintenance, windows production and experimental builds, "
"Documentation, general user support on PostGIS newsgroup, X3D support, Tiger "
"Geocoder Support, management functions, and smoke testing new functionality "
"or major code changes."
msgstr ""
#. Tag: term
#: introduction.xml:49
#, no-c-format
msgid "Paul Ramsey (Chair)"
msgstr ""
#. Tag: para
#: introduction.xml:51
#, no-c-format
msgid ""
"Co-founder of PostGIS project. General bug fixing, geography support, "
"geography and geometry index support (2D, 3D, nD index and anything spatial "
"index), underlying geometry internal structures, GEOS functionality "
"integration and alignment with GEOS releases, loader/dumper, and Shapefile "
"GUI loader."
msgstr ""
#. Tag: term
#: introduction.xml:57
#, no-c-format
msgid "Sandro Santilli"
msgstr ""
#. Tag: para
#: introduction.xml:60
#, no-c-format
msgid ""
"Bug fixes and maintenance and integration of new GEOS functionality and "
"alignment with GEOS releases, Topology support, and Raster framework and low "
"level api functions."
msgstr ""
#. Tag: title
#: introduction.xml:67
#, no-c-format
msgid "Contributors Past and Present"
msgstr ""
#. Tag: term
#: introduction.xml:71
#, no-c-format
msgid "Chris Hodgson"
msgstr ""
#. Tag: para
#: introduction.xml:73
#, no-c-format
msgid ""
"Prior PSC Member. General development, site and buildbot maintenance, OSGeo "
"incubation management"
msgstr ""
#. Tag: term
#: introduction.xml:77
#, no-c-format
msgid "Kevin Neufeld"
msgstr ""
#. Tag: para
#: introduction.xml:79
#, no-c-format
msgid ""
"Prior PSC Member. Documentation and documentation support tools, advanced "
"user support on PostGIS newsgroup, and PostGIS maintenance function "
"enhancements."
msgstr ""
#. Tag: term
#: introduction.xml:85
#, no-c-format
msgid "Dave Blasby"
msgstr ""
#. Tag: para
#: introduction.xml:88
#, no-c-format
msgid ""
"The original developer/Co-founder of PostGIS. Dave wrote the server side "
"objects, index bindings, and many of the server side analytical functions."
msgstr ""
#. Tag: term
#: introduction.xml:95
#, no-c-format
msgid "Jeff Lounsbury"
msgstr ""
#. Tag: para
#: introduction.xml:97
#, no-c-format
msgid ""
"Original development of the Shape file loader/dumper. Current PostGIS "
"Project Owner representative."
msgstr ""
#. Tag: term
#: introduction.xml:102
#, no-c-format
msgid "Olivier Courtin"
msgstr ""
#. Tag: para
#: introduction.xml:104
#, no-c-format
msgid "Input output XML (KML,GML)/GeoJSON functions, 3D support and bug fixes."
msgstr ""
#. Tag: term
#: introduction.xml:109
#, no-c-format
msgid "Mark Leslie"
msgstr ""
#. Tag: para
#: introduction.xml:111
#, no-c-format
msgid ""
"Ongoing maintenance and development of core functions. Enhanced curve "
"support. Shapefile GUI loader."
msgstr ""
#. Tag: term
#: introduction.xml:116
#, no-c-format
msgid "Pierre Racine"
msgstr ""
#. Tag: para
#: introduction.xml:118
#, no-c-format
msgid "Raster overall architecture, prototyping, programming support"
msgstr ""
#. Tag: term
#: introduction.xml:123
#, no-c-format
msgid "Nicklas Avén"
msgstr ""
#. Tag: para
#: introduction.xml:126
#, no-c-format
msgid ""
"Distance function enhancements (including 3D distance and relationship "
"functions) and additions, Windows testing, and general user support"
msgstr ""
#. Tag: term
#: introduction.xml:131
#, no-c-format
msgid "Jorge Arévalo"
msgstr ""
#. Tag: para
#: introduction.xml:134
#, no-c-format
msgid "Raster development, GDAL driver support, loader"
msgstr ""
#. Tag: term
#: introduction.xml:139
#, no-c-format
msgid "Bborie Park"
msgstr ""
#. Tag: para
#: introduction.xml:141
#, no-c-format
msgid "Raster development, raster loader"
msgstr ""
#. Tag: term
#: introduction.xml:146
#, no-c-format
msgid "Mateusz Loskot"
msgstr ""
#. Tag: para
#: introduction.xml:148
#, no-c-format
msgid "Raster loader, low level raster api functions"
msgstr ""
#. Tag: term
#: introduction.xml:153
#, no-c-format
msgid "David Zwarg"
msgstr ""
#. Tag: para
#: introduction.xml:156
#, no-c-format
msgid "Raster development"
msgstr ""
#. Tag: term
#: introduction.xml:161
#, no-c-format
msgid "Other contributors: Individuals"
msgstr ""
#. Tag: para
#: introduction.xml:164
#, no-c-format
msgid ""
"In alphabetical order: Alex Bodnaru, Alex Mayrhofer, Andrea Peri, Andreas "
"Forø Tollefsen, Andreas Neumann, Anne Ghisla, Barbara Phillipot, Ben Jubb, "
"Bernhard Reiter, Brian Hamlin, Bruce Rindahl, Bruno Wolff III, Bryce L. "
"Nordgren, Carl Anderson, Charlie Savage, Dane Springmeyer, David Skea, David "
"Techer, Eduin Carrillo, Even Rouault, Frank Warmerdam, George Silva, Gerald "
"Fenoy, Gino Lucrezi, Guillaume Lelarge, IIDA Tetsushi, Ingvild Nystuen, Jeff "
"Adams, Jose Carlos Martinez Llari, Kashif Rasul, Klaus Foerster, Kris Jurka, "
"Leo Hsu, Loic Dachary, Luca S. Percich, Maria Arias de Reyna, Mark Sondheim, "
"Markus Schaber, Maxime Guillaud, Maxime van Noppen, Michael Fuhr, Nikita "
"Shulga, Norman Vine, Rafal Magda, Ralph Mason, Richard Greenwood, Silvio "
"Grosso, Steffen Macke, Stephen Frost, Tom van Tilburg, Vincent Picavet"
msgstr ""
#. Tag: term
#: introduction.xml:221
#, no-c-format
msgid "Other contributors: Corporate Sponsors"
msgstr ""
#. Tag: para
#: introduction.xml:224
#, no-c-format
msgid ""
"These are corporate entities that have contributed developer time, hosting, "
"or direct monetary funding to the PostGIS project"
msgstr ""
#. Tag: para
#: introduction.xml:225
#, no-c-format
msgid ""
"In alphabetical order: Arrival 3D, Associazione Italiana per l'Informazione "
"Geografica Libera (GFOSS.it), AusVet, Avencia, Azavea, Cadcorp, CampToCamp, "
"City of Boston (DND), Clever Elephant Solutions, Cooperativa Alveo, Deimos "
"Space, Faunalia, Geographic Data BC, Hunter Systems Group, Lidwala "
"Consulting Engineers, LisaSoft, Logical Tracking &amp; Tracing International "
"AG, Michigan Tech Research Institute, Norwegian Forest and Landscape "
"Institute, OpenGeo, OSGeo, Oslandia, Paragon Corporation, R3 GIS,, "
"Refractions Research, Regione Toscana-SIGTA, Safe Software, Sirius "
"Corporation plc, Stadt Uster, UC Davis Center for Vectorborne Diseases, "
"University of Laval, U.S Department of State (HIU), Vizzuality, Zonar Systems"
msgstr ""
#. Tag: term
#: introduction.xml:265
#, no-c-format
msgid "Crowd Funding Campaigns"
msgstr ""
#. Tag: para
#: introduction.xml:268
#, no-c-format
msgid ""
"Crowd funding campaigns are campaigns we run to get badly wanted features "
"funded that can service a large number of people. Each campaign is "
"specifically focused on a particular feature or set of features. Each "
"sponsor chips in a small fraction of the needed funding and with enough "
"people/organizations contributing, we have the funds to pay for the work "
"that will help many. If you have an idea for a feature you think many others "
"would be willing to co-fund, please post to the <ulink url=\"http://www."
"postgis.org/mailman/listinfo/postgis-users\">PostGIS newsgroup</ulink> your "
"thoughts and together we can make it happen."
msgstr ""
#. Tag: para
#: introduction.xml:269
#, no-c-format
msgid ""
"PostGIS 2.0.0 was the first release we tried this strategy. We used <ulink "
"url=\"http://www.pledgebank.com\">PledgeBank</ulink> and we got two "
"successful campaigns out of it."
msgstr ""
#. Tag: para
#: introduction.xml:270
#, no-c-format
msgid ""
"<ulink url=\"http://www.pledgebank.com/postgistopology\"><emphasis role="
"\"bold\">postgistopology</emphasis></ulink> - 10 plus sponsors each "
"contributed $250 USD to build toTopoGeometry function and beef up topology "
"support in 2.0.0. It happened."
msgstr ""
#. Tag: para
#: introduction.xml:271
#, no-c-format
msgid ""
"<ulink url=\"http://www.pledgebank.com/postgis64windows\"><emphasis role="
"\"bold\">postgis64windows</emphasis></ulink> - 20 someodd sponsors each "
"contributed $100 USD to pay for the work needed to work out PostGIS 64-bit "
"on windows issues. It happened. We now have a 64-bit beta release for "
"PostGIS 2.0.0 and a final one planned for release that will be available on "
"PostgreSQL stack builder."
msgstr ""
#. Tag: term
#: introduction.xml:276
#, no-c-format
msgid "Important Support Libraries"
msgstr ""
#. Tag: para
#: introduction.xml:279
#, no-c-format
msgid ""
"The <ulink url=\"http://trac.osgeo.org/geos/\">GEOS</ulink> geometry "
"operations library, and the algorithmic work of Martin Davis in making it "
"all work, ongoing maintenance and support of Mateusz Loskot, Sandro Santilli "
"(strk), Paul Ramsey and others."
msgstr ""
#. Tag: para
#: introduction.xml:284
#, no-c-format
msgid ""
"The <ulink url=\"http://trac.osgeo.org/gdal/\">GDAL</ulink> Geospatial Data "
"Abstraction Library, by Frank Warmerdam and others is used to power much of "
"the raster functionality introduced in PostGIS 2.0.0. In kind, improvements "
"needed in GDAL to support PostGIS are contributed back to the GDAL project."
msgstr ""
#. Tag: para
#: introduction.xml:289
#, no-c-format
msgid ""
"The <ulink url=\"http://trac.osgeo.org/proj/\">Proj4</ulink> cartographic "
"projection library, and the work of Gerald Evenden and Frank Warmerdam in "
"creating and maintaining it."
msgstr ""
#. Tag: para
#: introduction.xml:293
#, no-c-format
msgid ""
"Last but not least, the <ulink url=\"http://www.postgresql.org\">PostgreSQL "
"DBMS</ulink>, The giant that PostGIS stands on. Much of the speed and "
"flexibility of PostGIS would not be possible without the extensibility, "
"great query planner, GIST index, and plethora of SQL features provided by "
"PostgreSQL."
msgstr ""
#. Tag: title
#: introduction.xml:302
#, no-c-format
msgid "More Information"
msgstr ""
#. Tag: para
#: introduction.xml:306
#, no-c-format
msgid ""
"The latest software, documentation and news items are available at the "
"PostGIS web site, <ulink url=\"http://www.postgis.org\">http://www.postgis."
"org</ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:312
#, no-c-format
msgid ""
"More information about the GEOS geometry operations library is available "
"at<ulink url=\"http://trac.osgeo.org/geos/\"> http://trac.osgeo.org/geos/</"
"ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:318
#, no-c-format
msgid ""
"More information about the Proj4 reprojection library is available at <ulink "
"url=\"http://trac.osgeo.org/proj/\">http://trac.osgeo.org/proj/</ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:324
#, no-c-format
msgid ""
"More information about the PostgreSQL database server is available at the "
"PostgreSQL main site <ulink url=\"http://www.postgresql.org\">http://www."
"postgresql.org</ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:330
#, no-c-format
msgid ""
"More information about GiST indexing is available at the PostgreSQL GiST "
"development site, <ulink url=\"http://www.sai.msu.su/~megera/postgres/gist/"
"\">http://www.sai.msu.su/~megera/postgres/gist/</ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:336
#, no-c-format
msgid ""
"More information about MapServer internet map server is available at <ulink "
"url=\"http://mapserver.org/\">http://mapserver.org</ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:342
#, no-c-format
msgid ""
"The &quot;<ulink url=\"http://www.opengeospatial.org/standards/sfs\">Simple "
"Features for Specification for SQL</ulink>&quot; is available at the OpenGIS "
"Consortium web site: <ulink url=\"http://www.opengeospatial.org/\">http://"
"www.opengeospatial.org/</ulink>."
msgstr ""

463
doc/po/it_IT/performance_tips.xml.po Normal file
View file

@ -0,0 +1,463 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: performance_tips.xml:3
#, no-c-format
msgid "Performance tips"
msgstr ""
#. Tag: title
#: performance_tips.xml:6
#, no-c-format
msgid "Small tables of large geometries"
msgstr ""
#. Tag: title
#: performance_tips.xml:9
#, no-c-format
msgid "Problem description"
msgstr ""
#. Tag: para
#: performance_tips.xml:11
#, no-c-format
msgid ""
"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 <ulink url=\"http://www.postgresql.org/docs/current/"
"static/storage-toast.html\">the PostgreSQL Documentation for TOAST</ulink> "
"for more information)."
msgstr ""
#. Tag: para
#: performance_tips.xml:19
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: performance_tips.xml:26
#, no-c-format
msgid ""
"Now issue a query where you use the geometry operator &amp;&amp; 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 &amp;&amp; operator has to fetch every "
"geometry from disk to compare the bounding boxes, thus reading all TOAST "
"pages, too."
msgstr ""
#. Tag: para
#: performance_tips.xml:35
#, no-c-format
msgid ""
"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"
msgstr ""
#. Tag: title
#: performance_tips.xml:43
#, no-c-format
msgid "Workarounds"
msgstr ""
#. Tag: para
#: performance_tips.xml:45
#, no-c-format
msgid ""
"The PostgreSQL people are trying to solve this issue by making the query "
"estimation TOAST-aware. For now, here are two workarounds:"
msgstr ""
#. Tag: para
#: performance_tips.xml:48
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: performance_tips.xml:56
#, no-c-format
msgid ""
"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:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:61
#, no-c-format
msgid ""
"SELECT AddGeometryColumn"
"('myschema','mytable','bbox','4326','GEOMETRY','2'); \n"
"UPDATE mytable SET bbox = ST_Envelope(ST_Force_2d(the_geom));"
msgstr ""
#. Tag: para
#: performance_tips.xml:63
#, no-c-format
msgid ""
"Now change your query to use the &amp;&amp; operator against bbox instead of "
"geom_column, like:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:66
#, no-c-format
msgid ""
"SELECT geom_column \n"
"FROM mytable \n"
"WHERE bbox &amp;&amp; ST_SetSRID('BOX3D(0 0,1 1)'::box3d,4326);"
msgstr ""
#. Tag: para
#: performance_tips.xml:68
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: title
#: performance_tips.xml:77
#, no-c-format
msgid "CLUSTERing on geometry indices"
msgstr ""
#. Tag: para
#: performance_tips.xml:79
#, no-c-format
msgid ""
"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.)"
msgstr ""
#. Tag: para
#: performance_tips.xml:89
#, no-c-format
msgid ""
"However, currently PostgreSQL does not allow clustering on PostGIS GIST "
"indices because GIST indices simply ignores NULL values, you get an error "
"message like:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:93
#, no-c-format
msgid ""
"lwgeom=# CLUSTER my_geom_index ON my_table; \n"
"ERROR: cannot cluster when index access method does not handle null values\n"
"HINT: You may be able to work around this by marking column \"the_geom\" NOT "
"NULL."
msgstr ""
#. Tag: para
#: performance_tips.xml:95
#, no-c-format
msgid ""
"As the HINT message tells you, one can work around this deficiency by adding "
"a \"not null\" constraint to the table:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:98
#, no-c-format
msgid ""
"lwgeom=# ALTER TABLE my_table ALTER COLUMN the_geom SET not null; \n"
"ALTER TABLE"
msgstr ""
#. Tag: para
#: performance_tips.xml:100
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: title
#: performance_tips.xml:107
#, no-c-format
msgid "Avoiding dimension conversion"
msgstr ""
#. Tag: para
#: performance_tips.xml:109
#, no-c-format
msgid ""
"Sometimes, you happen to have 3D or 4D data in your table, but always access "
"it using OpenGIS compliant ST_AsText() or ST_AsBinary() functions that only "
"output 2D geometries. They do this by internally calling the ST_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:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:116
#, no-c-format
msgid ""
"UPDATE mytable SET the_geom = ST_Force_2d(the_geom); \n"
"VACUUM FULL ANALYZE mytable;"
msgstr ""
#. Tag: para
#: performance_tips.xml:118
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: performance_tips.xml:124
#, no-c-format
msgid ""
"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)&gt;2\" "
"skips re-writing of geometries that already are in 2D."
msgstr ""
#. Tag: title
#: performance_tips.xml:136
#, no-c-format
msgid "Tuning your configuration"
msgstr ""
#. Tag: para
#: performance_tips.xml:138
#, no-c-format
msgid ""
"These tips are taken from Kevin Neufeld's presentation \"Tips for the "
"PostGIS Power User\" at the FOSS4G 2007 conference. Depending on your use of "
"PostGIS (for example, static data and complex analysis vs frequently updated "
"data and lots of users) these changes can provide significant speedups to "
"your queries."
msgstr ""
#. Tag: para
#: performance_tips.xml:144
#, no-c-format
msgid ""
"For a more tips (and better formatting), the original presentation is at "
"<ulink url=\"http://2007.foss4g.org/presentations/view.php?"
"abstract_id=117\"> http://2007.foss4g.org/presentations/view.php?"
"abstract_id=117</ulink>."
msgstr ""
#. Tag: title
#: performance_tips.xml:151
#, no-c-format
msgid "Startup"
msgstr ""
#. Tag: para
#: performance_tips.xml:153
#, no-c-format
msgid "These settings are configured in postgresql.conf:"
msgstr ""
#. Tag: ulink
#: performance_tips.xml:158
#, no-c-format
msgid "checkpoint_segments"
msgstr ""
#. Tag: para
#: performance_tips.xml:163
#, no-c-format
msgid ""
"Maximum number of log file segments between automatic WAL checkpoints (each "
"segment is normally 16MB); default is 3"
msgstr ""
#. Tag: para
#: performance_tips.xml:169
#, no-c-format
msgid ""
"Set to at least 10 or 30 for databases with heavy write activity, or more "
"for large database loads. Another article on the topic worth reading <ulink "
"url=\"http://www.westnet.com/~gsmith/content/postgresql/chkp-bgw-83.htm"
"\">Greg Smith: Checkpoint and Background writer</ulink>"
msgstr ""
#. Tag: para
#: performance_tips.xml:175
#, no-c-format
msgid "Possibly store the xlog on a separate disk device"
msgstr ""
#. Tag: ulink
#: performance_tips.xml:182
#, no-c-format
msgid "constraint_exclusion"
msgstr ""
#. Tag: para
#: performance_tips.xml:187
#, no-c-format
msgid ""
"Default: off (prior to PostgreSQL 8.4 and for PostgreSQL 8.4+ is set to "
"partition)"
msgstr ""
#. Tag: para
#: performance_tips.xml:192
#, no-c-format
msgid ""
"This is generally used for table partitioning. If you are running PostgreSQL "
"versions below 8.4, set to \"on\" to ensure the query planner will optimize "
"as desired. As of PostgreSQL 8.4, the default for this is set to \"partition"
"\" which is ideal for PostgreSQL 8.4 and above since it will force the "
"planner to only analyze tables for constraint consideration if they are in "
"an inherited hierarchy and not pay the planner penalty otherwise."
msgstr ""
#. Tag: ulink
#: performance_tips.xml:202
#, no-c-format
msgid "shared_buffers"
msgstr ""
#. Tag: para
#: performance_tips.xml:207
#, no-c-format
msgid "Default: ~32MB"
msgstr ""
#. Tag: para
#: performance_tips.xml:212
#, no-c-format
msgid "Set to about 1/3 to 3/4 of available RAM"
msgstr ""
#. Tag: title
#: performance_tips.xml:220
#, no-c-format
msgid "Runtime"
msgstr ""
#. Tag: para
#: performance_tips.xml:222
#, no-c-format
msgid ""
"<ulink url=\"http://www.postgresql.org/docs/current/static/runtime-config-"
"resource.html#GUC-WORK-MEM\">work_mem</ulink> (the memory used for sort "
"operations and complex queries)"
msgstr ""
#. Tag: para
#: performance_tips.xml:228
#, no-c-format
msgid "Default: 1MB"
msgstr ""
#. Tag: para
#: performance_tips.xml:233
#, no-c-format
msgid "Adjust up for large dbs, complex queries, lots of RAM"
msgstr ""
#. Tag: para
#: performance_tips.xml:238
#, no-c-format
msgid "Adjust down for many concurrent users or low RAM."
msgstr ""
#. Tag: para
#: performance_tips.xml:243
#, no-c-format
msgid "If you have lots of RAM and few developers:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:245
#, no-c-format
msgid "SET work_mem TO 1200000;"
msgstr ""
#. Tag: para
#: performance_tips.xml:250
#, no-c-format
msgid ""
"<ulink url=\"http://www.postgresql.org/docs/current/static/runtime-config-"
"resource.html#GUC-MAINTENANCE-WORK-MEM\">maintenance_work_mem</ulink> (used "
"for VACUUM, CREATE INDEX, etc.)"
msgstr ""
#. Tag: para
#: performance_tips.xml:256
#, no-c-format
msgid "Default: 16MB"
msgstr ""
#. Tag: para
#: performance_tips.xml:261
#, no-c-format
msgid "Generally too low - ties up I/O, locks objects while swapping memory"
msgstr ""
#. Tag: para
#: performance_tips.xml:266
#, no-c-format
msgid ""
"Recommend 32MB to 256MB on production servers w/lots of RAM, but depends on "
"the # of concurrent users. If you have lots of RAM and few developers:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:269
#, no-c-format
msgid "SET maintainence_work_mem TO 1200000;"
msgstr ""

63
doc/po/it_IT/postgis.xml.po Normal file
View file

@ -0,0 +1,63 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: 2012-09-14 19:55+CEST\n"
"Last-Translator: Sandro Santilli <strk@keybit.net>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: postgis.xml:106
#, no-c-format
msgid "PostGIS &last_release_version; Manual"
msgstr "Manuale di PostGIS &last_release_version;"
#. Tag: affiliation
#: postgis.xml:114
#, no-c-format
msgid ""
"<orgname><ulink url=\"http://www.cleverelephant.ca\">clever elephant</"
"ulink></orgname> <address><city>Victoria</city> <state>British Columbia</"
"state> <country>Canada</country> <email>pramsey@cleverelephant.ca</email></"
"address>"
msgstr ""
#. Tag: para
#: postgis.xml:124
#, no-c-format
msgid ""
"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."
msgstr ""
"PostGIS e' un'estensione per la base di dati relazionale ad oggetti PostgreSQL "
"che consente di conservare oggetti GIS (Sistemi di Informazione Geografica) nella "
"base di dati. PostGIS include il supporto per gli indici spaziali di tipo R-Tree "
"basati sul GiST e le funzioni per l'analisi e il trattamento degli oggetti GIS."
#. Tag: para
#: postgis.xml:133
#, no-c-format
msgid "This is the manual for version &last_release_version;"
msgstr "Questo e' il manuale per la versione &last_release_version;"
#. Tag: para
#: postgis.xml:134
#, no-c-format
msgid ""
"This work is licensed under a <ulink url=\"http://creativecommons.org/"
"licenses/by-sa/3.0/\">Creative Commons Attribution-Share Alike 3.0 License</"
"ulink>. Feel free to use this material any way you like, but we ask that you "
"attribute credit to the PostGIS Project and wherever possible, a link back "
"to <ulink url=\"http://www.postgis.org\">http://www.postgis.org</ulink>."
msgstr ""

55
doc/po/it_IT/reference.xml.po Normal file
View file

@ -0,0 +1,55 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reference.xml:3
#, no-c-format
msgid "PostGIS Reference"
msgstr ""
#. Tag: para
#: reference.xml:5
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: reference.xml:11
#, no-c-format
msgid ""
"PostGIS has begun a transition from the existing naming convention to an SQL-"
"MM-centric convention. As a result, most of the functions that you know and "
"love have been renamed using the standard spatial type (ST) prefix. Previous "
"functions are still available, though are not listed in this document where "
"updated functions are equivalent. The non ST_ functions not listed in this "
"documentation are deprecated and will be removed in a future release so STOP "
"USING THEM."
msgstr ""
#. Tag: chapter
#: reference.xml:16
#, no-c-format
msgid ""
"&reference_type; &reference_management; &reference_constructor; "
"&reference_accessor; &reference_editor; &reference_output; "
"&reference_operator; &reference_measure; &reference_processing; "
"&reference_lrs; &reference_transaction; &reference_misc; "
"&reference_exception;"
msgstr ""

3337
doc/po/it_IT/reference_accessor.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

2934
doc/po/it_IT/reference_constructor.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

2417
doc/po/it_IT/reference_editor.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

224
doc/po/it_IT/reference_exception.xml.po Normal file
View file

@ -0,0 +1,224 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reference_exception.xml:3
#, no-c-format
msgid "Exceptional Functions"
msgstr ""
#. Tag: para
#: reference_exception.xml:4
#, no-c-format
msgid ""
"These functions are rarely used functions that should only be used if your "
"data is corrupted in someway. They are used for troubleshooting corruption "
"and also fixing things that should under normal circumstances, never happen."
msgstr ""
#. Tag: refname
#: reference_exception.xml:9
#, no-c-format
msgid "PostGIS_AddBBox"
msgstr ""
#. Tag: refpurpose
#: reference_exception.xml:11
#, no-c-format
msgid "Add bounding box to the geometry."
msgstr ""
#. Tag: funcprototype
#: reference_exception.xml:16
#, no-c-format
msgid ""
"<funcdef>geometry <function>PostGIS_AddBBox</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: title
#: reference_exception.xml:24 reference_exception.xml:70
#: reference_exception.xml:119
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: reference_exception.xml:26
#, no-c-format
msgid ""
"Add bounding box to the geometry. This would make bounding box based queries "
"faster, but will increase the size of the geometry."
msgstr ""
#. Tag: para
#: reference_exception.xml:31
#, no-c-format
msgid ""
"Bounding boxes are automatically added to geometries so in general this is "
"not needed unless the generated bounding box somehow becomes corrupted or "
"you have an old install that is lacking bounding boxes. Then you need to "
"drop the old and readd."
msgstr ""
#. Tag: para
#: reference_exception.xml:35 reference_exception.xml:83
#: reference_exception.xml:124
#, no-c-format
msgid "&curve_support;"
msgstr ""
#. Tag: title
#: reference_exception.xml:40 reference_exception.xml:88
#: reference_exception.xml:129
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: programlisting
#: reference_exception.xml:42
#, no-c-format
msgid ""
"UPDATE sometable\n"
" SET the_geom = PostGIS_AddBBox(the_geom)\n"
" WHERE PostGIS_HasBBox(the_geom) = false;"
msgstr ""
#. Tag: title
#: reference_exception.xml:47 reference_exception.xml:95
#: reference_exception.xml:136
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: para
#: reference_exception.xml:49
#, no-c-format
msgid ", <xref linkend=\"PostGIS_HasBBox\"/>"
msgstr ""
#. Tag: refname
#: reference_exception.xml:55
#, no-c-format
msgid "PostGIS_DropBBox"
msgstr ""
#. Tag: refpurpose
#: reference_exception.xml:57
#, no-c-format
msgid "Drop the bounding box cache from the geometry."
msgstr ""
#. Tag: funcprototype
#: reference_exception.xml:62
#, no-c-format
msgid ""
"<funcdef>geometry <function>PostGIS_DropBBox</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_exception.xml:72
#, no-c-format
msgid ""
"Drop the bounding box cache from the geometry. This reduces geometry size, "
"but makes bounding-box based queries slower. It is also used to drop a "
"corrupt bounding box. A tale-tell sign of a corrupt cached bounding box is "
"when your ST_Intersects and other relation queries leave out geometries that "
"rightfully should return true."
msgstr ""
#. Tag: para
#: reference_exception.xml:77
#, no-c-format
msgid ""
"Bounding boxes are automatically added to geometries and improve speed of "
"queries so in general this is not needed unless the generated bounding box "
"somehow becomes corrupted or you have an old install that is lacking "
"bounding boxes. Then you need to drop the old and readd. This kind of "
"corruption has been observed in 8.3-8.3.6 series whereby cached bboxes were "
"not always recalculated when a geometry changed and upgrading to a newer "
"version without a dump reload will not correct already corrupted boxes. So "
"one can manually correct using below and readd the bbox or do a dump reload."
msgstr ""
#. Tag: programlisting
#: reference_exception.xml:90
#, no-c-format
msgid ""
"--This example drops bounding boxes where the cached box is not correct\n"
" --The force to ST_AsBinary before applying Box2D "
"forces a recalculation of the box, and Box2D applied to the table geometry "
"always\n"
" -- returns the cached bounding box.\n"
" UPDATE sometable\n"
" SET the_geom = PostGIS_DropBBox(the_geom)\n"
" WHERE Not (Box2D(ST_AsBinary(the_geom)) = Box2D(the_geom));\n"
"\n"
" UPDATE sometable\n"
" SET the_geom = PostGIS_AddBBox(the_geom)\n"
" WHERE Not PostGIS_HasBBOX(the_geom);"
msgstr ""
#. Tag: para
#: reference_exception.xml:97
#, no-c-format
msgid ", <xref linkend=\"PostGIS_HasBBox\"/>, <xref linkend=\"Box2D\"/>"
msgstr ""
#. Tag: refname
#: reference_exception.xml:104
#, no-c-format
msgid "PostGIS_HasBBox"
msgstr ""
#. Tag: refpurpose
#: reference_exception.xml:106
#, no-c-format
msgid "Returns TRUE if the bbox of this geometry is cached, FALSE otherwise."
msgstr ""
#. Tag: funcprototype
#: reference_exception.xml:111
#, no-c-format
msgid ""
"<funcdef>boolean <function>PostGIS_HasBBox</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_exception.xml:121
#, no-c-format
msgid ""
"Returns TRUE if the bbox of this geometry is cached, FALSE otherwise. Use "
"<xref linkend=\"PostGIS_AddBBox\"/> and <xref linkend=\"PostGIS_DropBBox\"/> "
"to control caching."
msgstr ""
#. Tag: programlisting
#: reference_exception.xml:131
#, no-c-format
msgid ""
"SELECT the_geom\n"
"FROM sometable WHERE PostGIS_HasBBox(the_geom) = false;"
msgstr ""
#. Tag: para
#: reference_exception.xml:138
#, no-c-format
msgid ", <xref linkend=\"PostGIS_DropBBox\"/>"
msgstr ""

778
doc/po/it_IT/reference_lrs.xml.po Normal file
View file

@ -0,0 +1,778 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reference_lrs.xml:3
#, no-c-format
msgid "Linear Referencing"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:7
#, no-c-format
msgid "ST_Line_Interpolate_Point"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:9
#, no-c-format
msgid ""
"Returns a point interpolated along a line. Second argument is a float8 "
"between 0 and 1 representing fraction of total length of linestring the "
"point has to be located."
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:15
#, no-c-format
msgid ""
"<funcdef>geometry <function>ST_Line_Interpolate_Point</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>a_linestring</parameter></"
"paramdef> <paramdef><type>float </type> <parameter>a_fraction</parameter></"
"paramdef>"
msgstr ""
#. Tag: title
#: reference_lrs.xml:24 reference_lrs.xml:85 reference_lrs.xml:136
#: reference_lrs.xml:202 reference_lrs.xml:260 reference_lrs.xml:311
#: reference_lrs.xml:356 reference_lrs.xml:400
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: reference_lrs.xml:26
#, no-c-format
msgid ""
"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 linestring length the point has to be located."
msgstr ""
#. Tag: para
#: reference_lrs.xml:30 reference_lrs.xml:147
#, no-c-format
msgid ""
"See <xref linkend=\"ST_Line_Locate_Point\"/> for computing the line location "
"nearest to a Point."
msgstr ""
#. Tag: para
#: reference_lrs.xml:34
#, no-c-format
msgid ""
"Since release 1.1.1 this function also interpolates M and Z values (when "
"present), while prior releases set them to 0.0."
msgstr ""
#. Tag: para
#: reference_lrs.xml:38
#, no-c-format
msgid "Availability: 0.8.2, Z and M supported added in 1.1.1"
msgstr ""
#. Tag: para
#: reference_lrs.xml:39 reference_lrs.xml:157 reference_lrs.xml:319
#: reference_lrs.xml:362 reference_lrs.xml:406
#, no-c-format
msgid "&Z_support;"
msgstr ""
#. Tag: title
#: reference_lrs.xml:44 reference_lrs.xml:101 reference_lrs.xml:161
#: reference_lrs.xml:225 reference_lrs.xml:276 reference_lrs.xml:323
#: reference_lrs.xml:366 reference_lrs.xml:410
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: para
#: reference_lrs.xml:50
#, no-c-format
msgid "A linestring with the interpolated point at 20% position (0.20)"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:53
#, no-c-format
msgid ""
"--Return point 20% along 2d line\n"
"SELECT ST_AsEWKT(ST_Line_Interpolate_Point(the_line, 0.20))\n"
" FROM (SELECT ST_GeomFromEWKT('LINESTRING(25 50, 100 125, 150 190)') "
"as the_line) As foo;\n"
" st_asewkt\n"
"----------------\n"
" POINT(51.5974135047432 76.5974135047432)"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:54
#, no-c-format
msgid ""
"--Return point mid-way of 3d line\n"
"SELECT ST_AsEWKT(ST_Line_Interpolate_Point(the_line, 0.5))\n"
" FROM (SELECT ST_GeomFromEWKT('LINESTRING(1 2 3, 4 5 6, 6 7 8)') as "
"the_line) As foo;\n"
"\n"
" st_asewkt\n"
"--------------------\n"
" POINT(3.5 4.5 5.5)\n"
"\n"
"\n"
"--find closest point on a line to a point or other geometry\n"
" SELECT ST_AsText(ST_Line_Interpolate_Point(foo.the_line, "
"ST_Line_Locate_Point(foo.the_line, ST_GeomFromText('POINT(4 3)'))))\n"
"FROM (SELECT ST_GeomFromText('LINESTRING(1 2, 4 5, 6 7)') As the_line) As "
"foo;\n"
" st_astext\n"
"----------------\n"
" POINT(3 4)"
msgstr ""
#. Tag: title
#: reference_lrs.xml:59 reference_lrs.xml:108 reference_lrs.xml:175
#: reference_lrs.xml:231 reference_lrs.xml:283 reference_lrs.xml:330
#: reference_lrs.xml:372
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: para
#: reference_lrs.xml:61
#, no-c-format
msgid ""
", <xref linkend=\"ST_AsEWKT\"/>, <xref linkend=\"ST_Length\"/>, <xref "
"linkend=\"ST_Line_Locate_Point\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:67
#, no-c-format
msgid "ST_Line_Locate_Point"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:69
#, no-c-format
msgid ""
"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 2d line "
"length."
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:76
#, no-c-format
msgid ""
"<funcdef>float <function>ST_Line_Locate_Point</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>a_linestring</parameter></"
"paramdef> <paramdef><type>geometry </type> <parameter>a_point</parameter></"
"paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:87
#, no-c-format
msgid ""
"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 <link linkend="
"\"ST_Length2D\">2d line</link> length."
msgstr ""
#. Tag: para
#: reference_lrs.xml:91
#, no-c-format
msgid ""
"You can use the returned location to extract a Point (<xref linkend="
"\"ST_Line_Interpolate_Point\"/>) or a substring (<xref linkend="
"\"ST_Line_Substring\"/>)."
msgstr ""
#. Tag: para
#: reference_lrs.xml:94
#, no-c-format
msgid "This is useful for approximating numbers of addresses"
msgstr ""
#. Tag: para
#: reference_lrs.xml:96
#, no-c-format
msgid "Availability: 1.1.0"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:103
#, no-c-format
msgid ""
"--Rough approximation of finding the street number of a point along the "
"street\n"
"--Note the whole foo thing is just to generate dummy data that looks\n"
"--like house centroids and street\n"
"--We use ST_DWithin to exclude\n"
"--houses too far away from the street to be considered on the street\n"
"SELECT ST_AsText(house_loc) As as_text_house_loc,\n"
" startstreet_num +\n"
" CAST( (endstreet_num - startstreet_num)\n"
" * ST_Line_Locate_Point(street_line, house_loc) As "
"integer) As street_num\n"
"FROM\n"
"(SELECT ST_GeomFromText('LINESTRING(1 2, 3 4)') As street_line,\n"
" ST_MakePoint(x*1.01,y*1.03) As house_loc, 10 As startstreet_num,\n"
" 20 As endstreet_num\n"
"FROM generate_series(1,3) x CROSS JOIN generate_series(2,4) As y)\n"
"As foo\n"
"WHERE ST_DWithin(street_line, house_loc, 0.2);\n"
"\n"
" as_text_house_loc | street_num\n"
"-------------------+------------\n"
" POINT(1.01 2.06) | 10\n"
" POINT(2.02 3.09) | 15\n"
" POINT(3.03 4.12) | 20\n"
"\n"
" --find closest point on a line to a point or other geometry\n"
" SELECT ST_AsText(ST_Line_Interpolate_Point(foo.the_line, "
"ST_Line_Locate_Point(foo.the_line, ST_GeomFromText('POINT(4 3)'))))\n"
"FROM (SELECT ST_GeomFromText('LINESTRING(1 2, 4 5, 6 7)') As the_line) As "
"foo;\n"
" st_astext\n"
"----------------\n"
" POINT(3 4)"
msgstr ""
#. Tag: para
#: reference_lrs.xml:110
#, no-c-format
msgid ""
", <xref linkend=\"ST_Length2D\"/>, <xref linkend=\"ST_Line_Interpolate_Point"
"\"/>, <xref linkend=\"ST_Line_Substring\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:116
#, no-c-format
msgid "ST_Line_Substring"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:118
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:126
#, no-c-format
msgid ""
"<funcdef>geometry <function>ST_Line_Substring</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>a_linestring</parameter></"
"paramdef> <paramdef><type>float </type> <parameter>startfraction</"
"parameter></paramdef> <paramdef><type>float </type> <parameter>endfraction</"
"parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:138
#, no-c-format
msgid ""
"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. This only works with LINESTRINGs. To use with "
"contiguous MULTILINESTRINGs use in conjunction with <xref linkend="
"\"ST_LineMerge\"/>."
msgstr ""
#. Tag: para
#: reference_lrs.xml:144
#, no-c-format
msgid ""
"If 'start' and 'end' have the same value this is equivalent to <xref linkend="
"\"ST_Line_Interpolate_Point\"/>."
msgstr ""
#. Tag: para
#: reference_lrs.xml:151
#, no-c-format
msgid ""
"Since release 1.1.1 this function also interpolates M and Z values (when "
"present), while prior releases set them to unspecified values."
msgstr ""
#. Tag: para
#: reference_lrs.xml:156
#, no-c-format
msgid "Availability: 1.1.0, Z and M supported added in 1.1.1"
msgstr ""
#. Tag: para
#: reference_lrs.xml:167
#, no-c-format
msgid "A linestring seen with 1/3 midrange overlaid (0.333, 0.666)"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:170
#, no-c-format
msgid ""
"--Return the approximate 1/3 mid-range part of a linestring\n"
"SELECT ST_AsText(ST_Line_SubString(ST_GeomFromText('LINESTRING(25 50, 100 "
"125, 150 190)'), 0.333, 0.666));\n"
"\n"
" st_astext\n"
"------------------------------------------------------------------------------------------------\n"
"LINESTRING(69.2846934853974 94.2846934853974,100 125,111.700356260683 "
"140.210463138888)\n"
"\n"
"--The below example simulates a while loop in\n"
"--SQL using PostgreSQL generate_series() to cut all\n"
"--linestrings in a table to 100 unit segments\n"
"-- of which no segment is longer than 100 units\n"
"-- units are measured in the SRID units of measurement\n"
"-- It also assumes all geometries are LINESTRING or contiguous "
"MULTILINESTRING\n"
"--and no geometry is longer than 100 units*10000\n"
"--for better performance you can reduce the 10000\n"
"--to match max number of segments you expect\n"
"\n"
"SELECT field1, field2, ST_Line_Substring(the_geom, 100.00*n/length,\n"
" CASE\n"
" WHEN 100.00*(n+1) &lt; length THEN 100.00*(n+1)/length\n"
" ELSE 1\n"
" END) As the_geom\n"
"FROM\n"
" (SELECT sometable.field1, sometable.field2,\n"
" ST_LineMerge(sometable.the_geom) AS the_geom,\n"
" ST_Length(sometable.the_geom) As length\n"
" FROM sometable\n"
" ) AS t\n"
"CROSS JOIN generate_series(0,10000) AS n\n"
"WHERE n*100.00/length &lt; 1;"
msgstr ""
#. Tag: para
#: reference_lrs.xml:177
#, no-c-format
msgid ""
", <xref linkend=\"ST_Line_Interpolate_Point\"/>, <xref linkend=\"ST_LineMerge"
"\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:183
#, no-c-format
msgid "ST_LocateAlong"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:185
#, no-c-format
msgid ""
"<refpurpose>Return a derived geometry collection value with elements that "
"match the specified measure. Polygonal elements are not supported.</"
"refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:192
#, no-c-format
msgid ""
"<funcdef>geometry <function>ST_LocateAlong</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>ageom_with_measure</parameter></"
"paramdef> <paramdef><type>float </type> <parameter>a_measure</parameter></"
"paramdef> <paramdef choice=\"opt\"><type>float </type> <parameter>offset</"
"parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:204
#, no-c-format
msgid ""
"<para>Return a derived geometry collection value with elements that match "
"the specified measure. Polygonal elements are not supported.</para>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:208
#, no-c-format
msgid ""
"If an offset is provided, the resultant will be offset to the left or right "
"of the input line by the specified number of units. A positive offset will "
"be to the left, and a negative one to the right."
msgstr ""
#. Tag: para
#: reference_lrs.xml:213 reference_lrs.xml:266
#, no-c-format
msgid ""
"Semantic is specified by: ISO/IEC CD 13249-3:200x(E) - Text for Continuation "
"CD Editing Meeting"
msgstr ""
#. Tag: para
#: reference_lrs.xml:216
#, no-c-format
msgid "Availability: 1.1.0 by old name ST_Locate_Along_Measure."
msgstr ""
#. Tag: para
#: reference_lrs.xml:217
#, no-c-format
msgid ""
"Changed: 2.0.0 in prior versions this used to be called "
"ST_Locate_Along_Measure. The old name has been deprecated and will be "
"removed in the future but is still available."
msgstr ""
#. Tag: para
#: reference_lrs.xml:218
#, no-c-format
msgid "Use this function only for geometries with an M component"
msgstr ""
#. Tag: para
#: reference_lrs.xml:220 reference_lrs.xml:272
#, no-c-format
msgid "&M_support;"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:226
#, no-c-format
msgid ""
"SELECT ST_AsText(the_geom)\n"
" FROM\n"
" (SELECT ST_LocateAlong(\n"
" ST_GeomFromText('MULTILINESTRINGM((1 2 3, 3 4 2, 9 4 "
"3),\n"
" (1 2 3, 5 4 5))'),3) As the_geom) As foo;\n"
"\n"
" st_asewkt\n"
"-----------------------------------------------------------\n"
" MULTIPOINT M (1 2 3)\n"
"\n"
"--Geometry collections are difficult animals so dump them\n"
"--to make them more digestable\n"
"SELECT ST_AsText((ST_Dump(the_geom)).geom)\n"
" FROM\n"
" (SELECT ST_LocateAlong(\n"
" ST_GeomFromText('MULTILINESTRINGM((1 2 3, 3 4 2, 9 4 "
"3),\n"
" (1 2 3, 5 4 5))'),3) As the_geom) As foo;\n"
"\n"
" st_asewkt\n"
"---------------\n"
" POINTM(1 2 3)\n"
" POINTM(9 4 3)\n"
" POINTM(1 2 3)"
msgstr ""
#. Tag: para
#: reference_lrs.xml:233
#, no-c-format
msgid ", <xref linkend=\"ST_LocateBetween\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:239
#, no-c-format
msgid "ST_LocateBetween"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:241
#, no-c-format
msgid ""
"<refpurpose>Return a derived geometry collection value with elements that "
"match the specified range of measures inclusively. Polygonal elements are "
"not supported.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:248
#, no-c-format
msgid ""
"<funcdef>geometry <function>ST_LocateBetween</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef> "
"<paramdef><type>float </type> <parameter>measure_start</parameter></"
"paramdef> <paramdef><type>float </type> <parameter>measure_end</parameter></"
"paramdef> <paramdef choice=\"opt\"><type>float </type> <parameter>offset</"
"parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:262
#, no-c-format
msgid ""
"<para>Return a derived geometry collection value with elements that match "
"the specified range of measures inclusively. Polygonal elements are not "
"supported.</para>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:269
#, no-c-format
msgid "Availability: 1.1.0 by old name ST_Locate_Between_Measures."
msgstr ""
#. Tag: para
#: reference_lrs.xml:270
#, no-c-format
msgid ""
"Changed: 2.0.0 - in prior versions this used to be called "
"ST_Locate_Between_Measures. The old name has been deprecated and will be "
"removed in the future but is still available for backward compatibility."
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:278
#, no-c-format
msgid ""
"SELECT ST_AsText(the_geom)\n"
" FROM\n"
" (SELECT ST_LocateBetween(\n"
" ST_GeomFromText('MULTILINESTRING M ((1 2 3, 3 4 2, 9 "
"4 3),\n"
" (1 2 3, 5 4 5))'),1.5, 3) As the_geom) As foo;\n"
"\n"
" st_asewkt\n"
"------------------------------------------------------------------------\n"
" GEOMETRYCOLLECTION M (LINESTRING M (1 2 3,3 4 2,9 4 3),POINT M (1 2 3))\n"
"\n"
"--Geometry collections are difficult animals so dump them\n"
"--to make them more digestable\n"
"SELECT ST_AsText((ST_Dump(the_geom)).geom)\n"
" FROM\n"
" (SELECT ST_LocateBetween(\n"
" ST_GeomFromText('MULTILINESTRING M ((1 2 3, 3 4 2, 9 "
"4 3),\n"
" (1 2 3, 5 4 5))'),1.5, 3) As the_geom) As foo;\n"
"\n"
" st_asewkt\n"
"--------------------------------\n"
" LINESTRING M (1 2 3,3 4 2,9 4 3)\n"
" POINT M (1 2 3)"
msgstr ""
#. Tag: para
#: reference_lrs.xml:285
#, no-c-format
msgid ", <xref linkend=\"ST_LocateAlong\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:291
#, no-c-format
msgid "ST_LocateBetweenElevations"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:293
#, no-c-format
msgid ""
"Return a derived geometry (collection) value with elements that intersect "
"the specified range of elevations inclusively. Only 3D, 4D LINESTRINGS and "
"MULTILINESTRINGS are supported."
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:300
#, no-c-format
msgid ""
"<funcdef>geometry <function>ST_LocateBetweenElevations</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>geom_mline</parameter></"
"paramdef> <paramdef><type>float </type> <parameter>elevation_start</"
"parameter></paramdef> <paramdef><type>float </type> "
"<parameter>elevation_end</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:313
#, no-c-format
msgid ""
"Return a derived geometry (collection) value with elements that intersect "
"the specified range of elevations inclusively. Only 3D, 3DM LINESTRINGS and "
"MULTILINESTRINGS are supported."
msgstr ""
#. Tag: para
#: reference_lrs.xml:317
#, no-c-format
msgid "Availability: 1.4.0"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:325
#, no-c-format
msgid ""
"SELECT ST_AsEWKT(ST_LocateBetweenElevations(\n"
" ST_GeomFromEWKT('LINESTRING(1 2 3, 4 5 6)'),2,4)) As "
"ewelev;\n"
" ewelev\n"
"----------------------------------------------------------------\n"
" MULTILINESTRING((1 2 3,2 3 4))\n"
"\n"
"SELECT ST_AsEWKT(ST_LocateBetweenElevations(\n"
" ST_GeomFromEWKT('LINESTRING(1 2 6, 4 5 -1, 7 8 "
"9)'),6,9)) As ewelev;\n"
"\n"
" ewelev\n"
"----------------------------------------------------------------\n"
"GEOMETRYCOLLECTION(POINT(1 2 6),LINESTRING(6.1 7.1 6,7 8 9))\n"
"\n"
"--Geometry collections are difficult animals so dump them\n"
"--to make them more digestable\n"
"SELECT ST_AsEWKT((ST_Dump(the_geom)).geom)\n"
" FROM\n"
" (SELECT ST_LocateBetweenElevations(\n"
" ST_GeomFromEWKT('LINESTRING(1 2 6, 4 5 -1, 7 8 "
"9)'),6,9) As the_geom) As foo;\n"
"\n"
" st_asewkt\n"
"--------------------------------\n"
"POINT(1 2 6)\n"
"LINESTRING(6.1 7.1 6,7 8 9)"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:339
#, no-c-format
msgid "ST_InterpolatePoint"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:341
#, no-c-format
msgid ""
"<refpurpose>Return the value of the measure dimension of a geometry at the "
"point closed to the provided point.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:346
#, no-c-format
msgid ""
"<funcdef>float <function>ST_InterpolatePoint</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>line</parameter></paramdef> "
"<paramdef><type>geometry </type> <parameter>point</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:358
#, no-c-format
msgid ""
"<para>Return the value of the measure dimension of a geometry at the point "
"closed to the provided point.</para>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:360
#, no-c-format
msgid "Availability: 2.0.0"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:368
#, no-c-format
msgid ""
"SELECT ST_InterpolatePoint('LINESTRING M (0 0 0, 10 0 20)', 'POINT(5 5)');\n"
" st_interpolatepoint \n"
" ---------------------\n"
" 10"
msgstr ""
#. Tag: para
#: reference_lrs.xml:374
#, no-c-format
msgid ""
", <xref linkend=\"ST_LocateAlong\"/>, <xref linkend=\"ST_LocateBetween\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:382
#, no-c-format
msgid "ST_AddMeasure"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:384
#, no-c-format
msgid ""
"<refpurpose>Return a derived geometry with measure elements linearly "
"interpolated between the start and end points. If the geometry has no "
"measure dimension, one is added. If the geometry has a measure dimension, it "
"is over-written with new values. Only LINESTRINGS and MULTILINESTRINGS are "
"supported.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:389
#, no-c-format
msgid ""
"<funcdef>geometry <function>ST_AddMeasure</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>geom_mline</parameter></"
"paramdef> <paramdef><type>float </type> <parameter>measure_start</"
"parameter></paramdef> <paramdef><type>float </type> <parameter>measure_end</"
"parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:402
#, no-c-format
msgid ""
"<para>Return a derived geometry with measure elements linearly interpolated "
"between the start and end points. If the geometry has no measure dimension, "
"one is added. If the geometry has a measure dimension, it is over-written "
"with new values. Only LINESTRINGS and MULTILINESTRINGS are supported.</para>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:404
#, no-c-format
msgid "Availability: 1.5.0"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:412
#, no-c-format
msgid ""
"SELECT ST_AsText(ST_AddMeasure(\n"
"ST_GeomFromEWKT('LINESTRING(1 0, 2 0, 4 0)'),1,4)) As ewelev;\n"
" ewelev \n"
"--------------------------------\n"
" LINESTRINGM(1 0 1,2 0 2,4 0 4)\n"
"\n"
"SELECT ST_AsText(ST_AddMeasure(\n"
"ST_GeomFromEWKT('LINESTRING(1 0 4, 2 0 4, 4 0 4)'),10,40)) As ewelev;\n"
" ewelev \n"
"----------------------------------------\n"
" LINESTRING(1 0 4 10,2 0 4 20,4 0 4 40)\n"
"\n"
"SELECT ST_AsText(ST_AddMeasure(\n"
"ST_GeomFromEWKT('LINESTRINGM(1 0 4, 2 0 4, 4 0 4)'),10,40)) As ewelev;\n"
" ewelev \n"
"----------------------------------------\n"
" LINESTRINGM(1 0 10,2 0 20,4 0 40)\n"
" \n"
"SELECT ST_AsText(ST_AddMeasure(\n"
"ST_GeomFromEWKT('MULTILINESTRINGM((1 0 4, 2 0 4, 4 0 4),(1 0 4, 2 0 4, 4 0 "
"4))'),10,70)) As ewelev;\n"
" ewelev \n"
"-----------------------------------------------------------------\n"
" MULTILINESTRINGM((1 0 10,2 0 20,4 0 40),(1 0 40,2 0 50,4 0 70))"
msgstr ""

1143
doc/po/it_IT/reference_management.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

4934
doc/po/it_IT/reference_measure.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

855
doc/po/it_IT/reference_misc.xml.po Normal file
View file

@ -0,0 +1,855 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reference_misc.xml:3
#, no-c-format
msgid "Miscellaneous Functions"
msgstr ""
#. Tag: refname
#: reference_misc.xml:7
#, no-c-format
msgid "ST_Accum"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:9
#, no-c-format
msgid "<refpurpose>Aggregate. Constructs an array of geometries.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:14
#, no-c-format
msgid ""
"<funcdef>geometry[] <function>ST_Accum</function></funcdef> "
"<paramdef><type>geometry set</type> <parameter>geomfield</parameter></"
"paramdef>"
msgstr ""
#. Tag: title
#: reference_misc.xml:22 reference_misc.xml:64 reference_misc.xml:106
#: reference_misc.xml:158 reference_misc.xml:229 reference_misc.xml:289
#: reference_misc.xml:343 reference_misc.xml:396 reference_misc.xml:438
#: reference_misc.xml:488
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: reference_misc.xml:24
#, no-c-format
msgid "<para>Aggregate. Constructs an array of geometries.</para>"
msgstr ""
#. Tag: para
#: reference_misc.xml:25 reference_misc.xml:68 reference_misc.xml:109
#: reference_misc.xml:255 reference_misc.xml:309 reference_misc.xml:355
#, no-c-format
msgid ""
"Enhanced: 2.0.0 support for Polyhedral surfaces, Triangles and TIN was "
"introduced."
msgstr ""
#. Tag: para
#: reference_misc.xml:26 reference_misc.xml:113 reference_misc.xml:357
#: reference_misc.xml:447
#, no-c-format
msgid "&Z_support;"
msgstr ""
#. Tag: para
#: reference_misc.xml:27 reference_misc.xml:69 reference_misc.xml:110
#: reference_misc.xml:183 reference_misc.xml:358 reference_misc.xml:448
#, no-c-format
msgid "&curve_support;"
msgstr ""
#. Tag: para
#: reference_misc.xml:28 reference_misc.xml:70 reference_misc.xml:111
#: reference_misc.xml:256 reference_misc.xml:310 reference_misc.xml:359
#: reference_misc.xml:449
#, no-c-format
msgid "&P_support;"
msgstr ""
#. Tag: para
#: reference_misc.xml:29 reference_misc.xml:71 reference_misc.xml:112
#: reference_misc.xml:257 reference_misc.xml:311 reference_misc.xml:360
#: reference_misc.xml:450
#, no-c-format
msgid "&T_support;"
msgstr ""
#. Tag: title
#: reference_misc.xml:34 reference_misc.xml:76 reference_misc.xml:118
#: reference_misc.xml:188 reference_misc.xml:262 reference_misc.xml:316
#: reference_misc.xml:364 reference_misc.xml:408 reference_misc.xml:455
#: reference_misc.xml:499
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:36
#, no-c-format
msgid ""
"SELECT (ST_Accum(the_geom)) As all_em, ST_AsText((ST_Accum(the_geom))[1]) As "
"grabone,\n"
"(ST_Accum(the_geom))[2:4] as grab_rest\n"
" FROM (SELECT ST_MakePoint(a*CAST(random()*10 As "
"integer), a*CAST(random()*10 As integer), a*CAST(random()*10 As integer)) As "
"the_geom\n"
" FROM generate_series(1,4) a) As foo;\n"
"\n"
"all_em|grabone | grab_rest\n"
"\n"
"-------------------------------------------------------------------------------"
"+\n"
"\n"
" {0101000080000000000000144000000000000024400000000000001040:\n"
" 0101000080000000000\n"
"00018400000000000002C400000000000003040:\n"
"0101000080000000000000354000000000000038400000000000001840:\n"
"010100008000000000000040400000000000003C400000000000003040} |\n"
" POINT(5 10) | {010100008000000000000018400000000000002C400000000000003040:\n"
" 0101000080000000000000354000000000000038400000000000001840:\n"
" 010100008000000000000040400000000000003C400000000000003040}\n"
"(1 row)"
msgstr ""
#. Tag: title
#: reference_misc.xml:41 reference_misc.xml:83 reference_misc.xml:125
#: reference_misc.xml:195 reference_misc.xml:268 reference_misc.xml:322
#: reference_misc.xml:369 reference_misc.xml:415 reference_misc.xml:462
#: reference_misc.xml:506
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: refname
#: reference_misc.xml:49
#, no-c-format
msgid "Box2D"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:51
#, no-c-format
msgid ""
"<refpurpose>Returns a BOX2D representing the maximum extents of the geometry."
"</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:56
#, no-c-format
msgid ""
"<funcdef>box2d <function>Box2D</function></funcdef> <paramdef><type>geometry "
"</type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:66
#, no-c-format
msgid ""
"<para>Returns a BOX2D representing the maximum extents of the geometry.</"
"para>"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:78
#, no-c-format
msgid ""
"SELECT Box2D(ST_GeomFromText('LINESTRING(1 2, 3 4, 5 6)'));\n"
" box2d\n"
" ---------\n"
" BOX(1 2,5 6)\n"
"\n"
" SELECT Box2D(ST_GeomFromText('CIRCULARSTRING(220268 150415,220227 "
"150505,220227 150406)'));\n"
" box2d\n"
" --------\n"
" BOX(220186.984375 150406,220288.25 150506.140625)"
msgstr ""
#. Tag: para
#: reference_misc.xml:85
#, no-c-format
msgid ", <xref linkend=\"ST_GeomFromText\"/>"
msgstr ""
#. Tag: refname
#: reference_misc.xml:91
#, no-c-format
msgid "Box3D"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:93
#, no-c-format
msgid ""
"<refpurpose>Returns a BOX3D representing the maximum extents of the geometry."
"</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:98
#, no-c-format
msgid ""
"<funcdef>box3d <function>Box3D</function></funcdef> <paramdef><type>geometry "
"</type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:108
#, no-c-format
msgid ""
"<para>Returns a BOX3D representing the maximum extents of the geometry.</"
"para>"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:120
#, no-c-format
msgid ""
"SELECT Box3D(ST_GeomFromEWKT('LINESTRING(1 2 3, 3 4 5, 5 6 5)'));\n"
" Box3d\n"
" ---------\n"
" BOX3D(1 2 3,5 6 5)\n"
"\n"
" SELECT Box3D(ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 "
"150505 1,220227 150406 1)'));\n"
" Box3d\n"
" --------\n"
" BOX3D(220227 150406 1,220268 150415 1)"
msgstr ""
#. Tag: para
#: reference_misc.xml:127
#, no-c-format
msgid ", <xref linkend=\"ST_GeomFromEWKT\"/>"
msgstr ""
#. Tag: refname
#: reference_misc.xml:133
#, no-c-format
msgid "ST_EstimatedExtent"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:135
#, no-c-format
msgid ""
"<refpurpose>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.</refpurpose>"
msgstr ""
#. Tag: funcsynopsis
#: reference_misc.xml:141
#, no-c-format
msgid ""
"<funcprototype> <funcdef>box2d <function>ST_EstimatedExtent</function></"
"funcdef> <paramdef><type>text </type> <parameter>schema_name</parameter></"
"paramdef> <paramdef><type>text </type> <parameter>table_name</parameter></"
"paramdef> <paramdef><type>text </type> <parameter>geocolumn_name</"
"parameter></paramdef> </funcprototype> <funcprototype> <funcdef>box2d "
"<function>ST_EstimatedExtent</function></funcdef> <paramdef><type>text </"
"type> <parameter>table_name</parameter></paramdef> <paramdef><type>text </"
"type> <parameter>geocolumn_name</parameter></paramdef> </funcprototype>"
msgstr ""
#. Tag: para
#: reference_misc.xml:160
#, no-c-format
msgid ""
"<para>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.</para>"
msgstr ""
#. Tag: para
#: reference_misc.xml:164
#, no-c-format
msgid ""
"For PostgreSQL&gt;=8.0.0 statistics are gathered by VACUUM ANALYZE and "
"resulting extent will be about 95% of the real one."
msgstr ""
#. Tag: para
#: reference_misc.xml:169
#, no-c-format
msgid ""
"In absence of statistics (empty table or no ANALYZE called) this function "
"returns NULL. Prior to version 1.5.4 an exception was thrown instead."
msgstr ""
#. Tag: para
#: reference_misc.xml:177
#, no-c-format
msgid ""
"For PostgreSQL&lt;8.0.0 statistics are gathered by update_geometry_stats() "
"and resulting extent will be exact."
msgstr ""
#. Tag: para
#: reference_misc.xml:180
#, no-c-format
msgid "Availability: 1.0.0"
msgstr ""
#. Tag: para
#: reference_misc.xml:181
#, no-c-format
msgid "Changed: 2.1.0. Up to 2.0.x this was called ST_Estimated_Extent."
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:190
#, no-c-format
msgid ""
"SELECT ST_EstimatedExtent('ny', 'edges', 'the_geom');\n"
"--result--\n"
"BOX(-8877653 4912316,-8010225.5 5589284)\n"
"\n"
"SELECT ST_EstimatedExtent('feature_poly', 'the_geom');\n"
"--result--\n"
"BOX(-124.659652709961 24.6830825805664,-67.7798080444336 49.0012092590332)"
msgstr ""
#. Tag: refname
#: reference_misc.xml:202
#, no-c-format
msgid "ST_Expand"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:203
#, no-c-format
msgid ""
"Returns bounding box expanded in all directions from the bounding box of the "
"input geometry. Uses double-precision"
msgstr ""
#. Tag: funcsynopsis
#: reference_misc.xml:207
#, no-c-format
msgid ""
"<funcprototype> <funcdef>geometry <function>ST_Expand</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>g1</parameter></paramdef> "
"<paramdef><type>float</type> <parameter>units_to_expand</parameter></"
"paramdef> </funcprototype> <funcprototype> <funcdef>box2d "
"<function>ST_Expand</function></funcdef> <paramdef><type>box2d </type> "
"<parameter>g1</parameter></paramdef> <paramdef><type>float</type> "
"<parameter>units_to_expand</parameter></paramdef> </funcprototype> "
"<funcprototype> <funcdef>box3d <function>ST_Expand</function></funcdef> "
"<paramdef><type>box3d </type> <parameter>g1</parameter></paramdef> "
"<paramdef><type>float</type> <parameter>units_to_expand</parameter></"
"paramdef> </funcprototype>"
msgstr ""
#. Tag: para
#: reference_misc.xml:231
#, no-c-format
msgid ""
"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. Uses double-precision. Very useful for distance() queries, or "
"bounding box queries to add an index filter to the query."
msgstr ""
#. Tag: para
#: reference_misc.xml:235
#, no-c-format
msgid ""
"There are 3 variants of this. The one that takes a geometry will return a "
"POLYGON geometry representation of the bounding box and is the most commonly "
"used variant."
msgstr ""
#. Tag: para
#: reference_misc.xml:237
#, no-c-format
msgid ""
"ST_Expand is similar in concept to ST_Buffer except while buffer expands the "
"geometry in all directions, ST_Expand expands the bounding box an x,y,z unit "
"amount."
msgstr ""
#. Tag: para
#: reference_misc.xml:239
#, no-c-format
msgid ""
"Units are in the units of the spatial reference system in use denoted by the "
"SRID"
msgstr ""
#. Tag: para
#: reference_misc.xml:242
#, no-c-format
msgid ""
"Pre 1.3, ST_Expand was used in conjunction with distance to do indexable "
"queries. Something of the form <code>the_geom &amp;&amp; ST_Expand('POINT(10 "
"20)', 10) AND ST_Distance(the_geom, 'POINT(10 20)') &lt; 10</code> Post 1.2, "
"this was replaced with the easier ST_DWithin construct."
msgstr ""
#. Tag: para
#: reference_misc.xml:248
#, no-c-format
msgid ""
"Bounding boxes of all geometries are currently 2-d even if they are 3-"
"dimensional geometries."
msgstr ""
#. Tag: para
#: reference_misc.xml:252
#, no-c-format
msgid ""
"Availability: 1.5.0 behavior changed to output double precision instead of "
"float4 coordinates."
msgstr ""
#. Tag: para
#: reference_misc.xml:263
#, no-c-format
msgid ""
"Examples below use US National Atlas Equal Area (SRID=2163) which is a meter "
"projection"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:264
#, no-c-format
msgid ""
"<!-- TODO: fix results of documentation to reflect new behavior -->\n"
"--10 meter expanded box around bbox of a linestring\n"
"SELECT CAST(ST_Expand(ST_GeomFromText('LINESTRING(2312980 110676,2312923 "
"110701,2312892 110714)', 2163),10) As box2d);\n"
" st_expand\n"
"------------------------------------\n"
" BOX(2312882 110666,2312990 110724)\n"
"\n"
"--10 meter expanded 3d box of a 3d box\n"
"SELECT ST_Expand(CAST('BOX3D(778783 2951741 1,794875 2970042.61545891 10)' "
"As box3d),10)\n"
" st_expand\n"
"-----------------------------------------------------\n"
" BOX3D(778773 2951731 -9,794885 2970052.61545891 20)\n"
"\n"
" --10 meter geometry astext rep of a expand box around a point geometry\n"
" SELECT ST_AsEWKT(ST_Expand(ST_GeomFromEWKT('SRID=2163;POINT(2312980 "
"110676)'),10));\n"
" st_asewkt\n"
"-------------------------------------------------------------------------------------------------\n"
" SRID=2163;POLYGON((2312970 110666,2312970 110686,2312990 110686,2312990 "
"110666,2312970 110666))"
msgstr ""
#. Tag: para
#: reference_misc.xml:269
#, no-c-format
msgid ""
", <xref linkend=\"ST_Buffer\"/>, <xref linkend=\"ST_DWithin\"/>, <xref "
"linkend=\"ST_GeomFromEWKT\"/>, <xref linkend=\"ST_GeomFromText\"/>, <xref "
"linkend=\"ST_SRID\"/>"
msgstr ""
#. Tag: refname
#: reference_misc.xml:275
#, no-c-format
msgid "ST_Extent"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:276
#, no-c-format
msgid ""
"an aggregate function that returns the bounding box that bounds rows of "
"geometries."
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:281
#, no-c-format
msgid ""
"<funcdef>box2d <function>ST_Extent</function></funcdef> "
"<paramdef><type>geometry set</type> <parameter>geomfield</parameter></"
"paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:291
#, no-c-format
msgid ""
"ST_Extent returns a bounding box that encloses a set of geometries. The "
"ST_Extent function is an \"aggregate\" function in the terminology of SQL. "
"That means that it operates on lists of data, in the same way the SUM() and "
"AVG() functions do."
msgstr ""
#. Tag: para
#: reference_misc.xml:294 reference_misc.xml:348
#, no-c-format
msgid ""
"Since it returns a bounding box, the spatial Units are in the units of the "
"spatial reference system in use denoted by the SRID"
msgstr ""
#. Tag: para
#: reference_misc.xml:295
#, no-c-format
msgid ""
"ST_Extent is similar in concept to Oracle Spatial/Locator's SDO_AGGR_MBR"
msgstr ""
#. Tag: para
#: reference_misc.xml:297
#, no-c-format
msgid ""
"Since ST_Extent returns a bounding box, the SRID meta-data is lost. Use "
"ST_SetSRID to force it back into a geometry with SRID meta data. The "
"coordinates are in the units of the spatial ref of the orginal geometries."
msgstr ""
#. Tag: para
#: reference_misc.xml:302
#, no-c-format
msgid ""
"ST_Extent will return boxes with only an x and y component even with (x,y,z) "
"coordinate geometries. To maintain x,y,z use ST_3DExtent instead."
msgstr ""
#. Tag: para
#: reference_misc.xml:306
#, no-c-format
msgid "Availability: 1.4.0"
msgstr ""
#. Tag: para
#: reference_misc.xml:317
#, no-c-format
msgid "Examples below use Massachusetts State Plane ft (SRID=2249)"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:318
#, no-c-format
msgid ""
"SELECT ST_Extent(the_geom) as bextent FROM sometable;\n"
" st_bextent\n"
"------------------------------------\n"
"BOX(739651.875 2908247.25,794875.8125 2970042.75)\n"
"\n"
"\n"
"--Return extent of each category of geometries\n"
"SELECT ST_Extent(the_geom) as bextent\n"
"FROM sometable\n"
"GROUP BY category ORDER BY category;\n"
"\n"
" bextent "
"| name\n"
"----------------------------------------------------+----------------\n"
" BOX(778783.5625 2951741.25,794875.8125 2970042.75) | A\n"
" BOX(751315.8125 2919164.75,765202.6875 2935417.25) | B\n"
" BOX(739651.875 2917394.75,756688.375 2935866) | C\n"
"\n"
" --Force back into a geometry\n"
" -- and render the extended text representation of that geometry\n"
"SELECT ST_SetSRID(ST_Extent(the_geom),2249) as bextent FROM sometable;\n"
"\n"
" bextent\n"
"--------------------------------------------------------------------------------\n"
" SRID=2249;POLYGON((739651.875 2908247.25,739651.875 2970042.75,794875.8125 "
"2970042.75,\n"
" 794875.8125 2908247.25,739651.875 2908247.25))"
msgstr ""
#. Tag: para
#: reference_misc.xml:323
#, no-c-format
msgid ""
", <xref linkend=\"ST_3DExtent\"/>, <xref linkend=\"ST_SetSRID\"/>, <xref "
"linkend=\"ST_SRID\"/>"
msgstr ""
#. Tag: refname
#: reference_misc.xml:329
#, no-c-format
msgid "ST_3DExtent"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:330
#, no-c-format
msgid ""
"an aggregate function that returns the box3D bounding box that bounds rows "
"of geometries."
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:335
#, no-c-format
msgid ""
"<funcdef>box3d <function>ST_3DExtent</function></funcdef> "
"<paramdef><type>geometry set</type> <parameter>geomfield</parameter></"
"paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:345
#, no-c-format
msgid ""
"ST_3DExtent returns a box3d (includes Z coordinate) bounding box that "
"encloses a set of geometries. The ST_3DExtent function is an \"aggregate\" "
"function in the terminology of SQL. That means that it operates on lists of "
"data, in the same way the SUM() and AVG() functions do."
msgstr ""
#. Tag: para
#: reference_misc.xml:351
#, no-c-format
msgid ""
"Since ST_3DExtent returns a bounding box, the SRID meta-data is lost. Use "
"ST_SetSRID to force it back into a geometry with SRID meta data. The "
"coordinates are in the units of the spatial ref of the orginal geometries."
msgstr ""
#. Tag: para
#: reference_misc.xml:356
#, no-c-format
msgid "Changed: 2.0.0 In prior versions this used to be called ST_Extent3D"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:365
#, no-c-format
msgid ""
"SELECT ST_3DExtent(foo.the_geom) As b3extent\n"
"FROM (SELECT ST_MakePoint(x,y,z) As the_geom\n"
" FROM generate_series(1,3) As x\n"
" CROSS JOIN generate_series(1,2) As y\n"
" CROSS JOIN generate_series(0,2) As Z) As foo;\n"
" b3extent\n"
"--------------------\n"
" BOX3D(1 1 0,3 2 2)\n"
"\n"
"--Get the extent of various elevated circular strings\n"
"SELECT ST_3DExtent(foo.the_geom) As b3extent\n"
"FROM (SELECT ST_Translate(ST_Force_3DZ(ST_LineToCurve(ST_Buffer(ST_MakePoint"
"(x,y),1))),0,0,z) As the_geom\n"
" FROM generate_series(1,3) As x\n"
" CROSS JOIN generate_series(1,2) As y\n"
" CROSS JOIN generate_series(0,2) As Z) As foo;\n"
"\n"
" b3extent\n"
"--------------------\n"
" BOX3D(1 0 0,4 2 2)"
msgstr ""
#. Tag: para
#: reference_misc.xml:370
#, no-c-format
msgid ", <xref linkend=\"ST_Force_3DZ\"/>"
msgstr ""
#. Tag: refname
#: reference_misc.xml:377
#, no-c-format
msgid "Find_SRID"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:379
#, no-c-format
msgid ""
"The syntax is find_srid(&lt;db/schema&gt;, &lt;table&gt;, &lt;column&gt;) "
"and the function returns the integer SRID of the specified column by "
"searching through the GEOMETRY_COLUMNS table."
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:386
#, no-c-format
msgid ""
"<funcdef>integer <function>Find_SRID</function></funcdef> "
"<paramdef><type>varchar </type> <parameter>a_schema_name</parameter></"
"paramdef> <paramdef><type>varchar </type> <parameter>a_table_name</"
"parameter></paramdef> <paramdef><type>varchar </type> "
"<parameter>a_geomfield_name</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:398
#, no-c-format
msgid ""
"The syntax is find_srid(&lt;db/schema&gt;, &lt;table&gt;, &lt;column&gt;) "
"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."
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:410
#, no-c-format
msgid ""
"SELECT Find_SRID('public', 'tiger_us_state_2007', 'the_geom_4269');\n"
"find_srid\n"
"----------\n"
"4269"
msgstr ""
#. Tag: refname
#: reference_misc.xml:423
#, no-c-format
msgid "ST_Mem_Size"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:425
#, no-c-format
msgid ""
"<refpurpose>Returns the amount of space (in bytes) the geometry takes.</"
"refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:430
#, no-c-format
msgid ""
"<funcdef>integer <function>ST_Mem_Size</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:440
#, no-c-format
msgid "<para>Returns the amount of space (in bytes) the geometry takes.</para>"
msgstr ""
#. Tag: para
#: reference_misc.xml:441
#, no-c-format
msgid ""
"This is a nice compliment to PostgreSQL built in functions pg_size_pretty, "
"pg_relation_size, pg_total_relation_size."
msgstr ""
#. Tag: para
#: reference_misc.xml:442
#, no-c-format
msgid ""
"pg_relation_size which gives the byte size of a table may return byte size "
"lower than ST_Mem_Size. This is because pg_relation_size does not add "
"toasted table contribution and large geometries are stored in TOAST tables."
msgstr ""
#. Tag: para
#: reference_misc.xml:444
#, no-c-format
msgid ""
"pg_total_relation_size - includes, the table, the toasted tables, and the "
"indexes."
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:457
#, no-c-format
msgid ""
"--Return how much byte space Boston takes up in our Mass data set\n"
"SELECT pg_size_pretty(SUM(ST_Mem_Size(the_geom))) as totgeomsum,\n"
"pg_size_pretty(SUM(CASE WHEN town = 'BOSTON' THEN st_mem_size(the_geom) ELSE "
"0 END)) As bossum,\n"
"CAST(SUM(CASE WHEN town = 'BOSTON' THEN st_mem_size(the_geom) ELSE 0 END)"
"*1.00 /\n"
" SUM(st_mem_size(the_geom))*100 As numeric(10,2)) As perbos\n"
"FROM towns;\n"
"\n"
"totgeomsum bossum perbos\n"
"---------- ------ ------\n"
"1522 kB 30 kB 1.99\n"
"\n"
"\n"
"SELECT ST_Mem_Size(ST_GeomFromText('CIRCULARSTRING(220268 150415,220227 "
"150505,220227 150406)'));\n"
"\n"
"---\n"
"73\n"
"\n"
"--What percentage of our table is taken up by just the geometry\n"
"SELECT pg_total_relation_size('public.neighborhoods') As fulltable_size, sum"
"(ST_Mem_Size(the_geom)) As geomsize,\n"
"sum(ST_Mem_Size(the_geom))*1.00/pg_total_relation_size('public."
"neighborhoods')*100 As pergeom\n"
"FROM neighborhoods;\n"
"fulltable_size geomsize pergeom\n"
"------------------------------------------------\n"
"262144 96238 36.71188354492187500000"
msgstr ""
#. Tag: refname
#: reference_misc.xml:470
#, no-c-format
msgid "ST_Point_Inside_Circle"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:472
#, no-c-format
msgid ""
"Is the point geometry insert circle defined by center_x, center_y, radius"
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:477
#, no-c-format
msgid ""
"<funcdef>boolean <function>ST_Point_Inside_Circle</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>a_point</parameter></paramdef> "
"<paramdef><type>float </type> <parameter>center_x</parameter></paramdef> "
"<paramdef><type>float </type> <parameter>center_y</parameter></paramdef> "
"<paramdef><type>float </type> <parameter>radius</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:490
#, no-c-format
msgid ""
"The syntax for this functions is point_inside_circle(&lt;geometry&gt;,&lt;"
"circle_center_x&gt;,&lt;circle_center_y&gt;,&lt;radius&gt;). Returns the "
"true if the geometry is a point and is inside the circle. Returns false "
"otherwise."
msgstr ""
#. Tag: para
#: reference_misc.xml:494
#, no-c-format
msgid "This only works for points as the name suggests"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:501
#, no-c-format
msgid ""
"SELECT ST_Point_Inside_Circle(ST_Point(1,2), 0.5, 2, 3);\n"
" st_point_inside_circle\n"
"------------------------\n"
" t"
msgstr ""

1307
doc/po/it_IT/reference_operator.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

1846
doc/po/it_IT/reference_output.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

3813
doc/po/it_IT/reference_processing.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

12499
doc/po/it_IT/reference_raster.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

392
doc/po/it_IT/reference_transaction.xml.po Normal file
View file

@ -0,0 +1,392 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reference_transaction.xml:3
#, no-c-format
msgid "Long Transactions Support"
msgstr ""
#. Tag: para
#: reference_transaction.xml:5
#, no-c-format
msgid ""
"This module and associated pl/pgsql functions have been implemented to "
"provide long locking support required by <ulink url=\"http://www."
"opengeospatial.org/standards/wfs\">Web Feature Service</ulink> specification."
msgstr ""
#. Tag: para
#: reference_transaction.xml:10
#, no-c-format
msgid ""
"Users must use <ulink url=\"http://www.postgresql.org/docs/current/static/"
"transaction-iso.html\">serializable transaction level</ulink> otherwise "
"locking mechanism would break."
msgstr ""
#. Tag: refname
#: reference_transaction.xml:18
#, no-c-format
msgid "AddAuth"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:20
#, no-c-format
msgid ""
"<refpurpose>Add an authorization token to be used in current transaction.</"
"refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_transaction.xml:25
#, no-c-format
msgid ""
"<funcdef>boolean <function>AddAuth</function></funcdef> <paramdef><type>text "
"</type> <parameter>auth_token</parameter></paramdef>"
msgstr ""
#. Tag: title
#: reference_transaction.xml:33 reference_transaction.xml:83
#: reference_transaction.xml:130 reference_transaction.xml:177
#: reference_transaction.xml:241 reference_transaction.xml:284
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: reference_transaction.xml:35
#, no-c-format
msgid ""
"<para>Add an authorization token to be used in current transaction.</para>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:37
#, no-c-format
msgid ""
"Creates/adds to a temp table called temp_lock_have_table the current "
"transaction identifier and authorization token key."
msgstr ""
#. Tag: para
#: reference_transaction.xml:40 reference_transaction.xml:92
#: reference_transaction.xml:138 reference_transaction.xml:185
#: reference_transaction.xml:248 reference_transaction.xml:289
#, no-c-format
msgid "Availability: 1.1.3"
msgstr ""
#. Tag: title
#: reference_transaction.xml:45 reference_transaction.xml:98
#: reference_transaction.xml:144 reference_transaction.xml:191
#: reference_transaction.xml:253 reference_transaction.xml:294
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:47
#, no-c-format
msgid ""
"SELECT LockRow('towns', '353', 'priscilla');\n"
" BEGIN TRANSACTION;\n"
" SELECT AddAuth('joey');\n"
" UPDATE towns SET the_geom = ST_Translate"
"(the_geom,2,2) WHERE gid = 353;\n"
" COMMIT;\n"
"\n"
"\n"
" ---Error--\n"
" ERROR: UPDATE where \"gid\" = '353' requires authorization "
"'priscilla'"
msgstr ""
#. Tag: title
#: reference_transaction.xml:52 reference_transaction.xml:105
#: reference_transaction.xml:151 reference_transaction.xml:198
#: reference_transaction.xml:260 reference_transaction.xml:301
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: refname
#: reference_transaction.xml:60
#, no-c-format
msgid "CheckAuth"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:62
#, no-c-format
msgid ""
"Creates trigger on a table to prevent/allow updates and deletes of rows "
"based on authorization token."
msgstr ""
#. Tag: funcsynopsis
#: reference_transaction.xml:66
#, no-c-format
msgid ""
"<funcprototype> <funcdef>integer <function>CheckAuth</function></funcdef> "
"<paramdef><type>text </type> <parameter>a_schema_name</parameter></paramdef> "
"<paramdef><type>text </type> <parameter>a_table_name</parameter></paramdef> "
"<paramdef><type>text </type> <parameter>a_key_column_name</parameter></"
"paramdef> </funcprototype> <funcprototype> <funcdef>integer "
"<function>CheckAuth</function></funcdef> <paramdef><type>text </type> "
"<parameter>a_table_name</parameter></paramdef> <paramdef><type>text </type> "
"<parameter>a_key_column_name</parameter></paramdef> </funcprototype>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:85
#, no-c-format
msgid ""
"Creates trigger on a table to prevent/allow updates and deletes of rows "
"based on authorization token. Identify rows using &lt;rowid_col&gt; column."
msgstr ""
#. Tag: para
#: reference_transaction.xml:87
#, no-c-format
msgid ""
"If a_schema_name is not passed in, then searches for table in current schema."
msgstr ""
#. Tag: para
#: reference_transaction.xml:88
#, no-c-format
msgid ""
"If an authorization trigger already exists on this table function errors."
msgstr ""
#. Tag: para
#: reference_transaction.xml:89
#, no-c-format
msgid "If Transaction support is not enabled, function throws an exception."
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:100
#, no-c-format
msgid ""
"SELECT CheckAuth('public', 'towns', 'gid');\n"
" result\n"
" ------\n"
" 0"
msgstr ""
#. Tag: refname
#: reference_transaction.xml:113
#, no-c-format
msgid "DisableLongTransactions"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:115
#, no-c-format
msgid ""
"<refpurpose>Disable long transaction support. This function removes the long "
"transaction support metadata tables, and drops all triggers attached to lock-"
"checked tables.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_transaction.xml:122
#, no-c-format
msgid ""
"<funcdef>text <function>DisableLongTransactions</function></funcdef> "
"<paramdef></paramdef>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:132
#, no-c-format
msgid ""
"<para>Disable long transaction support. This function removes the long "
"transaction support metadata tables, and drops all triggers attached to lock-"
"checked tables.</para>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:135
#, no-c-format
msgid ""
"Drops meta table called <varname>authorization_table</varname> and a view "
"called <varname>authorized_tables</varname> and all triggers called "
"<varname>checkauthtrigger</varname>"
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:146
#, no-c-format
msgid ""
"SELECT DisableLongTransactions();\n"
"--result--\n"
"Long transactions support disabled"
msgstr ""
#. Tag: refname
#: reference_transaction.xml:159
#, no-c-format
msgid "EnableLongTransactions"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:161
#, no-c-format
msgid ""
"<refpurpose>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.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_transaction.xml:169
#, no-c-format
msgid ""
"<funcdef>text <function>EnableLongTransactions</function></funcdef> "
"<paramdef></paramdef>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:179
#, no-c-format
msgid ""
"<para>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.</para>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:183
#, no-c-format
msgid ""
"Creates a meta table called <varname>authorization_table</varname> and a "
"view called <varname>authorized_tables</varname>"
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:193
#, no-c-format
msgid ""
"SELECT EnableLongTransactions();\n"
"--result--\n"
"Long transactions support enabled"
msgstr ""
#. Tag: refname
#: reference_transaction.xml:206
#, no-c-format
msgid "LockRow"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:208
#, no-c-format
msgid "Set lock/authorization for specific row in table"
msgstr ""
#. Tag: funcsynopsis
#: reference_transaction.xml:212
#, no-c-format
msgid ""
"<funcprototype> <funcdef>integer <function>LockRow</function></funcdef> "
"<paramdef><type>text </type> <parameter>a_schema_name</parameter></paramdef> "
"<paramdef><type>text </type> <parameter>a_table_name</parameter></paramdef> "
"<paramdef><type>text </type> <parameter>a_row_key</parameter></paramdef> "
"<paramdef><type>text</type> <parameter>an_auth_token</parameter></paramdef> "
"<paramdef><type>timestamp</type> <parameter>expire_dt</parameter></paramdef> "
"</funcprototype> <funcprototype> <funcdef>integer <function>LockRow</"
"function></funcdef> <paramdef><type>text </type> <parameter>a_table_name</"
"parameter></paramdef> <paramdef><type>text </type> <parameter>a_row_key</"
"parameter></paramdef> <paramdef><type>text</type> <parameter>an_auth_token</"
"parameter></paramdef> <paramdef><type>timestamp</type> <parameter>expire_dt</"
"parameter></paramdef> </funcprototype> <funcprototype> <funcdef>integer "
"<function>LockRow</function></funcdef> <paramdef><type>text </type> "
"<parameter>a_table_name</parameter></paramdef> <paramdef><type>text </type> "
"<parameter>a_row_key</parameter></paramdef> <paramdef><type>text</type> "
"<parameter>an_auth_token</parameter></paramdef> </funcprototype>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:243
#, no-c-format
msgid ""
"Set lock/authorization for specific row in table &lt;authid&gt; is a text "
"value, &lt;expires&gt; is a timestamp defaulting to now()+1hour. Returns 1 "
"if lock has been assigned, 0 otherwise (already locked by other auth)"
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:255
#, no-c-format
msgid ""
"SELECT LockRow('public', 'towns', '2', 'joey');\n"
"LockRow\n"
"-------\n"
"1\n"
"\n"
"--Joey has already locked the record and Priscilla is out of luck\n"
"SELECT LockRow('public', 'towns', '2', 'priscilla');\n"
"LockRow\n"
"-------\n"
"0"
msgstr ""
#. Tag: refname
#: reference_transaction.xml:268
#, no-c-format
msgid "UnlockRows"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:270
#, no-c-format
msgid ""
"<refpurpose>Remove all locks held by specified authorization id. Returns the "
"number of locks released.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_transaction.xml:276
#, no-c-format
msgid ""
"<funcdef>integer <function>UnlockRows</function></funcdef> "
"<paramdef><type>text </type> <parameter>auth_token</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:286
#, no-c-format
msgid ""
"<para>Remove all locks held by specified authorization id. Returns the "
"number of locks released.</para>"
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:296
#, no-c-format
msgid ""
"SELECT LockRow('towns', '353', 'priscilla');\n"
" SELECT LockRow('towns', '2', 'priscilla');\n"
" SELECT UnLockRows('priscilla');\n"
" UnLockRows\n"
" ------------\n"
" 2"
msgstr ""

279
doc/po/it_IT/reference_type.xml.po Normal file
View file

@ -0,0 +1,279 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 21:04+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: para
#: reference_type.xml:5
#, no-c-format
msgid ""
"This section lists the PostgreSQL data types installed by PostGIS. Note we "
"describe the casting behavior of these which is very important especially "
"when designing your own functions."
msgstr ""
#. Tag: para
#: reference_type.xml:8
#, no-c-format
msgid ""
"A Cast is when one type is coerced into another type. PostgreSQL is unique "
"from most databases in that it allows you to define casting behavior for "
"custom types and the functions used for casting. A cast can be specified as "
"automatic in which case, you do not have to do a CAST(myfoo As otherfootype) "
"or myfoo::otherfootype if you are feeding it to a function that only works "
"with otherfootype and there is an automatic cast in place for it."
msgstr ""
#. Tag: para
#: reference_type.xml:13
#, no-c-format
msgid ""
"The danger of relying on automatic cast behavior is when you have an "
"overloaded function say one that takes a box2d and one that takes a box3d "
"but no geometry. What happens is that both functions are equally good to use "
"with geometry since geometry has an autocast for both -- so you end up with "
"an ambiguous function error. To force PostgreSQL to choose, you do a CAST"
"(mygeom As box3d) or mygeom::box3d."
msgstr ""
#. Tag: para
#: reference_type.xml:17
#, no-c-format
msgid ""
"<emphasis>At least as of PostgreSQL 8.3</emphasis> - Everything can be CAST "
"to text (presumably because of the magical unknown type), so no defined "
"CASTS for that need to be present for you to CAST an object to text."
msgstr ""
#. Tag: title
#: reference_type.xml:20
#, no-c-format
msgid "PostgreSQL PostGIS Geometry/Geography/Box Types"
msgstr ""
#. Tag: refname
#: reference_type.xml:24
#, no-c-format
msgid "<refname>box2d</refname>"
msgstr ""
#. Tag: refpurpose
#: reference_type.xml:25
#, no-c-format
msgid ""
"A box composed of x min, ymin, xmax, ymax. Often used to return the 2d "
"enclosing box of a geometry."
msgstr ""
"Un rettangolo composto da xmin, ymin, xmax, ymax. "
"Spesso usato per restituire il rettangolo che racchiude una geometria."
#. Tag: title
#: reference_type.xml:29 reference_type.xml:40 reference_type.xml:79
#: reference_type.xml:136 reference_type.xml:155
#, no-c-format
msgid "Description"
msgstr "Descrizione"
#. Tag: para
#: reference_type.xml:30
#, no-c-format
msgid ""
"box2d is a spatial data type used to represent the enclosing box of a "
"geometry or set of geometries. ST_Extent in earlier versions prior to "
"PostGIS 1.4 would return a box2d."
msgstr ""
#. Tag: refname
#: reference_type.xml:35
#, no-c-format
msgid "<refname>box3d</refname>"
msgstr ""
#. Tag: refpurpose
#: reference_type.xml:36
#, no-c-format
msgid ""
"A box composed of x min, ymin, zmin, xmax, ymax, zmax. Often used to return "
"the 3d extent of a geometry or collection of geometries."
msgstr ""
#. Tag: para
#: reference_type.xml:41
#, no-c-format
msgid ""
"box3d is a postgis spatial data type used to represent the enclosing box of "
"a geometry or set of geometries. ST_3DExtent returns a box3d object."
msgstr ""
#. Tag: title
#: reference_type.xml:45 reference_type.xml:84 reference_type.xml:160
#, no-c-format
msgid "Casting Behavior"
msgstr ""
#. Tag: para
#: reference_type.xml:46 reference_type.xml:85 reference_type.xml:161
#, no-c-format
msgid ""
"This section lists the automatic as well as explicit casts allowed for this "
"data type"
msgstr ""
#. Tag: entry
#: reference_type.xml:51 reference_type.xml:90 reference_type.xml:166
#, no-c-format
msgid "Cast To"
msgstr ""
#. Tag: entry
#: reference_type.xml:52 reference_type.xml:91 reference_type.xml:167
#, no-c-format
msgid "Behavior"
msgstr ""
#. Tag: entry
#: reference_type.xml:55 reference_type.xml:94
#, no-c-format
msgid "<entry>box</entry>"
msgstr ""
#. Tag: entry
#: reference_type.xml:56 reference_type.xml:60 reference_type.xml:64
#: reference_type.xml:95 reference_type.xml:99 reference_type.xml:103
#: reference_type.xml:107 reference_type.xml:111 reference_type.xml:115
#, no-c-format
msgid "automatic"
msgstr ""
#. Tag: entry
#: reference_type.xml:59 reference_type.xml:98
#, no-c-format
msgid "<entry>box2d</entry>"
msgstr ""
#. Tag: entry
#: reference_type.xml:63 reference_type.xml:170
#, no-c-format
msgid "<entry>geometry</entry>"
msgstr ""
#. Tag: refname
#: reference_type.xml:74
#, no-c-format
msgid "<refname>geometry</refname>"
msgstr ""
#. Tag: refpurpose
#: reference_type.xml:75
#, no-c-format
msgid "Planar spatial data type."
msgstr ""
#. Tag: para
#: reference_type.xml:80
#, no-c-format
msgid ""
"geometry is a fundamental postgis spatial data type used to represent a "
"feature in the Euclidean coordinate system."
msgstr ""
#. Tag: entry
#: reference_type.xml:102
#, no-c-format
msgid "<entry>box3d</entry>"
msgstr ""
#. Tag: entry
#: reference_type.xml:106
#, no-c-format
msgid "bytea"
msgstr ""
#. Tag: entry
#: reference_type.xml:110
#, no-c-format
msgid "<entry>geography</entry>"
msgstr ""
#. Tag: entry
#: reference_type.xml:114
#, no-c-format
msgid "text"
msgstr ""
#. Tag: title
#: reference_type.xml:123 reference_type.xml:143 reference_type.xml:179
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: refname
#: reference_type.xml:130
#, no-c-format
msgid "geometry_dump"
msgstr ""
#. Tag: refpurpose
#: reference_type.xml:131
#, no-c-format
msgid ""
"A spatial datatype with two fields - geom (holding a geometry object) and "
"path[] (a 1-d array holding the position of the geometry within the dumped "
"object.)"
msgstr ""
#. Tag: para
#: reference_type.xml:137
#, no-c-format
msgid ""
"geometry_dump is a compound data type consisting of a geometry object "
"referenced by the .geom field and path[] a 1-dimensional integer array "
"(starting at 1 e.g. path[1] to get first element) array that defines the "
"navigation path within the dumped geometry to find this element. It is used "
"by the ST_Dump* family of functions as an output type to explode a more "
"complex geometry into its constituent parts and location of parts."
msgstr ""
#. Tag: refname
#: reference_type.xml:150
#, no-c-format
msgid "<refname>geography</refname>"
msgstr ""
#. Tag: refpurpose
#: reference_type.xml:151
#, no-c-format
msgid "Ellipsoidal spatial data type."
msgstr ""
#. Tag: para
#: reference_type.xml:156
#, no-c-format
msgid ""
"geography is a spatial data type used to represent a feature in the round-"
"earth coordinate system."
msgstr ""
#. Tag: entry
#: reference_type.xml:171
#, no-c-format
msgid "explicit"
msgstr ""
#. Tag: para
#: reference_type.xml:180
#, no-c-format
msgid ", <xref linkend=\"PostGIS_Geography\"/>"
msgstr ""

4422
doc/po/it_IT/release_notes.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

170
doc/po/it_IT/reporting.xml.po Normal file
View file

@ -0,0 +1,170 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reporting.xml:3
#, no-c-format
msgid "Reporting Problems"
msgstr "Segnalare Problemi"
#. Tag: title
#: reporting.xml:6
#, no-c-format
msgid "Reporting Software Bugs"
msgstr "Segnalare Malfunzionamenti del Programma"
#. Tag: para
#: reporting.xml:8
#, no-c-format
msgid ""
"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 <code>SELECT postgis_full_version()</code> "
"[for postgis] and <code>SELECT version()</code> [for postgresql]."
msgstr ""
#. Tag: para
#: reporting.xml:16
#, no-c-format
msgid ""
"If you aren't using the latest release, it's worth taking a look at its "
"<ulink url=\"http://svn.osgeo.org/postgis/trunk/NEWS\">release changelog</"
"ulink> first, to find out if your bug has already been fixed."
msgstr ""
#. Tag: para
#: reporting.xml:21
#, no-c-format
msgid ""
"Using the <ulink url=\"http://trac.osgeo.org/postgis/\">PostGIS bug tracker</"
"ulink> will ensure your reports are not discarded, and will keep you "
"informed on its 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."
msgstr ""
#. Tag: para
#: reporting.xml:28
#, no-c-format
msgid ""
"You might want to read Simon Tatham's paper about <ulink url=\"http://www."
"chiark.greenend.org.uk/~sgtatham/bugs.html\">How to Report Bugs Effectively</"
"ulink> before filing a new report."
msgstr ""
#. Tag: title
#: reporting.xml:34
#, no-c-format
msgid "Reporting Documentation Issues"
msgstr ""
#. Tag: para
#: reporting.xml:36
#, no-c-format
msgid ""
"The documentation should accurately reflect the features and behavior of the "
"software. If it doesn't, it could be because of a software bug or because "
"the documentation is in error or deficient."
msgstr ""
#. Tag: para
#: reporting.xml:40
#, no-c-format
msgid ""
"Documentation issues can also be reported to the <ulink url=\"http://trac."
"osgeo.org/postgis\">PostGIS bug tracker</ulink>."
msgstr ""
#. Tag: para
#: reporting.xml:44
#, no-c-format
msgid ""
"If your revision is trivial, just describe it in a new bug tracker issue, "
"being specific about its location in the documentation."
msgstr ""
#. Tag: para
#: reporting.xml:47
#, no-c-format
msgid ""
"If your changes are more extensive, a Subversion patch is definitely "
"preferred. This is a four step process on Unix (assuming you already have "
"<ulink url=\"http://subversion.apache.org/\">Subversion</ulink> installed):"
msgstr ""
#. Tag: para
#: reporting.xml:54
#, no-c-format
msgid "Check out a copy of PostGIS' Subversion trunk. On Unix, type:"
msgstr ""
#. Tag: command
#: reporting.xml:57
#, no-c-format
msgid "svn checkout http://svn.osgeo.org/postgis/trunk/"
msgstr ""
#. Tag: para
#: reporting.xml:60
#, no-c-format
msgid "This will be stored in the directory ./trunk"
msgstr ""
#. Tag: para
#: reporting.xml:64
#, no-c-format
msgid ""
"Make your changes to the documentation with your favorite text editor. On "
"Unix, type (for example):"
msgstr ""
#. Tag: command
#: reporting.xml:67
#, no-c-format
msgid "vim trunk/doc/postgis.xml"
msgstr ""
#. Tag: para
#: reporting.xml:69
#, no-c-format
msgid ""
"Note that the documentation is written in DocBook XML rather than HTML, so "
"if you are not familiar with it please follow the example of the rest of the "
"documentation."
msgstr ""
#. Tag: para
#: reporting.xml:75
#, no-c-format
msgid ""
"Make a patch file containing the differences from the master copy of the "
"documentation. On Unix, type:"
msgstr ""
#. Tag: command
#: reporting.xml:78
#, no-c-format
msgid "svn diff trunk/doc/postgis.xml &gt; doc.patch"
msgstr ""
#. Tag: para
#: reporting.xml:83
#, no-c-format
msgid "Attach the patch to a new issue in bug tracker."
msgstr ""

797
doc/po/it_IT/using_postgis_app.xml.po Normal file
View file

@ -0,0 +1,797 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: using_postgis_app.xml:3
#, no-c-format
msgid "Using PostGIS Geometry: Building Applications"
msgstr ""
#. Tag: title
#: using_postgis_app.xml:5
#, no-c-format
msgid "Using MapServer"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:7
#, no-c-format
msgid ""
"The Minnesota MapServer is an internet web-mapping server which conforms to "
"the OpenGIS Web Mapping Server specification."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:12
#, no-c-format
msgid ""
"The MapServer homepage is at <ulink url=\"http://mapserver.org\">http://"
"mapserver.org</ulink>."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:17
#, no-c-format
msgid ""
"The OpenGIS Web Map Specification is at <ulink url=\"http://www."
"opengeospatial.org/standards/wms\">http://www.opengeospatial.org/standards/"
"wms</ulink>."
msgstr ""
#. Tag: title
#: using_postgis_app.xml:23
#, no-c-format
msgid "Basic Usage"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:25
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:30
#, no-c-format
msgid "To use PostGIS with MapServer, you will need:"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:34
#, no-c-format
msgid "Version 0.6 or newer of PostGIS."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:38
#, no-c-format
msgid "Version 3.5 or newer of MapServer."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:42
#, no-c-format
msgid ""
"MapServer accesses PostGIS/PostgreSQL data like any other PostgreSQL client "
"-- using the <filename>libpq</filename> interface. This means that MapServer "
"can be installed on any machine with network access to the PostGIS server, "
"and use PostGIS as a source of data. The faster the connection between the "
"systems, the better."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:50
#, no-c-format
msgid ""
"Compile and install MapServer, with whatever options you desire, including "
"the \"--with-postgis\" configuration option."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:55
#, no-c-format
msgid "In your MapServer map file, add a PostGIS layer. For example:"
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:58
#, no-c-format
msgid ""
"LAYER \n"
" CONNECTIONTYPE postgis \n"
" NAME \"widehighways\" \n"
" # Connect to a remote spatial database\n"
" CONNECTION \"user=dbuser dbname=gisdatabase host=bigserver\"\n"
" PROCESSING \"CLOSE_CONNECTION=DEFER\"\n"
" # Get the lines from the 'geom' column of the 'roads' table \n"
" DATA \"geom from roads using srid=4326 using unique gid\" \n"
" STATUS ON\n"
" TYPE LINE \n"
" # Of the lines in the extents, only render the wide highways \n"
" FILTER \"type = 'highway' and numlanes &gt;= 4\" \n"
" CLASS \n"
" # Make the superhighways brighter and 2 pixels wide\n"
" EXPRESSION ([numlanes] &gt;= 6) \n"
" STYLE\n"
" COLOR 255 22 22 \n"
" WIDTH 2 \n"
" END\n"
" END \n"
" CLASS \n"
" # All the rest are darker and only 1 pixel wide \n"
" EXPRESSION ([numlanes] &lt; 6) \n"
" STYLE\n"
" COLOR 205 92 82\n"
" END\n"
" END \n"
"END"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:60
#, no-c-format
msgid "In the example above, the PostGIS-specific directives are as follows:"
msgstr ""
#. Tag: term
#: using_postgis_app.xml:65
#, no-c-format
msgid "CONNECTIONTYPE"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:68
#, no-c-format
msgid "For PostGIS layers, this is always \"postgis\"."
msgstr ""
#. Tag: term
#: using_postgis_app.xml:73
#, no-c-format
msgid "CONNECTION"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:76
#, no-c-format
msgid ""
"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 &lt;"
"&gt;):"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:80
#, no-c-format
msgid ""
"user=&lt;username&gt; password=&lt;password&gt; dbname=&lt;username&gt; "
"hostname=&lt;server&gt; port=&lt;5432&gt;"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:84
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: term
#: using_postgis_app.xml:92
#, no-c-format
msgid "DATA"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:95
#, no-c-format
msgid ""
"The form of this parameter is \"&lt;geocolumn&gt; from &lt;tablename&gt; "
"using srid=&lt;srid&gt; using unique &lt;primary key&gt;\" where the column "
"is the spatial column to be rendered to the map, the SRID is SRID used by "
"the column and the primary key is the table primary key (or any other "
"uniquely-valued column with an index)."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:99
#, no-c-format
msgid ""
"You can omit the \"using srid\" and \"using unique\" clauses and MapServer "
"will automatically determine the correct values if possible, but at the cost "
"of running a few extra queries on the server for each map draw."
msgstr ""
#. Tag: term
#: using_postgis_app.xml:106
#, no-c-format
msgid "PROCESSING"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:109
#, no-c-format
msgid ""
"Putting in a CLOSE_CONNECTION=DEFER if you have multiple layers reuses "
"existing connections instead of closing them. This improves speed. Refer to "
"for <ulink url=\"http://blog.cleverelephant.ca/2008/10/mapserverpostgis-"
"performance-tips.html\">MapServer PostGIS Performance Tips</ulink> for a "
"more detailed explanation."
msgstr ""
#. Tag: term
#: using_postgis_app.xml:115
#, no-c-format
msgid "FILTER"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:118
#, no-c-format
msgid ""
"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 &gt;= 6\"."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:128
#, no-c-format
msgid ""
"In your spatial database, ensure you have spatial (GiST) indexes built for "
"any the layers you will be drawing."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:131
#, no-c-format
msgid ""
"CREATE INDEX [indexname] ON [tablename] USING GIST ( [geometrycolumn] );"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:135
#, no-c-format
msgid ""
"If you will be querying your layers using MapServer you will also need to "
"use the \"using unique\" clause in your DATA statement."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:138
#, no-c-format
msgid ""
"MapServer requires unique identifiers for each spatial record when doing "
"queries, and the PostGIS module of MapServer uses the unique value you "
"specify in order to provide these unique identifiers. Using the table "
"primary key is the best practice."
msgstr ""
#. Tag: title
#: using_postgis_app.xml:147
#, no-c-format
msgid "Frequently Asked Questions"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:152
#, no-c-format
msgid ""
"When I use an <varname>EXPRESSION</varname> in my map file, the condition "
"never returns as true, even though I know the values exist in my table."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:158
#, no-c-format
msgid ""
"Unlike shape files, PostGIS field names have to be referenced in EXPRESSIONS "
"using <emphasis>lower case</emphasis>."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:162
#, no-c-format
msgid "EXPRESSION ([numlanes] &gt;= 6)"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:168
#, no-c-format
msgid ""
"The FILTER I use for my Shape files is not working for my PostGIS table of "
"the same data."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:173
#, no-c-format
msgid ""
"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)."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:177
#, no-c-format
msgid "FILTER \"type = 'highway' and numlanes &gt;= 4\""
msgstr ""
#. Tag: para
#: using_postgis_app.xml:183
#, no-c-format
msgid ""
"My PostGIS layer draws much slower than my Shape file layer, is this normal?"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:188
#, no-c-format
msgid ""
"In general, the more features you are drawing into a given map, the more "
"likely it is that PostGIS will be slower than Shape files. For maps with "
"relatively few features (100s), PostGIS will often be faster. For maps with "
"high feature density (1000s), PostGIS will always be slower."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:194
#, no-c-format
msgid ""
"If you are finding substantial draw performance problems, it is possible "
"that you have not built a spatial index on your table."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:198
#, no-c-format
msgid ""
"postgis# CREATE INDEX geotable_gix ON geotable USING GIST ( geocolumn ); \n"
"postgis# VACUUM ANALYZE;"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:204
#, no-c-format
msgid ""
"My PostGIS layer draws fine, but queries are really slow. What is wrong?"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:209
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:213
#, no-c-format
msgid ""
"You can specify what unique key for mapserver to use with the <varname>USING "
"UNIQUE</varname> clause in your <varname>DATA</varname> line:"
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:217
#, no-c-format
msgid "DATA \"geom FROM geotable USING UNIQUE gid\""
msgstr ""
#. Tag: para
#: using_postgis_app.xml:224
#, no-c-format
msgid ""
"Can I use \"geography\" columns (new in PostGIS 1.5) as a source for "
"MapServer layers?"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:229
#, no-c-format
msgid ""
"Yes! MapServer understands geography columns as being the same as geometry "
"columns, but always using an SRID of 4326. Just make sure to include a "
"\"using srid=4326\" clause in your <varname>DATA</varname> statement. "
"Everything else works exactly the same as with geometry."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:234
#, no-c-format
msgid "DATA \"geog FROM geogtable USING SRID=4326 USING UNIQUE gid\""
msgstr ""
#. Tag: title
#: using_postgis_app.xml:244
#, no-c-format
msgid "Advanced Usage"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:246
#, no-c-format
msgid ""
"The <varname>USING</varname> 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 <varname>DATA</"
"varname> definition) it is more difficult for mapserver to automatically "
"determine a unique identifier for each row and also the SRID for the table. "
"The <varname>USING</varname> clause can provide mapserver with these two "
"pieces of information as follows:"
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:255
#, no-c-format
msgid ""
"DATA \"geom FROM (\n"
" SELECT \n"
" table1.geom AS geom, \n"
" table1.gid AS gid, \n"
" table2.data AS data \n"
" FROM table1 \n"
" LEFT JOIN table2 \n"
" ON table1.id = table2.id\n"
") AS new_table USING UNIQUE gid USING SRID=4326\""
msgstr ""
#. Tag: term
#: using_postgis_app.xml:259
#, no-c-format
msgid "USING UNIQUE &lt;uniqueid&gt;"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:262
#, no-c-format
msgid ""
"MapServer requires a unique id for each row in order to identify the row "
"when doing map queries. Normally it identifies the primary key from the "
"system tables. However, views and subselects don't automatically have an "
"known unique column. If you want to use MapServer's query functionality, you "
"need to ensure your view or subselect includes a uniquely valued column, and "
"declare it with <varname>USING UNIQUE</varname>. For example, you could "
"explicitly select nee of the table's primary key values for this purpose, or "
"any other column which is guaranteed to be unique for the result set."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:273
#, no-c-format
msgid ""
"\"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 <varname>DATA</varname> definition."
msgstr ""
#. Tag: term
#: using_postgis_app.xml:282
#, no-c-format
msgid "USING SRID=&lt;srid&gt;"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:285
#, no-c-format
msgid ""
"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 <varname>USING "
"SRID=</varname> option allows the correct SRID to be specified in the "
"<varname>DATA</varname> definition."
msgstr ""
#. Tag: title
#: using_postgis_app.xml:300
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:302
#, no-c-format
msgid ""
"Lets start with a simple example and work our way up. Consider the following "
"MapServer layer definition:"
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:305
#, no-c-format
msgid ""
"LAYER \n"
" CONNECTIONTYPE postgis \n"
" NAME \"roads\"\n"
" CONNECTION \"user=theuser password=thepass dbname=thedb host=theserver\" \n"
" DATA \"geom from roads\" \n"
" STATUS ON \n"
" TYPE LINE \n"
" CLASS \n"
" STYLE\n"
" COLOR 0 0 0 \n"
" END\n"
" END \n"
"END"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:307
#, no-c-format
msgid ""
"This layer will display all the road geometries in the roads table as black "
"lines."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:310
#, no-c-format
msgid ""
"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:"
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:314
#, no-c-format
msgid ""
"LAYER \n"
" CONNECTIONTYPE postgis \n"
" CONNECTION \"user=theuser password=thepass dbname=thedb host=theserver\" \n"
" PROCESSING \"CLOSE_CONNECTION=DEFER\"\n"
" DATA \"geom from roads\"\n"
" MINSCALE 100000 \n"
" STATUS ON \n"
" TYPE LINE \n"
" FILTER \"road_type = 'highway'\" \n"
" CLASS \n"
" COLOR 0 0 0 \n"
" END \n"
"END \n"
"LAYER \n"
" CONNECTIONTYPE postgis \n"
" CONNECTION \"user=theuser password=thepass dbname=thedb host=theserver\"\n"
" PROCESSING \"CLOSE_CONNECTION=DEFER\"\n"
" DATA \"geom from roads\" \n"
" MAXSCALE 100000 \n"
" STATUS ON \n"
" TYPE LINE\n"
" CLASSITEM road_type \n"
" CLASS \n"
" EXPRESSION \"highway\" \n"
" STYLE\n"
" WIDTH 2 \n"
" COLOR 255 0 0 \n"
" END\n"
" END \n"
" CLASS \n"
" STYLE\n"
" COLOR 0 0 0 \n"
" END\n"
" END \n"
"END"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:316
#, no-c-format
msgid ""
"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 "
"<varname>FILTER</varname> option causes only roads of type \"highway\" to be "
"displayed."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:321
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:325
#, no-c-format
msgid ""
"So, we have done a couple of interesting things using only MapServer "
"functionality, but our <varname>DATA</varname> 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."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:331
#, no-c-format
msgid ""
"LAYER \n"
" CONNECTIONTYPE postgis\n"
" CONNECTION \"user=theuser password=thepass dbname=thedb host=theserver\" \n"
" DATA \"geom FROM (SELECT roads.gid AS gid, roads.geom AS geom, \n"
" road_names.name as name FROM roads LEFT JOIN road_names ON \n"
" roads.road_name_id = road_names.road_name_id) \n"
" AS named_roads USING UNIQUE gid USING SRID=4326\" \n"
" MAXSCALE 20000 \n"
" STATUS ON \n"
" TYPE ANNOTATION \n"
" LABELITEM name\n"
" CLASS \n"
" LABEL \n"
" ANGLE auto \n"
" SIZE 8 \n"
" COLOR 0 192 0 \n"
" TYPE truetype \n"
" FONT arial\n"
" END\n"
" END \n"
"END"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:333
#, no-c-format
msgid ""
"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 "
"<varname>DATA</varname> definition."
msgstr ""
#. Tag: title
#: using_postgis_app.xml:340
#, no-c-format
msgid "Java Clients (JDBC)"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:342
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:348
#, no-c-format
msgid ""
"import java.sql.*; \n"
"import java.util.*; \n"
"import java.lang.*; \n"
"import org.postgis.*; \n"
"\n"
"public class JavaGIS { \n"
"\n"
"public static void main(String[] args) { \n"
"\n"
" java.sql.Connection conn; \n"
"\n"
" try { \n"
" /* \n"
" * Load the JDBC driver and establish a connection. \n"
" */\n"
" Class.forName(\"org.postgresql.Driver\"); \n"
" String url = \"jdbc:postgresql://localhost:5432/database\"; \n"
" conn = DriverManager.getConnection(url, \"postgres\", \"\"); \n"
" /* \n"
" * Add the geometry types to the connection. Note that you \n"
" * must cast the connection to the pgsql-specific connection \n"
" * implementation before calling the addDataType() method. \n"
" */\n"
" ((org.postgresql.PGConnection)conn).addDataType(\"geometry\",Class."
"forName(\"org.postgis.PGgeometry\"));\n"
" ((org.postgresql.PGConnection)conn).addDataType(\"box3d\",Class.forName"
"(\"org.postgis.PGbox3d\"));\n"
" /* \n"
" * Create a statement and execute a select query. \n"
" */ \n"
" Statement s = conn.createStatement(); \n"
" ResultSet r = s.executeQuery(\"select geom,id from geomtable\"); \n"
" while( r.next() ) { \n"
" /* \n"
" * Retrieve the geometry as an object then cast it to the geometry "
"type. \n"
" * Print things out. \n"
" */ \n"
" PGgeometry geom = (PGgeometry)r.getObject(1); \n"
" int id = r.getInt(2); \n"
" System.out.println(\"Row \" + id + \":\");\n"
" System.out.println(geom.toString()); \n"
" } \n"
" s.close(); \n"
" conn.close(); \n"
" } \n"
"catch( Exception e ) { \n"
" e.printStackTrace(); \n"
" } \n"
"} \n"
"}"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:350
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:355
#, no-c-format
msgid ""
"PGgeometry geom = (PGgeometry)r.getObject(1); \n"
"if( geom.getType() == Geometry.POLYGON ) { \n"
" Polygon pl = (Polygon)geom.getGeometry(); \n"
" for( int r = 0; r &lt; pl.numRings(); r++) { \n"
" LinearRing rng = pl.getRing(r); \n"
" System.out.println(\"Ring: \" + r); \n"
" for( int p = 0; p &lt; rng.numPoints(); p++ ) { \n"
" Point pt = rng.getPoint(p); \n"
" System.out.println(\"Point: \" + p);\n"
" System.out.println(pt.toString()); \n"
" } \n"
" } \n"
"}"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:357
#, no-c-format
msgid ""
"The JavaDoc for the extension objects provides a reference for the various "
"data accessor functions in the geometric objects."
msgstr ""
#. Tag: title
#: using_postgis_app.xml:362
#, no-c-format
msgid "C Clients (libpq)"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:364 using_postgis_app.xml:369
#: using_postgis_app.xml:375
#, no-c-format
msgid "<para>...</para>"
msgstr ""
#. Tag: title
#: using_postgis_app.xml:367
#, no-c-format
msgid "Text Cursors"
msgstr ""
#. Tag: title
#: using_postgis_app.xml:373
#, no-c-format
msgid "Binary Cursors"
msgstr ""

3887
doc/po/it_IT/using_postgis_dataman.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

1568
doc/po/it_IT/using_raster_dataman.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

2
doc/po/pt_BR/Makefile Normal file
View file

@ -0,0 +1,2 @@
DOCSUFFIX=-br
include ../Makefile.local

16
doc/po/pt_BR/extras.xml.po Normal file
View file

@ -0,0 +1,16 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

260
doc/po/pt_BR/extras_historytable.xml.po Normal file
View file

@ -0,0 +1,260 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: extras_historytable.xml:3
#, no-c-format
msgid "History Tracking"
msgstr ""
#. Tag: para
#: extras_historytable.xml:6
#, no-c-format
msgid ""
"Suppose you have a table of data that represents the current state of a "
"particular geographic feature. A parcels table, or a roads table, or a fruit "
"trees table, whatever. Generally, GIS tools understand a table as a single "
"entity into which they can update, insert and delete rows from. How you do "
"allow common GIS tools to work against your data, while maintaining an audit "
"trail of what changes have been made, by whom, and what the past state of "
"the data is?"
msgstr ""
#. Tag: para
#: extras_historytable.xml:10
#, no-c-format
msgid ""
"This <varname>history_table</varname> extra module provides some utility "
"functions for creating and maintaining history."
msgstr ""
#. Tag: para
#: extras_historytable.xml:14
#, no-c-format
msgid ""
"The <varname>history_table</varname> was also packaged in PostGIS 1.5, but "
"added to the documentation in PostGIS 2.0. This package is written in "
"plpgsql and located in the <varname>extras/history_table</varname> of "
"PostGIS source tar balls and source repository."
msgstr ""
#. Tag: para
#: extras_historytable.xml:15
#, no-c-format
msgid ""
"If you have a table 'roads', this module will maintain a 'roads_history' "
"side table, which contains all the columns of the parent table, and the "
"following additional columns:"
msgstr ""
#. Tag: programlisting
#: extras_historytable.xml:16
#, no-c-format
msgid ""
"history_id | integer | not null default \n"
" date_added | timestamp without time zone | not null default now()\n"
" date_deleted | timestamp without time zone | \n"
" last_operation | character varying(30) | not null\n"
" active_user | character varying(90) | not null default "
"\"current_user\"()\n"
" current_version | text | not null"
msgstr ""
#. Tag: para
#: extras_historytable.xml:20
#, no-c-format
msgid ""
"When you insert a new record into 'roads' a record is automatically inserted "
"into 'roads_history', with the 'date_added' filled in the 'date_deleted' set "
"to NULL, a unique 'history_id', a 'last_operation' of 'INSERT' and "
"'active_user' set."
msgstr ""
#. Tag: para
#: extras_historytable.xml:23
#, no-c-format
msgid ""
"When you delete a record in 'roads', the record in the history table is "
"*not* deleted, but the 'date_deleted' is set to the current date."
msgstr ""
#. Tag: para
#: extras_historytable.xml:26
#, no-c-format
msgid ""
"When you update a record in 'roads', the current record has 'date_deleted' "
"filled in and a new record is created with the 'date_added' set and "
"'date_deleted' NULL."
msgstr ""
#. Tag: para
#: extras_historytable.xml:30
#, no-c-format
msgid ""
"With this information maintained, it is possible to retrieve the history of "
"any record in the roads table:"
msgstr ""
#. Tag: programlisting
#: extras_historytable.xml:31
#, no-c-format
msgid "SELECT * FROM roads_history WHERE roads_pk = 111;"
msgstr ""
#. Tag: para
#: extras_historytable.xml:33
#, no-c-format
msgid "Or, to retrieve a view of the roads table at any point in the past:"
msgstr ""
#. Tag: programlisting
#: extras_historytable.xml:34
#, no-c-format
msgid ""
"SELECT * FROM roads_history \n"
" WHERE date_added &lt; 'January 1, 2001' AND \n"
" ( date_deleted &gt;= 'January 1, 2001' OR date_deleted IS NULL );"
msgstr ""
#. Tag: refname
#: extras_historytable.xml:38
#, no-c-format
msgid "Postgis_Install_History"
msgstr ""
#. Tag: refpurpose
#: extras_historytable.xml:39
#, no-c-format
msgid ""
"Creates a table that will hold some interesting values for managing history "
"tables."
msgstr ""
#. Tag: funcprototype
#: extras_historytable.xml:44
#, no-c-format
msgid ""
"<funcdef>void <function>Postgis_Install_History</function></funcdef> "
"<paramdef></paramdef>"
msgstr ""
#. Tag: title
#: extras_historytable.xml:52 extras_historytable.xml:92
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: extras_historytable.xml:54
#, no-c-format
msgid ""
"Creates a table that will hold some interesting values for managing history "
"tables. Creates a table called <varname>historic_information</varname>"
msgstr ""
#. Tag: para
#: extras_historytable.xml:58 extras_historytable.xml:100
#, no-c-format
msgid "Availability: 1.5.0"
msgstr ""
#. Tag: title
#: extras_historytable.xml:63 extras_historytable.xml:105
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: programlisting
#: extras_historytable.xml:65
#, no-c-format
msgid "SELECT postgis_install_history();"
msgstr ""
#. Tag: title
#: extras_historytable.xml:71 extras_historytable.xml:113
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: refname
#: extras_historytable.xml:77
#, no-c-format
msgid "Postgis_Enable_History"
msgstr ""
#. Tag: refpurpose
#: extras_historytable.xml:78
#, no-c-format
msgid ""
"Registers a tablein the history_information table for tracking and also adds "
"in side line history table and insert, update, delete rules on the table."
msgstr ""
#. Tag: funcprototype
#: extras_historytable.xml:83
#, no-c-format
msgid ""
"<funcdef>boolean <function>Postgis_Enable_History</function></funcdef> "
"<paramdef><type>text </type> <parameter>p_schema</parameter></paramdef> "
"<paramdef><type>text </type> <parameter>p_table</parameter></paramdef>"
msgstr ""
#. Tag: para
#: extras_historytable.xml:94
#, no-c-format
msgid ""
"Registers a table in the history_information table for tracking and also "
"adds in side line history table with same name as table but prefixed with "
"<varname>history</varname> in the same schema as the original table. Puts in "
"insert, update, delete rules on the table. Any inserts,updates,deletes of "
"the geometry are recorded in the history table."
msgstr ""
#. Tag: para
#: extras_historytable.xml:97
#, no-c-format
msgid ""
"This function currently relies on a geometry column being registered in "
"<varname>geometry_columns</varname> and fails if the geometry column is not "
"present in <varname>geometry_columns</varname> table."
msgstr ""
#. Tag: programlisting
#: extras_historytable.xml:107
#, no-c-format
msgid ""
"CREATE TABLE roads(gid SERIAL PRIMARY KEY, road_name varchar(150));\n"
"SELECT AddGeometryColumn('roads', 'geom', 26986, 'LINESTRING', 2);\n"
" \n"
"SELECT postgis_enable_history('public', 'roads', 'geom') As register_table;\n"
"register_table\n"
"--------------\n"
"t\n"
"\n"
"INSERT INTO roads(road_name, geom) \n"
" VALUES('Test Street', ST_GeomFromText('LINESTRING(231660.5 832170,231647 "
"832202,231627.5 832250.5)',26986));\n"
"\n"
"-- check transaction detail --\n"
"SELECT date_added, last_operation, current_version \n"
"FROM roads_history \n"
"WHERE road_name = 'Test Street' ORDER BY date_added DESC;\n"
"\n"
" date_added | last_operation | current_version\n"
"------------------------+----------------+-----------------\n"
" 2011-02-07 12:44:36.92 | INSERT | 2"
msgstr ""

2161
doc/po/pt_BR/extras_tigergeocoder.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

3792
doc/po/pt_BR/extras_topology.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

667
doc/po/pt_BR/faq.xml.po Normal file
View file

@ -0,0 +1,667 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: faq.xml:3
#, no-c-format
msgid "PostGIS Frequently Asked Questions"
msgstr ""
#. Tag: para
#: faq.xml:8
#, no-c-format
msgid ""
"My applications and desktop tools worked with PostGIS 1.5,but they don't "
"work with PostGIS 2.0. How do I fix this?"
msgstr ""
#. Tag: para
#: faq.xml:12
#, no-c-format
msgid ""
"A lot of deprecated functions were removed from the PostGIS code base in "
"PostGIS 2.0. This has affected applications in addition to third-party tools "
"such as Geoserver, MapServer, QuantumGIS, and OpenJump to name a few. There "
"are a couple of ways to resolve this. For the third-party apps, you can try "
"to upgrade to the latest versions of these which have many of these issues "
"fixed. For your own code, you can change your code to not use the functions "
"removed. Most of these functions are non ST_ aliases of ST_Union, ST_Length "
"etc. and as a last resort, install the whole of <varname>legacy.sql</"
"varname> or just the portions of <varname>legacy.sql</varname> you need."
msgstr ""
#. Tag: para
#: faq.xml:18
#, no-c-format
msgid ""
"The <varname>legacy.sql</varname> file is located in the same folder as "
"postgis.sql. You can install this file after you have installed postgis.sql "
"and spatial_ref_sys.sql to get back all the 200 some-odd old functions we "
"removed."
msgstr ""
#. Tag: para
#: faq.xml:24
#, no-c-format
msgid ""
"I'm running PostgreSQL 9.0 and I can no longer read/view geometries in "
"OpenJump, Safe FME, and some other tools?"
msgstr ""
#. Tag: para
#: faq.xml:28
#, no-c-format
msgid ""
"In PostgreSQL 9.0+, the default encoding for bytea data has been changed to "
"hex and older JDBC drivers still assume escape format. This has affected "
"some applications such as Java applications using older JDBC drivers or .NET "
"applications that use the older npgsql driver that expect the old behavior "
"of ST_AsBinary. There are two approaches to getting this to work again."
msgstr ""
#. Tag: para
#: faq.xml:32
#, no-c-format
msgid ""
"You can upgrade your JDBC driver to the latest PostgreSQL 9.0 version which "
"you can get from <ulink url=\"http://jdbc.postgresql.org/download.html"
"\">http://jdbc.postgresql.org/download.html</ulink>"
msgstr ""
#. Tag: para
#: faq.xml:34
#, no-c-format
msgid ""
"If you are running a .NET app, you can use Npgsql 2.0.11 or higher which you "
"can download from <ulink url=\"http://pgfoundry.org/frs/?"
"group_id=1000140\">http://pgfoundry.org/frs/?group_id=1000140</ulink> and as "
"described on <ulink url=\"http://fxjr.blogspot.com/2010/11/npgsql-2011-"
"released.html\">Francisco Figueiredo's NpgSQL 2.0.11 released blog entry</"
"ulink>"
msgstr ""
#. Tag: para
#: faq.xml:38
#, no-c-format
msgid ""
"If upgrading your PostgreSQL driver is not an option, then you can set the "
"default back to the old behavior with the following change:"
msgstr ""
#. Tag: programlisting
#: faq.xml:39
#, no-c-format
msgid "ALTER DATABASE mypostgisdb SET bytea_output='escape';"
msgstr ""
#. Tag: para
#: faq.xml:46
#, no-c-format
msgid ""
"I tried to use PgAdmin to view my geometry column and it is blank, what "
"gives?"
msgstr ""
#. Tag: para
#: faq.xml:50
#, no-c-format
msgid ""
"PgAdmin doesn't show anything for large geometries. The best ways to verify "
"you do have data in your geometry columns are?"
msgstr ""
#. Tag: programlisting
#: faq.xml:53
#, no-c-format
msgid ""
"-- this should return no records if all your geom fields are filled "
"in \n"
"SELECT somefield FROM mytable WHERE geom IS NULL;"
msgstr ""
#. Tag: programlisting
#: faq.xml:55
#, no-c-format
msgid ""
"-- To tell just how large your geometry is do a query of the form\n"
"--which will tell you the most number of points you have in any of your "
"geometry columns\n"
"SELECT MAX(ST_NPoints(geom)) FROM sometable;"
msgstr ""
#. Tag: para
#: faq.xml:61
#, no-c-format
msgid "What kind of geometric objects can I store?"
msgstr ""
#. Tag: para
#: faq.xml:65
#, no-c-format
msgid ""
"You can store point, line, polygon, multipoint, multiline, multipolygon, and "
"geometrycollections. In PostGIS 2.0 and above you can also store TINS and "
"Polyhedral Surfaces in the basic geometry type. These are specified in the "
"Open GIS Well Known Text Format (with XYZ,XYM,XYZM extensions). There are "
"three data types currently supported. The standard OGC geometry data type "
"which uses a planar coordinate system for measurement, the geography data "
"type which uses a geodetic coordinate system (not OGC, but you'll find a "
"similar type in Microsoft SQL Server 2008+). Only WGS 84 long lat "
"(SRID:4326) is supported by the geography data type. The newest family "
"member of the PostGIS spatial type family is raster for storing and "
"analyzing raster data. Raster has its very own FAQ. Refer to <xref linkend="
"\"RT_FAQ\"/> and <xref linkend=\"RT_reference\"/> for more details."
msgstr ""
#. Tag: para
#: faq.xml:78
#, no-c-format
msgid "I'm all confused. Which data store should I use geometry or geography?"
msgstr ""
#. Tag: para
#: faq.xml:82
#, no-c-format
msgid ""
"Short Answer: geography is a new data type that supports long range "
"distances measurements, but most computations on it are currently slower "
"than they are on geometry. If you use geography -- you don't need to learn "
"much about planar coordinate systems. Geography is generally best if all you "
"care about is measuring distances and lengths and you have data from all "
"over the world. Geometry data type is an older data type that has many more "
"functions supporting it, enjoys greater support from third party tools, and "
"operations on it are generally faster -- sometimes as much as 10 fold faster "
"for larger geometries. Geometry is best if you are pretty comfortable with "
"spatial reference systems or you are dealing with localized data where all "
"your data fits in a single <link linkend=\"spatial_ref_sys\">spatial "
"reference system (SRID)</link>, or you need to do a lot of spatial "
"processing. Note: It is fairly easy to do one-off conversions between the "
"two types to gain the benefits of each. Refer to <xref linkend="
"\"PostGIS_TypeFunctionMatrix\"/> to see what is currently supported and what "
"is not."
msgstr ""
#. Tag: para
#: faq.xml:93
#, no-c-format
msgid ""
"Long Answer: Refer to our more lengthy discussion in the <xref linkend="
"\"PostGIS_GeographyVSGeometry\"/> and <link linkend="
"\"PostGIS_TypeFunctionMatrix\">function type matrix</link>."
msgstr ""
#. Tag: para
#: faq.xml:101
#, no-c-format
msgid ""
"I have more intense questions about geography, such as how big of a "
"geographic region can I stuff in a geography column and still get reasonable "
"answers. Are there limitations such as poles, everything in the field must "
"fit in a hemisphere (like SQL Server 2008 has), speed etc?"
msgstr ""
#. Tag: para
#: faq.xml:105
#, no-c-format
msgid ""
"Your questions are too deep and complex to be adequately answered in this "
"section. Please refer to our <xref linkend=\"PostGIS_Geography_AdvancedFAQ\"/"
">."
msgstr ""
#. Tag: para
#: faq.xml:112
#, no-c-format
msgid "How do I insert a GIS object into the database?"
msgstr ""
#. Tag: para
#: faq.xml:116
#, no-c-format
msgid ""
"First, you need to create a table with a column of type \"geometry\" or "
"\"geography\" to hold your GIS data. Storing geography type data is a little "
"different than storing geometry. Refer to <xref linkend=\"Geography_Basics\"/"
"> for details on storing geography."
msgstr ""
#. Tag: para
#: faq.xml:120
#, no-c-format
msgid ""
"For geometry: Connect to your database with <filename>psql</filename> and "
"try the following SQL:"
msgstr ""
#. Tag: programlisting
#: faq.xml:124
#, no-c-format
msgid ""
"CREATE TABLE gtest ( ID int4, NAME varchar(20) );\n"
"SELECT AddGeometryColumn('', 'gtest','geom',-1,'LINESTRING',2);"
msgstr ""
#. Tag: para
#: faq.xml:126
#, no-c-format
msgid ""
"If the geometry column addition fails, you probably have not loaded the "
"PostGIS functions and objects into this database. See the <xref linkend="
"\"PGInstall\"/>."
msgstr ""
#. Tag: para
#: faq.xml:130
#, no-c-format
msgid ""
"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:"
msgstr ""
#. Tag: programlisting
#: faq.xml:134
#, no-c-format
msgid ""
"INSERT INTO gtest (ID, NAME, GEOM) \n"
"VALUES (\n"
" 1, \n"
" 'First Geometry', \n"
" ST_GeomFromText('LINESTRING(2 3,4 5,6 5,7 8)', -1)\n"
");"
msgstr ""
#. Tag: para
#: faq.xml:136
#, no-c-format
msgid ""
"For more information about other GIS objects, see the <link linkend="
"\"RefObject\">object reference</link>."
msgstr ""
#. Tag: para
#: faq.xml:139
#, no-c-format
msgid "To view your GIS data in the table:"
msgstr ""
#. Tag: programlisting
#: faq.xml:141
#, no-c-format
msgid "SELECT id, name, ST_AsText(geom) AS geom FROM gtest;"
msgstr ""
#. Tag: para
#: faq.xml:143
#, no-c-format
msgid "The return value should look something like this:"
msgstr ""
#. Tag: programlisting
#: faq.xml:145
#, no-c-format
msgid ""
"id | name | geom\n"
"----+----------------+-----------------------------\n"
" 1 | First Geometry | LINESTRING(2 3,4 5,6 5,7 8) \n"
"(1 row)"
msgstr ""
#. Tag: para
#: faq.xml:151
#, no-c-format
msgid "How do I construct a spatial query?"
msgstr ""
#. Tag: para
#: faq.xml:155
#, no-c-format
msgid ""
"The same way you construct any other database query, as an SQL combination "
"of return values, functions, and boolean tests."
msgstr ""
#. Tag: para
#: faq.xml:158
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: faq.xml:163
#, no-c-format
msgid ""
"In general, you will want to use the \"intersects operator\" (&amp;&amp;) "
"which tests whether the bounding boxes of features intersect. The reason the "
"&amp;&amp; operator is useful is because if a spatial index is available to "
"speed up the test, the &amp;&amp; operator will make use of this. This can "
"make queries much much faster."
msgstr ""
#. Tag: para
#: faq.xml:170
#, no-c-format
msgid ""
"You will also make use of spatial functions, such as Distance(), "
"ST_Intersects(), ST_Contains() and ST_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 <emphasis>might</emphasis> meet the "
"condition of interest. The spatial functions are then use to test the "
"condition exactly."
msgstr ""
#. Tag: programlisting
#: faq.xml:178
#, no-c-format
msgid ""
"SELECT id, the_geom \n"
"FROM thetable \n"
"WHERE \n"
" ST_Contains(the_geom,'POLYGON((0 0, 0 10, 10 10, 10 0, 0 0))');"
msgstr ""
#. Tag: para
#: faq.xml:184
#, no-c-format
msgid "How do I speed up spatial queries on large tables?"
msgstr ""
#. Tag: para
#: faq.xml:188
#, no-c-format
msgid ""
"Fast queries on large tables is the <emphasis>raison d'etre</emphasis> of "
"spatial databases (along with transaction support) so having a good index is "
"important."
msgstr ""
#. Tag: para
#: faq.xml:192
#, no-c-format
msgid ""
"To build a spatial index on a table with a <varname>geometry</varname> "
"column, use the \"CREATE INDEX\" function as follows:"
msgstr ""
#. Tag: programlisting
#: faq.xml:196
#, no-c-format
msgid ""
"CREATE INDEX [indexname] ON [tablename] USING GIST ( [geometrycolumn] );"
msgstr ""
#. Tag: para
#: faq.xml:198
#, no-c-format
msgid ""
"The \"USING GIST\" option tells the server to use a GiST (Generalized Search "
"Tree) index."
msgstr ""
#. Tag: para
#: faq.xml:202
#, no-c-format
msgid ""
"GiST indexes are assumed to be lossy. Lossy indexes uses a proxy object (in "
"the spatial case, a bounding box) for building the index."
msgstr ""
#. Tag: para
#: faq.xml:207
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: faq.xml:212
#, no-c-format
msgid ""
"For PostgreSQL 8.0.x and greater, just run the <command>VACUUM ANALYZE</"
"command> command."
msgstr ""
#. Tag: para
#: faq.xml:215
#, no-c-format
msgid ""
"For PostgreSQL 7.4.x and below, run the <command>SELECT UPDATE_GEOMETRY_STATS"
"()</command> command."
msgstr ""
#. Tag: para
#: faq.xml:222
#, no-c-format
msgid "Why aren't PostgreSQL R-Tree indexes supported?"
msgstr ""
#. Tag: para
#: faq.xml:226
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: faq.xml:231
#, no-c-format
msgid ""
"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):"
msgstr ""
#. Tag: para
#: faq.xml:239
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: faq.xml:246
#, no-c-format
msgid ""
"R-Tree indexes in PostgreSQL are not \"null safe\", so building an index on "
"a geometry column which contains null geometries will fail."
msgstr ""
#. Tag: para
#: faq.xml:256
#, no-c-format
msgid ""
"Why should I use the <varname>AddGeometryColumn()</varname> function and all "
"the other OpenGIS stuff?"
msgstr ""
#. Tag: para
#: faq.xml:261
#, no-c-format
msgid ""
"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 <emphasis>not</emphasis> be filled in "
"properly. However, this will cause most applications based on PostGIS to "
"fail, and it is generally suggested that you do use "
"<varname>AddGeometryColumn()</varname> to create geometry tables."
msgstr ""
#. Tag: para
#: faq.xml:270
#, no-c-format
msgid ""
"MapServer is one application which makes use of the "
"<varname>geometry_columns</varname> 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."
msgstr ""
#. Tag: para
#: faq.xml:279
#, no-c-format
msgid ""
"What is the best way to find all objects within a radius of another object?"
msgstr ""
#. Tag: para
#: faq.xml:284
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: faq.xml:289
#, no-c-format
msgid ""
"The <varname>ST_DWithin(geometry, geometry, distance)</varname> function is "
"a handy way of performing an indexed distance search. It works by creating a "
"search rectangle large enough to enclose the distance radius, then "
"performing an exact distance search on the indexed subset of results."
msgstr ""
#. Tag: para
#: faq.xml:295
#, no-c-format
msgid ""
"For example, to find all objects with 100 meters of POINT(1000 1000) the "
"following query would work well:"
msgstr ""
#. Tag: programlisting
#: faq.xml:298
#, no-c-format
msgid ""
"SELECT * FROM geotable \n"
"WHERE ST_DWithin(geocolumn, 'POINT(1000 1000)', 100.0);"
msgstr ""
#. Tag: para
#: faq.xml:304
#, no-c-format
msgid "How do I perform a coordinate reprojection as part of a query?"
msgstr ""
#. Tag: para
#: faq.xml:309
#, no-c-format
msgid ""
"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. "
"The below projects a geometry to NAD 83 long lat. The below will only work "
"if the srid of the_geom is not -1 (not undefined spatial ref)"
msgstr ""
#. Tag: programlisting
#: faq.xml:316
#, no-c-format
msgid "SELECT ST_Transform(the_geom,4269) FROM geotable;"
msgstr ""
#. Tag: para
#: faq.xml:322
#, no-c-format
msgid ""
"I did an ST_AsEWKT and ST_AsText on my rather large geometry and it returned "
"blank field. What gives?"
msgstr ""
#. Tag: para
#: faq.xml:326
#, no-c-format
msgid ""
"You are probably using PgAdmin or some other tool that doesn't output large "
"text. If your geometry is big enough, it will appear blank in these tools. "
"Use PSQL if you really need to see it or output it in WKT."
msgstr ""
#. Tag: programlisting
#: faq.xml:329
#, no-c-format
msgid ""
"--To check number of geometries are really blank\n"
" SELECT count(gid) FROM geotable WHERE "
"the_geom IS NULL;"
msgstr ""
#. Tag: para
#: faq.xml:335
#, no-c-format
msgid ""
"When I do an ST_Intersects, it says my two geometries don't intersect when I "
"KNOW THEY DO. What gives?"
msgstr ""
#. Tag: para
#: faq.xml:339
#, no-c-format
msgid ""
"This generally happens in two common cases. Your geometry is invalid -- "
"check <xref linkend=\"ST_IsValid\"/> or you are assuming they intersect "
"because ST_AsText truncates the numbers and you have lots of decimals after "
"it is not showing you."
msgstr ""
#. Tag: para
#: faq.xml:347
#, no-c-format
msgid ""
"I am releasing software that uses PostGIS, does that mean my software has to "
"be licensed using the GPL like PostGIS? Will I have to publish all my code "
"if I use PostGIS?"
msgstr ""
#. Tag: para
#: faq.xml:351
#, no-c-format
msgid ""
"Almost certainly not. As an example, consider Oracle database running on "
"Linux. Linux is GPL, Oracle is not, does Oracle running on Linux have to be "
"distributed using the GPL? No. So your software can use a PostgreSQL/PostGIS "
"database as much as it wants and be under any license you like."
msgstr ""
#. Tag: para
#: faq.xml:352
#, no-c-format
msgid ""
"The only exception would be if you made changes to the PostGIS source code, "
"and distributed your changed version of PostGIS. In that case you would have "
"to share the code of your changed PostGIS (but not the code of applications "
"running on top of it). Even in this limited case, you would still only have "
"to distribute source code to people you distributed binaries to. The GPL "
"does not require that you <emphasis>publish</emphasis> your source code, "
"only that you share it with people you give binaries to."
msgstr ""

658
doc/po/pt_BR/faq_raster.xml.po Normal file
View file

@ -0,0 +1,658 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: faq_raster.xml:3
#, no-c-format
msgid "PostGIS Raster Frequently Asked Questions"
msgstr ""
#. Tag: para
#: faq_raster.xml:9
#, no-c-format
msgid "Where can I find out more about the PostGIS Raster Project?"
msgstr ""
#. Tag: para
#: faq_raster.xml:13
#, no-c-format
msgid ""
"Refer to the <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster"
"\">PostGIS Raster home page</ulink>."
msgstr ""
#. Tag: para
#: faq_raster.xml:19
#, no-c-format
msgid ""
"Are there any books or tutorials to get me started with this wonderful "
"invention?"
msgstr ""
#. Tag: para
#: faq_raster.xml:23
#, no-c-format
msgid ""
"There is a full length beginner tutorial <ulink url=\"http://trac.osgeo.org/"
"postgis/wiki/WKTRasterTutorial01\"> Intersecting vector buffers with large "
"raster coverage using PostGIS Raster</ulink>. Jorge has a series of blog "
"articles on PostGIS Raster that demonstrate how to load raster data as well "
"as cross compare to same tasks in Oracle GeoRaster. Check out <ulink url="
"\"http://gis4free.wordpress.com/category/postgis-raster/\">Jorge's PostGIS "
"Raster / Oracle GeoRaster Series</ulink>. There is a whole chapter (more "
"than 35 pages of content) dedicated to PostGIS Raster with free code and "
"data downloads at <ulink url=\"http://www.postgis.us/chapter_13\">PostGIS in "
"Action - Raster chapter</ulink>. You can <ulink url=\"http://www.postgis.us/"
"page_buy_book\">buy PostGIS in Action</ulink> now from Manning in hard-copy "
"(significant discounts for bulk purchases) or just the E-book format. You "
"can also buy from Amazon and various other book distributors. All hard-copy "
"books come with a free coupon to download the E-book version."
msgstr ""
#. Tag: para
#: faq_raster.xml:30
#, no-c-format
msgid ""
"Here is a review from a PostGIS Raster user <ulink url=\"http://"
"fuzzytolerance.info/code/postgis-raster-ftw/\">PostGIS raster applied to "
"land classification urban forestry</ulink>"
msgstr ""
#. Tag: para
#: faq_raster.xml:37
#, no-c-format
msgid "How do I install Raster support in my PostGIS database?"
msgstr ""
#. Tag: para
#: faq_raster.xml:41
#, no-c-format
msgid ""
"The easiest is to download binaries for PostGIS and Raster which are "
"currently available for windows and latest versions of Mac OSX. First you "
"need a working PostGIS 2.0.0 or above and be running PostgreSQL 8.4, 9.0, or "
"9.1. Note in PostGIS 2.0 PostGIS Raster is fully integrated, so it will be "
"compiled when you compile PostGIS."
msgstr ""
#. Tag: para
#: faq_raster.xml:43
#, no-c-format
msgid ""
"Instructions for installing and running under windows are available at "
"<ulink url=\"http://gis4free.wordpress.com/2011/03/10/how-to-install-and-"
"configure-postgis-raster-on-windows/\">How to Install and Configure PostGIS "
"raster on windows</ulink>"
msgstr ""
#. Tag: para
#: faq_raster.xml:44
#, no-c-format
msgid ""
"If you are on windows, you can compile yourself, or use the <ulink url="
"\"http://www.postgis.org/download/windows/experimental.php#wktraster\">pre-"
"compiled PostGIS Raster windows binaries</ulink>. If you are on Mac OSX "
"Leopard or Snow Leopard, there are binaries available at <ulink url=\"http://"
"www.kyngchaos.com/software/postgres\">Kyng Chaos Mac OSX PostgreSQL/GIS "
"binaries</ulink>."
msgstr ""
#. Tag: para
#: faq_raster.xml:50
#, no-c-format
msgid ""
"Then to enable raster support in your database, run the rtpostgis.sql file "
"in your database. To upgrade an existing install use "
"rtpostgis_upgrade_minor..sql instead of rtpostgis.sql"
msgstr ""
#. Tag: para
#: faq_raster.xml:51
#, no-c-format
msgid ""
"For other platforms, you generally need to compile yourself. Dependencies "
"are PostGIS and GDAL. For more details about compiling from source, please "
"refer to <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/"
"Documentation01#a2.3-CompilingandInstallingfromSources\">Installing PostGIS "
"Raster from source (in prior versions of PostGIS)</ulink>"
msgstr ""
#. Tag: para
#: faq_raster.xml:57
#, no-c-format
msgid ""
"I get error could not load library \"C:/Program Files/PostgreSQL/8.4/lib/"
"rtpostgis.dll\": The specified module could not be found. or could not load "
"library on Linux when trying to run rtpostgis.sql"
msgstr ""
#. Tag: para
#: faq_raster.xml:62
#, no-c-format
msgid ""
"rtpostgis.so/dll is built with dependency on libgdal.dll/so. Make sure for "
"Windows you have libgdal-1.dll in the bin folder of your PostgreSQL install. "
"For Linux libgdal has to be in your path or bin folder."
msgstr ""
#. Tag: para
#: faq_raster.xml:64
#, no-c-format
msgid ""
"You may also run into different errors if you don't have PostGIS installed "
"in your database. Make sure to install PostGIS first in your database before "
"trying to install the raster support."
msgstr ""
#. Tag: para
#: faq_raster.xml:71
#, no-c-format
msgid "How do I load Raster data into PostGIS?"
msgstr ""
#. Tag: para
#: faq_raster.xml:75
#, no-c-format
msgid ""
"The latest version of PostGIS comes packaged with a <varname>raster2pgsql</"
"varname> raster loader executable capable of loading many kinds of rasters "
"and also generating lower resolution overviews without any additional "
"software. Please refer to <xref linkend=\"RT_Raster_Loader\"/> for more "
"details. Pre-2.0 versions came with a <varname>raster2pgsql.py</varname> "
"that required python with numpy and GDAL. This is no longer needed."
msgstr ""
#. Tag: para
#: faq_raster.xml:81
#, no-c-format
msgid "What kind of raster file formats can I load into my database?"
msgstr ""
#. Tag: para
#: faq_raster.xml:85
#, no-c-format
msgid ""
"Any that your GDAL library supports. GDAL supported formats are documented "
"<ulink url=\"http://www.gdal.org/formats_list.html\">GDAL File Formats</"
"ulink>."
msgstr ""
#. Tag: para
#: faq_raster.xml:86
#, no-c-format
msgid ""
"Your particular GDAL install may not support all formats. To verify the ones "
"supported by your particular GDAL install, you can use"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:87
#, no-c-format
msgid "raster2pgsql -G"
msgstr ""
#. Tag: para
#: faq_raster.xml:93
#, no-c-format
msgid "Can I export my PostGIS raster data to other raster formats?"
msgstr ""
#. Tag: para
#: faq_raster.xml:97
#, no-c-format
msgid "<para>Yes</para>"
msgstr ""
#. Tag: para
#: faq_raster.xml:98
#, no-c-format
msgid ""
"GDAL 1.7+ has a PostGIS raster driver, but is only compiled in if you choose "
"to compile with PostgreSQL support."
msgstr ""
#. Tag: para
#: faq_raster.xml:99
#, no-c-format
msgid ""
"The driver currently doesn't support irregularly blocked rasters, although "
"you can store irregularly blocked rasters in PostGIS raster data type."
msgstr ""
#. Tag: para
#: faq_raster.xml:101
#, no-c-format
msgid ""
"If you are compiling from source, you need to include in your configure "
"<programlisting>--with-pg=path/to/pg_config</programlisting> to enable the "
"driver. Refer to <ulink url=\"http://trac.osgeo.org/gdal/wiki/BuildHints"
"\">GDAL Build Hints</ulink> for tips on building GDAL against in various OS "
"platforms."
msgstr ""
#. Tag: para
#: faq_raster.xml:106
#, no-c-format
msgid ""
"If your version of GDAL is compiled with the PostGIS Raster driver you "
"should see PostGIS Raster in list when you do"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:108
#, no-c-format
msgid "gdalinfo --formats"
msgstr ""
#. Tag: para
#: faq_raster.xml:110
#, no-c-format
msgid "To get a summary about your raster via GDAL use gdalinfo:"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:111
#, no-c-format
msgid ""
"gdalinfo \"PG:host=localhost port=5432 dbname='mygisdb' user='postgres' "
"password='whatever' schema='someschema' table=sometable\""
msgstr ""
#. Tag: para
#: faq_raster.xml:114
#, no-c-format
msgid ""
"To export data to other raster formats, use gdal_translate the below will "
"export all data from a table to a PNG file at 10% size."
msgstr ""
#. Tag: para
#: faq_raster.xml:116
#, no-c-format
msgid ""
"Depending on your pixel band types, some translations may not work if the "
"export format does not support that Pixel type. For example floating point "
"band types and 32 bit unsigned ints will not translate easily to JPG or some "
"others."
msgstr ""
#. Tag: para
#: faq_raster.xml:119
#, no-c-format
msgid "Here is an example simple translation"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:120
#, no-c-format
msgid ""
"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' "
"user='postgres' password=whatever' schema='someschema' table=sometable\" C:"
"\\somefile.png"
msgstr ""
#. Tag: para
#: faq_raster.xml:121
#, no-c-format
msgid ""
"You can also use SQL where clauses in your export using the where=... in "
"your driver connection string. Below are some using a where clause"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:123
#, no-c-format
msgid ""
"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' "
"user='postgres' password=whatever' schema='someschema' table=sometable where="
"\"owner='jimmy'\" \" C:\\somefile.png"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:124
#, no-c-format
msgid ""
"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' "
"user='postgres' password=whatever' schema='someschema' table=sometable "
"where='ST_Intersects(rast, ST_SetSRID(ST_Point(-71.032,42.3793),4326) )' \" "
"C:\\intersectregion.png"
msgstr ""
#. Tag: para
#: faq_raster.xml:125
#, no-c-format
msgid ""
"To see more examples and syntax refer to <ulink url=\"http://trac.osgeo.org/"
"gdal/wiki/frmts_wtkraster.html#a3.2-Readingrasterdatafromthedatabase"
"\">Reading Raster Data of PostGIS Raster section</ulink>"
msgstr ""
#. Tag: para
#: faq_raster.xml:130
#, no-c-format
msgid ""
"Are their binaries of GDAL available already compiled with PostGIS Raster "
"suppport?"
msgstr ""
#. Tag: para
#: faq_raster.xml:132
#, no-c-format
msgid ""
"Yes. Check out the page <ulink url=\"http://trac.osgeo.org/gdal/wiki/"
"DownloadingGdalBinaries\">GDAL Binaries</ulink> page. Any compiled with "
"PostgreSQL support should have PostGIS Raster in them."
msgstr ""
#. Tag: para
#: faq_raster.xml:134
#, no-c-format
msgid ""
"We know for sure the following windows binaries have PostGIS Raster built in."
msgstr ""
#. Tag: para
#: faq_raster.xml:135
#, no-c-format
msgid ""
"<ulink url=\"http://fwtools.maptools.org/\">FWTools latest stable version "
"for Windows is compiled with Raster support</ulink>."
msgstr ""
#. Tag: para
#: faq_raster.xml:136
#, no-c-format
msgid ""
"PostGIS Raster is undergoing many changes. If you want to get the latest "
"nightly build for Windows -- then check out the Tamas Szekeres nightly "
"builds built with Visual Studio which contain GDAL trunk, Python Bindings "
"and MapServer executables and PostGIS Raster driver built-in. Just click the "
"SDK bat and run your commands from there. <ulink url=\"http://vbkto.dyndns."
"org/sdk/\">http://vbkto.dyndns.org/sdk/</ulink>. Also available are VS "
"project files."
msgstr ""
#. Tag: para
#: faq_raster.xml:145
#, no-c-format
msgid "What tools can I use to view PostGIS raster data?"
msgstr ""
#. Tag: para
#: faq_raster.xml:149
#, no-c-format
msgid ""
"You can use MapServer compiled with GDAL 1.7+ and PostGIS Raster driver "
"support to view Raster data. QuantumGIS (QGIS) now supports viewing of "
"PostGIS Raster if you have PostGIS raster driver installed."
msgstr ""
#. Tag: para
#: faq_raster.xml:151
#, no-c-format
msgid ""
"In theory any tool that renders data using GDAL can support PostGIS raster "
"data or support it with fairly minimal effort. Again for Windows, Tamas' "
"binaries <ulink url=\"http://vbkto.dyndns.org/sdk/\">http://vbkto.dyndns.org/"
"sdk/</ulink> are a good choice if you don't want the hassle of having to "
"setup to compile your own."
msgstr ""
#. Tag: para
#: faq_raster.xml:158
#, no-c-format
msgid "How can I add a PostGIS raster layer to my MapServer map?"
msgstr ""
#. Tag: para
#: faq_raster.xml:162
#, no-c-format
msgid ""
"First you need GDAL 1.7 or higher compiled with PostGIS raster support. GDAL "
"1.8 or above is preferred since many issues have been fixed in 1.8 and more "
"PostGIS raster issues fixed in trunk version."
msgstr ""
#. Tag: para
#: faq_raster.xml:164
#, no-c-format
msgid ""
"You can much like you can with any other raster. Refer to <ulink url="
"\"http://mapserver.org/input/raster.html\">MapServer Raster processing "
"options</ulink> for list of various processing functions you can use with "
"MapServer raster layers."
msgstr ""
#. Tag: para
#: faq_raster.xml:167
#, no-c-format
msgid ""
"What makes PostGIS raster data particularly interesting, is that since each "
"tile can have various standard database columns, you can segment it in your "
"data source"
msgstr ""
#. Tag: para
#: faq_raster.xml:169
#, no-c-format
msgid ""
"Below is an example of how you would define a PostGIS raster layer in "
"MapServer."
msgstr ""
#. Tag: para
#: faq_raster.xml:170
#, no-c-format
msgid ""
"The mode=2 is required for tiled rasters and was added in PostGIS 2.0 and "
"GDAL 1.8 drivers. This does not exist in GDAL 1.7 drivers."
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:171
#, no-c-format
msgid ""
"-- displaying raster with standard raster options\n"
"LAYER\n"
" NAME coolwktraster\n"
" TYPE raster\n"
" STATUS ON\n"
" DATA \"PG:host=localhost port=5432 dbname='somedb' user='someuser' "
"password='whatever' \n"
" schema='someschema' table='cooltable' mode='2'\" \n"
" PROCESSING \"NODATA=0\"\n"
" PROCESSING \"SCALE=AUTO\"\n"
" #... other standard raster processing functions here\n"
" #... classes are optional but useful for 1 band data\n"
" CLASS\n"
" NAME \"boring\"\n"
" EXPRESSION ([pixel] &lt; 20)\n"
" COLOR 250 250 250\n"
" END\n"
" CLASS\n"
" NAME \"mildly interesting\"\n"
" EXPRESSION ([pixel] &gt; 20 AND [pixel] &lt; 1000)\n"
" COLOR 255 0 0\n"
" END\n"
" CLASS\n"
" NAME \"very interesting\"\n"
" EXPRESSION ([pixel] &gt;= 1000)\n"
" COLOR 0 255 0\n"
" END\n"
"END"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:173
#, no-c-format
msgid ""
"-- displaying raster with standard raster options and a where clause\n"
"LAYER\n"
" NAME soil_survey2009\n"
" TYPE raster\n"
" STATUS ON\n"
" DATA \"PG:host=localhost port=5432 dbname='somedb' user='someuser' "
"password='whatever' \n"
" schema='someschema' table='cooltable' "
"where='survey_year=2009' mode='2'\" \n"
" PROCESSING \"NODATA=0\"\n"
" #... other standard raster processing functions here\n"
" #... classes are optional but useful for 1 band data\n"
"END"
msgstr ""
#. Tag: para
#: faq_raster.xml:181
#, no-c-format
msgid "What functions can I currently use with my raster data?"
msgstr ""
#. Tag: para
#: faq_raster.xml:185
#, no-c-format
msgid ""
"Refer to the list of <xref linkend=\"RT_reference\"/>. There are more, but "
"this is still a work in progress."
msgstr ""
#. Tag: para
#: faq_raster.xml:187
#, no-c-format
msgid ""
"Refer to the <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/"
"PlanningAndFunding\">PostGIS Raster roadmap page</ulink> for details of what "
"you can expect in the future."
msgstr ""
#. Tag: para
#: faq_raster.xml:195
#, no-c-format
msgid ""
"I am getting error ERROR: function st_intersects(raster, unknown) is not "
"unique or st_union(geometry,text) is not unique. How do I fix?"
msgstr ""
#. Tag: para
#: faq_raster.xml:199
#, no-c-format
msgid ""
"The function is not unique error happens if one of your arguments is a "
"textual representation of a geometry instead of a geometry. In these cases, "
"PostgreSQL marks the textual representation as an unknown type, which means "
"it can fall into the st_intersects(raster, geometry) or st_intersects(raster,"
"raster) thus resulting in a non-unique case since both functions can in "
"theory support your request. To prevent this, you need to cast the geometry "
"to a geometry."
msgstr ""
#. Tag: para
#: faq_raster.xml:200
#, no-c-format
msgid "For example if your code looks like this:"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:201
#, no-c-format
msgid ""
"SELECT rast\n"
" FROM my_raster\n"
" WHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)');"
msgstr ""
#. Tag: para
#: faq_raster.xml:202
#, no-c-format
msgid ""
"Cast the textual geometry representation to a geometry by changing your code "
"to this:"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:203
#, no-c-format
msgid ""
"SELECT rast\n"
" FROM my_raster\n"
" WHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)'::geometry);"
msgstr ""
#. Tag: para
#: faq_raster.xml:211
#, no-c-format
msgid ""
"How is PostGIS Raster different from Oracle GeoRaster (SDO_GEORASTER) and "
"SDO_RASTER types?"
msgstr ""
#. Tag: para
#: faq_raster.xml:215
#, no-c-format
msgid ""
"For a more extensive discussion on this topic, check out Jorge Arévalo "
"<ulink url=\"http://gis4free.wordpress.com/2010/07/19/oracle-georaster-part-"
"i/\">Oracle GeoRaster and PostGIS Raster: First impressions </ulink>"
msgstr ""
#. Tag: para
#: faq_raster.xml:216
#, no-c-format
msgid ""
"The major advantage of one-georeference-by-raster over one-georeference-by-"
"layer is to allow:"
msgstr ""
#. Tag: para
#: faq_raster.xml:217
#, no-c-format
msgid ""
"* coverages to be not necessarily rectangular (which is often the case of "
"raster coverage covering large extents. See the possible raster arrangements "
"in the documentation)"
msgstr ""
#. Tag: para
#: faq_raster.xml:218
#, no-c-format
msgid ""
"* rasters to overlaps (which is necessary to implement lossless vector to "
"raster conversion)"
msgstr ""
#. Tag: para
#: faq_raster.xml:219
#, no-c-format
msgid ""
"These arrangements are possible in Oracle as well, but they imply the "
"storage of multiple SDO_GEORASTER objects linked to as many SDO_RASTER "
"tables. A complex coverage can lead to hundreds of tables in the database. "
"With PostGIS Raster you can store a similar raster arrangement into a unique "
"table."
msgstr ""
#. Tag: para
#: faq_raster.xml:224
#, no-c-format
msgid ""
"It's a bit like if PostGIS would force you to store only full rectangular "
"vector coverage without gaps or overlaps (a perfect rectangular topological "
"layer). This is very practical in some applications but practice has shown "
"that it is not realistic or desirable for most geographical coverages. "
"Vector structures needs the flexibility to store discontinuous and non-"
"rectangular coverages. We think it is a big advantage that raster structure "
"should benefit as well."
msgstr ""

1680
doc/po/pt_BR/installation.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

509
doc/po/pt_BR/introduction.xml.po Normal file
View file

@ -0,0 +1,509 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: introduction.xml:3
#, no-c-format
msgid "Introduction"
msgstr ""
#. Tag: para
#: introduction.xml:5
#, no-c-format
msgid ""
"PostGIS was 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."
msgstr ""
#. Tag: para
#: introduction.xml:15
#, no-c-format
msgid ""
"PostGIS is an incubation project of the OSGeo Foundation. PostGIS is being "
"continually improved and funded by many FOSS4G Developers as well as "
"corporations all over the world that gain great benefit from its "
"functionality and versatility."
msgstr ""
#. Tag: title
#: introduction.xml:21
#, no-c-format
msgid "Project Steering Committee"
msgstr ""
#. Tag: para
#: introduction.xml:22
#, no-c-format
msgid ""
"The PostGIS Project Steering Committee (PSC) coordinates the general "
"direction, release cycles, documentation, and outreach efforts for the "
"PostGIS project. In addition the PSC provides general user support, accepts "
"and approves patches from the general PostGIS community and votes on "
"miscellaneous issues involving PostGIS such as developer commit access, new "
"PSC members or significant API changes."
msgstr ""
#. Tag: term
#: introduction.xml:31
#, no-c-format
msgid "Mark Cave-Ayland"
msgstr ""
#. Tag: para
#: introduction.xml:33
#, no-c-format
msgid ""
"Coordinates bug fixing and maintenance effort, alignment of PostGIS with "
"PostgreSQL releases, spatial index selectivity and binding, loader/dumper, "
"and Shapefile GUI Loader, integration of new and new function enhancements."
msgstr ""
#. Tag: term
#: introduction.xml:40
#, no-c-format
msgid "Regina Obe"
msgstr ""
#. Tag: para
#: introduction.xml:42
#, no-c-format
msgid ""
"Buildbot Maintenance, windows production and experimental builds, "
"Documentation, general user support on PostGIS newsgroup, X3D support, Tiger "
"Geocoder Support, management functions, and smoke testing new functionality "
"or major code changes."
msgstr ""
#. Tag: term
#: introduction.xml:49
#, no-c-format
msgid "Paul Ramsey (Chair)"
msgstr ""
#. Tag: para
#: introduction.xml:51
#, no-c-format
msgid ""
"Co-founder of PostGIS project. General bug fixing, geography support, "
"geography and geometry index support (2D, 3D, nD index and anything spatial "
"index), underlying geometry internal structures, GEOS functionality "
"integration and alignment with GEOS releases, loader/dumper, and Shapefile "
"GUI loader."
msgstr ""
#. Tag: term
#: introduction.xml:57
#, no-c-format
msgid "Sandro Santilli"
msgstr ""
#. Tag: para
#: introduction.xml:60
#, no-c-format
msgid ""
"Bug fixes and maintenance and integration of new GEOS functionality and "
"alignment with GEOS releases, Topology support, and Raster framework and low "
"level api functions."
msgstr ""
#. Tag: title
#: introduction.xml:67
#, no-c-format
msgid "Contributors Past and Present"
msgstr ""
#. Tag: term
#: introduction.xml:71
#, no-c-format
msgid "Chris Hodgson"
msgstr ""
#. Tag: para
#: introduction.xml:73
#, no-c-format
msgid ""
"Prior PSC Member. General development, site and buildbot maintenance, OSGeo "
"incubation management"
msgstr ""
#. Tag: term
#: introduction.xml:77
#, no-c-format
msgid "Kevin Neufeld"
msgstr ""
#. Tag: para
#: introduction.xml:79
#, no-c-format
msgid ""
"Prior PSC Member. Documentation and documentation support tools, advanced "
"user support on PostGIS newsgroup, and PostGIS maintenance function "
"enhancements."
msgstr ""
#. Tag: term
#: introduction.xml:85
#, no-c-format
msgid "Dave Blasby"
msgstr ""
#. Tag: para
#: introduction.xml:88
#, no-c-format
msgid ""
"The original developer/Co-founder of PostGIS. Dave wrote the server side "
"objects, index bindings, and many of the server side analytical functions."
msgstr ""
#. Tag: term
#: introduction.xml:95
#, no-c-format
msgid "Jeff Lounsbury"
msgstr ""
#. Tag: para
#: introduction.xml:97
#, no-c-format
msgid ""
"Original development of the Shape file loader/dumper. Current PostGIS "
"Project Owner representative."
msgstr ""
#. Tag: term
#: introduction.xml:102
#, no-c-format
msgid "Olivier Courtin"
msgstr ""
#. Tag: para
#: introduction.xml:104
#, no-c-format
msgid "Input output XML (KML,GML)/GeoJSON functions, 3D support and bug fixes."
msgstr ""
#. Tag: term
#: introduction.xml:109
#, no-c-format
msgid "Mark Leslie"
msgstr ""
#. Tag: para
#: introduction.xml:111
#, no-c-format
msgid ""
"Ongoing maintenance and development of core functions. Enhanced curve "
"support. Shapefile GUI loader."
msgstr ""
#. Tag: term
#: introduction.xml:116
#, no-c-format
msgid "Pierre Racine"
msgstr ""
#. Tag: para
#: introduction.xml:118
#, no-c-format
msgid "Raster overall architecture, prototyping, programming support"
msgstr ""
#. Tag: term
#: introduction.xml:123
#, no-c-format
msgid "Nicklas Avén"
msgstr ""
#. Tag: para
#: introduction.xml:126
#, no-c-format
msgid ""
"Distance function enhancements (including 3D distance and relationship "
"functions) and additions, Windows testing, and general user support"
msgstr ""
#. Tag: term
#: introduction.xml:131
#, no-c-format
msgid "Jorge Arévalo"
msgstr ""
#. Tag: para
#: introduction.xml:134
#, no-c-format
msgid "Raster development, GDAL driver support, loader"
msgstr ""
#. Tag: term
#: introduction.xml:139
#, no-c-format
msgid "Bborie Park"
msgstr ""
#. Tag: para
#: introduction.xml:141
#, no-c-format
msgid "Raster development, raster loader"
msgstr ""
#. Tag: term
#: introduction.xml:146
#, no-c-format
msgid "Mateusz Loskot"
msgstr ""
#. Tag: para
#: introduction.xml:148
#, no-c-format
msgid "Raster loader, low level raster api functions"
msgstr ""
#. Tag: term
#: introduction.xml:153
#, no-c-format
msgid "David Zwarg"
msgstr ""
#. Tag: para
#: introduction.xml:156
#, no-c-format
msgid "Raster development"
msgstr ""
#. Tag: term
#: introduction.xml:161
#, no-c-format
msgid "Other contributors: Individuals"
msgstr ""
#. Tag: para
#: introduction.xml:164
#, no-c-format
msgid ""
"In alphabetical order: Alex Bodnaru, Alex Mayrhofer, Andrea Peri, Andreas "
"Forø Tollefsen, Andreas Neumann, Anne Ghisla, Barbara Phillipot, Ben Jubb, "
"Bernhard Reiter, Brian Hamlin, Bruce Rindahl, Bruno Wolff III, Bryce L. "
"Nordgren, Carl Anderson, Charlie Savage, Dane Springmeyer, David Skea, David "
"Techer, Eduin Carrillo, Even Rouault, Frank Warmerdam, George Silva, Gerald "
"Fenoy, Gino Lucrezi, Guillaume Lelarge, IIDA Tetsushi, Ingvild Nystuen, Jeff "
"Adams, Jose Carlos Martinez Llari, Kashif Rasul, Klaus Foerster, Kris Jurka, "
"Leo Hsu, Loic Dachary, Luca S. Percich, Maria Arias de Reyna, Mark Sondheim, "
"Markus Schaber, Maxime Guillaud, Maxime van Noppen, Michael Fuhr, Nikita "
"Shulga, Norman Vine, Rafal Magda, Ralph Mason, Richard Greenwood, Silvio "
"Grosso, Steffen Macke, Stephen Frost, Tom van Tilburg, Vincent Picavet"
msgstr ""
#. Tag: term
#: introduction.xml:221
#, no-c-format
msgid "Other contributors: Corporate Sponsors"
msgstr ""
#. Tag: para
#: introduction.xml:224
#, no-c-format
msgid ""
"These are corporate entities that have contributed developer time, hosting, "
"or direct monetary funding to the PostGIS project"
msgstr ""
#. Tag: para
#: introduction.xml:225
#, no-c-format
msgid ""
"In alphabetical order: Arrival 3D, Associazione Italiana per l'Informazione "
"Geografica Libera (GFOSS.it), AusVet, Avencia, Azavea, Cadcorp, CampToCamp, "
"City of Boston (DND), Clever Elephant Solutions, Cooperativa Alveo, Deimos "
"Space, Faunalia, Geographic Data BC, Hunter Systems Group, Lidwala "
"Consulting Engineers, LisaSoft, Logical Tracking &amp; Tracing International "
"AG, Michigan Tech Research Institute, Norwegian Forest and Landscape "
"Institute, OpenGeo, OSGeo, Oslandia, Paragon Corporation, R3 GIS,, "
"Refractions Research, Regione Toscana-SIGTA, Safe Software, Sirius "
"Corporation plc, Stadt Uster, UC Davis Center for Vectorborne Diseases, "
"University of Laval, U.S Department of State (HIU), Vizzuality, Zonar Systems"
msgstr ""
#. Tag: term
#: introduction.xml:265
#, no-c-format
msgid "Crowd Funding Campaigns"
msgstr ""
#. Tag: para
#: introduction.xml:268
#, no-c-format
msgid ""
"Crowd funding campaigns are campaigns we run to get badly wanted features "
"funded that can service a large number of people. Each campaign is "
"specifically focused on a particular feature or set of features. Each "
"sponsor chips in a small fraction of the needed funding and with enough "
"people/organizations contributing, we have the funds to pay for the work "
"that will help many. If you have an idea for a feature you think many others "
"would be willing to co-fund, please post to the <ulink url=\"http://www."
"postgis.org/mailman/listinfo/postgis-users\">PostGIS newsgroup</ulink> your "
"thoughts and together we can make it happen."
msgstr ""
#. Tag: para
#: introduction.xml:269
#, no-c-format
msgid ""
"PostGIS 2.0.0 was the first release we tried this strategy. We used <ulink "
"url=\"http://www.pledgebank.com\">PledgeBank</ulink> and we got two "
"successful campaigns out of it."
msgstr ""
#. Tag: para
#: introduction.xml:270
#, no-c-format
msgid ""
"<ulink url=\"http://www.pledgebank.com/postgistopology\"><emphasis role="
"\"bold\">postgistopology</emphasis></ulink> - 10 plus sponsors each "
"contributed $250 USD to build toTopoGeometry function and beef up topology "
"support in 2.0.0. It happened."
msgstr ""
#. Tag: para
#: introduction.xml:271
#, no-c-format
msgid ""
"<ulink url=\"http://www.pledgebank.com/postgis64windows\"><emphasis role="
"\"bold\">postgis64windows</emphasis></ulink> - 20 someodd sponsors each "
"contributed $100 USD to pay for the work needed to work out PostGIS 64-bit "
"on windows issues. It happened. We now have a 64-bit beta release for "
"PostGIS 2.0.0 and a final one planned for release that will be available on "
"PostgreSQL stack builder."
msgstr ""
#. Tag: term
#: introduction.xml:276
#, no-c-format
msgid "Important Support Libraries"
msgstr ""
#. Tag: para
#: introduction.xml:279
#, no-c-format
msgid ""
"The <ulink url=\"http://trac.osgeo.org/geos/\">GEOS</ulink> geometry "
"operations library, and the algorithmic work of Martin Davis in making it "
"all work, ongoing maintenance and support of Mateusz Loskot, Sandro Santilli "
"(strk), Paul Ramsey and others."
msgstr ""
#. Tag: para
#: introduction.xml:284
#, no-c-format
msgid ""
"The <ulink url=\"http://trac.osgeo.org/gdal/\">GDAL</ulink> Geospatial Data "
"Abstraction Library, by Frank Warmerdam and others is used to power much of "
"the raster functionality introduced in PostGIS 2.0.0. In kind, improvements "
"needed in GDAL to support PostGIS are contributed back to the GDAL project."
msgstr ""
#. Tag: para
#: introduction.xml:289
#, no-c-format
msgid ""
"The <ulink url=\"http://trac.osgeo.org/proj/\">Proj4</ulink> cartographic "
"projection library, and the work of Gerald Evenden and Frank Warmerdam in "
"creating and maintaining it."
msgstr ""
#. Tag: para
#: introduction.xml:293
#, no-c-format
msgid ""
"Last but not least, the <ulink url=\"http://www.postgresql.org\">PostgreSQL "
"DBMS</ulink>, The giant that PostGIS stands on. Much of the speed and "
"flexibility of PostGIS would not be possible without the extensibility, "
"great query planner, GIST index, and plethora of SQL features provided by "
"PostgreSQL."
msgstr ""
#. Tag: title
#: introduction.xml:302
#, no-c-format
msgid "More Information"
msgstr ""
#. Tag: para
#: introduction.xml:306
#, no-c-format
msgid ""
"The latest software, documentation and news items are available at the "
"PostGIS web site, <ulink url=\"http://www.postgis.org\">http://www.postgis."
"org</ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:312
#, no-c-format
msgid ""
"More information about the GEOS geometry operations library is available "
"at<ulink url=\"http://trac.osgeo.org/geos/\"> http://trac.osgeo.org/geos/</"
"ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:318
#, no-c-format
msgid ""
"More information about the Proj4 reprojection library is available at <ulink "
"url=\"http://trac.osgeo.org/proj/\">http://trac.osgeo.org/proj/</ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:324
#, no-c-format
msgid ""
"More information about the PostgreSQL database server is available at the "
"PostgreSQL main site <ulink url=\"http://www.postgresql.org\">http://www."
"postgresql.org</ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:330
#, no-c-format
msgid ""
"More information about GiST indexing is available at the PostgreSQL GiST "
"development site, <ulink url=\"http://www.sai.msu.su/~megera/postgres/gist/"
"\">http://www.sai.msu.su/~megera/postgres/gist/</ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:336
#, no-c-format
msgid ""
"More information about MapServer internet map server is available at <ulink "
"url=\"http://mapserver.org/\">http://mapserver.org</ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:342
#, no-c-format
msgid ""
"The &quot;<ulink url=\"http://www.opengeospatial.org/standards/sfs\">Simple "
"Features for Specification for SQL</ulink>&quot; is available at the OpenGIS "
"Consortium web site: <ulink url=\"http://www.opengeospatial.org/\">http://"
"www.opengeospatial.org/</ulink>."
msgstr ""

463
doc/po/pt_BR/performance_tips.xml.po Normal file
View file

@ -0,0 +1,463 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: performance_tips.xml:3
#, no-c-format
msgid "Performance tips"
msgstr ""
#. Tag: title
#: performance_tips.xml:6
#, no-c-format
msgid "Small tables of large geometries"
msgstr ""
#. Tag: title
#: performance_tips.xml:9
#, no-c-format
msgid "Problem description"
msgstr ""
#. Tag: para
#: performance_tips.xml:11
#, no-c-format
msgid ""
"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 <ulink url=\"http://www.postgresql.org/docs/current/"
"static/storage-toast.html\">the PostgreSQL Documentation for TOAST</ulink> "
"for more information)."
msgstr ""
#. Tag: para
#: performance_tips.xml:19
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: performance_tips.xml:26
#, no-c-format
msgid ""
"Now issue a query where you use the geometry operator &amp;&amp; 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 &amp;&amp; operator has to fetch every "
"geometry from disk to compare the bounding boxes, thus reading all TOAST "
"pages, too."
msgstr ""
#. Tag: para
#: performance_tips.xml:35
#, no-c-format
msgid ""
"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"
msgstr ""
#. Tag: title
#: performance_tips.xml:43
#, no-c-format
msgid "Workarounds"
msgstr ""
#. Tag: para
#: performance_tips.xml:45
#, no-c-format
msgid ""
"The PostgreSQL people are trying to solve this issue by making the query "
"estimation TOAST-aware. For now, here are two workarounds:"
msgstr ""
#. Tag: para
#: performance_tips.xml:48
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: performance_tips.xml:56
#, no-c-format
msgid ""
"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:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:61
#, no-c-format
msgid ""
"SELECT AddGeometryColumn"
"('myschema','mytable','bbox','4326','GEOMETRY','2'); \n"
"UPDATE mytable SET bbox = ST_Envelope(ST_Force_2d(the_geom));"
msgstr ""
#. Tag: para
#: performance_tips.xml:63
#, no-c-format
msgid ""
"Now change your query to use the &amp;&amp; operator against bbox instead of "
"geom_column, like:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:66
#, no-c-format
msgid ""
"SELECT geom_column \n"
"FROM mytable \n"
"WHERE bbox &amp;&amp; ST_SetSRID('BOX3D(0 0,1 1)'::box3d,4326);"
msgstr ""
#. Tag: para
#: performance_tips.xml:68
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: title
#: performance_tips.xml:77
#, no-c-format
msgid "CLUSTERing on geometry indices"
msgstr ""
#. Tag: para
#: performance_tips.xml:79
#, no-c-format
msgid ""
"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.)"
msgstr ""
#. Tag: para
#: performance_tips.xml:89
#, no-c-format
msgid ""
"However, currently PostgreSQL does not allow clustering on PostGIS GIST "
"indices because GIST indices simply ignores NULL values, you get an error "
"message like:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:93
#, no-c-format
msgid ""
"lwgeom=# CLUSTER my_geom_index ON my_table; \n"
"ERROR: cannot cluster when index access method does not handle null values\n"
"HINT: You may be able to work around this by marking column \"the_geom\" NOT "
"NULL."
msgstr ""
#. Tag: para
#: performance_tips.xml:95
#, no-c-format
msgid ""
"As the HINT message tells you, one can work around this deficiency by adding "
"a \"not null\" constraint to the table:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:98
#, no-c-format
msgid ""
"lwgeom=# ALTER TABLE my_table ALTER COLUMN the_geom SET not null; \n"
"ALTER TABLE"
msgstr ""
#. Tag: para
#: performance_tips.xml:100
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: title
#: performance_tips.xml:107
#, no-c-format
msgid "Avoiding dimension conversion"
msgstr ""
#. Tag: para
#: performance_tips.xml:109
#, no-c-format
msgid ""
"Sometimes, you happen to have 3D or 4D data in your table, but always access "
"it using OpenGIS compliant ST_AsText() or ST_AsBinary() functions that only "
"output 2D geometries. They do this by internally calling the ST_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:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:116
#, no-c-format
msgid ""
"UPDATE mytable SET the_geom = ST_Force_2d(the_geom); \n"
"VACUUM FULL ANALYZE mytable;"
msgstr ""
#. Tag: para
#: performance_tips.xml:118
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: performance_tips.xml:124
#, no-c-format
msgid ""
"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)&gt;2\" "
"skips re-writing of geometries that already are in 2D."
msgstr ""
#. Tag: title
#: performance_tips.xml:136
#, no-c-format
msgid "Tuning your configuration"
msgstr ""
#. Tag: para
#: performance_tips.xml:138
#, no-c-format
msgid ""
"These tips are taken from Kevin Neufeld's presentation \"Tips for the "
"PostGIS Power User\" at the FOSS4G 2007 conference. Depending on your use of "
"PostGIS (for example, static data and complex analysis vs frequently updated "
"data and lots of users) these changes can provide significant speedups to "
"your queries."
msgstr ""
#. Tag: para
#: performance_tips.xml:144
#, no-c-format
msgid ""
"For a more tips (and better formatting), the original presentation is at "
"<ulink url=\"http://2007.foss4g.org/presentations/view.php?"
"abstract_id=117\"> http://2007.foss4g.org/presentations/view.php?"
"abstract_id=117</ulink>."
msgstr ""
#. Tag: title
#: performance_tips.xml:151
#, no-c-format
msgid "Startup"
msgstr ""
#. Tag: para
#: performance_tips.xml:153
#, no-c-format
msgid "These settings are configured in postgresql.conf:"
msgstr ""
#. Tag: ulink
#: performance_tips.xml:158
#, no-c-format
msgid "checkpoint_segments"
msgstr ""
#. Tag: para
#: performance_tips.xml:163
#, no-c-format
msgid ""
"Maximum number of log file segments between automatic WAL checkpoints (each "
"segment is normally 16MB); default is 3"
msgstr ""
#. Tag: para
#: performance_tips.xml:169
#, no-c-format
msgid ""
"Set to at least 10 or 30 for databases with heavy write activity, or more "
"for large database loads. Another article on the topic worth reading <ulink "
"url=\"http://www.westnet.com/~gsmith/content/postgresql/chkp-bgw-83.htm"
"\">Greg Smith: Checkpoint and Background writer</ulink>"
msgstr ""
#. Tag: para
#: performance_tips.xml:175
#, no-c-format
msgid "Possibly store the xlog on a separate disk device"
msgstr ""
#. Tag: ulink
#: performance_tips.xml:182
#, no-c-format
msgid "constraint_exclusion"
msgstr ""
#. Tag: para
#: performance_tips.xml:187
#, no-c-format
msgid ""
"Default: off (prior to PostgreSQL 8.4 and for PostgreSQL 8.4+ is set to "
"partition)"
msgstr ""
#. Tag: para
#: performance_tips.xml:192
#, no-c-format
msgid ""
"This is generally used for table partitioning. If you are running PostgreSQL "
"versions below 8.4, set to \"on\" to ensure the query planner will optimize "
"as desired. As of PostgreSQL 8.4, the default for this is set to \"partition"
"\" which is ideal for PostgreSQL 8.4 and above since it will force the "
"planner to only analyze tables for constraint consideration if they are in "
"an inherited hierarchy and not pay the planner penalty otherwise."
msgstr ""
#. Tag: ulink
#: performance_tips.xml:202
#, no-c-format
msgid "shared_buffers"
msgstr ""
#. Tag: para
#: performance_tips.xml:207
#, no-c-format
msgid "Default: ~32MB"
msgstr ""
#. Tag: para
#: performance_tips.xml:212
#, no-c-format
msgid "Set to about 1/3 to 3/4 of available RAM"
msgstr ""
#. Tag: title
#: performance_tips.xml:220
#, no-c-format
msgid "Runtime"
msgstr ""
#. Tag: para
#: performance_tips.xml:222
#, no-c-format
msgid ""
"<ulink url=\"http://www.postgresql.org/docs/current/static/runtime-config-"
"resource.html#GUC-WORK-MEM\">work_mem</ulink> (the memory used for sort "
"operations and complex queries)"
msgstr ""
#. Tag: para
#: performance_tips.xml:228
#, no-c-format
msgid "Default: 1MB"
msgstr ""
#. Tag: para
#: performance_tips.xml:233
#, no-c-format
msgid "Adjust up for large dbs, complex queries, lots of RAM"
msgstr ""
#. Tag: para
#: performance_tips.xml:238
#, no-c-format
msgid "Adjust down for many concurrent users or low RAM."
msgstr ""
#. Tag: para
#: performance_tips.xml:243
#, no-c-format
msgid "If you have lots of RAM and few developers:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:245
#, no-c-format
msgid "SET work_mem TO 1200000;"
msgstr ""
#. Tag: para
#: performance_tips.xml:250
#, no-c-format
msgid ""
"<ulink url=\"http://www.postgresql.org/docs/current/static/runtime-config-"
"resource.html#GUC-MAINTENANCE-WORK-MEM\">maintenance_work_mem</ulink> (used "
"for VACUUM, CREATE INDEX, etc.)"
msgstr ""
#. Tag: para
#: performance_tips.xml:256
#, no-c-format
msgid "Default: 16MB"
msgstr ""
#. Tag: para
#: performance_tips.xml:261
#, no-c-format
msgid "Generally too low - ties up I/O, locks objects while swapping memory"
msgstr ""
#. Tag: para
#: performance_tips.xml:266
#, no-c-format
msgid ""
"Recommend 32MB to 256MB on production servers w/lots of RAM, but depends on "
"the # of concurrent users. If you have lots of RAM and few developers:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:269
#, no-c-format
msgid "SET maintainence_work_mem TO 1200000;"
msgstr ""

59
doc/po/pt_BR/postgis.xml.po Normal file
View file

@ -0,0 +1,59 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: postgis.xml:106
#, no-c-format
msgid "PostGIS &last_release_version; Manual"
msgstr ""
#. Tag: affiliation
#: postgis.xml:114
#, no-c-format
msgid ""
"<orgname><ulink url=\"http://www.cleverelephant.ca\">clever elephant</"
"ulink></orgname> <address><city>Victoria</city> <state>British Columbia</"
"state> <country>Canada</country> <email>pramsey@cleverelephant.ca</email></"
"address>"
msgstr ""
#. Tag: para
#: postgis.xml:124
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: postgis.xml:133
#, no-c-format
msgid "This is the manual for version &last_release_version;"
msgstr ""
#. Tag: para
#: postgis.xml:134
#, no-c-format
msgid ""
"This work is licensed under a <ulink url=\"http://creativecommons.org/"
"licenses/by-sa/3.0/\">Creative Commons Attribution-Share Alike 3.0 License</"
"ulink>. Feel free to use this material any way you like, but we ask that you "
"attribute credit to the PostGIS Project and wherever possible, a link back "
"to <ulink url=\"http://www.postgis.org\">http://www.postgis.org</ulink>."
msgstr ""

55
doc/po/pt_BR/reference.xml.po Normal file
View file

@ -0,0 +1,55 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reference.xml:3
#, no-c-format
msgid "PostGIS Reference"
msgstr ""
#. Tag: para
#: reference.xml:5
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: reference.xml:11
#, no-c-format
msgid ""
"PostGIS has begun a transition from the existing naming convention to an SQL-"
"MM-centric convention. As a result, most of the functions that you know and "
"love have been renamed using the standard spatial type (ST) prefix. Previous "
"functions are still available, though are not listed in this document where "
"updated functions are equivalent. The non ST_ functions not listed in this "
"documentation are deprecated and will be removed in a future release so STOP "
"USING THEM."
msgstr ""
#. Tag: chapter
#: reference.xml:16
#, no-c-format
msgid ""
"&reference_type; &reference_management; &reference_constructor; "
"&reference_accessor; &reference_editor; &reference_output; "
"&reference_operator; &reference_measure; &reference_processing; "
"&reference_lrs; &reference_transaction; &reference_misc; "
"&reference_exception;"
msgstr ""

3337
doc/po/pt_BR/reference_accessor.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

2934
doc/po/pt_BR/reference_constructor.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

2417
doc/po/pt_BR/reference_editor.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

224
doc/po/pt_BR/reference_exception.xml.po Normal file
View file

@ -0,0 +1,224 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reference_exception.xml:3
#, no-c-format
msgid "Exceptional Functions"
msgstr ""
#. Tag: para
#: reference_exception.xml:4
#, no-c-format
msgid ""
"These functions are rarely used functions that should only be used if your "
"data is corrupted in someway. They are used for troubleshooting corruption "
"and also fixing things that should under normal circumstances, never happen."
msgstr ""
#. Tag: refname
#: reference_exception.xml:9
#, no-c-format
msgid "PostGIS_AddBBox"
msgstr ""
#. Tag: refpurpose
#: reference_exception.xml:11
#, no-c-format
msgid "Add bounding box to the geometry."
msgstr ""
#. Tag: funcprototype
#: reference_exception.xml:16
#, no-c-format
msgid ""
"<funcdef>geometry <function>PostGIS_AddBBox</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: title
#: reference_exception.xml:24 reference_exception.xml:70
#: reference_exception.xml:119
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: reference_exception.xml:26
#, no-c-format
msgid ""
"Add bounding box to the geometry. This would make bounding box based queries "
"faster, but will increase the size of the geometry."
msgstr ""
#. Tag: para
#: reference_exception.xml:31
#, no-c-format
msgid ""
"Bounding boxes are automatically added to geometries so in general this is "
"not needed unless the generated bounding box somehow becomes corrupted or "
"you have an old install that is lacking bounding boxes. Then you need to "
"drop the old and readd."
msgstr ""
#. Tag: para
#: reference_exception.xml:35 reference_exception.xml:83
#: reference_exception.xml:124
#, no-c-format
msgid "&curve_support;"
msgstr ""
#. Tag: title
#: reference_exception.xml:40 reference_exception.xml:88
#: reference_exception.xml:129
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: programlisting
#: reference_exception.xml:42
#, no-c-format
msgid ""
"UPDATE sometable\n"
" SET the_geom = PostGIS_AddBBox(the_geom)\n"
" WHERE PostGIS_HasBBox(the_geom) = false;"
msgstr ""
#. Tag: title
#: reference_exception.xml:47 reference_exception.xml:95
#: reference_exception.xml:136
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: para
#: reference_exception.xml:49
#, no-c-format
msgid ", <xref linkend=\"PostGIS_HasBBox\"/>"
msgstr ""
#. Tag: refname
#: reference_exception.xml:55
#, no-c-format
msgid "PostGIS_DropBBox"
msgstr ""
#. Tag: refpurpose
#: reference_exception.xml:57
#, no-c-format
msgid "Drop the bounding box cache from the geometry."
msgstr ""
#. Tag: funcprototype
#: reference_exception.xml:62
#, no-c-format
msgid ""
"<funcdef>geometry <function>PostGIS_DropBBox</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_exception.xml:72
#, no-c-format
msgid ""
"Drop the bounding box cache from the geometry. This reduces geometry size, "
"but makes bounding-box based queries slower. It is also used to drop a "
"corrupt bounding box. A tale-tell sign of a corrupt cached bounding box is "
"when your ST_Intersects and other relation queries leave out geometries that "
"rightfully should return true."
msgstr ""
#. Tag: para
#: reference_exception.xml:77
#, no-c-format
msgid ""
"Bounding boxes are automatically added to geometries and improve speed of "
"queries so in general this is not needed unless the generated bounding box "
"somehow becomes corrupted or you have an old install that is lacking "
"bounding boxes. Then you need to drop the old and readd. This kind of "
"corruption has been observed in 8.3-8.3.6 series whereby cached bboxes were "
"not always recalculated when a geometry changed and upgrading to a newer "
"version without a dump reload will not correct already corrupted boxes. So "
"one can manually correct using below and readd the bbox or do a dump reload."
msgstr ""
#. Tag: programlisting
#: reference_exception.xml:90
#, no-c-format
msgid ""
"--This example drops bounding boxes where the cached box is not correct\n"
" --The force to ST_AsBinary before applying Box2D "
"forces a recalculation of the box, and Box2D applied to the table geometry "
"always\n"
" -- returns the cached bounding box.\n"
" UPDATE sometable\n"
" SET the_geom = PostGIS_DropBBox(the_geom)\n"
" WHERE Not (Box2D(ST_AsBinary(the_geom)) = Box2D(the_geom));\n"
"\n"
" UPDATE sometable\n"
" SET the_geom = PostGIS_AddBBox(the_geom)\n"
" WHERE Not PostGIS_HasBBOX(the_geom);"
msgstr ""
#. Tag: para
#: reference_exception.xml:97
#, no-c-format
msgid ", <xref linkend=\"PostGIS_HasBBox\"/>, <xref linkend=\"Box2D\"/>"
msgstr ""
#. Tag: refname
#: reference_exception.xml:104
#, no-c-format
msgid "PostGIS_HasBBox"
msgstr ""
#. Tag: refpurpose
#: reference_exception.xml:106
#, no-c-format
msgid "Returns TRUE if the bbox of this geometry is cached, FALSE otherwise."
msgstr ""
#. Tag: funcprototype
#: reference_exception.xml:111
#, no-c-format
msgid ""
"<funcdef>boolean <function>PostGIS_HasBBox</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_exception.xml:121
#, no-c-format
msgid ""
"Returns TRUE if the bbox of this geometry is cached, FALSE otherwise. Use "
"<xref linkend=\"PostGIS_AddBBox\"/> and <xref linkend=\"PostGIS_DropBBox\"/> "
"to control caching."
msgstr ""
#. Tag: programlisting
#: reference_exception.xml:131
#, no-c-format
msgid ""
"SELECT the_geom\n"
"FROM sometable WHERE PostGIS_HasBBox(the_geom) = false;"
msgstr ""
#. Tag: para
#: reference_exception.xml:138
#, no-c-format
msgid ", <xref linkend=\"PostGIS_DropBBox\"/>"
msgstr ""

778
doc/po/pt_BR/reference_lrs.xml.po Normal file
View file

@ -0,0 +1,778 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reference_lrs.xml:3
#, no-c-format
msgid "Linear Referencing"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:7
#, no-c-format
msgid "ST_Line_Interpolate_Point"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:9
#, no-c-format
msgid ""
"Returns a point interpolated along a line. Second argument is a float8 "
"between 0 and 1 representing fraction of total length of linestring the "
"point has to be located."
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:15
#, no-c-format
msgid ""
"<funcdef>geometry <function>ST_Line_Interpolate_Point</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>a_linestring</parameter></"
"paramdef> <paramdef><type>float </type> <parameter>a_fraction</parameter></"
"paramdef>"
msgstr ""
#. Tag: title
#: reference_lrs.xml:24 reference_lrs.xml:85 reference_lrs.xml:136
#: reference_lrs.xml:202 reference_lrs.xml:260 reference_lrs.xml:311
#: reference_lrs.xml:356 reference_lrs.xml:400
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: reference_lrs.xml:26
#, no-c-format
msgid ""
"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 linestring length the point has to be located."
msgstr ""
#. Tag: para
#: reference_lrs.xml:30 reference_lrs.xml:147
#, no-c-format
msgid ""
"See <xref linkend=\"ST_Line_Locate_Point\"/> for computing the line location "
"nearest to a Point."
msgstr ""
#. Tag: para
#: reference_lrs.xml:34
#, no-c-format
msgid ""
"Since release 1.1.1 this function also interpolates M and Z values (when "
"present), while prior releases set them to 0.0."
msgstr ""
#. Tag: para
#: reference_lrs.xml:38
#, no-c-format
msgid "Availability: 0.8.2, Z and M supported added in 1.1.1"
msgstr ""
#. Tag: para
#: reference_lrs.xml:39 reference_lrs.xml:157 reference_lrs.xml:319
#: reference_lrs.xml:362 reference_lrs.xml:406
#, no-c-format
msgid "&Z_support;"
msgstr ""
#. Tag: title
#: reference_lrs.xml:44 reference_lrs.xml:101 reference_lrs.xml:161
#: reference_lrs.xml:225 reference_lrs.xml:276 reference_lrs.xml:323
#: reference_lrs.xml:366 reference_lrs.xml:410
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: para
#: reference_lrs.xml:50
#, no-c-format
msgid "A linestring with the interpolated point at 20% position (0.20)"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:53
#, no-c-format
msgid ""
"--Return point 20% along 2d line\n"
"SELECT ST_AsEWKT(ST_Line_Interpolate_Point(the_line, 0.20))\n"
" FROM (SELECT ST_GeomFromEWKT('LINESTRING(25 50, 100 125, 150 190)') "
"as the_line) As foo;\n"
" st_asewkt\n"
"----------------\n"
" POINT(51.5974135047432 76.5974135047432)"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:54
#, no-c-format
msgid ""
"--Return point mid-way of 3d line\n"
"SELECT ST_AsEWKT(ST_Line_Interpolate_Point(the_line, 0.5))\n"
" FROM (SELECT ST_GeomFromEWKT('LINESTRING(1 2 3, 4 5 6, 6 7 8)') as "
"the_line) As foo;\n"
"\n"
" st_asewkt\n"
"--------------------\n"
" POINT(3.5 4.5 5.5)\n"
"\n"
"\n"
"--find closest point on a line to a point or other geometry\n"
" SELECT ST_AsText(ST_Line_Interpolate_Point(foo.the_line, "
"ST_Line_Locate_Point(foo.the_line, ST_GeomFromText('POINT(4 3)'))))\n"
"FROM (SELECT ST_GeomFromText('LINESTRING(1 2, 4 5, 6 7)') As the_line) As "
"foo;\n"
" st_astext\n"
"----------------\n"
" POINT(3 4)"
msgstr ""
#. Tag: title
#: reference_lrs.xml:59 reference_lrs.xml:108 reference_lrs.xml:175
#: reference_lrs.xml:231 reference_lrs.xml:283 reference_lrs.xml:330
#: reference_lrs.xml:372
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: para
#: reference_lrs.xml:61
#, no-c-format
msgid ""
", <xref linkend=\"ST_AsEWKT\"/>, <xref linkend=\"ST_Length\"/>, <xref "
"linkend=\"ST_Line_Locate_Point\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:67
#, no-c-format
msgid "ST_Line_Locate_Point"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:69
#, no-c-format
msgid ""
"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 2d line "
"length."
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:76
#, no-c-format
msgid ""
"<funcdef>float <function>ST_Line_Locate_Point</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>a_linestring</parameter></"
"paramdef> <paramdef><type>geometry </type> <parameter>a_point</parameter></"
"paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:87
#, no-c-format
msgid ""
"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 <link linkend="
"\"ST_Length2D\">2d line</link> length."
msgstr ""
#. Tag: para
#: reference_lrs.xml:91
#, no-c-format
msgid ""
"You can use the returned location to extract a Point (<xref linkend="
"\"ST_Line_Interpolate_Point\"/>) or a substring (<xref linkend="
"\"ST_Line_Substring\"/>)."
msgstr ""
#. Tag: para
#: reference_lrs.xml:94
#, no-c-format
msgid "This is useful for approximating numbers of addresses"
msgstr ""
#. Tag: para
#: reference_lrs.xml:96
#, no-c-format
msgid "Availability: 1.1.0"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:103
#, no-c-format
msgid ""
"--Rough approximation of finding the street number of a point along the "
"street\n"
"--Note the whole foo thing is just to generate dummy data that looks\n"
"--like house centroids and street\n"
"--We use ST_DWithin to exclude\n"
"--houses too far away from the street to be considered on the street\n"
"SELECT ST_AsText(house_loc) As as_text_house_loc,\n"
" startstreet_num +\n"
" CAST( (endstreet_num - startstreet_num)\n"
" * ST_Line_Locate_Point(street_line, house_loc) As "
"integer) As street_num\n"
"FROM\n"
"(SELECT ST_GeomFromText('LINESTRING(1 2, 3 4)') As street_line,\n"
" ST_MakePoint(x*1.01,y*1.03) As house_loc, 10 As startstreet_num,\n"
" 20 As endstreet_num\n"
"FROM generate_series(1,3) x CROSS JOIN generate_series(2,4) As y)\n"
"As foo\n"
"WHERE ST_DWithin(street_line, house_loc, 0.2);\n"
"\n"
" as_text_house_loc | street_num\n"
"-------------------+------------\n"
" POINT(1.01 2.06) | 10\n"
" POINT(2.02 3.09) | 15\n"
" POINT(3.03 4.12) | 20\n"
"\n"
" --find closest point on a line to a point or other geometry\n"
" SELECT ST_AsText(ST_Line_Interpolate_Point(foo.the_line, "
"ST_Line_Locate_Point(foo.the_line, ST_GeomFromText('POINT(4 3)'))))\n"
"FROM (SELECT ST_GeomFromText('LINESTRING(1 2, 4 5, 6 7)') As the_line) As "
"foo;\n"
" st_astext\n"
"----------------\n"
" POINT(3 4)"
msgstr ""
#. Tag: para
#: reference_lrs.xml:110
#, no-c-format
msgid ""
", <xref linkend=\"ST_Length2D\"/>, <xref linkend=\"ST_Line_Interpolate_Point"
"\"/>, <xref linkend=\"ST_Line_Substring\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:116
#, no-c-format
msgid "ST_Line_Substring"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:118
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:126
#, no-c-format
msgid ""
"<funcdef>geometry <function>ST_Line_Substring</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>a_linestring</parameter></"
"paramdef> <paramdef><type>float </type> <parameter>startfraction</"
"parameter></paramdef> <paramdef><type>float </type> <parameter>endfraction</"
"parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:138
#, no-c-format
msgid ""
"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. This only works with LINESTRINGs. To use with "
"contiguous MULTILINESTRINGs use in conjunction with <xref linkend="
"\"ST_LineMerge\"/>."
msgstr ""
#. Tag: para
#: reference_lrs.xml:144
#, no-c-format
msgid ""
"If 'start' and 'end' have the same value this is equivalent to <xref linkend="
"\"ST_Line_Interpolate_Point\"/>."
msgstr ""
#. Tag: para
#: reference_lrs.xml:151
#, no-c-format
msgid ""
"Since release 1.1.1 this function also interpolates M and Z values (when "
"present), while prior releases set them to unspecified values."
msgstr ""
#. Tag: para
#: reference_lrs.xml:156
#, no-c-format
msgid "Availability: 1.1.0, Z and M supported added in 1.1.1"
msgstr ""
#. Tag: para
#: reference_lrs.xml:167
#, no-c-format
msgid "A linestring seen with 1/3 midrange overlaid (0.333, 0.666)"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:170
#, no-c-format
msgid ""
"--Return the approximate 1/3 mid-range part of a linestring\n"
"SELECT ST_AsText(ST_Line_SubString(ST_GeomFromText('LINESTRING(25 50, 100 "
"125, 150 190)'), 0.333, 0.666));\n"
"\n"
" st_astext\n"
"------------------------------------------------------------------------------------------------\n"
"LINESTRING(69.2846934853974 94.2846934853974,100 125,111.700356260683 "
"140.210463138888)\n"
"\n"
"--The below example simulates a while loop in\n"
"--SQL using PostgreSQL generate_series() to cut all\n"
"--linestrings in a table to 100 unit segments\n"
"-- of which no segment is longer than 100 units\n"
"-- units are measured in the SRID units of measurement\n"
"-- It also assumes all geometries are LINESTRING or contiguous "
"MULTILINESTRING\n"
"--and no geometry is longer than 100 units*10000\n"
"--for better performance you can reduce the 10000\n"
"--to match max number of segments you expect\n"
"\n"
"SELECT field1, field2, ST_Line_Substring(the_geom, 100.00*n/length,\n"
" CASE\n"
" WHEN 100.00*(n+1) &lt; length THEN 100.00*(n+1)/length\n"
" ELSE 1\n"
" END) As the_geom\n"
"FROM\n"
" (SELECT sometable.field1, sometable.field2,\n"
" ST_LineMerge(sometable.the_geom) AS the_geom,\n"
" ST_Length(sometable.the_geom) As length\n"
" FROM sometable\n"
" ) AS t\n"
"CROSS JOIN generate_series(0,10000) AS n\n"
"WHERE n*100.00/length &lt; 1;"
msgstr ""
#. Tag: para
#: reference_lrs.xml:177
#, no-c-format
msgid ""
", <xref linkend=\"ST_Line_Interpolate_Point\"/>, <xref linkend=\"ST_LineMerge"
"\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:183
#, no-c-format
msgid "ST_LocateAlong"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:185
#, no-c-format
msgid ""
"<refpurpose>Return a derived geometry collection value with elements that "
"match the specified measure. Polygonal elements are not supported.</"
"refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:192
#, no-c-format
msgid ""
"<funcdef>geometry <function>ST_LocateAlong</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>ageom_with_measure</parameter></"
"paramdef> <paramdef><type>float </type> <parameter>a_measure</parameter></"
"paramdef> <paramdef choice=\"opt\"><type>float </type> <parameter>offset</"
"parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:204
#, no-c-format
msgid ""
"<para>Return a derived geometry collection value with elements that match "
"the specified measure. Polygonal elements are not supported.</para>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:208
#, no-c-format
msgid ""
"If an offset is provided, the resultant will be offset to the left or right "
"of the input line by the specified number of units. A positive offset will "
"be to the left, and a negative one to the right."
msgstr ""
#. Tag: para
#: reference_lrs.xml:213 reference_lrs.xml:266
#, no-c-format
msgid ""
"Semantic is specified by: ISO/IEC CD 13249-3:200x(E) - Text for Continuation "
"CD Editing Meeting"
msgstr ""
#. Tag: para
#: reference_lrs.xml:216
#, no-c-format
msgid "Availability: 1.1.0 by old name ST_Locate_Along_Measure."
msgstr ""
#. Tag: para
#: reference_lrs.xml:217
#, no-c-format
msgid ""
"Changed: 2.0.0 in prior versions this used to be called "
"ST_Locate_Along_Measure. The old name has been deprecated and will be "
"removed in the future but is still available."
msgstr ""
#. Tag: para
#: reference_lrs.xml:218
#, no-c-format
msgid "Use this function only for geometries with an M component"
msgstr ""
#. Tag: para
#: reference_lrs.xml:220 reference_lrs.xml:272
#, no-c-format
msgid "&M_support;"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:226
#, no-c-format
msgid ""
"SELECT ST_AsText(the_geom)\n"
" FROM\n"
" (SELECT ST_LocateAlong(\n"
" ST_GeomFromText('MULTILINESTRINGM((1 2 3, 3 4 2, 9 4 "
"3),\n"
" (1 2 3, 5 4 5))'),3) As the_geom) As foo;\n"
"\n"
" st_asewkt\n"
"-----------------------------------------------------------\n"
" MULTIPOINT M (1 2 3)\n"
"\n"
"--Geometry collections are difficult animals so dump them\n"
"--to make them more digestable\n"
"SELECT ST_AsText((ST_Dump(the_geom)).geom)\n"
" FROM\n"
" (SELECT ST_LocateAlong(\n"
" ST_GeomFromText('MULTILINESTRINGM((1 2 3, 3 4 2, 9 4 "
"3),\n"
" (1 2 3, 5 4 5))'),3) As the_geom) As foo;\n"
"\n"
" st_asewkt\n"
"---------------\n"
" POINTM(1 2 3)\n"
" POINTM(9 4 3)\n"
" POINTM(1 2 3)"
msgstr ""
#. Tag: para
#: reference_lrs.xml:233
#, no-c-format
msgid ", <xref linkend=\"ST_LocateBetween\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:239
#, no-c-format
msgid "ST_LocateBetween"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:241
#, no-c-format
msgid ""
"<refpurpose>Return a derived geometry collection value with elements that "
"match the specified range of measures inclusively. Polygonal elements are "
"not supported.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:248
#, no-c-format
msgid ""
"<funcdef>geometry <function>ST_LocateBetween</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef> "
"<paramdef><type>float </type> <parameter>measure_start</parameter></"
"paramdef> <paramdef><type>float </type> <parameter>measure_end</parameter></"
"paramdef> <paramdef choice=\"opt\"><type>float </type> <parameter>offset</"
"parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:262
#, no-c-format
msgid ""
"<para>Return a derived geometry collection value with elements that match "
"the specified range of measures inclusively. Polygonal elements are not "
"supported.</para>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:269
#, no-c-format
msgid "Availability: 1.1.0 by old name ST_Locate_Between_Measures."
msgstr ""
#. Tag: para
#: reference_lrs.xml:270
#, no-c-format
msgid ""
"Changed: 2.0.0 - in prior versions this used to be called "
"ST_Locate_Between_Measures. The old name has been deprecated and will be "
"removed in the future but is still available for backward compatibility."
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:278
#, no-c-format
msgid ""
"SELECT ST_AsText(the_geom)\n"
" FROM\n"
" (SELECT ST_LocateBetween(\n"
" ST_GeomFromText('MULTILINESTRING M ((1 2 3, 3 4 2, 9 "
"4 3),\n"
" (1 2 3, 5 4 5))'),1.5, 3) As the_geom) As foo;\n"
"\n"
" st_asewkt\n"
"------------------------------------------------------------------------\n"
" GEOMETRYCOLLECTION M (LINESTRING M (1 2 3,3 4 2,9 4 3),POINT M (1 2 3))\n"
"\n"
"--Geometry collections are difficult animals so dump them\n"
"--to make them more digestable\n"
"SELECT ST_AsText((ST_Dump(the_geom)).geom)\n"
" FROM\n"
" (SELECT ST_LocateBetween(\n"
" ST_GeomFromText('MULTILINESTRING M ((1 2 3, 3 4 2, 9 "
"4 3),\n"
" (1 2 3, 5 4 5))'),1.5, 3) As the_geom) As foo;\n"
"\n"
" st_asewkt\n"
"--------------------------------\n"
" LINESTRING M (1 2 3,3 4 2,9 4 3)\n"
" POINT M (1 2 3)"
msgstr ""
#. Tag: para
#: reference_lrs.xml:285
#, no-c-format
msgid ", <xref linkend=\"ST_LocateAlong\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:291
#, no-c-format
msgid "ST_LocateBetweenElevations"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:293
#, no-c-format
msgid ""
"Return a derived geometry (collection) value with elements that intersect "
"the specified range of elevations inclusively. Only 3D, 4D LINESTRINGS and "
"MULTILINESTRINGS are supported."
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:300
#, no-c-format
msgid ""
"<funcdef>geometry <function>ST_LocateBetweenElevations</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>geom_mline</parameter></"
"paramdef> <paramdef><type>float </type> <parameter>elevation_start</"
"parameter></paramdef> <paramdef><type>float </type> "
"<parameter>elevation_end</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:313
#, no-c-format
msgid ""
"Return a derived geometry (collection) value with elements that intersect "
"the specified range of elevations inclusively. Only 3D, 3DM LINESTRINGS and "
"MULTILINESTRINGS are supported."
msgstr ""
#. Tag: para
#: reference_lrs.xml:317
#, no-c-format
msgid "Availability: 1.4.0"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:325
#, no-c-format
msgid ""
"SELECT ST_AsEWKT(ST_LocateBetweenElevations(\n"
" ST_GeomFromEWKT('LINESTRING(1 2 3, 4 5 6)'),2,4)) As "
"ewelev;\n"
" ewelev\n"
"----------------------------------------------------------------\n"
" MULTILINESTRING((1 2 3,2 3 4))\n"
"\n"
"SELECT ST_AsEWKT(ST_LocateBetweenElevations(\n"
" ST_GeomFromEWKT('LINESTRING(1 2 6, 4 5 -1, 7 8 "
"9)'),6,9)) As ewelev;\n"
"\n"
" ewelev\n"
"----------------------------------------------------------------\n"
"GEOMETRYCOLLECTION(POINT(1 2 6),LINESTRING(6.1 7.1 6,7 8 9))\n"
"\n"
"--Geometry collections are difficult animals so dump them\n"
"--to make them more digestable\n"
"SELECT ST_AsEWKT((ST_Dump(the_geom)).geom)\n"
" FROM\n"
" (SELECT ST_LocateBetweenElevations(\n"
" ST_GeomFromEWKT('LINESTRING(1 2 6, 4 5 -1, 7 8 "
"9)'),6,9) As the_geom) As foo;\n"
"\n"
" st_asewkt\n"
"--------------------------------\n"
"POINT(1 2 6)\n"
"LINESTRING(6.1 7.1 6,7 8 9)"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:339
#, no-c-format
msgid "ST_InterpolatePoint"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:341
#, no-c-format
msgid ""
"<refpurpose>Return the value of the measure dimension of a geometry at the "
"point closed to the provided point.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:346
#, no-c-format
msgid ""
"<funcdef>float <function>ST_InterpolatePoint</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>line</parameter></paramdef> "
"<paramdef><type>geometry </type> <parameter>point</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:358
#, no-c-format
msgid ""
"<para>Return the value of the measure dimension of a geometry at the point "
"closed to the provided point.</para>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:360
#, no-c-format
msgid "Availability: 2.0.0"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:368
#, no-c-format
msgid ""
"SELECT ST_InterpolatePoint('LINESTRING M (0 0 0, 10 0 20)', 'POINT(5 5)');\n"
" st_interpolatepoint \n"
" ---------------------\n"
" 10"
msgstr ""
#. Tag: para
#: reference_lrs.xml:374
#, no-c-format
msgid ""
", <xref linkend=\"ST_LocateAlong\"/>, <xref linkend=\"ST_LocateBetween\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:382
#, no-c-format
msgid "ST_AddMeasure"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:384
#, no-c-format
msgid ""
"<refpurpose>Return a derived geometry with measure elements linearly "
"interpolated between the start and end points. If the geometry has no "
"measure dimension, one is added. If the geometry has a measure dimension, it "
"is over-written with new values. Only LINESTRINGS and MULTILINESTRINGS are "
"supported.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:389
#, no-c-format
msgid ""
"<funcdef>geometry <function>ST_AddMeasure</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>geom_mline</parameter></"
"paramdef> <paramdef><type>float </type> <parameter>measure_start</"
"parameter></paramdef> <paramdef><type>float </type> <parameter>measure_end</"
"parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:402
#, no-c-format
msgid ""
"<para>Return a derived geometry with measure elements linearly interpolated "
"between the start and end points. If the geometry has no measure dimension, "
"one is added. If the geometry has a measure dimension, it is over-written "
"with new values. Only LINESTRINGS and MULTILINESTRINGS are supported.</para>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:404
#, no-c-format
msgid "Availability: 1.5.0"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:412
#, no-c-format
msgid ""
"SELECT ST_AsText(ST_AddMeasure(\n"
"ST_GeomFromEWKT('LINESTRING(1 0, 2 0, 4 0)'),1,4)) As ewelev;\n"
" ewelev \n"
"--------------------------------\n"
" LINESTRINGM(1 0 1,2 0 2,4 0 4)\n"
"\n"
"SELECT ST_AsText(ST_AddMeasure(\n"
"ST_GeomFromEWKT('LINESTRING(1 0 4, 2 0 4, 4 0 4)'),10,40)) As ewelev;\n"
" ewelev \n"
"----------------------------------------\n"
" LINESTRING(1 0 4 10,2 0 4 20,4 0 4 40)\n"
"\n"
"SELECT ST_AsText(ST_AddMeasure(\n"
"ST_GeomFromEWKT('LINESTRINGM(1 0 4, 2 0 4, 4 0 4)'),10,40)) As ewelev;\n"
" ewelev \n"
"----------------------------------------\n"
" LINESTRINGM(1 0 10,2 0 20,4 0 40)\n"
" \n"
"SELECT ST_AsText(ST_AddMeasure(\n"
"ST_GeomFromEWKT('MULTILINESTRINGM((1 0 4, 2 0 4, 4 0 4),(1 0 4, 2 0 4, 4 0 "
"4))'),10,70)) As ewelev;\n"
" ewelev \n"
"-----------------------------------------------------------------\n"
" MULTILINESTRINGM((1 0 10,2 0 20,4 0 40),(1 0 40,2 0 50,4 0 70))"
msgstr ""

1143
doc/po/pt_BR/reference_management.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

4934
doc/po/pt_BR/reference_measure.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

855
doc/po/pt_BR/reference_misc.xml.po Normal file
View file

@ -0,0 +1,855 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reference_misc.xml:3
#, no-c-format
msgid "Miscellaneous Functions"
msgstr ""
#. Tag: refname
#: reference_misc.xml:7
#, no-c-format
msgid "ST_Accum"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:9
#, no-c-format
msgid "<refpurpose>Aggregate. Constructs an array of geometries.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:14
#, no-c-format
msgid ""
"<funcdef>geometry[] <function>ST_Accum</function></funcdef> "
"<paramdef><type>geometry set</type> <parameter>geomfield</parameter></"
"paramdef>"
msgstr ""
#. Tag: title
#: reference_misc.xml:22 reference_misc.xml:64 reference_misc.xml:106
#: reference_misc.xml:158 reference_misc.xml:229 reference_misc.xml:289
#: reference_misc.xml:343 reference_misc.xml:396 reference_misc.xml:438
#: reference_misc.xml:488
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: reference_misc.xml:24
#, no-c-format
msgid "<para>Aggregate. Constructs an array of geometries.</para>"
msgstr ""
#. Tag: para
#: reference_misc.xml:25 reference_misc.xml:68 reference_misc.xml:109
#: reference_misc.xml:255 reference_misc.xml:309 reference_misc.xml:355
#, no-c-format
msgid ""
"Enhanced: 2.0.0 support for Polyhedral surfaces, Triangles and TIN was "
"introduced."
msgstr ""
#. Tag: para
#: reference_misc.xml:26 reference_misc.xml:113 reference_misc.xml:357
#: reference_misc.xml:447
#, no-c-format
msgid "&Z_support;"
msgstr ""
#. Tag: para
#: reference_misc.xml:27 reference_misc.xml:69 reference_misc.xml:110
#: reference_misc.xml:183 reference_misc.xml:358 reference_misc.xml:448
#, no-c-format
msgid "&curve_support;"
msgstr ""
#. Tag: para
#: reference_misc.xml:28 reference_misc.xml:70 reference_misc.xml:111
#: reference_misc.xml:256 reference_misc.xml:310 reference_misc.xml:359
#: reference_misc.xml:449
#, no-c-format
msgid "&P_support;"
msgstr ""
#. Tag: para
#: reference_misc.xml:29 reference_misc.xml:71 reference_misc.xml:112
#: reference_misc.xml:257 reference_misc.xml:311 reference_misc.xml:360
#: reference_misc.xml:450
#, no-c-format
msgid "&T_support;"
msgstr ""
#. Tag: title
#: reference_misc.xml:34 reference_misc.xml:76 reference_misc.xml:118
#: reference_misc.xml:188 reference_misc.xml:262 reference_misc.xml:316
#: reference_misc.xml:364 reference_misc.xml:408 reference_misc.xml:455
#: reference_misc.xml:499
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:36
#, no-c-format
msgid ""
"SELECT (ST_Accum(the_geom)) As all_em, ST_AsText((ST_Accum(the_geom))[1]) As "
"grabone,\n"
"(ST_Accum(the_geom))[2:4] as grab_rest\n"
" FROM (SELECT ST_MakePoint(a*CAST(random()*10 As "
"integer), a*CAST(random()*10 As integer), a*CAST(random()*10 As integer)) As "
"the_geom\n"
" FROM generate_series(1,4) a) As foo;\n"
"\n"
"all_em|grabone | grab_rest\n"
"\n"
"-------------------------------------------------------------------------------"
"+\n"
"\n"
" {0101000080000000000000144000000000000024400000000000001040:\n"
" 0101000080000000000\n"
"00018400000000000002C400000000000003040:\n"
"0101000080000000000000354000000000000038400000000000001840:\n"
"010100008000000000000040400000000000003C400000000000003040} |\n"
" POINT(5 10) | {010100008000000000000018400000000000002C400000000000003040:\n"
" 0101000080000000000000354000000000000038400000000000001840:\n"
" 010100008000000000000040400000000000003C400000000000003040}\n"
"(1 row)"
msgstr ""
#. Tag: title
#: reference_misc.xml:41 reference_misc.xml:83 reference_misc.xml:125
#: reference_misc.xml:195 reference_misc.xml:268 reference_misc.xml:322
#: reference_misc.xml:369 reference_misc.xml:415 reference_misc.xml:462
#: reference_misc.xml:506
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: refname
#: reference_misc.xml:49
#, no-c-format
msgid "Box2D"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:51
#, no-c-format
msgid ""
"<refpurpose>Returns a BOX2D representing the maximum extents of the geometry."
"</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:56
#, no-c-format
msgid ""
"<funcdef>box2d <function>Box2D</function></funcdef> <paramdef><type>geometry "
"</type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:66
#, no-c-format
msgid ""
"<para>Returns a BOX2D representing the maximum extents of the geometry.</"
"para>"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:78
#, no-c-format
msgid ""
"SELECT Box2D(ST_GeomFromText('LINESTRING(1 2, 3 4, 5 6)'));\n"
" box2d\n"
" ---------\n"
" BOX(1 2,5 6)\n"
"\n"
" SELECT Box2D(ST_GeomFromText('CIRCULARSTRING(220268 150415,220227 "
"150505,220227 150406)'));\n"
" box2d\n"
" --------\n"
" BOX(220186.984375 150406,220288.25 150506.140625)"
msgstr ""
#. Tag: para
#: reference_misc.xml:85
#, no-c-format
msgid ", <xref linkend=\"ST_GeomFromText\"/>"
msgstr ""
#. Tag: refname
#: reference_misc.xml:91
#, no-c-format
msgid "Box3D"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:93
#, no-c-format
msgid ""
"<refpurpose>Returns a BOX3D representing the maximum extents of the geometry."
"</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:98
#, no-c-format
msgid ""
"<funcdef>box3d <function>Box3D</function></funcdef> <paramdef><type>geometry "
"</type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:108
#, no-c-format
msgid ""
"<para>Returns a BOX3D representing the maximum extents of the geometry.</"
"para>"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:120
#, no-c-format
msgid ""
"SELECT Box3D(ST_GeomFromEWKT('LINESTRING(1 2 3, 3 4 5, 5 6 5)'));\n"
" Box3d\n"
" ---------\n"
" BOX3D(1 2 3,5 6 5)\n"
"\n"
" SELECT Box3D(ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 "
"150505 1,220227 150406 1)'));\n"
" Box3d\n"
" --------\n"
" BOX3D(220227 150406 1,220268 150415 1)"
msgstr ""
#. Tag: para
#: reference_misc.xml:127
#, no-c-format
msgid ", <xref linkend=\"ST_GeomFromEWKT\"/>"
msgstr ""
#. Tag: refname
#: reference_misc.xml:133
#, no-c-format
msgid "ST_EstimatedExtent"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:135
#, no-c-format
msgid ""
"<refpurpose>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.</refpurpose>"
msgstr ""
#. Tag: funcsynopsis
#: reference_misc.xml:141
#, no-c-format
msgid ""
"<funcprototype> <funcdef>box2d <function>ST_EstimatedExtent</function></"
"funcdef> <paramdef><type>text </type> <parameter>schema_name</parameter></"
"paramdef> <paramdef><type>text </type> <parameter>table_name</parameter></"
"paramdef> <paramdef><type>text </type> <parameter>geocolumn_name</"
"parameter></paramdef> </funcprototype> <funcprototype> <funcdef>box2d "
"<function>ST_EstimatedExtent</function></funcdef> <paramdef><type>text </"
"type> <parameter>table_name</parameter></paramdef> <paramdef><type>text </"
"type> <parameter>geocolumn_name</parameter></paramdef> </funcprototype>"
msgstr ""
#. Tag: para
#: reference_misc.xml:160
#, no-c-format
msgid ""
"<para>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.</para>"
msgstr ""
#. Tag: para
#: reference_misc.xml:164
#, no-c-format
msgid ""
"For PostgreSQL&gt;=8.0.0 statistics are gathered by VACUUM ANALYZE and "
"resulting extent will be about 95% of the real one."
msgstr ""
#. Tag: para
#: reference_misc.xml:169
#, no-c-format
msgid ""
"In absence of statistics (empty table or no ANALYZE called) this function "
"returns NULL. Prior to version 1.5.4 an exception was thrown instead."
msgstr ""
#. Tag: para
#: reference_misc.xml:177
#, no-c-format
msgid ""
"For PostgreSQL&lt;8.0.0 statistics are gathered by update_geometry_stats() "
"and resulting extent will be exact."
msgstr ""
#. Tag: para
#: reference_misc.xml:180
#, no-c-format
msgid "Availability: 1.0.0"
msgstr ""
#. Tag: para
#: reference_misc.xml:181
#, no-c-format
msgid "Changed: 2.1.0. Up to 2.0.x this was called ST_Estimated_Extent."
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:190
#, no-c-format
msgid ""
"SELECT ST_EstimatedExtent('ny', 'edges', 'the_geom');\n"
"--result--\n"
"BOX(-8877653 4912316,-8010225.5 5589284)\n"
"\n"
"SELECT ST_EstimatedExtent('feature_poly', 'the_geom');\n"
"--result--\n"
"BOX(-124.659652709961 24.6830825805664,-67.7798080444336 49.0012092590332)"
msgstr ""
#. Tag: refname
#: reference_misc.xml:202
#, no-c-format
msgid "ST_Expand"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:203
#, no-c-format
msgid ""
"Returns bounding box expanded in all directions from the bounding box of the "
"input geometry. Uses double-precision"
msgstr ""
#. Tag: funcsynopsis
#: reference_misc.xml:207
#, no-c-format
msgid ""
"<funcprototype> <funcdef>geometry <function>ST_Expand</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>g1</parameter></paramdef> "
"<paramdef><type>float</type> <parameter>units_to_expand</parameter></"
"paramdef> </funcprototype> <funcprototype> <funcdef>box2d "
"<function>ST_Expand</function></funcdef> <paramdef><type>box2d </type> "
"<parameter>g1</parameter></paramdef> <paramdef><type>float</type> "
"<parameter>units_to_expand</parameter></paramdef> </funcprototype> "
"<funcprototype> <funcdef>box3d <function>ST_Expand</function></funcdef> "
"<paramdef><type>box3d </type> <parameter>g1</parameter></paramdef> "
"<paramdef><type>float</type> <parameter>units_to_expand</parameter></"
"paramdef> </funcprototype>"
msgstr ""
#. Tag: para
#: reference_misc.xml:231
#, no-c-format
msgid ""
"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. Uses double-precision. Very useful for distance() queries, or "
"bounding box queries to add an index filter to the query."
msgstr ""
#. Tag: para
#: reference_misc.xml:235
#, no-c-format
msgid ""
"There are 3 variants of this. The one that takes a geometry will return a "
"POLYGON geometry representation of the bounding box and is the most commonly "
"used variant."
msgstr ""
#. Tag: para
#: reference_misc.xml:237
#, no-c-format
msgid ""
"ST_Expand is similar in concept to ST_Buffer except while buffer expands the "
"geometry in all directions, ST_Expand expands the bounding box an x,y,z unit "
"amount."
msgstr ""
#. Tag: para
#: reference_misc.xml:239
#, no-c-format
msgid ""
"Units are in the units of the spatial reference system in use denoted by the "
"SRID"
msgstr ""
#. Tag: para
#: reference_misc.xml:242
#, no-c-format
msgid ""
"Pre 1.3, ST_Expand was used in conjunction with distance to do indexable "
"queries. Something of the form <code>the_geom &amp;&amp; ST_Expand('POINT(10 "
"20)', 10) AND ST_Distance(the_geom, 'POINT(10 20)') &lt; 10</code> Post 1.2, "
"this was replaced with the easier ST_DWithin construct."
msgstr ""
#. Tag: para
#: reference_misc.xml:248
#, no-c-format
msgid ""
"Bounding boxes of all geometries are currently 2-d even if they are 3-"
"dimensional geometries."
msgstr ""
#. Tag: para
#: reference_misc.xml:252
#, no-c-format
msgid ""
"Availability: 1.5.0 behavior changed to output double precision instead of "
"float4 coordinates."
msgstr ""
#. Tag: para
#: reference_misc.xml:263
#, no-c-format
msgid ""
"Examples below use US National Atlas Equal Area (SRID=2163) which is a meter "
"projection"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:264
#, no-c-format
msgid ""
"<!-- TODO: fix results of documentation to reflect new behavior -->\n"
"--10 meter expanded box around bbox of a linestring\n"
"SELECT CAST(ST_Expand(ST_GeomFromText('LINESTRING(2312980 110676,2312923 "
"110701,2312892 110714)', 2163),10) As box2d);\n"
" st_expand\n"
"------------------------------------\n"
" BOX(2312882 110666,2312990 110724)\n"
"\n"
"--10 meter expanded 3d box of a 3d box\n"
"SELECT ST_Expand(CAST('BOX3D(778783 2951741 1,794875 2970042.61545891 10)' "
"As box3d),10)\n"
" st_expand\n"
"-----------------------------------------------------\n"
" BOX3D(778773 2951731 -9,794885 2970052.61545891 20)\n"
"\n"
" --10 meter geometry astext rep of a expand box around a point geometry\n"
" SELECT ST_AsEWKT(ST_Expand(ST_GeomFromEWKT('SRID=2163;POINT(2312980 "
"110676)'),10));\n"
" st_asewkt\n"
"-------------------------------------------------------------------------------------------------\n"
" SRID=2163;POLYGON((2312970 110666,2312970 110686,2312990 110686,2312990 "
"110666,2312970 110666))"
msgstr ""
#. Tag: para
#: reference_misc.xml:269
#, no-c-format
msgid ""
", <xref linkend=\"ST_Buffer\"/>, <xref linkend=\"ST_DWithin\"/>, <xref "
"linkend=\"ST_GeomFromEWKT\"/>, <xref linkend=\"ST_GeomFromText\"/>, <xref "
"linkend=\"ST_SRID\"/>"
msgstr ""
#. Tag: refname
#: reference_misc.xml:275
#, no-c-format
msgid "ST_Extent"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:276
#, no-c-format
msgid ""
"an aggregate function that returns the bounding box that bounds rows of "
"geometries."
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:281
#, no-c-format
msgid ""
"<funcdef>box2d <function>ST_Extent</function></funcdef> "
"<paramdef><type>geometry set</type> <parameter>geomfield</parameter></"
"paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:291
#, no-c-format
msgid ""
"ST_Extent returns a bounding box that encloses a set of geometries. The "
"ST_Extent function is an \"aggregate\" function in the terminology of SQL. "
"That means that it operates on lists of data, in the same way the SUM() and "
"AVG() functions do."
msgstr ""
#. Tag: para
#: reference_misc.xml:294 reference_misc.xml:348
#, no-c-format
msgid ""
"Since it returns a bounding box, the spatial Units are in the units of the "
"spatial reference system in use denoted by the SRID"
msgstr ""
#. Tag: para
#: reference_misc.xml:295
#, no-c-format
msgid ""
"ST_Extent is similar in concept to Oracle Spatial/Locator's SDO_AGGR_MBR"
msgstr ""
#. Tag: para
#: reference_misc.xml:297
#, no-c-format
msgid ""
"Since ST_Extent returns a bounding box, the SRID meta-data is lost. Use "
"ST_SetSRID to force it back into a geometry with SRID meta data. The "
"coordinates are in the units of the spatial ref of the orginal geometries."
msgstr ""
#. Tag: para
#: reference_misc.xml:302
#, no-c-format
msgid ""
"ST_Extent will return boxes with only an x and y component even with (x,y,z) "
"coordinate geometries. To maintain x,y,z use ST_3DExtent instead."
msgstr ""
#. Tag: para
#: reference_misc.xml:306
#, no-c-format
msgid "Availability: 1.4.0"
msgstr ""
#. Tag: para
#: reference_misc.xml:317
#, no-c-format
msgid "Examples below use Massachusetts State Plane ft (SRID=2249)"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:318
#, no-c-format
msgid ""
"SELECT ST_Extent(the_geom) as bextent FROM sometable;\n"
" st_bextent\n"
"------------------------------------\n"
"BOX(739651.875 2908247.25,794875.8125 2970042.75)\n"
"\n"
"\n"
"--Return extent of each category of geometries\n"
"SELECT ST_Extent(the_geom) as bextent\n"
"FROM sometable\n"
"GROUP BY category ORDER BY category;\n"
"\n"
" bextent "
"| name\n"
"----------------------------------------------------+----------------\n"
" BOX(778783.5625 2951741.25,794875.8125 2970042.75) | A\n"
" BOX(751315.8125 2919164.75,765202.6875 2935417.25) | B\n"
" BOX(739651.875 2917394.75,756688.375 2935866) | C\n"
"\n"
" --Force back into a geometry\n"
" -- and render the extended text representation of that geometry\n"
"SELECT ST_SetSRID(ST_Extent(the_geom),2249) as bextent FROM sometable;\n"
"\n"
" bextent\n"
"--------------------------------------------------------------------------------\n"
" SRID=2249;POLYGON((739651.875 2908247.25,739651.875 2970042.75,794875.8125 "
"2970042.75,\n"
" 794875.8125 2908247.25,739651.875 2908247.25))"
msgstr ""
#. Tag: para
#: reference_misc.xml:323
#, no-c-format
msgid ""
", <xref linkend=\"ST_3DExtent\"/>, <xref linkend=\"ST_SetSRID\"/>, <xref "
"linkend=\"ST_SRID\"/>"
msgstr ""
#. Tag: refname
#: reference_misc.xml:329
#, no-c-format
msgid "ST_3DExtent"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:330
#, no-c-format
msgid ""
"an aggregate function that returns the box3D bounding box that bounds rows "
"of geometries."
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:335
#, no-c-format
msgid ""
"<funcdef>box3d <function>ST_3DExtent</function></funcdef> "
"<paramdef><type>geometry set</type> <parameter>geomfield</parameter></"
"paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:345
#, no-c-format
msgid ""
"ST_3DExtent returns a box3d (includes Z coordinate) bounding box that "
"encloses a set of geometries. The ST_3DExtent function is an \"aggregate\" "
"function in the terminology of SQL. That means that it operates on lists of "
"data, in the same way the SUM() and AVG() functions do."
msgstr ""
#. Tag: para
#: reference_misc.xml:351
#, no-c-format
msgid ""
"Since ST_3DExtent returns a bounding box, the SRID meta-data is lost. Use "
"ST_SetSRID to force it back into a geometry with SRID meta data. The "
"coordinates are in the units of the spatial ref of the orginal geometries."
msgstr ""
#. Tag: para
#: reference_misc.xml:356
#, no-c-format
msgid "Changed: 2.0.0 In prior versions this used to be called ST_Extent3D"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:365
#, no-c-format
msgid ""
"SELECT ST_3DExtent(foo.the_geom) As b3extent\n"
"FROM (SELECT ST_MakePoint(x,y,z) As the_geom\n"
" FROM generate_series(1,3) As x\n"
" CROSS JOIN generate_series(1,2) As y\n"
" CROSS JOIN generate_series(0,2) As Z) As foo;\n"
" b3extent\n"
"--------------------\n"
" BOX3D(1 1 0,3 2 2)\n"
"\n"
"--Get the extent of various elevated circular strings\n"
"SELECT ST_3DExtent(foo.the_geom) As b3extent\n"
"FROM (SELECT ST_Translate(ST_Force_3DZ(ST_LineToCurve(ST_Buffer(ST_MakePoint"
"(x,y),1))),0,0,z) As the_geom\n"
" FROM generate_series(1,3) As x\n"
" CROSS JOIN generate_series(1,2) As y\n"
" CROSS JOIN generate_series(0,2) As Z) As foo;\n"
"\n"
" b3extent\n"
"--------------------\n"
" BOX3D(1 0 0,4 2 2)"
msgstr ""
#. Tag: para
#: reference_misc.xml:370
#, no-c-format
msgid ", <xref linkend=\"ST_Force_3DZ\"/>"
msgstr ""
#. Tag: refname
#: reference_misc.xml:377
#, no-c-format
msgid "Find_SRID"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:379
#, no-c-format
msgid ""
"The syntax is find_srid(&lt;db/schema&gt;, &lt;table&gt;, &lt;column&gt;) "
"and the function returns the integer SRID of the specified column by "
"searching through the GEOMETRY_COLUMNS table."
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:386
#, no-c-format
msgid ""
"<funcdef>integer <function>Find_SRID</function></funcdef> "
"<paramdef><type>varchar </type> <parameter>a_schema_name</parameter></"
"paramdef> <paramdef><type>varchar </type> <parameter>a_table_name</"
"parameter></paramdef> <paramdef><type>varchar </type> "
"<parameter>a_geomfield_name</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:398
#, no-c-format
msgid ""
"The syntax is find_srid(&lt;db/schema&gt;, &lt;table&gt;, &lt;column&gt;) "
"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."
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:410
#, no-c-format
msgid ""
"SELECT Find_SRID('public', 'tiger_us_state_2007', 'the_geom_4269');\n"
"find_srid\n"
"----------\n"
"4269"
msgstr ""
#. Tag: refname
#: reference_misc.xml:423
#, no-c-format
msgid "ST_Mem_Size"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:425
#, no-c-format
msgid ""
"<refpurpose>Returns the amount of space (in bytes) the geometry takes.</"
"refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:430
#, no-c-format
msgid ""
"<funcdef>integer <function>ST_Mem_Size</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:440
#, no-c-format
msgid "<para>Returns the amount of space (in bytes) the geometry takes.</para>"
msgstr ""
#. Tag: para
#: reference_misc.xml:441
#, no-c-format
msgid ""
"This is a nice compliment to PostgreSQL built in functions pg_size_pretty, "
"pg_relation_size, pg_total_relation_size."
msgstr ""
#. Tag: para
#: reference_misc.xml:442
#, no-c-format
msgid ""
"pg_relation_size which gives the byte size of a table may return byte size "
"lower than ST_Mem_Size. This is because pg_relation_size does not add "
"toasted table contribution and large geometries are stored in TOAST tables."
msgstr ""
#. Tag: para
#: reference_misc.xml:444
#, no-c-format
msgid ""
"pg_total_relation_size - includes, the table, the toasted tables, and the "
"indexes."
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:457
#, no-c-format
msgid ""
"--Return how much byte space Boston takes up in our Mass data set\n"
"SELECT pg_size_pretty(SUM(ST_Mem_Size(the_geom))) as totgeomsum,\n"
"pg_size_pretty(SUM(CASE WHEN town = 'BOSTON' THEN st_mem_size(the_geom) ELSE "
"0 END)) As bossum,\n"
"CAST(SUM(CASE WHEN town = 'BOSTON' THEN st_mem_size(the_geom) ELSE 0 END)"
"*1.00 /\n"
" SUM(st_mem_size(the_geom))*100 As numeric(10,2)) As perbos\n"
"FROM towns;\n"
"\n"
"totgeomsum bossum perbos\n"
"---------- ------ ------\n"
"1522 kB 30 kB 1.99\n"
"\n"
"\n"
"SELECT ST_Mem_Size(ST_GeomFromText('CIRCULARSTRING(220268 150415,220227 "
"150505,220227 150406)'));\n"
"\n"
"---\n"
"73\n"
"\n"
"--What percentage of our table is taken up by just the geometry\n"
"SELECT pg_total_relation_size('public.neighborhoods') As fulltable_size, sum"
"(ST_Mem_Size(the_geom)) As geomsize,\n"
"sum(ST_Mem_Size(the_geom))*1.00/pg_total_relation_size('public."
"neighborhoods')*100 As pergeom\n"
"FROM neighborhoods;\n"
"fulltable_size geomsize pergeom\n"
"------------------------------------------------\n"
"262144 96238 36.71188354492187500000"
msgstr ""
#. Tag: refname
#: reference_misc.xml:470
#, no-c-format
msgid "ST_Point_Inside_Circle"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:472
#, no-c-format
msgid ""
"Is the point geometry insert circle defined by center_x, center_y, radius"
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:477
#, no-c-format
msgid ""
"<funcdef>boolean <function>ST_Point_Inside_Circle</function></funcdef> "
"<paramdef><type>geometry </type> <parameter>a_point</parameter></paramdef> "
"<paramdef><type>float </type> <parameter>center_x</parameter></paramdef> "
"<paramdef><type>float </type> <parameter>center_y</parameter></paramdef> "
"<paramdef><type>float </type> <parameter>radius</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:490
#, no-c-format
msgid ""
"The syntax for this functions is point_inside_circle(&lt;geometry&gt;,&lt;"
"circle_center_x&gt;,&lt;circle_center_y&gt;,&lt;radius&gt;). Returns the "
"true if the geometry is a point and is inside the circle. Returns false "
"otherwise."
msgstr ""
#. Tag: para
#: reference_misc.xml:494
#, no-c-format
msgid "This only works for points as the name suggests"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:501
#, no-c-format
msgid ""
"SELECT ST_Point_Inside_Circle(ST_Point(1,2), 0.5, 2, 3);\n"
" st_point_inside_circle\n"
"------------------------\n"
" t"
msgstr ""

1307
doc/po/pt_BR/reference_operator.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

1846
doc/po/pt_BR/reference_output.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

3813
doc/po/pt_BR/reference_processing.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

12499
doc/po/pt_BR/reference_raster.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

392
doc/po/pt_BR/reference_transaction.xml.po Normal file
View file

@ -0,0 +1,392 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reference_transaction.xml:3
#, no-c-format
msgid "Long Transactions Support"
msgstr ""
#. Tag: para
#: reference_transaction.xml:5
#, no-c-format
msgid ""
"This module and associated pl/pgsql functions have been implemented to "
"provide long locking support required by <ulink url=\"http://www."
"opengeospatial.org/standards/wfs\">Web Feature Service</ulink> specification."
msgstr ""
#. Tag: para
#: reference_transaction.xml:10
#, no-c-format
msgid ""
"Users must use <ulink url=\"http://www.postgresql.org/docs/current/static/"
"transaction-iso.html\">serializable transaction level</ulink> otherwise "
"locking mechanism would break."
msgstr ""
#. Tag: refname
#: reference_transaction.xml:18
#, no-c-format
msgid "AddAuth"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:20
#, no-c-format
msgid ""
"<refpurpose>Add an authorization token to be used in current transaction.</"
"refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_transaction.xml:25
#, no-c-format
msgid ""
"<funcdef>boolean <function>AddAuth</function></funcdef> <paramdef><type>text "
"</type> <parameter>auth_token</parameter></paramdef>"
msgstr ""
#. Tag: title
#: reference_transaction.xml:33 reference_transaction.xml:83
#: reference_transaction.xml:130 reference_transaction.xml:177
#: reference_transaction.xml:241 reference_transaction.xml:284
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: reference_transaction.xml:35
#, no-c-format
msgid ""
"<para>Add an authorization token to be used in current transaction.</para>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:37
#, no-c-format
msgid ""
"Creates/adds to a temp table called temp_lock_have_table the current "
"transaction identifier and authorization token key."
msgstr ""
#. Tag: para
#: reference_transaction.xml:40 reference_transaction.xml:92
#: reference_transaction.xml:138 reference_transaction.xml:185
#: reference_transaction.xml:248 reference_transaction.xml:289
#, no-c-format
msgid "Availability: 1.1.3"
msgstr ""
#. Tag: title
#: reference_transaction.xml:45 reference_transaction.xml:98
#: reference_transaction.xml:144 reference_transaction.xml:191
#: reference_transaction.xml:253 reference_transaction.xml:294
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:47
#, no-c-format
msgid ""
"SELECT LockRow('towns', '353', 'priscilla');\n"
" BEGIN TRANSACTION;\n"
" SELECT AddAuth('joey');\n"
" UPDATE towns SET the_geom = ST_Translate"
"(the_geom,2,2) WHERE gid = 353;\n"
" COMMIT;\n"
"\n"
"\n"
" ---Error--\n"
" ERROR: UPDATE where \"gid\" = '353' requires authorization "
"'priscilla'"
msgstr ""
#. Tag: title
#: reference_transaction.xml:52 reference_transaction.xml:105
#: reference_transaction.xml:151 reference_transaction.xml:198
#: reference_transaction.xml:260 reference_transaction.xml:301
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: refname
#: reference_transaction.xml:60
#, no-c-format
msgid "CheckAuth"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:62
#, no-c-format
msgid ""
"Creates trigger on a table to prevent/allow updates and deletes of rows "
"based on authorization token."
msgstr ""
#. Tag: funcsynopsis
#: reference_transaction.xml:66
#, no-c-format
msgid ""
"<funcprototype> <funcdef>integer <function>CheckAuth</function></funcdef> "
"<paramdef><type>text </type> <parameter>a_schema_name</parameter></paramdef> "
"<paramdef><type>text </type> <parameter>a_table_name</parameter></paramdef> "
"<paramdef><type>text </type> <parameter>a_key_column_name</parameter></"
"paramdef> </funcprototype> <funcprototype> <funcdef>integer "
"<function>CheckAuth</function></funcdef> <paramdef><type>text </type> "
"<parameter>a_table_name</parameter></paramdef> <paramdef><type>text </type> "
"<parameter>a_key_column_name</parameter></paramdef> </funcprototype>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:85
#, no-c-format
msgid ""
"Creates trigger on a table to prevent/allow updates and deletes of rows "
"based on authorization token. Identify rows using &lt;rowid_col&gt; column."
msgstr ""
#. Tag: para
#: reference_transaction.xml:87
#, no-c-format
msgid ""
"If a_schema_name is not passed in, then searches for table in current schema."
msgstr ""
#. Tag: para
#: reference_transaction.xml:88
#, no-c-format
msgid ""
"If an authorization trigger already exists on this table function errors."
msgstr ""
#. Tag: para
#: reference_transaction.xml:89
#, no-c-format
msgid "If Transaction support is not enabled, function throws an exception."
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:100
#, no-c-format
msgid ""
"SELECT CheckAuth('public', 'towns', 'gid');\n"
" result\n"
" ------\n"
" 0"
msgstr ""
#. Tag: refname
#: reference_transaction.xml:113
#, no-c-format
msgid "DisableLongTransactions"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:115
#, no-c-format
msgid ""
"<refpurpose>Disable long transaction support. This function removes the long "
"transaction support metadata tables, and drops all triggers attached to lock-"
"checked tables.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_transaction.xml:122
#, no-c-format
msgid ""
"<funcdef>text <function>DisableLongTransactions</function></funcdef> "
"<paramdef></paramdef>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:132
#, no-c-format
msgid ""
"<para>Disable long transaction support. This function removes the long "
"transaction support metadata tables, and drops all triggers attached to lock-"
"checked tables.</para>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:135
#, no-c-format
msgid ""
"Drops meta table called <varname>authorization_table</varname> and a view "
"called <varname>authorized_tables</varname> and all triggers called "
"<varname>checkauthtrigger</varname>"
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:146
#, no-c-format
msgid ""
"SELECT DisableLongTransactions();\n"
"--result--\n"
"Long transactions support disabled"
msgstr ""
#. Tag: refname
#: reference_transaction.xml:159
#, no-c-format
msgid "EnableLongTransactions"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:161
#, no-c-format
msgid ""
"<refpurpose>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.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_transaction.xml:169
#, no-c-format
msgid ""
"<funcdef>text <function>EnableLongTransactions</function></funcdef> "
"<paramdef></paramdef>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:179
#, no-c-format
msgid ""
"<para>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.</para>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:183
#, no-c-format
msgid ""
"Creates a meta table called <varname>authorization_table</varname> and a "
"view called <varname>authorized_tables</varname>"
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:193
#, no-c-format
msgid ""
"SELECT EnableLongTransactions();\n"
"--result--\n"
"Long transactions support enabled"
msgstr ""
#. Tag: refname
#: reference_transaction.xml:206
#, no-c-format
msgid "LockRow"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:208
#, no-c-format
msgid "Set lock/authorization for specific row in table"
msgstr ""
#. Tag: funcsynopsis
#: reference_transaction.xml:212
#, no-c-format
msgid ""
"<funcprototype> <funcdef>integer <function>LockRow</function></funcdef> "
"<paramdef><type>text </type> <parameter>a_schema_name</parameter></paramdef> "
"<paramdef><type>text </type> <parameter>a_table_name</parameter></paramdef> "
"<paramdef><type>text </type> <parameter>a_row_key</parameter></paramdef> "
"<paramdef><type>text</type> <parameter>an_auth_token</parameter></paramdef> "
"<paramdef><type>timestamp</type> <parameter>expire_dt</parameter></paramdef> "
"</funcprototype> <funcprototype> <funcdef>integer <function>LockRow</"
"function></funcdef> <paramdef><type>text </type> <parameter>a_table_name</"
"parameter></paramdef> <paramdef><type>text </type> <parameter>a_row_key</"
"parameter></paramdef> <paramdef><type>text</type> <parameter>an_auth_token</"
"parameter></paramdef> <paramdef><type>timestamp</type> <parameter>expire_dt</"
"parameter></paramdef> </funcprototype> <funcprototype> <funcdef>integer "
"<function>LockRow</function></funcdef> <paramdef><type>text </type> "
"<parameter>a_table_name</parameter></paramdef> <paramdef><type>text </type> "
"<parameter>a_row_key</parameter></paramdef> <paramdef><type>text</type> "
"<parameter>an_auth_token</parameter></paramdef> </funcprototype>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:243
#, no-c-format
msgid ""
"Set lock/authorization for specific row in table &lt;authid&gt; is a text "
"value, &lt;expires&gt; is a timestamp defaulting to now()+1hour. Returns 1 "
"if lock has been assigned, 0 otherwise (already locked by other auth)"
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:255
#, no-c-format
msgid ""
"SELECT LockRow('public', 'towns', '2', 'joey');\n"
"LockRow\n"
"-------\n"
"1\n"
"\n"
"--Joey has already locked the record and Priscilla is out of luck\n"
"SELECT LockRow('public', 'towns', '2', 'priscilla');\n"
"LockRow\n"
"-------\n"
"0"
msgstr ""
#. Tag: refname
#: reference_transaction.xml:268
#, no-c-format
msgid "UnlockRows"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:270
#, no-c-format
msgid ""
"<refpurpose>Remove all locks held by specified authorization id. Returns the "
"number of locks released.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_transaction.xml:276
#, no-c-format
msgid ""
"<funcdef>integer <function>UnlockRows</function></funcdef> "
"<paramdef><type>text </type> <parameter>auth_token</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:286
#, no-c-format
msgid ""
"<para>Remove all locks held by specified authorization id. Returns the "
"number of locks released.</para>"
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:296
#, no-c-format
msgid ""
"SELECT LockRow('towns', '353', 'priscilla');\n"
" SELECT LockRow('towns', '2', 'priscilla');\n"
" SELECT UnLockRows('priscilla');\n"
" UnLockRows\n"
" ------------\n"
" 2"
msgstr ""

277
doc/po/pt_BR/reference_type.xml.po Normal file
View file

@ -0,0 +1,277 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 21:04+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: para
#: reference_type.xml:5
#, no-c-format
msgid ""
"This section lists the PostgreSQL data types installed by PostGIS. Note we "
"describe the casting behavior of these which is very important especially "
"when designing your own functions."
msgstr ""
#. Tag: para
#: reference_type.xml:8
#, no-c-format
msgid ""
"A Cast is when one type is coerced into another type. PostgreSQL is unique "
"from most databases in that it allows you to define casting behavior for "
"custom types and the functions used for casting. A cast can be specified as "
"automatic in which case, you do not have to do a CAST(myfoo As otherfootype) "
"or myfoo::otherfootype if you are feeding it to a function that only works "
"with otherfootype and there is an automatic cast in place for it."
msgstr ""
#. Tag: para
#: reference_type.xml:13
#, no-c-format
msgid ""
"The danger of relying on automatic cast behavior is when you have an "
"overloaded function say one that takes a box2d and one that takes a box3d "
"but no geometry. What happens is that both functions are equally good to use "
"with geometry since geometry has an autocast for both -- so you end up with "
"an ambiguous function error. To force PostgreSQL to choose, you do a CAST"
"(mygeom As box3d) or mygeom::box3d."
msgstr ""
#. Tag: para
#: reference_type.xml:17
#, no-c-format
msgid ""
"<emphasis>At least as of PostgreSQL 8.3</emphasis> - Everything can be CAST "
"to text (presumably because of the magical unknown type), so no defined "
"CASTS for that need to be present for you to CAST an object to text."
msgstr ""
#. Tag: title
#: reference_type.xml:20
#, no-c-format
msgid "PostgreSQL PostGIS Geometry/Geography/Box Types"
msgstr ""
#. Tag: refname
#: reference_type.xml:24
#, no-c-format
msgid "<refname>box2d</refname>"
msgstr ""
#. Tag: refpurpose
#: reference_type.xml:25
#, no-c-format
msgid ""
"A box composed of x min, ymin, xmax, ymax. Often used to return the 2d "
"enclosing box of a geometry."
msgstr ""
#. Tag: title
#: reference_type.xml:29 reference_type.xml:40 reference_type.xml:79
#: reference_type.xml:136 reference_type.xml:155
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: reference_type.xml:30
#, no-c-format
msgid ""
"box2d is a spatial data type used to represent the enclosing box of a "
"geometry or set of geometries. ST_Extent in earlier versions prior to "
"PostGIS 1.4 would return a box2d."
msgstr ""
#. Tag: refname
#: reference_type.xml:35
#, no-c-format
msgid "<refname>box3d</refname>"
msgstr ""
#. Tag: refpurpose
#: reference_type.xml:36
#, no-c-format
msgid ""
"A box composed of x min, ymin, zmin, xmax, ymax, zmax. Often used to return "
"the 3d extent of a geometry or collection of geometries."
msgstr ""
#. Tag: para
#: reference_type.xml:41
#, no-c-format
msgid ""
"box3d is a postgis spatial data type used to represent the enclosing box of "
"a geometry or set of geometries. ST_3DExtent returns a box3d object."
msgstr ""
#. Tag: title
#: reference_type.xml:45 reference_type.xml:84 reference_type.xml:160
#, no-c-format
msgid "Casting Behavior"
msgstr ""
#. Tag: para
#: reference_type.xml:46 reference_type.xml:85 reference_type.xml:161
#, no-c-format
msgid ""
"This section lists the automatic as well as explicit casts allowed for this "
"data type"
msgstr ""
#. Tag: entry
#: reference_type.xml:51 reference_type.xml:90 reference_type.xml:166
#, no-c-format
msgid "Cast To"
msgstr ""
#. Tag: entry
#: reference_type.xml:52 reference_type.xml:91 reference_type.xml:167
#, no-c-format
msgid "Behavior"
msgstr ""
#. Tag: entry
#: reference_type.xml:55 reference_type.xml:94
#, no-c-format
msgid "<entry>box</entry>"
msgstr ""
#. Tag: entry
#: reference_type.xml:56 reference_type.xml:60 reference_type.xml:64
#: reference_type.xml:95 reference_type.xml:99 reference_type.xml:103
#: reference_type.xml:107 reference_type.xml:111 reference_type.xml:115
#, no-c-format
msgid "automatic"
msgstr ""
#. Tag: entry
#: reference_type.xml:59 reference_type.xml:98
#, no-c-format
msgid "<entry>box2d</entry>"
msgstr ""
#. Tag: entry
#: reference_type.xml:63 reference_type.xml:170
#, no-c-format
msgid "<entry>geometry</entry>"
msgstr ""
#. Tag: refname
#: reference_type.xml:74
#, no-c-format
msgid "<refname>geometry</refname>"
msgstr ""
#. Tag: refpurpose
#: reference_type.xml:75
#, no-c-format
msgid "Planar spatial data type."
msgstr ""
#. Tag: para
#: reference_type.xml:80
#, no-c-format
msgid ""
"geometry is a fundamental postgis spatial data type used to represent a "
"feature in the Euclidean coordinate system."
msgstr ""
#. Tag: entry
#: reference_type.xml:102
#, no-c-format
msgid "<entry>box3d</entry>"
msgstr ""
#. Tag: entry
#: reference_type.xml:106
#, no-c-format
msgid "bytea"
msgstr ""
#. Tag: entry
#: reference_type.xml:110
#, no-c-format
msgid "<entry>geography</entry>"
msgstr ""
#. Tag: entry
#: reference_type.xml:114
#, no-c-format
msgid "text"
msgstr ""
#. Tag: title
#: reference_type.xml:123 reference_type.xml:143 reference_type.xml:179
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: refname
#: reference_type.xml:130
#, no-c-format
msgid "geometry_dump"
msgstr ""
#. Tag: refpurpose
#: reference_type.xml:131
#, no-c-format
msgid ""
"A spatial datatype with two fields - geom (holding a geometry object) and "
"path[] (a 1-d array holding the position of the geometry within the dumped "
"object.)"
msgstr ""
#. Tag: para
#: reference_type.xml:137
#, no-c-format
msgid ""
"geometry_dump is a compound data type consisting of a geometry object "
"referenced by the .geom field and path[] a 1-dimensional integer array "
"(starting at 1 e.g. path[1] to get first element) array that defines the "
"navigation path within the dumped geometry to find this element. It is used "
"by the ST_Dump* family of functions as an output type to explode a more "
"complex geometry into its constituent parts and location of parts."
msgstr ""
#. Tag: refname
#: reference_type.xml:150
#, no-c-format
msgid "<refname>geography</refname>"
msgstr ""
#. Tag: refpurpose
#: reference_type.xml:151
#, no-c-format
msgid "Ellipsoidal spatial data type."
msgstr ""
#. Tag: para
#: reference_type.xml:156
#, no-c-format
msgid ""
"geography is a spatial data type used to represent a feature in the round-"
"earth coordinate system."
msgstr ""
#. Tag: entry
#: reference_type.xml:171
#, no-c-format
msgid "explicit"
msgstr ""
#. Tag: para
#: reference_type.xml:180
#, no-c-format
msgid ", <xref linkend=\"PostGIS_Geography\"/>"
msgstr ""

4422
doc/po/pt_BR/release_notes.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

170
doc/po/pt_BR/reporting.xml.po Normal file
View file

@ -0,0 +1,170 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reporting.xml:3
#, no-c-format
msgid "Reporting Problems"
msgstr ""
#. Tag: title
#: reporting.xml:6
#, no-c-format
msgid "Reporting Software Bugs"
msgstr ""
#. Tag: para
#: reporting.xml:8
#, no-c-format
msgid ""
"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 <code>SELECT postgis_full_version()</code> "
"[for postgis] and <code>SELECT version()</code> [for postgresql]."
msgstr ""
#. Tag: para
#: reporting.xml:16
#, no-c-format
msgid ""
"If you aren't using the latest release, it's worth taking a look at its "
"<ulink url=\"http://svn.osgeo.org/postgis/trunk/NEWS\">release changelog</"
"ulink> first, to find out if your bug has already been fixed."
msgstr ""
#. Tag: para
#: reporting.xml:21
#, no-c-format
msgid ""
"Using the <ulink url=\"http://trac.osgeo.org/postgis/\">PostGIS bug tracker</"
"ulink> will ensure your reports are not discarded, and will keep you "
"informed on its 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."
msgstr ""
#. Tag: para
#: reporting.xml:28
#, no-c-format
msgid ""
"You might want to read Simon Tatham's paper about <ulink url=\"http://www."
"chiark.greenend.org.uk/~sgtatham/bugs.html\">How to Report Bugs Effectively</"
"ulink> before filing a new report."
msgstr ""
#. Tag: title
#: reporting.xml:34
#, no-c-format
msgid "Reporting Documentation Issues"
msgstr ""
#. Tag: para
#: reporting.xml:36
#, no-c-format
msgid ""
"The documentation should accurately reflect the features and behavior of the "
"software. If it doesn't, it could be because of a software bug or because "
"the documentation is in error or deficient."
msgstr ""
#. Tag: para
#: reporting.xml:40
#, no-c-format
msgid ""
"Documentation issues can also be reported to the <ulink url=\"http://trac."
"osgeo.org/postgis\">PostGIS bug tracker</ulink>."
msgstr ""
#. Tag: para
#: reporting.xml:44
#, no-c-format
msgid ""
"If your revision is trivial, just describe it in a new bug tracker issue, "
"being specific about its location in the documentation."
msgstr ""
#. Tag: para
#: reporting.xml:47
#, no-c-format
msgid ""
"If your changes are more extensive, a Subversion patch is definitely "
"preferred. This is a four step process on Unix (assuming you already have "
"<ulink url=\"http://subversion.apache.org/\">Subversion</ulink> installed):"
msgstr ""
#. Tag: para
#: reporting.xml:54
#, no-c-format
msgid "Check out a copy of PostGIS' Subversion trunk. On Unix, type:"
msgstr ""
#. Tag: command
#: reporting.xml:57
#, no-c-format
msgid "svn checkout http://svn.osgeo.org/postgis/trunk/"
msgstr ""
#. Tag: para
#: reporting.xml:60
#, no-c-format
msgid "This will be stored in the directory ./trunk"
msgstr ""
#. Tag: para
#: reporting.xml:64
#, no-c-format
msgid ""
"Make your changes to the documentation with your favorite text editor. On "
"Unix, type (for example):"
msgstr ""
#. Tag: command
#: reporting.xml:67
#, no-c-format
msgid "vim trunk/doc/postgis.xml"
msgstr ""
#. Tag: para
#: reporting.xml:69
#, no-c-format
msgid ""
"Note that the documentation is written in DocBook XML rather than HTML, so "
"if you are not familiar with it please follow the example of the rest of the "
"documentation."
msgstr ""
#. Tag: para
#: reporting.xml:75
#, no-c-format
msgid ""
"Make a patch file containing the differences from the master copy of the "
"documentation. On Unix, type:"
msgstr ""
#. Tag: command
#: reporting.xml:78
#, no-c-format
msgid "svn diff trunk/doc/postgis.xml &gt; doc.patch"
msgstr ""
#. Tag: para
#: reporting.xml:83
#, no-c-format
msgid "Attach the patch to a new issue in bug tracker."
msgstr ""

797
doc/po/pt_BR/using_postgis_app.xml.po Normal file
View file

@ -0,0 +1,797 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: using_postgis_app.xml:3
#, no-c-format
msgid "Using PostGIS Geometry: Building Applications"
msgstr ""
#. Tag: title
#: using_postgis_app.xml:5
#, no-c-format
msgid "Using MapServer"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:7
#, no-c-format
msgid ""
"The Minnesota MapServer is an internet web-mapping server which conforms to "
"the OpenGIS Web Mapping Server specification."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:12
#, no-c-format
msgid ""
"The MapServer homepage is at <ulink url=\"http://mapserver.org\">http://"
"mapserver.org</ulink>."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:17
#, no-c-format
msgid ""
"The OpenGIS Web Map Specification is at <ulink url=\"http://www."
"opengeospatial.org/standards/wms\">http://www.opengeospatial.org/standards/"
"wms</ulink>."
msgstr ""
#. Tag: title
#: using_postgis_app.xml:23
#, no-c-format
msgid "Basic Usage"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:25
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:30
#, no-c-format
msgid "To use PostGIS with MapServer, you will need:"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:34
#, no-c-format
msgid "Version 0.6 or newer of PostGIS."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:38
#, no-c-format
msgid "Version 3.5 or newer of MapServer."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:42
#, no-c-format
msgid ""
"MapServer accesses PostGIS/PostgreSQL data like any other PostgreSQL client "
"-- using the <filename>libpq</filename> interface. This means that MapServer "
"can be installed on any machine with network access to the PostGIS server, "
"and use PostGIS as a source of data. The faster the connection between the "
"systems, the better."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:50
#, no-c-format
msgid ""
"Compile and install MapServer, with whatever options you desire, including "
"the \"--with-postgis\" configuration option."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:55
#, no-c-format
msgid "In your MapServer map file, add a PostGIS layer. For example:"
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:58
#, no-c-format
msgid ""
"LAYER \n"
" CONNECTIONTYPE postgis \n"
" NAME \"widehighways\" \n"
" # Connect to a remote spatial database\n"
" CONNECTION \"user=dbuser dbname=gisdatabase host=bigserver\"\n"
" PROCESSING \"CLOSE_CONNECTION=DEFER\"\n"
" # Get the lines from the 'geom' column of the 'roads' table \n"
" DATA \"geom from roads using srid=4326 using unique gid\" \n"
" STATUS ON\n"
" TYPE LINE \n"
" # Of the lines in the extents, only render the wide highways \n"
" FILTER \"type = 'highway' and numlanes &gt;= 4\" \n"
" CLASS \n"
" # Make the superhighways brighter and 2 pixels wide\n"
" EXPRESSION ([numlanes] &gt;= 6) \n"
" STYLE\n"
" COLOR 255 22 22 \n"
" WIDTH 2 \n"
" END\n"
" END \n"
" CLASS \n"
" # All the rest are darker and only 1 pixel wide \n"
" EXPRESSION ([numlanes] &lt; 6) \n"
" STYLE\n"
" COLOR 205 92 82\n"
" END\n"
" END \n"
"END"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:60
#, no-c-format
msgid "In the example above, the PostGIS-specific directives are as follows:"
msgstr ""
#. Tag: term
#: using_postgis_app.xml:65
#, no-c-format
msgid "CONNECTIONTYPE"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:68
#, no-c-format
msgid "For PostGIS layers, this is always \"postgis\"."
msgstr ""
#. Tag: term
#: using_postgis_app.xml:73
#, no-c-format
msgid "CONNECTION"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:76
#, no-c-format
msgid ""
"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 &lt;"
"&gt;):"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:80
#, no-c-format
msgid ""
"user=&lt;username&gt; password=&lt;password&gt; dbname=&lt;username&gt; "
"hostname=&lt;server&gt; port=&lt;5432&gt;"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:84
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: term
#: using_postgis_app.xml:92
#, no-c-format
msgid "DATA"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:95
#, no-c-format
msgid ""
"The form of this parameter is \"&lt;geocolumn&gt; from &lt;tablename&gt; "
"using srid=&lt;srid&gt; using unique &lt;primary key&gt;\" where the column "
"is the spatial column to be rendered to the map, the SRID is SRID used by "
"the column and the primary key is the table primary key (or any other "
"uniquely-valued column with an index)."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:99
#, no-c-format
msgid ""
"You can omit the \"using srid\" and \"using unique\" clauses and MapServer "
"will automatically determine the correct values if possible, but at the cost "
"of running a few extra queries on the server for each map draw."
msgstr ""
#. Tag: term
#: using_postgis_app.xml:106
#, no-c-format
msgid "PROCESSING"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:109
#, no-c-format
msgid ""
"Putting in a CLOSE_CONNECTION=DEFER if you have multiple layers reuses "
"existing connections instead of closing them. This improves speed. Refer to "
"for <ulink url=\"http://blog.cleverelephant.ca/2008/10/mapserverpostgis-"
"performance-tips.html\">MapServer PostGIS Performance Tips</ulink> for a "
"more detailed explanation."
msgstr ""
#. Tag: term
#: using_postgis_app.xml:115
#, no-c-format
msgid "FILTER"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:118
#, no-c-format
msgid ""
"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 &gt;= 6\"."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:128
#, no-c-format
msgid ""
"In your spatial database, ensure you have spatial (GiST) indexes built for "
"any the layers you will be drawing."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:131
#, no-c-format
msgid ""
"CREATE INDEX [indexname] ON [tablename] USING GIST ( [geometrycolumn] );"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:135
#, no-c-format
msgid ""
"If you will be querying your layers using MapServer you will also need to "
"use the \"using unique\" clause in your DATA statement."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:138
#, no-c-format
msgid ""
"MapServer requires unique identifiers for each spatial record when doing "
"queries, and the PostGIS module of MapServer uses the unique value you "
"specify in order to provide these unique identifiers. Using the table "
"primary key is the best practice."
msgstr ""
#. Tag: title
#: using_postgis_app.xml:147
#, no-c-format
msgid "Frequently Asked Questions"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:152
#, no-c-format
msgid ""
"When I use an <varname>EXPRESSION</varname> in my map file, the condition "
"never returns as true, even though I know the values exist in my table."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:158
#, no-c-format
msgid ""
"Unlike shape files, PostGIS field names have to be referenced in EXPRESSIONS "
"using <emphasis>lower case</emphasis>."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:162
#, no-c-format
msgid "EXPRESSION ([numlanes] &gt;= 6)"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:168
#, no-c-format
msgid ""
"The FILTER I use for my Shape files is not working for my PostGIS table of "
"the same data."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:173
#, no-c-format
msgid ""
"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)."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:177
#, no-c-format
msgid "FILTER \"type = 'highway' and numlanes &gt;= 4\""
msgstr ""
#. Tag: para
#: using_postgis_app.xml:183
#, no-c-format
msgid ""
"My PostGIS layer draws much slower than my Shape file layer, is this normal?"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:188
#, no-c-format
msgid ""
"In general, the more features you are drawing into a given map, the more "
"likely it is that PostGIS will be slower than Shape files. For maps with "
"relatively few features (100s), PostGIS will often be faster. For maps with "
"high feature density (1000s), PostGIS will always be slower."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:194
#, no-c-format
msgid ""
"If you are finding substantial draw performance problems, it is possible "
"that you have not built a spatial index on your table."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:198
#, no-c-format
msgid ""
"postgis# CREATE INDEX geotable_gix ON geotable USING GIST ( geocolumn ); \n"
"postgis# VACUUM ANALYZE;"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:204
#, no-c-format
msgid ""
"My PostGIS layer draws fine, but queries are really slow. What is wrong?"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:209
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:213
#, no-c-format
msgid ""
"You can specify what unique key for mapserver to use with the <varname>USING "
"UNIQUE</varname> clause in your <varname>DATA</varname> line:"
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:217
#, no-c-format
msgid "DATA \"geom FROM geotable USING UNIQUE gid\""
msgstr ""
#. Tag: para
#: using_postgis_app.xml:224
#, no-c-format
msgid ""
"Can I use \"geography\" columns (new in PostGIS 1.5) as a source for "
"MapServer layers?"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:229
#, no-c-format
msgid ""
"Yes! MapServer understands geography columns as being the same as geometry "
"columns, but always using an SRID of 4326. Just make sure to include a "
"\"using srid=4326\" clause in your <varname>DATA</varname> statement. "
"Everything else works exactly the same as with geometry."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:234
#, no-c-format
msgid "DATA \"geog FROM geogtable USING SRID=4326 USING UNIQUE gid\""
msgstr ""
#. Tag: title
#: using_postgis_app.xml:244
#, no-c-format
msgid "Advanced Usage"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:246
#, no-c-format
msgid ""
"The <varname>USING</varname> 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 <varname>DATA</"
"varname> definition) it is more difficult for mapserver to automatically "
"determine a unique identifier for each row and also the SRID for the table. "
"The <varname>USING</varname> clause can provide mapserver with these two "
"pieces of information as follows:"
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:255
#, no-c-format
msgid ""
"DATA \"geom FROM (\n"
" SELECT \n"
" table1.geom AS geom, \n"
" table1.gid AS gid, \n"
" table2.data AS data \n"
" FROM table1 \n"
" LEFT JOIN table2 \n"
" ON table1.id = table2.id\n"
") AS new_table USING UNIQUE gid USING SRID=4326\""
msgstr ""
#. Tag: term
#: using_postgis_app.xml:259
#, no-c-format
msgid "USING UNIQUE &lt;uniqueid&gt;"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:262
#, no-c-format
msgid ""
"MapServer requires a unique id for each row in order to identify the row "
"when doing map queries. Normally it identifies the primary key from the "
"system tables. However, views and subselects don't automatically have an "
"known unique column. If you want to use MapServer's query functionality, you "
"need to ensure your view or subselect includes a uniquely valued column, and "
"declare it with <varname>USING UNIQUE</varname>. For example, you could "
"explicitly select nee of the table's primary key values for this purpose, or "
"any other column which is guaranteed to be unique for the result set."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:273
#, no-c-format
msgid ""
"\"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 <varname>DATA</varname> definition."
msgstr ""
#. Tag: term
#: using_postgis_app.xml:282
#, no-c-format
msgid "USING SRID=&lt;srid&gt;"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:285
#, no-c-format
msgid ""
"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 <varname>USING "
"SRID=</varname> option allows the correct SRID to be specified in the "
"<varname>DATA</varname> definition."
msgstr ""
#. Tag: title
#: using_postgis_app.xml:300
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:302
#, no-c-format
msgid ""
"Lets start with a simple example and work our way up. Consider the following "
"MapServer layer definition:"
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:305
#, no-c-format
msgid ""
"LAYER \n"
" CONNECTIONTYPE postgis \n"
" NAME \"roads\"\n"
" CONNECTION \"user=theuser password=thepass dbname=thedb host=theserver\" \n"
" DATA \"geom from roads\" \n"
" STATUS ON \n"
" TYPE LINE \n"
" CLASS \n"
" STYLE\n"
" COLOR 0 0 0 \n"
" END\n"
" END \n"
"END"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:307
#, no-c-format
msgid ""
"This layer will display all the road geometries in the roads table as black "
"lines."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:310
#, no-c-format
msgid ""
"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:"
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:314
#, no-c-format
msgid ""
"LAYER \n"
" CONNECTIONTYPE postgis \n"
" CONNECTION \"user=theuser password=thepass dbname=thedb host=theserver\" \n"
" PROCESSING \"CLOSE_CONNECTION=DEFER\"\n"
" DATA \"geom from roads\"\n"
" MINSCALE 100000 \n"
" STATUS ON \n"
" TYPE LINE \n"
" FILTER \"road_type = 'highway'\" \n"
" CLASS \n"
" COLOR 0 0 0 \n"
" END \n"
"END \n"
"LAYER \n"
" CONNECTIONTYPE postgis \n"
" CONNECTION \"user=theuser password=thepass dbname=thedb host=theserver\"\n"
" PROCESSING \"CLOSE_CONNECTION=DEFER\"\n"
" DATA \"geom from roads\" \n"
" MAXSCALE 100000 \n"
" STATUS ON \n"
" TYPE LINE\n"
" CLASSITEM road_type \n"
" CLASS \n"
" EXPRESSION \"highway\" \n"
" STYLE\n"
" WIDTH 2 \n"
" COLOR 255 0 0 \n"
" END\n"
" END \n"
" CLASS \n"
" STYLE\n"
" COLOR 0 0 0 \n"
" END\n"
" END \n"
"END"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:316
#, no-c-format
msgid ""
"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 "
"<varname>FILTER</varname> option causes only roads of type \"highway\" to be "
"displayed."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:321
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:325
#, no-c-format
msgid ""
"So, we have done a couple of interesting things using only MapServer "
"functionality, but our <varname>DATA</varname> 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."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:331
#, no-c-format
msgid ""
"LAYER \n"
" CONNECTIONTYPE postgis\n"
" CONNECTION \"user=theuser password=thepass dbname=thedb host=theserver\" \n"
" DATA \"geom FROM (SELECT roads.gid AS gid, roads.geom AS geom, \n"
" road_names.name as name FROM roads LEFT JOIN road_names ON \n"
" roads.road_name_id = road_names.road_name_id) \n"
" AS named_roads USING UNIQUE gid USING SRID=4326\" \n"
" MAXSCALE 20000 \n"
" STATUS ON \n"
" TYPE ANNOTATION \n"
" LABELITEM name\n"
" CLASS \n"
" LABEL \n"
" ANGLE auto \n"
" SIZE 8 \n"
" COLOR 0 192 0 \n"
" TYPE truetype \n"
" FONT arial\n"
" END\n"
" END \n"
"END"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:333
#, no-c-format
msgid ""
"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 "
"<varname>DATA</varname> definition."
msgstr ""
#. Tag: title
#: using_postgis_app.xml:340
#, no-c-format
msgid "Java Clients (JDBC)"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:342
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:348
#, no-c-format
msgid ""
"import java.sql.*; \n"
"import java.util.*; \n"
"import java.lang.*; \n"
"import org.postgis.*; \n"
"\n"
"public class JavaGIS { \n"
"\n"
"public static void main(String[] args) { \n"
"\n"
" java.sql.Connection conn; \n"
"\n"
" try { \n"
" /* \n"
" * Load the JDBC driver and establish a connection. \n"
" */\n"
" Class.forName(\"org.postgresql.Driver\"); \n"
" String url = \"jdbc:postgresql://localhost:5432/database\"; \n"
" conn = DriverManager.getConnection(url, \"postgres\", \"\"); \n"
" /* \n"
" * Add the geometry types to the connection. Note that you \n"
" * must cast the connection to the pgsql-specific connection \n"
" * implementation before calling the addDataType() method. \n"
" */\n"
" ((org.postgresql.PGConnection)conn).addDataType(\"geometry\",Class."
"forName(\"org.postgis.PGgeometry\"));\n"
" ((org.postgresql.PGConnection)conn).addDataType(\"box3d\",Class.forName"
"(\"org.postgis.PGbox3d\"));\n"
" /* \n"
" * Create a statement and execute a select query. \n"
" */ \n"
" Statement s = conn.createStatement(); \n"
" ResultSet r = s.executeQuery(\"select geom,id from geomtable\"); \n"
" while( r.next() ) { \n"
" /* \n"
" * Retrieve the geometry as an object then cast it to the geometry "
"type. \n"
" * Print things out. \n"
" */ \n"
" PGgeometry geom = (PGgeometry)r.getObject(1); \n"
" int id = r.getInt(2); \n"
" System.out.println(\"Row \" + id + \":\");\n"
" System.out.println(geom.toString()); \n"
" } \n"
" s.close(); \n"
" conn.close(); \n"
" } \n"
"catch( Exception e ) { \n"
" e.printStackTrace(); \n"
" } \n"
"} \n"
"}"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:350
#, no-c-format
msgid ""
"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."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:355
#, no-c-format
msgid ""
"PGgeometry geom = (PGgeometry)r.getObject(1); \n"
"if( geom.getType() == Geometry.POLYGON ) { \n"
" Polygon pl = (Polygon)geom.getGeometry(); \n"
" for( int r = 0; r &lt; pl.numRings(); r++) { \n"
" LinearRing rng = pl.getRing(r); \n"
" System.out.println(\"Ring: \" + r); \n"
" for( int p = 0; p &lt; rng.numPoints(); p++ ) { \n"
" Point pt = rng.getPoint(p); \n"
" System.out.println(\"Point: \" + p);\n"
" System.out.println(pt.toString()); \n"
" } \n"
" } \n"
"}"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:357
#, no-c-format
msgid ""
"The JavaDoc for the extension objects provides a reference for the various "
"data accessor functions in the geometric objects."
msgstr ""
#. Tag: title
#: using_postgis_app.xml:362
#, no-c-format
msgid "C Clients (libpq)"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:364 using_postgis_app.xml:369
#: using_postgis_app.xml:375
#, no-c-format
msgid "<para>...</para>"
msgstr ""
#. Tag: title
#: using_postgis_app.xml:367
#, no-c-format
msgid "Text Cursors"
msgstr ""
#. Tag: title
#: using_postgis_app.xml:373
#, no-c-format
msgid "Binary Cursors"
msgstr ""

3887
doc/po/pt_BR/using_postgis_dataman.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

1568
doc/po/pt_BR/using_raster_dataman.xml.po Normal file
View file

File diff suppressed because it is too large Load diff

11
doc/po/templates/README Normal file
View file

@ -0,0 +1,11 @@
This directory contains the template files to use for starting
a translation of the PostGIS manual.
To start your own language add its code to the ``translations``
variable in POSTGIS/doc/Makefile.in, re-run ./configure and
then run ``make update-po``. The rule will take care of creating
the initial .po files under POSTGIS/doc/po/<language_code>/, you
can then add those files to the repository and send the whole
(Makefile.in changes and new .po files) as a patch or pull request.
--strk(2012-09-14)

16
doc/po/templates/extras.xml.pot Normal file
View file

@ -0,0 +1,16 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

212
doc/po/templates/extras_historytable.xml.pot Normal file
View file

@ -0,0 +1,212 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: extras_historytable.xml:3
#, no-c-format
msgid "History Tracking"
msgstr ""
#. Tag: para
#: extras_historytable.xml:6
#, no-c-format
msgid "Suppose you have a table of data that represents the current state of a particular geographic feature. A parcels table, or a roads table, or a fruit trees table, whatever. Generally, GIS tools understand a table as a single entity into which they can update, insert and delete rows from. How you do allow common GIS tools to work against your data, while maintaining an audit trail of what changes have been made, by whom, and what the past state of the data is?"
msgstr ""
#. Tag: para
#: extras_historytable.xml:10
#, no-c-format
msgid "This <varname>history_table</varname> extra module provides some utility functions for creating and maintaining history."
msgstr ""
#. Tag: para
#: extras_historytable.xml:14
#, no-c-format
msgid "The <varname>history_table</varname> was also packaged in PostGIS 1.5, but added to the documentation in PostGIS 2.0. This package is written in plpgsql and located in the <varname>extras/history_table</varname> of PostGIS source tar balls and source repository."
msgstr ""
#. Tag: para
#: extras_historytable.xml:15
#, no-c-format
msgid "If you have a table 'roads', this module will maintain a 'roads_history' side table, which contains all the columns of the parent table, and the following additional columns:"
msgstr ""
#. Tag: programlisting
#: extras_historytable.xml:16
#, no-c-format
msgid ""
"history_id | integer | not null default \n"
" date_added | timestamp without time zone | not null default now()\n"
" date_deleted | timestamp without time zone | \n"
" last_operation | character varying(30) | not null\n"
" active_user | character varying(90) | not null default \"current_user\"()\n"
" current_version | text | not null"
msgstr ""
#. Tag: para
#: extras_historytable.xml:20
#, no-c-format
msgid "When you insert a new record into 'roads' a record is automatically inserted into 'roads_history', with the 'date_added' filled in the 'date_deleted' set to NULL, a unique 'history_id', a 'last_operation' of 'INSERT' and 'active_user' set."
msgstr ""
#. Tag: para
#: extras_historytable.xml:23
#, no-c-format
msgid "When you delete a record in 'roads', the record in the history table is *not* deleted, but the 'date_deleted' is set to the current date."
msgstr ""
#. Tag: para
#: extras_historytable.xml:26
#, no-c-format
msgid "When you update a record in 'roads', the current record has 'date_deleted' filled in and a new record is created with the 'date_added' set and 'date_deleted' NULL."
msgstr ""
#. Tag: para
#: extras_historytable.xml:30
#, no-c-format
msgid "With this information maintained, it is possible to retrieve the history of any record in the roads table:"
msgstr ""
#. Tag: programlisting
#: extras_historytable.xml:31
#, no-c-format
msgid "SELECT * FROM roads_history WHERE roads_pk = 111;"
msgstr ""
#. Tag: para
#: extras_historytable.xml:33
#, no-c-format
msgid "Or, to retrieve a view of the roads table at any point in the past:"
msgstr ""
#. Tag: programlisting
#: extras_historytable.xml:34
#, no-c-format
msgid ""
"SELECT * FROM roads_history \n"
" WHERE date_added &lt; 'January 1, 2001' AND \n"
" ( date_deleted &gt;= 'January 1, 2001' OR date_deleted IS NULL );"
msgstr ""
#. Tag: refname
#: extras_historytable.xml:38
#, no-c-format
msgid "Postgis_Install_History"
msgstr ""
#. Tag: refpurpose
#: extras_historytable.xml:39
#, no-c-format
msgid "Creates a table that will hold some interesting values for managing history tables."
msgstr ""
#. Tag: funcprototype
#: extras_historytable.xml:44
#, no-c-format
msgid "<funcdef>void <function>Postgis_Install_History</function></funcdef> <paramdef></paramdef>"
msgstr ""
#. Tag: title
#: extras_historytable.xml:52 extras_historytable.xml:92
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: extras_historytable.xml:54
#, no-c-format
msgid "Creates a table that will hold some interesting values for managing history tables. Creates a table called <varname>historic_information</varname>"
msgstr ""
#. Tag: para
#: extras_historytable.xml:58 extras_historytable.xml:100
#, no-c-format
msgid "Availability: 1.5.0"
msgstr ""
#. Tag: title
#: extras_historytable.xml:63 extras_historytable.xml:105
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: programlisting
#: extras_historytable.xml:65
#, no-c-format
msgid "SELECT postgis_install_history();"
msgstr ""
#. Tag: title
#: extras_historytable.xml:71 extras_historytable.xml:113
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: refname
#: extras_historytable.xml:77
#, no-c-format
msgid "Postgis_Enable_History"
msgstr ""
#. Tag: refpurpose
#: extras_historytable.xml:78
#, no-c-format
msgid "Registers a tablein the history_information table for tracking and also adds in side line history table and insert, update, delete rules on the table."
msgstr ""
#. Tag: funcprototype
#: extras_historytable.xml:83
#, no-c-format
msgid "<funcdef>boolean <function>Postgis_Enable_History</function></funcdef> <paramdef><type>text </type> <parameter>p_schema</parameter></paramdef> <paramdef><type>text </type> <parameter>p_table</parameter></paramdef>"
msgstr ""
#. Tag: para
#: extras_historytable.xml:94
#, no-c-format
msgid "Registers a table in the history_information table for tracking and also adds in side line history table with same name as table but prefixed with <varname>history</varname> in the same schema as the original table. Puts in insert, update, delete rules on the table. Any inserts,updates,deletes of the geometry are recorded in the history table."
msgstr ""
#. Tag: para
#: extras_historytable.xml:97
#, no-c-format
msgid "This function currently relies on a geometry column being registered in <varname>geometry_columns</varname> and fails if the geometry column is not present in <varname>geometry_columns</varname> table."
msgstr ""
#. Tag: programlisting
#: extras_historytable.xml:107
#, no-c-format
msgid ""
"CREATE TABLE roads(gid SERIAL PRIMARY KEY, road_name varchar(150));\n"
"SELECT AddGeometryColumn('roads', 'geom', 26986, 'LINESTRING', 2);\n"
" \n"
"SELECT postgis_enable_history('public', 'roads', 'geom') As register_table;\n"
"register_table\n"
"--------------\n"
"t\n"
"\n"
"INSERT INTO roads(road_name, geom) \n"
" VALUES('Test Street', ST_GeomFromText('LINESTRING(231660.5 832170,231647 832202,231627.5 832250.5)',26986));\n"
"\n"
"-- check transaction detail --\n"
"SELECT date_added, last_operation, current_version \n"
"FROM roads_history \n"
"WHERE road_name = 'Test Street' ORDER BY date_added DESC;\n"
"\n"
" date_added | last_operation | current_version\n"
"------------------------+----------------+-----------------\n"
" 2011-02-07 12:44:36.92 | INSERT | 2"
msgstr ""

1576
doc/po/templates/extras_tigergeocoder.xml.pot Normal file
View file

File diff suppressed because it is too large Load diff

2896
doc/po/templates/extras_topology.xml.pot Normal file
View file

File diff suppressed because it is too large Load diff

473
doc/po/templates/faq.xml.pot Normal file
View file

@ -0,0 +1,473 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: faq.xml:3
#, no-c-format
msgid "PostGIS Frequently Asked Questions"
msgstr ""
#. Tag: para
#: faq.xml:8
#, no-c-format
msgid "My applications and desktop tools worked with PostGIS 1.5,but they don't work with PostGIS 2.0. How do I fix this?"
msgstr ""
#. Tag: para
#: faq.xml:12
#, no-c-format
msgid "A lot of deprecated functions were removed from the PostGIS code base in PostGIS 2.0. This has affected applications in addition to third-party tools such as Geoserver, MapServer, QuantumGIS, and OpenJump to name a few. There are a couple of ways to resolve this. For the third-party apps, you can try to upgrade to the latest versions of these which have many of these issues fixed. For your own code, you can change your code to not use the functions removed. Most of these functions are non ST_ aliases of ST_Union, ST_Length etc. and as a last resort, install the whole of <varname>legacy.sql</varname> or just the portions of <varname>legacy.sql</varname> you need."
msgstr ""
#. Tag: para
#: faq.xml:18
#, no-c-format
msgid "The <varname>legacy.sql</varname> file is located in the same folder as postgis.sql. You can install this file after you have installed postgis.sql and spatial_ref_sys.sql to get back all the 200 some-odd old functions we removed."
msgstr ""
#. Tag: para
#: faq.xml:24
#, no-c-format
msgid "I'm running PostgreSQL 9.0 and I can no longer read/view geometries in OpenJump, Safe FME, and some other tools?"
msgstr ""
#. Tag: para
#: faq.xml:28
#, no-c-format
msgid "In PostgreSQL 9.0+, the default encoding for bytea data has been changed to hex and older JDBC drivers still assume escape format. This has affected some applications such as Java applications using older JDBC drivers or .NET applications that use the older npgsql driver that expect the old behavior of ST_AsBinary. There are two approaches to getting this to work again."
msgstr ""
#. Tag: para
#: faq.xml:32
#, no-c-format
msgid "You can upgrade your JDBC driver to the latest PostgreSQL 9.0 version which you can get from <ulink url=\"http://jdbc.postgresql.org/download.html\">http://jdbc.postgresql.org/download.html</ulink>"
msgstr ""
#. Tag: para
#: faq.xml:34
#, no-c-format
msgid "If you are running a .NET app, you can use Npgsql 2.0.11 or higher which you can download from <ulink url=\"http://pgfoundry.org/frs/?group_id=1000140\">http://pgfoundry.org/frs/?group_id=1000140</ulink> and as described on <ulink url=\"http://fxjr.blogspot.com/2010/11/npgsql-2011-released.html\">Francisco Figueiredo's NpgSQL 2.0.11 released blog entry</ulink>"
msgstr ""
#. Tag: para
#: faq.xml:38
#, no-c-format
msgid "If upgrading your PostgreSQL driver is not an option, then you can set the default back to the old behavior with the following change:"
msgstr ""
#. Tag: programlisting
#: faq.xml:39
#, no-c-format
msgid "ALTER DATABASE mypostgisdb SET bytea_output='escape';"
msgstr ""
#. Tag: para
#: faq.xml:46
#, no-c-format
msgid "I tried to use PgAdmin to view my geometry column and it is blank, what gives?"
msgstr ""
#. Tag: para
#: faq.xml:50
#, no-c-format
msgid "PgAdmin doesn't show anything for large geometries. The best ways to verify you do have data in your geometry columns are?"
msgstr ""
#. Tag: programlisting
#: faq.xml:53
#, no-c-format
msgid ""
"-- this should return no records if all your geom fields are filled in \n"
"SELECT somefield FROM mytable WHERE geom IS NULL;"
msgstr ""
#. Tag: programlisting
#: faq.xml:55
#, no-c-format
msgid ""
"-- To tell just how large your geometry is do a query of the form\n"
"--which will tell you the most number of points you have in any of your geometry columns\n"
"SELECT MAX(ST_NPoints(geom)) FROM sometable;"
msgstr ""
#. Tag: para
#: faq.xml:61
#, no-c-format
msgid "What kind of geometric objects can I store?"
msgstr ""
#. Tag: para
#: faq.xml:65
#, no-c-format
msgid "You can store point, line, polygon, multipoint, multiline, multipolygon, and geometrycollections. In PostGIS 2.0 and above you can also store TINS and Polyhedral Surfaces in the basic geometry type. These are specified in the Open GIS Well Known Text Format (with XYZ,XYM,XYZM extensions). There are three data types currently supported. The standard OGC geometry data type which uses a planar coordinate system for measurement, the geography data type which uses a geodetic coordinate system (not OGC, but you'll find a similar type in Microsoft SQL Server 2008+). Only WGS 84 long lat (SRID:4326) is supported by the geography data type. The newest family member of the PostGIS spatial type family is raster for storing and analyzing raster data. Raster has its very own FAQ. Refer to <xref linkend=\"RT_FAQ\"/> and <xref linkend=\"RT_reference\"/> for more details."
msgstr ""
#. Tag: para
#: faq.xml:78
#, no-c-format
msgid "I'm all confused. Which data store should I use geometry or geography?"
msgstr ""
#. Tag: para
#: faq.xml:82
#, no-c-format
msgid "Short Answer: geography is a new data type that supports long range distances measurements, but most computations on it are currently slower than they are on geometry. If you use geography -- you don't need to learn much about planar coordinate systems. Geography is generally best if all you care about is measuring distances and lengths and you have data from all over the world. Geometry data type is an older data type that has many more functions supporting it, enjoys greater support from third party tools, and operations on it are generally faster -- sometimes as much as 10 fold faster for larger geometries. Geometry is best if you are pretty comfortable with spatial reference systems or you are dealing with localized data where all your data fits in a single <link linkend=\"spatial_ref_sys\">spatial reference system (SRID)</link>, or you need to do a lot of spatial processing. Note: It is fairly easy to do one-off conversions between the two types to gain the benefits of each. Refer to <xref linkend=\"PostGIS_TypeFunctionMatrix\"/> to see what is currently supported and what is not."
msgstr ""
#. Tag: para
#: faq.xml:93
#, no-c-format
msgid "Long Answer: Refer to our more lengthy discussion in the <xref linkend=\"PostGIS_GeographyVSGeometry\"/> and <link linkend=\"PostGIS_TypeFunctionMatrix\">function type matrix</link>."
msgstr ""
#. Tag: para
#: faq.xml:101
#, no-c-format
msgid "I have more intense questions about geography, such as how big of a geographic region can I stuff in a geography column and still get reasonable answers. Are there limitations such as poles, everything in the field must fit in a hemisphere (like SQL Server 2008 has), speed etc?"
msgstr ""
#. Tag: para
#: faq.xml:105
#, no-c-format
msgid "Your questions are too deep and complex to be adequately answered in this section. Please refer to our <xref linkend=\"PostGIS_Geography_AdvancedFAQ\"/>."
msgstr ""
#. Tag: para
#: faq.xml:112
#, no-c-format
msgid "How do I insert a GIS object into the database?"
msgstr ""
#. Tag: para
#: faq.xml:116
#, no-c-format
msgid "First, you need to create a table with a column of type \"geometry\" or \"geography\" to hold your GIS data. Storing geography type data is a little different than storing geometry. Refer to <xref linkend=\"Geography_Basics\"/> for details on storing geography."
msgstr ""
#. Tag: para
#: faq.xml:120
#, no-c-format
msgid "For geometry: Connect to your database with <filename>psql</filename> and try the following SQL:"
msgstr ""
#. Tag: programlisting
#: faq.xml:124
#, no-c-format
msgid ""
"CREATE TABLE gtest ( ID int4, NAME varchar(20) );\n"
"SELECT AddGeometryColumn('', 'gtest','geom',-1,'LINESTRING',2);"
msgstr ""
#. Tag: para
#: faq.xml:126
#, no-c-format
msgid "If the geometry column addition fails, you probably have not loaded the PostGIS functions and objects into this database. See the <xref linkend=\"PGInstall\"/>."
msgstr ""
#. Tag: para
#: faq.xml:130
#, no-c-format
msgid "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:"
msgstr ""
#. Tag: programlisting
#: faq.xml:134
#, no-c-format
msgid ""
"INSERT INTO gtest (ID, NAME, GEOM) \n"
"VALUES (\n"
" 1, \n"
" 'First Geometry', \n"
" ST_GeomFromText('LINESTRING(2 3,4 5,6 5,7 8)', -1)\n"
");"
msgstr ""
#. Tag: para
#: faq.xml:136
#, no-c-format
msgid "For more information about other GIS objects, see the <link linkend=\"RefObject\">object reference</link>."
msgstr ""
#. Tag: para
#: faq.xml:139
#, no-c-format
msgid "To view your GIS data in the table:"
msgstr ""
#. Tag: programlisting
#: faq.xml:141
#, no-c-format
msgid "SELECT id, name, ST_AsText(geom) AS geom FROM gtest;"
msgstr ""
#. Tag: para
#: faq.xml:143
#, no-c-format
msgid "The return value should look something like this:"
msgstr ""
#. Tag: programlisting
#: faq.xml:145
#, no-c-format
msgid ""
"id | name | geom\n"
"----+----------------+-----------------------------\n"
" 1 | First Geometry | LINESTRING(2 3,4 5,6 5,7 8) \n"
"(1 row)"
msgstr ""
#. Tag: para
#: faq.xml:151
#, no-c-format
msgid "How do I construct a spatial query?"
msgstr ""
#. Tag: para
#: faq.xml:155
#, no-c-format
msgid "The same way you construct any other database query, as an SQL combination of return values, functions, and boolean tests."
msgstr ""
#. Tag: para
#: faq.xml:158
#, no-c-format
msgid "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."
msgstr ""
#. Tag: para
#: faq.xml:163
#, no-c-format
msgid "In general, you will want to use the \"intersects operator\" (&amp;&amp;) which tests whether the bounding boxes of features intersect. The reason the &amp;&amp; operator is useful is because if a spatial index is available to speed up the test, the &amp;&amp; operator will make use of this. This can make queries much much faster."
msgstr ""
#. Tag: para
#: faq.xml:170
#, no-c-format
msgid "You will also make use of spatial functions, such as Distance(), ST_Intersects(), ST_Contains() and ST_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 <emphasis>might</emphasis> meet the condition of interest. The spatial functions are then use to test the condition exactly."
msgstr ""
#. Tag: programlisting
#: faq.xml:178
#, no-c-format
msgid ""
"SELECT id, the_geom \n"
"FROM thetable \n"
"WHERE \n"
" ST_Contains(the_geom,'POLYGON((0 0, 0 10, 10 10, 10 0, 0 0))');"
msgstr ""
#. Tag: para
#: faq.xml:184
#, no-c-format
msgid "How do I speed up spatial queries on large tables?"
msgstr ""
#. Tag: para
#: faq.xml:188
#, no-c-format
msgid "Fast queries on large tables is the <emphasis>raison d'etre</emphasis> of spatial databases (along with transaction support) so having a good index is important."
msgstr ""
#. Tag: para
#: faq.xml:192
#, no-c-format
msgid "To build a spatial index on a table with a <varname>geometry</varname> column, use the \"CREATE INDEX\" function as follows:"
msgstr ""
#. Tag: programlisting
#: faq.xml:196
#, no-c-format
msgid "CREATE INDEX [indexname] ON [tablename] USING GIST ( [geometrycolumn] );"
msgstr ""
#. Tag: para
#: faq.xml:198
#, no-c-format
msgid "The \"USING GIST\" option tells the server to use a GiST (Generalized Search Tree) index."
msgstr ""
#. Tag: para
#: faq.xml:202
#, no-c-format
msgid "GiST indexes are assumed to be lossy. Lossy indexes uses a proxy object (in the spatial case, a bounding box) for building the index."
msgstr ""
#. Tag: para
#: faq.xml:207
#, no-c-format
msgid "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."
msgstr ""
#. Tag: para
#: faq.xml:212
#, no-c-format
msgid "For PostgreSQL 8.0.x and greater, just run the <command>VACUUM ANALYZE</command> command."
msgstr ""
#. Tag: para
#: faq.xml:215
#, no-c-format
msgid "For PostgreSQL 7.4.x and below, run the <command>SELECT UPDATE_GEOMETRY_STATS()</command> command."
msgstr ""
#. Tag: para
#: faq.xml:222
#, no-c-format
msgid "Why aren't PostgreSQL R-Tree indexes supported?"
msgstr ""
#. Tag: para
#: faq.xml:226
#, no-c-format
msgid "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."
msgstr ""
#. Tag: para
#: faq.xml:231
#, no-c-format
msgid "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):"
msgstr ""
#. Tag: para
#: faq.xml:239
#, no-c-format
msgid "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."
msgstr ""
#. Tag: para
#: faq.xml:246
#, no-c-format
msgid "R-Tree indexes in PostgreSQL are not \"null safe\", so building an index on a geometry column which contains null geometries will fail."
msgstr ""
#. Tag: para
#: faq.xml:256
#, no-c-format
msgid "Why should I use the <varname>AddGeometryColumn()</varname> function and all the other OpenGIS stuff?"
msgstr ""
#. Tag: para
#: faq.xml:261
#, no-c-format
msgid "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 <emphasis>not</emphasis> be filled in properly. However, this will cause most applications based on PostGIS to fail, and it is generally suggested that you do use <varname>AddGeometryColumn()</varname> to create geometry tables."
msgstr ""
#. Tag: para
#: faq.xml:270
#, no-c-format
msgid "MapServer is one application which makes use of the <varname>geometry_columns</varname> 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."
msgstr ""
#. Tag: para
#: faq.xml:279
#, no-c-format
msgid "What is the best way to find all objects within a radius of another object?"
msgstr ""
#. Tag: para
#: faq.xml:284
#, no-c-format
msgid "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."
msgstr ""
#. Tag: para
#: faq.xml:289
#, no-c-format
msgid "The <varname>ST_DWithin(geometry, geometry, distance)</varname> function is a handy way of performing an indexed distance search. It works by creating a search rectangle large enough to enclose the distance radius, then performing an exact distance search on the indexed subset of results."
msgstr ""
#. Tag: para
#: faq.xml:295
#, no-c-format
msgid "For example, to find all objects with 100 meters of POINT(1000 1000) the following query would work well:"
msgstr ""
#. Tag: programlisting
#: faq.xml:298
#, no-c-format
msgid ""
"SELECT * FROM geotable \n"
"WHERE ST_DWithin(geocolumn, 'POINT(1000 1000)', 100.0);"
msgstr ""
#. Tag: para
#: faq.xml:304
#, no-c-format
msgid "How do I perform a coordinate reprojection as part of a query?"
msgstr ""
#. Tag: para
#: faq.xml:309
#, no-c-format
msgid "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. The below projects a geometry to NAD 83 long lat. The below will only work if the srid of the_geom is not -1 (not undefined spatial ref)"
msgstr ""
#. Tag: programlisting
#: faq.xml:316
#, no-c-format
msgid "SELECT ST_Transform(the_geom,4269) FROM geotable;"
msgstr ""
#. Tag: para
#: faq.xml:322
#, no-c-format
msgid "I did an ST_AsEWKT and ST_AsText on my rather large geometry and it returned blank field. What gives?"
msgstr ""
#. Tag: para
#: faq.xml:326
#, no-c-format
msgid "You are probably using PgAdmin or some other tool that doesn't output large text. If your geometry is big enough, it will appear blank in these tools. Use PSQL if you really need to see it or output it in WKT."
msgstr ""
#. Tag: programlisting
#: faq.xml:329
#, no-c-format
msgid ""
"--To check number of geometries are really blank\n"
" SELECT count(gid) FROM geotable WHERE the_geom IS NULL;"
msgstr ""
#. Tag: para
#: faq.xml:335
#, no-c-format
msgid "When I do an ST_Intersects, it says my two geometries don't intersect when I KNOW THEY DO. What gives?"
msgstr ""
#. Tag: para
#: faq.xml:339
#, no-c-format
msgid "This generally happens in two common cases. Your geometry is invalid -- check <xref linkend=\"ST_IsValid\"/> or you are assuming they intersect because ST_AsText truncates the numbers and you have lots of decimals after it is not showing you."
msgstr ""
#. Tag: para
#: faq.xml:347
#, no-c-format
msgid "I am releasing software that uses PostGIS, does that mean my software has to be licensed using the GPL like PostGIS? Will I have to publish all my code if I use PostGIS?"
msgstr ""
#. Tag: para
#: faq.xml:351
#, no-c-format
msgid "Almost certainly not. As an example, consider Oracle database running on Linux. Linux is GPL, Oracle is not, does Oracle running on Linux have to be distributed using the GPL? No. So your software can use a PostgreSQL/PostGIS database as much as it wants and be under any license you like."
msgstr ""
#. Tag: para
#: faq.xml:352
#, no-c-format
msgid "The only exception would be if you made changes to the PostGIS source code, and distributed your changed version of PostGIS. In that case you would have to share the code of your changed PostGIS (but not the code of applications running on top of it). Even in this limited case, you would still only have to distribute source code to people you distributed binaries to. The GPL does not require that you <emphasis>publish</emphasis> your source code, only that you share it with people you give binaries to."
msgstr ""

480
doc/po/templates/faq_raster.xml.pot Normal file
View file

@ -0,0 +1,480 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: faq_raster.xml:3
#, no-c-format
msgid "PostGIS Raster Frequently Asked Questions"
msgstr ""
#. Tag: para
#: faq_raster.xml:9
#, no-c-format
msgid "Where can I find out more about the PostGIS Raster Project?"
msgstr ""
#. Tag: para
#: faq_raster.xml:13
#, no-c-format
msgid "Refer to the <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster\">PostGIS Raster home page</ulink>."
msgstr ""
#. Tag: para
#: faq_raster.xml:19
#, no-c-format
msgid "Are there any books or tutorials to get me started with this wonderful invention?"
msgstr ""
#. Tag: para
#: faq_raster.xml:23
#, no-c-format
msgid "There is a full length beginner tutorial <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRasterTutorial01\"> Intersecting vector buffers with large raster coverage using PostGIS Raster</ulink>. Jorge has a series of blog articles on PostGIS Raster that demonstrate how to load raster data as well as cross compare to same tasks in Oracle GeoRaster. Check out <ulink url=\"http://gis4free.wordpress.com/category/postgis-raster/\">Jorge's PostGIS Raster / Oracle GeoRaster Series</ulink>. There is a whole chapter (more than 35 pages of content) dedicated to PostGIS Raster with free code and data downloads at <ulink url=\"http://www.postgis.us/chapter_13\">PostGIS in Action - Raster chapter</ulink>. You can <ulink url=\"http://www.postgis.us/page_buy_book\">buy PostGIS in Action</ulink> now from Manning in hard-copy (significant discounts for bulk purchases) or just the E-book format. You can also buy from Amazon and various other book distributors. All hard-copy books come with a free coupon to download the E-book version."
msgstr ""
#. Tag: para
#: faq_raster.xml:30
#, no-c-format
msgid "Here is a review from a PostGIS Raster user <ulink url=\"http://fuzzytolerance.info/code/postgis-raster-ftw/\">PostGIS raster applied to land classification urban forestry</ulink>"
msgstr ""
#. Tag: para
#: faq_raster.xml:37
#, no-c-format
msgid "How do I install Raster support in my PostGIS database?"
msgstr ""
#. Tag: para
#: faq_raster.xml:41
#, no-c-format
msgid "The easiest is to download binaries for PostGIS and Raster which are currently available for windows and latest versions of Mac OSX. First you need a working PostGIS 2.0.0 or above and be running PostgreSQL 8.4, 9.0, or 9.1. Note in PostGIS 2.0 PostGIS Raster is fully integrated, so it will be compiled when you compile PostGIS."
msgstr ""
#. Tag: para
#: faq_raster.xml:43
#, no-c-format
msgid "Instructions for installing and running under windows are available at <ulink url=\"http://gis4free.wordpress.com/2011/03/10/how-to-install-and-configure-postgis-raster-on-windows/\">How to Install and Configure PostGIS raster on windows</ulink>"
msgstr ""
#. Tag: para
#: faq_raster.xml:44
#, no-c-format
msgid "If you are on windows, you can compile yourself, or use the <ulink url=\"http://www.postgis.org/download/windows/experimental.php#wktraster\">pre-compiled PostGIS Raster windows binaries</ulink>. If you are on Mac OSX Leopard or Snow Leopard, there are binaries available at <ulink url=\"http://www.kyngchaos.com/software/postgres\">Kyng Chaos Mac OSX PostgreSQL/GIS binaries</ulink>."
msgstr ""
#. Tag: para
#: faq_raster.xml:50
#, no-c-format
msgid "Then to enable raster support in your database, run the rtpostgis.sql file in your database. To upgrade an existing install use rtpostgis_upgrade_minor..sql instead of rtpostgis.sql"
msgstr ""
#. Tag: para
#: faq_raster.xml:51
#, no-c-format
msgid "For other platforms, you generally need to compile yourself. Dependencies are PostGIS and GDAL. For more details about compiling from source, please refer to <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/Documentation01#a2.3-CompilingandInstallingfromSources\">Installing PostGIS Raster from source (in prior versions of PostGIS)</ulink>"
msgstr ""
#. Tag: para
#: faq_raster.xml:57
#, no-c-format
msgid "I get error could not load library \"C:/Program Files/PostgreSQL/8.4/lib/rtpostgis.dll\": The specified module could not be found. or could not load library on Linux when trying to run rtpostgis.sql"
msgstr ""
#. Tag: para
#: faq_raster.xml:62
#, no-c-format
msgid "rtpostgis.so/dll is built with dependency on libgdal.dll/so. Make sure for Windows you have libgdal-1.dll in the bin folder of your PostgreSQL install. For Linux libgdal has to be in your path or bin folder."
msgstr ""
#. Tag: para
#: faq_raster.xml:64
#, no-c-format
msgid "You may also run into different errors if you don't have PostGIS installed in your database. Make sure to install PostGIS first in your database before trying to install the raster support."
msgstr ""
#. Tag: para
#: faq_raster.xml:71
#, no-c-format
msgid "How do I load Raster data into PostGIS?"
msgstr ""
#. Tag: para
#: faq_raster.xml:75
#, no-c-format
msgid "The latest version of PostGIS comes packaged with a <varname>raster2pgsql</varname> raster loader executable capable of loading many kinds of rasters and also generating lower resolution overviews without any additional software. Please refer to <xref linkend=\"RT_Raster_Loader\"/> for more details. Pre-2.0 versions came with a <varname>raster2pgsql.py</varname> that required python with numpy and GDAL. This is no longer needed."
msgstr ""
#. Tag: para
#: faq_raster.xml:81
#, no-c-format
msgid "What kind of raster file formats can I load into my database?"
msgstr ""
#. Tag: para
#: faq_raster.xml:85
#, no-c-format
msgid "Any that your GDAL library supports. GDAL supported formats are documented <ulink url=\"http://www.gdal.org/formats_list.html\">GDAL File Formats</ulink>."
msgstr ""
#. Tag: para
#: faq_raster.xml:86
#, no-c-format
msgid "Your particular GDAL install may not support all formats. To verify the ones supported by your particular GDAL install, you can use"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:87
#, no-c-format
msgid "raster2pgsql -G"
msgstr ""
#. Tag: para
#: faq_raster.xml:93
#, no-c-format
msgid "Can I export my PostGIS raster data to other raster formats?"
msgstr ""
#. Tag: para
#: faq_raster.xml:97
#, no-c-format
msgid "<para>Yes</para>"
msgstr ""
#. Tag: para
#: faq_raster.xml:98
#, no-c-format
msgid "GDAL 1.7+ has a PostGIS raster driver, but is only compiled in if you choose to compile with PostgreSQL support."
msgstr ""
#. Tag: para
#: faq_raster.xml:99
#, no-c-format
msgid "The driver currently doesn't support irregularly blocked rasters, although you can store irregularly blocked rasters in PostGIS raster data type."
msgstr ""
#. Tag: para
#: faq_raster.xml:101
#, no-c-format
msgid "If you are compiling from source, you need to include in your configure <programlisting>--with-pg=path/to/pg_config</programlisting> to enable the driver. Refer to <ulink url=\"http://trac.osgeo.org/gdal/wiki/BuildHints\">GDAL Build Hints</ulink> for tips on building GDAL against in various OS platforms."
msgstr ""
#. Tag: para
#: faq_raster.xml:106
#, no-c-format
msgid "If your version of GDAL is compiled with the PostGIS Raster driver you should see PostGIS Raster in list when you do"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:108
#, no-c-format
msgid "gdalinfo --formats"
msgstr ""
#. Tag: para
#: faq_raster.xml:110
#, no-c-format
msgid "To get a summary about your raster via GDAL use gdalinfo:"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:111
#, no-c-format
msgid "gdalinfo \"PG:host=localhost port=5432 dbname='mygisdb' user='postgres' password='whatever' schema='someschema' table=sometable\""
msgstr ""
#. Tag: para
#: faq_raster.xml:114
#, no-c-format
msgid "To export data to other raster formats, use gdal_translate the below will export all data from a table to a PNG file at 10% size."
msgstr ""
#. Tag: para
#: faq_raster.xml:116
#, no-c-format
msgid "Depending on your pixel band types, some translations may not work if the export format does not support that Pixel type. For example floating point band types and 32 bit unsigned ints will not translate easily to JPG or some others."
msgstr ""
#. Tag: para
#: faq_raster.xml:119
#, no-c-format
msgid "Here is an example simple translation"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:120
#, no-c-format
msgid "gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' user='postgres' password=whatever' schema='someschema' table=sometable\" C:\\somefile.png"
msgstr ""
#. Tag: para
#: faq_raster.xml:121
#, no-c-format
msgid "You can also use SQL where clauses in your export using the where=... in your driver connection string. Below are some using a where clause"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:123
#, no-c-format
msgid "gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' user='postgres' password=whatever' schema='someschema' table=sometable where=\"owner='jimmy'\" \" C:\\somefile.png"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:124
#, no-c-format
msgid "gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' user='postgres' password=whatever' schema='someschema' table=sometable where='ST_Intersects(rast, ST_SetSRID(ST_Point(-71.032,42.3793),4326) )' \" C:\\intersectregion.png"
msgstr ""
#. Tag: para
#: faq_raster.xml:125
#, no-c-format
msgid "To see more examples and syntax refer to <ulink url=\"http://trac.osgeo.org/gdal/wiki/frmts_wtkraster.html#a3.2-Readingrasterdatafromthedatabase\">Reading Raster Data of PostGIS Raster section</ulink>"
msgstr ""
#. Tag: para
#: faq_raster.xml:130
#, no-c-format
msgid "Are their binaries of GDAL available already compiled with PostGIS Raster suppport?"
msgstr ""
#. Tag: para
#: faq_raster.xml:132
#, no-c-format
msgid "Yes. Check out the page <ulink url=\"http://trac.osgeo.org/gdal/wiki/DownloadingGdalBinaries\">GDAL Binaries</ulink> page. Any compiled with PostgreSQL support should have PostGIS Raster in them."
msgstr ""
#. Tag: para
#: faq_raster.xml:134
#, no-c-format
msgid "We know for sure the following windows binaries have PostGIS Raster built in."
msgstr ""
#. Tag: para
#: faq_raster.xml:135
#, no-c-format
msgid "<ulink url=\"http://fwtools.maptools.org/\">FWTools latest stable version for Windows is compiled with Raster support</ulink>."
msgstr ""
#. Tag: para
#: faq_raster.xml:136
#, no-c-format
msgid "PostGIS Raster is undergoing many changes. If you want to get the latest nightly build for Windows -- then check out the Tamas Szekeres nightly builds built with Visual Studio which contain GDAL trunk, Python Bindings and MapServer executables and PostGIS Raster driver built-in. Just click the SDK bat and run your commands from there. <ulink url=\"http://vbkto.dyndns.org/sdk/\">http://vbkto.dyndns.org/sdk/</ulink>. Also available are VS project files."
msgstr ""
#. Tag: para
#: faq_raster.xml:145
#, no-c-format
msgid "What tools can I use to view PostGIS raster data?"
msgstr ""
#. Tag: para
#: faq_raster.xml:149
#, no-c-format
msgid "You can use MapServer compiled with GDAL 1.7+ and PostGIS Raster driver support to view Raster data. QuantumGIS (QGIS) now supports viewing of PostGIS Raster if you have PostGIS raster driver installed."
msgstr ""
#. Tag: para
#: faq_raster.xml:151
#, no-c-format
msgid "In theory any tool that renders data using GDAL can support PostGIS raster data or support it with fairly minimal effort. Again for Windows, Tamas' binaries <ulink url=\"http://vbkto.dyndns.org/sdk/\">http://vbkto.dyndns.org/sdk/</ulink> are a good choice if you don't want the hassle of having to setup to compile your own."
msgstr ""
#. Tag: para
#: faq_raster.xml:158
#, no-c-format
msgid "How can I add a PostGIS raster layer to my MapServer map?"
msgstr ""
#. Tag: para
#: faq_raster.xml:162
#, no-c-format
msgid "First you need GDAL 1.7 or higher compiled with PostGIS raster support. GDAL 1.8 or above is preferred since many issues have been fixed in 1.8 and more PostGIS raster issues fixed in trunk version."
msgstr ""
#. Tag: para
#: faq_raster.xml:164
#, no-c-format
msgid "You can much like you can with any other raster. Refer to <ulink url=\"http://mapserver.org/input/raster.html\">MapServer Raster processing options</ulink> for list of various processing functions you can use with MapServer raster layers."
msgstr ""
#. Tag: para
#: faq_raster.xml:167
#, no-c-format
msgid "What makes PostGIS raster data particularly interesting, is that since each tile can have various standard database columns, you can segment it in your data source"
msgstr ""
#. Tag: para
#: faq_raster.xml:169
#, no-c-format
msgid "Below is an example of how you would define a PostGIS raster layer in MapServer."
msgstr ""
#. Tag: para
#: faq_raster.xml:170
#, no-c-format
msgid "The mode=2 is required for tiled rasters and was added in PostGIS 2.0 and GDAL 1.8 drivers. This does not exist in GDAL 1.7 drivers."
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:171
#, no-c-format
msgid ""
"-- displaying raster with standard raster options\n"
"LAYER\n"
" NAME coolwktraster\n"
" TYPE raster\n"
" STATUS ON\n"
" DATA \"PG:host=localhost port=5432 dbname='somedb' user='someuser' password='whatever' \n"
" schema='someschema' table='cooltable' mode='2'\" \n"
" PROCESSING \"NODATA=0\"\n"
" PROCESSING \"SCALE=AUTO\"\n"
" #... other standard raster processing functions here\n"
" #... classes are optional but useful for 1 band data\n"
" CLASS\n"
" NAME \"boring\"\n"
" EXPRESSION ([pixel] &lt; 20)\n"
" COLOR 250 250 250\n"
" END\n"
" CLASS\n"
" NAME \"mildly interesting\"\n"
" EXPRESSION ([pixel] &gt; 20 AND [pixel] &lt; 1000)\n"
" COLOR 255 0 0\n"
" END\n"
" CLASS\n"
" NAME \"very interesting\"\n"
" EXPRESSION ([pixel] &gt;= 1000)\n"
" COLOR 0 255 0\n"
" END\n"
"END"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:173
#, no-c-format
msgid ""
"-- displaying raster with standard raster options and a where clause\n"
"LAYER\n"
" NAME soil_survey2009\n"
" TYPE raster\n"
" STATUS ON\n"
" DATA \"PG:host=localhost port=5432 dbname='somedb' user='someuser' password='whatever' \n"
" schema='someschema' table='cooltable' where='survey_year=2009' mode='2'\" \n"
" PROCESSING \"NODATA=0\"\n"
" #... other standard raster processing functions here\n"
" #... classes are optional but useful for 1 band data\n"
"END"
msgstr ""
#. Tag: para
#: faq_raster.xml:181
#, no-c-format
msgid "What functions can I currently use with my raster data?"
msgstr ""
#. Tag: para
#: faq_raster.xml:185
#, no-c-format
msgid "Refer to the list of <xref linkend=\"RT_reference\"/>. There are more, but this is still a work in progress."
msgstr ""
#. Tag: para
#: faq_raster.xml:187
#, no-c-format
msgid "Refer to the <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/PlanningAndFunding\">PostGIS Raster roadmap page</ulink> for details of what you can expect in the future."
msgstr ""
#. Tag: para
#: faq_raster.xml:195
#, no-c-format
msgid "I am getting error ERROR: function st_intersects(raster, unknown) is not unique or st_union(geometry,text) is not unique. How do I fix?"
msgstr ""
#. Tag: para
#: faq_raster.xml:199
#, no-c-format
msgid "The function is not unique error happens if one of your arguments is a textual representation of a geometry instead of a geometry. In these cases, PostgreSQL marks the textual representation as an unknown type, which means it can fall into the st_intersects(raster, geometry) or st_intersects(raster,raster) thus resulting in a non-unique case since both functions can in theory support your request. To prevent this, you need to cast the geometry to a geometry."
msgstr ""
#. Tag: para
#: faq_raster.xml:200
#, no-c-format
msgid "For example if your code looks like this:"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:201
#, no-c-format
msgid ""
"SELECT rast\n"
" FROM my_raster\n"
" WHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)');"
msgstr ""
#. Tag: para
#: faq_raster.xml:202
#, no-c-format
msgid "Cast the textual geometry representation to a geometry by changing your code to this:"
msgstr ""
#. Tag: programlisting
#: faq_raster.xml:203
#, no-c-format
msgid ""
"SELECT rast\n"
" FROM my_raster\n"
" WHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)'::geometry);"
msgstr ""
#. Tag: para
#: faq_raster.xml:211
#, no-c-format
msgid "How is PostGIS Raster different from Oracle GeoRaster (SDO_GEORASTER) and SDO_RASTER types?"
msgstr ""
#. Tag: para
#: faq_raster.xml:215
#, no-c-format
msgid "For a more extensive discussion on this topic, check out Jorge Arévalo <ulink url=\"http://gis4free.wordpress.com/2010/07/19/oracle-georaster-part-i/\">Oracle GeoRaster and PostGIS Raster: First impressions </ulink>"
msgstr ""
#. Tag: para
#: faq_raster.xml:216
#, no-c-format
msgid "The major advantage of one-georeference-by-raster over one-georeference-by-layer is to allow:"
msgstr ""
#. Tag: para
#: faq_raster.xml:217
#, no-c-format
msgid "* coverages to be not necessarily rectangular (which is often the case of raster coverage covering large extents. See the possible raster arrangements in the documentation)"
msgstr ""
#. Tag: para
#: faq_raster.xml:218
#, no-c-format
msgid "* rasters to overlaps (which is necessary to implement lossless vector to raster conversion)"
msgstr ""
#. Tag: para
#: faq_raster.xml:219
#, no-c-format
msgid "These arrangements are possible in Oracle as well, but they imply the storage of multiple SDO_GEORASTER objects linked to as many SDO_RASTER tables. A complex coverage can lead to hundreds of tables in the database. With PostGIS Raster you can store a similar raster arrangement into a unique table."
msgstr ""
#. Tag: para
#: faq_raster.xml:224
#, no-c-format
msgid "It's a bit like if PostGIS would force you to store only full rectangular vector coverage without gaps or overlaps (a perfect rectangular topological layer). This is very practical in some applications but practice has shown that it is not realistic or desirable for most geographical coverages. Vector structures needs the flexibility to store discontinuous and non-rectangular coverages. We think it is a big advantage that raster structure should benefit as well."
msgstr ""

1680
doc/po/templates/installation.xml.pot Normal file
View file

File diff suppressed because it is too large Load diff

382
doc/po/templates/introduction.xml.pot Normal file
View file

@ -0,0 +1,382 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: introduction.xml:3
#, no-c-format
msgid "Introduction"
msgstr ""
#. Tag: para
#: introduction.xml:5
#, no-c-format
msgid "PostGIS was 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."
msgstr ""
#. Tag: para
#: introduction.xml:15
#, no-c-format
msgid "PostGIS is an incubation project of the OSGeo Foundation. PostGIS is being continually improved and funded by many FOSS4G Developers as well as corporations all over the world that gain great benefit from its functionality and versatility."
msgstr ""
#. Tag: title
#: introduction.xml:21
#, no-c-format
msgid "Project Steering Committee"
msgstr ""
#. Tag: para
#: introduction.xml:22
#, no-c-format
msgid "The PostGIS Project Steering Committee (PSC) coordinates the general direction, release cycles, documentation, and outreach efforts for the PostGIS project. In addition the PSC provides general user support, accepts and approves patches from the general PostGIS community and votes on miscellaneous issues involving PostGIS such as developer commit access, new PSC members or significant API changes."
msgstr ""
#. Tag: term
#: introduction.xml:31
#, no-c-format
msgid "Mark Cave-Ayland"
msgstr ""
#. Tag: para
#: introduction.xml:33
#, no-c-format
msgid "Coordinates bug fixing and maintenance effort, alignment of PostGIS with PostgreSQL releases, spatial index selectivity and binding, loader/dumper, and Shapefile GUI Loader, integration of new and new function enhancements."
msgstr ""
#. Tag: term
#: introduction.xml:40
#, no-c-format
msgid "Regina Obe"
msgstr ""
#. Tag: para
#: introduction.xml:42
#, no-c-format
msgid "Buildbot Maintenance, windows production and experimental builds, Documentation, general user support on PostGIS newsgroup, X3D support, Tiger Geocoder Support, management functions, and smoke testing new functionality or major code changes."
msgstr ""
#. Tag: term
#: introduction.xml:49
#, no-c-format
msgid "Paul Ramsey (Chair)"
msgstr ""
#. Tag: para
#: introduction.xml:51
#, no-c-format
msgid "Co-founder of PostGIS project. General bug fixing, geography support, geography and geometry index support (2D, 3D, nD index and anything spatial index), underlying geometry internal structures, GEOS functionality integration and alignment with GEOS releases, loader/dumper, and Shapefile GUI loader."
msgstr ""
#. Tag: term
#: introduction.xml:57
#, no-c-format
msgid "Sandro Santilli"
msgstr ""
#. Tag: para
#: introduction.xml:60
#, no-c-format
msgid "Bug fixes and maintenance and integration of new GEOS functionality and alignment with GEOS releases, Topology support, and Raster framework and low level api functions."
msgstr ""
#. Tag: title
#: introduction.xml:67
#, no-c-format
msgid "Contributors Past and Present"
msgstr ""
#. Tag: term
#: introduction.xml:71
#, no-c-format
msgid "Chris Hodgson"
msgstr ""
#. Tag: para
#: introduction.xml:73
#, no-c-format
msgid "Prior PSC Member. General development, site and buildbot maintenance, OSGeo incubation management"
msgstr ""
#. Tag: term
#: introduction.xml:77
#, no-c-format
msgid "Kevin Neufeld"
msgstr ""
#. Tag: para
#: introduction.xml:79
#, no-c-format
msgid "Prior PSC Member. Documentation and documentation support tools, advanced user support on PostGIS newsgroup, and PostGIS maintenance function enhancements."
msgstr ""
#. Tag: term
#: introduction.xml:85
#, no-c-format
msgid "Dave Blasby"
msgstr ""
#. Tag: para
#: introduction.xml:88
#, no-c-format
msgid "The original developer/Co-founder of PostGIS. Dave wrote the server side objects, index bindings, and many of the server side analytical functions."
msgstr ""
#. Tag: term
#: introduction.xml:95
#, no-c-format
msgid "Jeff Lounsbury"
msgstr ""
#. Tag: para
#: introduction.xml:97
#, no-c-format
msgid "Original development of the Shape file loader/dumper. Current PostGIS Project Owner representative."
msgstr ""
#. Tag: term
#: introduction.xml:102
#, no-c-format
msgid "Olivier Courtin"
msgstr ""
#. Tag: para
#: introduction.xml:104
#, no-c-format
msgid "Input output XML (KML,GML)/GeoJSON functions, 3D support and bug fixes."
msgstr ""
#. Tag: term
#: introduction.xml:109
#, no-c-format
msgid "Mark Leslie"
msgstr ""
#. Tag: para
#: introduction.xml:111
#, no-c-format
msgid "Ongoing maintenance and development of core functions. Enhanced curve support. Shapefile GUI loader."
msgstr ""
#. Tag: term
#: introduction.xml:116
#, no-c-format
msgid "Pierre Racine"
msgstr ""
#. Tag: para
#: introduction.xml:118
#, no-c-format
msgid "Raster overall architecture, prototyping, programming support"
msgstr ""
#. Tag: term
#: introduction.xml:123
#, no-c-format
msgid "Nicklas Avén"
msgstr ""
#. Tag: para
#: introduction.xml:126
#, no-c-format
msgid "Distance function enhancements (including 3D distance and relationship functions) and additions, Windows testing, and general user support"
msgstr ""
#. Tag: term
#: introduction.xml:131
#, no-c-format
msgid "Jorge Arévalo"
msgstr ""
#. Tag: para
#: introduction.xml:134
#, no-c-format
msgid "Raster development, GDAL driver support, loader"
msgstr ""
#. Tag: term
#: introduction.xml:139
#, no-c-format
msgid "Bborie Park"
msgstr ""
#. Tag: para
#: introduction.xml:141
#, no-c-format
msgid "Raster development, raster loader"
msgstr ""
#. Tag: term
#: introduction.xml:146
#, no-c-format
msgid "Mateusz Loskot"
msgstr ""
#. Tag: para
#: introduction.xml:148
#, no-c-format
msgid "Raster loader, low level raster api functions"
msgstr ""
#. Tag: term
#: introduction.xml:153
#, no-c-format
msgid "David Zwarg"
msgstr ""
#. Tag: para
#: introduction.xml:156
#, no-c-format
msgid "Raster development"
msgstr ""
#. Tag: term
#: introduction.xml:161
#, no-c-format
msgid "Other contributors: Individuals"
msgstr ""
#. Tag: para
#: introduction.xml:164
#, no-c-format
msgid "In alphabetical order: Alex Bodnaru, Alex Mayrhofer, Andrea Peri, Andreas Forø Tollefsen, Andreas Neumann, Anne Ghisla, Barbara Phillipot, Ben Jubb, Bernhard Reiter, Brian Hamlin, Bruce Rindahl, Bruno Wolff III, Bryce L. Nordgren, Carl Anderson, Charlie Savage, Dane Springmeyer, David Skea, David Techer, Eduin Carrillo, Even Rouault, Frank Warmerdam, George Silva, Gerald Fenoy, Gino Lucrezi, Guillaume Lelarge, IIDA Tetsushi, Ingvild Nystuen, Jeff Adams, Jose Carlos Martinez Llari, Kashif Rasul, Klaus Foerster, Kris Jurka, Leo Hsu, Loic Dachary, Luca S. Percich, Maria Arias de Reyna, Mark Sondheim, Markus Schaber, Maxime Guillaud, Maxime van Noppen, Michael Fuhr, Nikita Shulga, Norman Vine, Rafal Magda, Ralph Mason, Richard Greenwood, Silvio Grosso, Steffen Macke, Stephen Frost, Tom van Tilburg, Vincent Picavet"
msgstr ""
#. Tag: term
#: introduction.xml:221
#, no-c-format
msgid "Other contributors: Corporate Sponsors"
msgstr ""
#. Tag: para
#: introduction.xml:224
#, no-c-format
msgid "These are corporate entities that have contributed developer time, hosting, or direct monetary funding to the PostGIS project"
msgstr ""
#. Tag: para
#: introduction.xml:225
#, no-c-format
msgid "In alphabetical order: Arrival 3D, Associazione Italiana per l'Informazione Geografica Libera (GFOSS.it), AusVet, Avencia, Azavea, Cadcorp, CampToCamp, City of Boston (DND), Clever Elephant Solutions, Cooperativa Alveo, Deimos Space, Faunalia, Geographic Data BC, Hunter Systems Group, Lidwala Consulting Engineers, LisaSoft, Logical Tracking &amp; Tracing International AG, Michigan Tech Research Institute, Norwegian Forest and Landscape Institute, OpenGeo, OSGeo, Oslandia, Paragon Corporation, R3 GIS,, Refractions Research, Regione Toscana-SIGTA, Safe Software, Sirius Corporation plc, Stadt Uster, UC Davis Center for Vectorborne Diseases, University of Laval, U.S Department of State (HIU), Vizzuality, Zonar Systems"
msgstr ""
#. Tag: term
#: introduction.xml:265
#, no-c-format
msgid "Crowd Funding Campaigns"
msgstr ""
#. Tag: para
#: introduction.xml:268
#, no-c-format
msgid "Crowd funding campaigns are campaigns we run to get badly wanted features funded that can service a large number of people. Each campaign is specifically focused on a particular feature or set of features. Each sponsor chips in a small fraction of the needed funding and with enough people/organizations contributing, we have the funds to pay for the work that will help many. If you have an idea for a feature you think many others would be willing to co-fund, please post to the <ulink url=\"http://www.postgis.org/mailman/listinfo/postgis-users\">PostGIS newsgroup</ulink> your thoughts and together we can make it happen."
msgstr ""
#. Tag: para
#: introduction.xml:269
#, no-c-format
msgid "PostGIS 2.0.0 was the first release we tried this strategy. We used <ulink url=\"http://www.pledgebank.com\">PledgeBank</ulink> and we got two successful campaigns out of it."
msgstr ""
#. Tag: para
#: introduction.xml:270
#, no-c-format
msgid "<ulink url=\"http://www.pledgebank.com/postgistopology\"><emphasis role=\"bold\">postgistopology</emphasis></ulink> - 10 plus sponsors each contributed $250 USD to build toTopoGeometry function and beef up topology support in 2.0.0. It happened."
msgstr ""
#. Tag: para
#: introduction.xml:271
#, no-c-format
msgid "<ulink url=\"http://www.pledgebank.com/postgis64windows\"><emphasis role=\"bold\">postgis64windows</emphasis></ulink> - 20 someodd sponsors each contributed $100 USD to pay for the work needed to work out PostGIS 64-bit on windows issues. It happened. We now have a 64-bit beta release for PostGIS 2.0.0 and a final one planned for release that will be available on PostgreSQL stack builder."
msgstr ""
#. Tag: term
#: introduction.xml:276
#, no-c-format
msgid "Important Support Libraries"
msgstr ""
#. Tag: para
#: introduction.xml:279
#, no-c-format
msgid "The <ulink url=\"http://trac.osgeo.org/geos/\">GEOS</ulink> geometry operations library, and the algorithmic work of Martin Davis in making it all work, ongoing maintenance and support of Mateusz Loskot, Sandro Santilli (strk), Paul Ramsey and others."
msgstr ""
#. Tag: para
#: introduction.xml:284
#, no-c-format
msgid "The <ulink url=\"http://trac.osgeo.org/gdal/\">GDAL</ulink> Geospatial Data Abstraction Library, by Frank Warmerdam and others is used to power much of the raster functionality introduced in PostGIS 2.0.0. In kind, improvements needed in GDAL to support PostGIS are contributed back to the GDAL project."
msgstr ""
#. Tag: para
#: introduction.xml:289
#, no-c-format
msgid "The <ulink url=\"http://trac.osgeo.org/proj/\">Proj4</ulink> cartographic projection library, and the work of Gerald Evenden and Frank Warmerdam in creating and maintaining it."
msgstr ""
#. Tag: para
#: introduction.xml:293
#, no-c-format
msgid "Last but not least, the <ulink url=\"http://www.postgresql.org\">PostgreSQL DBMS</ulink>, The giant that PostGIS stands on. Much of the speed and flexibility of PostGIS would not be possible without the extensibility, great query planner, GIST index, and plethora of SQL features provided by PostgreSQL."
msgstr ""
#. Tag: title
#: introduction.xml:302
#, no-c-format
msgid "More Information"
msgstr ""
#. Tag: para
#: introduction.xml:306
#, no-c-format
msgid "The latest software, documentation and news items are available at the PostGIS web site, <ulink url=\"http://www.postgis.org\">http://www.postgis.org</ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:312
#, no-c-format
msgid "More information about the GEOS geometry operations library is available at<ulink url=\"http://trac.osgeo.org/geos/\"> http://trac.osgeo.org/geos/</ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:318
#, no-c-format
msgid "More information about the Proj4 reprojection library is available at <ulink url=\"http://trac.osgeo.org/proj/\">http://trac.osgeo.org/proj/</ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:324
#, no-c-format
msgid "More information about the PostgreSQL database server is available at the PostgreSQL main site <ulink url=\"http://www.postgresql.org\">http://www.postgresql.org</ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:330
#, no-c-format
msgid "More information about GiST indexing is available at the PostgreSQL GiST development site, <ulink url=\"http://www.sai.msu.su/~megera/postgres/gist/\">http://www.sai.msu.su/~megera/postgres/gist/</ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:336
#, no-c-format
msgid "More information about MapServer internet map server is available at <ulink url=\"http://mapserver.org/\">http://mapserver.org</ulink>."
msgstr ""
#. Tag: para
#: introduction.xml:342
#, no-c-format
msgid "The &quot;<ulink url=\"http://www.opengeospatial.org/standards/sfs\">Simple Features for Specification for SQL</ulink>&quot; is available at the OpenGIS Consortium web site: <ulink url=\"http://www.opengeospatial.org/\">http://www.opengeospatial.org/</ulink>."
msgstr ""

352
doc/po/templates/performance_tips.xml.pot Normal file
View file

@ -0,0 +1,352 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: performance_tips.xml:3
#, no-c-format
msgid "Performance tips"
msgstr ""
#. Tag: title
#: performance_tips.xml:6
#, no-c-format
msgid "Small tables of large geometries"
msgstr ""
#. Tag: title
#: performance_tips.xml:9
#, no-c-format
msgid "Problem description"
msgstr ""
#. Tag: para
#: performance_tips.xml:11
#, no-c-format
msgid "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 <ulink url=\"http://www.postgresql.org/docs/current/static/storage-toast.html\">the PostgreSQL Documentation for TOAST</ulink> for more information)."
msgstr ""
#. Tag: para
#: performance_tips.xml:19
#, no-c-format
msgid "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."
msgstr ""
#. Tag: para
#: performance_tips.xml:26
#, no-c-format
msgid "Now issue a query where you use the geometry operator &amp;&amp; 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 &amp;&amp; operator has to fetch every geometry from disk to compare the bounding boxes, thus reading all TOAST pages, too."
msgstr ""
#. Tag: para
#: performance_tips.xml:35
#, no-c-format
msgid "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"
msgstr ""
#. Tag: title
#: performance_tips.xml:43
#, no-c-format
msgid "Workarounds"
msgstr ""
#. Tag: para
#: performance_tips.xml:45
#, no-c-format
msgid "The PostgreSQL people are trying to solve this issue by making the query estimation TOAST-aware. For now, here are two workarounds:"
msgstr ""
#. Tag: para
#: performance_tips.xml:48
#, no-c-format
msgid "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."
msgstr ""
#. Tag: para
#: performance_tips.xml:56
#, no-c-format
msgid "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:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:61
#, no-c-format
msgid ""
"SELECT AddGeometryColumn('myschema','mytable','bbox','4326','GEOMETRY','2'); \n"
"UPDATE mytable SET bbox = ST_Envelope(ST_Force_2d(the_geom));"
msgstr ""
#. Tag: para
#: performance_tips.xml:63
#, no-c-format
msgid "Now change your query to use the &amp;&amp; operator against bbox instead of geom_column, like:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:66
#, no-c-format
msgid ""
"SELECT geom_column \n"
"FROM mytable \n"
"WHERE bbox &amp;&amp; ST_SetSRID('BOX3D(0 0,1 1)'::box3d,4326);"
msgstr ""
#. Tag: para
#: performance_tips.xml:68
#, no-c-format
msgid "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."
msgstr ""
#. Tag: title
#: performance_tips.xml:77
#, no-c-format
msgid "CLUSTERing on geometry indices"
msgstr ""
#. Tag: para
#: performance_tips.xml:79
#, no-c-format
msgid "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.)"
msgstr ""
#. Tag: para
#: performance_tips.xml:89
#, no-c-format
msgid "However, currently PostgreSQL does not allow clustering on PostGIS GIST indices because GIST indices simply ignores NULL values, you get an error message like:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:93
#, no-c-format
msgid ""
"lwgeom=# CLUSTER my_geom_index ON my_table; \n"
"ERROR: cannot cluster when index access method does not handle null values\n"
"HINT: You may be able to work around this by marking column \"the_geom\" NOT NULL."
msgstr ""
#. Tag: para
#: performance_tips.xml:95
#, no-c-format
msgid "As the HINT message tells you, one can work around this deficiency by adding a \"not null\" constraint to the table:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:98
#, no-c-format
msgid ""
"lwgeom=# ALTER TABLE my_table ALTER COLUMN the_geom SET not null; \n"
"ALTER TABLE"
msgstr ""
#. Tag: para
#: performance_tips.xml:100
#, no-c-format
msgid "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."
msgstr ""
#. Tag: title
#: performance_tips.xml:107
#, no-c-format
msgid "Avoiding dimension conversion"
msgstr ""
#. Tag: para
#: performance_tips.xml:109
#, no-c-format
msgid "Sometimes, you happen to have 3D or 4D data in your table, but always access it using OpenGIS compliant ST_AsText() or ST_AsBinary() functions that only output 2D geometries. They do this by internally calling the ST_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:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:116
#, no-c-format
msgid ""
"UPDATE mytable SET the_geom = ST_Force_2d(the_geom); \n"
"VACUUM FULL ANALYZE mytable;"
msgstr ""
#. Tag: para
#: performance_tips.xml:118
#, no-c-format
msgid "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."
msgstr ""
#. Tag: para
#: performance_tips.xml:124
#, no-c-format
msgid "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)&gt;2\" skips re-writing of geometries that already are in 2D."
msgstr ""
#. Tag: title
#: performance_tips.xml:136
#, no-c-format
msgid "Tuning your configuration"
msgstr ""
#. Tag: para
#: performance_tips.xml:138
#, no-c-format
msgid "These tips are taken from Kevin Neufeld's presentation \"Tips for the PostGIS Power User\" at the FOSS4G 2007 conference. Depending on your use of PostGIS (for example, static data and complex analysis vs frequently updated data and lots of users) these changes can provide significant speedups to your queries."
msgstr ""
#. Tag: para
#: performance_tips.xml:144
#, no-c-format
msgid "For a more tips (and better formatting), the original presentation is at <ulink url=\"http://2007.foss4g.org/presentations/view.php?abstract_id=117\"> http://2007.foss4g.org/presentations/view.php?abstract_id=117</ulink>."
msgstr ""
#. Tag: title
#: performance_tips.xml:151
#, no-c-format
msgid "Startup"
msgstr ""
#. Tag: para
#: performance_tips.xml:153
#, no-c-format
msgid "These settings are configured in postgresql.conf:"
msgstr ""
#. Tag: ulink
#: performance_tips.xml:158
#, no-c-format
msgid "checkpoint_segments"
msgstr ""
#. Tag: para
#: performance_tips.xml:163
#, no-c-format
msgid "Maximum number of log file segments between automatic WAL checkpoints (each segment is normally 16MB); default is 3"
msgstr ""
#. Tag: para
#: performance_tips.xml:169
#, no-c-format
msgid "Set to at least 10 or 30 for databases with heavy write activity, or more for large database loads. Another article on the topic worth reading <ulink url=\"http://www.westnet.com/~gsmith/content/postgresql/chkp-bgw-83.htm\">Greg Smith: Checkpoint and Background writer</ulink>"
msgstr ""
#. Tag: para
#: performance_tips.xml:175
#, no-c-format
msgid "Possibly store the xlog on a separate disk device"
msgstr ""
#. Tag: ulink
#: performance_tips.xml:182
#, no-c-format
msgid "constraint_exclusion"
msgstr ""
#. Tag: para
#: performance_tips.xml:187
#, no-c-format
msgid "Default: off (prior to PostgreSQL 8.4 and for PostgreSQL 8.4+ is set to partition)"
msgstr ""
#. Tag: para
#: performance_tips.xml:192
#, no-c-format
msgid "This is generally used for table partitioning. If you are running PostgreSQL versions below 8.4, set to \"on\" to ensure the query planner will optimize as desired. As of PostgreSQL 8.4, the default for this is set to \"partition\" which is ideal for PostgreSQL 8.4 and above since it will force the planner to only analyze tables for constraint consideration if they are in an inherited hierarchy and not pay the planner penalty otherwise."
msgstr ""
#. Tag: ulink
#: performance_tips.xml:202
#, no-c-format
msgid "shared_buffers"
msgstr ""
#. Tag: para
#: performance_tips.xml:207
#, no-c-format
msgid "Default: ~32MB"
msgstr ""
#. Tag: para
#: performance_tips.xml:212
#, no-c-format
msgid "Set to about 1/3 to 3/4 of available RAM"
msgstr ""
#. Tag: title
#: performance_tips.xml:220
#, no-c-format
msgid "Runtime"
msgstr ""
#. Tag: para
#: performance_tips.xml:222
#, no-c-format
msgid "<ulink url=\"http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-WORK-MEM\">work_mem</ulink> (the memory used for sort operations and complex queries)"
msgstr ""
#. Tag: para
#: performance_tips.xml:228
#, no-c-format
msgid "Default: 1MB"
msgstr ""
#. Tag: para
#: performance_tips.xml:233
#, no-c-format
msgid "Adjust up for large dbs, complex queries, lots of RAM"
msgstr ""
#. Tag: para
#: performance_tips.xml:238
#, no-c-format
msgid "Adjust down for many concurrent users or low RAM."
msgstr ""
#. Tag: para
#: performance_tips.xml:243
#, no-c-format
msgid "If you have lots of RAM and few developers:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:245
#, no-c-format
msgid "SET work_mem TO 1200000;"
msgstr ""
#. Tag: para
#: performance_tips.xml:250
#, no-c-format
msgid "<ulink url=\"http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-MAINTENANCE-WORK-MEM\">maintenance_work_mem</ulink> (used for VACUUM, CREATE INDEX, etc.)"
msgstr ""
#. Tag: para
#: performance_tips.xml:256
#, no-c-format
msgid "Default: 16MB"
msgstr ""
#. Tag: para
#: performance_tips.xml:261
#, no-c-format
msgid "Generally too low - ties up I/O, locks objects while swapping memory"
msgstr ""
#. Tag: para
#: performance_tips.xml:266
#, no-c-format
msgid "Recommend 32MB to 256MB on production servers w/lots of RAM, but depends on the # of concurrent users. If you have lots of RAM and few developers:"
msgstr ""
#. Tag: programlisting
#: performance_tips.xml:269
#, no-c-format
msgid "SET maintainence_work_mem TO 1200000;"
msgstr ""

46
doc/po/templates/postgis.xml.pot Normal file
View file

@ -0,0 +1,46 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: postgis.xml:106
#, no-c-format
msgid "PostGIS &last_release_version; Manual"
msgstr ""
#. Tag: affiliation
#: postgis.xml:114
#, no-c-format
msgid "<orgname><ulink url=\"http://www.cleverelephant.ca\">clever elephant</ulink></orgname> <address><city>Victoria</city> <state>British Columbia</state> <country>Canada</country> <email>pramsey@cleverelephant.ca</email></address>"
msgstr ""
#. Tag: para
#: postgis.xml:124
#, no-c-format
msgid "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."
msgstr ""
#. Tag: para
#: postgis.xml:133
#, no-c-format
msgid "This is the manual for version &last_release_version;"
msgstr ""
#. Tag: para
#: postgis.xml:134
#, no-c-format
msgid "This work is licensed under a <ulink url=\"http://creativecommons.org/licenses/by-sa/3.0/\">Creative Commons Attribution-Share Alike 3.0 License</ulink>. Feel free to use this material any way you like, but we ask that you attribute credit to the PostGIS Project and wherever possible, a link back to <ulink url=\"http://www.postgis.org\">http://www.postgis.org</ulink>."
msgstr ""

40
doc/po/templates/reference.xml.pot Normal file
View file

@ -0,0 +1,40 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reference.xml:3
#, no-c-format
msgid "PostGIS Reference"
msgstr ""
#. Tag: para
#: reference.xml:5
#, no-c-format
msgid "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."
msgstr ""
#. Tag: para
#: reference.xml:11
#, no-c-format
msgid "PostGIS has begun a transition from the existing naming convention to an SQL-MM-centric convention. As a result, most of the functions that you know and love have been renamed using the standard spatial type (ST) prefix. Previous functions are still available, though are not listed in this document where updated functions are equivalent. The non ST_ functions not listed in this documentation are deprecated and will be removed in a future release so STOP USING THEM."
msgstr ""
#. Tag: chapter
#: reference.xml:16
#, no-c-format
msgid "&reference_type; &reference_management; &reference_constructor; &reference_accessor; &reference_editor; &reference_output; &reference_operator; &reference_measure; &reference_processing; &reference_lrs; &reference_transaction; &reference_misc; &reference_exception;"
msgstr ""

2757
doc/po/templates/reference_accessor.xml.pot Normal file
View file

File diff suppressed because it is too large Load diff

2343
doc/po/templates/reference_constructor.xml.pot Normal file
View file

File diff suppressed because it is too large Load diff

1916
doc/po/templates/reference_editor.xml.pot Normal file
View file

File diff suppressed because it is too large Load diff

187
doc/po/templates/reference_exception.xml.pot Normal file
View file

@ -0,0 +1,187 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reference_exception.xml:3
#, no-c-format
msgid "Exceptional Functions"
msgstr ""
#. Tag: para
#: reference_exception.xml:4
#, no-c-format
msgid "These functions are rarely used functions that should only be used if your data is corrupted in someway. They are used for troubleshooting corruption and also fixing things that should under normal circumstances, never happen."
msgstr ""
#. Tag: refname
#: reference_exception.xml:9
#, no-c-format
msgid "PostGIS_AddBBox"
msgstr ""
#. Tag: refpurpose
#: reference_exception.xml:11
#, no-c-format
msgid "Add bounding box to the geometry."
msgstr ""
#. Tag: funcprototype
#: reference_exception.xml:16
#, no-c-format
msgid "<funcdef>geometry <function>PostGIS_AddBBox</function></funcdef> <paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: title
#: reference_exception.xml:24 reference_exception.xml:70 reference_exception.xml:119
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: reference_exception.xml:26
#, no-c-format
msgid "Add bounding box to the geometry. This would make bounding box based queries faster, but will increase the size of the geometry."
msgstr ""
#. Tag: para
#: reference_exception.xml:31
#, no-c-format
msgid "Bounding boxes are automatically added to geometries so in general this is not needed unless the generated bounding box somehow becomes corrupted or you have an old install that is lacking bounding boxes. Then you need to drop the old and readd."
msgstr ""
#. Tag: para
#: reference_exception.xml:35 reference_exception.xml:83 reference_exception.xml:124
#, no-c-format
msgid "&curve_support;"
msgstr ""
#. Tag: title
#: reference_exception.xml:40 reference_exception.xml:88 reference_exception.xml:129
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: programlisting
#: reference_exception.xml:42
#, no-c-format
msgid ""
"UPDATE sometable\n"
" SET the_geom = PostGIS_AddBBox(the_geom)\n"
" WHERE PostGIS_HasBBox(the_geom) = false;"
msgstr ""
#. Tag: title
#: reference_exception.xml:47 reference_exception.xml:95 reference_exception.xml:136
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: para
#: reference_exception.xml:49
#, no-c-format
msgid ", <xref linkend=\"PostGIS_HasBBox\"/>"
msgstr ""
#. Tag: refname
#: reference_exception.xml:55
#, no-c-format
msgid "PostGIS_DropBBox"
msgstr ""
#. Tag: refpurpose
#: reference_exception.xml:57
#, no-c-format
msgid "Drop the bounding box cache from the geometry."
msgstr ""
#. Tag: funcprototype
#: reference_exception.xml:62
#, no-c-format
msgid "<funcdef>geometry <function>PostGIS_DropBBox</function></funcdef> <paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_exception.xml:72
#, no-c-format
msgid "Drop the bounding box cache from the geometry. This reduces geometry size, but makes bounding-box based queries slower. It is also used to drop a corrupt bounding box. A tale-tell sign of a corrupt cached bounding box is when your ST_Intersects and other relation queries leave out geometries that rightfully should return true."
msgstr ""
#. Tag: para
#: reference_exception.xml:77
#, no-c-format
msgid "Bounding boxes are automatically added to geometries and improve speed of queries so in general this is not needed unless the generated bounding box somehow becomes corrupted or you have an old install that is lacking bounding boxes. Then you need to drop the old and readd. This kind of corruption has been observed in 8.3-8.3.6 series whereby cached bboxes were not always recalculated when a geometry changed and upgrading to a newer version without a dump reload will not correct already corrupted boxes. So one can manually correct using below and readd the bbox or do a dump reload."
msgstr ""
#. Tag: programlisting
#: reference_exception.xml:90
#, no-c-format
msgid ""
"--This example drops bounding boxes where the cached box is not correct\n"
" --The force to ST_AsBinary before applying Box2D forces a recalculation of the box, and Box2D applied to the table geometry always\n"
" -- returns the cached bounding box.\n"
" UPDATE sometable\n"
" SET the_geom = PostGIS_DropBBox(the_geom)\n"
" WHERE Not (Box2D(ST_AsBinary(the_geom)) = Box2D(the_geom));\n"
"\n"
" UPDATE sometable\n"
" SET the_geom = PostGIS_AddBBox(the_geom)\n"
" WHERE Not PostGIS_HasBBOX(the_geom);"
msgstr ""
#. Tag: para
#: reference_exception.xml:97
#, no-c-format
msgid ", <xref linkend=\"PostGIS_HasBBox\"/>, <xref linkend=\"Box2D\"/>"
msgstr ""
#. Tag: refname
#: reference_exception.xml:104
#, no-c-format
msgid "PostGIS_HasBBox"
msgstr ""
#. Tag: refpurpose
#: reference_exception.xml:106
#, no-c-format
msgid "Returns TRUE if the bbox of this geometry is cached, FALSE otherwise."
msgstr ""
#. Tag: funcprototype
#: reference_exception.xml:111
#, no-c-format
msgid "<funcdef>boolean <function>PostGIS_HasBBox</function></funcdef> <paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_exception.xml:121
#, no-c-format
msgid "Returns TRUE if the bbox of this geometry is cached, FALSE otherwise. Use <xref linkend=\"PostGIS_AddBBox\"/> and <xref linkend=\"PostGIS_DropBBox\"/> to control caching."
msgstr ""
#. Tag: programlisting
#: reference_exception.xml:131
#, no-c-format
msgid ""
"SELECT the_geom\n"
"FROM sometable WHERE PostGIS_HasBBox(the_geom) = false;"
msgstr ""
#. Tag: para
#: reference_exception.xml:138
#, no-c-format
msgid ", <xref linkend=\"PostGIS_DropBBox\"/>"
msgstr ""

636
doc/po/templates/reference_lrs.xml.pot Normal file
View file

@ -0,0 +1,636 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reference_lrs.xml:3
#, no-c-format
msgid "Linear Referencing"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:7
#, no-c-format
msgid "ST_Line_Interpolate_Point"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:9
#, no-c-format
msgid "Returns a point interpolated along a line. Second argument is a float8 between 0 and 1 representing fraction of total length of linestring the point has to be located."
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:15
#, no-c-format
msgid "<funcdef>geometry <function>ST_Line_Interpolate_Point</function></funcdef> <paramdef><type>geometry </type> <parameter>a_linestring</parameter></paramdef> <paramdef><type>float </type> <parameter>a_fraction</parameter></paramdef>"
msgstr ""
#. Tag: title
#: reference_lrs.xml:24 reference_lrs.xml:85 reference_lrs.xml:136 reference_lrs.xml:202 reference_lrs.xml:260 reference_lrs.xml:311 reference_lrs.xml:356 reference_lrs.xml:400
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: reference_lrs.xml:26
#, no-c-format
msgid "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 linestring length the point has to be located."
msgstr ""
#. Tag: para
#: reference_lrs.xml:30 reference_lrs.xml:147
#, no-c-format
msgid "See <xref linkend=\"ST_Line_Locate_Point\"/> for computing the line location nearest to a Point."
msgstr ""
#. Tag: para
#: reference_lrs.xml:34
#, no-c-format
msgid "Since release 1.1.1 this function also interpolates M and Z values (when present), while prior releases set them to 0.0."
msgstr ""
#. Tag: para
#: reference_lrs.xml:38
#, no-c-format
msgid "Availability: 0.8.2, Z and M supported added in 1.1.1"
msgstr ""
#. Tag: para
#: reference_lrs.xml:39 reference_lrs.xml:157 reference_lrs.xml:319 reference_lrs.xml:362 reference_lrs.xml:406
#, no-c-format
msgid "&Z_support;"
msgstr ""
#. Tag: title
#: reference_lrs.xml:44 reference_lrs.xml:101 reference_lrs.xml:161 reference_lrs.xml:225 reference_lrs.xml:276 reference_lrs.xml:323 reference_lrs.xml:366 reference_lrs.xml:410
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: para
#: reference_lrs.xml:50
#, no-c-format
msgid "A linestring with the interpolated point at 20% position (0.20)"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:53
#, no-c-format
msgid ""
"--Return point 20% along 2d line\n"
"SELECT ST_AsEWKT(ST_Line_Interpolate_Point(the_line, 0.20))\n"
" FROM (SELECT ST_GeomFromEWKT('LINESTRING(25 50, 100 125, 150 190)') as the_line) As foo;\n"
" st_asewkt\n"
"----------------\n"
" POINT(51.5974135047432 76.5974135047432)"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:54
#, no-c-format
msgid ""
"--Return point mid-way of 3d line\n"
"SELECT ST_AsEWKT(ST_Line_Interpolate_Point(the_line, 0.5))\n"
" FROM (SELECT ST_GeomFromEWKT('LINESTRING(1 2 3, 4 5 6, 6 7 8)') as the_line) As foo;\n"
"\n"
" st_asewkt\n"
"--------------------\n"
" POINT(3.5 4.5 5.5)\n"
"\n"
"\n"
"--find closest point on a line to a point or other geometry\n"
" SELECT ST_AsText(ST_Line_Interpolate_Point(foo.the_line, ST_Line_Locate_Point(foo.the_line, ST_GeomFromText('POINT(4 3)'))))\n"
"FROM (SELECT ST_GeomFromText('LINESTRING(1 2, 4 5, 6 7)') As the_line) As foo;\n"
" st_astext\n"
"----------------\n"
" POINT(3 4)"
msgstr ""
#. Tag: title
#: reference_lrs.xml:59 reference_lrs.xml:108 reference_lrs.xml:175 reference_lrs.xml:231 reference_lrs.xml:283 reference_lrs.xml:330 reference_lrs.xml:372
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: para
#: reference_lrs.xml:61
#, no-c-format
msgid ", <xref linkend=\"ST_AsEWKT\"/>, <xref linkend=\"ST_Length\"/>, <xref linkend=\"ST_Line_Locate_Point\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:67
#, no-c-format
msgid "ST_Line_Locate_Point"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:69
#, no-c-format
msgid "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 2d line length."
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:76
#, no-c-format
msgid "<funcdef>float <function>ST_Line_Locate_Point</function></funcdef> <paramdef><type>geometry </type> <parameter>a_linestring</parameter></paramdef> <paramdef><type>geometry </type> <parameter>a_point</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:87
#, no-c-format
msgid "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 <link linkend=\"ST_Length2D\">2d line</link> length."
msgstr ""
#. Tag: para
#: reference_lrs.xml:91
#, no-c-format
msgid "You can use the returned location to extract a Point (<xref linkend=\"ST_Line_Interpolate_Point\"/>) or a substring (<xref linkend=\"ST_Line_Substring\"/>)."
msgstr ""
#. Tag: para
#: reference_lrs.xml:94
#, no-c-format
msgid "This is useful for approximating numbers of addresses"
msgstr ""
#. Tag: para
#: reference_lrs.xml:96
#, no-c-format
msgid "Availability: 1.1.0"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:103
#, no-c-format
msgid ""
"--Rough approximation of finding the street number of a point along the street\n"
"--Note the whole foo thing is just to generate dummy data that looks\n"
"--like house centroids and street\n"
"--We use ST_DWithin to exclude\n"
"--houses too far away from the street to be considered on the street\n"
"SELECT ST_AsText(house_loc) As as_text_house_loc,\n"
" startstreet_num +\n"
" CAST( (endstreet_num - startstreet_num)\n"
" * ST_Line_Locate_Point(street_line, house_loc) As integer) As street_num\n"
"FROM\n"
"(SELECT ST_GeomFromText('LINESTRING(1 2, 3 4)') As street_line,\n"
" ST_MakePoint(x*1.01,y*1.03) As house_loc, 10 As startstreet_num,\n"
" 20 As endstreet_num\n"
"FROM generate_series(1,3) x CROSS JOIN generate_series(2,4) As y)\n"
"As foo\n"
"WHERE ST_DWithin(street_line, house_loc, 0.2);\n"
"\n"
" as_text_house_loc | street_num\n"
"-------------------+------------\n"
" POINT(1.01 2.06) | 10\n"
" POINT(2.02 3.09) | 15\n"
" POINT(3.03 4.12) | 20\n"
"\n"
" --find closest point on a line to a point or other geometry\n"
" SELECT ST_AsText(ST_Line_Interpolate_Point(foo.the_line, ST_Line_Locate_Point(foo.the_line, ST_GeomFromText('POINT(4 3)'))))\n"
"FROM (SELECT ST_GeomFromText('LINESTRING(1 2, 4 5, 6 7)') As the_line) As foo;\n"
" st_astext\n"
"----------------\n"
" POINT(3 4)"
msgstr ""
#. Tag: para
#: reference_lrs.xml:110
#, no-c-format
msgid ", <xref linkend=\"ST_Length2D\"/>, <xref linkend=\"ST_Line_Interpolate_Point\"/>, <xref linkend=\"ST_Line_Substring\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:116
#, no-c-format
msgid "ST_Line_Substring"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:118
#, no-c-format
msgid "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."
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:126
#, no-c-format
msgid "<funcdef>geometry <function>ST_Line_Substring</function></funcdef> <paramdef><type>geometry </type> <parameter>a_linestring</parameter></paramdef> <paramdef><type>float </type> <parameter>startfraction</parameter></paramdef> <paramdef><type>float </type> <parameter>endfraction</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:138
#, no-c-format
msgid "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. This only works with LINESTRINGs. To use with contiguous MULTILINESTRINGs use in conjunction with <xref linkend=\"ST_LineMerge\"/>."
msgstr ""
#. Tag: para
#: reference_lrs.xml:144
#, no-c-format
msgid "If 'start' and 'end' have the same value this is equivalent to <xref linkend=\"ST_Line_Interpolate_Point\"/>."
msgstr ""
#. Tag: para
#: reference_lrs.xml:151
#, no-c-format
msgid "Since release 1.1.1 this function also interpolates M and Z values (when present), while prior releases set them to unspecified values."
msgstr ""
#. Tag: para
#: reference_lrs.xml:156
#, no-c-format
msgid "Availability: 1.1.0, Z and M supported added in 1.1.1"
msgstr ""
#. Tag: para
#: reference_lrs.xml:167
#, no-c-format
msgid "A linestring seen with 1/3 midrange overlaid (0.333, 0.666)"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:170
#, no-c-format
msgid ""
"--Return the approximate 1/3 mid-range part of a linestring\n"
"SELECT ST_AsText(ST_Line_SubString(ST_GeomFromText('LINESTRING(25 50, 100 125, 150 190)'), 0.333, 0.666));\n"
"\n"
" st_astext\n"
"------------------------------------------------------------------------------------------------\n"
"LINESTRING(69.2846934853974 94.2846934853974,100 125,111.700356260683 140.210463138888)\n"
"\n"
"--The below example simulates a while loop in\n"
"--SQL using PostgreSQL generate_series() to cut all\n"
"--linestrings in a table to 100 unit segments\n"
"-- of which no segment is longer than 100 units\n"
"-- units are measured in the SRID units of measurement\n"
"-- It also assumes all geometries are LINESTRING or contiguous MULTILINESTRING\n"
"--and no geometry is longer than 100 units*10000\n"
"--for better performance you can reduce the 10000\n"
"--to match max number of segments you expect\n"
"\n"
"SELECT field1, field2, ST_Line_Substring(the_geom, 100.00*n/length,\n"
" CASE\n"
" WHEN 100.00*(n+1) &lt; length THEN 100.00*(n+1)/length\n"
" ELSE 1\n"
" END) As the_geom\n"
"FROM\n"
" (SELECT sometable.field1, sometable.field2,\n"
" ST_LineMerge(sometable.the_geom) AS the_geom,\n"
" ST_Length(sometable.the_geom) As length\n"
" FROM sometable\n"
" ) AS t\n"
"CROSS JOIN generate_series(0,10000) AS n\n"
"WHERE n*100.00/length &lt; 1;"
msgstr ""
#. Tag: para
#: reference_lrs.xml:177
#, no-c-format
msgid ", <xref linkend=\"ST_Line_Interpolate_Point\"/>, <xref linkend=\"ST_LineMerge\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:183
#, no-c-format
msgid "ST_LocateAlong"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:185
#, no-c-format
msgid "<refpurpose>Return a derived geometry collection value with elements that match the specified measure. Polygonal elements are not supported.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:192
#, no-c-format
msgid "<funcdef>geometry <function>ST_LocateAlong</function></funcdef> <paramdef><type>geometry </type> <parameter>ageom_with_measure</parameter></paramdef> <paramdef><type>float </type> <parameter>a_measure</parameter></paramdef> <paramdef choice=\"opt\"><type>float </type> <parameter>offset</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:204
#, no-c-format
msgid "<para>Return a derived geometry collection value with elements that match the specified measure. Polygonal elements are not supported.</para>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:208
#, no-c-format
msgid "If an offset is provided, the resultant will be offset to the left or right of the input line by the specified number of units. A positive offset will be to the left, and a negative one to the right."
msgstr ""
#. Tag: para
#: reference_lrs.xml:213 reference_lrs.xml:266
#, no-c-format
msgid "Semantic is specified by: ISO/IEC CD 13249-3:200x(E) - Text for Continuation CD Editing Meeting"
msgstr ""
#. Tag: para
#: reference_lrs.xml:216
#, no-c-format
msgid "Availability: 1.1.0 by old name ST_Locate_Along_Measure."
msgstr ""
#. Tag: para
#: reference_lrs.xml:217
#, no-c-format
msgid "Changed: 2.0.0 in prior versions this used to be called ST_Locate_Along_Measure. The old name has been deprecated and will be removed in the future but is still available."
msgstr ""
#. Tag: para
#: reference_lrs.xml:218
#, no-c-format
msgid "Use this function only for geometries with an M component"
msgstr ""
#. Tag: para
#: reference_lrs.xml:220 reference_lrs.xml:272
#, no-c-format
msgid "&M_support;"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:226
#, no-c-format
msgid ""
"SELECT ST_AsText(the_geom)\n"
" FROM\n"
" (SELECT ST_LocateAlong(\n"
" ST_GeomFromText('MULTILINESTRINGM((1 2 3, 3 4 2, 9 4 3),\n"
" (1 2 3, 5 4 5))'),3) As the_geom) As foo;\n"
"\n"
" st_asewkt\n"
"-----------------------------------------------------------\n"
" MULTIPOINT M (1 2 3)\n"
"\n"
"--Geometry collections are difficult animals so dump them\n"
"--to make them more digestable\n"
"SELECT ST_AsText((ST_Dump(the_geom)).geom)\n"
" FROM\n"
" (SELECT ST_LocateAlong(\n"
" ST_GeomFromText('MULTILINESTRINGM((1 2 3, 3 4 2, 9 4 3),\n"
" (1 2 3, 5 4 5))'),3) As the_geom) As foo;\n"
"\n"
" st_asewkt\n"
"---------------\n"
" POINTM(1 2 3)\n"
" POINTM(9 4 3)\n"
" POINTM(1 2 3)"
msgstr ""
#. Tag: para
#: reference_lrs.xml:233
#, no-c-format
msgid ", <xref linkend=\"ST_LocateBetween\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:239
#, no-c-format
msgid "ST_LocateBetween"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:241
#, no-c-format
msgid "<refpurpose>Return a derived geometry collection value with elements that match the specified range of measures inclusively. Polygonal elements are not supported.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:248
#, no-c-format
msgid "<funcdef>geometry <function>ST_LocateBetween</function></funcdef> <paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef> <paramdef><type>float </type> <parameter>measure_start</parameter></paramdef> <paramdef><type>float </type> <parameter>measure_end</parameter></paramdef> <paramdef choice=\"opt\"><type>float </type> <parameter>offset</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:262
#, no-c-format
msgid "<para>Return a derived geometry collection value with elements that match the specified range of measures inclusively. Polygonal elements are not supported.</para>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:269
#, no-c-format
msgid "Availability: 1.1.0 by old name ST_Locate_Between_Measures."
msgstr ""
#. Tag: para
#: reference_lrs.xml:270
#, no-c-format
msgid "Changed: 2.0.0 - in prior versions this used to be called ST_Locate_Between_Measures. The old name has been deprecated and will be removed in the future but is still available for backward compatibility."
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:278
#, no-c-format
msgid ""
"SELECT ST_AsText(the_geom)\n"
" FROM\n"
" (SELECT ST_LocateBetween(\n"
" ST_GeomFromText('MULTILINESTRING M ((1 2 3, 3 4 2, 9 4 3),\n"
" (1 2 3, 5 4 5))'),1.5, 3) As the_geom) As foo;\n"
"\n"
" st_asewkt\n"
"------------------------------------------------------------------------\n"
" GEOMETRYCOLLECTION M (LINESTRING M (1 2 3,3 4 2,9 4 3),POINT M (1 2 3))\n"
"\n"
"--Geometry collections are difficult animals so dump them\n"
"--to make them more digestable\n"
"SELECT ST_AsText((ST_Dump(the_geom)).geom)\n"
" FROM\n"
" (SELECT ST_LocateBetween(\n"
" ST_GeomFromText('MULTILINESTRING M ((1 2 3, 3 4 2, 9 4 3),\n"
" (1 2 3, 5 4 5))'),1.5, 3) As the_geom) As foo;\n"
"\n"
" st_asewkt\n"
"--------------------------------\n"
" LINESTRING M (1 2 3,3 4 2,9 4 3)\n"
" POINT M (1 2 3)"
msgstr ""
#. Tag: para
#: reference_lrs.xml:285
#, no-c-format
msgid ", <xref linkend=\"ST_LocateAlong\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:291
#, no-c-format
msgid "ST_LocateBetweenElevations"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:293
#, no-c-format
msgid "Return a derived geometry (collection) value with elements that intersect the specified range of elevations inclusively. Only 3D, 4D LINESTRINGS and MULTILINESTRINGS are supported."
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:300
#, no-c-format
msgid "<funcdef>geometry <function>ST_LocateBetweenElevations</function></funcdef> <paramdef><type>geometry </type> <parameter>geom_mline</parameter></paramdef> <paramdef><type>float </type> <parameter>elevation_start</parameter></paramdef> <paramdef><type>float </type> <parameter>elevation_end</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:313
#, no-c-format
msgid "Return a derived geometry (collection) value with elements that intersect the specified range of elevations inclusively. Only 3D, 3DM LINESTRINGS and MULTILINESTRINGS are supported."
msgstr ""
#. Tag: para
#: reference_lrs.xml:317
#, no-c-format
msgid "Availability: 1.4.0"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:325
#, no-c-format
msgid ""
"SELECT ST_AsEWKT(ST_LocateBetweenElevations(\n"
" ST_GeomFromEWKT('LINESTRING(1 2 3, 4 5 6)'),2,4)) As ewelev;\n"
" ewelev\n"
"----------------------------------------------------------------\n"
" MULTILINESTRING((1 2 3,2 3 4))\n"
"\n"
"SELECT ST_AsEWKT(ST_LocateBetweenElevations(\n"
" ST_GeomFromEWKT('LINESTRING(1 2 6, 4 5 -1, 7 8 9)'),6,9)) As ewelev;\n"
"\n"
" ewelev\n"
"----------------------------------------------------------------\n"
"GEOMETRYCOLLECTION(POINT(1 2 6),LINESTRING(6.1 7.1 6,7 8 9))\n"
"\n"
"--Geometry collections are difficult animals so dump them\n"
"--to make them more digestable\n"
"SELECT ST_AsEWKT((ST_Dump(the_geom)).geom)\n"
" FROM\n"
" (SELECT ST_LocateBetweenElevations(\n"
" ST_GeomFromEWKT('LINESTRING(1 2 6, 4 5 -1, 7 8 9)'),6,9) As the_geom) As foo;\n"
"\n"
" st_asewkt\n"
"--------------------------------\n"
"POINT(1 2 6)\n"
"LINESTRING(6.1 7.1 6,7 8 9)"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:339
#, no-c-format
msgid "ST_InterpolatePoint"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:341
#, no-c-format
msgid "<refpurpose>Return the value of the measure dimension of a geometry at the point closed to the provided point.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:346
#, no-c-format
msgid "<funcdef>float <function>ST_InterpolatePoint</function></funcdef> <paramdef><type>geometry </type> <parameter>line</parameter></paramdef> <paramdef><type>geometry </type> <parameter>point</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:358
#, no-c-format
msgid "<para>Return the value of the measure dimension of a geometry at the point closed to the provided point.</para>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:360
#, no-c-format
msgid "Availability: 2.0.0"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:368
#, no-c-format
msgid ""
"SELECT ST_InterpolatePoint('LINESTRING M (0 0 0, 10 0 20)', 'POINT(5 5)');\n"
" st_interpolatepoint \n"
" ---------------------\n"
" 10"
msgstr ""
#. Tag: para
#: reference_lrs.xml:374
#, no-c-format
msgid ", <xref linkend=\"ST_LocateAlong\"/>, <xref linkend=\"ST_LocateBetween\"/>"
msgstr ""
#. Tag: refname
#: reference_lrs.xml:382
#, no-c-format
msgid "ST_AddMeasure"
msgstr ""
#. Tag: refpurpose
#: reference_lrs.xml:384
#, no-c-format
msgid "<refpurpose>Return a derived geometry with measure elements linearly interpolated between the start and end points. If the geometry has no measure dimension, one is added. If the geometry has a measure dimension, it is over-written with new values. Only LINESTRINGS and MULTILINESTRINGS are supported.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_lrs.xml:389
#, no-c-format
msgid "<funcdef>geometry <function>ST_AddMeasure</function></funcdef> <paramdef><type>geometry </type> <parameter>geom_mline</parameter></paramdef> <paramdef><type>float </type> <parameter>measure_start</parameter></paramdef> <paramdef><type>float </type> <parameter>measure_end</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:402
#, no-c-format
msgid "<para>Return a derived geometry with measure elements linearly interpolated between the start and end points. If the geometry has no measure dimension, one is added. If the geometry has a measure dimension, it is over-written with new values. Only LINESTRINGS and MULTILINESTRINGS are supported.</para>"
msgstr ""
#. Tag: para
#: reference_lrs.xml:404
#, no-c-format
msgid "Availability: 1.5.0"
msgstr ""
#. Tag: programlisting
#: reference_lrs.xml:412
#, no-c-format
msgid ""
"SELECT ST_AsText(ST_AddMeasure(\n"
"ST_GeomFromEWKT('LINESTRING(1 0, 2 0, 4 0)'),1,4)) As ewelev;\n"
" ewelev \n"
"--------------------------------\n"
" LINESTRINGM(1 0 1,2 0 2,4 0 4)\n"
"\n"
"SELECT ST_AsText(ST_AddMeasure(\n"
"ST_GeomFromEWKT('LINESTRING(1 0 4, 2 0 4, 4 0 4)'),10,40)) As ewelev;\n"
" ewelev \n"
"----------------------------------------\n"
" LINESTRING(1 0 4 10,2 0 4 20,4 0 4 40)\n"
"\n"
"SELECT ST_AsText(ST_AddMeasure(\n"
"ST_GeomFromEWKT('LINESTRINGM(1 0 4, 2 0 4, 4 0 4)'),10,40)) As ewelev;\n"
" ewelev \n"
"----------------------------------------\n"
" LINESTRINGM(1 0 10,2 0 20,4 0 40)\n"
" \n"
"SELECT ST_AsText(ST_AddMeasure(\n"
"ST_GeomFromEWKT('MULTILINESTRINGM((1 0 4, 2 0 4, 4 0 4),(1 0 4, 2 0 4, 4 0 4))'),10,70)) As ewelev;\n"
" ewelev \n"
"-----------------------------------------------------------------\n"
" MULTILINESTRINGM((1 0 10,2 0 20,4 0 40),(1 0 40,2 0 50,4 0 70))"
msgstr ""

854
doc/po/templates/reference_management.xml.pot Normal file
View file

@ -0,0 +1,854 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reference_management.xml:3
#, no-c-format
msgid "Management Functions"
msgstr ""
#. Tag: refname
#: reference_management.xml:7
#, no-c-format
msgid "AddGeometryColumn"
msgstr ""
#. Tag: refpurpose
#: reference_management.xml:9
#, no-c-format
msgid "Adds a geometry column to an existing table of attributes. By default uses type modifier to define rather than constraints. Pass in false for use_typmod to get old check constraint based behavior"
msgstr ""
#. Tag: funcsynopsis
#: reference_management.xml:15
#, no-c-format
msgid "<funcprototype> <funcdef>text <function>AddGeometryColumn</function></funcdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> <paramdef><type>integer </type> <parameter>srid</parameter></paramdef> <paramdef><type>varchar </type> <parameter>type</parameter></paramdef> <paramdef><type>integer </type> <parameter>dimension</parameter></paramdef> <paramdef choice=\"opt\"><type>boolean </type> <parameter>use_typmod=true</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>text <function>AddGeometryColumn</function></funcdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> <paramdef><type>integer </type> <parameter>srid</parameter></paramdef> <paramdef><type>varchar </type> <parameter>type</parameter></paramdef> <paramdef><type>integer </type> <parameter>dimension</parameter></paramdef> <paramdef choice=\"opt\"><type>boolean </type> <parameter>use_typmod=true</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>text <function>AddGeometryColumn</function></funcdef> <paramdef><type>varchar </type> <parameter>catalog_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> <paramdef><type>integer </type> <parameter>srid</parameter></paramdef> <paramdef><type>varchar </type> <parameter>type</parameter></paramdef> <paramdef><type>integer </type> <parameter>dimension</parameter></paramdef> <paramdef choice=\"opt\"><type>boolean </type> <parameter>use_typmod=true</parameter></paramdef> </funcprototype>"
msgstr ""
#. Tag: title
#: reference_management.xml:92 reference_management.xml:188 reference_management.xml:254 reference_management.xml:298 reference_management.xml:344 reference_management.xml:386 reference_management.xml:427 reference_management.xml:458 reference_management.xml:499 reference_management.xml:540 reference_management.xml:583 reference_management.xml:631 reference_management.xml:677 reference_management.xml:726 reference_management.xml:862
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: reference_management.xml:94
#, no-c-format
msgid "Adds a geometry column to an existing table of attributes. The <varname>schema_name</varname> is the name of the table schema. The <varname>srid</varname> must be an integer value reference to an entry in the SPATIAL_REF_SYS table. The <varname>type</varname> must be a string corresponding to the geometry type, eg, 'POLYGON' or 'MULTILINESTRING' . An error is thrown if the schemaname doesn't exist (or not visible in the current search_path) or the specified SRID, geometry type, or dimension is invalid."
msgstr ""
#. Tag: para
#: reference_management.xml:104
#, no-c-format
msgid "Changed: 2.0.0 This function no longer updates geometry_columns since geometry_columns is a view that reads from system catalogs. It by default also does not create constraints, but instead uses the built in type modifier behavior of PostgreSQL. So for example building a wgs84 POINT column with this function is now equivalent to: <code>ALTER TABLE some_table ADD COLUMN geom geometry(Point,4326);</code>"
msgstr ""
#. Tag: para
#: reference_management.xml:107
#, no-c-format
msgid "Changed: 2.0.0 If you require the old behavior of constraints use the default <varname>use_typmod</varname>, but set it to false."
msgstr ""
#. Tag: para
#: reference_management.xml:111
#, no-c-format
msgid "Changed: 2.0.0 Views can no longer be manually registered in geometry_columns, however views built against geometry typmod tables geometries and used without wrapper functions will register themselves correctly because they inherit the typmod behavior of their parent table column. Views that use geometry functions that output other geometries will need to be cast to typmod geometries for these view geometry columns to be registered correctly in geometry_columns. Refer to <xref linkend=\"Manual_Register_Spatial_Column\"/>."
msgstr ""
#. Tag: para
#: reference_management.xml:117 reference_management.xml:194
#, no-c-format
msgid "&sfs_compliant;"
msgstr ""
#. Tag: para
#: reference_management.xml:118 reference_management.xml:195 reference_management.xml:868
#, no-c-format
msgid "&Z_support;"
msgstr ""
#. Tag: para
#: reference_management.xml:119 reference_management.xml:196 reference_management.xml:869
#, no-c-format
msgid "&curve_support;"
msgstr ""
#. Tag: para
#: reference_management.xml:120
#, no-c-format
msgid "Enhanced: 2.0.0 use_typmod argument introduced. Defaults to creating typmod geometry column instead of constraint-based."
msgstr ""
#. Tag: title
#: reference_management.xml:124 reference_management.xml:203 reference_management.xml:267 reference_management.xml:306 reference_management.xml:351 reference_management.xml:393 reference_management.xml:433 reference_management.xml:464 reference_management.xml:506 reference_management.xml:548 reference_management.xml:600 reference_management.xml:646 reference_management.xml:683 reference_management.xml:784
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: programlisting
#: reference_management.xml:126
#, no-c-format
msgid ""
"-- Create schema to hold data\n"
"CREATE SCHEMA my_schema;\n"
"-- Create a new simple PostgreSQL table\n"
"CREATE TABLE my_schema.my_spatial_table (id serial);\n"
"\n"
"-- Describing the table shows a simple table with a single \"id\" column.\n"
"postgis=# \\d my_schema.my_spatial_table\n"
" Table \"my_schema.my_spatial_table\"\n"
" Column | Type | Modifiers\n"
"--------+---------+-------------------------------------------------------------------------\n"
" id | integer | not null default nextval('my_schema.my_spatial_table_id_seq'::regclass)\n"
"\n"
"-- Add a spatial column to the table\n"
"SELECT AddGeometryColumn ('my_schema','my_spatial_table','geom',4326,'POINT',2);\n"
"\n"
"-- Add a point using the old constraint based behavior\n"
"SELECT AddGeometryColumn ('my_schema','my_spatial_table','geom_c',4326,'POINT',2, false);\n"
"\n"
"--Add a curvepolygon using old constraint behavior\n"
"SELECT AddGeometryColumn ('my_schema','my_spatial_table','geomcp_c',4326,'CURVEPOLYGON',2, false);\n"
"\n"
"-- Describe the table again reveals the addition of a new geometry columns.\n"
"\\d my_schema.my_spatial_table\n"
" addgeometrycolumn \n"
"-------------------------------------------------------------------------\n"
" my_schema.my_spatial_table.geomcp_c SRID:4326 TYPE:CURVEPOLYGON DIMS:2 \n"
"(1 row)\n"
"\n"
" Table \"my_schema.my_spatial_table\"\n"
" Column | Type | Modifiers \n"
"----------+----------------------+-------------------------------------------------------------------------\n"
" id | integer | not null default nextval('my_schema.my_spatial_table_id_seq'::regclass)\n"
" geom | geometry(Point,4326) | \n"
" geom_c | geometry | \n"
" geomcp_c | geometry | \n"
"Check constraints:\n"
" \"enforce_dims_geom_c\" CHECK (st_ndims(geom_c) = 2)\n"
" \"enforce_dims_geomcp_c\" CHECK (st_ndims(geomcp_c) = 2)\n"
" \"enforce_geotype_geom_c\" CHECK (geometrytype(geom_c) = 'POINT'::text OR geom_c IS NULL)\n"
" \"enforce_geotype_geomcp_c\" CHECK (geometrytype(geomcp_c) = 'CURVEPOLYGON'::text OR geomcp_c IS NULL)\n"
" \"enforce_srid_geom_c\" CHECK (st_srid(geom_c) = 4326)\n"
" \"enforce_srid_geomcp_c\" CHECK (st_srid(geomcp_c) = 4326)\n"
" \n"
"-- geometry_columns view also registers the new columns --\n"
"SELECT f_geometry_column As col_name, type, srid, coord_dimension As ndims \n"
" FROM geometry_columns\n"
" WHERE f_table_name = 'my_spatial_table' AND f_table_schema = 'my_schema';\n"
"\n"
" col_name | type | srid | ndims \n"
"----------+--------------+------+-------\n"
" geom | Point | 4326 | 2\n"
" geom_c | Point | 4326 | 2\n"
" geomcp_c | CurvePolygon | 4326 | 2"
msgstr ""
#. Tag: title
#: reference_management.xml:130 reference_management.xml:208 reference_management.xml:272 reference_management.xml:312 reference_management.xml:357 reference_management.xml:399 reference_management.xml:470 reference_management.xml:512 reference_management.xml:554 reference_management.xml:606 reference_management.xml:652 reference_management.xml:689 reference_management.xml:873
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: para
#: reference_management.xml:132
#, no-c-format
msgid ", <xref linkend=\"DropGeometryTable\"/>, <xref linkend=\"geometry_columns\"/>, <xref linkend=\"Manual_Register_Spatial_Column\"/>"
msgstr ""
#. Tag: refname
#: reference_management.xml:138
#, no-c-format
msgid "DropGeometryColumn"
msgstr ""
#. Tag: refpurpose
#: reference_management.xml:140
#, no-c-format
msgid "Removes a geometry column from a spatial table."
msgstr ""
#. Tag: funcsynopsis
#: reference_management.xml:145
#, no-c-format
msgid "<funcprototype> <funcdef>text <function>DropGeometryColumn</function></funcdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>text <function>DropGeometryColumn</function></funcdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>text <function>DropGeometryColumn</function></funcdef> <paramdef><type>varchar </type> <parameter>catalog_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> </funcprototype>"
msgstr ""
#. Tag: para
#: reference_management.xml:190
#, no-c-format
msgid "Removes a geometry column from a spatial table. Note that schema_name will need to match the f_table_schema field of the table's row in the geometry_columns table."
msgstr ""
#. Tag: para
#: reference_management.xml:198
#, no-c-format
msgid "Changed: 2.0.0 This function is provided for backward compatibility. Now that since geometry_columns is now a view against the system catalogs, you can drop a geometry column like any other table column using <code>ALTER TABLE</code>"
msgstr ""
#. Tag: programlisting
#: reference_management.xml:205
#, no-c-format
msgid ""
"SELECT DropGeometryColumn ('my_schema','my_spatial_table','geom');\n"
" ----RESULT output ---\n"
" dropgeometrycolumn\n"
"------------------------------------------------------\n"
" my_schema.my_spatial_table.geom effectively removed.\n"
" \n"
"-- In PostGIS 2.0+ the above is also equivalent to the standard\n"
"-- the standard alter table. Both will deregister from geometry_columns\n"
"ALTER TABLE my_schema.my_spatial_table DROP column geom;"
msgstr ""
#. Tag: para
#: reference_management.xml:210
#, no-c-format
msgid ", <xref linkend=\"DropGeometryTable\"/>, <xref linkend=\"geometry_columns\"/>"
msgstr ""
#. Tag: refname
#: reference_management.xml:216
#, no-c-format
msgid "DropGeometryTable"
msgstr ""
#. Tag: refpurpose
#: reference_management.xml:218
#, no-c-format
msgid "Drops a table and all its references in geometry_columns."
msgstr ""
#. Tag: funcsynopsis
#: reference_management.xml:223
#, no-c-format
msgid "<funcprototype> <funcdef>boolean <function>DropGeometryTable</function></funcdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>boolean <function>DropGeometryTable</function></funcdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>boolean <function>DropGeometryTable</function></funcdef> <paramdef><type>varchar </type> <parameter>catalog_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> </funcprototype>"
msgstr ""
#. Tag: para
#: reference_management.xml:256
#, no-c-format
msgid "Drops a table and all its references in geometry_columns. Note: uses current_schema() on schema-aware pgsql installations if schema is not provided."
msgstr ""
#. Tag: para
#: reference_management.xml:261
#, no-c-format
msgid "Changed: 2.0.0 This function is provided for backward compatibility. Now that since geometry_columns is now a view against the system catalogs, you can drop a table with geometry columns like any other table using <code>DROP TABLE</code>"
msgstr ""
#. Tag: programlisting
#: reference_management.xml:269
#, no-c-format
msgid ""
"SELECT DropGeometryTable ('my_schema','my_spatial_table');\n"
"----RESULT output ---\n"
"my_schema.my_spatial_table dropped.\n"
" \n"
"-- The above is now equivalent to --\n"
"DROP TABLE my_schema.my_spatial_table;"
msgstr ""
#. Tag: para
#: reference_management.xml:274
#, no-c-format
msgid ", <xref linkend=\"DropGeometryColumn\"/>, <xref linkend=\"geometry_columns\"/>"
msgstr ""
#. Tag: refname
#: reference_management.xml:281
#, no-c-format
msgid "PostGIS_Full_Version"
msgstr ""
#. Tag: refpurpose
#: reference_management.xml:283
#, no-c-format
msgid "Reports full postgis version and build configuration infos."
msgstr ""
#. Tag: funcprototype
#: reference_management.xml:289
#, no-c-format
msgid "<funcdef>text <function>PostGIS_Full_Version</function></funcdef> <paramdef></paramdef>"
msgstr ""
#. Tag: para
#: reference_management.xml:300
#, no-c-format
msgid "Reports full postgis version and build configuration infos. Also informs about synchronization between libraries and scripts suggesting upgrades as needed."
msgstr ""
#. Tag: programlisting
#: reference_management.xml:308
#, no-c-format
msgid ""
"SELECT PostGIS_Full_Version();\n"
" postgis_full_version\n"
"----------------------------------------------------------------------------------\n"
" POSTGIS=\"1.3.3\" GEOS=\"3.1.0-CAPI-1.5.0\" PROJ=\"Rel. 4.4.9, 29 Oct 2004\" USE_STATS\n"
"(1 row)"
msgstr ""
#. Tag: para
#: reference_management.xml:314
#, no-c-format
msgid ", <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref linkend=\"PostGIS_Lib_Version\"/>, <xref linkend=\"PostGIS_LibXML_Version\"/>, <xref linkend=\"PostGIS_PROJ_Version\"/>, <xref linkend=\"PostGIS_Version\"/>"
msgstr ""
#. Tag: refname
#: reference_management.xml:327
#, no-c-format
msgid "PostGIS_GEOS_Version"
msgstr ""
#. Tag: refpurpose
#: reference_management.xml:329
#, no-c-format
msgid "Returns the version number of the GEOS library."
msgstr ""
#. Tag: funcprototype
#: reference_management.xml:335
#, no-c-format
msgid "<funcdef>text <function>PostGIS_GEOS_Version</function></funcdef> <paramdef></paramdef>"
msgstr ""
#. Tag: para
#: reference_management.xml:346
#, no-c-format
msgid "Returns the version number of the GEOS library, or <varname>NULL</varname> if GEOS support is not enabled."
msgstr ""
#. Tag: programlisting
#: reference_management.xml:353
#, no-c-format
msgid ""
"SELECT PostGIS_GEOS_Version();\n"
" postgis_geos_version\n"
"----------------------\n"
" 3.1.0-CAPI-1.5.0\n"
"(1 row)"
msgstr ""
#. Tag: para
#: reference_management.xml:359
#, no-c-format
msgid ", <xref linkend=\"PostGIS_Lib_Version\"/>, <xref linkend=\"PostGIS_LibXML_Version\"/>, <xref linkend=\"PostGIS_PROJ_Version\"/>, <xref linkend=\"PostGIS_Version\"/>"
msgstr ""
#. Tag: refname
#: reference_management.xml:369
#, no-c-format
msgid "PostGIS_LibXML_Version"
msgstr ""
#. Tag: refpurpose
#: reference_management.xml:371
#, no-c-format
msgid "Returns the version number of the libxml2 library."
msgstr ""
#. Tag: funcprototype
#: reference_management.xml:377
#, no-c-format
msgid "<funcdef>text <function>PostGIS_LibXML_Version</function></funcdef> <paramdef></paramdef>"
msgstr ""
#. Tag: para
#: reference_management.xml:388
#, no-c-format
msgid "Returns the version number of the LibXML2 library."
msgstr ""
#. Tag: para
#: reference_management.xml:389
#, no-c-format
msgid "Availability: 1.5"
msgstr ""
#. Tag: programlisting
#: reference_management.xml:395
#, no-c-format
msgid ""
"SELECT PostGIS_LibXML_Version();\n"
" postgis_libxml_version\n"
"----------------------\n"
" 2.7.6\n"
"(1 row)"
msgstr ""
#. Tag: para
#: reference_management.xml:401
#, no-c-format
msgid ", <xref linkend=\"PostGIS_Lib_Version\"/>, <xref linkend=\"PostGIS_PROJ_Version\"/>, <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref linkend=\"PostGIS_Version\"/>"
msgstr ""
#. Tag: refname
#: reference_management.xml:411
#, no-c-format
msgid "PostGIS_Lib_Build_Date"
msgstr ""
#. Tag: refpurpose
#: reference_management.xml:413
#, no-c-format
msgid "<refpurpose>Returns build date of the PostGIS library.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_management.xml:418
#, no-c-format
msgid "<funcdef>text <function>PostGIS_Lib_Build_Date</function></funcdef> <paramdef></paramdef>"
msgstr ""
#. Tag: para
#: reference_management.xml:429
#, no-c-format
msgid "<para>Returns build date of the PostGIS library.</para>"
msgstr ""
#. Tag: programlisting
#: reference_management.xml:435
#, no-c-format
msgid ""
"SELECT PostGIS_Lib_Build_Date();\n"
" postgis_lib_build_date\n"
"------------------------\n"
" 2008-06-21 17:53:21\n"
"(1 row)"
msgstr ""
#. Tag: refname
#: reference_management.xml:441
#, no-c-format
msgid "PostGIS_Lib_Version"
msgstr ""
#. Tag: refpurpose
#: reference_management.xml:443
#, no-c-format
msgid "<refpurpose>Returns the version number of the PostGIS library.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_management.xml:449
#, no-c-format
msgid "<funcdef>text <function>PostGIS_Lib_Version</function></funcdef> <paramdef></paramdef>"
msgstr ""
#. Tag: para
#: reference_management.xml:460
#, no-c-format
msgid "<para>Returns the version number of the PostGIS library.</para>"
msgstr ""
#. Tag: programlisting
#: reference_management.xml:466
#, no-c-format
msgid ""
"SELECT PostGIS_Lib_Version();\n"
" postgis_lib_version\n"
"---------------------\n"
" 1.3.3\n"
"(1 row)"
msgstr ""
#. Tag: para
#: reference_management.xml:472
#, no-c-format
msgid ", <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref linkend=\"PostGIS_LibXML_Version\"/>, <xref linkend=\"PostGIS_PROJ_Version\"/>, <xref linkend=\"PostGIS_Version\"/>"
msgstr ""
#. Tag: refname
#: reference_management.xml:482
#, no-c-format
msgid "PostGIS_PROJ_Version"
msgstr ""
#. Tag: refpurpose
#: reference_management.xml:484
#, no-c-format
msgid "Returns the version number of the PROJ4 library."
msgstr ""
#. Tag: funcprototype
#: reference_management.xml:490
#, no-c-format
msgid "<funcdef>text <function>PostGIS_PROJ_Version</function></funcdef> <paramdef></paramdef>"
msgstr ""
#. Tag: para
#: reference_management.xml:501
#, no-c-format
msgid "Returns the version number of the PROJ4 library, or <varname>NULL</varname> if PROJ4 support is not enabled."
msgstr ""
#. Tag: programlisting
#: reference_management.xml:508
#, no-c-format
msgid ""
"SELECT PostGIS_PROJ_Version();\n"
" postgis_proj_version\n"
"-------------------------\n"
" Rel. 4.4.9, 29 Oct 2004\n"
"(1 row)"
msgstr ""
#. Tag: para
#: reference_management.xml:514 reference_management.xml:556
#, no-c-format
msgid ", <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref linkend=\"PostGIS_Lib_Version\"/>, <xref linkend=\"PostGIS_LibXML_Version\"/>, <xref linkend=\"PostGIS_Version\"/>"
msgstr ""
#. Tag: refname
#: reference_management.xml:524
#, no-c-format
msgid "PostGIS_Scripts_Build_Date"
msgstr ""
#. Tag: refpurpose
#: reference_management.xml:526
#, no-c-format
msgid "<refpurpose>Returns build date of the PostGIS scripts.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_management.xml:531
#, no-c-format
msgid "<funcdef>text <function>PostGIS_Scripts_Build_Date</function></funcdef> <paramdef></paramdef>"
msgstr ""
#. Tag: para
#: reference_management.xml:542
#, no-c-format
msgid "<para>Returns build date of the PostGIS scripts.</para>"
msgstr ""
#. Tag: para
#: reference_management.xml:544
#, no-c-format
msgid "Availability: 1.0.0RC1"
msgstr ""
#. Tag: programlisting
#: reference_management.xml:550
#, no-c-format
msgid ""
"SELECT PostGIS_Scripts_Build_Date();\n"
" postgis_scripts_build_date\n"
"-------------------------\n"
" 2007-08-18 09:09:26\n"
"(1 row)"
msgstr ""
#. Tag: refname
#: reference_management.xml:566
#, no-c-format
msgid "PostGIS_Scripts_Installed"
msgstr ""
#. Tag: refpurpose
#: reference_management.xml:568
#, no-c-format
msgid "<refpurpose>Returns version of the postgis scripts installed in this database.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_management.xml:574
#, no-c-format
msgid "<funcdef>text <function>PostGIS_Scripts_Installed</function></funcdef> <paramdef></paramdef>"
msgstr ""
#. Tag: para
#: reference_management.xml:585
#, no-c-format
msgid "<para>Returns version of the postgis scripts installed in this database.</para>"
msgstr ""
#. Tag: para
#: reference_management.xml:589
#, no-c-format
msgid "If the output of this function doesn't match the output of <xref linkend=\"PostGIS_Scripts_Released\"/> you probably missed to properly upgrade an existing database. See the <link linkend=\"upgrading\">Upgrading</link> section for more info."
msgstr ""
#. Tag: para
#: reference_management.xml:596 reference_management.xml:642
#, no-c-format
msgid "Availability: 0.9.0"
msgstr ""
#. Tag: programlisting
#: reference_management.xml:602
#, no-c-format
msgid ""
"SELECT PostGIS_Scripts_Installed();\n"
" postgis_scripts_installed\n"
"-------------------------\n"
" 1.5.0SVN\n"
"(1 row)"
msgstr ""
#. Tag: para
#: reference_management.xml:608
#, no-c-format
msgid ", <xref linkend=\"PostGIS_Scripts_Released\"/>, <xref linkend=\"PostGIS_Version\"/>"
msgstr ""
#. Tag: refname
#: reference_management.xml:614
#, no-c-format
msgid "PostGIS_Scripts_Released"
msgstr ""
#. Tag: refpurpose
#: reference_management.xml:616
#, no-c-format
msgid "<refpurpose>Returns the version number of the postgis.sql script released with the installed postgis lib.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_management.xml:622
#, no-c-format
msgid "<funcdef>text <function>PostGIS_Scripts_Released</function></funcdef> <paramdef></paramdef>"
msgstr ""
#. Tag: para
#: reference_management.xml:633
#, no-c-format
msgid "<para>Returns the version number of the postgis.sql script released with the installed postgis lib.</para>"
msgstr ""
#. Tag: para
#: reference_management.xml:637
#, no-c-format
msgid "Starting with version 1.1.0 this function returns the same value of <xref linkend=\"PostGIS_Lib_Version\"/>. Kept for backward compatibility."
msgstr ""
#. Tag: programlisting
#: reference_management.xml:648
#, no-c-format
msgid ""
"SELECT PostGIS_Scripts_Released();\n"
" postgis_scripts_released\n"
"-------------------------\n"
" 1.3.4SVN\n"
"(1 row)"
msgstr ""
#. Tag: para
#: reference_management.xml:654
#, no-c-format
msgid ", <xref linkend=\"PostGIS_Scripts_Installed\"/>, <xref linkend=\"PostGIS_Lib_Version\"/>"
msgstr ""
#. Tag: refname
#: reference_management.xml:660
#, no-c-format
msgid "PostGIS_Version"
msgstr ""
#. Tag: refpurpose
#: reference_management.xml:662
#, no-c-format
msgid "<refpurpose>Returns PostGIS version number and compile-time options.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_management.xml:668
#, no-c-format
msgid "<funcdef>text <function>PostGIS_Version</function></funcdef> <paramdef></paramdef>"
msgstr ""
#. Tag: para
#: reference_management.xml:679
#, no-c-format
msgid "<para>Returns PostGIS version number and compile-time options.</para>"
msgstr ""
#. Tag: programlisting
#: reference_management.xml:685
#, no-c-format
msgid ""
"SELECT PostGIS_Version();\n"
" postgis_version\n"
"---------------------------------------\n"
" 1.3 USE_GEOS=1 USE_PROJ=1 USE_STATS=1\n"
"(1 row)"
msgstr ""
#. Tag: para
#: reference_management.xml:691
#, no-c-format
msgid ", <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref linkend=\"PostGIS_Lib_Version\"/>, <xref linkend=\"PostGIS_LibXML_Version\"/>, <xref linkend=\"PostGIS_PROJ_Version\"/>"
msgstr ""
#. Tag: refname
#: reference_management.xml:701
#, no-c-format
msgid "Populate_Geometry_Columns"
msgstr ""
#. Tag: refpurpose
#: reference_management.xml:703
#, no-c-format
msgid "Ensures geometry columns are defined with type modifiers or have appropriate spatial constraints This ensures they will be registered correctly in <varname>geometry_columns</varname> view. By default will convert all geometry columns with no type modifier to ones with type modifiers. To get old behavior set <varname>use_typmod=false</varname>"
msgstr ""
#. Tag: funcsynopsis
#: reference_management.xml:709
#, no-c-format
msgid "<funcprototype> <funcdef>text <function>Populate_Geometry_Columns</function></funcdef> <paramdef><type>boolean </type> <parameter>use_typmod=true</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>int <function>Populate_Geometry_Columns</function></funcdef> <paramdef><type>oid</type> <parameter>relation_oid</parameter></paramdef> <paramdef><type>boolean </type> <parameter>use_typmod=true</parameter></paramdef> </funcprototype>"
msgstr ""
#. Tag: para
#: reference_management.xml:728
#, no-c-format
msgid "Ensures geometry columns have appropriate type modifiers or spatial constraints to ensure they are registered correctly in <varname>geometry_columns</varname> table."
msgstr ""
#. Tag: para
#: reference_management.xml:730
#, no-c-format
msgid "For backwards compatibility and for spatial needs such as tble inheritance where each child table may have different geometry type, the old check constraint behavior is still supported. If you need the old behavior, you need to pass in the new optional argument as false <varname>use_typmod=false</varname>. When this is done geometry columns will be created with no type modifiers but will have 3 constraints defined. In particular, this means that every geometry column belonging to a table has at least three constraints:"
msgstr ""
#. Tag: para
#: reference_management.xml:738
#, no-c-format
msgid "<varname>enforce_dims_the_geom</varname> - ensures every geometry has the same dimension (see <xref linkend=\"ST_NDims\"/>)"
msgstr ""
#. Tag: para
#: reference_management.xml:744
#, no-c-format
msgid "<varname>enforce_geotype_the_geom</varname> - ensures every geometry is of the same type (see <xref linkend=\"GeometryType\"/>)"
msgstr ""
#. Tag: para
#: reference_management.xml:750
#, no-c-format
msgid "<varname>enforce_srid_the_geom</varname> - ensures every geometry is in the same projection (see <xref linkend=\"ST_SRID\"/>)"
msgstr ""
#. Tag: para
#: reference_management.xml:756
#, no-c-format
msgid "If a table <varname>oid</varname> is provided, this function tries to determine the srid, dimension, and geometry type of all geometry columns in the table, adding constraints as necessary. If successful, an appropriate row is inserted into the geometry_columns table, otherwise, the exception is caught and an error notice is raised describing the problem."
msgstr ""
#. Tag: para
#: reference_management.xml:763
#, no-c-format
msgid "If the <varname>oid</varname> of a view is provided, as with a table oid, this function tries to determine the srid, dimension, and type of all the geometries in the view, inserting appropriate entries into the <varname>geometry_columns</varname> table, but nothing is done to enforce constraints."
msgstr ""
#. Tag: para
#: reference_management.xml:769
#, no-c-format
msgid "The parameterless variant is a simple wrapper for the parameterized variant that first truncates and repopulates the geometry_columns table for every spatial table and view in the database, adding spatial constraints to tables where appropriate. It returns a summary of the number of geometry columns detected in the database and the number that were inserted into the <varname>geometry_columns</varname> table. The parameterized version simply returns the number of rows inserted into the <varname>geometry_columns</varname> table."
msgstr ""
#. Tag: para
#: reference_management.xml:777
#, no-c-format
msgid "Availability: 1.4.0"
msgstr ""
#. Tag: para
#: reference_management.xml:778
#, no-c-format
msgid "Changed: 2.0.0 By default, now uses type modifiers instead of check constraints to constrain geometry types. You can still use check constraint behavior instead by using the new <varname>use_typmod</varname> and setting it to false."
msgstr ""
#. Tag: para
#: reference_management.xml:780
#, no-c-format
msgid "Enhanced: 2.0.0 <varname>use_typmod</varname> optional argument was introduced that allows controlling if columns are created with typmodifiers or with check constraints."
msgstr ""
#. Tag: programlisting
#: reference_management.xml:786
#, no-c-format
msgid ""
"CREATE TABLE public.myspatial_table(gid serial, geom geometry);\n"
"INSERT INTO myspatial_table(geom) VALUES(ST_GeomFromText('LINESTRING(1 2, 3 4)',4326) );\n"
"-- This will now use typ modifiers. For this to work, there must exist data\n"
"SELECT Populate_Geometry_Columns('public.myspatial_table'::regclass);\n"
"\n"
"populate_geometry_columns\n"
"--------------------------\n"
" 1\n"
" \n"
" \n"
"\\d myspatial_table\n"
"\n"
" Table \"public.myspatial_table\"\n"
" Column | Type | Modifiers \n"
"--------+---------------------------+---------------------------------------------------------------\n"
" gid | integer | not null default nextval('myspatial_table_gid_seq'::regclass)\n"
" geom | geometry(LineString,4326) |"
msgstr ""
#. Tag: programlisting
#: reference_management.xml:788
#, no-c-format
msgid ""
"-- This will change the geometry columns to use constraints if they are not typmod or have constraints already. \n"
"--For this to work, there must exist data\n"
"CREATE TABLE public.myspatial_table_cs(gid serial, geom geometry);\n"
"INSERT INTO myspatial_table_cs(geom) VALUES(ST_GeomFromText('LINESTRING(1 2, 3 4)',4326) );\n"
"SELECT Populate_Geometry_Columns('public.myspatial_table_cs'::regclass, false);\n"
"populate_geometry_columns\n"
"--------------------------\n"
" 1\n"
"\\d myspatial_table_cs\n"
"\n"
" Table \"public.myspatial_table_cs\"\n"
" Column | Type | Modifiers \n"
"--------+----------+------------------------------------------------------------------\n"
" gid | integer | not null default nextval('myspatial_table_cs_gid_seq'::regclass)\n"
" geom | geometry | \n"
"Check constraints:\n"
" \"enforce_dims_geom\" CHECK (st_ndims(geom) = 2)\n"
" \"enforce_geotype_geom\" CHECK (geometrytype(geom) = 'LINESTRING'::text OR geom IS NULL)\n"
" \"enforce_srid_geom\" CHECK (st_srid(geom) = 4326)"
msgstr ""
#. Tag: refname
#: reference_management.xml:803
#, no-c-format
msgid "UpdateGeometrySRID"
msgstr ""
#. Tag: refpurpose
#: reference_management.xml:805
#, no-c-format
msgid "Updates the SRID of all features in a geometry column, geometry_columns metadata and srid table constraint"
msgstr ""
#. Tag: funcsynopsis
#: reference_management.xml:810
#, no-c-format
msgid "<funcprototype> <funcdef>text <function>UpdateGeometrySRID</function></funcdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> <paramdef><type>integer </type> <parameter>srid</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>text <function>UpdateGeometrySRID</function></funcdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> <paramdef><type>integer </type> <parameter>srid</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>text <function>UpdateGeometrySRID</function></funcdef> <paramdef><type>varchar </type> <parameter>catalog_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> <paramdef><type>integer </type> <parameter>srid</parameter></paramdef> </funcprototype>"
msgstr ""
#. Tag: para
#: reference_management.xml:864
#, no-c-format
msgid "Updates 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."
msgstr ""

3886
doc/po/templates/reference_measure.xml.pot Normal file
View file

File diff suppressed because it is too large Load diff

681
doc/po/templates/reference_misc.xml.pot Normal file
View file

@ -0,0 +1,681 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reference_misc.xml:3
#, no-c-format
msgid "Miscellaneous Functions"
msgstr ""
#. Tag: refname
#: reference_misc.xml:7
#, no-c-format
msgid "ST_Accum"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:9
#, no-c-format
msgid "<refpurpose>Aggregate. Constructs an array of geometries.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:14
#, no-c-format
msgid "<funcdef>geometry[] <function>ST_Accum</function></funcdef> <paramdef><type>geometry set</type> <parameter>geomfield</parameter></paramdef>"
msgstr ""
#. Tag: title
#: reference_misc.xml:22 reference_misc.xml:64 reference_misc.xml:106 reference_misc.xml:158 reference_misc.xml:229 reference_misc.xml:289 reference_misc.xml:343 reference_misc.xml:396 reference_misc.xml:438 reference_misc.xml:488
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: reference_misc.xml:24
#, no-c-format
msgid "<para>Aggregate. Constructs an array of geometries.</para>"
msgstr ""
#. Tag: para
#: reference_misc.xml:25 reference_misc.xml:68 reference_misc.xml:109 reference_misc.xml:255 reference_misc.xml:309 reference_misc.xml:355
#, no-c-format
msgid "Enhanced: 2.0.0 support for Polyhedral surfaces, Triangles and TIN was introduced."
msgstr ""
#. Tag: para
#: reference_misc.xml:26 reference_misc.xml:113 reference_misc.xml:357 reference_misc.xml:447
#, no-c-format
msgid "&Z_support;"
msgstr ""
#. Tag: para
#: reference_misc.xml:27 reference_misc.xml:69 reference_misc.xml:110 reference_misc.xml:183 reference_misc.xml:358 reference_misc.xml:448
#, no-c-format
msgid "&curve_support;"
msgstr ""
#. Tag: para
#: reference_misc.xml:28 reference_misc.xml:70 reference_misc.xml:111 reference_misc.xml:256 reference_misc.xml:310 reference_misc.xml:359 reference_misc.xml:449
#, no-c-format
msgid "&P_support;"
msgstr ""
#. Tag: para
#: reference_misc.xml:29 reference_misc.xml:71 reference_misc.xml:112 reference_misc.xml:257 reference_misc.xml:311 reference_misc.xml:360 reference_misc.xml:450
#, no-c-format
msgid "&T_support;"
msgstr ""
#. Tag: title
#: reference_misc.xml:34 reference_misc.xml:76 reference_misc.xml:118 reference_misc.xml:188 reference_misc.xml:262 reference_misc.xml:316 reference_misc.xml:364 reference_misc.xml:408 reference_misc.xml:455 reference_misc.xml:499
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:36
#, no-c-format
msgid ""
"SELECT (ST_Accum(the_geom)) As all_em, ST_AsText((ST_Accum(the_geom))[1]) As grabone,\n"
"(ST_Accum(the_geom))[2:4] as grab_rest\n"
" FROM (SELECT ST_MakePoint(a*CAST(random()*10 As integer), a*CAST(random()*10 As integer), a*CAST(random()*10 As integer)) As the_geom\n"
" FROM generate_series(1,4) a) As foo;\n"
"\n"
"all_em|grabone | grab_rest\n"
"\n"
"-------------------------------------------------------------------------------+\n"
"\n"
" {0101000080000000000000144000000000000024400000000000001040:\n"
" 0101000080000000000\n"
"00018400000000000002C400000000000003040:\n"
"0101000080000000000000354000000000000038400000000000001840:\n"
"010100008000000000000040400000000000003C400000000000003040} |\n"
" POINT(5 10) | {010100008000000000000018400000000000002C400000000000003040:\n"
" 0101000080000000000000354000000000000038400000000000001840:\n"
" 010100008000000000000040400000000000003C400000000000003040}\n"
"(1 row)"
msgstr ""
#. Tag: title
#: reference_misc.xml:41 reference_misc.xml:83 reference_misc.xml:125 reference_misc.xml:195 reference_misc.xml:268 reference_misc.xml:322 reference_misc.xml:369 reference_misc.xml:415 reference_misc.xml:462 reference_misc.xml:506
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: refname
#: reference_misc.xml:49
#, no-c-format
msgid "Box2D"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:51
#, no-c-format
msgid "<refpurpose>Returns a BOX2D representing the maximum extents of the geometry.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:56
#, no-c-format
msgid "<funcdef>box2d <function>Box2D</function></funcdef> <paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:66
#, no-c-format
msgid "<para>Returns a BOX2D representing the maximum extents of the geometry.</para>"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:78
#, no-c-format
msgid ""
"SELECT Box2D(ST_GeomFromText('LINESTRING(1 2, 3 4, 5 6)'));\n"
" box2d\n"
" ---------\n"
" BOX(1 2,5 6)\n"
"\n"
" SELECT Box2D(ST_GeomFromText('CIRCULARSTRING(220268 150415,220227 150505,220227 150406)'));\n"
" box2d\n"
" --------\n"
" BOX(220186.984375 150406,220288.25 150506.140625)"
msgstr ""
#. Tag: para
#: reference_misc.xml:85
#, no-c-format
msgid ", <xref linkend=\"ST_GeomFromText\"/>"
msgstr ""
#. Tag: refname
#: reference_misc.xml:91
#, no-c-format
msgid "Box3D"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:93
#, no-c-format
msgid "<refpurpose>Returns a BOX3D representing the maximum extents of the geometry.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:98
#, no-c-format
msgid "<funcdef>box3d <function>Box3D</function></funcdef> <paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:108
#, no-c-format
msgid "<para>Returns a BOX3D representing the maximum extents of the geometry.</para>"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:120
#, no-c-format
msgid ""
"SELECT Box3D(ST_GeomFromEWKT('LINESTRING(1 2 3, 3 4 5, 5 6 5)'));\n"
" Box3d\n"
" ---------\n"
" BOX3D(1 2 3,5 6 5)\n"
"\n"
" SELECT Box3D(ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 150505 1,220227 150406 1)'));\n"
" Box3d\n"
" --------\n"
" BOX3D(220227 150406 1,220268 150415 1)"
msgstr ""
#. Tag: para
#: reference_misc.xml:127
#, no-c-format
msgid ", <xref linkend=\"ST_GeomFromEWKT\"/>"
msgstr ""
#. Tag: refname
#: reference_misc.xml:133
#, no-c-format
msgid "ST_EstimatedExtent"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:135
#, no-c-format
msgid "<refpurpose>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.</refpurpose>"
msgstr ""
#. Tag: funcsynopsis
#: reference_misc.xml:141
#, no-c-format
msgid "<funcprototype> <funcdef>box2d <function>ST_EstimatedExtent</function></funcdef> <paramdef><type>text </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>text </type> <parameter>table_name</parameter></paramdef> <paramdef><type>text </type> <parameter>geocolumn_name</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>box2d <function>ST_EstimatedExtent</function></funcdef> <paramdef><type>text </type> <parameter>table_name</parameter></paramdef> <paramdef><type>text </type> <parameter>geocolumn_name</parameter></paramdef> </funcprototype>"
msgstr ""
#. Tag: para
#: reference_misc.xml:160
#, no-c-format
msgid "<para>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.</para>"
msgstr ""
#. Tag: para
#: reference_misc.xml:164
#, no-c-format
msgid "For PostgreSQL&gt;=8.0.0 statistics are gathered by VACUUM ANALYZE and resulting extent will be about 95% of the real one."
msgstr ""
#. Tag: para
#: reference_misc.xml:169
#, no-c-format
msgid "In absence of statistics (empty table or no ANALYZE called) this function returns NULL. Prior to version 1.5.4 an exception was thrown instead."
msgstr ""
#. Tag: para
#: reference_misc.xml:177
#, no-c-format
msgid "For PostgreSQL&lt;8.0.0 statistics are gathered by update_geometry_stats() and resulting extent will be exact."
msgstr ""
#. Tag: para
#: reference_misc.xml:180
#, no-c-format
msgid "Availability: 1.0.0"
msgstr ""
#. Tag: para
#: reference_misc.xml:181
#, no-c-format
msgid "Changed: 2.1.0. Up to 2.0.x this was called ST_Estimated_Extent."
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:190
#, no-c-format
msgid ""
"SELECT ST_EstimatedExtent('ny', 'edges', 'the_geom');\n"
"--result--\n"
"BOX(-8877653 4912316,-8010225.5 5589284)\n"
"\n"
"SELECT ST_EstimatedExtent('feature_poly', 'the_geom');\n"
"--result--\n"
"BOX(-124.659652709961 24.6830825805664,-67.7798080444336 49.0012092590332)"
msgstr ""
#. Tag: refname
#: reference_misc.xml:202
#, no-c-format
msgid "ST_Expand"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:203
#, no-c-format
msgid "Returns bounding box expanded in all directions from the bounding box of the input geometry. Uses double-precision"
msgstr ""
#. Tag: funcsynopsis
#: reference_misc.xml:207
#, no-c-format
msgid "<funcprototype> <funcdef>geometry <function>ST_Expand</function></funcdef> <paramdef><type>geometry </type> <parameter>g1</parameter></paramdef> <paramdef><type>float</type> <parameter>units_to_expand</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>box2d <function>ST_Expand</function></funcdef> <paramdef><type>box2d </type> <parameter>g1</parameter></paramdef> <paramdef><type>float</type> <parameter>units_to_expand</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>box3d <function>ST_Expand</function></funcdef> <paramdef><type>box3d </type> <parameter>g1</parameter></paramdef> <paramdef><type>float</type> <parameter>units_to_expand</parameter></paramdef> </funcprototype>"
msgstr ""
#. Tag: para
#: reference_misc.xml:231
#, no-c-format
msgid "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. Uses double-precision. Very useful for distance() queries, or bounding box queries to add an index filter to the query."
msgstr ""
#. Tag: para
#: reference_misc.xml:235
#, no-c-format
msgid "There are 3 variants of this. The one that takes a geometry will return a POLYGON geometry representation of the bounding box and is the most commonly used variant."
msgstr ""
#. Tag: para
#: reference_misc.xml:237
#, no-c-format
msgid "ST_Expand is similar in concept to ST_Buffer except while buffer expands the geometry in all directions, ST_Expand expands the bounding box an x,y,z unit amount."
msgstr ""
#. Tag: para
#: reference_misc.xml:239
#, no-c-format
msgid "Units are in the units of the spatial reference system in use denoted by the SRID"
msgstr ""
#. Tag: para
#: reference_misc.xml:242
#, no-c-format
msgid "Pre 1.3, ST_Expand was used in conjunction with distance to do indexable queries. Something of the form <code>the_geom &amp;&amp; ST_Expand('POINT(10 20)', 10) AND ST_Distance(the_geom, 'POINT(10 20)') &lt; 10</code> Post 1.2, this was replaced with the easier ST_DWithin construct."
msgstr ""
#. Tag: para
#: reference_misc.xml:248
#, no-c-format
msgid "Bounding boxes of all geometries are currently 2-d even if they are 3-dimensional geometries."
msgstr ""
#. Tag: para
#: reference_misc.xml:252
#, no-c-format
msgid "Availability: 1.5.0 behavior changed to output double precision instead of float4 coordinates."
msgstr ""
#. Tag: para
#: reference_misc.xml:263
#, no-c-format
msgid "Examples below use US National Atlas Equal Area (SRID=2163) which is a meter projection"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:264
#, no-c-format
msgid ""
"<!-- TODO: fix results of documentation to reflect new behavior -->\n"
"--10 meter expanded box around bbox of a linestring\n"
"SELECT CAST(ST_Expand(ST_GeomFromText('LINESTRING(2312980 110676,2312923 110701,2312892 110714)', 2163),10) As box2d);\n"
" st_expand\n"
"------------------------------------\n"
" BOX(2312882 110666,2312990 110724)\n"
"\n"
"--10 meter expanded 3d box of a 3d box\n"
"SELECT ST_Expand(CAST('BOX3D(778783 2951741 1,794875 2970042.61545891 10)' As box3d),10)\n"
" st_expand\n"
"-----------------------------------------------------\n"
" BOX3D(778773 2951731 -9,794885 2970052.61545891 20)\n"
"\n"
" --10 meter geometry astext rep of a expand box around a point geometry\n"
" SELECT ST_AsEWKT(ST_Expand(ST_GeomFromEWKT('SRID=2163;POINT(2312980 110676)'),10));\n"
" st_asewkt\n"
"-------------------------------------------------------------------------------------------------\n"
" SRID=2163;POLYGON((2312970 110666,2312970 110686,2312990 110686,2312990 110666,2312970 110666))"
msgstr ""
#. Tag: para
#: reference_misc.xml:269
#, no-c-format
msgid ", <xref linkend=\"ST_Buffer\"/>, <xref linkend=\"ST_DWithin\"/>, <xref linkend=\"ST_GeomFromEWKT\"/>, <xref linkend=\"ST_GeomFromText\"/>, <xref linkend=\"ST_SRID\"/>"
msgstr ""
#. Tag: refname
#: reference_misc.xml:275
#, no-c-format
msgid "ST_Extent"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:276
#, no-c-format
msgid "an aggregate function that returns the bounding box that bounds rows of geometries."
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:281
#, no-c-format
msgid "<funcdef>box2d <function>ST_Extent</function></funcdef> <paramdef><type>geometry set</type> <parameter>geomfield</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:291
#, no-c-format
msgid "ST_Extent returns a bounding box that encloses a set of geometries. The ST_Extent function is an \"aggregate\" function in the terminology of SQL. That means that it operates on lists of data, in the same way the SUM() and AVG() functions do."
msgstr ""
#. Tag: para
#: reference_misc.xml:294 reference_misc.xml:348
#, no-c-format
msgid "Since it returns a bounding box, the spatial Units are in the units of the spatial reference system in use denoted by the SRID"
msgstr ""
#. Tag: para
#: reference_misc.xml:295
#, no-c-format
msgid "ST_Extent is similar in concept to Oracle Spatial/Locator's SDO_AGGR_MBR"
msgstr ""
#. Tag: para
#: reference_misc.xml:297
#, no-c-format
msgid "Since ST_Extent returns a bounding box, the SRID meta-data is lost. Use ST_SetSRID to force it back into a geometry with SRID meta data. The coordinates are in the units of the spatial ref of the orginal geometries."
msgstr ""
#. Tag: para
#: reference_misc.xml:302
#, no-c-format
msgid "ST_Extent will return boxes with only an x and y component even with (x,y,z) coordinate geometries. To maintain x,y,z use ST_3DExtent instead."
msgstr ""
#. Tag: para
#: reference_misc.xml:306
#, no-c-format
msgid "Availability: 1.4.0"
msgstr ""
#. Tag: para
#: reference_misc.xml:317
#, no-c-format
msgid "Examples below use Massachusetts State Plane ft (SRID=2249)"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:318
#, no-c-format
msgid ""
"SELECT ST_Extent(the_geom) as bextent FROM sometable;\n"
" st_bextent\n"
"------------------------------------\n"
"BOX(739651.875 2908247.25,794875.8125 2970042.75)\n"
"\n"
"\n"
"--Return extent of each category of geometries\n"
"SELECT ST_Extent(the_geom) as bextent\n"
"FROM sometable\n"
"GROUP BY category ORDER BY category;\n"
"\n"
" bextent | name\n"
"----------------------------------------------------+----------------\n"
" BOX(778783.5625 2951741.25,794875.8125 2970042.75) | A\n"
" BOX(751315.8125 2919164.75,765202.6875 2935417.25) | B\n"
" BOX(739651.875 2917394.75,756688.375 2935866) | C\n"
"\n"
" --Force back into a geometry\n"
" -- and render the extended text representation of that geometry\n"
"SELECT ST_SetSRID(ST_Extent(the_geom),2249) as bextent FROM sometable;\n"
"\n"
" bextent\n"
"--------------------------------------------------------------------------------\n"
" SRID=2249;POLYGON((739651.875 2908247.25,739651.875 2970042.75,794875.8125 2970042.75,\n"
" 794875.8125 2908247.25,739651.875 2908247.25))"
msgstr ""
#. Tag: para
#: reference_misc.xml:323
#, no-c-format
msgid ", <xref linkend=\"ST_3DExtent\"/>, <xref linkend=\"ST_SetSRID\"/>, <xref linkend=\"ST_SRID\"/>"
msgstr ""
#. Tag: refname
#: reference_misc.xml:329
#, no-c-format
msgid "ST_3DExtent"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:330
#, no-c-format
msgid "an aggregate function that returns the box3D bounding box that bounds rows of geometries."
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:335
#, no-c-format
msgid "<funcdef>box3d <function>ST_3DExtent</function></funcdef> <paramdef><type>geometry set</type> <parameter>geomfield</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:345
#, no-c-format
msgid "ST_3DExtent returns a box3d (includes Z coordinate) bounding box that encloses a set of geometries. The ST_3DExtent function is an \"aggregate\" function in the terminology of SQL. That means that it operates on lists of data, in the same way the SUM() and AVG() functions do."
msgstr ""
#. Tag: para
#: reference_misc.xml:351
#, no-c-format
msgid "Since ST_3DExtent returns a bounding box, the SRID meta-data is lost. Use ST_SetSRID to force it back into a geometry with SRID meta data. The coordinates are in the units of the spatial ref of the orginal geometries."
msgstr ""
#. Tag: para
#: reference_misc.xml:356
#, no-c-format
msgid "Changed: 2.0.0 In prior versions this used to be called ST_Extent3D"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:365
#, no-c-format
msgid ""
"SELECT ST_3DExtent(foo.the_geom) As b3extent\n"
"FROM (SELECT ST_MakePoint(x,y,z) As the_geom\n"
" FROM generate_series(1,3) As x\n"
" CROSS JOIN generate_series(1,2) As y\n"
" CROSS JOIN generate_series(0,2) As Z) As foo;\n"
" b3extent\n"
"--------------------\n"
" BOX3D(1 1 0,3 2 2)\n"
"\n"
"--Get the extent of various elevated circular strings\n"
"SELECT ST_3DExtent(foo.the_geom) As b3extent\n"
"FROM (SELECT ST_Translate(ST_Force_3DZ(ST_LineToCurve(ST_Buffer(ST_MakePoint(x,y),1))),0,0,z) As the_geom\n"
" FROM generate_series(1,3) As x\n"
" CROSS JOIN generate_series(1,2) As y\n"
" CROSS JOIN generate_series(0,2) As Z) As foo;\n"
"\n"
" b3extent\n"
"--------------------\n"
" BOX3D(1 0 0,4 2 2)"
msgstr ""
#. Tag: para
#: reference_misc.xml:370
#, no-c-format
msgid ", <xref linkend=\"ST_Force_3DZ\"/>"
msgstr ""
#. Tag: refname
#: reference_misc.xml:377
#, no-c-format
msgid "Find_SRID"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:379
#, no-c-format
msgid "The syntax is find_srid(&lt;db/schema&gt;, &lt;table&gt;, &lt;column&gt;) and the function returns the integer SRID of the specified column by searching through the GEOMETRY_COLUMNS table."
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:386
#, no-c-format
msgid "<funcdef>integer <function>Find_SRID</function></funcdef> <paramdef><type>varchar </type> <parameter>a_schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>a_table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>a_geomfield_name</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:398
#, no-c-format
msgid "The syntax is find_srid(&lt;db/schema&gt;, &lt;table&gt;, &lt;column&gt;) 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."
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:410
#, no-c-format
msgid ""
"SELECT Find_SRID('public', 'tiger_us_state_2007', 'the_geom_4269');\n"
"find_srid\n"
"----------\n"
"4269"
msgstr ""
#. Tag: refname
#: reference_misc.xml:423
#, no-c-format
msgid "ST_Mem_Size"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:425
#, no-c-format
msgid "<refpurpose>Returns the amount of space (in bytes) the geometry takes.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:430
#, no-c-format
msgid "<funcdef>integer <function>ST_Mem_Size</function></funcdef> <paramdef><type>geometry </type> <parameter>geomA</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:440
#, no-c-format
msgid "<para>Returns the amount of space (in bytes) the geometry takes.</para>"
msgstr ""
#. Tag: para
#: reference_misc.xml:441
#, no-c-format
msgid "This is a nice compliment to PostgreSQL built in functions pg_size_pretty, pg_relation_size, pg_total_relation_size."
msgstr ""
#. Tag: para
#: reference_misc.xml:442
#, no-c-format
msgid "pg_relation_size which gives the byte size of a table may return byte size lower than ST_Mem_Size. This is because pg_relation_size does not add toasted table contribution and large geometries are stored in TOAST tables."
msgstr ""
#. Tag: para
#: reference_misc.xml:444
#, no-c-format
msgid "pg_total_relation_size - includes, the table, the toasted tables, and the indexes."
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:457
#, no-c-format
msgid ""
"--Return how much byte space Boston takes up in our Mass data set\n"
"SELECT pg_size_pretty(SUM(ST_Mem_Size(the_geom))) as totgeomsum,\n"
"pg_size_pretty(SUM(CASE WHEN town = 'BOSTON' THEN st_mem_size(the_geom) ELSE 0 END)) As bossum,\n"
"CAST(SUM(CASE WHEN town = 'BOSTON' THEN st_mem_size(the_geom) ELSE 0 END)*1.00 /\n"
" SUM(st_mem_size(the_geom))*100 As numeric(10,2)) As perbos\n"
"FROM towns;\n"
"\n"
"totgeomsum bossum perbos\n"
"---------- ------ ------\n"
"1522 kB 30 kB 1.99\n"
"\n"
"\n"
"SELECT ST_Mem_Size(ST_GeomFromText('CIRCULARSTRING(220268 150415,220227 150505,220227 150406)'));\n"
"\n"
"---\n"
"73\n"
"\n"
"--What percentage of our table is taken up by just the geometry\n"
"SELECT pg_total_relation_size('public.neighborhoods') As fulltable_size, sum(ST_Mem_Size(the_geom)) As geomsize,\n"
"sum(ST_Mem_Size(the_geom))*1.00/pg_total_relation_size('public.neighborhoods')*100 As pergeom\n"
"FROM neighborhoods;\n"
"fulltable_size geomsize pergeom\n"
"------------------------------------------------\n"
"262144 96238 36.71188354492187500000"
msgstr ""
#. Tag: refname
#: reference_misc.xml:470
#, no-c-format
msgid "ST_Point_Inside_Circle"
msgstr ""
#. Tag: refpurpose
#: reference_misc.xml:472
#, no-c-format
msgid "Is the point geometry insert circle defined by center_x, center_y, radius"
msgstr ""
#. Tag: funcprototype
#: reference_misc.xml:477
#, no-c-format
msgid "<funcdef>boolean <function>ST_Point_Inside_Circle</function></funcdef> <paramdef><type>geometry </type> <parameter>a_point</parameter></paramdef> <paramdef><type>float </type> <parameter>center_x</parameter></paramdef> <paramdef><type>float </type> <parameter>center_y</parameter></paramdef> <paramdef><type>float </type> <parameter>radius</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_misc.xml:490
#, no-c-format
msgid "The syntax for this functions is point_inside_circle(&lt;geometry&gt;,&lt;circle_center_x&gt;,&lt;circle_center_y&gt;,&lt;radius&gt;). Returns the true if the geometry is a point and is inside the circle. Returns false otherwise."
msgstr ""
#. Tag: para
#: reference_misc.xml:494
#, no-c-format
msgid "This only works for points as the name suggests"
msgstr ""
#. Tag: programlisting
#: reference_misc.xml:501
#, no-c-format
msgid ""
"SELECT ST_Point_Inside_Circle(ST_Point(1,2), 0.5, 2, 3);\n"
" st_point_inside_circle\n"
"------------------------\n"
" t"
msgstr ""

1059
doc/po/templates/reference_operator.xml.pot Normal file
View file

File diff suppressed because it is too large Load diff

1478
doc/po/templates/reference_output.xml.pot Normal file
View file

File diff suppressed because it is too large Load diff

3079
doc/po/templates/reference_processing.xml.pot Normal file
View file

File diff suppressed because it is too large Load diff

9079
doc/po/templates/reference_raster.xml.pot Normal file
View file

File diff suppressed because one or more lines are too long

309
doc/po/templates/reference_transaction.xml.pot Normal file
View file

@ -0,0 +1,309 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reference_transaction.xml:3
#, no-c-format
msgid "Long Transactions Support"
msgstr ""
#. Tag: para
#: reference_transaction.xml:5
#, no-c-format
msgid "This module and associated pl/pgsql functions have been implemented to provide long locking support required by <ulink url=\"http://www.opengeospatial.org/standards/wfs\">Web Feature Service</ulink> specification."
msgstr ""
#. Tag: para
#: reference_transaction.xml:10
#, no-c-format
msgid "Users must use <ulink url=\"http://www.postgresql.org/docs/current/static/transaction-iso.html\">serializable transaction level</ulink> otherwise locking mechanism would break."
msgstr ""
#. Tag: refname
#: reference_transaction.xml:18
#, no-c-format
msgid "AddAuth"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:20
#, no-c-format
msgid "<refpurpose>Add an authorization token to be used in current transaction.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_transaction.xml:25
#, no-c-format
msgid "<funcdef>boolean <function>AddAuth</function></funcdef> <paramdef><type>text </type> <parameter>auth_token</parameter></paramdef>"
msgstr ""
#. Tag: title
#: reference_transaction.xml:33 reference_transaction.xml:83 reference_transaction.xml:130 reference_transaction.xml:177 reference_transaction.xml:241 reference_transaction.xml:284
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: reference_transaction.xml:35
#, no-c-format
msgid "<para>Add an authorization token to be used in current transaction.</para>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:37
#, no-c-format
msgid "Creates/adds to a temp table called temp_lock_have_table the current transaction identifier and authorization token key."
msgstr ""
#. Tag: para
#: reference_transaction.xml:40 reference_transaction.xml:92 reference_transaction.xml:138 reference_transaction.xml:185 reference_transaction.xml:248 reference_transaction.xml:289
#, no-c-format
msgid "Availability: 1.1.3"
msgstr ""
#. Tag: title
#: reference_transaction.xml:45 reference_transaction.xml:98 reference_transaction.xml:144 reference_transaction.xml:191 reference_transaction.xml:253 reference_transaction.xml:294
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:47
#, no-c-format
msgid ""
"SELECT LockRow('towns', '353', 'priscilla');\n"
" BEGIN TRANSACTION;\n"
" SELECT AddAuth('joey');\n"
" UPDATE towns SET the_geom = ST_Translate(the_geom,2,2) WHERE gid = 353;\n"
" COMMIT;\n"
"\n"
"\n"
" ---Error--\n"
" ERROR: UPDATE where \"gid\" = '353' requires authorization 'priscilla'"
msgstr ""
#. Tag: title
#: reference_transaction.xml:52 reference_transaction.xml:105 reference_transaction.xml:151 reference_transaction.xml:198 reference_transaction.xml:260 reference_transaction.xml:301
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: refname
#: reference_transaction.xml:60
#, no-c-format
msgid "CheckAuth"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:62
#, no-c-format
msgid "Creates trigger on a table to prevent/allow updates and deletes of rows based on authorization token."
msgstr ""
#. Tag: funcsynopsis
#: reference_transaction.xml:66
#, no-c-format
msgid "<funcprototype> <funcdef>integer <function>CheckAuth</function></funcdef> <paramdef><type>text </type> <parameter>a_schema_name</parameter></paramdef> <paramdef><type>text </type> <parameter>a_table_name</parameter></paramdef> <paramdef><type>text </type> <parameter>a_key_column_name</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>integer <function>CheckAuth</function></funcdef> <paramdef><type>text </type> <parameter>a_table_name</parameter></paramdef> <paramdef><type>text </type> <parameter>a_key_column_name</parameter></paramdef> </funcprototype>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:85
#, no-c-format
msgid "Creates trigger on a table to prevent/allow updates and deletes of rows based on authorization token. Identify rows using &lt;rowid_col&gt; column."
msgstr ""
#. Tag: para
#: reference_transaction.xml:87
#, no-c-format
msgid "If a_schema_name is not passed in, then searches for table in current schema."
msgstr ""
#. Tag: para
#: reference_transaction.xml:88
#, no-c-format
msgid "If an authorization trigger already exists on this table function errors."
msgstr ""
#. Tag: para
#: reference_transaction.xml:89
#, no-c-format
msgid "If Transaction support is not enabled, function throws an exception."
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:100
#, no-c-format
msgid ""
"SELECT CheckAuth('public', 'towns', 'gid');\n"
" result\n"
" ------\n"
" 0"
msgstr ""
#. Tag: refname
#: reference_transaction.xml:113
#, no-c-format
msgid "DisableLongTransactions"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:115
#, no-c-format
msgid "<refpurpose>Disable long transaction support. This function removes the long transaction support metadata tables, and drops all triggers attached to lock-checked tables.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_transaction.xml:122
#, no-c-format
msgid "<funcdef>text <function>DisableLongTransactions</function></funcdef> <paramdef></paramdef>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:132
#, no-c-format
msgid "<para>Disable long transaction support. This function removes the long transaction support metadata tables, and drops all triggers attached to lock-checked tables.</para>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:135
#, no-c-format
msgid "Drops meta table called <varname>authorization_table</varname> and a view called <varname>authorized_tables</varname> and all triggers called <varname>checkauthtrigger</varname>"
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:146
#, no-c-format
msgid ""
"SELECT DisableLongTransactions();\n"
"--result--\n"
"Long transactions support disabled"
msgstr ""
#. Tag: refname
#: reference_transaction.xml:159
#, no-c-format
msgid "EnableLongTransactions"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:161
#, no-c-format
msgid "<refpurpose>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.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_transaction.xml:169
#, no-c-format
msgid "<funcdef>text <function>EnableLongTransactions</function></funcdef> <paramdef></paramdef>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:179
#, no-c-format
msgid "<para>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.</para>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:183
#, no-c-format
msgid "Creates a meta table called <varname>authorization_table</varname> and a view called <varname>authorized_tables</varname>"
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:193
#, no-c-format
msgid ""
"SELECT EnableLongTransactions();\n"
"--result--\n"
"Long transactions support enabled"
msgstr ""
#. Tag: refname
#: reference_transaction.xml:206
#, no-c-format
msgid "LockRow"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:208
#, no-c-format
msgid "Set lock/authorization for specific row in table"
msgstr ""
#. Tag: funcsynopsis
#: reference_transaction.xml:212
#, no-c-format
msgid "<funcprototype> <funcdef>integer <function>LockRow</function></funcdef> <paramdef><type>text </type> <parameter>a_schema_name</parameter></paramdef> <paramdef><type>text </type> <parameter>a_table_name</parameter></paramdef> <paramdef><type>text </type> <parameter>a_row_key</parameter></paramdef> <paramdef><type>text</type> <parameter>an_auth_token</parameter></paramdef> <paramdef><type>timestamp</type> <parameter>expire_dt</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>integer <function>LockRow</function></funcdef> <paramdef><type>text </type> <parameter>a_table_name</parameter></paramdef> <paramdef><type>text </type> <parameter>a_row_key</parameter></paramdef> <paramdef><type>text</type> <parameter>an_auth_token</parameter></paramdef> <paramdef><type>timestamp</type> <parameter>expire_dt</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>integer <function>LockRow</function></funcdef> <paramdef><type>text </type> <parameter>a_table_name</parameter></paramdef> <paramdef><type>text </type> <parameter>a_row_key</parameter></paramdef> <paramdef><type>text</type> <parameter>an_auth_token</parameter></paramdef> </funcprototype>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:243
#, no-c-format
msgid "Set lock/authorization for specific row in table &lt;authid&gt; is a text value, &lt;expires&gt; is a timestamp defaulting to now()+1hour. Returns 1 if lock has been assigned, 0 otherwise (already locked by other auth)"
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:255
#, no-c-format
msgid ""
"SELECT LockRow('public', 'towns', '2', 'joey');\n"
"LockRow\n"
"-------\n"
"1\n"
"\n"
"--Joey has already locked the record and Priscilla is out of luck\n"
"SELECT LockRow('public', 'towns', '2', 'priscilla');\n"
"LockRow\n"
"-------\n"
"0"
msgstr ""
#. Tag: refname
#: reference_transaction.xml:268
#, no-c-format
msgid "UnlockRows"
msgstr ""
#. Tag: refpurpose
#: reference_transaction.xml:270
#, no-c-format
msgid "<refpurpose>Remove all locks held by specified authorization id. Returns the number of locks released.</refpurpose>"
msgstr ""
#. Tag: funcprototype
#: reference_transaction.xml:276
#, no-c-format
msgid "<funcdef>integer <function>UnlockRows</function></funcdef> <paramdef><type>text </type> <parameter>auth_token</parameter></paramdef>"
msgstr ""
#. Tag: para
#: reference_transaction.xml:286
#, no-c-format
msgid "<para>Remove all locks held by specified authorization id. Returns the number of locks released.</para>"
msgstr ""
#. Tag: programlisting
#: reference_transaction.xml:296
#, no-c-format
msgid ""
"SELECT LockRow('towns', '353', 'priscilla');\n"
" SELECT LockRow('towns', '2', 'priscilla');\n"
" SELECT UnLockRows('priscilla');\n"
" UnLockRows\n"
" ------------\n"
" 2"
msgstr ""

232
doc/po/templates/reference_type.xml.pot Normal file
View file

@ -0,0 +1,232 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 21:04+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: para
#: reference_type.xml:5
#, no-c-format
msgid "This section lists the PostgreSQL data types installed by PostGIS. Note we describe the casting behavior of these which is very important especially when designing your own functions."
msgstr ""
#. Tag: para
#: reference_type.xml:8
#, no-c-format
msgid "A Cast is when one type is coerced into another type. PostgreSQL is unique from most databases in that it allows you to define casting behavior for custom types and the functions used for casting. A cast can be specified as automatic in which case, you do not have to do a CAST(myfoo As otherfootype) or myfoo::otherfootype if you are feeding it to a function that only works with otherfootype and there is an automatic cast in place for it."
msgstr ""
#. Tag: para
#: reference_type.xml:13
#, no-c-format
msgid "The danger of relying on automatic cast behavior is when you have an overloaded function say one that takes a box2d and one that takes a box3d but no geometry. What happens is that both functions are equally good to use with geometry since geometry has an autocast for both -- so you end up with an ambiguous function error. To force PostgreSQL to choose, you do a CAST(mygeom As box3d) or mygeom::box3d."
msgstr ""
#. Tag: para
#: reference_type.xml:17
#, no-c-format
msgid "<emphasis>At least as of PostgreSQL 8.3</emphasis> - Everything can be CAST to text (presumably because of the magical unknown type), so no defined CASTS for that need to be present for you to CAST an object to text."
msgstr ""
#. Tag: title
#: reference_type.xml:20
#, no-c-format
msgid "PostgreSQL PostGIS Geometry/Geography/Box Types"
msgstr ""
#. Tag: refname
#: reference_type.xml:24
#, no-c-format
msgid "<refname>box2d</refname>"
msgstr ""
#. Tag: refpurpose
#: reference_type.xml:25
#, no-c-format
msgid "A box composed of x min, ymin, xmax, ymax. Often used to return the 2d enclosing box of a geometry."
msgstr ""
#. Tag: title
#: reference_type.xml:29 reference_type.xml:40 reference_type.xml:79 reference_type.xml:136 reference_type.xml:155
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#: reference_type.xml:30
#, no-c-format
msgid "box2d is a spatial data type used to represent the enclosing box of a geometry or set of geometries. ST_Extent in earlier versions prior to PostGIS 1.4 would return a box2d."
msgstr ""
#. Tag: refname
#: reference_type.xml:35
#, no-c-format
msgid "<refname>box3d</refname>"
msgstr ""
#. Tag: refpurpose
#: reference_type.xml:36
#, no-c-format
msgid "A box composed of x min, ymin, zmin, xmax, ymax, zmax. Often used to return the 3d extent of a geometry or collection of geometries."
msgstr ""
#. Tag: para
#: reference_type.xml:41
#, no-c-format
msgid "box3d is a postgis spatial data type used to represent the enclosing box of a geometry or set of geometries. ST_3DExtent returns a box3d object."
msgstr ""
#. Tag: title
#: reference_type.xml:45 reference_type.xml:84 reference_type.xml:160
#, no-c-format
msgid "Casting Behavior"
msgstr ""
#. Tag: para
#: reference_type.xml:46 reference_type.xml:85 reference_type.xml:161
#, no-c-format
msgid "This section lists the automatic as well as explicit casts allowed for this data type"
msgstr ""
#. Tag: entry
#: reference_type.xml:51 reference_type.xml:90 reference_type.xml:166
#, no-c-format
msgid "Cast To"
msgstr ""
#. Tag: entry
#: reference_type.xml:52 reference_type.xml:91 reference_type.xml:167
#, no-c-format
msgid "Behavior"
msgstr ""
#. Tag: entry
#: reference_type.xml:55 reference_type.xml:94
#, no-c-format
msgid "<entry>box</entry>"
msgstr ""
#. Tag: entry
#: reference_type.xml:56 reference_type.xml:60 reference_type.xml:64 reference_type.xml:95 reference_type.xml:99 reference_type.xml:103 reference_type.xml:107 reference_type.xml:111 reference_type.xml:115
#, no-c-format
msgid "automatic"
msgstr ""
#. Tag: entry
#: reference_type.xml:59 reference_type.xml:98
#, no-c-format
msgid "<entry>box2d</entry>"
msgstr ""
#. Tag: entry
#: reference_type.xml:63 reference_type.xml:170
#, no-c-format
msgid "<entry>geometry</entry>"
msgstr ""
#. Tag: refname
#: reference_type.xml:74
#, no-c-format
msgid "<refname>geometry</refname>"
msgstr ""
#. Tag: refpurpose
#: reference_type.xml:75
#, no-c-format
msgid "Planar spatial data type."
msgstr ""
#. Tag: para
#: reference_type.xml:80
#, no-c-format
msgid "geometry is a fundamental postgis spatial data type used to represent a feature in the Euclidean coordinate system."
msgstr ""
#. Tag: entry
#: reference_type.xml:102
#, no-c-format
msgid "<entry>box3d</entry>"
msgstr ""
#. Tag: entry
#: reference_type.xml:106
#, no-c-format
msgid "bytea"
msgstr ""
#. Tag: entry
#: reference_type.xml:110
#, no-c-format
msgid "<entry>geography</entry>"
msgstr ""
#. Tag: entry
#: reference_type.xml:114
#, no-c-format
msgid "text"
msgstr ""
#. Tag: title
#: reference_type.xml:123 reference_type.xml:143 reference_type.xml:179
#, no-c-format
msgid "See Also"
msgstr ""
#. Tag: refname
#: reference_type.xml:130
#, no-c-format
msgid "geometry_dump"
msgstr ""
#. Tag: refpurpose
#: reference_type.xml:131
#, no-c-format
msgid "A spatial datatype with two fields - geom (holding a geometry object) and path[] (a 1-d array holding the position of the geometry within the dumped object.)"
msgstr ""
#. Tag: para
#: reference_type.xml:137
#, no-c-format
msgid "geometry_dump is a compound data type consisting of a geometry object referenced by the .geom field and path[] a 1-dimensional integer array (starting at 1 e.g. path[1] to get first element) array that defines the navigation path within the dumped geometry to find this element. It is used by the ST_Dump* family of functions as an output type to explode a more complex geometry into its constituent parts and location of parts."
msgstr ""
#. Tag: refname
#: reference_type.xml:150
#, no-c-format
msgid "<refname>geography</refname>"
msgstr ""
#. Tag: refpurpose
#: reference_type.xml:151
#, no-c-format
msgid "Ellipsoidal spatial data type."
msgstr ""
#. Tag: para
#: reference_type.xml:156
#, no-c-format
msgid "geography is a spatial data type used to represent a feature in the round-earth coordinate system."
msgstr ""
#. Tag: entry
#: reference_type.xml:171
#, no-c-format
msgid "explicit"
msgstr ""
#. Tag: para
#: reference_type.xml:180
#, no-c-format
msgid ", <xref linkend=\"PostGIS_Geography\"/>"
msgstr ""

3982
doc/po/templates/release_notes.xml.pot Normal file
View file

File diff suppressed because it is too large Load diff

136
doc/po/templates/reporting.xml.pot Normal file
View file

@ -0,0 +1,136 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: reporting.xml:3
#, no-c-format
msgid "Reporting Problems"
msgstr ""
#. Tag: title
#: reporting.xml:6
#, no-c-format
msgid "Reporting Software Bugs"
msgstr ""
#. Tag: para
#: reporting.xml:8
#, no-c-format
msgid "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 <code>SELECT postgis_full_version()</code> [for postgis] and <code>SELECT version()</code> [for postgresql]."
msgstr ""
#. Tag: para
#: reporting.xml:16
#, no-c-format
msgid "If you aren't using the latest release, it's worth taking a look at its <ulink url=\"http://svn.osgeo.org/postgis/trunk/NEWS\">release changelog</ulink> first, to find out if your bug has already been fixed."
msgstr ""
#. Tag: para
#: reporting.xml:21
#, no-c-format
msgid "Using the <ulink url=\"http://trac.osgeo.org/postgis/\">PostGIS bug tracker</ulink> will ensure your reports are not discarded, and will keep you informed on its 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."
msgstr ""
#. Tag: para
#: reporting.xml:28
#, no-c-format
msgid "You might want to read Simon Tatham's paper about <ulink url=\"http://www.chiark.greenend.org.uk/~sgtatham/bugs.html\">How to Report Bugs Effectively</ulink> before filing a new report."
msgstr ""
#. Tag: title
#: reporting.xml:34
#, no-c-format
msgid "Reporting Documentation Issues"
msgstr ""
#. Tag: para
#: reporting.xml:36
#, no-c-format
msgid "The documentation should accurately reflect the features and behavior of the software. If it doesn't, it could be because of a software bug or because the documentation is in error or deficient."
msgstr ""
#. Tag: para
#: reporting.xml:40
#, no-c-format
msgid "Documentation issues can also be reported to the <ulink url=\"http://trac.osgeo.org/postgis\">PostGIS bug tracker</ulink>."
msgstr ""
#. Tag: para
#: reporting.xml:44
#, no-c-format
msgid "If your revision is trivial, just describe it in a new bug tracker issue, being specific about its location in the documentation."
msgstr ""
#. Tag: para
#: reporting.xml:47
#, no-c-format
msgid "If your changes are more extensive, a Subversion patch is definitely preferred. This is a four step process on Unix (assuming you already have <ulink url=\"http://subversion.apache.org/\">Subversion</ulink> installed):"
msgstr ""
#. Tag: para
#: reporting.xml:54
#, no-c-format
msgid "Check out a copy of PostGIS' Subversion trunk. On Unix, type:"
msgstr ""
#. Tag: command
#: reporting.xml:57
#, no-c-format
msgid "svn checkout http://svn.osgeo.org/postgis/trunk/"
msgstr ""
#. Tag: para
#: reporting.xml:60
#, no-c-format
msgid "This will be stored in the directory ./trunk"
msgstr ""
#. Tag: para
#: reporting.xml:64
#, no-c-format
msgid "Make your changes to the documentation with your favorite text editor. On Unix, type (for example):"
msgstr ""
#. Tag: command
#: reporting.xml:67
#, no-c-format
msgid "vim trunk/doc/postgis.xml"
msgstr ""
#. Tag: para
#: reporting.xml:69
#, no-c-format
msgid "Note that the documentation is written in DocBook XML rather than HTML, so if you are not familiar with it please follow the example of the rest of the documentation."
msgstr ""
#. Tag: para
#: reporting.xml:75
#, no-c-format
msgid "Make a patch file containing the differences from the master copy of the documentation. On Unix, type:"
msgstr ""
#. Tag: command
#: reporting.xml:78
#, no-c-format
msgid "svn diff trunk/doc/postgis.xml &gt; doc.patch"
msgstr ""
#. Tag: para
#: reporting.xml:83
#, no-c-format
msgid "Attach the patch to a new issue in bug tracker."
msgstr ""

659
doc/po/templates/using_postgis_app.xml.pot Normal file
View file

@ -0,0 +1,659 @@
# SOME DESCRIPTIVE TITLE.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#: using_postgis_app.xml:3
#, no-c-format
msgid "Using PostGIS Geometry: Building Applications"
msgstr ""
#. Tag: title
#: using_postgis_app.xml:5
#, no-c-format
msgid "Using MapServer"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:7
#, no-c-format
msgid "The Minnesota MapServer is an internet web-mapping server which conforms to the OpenGIS Web Mapping Server specification."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:12
#, no-c-format
msgid "The MapServer homepage is at <ulink url=\"http://mapserver.org\">http://mapserver.org</ulink>."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:17
#, no-c-format
msgid "The OpenGIS Web Map Specification is at <ulink url=\"http://www.opengeospatial.org/standards/wms\">http://www.opengeospatial.org/standards/wms</ulink>."
msgstr ""
#. Tag: title
#: using_postgis_app.xml:23
#, no-c-format
msgid "Basic Usage"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:25
#, no-c-format
msgid "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."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:30
#, no-c-format
msgid "To use PostGIS with MapServer, you will need:"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:34
#, no-c-format
msgid "Version 0.6 or newer of PostGIS."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:38
#, no-c-format
msgid "Version 3.5 or newer of MapServer."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:42
#, no-c-format
msgid "MapServer accesses PostGIS/PostgreSQL data like any other PostgreSQL client -- using the <filename>libpq</filename> interface. This means that MapServer can be installed on any machine with network access to the PostGIS server, and use PostGIS as a source of data. The faster the connection between the systems, the better."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:50
#, no-c-format
msgid "Compile and install MapServer, with whatever options you desire, including the \"--with-postgis\" configuration option."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:55
#, no-c-format
msgid "In your MapServer map file, add a PostGIS layer. For example:"
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:58
#, no-c-format
msgid ""
"LAYER \n"
" CONNECTIONTYPE postgis \n"
" NAME \"widehighways\" \n"
" # Connect to a remote spatial database\n"
" CONNECTION \"user=dbuser dbname=gisdatabase host=bigserver\"\n"
" PROCESSING \"CLOSE_CONNECTION=DEFER\"\n"
" # Get the lines from the 'geom' column of the 'roads' table \n"
" DATA \"geom from roads using srid=4326 using unique gid\" \n"
" STATUS ON\n"
" TYPE LINE \n"
" # Of the lines in the extents, only render the wide highways \n"
" FILTER \"type = 'highway' and numlanes &gt;= 4\" \n"
" CLASS \n"
" # Make the superhighways brighter and 2 pixels wide\n"
" EXPRESSION ([numlanes] &gt;= 6) \n"
" STYLE\n"
" COLOR 255 22 22 \n"
" WIDTH 2 \n"
" END\n"
" END \n"
" CLASS \n"
" # All the rest are darker and only 1 pixel wide \n"
" EXPRESSION ([numlanes] &lt; 6) \n"
" STYLE\n"
" COLOR 205 92 82\n"
" END\n"
" END \n"
"END"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:60
#, no-c-format
msgid "In the example above, the PostGIS-specific directives are as follows:"
msgstr ""
#. Tag: term
#: using_postgis_app.xml:65
#, no-c-format
msgid "CONNECTIONTYPE"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:68
#, no-c-format
msgid "For PostGIS layers, this is always \"postgis\"."
msgstr ""
#. Tag: term
#: using_postgis_app.xml:73
#, no-c-format
msgid "CONNECTION"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:76
#, no-c-format
msgid "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 &lt;&gt;):"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:80
#, no-c-format
msgid "user=&lt;username&gt; password=&lt;password&gt; dbname=&lt;username&gt; hostname=&lt;server&gt; port=&lt;5432&gt;"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:84
#, no-c-format
msgid "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."
msgstr ""
#. Tag: term
#: using_postgis_app.xml:92
#, no-c-format
msgid "DATA"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:95
#, no-c-format
msgid "The form of this parameter is \"&lt;geocolumn&gt; from &lt;tablename&gt; using srid=&lt;srid&gt; using unique &lt;primary key&gt;\" where the column is the spatial column to be rendered to the map, the SRID is SRID used by the column and the primary key is the table primary key (or any other uniquely-valued column with an index)."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:99
#, no-c-format
msgid "You can omit the \"using srid\" and \"using unique\" clauses and MapServer will automatically determine the correct values if possible, but at the cost of running a few extra queries on the server for each map draw."
msgstr ""
#. Tag: term
#: using_postgis_app.xml:106
#, no-c-format
msgid "PROCESSING"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:109
#, no-c-format
msgid "Putting in a CLOSE_CONNECTION=DEFER if you have multiple layers reuses existing connections instead of closing them. This improves speed. Refer to for <ulink url=\"http://blog.cleverelephant.ca/2008/10/mapserverpostgis-performance-tips.html\">MapServer PostGIS Performance Tips</ulink> for a more detailed explanation."
msgstr ""
#. Tag: term
#: using_postgis_app.xml:115
#, no-c-format
msgid "FILTER"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:118
#, no-c-format
msgid "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 &gt;= 6\"."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:128
#, no-c-format
msgid "In your spatial database, ensure you have spatial (GiST) indexes built for any the layers you will be drawing."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:131
#, no-c-format
msgid "CREATE INDEX [indexname] ON [tablename] USING GIST ( [geometrycolumn] );"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:135
#, no-c-format
msgid "If you will be querying your layers using MapServer you will also need to use the \"using unique\" clause in your DATA statement."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:138
#, no-c-format
msgid "MapServer requires unique identifiers for each spatial record when doing queries, and the PostGIS module of MapServer uses the unique value you specify in order to provide these unique identifiers. Using the table primary key is the best practice."
msgstr ""
#. Tag: title
#: using_postgis_app.xml:147
#, no-c-format
msgid "Frequently Asked Questions"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:152
#, no-c-format
msgid "When I use an <varname>EXPRESSION</varname> in my map file, the condition never returns as true, even though I know the values exist in my table."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:158
#, no-c-format
msgid "Unlike shape files, PostGIS field names have to be referenced in EXPRESSIONS using <emphasis>lower case</emphasis>."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:162
#, no-c-format
msgid "EXPRESSION ([numlanes] &gt;= 6)"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:168
#, no-c-format
msgid "The FILTER I use for my Shape files is not working for my PostGIS table of the same data."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:173
#, no-c-format
msgid "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)."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:177
#, no-c-format
msgid "FILTER \"type = 'highway' and numlanes &gt;= 4\""
msgstr ""
#. Tag: para
#: using_postgis_app.xml:183
#, no-c-format
msgid "My PostGIS layer draws much slower than my Shape file layer, is this normal?"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:188
#, no-c-format
msgid "In general, the more features you are drawing into a given map, the more likely it is that PostGIS will be slower than Shape files. For maps with relatively few features (100s), PostGIS will often be faster. For maps with high feature density (1000s), PostGIS will always be slower."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:194
#, no-c-format
msgid "If you are finding substantial draw performance problems, it is possible that you have not built a spatial index on your table."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:198
#, no-c-format
msgid ""
"postgis# CREATE INDEX geotable_gix ON geotable USING GIST ( geocolumn ); \n"
"postgis# VACUUM ANALYZE;"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:204
#, no-c-format
msgid "My PostGIS layer draws fine, but queries are really slow. What is wrong?"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:209
#, no-c-format
msgid "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."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:213
#, no-c-format
msgid "You can specify what unique key for mapserver to use with the <varname>USING UNIQUE</varname> clause in your <varname>DATA</varname> line:"
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:217
#, no-c-format
msgid "DATA \"geom FROM geotable USING UNIQUE gid\""
msgstr ""
#. Tag: para
#: using_postgis_app.xml:224
#, no-c-format
msgid "Can I use \"geography\" columns (new in PostGIS 1.5) as a source for MapServer layers?"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:229
#, no-c-format
msgid "Yes! MapServer understands geography columns as being the same as geometry columns, but always using an SRID of 4326. Just make sure to include a \"using srid=4326\" clause in your <varname>DATA</varname> statement. Everything else works exactly the same as with geometry."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:234
#, no-c-format
msgid "DATA \"geog FROM geogtable USING SRID=4326 USING UNIQUE gid\""
msgstr ""
#. Tag: title
#: using_postgis_app.xml:244
#, no-c-format
msgid "Advanced Usage"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:246
#, no-c-format
msgid "The <varname>USING</varname> 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 <varname>DATA</varname> definition) it is more difficult for mapserver to automatically determine a unique identifier for each row and also the SRID for the table. The <varname>USING</varname> clause can provide mapserver with these two pieces of information as follows:"
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:255
#, no-c-format
msgid ""
"DATA \"geom FROM (\n"
" SELECT \n"
" table1.geom AS geom, \n"
" table1.gid AS gid, \n"
" table2.data AS data \n"
" FROM table1 \n"
" LEFT JOIN table2 \n"
" ON table1.id = table2.id\n"
") AS new_table USING UNIQUE gid USING SRID=4326\""
msgstr ""
#. Tag: term
#: using_postgis_app.xml:259
#, no-c-format
msgid "USING UNIQUE &lt;uniqueid&gt;"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:262
#, no-c-format
msgid "MapServer requires a unique id for each row in order to identify the row when doing map queries. Normally it identifies the primary key from the system tables. However, views and subselects don't automatically have an known unique column. If you want to use MapServer's query functionality, you need to ensure your view or subselect includes a uniquely valued column, and declare it with <varname>USING UNIQUE</varname>. For example, you could explicitly select nee of the table's primary key values for this purpose, or any other column which is guaranteed to be unique for the result set."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:273
#, no-c-format
msgid "\"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 <varname>DATA</varname> definition."
msgstr ""
#. Tag: term
#: using_postgis_app.xml:282
#, no-c-format
msgid "USING SRID=&lt;srid&gt;"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:285
#, no-c-format
msgid "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 <varname>USING SRID=</varname> option allows the correct SRID to be specified in the <varname>DATA</varname> definition."
msgstr ""
#. Tag: title
#: using_postgis_app.xml:300
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:302
#, no-c-format
msgid "Lets start with a simple example and work our way up. Consider the following MapServer layer definition:"
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:305
#, no-c-format
msgid ""
"LAYER \n"
" CONNECTIONTYPE postgis \n"
" NAME \"roads\"\n"
" CONNECTION \"user=theuser password=thepass dbname=thedb host=theserver\" \n"
" DATA \"geom from roads\" \n"
" STATUS ON \n"
" TYPE LINE \n"
" CLASS \n"
" STYLE\n"
" COLOR 0 0 0 \n"
" END\n"
" END \n"
"END"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:307
#, no-c-format
msgid "This layer will display all the road geometries in the roads table as black lines."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:310
#, no-c-format
msgid "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:"
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:314
#, no-c-format
msgid ""
"LAYER \n"
" CONNECTIONTYPE postgis \n"
" CONNECTION \"user=theuser password=thepass dbname=thedb host=theserver\" \n"
" PROCESSING \"CLOSE_CONNECTION=DEFER\"\n"
" DATA \"geom from roads\"\n"
" MINSCALE 100000 \n"
" STATUS ON \n"
" TYPE LINE \n"
" FILTER \"road_type = 'highway'\" \n"
" CLASS \n"
" COLOR 0 0 0 \n"
" END \n"
"END \n"
"LAYER \n"
" CONNECTIONTYPE postgis \n"
" CONNECTION \"user=theuser password=thepass dbname=thedb host=theserver\"\n"
" PROCESSING \"CLOSE_CONNECTION=DEFER\"\n"
" DATA \"geom from roads\" \n"
" MAXSCALE 100000 \n"
" STATUS ON \n"
" TYPE LINE\n"
" CLASSITEM road_type \n"
" CLASS \n"
" EXPRESSION \"highway\" \n"
" STYLE\n"
" WIDTH 2 \n"
" COLOR 255 0 0 \n"
" END\n"
" END \n"
" CLASS \n"
" STYLE\n"
" COLOR 0 0 0 \n"
" END\n"
" END \n"
"END"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:316
#, no-c-format
msgid "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 <varname>FILTER</varname> option causes only roads of type \"highway\" to be displayed."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:321
#, no-c-format
msgid "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."
msgstr ""
#. Tag: para
#: using_postgis_app.xml:325
#, no-c-format
msgid "So, we have done a couple of interesting things using only MapServer functionality, but our <varname>DATA</varname> 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."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:331
#, no-c-format
msgid ""
"LAYER \n"
" CONNECTIONTYPE postgis\n"
" CONNECTION \"user=theuser password=thepass dbname=thedb host=theserver\" \n"
" DATA \"geom FROM (SELECT roads.gid AS gid, roads.geom AS geom, \n"
" road_names.name as name FROM roads LEFT JOIN road_names ON \n"
" roads.road_name_id = road_names.road_name_id) \n"
" AS named_roads USING UNIQUE gid USING SRID=4326\" \n"
" MAXSCALE 20000 \n"
" STATUS ON \n"
" TYPE ANNOTATION \n"
" LABELITEM name\n"
" CLASS \n"
" LABEL \n"
" ANGLE auto \n"
" SIZE 8 \n"
" COLOR 0 192 0 \n"
" TYPE truetype \n"
" FONT arial\n"
" END\n"
" END \n"
"END"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:333
#, no-c-format
msgid "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 <varname>DATA</varname> definition."
msgstr ""
#. Tag: title
#: using_postgis_app.xml:340
#, no-c-format
msgid "Java Clients (JDBC)"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:342
#, no-c-format
msgid "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."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:348
#, no-c-format
msgid ""
"import java.sql.*; \n"
"import java.util.*; \n"
"import java.lang.*; \n"
"import org.postgis.*; \n"
"\n"
"public class JavaGIS { \n"
"\n"
"public static void main(String[] args) { \n"
"\n"
" java.sql.Connection conn; \n"
"\n"
" try { \n"
" /* \n"
" * Load the JDBC driver and establish a connection. \n"
" */\n"
" Class.forName(\"org.postgresql.Driver\"); \n"
" String url = \"jdbc:postgresql://localhost:5432/database\"; \n"
" conn = DriverManager.getConnection(url, \"postgres\", \"\"); \n"
" /* \n"
" * Add the geometry types to the connection. Note that you \n"
" * must cast the connection to the pgsql-specific connection \n"
" * implementation before calling the addDataType() method. \n"
" */\n"
" ((org.postgresql.PGConnection)conn).addDataType(\"geometry\",Class.forName(\"org.postgis.PGgeometry\"));\n"
" ((org.postgresql.PGConnection)conn).addDataType(\"box3d\",Class.forName(\"org.postgis.PGbox3d\"));\n"
" /* \n"
" * Create a statement and execute a select query. \n"
" */ \n"
" Statement s = conn.createStatement(); \n"
" ResultSet r = s.executeQuery(\"select geom,id from geomtable\"); \n"
" while( r.next() ) { \n"
" /* \n"
" * Retrieve the geometry as an object then cast it to the geometry type. \n"
" * Print things out. \n"
" */ \n"
" PGgeometry geom = (PGgeometry)r.getObject(1); \n"
" int id = r.getInt(2); \n"
" System.out.println(\"Row \" + id + \":\");\n"
" System.out.println(geom.toString()); \n"
" } \n"
" s.close(); \n"
" conn.close(); \n"
" } \n"
"catch( Exception e ) { \n"
" e.printStackTrace(); \n"
" } \n"
"} \n"
"}"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:350
#, no-c-format
msgid "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."
msgstr ""
#. Tag: programlisting
#: using_postgis_app.xml:355
#, no-c-format
msgid ""
"PGgeometry geom = (PGgeometry)r.getObject(1); \n"
"if( geom.getType() == Geometry.POLYGON ) { \n"
" Polygon pl = (Polygon)geom.getGeometry(); \n"
" for( int r = 0; r &lt; pl.numRings(); r++) { \n"
" LinearRing rng = pl.getRing(r); \n"
" System.out.println(\"Ring: \" + r); \n"
" for( int p = 0; p &lt; rng.numPoints(); p++ ) { \n"
" Point pt = rng.getPoint(p); \n"
" System.out.println(\"Point: \" + p);\n"
" System.out.println(pt.toString()); \n"
" } \n"
" } \n"
"}"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:357
#, no-c-format
msgid "The JavaDoc for the extension objects provides a reference for the various data accessor functions in the geometric objects."
msgstr ""
#. Tag: title
#: using_postgis_app.xml:362
#, no-c-format
msgid "C Clients (libpq)"
msgstr ""
#. Tag: para
#: using_postgis_app.xml:364 using_postgis_app.xml:369 using_postgis_app.xml:375
#, no-c-format
msgid "<para>...</para>"
msgstr ""
#. Tag: title
#: using_postgis_app.xml:367
#, no-c-format
msgid "Text Cursors"
msgstr ""
#. Tag: title
#: using_postgis_app.xml:373
#, no-c-format
msgid "Binary Cursors"
msgstr ""

3084
doc/po/templates/using_postgis_dataman.xml.pot Normal file
View file

File diff suppressed because it is too large Load diff

1264
doc/po/templates/using_raster_dataman.xml.pot Normal file
View file

File diff suppressed because it is too large Load diff