From bea01616985c834e7d0c12ef2605fa0b1dddc491 Mon Sep 17 00:00:00 2001 From: Sandro Santilli Date: Tue, 29 Sep 2015 19:29:51 +0000 Subject: [PATCH] update-po after new german translation was added git-svn-id: http://svn.osgeo.org/postgis/trunk@14140 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/po/de_DE/extras.xml.po | 7 +- .../de_DE/extras_address_standardizer.xml.po | 264 +- doc/po/de_DE/extras_historytable.xml.po | 158 +- doc/po/de_DE/extras_tigergeocoder.xml.po | 792 +- doc/po/de_DE/extras_topology.xml.po | 938 +-- doc/po/de_DE/faq.xml.po | 396 +- doc/po/de_DE/faq_raster.xml.po | 214 +- doc/po/de_DE/installation.xml.po | 705 +- doc/po/de_DE/introduction.xml.po | 93 +- doc/po/de_DE/performance_tips.xml.po | 100 +- doc/po/de_DE/postgis.xml.po | 26 +- doc/po/de_DE/reference.xml.po | 21 +- doc/po/de_DE/reference_accessor.xml.po | 529 +- doc/po/de_DE/reference_constructor.xml.po | 657 +- doc/po/de_DE/reference_editor.xml.po | 580 +- doc/po/de_DE/reference_exception.xml.po | 23 +- doc/po/de_DE/reference_guc.xml.po | 55 +- doc/po/de_DE/reference_lrs.xml.po | 155 +- doc/po/de_DE/reference_management.xml.po | 371 +- doc/po/de_DE/reference_measure.xml.po | 1142 +-- doc/po/de_DE/reference_misc.xml.po | 196 +- doc/po/de_DE/reference_operator.xml.po | 317 +- doc/po/de_DE/reference_output.xml.po | 533 +- doc/po/de_DE/reference_processing.xml.po | 1030 +-- doc/po/de_DE/reference_raster.xml.po | 5946 +++++++-------- doc/po/de_DE/reference_sfcgal.xml.po | 148 +- doc/po/de_DE/reference_temporal.xml.po | 277 + doc/po/de_DE/reference_transaction.xml.po | 83 +- doc/po/de_DE/reference_type.xml.po | 17 +- doc/po/de_DE/release_notes.xml.po | 6352 +++++++++++++++++ doc/po/de_DE/reporting.xml.po | 136 + doc/po/de_DE/using_postgis_app.xml.po | 659 ++ doc/po/de_DE/using_postgis_dataman.xml.po | 3110 ++++++++ doc/po/de_DE/using_raster_dataman.xml.po | 1317 ++++ 34 files changed, 20180 insertions(+), 7167 deletions(-) create mode 100644 doc/po/de_DE/reference_temporal.xml.po create mode 100644 doc/po/de_DE/release_notes.xml.po create mode 100644 doc/po/de_DE/reporting.xml.po create mode 100644 doc/po/de_DE/using_postgis_app.xml.po create mode 100644 doc/po/de_DE/using_postgis_dataman.xml.po create mode 100644 doc/po/de_DE/using_raster_dataman.xml.po diff --git a/doc/po/de_DE/extras.xml.po b/doc/po/de_DE/extras.xml.po index 9bdd75b9b..ef3e71138 100644 --- a/doc/po/de_DE/extras.xml.po +++ b/doc/po/de_DE/extras.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2014-10-14 22:30+0000\n" "PO-Revision-Date: 2015-09-29 11:54+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title diff --git a/doc/po/de_DE/extras_address_standardizer.xml.po b/doc/po/de_DE/extras_address_standardizer.xml.po index f6f36affd..defd1cca2 100644 --- a/doc/po/de_DE/extras_address_standardizer.xml.po +++ b/doc/po/de_DE/extras_address_standardizer.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:22+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -25,19 +26,18 @@ msgstr "" #: extras_address_standardizer.xml:4 #, no-c-format msgid "" -"This is a fork of the PAGC " -"standardizer (original code for this portion was PAGC PostgreSQL Address Standardizer)." +"This is a fork of the PAGC standardizer (original code for this portion was PAGC PostgreSQL Address Standardizer)." msgstr "" #. Tag: para #: extras_address_standardizer.xml:5 #, no-c-format msgid "" -"The address standardizer is a single line address parser that takes an input" -" address and normalizes it based on a set of rules stored in a table and " +"The address standardizer is a single line address parser that takes an input " +"address and normalizes it based on a set of rules stored in a table and " "helper lex and gaz tables." msgstr "" @@ -58,17 +58,16 @@ msgstr "" #: extras_address_standardizer.xml:7 #, no-c-format msgid "" -"The code for this extension can be found in the PostGIS " -"extensions/address_standardizer and is currently self-" -"contained." +"The code for this extension can be found in the PostGIS extensions/" +"address_standardizer and is currently self-contained." msgstr "" #. Tag: para #: extras_address_standardizer.xml:8 #, no-c-format msgid "" -"For installation instructions refer to: ." +"For installation instructions refer to: ." msgstr "" #. Tag: title @@ -83,8 +82,8 @@ msgstr "" msgid "" "The parser works from right to left looking first at the macro elements for " "postcode, state/province, city, and then looks micro elements to determine " -"if we are dealing with a house number street or intersection or landmark. It" -" currently does not look for a country code or name, but that could be " +"if we are dealing with a house number street or intersection or landmark. It " +"currently does not look for a country code or name, but that could be " "introduced in the future." msgstr "" @@ -112,8 +111,8 @@ msgstr "" #: extras_address_standardizer.xml:22 #, no-c-format msgid "" -"These are recognized using Perl compatible regular expressions. These regexs" -" are currently in the parseaddress-api.c and are relatively simple to make " +"These are recognized using Perl compatible regular expressions. These regexs " +"are currently in the parseaddress-api.c and are relatively simple to make " "changes to if needed." msgstr "" @@ -127,9 +126,9 @@ msgstr "" #: extras_address_standardizer.xml:28 #, no-c-format msgid "" -"These are recognized using Perl compatible regular expressions. These regexs" -" are currently in the parseaddress-api.c but could get moved into includes " -"in the future for easier maintenance." +"These are recognized using Perl compatible regular expressions. These regexs " +"are currently in the parseaddress-api.c but could get moved into includes in " +"the future for easier maintenance." msgstr "" #. Tag: para @@ -137,8 +136,8 @@ msgstr "" #, no-c-format msgid "" "This section lists the PostgreSQL data types installed by Address " -"Standardizer extension. Note we describe the casting behavior of these which" -" is very important especially when designing your own functions." +"Standardizer extension. Note we describe the casting behavior of these which " +"is very important especially when designing your own functions." msgstr "" #. Tag: title @@ -173,19 +172,18 @@ msgstr "Beschreibung" #: extras_address_standardizer.xml:50 #, no-c-format msgid "" -"A composite type that consists of elements of an address. This is the return" -" type for function. Some " -"descriptions for elements are borrowed from PAGC Postal " -"Attributes." +"A composite type that consists of elements of an address. This is the return " +"type for function. Some descriptions " +"for elements are borrowed from PAGC Postal Attributes." msgstr "" #. Tag: para #: extras_address_standardizer.xml:51 #, no-c-format msgid "" -"The token numbers denote the output reference number in the ." +"The token numbers denote the output reference number in the ." msgstr "" #. Tag: para @@ -285,9 +283,9 @@ msgstr "" #: extras_address_standardizer.xml:85 extras_address_standardizer.xml:420 #, no-c-format msgid "" -"is text (token number 6): STREET POST TYPE e.g. St, Ave, Cir. A" -" street type following the root street name. Example " -"STREET in 75 State Street." +"is text (token number 6): STREET POST TYPE e.g. St, Ave, Cir. A " +"street type following the root street name. Example STREET in 75 State Street." msgstr "" #. Tag: term @@ -300,9 +298,9 @@ msgstr "" #: extras_address_standardizer.xml:90 extras_address_standardizer.xml:425 #, no-c-format msgid "" -"is text (token number 7): STREET POST-DIRECTIONAL A directional" -" modifier that follows the street name.. Example WEST " -"in 3715 TENTH AVENUE WEST." +"is text (token number 7): STREET POST-DIRECTIONAL A directional " +"modifier that follows the street name.. Example WEST in " +"3715 TENTH AVENUE WEST." msgstr "" #. Tag: term @@ -315,8 +313,8 @@ msgstr "" #: extras_address_standardizer.xml:95 #, no-c-format msgid "" -"is text (token number 8): RURAL ROUTE . Example " -"8 in RR 7." +"is text (token number 8): RURAL ROUTE . Example 8 in RR 7." msgstr "" #. Tag: term @@ -448,8 +446,8 @@ msgstr "" msgid "" "The rules table contains a set of rules that maps address input sequence " "tokens to standardized output sequence. A rule is defined as a set of input " -"tokens followed by -1 (terminator) followed by set of output tokens followed" -" by -1 followed by number denoting kind of rule followed by ranking of rule." +"tokens followed by -1 (terminator) followed by set of output tokens followed " +"by -1 followed by number denoting kind of rule followed by ranking of rule." msgstr "" #. Tag: para @@ -484,17 +482,17 @@ msgstr "" #: extras_address_standardizer.xml:165 #, no-c-format msgid "" -"text field denoting the rule. Details at PAGC Address" -" Standardizer Rule records." +"text field denoting the rule. Details at PAGC Address Standardizer Rule records." msgstr "" #. Tag: para #: extras_address_standardizer.xml:166 #, no-c-format msgid "" -"A rule consists of a set of non-negative integers representing input tokens," -" terminated by a -1, followed by an equal number of non-negative integers " +"A rule consists of a set of non-negative integers representing input tokens, " +"terminated by a -1, followed by an equal number of non-negative integers " "representing postal attributes, terminated by a -1, followed by an integer " "representing a rule type, followed by an integer representing the rank of " "the rule. The rules are ranked from 0 (lowest) to 17 (highest)." @@ -505,17 +503,17 @@ msgstr "" #, no-c-format msgid "" "So for example the rule 2 0 2 22 3 -1 5 5 6 7 3 -1 2 6 maps to " -"sequence of output tokens TYPE NUMBER TYPE DIRECT " -"QUALIF to the output sequence STREET STREET SUFTYP " -"SUFDIR QUALIF. The rule is an ARC_C rule of rank 6." +"sequence of output tokens TYPE NUMBER TYPE DIRECT QUALIF to the output sequence STREET STREET SUFTYP SUFDIR " +"QUALIF. The rule is an ARC_C rule of rank 6." msgstr "" #. Tag: para #: extras_address_standardizer.xml:168 #, no-c-format msgid "" -"Numbers for corresponding output tokens are listed in ." +"Numbers for corresponding output tokens are listed in ." msgstr "" #. Tag: title @@ -529,9 +527,9 @@ msgstr "" #, no-c-format msgid "" "Each rule starts with a set of input tokens followed by a terminator " -"-1. Valid input tokens excerpted from PAGC Input " -"Tokens are as follows:" +"-1. Valid input tokens excerpted from PAGC Input Tokens are as " +"follows:" msgstr "" #. Tag: emphasis @@ -550,8 +548,8 @@ msgstr "" #: extras_address_standardizer.xml:181 #, no-c-format msgid "" -"(13). The ampersand (&) is frequently used to abbreviate the word " -"\"and\"." +"(13). The ampersand (&) is frequently used to abbreviate the word \"and" +"\"." msgstr "" #. Tag: term @@ -600,8 +598,8 @@ msgstr "" #: extras_address_standardizer.xml:209 #, no-c-format msgid "" -"(23). An alphanumeric string that contains both letters and digits. Used for" -" identifiers." +"(23). An alphanumeric string that contains both letters and digits. Used for " +"identifiers." msgstr "" #. Tag: term @@ -625,8 +623,7 @@ msgstr "" #. Tag: para #: extras_address_standardizer.xml:223 #, no-c-format -msgid "" -"(15). Representations such as First or 1st. Often used in street names." +msgid "(15). Representations such as First or 1st. Often used in street names." msgstr "" #. Tag: para @@ -665,8 +662,8 @@ msgstr "" #: extras_address_standardizer.xml:247 #, no-c-format msgid "" -"(14). Words used to denote post office boxes. For example " -"Box or PO Box." +"(14). Words used to denote post office boxes. For example Box or PO Box." msgstr "" #. Tag: term @@ -680,8 +677,8 @@ msgstr "" #, no-c-format msgid "" "(19). Words used to denote buildings or building complexes, usually as a " -"prefix. For example: Tower in Tower " -"7A." +"prefix. For example: Tower in Tower 7A." msgstr "" #. Tag: term @@ -695,8 +692,8 @@ msgstr "" #, no-c-format msgid "" "(24). Words and abbreviations used to denote buildings or building " -"complexes, usually as a suffix. For example: Shopping " -"Centre." +"complexes, usually as a suffix. For example: Shopping Centre." msgstr "" #. Tag: term @@ -709,8 +706,8 @@ msgstr "" #: extras_address_standardizer.xml:268 #, no-c-format msgid "" -"(22). Words used to denote directions, for example " -"North." +"(22). Words used to denote directions, for example North." msgstr "" #. Tag: term @@ -735,8 +732,8 @@ msgstr "" #: extras_address_standardizer.xml:282 #, no-c-format msgid "" -"(6). Words and abbreviations used to denote highways and roads. For example:" -" the Interstate in Interstate 5" +"(6). Words and abbreviations used to denote highways and roads. For example: " +"the Interstate in Interstate 5" msgstr "" #. Tag: term @@ -749,8 +746,8 @@ msgstr "" #: extras_address_standardizer.xml:289 #, no-c-format msgid "" -"(8). Words and abbreviations used to denote rural routes. " -"RR." +"(8). Words and abbreviations used to denote rural routes. RR." msgstr "" #. Tag: term @@ -821,8 +818,8 @@ msgstr "" #: extras_address_standardizer.xml:327 #, no-c-format msgid "" -"(27). A 3 character sequence of letter number letter. Identifies an FSA, the" -" first 3 characters of a Canadian postal code." +"(27). A 3 character sequence of letter number letter. Identifies an FSA, the " +"first 3 characters of a Canadian postal code." msgstr "" #. Tag: term @@ -835,8 +832,8 @@ msgstr "" #: extras_address_standardizer.xml:334 #, no-c-format msgid "" -"(26). A 3 character sequence of number letter number. Identifies an LDU, the" -" last 3 characters of a Canadian postal code." +"(26). A 3 character sequence of number letter number. Identifies an LDU, the " +"last 3 characters of a Canadian postal code." msgstr "" #. Tag: emphasis @@ -880,8 +877,8 @@ msgid "" "After the first -1 (terminator), follows the output tokens and their order, " "followed by a terminator -1. Numbers for corresponding output " "tokens are listed in . What are allowed is " -"dependent on kind of rule. Output tokens valid for each rule type are listed" -" in ." +"dependent on kind of rule. Output tokens valid for each rule type are listed " +"in ." msgstr "" #. Tag: title @@ -918,8 +915,8 @@ msgstr "" #, no-c-format msgid "" "MACRO_C output tokens (excerpted from " -"http://www.pagcgeo.org/docs/html/pagc-12.html#--r-typ--." +"http://www.pagcgeo.org/docs/html/pagc-12.html#--r-typ--." msgstr "" #. Tag: term @@ -985,8 +982,8 @@ msgstr "" #, no-c-format msgid "" "(token number = \"1\"). The class of " -"rules for parsing full MICRO clauses (such as House, street, sufdir, predir," -" pretyp, suftype, qualif) (ie ARC_C plus CIVIC_C). These rules are not used " +"rules for parsing full MICRO clauses (such as House, street, sufdir, predir, " +"pretyp, suftype, qualif) (ie ARC_C plus CIVIC_C). These rules are not used " "in the build phase." msgstr "" @@ -995,8 +992,8 @@ msgstr "" #, no-c-format msgid "" "MICRO_C output tokens (excerpted from " -"http://www.pagcgeo.org/docs/html/pagc-12.html#--r-typ--." +"http://www.pagcgeo.org/docs/html/pagc-12.html#--r-typ--." msgstr "" #. Tag: term @@ -1022,8 +1019,8 @@ msgstr "" #, no-c-format msgid "" "(token number = \"2\"). The class of " -"rules for parsing MICRO clauses, excluding the HOUSE attribute. As such uses" -" same set of output tokens as MICRO_C minus the HOUSE token." +"rules for parsing MICRO clauses, excluding the HOUSE attribute. As such uses " +"same set of output tokens as MICRO_C minus the HOUSE token." msgstr "" #. Tag: emphasis @@ -1060,8 +1057,8 @@ msgstr "" #, no-c-format msgid "" "EXTRA_C output tokens (excerpted from " -"http://www.pagcgeo.org/docs/html/pagc-12.html#--r-typ--." +"http://www.pagcgeo.org/docs/html/pagc-12.html#--r-typ--." msgstr "" #. Tag: term @@ -1073,8 +1070,7 @@ msgstr "" #. Tag: para #: extras_address_standardizer.xml:443 #, no-c-format -msgid "" -"(token number 0): Unparsed building identifiers and types." +msgid "(token number 0): Unparsed building identifiers and types." msgstr "" #. Tag: para @@ -1095,8 +1091,8 @@ msgstr "" #: extras_address_standardizer.xml:453 #, no-c-format msgid "" -"(token number 15): The 3B in" -" BOX 3B" +"(token number 15): The 3B in " +"BOX 3B" msgstr "" #. Tag: para @@ -1125,8 +1121,8 @@ msgstr "" #: extras_address_standardizer.xml:468 #, no-c-format msgid "" -"(token number 17): The 3B in" -" APT 3B" +"(token number 17): The 3B in " +"APT 3B" msgstr "" #. Tag: term @@ -1219,9 +1215,8 @@ msgstr "" #, no-c-format msgid "" "integer: the kind of word it is. Only if it is used in this context will it " -"be replaced. Refer to PAGC " -"Tokens." +"be replaced. Refer to PAGC Tokens." msgstr "" #. Tag: refname @@ -1234,8 +1229,8 @@ msgstr "" #: extras_address_standardizer.xml:525 #, no-c-format msgid "" -"A gaz table is used to standardize place names and associate that input with" -" (a) input tokens ( See ) and (b) " +"A gaz table is used to standardize place names and associate that input with " +"(a) input tokens ( See ) and (b) " "standardized representations." msgstr "" @@ -1294,12 +1289,11 @@ msgstr "" #: extras_address_standardizer.xml:588 #, no-c-format msgid "" -"Returns takes as input an address, and returns a record output consisting of" -" fields num, street, " -"street2, address1, " -"city, state, " -"zip, zipplus, " -"country." +"Returns takes as input an address, and returns a record output consisting of " +"fields num, street, " +"street2, address1, city, state, zip, " +"zipplus, country." msgstr "" #. Tag: para @@ -1318,7 +1312,8 @@ msgstr "Beispiele" #: extras_address_standardizer.xml:600 #, no-c-format msgid "" -"SELECT num, street, city, zip, zipplus FROM parse_address('1 Devonshire Place, Boston, MA 02109-1234');\n" +"SELECT num, street, city, zip, zipplus FROM parse_address('1 Devonshire " +"Place, Boston, MA 02109-1234');\n" " num | street | city | zip | zipplus\n" "-----+------------------+--------+-------+---------\n" " 1 | Devonshire Place | Boston | 02109 | 1234" @@ -1348,19 +1343,18 @@ msgstr "" #: extras_address_standardizer.xml:620 #, no-c-format msgid "" -" stdaddr " -"standardize_address text " -" lextab text " -" gaztab text " -" rultab text " -" address " -" stdaddr " -"standardize_address text " -" lextab text " -" gaztab text " -" rultab text " -" micro text " -" macro " +" stdaddr standardize_address text lextab text gaztab text rultab text address stdaddr " +"standardize_address text lextab text " +"gaztab text " +"rultab text " +"micro text " +"macro " msgstr "" #. Tag: para @@ -1368,8 +1362,8 @@ msgstr "" #, no-c-format msgid "" "Returns an form of an input address utilizing " -" table name, , and table names and an address." +" table name, , and table names and an address." msgstr "" #. Tag: para @@ -1382,18 +1376,24 @@ msgstr "" #: extras_address_standardizer.xml:654 #, no-c-format msgid "" -"CREATE EXTENSION address_standardizer_data_us; -- only needs to be done once\n" -"SELECT house_num, name, suftype, city, country, state, unit FROM standardize_address('us_lex', \n" -" 'us_gaz', 'us_rules', 'One Devonshire Place, PH 301, Boston, MA 02109-1234');" +"CREATE EXTENSION address_standardizer_data_us; -- only needs to be done " +"once\n" +"SELECT house_num, name, suftype, city, country, state, unit FROM " +"standardize_address('us_lex', \n" +" 'us_gaz', 'us_rules', 'One Devonshire Place, PH " +"301, Boston, MA 02109-1234');" msgstr "" #. Tag: screen #: extras_address_standardizer.xml:655 #, no-c-format msgid "" -"house_num | name | suftype | city | country | state | unit\n" -"----------+------------+---------+--------+---------+---------------+-----------------\n" -"1 | DEVONSHIRE | PLACE | BOSTON | USA | MASSACHUSETTS | # PENTHOUSE 301" +"house_num | name | suftype | city | country | state | " +"unit\n" +"----------+------------+---------+--------+---------+---------------" +"+-----------------\n" +"1 | DEVONSHIRE | PLACE | BOSTON | USA | MASSACHUSETTS | # " +"PENTHOUSE 301" msgstr "" #. Tag: para @@ -1409,7 +1409,8 @@ msgstr "" #, no-c-format msgid "" "SELECT * FROM standardize_address('tiger.pagc_lex', \n" -" 'tiger.pagc_gaz', 'tiger.pagc_rules', 'One Devonshire Place, PH 301, Boston, MA 02109-1234');" +" 'tiger.pagc_gaz', 'tiger.pagc_rules', 'One Devonshire Place, PH " +"301, Boston, MA 02109-1234');" msgstr "" #. Tag: para @@ -1426,7 +1427,8 @@ msgstr "" msgid "" "SELECT (each(hstore(p))).* \n" " FROM standardize_address('tiger.pagc_lex', 'tiger.pagc_gaz', \n" -" 'tiger.pagc_rules', 'One Devonshire Place, PH 301, Boston, MA 02109-1234') As p;" +" 'tiger.pagc_rules', 'One Devonshire Place, PH 301, Boston, MA " +"02109-1234') As p;" msgstr "" #. Tag: screen @@ -1458,6 +1460,6 @@ msgstr "" #: extras_address_standardizer.xml:668 #, no-c-format msgid "" -", , , , " +", , , , " msgstr "" diff --git a/doc/po/de_DE/extras_historytable.xml.po b/doc/po/de_DE/extras_historytable.xml.po index 126509077..686c16cc1 100644 --- a/doc/po/de_DE/extras_historytable.xml.po +++ b/doc/po/de_DE/extras_historytable.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: # Chris Leick , 2013 msgid "" @@ -9,11 +9,12 @@ msgstr "" "POT-Creation-Date: 2012-09-14 17:50+0000\n" "PO-Revision-Date: 2015-09-29 11:54+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -27,13 +28,21 @@ msgstr "Chronikverfolgung" #, 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 " +"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 " +"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 "Angenommen, Sie haben eine Datentabelle, die den aktuellen Status einer bestimmten geografischen Funktionalität darstellt, etwa eine Pakettabelle, eine Straßentabelle, eine Obstbaumtabelle oder was auch immer. Im Allgemeinen betrachten GIS-Werkzeuge eine Tabelle als eine einzelne Einheit, in der sie Zeilen aktualisieren, einfügen oder löschen können. Wie ermöglichen Sie üblichen GIS-Werkzeugen mit Ihren Daten zu arbeiten, wenn eine Kontrolle durchgeführt wird, welche Änderungen gemacht wurden, durch wen und was der frühere Status der Daten ist?" +msgstr "" +"Angenommen, Sie haben eine Datentabelle, die den aktuellen Status einer " +"bestimmten geografischen Funktionalität darstellt, etwa eine Pakettabelle, " +"eine Straßentabelle, eine Obstbaumtabelle oder was auch immer. Im " +"Allgemeinen betrachten GIS-Werkzeuge eine Tabelle als eine einzelne Einheit, " +"in der sie Zeilen aktualisieren, einfügen oder löschen können. Wie " +"ermöglichen Sie üblichen GIS-Werkzeugen mit Ihren Daten zu arbeiten, wenn " +"eine Kontrolle durchgeführt wird, welche Änderungen gemacht wurden, durch " +"wen und was der frühere Status der Daten ist?" #. Tag: para #: extras_historytable.xml:10 @@ -41,7 +50,9 @@ msgstr "Angenommen, Sie haben eine Datentabelle, die den aktuellen Status einer msgid "" "This history_table extra module provides some utility " "functions for creating and maintaining history." -msgstr "Dieses Zusatzmodul history_table stellt einige Hilfswerkzeuge zum Erstellen und Verwalten der Chronik bereit." +msgstr "" +"Dieses Zusatzmodul history_table stellt einige " +"Hilfswerkzeuge zum Erstellen und Verwalten der Chronik bereit." #. Tag: para #: extras_historytable.xml:14 @@ -51,7 +62,11 @@ msgid "" "added to the documentation in PostGIS 2.0. This package is written in " "plpgsql and located in the extras/history_table of " "PostGIS source tar balls and source repository." -msgstr "Die history_table wurde auch in PostGIS 1.5 paketiert, dieser Dokumentation aber erst in PostGIS 2.0 hinzugefügt. Dieses Paket wurde in PL/pgSQL geschrieben und befindet sich in extras/history_table der PostGIS-Quell-Tarballs und dem Quelldepot." +msgstr "" +"Die history_table wurde auch in PostGIS 1.5 paketiert, " +"dieser Dokumentation aber erst in PostGIS 2.0 hinzugefügt. Dieses Paket " +"wurde in PL/pgSQL geschrieben und befindet sich in extras/" +"history_table der PostGIS-Quell-Tarballs und dem Quelldepot." #. Tag: para #: extras_historytable.xml:15 @@ -60,7 +75,10 @@ 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 "Falls Sie eine Tabelle »roads« haben, wird dieses Modul eine Nebentabelle »roads_history« verwalten, die alle Spalten der übergeordneten Tabelle sowie die folgenden zusätzlichen Spalten enthält:" +msgstr "" +"Falls Sie eine Tabelle »roads« haben, wird dieses Modul eine Nebentabelle " +"»roads_history« verwalten, die alle Spalten der übergeordneten Tabelle sowie " +"die folgenden zusätzlichen Spalten enthält:" #. Tag: programlisting #: extras_historytable.xml:16 @@ -70,19 +88,32 @@ msgid "" " 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" +" active_user | character varying(90) | not null default " +"\"current_user\"()\n" +" current_version | text | not null" +msgstr "" +"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 "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" #. 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 " +"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 "Wenn Sie einen neuen Datensatz in »roads« einfügen, wird automatisch ein neuer Datensatz in »roads_history« eingefügt, bei dem »date_added« ausgefüllt und »date_deleted« auf NULL gesetzt wird. Er hat eine eindeutige »history_id«, eine »last_operation« von »INSERT« und einen gesetzten »active_user«." +msgstr "" +"Wenn Sie einen neuen Datensatz in »roads« einfügen, wird automatisch ein " +"neuer Datensatz in »roads_history« eingefügt, bei dem »date_added« " +"ausgefüllt und »date_deleted« auf NULL gesetzt wird. Er hat eine eindeutige " +"»history_id«, eine »last_operation« von »INSERT« und einen gesetzten " +"»active_user«." #. Tag: para #: extras_historytable.xml:23 @@ -90,7 +121,10 @@ msgstr "Wenn Sie einen neuen Datensatz in »roads« einfügen, wird automatisch 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 "Wenn Sie einen Datensatz aus »roads« löschen, wird der Datensatz *nicht* aus »roads_history« gelöscht, das »date_deleted« jedoch auf das aktuelle Datum gesetzt." +msgstr "" +"Wenn Sie einen Datensatz aus »roads« löschen, wird der Datensatz *nicht* aus " +"»roads_history« gelöscht, das »date_deleted« jedoch auf das aktuelle Datum " +"gesetzt." #. Tag: para #: extras_historytable.xml:26 @@ -99,7 +133,10 @@ 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 "Wenn Sie einen Datensatz in »roads« aktualisieren, wird beim aktuellen Datensatz »date_deleted« ausgefüllt und es wird ein neuer Datensatz mit gesetztem »date_added« erstellt, dessen »date_deleted« NULL ist." +msgstr "" +"Wenn Sie einen Datensatz in »roads« aktualisieren, wird beim aktuellen " +"Datensatz »date_deleted« ausgefüllt und es wird ein neuer Datensatz mit " +"gesetztem »date_added« erstellt, dessen »date_deleted« NULL ist." #. Tag: para #: extras_historytable.xml:30 @@ -107,7 +144,9 @@ msgstr "Wenn Sie einen Datensatz in »roads« aktualisieren, wird beim aktuellen msgid "" "With this information maintained, it is possible to retrieve the history of " "any record in the roads table:" -msgstr "Mit der Verwaltung dieser Informationen ist es möglich, die Chronik aller Datensätze in der Tabelle »roads« abzufragen:" +msgstr "" +"Mit der Verwaltung dieser Informationen ist es möglich, die Chronik aller " +"Datensätze in der Tabelle »roads« abzufragen:" #. Tag: programlisting #: extras_historytable.xml:31 @@ -119,7 +158,9 @@ msgstr "SELECT * FROM roads_history WHERE roads_pk = 111;" #: extras_historytable.xml:33 #, no-c-format msgid "Or, to retrieve a view of the roads table at any point in the past:" -msgstr "Oder, um eine Ansicht der Tabelle »roads« für einen beliebigen Zeitpunkt in der Vergangenheit zu erhalten:" +msgstr "" +"Oder, um eine Ansicht der Tabelle »roads« für einen beliebigen Zeitpunkt in " +"der Vergangenheit zu erhalten:" #. Tag: programlisting #: extras_historytable.xml:34 @@ -128,7 +169,10 @@ msgid "" "SELECT * FROM roads_history \n" " WHERE date_added < 'January 1, 2001' AND \n" " ( date_deleted >= 'January 1, 2001' OR date_deleted IS NULL );" -msgstr "SELECT * FROM roads_history \n WHERE date_added < '1. Januar 2001' AND \n ( date_deleted >= '1. Januar 2001' OR date_deleted IS NULL );" +msgstr "" +"SELECT * FROM roads_history \n" +" WHERE date_added < '1. Januar 2001' AND \n" +" ( date_deleted >= '1. Januar 2001' OR date_deleted IS NULL );" #. Tag: refname #: extras_historytable.xml:38 @@ -142,7 +186,9 @@ msgstr "Postgis_Install_History" msgid "" "Creates a table that will hold some interesting values for managing history " "tables." -msgstr "erstellt eine Tabelle, die einige interessante Werte zum Verwalten von Chroniktabellen bereithalten wird." +msgstr "" +"erstellt eine Tabelle, die einige interessante Werte zum Verwalten von " +"Chroniktabellen bereithalten wird." #. Tag: funcprototype #: extras_historytable.xml:44 @@ -150,7 +196,9 @@ msgstr "erstellt eine Tabelle, die einige interessante Werte zum Verwalten von C msgid "" "void Postgis_Install_History " "" -msgstr "void Postgis_Install_History " +msgstr "" +"void Postgis_Install_History " +"" #. Tag: title #: extras_historytable.xml:52 extras_historytable.xml:92 @@ -164,7 +212,10 @@ msgstr "Beschreibung" msgid "" "Creates a table that will hold some interesting values for managing history " "tables. Creates a table called historic_information" -msgstr "erstellt eine Tabelle, die einige interessante Werte zum Verwalten von Chroniktabellen bereithalten wird. Es wird eine Tabelle namens historic_information erstellt." +msgstr "" +"erstellt eine Tabelle, die einige interessante Werte zum Verwalten von " +"Chroniktabellen bereithalten wird. Es wird eine Tabelle namens " +"historic_information erstellt." #. Tag: para #: extras_historytable.xml:58 extras_historytable.xml:100 @@ -200,9 +251,12 @@ msgstr "Postgis_Enable_History" #: 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 "registriert eine Tabelle zur Verfolgung in der Tabelle »history_information« und fügt außerdem innerhalb eine Zeilenchroniktabelle sowie Regeln zum Einfügen, Löschen und Aktualisieren in der Tabelle ein." +"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 "" +"registriert eine Tabelle zur Verfolgung in der Tabelle »history_information« " +"und fügt außerdem innerhalb eine Zeilenchroniktabelle sowie Regeln zum " +"Einfügen, Löschen und Aktualisieren in der Tabelle ein." #. Tag: funcprototype #: extras_historytable.xml:83 @@ -211,7 +265,10 @@ msgid "" "boolean Postgis_Enable_History " "text p_schema " "text p_table" -msgstr "boolean Postgis_Enable_History text p_schema text p_table" +msgstr "" +"boolean Postgis_Enable_History " +"text p_schema " +"text p_table" #. Tag: para #: extras_historytable.xml:94 @@ -219,10 +276,16 @@ msgstr "boolean Postgis_Enable_History < 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 " -"history in the same schema as the original table. Puts in" -" insert, update, delete rules on the table. Any inserts,updates,deletes of " +"history 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 "registriert eine Tabelle zur Verfolgung in der Tabelle »history_information« und fügt außerdem innerhalb eine Zeilenchroniktabelle ein. Sie hat denselben Tabellennamen, dem jedoch ein history vorangestellt wird und dasselbe Schema wie die Originaltabelle. Darin werden Regeln zum Einfügen, Löschen und Aktualisieren in der Tabelle abgelegt. Jegliches Einfügen, Aktualisieren und Löschen wird in der Chroniktabelle aufgezeichnet." +msgstr "" +"registriert eine Tabelle zur Verfolgung in der Tabelle »history_information« " +"und fügt außerdem innerhalb eine Zeilenchroniktabelle ein. Sie hat denselben " +"Tabellennamen, dem jedoch ein history vorangestellt wird " +"und dasselbe Schema wie die Originaltabelle. Darin werden Regeln zum " +"Einfügen, Löschen und Aktualisieren in der Tabelle abgelegt. Jegliches " +"Einfügen, Aktualisieren und Löschen wird in der Chroniktabelle aufgezeichnet." #. Tag: para #: extras_historytable.xml:97 @@ -231,7 +294,11 @@ msgid "" "This function currently relies on a geometry column being registered in " "geometry_columns and fails if the geometry column is not " "present in geometry_columns table." -msgstr "Diese Funktion beruht derzeit darauf, dass eine Geometriespalte in geometry_columns registriert wurde. Sie scheitert, falls die Geometriespalte nicht in der Tabelle geometry_columns vorhanden ist." +msgstr "" +"Diese Funktion beruht derzeit darauf, dass eine Geometriespalte in " +"geometry_columns registriert wurde. Sie scheitert, falls " +"die Geometriespalte nicht in der Tabelle geometry_columns " +"vorhanden ist." #. Tag: programlisting #: extras_historytable.xml:107 @@ -246,7 +313,29 @@ msgid "" "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" +" 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 "" +"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" @@ -256,4 +345,3 @@ msgid "" " date_added | last_operation | current_version\n" "------------------------+----------------+-----------------\n" " 2011-02-07 12:44:36.92 | INSERT | 2" -msgstr "CREATE TABLE roads(gid SERIAL PRIMARY KEY, road_name varchar(150));\nSELECT AddGeometryColumn('roads', 'geom', 26986, 'LINESTRING', 2);\n \nSELECT postgis_enable_history('public', 'roads', 'geom') As register_table;\nregister_table\n--------------\nt\n\nINSERT 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 --\nSELECT date_added, last_operation, current_version \nFROM roads_history \nWHERE 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" diff --git a/doc/po/de_DE/extras_tigergeocoder.xml.po b/doc/po/de_DE/extras_tigergeocoder.xml.po index 604d20177..8feadf6fc 100644 --- a/doc/po/de_DE/extras_tigergeocoder.xml.po +++ b/doc/po/de_DE/extras_tigergeocoder.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,21 +8,22 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:23+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: para #: extras_tigergeocoder.xml:6 #, no-c-format msgid "" -"A plpgsql based geocoder written to work with the TIGER (Topologically Integrated" -" Geographic Encoding and Referencing system ) / Line and Master Address " -"database export released by the US Census Bureau." +"A plpgsql based geocoder written to work with the TIGER (Topologically Integrated Geographic " +"Encoding and Referencing system ) / Line and Master Address database export released by the US Census Bureau." msgstr "" #. Tag: para @@ -59,11 +60,11 @@ msgid "" "Another schema called tiger_data is also created which " "houses all the census data for each state that the loader downloads from " "Census site and loads into the database. In the current model, each set of " -"state tables is prefixed with the state code e.g ma_addr," -" ma_edges etc with constraints to enforce only that state" -" data. Each of these tables inherits from the tables " -"addr, faces, edges," -" etc located in the tiger schema." +"state tables is prefixed with the state code e.g ma_addr, " +"ma_edges etc with constraints to enforce only that state " +"data. Each of these tables inherits from the tables addr, " +"faces, edges, etc located in the " +"tiger schema." msgstr "" #. Tag: para @@ -72,9 +73,9 @@ msgstr "" msgid "" "All the geocode functions only reference the base tables, so there is no " "requirement that the data schema be called tiger_data or " -"that data can't be further partitioned into other schemas -- e.g a different" -" schema for each state, as long as all the tables inherit from the tables in" -" the tiger schema." +"that data can't be further partitioned into other schemas -- e.g a different " +"schema for each state, as long as all the tables inherit from the tables in " +"the tiger schema." msgstr "" #. Tag: para @@ -84,18 +85,18 @@ msgid "" "If you are using tiger geocoder (tiger_2010), you can upgrade the scripts " "using the accompanying upgrade_geocoder.bat / .sh scripts in extras/tiger. " "One major change between tiger_2010 and " -"tiger_2011+ is that the county and " -"county and state tables are no longer " -"broken out by state. If you have data from tiger_2010 and want replace with " -"tiger_2015 refer to " +"tiger_2011+ is that the county and county and state tables are no longer broken out by " +"state. If you have data from tiger_2010 and want replace with tiger_2015 " +"refer to " msgstr "" #. Tag: para #: extras_tigergeocoder.xml:23 #, no-c-format msgid "" -"New in PostGIS 2.2.0 release is support for Tiger 2015 data and inclusion of" -" Address Standardizer as part of PostGIS." +"New in PostGIS 2.2.0 release is support for Tiger 2015 data and inclusion of " +"Address Standardizer as part of PostGIS." msgstr "" #. Tag: para @@ -128,9 +129,9 @@ msgstr "" #, no-c-format msgid "" "The goal of this project is to build a fully functional geocoder that can " -"process an arbitrary United States address string and using normalized TIGER" -" census data, produce a point geometry and rating reflecting the location of" -" the given address and likeliness of the location. The higher the rating " +"process an arbitrary United States address string and using normalized TIGER " +"census data, produce a point geometry and rating reflecting the location of " +"the given address and likeliness of the location. The higher the rating " "number the worse the result." msgstr "" @@ -138,8 +139,8 @@ msgstr "" #: extras_tigergeocoder.xml:33 #, no-c-format msgid "" -"The reverse_geocode function, introduced in PostGIS 2.0.0" -" is useful for deriving the street address and cross streets of a GPS " +"The reverse_geocode function, introduced in PostGIS 2.0.0 " +"is useful for deriving the street address and cross streets of a GPS " "location." msgstr "" @@ -194,15 +195,14 @@ msgstr "" #: extras_tigergeocoder.xml:46 #, no-c-format msgid "" -"Nominatim and " -"uses OpenStreetMap gazeteer formatted data. It requires osm2pgsql for " -"loading the data, PostgreSQL 8.4+ and PostGIS 1.5+ to function. It is " +"Nominatim and uses OpenStreetMap gazeteer formatted data. It requires osm2pgsql " +"for loading the data, PostgreSQL 8.4+ and PostGIS 1.5+ to function. It is " "packaged as a webservice interface and seems designed to be called as a " "webservice. Just like the tiger geocoder, it has both a geocoder and a " "reverse geocoder component. From the documentation, it is unclear if it has " -"a pure SQL interface like the tiger geocoder, or if a good deal of the logic" -" is implemented in the web interface." +"a pure SQL interface like the tiger geocoder, or if a good deal of the logic " +"is implemented in the web interface." msgstr "" #. Tag: para @@ -213,8 +213,8 @@ msgid "" "PostGIS and like Nominatim works with OpenStreetMap (OSM) data. It comes " "with a loader to load OSM data and similar to Nominatim is capable of " "geocoding not just US. Much like Nominatim, it runs as a webservice and " -"relies on Java 1.5, Servlet apps, Solr. GisGraphy is cross-platform and also" -" has a reverse geocoder among some other neat features." +"relies on Java 1.5, Servlet apps, Solr. GisGraphy is cross-platform and also " +"has a reverse geocoder among some other neat features." msgstr "" #. Tag: refname @@ -227,8 +227,8 @@ msgstr "" #: extras_tigergeocoder.xml:56 #, no-c-format msgid "" -"Generates a script that drops all non-primary key and non-unique" -" indexes on tiger schema and user specified schema. Defaults schema to " +"Generates a script that drops all non-primary key and non-unique " +"indexes on tiger schema and user specified schema. Defaults schema to " "tiger_data if no schema is specified." msgstr "" @@ -268,10 +268,9 @@ msgstr "" #: extras_tigergeocoder.xml:72 #, no-c-format msgid "" -"This is useful for minimizing index bloat that may confuse the query planner" -" or take up unnecessary space. Use in combination with to add just the indexes used by the " -"geocoder." +"This is useful for minimizing index bloat that may confuse the query planner " +"or take up unnecessary space. Use in combination with to add just the indexes used by the geocoder." msgstr "" #. Tag: para @@ -374,9 +373,8 @@ msgstr "" #: extras_tigergeocoder.xml:103 #, no-c-format msgid "" -"text " -"Drop_Nation_Tables_Generate_Script text " +"text Drop_Nation_Tables_Generate_Script text " "param_schema=tiger_data" msgstr "" @@ -386,8 +384,8 @@ msgstr "" msgid "" "Generates a script that drops all tables in the specified schema that start " "with county_all, state_all or stae " -"code followed by county or state. This" -" is needed if you are upgrading from tiger_2010 to " +"code followed by county or state. This " +"is needed if you are upgrading from tiger_2010 to " "tiger_2011 data." msgstr "" @@ -430,10 +428,9 @@ msgstr "" #: extras_tigergeocoder.xml:144 #, no-c-format msgid "" -"text " -"Drop_State_Tables_Generate_Script " -"text param_state " -"text " +"text Drop_State_Tables_Generate_Script text param_state text " "param_schema=tiger_data" msgstr "" @@ -444,8 +441,8 @@ msgid "" "Generates a script that drops all tables in the specified schema that are " "prefixed with the state abbreviation. Defaults schema to " "tiger_data if no schema is specified. This function is " -"useful for dropping tables of a state just before you reload a state in case" -" something went wrong during your previous load." +"useful for dropping tables of a state just before you reload a state in case " +"something went wrong during your previous load." msgstr "" #. Tag: programlisting @@ -478,37 +475,35 @@ msgstr "" #, no-c-format msgid "" "Takes in an address as a string (or other normalized address) and outputs a " -"set of possible locations which include a point geometry in NAD 83 long lat," -" a normalized address for each, and the rating. The lower the rating the " -"more likely the match. Results are sorted by lowest rating first. Can " -"optionally pass in maximum results, defaults to 10, and restrict_region " -"(defaults to NULL)" +"set of possible locations which include a point geometry in NAD 83 long lat, " +"a normalized address for each, and the rating. The lower the rating the more " +"likely the match. Results are sorted by lowest rating first. Can optionally " +"pass in maximum results, defaults to 10, and restrict_region (defaults to " +"NULL)" msgstr "" #. Tag: funcsynopsis #: extras_tigergeocoder.xml:186 #, no-c-format msgid "" -" setof record geocode" -" varchar address " -"integer " -"max_results=10 geometry " +" setof record geocode " +"varchar address " +"integer max_results=10 geometry " "restrict_region=NULL " -"norm_addy OUT addy" -" geometry OUT " -"geomout integer " -"OUT rating " -" setof record geocode" -" norm_addy in_addy" -" integer " -"max_results=10 geometry " +"norm_addy OUT addy " +"geometry OUT geomout integer OUT rating setof record " +"geocode norm_addy " +"in_addy integer max_results=10 " +"geometry " "restrict_region=NULL " -"norm_addy OUT addy" -" geometry OUT " -"geomout integer " -"OUT rating " +"norm_addy OUT addy " +"geometry OUT geomout integer OUT rating " msgstr "" #. Tag: para @@ -519,22 +514,22 @@ msgid "" "a set of possible locations which include a point geometry in NAD 83 long " "lat, a normalized_address (addy) for each, and the " "rating. The lower the rating the more likely the match. Results are sorted " -"by lowest rating first. Uses Tiger data (edges,faces,addr), PostgreSQL fuzzy" -" string matching (soundex,levenshtein) and PostGIS line interpolation " +"by lowest rating first. Uses Tiger data (edges,faces,addr), PostgreSQL fuzzy " +"string matching (soundex,levenshtein) and PostGIS line interpolation " "functions to interpolate address along the Tiger edges. The higher the " -"rating the less likely the geocode is right. The geocoded point is defaulted" -" to offset 10 meters from center-line off to side (L/R) of street address is" -" located on." +"rating the less likely the geocode is right. The geocoded point is defaulted " +"to offset 10 meters from center-line off to side (L/R) of street address is " +"located on." msgstr "" #. Tag: para #: extras_tigergeocoder.xml:215 #, no-c-format msgid "" -"Enhanced: 2.0.0 to support Tiger 2010 structured data and revised some logic" -" to improve speed, accuracy of geocoding, and to offset point from " -"centerline to side of street address is located on. New parameter " -"max_results useful for specifying ot just return the best result." +"Enhanced: 2.0.0 to support Tiger 2010 structured data and revised some logic " +"to improve speed, accuracy of geocoding, and to offset point from centerline " +"to side of street address is located on. New parameter max_results useful " +"for specifying ot just return the best result." msgstr "" #. Tag: title @@ -565,11 +560,15 @@ msgstr "" msgid "" "SELECT g.rating, ST_X(g.geomout) As lon, ST_Y(g.geomout) As lat, \n" " (addy).address As stno, (addy).streetname As street, \n" -" (addy).streettypeabbrev As styp, (addy).location As city, (addy).stateabbrev As st,(addy).zip \n" +" (addy).streettypeabbrev As styp, (addy).location As city, (addy)." +"stateabbrev As st,(addy).zip \n" " FROM geocode('75 State Street, Boston MA 02109') As g; \n" -" rating | lon | lat | stno | street | styp | city | st | zip \n" -"--------+-------------------+------------------+------+--------+------+--------+----+-------\n" -" 0 | -71.0556722990239 | 42.3589914927049 | 75 | State | St | Boston | MA | 02109" +" rating | lon | lat | stno | street | styp | " +"city | st | zip \n" +"--------+-------------------+------------------+------+--------+------" +"+--------+----+-------\n" +" 0 | -71.0556722990239 | 42.3589914927049 | 75 | State | St | " +"Boston | MA | 02109" msgstr "" #. Tag: para @@ -585,11 +584,15 @@ msgstr "" msgid "" "SELECT g.rating, ST_AsText(ST_SnapToGrid(g.geomout,0.00001)) As wktlonlat, \n" " (addy).address As stno, (addy).streetname As street, \n" -" (addy).streettypeabbrev As styp, (addy).location As city, (addy).stateabbrev As st,(addy).zip \n" +" (addy).streettypeabbrev As styp, (addy).location As city, (addy)." +"stateabbrev As st,(addy).zip \n" " FROM geocode('226 Hanover Street, Boston, MA',1) As g; \n" -" rating | wktlonlat | stno | street | styp | city | st | zip \n" -"--------+---------------------------+------+---------+------+--------+----+-------\n" -" 1 | POINT(-71.05528 42.36316) | 226 | Hanover | St | Boston | MA | 02113" +" rating | wktlonlat | stno | street | styp | city | st | " +"zip \n" +"--------+---------------------------+------+---------+------+--------+----" +"+-------\n" +" 1 | POINT(-71.05528 42.36316) | 226 | Hanover | St | Boston | MA | " +"02113" msgstr "" #. Tag: para @@ -606,11 +609,15 @@ msgstr "" msgid "" "SELECT g.rating, ST_AsText(ST_SnapToGrid(g.geomout,0.00001)) As wktlonlat, \n" " (addy).address As stno, (addy).streetname As street, \n" -" (addy).streettypeabbrev As styp, (addy).location As city, (addy).stateabbrev As st,(addy).zip \n" +" (addy).streettypeabbrev As styp, (addy).location As city, (addy)." +"stateabbrev As st,(addy).zip \n" " FROM geocode('31 - 37 Stewart Street, Boston, MA 02116') As g; \n" -" rating | wktlonlat | stno | street | styp | city | st | zip \n" -"--------+---------------------------+------+--------+------+--------+----+-------\n" -" 70 | POINT(-71.06459 42.35113) | 31 | Stuart | St | Boston | MA | 02116" +" rating | wktlonlat | stno | street | styp | city | st | " +"zip \n" +"--------+---------------------------+------+--------+------+--------+----" +"+-------\n" +" 70 | POINT(-71.06459 42.35113) | 31 | Stuart | St | Boston | MA | " +"02116" msgstr "" #. Tag: para @@ -637,7 +644,8 @@ msgid "" " ('124 Mount Auburn St, Cambridge, Massachusetts 02138'),\n" " ('950 Main Street, Worcester, MA 01610');\n" " \n" -"-- only update the first 3 addresses (323-704 ms - there are caching and shared memory effects so first geocode you do is always slower) --\n" +"-- only update the first 3 addresses (323-704 ms - there are caching and " +"shared memory effects so first geocode you do is always slower) --\n" "-- for large numbers of addresses you don't want to update all at once\n" "-- since the whole geocode must commit at once \n" "-- For this example we rejoin with LEFT JOIN \n" @@ -646,13 +654,15 @@ msgid "" "UPDATE addresses_to_geocode\n" " SET (rating, new_address, lon, lat) \n" " = ( COALESCE((g.geo).rating,-1), pprint_addy((g.geo).addy),\n" -" ST_X((g.geo).geomout)::numeric(8,5), ST_Y((g.geo).geomout)::numeric(8,5) )\n" +" ST_X((g.geo).geomout)::numeric(8,5), ST_Y((g.geo).geomout)::" +"numeric(8,5) )\n" "FROM (SELECT addid \n" " FROM addresses_to_geocode \n" " WHERE rating IS NULL ORDER BY addid LIMIT 3) As a\n" " LEFT JOIN (SELECT addid, (geocode(address,1)) As geo\n" " FROM addresses_to_geocode As ag\n" -" WHERE ag.rating IS NULL ORDER BY addid LIMIT 3) As g ON a.addid = g.addid\n" +" WHERE ag.rating IS NULL ORDER BY addid LIMIT 3) As g ON a.addid = g." +"addid\n" "WHERE a.addid = addresses_to_geocode.addid;\n" "\n" "result\n" @@ -661,11 +671,16 @@ msgid "" "\n" "SELECT * FROM addresses_to_geocode WHERE rating is not null;\n" "\n" -" addid | address | lon | lat | new_address | rating \n" -"-------+----------------------------------------------+-----------+----------+-------------------------------------------+--------\n" -" 1 | 529 Main Street, Boston MA, 02129 | -71.07181 | 42.38359 | 529 Main St, Boston, MA 02129 | 0\n" -" 2 | 77 Massachusetts Avenue, Cambridge, MA 02139 | -71.09428 | 42.35988 | 77 Massachusetts Ave, Cambridge, MA 02139 | 0\n" -" 3 | 25 Wizard of Oz, Walaford, KS 99912323 | | | | -1" +" addid | address | lon | lat " +"| new_address | rating \n" +"-------+----------------------------------------------+-----------+----------" +"+-------------------------------------------+--------\n" +" 1 | 529 Main Street, Boston MA, 02129 | -71.07181 | 42.38359 " +"| 529 Main St, Boston, MA 02129 | 0\n" +" 2 | 77 Massachusetts Avenue, Cambridge, MA 02139 | -71.09428 | 42.35988 " +"| 77 Massachusetts Ave, Cambridge, MA 02139 | 0\n" +" 3 | 25 Wizard of Oz, Walaford, KS 99912323 | | " +"| | -1" msgstr "" #. Tag: title @@ -688,9 +703,12 @@ msgid "" " FROM place WHERE statefp = '25' AND name = 'Lynn')::geometry\n" " ) As g;\n" "\n" -" rating | wktlonlat | stno | street | styp | city | st | zip\n" -"--------+--------------------------+------+---------+------+------+----+-------\n" -" 8 | POINT(-70.96796 42.4659) | 100 | Federal | St | Lynn | MA | 01905\n" +" rating | wktlonlat | stno | street | styp | city | st | " +"zip\n" +"--------+--------------------------+------+---------+------+------+----" +"+-------\n" +" 8 | POINT(-70.96796 42.4659) | 100 | Federal | St | Lynn | MA | " +"01905\n" "Total query runtime: 245 ms." msgstr "" @@ -699,8 +717,8 @@ msgstr "" #, no-c-format msgid "" ", , , , , " +"linkend=\"ST_SnapToGrid\"/>, , " msgstr "" #. Tag: refname @@ -714,9 +732,9 @@ msgstr "" #, no-c-format msgid "" "Takes in 2 streets that intersect and a state, city, zip, and outputs a set " -"of possible locations on the first cross street that is at the intersection," -" also includes a point geometry in NAD 83 long lat, a normalized address for" -" each location, and the rating. The lower the rating the more likely the " +"of possible locations on the first cross street that is at the intersection, " +"also includes a point geometry in NAD 83 long lat, a normalized address for " +"each location, and the rating. The lower the rating the more likely the " "match. Results are sorted by lowest rating first. Can optionally pass in " "maximum results, defaults to 10" msgstr "" @@ -729,14 +747,13 @@ msgid "" "text roadway1 " "text roadway2 " "text in_state " -"text " -"in_city text " -" in_zip integer " -"max_results=10 norm_addy " -" OUT addy geometry " -" OUT geomout " -"integer OUT rating" +"text in_city text in_zip integer " +"max_results=10 norm_addy OUT addy geometry OUT geomout integer " +" OUT rating" msgstr "" #. Tag: para @@ -744,15 +761,15 @@ msgstr "" #, no-c-format msgid "" "Takes in 2 streets that intersect and a state, city, zip, and outputs a set " -"of possible locations on the first cross street that is at the intersection," -" also includes a point geometry in NAD 83 long lat, a normalized address for" -" each location, and the rating. The lower the rating the more likely the " +"of possible locations on the first cross street that is at the intersection, " +"also includes a point geometry in NAD 83 long lat, a normalized address for " +"each location, and the rating. The lower the rating the more likely the " "match. Results are sorted by lowest rating first. Can optionally pass in " -"maximum results, defaults to 10. Returns " -"normalized_address (addy) for each, geomout as the point " -"location in nad 83 long lat, and the rating. The lower the rating the more " -"likely the match. Results are sorted by lowest rating first. Uses Tiger data" -" (edges,faces,addr), PostgreSQL fuzzy string matching (soundex,levenshtein)" +"maximum results, defaults to 10. Returns normalized_address (addy) for each, geomout as the point location in nad 83 long lat, " +"and the rating. The lower the rating the more likely the match. Results are " +"sorted by lowest rating first. Uses Tiger data (edges,faces,addr), " +"PostgreSQL fuzzy string matching (soundex,levenshtein)" msgstr "" #. Tag: para @@ -777,7 +794,8 @@ msgstr "" #, no-c-format msgid "" "SELECT pprint_addy(addy), st_astext(geomout),rating \n" -" FROM geocode_intersection( 'Haverford St','Germania St', 'MA', 'Boston', '02130',1); \n" +" FROM geocode_intersection( 'Haverford St','Germania St', 'MA', " +"'Boston', '02130',1); \n" " pprint_addy | st_astext | rating\n" "----------------------------------+----------------------------+--------\n" "98 Haverford St, Boston, MA 02130 | POINT(-71.101375 42.31376) | 0" @@ -796,7 +814,8 @@ msgstr "" #, no-c-format msgid "" "SELECT pprint_addy(addy), st_astext(geomout),rating \n" -" FROM geocode_intersection('Weld', 'School', 'MA', 'Boston');\n" +" FROM geocode_intersection('Weld', 'School', 'MA', " +"'Boston');\n" " pprint_addy | st_astext | rating\n" "-------------------------------+--------------------------+--------\n" " 98 Weld Ave, Boston, MA 02119 | POINT(-71.099 42.314234) | 3\n" @@ -843,16 +862,31 @@ msgstr "" #: extras_tigergeocoder.xml:319 #, no-c-format msgid "" -"name | setting | unit | category | short_desc\n" -"--------------------------------+---------+---------+-----------+------------------------------------------------------------------------------------------------------------------------------\n" -" debug_geocode_address | false | boolean | debug | outputs debug information in notice log such as queries when geocode_addresss is called if true\n" -" debug_geocode_intersection | false | boolean | debug | outputs debug information in notice log such as queries when geocode_intersection is called if true\n" -" debug_normalize_address | false | boolean | debug | outputs debug information in notice log such as queries and intermediate expressions when normalize_address is called if true\n" -" debug_reverse_geocode | false | boolean | debug | if true, outputs debug information in notice log such as queries and intermediate expressions when reverse_geocode\n" -" reverse_geocode_numbered_roads | 0 | integer | rating | For state and county highways, 0 - no preference in name, \n" -" 1 - prefer the numbered highway name, 2 - prefer local state/county name\n" -" use_pagc_address_parser | false | boolean | normalize | If set to true, will try to use the address_standardizer extension (via pagc_normalize_address) \n" -" instead of tiger normalize_address built one" +"name | setting | unit | category " +"| short_desc\n" +"--------------------------------+---------+---------+-----------" +"+------------------------------------------------------------------------------------------------------------------------------\n" +" debug_geocode_address | false | boolean | debug | outputs " +"debug information in notice log such as queries when geocode_addresss is " +"called if true\n" +" debug_geocode_intersection | false | boolean | debug | outputs " +"debug information in notice log such as queries when geocode_intersection is " +"called if true\n" +" debug_normalize_address | false | boolean | debug | outputs " +"debug information in notice log such as queries and intermediate expressions " +"when normalize_address is called if true\n" +" debug_reverse_geocode | false | boolean | debug | if true, " +"outputs debug information in notice log such as queries and intermediate " +"expressions when reverse_geocode\n" +" reverse_geocode_numbered_roads | 0 | integer | rating | For state " +"and county highways, 0 - no preference in name, \n" +" 1 - prefer " +"the numbered highway name, 2 - prefer local state/county name\n" +" use_pagc_address_parser | false | boolean | normalize | If set to " +"true, will try to use the address_standardizer extension (via " +"pagc_normalize_address) \n" +" instead of " +"tiger normalize_address built one" msgstr "" #. Tag: para @@ -899,17 +933,17 @@ msgstr "" #, no-c-format msgid "" "text get_tract " -"geometry loc_geom" -" text " -"output_field=name" +"geometry loc_geom " +"text output_field=name" msgstr "" #. Tag: para #: extras_tigergeocoder.xml:359 #, no-c-format msgid "" -"Given a geometry will return the census tract location of that geometry. NAD" -" 83 long lat is assumed if no spatial ref sys is specified." +"Given a geometry will return the census tract location of that geometry. NAD " +"83 long lat is assumed if no spatial ref sys is specified." msgstr "" #. Tag: programlisting @@ -965,16 +999,15 @@ msgstr "" #: extras_tigergeocoder.xml:398 #, no-c-format msgid "" -"Finds all tables in tiger and " -"tiger_data schemas with key columns used in geocoder " -"joins and filters that are missing indexes on those columns and will output " -"the SQL DDL to define the index for those tables and then execute the " -"generated script. This is a helper function that adds new indexes needed to " -"make queries faster that may have been missing during the load process. This" -" function is a companion to that in addition to generating" -" the create index script, also executes it. It is called as part of the " -"update_geocode.sql upgrade script." +"Finds all tables in tiger and tiger_data schemas with key columns used in geocoder joins and filters that " +"are missing indexes on those columns and will output the SQL DDL to define " +"the index for those tables and then execute the generated script. This is a " +"helper function that adds new indexes needed to make queries faster that may " +"have been missing during the load process. This function is a companion to " +" that in addition to " +"generating the create index script, also executes it. It is called as part " +"of the update_geocode.sql upgrade script." msgstr "" #. Tag: programlisting @@ -997,28 +1030,27 @@ msgstr "" #: extras_tigergeocoder.xml:427 #, no-c-format msgid "" -"Generates a shell script for the specified platform for the specified states" -" that will download Tiger census state tract, bg, and tabblocks data tables," -" stage and load into tiger_data schema. Each state script" -" is returned as a separate record." +"Generates a shell script for the specified platform for the specified states " +"that will download Tiger census state tract, bg, and tabblocks data tables, " +"stage and load into tiger_data schema. Each state script " +"is returned as a separate record." msgstr "" #. Tag: funcprototype #: extras_tigergeocoder.xml:432 #, no-c-format msgid "" -"setof text " -"loader_generate_census_script " -"text[] param_states" -" text os" +"setof text loader_generate_census_script text[] param_states text os" msgstr "" #. Tag: para #: extras_tigergeocoder.xml:443 #, no-c-format msgid "" -"Generates a shell script for the specified platform for the specified states" -" that will download Tiger data census state tract, block " +"Generates a shell script for the specified platform for the specified states " +"that will download Tiger data census state tract, block " "groups bg, and tabblocks data tables, " "stage and load into tiger_data schema. Each state script " "is returned as a separate record." @@ -1038,8 +1070,8 @@ msgstr "" #: extras_tigergeocoder.xml:446 extras_tigergeocoder.xml:504 #, no-c-format msgid "" -"It uses the following control tables to control the process and different OS" -" shell syntax variations." +"It uses the following control tables to control the process and different OS " +"shell syntax variations." msgstr "" #. Tag: para @@ -1047,8 +1079,8 @@ msgstr "" #: extras_tigergeocoder.xml:564 #, no-c-format msgid "" -"loader_variables keeps track of various variables such as" -" census site, year, data and staging schemas" +"loader_variables keeps track of various variables such as " +"census site, year, data and staging schemas" msgstr "" #. Tag: para @@ -1067,11 +1099,10 @@ msgstr "" msgid "" "loader_lookuptables each record defines a kind of table " "(state, county), whether to process records in it and how to load them in. " -"Defines the steps to import data, stage data, add, removes columns, indexes," -" and constraints for each. Each table is prefixed with the state and " -"inherits from a table in the tiger schema. e.g. creates " -"tiger_data.ma_faces which inherits from " -"tiger.faces" +"Defines the steps to import data, stage data, add, removes columns, indexes, " +"and constraints for each. Each table is prefixed with the state and inherits " +"from a table in the tiger schema. e.g. creates tiger_data.ma_faces which inherits from tiger.faces" msgstr "" #. Tag: para @@ -1079,8 +1110,8 @@ msgstr "" #, no-c-format msgid "" "includes this logic, but if you installed tiger geocoder prior to PostGIS " -"2.0.0 alpha5, you'll need to run this on the states you have already done to" -" get these additional tables." +"2.0.0 alpha5, you'll need to run this on the states you have already done to " +"get these additional tables." msgstr "" #. Tag: para @@ -1097,7 +1128,8 @@ msgstr "" msgid "" "SELECT loader_generate_census_script(ARRAY['MA'], 'windows');\n" "-- result --\n" -"set STATEDIR=\"\\gisdata\\www2.census.gov\\geo\\pvs\\tiger2010st\\25_Massachusetts\"\n" +"set STATEDIR=\"\\gisdata\\www2.census.gov\\geo\\pvs\\tiger2010st" +"\\25_Massachusetts\"\n" "set TMPDIR=\\gisdata\\temp\\\n" "set UNZIPTOOL=\"C:\\Program Files\\7-Zip\\7z.exe\"\n" "set WGETTOOL=\"C:\\wget\\wget.exe\"\n" @@ -1111,19 +1143,27 @@ msgid "" "set SHP2PGSQL=\"%PGBIN%shp2pgsql\"\n" "cd \\gisdata\n" "\n" -"%WGETTOOL% http://www2.census.gov/geo/pvs/tiger2010st/25_Massachusetts/25/ --no-parent --relative --accept=*bg10.zip,*tract10.zip,*tabblock10.zip --mirror --reject=html\n" +"%WGETTOOL% http://www2.census.gov/geo/pvs/tiger2010st/25_Massachusetts/25/ --" +"no-parent --relative --accept=*bg10.zip,*tract10.zip,*tabblock10.zip --" +"mirror --reject=html\n" "del %TMPDIR%\\*.* /Q\n" "%PSQL% -c \"DROP SCHEMA tiger_staging CASCADE;\"\n" "%PSQL% -c \"CREATE SCHEMA tiger_staging;\"\n" "cd %STATEDIR%\n" "for /r %%z in (*.zip) do %UNZIPTOOL% e %%z -o%TMPDIR% \n" "cd %TMPDIR% \n" -"%PSQL% -c \"CREATE TABLE tiger_data.MA_tract(CONSTRAINT pk_MA_tract PRIMARY KEY (tract_id) ) INHERITS(tiger.tract); \" \n" -"%SHP2PGSQL% -c -s 4269 -g the_geom -W \"latin1\" tl_2010_25_tract10.dbf tiger_staging.ma_tract10 | %PSQL%\n" -"%PSQL% -c \"ALTER TABLE tiger_staging.MA_tract10 RENAME geoid10 TO tract_id; SELECT loader_load_staged_data(lower('MA_tract10'), lower('MA_tract')); \"\n" -"%PSQL% -c \"CREATE INDEX tiger_data_MA_tract_the_geom_gist ON tiger_data.MA_tract USING gist(the_geom);\"\n" +"%PSQL% -c \"CREATE TABLE tiger_data.MA_tract(CONSTRAINT pk_MA_tract PRIMARY " +"KEY (tract_id) ) INHERITS(tiger.tract); \" \n" +"%SHP2PGSQL% -c -s 4269 -g the_geom -W \"latin1\" tl_2010_25_tract10.dbf " +"tiger_staging.ma_tract10 | %PSQL%\n" +"%PSQL% -c \"ALTER TABLE tiger_staging.MA_tract10 RENAME geoid10 TO " +"tract_id; SELECT loader_load_staged_data(lower('MA_tract10'), " +"lower('MA_tract')); \"\n" +"%PSQL% -c \"CREATE INDEX tiger_data_MA_tract_the_geom_gist ON tiger_data." +"MA_tract USING gist(the_geom);\"\n" "%PSQL% -c \"VACUUM ANALYZE tiger_data.MA_tract;\"\n" -"%PSQL% -c \"ALTER TABLE tiger_data.MA_tract ADD CONSTRAINT chk_statefp CHECK (statefp = '25');\"\n" +"%PSQL% -c \"ALTER TABLE tiger_data.MA_tract ADD CONSTRAINT chk_statefp CHECK " +"(statefp = '25');\"\n" ":" msgstr "" @@ -1151,7 +1191,9 @@ msgid "" "SHP2PGSQL=${PGBIN}/shp2pgsql\n" "cd /gisdata\n" "\n" -"wget http://www2.census.gov/geo/pvs/tiger2010st/25_Massachusetts/25/ --no-parent --relative --accept=*bg10.zip,*tract10.zip,*tabblock10.zip --mirror --reject=html\n" +"wget http://www2.census.gov/geo/pvs/tiger2010st/25_Massachusetts/25/ --no-" +"parent --relative --accept=*bg10.zip,*tract10.zip,*tabblock10.zip --mirror --" +"reject=html\n" "rm -f ${TMPDIR}/*.*\n" "${PSQL} -c \"DROP SCHEMA tiger_staging CASCADE;\"\n" "${PSQL} -c \"CREATE SCHEMA tiger_staging;\"\n" @@ -1171,11 +1213,11 @@ msgstr "" #: extras_tigergeocoder.xml:485 #, no-c-format msgid "" -"Generates a shell script for the specified platform for the specified states" -" that will download Tiger data, stage and load into " -"tiger_data schema. Each state script is returned as a " -"separate record. Latest version supports Tiger 2010 structural changes and " -"also loads census tract, block groups, and blocks tables." +"Generates a shell script for the specified platform for the specified states " +"that will download Tiger data, stage and load into tiger_data schema. Each state script is returned as a separate record. Latest " +"version supports Tiger 2010 structural changes and also loads census tract, " +"block groups, and blocks tables." msgstr "" #. Tag: funcprototype @@ -1183,18 +1225,17 @@ msgstr "" #, no-c-format msgid "" "setof text loader_generate_script " -"text[] param_states" -" text os" +"text[] param_states " +"text os" msgstr "" #. Tag: para #: extras_tigergeocoder.xml:501 #, no-c-format msgid "" -"Generates a shell script for the specified platform for the specified states" -" that will download Tiger data, stage and load into " -"tiger_data schema. Each state script is returned as a " -"separate record." +"Generates a shell script for the specified platform for the specified states " +"that will download Tiger data, stage and load into tiger_data schema. Each state script is returned as a separate record." msgstr "" #. Tag: para @@ -1203,8 +1244,8 @@ msgstr "" msgid "" "It uses unzip on Linux (7-zip on Windows by default) and wget to do the " "downloading. It uses to load in the " -"data. Note the smallest unit it does is a whole state, but you can overwrite" -" this by downloading the files yourself. It will only process the files in " +"data. Note the smallest unit it does is a whole state, but you can overwrite " +"this by downloading the files yourself. It will only process the files in " "the staging and temp folders." msgstr "" @@ -1229,7 +1270,8 @@ msgstr "" msgid "" "SELECT loader_generate_script(ARRAY['MA','RI'], 'windows') AS result;\n" "-- result --\n" -"set STATEDIR=\"\\gisdata\\www2.census.gov\\geo\\pvs\\tiger2010st\\44_Rhode_Island\"\n" +"set STATEDIR=\"\\gisdata\\www2.census.gov\\geo\\pvs\\tiger2010st" +"\\44_Rhode_Island\"\n" "set TMPDIR=\\gisdata\\temp\\\n" "set UNZIPTOOL=\"C:\\Program Files\\7-Zip\\7z.exe\"\n" "set WGETTOOL=\"C:\\wget\\wget.exe\"\n" @@ -1242,7 +1284,9 @@ msgid "" "set PSQL=\"%PGBIN%psql\"\n" "set SHP2PGSQL=\"%PGBIN%shp2pgsql\"\n" "\n" -"%WGETTOOL% http://www2.census.gov/geo/pvs/tiger2010st/44_Rhode_Island/ --no-parent --relative --recursive --level=2 --accept=zip,txt --mirror --reject=html\n" +"%WGETTOOL% http://www2.census.gov/geo/pvs/tiger2010st/44_Rhode_Island/ --no-" +"parent --relative --recursive --level=2 --accept=zip,txt --mirror --" +"reject=html\n" ":\n" ":" msgstr "" @@ -1264,7 +1308,8 @@ msgid "" "PSQL=psql\n" "SHP2PGSQ=shp2pgsql\n" "\n" -"wget http://www2.census.gov/geo/pvs/tiger2010st/44_Rhode_Island/ --no-parent --relative --recursive --level=2 --accept=zip,txt --mirror --reject=html\n" +"wget http://www2.census.gov/geo/pvs/tiger2010st/44_Rhode_Island/ --no-parent " +"--relative --recursive --level=2 --accept=zip,txt --mirror --reject=html\n" ":\n" ":" msgstr "" @@ -1279,8 +1324,8 @@ msgstr "" #: extras_tigergeocoder.xml:543 #, no-c-format msgid "" -"Generates a shell script for the specified platform that loads in the county" -" and state lookup tables." +"Generates a shell script for the specified platform that loads in the county " +"and state lookup tables." msgstr "" #. Tag: funcprototype @@ -1308,19 +1353,17 @@ msgstr "" #, no-c-format msgid "" "It uses unzip on Linux (7-zip on Windows by default) and wget to do the " -"downloading. It uses to load in the " -"data." +"downloading. It uses to load in the data." msgstr "" #. Tag: para #: extras_tigergeocoder.xml:560 #, no-c-format msgid "" -"It uses the following control tables " -"tiger.loader_platform, " -"tiger.loader_variables, and " -"tiger.loader_lookuptables to control the process and " -"different OS shell syntax variations." +"It uses the following control tables tiger.loader_platform, tiger.loader_variables, and tiger." +"loader_lookuptables to control the process and different OS shell " +"syntax variations." msgstr "" #. Tag: para @@ -1328,8 +1371,8 @@ msgstr "" #, no-c-format msgid "" "loader_platform profiles of various platforms and where " -"the various executables are located. Comes with windows and linux/unix. More" -" can be added." +"the various executables are located. Comes with windows and linux/unix. More " +"can be added." msgstr "" #. Tag: para @@ -1338,8 +1381,8 @@ msgstr "" msgid "" "If you were running tiger_2010 version and you want to " "reload as state with tiger_2011, you'll need to for the " -"very first load generate and run drop statements before you run this script." +"very first load generate and run drop statements before you run this script." msgstr "" #. Tag: para @@ -1377,31 +1420,30 @@ msgstr "" #, no-c-format msgid "" "Finds all tables with key columns used in geocoder joins that are missing " -"indexes on those columns and will output the SQL DDL to define the index for" -" those tables." +"indexes on those columns and will output the SQL DDL to define the index for " +"those tables." msgstr "" #. Tag: funcprototype #: extras_tigergeocoder.xml:603 #, no-c-format msgid "" -"text Missing_Indexes_Generate_Script" -" " +"text Missing_Indexes_Generate_Script " +"" msgstr "" #. Tag: para #: extras_tigergeocoder.xml:613 #, no-c-format msgid "" -"Finds all tables in tiger and " -"tiger_data schemas with key columns used in geocoder " -"joins that are missing indexes on those columns and will output the SQL DDL " -"to define the index for those tables. This is a helper function that adds " -"new indexes needed to make queries faster that may have been missing during " -"the load process. As the geocoder is improved, this function will be updated" -" to accommodate new indexes being used. If this function outputs nothing, it" -" means all your tables have what we think are the key indexes already in " -"place." +"Finds all tables in tiger and tiger_data schemas with key columns used in geocoder joins that are missing " +"indexes on those columns and will output the SQL DDL to define the index for " +"those tables. This is a helper function that adds new indexes needed to make " +"queries faster that may have been missing during the load process. As the " +"geocoder is improved, this function will be updated to accommodate new " +"indexes being used. If this function outputs nothing, it means all your " +"tables have what we think are the key indexes already in place." msgstr "" #. Tag: programlisting @@ -1409,16 +1451,24 @@ msgstr "" #, no-c-format msgid "" "SELECT missing_indexes_generate_script();\n" -"-- output: This was run on a database that was created before many corrections were made to the loading script ---\n" -"CREATE INDEX idx_tiger_county_countyfp ON tiger.county USING btree(countyfp);\n" -"CREATE INDEX idx_tiger_cousub_countyfp ON tiger.cousub USING btree(countyfp);\n" +"-- output: This was run on a database that was created before many " +"corrections were made to the loading script ---\n" +"CREATE INDEX idx_tiger_county_countyfp ON tiger.county USING " +"btree(countyfp);\n" +"CREATE INDEX idx_tiger_cousub_countyfp ON tiger.cousub USING " +"btree(countyfp);\n" "CREATE INDEX idx_tiger_edges_tfidr ON tiger.edges USING btree(tfidr);\n" "CREATE INDEX idx_tiger_edges_tfidl ON tiger.edges USING btree(tfidl);\n" -"CREATE INDEX idx_tiger_zip_lookup_all_zip ON tiger.zip_lookup_all USING btree(zip);\n" -"CREATE INDEX idx_tiger_data_ma_county_countyfp ON tiger_data.ma_county USING btree(countyfp);\n" -"CREATE INDEX idx_tiger_data_ma_cousub_countyfp ON tiger_data.ma_cousub USING btree(countyfp);\n" -"CREATE INDEX idx_tiger_data_ma_edges_countyfp ON tiger_data.ma_edges USING btree(countyfp);\n" -"CREATE INDEX idx_tiger_data_ma_faces_countyfp ON tiger_data.ma_faces USING btree(countyfp);" +"CREATE INDEX idx_tiger_zip_lookup_all_zip ON tiger.zip_lookup_all USING " +"btree(zip);\n" +"CREATE INDEX idx_tiger_data_ma_county_countyfp ON tiger_data.ma_county USING " +"btree(countyfp);\n" +"CREATE INDEX idx_tiger_data_ma_cousub_countyfp ON tiger_data.ma_cousub USING " +"btree(countyfp);\n" +"CREATE INDEX idx_tiger_data_ma_edges_countyfp ON tiger_data.ma_edges USING " +"btree(countyfp);\n" +"CREATE INDEX idx_tiger_data_ma_faces_countyfp ON tiger_data.ma_faces USING " +"btree(countyfp);" msgstr "" #. Tag: para @@ -1437,11 +1487,11 @@ msgstr "" #: extras_tigergeocoder.xml:642 #, no-c-format msgid "" -"Given a textual street address, returns a composite " -"norm_addy type that has road suffix, prefix and type " -"standardized, street, streetname etc. broken into separate fields. This " -"function will work with just the lookup data packaged with the " -"tiger_geocoder (no need for tiger census data)." +"Given a textual street address, returns a composite norm_addy type that has road suffix, prefix and type standardized, street, " +"streetname etc. broken into separate fields. This function will work with " +"just the lookup data packaged with the tiger_geocoder (no need for tiger " +"census data)." msgstr "" #. Tag: funcprototype @@ -1456,12 +1506,11 @@ msgstr "" #: extras_tigergeocoder.xml:658 extras_tigergeocoder.xml:737 #, no-c-format msgid "" -"Given a textual street address, returns a composite " -"norm_addy type that has road suffix, prefix and type " -"standardized, street, streetname etc. broken into separate fields. This is " -"the first step in the geocoding process to get all addresses into normalized" -" postal form. No other data is required aside from what is packaged with the" -" geocoder." +"Given a textual street address, returns a composite norm_addy type that has road suffix, prefix and type standardized, street, " +"streetname etc. broken into separate fields. This is the first step in the " +"geocoding process to get all addresses into normalized postal form. No other " +"data is required aside from what is packaged with the geocoder." msgstr "" #. Tag: para @@ -1469,11 +1518,11 @@ msgstr "" #, no-c-format msgid "" "This function just uses the various direction/state/suffix lookup tables " -"preloaded with the tiger_geocoder and located in the " -"tiger schema, so it doesn't need you to download tiger " -"census data or any other additional data to make use of it. You may find the" -" need to add more abbreviations or alternative namings to the various lookup" -" tables in the tiger schema." +"preloaded with the tiger_geocoder and located in the tiger schema, so it doesn't need you to download tiger census data or any " +"other additional data to make use of it. You may find the need to add more " +"abbreviations or alternative namings to the various lookup tables in the " +"tiger schema." msgstr "" #. Tag: para @@ -1512,8 +1561,8 @@ msgstr "" #, no-c-format msgid "" "predirAbbrev is varchar: Directional prefix of road such " -"as N, S, E, W etc. These are controlled using the " -"direction_lookup table." +"as N, S, E, W etc. These are controlled using the direction_lookup table." msgstr "" #. Tag: para @@ -1544,8 +1593,8 @@ msgstr "" #: extras_tigergeocoder.xml:682 extras_tigergeocoder.xml:767 #, no-c-format msgid "" -"internal varchar internal address such as an apartment or" -" suite number." +"internal varchar internal address such as an apartment or " +"suite number." msgstr "" #. Tag: para @@ -1594,8 +1643,10 @@ msgid "" " FROM (SELECT address, normalize_address(address) As na\n" " FROM addresses_to_geocode) As g;\n" " \n" -" orig | streetname | streettypeabbrev \n" -"-----------------------------------------------------+---------------+------------------\n" +" orig | streetname | " +"streettypeabbrev \n" +"-----------------------------------------------------+---------------" +"+------------------\n" " 28 Capen Street, Medford, MA | Capen | St\n" " 124 Mount Auburn St, Cambridge, Massachusetts 02138 | Mount Auburn | St\n" " 950 Main Street, Worcester, MA 01610 | Main | St\n" @@ -1620,12 +1671,11 @@ msgstr "" #: extras_tigergeocoder.xml:721 #, no-c-format msgid "" -"Given a textual street address, returns a composite " -"norm_addy type that has road suffix, prefix and type " -"standardized, street, streetname etc. broken into separate fields. This " -"function will work with just the lookup data packaged with the " -"tiger_geocoder (no need for tiger census data). Requires " -"address_standardizer extension." +"Given a textual street address, returns a composite norm_addy type that has road suffix, prefix and type standardized, street, " +"streetname etc. broken into separate fields. This function will work with " +"just the lookup data packaged with the tiger_geocoder (no need for tiger " +"census data). Requires address_standardizer extension." msgstr "" #. Tag: funcprototype @@ -1644,16 +1694,16 @@ msgid "" "tiger_geocoder and located in the tiger schema, so it " "doesn't need you to download tiger census data or any other additional data " "to make use of it. You may find the need to add more abbreviations or " -"alternative namings to the various lookup tables in the " -"tiger schema." +"alternative namings to the various lookup tables in the tiger schema." msgstr "" #. Tag: para #: extras_tigergeocoder.xml:743 #, no-c-format msgid "" -"There are slight variations in casing and formatting over the ." +"There are slight variations in casing and formatting over the ." msgstr "" #. Tag: para @@ -1688,12 +1738,16 @@ msgstr "" #, no-c-format msgid "" "SELECT addy.*\n" -"FROM pagc_normalize_address('9000 E ROO ST STE 999, Springfield, CO') AS addy;\n" +"FROM pagc_normalize_address('9000 E ROO ST STE 999, Springfield, CO') AS " +"addy;\n" "\n" " \n" -" address | predirabbrev | streetname | streettypeabbrev | postdirabbrev | internal | location | stateabbrev | zip | parsed\n" -"---------+--------------+------------+------------------+---------------+-----------+-------------+-------------+-----+--------\n" -" 9000 | E | ROO | ST | | SUITE 999 | SPRINGFIELD | CO | | t" +" address | predirabbrev | streetname | streettypeabbrev | postdirabbrev | " +"internal | location | stateabbrev | zip | parsed\n" +"---------+--------------+------------+------------------+---------------" +"+-----------+-------------+-------------+-----+--------\n" +" 9000 | E | ROO | ST | | " +"SUITE 999 | SPRINGFIELD | CO | | t" msgstr "" #. Tag: para @@ -1706,8 +1760,8 @@ msgid "" "batch geocoding to call generate a normaddy in batch mode, you are " "encouraged to directly call the address_standardizer standardize_address " "function as shown below which is similar exercise to what we did in that uses data created in ." +"linkend=\"Normalize_Address\"/> that uses data created in ." msgstr "" #. Tag: programlisting @@ -1715,7 +1769,8 @@ msgstr "" #, no-c-format msgid "" "WITH g AS (SELECT address, ROW((sa).house_num, (sa).predir, (sa).name\n" -" , (sa).suftype, (sa).sufdir, (sa).unit , (sa).city, (sa).state, (sa).postcode, true)::norm_addy As na\n" +" , (sa).suftype, (sa).sufdir, (sa).unit , (sa).city, (sa).state, (sa)." +"postcode, true)::norm_addy As na\n" " FROM (SELECT address, standardize_address('tiger.pagc_lex'\n" " , 'tiger.pagc_gaz'\n" " , 'tiger.pagc_rules', address) As sa\n" @@ -1723,8 +1778,10 @@ msgid "" "SELECT address As orig, (g.na).streetname, (g.na).streettypeabbrev\n" " FROM g;\n" " \n" -" orig | streetname | streettypeabbrev\n" -"-----------------------------------------------------+---------------+------------------\n" +" orig | streetname | " +"streettypeabbrev\n" +"-----------------------------------------------------+---------------" +"+------------------\n" " 529 Main Street, Boston MA, 02129 | MAIN | ST\n" " 77 Massachusetts Avenue, Cambridge, MA 02139 | MASSACHUSETTS | AVE\n" " 25 Wizard of Oz, Walaford, KS 99912323 | WIZARD OF |\n" @@ -1749,8 +1806,8 @@ msgstr "" #: extras_tigergeocoder.xml:807 #, no-c-format msgid "" -"Given a norm_addy composite type object, returns a pretty" -" print representation of it. Usually used in conjunction with " +"Given a norm_addy composite type object, returns a pretty " +"print representation of it. Usually used in conjunction with " "normalize_address." msgstr "" @@ -1766,8 +1823,8 @@ msgstr "" #: extras_tigergeocoder.xml:822 #, no-c-format msgid "" -"Given a norm_addy composite type object, returns a pretty" -" print representation of it. No other data is required aside from what is " +"Given a norm_addy composite type object, returns a pretty " +"print representation of it. No other data is required aside from what is " "packaged with the geocoder." msgstr "" @@ -1787,7 +1844,8 @@ msgstr "" #: extras_tigergeocoder.xml:832 #, no-c-format msgid "" -"SELECT pprint_addy(normalize_address('202 East Fremont Street, Las Vegas, Nevada 89101')) As pretty_address;\n" +"SELECT pprint_addy(normalize_address('202 East Fremont Street, Las Vegas, " +"Nevada 89101')) As pretty_address;\n" " pretty_address\n" "---------------------------------------\n" " 202 E Fremont St, Las Vegas, NV 89101" @@ -1803,16 +1861,24 @@ msgstr "" #: extras_tigergeocoder.xml:835 #, no-c-format msgid "" -"SELECT address As orig, pprint_addy(normalize_address(address)) As pretty_address\n" +"SELECT address As orig, pprint_addy(normalize_address(address)) As " +"pretty_address\n" " FROM addresses_to_geocode;\n" " \n" -" orig | pretty_address\n" -"-----------------------------------------------------+-------------------------------------------\n" -" 529 Main Street, Boston MA, 02129 | 529 Main St, Boston MA, 02129\n" -" 77 Massachusetts Avenue, Cambridge, MA 02139 | 77 Massachusetts Ave, Cambridge, MA 02139\n" -" 28 Capen Street, Medford, MA | 28 Capen St, Medford, MA\n" -" 124 Mount Auburn St, Cambridge, Massachusetts 02138 | 124 Mount Auburn St, Cambridge, MA 02138\n" -" 950 Main Street, Worcester, MA 01610 | 950 Main St, Worcester, MA 01610" +" orig | " +"pretty_address\n" +"-----------------------------------------------------" +"+-------------------------------------------\n" +" 529 Main Street, Boston MA, 02129 | 529 Main St, Boston " +"MA, 02129\n" +" 77 Massachusetts Avenue, Cambridge, MA 02139 | 77 Massachusetts Ave, " +"Cambridge, MA 02139\n" +" 28 Capen Street, Medford, MA | 28 Capen St, Medford, " +"MA\n" +" 124 Mount Auburn St, Cambridge, Massachusetts 02138 | 124 Mount Auburn St, " +"Cambridge, MA 02138\n" +" 950 Main Street, Worcester, MA 01610 | 950 Main St, " +"Worcester, MA 01610" msgstr "" #. Tag: refname @@ -1839,10 +1905,10 @@ msgid "" "geometry pt " "boolean " "include_strnum_range=false " -"geometry[] OUT " -"intpt norm_addy[] " -"OUT addy varchar[] " -" OUT street" +"geometry[] OUT intpt norm_addy[] OUT addy varchar[] OUT " +"street" msgstr "" #. Tag: para @@ -1862,15 +1928,15 @@ msgstr "" #, no-c-format msgid "" "Why do we say theoretical instead of actual addresses. The Tiger data " -"doesn't have real addresses, but just street ranges. As such the theoretical" -" address is an interpolated address based on the street ranges. Like for " +"doesn't have real addresses, but just street ranges. As such the theoretical " +"address is an interpolated address based on the street ranges. Like for " "example interpolating one of my addresses returns a 26 Court St. and 26 " "Court Sq., though there is no such place as 26 Court Sq. This is because a " "point may be at a corner of 2 streets and thus the logic interpolates along " "both streets. The logic also assumes addresses are equally spaced along a " "street, which of course is wrong since you can have a municipal building " -"taking up a good chunk of the street range and the rest of the buildings are" -" clustered at the end." +"taking up a good chunk of the street range and the rest of the buildings are " +"clustered at the end." msgstr "" #. Tag: para @@ -1893,8 +1959,8 @@ msgstr "" #, no-c-format msgid "" "intpt is an array of points: These are the center line " -"points on the street closest to the input point. There are as many points as" -" there are addresses." +"points on the street closest to the input point. There are as many points as " +"there are addresses." msgstr "" #. Tag: para @@ -1902,10 +1968,10 @@ msgstr "" #, no-c-format msgid "" "addy is an array of norm_addy (normalized addresses): " -"These are an array of possible addresses that fit the input point. The first" -" one in the array is most likely. Generally there should be only one, except" -" in the case when a point is at the corner of 2 or 3 streets, or the point " -"is somewhere on the road and not off to the side." +"These are an array of possible addresses that fit the input point. The first " +"one in the array is most likely. Generally there should be only one, except " +"in the case when a point is at the corner of 2 or 3 streets, or the point is " +"somewhere on the road and not off to the side." msgstr "" #. Tag: para @@ -1913,33 +1979,38 @@ msgstr "" #, no-c-format msgid "" "street an array of varchar: These are cross streets (or " -"the street) (streets that intersect or are the street the point is projected" -" to be on)." +"the street) (streets that intersect or are the street the point is projected " +"to be on)." msgstr "" #. Tag: para #: extras_tigergeocoder.xml:899 #, no-c-format msgid "" -"Example of a point at the corner of two streets, but closest to one. This is" -" approximate location of MIT: 77 Massachusetts Ave, Cambridge, MA 02139 Note" -" that although we don't have 3 streets, PostgreSQL will just return null for" -" entries above our upper bound so safe to use. This includes street ranges" +"Example of a point at the corner of two streets, but closest to one. This is " +"approximate location of MIT: 77 Massachusetts Ave, Cambridge, MA 02139 Note " +"that although we don't have 3 streets, PostgreSQL will just return null for " +"entries above our upper bound so safe to use. This includes street ranges" msgstr "" #. Tag: programlisting #: extras_tigergeocoder.xml:901 #, no-c-format msgid "" -"SELECT pprint_addy(r.addy[1]) As st1, pprint_addy(r.addy[2]) As st2, pprint_addy(r.addy[3]) As st3, \n" +"SELECT pprint_addy(r.addy[1]) As st1, pprint_addy(r.addy[2]) As st2, " +"pprint_addy(r.addy[3]) As st3, \n" " array_to_string(r.street, ',') As cross_streets \n" -" FROM reverse_geocode(ST_GeomFromText('POINT(-71.093902 42.359446)',4269),true) As r;\n" +" FROM reverse_geocode(ST_GeomFromText('POINT(-71.093902 " +"42.359446)',4269),true) As r;\n" " \n" " result\n" " ------\n" -" st1 | st2 | st3 | cross_streets\n" -"-------------------------------------------+-----+-----+----------------------------------------------\n" -" 67 Massachusetts Ave, Cambridge, MA 02139 | | | 67 - 127 Massachusetts Ave,32 - 88 Vassar St" +" st1 | st2 | st3 | " +"cross_streets\n" +"-------------------------------------------+-----+-----" +"+----------------------------------------------\n" +" 67 Massachusetts Ave, Cambridge, MA 02139 | | | 67 - 127 " +"Massachusetts Ave,32 - 88 Vassar St" msgstr "" #. Tag: para @@ -1947,8 +2018,8 @@ msgstr "" #, no-c-format msgid "" "Here we choose not to include the address ranges for the cross streets and " -"picked a location really really close to a corner of 2 streets thus could be" -" known by two different addresses." +"picked a location really really close to a corner of 2 streets thus could be " +"known by two different addresses." msgstr "" #. Tag: programlisting @@ -1957,13 +2028,17 @@ msgstr "" msgid "" "SELECT pprint_addy(r.addy[1]) As st1, pprint_addy(r.addy[2]) As st2, \n" "pprint_addy(r.addy[3]) As st3, array_to_string(r.street, ',') As cross_str\n" -"FROM reverse_geocode(ST_GeomFromText('POINT(-71.06941 42.34225)',4269)) As r;\n" +"FROM reverse_geocode(ST_GeomFromText('POINT(-71.06941 42.34225)',4269)) As " +"r;\n" "\n" "result\n" "--------\n" -" st1 | st2 | st3 | cross_str\n" -"---------------------------------+---------------------------------+-----+------------------------\n" -" 5 Bradford St, Boston, MA 02118 | 49 Waltham St, Boston, MA 02118 | | Waltham St" +" st1 | st2 | st3 | " +"cross_str\n" +"---------------------------------+---------------------------------+-----" +"+------------------------\n" +" 5 Bradford St, Boston, MA 02118 | 49 Waltham St, Boston, MA 02118 | | " +"Waltham St" msgstr "" #. Tag: para @@ -1984,13 +2059,20 @@ msgid "" " reverse_geocode( ST_SetSRID(ST_Point(lon,lat),4326) ) As rg\n" " FROM addresses_to_geocode WHERE rating > -1) As foo;\n" "\n" -" actual_addr | lon | lat | int_addr1 | cross1 | cross2 \n" -"-----------------------------------------------------+-----------+----------+-------------------------------------------+-----------------+------------\n" -" 529 Main Street, Boston MA, 02129 | -71.07181 | 42.38359 | 527 Main St, Boston, MA 02129 | Medford St | \n" -" 77 Massachusetts Avenue, Cambridge, MA 02139 | -71.09428 | 42.35988 | 77 Massachusetts Ave, Cambridge, MA 02139 | Vassar St | \n" -" 26 Capen Street, Medford, MA | -71.12377 | 42.41101 | 9 Edison Ave, Medford, MA 02155 | Capen St | Tesla Ave\n" -" 124 Mount Auburn St, Cambridge, Massachusetts 02138 | -71.12304 | 42.37328 | 3 University Rd, Cambridge, MA 02138 | Mount Auburn St | \n" -" 950 Main Street, Worcester, MA 01610 | -71.82368 | 42.24956 | 3 Maywood St, Worcester, MA 01603 | Main St | Maywood Pl" +" actual_addr | lon | lat " +"| int_addr1 | cross1 | cross2 \n" +"-----------------------------------------------------+-----------+----------" +"+-------------------------------------------+-----------------+------------\n" +" 529 Main Street, Boston MA, 02129 | -71.07181 | 42.38359 " +"| 527 Main St, Boston, MA 02129 | Medford St | \n" +" 77 Massachusetts Avenue, Cambridge, MA 02139 | -71.09428 | 42.35988 " +"| 77 Massachusetts Ave, Cambridge, MA 02139 | Vassar St | \n" +" 26 Capen Street, Medford, MA | -71.12377 | 42.41101 " +"| 9 Edison Ave, Medford, MA 02155 | Capen St | Tesla Ave\n" +" 124 Mount Auburn St, Cambridge, Massachusetts 02138 | -71.12304 | 42.37328 " +"| 3 University Rd, Cambridge, MA 02138 | Mount Auburn St | \n" +" 950 Main Street, Worcester, MA 01610 | -71.82368 | 42.24956 " +"| 3 Maywood St, Worcester, MA 01603 | Main St | Maywood Pl" msgstr "" #. Tag: refname @@ -2014,9 +2096,9 @@ msgstr "" msgid "" "text Topology_Load_Tiger " "varchar topo_name " -"varchar " -"region_type varchar " -" region_id" +"varchar region_type varchar region_id" msgstr "" #. Tag: para @@ -2046,19 +2128,19 @@ msgstr "" #, no-c-format msgid "" "This function relies on Tiger data as well as the installation of the " -"PostGIS topology module. For more information, refer to and . " -"If you have not loaded data covering the region of interest, then no " -"topology records will be created. This function will also fail if you have " -"not created a topology using the topology functions." +"PostGIS topology module. For more information, refer to and . If you " +"have not loaded data covering the region of interest, then no topology " +"records will be created. This function will also fail if you have not " +"created a topology using the topology functions." msgstr "" #. Tag: para #: extras_tigergeocoder.xml:948 #, no-c-format msgid "" -"Most topology validation errors are a result of tolerance issues where after" -" transformation the edges points don't quite line up or overlap. To remedy " +"Most topology validation errors are a result of tolerance issues where after " +"transformation the edges points don't quite line up or overlap. To remedy " "the situation you may want to increase or lower the precision if you get " "topology validation failures." msgstr "" @@ -2083,8 +2165,8 @@ msgstr "" msgid "" "region_type The type of bounding region. Currently only " "place and county are supported. Plan " -"is to have several more. This is the table to look into to define the region" -" bounds. e.g tiger.place, tiger.county" +"is to have several more. This is the table to look into to define the region " +"bounds. e.g tiger.place, tiger.county" msgstr "" #. Tag: para @@ -2094,8 +2176,8 @@ msgid "" "region_id This is what TIGER calls the geoid. It is the " "unique identifier of the region in the table. For place it is the " "plcidfp column in tiger.place. For " -"county it is the cntyidfp column in " -"tiger.county" +"county it is the cntyidfp column in tiger." +"county" msgstr "" #. Tag: title @@ -2121,11 +2203,14 @@ msgid "" "createtopology\n" "--------------\n" " 15\n" -"-- 60,902 ms ~ 1 minute on windows 7 desktop running 9.1 (with 5 states tiger data loaded) \n" +"-- 60,902 ms ~ 1 minute on windows 7 desktop running 9.1 (with 5 states " +"tiger data loaded) \n" "SELECT tiger.topology_load_tiger('topo_boston', 'place', '2507000'); \n" "-- topology_loader_tiger --\n" -"29722 edges holding in temporary. 11108 faces added. 1875 edges of faces added. 20576 nodes added. \n" -"19962 nodes contained in a face. 0 edge start end corrected. 31597 edges added. \n" +"29722 edges holding in temporary. 11108 faces added. 1875 edges of faces " +"added. 20576 nodes added. \n" +"19962 nodes contained in a face. 0 edge start end corrected. 31597 edges " +"added. \n" " \n" "-- 41 ms --\n" "SELECT topology.TopologySummary('topo_boston');\n" @@ -2161,12 +2246,15 @@ msgstr "" #, no-c-format msgid "" "SELECT topology.CreateTopology('topo_suffolk', 26986, 0.25);\n" -"-- this took 56,275 ms ~ 1 minute on Windows 7 32-bit with 5 states of tiger loaded\n" +"-- this took 56,275 ms ~ 1 minute on Windows 7 32-bit with 5 states of tiger " +"loaded\n" "-- must have been warmed up after loading boston\n" "SELECT tiger.topology_load_tiger('topo_suffolk', 'county', '25025'); \n" "-- topology_loader_tiger --\n" -" 36003 edges holding in temporary. 13518 faces added. 2172 edges of faces added. \n" -" 24761 nodes added. 24075 nodes contained in a face. 0 edge start end corrected. 38175 edges added. \n" +" 36003 edges holding in temporary. 13518 faces added. 2172 edges of faces " +"added. \n" +" 24761 nodes added. 24075 nodes contained in a face. 0 edge start end " +"corrected. 38175 edges added. \n" "-- 31 ms --\n" "SELECT topology.TopologySummary('topo_suffolk');\n" " -- topologysummary--\n" @@ -2213,20 +2301,18 @@ msgstr "" #, no-c-format msgid "" "text Set_Geocode_Setting " -"text setting_name" -" text " -"setting_value" +"text setting_name " +"text setting_value" msgstr "" #. Tag: para #: extras_tigergeocoder.xml:1006 #, no-c-format msgid "" -"Sets value of specific setting stored in " -"tiger.geocode_settings table. Settings allow you to " -"toggle debugging of functions. Later plans will be to control rating with " -"settings. Current list of settings are listed in ." +"Sets value of specific setting stored in tiger.geocode_settings table. Settings allow you to toggle debugging of functions. Later " +"plans will be to control rating with settings. Current list of settings are " +"listed in ." msgstr "" #. Tag: para diff --git a/doc/po/de_DE/extras_topology.xml.po b/doc/po/de_DE/extras_topology.xml.po index 32eb54c8e..5f0f3e69e 100644 --- a/doc/po/de_DE/extras_topology.xml.po +++ b/doc/po/de_DE/extras_topology.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:23+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -34,9 +35,9 @@ msgstr "" #, no-c-format msgid "" "Sandro Santilli's presentation at PostGIS Day Paris 2011 conference gives a " -"good synopsis of PostGIS Topology and where it is headed Topology" -" with PostGIS 2.0 slide deck." +"good synopsis of PostGIS Topology and where it is headed Topology with PostGIS 2.0 slide deck." msgstr "" #. Tag: para @@ -44,28 +45,29 @@ msgstr "" #, no-c-format msgid "" "Vincent Picavet provides a good synopsis and overview of what is Topology, " -"how is it used, and various FOSS4G tools that support it in PostGIS" -" Topology PGConf EU 2012." +"how is it used, and various FOSS4G tools that support it in PostGIS " +"Topology PGConf EU 2012." msgstr "" #. Tag: para #: extras_topology.xml:7 #, no-c-format msgid "" -"An example of a topologically based GIS database is the US Census " -"Topologically Integrated Geographic Encoding and Reference System " -"(TIGER) database. If you want to experiment with PostGIS topology " -"and need some data, check out ." +"An example of a topologically based GIS database is the US Census Topologically " +"Integrated Geographic Encoding and Reference System (TIGER) " +"database. If you want to experiment with PostGIS topology and need some " +"data, check out ." msgstr "" #. Tag: para #: extras_topology.xml:8 #, no-c-format msgid "" -"The PostGIS topology module has existed in prior versions of PostGIS but was" -" never part of the Official PostGIS documentation. In PostGIS 2.0.0 major " +"The PostGIS topology module has existed in prior versions of PostGIS but was " +"never part of the Official PostGIS documentation. In PostGIS 2.0.0 major " "cleanup is going on to remove use of all deprecated functions in it, fix " "known usability issues, better document the features and functions, add new " "functions, and enhance to closer conform to SQL-MM standards." @@ -75,9 +77,8 @@ msgstr "" #: extras_topology.xml:10 #, no-c-format msgid "" -"Details of this project can be found at PostGIS " -"Topology Wiki" +"Details of this project can be found at PostGIS Topology Wiki" msgstr "" #. Tag: para @@ -100,8 +101,8 @@ msgstr "" #: extras_topology.xml:13 #, no-c-format msgid "" -"To build PostGIS 2.0 with topology support, compile with the --with-topology" -" option as described in . Some " +"To build PostGIS 2.0 with topology support, compile with the --with-topology " +"option as described in . Some " "functions depend on GEOS 3.3+ so you should compile with GEOS 3.3+ to fully " "utilize the topology support." msgstr "" @@ -131,8 +132,8 @@ msgstr "" #: extras_topology.xml:28 #, no-c-format msgid "" -"A composite type that consists of a sequence number and edge number. This is" -" the return type for ST_GetFaceEdges" +"A composite type that consists of a sequence number and edge number. This is " +"the return type for ST_GetFaceEdges" msgstr "" #. Tag: title @@ -162,8 +163,8 @@ msgstr "Beschreibung" #: extras_topology.xml:32 #, no-c-format msgid "" -"A composite type that consists of a sequence number and edge number. This is" -" the return type for ST_GetFaceEdges function." +"A composite type that consists of a sequence number and edge number. This is " +"the return type for ST_GetFaceEdges function." msgstr "" #. Tag: para @@ -307,9 +308,9 @@ msgstr "" #: extras_topology.xml:96 #, no-c-format msgid "" -"A composite type that consists of an error message and id1 and id2 to denote" -" location of error. This is the return type for " -"ValidateTopology" +"A composite type that consists of an error message and id1 and id2 to denote " +"location of error. This is the return type for ValidateTopology" msgstr "" #. Tag: para @@ -332,9 +333,9 @@ msgstr "" #: extras_topology.xml:104 #, no-c-format msgid "" -"Current error descriptors are: coincident nodes, edge crosses node, edge not" -" simple, edge end node geometry mis-match, edge start node geometry " -"mismatch, face overlaps face,face within face," +"Current error descriptors are: coincident nodes, edge crosses node, edge not " +"simple, edge end node geometry mis-match, edge start node geometry mismatch, " +"face overlaps face,face within face," msgstr "" #. Tag: para @@ -405,8 +406,8 @@ msgstr "" #: extras_topology.xml:153 #, no-c-format msgid "" -"For any given hierarchical TopoGeometry all child TopoGeometry elements will" -" come from the same child layer, as specified in the topology.layer record " +"For any given hierarchical TopoGeometry all child TopoGeometry elements will " +"come from the same child layer, as specified in the topology.layer record " "for the layer of the TopoGeometry being defined." msgstr "" @@ -454,16 +455,19 @@ msgstr "" #: extras_topology.xml:165 #, no-c-format msgid "" -"--Example of what happens when you try to case a 3 element array to topoelement\n" +"--Example of what happens when you try to case a 3 element array to " +"topoelement\n" "-- NOTE: topoement has to be a 2 element array so fails dimension check\n" "SELECT ARRAY[1,2,3]::topology.topoelement;\n" -"ERROR: value for domain topology.topoelement violates check constraint \"dimensions\"" +"ERROR: value for domain topology.topoelement violates check constraint " +"\"dimensions\"" msgstr "" #. Tag: para #: extras_topology.xml:170 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -515,23 +519,24 @@ msgstr "" #, no-c-format msgid "" "SELECT '{{1,2,4},{3,4,5}}'::topology.topoelementarray As tea;\n" -"ERROR: value for domain topology.topoelementarray violates check constraint \"dimensions\"" +"ERROR: value for domain topology.topoelementarray violates check constraint " +"\"dimensions\"" msgstr "" #. Tag: para #: extras_topology.xml:195 #, no-c-format msgid "" -", , " +", , " msgstr "" #. Tag: para #: extras_topology.xml:207 #, no-c-format msgid "" -"This section lists the Topology functions for building new Topology schemas," -" validating topologies, and managing TopoGeometry Columns" +"This section lists the Topology functions for building new Topology schemas, " +"validating topologies, and managing TopoGeometry Columns" msgstr "" #. Tag: title @@ -558,35 +563,32 @@ msgstr "" #: extras_topology.xml:218 #, no-c-format msgid "" -" text " -"AddTopoGeometryColumn varchar" -" topology_name " -"varchar " -"schema_name varchar " -" table_name varchar" -" column_name " -"varchar " -"feature_type " -" text " -"AddTopoGeometryColumn varchar" -" topology_name " -"varchar " -"schema_name varchar " -" table_name varchar" -" column_name " -"varchar " -"feature_type integer " -" child_layer " +" text AddTopoGeometryColumn varchar topology_name varchar " +"schema_name varchar table_name varchar column_name varchar " +" feature_type " +" text AddTopoGeometryColumn varchar topology_name varchar " +"schema_name varchar table_name varchar column_name varchar " +" feature_type " +"integer child_layer " msgstr "" #. Tag: para #: extras_topology.xml:263 #, no-c-format msgid "" -"Each TopoGeometry object belongs to a specific Layer of a specific Topology." -" Before creating a TopoGeometry object you need to create its TopologyLayer." -" A Topology Layer is an association of a feature-table with the topology. It" -" also contain type and hierarchy information. We create a layer using the " +"Each TopoGeometry object belongs to a specific Layer of a specific Topology. " +"Before creating a TopoGeometry object you need to create its TopologyLayer. " +"A Topology Layer is an association of a feature-table with the topology. It " +"also contain type and hierarchy information. We create a layer using the " "AddTopoGeometryColumn() function:" msgstr "" @@ -639,10 +641,13 @@ msgstr "" #, no-c-format msgid "" "-- Note for this example we created our new table in the ma_topo schema \n" -"-- though we could have created it in a different schema -- in which case topology_name and schema_name would be different \n" +"-- though we could have created it in a different schema -- in which case " +"topology_name and schema_name would be different \n" "CREATE SCHEMA ma;\n" -"CREATE TABLE ma.parcels(gid serial, parcel_id varchar(20) PRIMARY KEY, address text);\n" -"SELECT topology.AddTopoGeometryColumn('ma_topo', 'ma', 'parcels', 'topo', 'POLYGON');" +"CREATE TABLE ma.parcels(gid serial, parcel_id varchar(20) PRIMARY KEY, " +"address text);\n" +"SELECT topology.AddTopoGeometryColumn('ma_topo', 'ma', 'parcels', 'topo', " +"'POLYGON');" msgstr "" #. Tag: programlisting @@ -651,7 +656,8 @@ msgstr "" msgid "" "CREATE SCHEMA ri;\n" "CREATE TABLE ri.roads(gid serial PRIMARY KEY, road_name text);\n" -"SELECT topology.AddTopoGeometryColumn('ri_topo', 'ri', 'roads', 'topo', 'LINE');" +"SELECT topology.AddTopoGeometryColumn('ri_topo', 'ri', 'roads', 'topo', " +"'LINE');" msgstr "" #. Tag: para @@ -680,8 +686,8 @@ msgstr "" #, no-c-format msgid "" "integer DropTopology " -"varchar " -"topology_schema_name" +"varchar topology_schema_name" msgstr "" #. Tag: para @@ -719,9 +725,9 @@ msgstr "" #: extras_topology.xml:334 #, no-c-format msgid "" -"Drops the topogeometry column from the table named " -"table_name in schema schema_name and " -"unregisters the columns from topology.layer table." +"Drops the topogeometry column from the table named table_name in schema schema_name and unregisters the " +"columns from topology.layer table." msgstr "" #. Tag: funcprototype @@ -729,21 +735,21 @@ msgstr "" #, no-c-format msgid "" "text DropTopoGeometryColumn " -"varchar " -"schema_name varchar " -" table_name varchar" -" column_name" +"varchar schema_name varchar table_name varchar column_name" msgstr "" #. Tag: para #: extras_topology.xml:351 #, no-c-format msgid "" -"Drops the topogeometry column from the table named " -"table_name in schema schema_name and " -"unregisters the columns from topology.layer table. Returns summary of drop " -"status. NOTE: it first sets all values to NULL before dropping to bypass " -"referential integrity checks." +"Drops the topogeometry column from the table named table_name in schema schema_name and unregisters the " +"columns from topology.layer table. Returns summary of drop status. NOTE: it " +"first sets all values to NULL before dropping to bypass referential " +"integrity checks." msgstr "" #. Tag: programlisting @@ -772,8 +778,8 @@ msgstr "" #, no-c-format msgid "" "text TopologySummary " -"varchar " -"topology_schema_name" +"varchar topology_schema_name" msgstr "" #. Tag: para @@ -834,9 +840,9 @@ msgstr "" #: extras_topology.xml:417 #, no-c-format msgid "" -"setof validatetopology_returntype " -"ValidateTopology varchar " -" topology_schema_name" +"setof validatetopology_returntype ValidateTopology varchar " +"topology_schema_name" msgstr "" #. Tag: para @@ -1007,8 +1013,7 @@ msgstr "" #. Tag: para #: extras_topology.xml:511 #, no-c-format -msgid "" -"This section covers the topology functions for creating new topologies." +msgid "This section covers the topology functions for creating new topologies." msgstr "" #. Tag: title @@ -1027,34 +1032,32 @@ msgstr "" #: extras_topology.xml:519 #, no-c-format msgid "" -"Creates a new topology schema and registers this new schema in the " -"topology.topology table." +"Creates a new topology schema and registers this new schema in the topology." +"topology table." msgstr "" #. Tag: funcsynopsis #: extras_topology.xml:523 #, no-c-format msgid "" -" integer " -"CreateTopology varchar " -" topology_schema_name " -" integer " -"CreateTopology varchar " -" topology_schema_name " -"integer srid " -" integer " -"CreateTopology varchar " -" topology_schema_name " -"integer srid " -"double precision " -"tolerance " -" integer CreateTopology " -"varchar " +" integer CreateTopology varchar topology_schema_name integer " +"CreateTopology varchar topology_schema_name " +"integer srid integer CreateTopology varchar " "topology_schema_name " "integer srid " -"double precision " -"tolerance boolean " -"hasz " +"double precision tolerance integer " +"CreateTopology varchar topology_schema_name " +"integer srid " +"double precision tolerance boolean hasz " msgstr "" #. Tag: para @@ -1062,14 +1065,13 @@ msgstr "" #, no-c-format msgid "" "Creates a new schema with name topology_name consisting " -"of tables " -"(edge_data,face,node," -" relation and registers this new topology in the " -"topology.topology table. It returns the id of the topology in the topology " -"table. The srid is the spatial reference identified as defined in " -"spatial_ref_sys table for that topology. Topologies must be uniquely named. " -"The tolerance is measured in the units of the spatial reference system. If " -"the tolerance is not specified defaults to 0." +"of tables (edge_data,face," +"node, relation and registers this new " +"topology in the topology.topology table. It returns the id of the topology " +"in the topology table. The srid is the spatial reference identified as " +"defined in spatial_ref_sys table for that topology. Topologies must be " +"uniquely named. The tolerance is measured in the units of the spatial " +"reference system. If the tolerance is not specified defaults to 0." msgstr "" #. Tag: para @@ -1115,7 +1117,8 @@ msgstr "" #. Tag: para #: extras_topology.xml:580 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -1137,9 +1140,9 @@ msgstr "" #, no-c-format msgid "" "integer CopyTopology " -"varchar " -"existing_topology_name " -"varchar new_name" +"varchar existing_topology_name varchar new_name" msgstr "" #. Tag: para @@ -1157,8 +1160,8 @@ msgstr "" #, no-c-format msgid "" "The new rows in topology.layer will contain synthesized values for " -"schema_name, table_name and feature_column. This is because the TopoGeometry" -" will only exist as a definition but won't be available in any user-level " +"schema_name, table_name and feature_column. This is because the TopoGeometry " +"will only exist as a definition but won't be available in any user-level " "table yet." msgstr "" @@ -1190,8 +1193,8 @@ msgstr "" #: extras_topology.xml:636 #, no-c-format msgid "" -"Creates a new topology schema and registers this new schema in the " -"topology.topology table and details summary of process." +"Creates a new topology schema and registers this new schema in the topology." +"topology table and details summary of process." msgstr "" #. Tag: funcprototype @@ -1199,8 +1202,8 @@ msgstr "" #, no-c-format msgid "" "text ST_InitTopoGeo " -"varchar " -"topology_schema_name" +"varchar topology_schema_name" msgstr "" #. Tag: para @@ -1249,8 +1252,8 @@ msgstr "" msgid "" "text ST_CreateTopoGeo " "varchar atopology " -"geometry " -"acollection" +"geometry acollection" msgstr "" #. Tag: para @@ -1289,16 +1292,26 @@ msgstr "" msgid "" "-- Populate topology --\n" "SELECT topology.ST_CreateTopoGeo('ri_topo', \n" -" ST_GeomFromText('MULTILINESTRING((384744 236928,384750 236923,384769 236911,384799 236895,384811 236890,384833 236884,\n" -" 384844 236882,384866 236881,384879 236883,384954 236898,385087 236932,385117 236938,\n" -" 385167 236938,385203 236941,385224 236946,385233 236950,385241 236956,385254 236971,\n" -" 385260 236979,385268 236999,385273 237018,385273 237037,385271 237047,385267 237057,\n" -" 385225 237125,385210 237144,385192 237161,385167 237192,385162 237202,385159 237214,\n" -" 385159 237227,385162 237241,385166 237256,385196 237324,385209 237345,385234 237375,\n" -" 385237 237383,385238 237399,385236 237407,385227 237419,385213 237430,385193 237439,\n" -" 385174 237451,385170 237455,385169 237460,385171 237475,385181 237503,385190 237521,\n" -" 385200 237533,385206 237538,385213 237541,385221 237542,385235 237540,385242 237541,\n" -" 385249 237544,385260 237555,385270 237570,385289 237584,385292 237589,385291 237596,385284 237630))',3438) \n" +" ST_GeomFromText('MULTILINESTRING((384744 236928,384750 236923,384769 " +"236911,384799 236895,384811 236890,384833 236884,\n" +" 384844 236882,384866 236881,384879 236883,384954 236898,385087 " +"236932,385117 236938,\n" +" 385167 236938,385203 236941,385224 236946,385233 236950,385241 " +"236956,385254 236971,\n" +" 385260 236979,385268 236999,385273 237018,385273 237037,385271 " +"237047,385267 237057,\n" +" 385225 237125,385210 237144,385192 237161,385167 237192,385162 " +"237202,385159 237214,\n" +" 385159 237227,385162 237241,385166 237256,385196 237324,385209 " +"237345,385234 237375,\n" +" 385237 237383,385238 237399,385236 237407,385227 237419,385213 " +"237430,385193 237439,\n" +" 385174 237451,385170 237455,385169 237460,385171 237475,385181 " +"237503,385190 237521,\n" +" 385200 237533,385206 237538,385213 237541,385221 237542,385235 " +"237540,385242 237541,\n" +" 385249 237544,385260 237555,385270 237570,385289 237584,385292 " +"237589,385291 237596,385284 237630))',3438) \n" " );\n" "\n" " st_createtopogeo\n" @@ -1309,7 +1322,8 @@ msgid "" "-- create tables and topo geometries --\n" "CREATE TABLE ri.roads(gid serial PRIMARY KEY, road_name text);\n" "\n" -"SELECT topology.AddTopoGeometryColumn('ri_topo', 'ri', 'roads', 'topo', 'LINE');" +"SELECT topology.AddTopoGeometryColumn('ri_topo', 'ri', 'roads', 'topo', " +"'LINE');" msgstr "" #. Tag: para @@ -1339,8 +1353,8 @@ msgid "" "integer TopoGeo_AddPoint " "varchar toponame " "geometry apoint " -"float8 " -"tolerance" +"float8 tolerance" msgstr "" #. Tag: para @@ -1356,8 +1370,8 @@ msgstr "" #: extras_topology.xml:757 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -1381,8 +1395,8 @@ msgid "" "SETOF integer TopoGeo_AddLineString " "varchar toponame " "geometry aline " -"float8 " -"tolerance" +"float8 tolerance" msgstr "" #. Tag: para @@ -1399,8 +1413,8 @@ msgstr "" #: extras_topology.xml:803 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -1424,8 +1438,8 @@ msgid "" "integer TopoGeo_AddPolygon " "varchar atopology " "geometry apoly " -"float8 " -"atolerance" +"float8 atolerance" msgstr "" #. Tag: para @@ -1433,8 +1447,8 @@ msgstr "" #, no-c-format msgid "" "Adds a polygon to an existing topology and return a set of face identifiers " -"forming it up. The boundary of the given polygon will snap to existing nodes" -" or edges within given tolerance. Existing edges and faces may be split by " +"forming it up. The boundary of the given polygon will snap to existing nodes " +"or edges within given tolerance. Existing edges and faces may be split by " "the boundary of the new polygon." msgstr "" @@ -1451,8 +1465,8 @@ msgstr "" #, no-c-format msgid "" "This section covers topology functions for adding, moving, deleting, and " -"splitting edges, faces, and nodes. All of these functions are defined by ISO" -" SQL/MM." +"splitting edges, faces, and nodes. All of these functions are defined by ISO " +"SQL/MM." msgstr "" #. Tag: title @@ -1498,9 +1512,9 @@ msgstr "" #: extras_topology.xml:891 #, no-c-format msgid "" -"If the spatial reference system (srid) of the point geometry is not the same" -" as the topology, the apoint is not a point geometry, the" -" point is null, or the point intersects an existing edge (even at the " +"If the spatial reference system (srid) of the point geometry is not the same " +"as the topology, the apoint is not a point geometry, the " +"point is null, or the point intersects an existing edge (even at the " "boundaries) then an exception is thrown. If the point already exists as a " "node, an exception is thrown." msgstr "" @@ -1509,8 +1523,8 @@ msgstr "" #: extras_topology.xml:893 #, no-c-format msgid "" -"If aface is not null and the apoint is" -" not within the face, then an exception is thrown." +"If aface is not null and the apoint is " +"not within the face, then an exception is thrown." msgstr "" #. Tag: para @@ -1537,10 +1551,10 @@ msgstr "" #: extras_topology.xml:918 #, no-c-format msgid "" -"Adds an isolated edge defined by geometry " -"alinestring to a topology connecting two existing " -"isolated nodes anode and anothernode " -"and returns the edge id of the new edge." +"Adds an isolated edge defined by geometry alinestring to a topology connecting two existing isolated nodes " +"anode and anothernode and returns the " +"edge id of the new edge." msgstr "" #. Tag: funcprototype @@ -1550,27 +1564,27 @@ msgid "" "integer ST_AddIsoEdge " "varchar atopology " "integer anode " -"integer " -"anothernode geometry " -" alinestring" +"integer anothernode geometry alinestring" msgstr "" #. Tag: para #: extras_topology.xml:936 #, no-c-format msgid "" -"Adds an isolated edge defined by geometry " -"alinestring to a topology connecting two existing " -"isolated nodes anode and anothernode " -"and returns the edge id of the new edge." +"Adds an isolated edge defined by geometry alinestring to a topology connecting two existing isolated nodes " +"anode and anothernode and returns the " +"edge id of the new edge." msgstr "" #. Tag: para #: extras_topology.xml:937 #, no-c-format msgid "" -"If the spatial reference system (srid) of the alinestring" -" geometry is not the same as the topology, any of the input arguments are " +"If the spatial reference system (srid) of the alinestring " +"geometry is not the same as the topology, any of the input arguments are " "null, or the nodes are contained in more than one face, or the nodes are " "start or end nodes of an existing edge, then an exception is thrown." msgstr "" @@ -1579,9 +1593,9 @@ msgstr "" #: extras_topology.xml:939 #, no-c-format msgid "" -"If the alinestring is not within the face of the face the" -" anode and anothernode belong to, then" -" an exception is thrown." +"If the alinestring is not within the face of the face the " +"anode and anothernode belong to, then " +"an exception is thrown." msgstr "" #. Tag: para @@ -1627,9 +1641,9 @@ msgid "" "integer ST_AddEdgeNewFaces " "varchar atopology " "integer anode " -"integer " -"anothernode geometry " -" acurve" +"integer anothernode geometry acurve" msgstr "" #. Tag: para @@ -1695,9 +1709,9 @@ msgid "" "integer ST_AddEdgeModFace " "varchar atopology " "integer anode " -"integer " -"anothernode geometry " -" acurve" +"integer anothernode geometry acurve" msgstr "" #. Tag: para @@ -1712,8 +1726,8 @@ msgstr "" #: extras_topology.xml:1045 #, no-c-format msgid "" -"If possible, the new face will be created on left side of the new edge. This" -" will not be possible if the face on the left side will need to be the " +"If possible, the new face will be created on left side of the new edge. This " +"will not be possible if the face on the left side will need to be the " "Universe face (unbounded)." msgstr "" @@ -1767,8 +1781,8 @@ msgstr "" msgid "" "Returns the id of a newly created face or NULL, if no new face is created. " "No new face is created when the removed edge is dangling or isolated or " -"confined with the universe face (possibly making the universe flood into the" -" face on the other side)." +"confined with the universe face (possibly making the universe flood into the " +"face on the other side)." msgstr "" #. Tag: para @@ -1785,8 +1799,8 @@ msgstr "" #, no-c-format msgid "" "If any arguments are null, the given edge is unknown (must already exist in " -"the edge table of the topology schema), the topology name" -" is invalid then an error is thrown." +"the edge table of the topology schema), the topology name " +"is invalid then an error is thrown." msgstr "" #. Tag: para @@ -1865,8 +1879,8 @@ msgstr "" #: extras_topology.xml:1246 #, no-c-format msgid "" -"Changes the shape of an edge without affecting the topology " -"structure." +"Changes the shape of an edge without affecting the topology structure." +"" msgstr "" #. Tag: para @@ -1874,11 +1888,11 @@ msgstr "" #, no-c-format msgid "" "If any arguments are null, the given edge does not exist in the " -"node table of the topology schema, the " -"acurve is not a LINESTRING, the " -"anode and anothernode are not the " -"start and endpoints of acurve or the modification would " -"change the underlying topology then an error is thrown." +"node table of the topology schema, the acurve is not a LINESTRING, the anode and anothernode are not the start and endpoints " +"of acurve or the modification would change the underlying " +"topology then an error is thrown." msgstr "" #. Tag: para @@ -1920,7 +1934,8 @@ msgstr "" #, no-c-format msgid "" "SELECT topology.ST_ChangeEdgeGeom('ma_topo', 1, \n" -" ST_GeomFromText('LINESTRING(227591.9 893900.4,227622.6 893844.3,227641.6 893816.6, 227704.5 893778.5)', 26986) );\n" +" ST_GeomFromText('LINESTRING(227591.9 893900.4,227622.6 " +"893844.3,227641.6 893816.6, 227704.5 893778.5)', 26986) );\n" " ----\n" " Edge 1 changed" msgstr "" @@ -1976,14 +1991,16 @@ msgstr "" #, no-c-format msgid "" "-- Add an edge --\n" -" SELECT topology.AddEdge('ma_topo', ST_GeomFromText('LINESTRING(227592 893910, 227600 893910)', 26986) ) As edgeid;\n" +" SELECT topology.AddEdge('ma_topo', ST_GeomFromText('LINESTRING(227592 " +"893910, 227600 893910)', 26986) ) As edgeid;\n" " \n" "-- edgeid-\n" "3\n" "\n" "\n" "-- Split the edge --\n" -"SELECT topology.ST_ModEdgeSplit('ma_topo', 3, ST_SetSRID(ST_Point(227594,893910),26986) ) As node_id;\n" +"SELECT topology.ST_ModEdgeSplit('ma_topo', 3, " +"ST_SetSRID(ST_Point(227594,893910),26986) ) As node_id;\n" " node_id\n" "-------------------------\n" "7" @@ -2018,8 +2035,7 @@ msgid "" "int ST_ModEdgeHeal " "varchar atopology " "integer anedge " -"integer " -"anotheredge" +"integer anotheredge" msgstr "" #. Tag: para @@ -2053,8 +2069,7 @@ msgid "" "int ST_NewEdgeHeal " "varchar atopology " "integer anedge " -"integer " -"anotheredge" +"integer anotheredge" msgstr "" #. Tag: para @@ -2104,18 +2119,18 @@ msgstr "" #: extras_topology.xml:1463 #, no-c-format msgid "" -"If any arguments are null, the apoint is not a point, the" -" existing node is not isolated (is a start or end point of an existing " -"edge), new node location intersects an existing edge (even at the end " -"points) then an exception is thrown." +"If any arguments are null, the apoint is not a point, the " +"existing node is not isolated (is a start or end point of an existing edge), " +"new node location intersects an existing edge (even at the end points) then " +"an exception is thrown." msgstr "" #. Tag: para #: extras_topology.xml:1464 #, no-c-format msgid "" -"If the spatial reference system (srid) of the point geometry is not the same" -" as the topology an exception is thrown." +"If the spatial reference system (srid) of the point geometry is not the same " +"as the topology an exception is thrown." msgstr "" #. Tag: para @@ -2129,12 +2144,14 @@ msgstr "" #, no-c-format msgid "" "-- Add an isolated node with no face --\n" -"SELECT topology.ST_AddIsoNode('ma_topo', NULL, ST_GeomFromText('POINT(227579 893916)', 26986) ) As nodeid;\n" +"SELECT topology.ST_AddIsoNode('ma_topo', NULL, " +"ST_GeomFromText('POINT(227579 893916)', 26986) ) As nodeid;\n" " nodeid\n" "--------\n" " 7\n" "-- Move the new node --\n" -"SELECT topology.ST_MoveIsoNode('ma_topo', 7, ST_GeomFromText('POINT(227579.5 893916.5)', 26986) ) As descrip; \n" +"SELECT topology.ST_MoveIsoNode('ma_topo', 7, " +"ST_GeomFromText('POINT(227579.5 893916.5)', 26986) ) As descrip; \n" " descrip\n" "----------------------------------------------------\n" "Isolated Node 7 moved to location 227579.5,893916.5" @@ -2151,8 +2168,8 @@ msgstr "" #, no-c-format msgid "" "Split an edge by creating a new node along an existing edge, deleting the " -"original edge and replacing it with two new edges. Returns the id of the new" -" node created that joins the new edges." +"original edge and replacing it with two new edges. Returns the id of the new " +"node created that joins the new edges." msgstr "" #. Tag: funcprototype @@ -2171,18 +2188,18 @@ msgstr "" msgid "" "Split an edge with edge id anedge by creating a new node " "with point location apoint along current edge, deleting " -"the original edge and replacing it with two new edges. Returns the id of the" -" new node created that joins the new edges. Updates all existing joined " -"edges and relationships accordingly." +"the original edge and replacing it with two new edges. Returns the id of the " +"new node created that joins the new edges. Updates all existing joined edges " +"and relationships accordingly." msgstr "" #. Tag: para #: extras_topology.xml:1513 #, no-c-format msgid "" -"If the spatial reference system (srid) of the point geometry is not the same" -" as the topology, the apoint is not a point geometry, the" -" point is null, the point already exists as a node, the edge does not " +"If the spatial reference system (srid) of the point geometry is not the same " +"as the topology, the apoint is not a point geometry, the " +"point is null, the point already exists as a node, the edge does not " "correspond to an existing edge or the point is not within the edge then an " "exception is thrown." msgstr "" @@ -2198,13 +2215,15 @@ msgstr "" #, no-c-format msgid "" "-- Add an edge --\n" -"SELECT topology.AddEdge('ma_topo', ST_GeomFromText('LINESTRING(227575 893917,227592 893900)', 26986) ) As edgeid;\n" +"SELECT topology.AddEdge('ma_topo', ST_GeomFromText('LINESTRING(227575 " +"893917,227592 893900)', 26986) ) As edgeid;\n" "-- result-\n" "edgeid\n" "------\n" " 2\n" "-- Split the new edge --\n" -"SELECT topology.ST_NewEdgesSplit('ma_topo', 2, ST_GeomFromText('POINT(227578.5 893913.5)', 26986) ) As newnodeid; \n" +"SELECT topology.ST_NewEdgesSplit('ma_topo', 2, " +"ST_GeomFromText('POINT(227578.5 893913.5)', 26986) ) As newnodeid; \n" " newnodeid\n" "---------\n" " 6" @@ -2340,7 +2359,8 @@ msgstr "" #: extras_topology.xml:1622 #, no-c-format msgid "" -"SELECT topology.GetEdgeByPoint('ma_topo',geom, 1) As with1mtol, topology.GetEdgeByPoint('ma_topo',geom,0) As withnotol\n" +"SELECT topology.GetEdgeByPoint('ma_topo',geom, 1) As with1mtol, topology." +"GetEdgeByPoint('ma_topo',geom,0) As withnotol\n" "FROM ST_GeomFromEWKT('SRID=26986;POINT(227622.6 893843)') As geom;\n" " with1mtol | withnotol\n" "-----------+-----------\n" @@ -2361,7 +2381,8 @@ msgstr "" #. Tag: para #: extras_topology.xml:1630 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -2431,7 +2452,8 @@ msgstr "" #: extras_topology.xml:1670 #, no-c-format msgid "" -"SELECT topology.GetFaceByPoint('ma_topo',geom, 10) As with1mtol, topology.GetFaceByPoint('ma_topo',geom,0) As withnotol\n" +"SELECT topology.GetFaceByPoint('ma_topo',geom, 10) As with1mtol, topology." +"GetFaceByPoint('ma_topo',geom,0) As withnotol\n" " FROM ST_GeomFromEWKT('POINT(234604.6 899382.0)') As geom;\n" " \n" " with1mtol | withnotol\n" @@ -2453,7 +2475,8 @@ msgstr "" #. Tag: para #: extras_topology.xml:1676 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -2489,8 +2512,8 @@ msgstr "" #, no-c-format msgid "" "The function return an integer (id-node) given a topology, a POINT and a " -"tolerance. If tolerance = 0 mean exactly intersection otherwise retrieve the" -" node from an interval." +"tolerance. If tolerance = 0 mean exactly intersection otherwise retrieve the " +"node from an interval." msgstr "" #. Tag: para @@ -2540,7 +2563,8 @@ msgstr "" #. Tag: para #: extras_topology.xml:1731 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -2601,8 +2625,8 @@ msgstr "" #: extras_topology.xml:1785 #, no-c-format msgid "" -"Returns the SRID of a topology in the topology.topology table given the name" -" of the topology." +"Returns the SRID of a topology in the topology.topology table given the name " +"of the topology." msgstr "" #. Tag: para @@ -2673,8 +2697,8 @@ msgstr "" #: extras_topology.xml:1856 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -2693,10 +2717,10 @@ msgstr "" #: extras_topology.xml:1874 #, no-c-format msgid "" -"getfaceedges_returntype " -"ST_GetFaceEdges varchar " -" atopology integer " -" aface" +"getfaceedges_returntype ST_GetFaceEdges varchar atopology integer aface" msgstr "" #. Tag: para @@ -2712,8 +2736,8 @@ msgstr "" #: extras_topology.xml:1887 #, no-c-format msgid "" -"Enumeration of each ring edges start from the edge with smallest identifier." -" Order of edges follows a left-hand-rule (bound face is on the left of each " +"Enumeration of each ring edges start from the edge with smallest identifier. " +"Order of edges follows a left-hand-rule (bound face is on the left of each " "directed edge)." msgstr "" @@ -2786,8 +2810,8 @@ msgstr "" #: extras_topology.xml:1935 #, no-c-format msgid "" -"Returns the polygon in the given topology with the specified face id. Builds" -" the polygon from the edges making up the face." +"Returns the polygon in the given topology with the specified face id. Builds " +"the polygon from the edges making up the face." msgstr "" #. Tag: para @@ -2807,7 +2831,8 @@ msgid "" " facegeomwkt\n" "\n" "--------------------------------------------------------------------------------\n" -" POLYGON((234776.9 899563.7,234896.5 899456.7,234914 899436.4,234946.6 899356.9,\n" +" POLYGON((234776.9 899563.7,234896.5 899456.7,234914 899436.4,234946.6 " +"899356.9,\n" "234872.5 899328.7,234891 899285.4,234992.5 899145,234890.6 899069,\n" "234755.2 899255.4,234612.7 899379.4,234776.9 899563.7))" msgstr "" @@ -2830,11 +2855,11 @@ msgstr "" #: extras_topology.xml:1968 #, no-c-format msgid "" -"getfaceedges_returntype GetRingEdges" -" varchar atopology" -" integer aring " -"integer " -"max_edges=null" +"getfaceedges_returntype GetRingEdges " +"varchar atopology " +"integer aring " +"integer max_edges=null" msgstr "" #. Tag: para @@ -2892,9 +2917,9 @@ msgstr "" #: extras_topology.xml:2030 #, no-c-format msgid "" -"getfaceedges_returntype GetNodeEdges" -" varchar atopology" -" integer anode" +"getfaceedges_returntype GetNodeEdges " +"varchar atopology " +"integer anode" msgstr "" #. Tag: para @@ -2903,8 +2928,8 @@ msgstr "" msgid "" "Returns an ordered set of edges incident to the given node. Each output " "consists of a sequence and a signed edge id. Sequence numbers start with " -"value 1. A positive edge starts at the given node. A negative edge ends into" -" the given node. Closed edges will appear twice (with both signs). Order is " +"value 1. A positive edge starts at the given node. A negative edge ends into " +"the given node. Closed edges will appear twice (with both signs). Order is " "clockwise starting from northbound." msgstr "" @@ -3013,9 +3038,9 @@ msgid "" "varchar toponame " "geometry apoint " "boolean " -"allowEdgeSplitting=false boolean " -"computeContainingFace=false" +"allowEdgeSplitting=false boolean computeContainingFace=false" msgstr "" #. Tag: para @@ -3023,8 +3048,8 @@ msgstr "" #, no-c-format msgid "" "Adds a point node to the node table in the specified topology schema. The " -" function automatically adds start and end points" -" of an edge when called so not necessary to explicitly add nodes of an edge." +" function automatically adds start and end points " +"of an edge when called so not necessary to explicitly add nodes of an edge." msgstr "" #. Tag: para @@ -3040,23 +3065,24 @@ msgstr "" #: extras_topology.xml:2153 #, no-c-format msgid "" -"If computeContainingFace is true a newly added node would" -" get the correct containing face computed." +"If computeContainingFace is true a newly added node would " +"get the correct containing face computed." msgstr "" #. Tag: para #: extras_topology.xml:2158 #, no-c-format msgid "" -"If the apoint geometry already exists as a node, the node" -" is not added but the existing nodeid is returned." +"If the apoint geometry already exists as a node, the node " +"is not added but the existing nodeid is returned." msgstr "" #. Tag: programlisting #: extras_topology.xml:2167 #, no-c-format msgid "" -"SELECT topology.AddNode('ma_topo', ST_GeomFromText('POINT(227641.6 893816.5)', 26986) ) As nodeid;\n" +"SELECT topology.AddNode('ma_topo', ST_GeomFromText('POINT(227641.6 " +"893816.5)', 26986) ) As nodeid;\n" "-- result --\n" "nodeid\n" "--------\n" @@ -3073,8 +3099,8 @@ msgstr "" #: extras_topology.xml:2181 #, no-c-format msgid "" -"Adds a linestring edge to the edge table and associated start and end points" -" to the point nodes table of the specified topology schema using the " +"Adds a linestring edge to the edge table and associated start and end points " +"to the point nodes table of the specified topology schema using the " "specified linestring geometry and returns the edgeid of the new (or " "existing) edge." msgstr "" @@ -3095,8 +3121,7 @@ msgid "" "Adds an edge to the edge table and associated nodes to the nodes table of " "the specified toponame schema using the specified " "linestring geometry and returns the edgeid of the new or existing record. " -"The newly added edge has \"universe\" face on both sides and links to " -"itself." +"The newly added edge has \"universe\" face on both sides and links to itself." msgstr "" #. Tag: para @@ -3112,9 +3137,9 @@ msgstr "" #: extras_topology.xml:2200 #, no-c-format msgid "" -"The geometry of aline must have the same " -"srid as defined for the topology otherwise an invalid " -"spatial reference sys error will be thrown." +"The geometry of aline must have the same srid as defined for the topology otherwise an invalid spatial reference " +"sys error will be thrown." msgstr "" #. Tag: para @@ -3127,20 +3152,23 @@ msgstr "" #: extras_topology.xml:2210 #, no-c-format msgid "" -"SELECT topology.AddEdge('ma_topo', ST_GeomFromText('LINESTRING(227575.8 893917.2,227591.9 893900.4)', 26986) ) As edgeid;\n" +"SELECT topology.AddEdge('ma_topo', ST_GeomFromText('LINESTRING(227575.8 " +"893917.2,227591.9 893900.4)', 26986) ) As edgeid;\n" "-- result-\n" "edgeid\n" "--------\n" " 1\n" " \n" -"SELECT topology.AddEdge('ma_topo', ST_GeomFromText('LINESTRING(227591.9 893900.4,227622.6 893844.2,227641.6 893816.5,\n" +"SELECT topology.AddEdge('ma_topo', ST_GeomFromText('LINESTRING(227591.9 " +"893900.4,227622.6 893844.2,227641.6 893816.5,\n" " 227704.5 893778.5)', 26986) ) As edgeid;\n" "-- result --\n" "edgeid\n" "--------\n" " 2\n" " \n" -" SELECT topology.AddEdge('ma_topo', ST_GeomFromText('LINESTRING(227591.2 893900, 227591.9 893900.4,\n" +" SELECT topology.AddEdge('ma_topo', ST_GeomFromText('LINESTRING(227591.2 " +"893900, 227591.9 893900.4,\n" " 227704.5 893778.5)', 26986) ) As edgeid;\n" " -- gives error --\n" " ERROR: Edge intersects (not on endpoints) with existing edge 1" @@ -3162,8 +3190,8 @@ msgstr "" #: extras_topology.xml:2224 #, no-c-format msgid "" -"Registers a face primitive to a topology and gets its " -"identifier." +"Registers a face primitive to a topology and gets its identifier." +"" msgstr "" #. Tag: funcprototype @@ -3173,16 +3201,16 @@ msgid "" "integer AddFace " "varchar toponame " "geometry apolygon " -"boolean " -"force_new=false" +"boolean force_new=false" msgstr "" #. Tag: para #: extras_topology.xml:2243 #, no-c-format msgid "" -"Registers a face primitive to a topology and gets its " -"identifier." +"Registers a face primitive to a topology and gets its identifier." msgstr "" #. Tag: para @@ -3200,8 +3228,8 @@ msgstr "" #, no-c-format msgid "" "The target topology is assumed to be valid (containing no self-intersecting " -"edges). An exception is raised if: The polygon boundary is not fully defined" -" by existing edges or the polygon overlaps an existing face." +"edges). An exception is raised if: The polygon boundary is not fully defined " +"by existing edges or the polygon overlaps an existing face." msgstr "" #. Tag: para @@ -3220,17 +3248,17 @@ msgstr "" msgid "" "When a new registration of an existing face is performed (force_new=true), " "no action will be taken to resolve dangling references to the existing face " -"in the edge, node an relation tables, nor will the MBR field of the existing" -" face record be updated. It is up to the caller to deal with that." +"in the edge, node an relation tables, nor will the MBR field of the existing " +"face record be updated. It is up to the caller to deal with that." msgstr "" #. Tag: para #: extras_topology.xml:2276 #, no-c-format msgid "" -"The apolygon geometry must have the same " -"srid as defined for the topology otherwise an invalid " -"spatial reference sys error will be thrown." +"The apolygon geometry must have the same srid as defined for the topology otherwise an invalid spatial reference " +"sys error will be thrown." msgstr "" #. Tag: programlisting @@ -3238,13 +3266,18 @@ msgstr "" #, no-c-format msgid "" "-- first add the edges we use generate_series as an iterator (the below \n" -"-- will only work for polygons with < 10000 points because of our max in gs) \n" -"SELECT topology.AddEdge('ma_topo', ST_MakeLine(ST_PointN(geom,i), ST_PointN(geom, i + 1) )) As edgeid\n" +"-- will only work for polygons with < 10000 points because of our max in " +"gs) \n" +"SELECT topology.AddEdge('ma_topo', ST_MakeLine(ST_PointN(geom,i), " +"ST_PointN(geom, i + 1) )) As edgeid\n" " FROM (SELECT ST_NPoints(geom) AS npt, geom\n" " FROM \n" -" (SELECT ST_Boundary(ST_GeomFromText('POLYGON((234896.5 899456.7,234914 899436.4,234946.6 899356.9,234872.5 899328.7,\n" -" 234891 899285.4,234992.5 899145, 234890.6 899069,234755.2 899255.4,\n" -" 234612.7 899379.4,234776.9 899563.7,234896.5 899456.7))', 26986) ) As geom\n" +" (SELECT ST_Boundary(ST_GeomFromText('POLYGON((234896.5 " +"899456.7,234914 899436.4,234946.6 899356.9,234872.5 899328.7,\n" +" 234891 899285.4,234992.5 899145, 234890.6 899069,234755.2 " +"899255.4,\n" +" 234612.7 899379.4,234776.9 899563.7,234896.5 899456.7))', " +"26986) ) As geom\n" " ) As geoms) As facen CROSS JOIN generate_series(1,10000) As i\n" " WHERE i < npt;\n" "-- result --\n" @@ -3264,9 +3297,11 @@ msgid "" "-- then add the face -\n" " \n" "SELECT topology.AddFace('ma_topo', \n" -" ST_GeomFromText('POLYGON((234896.5 899456.7,234914 899436.4,234946.6 899356.9,234872.5 899328.7,\n" +" ST_GeomFromText('POLYGON((234896.5 899456.7,234914 899436.4,234946.6 " +"899356.9,234872.5 899328.7,\n" " 234891 899285.4,234992.5 899145, 234890.6 899069,234755.2 899255.4,\n" -" 234612.7 899379.4,234776.9 899563.7,234896.5 899456.7))', 26986) ) As faceid;\n" +" 234612.7 899379.4,234776.9 899563.7,234896.5 899456.7))', 26986) ) As " +"faceid;\n" "-- result --\n" "faceid\n" "--------\n" @@ -3276,7 +3311,8 @@ msgstr "" #. Tag: para #: extras_topology.xml:2291 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -3365,51 +3401,49 @@ msgstr "" #: extras_topology.xml:2344 #, no-c-format msgid "" -"Creates a new topo geometry object from topo element array - tg_type: " -"1:[multi]point, 2:[multi]line, 3:[multi]poly, 4:collection" +"Creates a new topo geometry object from topo element array - tg_type: 1:" +"[multi]point, 2:[multi]line, 3:[multi]poly, 4:collection" msgstr "" #. Tag: funcsynopsis #: extras_topology.xml:2348 #, no-c-format msgid "" -" topogeometry " -"CreateTopoGeom varchar " -" toponame integer " -" tg_type " -"integer layer_id " -"topoelementarray " -"tg_objs " -"topogeometry CreateTopoGeom " -"varchar toponame " -"integer tg_type " -"integer layer_id " -"" +" topogeometry CreateTopoGeom varchar toponame integer tg_type integer layer_id topoelementarray tg_objs topogeometry " +"CreateTopoGeom varchar toponame integer tg_type integer layer_id " msgstr "" #. Tag: para #: extras_topology.xml:2369 #, no-c-format msgid "" -"Creates a topogeometry object for layer denoted by layer_id and registers it" -" in the relations table in the toponame schema." +"Creates a topogeometry object for layer denoted by layer_id and registers it " +"in the relations table in the toponame schema." msgstr "" #. Tag: para #: extras_topology.xml:2370 #, no-c-format msgid "" -"tg_type is an integer: 1:[multi]point (punctal), 2:[multi]line (lineal), " -"3:[multi]poly (areal), 4:collection. layer_id is the layer id in the " -"topology.layer table." +"tg_type is an integer: 1:[multi]point (punctal), 2:[multi]line (lineal), 3:" +"[multi]poly (areal), 4:collection. layer_id is the layer id in the topology." +"layer table." msgstr "" #. Tag: para #: extras_topology.xml:2371 #, no-c-format msgid "" -"punctal layers are formed from set of nodes, lineal layers are formed from a" -" set of edges, areal layers are formed from a set of faces, and collections " +"punctal layers are formed from set of nodes, lineal layers are formed from a " +"set of edges, areal layers are formed from a set of faces, and collections " "can be formed from a mixture of nodes, edges, and faces." msgstr "" @@ -3438,8 +3472,8 @@ msgstr "" #: extras_topology.xml:2382 #, no-c-format msgid "" -"INSERT INTO ri.ri_roads(road_name, topo) VALUES('Unknown', " -"topology.CreateTopoGeom('ri_topo',2,2,'{{1,2}}'::topology.topoelementarray);" +"INSERT INTO ri.ri_roads(road_name, topo) VALUES('Unknown', topology." +"CreateTopoGeom('ri_topo',2,2,'{{1,2}}'::topology.topoelementarray);" msgstr "" #. Tag: title @@ -3454,8 +3488,8 @@ msgstr "" msgid "" "Lets say we have geometries that should be formed from a collection of " "faces. We have for example blockgroups table and want to know the topo " -"geometry of each block group. If our data was perfectly aligned, we could do" -" this:" +"geometry of each block group. If our data was perfectly aligned, we could do " +"this:" msgstr "" #. Tag: programlisting @@ -3476,10 +3510,12 @@ msgid "" " SET topo = topology.CreateTopoGeom('topo_boston'\n" " ,3,1\n" " , foo.bfaces)\n" -"FROM (SELECT b.gid, topology.TopoElementArray_Agg(ARRAY[f.face_id,3]) As bfaces\n" +"FROM (SELECT b.gid, topology.TopoElementArray_Agg(ARRAY[f.face_id,3]) As " +"bfaces\n" " FROM boston.blockgroups As b\n" " INNER JOIN topo_boston.face As f ON b.geom && f.mbr\n" -" WHERE ST_Covers(b.geom, topology.ST_GetFaceGeometry('topo_boston', f.face_id))\n" +" WHERE ST_Covers(b.geom, topology.ST_GetFaceGeometry('topo_boston', f." +"face_id))\n" " GROUP BY b.gid) As foo\n" "WHERE foo.gid = bg.gid;" msgstr "" @@ -3495,14 +3531,19 @@ msgid "" " SET topo = topology.CreateTopoGeom('topo_boston'\n" " ,3,1\n" " , foo.bfaces)\n" -"FROM (SELECT b.gid, topology.TopoElementArray_Agg(ARRAY[f.face_id,3]) As bfaces\n" +"FROM (SELECT b.gid, topology.TopoElementArray_Agg(ARRAY[f.face_id,3]) As " +"bfaces\n" " FROM boston.blockgroups As b\n" " INNER JOIN topo_boston.face As f ON b.geom && f.mbr\n" -" WHERE ST_Covers(b.geom, topology.ST_GetFaceGeometry('topo_boston', f.face_id))\n" +" WHERE ST_Covers(b.geom, topology.ST_GetFaceGeometry('topo_boston', f." +"face_id))\n" " OR\n" -" ( ST_Intersects(b.geom, topology.ST_GetFaceGeometry('topo_boston', f.face_id))\n" -" AND ST_Area(ST_Intersection(b.geom, topology.ST_GetFaceGeometry('topo_boston', f.face_id) ) ) > \n" -" ST_Area(topology.ST_GetFaceGeometry('topo_boston', f.face_id))*0.5\n" +" ( ST_Intersects(b.geom, topology.ST_GetFaceGeometry('topo_boston', f." +"face_id))\n" +" AND ST_Area(ST_Intersection(b.geom, topology." +"ST_GetFaceGeometry('topo_boston', f.face_id) ) ) > \n" +" ST_Area(topology.ST_GetFaceGeometry('topo_boston', f." +"face_id))*0.5\n" " )\n" " GROUP BY b.gid) As foo\n" "WHERE foo.gid = bg.gid; \n" @@ -3519,8 +3560,8 @@ msgstr "" #: extras_topology.xml:2398 #, no-c-format msgid "" -", , , , " +", , , , " "" msgstr "" @@ -3540,19 +3581,17 @@ msgstr "" #: extras_topology.xml:2419 #, no-c-format msgid "" -" topogeometry " +" topogeometry toTopoGeom geometry geom varchar toponame integer layer_id float8 tolerance topogeometry " "toTopoGeom geometry " -"geom varchar " -"toponame integer " -"layer_id float8 " -"tolerance " -" topogeometry toTopoGeom " -"geometry geom " -"topogeometry " -"topogeom float8 " -"tolerance " +"geom topogeometry " +"topogeom float8 tolerance " msgstr "" #. Tag: para @@ -3566,9 +3605,9 @@ msgstr "" #, no-c-format msgid "" "Topological primitives required to represent the input geometry will be " -"added to the underlying topology, possibly splitting existing ones, and they" -" will be associated with the output TopoGeometry in the " -"relation table." +"added to the underlying topology, possibly splitting existing ones, and they " +"will be associated with the output TopoGeometry in the relation table." msgstr "" #. Tag: para @@ -3583,8 +3622,8 @@ msgstr "" #: extras_topology.xml:2456 #, no-c-format msgid "" -"When tolerance is given it will be used to snap the input" -" geometry to existing primitives." +"When tolerance is given it will be used to snap the input " +"geometry to existing primitives." msgstr "" #. Tag: para @@ -3592,8 +3631,8 @@ msgstr "" #, no-c-format msgid "" "In the first form a new TopoGeometry will be created for the given layer " -"(layer_id) of the given topology " -"(toponame)." +"(layer_id) of the given topology (toponame)." msgstr "" #. Tag: para @@ -3628,7 +3667,8 @@ msgid "" "-- create a new table\n" "CREATE TABLE nei_topo(gid serial primary key, nei varchar(30));\n" "--add a topogeometry column to it\n" -"SELECT topology.AddTopoGeometryColumn('topo_boston_test', 'public', 'nei_topo', 'topo', 'MULTIPOLYGON') As new_layer_id;\n" +"SELECT topology.AddTopoGeometryColumn('topo_boston_test', 'public', " +"'nei_topo', 'topo', 'MULTIPOLYGON') As new_layer_id;\n" "new_layer_id\n" "-----------\n" "1\n" @@ -3673,9 +3713,8 @@ msgstr "" #: extras_topology.xml:2488 #, no-c-format msgid "" -", , , , " +", , , , " msgstr "" #. Tag: refname @@ -3696,10 +3735,9 @@ msgstr "" #: extras_topology.xml:2506 #, no-c-format msgid "" -"topoelementarray " -"TopoElementArray_Agg " -"topoelement set " -"tefield" +"topoelementarray TopoElementArray_Agg topoelement set tefield" msgstr "" #. Tag: para @@ -3758,8 +3796,8 @@ msgstr "" #, no-c-format msgid "" "topogeometry clearTopoGeom " -"topogeometry " -"topogeom" +"topogeometry topogeom" msgstr "" #. Tag: para @@ -3823,20 +3861,20 @@ msgstr "" #: extras_topology.xml:2613 #, no-c-format msgid "" -"topoelementarray " -"GetTopoGeomElementArray " -"varchar toponame " -"integer layer_id " -"integer tg_id" +"topoelementarray GetTopoGeomElementArray varchar toponame integer layer_id integer tg_id" msgstr "" #. Tag: funcprototype #: extras_topology.xml:2621 #, no-c-format msgid "" -"topoelementarray topoelement " -"GetTopoGeomElementArray " -"topogeometry tg" +"topoelementarray topoelement GetTopoGeomElementArray topogeometry tg" msgstr "" #. Tag: para @@ -3854,8 +3892,7 @@ msgstr "" #, no-c-format msgid "" "tg_id is the topogeometry id of the topogeometry object in the topology in " -"the layer denoted by layer_id in the topology.layer " -"table." +"the layer denoted by layer_id in the topology.layer table." msgstr "" #. Tag: refname @@ -3877,20 +3914,20 @@ msgstr "" #: extras_topology.xml:2661 #, no-c-format msgid "" -"setof topoelement " -"GetTopoGeomElements varchar " -" toponame integer " -" layer_id " -"integer tg_id" +"setof topoelement GetTopoGeomElements varchar toponame integer layer_id integer tg_id" msgstr "" #. Tag: funcprototype #: extras_topology.xml:2669 #, no-c-format msgid "" -"setof topoelement " -"GetTopoGeomElements " -"topogeometry tg" +"setof topoelement GetTopoGeomElements topogeometry tg" msgstr "" #. Tag: para @@ -3930,46 +3967,43 @@ msgstr "" #, no-c-format msgid "" " text AsGML " -"topogeometry tg " -" text " -"AsGML topogeometry " -"tg text " -"nsprefix_in " -" text AsGML " -"topogeometry tg " -"regclass " +"topogeometry tg text AsGML topogeometry tg text nsprefix_in text AsGML topogeometry tg regclass " "visitedTable " " text AsGML " "topogeometry tg " -"regclass " -"visitedTable text " -"nsprefix " -"text AsGML " -"topogeometry tg " -"text nsprefix_in " -"integer precision " -"integer options " -" text " +"regclass visitedTable text nsprefix text AsGML topogeometry tg text nsprefix_in integer precision integer options text " "AsGML topogeometry " "tg text " -"nsprefix_in integer " -" precision integer " -" options regclass " -" visitedTable " +"nsprefix_in integer precision integer options regclass visitedTable " " text AsGML " "topogeometry tg " "text nsprefix_in " "integer precision " "integer options " -"regclass " -"visitedTable text " -"idprefix " -"text AsGML " -"topogeometry tg " -"text nsprefix_in " -"integer precision " -"integer options " -"regclass " +"regclass visitedTable text idprefix text AsGML topogeometry tg text nsprefix_in integer precision integer options regclass " "visitedTable text " "idprefix int " "gmlversion " @@ -3990,15 +4024,15 @@ msgstr "" #: extras_topology.xml:2776 #, no-c-format msgid "" -"The visitedTable parameter, if given, is used for keeping" -" track of the visited Node and Edge elements so to use cross-references " +"The visitedTable parameter, if given, is used for keeping " +"track of the visited Node and Edge elements so to use cross-references " "(xlink:xref) rather than duplicating definitions. The table is expected to " "have (at least) two integer fields: 'element_type' and 'element_id'. The " "calling user must have both read and write privileges on the given table. " -"For best performance, an index should be defined on " -"element_type and element_id, in that " -"order. Such index would be created automatically by adding a unique " -"constraint to the fields. Example:" +"For best performance, an index should be defined on element_type and element_id, in that order. Such index would " +"be created automatically by adding a unique constraint to the fields. " +"Example:" msgstr "" #. Tag: programlisting @@ -4054,15 +4088,24 @@ msgid "" " \n" " \n" " \n" -" 384744 236928 384750 236923 384769 236911 384799 236895 384811 236890 \n" -" 384833 236884 384844 236882 384866 236881 384879 236883 384954 236898 385087 236932 385117 236938 \n" -" 385167 236938 385203 236941 385224 236946 385233 236950 385241 236956 385254 236971 \n" -" 385260 236979 385268 236999 385273 237018 385273 237037 385271 237047 385267 237057 385225 237125 \n" -" 385210 237144 385192 237161 385167 237192 385162 237202 385159 237214 385159 237227 385162 237241 \n" -" 385166 237256 385196 237324 385209 237345 385234 237375 385237 237383 385238 237399 385236 237407 \n" -" 385227 237419 385213 237430 385193 237439 385174 237451 385170 237455 385169 237460 385171 237475 \n" -" 385181 237503 385190 237521 385200 237533 385206 237538 385213 237541 385221 237542 385235 237540 385242 237541 \n" -" 385249 237544 385260 237555 385270 237570 385289 237584 385292 237589 385291 237596 385284 237630\n" +" 384744 236928 " +"384750 236923 384769 236911 384799 236895 384811 236890 \n" +" 384833 236884 384844 236882 384866 236881 384879 " +"236883 384954 236898 385087 236932 385117 236938 \n" +" 385167 236938 385203 236941 385224 236946 385233 " +"236950 385241 236956 385254 236971 \n" +" 385260 236979 385268 236999 385273 237018 385273 " +"237037 385271 237047 385267 237057 385225 237125 \n" +" 385210 237144 385192 237161 385167 237192 385162 " +"237202 385159 237214 385159 237227 385162 237241 \n" +" 385166 237256 385196 237324 385209 237345 385234 " +"237375 385237 237383 385238 237399 385236 237407 \n" +" 385227 237419 385213 237430 385193 237439 385174 " +"237451 385170 237455 385169 237460 385171 237475 \n" +" 385181 237503 385190 237521 385200 237533 385206 " +"237538 385213 237541 385221 237542 385235 237540 385242 237541 \n" +" 385249 237544 385260 237555 385270 237570 385289 " +"237584 385292 237589 385291 237596 385284 237630\n" " \n" " \n" " \n" @@ -4098,15 +4141,24 @@ msgid "" " \n" " \n" " \n" -" 384744 236928 384750 236923 384769 236911 384799 236895 384811 236890 \n" -" 384833 236884 384844 236882 384866 236881 384879 236883 384954 236898 385087 236932 385117 236938 \n" -" 385167 236938 385203 236941 385224 236946 385233 236950 385241 236956 385254 236971 \n" -" 385260 236979 385268 236999 385273 237018 385273 237037 385271 237047 385267 237057 385225 237125 \n" -" 385210 237144 385192 237161 385167 237192 385162 237202 385159 237214 385159 237227 385162 237241 \n" -" 385166 237256 385196 237324 385209 237345 385234 237375 385237 237383 385238 237399 385236 237407 \n" -" 385227 237419 385213 237430 385193 237439 385174 237451 385170 237455 385169 237460 385171 237475 \n" -" 385181 237503 385190 237521 385200 237533 385206 237538 385213 237541 385221 237542 385235 237540 385242 237541 \n" -" 385249 237544 385260 237555 385270 237570 385289 237584 385292 237589 385291 237596 385284 237630\n" +" 384744 236928 384750 " +"236923 384769 236911 384799 236895 384811 236890 \n" +" 384833 236884 384844 236882 384866 236881 384879 " +"236883 384954 236898 385087 236932 385117 236938 \n" +" 385167 236938 385203 236941 385224 236946 385233 " +"236950 385241 236956 385254 236971 \n" +" 385260 236979 385268 236999 385273 237018 385273 " +"237037 385271 237047 385267 237057 385225 237125 \n" +" 385210 237144 385192 237161 385167 237192 385162 " +"237202 385159 237214 385159 237227 385162 237241 \n" +" 385166 237256 385196 237324 385209 237345 385234 " +"237375 385237 237383 385238 237399 385236 237407 \n" +" 385227 237419 385213 237430 385193 237439 385174 " +"237451 385170 237455 385169 237460 385171 237475 \n" +" 385181 237503 385190 237521 385200 237533 385206 " +"237538 385213 237541 385221 237542 385235 237540 385242 237541 \n" +" 385249 237544 385260 237555 385270 237570 385289 " +"237584 385292 237589 385291 237596 385284 237630\n" " \n" " \n" " \n" @@ -4140,8 +4192,8 @@ msgstr "" msgid "" "text AsTopoJSON " "topogeometry tg " -"regclass " -"edgeMapTable" +"regclass edgeMapTable" msgstr "" #. Tag: para @@ -4149,18 +4201,18 @@ msgstr "" #, no-c-format msgid "" "Returns the TopoJSON representation of a topogeometry. If " -"edgeMapTable is not null, it will be used as a " -"lookup/storage mapping of edge identifiers to arc indices. This is to be " -"able to allow for a compact \"arcs\" array in the final document." +"edgeMapTable is not null, it will be used as a lookup/" +"storage mapping of edge identifiers to arc indices. This is to be able to " +"allow for a compact \"arcs\" array in the final document." msgstr "" #. Tag: para #: extras_topology.xml:2831 #, no-c-format msgid "" -"The table, if given, is expected to have an \"arc_id\" field of type " -"\"serial\" and an \"edge_id\" of type integer; the code will query the table" -" for \"edge_id\" so it is recommended to add an index on that field." +"The table, if given, is expected to have an \"arc_id\" field of type \"serial" +"\" and an \"edge_id\" of type integer; the code will query the table for " +"\"edge_id\" so it is recommended to add an index on that field." msgstr "" #. Tag: para @@ -4177,9 +4229,8 @@ msgstr "" msgid "" "A full TopoJSON document will be need to contain, in addition to the " "snippets returned by this function, the actual arcs plus some headers. See " -"the TopoJSON " -"specification." +"the TopoJSON specification." msgstr "" #. Tag: programlisting @@ -4189,10 +4240,12 @@ msgid "" "CREATE TEMP TABLE edgemap(arc_id serial, edge_id int unique);\n" "\n" "-- header\n" -"SELECT '{ \"type\": \"Topology\", \"transform\": { \"scale\": [1,1], \"translate\": [0,0] }, \"objects\": {'\n" +"SELECT '{ \"type\": \"Topology\", \"transform\": { \"scale\": [1,1], " +"\"translate\": [0,0] }, \"objects\": {'\n" "\n" "-- objects\n" -"UNION ALL SELECT '\"' || feature_name || '\": ' || AsTopoJSON(feature, 'edgemap')\n" +"UNION ALL SELECT '\"' || feature_name || '\": ' || AsTopoJSON(feature, " +"'edgemap')\n" "FROM features.big_parcels WHERE feature_name = 'P3P4';\n" "\n" "-- arcs\n" @@ -4213,7 +4266,8 @@ msgid "" " SELECT arc_id, (regexp_matches( ST_AsGeoJSON(geom), '\\[.*\\]'))[1] as t\n" " FROM compare\n" "), arcs AS (\n" -" SELECT arc_id, '[' || array_to_string(array_agg(t), ',') || ']' as a FROM arcsdump\n" +" SELECT arc_id, '[' || array_to_string(array_agg(t), ',') || ']' as a FROM " +"arcsdump\n" " GROUP BY arc_id\n" " ORDER BY arc_id\n" ")\n" @@ -4224,8 +4278,10 @@ msgid "" "UNION ALL SELECT ']}'::text as t;\n" "\n" "-- Result:\n" -"{ \"type\": \"Topology\", \"transform\": { \"scale\": [1,1], \"translate\": [0,0] }, \"objects\": {\n" -"\"P3P4\": { \"type\": \"MultiPolygon\", \"arcs\": [[[-1]],[[6,5,-5,-4,-3,1]]]}\n" +"{ \"type\": \"Topology\", \"transform\": { \"scale\": [1,1], \"translate\": " +"[0,0] }, \"objects\": {\n" +"\"P3P4\": { \"type\": \"MultiPolygon\", \"arcs\": [[[-1]]," +"[[6,5,-5,-4,-3,1]]]}\n" "}, \"arcs\": [\n" " [[25,30],[6,0],[0,10],[-14,0],[0,-10],[8,0]],\n" " [[35,6],[0,8]],\n" diff --git a/doc/po/de_DE/faq.xml.po b/doc/po/de_DE/faq.xml.po index 53bd61072..8e3e317de 100644 --- a/doc/po/de_DE/faq.xml.po +++ b/doc/po/de_DE/faq.xml.po @@ -11,11 +11,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:23+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -37,29 +38,28 @@ msgstr "" #: faq.xml:12 #, no-c-format msgid "" -"OpenGeo has a step by step tutorial guide workshop Introduction to " -"PostGIS. It includes packaged data as well as intro to working with " -"OpenGeo Suite. It is probably the best tutorial on PostGIS." +"OpenGeo has a step by step tutorial guide workshop Introduction to PostGIS. " +"It includes packaged data as well as intro to working with OpenGeo Suite. It " +"is probably the best tutorial on PostGIS." msgstr "" -"OpenGeo hat ein schrittweises Lernprogramm Introduction to " -"PostGIS. Es beinhaltet sowohl paketierte Daten als auch ein " -"Einführung in das Arbeiten mit der OpenGeo-Suite. Es ist wahrscheinlich das " -"beste Lernprogramm für PostGIS." +"OpenGeo hat ein schrittweises Lernprogramm Introduction to PostGIS. Es beinhaltet " +"sowohl paketierte Daten als auch ein Einführung in das Arbeiten mit der " +"OpenGeo-Suite. Es ist wahrscheinlich das beste Lernprogramm für PostGIS." #. Tag: para #: faq.xml:13 #, no-c-format msgid "" -"BostonGIS also has a PostGIS" -" almost idiot's guide on getting started. That one is more focused " -"on the windows user." +"BostonGIS also has a PostGIS almost idiot's guide on getting " +"started. That one is more focused on the windows user." msgstr "" -"Außerdem hat BostonGIS ein PostGIS almost idiot's guide on getting " -"started. Dieser ist eher für Windows-Benutzer gedacht." +"Außerdem hat BostonGIS ein PostGIS almost idiot's " +"guide on getting started. Dieser ist eher für Windows-Benutzer " +"gedacht." #. Tag: para #: faq.xml:18 @@ -68,33 +68,32 @@ 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 "" -"Meine Anwendungen und Arbeitsflächenwerkzeuge funktionierten mit PostGIS 1.5, " -"nicht jedoch mit PostGIS 2.0. Wie kann ich dies beheben?" +"Meine Anwendungen und Arbeitsflächenwerkzeuge funktionierten mit PostGIS " +"1.5, nicht jedoch mit PostGIS 2.0. Wie kann ich dies beheben?" #. Tag: para #: faq.xml:22 #, 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 " +"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 " -"legacy.sql or just the portions of " -"legacy.sql you need." +"etc. and as a last resort, install the whole of legacy.sql or just the portions of legacy.sql you need." msgstr "" "Viele missbilligte Funktionen wurden aus der Codebasis von PostGIS 2.0 " "entfernt. Dies betraf Anwendungen sowie Werkzeuge von Drittanbietern wie " "Geoserver, MapServer, QuantumGIS und OpenJump, um einige zu nennen. Es gibt " -"ein paar Wege, dies zu beheben. Für die Anwendungen von Drittanbietern können " -"Sie versuchen, sie auf die neuste Version zu aktualisieren, bei der viele " -"dieser Probleme behoben wurden. Ihren eigenen Code könne Sie so ändern, dass " -"er die entfernten Funktionen nicht mehr benutzt. Die meisten dieser " -"Funktionen sind Nicht-ST-Alias von ST_Union, ST_Length etc. und als letzten " -"Ausweg können Sie die gesamte legacy.sql oder nur " +"ein paar Wege, dies zu beheben. Für die Anwendungen von Drittanbietern " +"können Sie versuchen, sie auf die neuste Version zu aktualisieren, bei der " +"viele dieser Probleme behoben wurden. Ihren eigenen Code könne Sie so " +"ändern, dass er die entfernten Funktionen nicht mehr benutzt. Die meisten " +"dieser Funktionen sind Nicht-ST-Alias von ST_Union, ST_Length etc. und als " +"letzten Ausweg können Sie die gesamte legacy.sql oder nur " "die Teile davon, die Sie benötigen, installieren." #. Tag: para @@ -107,17 +106,17 @@ msgid "" "removed." msgstr "" "Die Datei legacy.sql liegt im selben Verzeichnis wie " -"»postgis.sql«. Sie können diese Datei nach der Installation von »postgis.sql« " -"und »spatial_ref_sys.sql« installieren, um alle etwa 200 alten Funktionen " -"zurückzubekommen, die entfernt wurden." +"»postgis.sql«. Sie können diese Datei nach der Installation von »postgis." +"sql« und »spatial_ref_sys.sql« installieren, um alle etwa 200 alten " +"Funktionen zurückzubekommen, die entfernt wurden." #. Tag: para #: faq.xml:35 #, no-c-format msgid "" "When I load OpenStreetMap data with osm2pgsql, I'm getting an error failed: " -"ERROR: operator class \"gist_geometry_ops\" does not exist for access method" -" \"gist\" Error occurred. This worked fine in PostGIS 1.5." +"ERROR: operator class \"gist_geometry_ops\" does not exist for access method " +"\"gist\" Error occurred. This worked fine in PostGIS 1.5." msgstr "" "Wenn ich OpenStreetMap-Daten mit »osm2pgsql« lade, bekomme ich eine " "Fehlermeldung: »operator class \"gist_geometry_ops\" does not exist for " @@ -134,8 +133,8 @@ msgid "" msgstr "" "In PostGIS 2 wurde die Standardgeometrieoperatorklasse »gist_geometry_ops« " "in »gist_geometry_ops_2d« geändert und »gist_geometry_ops« wurde vollständig " -"entfernt. Grund ist, dass PostGIS auch räumliche Nd-Indizes für " -"3D-Unterstützung einführt und der alte Name als verwirrend und fehlerhaft " +"entfernt. Grund ist, dass PostGIS auch räumliche Nd-Indizes für 3D-" +"Unterstützung einführt und der alte Name als verwirrend und fehlerhaft " "angesehen wurde." #. Tag: para @@ -143,14 +142,14 @@ msgstr "" #, no-c-format msgid "" "Some older applications that as part of the process create tables and " -"indexes, explicitly referenced the operator class name. This was unnecessary" -" if you want the default 2D index. So if you manage said good, change index " +"indexes, explicitly referenced the operator class name. This was unnecessary " +"if you want the default 2D index. So if you manage said good, change index " "creation from:" msgstr "" "Einige ältere Anwendungen, die als Teil des Prozesses Tabellen und Indizes " -"erstellen, referenzieren explizit den Operatorklassennamen. Dies war unnötig, " -"falls Sie den Standard-2D-Index wollten. Falls Sie dies also gut hinbekommen " -"möchten, ändern Sie die Indexerstellung von:" +"erstellen, referenzieren explizit den Operatorklassennamen. Dies war " +"unnötig, falls Sie den Standard-2D-Index wollten. Falls Sie dies also gut " +"hinbekommen möchten, ändern Sie die Indexerstellung von:" #. Tag: para #: faq.xml:42 @@ -236,47 +235,46 @@ msgstr "" 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 " +"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 "" "In PostgreSQL 9.0+ wurde die Standardcodierung für »bytea«-Daten in " -"hexadezimal geändert und ältere JDBC-Treiber gehen immer noch vom " -"Escape-Format aus. Dies beeinflusste einige Anwendungen wie Java-Programme, " -"die ältere JDBC-Treiber benutzen oder .NET-Anwendungen, die ältere " -"»npgsql«-Treiber verwenden, die das frühere Verhalten von ST_AsBinary " -"erwarten. Es gibt zwei Herangehensweisen, dies wieder zum Laufen zu bringen." +"hexadezimal geändert und ältere JDBC-Treiber gehen immer noch vom Escape-" +"Format aus. Dies beeinflusste einige Anwendungen wie Java-Programme, die " +"ältere JDBC-Treiber benutzen oder .NET-Anwendungen, die ältere »npgsql«-" +"Treiber verwenden, die das frühere Verhalten von ST_AsBinary erwarten. Es " +"gibt zwei Herangehensweisen, dies wieder zum Laufen zu bringen." #. Tag: para #: faq.xml:64 #, no-c-format msgid "" "You can upgrade your JDBC driver to the latest PostgreSQL 9.0 version which " -"you can get from http://jdbc.postgresql.org/download.html" +"you can get from http://jdbc.postgresql.org/download.html" msgstr "" "Sie können Ihren JDBC-Treiber auf die neuste PostgreSQL-9.0-Version " -"aktualisieren. Diese erhalten Sie unter " -"http://jdbc.postgresql.org/download.html." +"aktualisieren. Diese erhalten Sie unter http://jdbc.postgresql.org/download.html." #. Tag: para #: faq.xml:66 #, 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 http://pgfoundry.org/frs/?group_id=1000140" -" and as described on Francisco" -" Figueiredo's NpgSQL 2.0.11 released blog entry" +"If you are running a .NET app, you can use Npgsql 2.0.11 or higher which you " +"can download from http://pgfoundry.org/frs/?group_id=1000140 and as " +"described on Francisco Figueiredo's NpgSQL 2.0.11 released blog entry" msgstr "" "Falls Sie eine .NET-Anwendung ausführen, können Sie Npgsql 2.0.11 oder neuer " -"verwenden. Dies können Sie von http://pgfoundry.org/frs/?group_id=1000140, wie im " -"Blog-Eintrag von Francisco Figueiredo zur Veröffentlichung von NpgSQL 2.0.11<" -"/ulink> beschrieben, herunterladen." +"verwenden. Dies können Sie von http://pgfoundry.org/frs/?group_id=1000140, wie " +"im Blog-Eintrag von Francisco Figueiredo zur Veröffentlichung von NpgSQL " +"2.0.11 beschrieben, herunterladen." #. Tag: para #: faq.xml:70 @@ -319,12 +317,12 @@ msgstr "" #: faq.xml:85 #, no-c-format msgid "" -"-- this should return no records if all your geom fields are filled in \n" +"-- this should return no records if all your geom fields are filled " +"in \n" "SELECT somefield FROM mytable WHERE geom IS NULL;" msgstr "" "-- Falls alle Geometriefelder gefüllt sind, sollte dies keine Datensätze " -"zurückgeben " -"\n" +"zurückgeben \n" "SELECT ein_feld FROM meine_tabelle WHERE geom IS NULL;" #. Tag: programlisting @@ -332,7 +330,8 @@ msgstr "" #, 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" +"--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 "" "-- Um nur mitzuteilen, wie groß Ihre Geometrie ist, führen Sie eine Abfrage " @@ -355,27 +354,28 @@ msgid "" "MultiPolygon, and GeometryCollection geometries. 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 Z, M, and " -"ZM extensions). There are three data types currently supported. The standard" -" OGC geometry data type which uses a planar coordinate system for " +"ZM 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, with calculations on either a sphere or spheroid. 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 and for more details." +"analyzing raster data. Raster has its very own FAQ. Refer to and for more details." msgstr "" -"Sie können Punkte, Linien, Polygone, Objekte aus mehreren Punkten, Linien und " -"Polygonen, sowie Geometriesammlungen speichern. In PostGIS 2.0 und höher " +"Sie können Punkte, Linien, Polygone, Objekte aus mehreren Punkten, Linien " +"und Polygonen, sowie Geometriesammlungen speichern. In PostGIS 2.0 und höher " "können Sie auch TINs und Polyederoberflächen im Basistyp »geometry« " "speichern. Diese werden im »Well-known Text«-Open-GIS-Textformat (mit XYZ-, " "XYM- und XYZM-Erweiterungen) angegeben. Derzeit werden drei Datentypen " "unterstützt: Der Standard-OGC-Datentyp »geometry«, der für die Messung ein " "flaches Koordinatensystem verwendet, der Datentyp »geography«, der ein " "geodätisches Koordinatensystem benutzt (nicht OGC, aber Sie finden einen " -"ähnlichen Typ in Microsoft SQL Server 2008+). Nur WGS 84 long lat (SRID:4326) " -"wird vom Datentyp »geography« unterstützt. Das neuste Familienmitglied der " -"räumlichen PostGIS-Typenfamilie ist »raster« zum Speichern und Analysieren " -"von Rasterdaten. »raster« hat seine eigene FAQ. Weitere Einzelheiten finden " -"Sie unter und ." +"ähnlichen Typ in Microsoft SQL Server 2008+). Nur WGS 84 long lat " +"(SRID:4326) wird vom Datentyp »geography« unterstützt. Das neuste " +"Familienmitglied der räumlichen PostGIS-Typenfamilie ist »raster« zum " +"Speichern und Analysieren von Rasterdaten. »raster« hat seine eigene FAQ. " +"Weitere Einzelheiten finden Sie unter und ." #. Tag: para #: faq.xml:110 @@ -390,21 +390,20 @@ msgstr "" #, no-c-format msgid "" "Short Answer: geography is a newer data type that supports long range " -"distances measurements, but most computations on it are 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 spatial " -"reference system (SRID), 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 to see what is currently supported " -"and what is not." +"distances measurements, but most computations on it are 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 spatial reference system " +"(SRID), 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 to " +"see what is currently supported and what is not." msgstr "" "Kurze Antwort: »geography« ist ein neuer Datentyp, der große Bereiche von " "Distanzvermessungen unterstützt, die meisten Berechnungen damit sind derzeit " @@ -429,21 +428,21 @@ msgstr "" #: faq.xml:125 #, no-c-format msgid "" -"Long Answer: Refer to our more lengthy discussion in the and function type matrix." +"Long Answer: Refer to our more lengthy discussion in the and function type matrix." msgstr "" -"Lange Antwort: Eine ausführlichere Erörterung finden Sie unter und in der Funktionstypmatrix." +"Lange Antwort: Eine ausführlichere Erörterung finden Sie unter und in der Funktionstypmatrix." #. Tag: para #: faq.xml:133 #, 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 " +"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 "" "Ich habe tiefergehende Fragen über »geography«, wie beispielsweise welche " @@ -457,11 +456,11 @@ msgstr "" #, no-c-format msgid "" "Your questions are too deep and complex to be adequately answered in this " -"section. Please refer to our ." +"section. Please refer to our ." msgstr "" -"Ihre Fragen sind zu tiefgehend und komplex, um in diesem Abschnitt angemessen " -"beantwortet werden zu können. Bitte lesen Sie unsere ." #. Tag: para @@ -475,9 +474,9 @@ msgstr "Wie füge ich ein GIS-Objekt in die Datenbank ein?" #, 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 for details on storing geography." +"\"geography\" to hold your GIS data. Storing geography type data is a little " +"different than storing geometry. Refer to for details on storing geography." msgstr "" "Zuerst müssen Sie eine Tabelle mit einer Spalte des Typs »geometry« oder " "»geography« erstellen, die Ihre GIS-Daten bereithält. Das Speichern des " @@ -522,9 +521,9 @@ msgstr "" #: faq.xml:162 #, 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:" +"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 "" "Dann können Sie mittels eines SQL-INSERT-Befehls eine Geometrie in Ihre " "Tabelle einfügen. Das GIS-Objekt selbst ist mit dem Format »well-known-text« " @@ -552,11 +551,11 @@ msgstr "" #: faq.xml:168 #, no-c-format msgid "" -"For more information about other GIS objects, see the object reference." +"For more information about other GIS objects, see the object reference." msgstr "" -"Mehr Informationen über weitere GIS-Objekte finden Sie in der Objektreferenz." +"Mehr Informationen über weitere GIS-Objekte finden Sie in der Objektreferenz." #. Tag: para #: faq.xml:171 @@ -610,10 +609,9 @@ msgstr "" #: faq.xml:190 #, 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." +"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 "" "Es gibt bei räumlichen Abfragen zwei Aspekte, die Sie beim Erstellen Ihrer " "Abfrage im Hinterkopf behalten sollten: Es gibt einen räumlichen Index, von " @@ -625,24 +623,24 @@ msgstr "" #, no-c-format msgid "" "In general, you will want to use the \"intersects operator\" (&&) " -"which tests whether the bounding boxes of features intersect. The reason the" -" && operator is useful is because if a spatial index is available to" -" speed up the test, the && operator will make use of this. This can " +"which tests whether the bounding boxes of features intersect. The reason the " +"&& operator is useful is because if a spatial index is available to " +"speed up the test, the && operator will make use of this. This can " "make queries much much faster." msgstr "" -"Im Allgemeinen werden Sie den »Überschneidungsoperator« (&&) benutzen " -"wollen, der prüft, ob sich die Hüllquader der Objekte überschneiden. Der " -"Hauptnutzen des &&-Operators besteht darin, dass er, falls ein " -"räumlicher Index zum Beschleunigen des Tests verfügbar ist, Gebrauch davon " -"macht. Dies kann Abfragen sehr stark beschleunigen." +"Im Allgemeinen werden Sie den »Überschneidungsoperator« (&&) " +"benutzen wollen, der prüft, ob sich die Hüllquader der Objekte " +"überschneiden. Der Hauptnutzen des &&-Operators besteht darin, dass " +"er, falls ein räumlicher Index zum Beschleunigen des Tests verfügbar ist, " +"Gebrauch davon macht. Dies kann Abfragen sehr stark beschleunigen." #. Tag: para #: faq.xml:202 #, 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 " +"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 might meet the " "condition of interest. The spatial functions are then use to test the " @@ -681,13 +679,12 @@ msgstr "Wie kann ich räumliche Abfragen auf großen Tabellen beschleunigen?" #, no-c-format msgid "" "Fast queries on large tables is the raison d'etre of " -"spatial databases (along with transaction support) so having a good index is" -" important." +"spatial databases (along with transaction support) so having a good index is " +"important." msgstr "" -"Schnelle Abfragen großer Tabellen sind die " -"Daseinsberechtigung räumlicher Datenbanken (neben der " -"Unterstützung von Transaktionen). Daher ist es wichtig, über einen guten " -"Index zu verfügen." +"Schnelle Abfragen großer Tabellen sind die Daseinsberechtigung räumlicher Datenbanken (neben der Unterstützung von " +"Transaktionen). Daher ist es wichtig, über einen guten Index zu verfügen." #. Tag: para #: faq.xml:224 @@ -696,8 +693,8 @@ msgid "" "To build a spatial index on a table with a geometry " "column, use the \"CREATE INDEX\" function as follows:" msgstr "" -"Um einen räumlichen Index für eine Tablle mit einer geometry<" -"/varname>-Spalte zu erstellen, benutzen Sie die Funktion »CREATE INDEX« wie " +"Um einen räumlichen Index für eine Tablle mit einer geometry-Spalte zu erstellen, benutzen Sie die Funktion »CREATE INDEX« wie " "folgt:" #. Tag: programlisting @@ -712,8 +709,8 @@ msgstr "" #: faq.xml:230 #, no-c-format msgid "" -"The \"USING GIST\" option tells the server to use a GiST (Generalized Search" -" Tree) index." +"The \"USING GIST\" option tells the server to use a GiST (Generalized Search " +"Tree) index." msgstr "" "Die Option »USING GIST« teilt dem Server mit, dass er einen GiST-Index " "(Generalized Search Tree/Verallgemeinerter Suchbaum) verwenden soll." @@ -737,21 +734,20 @@ msgid "" "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 "" -"Sie sollten außerdem sicherstellen, dass das " -"PostgreSQL-Abfrageplanungsprogramm ausreichende Informationen über Ihren " -"Index hat, um vernünftige Entscheidungen treffen zu können, wann er benutzt " -"wird. Zu diesem Zweck müssen Sie für Ihre Geometrietabellen »Statistiken " -"erstellen«." +"Sie sollten außerdem sicherstellen, dass das PostgreSQL-" +"Abfrageplanungsprogramm ausreichende Informationen über Ihren Index hat, um " +"vernünftige Entscheidungen treffen zu können, wann er benutzt wird. Zu " +"diesem Zweck müssen Sie für Ihre Geometrietabellen »Statistiken erstellen«." #. Tag: para #: faq.xml:244 #, no-c-format msgid "" -"For PostgreSQL 8.0.x and greater, just run the VACUUM " -"ANALYZE command." +"For PostgreSQL 8.0.x and greater, just run the VACUUM ANALYZE command." msgstr "" -"Unter PostgeSQL 8.0.x und neuer führen Sie einfach den Befehl VACUUM " -"ANALYZE aus." +"Unter PostgeSQL 8.0.x und neuer führen Sie einfach den Befehl " +"VACUUM ANALYZE aus." #. Tag: para #: faq.xml:247 @@ -802,13 +798,13 @@ msgstr "" #: faq.xml:271 #, 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 " +"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 "" "R-Baum-Indizes können in PostgreSQL nicht mit Objekten umgehen, die größer " -"als 8k sind. GiST-Indizes können dies mittels des »verlustbehafteten« Tricks, " -"das Objekt selbst durch seinen Hüllquader zu ersetzen." +"als 8k sind. GiST-Indizes können dies mittels des »verlustbehafteten« " +"Tricks, das Objekt selbst durch seinen Hüllquader zu ersetzen." #. Tag: para #: faq.xml:278 @@ -825,8 +821,8 @@ msgstr "" #: faq.xml:288 #, no-c-format msgid "" -"Why should I use the AddGeometryColumn() function and all" -" the other OpenGIS stuff?" +"Why should I use the AddGeometryColumn() function and all " +"the other OpenGIS stuff?" msgstr "" "Warum soll ich die Funktion AddGeometryColumn() und all " "das andere OpenGIS-Zeug verwenden?" @@ -835,9 +831,9 @@ msgstr "" #: faq.xml:293 #, 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 " +"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 not be filled in " "properly. However, this will cause most applications based on PostGIS to " "fail, and it is generally suggested that you do use " @@ -847,9 +843,9 @@ msgstr "" "nicht. Erstellen Sie einfach Ihre Tabellen in älteren Versionen, indem Sie " "Ihre »geometry«-Spalten im CREATE-Befehl erstellen. Alle Ihre Geometrien " "werden SRIDs von -1 haben und die OpenGIS-Metadatentabellen werden " -"nicht ordentlich gefüllt. Dies wird jedoch die meisten" -"Anwendungen, die auf PostGIS basieren, zum Abstürzen bringen und es wird " -"generell empfohlen, dass Sie zum Erstellen von »geometry«-Tabellen " +"nicht ordentlich gefüllt. Dies wird jedoch die " +"meistenAnwendungen, die auf PostGIS basieren, zum Abstürzen bringen und es " +"wird generell empfohlen, dass Sie zum Erstellen von »geometry«-Tabellen " "AddGeometryColumn() verwenden." #. Tag: para @@ -861,10 +857,10 @@ msgid "" "use the SRID of the geometry column to do on-the-fly reprojection of " "features into the correct map projection." msgstr "" -"MapServer ist eine dieser Anwendungen, die Gebrauch von " -"geometry_columns-Metadaten machen. Insbesondere kann MapServer die " -"SRID der »geometry«-Spalte nutzen, um direkt eine Rückprojektion von Objekten " -"in die korrekte Abbildungsprojektion vorzunehmen." +"MapServer ist eine dieser Anwendungen, die Gebrauch von " +"geometry_columns-Metadaten machen. Insbesondere kann " +"MapServer die SRID der »geometry«-Spalte nutzen, um direkt eine " +"Rückprojektion von Objekten in die korrekte Abbildungsprojektion vorzunehmen." #. Tag: para #: faq.xml:311 @@ -880,8 +876,8 @@ msgstr "" #, 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 " +"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 "" "Um die Datenbank möglichst effizient zu nutzen, ist es am besten " @@ -895,13 +891,13 @@ msgstr "" #, no-c-format msgid "" "The ST_DWithin(geometry, geometry, distance) 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 " +"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 "" "Die Funktion ST_DWithin(geometry, geometry, distance) ist " -"eine praktische Art, eine Entfernungssuche per Index durchzuführen. Dazu wird " -"ein Suchrechteck erstellt, das groß genug ist, um den Entfernungsradius " +"eine praktische Art, eine Entfernungssuche per Index durchzuführen. Dazu " +"wird ein Suchrechteck erstellt, das groß genug ist, um den Entfernungsradius " "einzuschließen. Dann wird in der indizitierten Untermenge der Ergebnisse die " "genaue Entfernung gesucht." @@ -912,8 +908,8 @@ msgid "" "For example, to find all objects with 100 meters of POINT(1000 1000) the " "following query would work well:" msgstr "" -"Um zum Beispiel alle Objekte mit 100 Metern Entfernung zu POINT(1000 1000) zu " -"finden, wäre die folgende Abfrage gut geeignet:" +"Um zum Beispiel alle Objekte mit 100 Metern Entfernung zu POINT(1000 1000) " +"zu finden, wäre die folgende Abfrage gut geeignet:" #. Tag: programlisting #: faq.xml:330 @@ -947,10 +943,11 @@ msgstr "" "Um eine Rückprojektion durchzuführen, müssen sowohl die Quell- als auch die " "Zielkoordinatensysteme in einer SPATIAL_REF_SYS-Tabelle definiert sein und " "und die SRIDs der Geometrien, die rückprojiziert werden, müssen bereits " -"gesetzt sein. Sobald dies erledigt ist, ist die Rückprojektion so einfach wie " -"Bezug auf die gewünschte Ziel-SRID zu nehmen. Nachfolgend wird eine Geometrie " -"auf »NAD 83 long lat« projiziert. Das Folgende funktioniert nur, falls die " -"SRID der Geometrie nicht -1 ist (keine undefinierte räumliche Referenz)." +"gesetzt sein. Sobald dies erledigt ist, ist die Rückprojektion so einfach " +"wie Bezug auf die gewünschte Ziel-SRID zu nehmen. Nachfolgend wird eine " +"Geometrie auf »NAD 83 long lat« projiziert. Das Folgende funktioniert nur, " +"falls die SRID der Geometrie nicht -1 ist (keine undefinierte räumliche " +"Referenz)." #. Tag: programlisting #: faq.xml:348 @@ -962,8 +959,8 @@ msgstr "SELECT ST_Transform(die_geometrie,4269) FROM geometrietabelle;" #: faq.xml:354 #, no-c-format msgid "" -"I did an ST_AsEWKT and ST_AsText on my rather large geometry and it returned" -" blank field. What gives?" +"I did an ST_AsEWKT and ST_AsText on my rather large geometry and it returned " +"blank field. What gives?" msgstr "" "Ich führte ein ST_AsEWKT und ST_AsText auf meiner eher großen Geometrie aus " "und erhielt ein leeres Feld zurück. Was ist passiert?" @@ -977,16 +974,17 @@ msgid "" "Use PSQL if you really need to see it or output it in WKT." msgstr "" "Sie verwenden vermutlich PgAdmin oder irgendein anderes Werkzeug, das keine " -"großen Texte ausgibt. Falls Ihre Geometrie groß genug ist, wird sie in diesen " -"Werkzeugen leer erscheinen. Falls Sie sie wirklich sehen oder in WKT ausgeben " -"möchten, verwenden Sie PSQL." +"großen Texte ausgibt. Falls Ihre Geometrie groß genug ist, wird sie in " +"diesen Werkzeugen leer erscheinen. Falls Sie sie wirklich sehen oder in WKT " +"ausgeben möchten, verwenden Sie PSQL." #. Tag: programlisting #: faq.xml:361 #, no-c-format msgid "" "--To check number of geometries are really blank\n" -" SELECT count(gid) FROM geotable WHERE the_geom IS NULL;" +" SELECT count(gid) FROM geotable WHERE " +"the_geom IS NULL;" msgstr "" "--zum Prüfen, ob die Anzahl der Geometrien wirklich leer ist\n" " SELECT count(gid) FROM geotable WHERE " @@ -996,8 +994,8 @@ msgstr "" #: faq.xml:367 #, 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?" +"When I do an ST_Intersects, it says my two geometries don't intersect when I " +"KNOW THEY DO. What gives?" msgstr "" "Wenn ich ein ST_Intersects ausführe, sagt es, dass sich meine beiden " "Geometrien nicht überschneiden, obwohl ICH WEIẞ, DASS SIE DIES TUN. Was ist " @@ -1021,8 +1019,8 @@ msgstr "" #: faq.xml:379 #, 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 " +"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 "" "Ich veröffentliche Software, die PostGIS verwendet. Bedeutet das, dass meine " @@ -1035,8 +1033,8 @@ msgstr "" 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." +"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 "" "Höchstwahrscheinlich nicht. Oracle-Datenbanken laufen zum Beispiel unter " "Linux. Linux steht unter der GPL, Oracles Datenbank nicht. Muss Oracles " @@ -1049,17 +1047,17 @@ msgstr "" #, 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 " +"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 publish your source code, " "only that you share it with people you give binaries to." msgstr "" "Die einzige Ausnahme wäre, wenn Sie Veränderungen am PostGIS-Quellcode " "vorgenommen hätten und Ihre veränderte Version von PostGIS verteilen würden. " -"In diesem Fall müssten Sie den Code Ihres veränderten PostGIS freigeben (aber " -"nicht den Code von Anwendungen, die darauf laufen). Sogar in diesem " +"In diesem Fall müssten Sie den Code Ihres veränderten PostGIS freigeben " +"(aber nicht den Code von Anwendungen, die darauf laufen). Sogar in diesem " "begrenzten Fall müssten Sie nur den Quellcode an Leute verteilen, denen Sie " "Binärcode weitergegeben haben. Die GPL verlangt nicht, dass Sie Ihren " "Quellcode veröffentlichen, nur dass Sie ihn mit Leuten " diff --git a/doc/po/de_DE/faq_raster.xml.po b/doc/po/de_DE/faq_raster.xml.po index 610ec09ef..56d5c6383 100644 --- a/doc/po/de_DE/faq_raster.xml.po +++ b/doc/po/de_DE/faq_raster.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:23+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -40,8 +41,8 @@ msgid "" "disable all GDAL drivers and out of db rasters. The release notes are at " "PostGIS 2.0.6, 2.1.3 " "security release. In order to reenable specific drivers or all " -"drivers and reenable out of database support, refer to ." +"drivers and reenable out of database support, refer to ." msgstr "" #. Tag: para @@ -54,9 +55,8 @@ msgstr "" #: faq_raster.xml:26 #, no-c-format msgid "" -"Refer to the PostGIS Raster home " -"page." +"Refer to the PostGIS Raster home page." msgstr "" #. Tag: para @@ -71,31 +71,29 @@ msgstr "" #: faq_raster.xml:36 #, no-c-format msgid "" -"There is a full length beginner tutorial Intersecting" -" vector buffers with large raster coverage using PostGIS Raster. " -"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 Jorge's PostGIS Raster / Oracle GeoRaster Series." -" There is a whole chapter (more than 35 pages of content) dedicated to " -"PostGIS Raster with free code and data downloads at PostGIS in Action - Raster " -"chapter. You can buy PostGIS in Action " -"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." +"There is a full length beginner tutorial Intersecting vector buffers with large " +"raster coverage using PostGIS Raster. 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 Jorge's PostGIS " +"Raster / Oracle GeoRaster Series. There is a whole chapter (more " +"than 35 pages of content) dedicated to PostGIS Raster with free code and " +"data downloads at PostGIS in " +"Action - Raster chapter. You can buy PostGIS in Action 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:43 #, no-c-format msgid "" -"Here is a review from a PostGIS Raster user PostGIS raster " -"applied to land classification urban forestry" +"Here is a review from a PostGIS Raster user PostGIS raster applied to " +"land classification urban forestry" msgstr "" #. Tag: para @@ -110,8 +108,8 @@ msgstr "" 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 " +"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 "" @@ -129,12 +127,11 @@ msgstr "" #: faq_raster.xml:57 #, no-c-format msgid "" -"If you are on windows, you can compile yourself, or use the pre-compiled PostGIS Raster " -"windows binaries. If you are on Mac OSX Leopard or Snow Leopard, " -"there are binaries available at Kyng Chaos Mac OSX " -"PostgreSQL/GIS binaries." +"If you are on windows, you can compile yourself, or use the pre-compiled PostGIS Raster windows " +"binaries. If you are on Mac OSX Leopard or Snow Leopard, there are " +"binaries available at Kyng Chaos Mac OSX PostgreSQL/GIS binaries." msgstr "" #. Tag: para @@ -152,18 +149,18 @@ msgstr "" 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 Installing" -" PostGIS Raster from source (in prior versions of PostGIS)" +"refer to Installing PostGIS " +"Raster from source (in prior versions of PostGIS)" msgstr "" #. Tag: para #: faq_raster.xml:70 #, 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" +"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 @@ -171,8 +168,8 @@ msgstr "" #, 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." +"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 @@ -180,8 +177,8 @@ msgstr "" #, 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." +"in your database. Make sure to install PostGIS first in your database before " +"trying to install the raster support." msgstr "" #. Tag: para @@ -194,13 +191,12 @@ msgstr "" #: faq_raster.xml:88 #, no-c-format msgid "" -"The latest version of PostGIS comes packaged with a " -"raster2pgsql raster loader executable capable of loading " -"many kinds of rasters and also generating lower resolution overviews without" -" any additional software. Please refer to for more details. Pre-2.0 versions came with " -"a raster2pgsql.py that required python with numpy and " -"GDAL. This is no longer needed." +"The latest version of PostGIS comes packaged with a raster2pgsql raster loader executable capable of loading many kinds of rasters " +"and also generating lower resolution overviews without any additional " +"software. Please refer to for more " +"details. Pre-2.0 versions came with a raster2pgsql.py " +"that required python with numpy and GDAL. This is no longer needed." msgstr "" #. Tag: para @@ -214,16 +210,16 @@ msgstr "" #, no-c-format msgid "" "Any that your GDAL library supports. GDAL supported formats are documented " -"GDAL File " -"Formats." +"GDAL File Formats." msgstr "" #. Tag: para #: faq_raster.xml:99 #, 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" +"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 @@ -248,8 +244,8 @@ msgstr "" #: faq_raster.xml:111 #, 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." +"GDAL 1.7+ has a PostGIS raster driver, but is only compiled in if you choose " +"to compile with PostgreSQL support." msgstr "" #. Tag: para @@ -266,9 +262,9 @@ msgstr "" msgid "" "If you are compiling from source, you need to include in your configure " "--with-pg=path/to/pg_config to enable the " -"driver. Refer to GDAL Build Hints " -"for tips on building GDAL against in various OS platforms." +"driver. Refer to GDAL Build Hints for tips on building GDAL against in various OS " +"platforms." msgstr "" #. Tag: para @@ -313,8 +309,8 @@ msgstr "" 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." +"band types and 32 bit unsigned ints will not translate easily to JPG or some " +"others." msgstr "" #. Tag: para @@ -363,9 +359,9 @@ msgstr "" #: faq_raster.xml:138 #, no-c-format msgid "" -"To see more examples and syntax refer to Reading" -" Raster Data of PostGIS Raster section" +"To see more examples and syntax refer to Reading Raster Data of PostGIS Raster section" msgstr "" #. Tag: para @@ -380,10 +376,9 @@ msgstr "" #: faq_raster.xml:145 #, no-c-format msgid "" -"Yes. Check out the page GDAL " -"Binaries page. Any compiled with PostgreSQL support should have " -"PostGIS Raster in them." +"Yes. Check out the page GDAL Binaries page. Any compiled with " +"PostgreSQL support should have PostGIS Raster in them." msgstr "" #. Tag: para @@ -393,10 +388,10 @@ 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. http://vbkto.dyndns.org/sdk/. " -"Also available are VS project files." +"and MapServer executables and PostGIS Raster driver built-in. Just click the " +"SDK bat and run your commands from there. http://vbkto.dyndns.org/sdk/. Also available are VS " +"project files." msgstr "" #. Tag: para @@ -428,10 +423,9 @@ msgstr "" 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 http://vbkto.dyndns.org/sdk/ " -"are a good choice if you don't want the hassle of having to setup to compile" -" your own." +"binaries http://vbkto.dyndns.org/" +"sdk/ are a good choice if you don't want the hassle of having to " +"setup to compile your own." msgstr "" #. Tag: para @@ -444,17 +438,17 @@ msgstr "" #: faq_raster.xml:174 #, 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." +"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:176 #, no-c-format msgid "" -"You can much like you can with any other raster. Refer to MapServer Raster processing " +"You can much like you can with any other raster. Refer to MapServer Raster processing " "options for list of various processing functions you can use with " "MapServer raster layers." msgstr "" @@ -493,7 +487,8 @@ msgid "" " NAME coolwktraster\n" " TYPE raster\n" " STATUS ON\n" -" DATA \"PG:host=localhost port=5432 dbname='somedb' user='someuser' password='whatever' \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" @@ -526,8 +521,10 @@ msgid "" " 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" +" 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" @@ -552,10 +549,9 @@ msgstr "" #: faq_raster.xml:199 #, no-c-format msgid "" -"Refer to the PostGIS" -" Raster roadmap page for details of what you can expect in the " -"future." +"Refer to the PostGIS Raster roadmap page for details of what " +"you can expect in the future." msgstr "" #. Tag: para @@ -573,10 +569,10 @@ 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." +"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 @@ -598,8 +594,8 @@ msgstr "" #: faq_raster.xml:214 #, no-c-format msgid "" -"Cast the textual geometry representation to a geometry by changing your code" -" to this:" +"Cast the textual geometry representation to a geometry by changing your code " +"to this:" msgstr "" #. Tag: programlisting @@ -624,8 +620,8 @@ msgstr "" #, no-c-format msgid "" "For a more extensive discussion on this topic, check out Jorge Arévalo " -"Oracle GeoRaster and PostGIS Raster: First impressions " +"Oracle GeoRaster and PostGIS Raster: First impressions " msgstr "" #. Tag: para @@ -641,8 +637,8 @@ msgstr "" #, 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)" +"raster coverage covering large extents. See the possible raster arrangements " +"in the documentation)" msgstr "" #. Tag: para @@ -660,8 +656,8 @@ 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." +"With PostGIS Raster you can store a similar raster arrangement into a unique " +"table." msgstr "" #. Tag: para @@ -681,8 +677,8 @@ msgstr "" #: faq_raster.xml:242 #, no-c-format msgid "" -"raster2pgsql load of large file fails with String of N bytes is too long for" -" encoding conversion?" +"raster2pgsql load of large file fails with String of N bytes is too long for " +"encoding conversion?" msgstr "" #. Tag: para @@ -700,9 +696,9 @@ msgstr "" #: faq_raster.xml:248 #, no-c-format msgid "" -"This generally happens if for example you have your database in UTF8, but to" -" support windows apps, you have the client encoding set to " -"WIN1252." +"This generally happens if for example you have your database in UTF8, but to " +"support windows apps, you have the client encoding set to WIN1252." msgstr "" #. Tag: para @@ -736,6 +732,6 @@ msgstr "" #: faq_raster.xml:253 #, no-c-format msgid "" -"Gory details of this issue are detailed in http://trac.osgeo.org/postgis/ticket/2209" +"Gory details of this issue are detailed in http://trac.osgeo.org/postgis/ticket/2209" msgstr "" diff --git a/doc/po/de_DE/installation.xml.po b/doc/po/de_DE/installation.xml.po index 65870cbdc..a5201f0e7 100644 --- a/doc/po/de_DE/installation.xml.po +++ b/doc/po/de_DE/installation.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:23+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -90,8 +91,8 @@ msgstr "" #: installation.xml:18 #, no-c-format msgid "" -"Please refer to for more" -" details about querying installed/available extensions and upgrading " +"Please refer to for more " +"details about querying installed/available extensions and upgrading " "extensions, or switching from a non-extension install to an extension " "install." msgstr "" @@ -109,8 +110,8 @@ msgstr "" #: installation.xml:21 #, no-c-format msgid "" -"All the .sql files once installed will be installed in " -"share/contrib/postgis-&last_minor_version; folder of your PostgreSQL install" +"All the .sql files once installed will be installed in share/contrib/postgis-" +"&last_minor_version; folder of your PostgreSQL install" msgstr "" #. Tag: programlisting @@ -171,8 +172,8 @@ msgstr "" #: installation.xml:37 #, no-c-format msgid "" -"In order to enable all GDAL drivers available in your GDAL install, set this" -" environment variable as follows" +"In order to enable all GDAL drivers available in your GDAL install, set this " +"environment variable as follows" msgstr "" #. Tag: programlisting @@ -207,9 +208,9 @@ msgstr "" msgid "" "Setting environment variables varies depending on OS. For PostgreSQL " "installed on Ubuntu or Debian via apt-postgresql, the preferred way is to " -"edit " -"/etc/postgresql/9.3/main/environment" -" where 9.3 refers to version of PostgreSQL and main refers to the cluster." +"edit /etc/postgresql/9.3/" +"main/environment where 9.3 refers to " +"version of PostgreSQL and main refers to the cluster." msgstr "" #. Tag: para @@ -217,9 +218,9 @@ msgstr "" #, no-c-format msgid "" "On windows, if you are running as a service, you can set via System " -"variables which for Windows 7 you can get to by right-clicking on " -"Computer->Properties Advanced System Settings or in explorer navigating " -"to Control Panel\\All Control Panel Items\\System. Then " +"variables which for Windows 7 you can get to by right-clicking on Computer-" +">Properties Advanced System Settings or in explorer navigating to " +"Control Panel\\All Control Panel Items\\System. Then " "clicking Advanced System Settings ->Advanced->Environment " "Variables and adding new system variables." msgstr "" @@ -256,8 +257,8 @@ msgstr "" msgid "" "PostgreSQL &min_postgres_version; or higher. A complete installation of " "PostgreSQL (including server headers) is required. PostgreSQL is available " -"from http://www.postgresql.org " -" ." +"from http://www.postgresql.org ." msgstr "" #. Tag: para @@ -265,8 +266,9 @@ msgstr "" #, no-c-format msgid "" "For a full PostgreSQL / PostGIS support matrix and PostGIS/GEOS support " -"matrix refer to http://trac.osgeo.org/postgis/wiki/UsersWikiPostgreSQLPostGIS" +"matrix refer to http://trac.osgeo.org/postgis/wiki/" +"UsersWikiPostgreSQLPostGIS" msgstr "" #. Tag: para @@ -282,11 +284,11 @@ msgstr "" #: installation.xml:88 #, no-c-format msgid "" -"GNU Make (gmake or make). For many" -" systems, GNU make is the default version of make. " -"Check the version by invoking make -v. Other versions " -"of make may not process the PostGIS " -"Makefile properly." +"GNU Make (gmake or make). For many " +"systems, GNU make is the default version of make. Check " +"the version by invoking make -v. Other versions of " +"make may not process the PostGIS Makefile properly." msgstr "" #. Tag: para @@ -305,11 +307,11 @@ msgstr "" msgid "" "GEOS geometry library, version 3.3 or greater, but GEOS 3.5+ is recommended " "to take full advantage of all the new functions and features. Without GEOS " -"3.5, you will be missing some major enhancements such as and . GEOS is " -"available for download from " -"http://trac.osgeo.org/geos/ and 3.4+ is backward-compatible with " -"older versions so fairly safe to upgrade." +"3.5, you will be missing some major enhancements such as and . GEOS is available " +"for download from http://trac." +"osgeo.org/geos/ and 3.4+ is backward-compatible with older versions " +"so fairly safe to upgrade." msgstr "" #. Tag: para @@ -318,8 +320,8 @@ msgstr "" msgid "" "LibXML2, version 2.5.x or higher. LibXML2 is currently used in some imports " "functions (ST_GeomFromGML and ST_GeomFromKML). LibXML2 is available for " -"download from http://xmlsoft.org/downloads.html." +"download from http://" +"xmlsoft.org/downloads.html." msgstr "" #. Tag: para @@ -328,8 +330,8 @@ msgstr "" msgid "" "JSON-C, version 0.9 or higher. JSON-C is currently used to import GeoJSON " "via the function ST_GeomFromGeoJson. JSON-C is available for download from " -"https://github.com/json-c/json-c/releases/." +"https://github.com/" +"json-c/json-c/releases/." msgstr "" #. Tag: para @@ -337,11 +339,11 @@ msgstr "" #, no-c-format msgid "" "GDAL, version 1.8 or higher (1.9 or higher is strongly recommended since " -"some things will not work well or behavior differently with lower versions)." -" This is required for raster support and to be able to install with " +"some things will not work well or behavior differently with lower versions). " +"This is required for raster support and to be able to install with " "CREATE EXTENSION postgis so highly recommended for those " -"running 9.1+. http://trac.osgeo.org/gdal/wiki/DownloadSource." +"running 9.1+. http://trac.osgeo.org/gdal/wiki/DownloadSource." msgstr "" #. Tag: emphasis @@ -373,8 +375,8 @@ msgstr "" #: installation.xml:154 #, no-c-format msgid "" -"GTK (requires GTK+2.0, 2.8+) to compile the shp2pgsql-gui shape file loader." -" http://www.gtk.org/ ." +"GTK (requires GTK+2.0, 2.8+) to compile the shp2pgsql-gui shape file loader. " +" http://www.gtk.org/ ." msgstr "" #. Tag: para @@ -382,30 +384,29 @@ msgstr "" #, no-c-format msgid "" "SFCGAL, version 1.1 (or higher) could be used to provide additional 2D and " -"3D advanced analysis functions to PostGIS cf . And also allow to use SFCGAL rather than " -"GEOS for some 2D functions provided by both backends (like ST_Intersection " -"or ST_Area, for instance). A PostgreSQL configuration variable " -"postgis.backend allow end user to control which backend he want" -" to use if SFCGAL is installed (GEOS by default). Nota: SFCGAL 1.2 require " -"at least CGAL 4.3 and Boost 1.54 (cf: http://oslandia.github.io/SFCGAL/installation.html)" -" https://github.com/Oslandia/SFCGAL." +"3D advanced analysis functions to PostGIS cf . And also allow to use SFCGAL rather than GEOS for some 2D functions " +"provided by both backends (like ST_Intersection or ST_Area, for instance). A " +"PostgreSQL configuration variable postgis.backend allow end " +"user to control which backend he want to use if SFCGAL is installed (GEOS by " +"default). Nota: SFCGAL 1.2 require at least CGAL 4.3 and Boost 1.54 (cf: " +"http://" +"oslandia.github.io/SFCGAL/installation.html) https://github.com/Oslandia/SFCGAL." msgstr "" #. Tag: para #: installation.xml:172 #, no-c-format msgid "" -"In order to build the you will also" -" need PCRE http://www.pcre.org " -"(which generally is already installed on nix systems). " -"Regex::Assemble perl CPAN package is only needed if you want to" -" rebuild the data encoded in parseaddress-stcities.h. " -" will automatically be built if it " -"detects a PCRE library, or you pass in a valid --with-pcre-" -"dir=/path/to/pcre during configure." +"In order to build the you will also " +"need PCRE http://www.pcre.org " +"(which generally is already installed on nix systems). Regex::" +"Assemble perl CPAN package is only needed if you want to rebuild the " +"data encoded in parseaddress-stcities.h. will automatically be built if it detects a PCRE " +"library, or you pass in a valid --with-pcre-dir=/path/to/pcre during configure." msgstr "" #. Tag: para @@ -413,8 +414,8 @@ msgstr "" #, no-c-format msgid "" "CUnit (CUnit). This is needed for regression testing. " -"http://cunit.sourceforge.net/" +"http://cunit.sourceforge.net/" msgstr "" #. Tag: para @@ -422,8 +423,8 @@ msgstr "" #, no-c-format msgid "" "DocBook (xsltproc) is required for building the " -"documentation. Docbook is available from http://www.docbook.org/ ." +"documentation. Docbook is available from http://www.docbook.org/ ." msgstr "" #. Tag: para @@ -431,9 +432,8 @@ msgstr "" #, no-c-format msgid "" "DBLatex (dblatex) is required for building the " -"documentation in PDF format. DBLatex is available from http://dblatex.sourceforge.net/ " -" ." +"documentation in PDF format. DBLatex is available from http://dblatex.sourceforge.net/ ." msgstr "" #. Tag: para @@ -441,8 +441,8 @@ msgstr "" #, no-c-format msgid "" "ImageMagick (convert) is required to generate the " -"images used in the documentation. ImageMagick is available from http://www.imagemagick.org/ ." +"images used in the documentation. ImageMagick is available from http://www.imagemagick.org/ ." msgstr "" #. Tag: title @@ -455,8 +455,8 @@ msgstr "" #: installation.xml:222 #, no-c-format msgid "" -"Retrieve the PostGIS source archive from the downloads website &postgis_download_url; " +"Retrieve the PostGIS source archive from the downloads website &postgis_download_url; " msgstr "" #. Tag: programlisting @@ -471,36 +471,33 @@ msgstr "" #: installation.xml:231 #, no-c-format msgid "" -"This will create a directory called " -"postgis-&last_release_version; in the current working " -"directory." +"This will create a directory called postgis-&last_release_version; in the current working directory." msgstr "" #. Tag: para #: installation.xml:237 #, no-c-format msgid "" -"Alternatively, checkout the source from the svn repository " -"http://svn.osgeo.org/postgis/trunk/ ." +"Alternatively, checkout the source from the svn repository http://svn.osgeo.org/postgis/trunk/ ." msgstr "" #. Tag: programlisting #: installation.xml:249 #, no-c-format msgid "" -"svn checkout http://svn.osgeo.org/postgis/trunk/ " -"postgis-&last_release_version;" +"svn checkout http://svn.osgeo.org/postgis/trunk/ postgis-" +"&last_release_version;" msgstr "" #. Tag: para #: installation.xml:251 #, no-c-format msgid "" -"Change into the newly created " -"postgis-&last_release_version; directory to continue the " -"installation." +"Change into the newly created postgis-&last_release_version; directory to continue the installation." msgstr "" #. Tag: title @@ -522,22 +519,19 @@ msgstr "" #: installation.xml:267 #, no-c-format msgid "" -"This section includes general compilation instructions, if you are compiling" -" for Windows etc or another OS, you may find additional more detailed help " -"at PostGIS User " -"contributed compile guides and PostGIS Dev " -"Wiki." +"This section includes general compilation instructions, if you are compiling " +"for Windows etc or another OS, you may find additional more detailed help at " +"PostGIS " +"User contributed compile guides and PostGIS Dev Wiki." msgstr "" #. Tag: para #: installation.xml:269 #, no-c-format msgid "" -"Pre-Built Packages for various OS are listed in PostGIS Pre-" -"built Packages" +"Pre-Built Packages for various OS are listed in PostGIS Pre-built Packages" msgstr "" #. Tag: para @@ -546,11 +540,11 @@ msgstr "" msgid "" "If you are a windows user, you can get stable builds via Stackbuilder or " "PostGIS Windows " -"download site We also have very " -"bleeding-edge windows experimental builds that are built usually " -"once or twice a week or whenever anything exciting happens. You can use " -"these to experiment with the in progress releases of PostGIS" +"download site We also have very bleeding-edge windows experimental " +"builds that are built usually once or twice a week or whenever " +"anything exciting happens. You can use these to experiment with the in " +"progress releases of PostGIS" msgstr "" #. Tag: para @@ -568,9 +562,9 @@ msgstr "" #: installation.xml:283 #, no-c-format msgid "" -"Refer to the PostgreSQL installation guides if you haven't already installed" -" PostgreSQL. " -"http://www.postgresql.org ." +"Refer to the PostgreSQL installation guides if you haven't already installed " +"PostgreSQL. http://www.postgresql." +"org ." msgstr "" #. Tag: para @@ -593,17 +587,16 @@ msgstr "" msgid "" "This is a workaround for bogus C++ exceptions interaction with older " "development tools. If you experience weird problems (backend unexpectedly " -"closed or similar things) try this trick. This will require recompiling your" -" PostgreSQL from scratch, of course." +"closed or similar things) try this trick. This will require recompiling your " +"PostgreSQL from scratch, of course." msgstr "" #. Tag: para #: installation.xml:308 #, no-c-format msgid "" -"The following steps outline the configuration and compilation of the PostGIS" -" source. They are written for Linux users and will not work on Windows or " -"Mac." +"The following steps outline the configuration and compilation of the PostGIS " +"source. They are written for Linux users and will not work on Windows or Mac." msgstr "" #. Tag: title @@ -616,8 +609,8 @@ msgstr "" #: installation.xml:317 #, no-c-format msgid "" -"As with most linux installations, the first step is to generate the Makefile" -" that will be used to build the source code. This is done by running the " +"As with most linux installations, the first step is to generate the Makefile " +"that will be used to build the source code. This is done by running the " "shell script" msgstr "" @@ -629,8 +622,7 @@ msgid "" "locate the required components and libraries needed to build the PostGIS " "source code on your system. Although this is the most common usage of " "./configure, the script accepts several parameters for " -"those who have the required libraries and programs in non-standard " -"locations." +"those who have the required libraries and programs in non-standard locations." msgstr "" #. Tag: para @@ -638,16 +630,16 @@ msgstr "" #, no-c-format msgid "" "The following list shows only the most commonly used parameters. For a " -"complete list, use the --help or " -"--help=short parameters." +"complete list, use the --help or --help=short parameters." msgstr "" #. Tag: para #: installation.xml:346 #, no-c-format msgid "" -"This is the location the PostGIS libraries and SQL scripts will be installed" -" to. By default, this location is the same as the detected PostgreSQL " +"This is the location the PostGIS libraries and SQL scripts will be installed " +"to. By default, this location is the same as the detected PostgreSQL " "installation." msgstr "" @@ -656,9 +648,9 @@ msgstr "" #, no-c-format msgid "" "This parameter is currently broken, as the package will only install into " -"the PostgreSQL installation directory. Visit " -"http://trac.osgeo.org/postgis/ticket/635 to track this bug." +"the PostgreSQL installation directory. Visit http://trac.osgeo.org/postgis/ticket/635 " +"to track this bug." msgstr "" #. Tag: para @@ -666,8 +658,8 @@ msgstr "" #, no-c-format msgid "" "PostgreSQL provides a utility called pg_config to enable " -"extensions like PostGIS to locate the PostgreSQL installation directory. Use" -" this parameter (--with-pgconfig=/path/to/pg_config) to " +"extensions like PostGIS to locate the PostgreSQL installation directory. Use " +"this parameter (--with-pgconfig=/path/to/pg_config) to " "manually specify a particular PostgreSQL installation that PostGIS will " "build against." msgstr "" @@ -689,9 +681,9 @@ msgstr "" msgid "" "GEOS, a required geometry library, provides a utility called geos-" "config to enable software installations to locate the GEOS " -"installation directory. Use this parameter (--with-" -"geosconfig=/path/to/geos-config) to manually specify a particular " -"GEOS installation that PostGIS will build against." +"installation directory. Use this parameter (--with-geosconfig=/path/" +"to/geos-config) to manually specify a particular GEOS installation " +"that PostGIS will build against." msgstr "" #. Tag: para @@ -701,9 +693,9 @@ msgid "" "LibXML is the library required for doing GeomFromKML/GML processes. It " "normally is found if you have libxml installed, but if not or you want a " "specific version used, you'll need to point PostGIS at a specific " -"xml2-config confi file to enable software installations" -" to locate the LibXML installation directory. Use this parameter (>--with-xml2config=/path/to/xml2-config) to manually specify a " +"xml2-config confi file to enable software installations " +"to locate the LibXML installation directory. Use this parameter (>--" +"with-xml2config=/path/to/xml2-config) to manually specify a " "particular LibXML installation that PostGIS will build against." msgstr "" @@ -739,9 +731,9 @@ msgstr "" msgid "" "PCRE is an BSD-licensed Perl " "Compatible Regular Expression library required by address_standardizer " -"extension. Use this parameter (--with-" -"pcredir=/path/to/pcredir) to manually specify a particular PCRE " -"installation directory that PostGIS will build against." +"extension. Use this parameter (--with-pcredir=/path/to/pcredir) to manually specify a particular PCRE installation directory that " +"PostGIS will build against." msgstr "" #. Tag: para @@ -756,10 +748,9 @@ msgstr "" #: installation.xml:482 #, no-c-format msgid "" -"Compile with raster support. This will build " -"rtpostgis-&last_release_version; library and rtpostgis.sql file. This may " -"not be required in final release as plan is to build in raster support by " -"default." +"Compile with raster support. This will build rtpostgis-" +"&last_release_version; library and rtpostgis.sql file. This may not be " +"required in final release as plan is to build in raster support by default." msgstr "" #. Tag: para @@ -767,8 +758,8 @@ msgstr "" #, no-c-format msgid "" "Compile with topology support. This will build the topology.sql file. There " -"is no corresponding library as all logic needed for topology is in " -"postgis-&last_release_version; library." +"is no corresponding library as all logic needed for topology is in postgis-" +"&last_release_version; library." msgstr "" #. Tag: para @@ -778,20 +769,19 @@ msgid "" "By default PostGIS will try to detect gettext support and compile with it, " "however if you run into incompatibility issues that cause breakage of " "loader, you can disable it entirely with this command. Refer to ticket " -"http://trac.osgeo.org/postgis/ticket/748" -" for an example issue solved by configuring with this. NOTE: that you aren't" -" missing much by turning this off. This is used for international help/label" -" support for the GUI loader which is not yet documented and still " -"experimental." +"http://trac.osgeo." +"org/postgis/ticket/748 for an example issue solved by configuring " +"with this. NOTE: that you aren't missing much by turning this off. This is " +"used for international help/label support for the GUI loader which is not " +"yet documented and still experimental." msgstr "" #. Tag: para #: installation.xml:511 #, no-c-format msgid "" -"By default PostGIS will not install with sfcgal support without this switch." -" PATH is an optional argument that allows to specify an " +"By default PostGIS will not install with sfcgal support without this switch. " +"PATH is an optional argument that allows to specify an " "alternate PATH to sfcgal-config." msgstr "" @@ -799,9 +789,9 @@ msgstr "" #: installation.xml:519 #, no-c-format msgid "" -"If you obtained PostGIS from the SVN repository , the first" -" step is really to run the script" +"If you obtained PostGIS from the SVN repository , the first step is really to run the " +"script" msgstr "" #. Tag: para @@ -816,9 +806,9 @@ msgstr "" #: installation.xml:536 #, no-c-format msgid "" -"If you instead obtained PostGIS as a tarball, running " -"./autogen.sh is not necessary as " -"configure has already been generated." +"If you instead obtained PostGIS as a tarball, running ./autogen.sh is not necessary as configure has already been " +"generated." msgstr "" #. Tag: title @@ -866,12 +856,11 @@ msgstr "" #, no-c-format msgid "" "Introduced in PostGIS 2.0. This generates html cheat sheets suitable for " -"quick reference or for student handouts. This requires xsltproc to build and" -" will generate 4 files in doc folder " -"topology_cheatsheet.html, " -"tiger_geocoder_cheatsheet.html, " -"raster_cheatsheet.html, " -"postgis_cheatsheet.html" +"quick reference or for student handouts. This requires xsltproc to build and " +"will generate 4 files in doc folder topology_cheatsheet.html, tiger_geocoder_cheatsheet.html, " +"raster_cheatsheet.html, postgis_cheatsheet." +"html" msgstr "" #. Tag: para @@ -970,8 +959,8 @@ msgstr "" #, no-c-format msgid "" "The extension files will always be the same for the same version of PostGIS " -"regardless of OS, so it is fine to copy over the extension files from one OS" -" to another as long as you have the PostGIS binaries already installed on " +"regardless of OS, so it is fine to copy over the extension files from one OS " +"to another as long as you have the PostGIS binaries already installed on " "your servers." msgstr "" @@ -981,9 +970,9 @@ msgstr "" msgid "" "If you want to install the extensions manually on a separate server " "different from your development, You need to copy the following files from " -"the extensions folder into the PostgreSQL / share / " -"extension folder of your PostgreSQL install as well as the needed" -" binaries for regular PostGIS if you don't have them already on the server." +"the extensions folder into the PostgreSQL / share / extension folder of your PostgreSQL install as well as the needed binaries " +"for regular PostGIS if you don't have them already on the server." msgstr "" #. Tag: para @@ -1001,8 +990,8 @@ msgstr "" msgid "" "All the files in the /sql folder of each extension. Note that these need to " "be copied to the root of the PostgreSQL share/extension folder " -"extensions/postgis/sql/*.sql, " -"extensions/postgis_topology/sql/*.sql" +"extensions/postgis/sql/*.sql, extensions/" +"postgis_topology/sql/*.sql" msgstr "" #. Tag: para @@ -1027,15 +1016,20 @@ msgstr "" #, no-c-format msgid "" "SELECT name, default_version,installed_version \n" -"FROM pg_available_extensions WHERE name LIKE 'postgis%' or name LIKE 'address%';\n" +"FROM pg_available_extensions WHERE name LIKE 'postgis%' or name LIKE 'address" +"%';\n" "\n" " name | default_version | installed_version\n" "------------------------------+-----------------+-------------------\n" -" address_standardizer | &last_release_version; | &last_release_version; \n" -" address_standardizer_data_us | &last_release_version; | &last_release_version; \n" -" postgis | &last_release_version; | &last_release_version; \n" +" address_standardizer | &last_release_version; | " +"&last_release_version; \n" +" address_standardizer_data_us | &last_release_version; | " +"&last_release_version; \n" +" postgis | &last_release_version; | " +"&last_release_version; \n" " postgis_sfcgal | &last_release_version; |\n" -" postgis_tiger_geocoder | &last_release_version; | &last_release_version; \n" +" postgis_tiger_geocoder | &last_release_version; | " +"&last_release_version; \n" " postgis_topology | &last_release_version; |\n" "(6 rows)" msgstr "" @@ -1044,10 +1038,10 @@ msgstr "" #: installation.xml:626 #, no-c-format msgid "" -"If you have the extension installed in the database you are querying, you'll" -" see mention in the installed_version column. If you get " -"no records back, it means you don't have postgis extensions installed on the" -" server at all. PgAdmin III 1.14+ will also provide this information in the " +"If you have the extension installed in the database you are querying, you'll " +"see mention in the installed_version column. If you get " +"no records back, it means you don't have postgis extensions installed on the " +"server at all. PgAdmin III 1.14+ will also provide this information in the " "extensions section of the database browser tree and will " "even allow upgrade or uninstall by right-clicking." msgstr "" @@ -1121,18 +1115,18 @@ msgstr "" #: installation.xml:638 #, no-c-format msgid "" -"Extension tables spatial_ref_sys, " -"layer, topology can not be explicitly " -"backed up. They can only be backed up when the respective " -"postgis or postgis_topology extension " -"is backed up, which only seems to happen when you backup the whole database." -" As of PostGIS 2.0.1, only srid records not packaged with PostGIS are backed" -" up when the database is backed up so don't go around changing srids we " -"package and expect your changes to be there. Put in a ticket if you find an " -"issue. The structures of extension tables are never backed up since they are" -" created with CREATE EXTENSION and assumed to be the same for a" -" given version of an extension. These behaviors are built into the current " -"PostgreSQL extension model, so nothing we can do about it." +"Extension tables spatial_ref_sys, layer, topology can not be explicitly backed up. They " +"can only be backed up when the respective postgis or " +"postgis_topology extension is backed up, which only seems " +"to happen when you backup the whole database. As of PostGIS 2.0.1, only srid " +"records not packaged with PostGIS are backed up when the database is backed " +"up so don't go around changing srids we package and expect your changes to " +"be there. Put in a ticket if you find an issue. The structures of extension " +"tables are never backed up since they are created with CREATE " +"EXTENSION and assumed to be the same for a given version of an " +"extension. These behaviors are built into the current PostgreSQL extension " +"model, so nothing we can do about it." msgstr "" #. Tag: para @@ -1140,9 +1134,11 @@ msgstr "" #, no-c-format msgid "" "If you installed &last_release_version;, without using our wonderful " -"extension system, you can change it to be extension based by first upgrading" -" to the latest micro version running the upgrade scripts: " -"postgis_upgrade_22_minor.sql,raster_upgrade_22_minor.sql,topology_upgrade_22_minor.sql." +"extension system, you can change it to be extension based by first upgrading " +"to the latest micro version running the upgrade scripts: " +"postgis_upgrade_22_minor.sql," +"raster_upgrade_22_minor.sql," +"topology_upgrade_22_minor.sql." msgstr "" #. Tag: para @@ -1192,8 +1188,8 @@ msgstr "" #: installation.xml:662 #, no-c-format msgid "" -"The above command will run through various checks and regression tests using" -" the generated library against an actual PostgreSQL database." +"The above command will run through various checks and regression tests using " +"the generated library against an actual PostgreSQL database." msgstr "" #. Tag: para @@ -1209,13 +1205,13 @@ msgstr "" #: installation.xml:676 #, no-c-format msgid "" -"Currently, the make check relies on the PATH" -" and PGPORT environment variables when performing the checks - " +"Currently, the make check relies on the PATH " +"and PGPORT environment variables when performing the checks - " "it does not use the PostgreSQL version that may have " -"been specified using the configuration parameter --with-" -"pgconfig. So make sure to modify your PATH to match the detected " -"PostgreSQL installation during configuration or be prepared to deal with the" -" impending headaches." +"been specified using the configuration parameter --with-pgconfig. So make sure to modify your PATH to match the detected PostgreSQL " +"installation during configuration or be prepared to deal with the impending " +"headaches." msgstr "" #. Tag: para @@ -1532,11 +1528,15 @@ msgid "" "\n" "Creating database 'postgis_reg' \n" "Loading PostGIS into 'postgis_reg' \n" -" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/postgis/postgis.sql\n" -" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/postgis/postgis_comments.sql\n" +" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/" +"postgis/postgis.sql\n" +" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/" +"postgis/postgis_comments.sql\n" "Loading SFCGAL into 'postgis_reg'\n" -" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/postgis/sfcgal.sql\n" -" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/postgis/sfcgal_comments.sql\n" +" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/" +"postgis/sfcgal.sql\n" +" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/" +"postgis/sfcgal_comments.sql\n" "PostgreSQL 9.4.4, compiled by Visual C++ build 1800, 32-bit\n" " Postgis 2.2.0dev - r13980 - 2015-08-23 06:13:07\n" " scripts 2.2.0dev r13980\n" @@ -1663,8 +1663,10 @@ msgid "" " sfcgal/concave_hull .. ok \n" " sfcgal/wmsservers .. ok \n" " sfcgal/approximatemedialaxis .. ok \n" -" uninstall . /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/postgis/uninstall_sfcgal.sql\n" -" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/postgis/uninstall_postgis.sql\n" +" uninstall . /projects/postgis/branches/2.2/regress/00-regress-install/" +"share/contrib/postgis/uninstall_sfcgal.sql\n" +" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/" +"postgis/uninstall_postgis.sql\n" ". ok (4336)\n" "\n" "Run tests: 118\n" @@ -1695,8 +1697,8 @@ msgstr "" msgid "" "The postgis_tiger_geocoder and " "address_standardizer extensions, currenlty only support " -"the standard PostgreSQL installcheck. To test these use the below. Note: the" -" make install is not necessary if you already did make install at root of " +"the standard PostgreSQL installcheck. To test these use the below. Note: the " +"make install is not necessary if you already did make install at root of " "PostGIS code folder." msgstr "" @@ -1822,8 +1824,8 @@ msgstr "" #: installation.xml:727 #, no-c-format msgid "" -"The loader and dumper binaries are installed in " -"[prefix]/bin." +"The loader and dumper binaries are installed in [prefix]/bin." msgstr "" #. Tag: para @@ -1861,11 +1863,10 @@ msgstr "" #: installation.xml:759 #, no-c-format msgid "" -"postgis_comments.sql, " -"raster_comments.sql, " -"topology_comments.sql was separated from the typical " -"build and installation targets since with it comes the extra dependency of " -"xsltproc." +"postgis_comments.sql, raster_comments.sql, topology_comments.sql was separated from the " +"typical build and installation targets since with it comes the extra " +"dependency of xsltproc." msgstr "" #. Tag: title @@ -1925,10 +1926,10 @@ msgstr "" #: installation.xml:802 #, no-c-format msgid "" -"For a complete set of EPSG coordinate system definition identifiers, you can" -" also load the spatial_ref_sys.sql definitions file and" -" populate the spatial_ref_sys table. This will permit you" -" to perform ST_Transform() operations on geometries." +"For a complete set of EPSG coordinate system definition identifiers, you can " +"also load the spatial_ref_sys.sql definitions file and " +"populate the spatial_ref_sys table. This will permit you " +"to perform ST_Transform() operations on geometries." msgstr "" #. Tag: command @@ -2011,8 +2012,7 @@ msgstr "" #: installation.xml:857 installation.xml:894 #, no-c-format msgid "" -"If you plan to restore an old backup from prior versions in this new db, " -"run:" +"If you plan to restore an old backup from prior versions in this new db, run:" msgstr "" #. Tag: command @@ -2028,8 +2028,8 @@ msgid "" "There is an alternative legacy_minimal.sql you can run " "instead which will install barebones needed to recover tables and work with " "apps like MapServer and GeoServer. If you have views that use things like " -"distance / length etc, you'll need the full blown " -"legacy.sql" +"distance / length etc, you'll need the full blown legacy.sql" msgstr "" #. Tag: para @@ -2095,20 +2095,20 @@ msgid "" "The address_standardizer extension used to be a separate " "package that required separate download. From PostGIS 2.2 on, it is now " "bundled in. For more information about the address_standardize, what it " -"does, and how to configure it for your needs, refer to ." +"does, and how to configure it for your needs, refer to ." msgstr "" #. Tag: para #: installation.xml:903 #, no-c-format msgid "" -"This standardizer can be used in conjunction with the PostGIS packaged tiger" -" geocoder extension as a replacement for the discussed. To use as replacement refer to " -". You can also use it as" -" a building block for your own geocoder or use it to standardize your " -"addresses for easier compare of addresses." +"This standardizer can be used in conjunction with the PostGIS packaged tiger " +"geocoder extension as a replacement for the discussed. To use as replacement refer to . You can also use it as a building " +"block for your own geocoder or use it to standardize your addresses for " +"easier compare of addresses." msgstr "" #. Tag: para @@ -2116,13 +2116,13 @@ msgstr "" #, no-c-format msgid "" "The address standardizer relies on PCRE which is usually already installed " -"on many Nix systems, but you can download the latest at: http://www.pcre.org. If during , PCRE is found, then the address " +"on many Nix systems, but you can download the latest at: http://www.pcre.org. If during , PCRE is found, then the address " "standardizer extension will automatically be built. If you have a custom " "pcre install you want to use instead, pass to configure --with-" -"pcredir=/path/to/pcre where /path/to/pcre is the" -" root folder for your pcre include and lib directories." +"pcredir=/path/to/pcre where /path/to/pcre is the " +"root folder for your pcre include and lib directories." msgstr "" #. Tag: para @@ -2189,8 +2189,8 @@ msgid "" "Perl Regex:Assemble is no longer needed for compiling address_standardizer " "extension since the files it generates are part of the source tree. However " "if you need to edit the usps-st-city-orig.txt or " -"usps-st-city-orig.txt usps-st-city-adds.tx, you need to" -" rebuild parseaddress-stcities.h which does require " +"usps-st-city-orig.txt usps-st-city-adds.tx, you need to " +"rebuild parseaddress-stcities.h which does require " "Regex:Assemble." msgstr "" @@ -2222,8 +2222,8 @@ msgstr "" #: installation.xml:932 #, no-c-format msgid "" -"Extras like Tiger geocoder may not be packaged in your PostGIS distribution," -" but will always be available in the postgis-&last_release_version;.tar.gz " +"Extras like Tiger geocoder may not be packaged in your PostGIS distribution, " +"but will always be available in the postgis-&last_release_version;.tar.gz " "file. The instructions provided here are also available in the " "extras/tiger_geocoder/README" msgstr "" @@ -2247,8 +2247,8 @@ msgstr "" #: installation.xml:936 #, no-c-format msgid "" -"If you are using PostgreSQL 9.1+ and PostGIS 2.1+, you can take advantage of" -" the new extension model for installing tiger geocoder. To do so:" +"If you are using PostgreSQL 9.1+ and PostGIS 2.1+, you can take advantage of " +"the new extension model for installing tiger geocoder. To do so:" msgstr "" #. Tag: para @@ -2266,8 +2266,8 @@ msgid "" "Connect to your database via psql or pgAdmin or some other tool and run the " "following SQL commands. Note that if you are installing in a database that " "already has postgis, you don't need to do the first step. If you have " -"fuzzystrmatch extension already installed, you don't need" -" to do the second step either." +"fuzzystrmatch extension already installed, you don't need " +"to do the second step either." msgstr "" #. Tag: programlisting @@ -2321,15 +2321,16 @@ msgstr "" #: installation.xml:947 #, no-c-format msgid "" -"So for example to create a profile called debbie that follows " -"sh convention. You would do:" +"So for example to create a profile called debbie that follows sh convention. You would do:" msgstr "" #. Tag: programlisting #: installation.xml:948 #, no-c-format msgid "" -"INSERT INTO tiger.loader_platform(os, declare_sect, pgbin, wget, unzip_command, psql, path_sep, \n" +"INSERT INTO tiger.loader_platform(os, declare_sect, pgbin, wget, " +"unzip_command, psql, path_sep, \n" " loader, environ_set_command, county_process_command)\n" "SELECT 'debbie', declare_sect, pgbin, wget, unzip_command, psql, path_sep, \n" " loader, environ_set_command, county_process_command\n" @@ -2359,8 +2360,8 @@ msgstr "" #, no-c-format msgid "" "Then run the and SQL functions make sure to use the name" -" of your custom profile and copy the scripts to a .sh or .bat file. So for " +"linkend=\"Loader_Generate_Script\"/> SQL functions make sure to use the name " +"of your custom profile and copy the scripts to a .sh or .bat file. So for " "example to do the nation load and one state using our new profile we would:" msgstr "" @@ -2386,9 +2387,8 @@ msgstr "" #: installation.xml:958 #, no-c-format msgid "" -"After you are done loading all data or at a stopping point, it's a good idea" -" to analyze all the tiger tables to update the stats (include inherited " -"stats)" +"After you are done loading all data or at a stopping point, it's a good idea " +"to analyze all the tiger tables to update the stats (include inherited stats)" msgstr "" #. Tag: programlisting @@ -2457,8 +2457,8 @@ msgstr "" #: installation.xml:979 installation.xml:1039 #, no-c-format msgid "" -"If you don't have an extras folder, download &postgis_download_url;" +"If you don't have an extras folder, download &postgis_download_url;" msgstr "" #. Tag: command @@ -2482,10 +2482,10 @@ msgid "" "executables server etc or alternatively you can update the " "loader_platform table once installed. If you don't edit " "this file or the loader_platform table, it will just " -"contain common case locations of items and you'll have to edit the generated" -" script after the fact when you run the and SQL functions." +"contain common case locations of items and you'll have to edit the generated " +"script after the fact when you run the and SQL functions." msgstr "" #. Tag: para @@ -2494,9 +2494,9 @@ msgstr "" msgid "" "If you are installing Tiger geocoder for the first time edit either the " "create_geocode.bat script If you are on windows or the " -"create_geocode.sh if you are on Linux/Unix/Mac OSX with" -" your PostgreSQL specific settings and run the corresponding script from the" -" commandline." +"create_geocode.sh if you are on Linux/Unix/Mac OSX with " +"your PostgreSQL specific settings and run the corresponding script from the " +"commandline." msgstr "" #. Tag: para @@ -2526,7 +2526,8 @@ msgstr "" #: installation.xml:999 #, no-c-format msgid "" -"SELECT pprint_addy(normalize_address('202 East Fremont Street, Las Vegas, Nevada 89101')) As pretty_address;\n" +"SELECT pprint_addy(normalize_address('202 East Fremont Street, Las Vegas, " +"Nevada 89101')) As pretty_address;\n" "pretty_address\n" "---------------------------------------\n" "202 E Fremont St, Las Vegas, NV 89101" @@ -2542,8 +2543,8 @@ msgstr "" #: installation.xml:1003 #, no-c-format msgid "" -"One of the many complaints of folks is the address normalizer function function that normalizes an address for " +"One of the many complaints of folks is the address normalizer function function that normalizes an address for " "prepping before geocoding. The normalizer is far from perfect and trying to " "patch its imperfectness takes a vast amount of resources. As such we have " "integrated with another project that has a much better address standardizer " @@ -2557,15 +2558,15 @@ msgstr "" #, no-c-format msgid "" "Once you install this extension in the same database as you have installed " -"postgis_tiger_geocoder, then the can be used instead of . This extension is tiger agnostic, so can be" -" used with other data sources such as international addresses. The tiger " -"geocoder extension does come packaged with its own custom versions of ( tiger.pagc_rules) , (tiger.pagc_gaz), and (tiger.pagc_lex). These you can add and " -"update to improve your standardizing experience for your own needs." +"postgis_tiger_geocoder, then the can be used instead of . This extension is tiger agnostic, so can be used " +"with other data sources such as international addresses. The tiger geocoder " +"extension does come packaged with its own custom versions of ( tiger.pagc_rules) , " +"(tiger.pagc_gaz), and (tiger." +"pagc_lex). These you can add and update to improve your standardizing " +"experience for your own needs." msgstr "" #. Tag: title @@ -2592,9 +2593,9 @@ msgid "" "state into its own separate set of state tables. Each state table inherits " "from the tables defined in tiger schema so that its " "sufficient to just query those tables to access all the data and drop a set " -"of state tables at any time using the if you need to reload a " -"state or just don't need a state anymore." +"of state tables at any time using the if you need to reload a state or " +"just don't need a state anymore." msgstr "" #. Tag: para @@ -2621,8 +2622,8 @@ msgstr "" #: installation.xml:1017 #, no-c-format msgid "" -"For Windows, 7-zip which is a free compress/uncompress tool you can download" -" from http://www.7-zip.org/" +"For Windows, 7-zip which is a free compress/uncompress tool you can download " +"from http://www.7-zip.org/" msgstr "" #. Tag: para @@ -2645,8 +2646,9 @@ msgstr "" #: installation.xml:1021 #, no-c-format msgid "" -"If you are on windows, you can get pre-compiled binaries from http://gnuwin32.sourceforge.net/packages/wget.htm" +"If you are on windows, you can get pre-compiled binaries from http://gnuwin32." +"sourceforge.net/packages/wget.htm" msgstr "" #. Tag: para @@ -2658,8 +2660,7 @@ msgid "" "state data, you need to load the nation wide data which you do with . Which will generate a loader " "script for you. is a one-" -"time step that should be done for upgrading (from 2010) and for new " -"installs." +"time step that should be done for upgrading (from 2010) and for new installs." msgstr "" #. Tag: para @@ -2700,8 +2701,8 @@ msgstr "" #, no-c-format msgid "" "If you have Tiger Geocoder packaged with 2.0+ already installed, you can " -"upgrade the functions at any time even from an interim tar ball if there are" -" fixes you badly need. This will only work for Tiger geocoder not installed " +"upgrade the functions at any time even from an interim tar ball if there are " +"fixes you badly need. This will only work for Tiger geocoder not installed " "with extensions." msgstr "" @@ -2716,16 +2717,16 @@ msgstr "" #, no-c-format msgid "" "Locate the upgrade_geocoder.bat script If you are on " -"windows or the upgrade_geocoder.sh if you are on " -"Linux/Unix/Mac OSX. Edit the file to have your postgis database credentials." +"windows or the upgrade_geocoder.sh if you are on Linux/" +"Unix/Mac OSX. Edit the file to have your postgis database credentials." msgstr "" #. Tag: para #: installation.xml:1054 #, no-c-format msgid "" -"If you are upgrading from 2010 or 2011, make sure to unremark out the loader" -" script line so you get the latest script for loading 2012 data." +"If you are upgrading from 2010 or 2011, make sure to unremark out the loader " +"script line so you get the latest script for loading 2012 data." msgstr "" #. Tag: para @@ -2738,9 +2739,9 @@ msgstr "" #: installation.xml:1059 #, no-c-format msgid "" -"Next drop all nation tables and load up the new ones. Generate a drop script" -" with this SQL statement as detailed in " +"Next drop all nation tables and load up the new ones. Generate a drop script " +"with this SQL statement as detailed in " msgstr "" #. Tag: programlisting @@ -2791,8 +2792,8 @@ msgstr "" #: installation.xml:1067 #, no-c-format msgid "" -"Refer to for instructions on" -" how to run the generate script. This only needs to be done once." +"Refer to for instructions on " +"how to run the generate script. This only needs to be done once." msgstr "" #. Tag: para @@ -2801,8 +2802,8 @@ msgstr "" msgid "" "You can have a mix of 2010/2011 state tables and can upgrade each state " "separately. Before you upgrade a state to 2011, you first need to drop the " -"2010 tables for that state using ." +"2010 tables for that state using ." msgstr "" #. Tag: title @@ -2816,12 +2817,12 @@ msgstr "" #, no-c-format msgid "" "Some packaged distributions of PostGIS (in particular the Win32 installers " -"for PostGIS >= 1.1.5) load the PostGIS functions into a template database" -" called template_postgis. If the " +"for PostGIS >= 1.1.5) load the PostGIS functions into a template database " +"called template_postgis. If the " "template_postgis database exists in your PostgreSQL " "installation then it is possible for users and/or applications to create " -"spatially-enabled databases using a single command. Note that in both cases," -" the database user must have been granted the privilege to create new " +"spatially-enabled databases using a single command. Note that in both cases, " +"the database user must have been granted the privilege to create new " "databases." msgstr "" @@ -2867,8 +2868,8 @@ msgstr "" #: installation.xml:1108 #, no-c-format msgid "" -"Unfortunately not all definitions can be easily replaced in a live database," -" so sometimes your best bet is a dump/reload process." +"Unfortunately not all definitions can be easily replaced in a live database, " +"so sometimes your best bet is a dump/reload process." msgstr "" #. Tag: para @@ -2899,8 +2900,8 @@ msgstr "" #, no-c-format msgid "" "If you installed your database using extensions, you'll need to upgrade " -"using the extension model as well. If you installed using the old sql script" -" way, then you should upgrade using the sql script way. Please refer to the " +"using the extension model as well. If you installed using the old sql script " +"way, then you should upgrade using the sql script way. Please refer to the " "appropriate." msgstr "" @@ -2930,15 +2931,14 @@ msgstr "" #, no-c-format msgid "" "After compiling and installing (make install) you should find a " -"postgis_upgrade.sql and " -"rtpostgis_upgrade.sql in the installation folders. For " -"example " -"/usr/share/postgresql/9.3/contrib/postgis_upgrade.sql. " -"Install the postgis_upgrade.sql. If you have raster " -"functionality installed, you will also need to install the " -"/usr/share/postgresql/9.3/contrib/postgis_upgrade.sql. " -"If you are moving from PostGIS 1.* to PostGIS 2.* or from PostGIS 2.* prior " -"to r7409, you need to do a HARD UPGRADE." +"postgis_upgrade.sql and rtpostgis_upgrade." +"sql in the installation folders. For example /usr/share/" +"postgresql/9.3/contrib/postgis_upgrade.sql. Install the " +"postgis_upgrade.sql. If you have raster functionality " +"installed, you will also need to install the /usr/share/" +"postgresql/9.3/contrib/postgis_upgrade.sql. If you are moving " +"from PostGIS 1.* to PostGIS 2.* or from PostGIS 2.* prior to r7409, you need " +"to do a HARD UPGRADE." msgstr "" #. Tag: programlisting @@ -2972,9 +2972,9 @@ msgstr "" #: installation.xml:1151 #, no-c-format msgid "" -"If you can't find the postgis_upgrade*.sql specific for" -" upgrading your version you are using a version too early for a soft upgrade" -" and need to do a HARD UPGRADE." +"If you can't find the postgis_upgrade*.sql specific for " +"upgrading your version you are using a version too early for a soft upgrade " +"and need to do a HARD UPGRADE." msgstr "" #. Tag: para @@ -3025,8 +3025,8 @@ msgstr "" #: installation.xml:1169 #, no-c-format msgid "" -"Then you'll need to backup your database, create a fresh one as described in" -" and then restore your backup " +"Then you'll need to backup your database, create a fresh one as described in " +" and then restore your backup " "ontop of this new database." msgstr "" @@ -3050,8 +3050,8 @@ msgstr "" msgid "" "Then everything is already up to date and you can safely ignore it. " "UNLESS you're attempting to upgrade from " -"an SVN version to the next (which doesn't get a new version number); in that" -" case you can append \"next\" to the version string, and next time you'll " +"an SVN version to the next (which doesn't get a new version number); in that " +"case you can append \"next\" to the version string, and next time you'll " "need to drop the \"next\" suffix again:" msgstr "" @@ -3086,8 +3086,8 @@ msgid "" "By HARD UPGRADE we mean full dump/reload of postgis-enabled databases. You " "need a HARD UPGRADE when PostGIS objects' internal storage changes or when " "SOFT UPGRADE is not possible. The Release " -"Notes appendix reports for each version whether you need a " -"dump/reload (HARD UPGRADE) to upgrade." +"Notes appendix reports for each version whether you need a dump/" +"reload (HARD UPGRADE) to upgrade." msgstr "" #. Tag: para @@ -3095,8 +3095,8 @@ msgstr "" #, no-c-format msgid "" "The dump/reload process is assisted by the postgis_restore.pl script which " -"takes care of skipping from the dump all definitions which belong to PostGIS" -" (including old ones), allowing you to restore your schemas and data into a " +"takes care of skipping from the dump all definitions which belong to PostGIS " +"(including old ones), allowing you to restore your schemas and data into a " "database with PostGIS installed without getting duplicate symbol errors or " "bringing forward deprecated objects." msgstr "" @@ -3105,8 +3105,8 @@ msgstr "" #: installation.xml:1206 #, no-c-format msgid "" -"Supplementary instructions for windows users are available at Windows Hard " +"Supplementary instructions for windows users are available at Windows Hard " "upgrade." msgstr "" @@ -3121,8 +3121,8 @@ msgstr "" #, no-c-format msgid "" "Create a \"custom-format\" dump of the database you want to upgrade (let's " -"call it olddb) include binary blobs (-b) and verbose (-v)" -" output. The user can be the owner of the db, need not be postgres super " +"call it olddb) include binary blobs (-b) and verbose (-v) " +"output. The user can be the owner of the db, need not be postgres super " "account." msgstr "" @@ -3130,8 +3130,8 @@ msgstr "" #: installation.xml:1225 #, no-c-format msgid "" -"pg_dump -h localhost -p 5432 -U postgres -Fc -b -v -f " -"\"/somepath/olddb.backup\" olddb" +"pg_dump -h localhost -p 5432 -U postgres -Fc -b -v -f \"/somepath/olddb." +"backup\" olddb" msgstr "" #. Tag: para @@ -3139,9 +3139,9 @@ msgstr "" #, no-c-format msgid "" "Do a fresh install of PostGIS in a new database -- we'll refer to this " -"database as newdb. Please refer to and " -" for instructions on how to do this." +"database as newdb. Please refer to and for " +"instructions on how to do this." msgstr "" #. Tag: para @@ -3150,8 +3150,8 @@ msgstr "" msgid "" "The spatial_ref_sys entries found in your dump will be restored, but they " "will not override existing ones in spatial_ref_sys. This is to ensure that " -"fixes in the official set will be properly propagated to restored databases." -" If for any reason you really want your own overrides of standard entries " +"fixes in the official set will be properly propagated to restored databases. " +"If for any reason you really want your own overrides of standard entries " "just don't load the spatial_ref_sys.sql file when creating the new db." msgstr "" @@ -3159,13 +3159,13 @@ msgstr "" #: installation.xml:1248 #, no-c-format msgid "" -"If your database is really old or you know you've been using long deprecated" -" functions in your views and functions, you might need to load " +"If your database is really old or you know you've been using long deprecated " +"functions in your views and functions, you might need to load " "legacy.sql for all your functions and views etc. to " -"properly come back. Only do this if _really_ needed. Consider upgrading your" -" views and functions before dumping instead, if possible. The deprecated " -"functions can be later removed by loading " -"uninstall_legacy.sql." +"properly come back. Only do this if _really_ needed. Consider upgrading your " +"views and functions before dumping instead, if possible. The deprecated " +"functions can be later removed by loading uninstall_legacy.sql." msgstr "" #. Tag: para @@ -3181,8 +3181,8 @@ msgstr "" #: installation.xml:1272 #, no-c-format msgid "" -"perl utils/postgis_restore.pl \"/somepath/olddb.backup\" | psql -h localhost" -" -p 5432 -U postgres newdb 2> errors.txt" +"perl utils/postgis_restore.pl \"/somepath/olddb.backup\" | psql -h localhost " +"-p 5432 -U postgres newdb 2> errors.txt" msgstr "" #. Tag: para @@ -3196,11 +3196,11 @@ msgstr "" #, no-c-format msgid "" "Some of your views or functions make use of deprecated PostGIS objects. In " -"order to fix this you may try loading legacy.sql script" -" prior to restore or you'll have to restore to a version of PostGIS which " +"order to fix this you may try loading legacy.sql script " +"prior to restore or you'll have to restore to a version of PostGIS which " "still contains those objects and try a migration again after porting your " -"code. If the legacy.sql way works for you, don't forget" -" to fix your code to stop using deprecated functions and drop them loading " +"code. If the legacy.sql way works for you, don't forget " +"to fix your code to stop using deprecated functions and drop them loading " "uninstall_legacy.sql." msgstr "" @@ -3211,8 +3211,8 @@ msgid "" "Some custom records of spatial_ref_sys in dump file have an invalid SRID " "value. Valid SRID values are bigger than 0 and smaller than 999000. Values " "in the 999000.999999 range are reserved for internal use while values > " -"999999 can't be used at all. All your custom records with invalid SRIDs will" -" be retained, with those > 999999 moved into the reserved range, but the " +"999999 can't be used at all. All your custom records with invalid SRIDs will " +"be retained, with those > 999999 moved into the reserved range, but the " "spatial_ref_sys table would loose a check constraint guarding for that " "invariant to hold and possibly also its primary key ( when multiple invalid " "SRIDS get converted to the same reserved SRID value )." @@ -3261,13 +3261,13 @@ msgstr "" #, no-c-format msgid "" "Check that you have installed PostgreSQL &min_postgres_version; or newer, " -"and that you are compiling against the same version of the PostgreSQL source" -" as the version of PostgreSQL that is running. Mix-ups can occur when your " -"(Linux) distribution has already installed PostgreSQL, or you have otherwise" -" installed PostgreSQL before and forgotten about it. PostGIS will only work " +"and that you are compiling against the same version of the PostgreSQL source " +"as the version of PostgreSQL that is running. Mix-ups can occur when your " +"(Linux) distribution has already installed PostgreSQL, or you have otherwise " +"installed PostgreSQL before and forgotten about it. PostGIS will only work " "with PostgreSQL &min_postgres_version; or newer, and strange, unexpected " -"error messages will result if you use an older version. To check the version" -" of PostgreSQL which is running, connect to the database using psql and run " +"error messages will result if you use an older version. To check the version " +"of PostgreSQL which is running, connect to the database using psql and run " "this query:" msgstr "" @@ -3282,8 +3282,8 @@ msgstr "" #, no-c-format msgid "" "If you are running an RPM based distribution, you can check for the " -"existence of pre-installed packages using the rpm command" -" as follows: rpm -qa | grep postgresql" +"existence of pre-installed packages using the rpm command " +"as follows: rpm -qa | grep postgresql" msgstr "" #. Tag: para @@ -3304,19 +3304,18 @@ msgstr "" #: installation.xml:1366 #, no-c-format msgid "" -"Also check that configure has correctly detected the location and version of" -" PostgreSQL, the Proj4 library and the GEOS library." +"Also check that configure has correctly detected the location and version of " +"PostgreSQL, the Proj4 library and the GEOS library." msgstr "" #. Tag: para #: installation.xml:1373 #, no-c-format msgid "" -"The output from configure is used to generate the " -"postgis_config.h file. Check that the " -"POSTGIS_PGSQL_VERSION, " -"POSTGIS_PROJ_VERSION and " -"POSTGIS_GEOS_VERSION variables have been set correctly." +"The output from configure is used to generate the postgis_config." +"h file. Check that the POSTGIS_PGSQL_VERSION, " +"POSTGIS_PROJ_VERSION and POSTGIS_GEOS_VERSION variables have been set correctly." msgstr "" #. Tag: title diff --git a/doc/po/de_DE/introduction.xml.po b/doc/po/de_DE/introduction.xml.po index 8a3a59a91..e2b83d555 100644 --- a/doc/po/de_DE/introduction.xml.po +++ b/doc/po/de_DE/introduction.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:23+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -89,9 +90,9 @@ msgstr "" #, 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." +"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 @@ -105,8 +106,7 @@ msgstr "" #, no-c-format msgid "" "Raster development, integration with GDAL, raster loader, user support, " -"general bug fixing, testing on various OS (Slackware, Mac, Windows, and " -"more)" +"general bug fixing, testing on various OS (Slackware, Mac, Windows, and more)" msgstr "" #. Tag: term @@ -137,8 +137,8 @@ msgstr "" #, 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." +"alignment with GEOS releases, Topology support, and Raster framework and low " +"level api functions." msgstr "" #. Tag: title @@ -170,8 +170,8 @@ msgstr "" #, no-c-format msgid "" "Distance function enhancements (including 3D distance and relationship " -"functions) and additions, Tiny WKB output format (TWKB) (in development) and" -" general user support" +"functions) and additions, Tiny WKB output format (TWKB) (in development) and " +"general user support" msgstr "" #. Tag: term @@ -183,8 +183,7 @@ msgstr "" #. Tag: para #: introduction.xml:94 #, no-c-format -msgid "" -"Input output XML (KML,GML)/GeoJSON functions, 3D support and bug fixes." +msgid "Input output XML (KML,GML)/GeoJSON functions, 3D support and bug fixes." msgstr "" #. Tag: term @@ -321,12 +320,12 @@ 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, " +"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, " "Jason Smith, 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, " +"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, Mike Toews, Nathan Wagner, Nathaniel Clay, Nikita Shulga, " "Norman Vine, Rafal Magda, Ralph Mason, Richard Greenwood, Silvio Grosso, " "Steffen Macke, Stephen Frost, Tom van Tilburg, Vincent Mora, Vincent Picavet" @@ -354,10 +353,10 @@ msgid "" "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 & Tracing International" -" AG, Michigan Tech Research Institute, Natural Resources Canada, Norwegian " -"Forest and Landscape Institute, Boundless (former OpenGeo), OSGeo, Oslandia," -" Palantir Technologies, Paragon Corporation, R3 GIS, Refractions Research, " +"Consulting Engineers, LisaSoft, Logical Tracking & Tracing International " +"AG, Michigan Tech Research Institute, Natural Resources Canada, Norwegian " +"Forest and Landscape Institute, Boundless (former OpenGeo), OSGeo, Oslandia, " +"Palantir Technologies, Paragon Corporation, R3 GIS, Refractions Research, " "Regione Toscana - SITA, Safe Software, Sirius Corporation plc, Stadt Uster, " "UC Davis Center for Vectorborne Diseases, University of Laval, U.S " "Department of State (HIU), CartoDB, Zonar Systems" @@ -378,10 +377,10 @@ msgid "" "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 PostGIS " -"newsgroup your thoughts and together we can make it happen." +"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 PostGIS newsgroup your thoughts " +"and together we can make it happen." msgstr "" #. Tag: para @@ -397,8 +396,8 @@ msgstr "" #: introduction.xml:283 #, no-c-format msgid "" -"postgistopology - 10 plus sponsors each " +"postgistopology - 10 plus sponsors each " "contributed $250 USD to build toTopoGeometry function and beef up topology " "support in 2.0.0. It happened." msgstr "" @@ -407,9 +406,9 @@ msgstr "" #: introduction.xml:284 #, no-c-format msgid "" -"postgis64windows - 20 someodd sponsors each" -" contributed $100 USD to pay for the work needed to work out PostGIS 64-bit " +"postgis64windows - 20 someodd sponsors each " +"contributed $100 USD to pay for the work needed to work out PostGIS 64-bit " "issues on windows. It happened. We now have a 64-bit release for PostGIS " "2.0.1 available on PostgreSQL stack builder." msgstr "" @@ -426,8 +425,8 @@ msgstr "" msgid "" "The GEOS 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." +"all work, ongoing maintenance and support of Mateusz Loskot, Sandro Santilli " +"(strk), Paul Ramsey and others." msgstr "" #. Tag: para @@ -471,8 +470,8 @@ msgstr "" #, no-c-format msgid "" "The latest software, documentation and news items are available at the " -"PostGIS web site, http://postgis.net." +"PostGIS web site, http://postgis.net." msgstr "" #. Tag: para @@ -480,16 +479,16 @@ msgstr "" #, no-c-format msgid "" "More information about the GEOS geometry operations library is available " -"at " -"http://trac.osgeo.org/geos/." +"at http://trac.osgeo.org/geos/." msgstr "" #. Tag: para #: introduction.xml:331 #, no-c-format msgid "" -"More information about the Proj4 reprojection library is available at http://trac.osgeo.org/proj/." +"More information about the Proj4 reprojection library is available at http://trac.osgeo.org/proj/." msgstr "" #. Tag: para @@ -497,8 +496,8 @@ msgstr "" #, no-c-format msgid "" "More information about the PostgreSQL database server is available at the " -"PostgreSQL main site http://www.postgresql.org." +"PostgreSQL main site http://www." +"postgresql.org." msgstr "" #. Tag: para @@ -506,8 +505,8 @@ msgstr "" #, no-c-format msgid "" "More information about GiST indexing is available at the PostgreSQL GiST " -"development site, http://www.sai.msu.su/~megera/postgres/gist/." +"development site, http://www.sai.msu.su/~megera/postgres/gist/." msgstr "" #. Tag: para @@ -523,7 +522,7 @@ msgstr "" #, no-c-format msgid "" "The "Simple " -"Features for Specification for SQL" is available at the OpenGIS" -" Consortium web site: http://www.opengeospatial.org/." +"Features for Specification for SQL" is available at the OpenGIS " +"Consortium web site: http://" +"www.opengeospatial.org/." msgstr "" diff --git a/doc/po/de_DE/performance_tips.xml.po b/doc/po/de_DE/performance_tips.xml.po index e1209c0d0..c544a06d4 100644 --- a/doc/po/de_DE/performance_tips.xml.po +++ b/doc/po/de_DE/performance_tips.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2014-10-18 10:29+0000\n" "PO-Revision-Date: 2015-09-29 11:54+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -38,12 +39,12 @@ msgstr "" #, 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 the" -" PostgreSQL Documentation for TOAST for more information)." +"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 the PostgreSQL Documentation for TOAST " +"for more information)." msgstr "" #. Tag: para @@ -78,8 +79,8 @@ msgstr "" 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" +"read the thread on the postgres performance mailing list: http://archives." +"postgresql.org/pgsql-performance/2005-02/msg00030.php" msgstr "" #. Tag: title @@ -103,9 +104,9 @@ 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." +"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 @@ -114,15 +115,16 @@ msgstr "" 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:" +"\"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" +"SELECT " +"AddGeometryColumn('myschema','mytable','bbox','4326','GEOMETRY','2'); \n" "UPDATE mytable SET bbox = ST_Envelope(ST_Force2D(the_geom));" msgstr "" @@ -130,8 +132,8 @@ msgstr "" #: performance_tips.xml:63 #, no-c-format msgid "" -"Now change your query to use the && operator against bbox instead of" -" geom_column, like:" +"Now change your query to use the && operator against bbox instead of " +"geom_column, like:" msgstr "" #. Tag: programlisting @@ -164,14 +166,14 @@ msgstr "" #, 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 " +"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.)" +"data pages. (Feel invited to read the CLUSTER command documentation from the " +"PostgreSQL manual at this point.)" msgstr "" #. Tag: para @@ -189,15 +191,16 @@ msgstr "" 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." +"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:" +"As the HINT message tells you, one can work around this deficiency by adding " +"a \"not null\" constraint to the table:" msgstr "" #. Tag: programlisting @@ -228,9 +231,9 @@ msgstr "" #: 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_Force2D() " +"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_Force2D() " "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:" @@ -250,8 +253,8 @@ msgstr "" 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." +"to drop the constraint. Remember to update the entry in the geometry_columns " +"table and recreate the constraint afterwards." msgstr "" #. Tag: para @@ -278,10 +281,10 @@ msgstr "" #, 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." +"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 @@ -289,9 +292,9 @@ msgstr "" #, no-c-format msgid "" "For a more tips (and better formatting), the original presentation is at " -" " -"http://2007.foss4g.org/presentations/view.php?abstract_id=117." +" http://2007.foss4g.org/presentations/view.php?" +"abstract_id=117." msgstr "" #. Tag: title @@ -326,8 +329,8 @@ msgstr "" 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 Greg Smith: Checkpoint and Background writer" +"url=\"http://www.westnet.com/~gsmith/content/postgresql/chkp-bgw-83.htm" +"\">Greg Smith: Checkpoint and Background writer" msgstr "" #. Tag: para @@ -354,13 +357,12 @@ msgstr "" #: 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." +"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 diff --git a/doc/po/de_DE/postgis.xml.po b/doc/po/de_DE/postgis.xml.po index fc9ac2e83..fa824908b 100644 --- a/doc/po/de_DE/postgis.xml.po +++ b/doc/po/de_DE/postgis.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 11:54+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -31,10 +32,10 @@ msgstr "" #: postgis.xml:138 #, no-c-format msgid "" -"clever " -"elephant
Victoria British " -"Columbia Canada " -"pramsey@cleverelephant.ca
" +"clever elephant
Victoria British Columbia Canada pramsey@cleverelephant.ca" msgstr "" #. Tag: para @@ -57,10 +58,9 @@ msgstr "" #: postgis.xml:162 #, no-c-format msgid "" -"This work is licensed under a Creative Commons " -"Attribution-Share Alike 3.0 License. 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 http://postgis.net." +"This work is licensed under a Creative Commons Attribution-Share Alike 3.0 License. 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 http://postgis.net." msgstr "" diff --git a/doc/po/de_DE/reference.xml.po b/doc/po/de_DE/reference.xml.po index c6d6c349e..6f6966bef 100644 --- a/doc/po/de_DE/reference.xml.po +++ b/doc/po/de_DE/reference.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:24+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -34,13 +35,13 @@ msgstr "" #: 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." +"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 diff --git a/doc/po/de_DE/reference_accessor.xml.po b/doc/po/de_DE/reference_accessor.xml.po index bf11c9e49..3386ddba9 100644 --- a/doc/po/de_DE/reference_accessor.xml.po +++ b/doc/po/de_DE/reference_accessor.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:23+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -81,8 +82,8 @@ msgstr "" #: reference_accessor.xml:29 #, no-c-format msgid "" -"OGC SPEC s2.1.1.1 - Returns the name of the instantiable subtype of Geometry" -" of which this Geometry instance is a member. The name of the instantiable " +"OGC SPEC s2.1.1.1 - Returns the name of the instantiable subtype of Geometry " +"of which this Geometry instance is a member. The name of the instantiable " "subtype of Geometry is returned as a string." msgstr "" @@ -197,7 +198,8 @@ msgstr "Beispiele" #: reference_accessor.xml:51 #, no-c-format msgid "" -"SELECT GeometryType(ST_GeomFromText('LINESTRING(77.29 29.07,77.42 29.26,77.27 29.31,77.29 29.07)'));\n" +"SELECT GeometryType(ST_GeomFromText('LINESTRING(77.29 29.07,77.42 " +"29.26,77.27 29.31,77.29 29.07)'));\n" " geometrytype\n" "--------------\n" " LINESTRING" @@ -207,10 +209,13 @@ msgstr "" #: reference_accessor.xml:52 #, no-c-format msgid "" -"SELECT ST_GeometryType(ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)), \n" -" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 0)), \n" +"SELECT ST_GeometryType(ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 " +"1 1, 0 1 0, 0 0 0)), \n" +" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 " +"1, 0 0 1, 0 0 0)), \n" " ((1 1 0, 1 1 1, 1 0 1, 1 0 0, 1 1 0)), \n" -" ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 1)) )'));\n" +" ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 " +"1, 0 1 1, 0 0 1)) )'));\n" " --result\n" " POLYHEDRALSURFACE" msgstr "" @@ -335,25 +340,29 @@ msgstr "" #: reference_accessor.xml:103 #, no-c-format msgid "" -"SELECT ST_AsText(ST_Boundary(ST_GeomFromText('LINESTRING(1 1,0 0, -1 1)')));\n" +"SELECT ST_AsText(ST_Boundary(ST_GeomFromText('LINESTRING(1 1,0 0, -1 " +"1)')));\n" "st_astext\n" "-----------\n" "MULTIPOINT(1 1,-1 1)\n" "\n" -"SELECT ST_AsText(ST_Boundary(ST_GeomFromText('POLYGON((1 1,0 0, -1 1, 1 1))')));\n" +"SELECT ST_AsText(ST_Boundary(ST_GeomFromText('POLYGON((1 1,0 0, -1 1, 1 " +"1))')));\n" "st_astext\n" "----------\n" "LINESTRING(1 1,0 0,-1 1,1 1)\n" "\n" "--Using a 3d polygon\n" -"SELECT ST_AsEWKT(ST_Boundary(ST_GeomFromEWKT('POLYGON((1 1 1,0 0 1, -1 1 1, 1 1 1))')));\n" +"SELECT ST_AsEWKT(ST_Boundary(ST_GeomFromEWKT('POLYGON((1 1 1,0 0 1, -1 1 1, " +"1 1 1))')));\n" "\n" "st_asewkt\n" "-----------------------------------\n" "LINESTRING(1 1 1,0 0 1,-1 1 1,1 1 1)\n" "\n" "--Using a 3d multilinestring\n" -"SELECT ST_AsEWKT(ST_Boundary(ST_GeomFromEWKT('MULTILINESTRING((1 1 1,0 0 0.5, -1 1 1),(1 1 0.5,0 0 0.5, -1 1 0.5, 1 1 0.5) )')));\n" +"SELECT ST_AsEWKT(ST_Boundary(ST_GeomFromEWKT('MULTILINESTRING((1 1 1,0 0 " +"0.5, -1 1 1),(1 1 0.5,0 0 0.5, -1 1 0.5, 1 1 0.5) )')));\n" "\n" "st_asewkt\n" "----------\n" @@ -376,8 +385,8 @@ msgstr "" #: reference_accessor.xml:116 #, no-c-format msgid "" -"Return the coordinate dimension of the ST_Geometry " -"value." +"Return the coordinate dimension of the ST_Geometry value." msgstr "" #. Tag: funcprototype @@ -410,7 +419,8 @@ msgstr "" #: reference_accessor.xml:147 #, no-c-format msgid "" -"SELECT ST_CoordDim('CIRCULARSTRING(1 2 3, 1 3 4, 5 6 7, 8 9 10, 11 12 13)');\n" +"SELECT ST_CoordDim('CIRCULARSTRING(1 2 3, 1 3 4, 5 6 7, 8 9 10, 11 12 " +"13)');\n" " ---result--\n" " 3\n" "\n" @@ -448,8 +458,8 @@ msgid "" "The inherent dimension of this Geometry object, which must be less than or " "equal to the coordinate dimension. OGC SPEC s2.1.1.1 - returns 0 for " "POINT, 1 for LINESTRING, 2 for " -"POLYGON, and the largest dimension of the components of a" -" GEOMETRYCOLLECTION. If unknown (empty geometry) null is " +"POLYGON, and the largest dimension of the components of a " +"GEOMETRYCOLLECTION. If unknown (empty geometry) null is " "returned." msgstr "" @@ -496,8 +506,7 @@ msgstr "" #, no-c-format msgid "" "Returns the last point of a LINESTRING or " -"CIRCULARLINESTRING geometry as a " -"POINT." +"CIRCULARLINESTRING geometry as a POINT." msgstr "" #. Tag: funcprototype @@ -539,7 +548,8 @@ msgstr "" #: reference_accessor.xml:246 #, no-c-format msgid "" -"postgis=# SELECT ST_AsText(ST_EndPoint('LINESTRING(1 1, 2 2, 3 3)'::geometry));\n" +"postgis=# SELECT ST_AsText(ST_EndPoint('LINESTRING(1 1, 2 2, 3 3)'::" +"geometry));\n" " st_astext\n" "------------\n" " POINT(3 3)\n" @@ -593,10 +603,9 @@ msgstr "" msgid "" "Returns the float8 minimum bounding box for the supplied geometry, as a " "geometry. The polygon is defined by the corner points of the bounding box " -"((MINX, MINY), " -"(MINX, MAXY), " -"(MAXX, MAXY), " -"(MAXX, MINY), " +"((MINX, MINY), (MINX, MAXY), (MAXX, MAXY), (MAXX, MINY), " "(MINX, MINY)). (PostGIS will add a " "ZMIN/ZMAX coordinate as well)." msgstr "" @@ -649,19 +658,23 @@ msgid "" "(1 row)\n" "\n" "\n" -"SELECT ST_AsText(ST_Envelope('POLYGON((0 0, 0 1, 1.0000001 1, 1.0000001 0, 0 0))'::geometry));\n" +"SELECT ST_AsText(ST_Envelope('POLYGON((0 0, 0 1, 1.0000001 1, 1.0000001 0, 0 " +"0))'::geometry));\n" " st_astext\n" "--------------------------------------------------------------\n" " POLYGON((0 0,0 1,1.00000011920929 1,1.00000011920929 0,0 0))\n" "(1 row)\n" -"SELECT ST_AsText(ST_Envelope('POLYGON((0 0, 0 1, 1.0000000001 1, 1.0000000001 0, 0 0))'::geometry));\n" +"SELECT ST_AsText(ST_Envelope('POLYGON((0 0, 0 1, 1.0000000001 1, " +"1.0000000001 0, 0 0))'::geometry));\n" " st_astext\n" "--------------------------------------------------------------\n" " POLYGON((0 0,0 1,1.00000011920929 1,1.00000011920929 0,0 0))\n" "(1 row)\n" " \n" -"SELECT Box3D(geom), Box2D(geom), ST_AsText(ST_Envelope(geom)) As envelopewkt\n" -" FROM (SELECT 'POLYGON((0 0, 0 1000012333334.34545678, 1.0000001 1, 1.0000001 0, 0 0))'::geometry As geom) As foo;\n" +"SELECT Box3D(geom), Box2D(geom), ST_AsText(ST_Envelope(geom)) As " +"envelopewkt\n" +" FROM (SELECT 'POLYGON((0 0, 0 1000012333334.34545678, 1.0000001 1, " +"1.0000001 0, 0 0))'::geometry As geom) As foo;\n" "\n" "" msgstr "" @@ -690,8 +703,8 @@ msgstr "" msgid "" "geometry ST_BoundingDiagonal " "geometry geom " -"boolean " -"fits=false" +"boolean fits=false" msgstr "" #. Tag: para @@ -717,8 +730,8 @@ msgstr "" #, no-c-format msgid "" "The fits parameter specifies if the best fit is needed. " -"If false, the diagonal of a somewhat larger bounding box can be accepted (is" -" faster to obtain for geometries with a lot of vertices). In any case the " +"If false, the diagonal of a somewhat larger bounding box can be accepted (is " +"faster to obtain for geometries with a lot of vertices). In any case the " "bounding box of the returned diagonal line always covers the input geometry." msgstr "" @@ -760,9 +773,9 @@ msgstr "" #: reference_accessor.xml:368 #, no-c-format msgid "" -", , , , , , " -"" +", , , , , , " msgstr "" #. Tag: refname @@ -824,7 +837,8 @@ msgid "" "FROM sometable;\n" "\n" "--If you have a table of MULTIPOLYGONs\n" -"--and want to return a MULTILINESTRING composed of the exterior rings of each polygon\n" +"--and want to return a MULTILINESTRING composed of the exterior rings of " +"each polygon\n" "SELECT gid, ST_Collect(ST_ExteriorRing(the_geom)) AS erings\n" " FROM (SELECT gid, (ST_Dump(the_geom)).geom As the_geom\n" " FROM sometable) As foo\n" @@ -845,7 +859,8 @@ msgstr "" #. Tag: para #: reference_accessor.xml:420 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -925,7 +940,8 @@ msgid "" "SELECT n, ST_AsEWKT(ST_GeometryN(the_geom, n)) As geomewkt\n" "FROM (\n" "VALUES (ST_GeomFromEWKT('MULTIPOINT(1 2 7, 3 4 7, 5 6 7, 8 9 10)') ),\n" -"( ST_GeomFromEWKT('MULTICURVE(CIRCULARSTRING(2.5 2.5,4.5 2.5, 3.5 3.5), (10 11, 12 11))') )\n" +"( ST_GeomFromEWKT('MULTICURVE(CIRCULARSTRING(2.5 2.5,4.5 2.5, 3.5 3.5), (10 " +"11, 12 11))') )\n" " )As foo(the_geom)\n" " CROSS JOIN generate_series(1,100) n\n" "WHERE n <= ST_NumGeometries(the_geom);\n" @@ -1033,8 +1049,8 @@ msgid "" "Returns the type of the geometry as a string. EG: 'ST_Linestring', " "'ST_Polygon','ST_MultiPolygon' etc. This function differs from " "GeometryType(geometry) in the case of the string and ST in front that is " -"returned, as well as the fact that it will not indicate whether the geometry" -" is measured." +"returned, as well as the fact that it will not indicate whether the geometry " +"is measured." msgstr "" #. Tag: para @@ -1054,7 +1070,8 @@ msgstr "" #: reference_accessor.xml:523 #, no-c-format msgid "" -"SELECT ST_GeometryType(ST_GeomFromText('LINESTRING(77.29 29.07,77.42 29.26,77.27 29.31,77.29 29.07)'));\n" +"SELECT ST_GeometryType(ST_GeomFromText('LINESTRING(77.29 29.07,77.42 " +"29.26,77.27 29.31,77.29 29.07)'));\n" " --result\n" " ST_LineString" msgstr "" @@ -1063,10 +1080,13 @@ msgstr "" #: reference_accessor.xml:525 reference_accessor.xml:527 #, no-c-format msgid "" -"SELECT ST_GeometryType(ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)), \n" -" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 0)), \n" +"SELECT ST_GeometryType(ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 " +"1 1, 0 1 0, 0 0 0)), \n" +" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 " +"1, 0 0 1, 0 0 0)), \n" " ((1 1 0, 1 1 1, 1 0 1, 1 0 0, 1 1 0)), \n" -" ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 1)) )'));\n" +" ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 " +"1, 0 1 1, 0 0 1)) )'));\n" " --result\n" " ST_PolyhedralSurface" msgstr "" @@ -1106,8 +1126,8 @@ msgstr "" #: reference_accessor.xml:544 #, no-c-format msgid "" -"Return the Nth interior linestring ring of the polygon geometry. Return NULL" -" if the geometry is not a polygon or the given N is out of range." +"Return the Nth interior linestring ring of the polygon geometry. Return NULL " +"if the geometry is not a polygon or the given N is out of range." msgstr "" #. Tag: funcprototype @@ -1115,16 +1135,16 @@ msgstr "" #, no-c-format msgid "" "geometry ST_InteriorRingN " -"geometry a_polygon" -" integer n" +"geometry a_polygon " +"integer n" msgstr "" #. Tag: para #: reference_accessor.xml:562 #, no-c-format msgid "" -"Return the Nth interior linestring ring of the polygon geometry. Return NULL" -" if the geometry is not a polygon or the given N is out of range. index " +"Return the Nth interior linestring ring of the polygon geometry. Return NULL " +"if the geometry is not a polygon or the given N is out of range. index " "starts at 1." msgstr "" @@ -1157,8 +1177,8 @@ msgstr "" #: reference_accessor.xml:588 #, no-c-format msgid "" -", , , ," +", , , ," msgstr "" #. Tag: refname @@ -1171,9 +1191,8 @@ msgstr "" #: reference_accessor.xml:603 #, no-c-format msgid "" -"Returns TRUE if the LINESTRING's start" -" and end points are coincident. For Polyhedral surface is closed " -"(volumetric)." +"Returns TRUE if the LINESTRING's start " +"and end points are coincident. For Polyhedral surface is closed (volumetric)." msgstr "" #. Tag: funcprototype @@ -1188,9 +1207,9 @@ msgstr "" #: reference_accessor.xml:621 #, no-c-format msgid "" -"Returns TRUE if the LINESTRING's start" -" and end points are coincident. For Polyhedral Surfaces, it tells you if the" -" surface is areal (open) or volumetric (closed)." +"Returns TRUE if the LINESTRING's start " +"and end points are coincident. For Polyhedral Surfaces, it tells you if the " +"surface is areal (open) or volumetric (closed)." msgstr "" #. Tag: para @@ -1203,9 +1222,8 @@ msgstr "" #: reference_accessor.xml:627 #, no-c-format msgid "" -"SQL-MM defines the result of " -"ST_IsClosed(NULL) to be 0, while " -"PostGIS returns NULL." +"SQL-MM defines the result of ST_IsClosed(NULL) to be 0, while PostGIS returns NULL." msgstr "" #. Tag: title @@ -1230,7 +1248,8 @@ msgid "" " t\n" "(1 row)\n" "\n" -"postgis=# SELECT ST_IsClosed('MULTILINESTRING((0 0, 0 1, 1 1, 0 0),(0 0, 1 1))'::geometry);\n" +"postgis=# SELECT ST_IsClosed('MULTILINESTRING((0 0, 0 1, 1 1, 0 0),(0 0, 1 " +"1))'::geometry);\n" " st_isclosed\n" "-------------\n" " f\n" @@ -1260,10 +1279,13 @@ msgstr "" #, no-c-format msgid "" "-- A cube --\n" -" SELECT ST_IsClosed(ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)), \n" -" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 0)), \n" +" SELECT ST_IsClosed(ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 " +"0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)), \n" +" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 " +"1, 0 0 1, 0 0 0)), \n" " ((1 1 0, 1 1 1, 1 0 1, 1 0 0, 1 1 0)), \n" -" ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 1)) )'));\n" +" ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 " +"1, 0 1 1, 0 0 1)) )'));\n" "\n" " st_isclosed\n" "-------------\n" @@ -1271,8 +1293,10 @@ msgid "" "\n" "\n" " -- Same as cube but missing a side --\n" -" SELECT ST_IsClosed(ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)), \n" -" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 0)), \n" +" SELECT ST_IsClosed(ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 " +"1, 0 1 0, 0 0 0)), \n" +" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 " +"1, 0 0 1, 0 0 0)), \n" " ((1 1 0, 1 1 1, 1 0 1, 1 0 0, 1 1 0)), \n" " ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)) )'));\n" "\n" @@ -1334,8 +1358,8 @@ msgstr "" #, no-c-format msgid "" "This function analyzes the type of the geometry. This means that it will " -"return TRUE on collections that are empty or that contain" -" a single element." +"return TRUE on collections that are empty or that contain " +"a single element." msgstr "" #. Tag: programlisting @@ -1366,7 +1390,8 @@ msgid "" " t\n" "(1 row)\n" "\n" -"postgis=# SELECT ST_IsCollection('GEOMETRYCOLLECTION(POINT(0 0))'::geometry);\n" +"postgis=# SELECT ST_IsCollection('GEOMETRYCOLLECTION(POINT(0 0))'::" +"geometry);\n" " st_iscollection\n" "-------------\n" " t\n" @@ -1383,8 +1408,8 @@ msgstr "" #: reference_accessor.xml:719 #, no-c-format msgid "" -"Returns true if this Geometry is an empty geometrycollection, polygon, point" -" etc." +"Returns true if this Geometry is an empty geometrycollection, polygon, point " +"etc." msgstr "" #. Tag: funcprototype @@ -1407,8 +1432,8 @@ msgstr "" #: reference_accessor.xml:738 #, no-c-format msgid "" -"SQL-MM defines the result of ST_IsEmpty(NULL) to be 0, while PostGIS returns" -" NULL." +"SQL-MM defines the result of ST_IsEmpty(NULL) to be 0, while PostGIS returns " +"NULL." msgstr "" #. Tag: para @@ -1449,7 +1474,8 @@ msgid "" " f\n" "(1 row)\n" "\n" -" SELECT ST_IsEmpty(ST_GeomFromText('POLYGON((1 2, 3 4, 5 6, 1 2))')) = false;\n" +" SELECT ST_IsEmpty(ST_GeomFromText('POLYGON((1 2, 3 4, 5 6, 1 2))')) = " +"false;\n" " ?column?\n" "----------\n" " t\n" @@ -1489,9 +1515,8 @@ msgstr "" #, no-c-format msgid "" "Returns TRUE if this LINESTRING is " -"both " -"(ST_StartPoint(g) " -"~= " +"both (ST_StartPoint(g) ~= " "ST_Endpoint(g)) and (does not self intersect)." msgstr "" @@ -1506,9 +1531,8 @@ msgstr "" #: reference_accessor.xml:789 #, no-c-format msgid "" -"SQL-MM defines the result of " -"ST_IsRing(NULL) to be 0, while " -"PostGIS returns NULL." +"SQL-MM defines the result of ST_IsRing(NULL) to be 0, while PostGIS returns NULL." msgstr "" #. Tag: programlisting @@ -1516,14 +1540,16 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_IsRing(the_geom), ST_IsClosed(the_geom), ST_IsSimple(the_geom)\n" -"FROM (SELECT 'LINESTRING(0 0, 0 1, 1 1, 1 0, 0 0)'::geometry AS the_geom) AS foo;\n" +"FROM (SELECT 'LINESTRING(0 0, 0 1, 1 1, 1 0, 0 0)'::geometry AS the_geom) AS " +"foo;\n" " st_isring | st_isclosed | st_issimple\n" "-----------+-------------+-------------\n" " t | t | t\n" "(1 row)\n" "\n" "SELECT ST_IsRing(the_geom), ST_IsClosed(the_geom), ST_IsSimple(the_geom)\n" -"FROM (SELECT 'LINESTRING(0 0, 0 1, 1 0, 1 1, 0 0)'::geometry AS the_geom) AS foo;\n" +"FROM (SELECT 'LINESTRING(0 0, 0 1, 1 0, 1 1, 0 0)'::geometry AS the_geom) AS " +"foo;\n" " st_isring | st_isclosed | st_issimple\n" "-----------+-------------+-------------\n" " f | t | f\n" @@ -1566,9 +1592,8 @@ msgstr "" msgid "" "Returns true if this Geometry has no anomalous geometric points, such as " "self intersection or self tangency. For more information on the OGC's " -"definition of geometry simplicity and validity, refer to \"Ensuring OpenGIS compliancy of " -"geometries\"" +"definition of geometry simplicity and validity, refer to \"Ensuring OpenGIS compliancy of geometries\"" msgstr "" #. Tag: para @@ -1595,7 +1620,8 @@ msgid "" " t\n" "(1 row)\n" "\n" -" SELECT ST_IsSimple(ST_GeomFromText('LINESTRING(1 1,2 2,2 3.5,1 3,1 2,2 1)'));\n" +" SELECT ST_IsSimple(ST_GeomFromText('LINESTRING(1 1,2 2,2 3.5,1 3,1 2,2 " +"1)'));\n" " st_issimple\n" "-------------\n" " f\n" @@ -1621,11 +1647,11 @@ msgstr "" #, no-c-format msgid "" " boolean ST_IsValid " -"geometry g " -" boolean " -"ST_IsValid geometry " -"g integer " -"flags " +"geometry g boolean ST_IsValid geometry g integer flags " msgstr "" #. Tag: para @@ -1643,8 +1669,8 @@ msgstr "" #: reference_accessor.xml:893 #, no-c-format msgid "" -"SQL-MM defines the result of ST_IsValid(NULL) to be 0, while PostGIS returns" -" NULL." +"SQL-MM defines the result of ST_IsValid(NULL) to be 0, while PostGIS returns " +"NULL." msgstr "" #. Tag: para @@ -1653,8 +1679,8 @@ msgstr "" msgid "" "The version accepting flags is available starting with 2.0.0 and requires " "GEOS >= 3.3.0. Such version does not print a NOTICE explaining the " -"invalidity. Allowed flags are documented in ." +"invalidity. Allowed flags are documented in ." msgstr "" #. Tag: para @@ -1668,7 +1694,8 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_IsValid(ST_GeomFromText('LINESTRING(0 0, 1 1)')) As good_line,\n" -" ST_IsValid(ST_GeomFromText('POLYGON((0 0, 1 1, 1 2, 1 1, 0 0))')) As bad_poly\n" +" ST_IsValid(ST_GeomFromText('POLYGON((0 0, 1 1, 1 2, 1 1, 0 0))')) As " +"bad_poly\n" "--results\n" "NOTICE: Self-intersection at or near point 0 0\n" " good_line | bad_poly\n" @@ -1680,8 +1707,8 @@ msgstr "" #: reference_accessor.xml:919 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -1702,21 +1729,20 @@ msgstr "" #: reference_accessor.xml:936 #, no-c-format msgid "" -" text " -"ST_IsValidReason geometry " -" geomA " -" text " -"ST_IsValidReason geometry " -" geomA integer " -" flags " +" text ST_IsValidReason geometry geomA text " +"ST_IsValidReason geometry geomA integer flags " msgstr "" #. Tag: para #: reference_accessor.xml:952 #, no-c-format msgid "" -"Returns text stating if a geometry is valid or not an if not valid, a reason" -" why." +"Returns text stating if a geometry is valid or not an if not valid, a reason " +"why." msgstr "" #. Tag: para @@ -1731,8 +1757,8 @@ msgstr "" #: reference_accessor.xml:956 #, no-c-format msgid "" -"Allowed flags are documented in ." +"Allowed flags are documented in ." msgstr "" #. Tag: para @@ -1755,13 +1781,17 @@ msgid "" "--First 3 Rejects from a successful quintuplet experiment\n" "SELECT gid, ST_IsValidReason(the_geom) as validity_info\n" "FROM\n" -"(SELECT ST_MakePolygon(ST_ExteriorRing(e.buff), ST_Accum(f.line)) As the_geom, gid\n" -"FROM (SELECT ST_Buffer(ST_MakePoint(x1*10,y1), z1) As buff, x1*10 + y1*100 + z1*1000 As gid\n" +"(SELECT ST_MakePolygon(ST_ExteriorRing(e.buff), ST_Accum(f.line)) As " +"the_geom, gid\n" +"FROM (SELECT ST_Buffer(ST_MakePoint(x1*10,y1), z1) As buff, x1*10 + y1*100 + " +"z1*1000 As gid\n" " FROM generate_series(-4,6) x1\n" " CROSS JOIN generate_series(2,5) y1\n" " CROSS JOIN generate_series(1,8) z1\n" " WHERE x1 > y1*0.5 AND z1 < x1*y1) As e\n" -" INNER JOIN (SELECT ST_Translate(ST_ExteriorRing(ST_Buffer(ST_MakePoint(x1*10,y1), z1)),y1*1, z1*2) As line\n" +" INNER JOIN (SELECT " +"ST_Translate(ST_ExteriorRing(ST_Buffer(ST_MakePoint(x1*10,y1), z1)),y1*1, " +"z1*2) As line\n" " FROM generate_series(-3,6) x1\n" " CROSS JOIN generate_series(2,5) y1\n" " CROSS JOIN generate_series(1,10) z1\n" @@ -1779,7 +1809,8 @@ msgid "" " 5350 | Self-intersection [52 5]\n" "\n" " --simple example\n" -"SELECT ST_IsValidReason('LINESTRING(220227 150406,2220227 150407,222020 150410)');\n" +"SELECT ST_IsValidReason('LINESTRING(220227 150406,2220227 150407,222020 " +"150410)');\n" "\n" " st_isvalidreason\n" "------------------\n" @@ -1810,13 +1841,12 @@ msgstr "" #: reference_accessor.xml:988 #, no-c-format msgid "" -" valid_detail " -"ST_IsValidDetail geometry " -" geom " -" valid_detail " -"ST_IsValidDetail geometry " -" geom integer " -" flags " +" valid_detail ST_IsValidDetail geometry geom valid_detail " +"ST_IsValidDetail geometry geom integer " +"flags " msgstr "" #. Tag: para @@ -1824,8 +1854,8 @@ msgstr "" #, no-c-format msgid "" "Returns a valid_detail row, formed by a boolean (valid) stating if a " -"geometry is valid, a varchar (reason) stating a reason why it is invalid and" -" a geometry (location) pointing out where it is invalid." +"geometry is valid, a varchar (reason) stating a reason why it is invalid and " +"a geometry (location) pointing out where it is invalid." msgstr "" #. Tag: para @@ -1861,15 +1891,20 @@ msgstr "" #, no-c-format msgid "" "--First 3 Rejects from a successful quintuplet experiment\n" -"SELECT gid, reason(ST_IsValidDetail(the_geom)), ST_AsText(location(ST_IsValidDetail(the_geom))) as location \n" +"SELECT gid, reason(ST_IsValidDetail(the_geom)), " +"ST_AsText(location(ST_IsValidDetail(the_geom))) as location \n" "FROM\n" -"(SELECT ST_MakePolygon(ST_ExteriorRing(e.buff), ST_Accum(f.line)) As the_geom, gid\n" -"FROM (SELECT ST_Buffer(ST_MakePoint(x1*10,y1), z1) As buff, x1*10 + y1*100 + z1*1000 As gid\n" +"(SELECT ST_MakePolygon(ST_ExteriorRing(e.buff), ST_Accum(f.line)) As " +"the_geom, gid\n" +"FROM (SELECT ST_Buffer(ST_MakePoint(x1*10,y1), z1) As buff, x1*10 + y1*100 + " +"z1*1000 As gid\n" " FROM generate_series(-4,6) x1\n" " CROSS JOIN generate_series(2,5) y1\n" " CROSS JOIN generate_series(1,8) z1\n" " WHERE x1 > y1*0.5 AND z1 < x1*y1) As e\n" -" INNER JOIN (SELECT ST_Translate(ST_ExteriorRing(ST_Buffer(ST_MakePoint(x1*10,y1), z1)),y1*1, z1*2) As line\n" +" INNER JOIN (SELECT " +"ST_Translate(ST_ExteriorRing(ST_Buffer(ST_MakePoint(x1*10,y1), z1)),y1*1, " +"z1*2) As line\n" " FROM generate_series(-3,6) x1\n" " CROSS JOIN generate_series(2,5) y1\n" " CROSS JOIN generate_series(1,10) z1\n" @@ -1887,7 +1922,8 @@ msgid "" " 5350 | Self-intersection | POINT(52 5)\n" "\n" " --simple example\n" -"SELECT * FROM ST_IsValidDetail('LINESTRING(220227 150406,2220227 150407,222020 150410)');\n" +"SELECT * FROM ST_IsValidDetail('LINESTRING(220227 150406,2220227 " +"150407,222020 150410)');\n" "\n" " valid | reason | location\n" "-------+--------+----------\n" @@ -1958,7 +1994,9 @@ msgstr "" #. Tag: para #: reference_accessor.xml:1086 #, no-c-format -msgid ", , , " +msgid "" +", , , " msgstr "" #. Tag: refname @@ -1971,8 +2009,8 @@ msgstr "" #: reference_accessor.xml:1093 #, no-c-format msgid "" -"Returns coordinate dimension of the geometry as a small int. Values are: 2,3" -" or 4." +"Returns coordinate dimension of the geometry as a small int. Values are: 2,3 " +"or 4." msgstr "" #. Tag: funcprototype @@ -1987,9 +2025,9 @@ msgstr "" #: reference_accessor.xml:1109 #, no-c-format msgid "" -"Returns the coordinate dimension of the geometry. PostGIS supports 2 - (x,y)" -" , 3 - (x,y,z) or 2D with measure - x,y,m, and 4 - 3D with measure space " -"x,y,z,m" +"Returns the coordinate dimension of the geometry. PostGIS supports 2 - (x," +"y) , 3 - (x,y,z) or 2D with measure - x,y,m, and 4 - 3D with measure space x," +"y,z,m" msgstr "" #. Tag: programlisting @@ -2049,12 +2087,14 @@ msgstr "" #: reference_accessor.xml:1156 #, no-c-format msgid "" -"SELECT ST_NPoints(ST_GeomFromText('LINESTRING(77.29 29.07,77.42 29.26,77.27 29.31,77.29 29.07)'));\n" +"SELECT ST_NPoints(ST_GeomFromText('LINESTRING(77.29 29.07,77.42 29.26,77.27 " +"29.31,77.29 29.07)'));\n" "--result\n" "4\n" "\n" "--Polygon in 3D space\n" -"SELECT ST_NPoints(ST_GeomFromEWKT('LINESTRING(77.29 29.07 1,77.42 29.26 0,77.27 29.31 -1,77.29 29.07 3)'))\n" +"SELECT ST_NPoints(ST_GeomFromEWKT('LINESTRING(77.29 29.07 1,77.42 29.26 " +"0,77.27 29.31 -1,77.29 29.07 3)'))\n" "--result\n" "4" msgstr "" @@ -2092,8 +2132,10 @@ msgstr "" #: reference_accessor.xml:1193 #, no-c-format msgid "" -"SELECT ST_NRings(the_geom) As Nrings, ST_NumInteriorRings(the_geom) As ninterrings\n" -" FROM (SELECT ST_GeomFromText('POLYGON((1 2, 3 4, 5 6, 1 2))') As the_geom) As foo;\n" +"SELECT ST_NRings(the_geom) As Nrings, ST_NumInteriorRings(the_geom) As " +"ninterrings\n" +" FROM (SELECT " +"ST_GeomFromText('POLYGON((1 2, 3 4, 5 6, 1 2))') As the_geom) As foo;\n" " nrings | ninterrings\n" "--------+-------------\n" " 1 | 0\n" @@ -2150,13 +2192,16 @@ msgstr "" #: reference_accessor.xml:1239 #, no-c-format msgid "" -"--Prior versions would have returned NULL for this -- in 2.0.0 this returns 1\n" -"SELECT ST_NumGeometries(ST_GeomFromText('LINESTRING(77.29 29.07,77.42 29.26,77.27 29.31,77.29 29.07)'));\n" +"--Prior versions would have returned NULL for this -- in 2.0.0 this returns " +"1\n" +"SELECT ST_NumGeometries(ST_GeomFromText('LINESTRING(77.29 29.07,77.42 " +"29.26,77.27 29.31,77.29 29.07)'));\n" "--result\n" "1\n" "\n" "--Geometry Collection Example - multis count as one geom in a collection\n" -"SELECT ST_NumGeometries(ST_GeomFromEWKT('GEOMETRYCOLLECTION(MULTIPOINT(-2 3 , -2 2),\n" +"SELECT ST_NumGeometries(ST_GeomFromEWKT('GEOMETRYCOLLECTION(MULTIPOINT(-2 " +"3 , -2 2),\n" "LINESTRING(5 5 ,10 10),\n" "POLYGON((-7 4.2,-7.1 5,-7.1 4.3,-7 4.2)))'));\n" "--result\n" @@ -2224,7 +2269,8 @@ msgid "" "FROM sometable;\n" "\n" "--If you have multipolygons\n" -"--And you want to know the total number of interior rings in the MULTIPOLYGON\n" +"--And you want to know the total number of interior rings in the " +"MULTIPOLYGON\n" "SELECT gid, field1, field2, SUM(ST_NumInteriorRings(the_geom)) AS numholes\n" "FROM (SELECT gid, field1, field2, (ST_Dump(the_geom)).geom As the_geom\n" " FROM sometable) As foo\n" @@ -2263,8 +2309,8 @@ msgstr "" #: reference_accessor.xml:1314 #, no-c-format msgid "" -"Return the number of faces on a Polyhedral Surface. Will return null for " -"non-polyhedral geometries." +"Return the number of faces on a Polyhedral Surface. Will return null for non-" +"polyhedral geometries." msgstr "" #. Tag: funcprototype @@ -2279,10 +2325,9 @@ msgstr "" #: reference_accessor.xml:1329 #, no-c-format msgid "" -"Return the number of faces on a Polyhedral Surface. Will return null for " -"non-polyhedral geometries. This is an alias for ST_NumGeometries to support " -"MM naming. Faster to use ST_NumGeometries if you don't care about MM " -"convention." +"Return the number of faces on a Polyhedral Surface. Will return null for non-" +"polyhedral geometries. This is an alias for ST_NumGeometries to support MM " +"naming. Faster to use ST_NumGeometries if you don't care about MM convention." msgstr "" #. Tag: para @@ -2301,10 +2346,13 @@ msgstr "" #: reference_accessor.xml:1342 #, no-c-format msgid "" -"SELECT ST_NumPatches(ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)), \n" -" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 0)), \n" +"SELECT ST_NumPatches(ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 " +"1, 0 1 0, 0 0 0)), \n" +" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 " +"1, 0 0 1, 0 0 0)), \n" " ((1 1 0, 1 1 1, 1 0 1, 1 0 0, 1 1 0)), \n" -" ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 1)) )'));\n" +" ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 " +"1, 0 1 1, 0 0 1)) )'));\n" " --result\n" " 6" msgstr "" @@ -2336,8 +2384,8 @@ msgstr "" msgid "" "Return the number of points in an ST_LineString or ST_CircularString value. " "Prior to 1.4 only works with Linestrings as the specs state. From 1.4 " -"forward this is an alias for ST_NPoints which returns number of vertexes for" -" not just line strings. Consider using ST_NPoints instead which is multi-" +"forward this is an alias for ST_NPoints which returns number of vertexes for " +"not just line strings. Consider using ST_NPoints instead which is multi-" "purpose and works with many geometry types." msgstr "" @@ -2351,7 +2399,8 @@ msgstr "" #: reference_accessor.xml:1383 #, no-c-format msgid "" -"SELECT ST_NumPoints(ST_GeomFromText('LINESTRING(77.29 29.07,77.42 29.26,77.27 29.31,77.29 29.07)'));\n" +"SELECT ST_NumPoints(ST_GeomFromText('LINESTRING(77.29 29.07,77.42 " +"29.26,77.27 29.31,77.29 29.07)'));\n" " --result\n" " 4" msgstr "" @@ -2410,10 +2459,13 @@ msgid "" "--Extract the 2nd face of the polyhedral surface\n" "SELECT ST_AsEWKT(ST_PatchN(geom, 2)) As geomewkt\n" "FROM (\n" -"VALUES (ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)), \n" -" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 0)), \n" +"VALUES (ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 " +"0 0)), \n" +" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, " +"0 0 0)), \n" " ((1 1 0, 1 1 1, 1 0 1, 1 0 0, 1 1 0)), \n" -" ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 1)) )')) ) As foo(geom);\n" +" ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, " +"0 0 1)) )')) ) As foo(geom);\n" "\n" " geomewkt\n" "---+-----------------------------------------\n" @@ -2447,9 +2499,8 @@ msgstr "" #, no-c-format msgid "" "geometry ST_PointN " -"geometry " -"a_linestring integer " -" n" +"geometry a_linestring integer n" msgstr "" #. Tag: para @@ -2504,7 +2555,8 @@ msgid "" "(3 rows)\n" "\n" "--Example circular string\n" -"SELECT ST_AsText(ST_PointN(ST_GeomFromText('CIRCULARSTRING(1 2, 3 2, 1 2)'),2));\n" +"SELECT ST_AsText(ST_PointN(ST_GeomFromText('CIRCULARSTRING(1 2, 3 2, 1 " +"2)'),2));\n" "\n" "st_astext\n" "----------\n" @@ -2545,10 +2597,10 @@ msgstr "" #: reference_accessor.xml:1528 #, no-c-format msgid "" -"spatial_ref_sys table is a table that catalogs all spatial reference systems" -" known to PostGIS and is used for transformations from one spatial reference" -" system to another. So verifying you have the right spatial reference system" -" identifier is important if you plan to ever transform your geometries." +"spatial_ref_sys table is a table that catalogs all spatial reference systems " +"known to PostGIS and is used for transformations from one spatial reference " +"system to another. So verifying you have the right spatial reference system " +"identifier is important if you plan to ever transform your geometries." msgstr "" #. Tag: para @@ -2570,8 +2622,8 @@ msgstr "" #: reference_accessor.xml:1545 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -2601,8 +2653,8 @@ msgstr "" #, no-c-format msgid "" "Returns the first point of a LINESTRING or " -"CIRCULARLINESTRING geometry as a POINT" -" or NULL if the input parameter is not a " +"CIRCULARLINESTRING geometry as a POINT " +"or NULL if the input parameter is not a " "LINESTRING or CIRCULARLINESTRING." msgstr "" @@ -2636,7 +2688,8 @@ msgid "" "(1 row)\n" "\n" "-- circular linestring --\n" -"SELECT ST_AsText(ST_StartPoint('CIRCULARSTRING(5 2,-3 1.999999, -2 1, -4 2, 5 2)'::geometry));\n" +"SELECT ST_AsText(ST_StartPoint('CIRCULARSTRING(5 2,-3 1.999999, -2 1, -4 2, " +"5 2)'::geometry));\n" " st_astext\n" "------------\n" " POINT(5 2)" @@ -2658,8 +2711,8 @@ msgstr "" #: reference_accessor.xml:1602 #, no-c-format msgid "" -"Returns a text summary of the contents of the " -"geometry." +"Returns a text summary of the contents of the geometry." msgstr "" #. Tag: funcsynopsis @@ -2667,10 +2720,10 @@ msgstr "" #, no-c-format msgid "" " text ST_Summary " -"geometry g " -" text " -"ST_Summary geography " -"g " +"geometry g text ST_Summary geography g " msgstr "" #. Tag: para @@ -2741,7 +2794,8 @@ msgstr "" #, no-c-format msgid "" "=# SELECT ST_Summary(ST_GeomFromText('LINESTRING(0 0, 1 1)')) as geom,\n" -" ST_Summary(ST_GeogFromText('POLYGON((0 0, 1 1, 1 2, 1 1, 0 0))')) geog;\n" +" ST_Summary(ST_GeogFromText('POLYGON((0 0, 1 1, 1 2, 1 1, 0 0))')) " +"geog;\n" " geom | geog \n" "-----------------------------+--------------------------\n" " LineString[B] with 2 points | Polygon[BGS] with 1 rings\n" @@ -2750,8 +2804,10 @@ msgid "" "(1 row)\n" "\n" "\n" -"=# SELECT ST_Summary(ST_GeogFromText('LINESTRING(0 0 1, 1 1 1)')) As geog_line,\n" -" ST_Summary(ST_GeomFromText('SRID=4326;POLYGON((0 0 1, 1 1 2, 1 2 3, 1 1 1, 0 0 1))')) As geom_poly;\n" +"=# SELECT ST_Summary(ST_GeogFromText('LINESTRING(0 0 1, 1 1 1)')) As " +"geog_line,\n" +" ST_Summary(ST_GeomFromText('SRID=4326;POLYGON((0 0 1, 1 1 2, 1 2 3, " +"1 1 1, 0 0 1))')) As geom_poly;\n" ";\n" " geog_line | geom_poly\n" "-------------------------------- +--------------------------\n" @@ -2844,8 +2900,8 @@ msgstr "" #, no-c-format msgid "" ", , , , , , " +"linkend=\"ST_XMax\"/>, , , " msgstr "" #. Tag: refname @@ -2858,8 +2914,8 @@ msgstr "" #: reference_accessor.xml:1718 #, no-c-format msgid "" -"Returns X maxima of a bounding box 2d or 3d or a " -"geometry." +"Returns X maxima of a bounding box 2d or 3d or a geometry." msgstr "" #. Tag: funcprototype @@ -2873,8 +2929,7 @@ msgstr "" #. Tag: para #: reference_accessor.xml:1733 #, no-c-format -msgid "" -"Returns X maxima of a bounding box 2d or 3d or a geometry." +msgid "Returns X maxima of a bounding box 2d or 3d or a geometry." msgstr "" #. Tag: para @@ -2883,8 +2938,8 @@ msgstr "" #: reference_accessor.xml:2002 reference_accessor.xml:2089 #, no-c-format msgid "" -"Although this function is only defined for box3d, it will work for box2d and" -" geometry because of the auto-casting behavior defined for geometries and " +"Although this function is only defined for box3d, it will work for box2d and " +"geometry because of the auto-casting behavior defined for geometries and " "box2d. However you can not feed it a geometry or box2d text representation, " "since that will not auto-cast." msgstr "" @@ -2907,12 +2962,14 @@ msgid "" "st_xmax\n" "-------\n" "3\n" -"--Observe THIS DOES NOT WORK because it will try to autocast the string representation to a BOX3D\n" +"--Observe THIS DOES NOT WORK because it will try to autocast the string " +"representation to a BOX3D\n" "SELECT ST_XMax('LINESTRING(1 3, 5 6)');\n" "\n" "--ERROR: BOX3D parser - doesnt start with BOX3D(\n" "\n" -"SELECT ST_XMax(ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 150505 2,220227 150406 3)'));\n" +"SELECT ST_XMax(ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 150505 " +"2,220227 150406 3)'));\n" "st_xmax\n" "--------\n" "220288.248780547" @@ -2922,8 +2979,8 @@ msgstr "" #: reference_accessor.xml:1755 reference_accessor.xml:1800 #, no-c-format msgid "" -", , , , " +", , , , " msgstr "" #. Tag: refname @@ -2936,8 +2993,8 @@ msgstr "" #: reference_accessor.xml:1763 #, no-c-format msgid "" -"Returns X minima of a bounding box 2d or 3d or a " -"geometry." +"Returns X minima of a bounding box 2d or 3d or a geometry." msgstr "" #. Tag: funcprototype @@ -2951,8 +3008,7 @@ msgstr "" #. Tag: para #: reference_accessor.xml:1778 #, no-c-format -msgid "" -"Returns X minima of a bounding box 2d or 3d or a geometry." +msgid "Returns X minima of a bounding box 2d or 3d or a geometry." msgstr "" #. Tag: programlisting @@ -2973,12 +3029,14 @@ msgid "" "st_xmin\n" "-------\n" "-3\n" -"--Observe THIS DOES NOT WORK because it will try to autocast the string representation to a BOX3D\n" +"--Observe THIS DOES NOT WORK because it will try to autocast the string " +"representation to a BOX3D\n" "SELECT ST_XMin('LINESTRING(1 3, 5 6)');\n" "\n" "--ERROR: BOX3D parser - doesnt start with BOX3D(\n" "\n" -"SELECT ST_XMin(ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 150505 2,220227 150406 3)'));\n" +"SELECT ST_XMin(ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 150505 " +"2,220227 150406 3)'));\n" "st_xmin\n" "--------\n" "220186.995121892" @@ -3042,8 +3100,8 @@ msgstr "" #, no-c-format msgid "" ", , , , , , " +"linkend=\"ST_X\"/>, , , " msgstr "" #. Tag: refname @@ -3056,8 +3114,8 @@ msgstr "" #: reference_accessor.xml:1851 #, no-c-format msgid "" -"Returns Y maxima of a bounding box 2d or 3d or a " -"geometry." +"Returns Y maxima of a bounding box 2d or 3d or a geometry." msgstr "" #. Tag: funcprototype @@ -3071,8 +3129,7 @@ msgstr "" #. Tag: para #: reference_accessor.xml:1866 #, no-c-format -msgid "" -"Returns Y maxima of a bounding box 2d or 3d or a geometry." +msgid "Returns Y maxima of a bounding box 2d or 3d or a geometry." msgstr "" #. Tag: programlisting @@ -3093,12 +3150,14 @@ msgid "" "st_ymax\n" "-------\n" "4\n" -"--Observe THIS DOES NOT WORK because it will try to autocast the string representation to a BOX3D\n" +"--Observe THIS DOES NOT WORK because it will try to autocast the string " +"representation to a BOX3D\n" "SELECT ST_YMax('LINESTRING(1 3, 5 6)');\n" "\n" "--ERROR: BOX3D parser - doesnt start with BOX3D(\n" "\n" -"SELECT ST_YMax(ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 150505 2,220227 150406 3)'));\n" +"SELECT ST_YMax(ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 150505 " +"2,220227 150406 3)'));\n" "st_ymax\n" "--------\n" "150506.126829327" @@ -3108,8 +3167,8 @@ msgstr "" #: reference_accessor.xml:1888 #, no-c-format msgid "" -", , , , " +", , , , " msgstr "" #. Tag: refname @@ -3122,8 +3181,8 @@ msgstr "" #: reference_accessor.xml:1896 #, no-c-format msgid "" -"Returns Y minima of a bounding box 2d or 3d or a " -"geometry." +"Returns Y minima of a bounding box 2d or 3d or a geometry." msgstr "" #. Tag: funcprototype @@ -3137,8 +3196,7 @@ msgstr "" #. Tag: para #: reference_accessor.xml:1911 #, no-c-format -msgid "" -"Returns Y minima of a bounding box 2d or 3d or a geometry." +msgid "Returns Y minima of a bounding box 2d or 3d or a geometry." msgstr "" #. Tag: programlisting @@ -3159,12 +3217,14 @@ msgid "" "st_ymin\n" "-------\n" "2\n" -"--Observe THIS DOES NOT WORK because it will try to autocast the string representation to a BOX3D\n" +"--Observe THIS DOES NOT WORK because it will try to autocast the string " +"representation to a BOX3D\n" "SELECT ST_YMin('LINESTRING(1 3, 5 6)');\n" "\n" "--ERROR: BOX3D parser - doesnt start with BOX3D(\n" "\n" -"SELECT ST_YMin(ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 150505 2,220227 150406 3)'));\n" +"SELECT ST_YMin(ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 150505 " +"2,220227 150406 3)'));\n" "st_ymin\n" "--------\n" "150406" @@ -3174,9 +3234,8 @@ msgstr "" #: reference_accessor.xml:1933 #, no-c-format msgid "" -", , , , , " +", , , , , " msgstr "" #. Tag: refname @@ -3224,8 +3283,8 @@ msgstr "" #: reference_accessor.xml:1976 #, no-c-format msgid "" -", , , , , " +", , , , , " msgstr "" #. Tag: refname @@ -3238,8 +3297,8 @@ msgstr "" #: reference_accessor.xml:1984 reference_accessor.xml:2071 #, no-c-format msgid "" -"Returns Z minima of a bounding box 2d or 3d or a " -"geometry." +"Returns Z minima of a bounding box 2d or 3d or a geometry." msgstr "" #. Tag: funcprototype @@ -3274,12 +3333,14 @@ msgid "" "st_zmax\n" "-------\n" "1\n" -"--Observe THIS DOES NOT WORK because it will try to autocast the string representation to a BOX3D\n" +"--Observe THIS DOES NOT WORK because it will try to autocast the string " +"representation to a BOX3D\n" "SELECT ST_ZMax('LINESTRING(1 3 4, 5 6 7)');\n" "\n" "--ERROR: BOX3D parser - doesnt start with BOX3D(\n" "\n" -"SELECT ST_ZMax(ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 150505 2,220227 150406 3)'));\n" +"SELECT ST_ZMax(ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 150505 " +"2,220227 150406 3)'));\n" "st_zmax\n" "--------\n" "3" @@ -3289,9 +3350,8 @@ msgstr "" #: reference_accessor.xml:2021 #, no-c-format msgid "" -", , , , , " +", , , , , " msgstr "" #. Tag: refname @@ -3320,8 +3380,8 @@ msgstr "" #: reference_accessor.xml:2045 #, no-c-format msgid "" -"Returns ZM (dimension semantic) flag of the geometries as a small int." -" Values are: 0=2d, 1=3dm, 2=3dz, 3=4d." +"Returns ZM (dimension semantic) flag of the geometries as a small int. " +"Values are: 0=2d, 1=3dm, 2=3dz, 3=4d." msgstr "" #. Tag: programlisting @@ -3371,8 +3431,7 @@ msgstr "" #. Tag: para #: reference_accessor.xml:2086 #, no-c-format -msgid "" -"Returns Z minima of a bounding box 2d or 3d or a geometry." +msgid "Returns Z minima of a bounding box 2d or 3d or a geometry." msgstr "" #. Tag: programlisting @@ -3393,12 +3452,14 @@ msgid "" "st_zmin\n" "-------\n" "1\n" -"--Observe THIS DOES NOT WORK because it will try to autocast the string representation to a BOX3D\n" +"--Observe THIS DOES NOT WORK because it will try to autocast the string " +"representation to a BOX3D\n" "SELECT ST_ZMin('LINESTRING(1 3 4, 5 6 7)');\n" "\n" "--ERROR: BOX3D parser - doesnt start with BOX3D(\n" "\n" -"SELECT ST_ZMin(ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 150505 2,220227 150406 3)'));\n" +"SELECT ST_ZMin(ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 150505 " +"2,220227 150406 3)'));\n" "st_zmin\n" "--------\n" "1" @@ -3409,6 +3470,6 @@ msgstr "" #, no-c-format msgid "" ", , , , , , " +"linkend=\"ST_XMax\"/>, , , " msgstr "" diff --git a/doc/po/de_DE/reference_constructor.xml.po b/doc/po/de_DE/reference_constructor.xml.po index 30a38d255..4228b6a92 100644 --- a/doc/po/de_DE/reference_constructor.xml.po +++ b/doc/po/de_DE/reference_constructor.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:23+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -32,8 +33,7 @@ msgstr "" #, no-c-format msgid "" "Construct a Polygon given an arbitrary collection of closed " -"linestrings as a MultiLineString Well-Known text " -"representation." +"linestrings as a MultiLineString Well-Known text representation." msgstr "" #. Tag: funcprototype @@ -172,8 +172,8 @@ msgstr "" #: reference_constructor.xml:56 #, no-c-format msgid "" -"Construct a MultiPolygon given an arbitrary collection of closed linestrings" -" as a MultiLineString text representation Well-Known text representation." +"Construct a MultiPolygon given an arbitrary collection of closed linestrings " +"as a MultiLineString text representation Well-Known text representation." msgstr "" #. Tag: funcprototype @@ -200,9 +200,8 @@ msgid "" "Throws an error if WKT is not a MULTILINESTRING. Forces MULTIPOLYGON output " "even when result is really only composed by a single POLYGON; use ST_BdPolyFromText if you're sure a " -"single POLYGON will result from operation, or see ST_BuildArea() for a postgis-specific " -"approach." +"single POLYGON will result from operation, or see ST_BuildArea() for a postgis-specific approach." msgstr "" #. Tag: para @@ -290,8 +289,8 @@ msgstr "" #: reference_constructor.xml:141 #, no-c-format msgid "" -", , " +", , " msgstr "" #. Tag: refname @@ -331,7 +330,8 @@ msgstr "" msgid "" "--- converting lon lat coords to geography\n" "ALTER TABLE sometable ADD COLUMN geog geography(POINT,4326);\n" -"UPDATE sometable SET geog = ST_GeogFromText('SRID=4326;POINT(' || lon || ' ' || lat || ')');\n" +"UPDATE sometable SET geog = ST_GeogFromText('SRID=4326;POINT(' || lon || ' ' " +"|| lat || ')');\n" "\n" "--- specify a geography point using EPSG:4267, NAD27\n" "SELECT ST_AsEWKT(ST_GeogFromText('SRID=4267;POINT(-77.0092 38.889588)'));" @@ -421,9 +421,13 @@ msgstr "" #: reference_constructor.xml:232 #, no-c-format msgid "" -"--Although bytea rep contains single \\, these need to be escaped when inserting into a table\n" +"--Although bytea rep contains single \\, these need to be escaped when " +"inserting into a table\n" "SELECT ST_AsText(\n" -"ST_GeogFromWKB(E'\\\\001\\\\002\\\\000\\\\000\\\\000\\\\002\\\\000\\\\000\\\\000\\\\037\\\\205\\\\353Q\\\\270~\\\\\\\\\\\\300\\\\323Mb\\\\020X\\\\231C@\\\\020X9\\\\264\\\\310~\\\\\\\\\\\\300)\\\\\\\\\\\\217\\\\302\\\\365\\\\230C@')\n" +"ST_GeogFromWKB(E'\\\\001\\\\002\\\\000\\\\000\\\\000\\\\002\\\\000\\\\000\\" +"\\000\\\\037\\\\205\\\\353Q\\\\270~\\\\\\\\\\\\300\\\\323Mb\\\\020X\\\\231C@" +"\\\\020X9\\\\264\\\\310~\\\\\\\\\\\\300)\\\\\\\\\\\\217\\\\302\\\\365\\" +"\\230C@')\n" ");\n" " st_astext\n" "------------------------------------------------------\n" @@ -447,9 +451,9 @@ msgstr "" #: reference_constructor.xml:244 #, no-c-format msgid "" -"Creates a geometry instance from a TWKB (\"Tiny Well-" -"Known Binary\") geometry representation." +"Creates a geometry instance from a TWKB (\"Tiny Well-Known Binary\") " +"geometry representation." msgstr "" #. Tag: funcprototype @@ -474,7 +478,8 @@ msgstr "" #: reference_constructor.xml:269 #, no-c-format msgid "" -"SELECT ST_AsText(ST_GeomFromTWKB(ST_AsTWKB('LINESTRING(126 34, 127 35)'::geometry)));\n" +"SELECT ST_AsText(ST_GeomFromTWKB(ST_AsTWKB('LINESTRING(126 34, 127 35)'::" +"geometry)));\n" "\n" " st_astext\n" "-----------------------------\n" @@ -501,21 +506,20 @@ msgstr "" #: reference_constructor.xml:282 #, no-c-format msgid "" -"Makes a collection Geometry from collection WKT with the given SRID. If SRID" -" is not give, it defaults to 0." +"Makes a collection Geometry from collection WKT with the given SRID. If SRID " +"is not give, it defaults to 0." msgstr "" #. Tag: funcsynopsis #: reference_constructor.xml:287 #, no-c-format msgid "" -" geometry " -"ST_GeomCollFromText text " -" WKT integer " -" srid " -" geometry " -"ST_GeomCollFromText text " -" WKT " +" geometry ST_GeomCollFromText text WKT " +"integer srid geometry " +"ST_GeomCollFromText text WKT " msgstr "" #. Tag: para @@ -611,8 +615,7 @@ msgstr "" #: reference_constructor.xml:360 reference_constructor.xml:408 #: reference_constructor.xml:537 reference_constructor.xml:684 #, no-c-format -msgid "" -"Enhanced: 2.0.0 support for Polyhedral surfaces and TIN was introduced." +msgid "Enhanced: 2.0.0 support for Polyhedral surfaces and TIN was introduced." msgstr "" #. Tag: para @@ -661,7 +664,8 @@ msgstr "" #: reference_constructor.xml:373 #, no-c-format msgid "" -"SELECT ST_GeomFromEWKB(E'\\\\001\\\\002\\\\000\\\\000 \\\\255\\\\020\\\\000\\\\000\\\\003\\\\000\\\\000\\\\000\\\\344J=\n" +"SELECT ST_GeomFromEWKB(E'\\\\001\\\\002\\\\000\\\\000 \\\\255\\\\020\\\\000\\" +"\\000\\\\003\\\\000\\\\000\\\\000\\\\344J=\n" "\\\\013B\\\\312Q\\\\300n\\\\303(\\\\010\\\\036!E@''\\\\277E''K\n" "\\\\312Q\\\\300\\\\366{b\\\\235*!E@\\\\225|\\\\354.P\\\\312Q\n" "\\\\300p\\\\231\\\\323e1!E@');" @@ -683,8 +687,10 @@ msgstr "" #, no-c-format msgid "" "set standard_conforming_strings = on;\n" -"SELECT ST_GeomFromEWKB('\\001\\002\\000\\000 \\255\\020\\000\\000\\003\\000\\000\\000\\344J=\\012\\013B\n" -" \\312Q\\300n\\303(\\010\\036!E@''\\277E''K\\012\\312Q\\300\\366{b\\235*!E@\\225|\\354.P\\312Q\\012\\300p\\231\\323e1')" +"SELECT ST_GeomFromEWKB('\\001\\002\\000\\000 " +"\\255\\020\\000\\000\\003\\000\\000\\000\\344J=\\012\\013B\n" +" \\312Q\\300n\\303(\\010\\036!E@''\\277E''K\\012\\312Q\\300\\366{b\\235*!" +"E@\\225|\\354.P\\312Q\\012\\300p\\231\\323e1')" msgstr "" #. Tag: para @@ -735,15 +741,20 @@ msgstr "" #: reference_constructor.xml:417 #, no-c-format msgid "" -"SELECT ST_GeomFromEWKT('SRID=4269;LINESTRING(-71.160281 42.258729,-71.160837 42.259113,-71.161144 42.25932)');\n" -"SELECT ST_GeomFromEWKT('SRID=4269;MULTILINESTRING((-71.160281 42.258729,-71.160837 42.259113,-71.161144 42.25932))');\n" +"SELECT ST_GeomFromEWKT('SRID=4269;LINESTRING(-71.160281 42.258729,-71.160837 " +"42.259113,-71.161144 42.25932)');\n" +"SELECT ST_GeomFromEWKT('SRID=4269;MULTILINESTRING((-71.160281 " +"42.258729,-71.160837 42.259113,-71.161144 42.25932))');\n" "\n" "SELECT ST_GeomFromEWKT('SRID=4269;POINT(-71.064544 42.28787)');\n" "\n" -"SELECT ST_GeomFromEWKT('SRID=4269;POLYGON((-71.1776585052917 42.3902909739571,-71.1776820268866 42.3903701743239,\n" -"-71.1776063012595 42.3903825660754,-71.1775826583081 42.3903033653531,-71.1776585052917 42.3902909739571))');\n" +"SELECT ST_GeomFromEWKT('SRID=4269;POLYGON((-71.1776585052917 " +"42.3902909739571,-71.1776820268866 42.3903701743239,\n" +"-71.1776063012595 42.3903825660754,-71.1775826583081 " +"42.3903033653531,-71.1776585052917 42.3902909739571))');\n" "\n" -"SELECT ST_GeomFromEWKT('SRID=4269;MULTIPOLYGON(((-71.1031880899493 42.3152774590236,\n" +"SELECT ST_GeomFromEWKT('SRID=4269;MULTIPOLYGON(((-71.1031880899493 " +"42.3152774590236,\n" "-71.1031627617667 42.3152960829043,-71.102923838298 42.3149156848307,\n" "-71.1023097974109 42.3151969047397,-71.1019285062273 42.3147384934248,\n" "-71.102505233663 42.3144722937587,-71.10277487471 42.3141658254797,\n" @@ -765,7 +776,8 @@ msgid "" "-71.1032580383161 42.3152269126061,-71.103223066939 42.3152517403219,\n" "-71.1031880899493 42.3152774590236)),\n" "((-71.1043632495873 42.315113108546,-71.1043583974082 42.3151211109857,\n" -"-71.1043443253471 42.3150676015829,-71.1043850704575 42.3150793250568,-71.1043632495873 42.315113108546)))');" +"-71.1043443253471 42.3150676015829,-71.1043850704575 " +"42.3150793250568,-71.1043632495873 42.315113108546)))');" msgstr "" #. Tag: programlisting @@ -773,7 +785,8 @@ msgstr "" #, no-c-format msgid "" "--3d circular string\n" -"SELECT ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 150505 2,220227 150406 3)');" +"SELECT ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 150505 " +"2,220227 150406 3)');" msgstr "" #. Tag: programlisting @@ -794,7 +807,8 @@ msgstr "" #. Tag: para #: reference_constructor.xml:423 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -815,13 +829,12 @@ msgstr "" #: reference_constructor.xml:432 #, no-c-format msgid "" -" geometry " -"ST_GeometryFromText text " -" WKT " -" geometry " -"ST_GeometryFromText text " -" WKT integer " -" srid " +" geometry ST_GeometryFromText text WKT " +" geometry " +"ST_GeometryFromText text WKT integer " +"srid " msgstr "" #. Tag: para @@ -889,17 +902,21 @@ msgid "" "" msgstr "" @@ -907,8 +924,8 @@ msgstr "" #: reference_constructor.xml:492 #, no-c-format msgid "" -",, " +",, " msgstr "" #. Tag: refname @@ -921,21 +938,20 @@ msgstr "" #: reference_constructor.xml:499 #, no-c-format msgid "" -"Takes as input GML representation of geometry and outputs a PostGIS geometry" -" object" +"Takes as input GML representation of geometry and outputs a PostGIS geometry " +"object" msgstr "" #. Tag: funcsynopsis #: reference_constructor.xml:503 #, no-c-format msgid "" -" geometry " +" geometry ST_GeomFromGML text geomgml geometry " "ST_GeomFromGML text " -"geomgml " -"geometry ST_GeomFromGML " -"text geomgml " -"integer srid " -"" +"geomgml integer " +"srid " msgstr "" #. Tag: para @@ -959,10 +975,10 @@ msgstr "" msgid "" "OGC GML versions supported: GML 3.2.1 " "Namespace GML 3.1.1 Simple Features " -"profile SF-2 (with GML 3.1.0 and 3.0.0 backward compatibility) " -" GML 2.1.2 " -"OGC GML standards, cf: http://www.opengeospatial.org/standards/gml:" +"profile SF-2 (with GML 3.1.0 and 3.0.0 backward compatibility) GML 2.1.2 OGC " +"GML standards, cf: http://www.opengeospatial.org/standards/gml:" msgstr "" #. Tag: para @@ -1000,8 +1016,8 @@ msgstr "" #: reference_constructor.xml:546 #, no-c-format msgid "" -"ST_GeomFromGML function is not pedantic about an explicit GML namespace. You" -" could avoid to mention it explicitly for common usages. But you need it if " +"ST_GeomFromGML function is not pedantic about an explicit GML namespace. You " +"could avoid to mention it explicitly for common usages. But you need it if " "you want to use XLink feature inside GML." msgstr "" @@ -1024,7 +1040,8 @@ msgid "" "SELECT ST_GeomFromGML('\n" " \n" -" -71.16028,42.258729 -71.160837,42.259112 -71.161143,42.25932\n" +" -71.16028,42.258729 -71.160837,42.259112 " +"-71.161143,42.25932\n" " \n" " ']]>);" msgstr "" @@ -1041,14 +1058,17 @@ msgstr "" msgid "" "SELECT \n" " \n" -" 42.258729 -71.16028\n" +" 42.258729 " +"-71.16028\n" " \n" " 42.259112 -71.160837\n" " \n" -" \n" +" \n" " \n" " ');]]>);" msgstr "" @@ -1068,32 +1088,38 @@ msgid "" "\n" " \n" " \n" -" 0 0 0 0 0 1 0 1 1 0 1 0 0 0 0\n" +" 0 0 0 0 0 1 0 1 1 0 1 " +"0 0 0 0\n" " \n" " \n" " \n" " \n" -" 0 0 0 0 1 0 1 1 0 1 0 0 0 0 0\n" +" 0 0 0 0 1 0 1 1 " +"0 1 0 0 0 0 0\n" " \n" " \n" " \n" " \n" -" 0 0 0 1 0 0 1 0 1 0 0 1 0 0 0\n" +" 0 0 0 1 0 0 1 0 " +"1 0 0 1 0 0 0\n" " \n" " \n" " \n" " \n" -" 1 1 0 1 1 1 1 0 1 1 0 0 1 1 0\n" +" 1 1 0 1 1 1 1 0 " +"1 1 0 0 1 1 0\n" " \n" " \n" " \n" " \n" -" 0 1 0 0 1 1 1 1 1 1 1 0 0 1 0\n" +" 0 1 0 0 1 1 1 1 " +"1 1 1 0 0 1 0\n" " \n" " \n" " \n" " \n" -" 0 0 1 1 0 1 1 1 1 0 1 1 0 0 1\n" +" 0 0 1 1 0 1 1 1 " +"1 0 1 1 0 0 1\n" " \n" " \n" "\n" @@ -1161,16 +1187,17 @@ msgstr "" #, no-c-format msgid "" "If you do not have JSON-C enabled, support you will get an error notice " -"instead of seeing an output. To enable JSON-C, run configure --with-" -"jsondir=/path/to/json-c. See " -"for details." +"instead of seeing an output. To enable JSON-C, run configure --with-jsondir=/" +"path/to/json-c. See for " +"details." msgstr "" #. Tag: programlisting #: reference_constructor.xml:603 #, no-c-format msgid "" -"SELECT ST_AsText(ST_GeomFromGeoJSON('{\"type\":\"Point\",\"coordinates\":[-48.23456,20.12345]}')) As wkt;\n" +"SELECT ST_AsText(ST_GeomFromGeoJSON('{\"type\":\"Point\",\"coordinates\":" +"[-48.23456,20.12345]}')) As wkt;\n" "wkt\n" "------\n" "POINT(-48.23456 20.12345)" @@ -1181,7 +1208,8 @@ msgstr "" #, no-c-format msgid "" "-- a 3D linestring\n" -"SELECT ST_AsText(ST_GeomFromGeoJSON('{\"type\":\"LineString\",\"coordinates\":[[1,2,3],[4,5,6],[7,8,9]]}')) As wkt;\n" +"SELECT ST_AsText(ST_GeomFromGeoJSON('{\"type\":\"LineString\",\"coordinates" +"\":[[1,2,3],[4,5,6],[7,8,9]]}')) As wkt;\n" "\n" "wkt\n" "-------------------\n" @@ -1192,8 +1220,8 @@ msgstr "" #: reference_constructor.xml:610 #, no-c-format msgid "" -", , " +", , " msgstr "" #. Tag: refname @@ -1206,8 +1234,8 @@ msgstr "" #: reference_constructor.xml:617 #, no-c-format msgid "" -"Takes as input KML representation of geometry and outputs a PostGIS geometry" -" object" +"Takes as input KML representation of geometry and outputs a PostGIS geometry " +"object" msgstr "" #. Tag: funcprototype @@ -1239,7 +1267,8 @@ msgstr "" msgid "" "OGC KML versions supported: KML 2.2.0 " "Namespace OGC KML standards, cf: http://www.opengeospatial.org/standards/kml:" +"url=\"http://www.opengeospatial.org/standards/kml\">http://www." +"opengeospatial.org/standards/kml:" msgstr "" #. Tag: para @@ -1289,12 +1318,12 @@ msgstr "" #: reference_constructor.xml:668 #, no-c-format msgid "" -" geometry ST_GMLToSQL" -" text geomgml " -" geometry " -"ST_GMLToSQL text " -"geomgml integer " -"srid " +" geometry ST_GMLToSQL " +"text geomgml geometry ST_GMLToSQL text geomgml integer srid " msgstr "" #. Tag: para @@ -1327,13 +1356,12 @@ msgstr "" #: reference_constructor.xml:699 #, no-c-format msgid "" -" geometry " +" geometry ST_GeomFromText text WKT " +" geometry " "ST_GeomFromText text " -"WKT " -"geometry ST_GeomFromText " -"text WKT " -"integer srid " -"" +"WKT integer " +"srid " msgstr "" #. Tag: para @@ -1375,15 +1403,20 @@ msgstr "" #: reference_constructor.xml:735 #, no-c-format msgid "" -"SELECT ST_GeomFromText('LINESTRING(-71.160281 42.258729,-71.160837 42.259113,-71.161144 42.25932)');\n" -"SELECT ST_GeomFromText('LINESTRING(-71.160281 42.258729,-71.160837 42.259113,-71.161144 42.25932)',4269);\n" +"SELECT ST_GeomFromText('LINESTRING(-71.160281 42.258729,-71.160837 " +"42.259113,-71.161144 42.25932)');\n" +"SELECT ST_GeomFromText('LINESTRING(-71.160281 42.258729,-71.160837 " +"42.259113,-71.161144 42.25932)',4269);\n" "\n" -"SELECT ST_GeomFromText('MULTILINESTRING((-71.160281 42.258729,-71.160837 42.259113,-71.161144 42.25932))');\n" +"SELECT ST_GeomFromText('MULTILINESTRING((-71.160281 42.258729,-71.160837 " +"42.259113,-71.161144 42.25932))');\n" "\n" "SELECT ST_GeomFromText('POINT(-71.064544 42.28787)');\n" "\n" -"SELECT ST_GeomFromText('POLYGON((-71.1776585052917 42.3902909739571,-71.1776820268866 42.3903701743239,\n" -"-71.1776063012595 42.3903825660754,-71.1775826583081 42.3903033653531,-71.1776585052917 42.3902909739571))');\n" +"SELECT ST_GeomFromText('POLYGON((-71.1776585052917 " +"42.3902909739571,-71.1776820268866 42.3903701743239,\n" +"-71.1776063012595 42.3903825660754,-71.1775826583081 " +"42.3903033653531,-71.1776585052917 42.3902909739571))');\n" "\n" "SELECT ST_GeomFromText('MULTIPOLYGON(((-71.1031880899493 42.3152774590236,\n" "-71.1031627617667 42.3152960829043,-71.102923838298 42.3149156848307,\n" @@ -1407,9 +1440,11 @@ msgid "" "-71.1032580383161 42.3152269126061,-71.103223066939 42.3152517403219,\n" "-71.1031880899493 42.3152774590236)),\n" "((-71.1043632495873 42.315113108546,-71.1043583974082 42.3151211109857,\n" -"-71.1043443253471 42.3150676015829,-71.1043850704575 42.3150793250568,-71.1043632495873 42.315113108546)))',4326);\n" +"-71.1043443253471 42.3150676015829,-71.1043850704575 " +"42.3150793250568,-71.1043632495873 42.315113108546)))',4326);\n" "\n" -"SELECT ST_GeomFromText('CIRCULARSTRING(220268 150415,220227 150505,220227 150406)');" +"SELECT ST_GeomFromText('CIRCULARSTRING(220268 150415,220227 150505,220227 " +"150406)');" msgstr "" #. Tag: para @@ -1428,21 +1463,20 @@ msgstr "" #: reference_constructor.xml:746 #, no-c-format msgid "" -"Creates a geometry instance from a Well-Known Binary geometry representation" -" (WKB) and optional SRID." +"Creates a geometry instance from a Well-Known Binary geometry representation " +"(WKB) and optional SRID." msgstr "" #. Tag: funcsynopsis #: reference_constructor.xml:751 reference_constructor.xml:1774 #, no-c-format msgid "" -" geometry " +" geometry ST_GeomFromWKB bytea geom geometry " "ST_GeomFromWKB bytea " -"geom " -"geometry ST_GeomFromWKB " -"bytea geom " -"integer srid " -"" +"geom integer " +"srid " msgstr "" #. Tag: para @@ -1479,10 +1513,14 @@ msgstr "" #: reference_constructor.xml:784 #, no-c-format msgid "" -"--Although bytea rep contains single \\, these need to be escaped when inserting into a table \n" +"--Although bytea rep contains single \\, these need to be escaped when " +"inserting into a table \n" " -- unless standard_conforming_strings is set to on.\n" "SELECT ST_AsEWKT(\n" -"ST_GeomFromWKB(E'\\\\001\\\\002\\\\000\\\\000\\\\000\\\\002\\\\000\\\\000\\\\000\\\\037\\\\205\\\\353Q\\\\270~\\\\\\\\\\\\300\\\\323Mb\\\\020X\\\\231C@\\\\020X9\\\\264\\\\310~\\\\\\\\\\\\300)\\\\\\\\\\\\217\\\\302\\\\365\\\\230C@',4326)\n" +"ST_GeomFromWKB(E'\\\\001\\\\002\\\\000\\\\000\\\\000\\\\002\\\\000\\\\000\\" +"\\000\\\\037\\\\205\\\\353Q\\\\270~\\\\\\\\\\\\300\\\\323Mb\\\\020X\\\\231C@" +"\\\\020X9\\\\264\\\\310~\\\\\\\\\\\\300)\\\\\\\\\\\\217\\\\302\\\\365\\" +"\\230C@',4326)\n" ");\n" " st_asewkt\n" "------------------------------------------------------\n" @@ -1525,8 +1563,8 @@ msgstr "" msgid "" "geometry ST_LineFromEncodedPolyline " "text polyline " -"integer " -"precision=5" +"integer precision=5" msgstr "" #. Tag: para @@ -1539,8 +1577,8 @@ msgstr "" #: reference_constructor.xml:817 #, no-c-format msgid "" -"See " -"http://developers.google.com/maps/documentation/utilities/polylinealgorithm" +"See http://developers.google.com/maps/documentation/utilities/" +"polylinealgorithm" msgstr "" #. Tag: programlisting @@ -1548,7 +1586,8 @@ msgstr "" #, no-c-format msgid "" "--Create a line string from a polyline\n" -"SELECT ST_AsEWKT(ST_LineFromEncodedPolyline('_p~iF~ps|U_ulLnnqC_mqNvxq`@'));\n" +"SELECT ST_AsEWKT(ST_LineFromEncodedPolyline('_p~iF~ps|" +"U_ulLnnqC_mqNvxq`@'));\n" "--result--\n" "LINESTRING(-120.2 38.5,-120.95 40.7,-126.453 43.252)" msgstr "" @@ -1571,8 +1610,8 @@ msgstr "" #, no-c-format msgid "" "geometry ST_LineFromMultiPoint " -"geometry " -"aMultiPoint" +"geometry aMultiPoint" msgstr "" #. Tag: para @@ -1586,7 +1625,8 @@ msgstr "" #, no-c-format msgid "" "--Create a 3d line string from a 3d multipoint\n" -"SELECT ST_AsEWKT(ST_LineFromMultiPoint(ST_GeomFromEWKT('MULTIPOINT(1 2 3, 4 5 6, 7 8 9)')));\n" +"SELECT ST_AsEWKT(ST_LineFromMultiPoint(ST_GeomFromEWKT('MULTIPOINT(1 2 3, 4 " +"5 6, 7 8 9)')));\n" "--result--\n" "LINESTRING(1 2 3,4 5 6,7 8 9)" msgstr "" @@ -1607,21 +1647,20 @@ msgstr "" #: reference_constructor.xml:877 #, no-c-format msgid "" -"Makes a Geometry from WKT representation with the given SRID. If SRID is not" -" given, it defaults to 0." +"Makes a Geometry from WKT representation with the given SRID. If SRID is not " +"given, it defaults to 0." msgstr "" #. Tag: funcsynopsis #: reference_constructor.xml:882 #, no-c-format msgid "" -" geometry " +" geometry ST_LineFromText text WKT " +" geometry " "ST_LineFromText text " -"WKT " -"geometry ST_LineFromText " -"text WKT " -"integer srid " -"" +"WKT integer " +"srid " msgstr "" #. Tag: para @@ -1657,7 +1696,8 @@ msgstr "" #: reference_constructor.xml:922 #, no-c-format msgid "" -"SELECT ST_LineFromText('LINESTRING(1 2, 3 4)') AS aline, ST_LineFromText('POINT(1 2)') AS null_return;\n" +"SELECT ST_LineFromText('LINESTRING(1 2, 3 4)') AS aline, " +"ST_LineFromText('POINT(1 2)') AS null_return;\n" "aline | null_return\n" "------------------------------------------------\n" "010200000002000000000000000000F ... | t" @@ -1679,13 +1719,12 @@ msgstr "" #: reference_constructor.xml:941 #, no-c-format msgid "" -" geometry " -"ST_LineFromWKB bytea " -"WKB " -"geometry ST_LineFromWKB " -"bytea WKB " -"integer srid " -"" +" geometry ST_LineFromWKB bytea WKB " +" geometry ST_LineFromWKB bytea WKB integer srid " msgstr "" #. Tag: para @@ -1693,10 +1732,10 @@ msgstr "" #, no-c-format msgid "" "The ST_LineFromWKB function, takes a well-known binary " -"representation of geometry and a Spatial Reference System ID " -"(SRID) and creates an instance of the appropriate " -"geometry type - in this case, a LINESTRING geometry. This" -" function plays the role of the Geometry Factory in SQL." +"representation of geometry and a Spatial Reference System ID (SRID) and creates an instance of the appropriate geometry type - in this " +"case, a LINESTRING geometry. This function plays the role " +"of the Geometry Factory in SQL." msgstr "" #. Tag: para @@ -1712,10 +1751,10 @@ msgstr "" #: reference_constructor.xml:974 #, no-c-format msgid "" -"If you know all your geometries are LINESTRINGs, its more" -" efficient to just use . This function " -"just calls and adds additional validation" -" that it returns a linestring." +"If you know all your geometries are LINESTRINGs, its more " +"efficient to just use . This function just " +"calls and adds additional validation that " +"it returns a linestring." msgstr "" #. Tag: para @@ -1728,8 +1767,10 @@ msgstr "" #: reference_constructor.xml:990 #, no-c-format msgid "" -"SELECT ST_LineFromWKB(ST_AsBinary(ST_GeomFromText('LINESTRING(1 2, 3 4)'))) AS aline,\n" -" ST_LineFromWKB(ST_AsBinary(ST_GeomFromText('POINT(1 2)'))) IS NULL AS null_return;\n" +"SELECT ST_LineFromWKB(ST_AsBinary(ST_GeomFromText('LINESTRING(1 2, 3 4)'))) " +"AS aline,\n" +" ST_LineFromWKB(ST_AsBinary(ST_GeomFromText('POINT(1 2)'))) " +"IS NULL AS null_return;\n" "aline | null_return\n" "------------------------------------------------\n" "010200000002000000000000000000F ... | t" @@ -1757,13 +1798,12 @@ msgstr "" #: reference_constructor.xml:1009 #, no-c-format msgid "" -" geometry " -"ST_LinestringFromWKB bytea " -" WKB " -" geometry " -"ST_LinestringFromWKB bytea " -" WKB integer " -" srid " +" geometry ST_LinestringFromWKB bytea WKB " +" geometry " +"ST_LinestringFromWKB bytea WKB integer " +"srid " msgstr "" #. Tag: para @@ -1773,8 +1813,8 @@ msgid "" "The ST_LinestringFromWKB function, takes a well-known " "binary representation of geometry and a Spatial Reference System ID " "(SRID) and creates an instance of the appropriate " -"geometry type - in this case, a LINESTRING geometry. This" -" function plays the role of the Geometry Factory in SQL." +"geometry type - in this case, a LINESTRING geometry. This " +"function plays the role of the Geometry Factory in SQL." msgstr "" #. Tag: para @@ -1783,8 +1823,8 @@ msgstr "" msgid "" "If an SRID is not specified, it defaults to 0. NULL is " "returned if the input bytea does not represent a " -"LINESTRING geometry. This an alias for ." +"LINESTRING geometry. This an alias for ." msgstr "" #. Tag: para @@ -1798,9 +1838,9 @@ msgstr "" #, no-c-format msgid "" "If you know all your geometries are LINESTRINGs, it's " -"more efficient to just use . This function" -" just calls and adds additional " -"validation that it returns a LINESTRING." +"more efficient to just use . This function " +"just calls and adds additional validation " +"that it returns a LINESTRING." msgstr "" #. Tag: programlisting @@ -1842,9 +1882,9 @@ msgstr "" #, no-c-format msgid "" "box2d ST_MakeBox2D " -"geometry " -"pointLowLeft geometry " -" pointUpRight" +"geometry pointLowLeft geometry pointUpRight" msgstr "" #. Tag: para @@ -1859,11 +1899,14 @@ msgstr "" #: reference_constructor.xml:1094 #, no-c-format msgid "" -"--Return all features that fall reside or partly reside in a US national atlas coordinate bounding box\n" -"--It is assumed here that the geometries are stored with SRID = 2163 (US National atlas equal area)\n" +"--Return all features that fall reside or partly reside in a US national " +"atlas coordinate bounding box\n" +"--It is assumed here that the geometries are stored with SRID = 2163 (US " +"National atlas equal area)\n" "SELECT feature_id, feature_name, the_geom\n" "FROM features\n" -"WHERE the_geom && ST_SetSRID(ST_MakeBox2D(ST_Point(-989502.1875, 528439.5625),\n" +"WHERE the_geom && ST_SetSRID(ST_MakeBox2D(ST_Point(-989502.1875, " +"528439.5625),\n" " ST_Point(-987121.375 ,529933.1875)),2163)" msgstr "" @@ -1892,9 +1935,8 @@ msgstr "" #, no-c-format msgid "" "box3d ST_3DMakeBox " -"geometry " -"point3DLowLeftBottom " -"geometry " +"geometry point3DLowLeftBottom geometry " "point3DUpRightTop" msgstr "" @@ -1950,14 +1992,13 @@ msgstr "" #: reference_constructor.xml:1160 #, no-c-format msgid "" -" geometry ST_MakeLine" -" geometry set geoms" -" geometry " -"ST_MakeLine geometry " -"geom1 geometry " -"geom2 " -"geometry ST_MakeLine " -"geometry[] " +" geometry ST_MakeLine " +"geometry set geoms " +" geometry ST_MakeLine geometry geom1 geometry geom2 geometry " +"ST_MakeLine geometry[] " "geoms_array " msgstr "" @@ -1966,10 +2007,10 @@ msgstr "" #, no-c-format msgid "" "ST_MakeLine comes in 3 forms: a spatial aggregate that takes rows of point-" -"or-line geometries and returns a line string, a function that takes an array" -" of point-or-lines, and a regular function that takes two point-or-line " -"geometries. You might want to use a subselect to order points before feeding" -" them to the aggregate version of this function." +"or-line geometries and returns a line string, a function that takes an array " +"of point-or-lines, and a regular function that takes two point-or-line " +"geometries. You might want to use a subselect to order points before feeding " +"them to the aggregate version of this function." msgstr "" #. Tag: para @@ -2013,10 +2054,12 @@ msgstr "" #, no-c-format msgid "" "-- For pre-PostgreSQL 9.0 - this usually works, \n" -"-- but the planner may on occasion choose not to respect the order of the subquery\n" +"-- but the planner may on occasion choose not to respect the order of the " +"subquery\n" "SELECT gps.gps_track, ST_MakeLine(gps.the_geom) As newgeom\n" " FROM (SELECT gps_track,gps_time, the_geom\n" -" FROM gps_points ORDER BY gps_track, gps_time) As gps\n" +" FROM gps_points ORDER BY gps_track, gps_time) As " +"gps\n" " GROUP BY gps.gps_track;" msgstr "" @@ -2028,7 +2071,8 @@ msgid "" "-- (you can use the new ORDER BY support for aggregates)\n" "-- this is a guaranteed way to get a correctly ordered linestring\n" "-- Your order by part can order by more than one column if needed\n" -"SELECT gps.gps_track, ST_MakeLine(gps.the_geom ORDER BY gps_time) As newgeom\n" +"SELECT gps.gps_track, ST_MakeLine(gps.the_geom ORDER BY gps_time) As " +"newgeom\n" " FROM gps_points As gps\n" " GROUP BY gps.gps_track;" msgstr "" @@ -2076,11 +2120,13 @@ msgstr "" #: reference_constructor.xml:1217 #, no-c-format msgid "" -"SELECT ST_MakeLine(ARRAY(SELECT ST_Centroid(the_geom) FROM visit_locations ORDER BY visit_time));\n" +"SELECT ST_MakeLine(ARRAY(SELECT ST_Centroid(the_geom) FROM visit_locations " +"ORDER BY visit_time));\n" "\n" "--Making a 3d line with 3 3-d points\n" "SELECT ST_AsEWKT(ST_MakeLine(ARRAY[ST_MakePoint(1,2,3),\n" -" ST_MakePoint(3,4,5), ST_MakePoint(6,6,6)]));\n" +" ST_MakePoint(3,4,5), " +"ST_MakePoint(6,6,6)]));\n" " st_asewkt\n" "-------------------------\n" "LINESTRING(1 2 3,3 4 5,6 6 6)" @@ -2113,14 +2159,12 @@ msgstr "" #, no-c-format msgid "" "geometry ST_MakeEnvelope " -"double precision " -"xmin double " -"precision ymin " -"double precision " -"xmax double " -"precision ymax integer " -"srid=unknown" +"double precision xmin double precision ymin double precision " +"xmax double precision ymax integer srid=unknown" msgstr "" #. Tag: para @@ -2142,8 +2186,8 @@ msgstr "" #: reference_constructor.xml:1257 #, no-c-format msgid "" -"Enhanced: 2.0: Ability to specify an envelope without specifying an SRID was" -" introduced." +"Enhanced: 2.0: Ability to specify an envelope without specifying an SRID was " +"introduced." msgstr "" #. Tag: title @@ -2179,8 +2223,8 @@ msgstr "" #: reference_constructor.xml:1275 #, no-c-format msgid "" -"Creates a Polygon formed by the given shell. Input geometries must be closed" -" LINESTRINGS." +"Creates a Polygon formed by the given shell. Input geometries must be closed " +"LINESTRINGS." msgstr "" #. Tag: funcprototype @@ -2196,18 +2240,17 @@ msgstr "" #, no-c-format msgid "" "geometry ST_MakePolygon " -"geometry " -"outerlinestring " -"geometry[] " -"interiorlinestrings" +"geometry outerlinestring geometry[] interiorlinestrings" msgstr "" #. Tag: para #: reference_constructor.xml:1298 #, no-c-format msgid "" -"Creates a Polygon formed by the given shell. Input geometries must be closed" -" LINESTRINGS. Comes in 2 variants." +"Creates a Polygon formed by the given shell. Input geometries must be closed " +"LINESTRINGS. Comes in 2 variants." msgstr "" #. Tag: para @@ -2229,9 +2272,8 @@ msgstr "" #: reference_constructor.xml:1305 #, no-c-format msgid "" -"This function will not accept a MULTILINESTRING. Use or to generate line " -"strings." +"This function will not accept a MULTILINESTRING. Use or to generate line strings." msgstr "" #. Tag: title @@ -2245,22 +2287,27 @@ msgstr "" #, no-c-format msgid "" "--2d line\n" -"SELECT ST_MakePolygon(ST_GeomFromText('LINESTRING(75.15 29.53,77 29,77.6 29.5, 75.15 29.53)'));\n" +"SELECT ST_MakePolygon(ST_GeomFromText('LINESTRING(75.15 29.53,77 29,77.6 " +"29.5, 75.15 29.53)'));\n" "--If linestring is not closed\n" "--you can add the start point to close it\n" -"SELECT ST_MakePolygon(ST_AddPoint(foo.open_line, ST_StartPoint(foo.open_line)))\n" +"SELECT ST_MakePolygon(ST_AddPoint(foo.open_line, ST_StartPoint(foo." +"open_line)))\n" "FROM (\n" -"SELECT ST_GeomFromText('LINESTRING(75.15 29.53,77 29,77.6 29.5)') As open_line) As foo;\n" +"SELECT ST_GeomFromText('LINESTRING(75.15 29.53,77 29,77.6 29.5)') As " +"open_line) As foo;\n" "\n" "--3d closed line\n" -"SELECT ST_MakePolygon(ST_GeomFromText('LINESTRING(75.15 29.53 1,77 29 1,77.6 29.5 1, 75.15 29.53 1)'));\n" +"SELECT ST_MakePolygon(ST_GeomFromText('LINESTRING(75.15 29.53 1,77 29 1,77.6 " +"29.5 1, 75.15 29.53 1)'));\n" "\n" "st_asewkt\n" "-----------\n" "POLYGON((75.15 29.53 1,77 29 1,77.6 29.5 1,75.15 29.53 1))\n" "\n" "--measured line --\n" -"SELECT ST_MakePolygon(ST_GeomFromText('LINESTRINGM(75.15 29.53 1,77 29 1,77.6 29.5 2, 75.15 29.53 2)'));\n" +"SELECT ST_MakePolygon(ST_GeomFromText('LINESTRINGM(75.15 29.53 1,77 29 " +"1,77.6 29.5 2, 75.15 29.53 2)'));\n" "\n" "st_asewkt\n" "----------\n" @@ -2298,8 +2345,8 @@ msgstr "" #: reference_constructor.xml:1320 #, no-c-format msgid "" -"Build province boundaries with holes representing lakes in the province from" -" a set of province polygons/multipolygons and water line strings this is an " +"Build province boundaries with holes representing lakes in the province from " +"a set of province polygons/multipolygons and water line strings this is an " "example of using PostGIS ST_Accum" msgstr "" @@ -2326,14 +2373,17 @@ msgid "" "SELECT p.gid, p.province_name,\n" " CASE WHEN\n" " ST_Accum(w.the_geom) IS NULL THEN p.the_geom\n" -" ELSE ST_MakePolygon(ST_LineMerge(ST_Boundary(p.the_geom)), ST_Accum(w.the_geom)) END\n" +" ELSE ST_MakePolygon(ST_LineMerge(ST_Boundary(p.the_geom)), " +"ST_Accum(w.the_geom)) END\n" " FROM\n" " provinces p LEFT JOIN waterlines w\n" -" ON (ST_Within(w.the_geom, p.the_geom) AND ST_IsClosed(w.the_geom))\n" +" ON (ST_Within(w.the_geom, p.the_geom) AND " +"ST_IsClosed(w.the_geom))\n" " GROUP BY p.gid, p.province_name, p.the_geom;\n" "\n" " --Same example above but utilizing a correlated subquery\n" -" --and PostgreSQL built-in ARRAY() function that converts a row set to an array\n" +" --and PostgreSQL built-in ARRAY() function that converts a row set " +"to an array\n" "\n" " SELECT p.gid, p.province_name, CASE WHEN\n" " EXISTS(SELECT w.the_geom\n" @@ -2423,8 +2473,7 @@ msgstr "" #: reference_constructor.xml:1387 #, no-c-format msgid "" -"Use if you need to make a point with " -"x,y,m." +"Use if you need to make a point with x,y,m." msgstr "" #. Tag: programlisting @@ -2509,8 +2558,10 @@ msgid "" "-----------------------------------------------\n" " POINTM(-71.1043443253471 42.3150676015829 10)\n" "\n" -"--Return EWKT representation of point with measure marked as WGS 84 long lat\n" -"SELECT ST_AsEWKT(ST_SetSRID(ST_MakePointM(-71.1043443253471, 42.3150676015829,10),4326));\n" +"--Return EWKT representation of point with measure marked as WGS 84 long " +"lat\n" +"SELECT ST_AsEWKT(ST_SetSRID(ST_MakePointM(-71.1043443253471, " +"42.3150676015829,10),4326));\n" "\n" " st_asewkt\n" "---------------------------------------------------------\n" @@ -2548,13 +2599,12 @@ msgstr "" #: reference_constructor.xml:1447 #, no-c-format msgid "" -" geometry " -"ST_MLineFromText text " -" WKT integer " -"srid " -"geometry ST_MLineFromText " -"text WKT " -"" +" geometry ST_MLineFromText text WKT " +"integer srid geometry ST_MLineFromText text WKT " msgstr "" #. Tag: para @@ -2576,8 +2626,8 @@ msgstr "" #, no-c-format msgid "" "If you are absolutely sure all your WKT geometries are points, don't use " -"this function. It is slower than ST_GeomFromText since it adds an additional" -" validation step." +"this function. It is slower than ST_GeomFromText since it adds an additional " +"validation step." msgstr "" #. Tag: para @@ -2610,21 +2660,20 @@ msgstr "" #: reference_constructor.xml:1508 #, no-c-format msgid "" -" geometry " -"ST_MPointFromText text " -" WKT integer " -" srid " -" geometry " -"ST_MPointFromText text " -" WKT " +" geometry ST_MPointFromText text WKT " +"integer srid geometry " +"ST_MPointFromText text WKT " msgstr "" #. Tag: para #: reference_constructor.xml:1526 #, no-c-format msgid "" -"Makes a Geometry from WKT with the given SRID. If SRID is not give, it" -" defaults to 0." +"Makes a Geometry from WKT with the given SRID. If SRID is not give, it " +"defaults to 0." msgstr "" #. Tag: para @@ -2650,7 +2699,8 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_MPointFromText('MULTIPOINT(1 2, 3 4)');\n" -"SELECT ST_MPointFromText('MULTIPOINT(-70.9590 42.1180, -70.9611 42.1223)', 4326);" +"SELECT ST_MPointFromText('MULTIPOINT(-70.9590 42.1180, -70.9611 42.1223)', " +"4326);" msgstr "" #. Tag: refname @@ -2671,13 +2721,12 @@ msgstr "" #: reference_constructor.xml:1569 #, no-c-format msgid "" -" geometry " -"ST_MPolyFromText text " -" WKT integer " -"srid " -"geometry ST_MPolyFromText " -"text WKT " -"" +" geometry ST_MPolyFromText text WKT " +"integer srid geometry ST_MPolyFromText text WKT " msgstr "" #. Tag: para @@ -2713,8 +2762,22 @@ msgstr "" #: reference_constructor.xml:1610 #, no-c-format msgid "" -"SELECT ST_MPolyFromText('MULTIPOLYGON(((0 0 1,20 0 1,20 20 1,0 20 1,0 0 1),(5 5 3,5 7 3,7 7 3,7 5 3,5 5 3)))');\n" -"SELECt ST_MPolyFromText('MULTIPOLYGON(((-70.916 42.1002,-70.9468 42.0946,-70.9765 42.0872,-70.9754 42.0875,-70.9749 42.0879,-70.9752 42.0881,-70.9754 42.0891,-70.9758 42.0894,-70.9759 42.0897,-70.9759 42.0899,-70.9754 42.0902,-70.9756 42.0906,-70.9753 42.0907,-70.9753 42.0917,-70.9757 42.0924,-70.9755 42.0928,-70.9755 42.0942,-70.9751 42.0948,-70.9755 42.0953,-70.9751 42.0958,-70.9751 42.0962,-70.9759 42.0983,-70.9767 42.0987,-70.9768 42.0991,-70.9771 42.0997,-70.9771 42.1003,-70.9768 42.1005,-70.977 42.1011,-70.9766 42.1019,-70.9768 42.1026,-70.9769 42.1033,-70.9775 42.1042,-70.9773 42.1043,-70.9776 42.1043,-70.9778 42.1048,-70.9773 42.1058,-70.9774 42.1061,-70.9779 42.1065,-70.9782 42.1078,-70.9788 42.1085,-70.9798 42.1087,-70.9806 42.109,-70.9807 42.1093,-70.9806 42.1099,-70.9809 42.1109,-70.9808 42.1112,-70.9798 42.1116,-70.9792 42.1127,-70.979 42.1129,-70.9787 42.1134,-70.979 42.1139,-70.9791 42.1141,-70.9987 42.1116,-71.0022 42.1273,\n" +"SELECT ST_MPolyFromText('MULTIPOLYGON(((0 0 1,20 0 1,20 20 1,0 20 1,0 0 1)," +"(5 5 3,5 7 3,7 7 3,7 5 3,5 5 3)))');\n" +"SELECt ST_MPolyFromText('MULTIPOLYGON(((-70.916 42.1002,-70.9468 " +"42.0946,-70.9765 42.0872,-70.9754 42.0875,-70.9749 42.0879,-70.9752 " +"42.0881,-70.9754 42.0891,-70.9758 42.0894,-70.9759 42.0897,-70.9759 " +"42.0899,-70.9754 42.0902,-70.9756 42.0906,-70.9753 42.0907,-70.9753 " +"42.0917,-70.9757 42.0924,-70.9755 42.0928,-70.9755 42.0942,-70.9751 " +"42.0948,-70.9755 42.0953,-70.9751 42.0958,-70.9751 42.0962,-70.9759 " +"42.0983,-70.9767 42.0987,-70.9768 42.0991,-70.9771 42.0997,-70.9771 " +"42.1003,-70.9768 42.1005,-70.977 42.1011,-70.9766 42.1019,-70.9768 " +"42.1026,-70.9769 42.1033,-70.9775 42.1042,-70.9773 42.1043,-70.9776 " +"42.1043,-70.9778 42.1048,-70.9773 42.1058,-70.9774 42.1061,-70.9779 " +"42.1065,-70.9782 42.1078,-70.9788 42.1085,-70.9798 42.1087,-70.9806 " +"42.109,-70.9807 42.1093,-70.9806 42.1099,-70.9809 42.1109,-70.9808 " +"42.1112,-70.9798 42.1116,-70.9792 42.1127,-70.979 42.1129,-70.9787 " +"42.1134,-70.979 42.1139,-70.9791 42.1141,-70.9987 42.1116,-71.0022 42.1273,\n" " -70.9408 42.1513,-70.9315 42.1165,-70.916 42.1002)))',4326);" msgstr "" @@ -2745,8 +2808,8 @@ msgstr "" #: reference_constructor.xml:1641 #, no-c-format msgid "" -"Returns an ST_Point with the given coordinate values. MM compliant alias for" -" ST_MakePoint that takes just an x and y." +"Returns an ST_Point with the given coordinate values. MM compliant alias for " +"ST_MakePoint that takes just an x and y." msgstr "" #. Tag: para @@ -2786,16 +2849,20 @@ msgstr "" #, no-c-format msgid "" "-- the :: is PostgreSQL short-hand for casting.\n" -"SELECT ST_SetSRID(ST_Point(-71.1043443253471, 42.3150676015829),4326)::geography;" +"SELECT ST_SetSRID(ST_Point(-71.1043443253471, 42.3150676015829),4326)::" +"geography;" msgstr "" #. Tag: programlisting #: reference_constructor.xml:1661 #, no-c-format msgid "" -"--If your point coordinates are in a different spatial reference from WGS-84 long lat, then you need to transform before casting\n" -"-- This example we convert a point in Pennsylvania State Plane feet to WGS 84 and then geography\n" -"SELECT ST_Transform(ST_SetSRID(ST_Point(3637510, 3014852),2273),4326)::geography;" +"--If your point coordinates are in a different spatial reference from WGS-84 " +"long lat, then you need to transform before casting\n" +"-- This example we convert a point in Pennsylvania State Plane feet to WGS " +"84 and then geography\n" +"SELECT ST_Transform(ST_SetSRID(ST_Point(3637510, 3014852),2273),4326)::" +"geography;" msgstr "" #. Tag: para @@ -2877,8 +2944,8 @@ msgstr "" #: reference_constructor.xml:1708 #, no-c-format msgid "" -", , " +", , " msgstr "" #. Tag: refname @@ -2899,13 +2966,12 @@ msgstr "" #: reference_constructor.xml:1719 #, no-c-format msgid "" -" geometry " -"ST_PointFromText text " -" WKT " -"geometry ST_PointFromText " -"text WKT " -"integer srid " -"" +" geometry ST_PointFromText text WKT " +" geometry " +"ST_PointFromText text " +"WKT integer " +"srid " msgstr "" #. Tag: para @@ -2934,11 +3000,11 @@ msgstr "" #, no-c-format msgid "" "If you are absolutely sure all your WKT geometries are points, don't use " -"this function. It is slower than ST_GeomFromText since it adds an additional" -" validation step. If you are building points from long lat coordinates and " +"this function. It is slower than ST_GeomFromText since it adds an additional " +"validation step. If you are building points from long lat coordinates and " "care more about performance and accuracy than OGC compliance, use or OGC compliant alias ." +"linkend=\"ST_MakePoint\"/> or OGC compliant alias ." msgstr "" #. Tag: para @@ -2980,10 +3046,10 @@ msgstr "" #, no-c-format msgid "" "The ST_PointFromWKB function, takes a well-known binary " -"representation of geometry and a Spatial Reference System ID " -"(SRID) and creates an instance of the appropriate " -"geometry type - in this case, a POINT geometry. This " -"function plays the role of the Geometry Factory in SQL." +"representation of geometry and a Spatial Reference System ID (SRID) and creates an instance of the appropriate geometry type - in this " +"case, a POINT geometry. This function plays the role of " +"the Geometry Factory in SQL." msgstr "" #. Tag: para @@ -3044,8 +3110,8 @@ msgstr "" #: reference_constructor.xml:1824 #, no-c-format msgid "" -"Returns a polygon built from the specified linestring and " -"SRID." +"Returns a polygon built from the specified linestring and SRID." msgstr "" #. Tag: funcprototype @@ -3053,9 +3119,9 @@ msgstr "" #, no-c-format msgid "" "geometry ST_Polygon " -"geometry " -"aLineString integer " -" srid" +"geometry aLineString integer srid" msgstr "" #. Tag: para @@ -3086,12 +3152,14 @@ msgstr "" #, no-c-format msgid "" "--a 2d polygon\n" -"SELECT ST_Polygon(ST_GeomFromText('LINESTRING(75.15 29.53,77 29,77.6 29.5, 75.15 29.53)'), 4326);\n" +"SELECT ST_Polygon(ST_GeomFromText('LINESTRING(75.15 29.53,77 29,77.6 29.5, " +"75.15 29.53)'), 4326);\n" "\n" "--result--\n" "POLYGON((75.15 29.53,77 29,77.6 29.5,75.15 29.53))\n" "--a 3d polygon\n" -"SELECT ST_AsEWKT(ST_Polygon(ST_GeomFromEWKT('LINESTRING(75.15 29.53 1,77 29 1,77.6 29.5 1, 75.15 29.53 1)'), 4326));\n" +"SELECT ST_AsEWKT(ST_Polygon(ST_GeomFromEWKT('LINESTRING(75.15 29.53 1,77 29 " +"1,77.6 29.5 1, 75.15 29.53 1)'), 4326));\n" "\n" "result\n" "------\n" @@ -3117,13 +3185,12 @@ msgstr "" #: reference_constructor.xml:1878 #, no-c-format msgid "" -" geometry " -"ST_PolygonFromText text " -" WKT " -" geometry " -"ST_PolygonFromText text " -" WKT integer " -" srid " +" geometry ST_PolygonFromText text WKT " +" geometry " +"ST_PolygonFromText text WKT integer " +"srid " msgstr "" #. Tag: para @@ -3139,8 +3206,8 @@ msgstr "" #, no-c-format msgid "" "If you are absolutely sure all your WKT geometries are polygons, don't use " -"this function. It is slower than ST_GeomFromText since it adds an additional" -" validation step." +"this function. It is slower than ST_GeomFromText since it adds an additional " +"validation step." msgstr "" #. Tag: para @@ -3153,8 +3220,10 @@ msgstr "" #: reference_constructor.xml:1910 #, no-c-format msgid "" -"SELECT ST_PolygonFromText('POLYGON((-71.1776585052917 42.3902909739571,-71.1776820268866 42.3903701743239,\n" -"-71.1776063012595 42.3903825660754,-71.1775826583081 42.3903033653531,-71.1776585052917 42.3902909739571))');\n" +"SELECT ST_PolygonFromText('POLYGON((-71.1776585052917 " +"42.3902909739571,-71.1776820268866 42.3903701743239,\n" +"-71.1776063012595 42.3903825660754,-71.1775826583081 " +"42.3903033653531,-71.1776585052917 42.3902909739571))');\n" "st_polygonfromtext\n" "------------------\n" "010300000001000000050000006...\n" diff --git a/doc/po/de_DE/reference_editor.xml.po b/doc/po/de_DE/reference_editor.xml.po index e6160cfc8..4a02ac5c7 100644 --- a/doc/po/de_DE/reference_editor.xml.po +++ b/doc/po/de_DE/reference_editor.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:23+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -39,8 +40,8 @@ msgstr "" #, no-c-format msgid "" "geometry ST_AddPoint " -"geometry linestring" -" geometry point" +"geometry linestring " +"geometry point" msgstr "" #. Tag: funcprototype @@ -48,8 +49,8 @@ msgstr "" #, no-c-format msgid "" "geometry ST_AddPoint " -"geometry linestring" -" geometry point " +"geometry linestring " +"geometry point " "integer position" msgstr "" @@ -119,15 +120,18 @@ msgstr "Beispiele" #, no-c-format msgid "" "--guarantee all linestrings in a table are closed\n" -" --by adding the start point of each linestring to the end of the line string\n" +" --by adding the start point of each linestring to the end of " +"the line string\n" " --only for those that are not closed\n" " UPDATE sometable\n" -" SET the_geom = ST_AddPoint(the_geom, ST_StartPoint(the_geom))\n" +" SET the_geom = ST_AddPoint(the_geom, " +"ST_StartPoint(the_geom))\n" " FROM sometable\n" " WHERE ST_IsClosed(the_geom) = false;\n" "\n" " --Adding point to a 3-d line\n" -" SELECT ST_AsEWKT(ST_AddPoint(ST_GeomFromEWKT('LINESTRING(0 0 1, 1 1 1)'), ST_MakePoint(1, 2, 3)));\n" +" SELECT ST_AsEWKT(ST_AddPoint(ST_GeomFromEWKT('LINESTRING(0 0 " +"1, 1 1 1)'), ST_MakePoint(1, 2, 3)));\n" "\n" " --result\n" " st_asewkt\n" @@ -188,16 +192,16 @@ msgid "" "float i " "float xoff " "float yoff " -"float zoff " -" geometry " -"ST_Affine geometry " -"geomA float " -"a float " -"b float " -"d float " -"e float " -"xoff float " -"yoff " +"float zoff geometry ST_Affine geometry geomA float a float b float d float e float xoff float yoff " msgstr "" #. Tag: para @@ -212,22 +216,30 @@ msgstr "" #: reference_editor.xml:92 #, no-c-format msgid "" -"Version 1: The call ST_Affine(geom, a, b, c, d, e, f, g, h, i, xoff, yoff, zoff) represents the transformation matrix / a b c xoff \\\n" +"Version 1: The call ST_Affine(geom, a, b, c, d, e, f, g, h, " +"i, xoff, yoff, zoff) represents the transformation matrix " +"/ a b c xoff \\\n" "| d e f yoff |\n" "| g h i zoff |\n" -"\\ 0 0 0 1 / and the vertices are transformed as follows: x' = a*x + b*y + c*z + xoff\n" +"\\ 0 0 0 1 / and the vertices are transformed as " +"follows: x' = a*x + b*y + c*z + xoff\n" "y' = d*x + e*y + f*z + yoff\n" -"z' = g*x + h*y + i*z + zoff All of the translate / scale functions below are expressed via such an affine transformation." +"z' = g*x + h*y + i*z + zoff All of the translate / scale " +"functions below are expressed via such an affine transformation." msgstr "" #. Tag: para #: reference_editor.xml:99 #, no-c-format msgid "" -"Version 2: Applies a 2d affine transformation to the geometry. The call ST_Affine(geom, a, b, d, e, xoff, yoff) represents the transformation matrix / a b 0 xoff \\ / a b xoff \\\n" +"Version 2: Applies a 2d affine transformation to the geometry. The call " +"ST_Affine(geom, a, b, d, e, xoff, yoff) " +"represents the transformation matrix / a b 0 xoff " +"\\ / a b xoff \\\n" "| d e 0 yoff | rsp. | d e yoff |\n" "| 0 0 1 0 | \\ 0 0 1 /\n" -"\\ 0 0 0 1 / and the vertices are transformed as follows: x' = a*x + b*y + xoff\n" +"\\ 0 0 0 1 / and the vertices are transformed as " +"follows: x' = a*x + b*y + xoff\n" "y' = d*x + e*y + yoff\n" "z' = z This method is a subcase of the 3D method above." msgstr "" @@ -290,18 +302,23 @@ msgstr "" #: reference_editor.xml:119 #, no-c-format msgid "" -"--Rotate a 3d line 180 degrees about the z axis. Note this is long-hand for doing ST_Rotate();\n" -" SELECT ST_AsEWKT(ST_Affine(the_geom, cos(pi()), -sin(pi()), 0, sin(pi()), cos(pi()), 0, 0, 0, 1, 0, 0, 0)) As using_affine,\n" +"--Rotate a 3d line 180 degrees about the z axis. Note this is long-hand for " +"doing ST_Rotate();\n" +" SELECT ST_AsEWKT(ST_Affine(the_geom, cos(pi()), -sin(pi()), 0, sin(pi()), " +"cos(pi()), 0, 0, 0, 1, 0, 0, 0)) As using_affine,\n" " ST_AsEWKT(ST_Rotate(the_geom, pi())) As using_rotate\n" -" FROM (SELECT ST_GeomFromEWKT('LINESTRING(1 2 3, 1 4 3)') As the_geom) As foo;\n" +" FROM (SELECT ST_GeomFromEWKT('LINESTRING(1 2 3, 1 4 3)') As " +"the_geom) As foo;\n" " using_affine | using_rotate\n" "-----------------------------+-----------------------------\n" " LINESTRING(-1 -2 3,-1 -4 3) | LINESTRING(-1 -2 3,-1 -4 3)\n" "(1 row)\n" "\n" "--Rotate a 3d line 180 degrees in both the x and z axis\n" -"SELECT ST_AsEWKT(ST_Affine(the_geom, cos(pi()), -sin(pi()), 0, sin(pi()), cos(pi()), -sin(pi()), 0, sin(pi()), cos(pi()), 0, 0, 0))\n" -" FROM (SELECT ST_GeomFromEWKT('LINESTRING(1 2 3, 1 4 3)') As the_geom) As foo;\n" +"SELECT ST_AsEWKT(ST_Affine(the_geom, cos(pi()), -sin(pi()), 0, sin(pi()), " +"cos(pi()), -sin(pi()), 0, sin(pi()), cos(pi()), 0, 0, 0))\n" +" FROM (SELECT ST_GeomFromEWKT('LINESTRING(1 2 3, 1 4 3)') As " +"the_geom) As foo;\n" " st_asewkt\n" "-------------------------------\n" " LINESTRING(-1 -2 -3,-1 -4 -3)\n" @@ -364,12 +381,14 @@ msgstr "" #: reference_editor.xml:166 #, no-c-format msgid "" -"SELECT ST_AsEWKT(ST_Force2D(ST_GeomFromEWKT('CIRCULARSTRING(1 1 2, 2 3 2, 4 5 2, 6 7 2, 5 6 2)')));\n" +"SELECT ST_AsEWKT(ST_Force2D(ST_GeomFromEWKT('CIRCULARSTRING(1 1 2, 2 3 2, 4 " +"5 2, 6 7 2, 5 6 2)')));\n" " st_asewkt\n" "-------------------------------------\n" "CIRCULARSTRING(1 1,2 3,4 5,6 7,5 6)\n" "\n" -"SELECT ST_AsEWKT(ST_Force2D('POLYGON((0 0 2,0 5 2,5 0 2,0 0 2),(1 1 2,3 1 2,1 3 2,1 1 2))'));\n" +"SELECT ST_AsEWKT(ST_Force2D('POLYGON((0 0 2,0 5 2,5 0 2,0 0 2),(1 1 2,3 1 " +"2,1 3 2,1 1 2))'));\n" "\n" " st_asewkt\n" "----------------------------------------------\n" @@ -400,8 +419,8 @@ msgstr "" #: reference_editor.xml:196 #, no-c-format msgid "" -"Forces the geometries into XYZ mode. This is an alias for ST_Force_3DZ. If a" -" geometry has no Z component, then a 0 Z coordinate is tacked on." +"Forces the geometries into XYZ mode. This is an alias for ST_Force_3DZ. If a " +"geometry has no Z component, then a 0 Z coordinate is tacked on." msgstr "" #. Tag: para @@ -415,13 +434,16 @@ msgstr "" #, no-c-format msgid "" "--Nothing happens to an already 3D geometry\n" -" SELECT ST_AsEWKT(ST_Force3D(ST_GeomFromEWKT('CIRCULARSTRING(1 1 2, 2 3 2, 4 5 2, 6 7 2, 5 6 2)')));\n" +" SELECT " +"ST_AsEWKT(ST_Force3D(ST_GeomFromEWKT('CIRCULARSTRING(1 1 2, 2 3 2, 4 5 2, 6 " +"7 2, 5 6 2)')));\n" " st_asewkt\n" "-----------------------------------------------\n" " CIRCULARSTRING(1 1 2,2 3 2,4 5 2,6 7 2,5 6 2)\n" "\n" "\n" -"SELECT ST_AsEWKT(ST_Force3D('POLYGON((0 0,0 5,5 0,0 0),(1 1,3 1,1 3,1 1))'));\n" +"SELECT ST_AsEWKT(ST_Force3D('POLYGON((0 0,0 5,5 0,0 0),(1 1,3 1,1 3,1 " +"1))'));\n" "\n" " st_asewkt\n" "--------------------------------------------------------------\n" @@ -460,8 +482,8 @@ msgstr "" #: reference_editor.xml:239 #, no-c-format msgid "" -"Forces the geometries into XYZ mode. This is a synonym for ST_Force3DZ. If a" -" geometry has no Z component, then a 0 Z coordinate is tacked on." +"Forces the geometries into XYZ mode. This is a synonym for ST_Force3DZ. If a " +"geometry has no Z component, then a 0 Z coordinate is tacked on." msgstr "" #. Tag: para @@ -475,13 +497,15 @@ msgstr "" #, no-c-format msgid "" "--Nothing happens to an already 3D geometry\n" -"SELECT ST_AsEWKT(ST_Force3DZ(ST_GeomFromEWKT('CIRCULARSTRING(1 1 2, 2 3 2, 4 5 2, 6 7 2, 5 6 2)')));\n" +"SELECT ST_AsEWKT(ST_Force3DZ(ST_GeomFromEWKT('CIRCULARSTRING(1 1 2, 2 3 2, 4 " +"5 2, 6 7 2, 5 6 2)')));\n" " st_asewkt\n" "-----------------------------------------------\n" " CIRCULARSTRING(1 1 2,2 3 2,4 5 2,6 7 2,5 6 2)\n" "\n" "\n" -"SELECT ST_AsEWKT(ST_Force3DZ('POLYGON((0 0,0 5,5 0,0 0),(1 1,3 1,1 3,1 1))'));\n" +"SELECT ST_AsEWKT(ST_Force3DZ('POLYGON((0 0,0 5,5 0,0 0),(1 1,3 1,1 3,1 " +"1))'));\n" "\n" " st_asewkt\n" "--------------------------------------------------------------\n" @@ -535,13 +559,15 @@ msgstr "" #, no-c-format msgid "" "--Nothing happens to an already 3D geometry\n" -"SELECT ST_AsEWKT(ST_Force3DM(ST_GeomFromEWKT('CIRCULARSTRING(1 1 2, 2 3 2, 4 5 2, 6 7 2, 5 6 2)')));\n" +"SELECT ST_AsEWKT(ST_Force3DM(ST_GeomFromEWKT('CIRCULARSTRING(1 1 2, 2 3 2, 4 " +"5 2, 6 7 2, 5 6 2)')));\n" " st_asewkt\n" "------------------------------------------------\n" " CIRCULARSTRINGM(1 1 0,2 3 0,4 5 0,6 7 0,5 6 0)\n" "\n" "\n" -"SELECT ST_AsEWKT(ST_Force3DM('POLYGON((0 0 1,0 5 1,5 0 1,0 0 1),(1 1 1,3 1 1,1 3 1,1 1 1))'));\n" +"SELECT ST_AsEWKT(ST_Force3DM('POLYGON((0 0 1,0 5 1,5 0 1,0 0 1),(1 1 1,3 1 " +"1,1 3 1,1 1 1))'));\n" "\n" " st_asewkt\n" "---------------------------------------------------------------\n" @@ -595,18 +621,21 @@ msgstr "" #, no-c-format msgid "" "--Nothing happens to an already 3D geometry\n" -"SELECT ST_AsEWKT(ST_Force4D(ST_GeomFromEWKT('CIRCULARSTRING(1 1 2, 2 3 2, 4 5 2, 6 7 2, 5 6 2)')));\n" +"SELECT ST_AsEWKT(ST_Force4D(ST_GeomFromEWKT('CIRCULARSTRING(1 1 2, 2 3 2, 4 " +"5 2, 6 7 2, 5 6 2)')));\n" " st_asewkt\n" "---------------------------------------------------------\n" " CIRCULARSTRING(1 1 2 0,2 3 2 0,4 5 2 0,6 7 2 0,5 6 2 0)\n" "\n" "\n" "\n" -"SELECT ST_AsEWKT(ST_Force4D('MULTILINESTRINGM((0 0 1,0 5 2,5 0 3,0 0 4),(1 1 1,3 1 1,1 3 1,1 1 1))'));\n" +"SELECT ST_AsEWKT(ST_Force4D('MULTILINESTRINGM((0 0 1,0 5 2,5 0 3,0 0 4),(1 " +"1 1,3 1 1,1 3 1,1 1 1))'));\n" "\n" " st_asewkt\n" "--------------------------------------------------------------------------------------\n" -" MULTILINESTRING((0 0 0 1,0 5 0 2,5 0 0 3,0 0 0 4),(1 1 0 1,3 1 0 1,1 3 0 1,1 1 0 1))" +" MULTILINESTRING((0 0 0 1,0 5 0 2,5 0 0 3,0 0 0 4),(1 1 0 1,3 1 0 1,1 3 0 " +"1,1 1 0 1))" msgstr "" #. Tag: refname @@ -655,17 +684,21 @@ msgstr "" #: reference_editor.xml:380 #, no-c-format msgid "" -"SELECT ST_AsEWKT(ST_ForceCollection('POLYGON((0 0 1,0 5 1,5 0 1,0 0 1),(1 1 1,3 1 1,1 3 1,1 1 1))'));\n" +"SELECT ST_AsEWKT(ST_ForceCollection('POLYGON((0 0 1,0 5 1,5 0 1,0 0 1),(1 1 " +"1,3 1 1,1 3 1,1 1 1))'));\n" "\n" " st_asewkt\n" "----------------------------------------------------------------------------------\n" -" GEOMETRYCOLLECTION(POLYGON((0 0 1,0 5 1,5 0 1,0 0 1),(1 1 1,3 1 1,1 3 1,1 1 1)))\n" +" GEOMETRYCOLLECTION(POLYGON((0 0 1,0 5 1,5 0 1,0 0 1),(1 1 1,3 1 1,1 3 1,1 1 " +"1)))\n" "\n" "\n" -" SELECT ST_AsText(ST_ForceCollection('CIRCULARSTRING(220227 150406,2220227 150407,220227 150406)'));\n" +" SELECT ST_AsText(ST_ForceCollection('CIRCULARSTRING(220227 150406,2220227 " +"150407,220227 150406)'));\n" " st_astext\n" "--------------------------------------------------------------------------------\n" -" GEOMETRYCOLLECTION(CIRCULARSTRING(220227 150406,2220227 150407,220227 150406))\n" +" GEOMETRYCOLLECTION(CIRCULARSTRING(220227 150406,2220227 150407,220227 " +"150406))\n" "(1 row)" msgstr "" @@ -674,7 +707,8 @@ msgstr "" #, no-c-format msgid "" "-- POLYHEDRAL example --\n" -"SELECT ST_AsEWKT(ST_ForceCollection('POLYHEDRALSURFACE(((0 0 0,0 0 1,0 1 1,0 1 0,0 0 0)),\n" +"SELECT ST_AsEWKT(ST_ForceCollection('POLYHEDRALSURFACE(((0 0 0,0 0 1,0 1 1,0 " +"1 0,0 0 0)),\n" " ((0 0 0,0 1 0,1 1 0,1 0 0,0 0 0)),\n" " ((0 0 0,1 0 0,1 0 1,0 0 1,0 0 0)),\n" " ((1 1 0,1 1 1,1 0 1,1 0 0,1 1 0)),\n" @@ -709,12 +743,12 @@ msgstr "" #: reference_editor.xml:402 #, no-c-format msgid "" -" geometry ST_ForceSFS" -" geometry geomA " -" geometry " -"ST_ForceSFS geometry " -"geomA text " -"version " +" geometry ST_ForceSFS " +"geometry geomA geometry ST_ForceSFS geometry geomA text version " msgstr "" #. Tag: refname @@ -727,8 +761,8 @@ msgstr "" #: reference_editor.xml:430 #, no-c-format msgid "" -"Forces the orientation of the vertices in a polygon to follow the Right-" -"Hand-Rule." +"Forces the orientation of the vertices in a polygon to follow the Right-Hand-" +"Rule." msgstr "" #. Tag: funcprototype @@ -743,11 +777,11 @@ msgstr "" #: reference_editor.xml:447 #, no-c-format msgid "" -"Forces the orientation of the vertices in a polygon to follow the Right-" -"Hand-Rule. In GIS terminology, this means that the area that is bounded by " -"the polygon is to the right of the boundary. In particular, the exterior " -"ring is orientated in a clockwise direction and the interior rings in a " -"counter-clockwise direction." +"Forces the orientation of the vertices in a polygon to follow the Right-Hand-" +"Rule. In GIS terminology, this means that the area that is bounded by the " +"polygon is to the right of the boundary. In particular, the exterior ring is " +"orientated in a clockwise direction and the interior rings in a counter-" +"clockwise direction." msgstr "" #. Tag: programlisting @@ -756,7 +790,8 @@ msgstr "" msgid "" "SELECT ST_AsEWKT(\n" " ST_ForceRHR(\n" -" 'POLYGON((0 0 2, 5 0 2, 0 5 2, 0 0 2),(1 1 2, 1 3 2, 3 1 2, 1 1 2))'\n" +" 'POLYGON((0 0 2, 5 0 2, 0 5 2, 0 0 2),(1 1 2, 1 3 2, 3 1 2, 1 1 " +"2))'\n" " )\n" ");\n" " st_asewkt\n" @@ -795,9 +830,9 @@ msgstr "" #: reference_editor.xml:493 #, no-c-format msgid "" -"Turns a geometry into its curved representation, if applicable: lines become" -" compoundcurves, multilines become multicurves polygons become curvepolygons" -" multipolygons become multisurfaces. If the geometry input is already a " +"Turns a geometry into its curved representation, if applicable: lines become " +"compoundcurves, multilines become multicurves polygons become curvepolygons " +"multipolygons become multisurfaces. If the geometry input is already a " "curved representation returns back same as input." msgstr "" @@ -813,7 +848,8 @@ msgstr "" msgid "" "SELECT ST_AsText(\n" " ST_ForceCurve(\n" -" 'POLYGON((0 0 2, 5 0 2, 0 5 2, 0 0 2),(1 1 2, 1 3 2, 3 1 2, 1 1 2))'::geometry\n" +" 'POLYGON((0 0 2, 5 0 2, 0 5 2, 0 0 2),(1 1 2, 1 3 2, 3 1 2, 1 1 " +"2))'::geometry\n" " )\n" ");\n" " st_astext\n" @@ -832,8 +868,7 @@ msgstr "" #: reference_editor.xml:522 #, no-c-format msgid "" -"Returns a (set of) LineString(s) formed by sewing together a " -"MULTILINESTRING." +"Returns a (set of) LineString(s) formed by sewing together a MULTILINESTRING." msgstr "" #. Tag: funcprototype @@ -841,8 +876,8 @@ msgstr "" #, no-c-format msgid "" "geometry ST_LineMerge " -"geometry " -"amultilinestring" +"geometry amultilinestring" msgstr "" #. Tag: para @@ -857,8 +892,8 @@ msgstr "" #: reference_editor.xml:540 #, no-c-format msgid "" -"Only use with MULTILINESTRING/LINESTRINGs. If you feed a polygon or geometry" -" collection into this function, it will return an empty GEOMETRYCOLLECTION" +"Only use with MULTILINESTRING/LINESTRINGs. If you feed a polygon or geometry " +"collection into this function, it will return an empty GEOMETRYCOLLECTION" msgstr "" #. Tag: para @@ -872,7 +907,8 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_AsText(ST_LineMerge(\n" -"ST_GeomFromText('MULTILINESTRING((-29 -27,-30 -29.7,-36 -31,-45 -33),(-45 -33,-46 -32))')\n" +"ST_GeomFromText('MULTILINESTRING((-29 -27,-30 -29.7,-36 -31,-45 -33),(-45 " +"-33,-46 -32))')\n" " )\n" ");\n" "st_astext\n" @@ -882,7 +918,8 @@ msgid "" "\n" "--If can't be merged - original MULTILINESTRING is returned\n" "SELECT ST_AsText(ST_LineMerge(\n" -"ST_GeomFromText('MULTILINESTRING((-29 -27,-30 -29.7,-36 -31,-45 -33),(-45.2 -33.2,-46 -32))')\n" +"ST_GeomFromText('MULTILINESTRING((-29 -27,-30 -29.7,-36 -31,-45 -33),(-45.2 " +"-33.2,-46 -32))')\n" ")\n" ");\n" "st_astext\n" @@ -915,9 +952,9 @@ msgstr "" #, no-c-format msgid "" "geometry ST_CollectionExtract " -"geometry " -"collection integer " -" type" +"geometry collection integer type" msgstr "" #. Tag: para @@ -926,8 +963,8 @@ msgstr "" msgid "" "Given a (multi)geometry, returns a (multi)geometry consisting only of " "elements of the specified type. Sub-geometries that are not the specified " -"type are ignored. If there are no sub-geometries of the right type, an EMPTY" -" geometry will be returned. Only points, lines and polygons are supported. " +"type are ignored. If there are no sub-geometries of the right type, an EMPTY " +"geometry will be returned. Only points, lines and polygons are supported. " "Type numbers are 1 == POINT, 2 == LINESTRING, 3 == POLYGON." msgstr "" @@ -961,13 +998,17 @@ msgstr "" #, no-c-format msgid "" "-- Constants: 1 == POINT, 2 == LINESTRING, 3 == POLYGON\n" -"SELECT ST_AsText(ST_CollectionExtract(ST_GeomFromText('GEOMETRYCOLLECTION(GEOMETRYCOLLECTION(POINT(0 0)))'),1));\n" +"SELECT " +"ST_AsText(ST_CollectionExtract(ST_GeomFromText('GEOMETRYCOLLECTION(GEOMETRYCOLLECTION(POINT(0 " +"0)))'),1));\n" "st_astext\n" "---------------\n" "MULTIPOINT(0 0)\n" "(1 row)\n" "\n" -"SELECT ST_AsText(ST_CollectionExtract(ST_GeomFromText('GEOMETRYCOLLECTION(GEOMETRYCOLLECTION(LINESTRING(0 0, 1 1)),LINESTRING(2 2, 3 3))'),2));\n" +"SELECT " +"ST_AsText(ST_CollectionExtract(ST_GeomFromText('GEOMETRYCOLLECTION(GEOMETRYCOLLECTION(LINESTRING(0 " +"0, 1 1)),LINESTRING(2 2, 3 3))'),2));\n" "st_astext\n" "---------------\n" "MULTILINESTRING((0 0, 1 1), (2 2, 3 3))\n" @@ -977,7 +1018,8 @@ msgstr "" #. Tag: para #: reference_editor.xml:606 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -999,8 +1041,7 @@ msgstr "" #, no-c-format msgid "" "geometry ST_CollectionHomogenize " -"geometry " -"collection" +"geometry collection" msgstr "" #. Tag: para @@ -1022,14 +1063,16 @@ msgstr "" #: reference_editor.xml:646 #, no-c-format msgid "" -"SELECT ST_AsText(ST_CollectionHomogenize('GEOMETRYCOLLECTION(POINT(0 0))')); \n" +"SELECT ST_AsText(ST_CollectionHomogenize('GEOMETRYCOLLECTION(POINT(0 " +"0))')); \n" "\n" " st_astext\n" " ------------\n" " POINT(0 0)\n" " (1 row)\n" "\n" -" SELECT ST_AsText(ST_CollectionHomogenize('GEOMETRYCOLLECTION(POINT(0 0),POINT(1 1))')); \n" +" SELECT ST_AsText(ST_CollectionHomogenize('GEOMETRYCOLLECTION(POINT(0 0)," +"POINT(1 1))')); \n" "\n" " st_astext\n" " ---------------------\n" @@ -1077,11 +1120,14 @@ msgstr "" #: reference_editor.xml:682 #, no-c-format msgid "" -"SELECT ST_AsText(ST_Multi(ST_GeomFromText('POLYGON((743238 2967416,743238 2967450,\n" -" 743265 2967450,743265.625 2967416,743238 2967416))')));\n" +"SELECT ST_AsText(ST_Multi(ST_GeomFromText('POLYGON((743238 2967416,743238 " +"2967450,\n" +" 743265 2967450,743265.625 2967416,743238 " +"2967416))')));\n" " st_astext\n" " --------------------------------------------------------------------------------------------------\n" -" MULTIPOLYGON(((743238 2967416,743238 2967450,743265 2967450,743265.625 2967416,\n" +" MULTIPOLYGON(((743238 2967416,743238 2967450,743265 " +"2967450,743265.625 2967416,\n" " 743238 2967416)))\n" " (1 row)" msgstr "" @@ -1103,8 +1149,8 @@ msgstr "" #, no-c-format msgid "" "geometry ST_RemovePoint " -"geometry linestring" -" integer offset" +"geometry linestring " +"integer offset" msgstr "" #. Tag: para @@ -1120,7 +1166,8 @@ msgstr "" #, no-c-format msgid "" "--guarantee no LINESTRINGS are closed\n" -"--by removing the end point. The below assumes the_geom is of type LINESTRING\n" +"--by removing the end point. The below assumes the_geom is of type " +"LINESTRING\n" "UPDATE sometable\n" " SET the_geom = ST_RemovePoint(the_geom, ST_NPoints(the_geom) - 1)\n" " FROM sometable\n" @@ -1163,7 +1210,8 @@ msgstr "" #: reference_editor.xml:746 #, no-c-format msgid "" -"SELECT ST_AsText(the_geom) as line, ST_AsText(ST_Reverse(the_geom)) As reverseline\n" +"SELECT ST_AsText(the_geom) as line, ST_AsText(ST_Reverse(the_geom)) As " +"reverseline\n" "FROM\n" "(SELECT ST_MakeLine(ST_MakePoint(1,2),\n" " ST_MakePoint(1,10)) As the_geom) as foo;\n" @@ -1191,17 +1239,16 @@ msgstr "" msgid "" " geometry ST_Rotate " "geometry geomA " -"float rotRadians " -" geometry " +"float rotRadians geometry ST_Rotate geometry geomA float rotRadians float x0 float y0 geometry " "ST_Rotate geometry " "geomA float " -"rotRadians float " -"x0 float " -"y0 " -"geometry ST_Rotate " -"geometry geomA " -"float rotRadians " -"geometry " +"rotRadians geometry " "pointOrigin " msgstr "" @@ -1209,8 +1256,8 @@ msgstr "" #: reference_editor.xml:785 #, no-c-format msgid "" -"Rotates geometry rotRadians counter-clockwise about the origin. The rotation" -" origin can be specified either as a POINT geometry, or as x and y " +"Rotates geometry rotRadians counter-clockwise about the origin. The rotation " +"origin can be specified either as a POINT geometry, or as x and y " "coordinates. If the origin is not specified, the geometry is rotated about " "POINT(0 0)." msgstr "" @@ -1241,7 +1288,8 @@ msgid "" "(1 row)\n" "\n" "--Rotate 30 degrees counter-clockwise at x=50, y=160\n" -"SELECT ST_AsEWKT(ST_Rotate('LINESTRING (50 160, 50 50, 100 50)', pi()/6, 50, 160));\n" +"SELECT ST_AsEWKT(ST_Rotate('LINESTRING (50 160, 50 50, 100 50)', pi()/6, 50, " +"160));\n" " st_asewkt\n" "---------------------------------------------------------------------------\n" " LINESTRING(50 160,105 64.7372055837117,148.301270189222 89.7372055837117)\n" @@ -1249,7 +1297,8 @@ msgid "" "\n" "--Rotate 60 degrees clockwise from centroid\n" "SELECT ST_AsEWKT(ST_Rotate(geom, -pi()/3, ST_Centroid(geom)))\n" -"FROM (SELECT 'LINESTRING (50 160, 50 50, 100 50)'::geometry AS geom) AS foo;\n" +"FROM (SELECT 'LINESTRING (50 160, 50 50, 100 50)'::geometry AS geom) AS " +"foo;\n" " st_asewkt\n" "--------------------------------------------------------------\n" " LINESTRING(116.4225 130.6721,21.1597 75.6721,46.1597 32.3708)\n" @@ -1311,7 +1360,8 @@ msgstr "" #, no-c-format msgid "" "--Rotate a line 90 degrees along x-axis\n" -"SELECT ST_AsEWKT(ST_RotateX(ST_GeomFromEWKT('LINESTRING(1 2 3, 1 1 1)'), pi()/2));\n" +"SELECT ST_AsEWKT(ST_RotateX(ST_GeomFromEWKT('LINESTRING(1 2 3, 1 1 1)'), " +"pi()/2));\n" " st_asewkt\n" "---------------------------\n" " LINESTRING(1 -3 2,1 -1 1)" @@ -1355,8 +1405,8 @@ msgstr "" #, no-c-format msgid "" "ST_RotateY(geomA, rotRadians) is short-hand for " -"ST_Affine(geomA, cos(rotRadians), 0, sin(rotRadians), 0, 1, 0, " -"-sin(rotRadians), 0, cos(rotRadians), 0, 0, 0)." +"ST_Affine(geomA, cos(rotRadians), 0, sin(rotRadians), 0, 1, 0, -" +"sin(rotRadians), 0, cos(rotRadians), 0, 0, 0)." msgstr "" #. Tag: para @@ -1370,7 +1420,8 @@ msgstr "" #, no-c-format msgid "" "--Rotate a line 90 degrees along y-axis\n" -" SELECT ST_AsEWKT(ST_RotateY(ST_GeomFromEWKT('LINESTRING(1 2 3, 1 1 1)'), pi()/2));\n" +" SELECT ST_AsEWKT(ST_RotateY(ST_GeomFromEWKT('LINESTRING(1 2 3, 1 1 1)'), " +"pi()/2));\n" " st_asewkt\n" "---------------------------\n" " LINESTRING(3 2 -1,1 1 -1)" @@ -1435,18 +1486,21 @@ msgstr "" #, no-c-format msgid "" "--Rotate a line 90 degrees along z-axis\n" -"SELECT ST_AsEWKT(ST_RotateZ(ST_GeomFromEWKT('LINESTRING(1 2 3, 1 1 1)'), pi()/2));\n" +"SELECT ST_AsEWKT(ST_RotateZ(ST_GeomFromEWKT('LINESTRING(1 2 3, 1 1 1)'), " +"pi()/2));\n" " st_asewkt\n" "---------------------------\n" " LINESTRING(-2 1 3,-1 1 1)\n" "\n" " --Rotate a curved circle around z-axis\n" "SELECT ST_AsEWKT(ST_RotateZ(the_geom, pi()/2))\n" -"FROM (SELECT ST_LineToCurve(ST_Buffer(ST_GeomFromText('POINT(234 567)'), 3)) As the_geom) As foo;\n" +"FROM (SELECT ST_LineToCurve(ST_Buffer(ST_GeomFromText('POINT(234 567)'), 3)) " +"As the_geom) As foo;\n" "\n" " st_asewkt\n" "----------------------------------------------------------------------------------------------------------------------------\n" -" CURVEPOLYGON(CIRCULARSTRING(-567 237,-564.87867965644 236.12132034356,-564 234,-569.12132034356 231.87867965644,-567 237))" +" CURVEPOLYGON(CIRCULARSTRING(-567 237,-564.87867965644 236.12132034356,-564 " +"234,-569.12132034356 231.87867965644,-567 237))" msgstr "" #. Tag: para @@ -1477,16 +1531,15 @@ msgid "" "geometry geomA " "float XFactor " "float YFactor " -"float ZFactor " -" geometry " +"float ZFactor geometry ST_Scale geometry geomA float XFactor float YFactor geometry " "ST_Scale geometry " -"geomA float " -"XFactor float " -"YFactor " -"geometry ST_Scale " -"geometry geom " -"geometry factor " -"" +"geom geometry " +"factor " msgstr "" #. Tag: para @@ -1532,13 +1585,15 @@ msgstr "" #, no-c-format msgid "" "--Version 1: scale X, Y, Z\n" -"SELECT ST_AsEWKT(ST_Scale(ST_GeomFromEWKT('LINESTRING(1 2 3, 1 1 1)'), 0.5, 0.75, 0.8));\n" +"SELECT ST_AsEWKT(ST_Scale(ST_GeomFromEWKT('LINESTRING(1 2 3, 1 1 1)'), 0.5, " +"0.75, 0.8));\n" " st_asewkt\n" "--------------------------------------\n" " LINESTRING(0.5 1.5 2.4,0.5 0.75 0.8)\n" "\n" "--Version 2: Scale X Y\n" -" SELECT ST_AsEWKT(ST_Scale(ST_GeomFromEWKT('LINESTRING(1 2 3, 1 1 1)'), 0.5, 0.75));\n" +" SELECT ST_AsEWKT(ST_Scale(ST_GeomFromEWKT('LINESTRING(1 2 3, 1 1 1)'), 0.5, " +"0.75));\n" " st_asewkt\n" "----------------------------------\n" " LINESTRING(0.5 1.5 3,0.5 0.75 1)\n" @@ -1567,24 +1622,22 @@ msgstr "" #: reference_editor.xml:1043 #, no-c-format msgid "" -"Return a modified geometry/geography having no segment longer than the given" -" distance. Distance computation is performed in 2d only. For geometry, " -"length units are in units of spatial reference. For geography, units are in " -"meters." +"Return a modified geometry/geography having no segment longer than the given " +"distance. Distance computation is performed in 2d only. For geometry, length " +"units are in units of spatial reference. For geography, units are in meters." msgstr "" #. Tag: funcsynopsis #: reference_editor.xml:1049 #, no-c-format msgid "" -" geometry " -"ST_Segmentize geometry " -" geom float " -" max_segment_length " -" geography " -"ST_Segmentize geography " -" geog float " -" max_segment_length " +" geometry ST_Segmentize geometry geom float max_segment_length geography " +"ST_Segmentize geography geog float " +"max_segment_length " msgstr "" #. Tag: para @@ -1617,16 +1670,16 @@ msgid "" "construct SELECT ST_Segmentize('LINESTRING(1 2, 3 4)',0.5); " "will result in ambiguous function error. You need to have properly typed " "object e.g. a geometry/geography column, use ST_GeomFromText, " -"ST_GeogFromText or SELECT ST_Segmentize('LINESTRING(1 2, 3 " -"4)'::geometry,0.5);" +"ST_GeogFromText or SELECT ST_Segmentize('LINESTRING(1 2, 3 4)'::" +"geometry,0.5);" msgstr "" #. Tag: para #: reference_editor.xml:1073 #, no-c-format msgid "" -"This will only increase segments. It will not lengthen segments shorter than" -" max length" +"This will only increase segments. It will not lengthen segments shorter than " +"max length" msgstr "" #. Tag: programlisting @@ -1634,20 +1687,24 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_AsText(ST_Segmentize(\n" -"ST_GeomFromText('MULTILINESTRING((-29 -27,-30 -29.7,-36 -31,-45 -33),(-45 -33,-46 -32))')\n" +"ST_GeomFromText('MULTILINESTRING((-29 -27,-30 -29.7,-36 -31,-45 -33),(-45 " +"-33,-46 -32))')\n" " ,5)\n" ");\n" "st_astext\n" "--------------------------------------------------------------------------------------------------\n" -"MULTILINESTRING((-29 -27,-30 -29.7,-34.886615700134 -30.758766735029,-36 -31,\n" +"MULTILINESTRING((-29 -27,-30 -29.7,-34.886615700134 -30.758766735029,-36 " +"-31,\n" "-40.8809353009198 -32.0846522890933,-45 -33),\n" "(-45 -33,-46 -32))\n" "(1 row)\n" "\n" -"SELECT ST_AsText(ST_Segmentize(ST_GeomFromText('POLYGON((-29 28, -30 40, -29 28))'),10));\n" +"SELECT ST_AsText(ST_Segmentize(ST_GeomFromText('POLYGON((-29 28, -30 40, -29 " +"28))'),10));\n" "st_astext\n" "-----------------------\n" -"POLYGON((-29 28,-29.8304547985374 37.9654575824488,-30 40,-29.1695452014626 30.0345424175512,-29 28))\n" +"POLYGON((-29 28,-29.8304547985374 37.9654575824488,-30 40,-29.1695452014626 " +"30.0345424175512,-29 28))\n" "(1 row)" msgstr "" @@ -1668,10 +1725,10 @@ msgstr "" #, no-c-format msgid "" "geometry ST_SetPoint " -"geometry linestring" -" integer " -"zerobasedposition " -"geometry point" +"geometry linestring " +"integer zerobasedposition geometry point" msgstr "" #. Tag: para @@ -1679,8 +1736,8 @@ msgstr "" #, no-c-format msgid "" "Replace point N of linestring with given point. Index is 0-based. This is " -"especially useful in triggers when trying to maintain relationship of joints" -" when one vertex moves." +"especially useful in triggers when trying to maintain relationship of joints " +"when one vertex moves." msgstr "" #. Tag: programlisting @@ -1693,9 +1750,12 @@ msgid "" "-----------------------\n" " LINESTRING(-1 1,-1 3)\n" "\n" -"---Change last point in a line string (lets play with 3d linestring this time)\n" -"SELECT ST_AsEWKT(ST_SetPoint(foo.the_geom, ST_NumPoints(foo.the_geom) - 1, ST_GeomFromEWKT('POINT(-1 1 3)')))\n" -"FROM (SELECT ST_GeomFromEWKT('LINESTRING(-1 2 3,-1 3 4, 5 6 7)') As the_geom) As foo;\n" +"---Change last point in a line string (lets play with 3d linestring this " +"time)\n" +"SELECT ST_AsEWKT(ST_SetPoint(foo.the_geom, ST_NumPoints(foo.the_geom) - 1, " +"ST_GeomFromEWKT('POINT(-1 1 3)')))\n" +"FROM (SELECT ST_GeomFromEWKT('LINESTRING(-1 2 3,-1 3 4, 5 6 7)') As " +"the_geom) As foo;\n" " st_asewkt\n" "-----------------------\n" "LINESTRING(-1 2 3,-1 3 4,-1 1 3)" @@ -1743,8 +1803,8 @@ msgstr "" #, no-c-format msgid "" "This function does not transform the geometry coordinates in any way - it " -"simply sets the meta data defining the spatial reference system the geometry" -" is assumed to be in. Use if you want to " +"simply sets the meta data defining the spatial reference system the geometry " +"is assumed to be in. Use if you want to " "transform the geometry into a new projection." msgstr "" @@ -1781,7 +1841,8 @@ msgstr "" #: reference_editor.xml:1169 #, no-c-format msgid "" -"SELECT ST_Transform(ST_SetSRID(ST_Point(-123.365556, 48.428611),4326),3785) As spere_merc;\n" +"SELECT ST_Transform(ST_SetSRID(ST_Point(-123.365556, 48.428611),4326),3785) " +"As spere_merc;\n" "-- the ewkt representation (wrap with ST_AsEWKT) -\n" "SRID=3785;POINT(-13732990.8753491 6178458.96425423)" msgstr "" @@ -1790,9 +1851,9 @@ msgstr "" #: reference_editor.xml:1175 #, no-c-format msgid "" -", , , , , " +", , , , , " msgstr "" #. Tag: refname @@ -1811,30 +1872,28 @@ msgstr "" #: reference_editor.xml:1190 #, no-c-format msgid "" -" geometry " -"ST_SnapToGrid geometry " -" geomA float " -" originX float " -" originY float " -" sizeX float " -" sizeY " -" geometry " -"ST_SnapToGrid geometry " -" geomA float " -" sizeX float " -" sizeY " -" geometry " -"ST_SnapToGrid geometry " -" geomA float " -" size " -" geometry " -"ST_SnapToGrid geometry " -" geomA geometry " -" pointOrigin float " -" sizeX float " -" sizeY float " -" sizeZ float " -" sizeM " +" geometry ST_SnapToGrid geometry geomA float originX float originY float sizeX float sizeY geometry " +"ST_SnapToGrid geometry geomA float " +"sizeX float " +"sizeY " +"geometry ST_SnapToGrid " +"geometry geomA " +"float size geometry ST_SnapToGrid geometry geomA geometry " +"pointOrigin float " +"sizeX float " +"sizeY float " +"sizeZ float " +"sizeM " msgstr "" #. Tag: para @@ -1861,8 +1920,8 @@ msgstr "" #: reference_editor.xml:1242 #, no-c-format msgid "" -"The returned geometry might loose its simplicity (see )." +"The returned geometry might loose its simplicity (see )." msgstr "" #. Tag: para @@ -1896,7 +1955,8 @@ msgid "" " SET the_geom = ST_SnapToGrid(the_geom, 0.001);\n" "\n" "SELECT ST_AsText(ST_SnapToGrid(\n" -" ST_GeomFromText('LINESTRING(1.1115678 2.123, 4.111111 3.2374897, 4.11112 3.23748667)'),\n" +" ST_GeomFromText('LINESTRING(1.1115678 2.123, " +"4.111111 3.2374897, 4.11112 3.23748667)'),\n" " 0.001)\n" " );\n" " st_astext\n" @@ -1905,16 +1965,20 @@ msgid "" " --Snap a 4d geometry\n" "SELECT ST_AsEWKT(ST_SnapToGrid(\n" " ST_GeomFromEWKT('LINESTRING(-1.1115678 2.123 2.3456 1.11111,\n" -" 4.111111 3.2374897 3.1234 1.1111, -1.11111112 2.123 2.3456 1.1111112)'),\n" +" 4.111111 3.2374897 3.1234 1.1111, -1.11111112 2.123 2.3456 " +"1.1111112)'),\n" " ST_GeomFromEWKT('POINT(1.12 2.22 3.2 4.4444)'),\n" " 0.1, 0.1, 0.1, 0.01) );\n" " st_asewkt\n" "------------------------------------------------------------------------------\n" -" LINESTRING(-1.08 2.12 2.3 1.1144,4.12 3.22 3.1 1.1144,-1.08 2.12 2.3 1.1144)\n" +" LINESTRING(-1.08 2.12 2.3 1.1144,4.12 3.22 3.1 1.1144,-1.08 2.12 2.3 " +"1.1144)\n" "\n" "\n" -"--With a 4d geometry - the ST_SnapToGrid(geom,size) only touches x and y coords but keeps m and z the same\n" -"SELECT ST_AsEWKT(ST_SnapToGrid(ST_GeomFromEWKT('LINESTRING(-1.1115678 2.123 3 2.3456,\n" +"--With a 4d geometry - the ST_SnapToGrid(geom,size) only touches x and y " +"coords but keeps m and z the same\n" +"SELECT ST_AsEWKT(ST_SnapToGrid(ST_GeomFromEWKT('LINESTRING(-1.1115678 2.123 " +"3 2.3456,\n" " 4.111111 3.2374897 3.1234 1.1111)'),\n" " 0.01) );\n" " st_asewkt\n" @@ -1951,16 +2015,16 @@ msgstr "" msgid "" "geometry ST_Snap " "geometry input " -"geometry reference" -" float tolerance" +"geometry reference " +"float tolerance" msgstr "" #. Tag: para #: reference_editor.xml:1306 #, no-c-format msgid "" -"Snaps the vertices and segments of a geometry another Geometry's vertices. A" -" snap distance tolerance is used to control where snapping is performed." +"Snaps the vertices and segments of a geometry another Geometry's vertices. A " +"snap distance tolerance is used to control where snapping is performed." msgstr "" #. Tag: para @@ -1986,9 +2050,8 @@ msgstr "" #: reference_editor.xml:1327 #, no-c-format msgid "" -"The returned geometry might loose its simplicity (see ) and validity (see )." +"The returned geometry might loose its simplicity (see ) and validity (see )." msgstr "" #. Tag: para @@ -2007,15 +2070,16 @@ msgstr "" #: reference_editor.xml:1362 #, no-c-format msgid "" -"A multipolygon snapped to linestring to tolerance: 1.01 of distance. The new" -" multipolygon is shown with reference linestring" +"A multipolygon snapped to linestring to tolerance: 1.01 of distance. The new " +"multipolygon is shown with reference linestring" msgstr "" #. Tag: programlisting #: reference_editor.xml:1366 #, no-c-format msgid "" -"SELECT ST_AsText(ST_Snap(poly,line, ST_Distance(poly,line)*1.01)) AS polysnapped\n" +"SELECT ST_AsText(ST_Snap(poly,line, ST_Distance(poly,line)*1.01)) AS " +"polysnapped\n" "FROM (SELECT \n" " ST_GeomFromText('MULTIPOLYGON(\n" " ((26 125, 26 200, 126 200, 126 125, 26 125 ),\n" @@ -2035,8 +2099,8 @@ msgstr "" #: reference_editor.xml:1373 #, no-c-format msgid "" -"A multipolygon snapped to linestring to tolerance: 1.25 of distance. The new" -" multipolygon is shown with reference linestring" +"A multipolygon snapped to linestring to tolerance: 1.25 of distance. The new " +"multipolygon is shown with reference linestring" msgstr "" #. Tag: programlisting @@ -2109,7 +2173,8 @@ msgid "" " (( 26 125, 26 200, 126 200, 126 125, 26 125 ),\n" " (51 150, 101 150, 76 175, 51 150 )), \n" " ((151 100, 151 200, 176 175, 151 100 )))') As poly,\n" -" ST_GeomFromText('LINESTRING (5 107, 54 84, 101 100)') As line \n" +" ST_GeomFromText('LINESTRING (5 107, 54 84, 101 100)') As " +"line \n" " ) As foo;\n" " linesnapped\n" "---------------------------------------\n" @@ -2143,8 +2208,8 @@ msgstr "" #: reference_editor.xml:1442 #, no-c-format msgid "" -"Returns a new geometry with its coordinates transformed to spatial reference" -" system referenced by the SRID integer parameter. The destination SRID must " +"Returns a new geometry with its coordinates transformed to spatial reference " +"system referenced by the SRID integer parameter. The destination SRID must " "exist in the SPATIAL_REF_SYS table." msgstr "" @@ -2162,9 +2227,8 @@ msgstr "" #: reference_editor.xml:1450 #, no-c-format msgid "" -"Requires PostGIS be compiled with Proj support. Use to confirm you have proj support compiled" -" in." +"Requires PostGIS be compiled with Proj support. Use to confirm you have proj support compiled in." msgstr "" #. Tag: para @@ -2191,22 +2255,29 @@ msgstr "" #: reference_editor.xml:1470 #, no-c-format msgid "" -"SELECT ST_AsText(ST_Transform(ST_GeomFromText('POLYGON((743238 2967416,743238 2967450,\n" -" 743265 2967450,743265.625 2967416,743238 2967416))',2249),4326)) As wgs_geom;\n" +"SELECT ST_AsText(ST_Transform(ST_GeomFromText('POLYGON((743238 " +"2967416,743238 2967450,\n" +" 743265 2967450,743265.625 2967416,743238 2967416))',2249),4326)) As " +"wgs_geom;\n" "\n" " wgs_geom\n" "---------------------------\n" -" POLYGON((-71.1776848522251 42.3902896512902,-71.1776843766326 42.3903829478009,\n" -"-71.1775844305465 42.3903826677917,-71.1775825927231 42.3902893647987,-71.177684\n" +" POLYGON((-71.1776848522251 42.3902896512902,-71.1776843766326 " +"42.3903829478009,\n" +"-71.1775844305465 42.3903826677917,-71.1775825927231 " +"42.3902893647987,-71.177684\n" "8522251 42.3902896512902));\n" "(1 row)\n" "\n" "--3D Circular String example\n" -"SELECT ST_AsEWKT(ST_Transform(ST_GeomFromEWKT('SRID=2249;CIRCULARSTRING(743238 2967416 1,743238 2967450 2,743265 2967450 3,743265.625 2967416 3,743238 2967416 4)'),4326));\n" +"SELECT ST_AsEWKT(ST_Transform(ST_GeomFromEWKT('SRID=2249;" +"CIRCULARSTRING(743238 2967416 1,743238 2967450 2,743265 2967450 3,743265.625 " +"2967416 3,743238 2967416 4)'),4326));\n" "\n" " st_asewkt\n" "--------------------------------------------------------------------------------------\n" -" SRID=4326;CIRCULARSTRING(-71.1776848522251 42.3902896512902 1,-71.1776843766326 42.3903829478009 2,\n" +" SRID=4326;CIRCULARSTRING(-71.1776848522251 42.3902896512902 " +"1,-71.1776843766326 42.3903829478009 2,\n" " -71.1775844305465 42.3903826677917 3,\n" " -71.1775825927231 42.3902893647987 3,-71.1776848522251 42.3902896512902 4)" msgstr "" @@ -2215,10 +2286,10 @@ msgstr "" #: reference_editor.xml:1471 #, no-c-format msgid "" -"Example of creating a partial functional index. For tables where you are not" -" sure all the geometries will be filled in, its best to use a partial index " -"that leaves out null geometries which will both conserve space and make your" -" index smaller and more efficient." +"Example of creating a partial functional index. For tables where you are not " +"sure all the geometries will be filled in, its best to use a partial index " +"that leaves out null geometries which will both conserve space and make your " +"index smaller and more efficient." msgstr "" #. Tag: programlisting @@ -2243,8 +2314,8 @@ msgstr "" #, no-c-format msgid "" "Sometimes coordinate transformation involving a grid-shift can fail, for " -"example if PROJ.4 has not been built with grid-shift files or the coordinate" -" does not lie within the range for which the grid shift is defined. By " +"example if PROJ.4 has not been built with grid-shift files or the coordinate " +"does not lie within the range for which the grid shift is defined. By " "default, PostGIS will throw an error if a grid shift file is not present, " "but this behaviour can be configured on a per-SRID basis by altering the " "proj4text value within the spatial_ref_sys table." @@ -2268,8 +2339,8 @@ msgstr "" #: reference_editor.xml:1481 #, no-c-format msgid "" -"The @ prefix means no error is reported if the files are not present, but if" -" the end of the list is reached with no file having been appropriate (ie. " +"The @ prefix means no error is reported if the files are not present, but if " +"the end of the list is reached with no file having been appropriate (ie. " "found and overlapping) then an error is issued." msgstr "" @@ -2292,8 +2363,8 @@ msgstr "" #: reference_editor.xml:1484 #, no-c-format msgid "" -"The null grid shift file is a valid grid shift file covering the whole world" -" and applying no shift. So for a complete example, if you wanted to alter " +"The null grid shift file is a valid grid shift file covering the whole world " +"and applying no shift. So for a complete example, if you wanted to alter " "PostGIS so that transformations to SRID 4267 that didn't lie within the " "correct range did not throw an ERROR, you would use the following:" msgstr "" @@ -2303,8 +2374,8 @@ msgstr "" #, no-c-format msgid "" "UPDATE spatial_ref_sys SET proj4text = '+proj=longlat +ellps=clrk66 " -"+nadgrids=@conus,@alaska,@ntv2_0.gsb,@ntv1_can.dat,null +no_defs' WHERE srid" -" = 4267;" +"+nadgrids=@conus,@alaska,@ntv2_0.gsb,@ntv1_can.dat,null +no_defs' WHERE srid " +"= 4267;" msgstr "" #. Tag: para @@ -2333,25 +2404,24 @@ msgstr "" #: reference_editor.xml:1505 #, no-c-format msgid "" -" geometry " -"ST_Translate geometry " -" g1 float " +" geometry ST_Translate geometry g1 float deltax float deltay geometry " +"ST_Translate geometry " +"g1 float " "deltax float " -"deltay " -"geometry ST_Translate " -"geometry g1 " -"float deltax " -"float deltay " -"float deltaz " -"" +"deltay float " +"deltaz " msgstr "" #. Tag: para #: reference_editor.xml:1525 #, no-c-format msgid "" -"Returns a new geometry whose coordinates are translated delta x,delta " -"y,delta z units. Units are based on the units defined in spatial reference " +"Returns a new geometry whose coordinates are translated delta x,delta y," +"delta z units. Units are based on the units defined in spatial reference " "(SRID) for this geometry." msgstr "" @@ -2365,7 +2435,8 @@ msgstr "" #: reference_editor.xml:1538 #, no-c-format msgid "" -"SELECT ST_AsText(ST_Translate(ST_GeomFromText('POINT(-71.01 42.37)',4326),1,0)) As wgs_transgeomtxt;\n" +"SELECT ST_AsText(ST_Translate(ST_GeomFromText('POINT(-71.01 " +"42.37)',4326),1,0)) As wgs_transgeomtxt;\n" "\n" " wgs_transgeomtxt\n" " ---------------------\n" @@ -2382,7 +2453,8 @@ msgstr "" #: reference_editor.xml:1540 #, no-c-format msgid "" -"SELECT ST_AsText(ST_Translate(ST_GeomFromText('LINESTRING(-71.01 42.37,-71.11 42.38)',4326),1,0.5)) As wgs_transgeomtxt;\n" +"SELECT ST_AsText(ST_Translate(ST_GeomFromText('LINESTRING(-71.01 " +"42.37,-71.11 42.38)',4326),1,0.5)) As wgs_transgeomtxt;\n" " wgs_transgeomtxt\n" " ---------------------------------------\n" " LINESTRING(-70.01 42.87,-70.11 42.88)" @@ -2414,10 +2486,12 @@ msgstr "" #: reference_editor.xml:1544 #, no-c-format msgid "" -"SELECT ST_AsText(ST_Translate(ST_Collect('CURVEPOLYGON(CIRCULARSTRING(4 3,3.12 0.878,1 0,-1.121 5.1213,6 7, 8 9,4 3))','POINT(1 3)'),1,2));\n" +"SELECT ST_AsText(ST_Translate(ST_Collect('CURVEPOLYGON(CIRCULARSTRING(4 " +"3,3.12 0.878,1 0,-1.121 5.1213,6 7, 8 9,4 3))','POINT(1 3)'),1,2));\n" " st_astext\n" "------------------------------------------------------------------------------------------------------------\n" -" GEOMETRYCOLLECTION(CURVEPOLYGON(CIRCULARSTRING(5 5,4.12 2.878,2 2,-0.121 7.1213,7 9,9 11,5 5)),POINT(2 5))" +" GEOMETRYCOLLECTION(CURVEPOLYGON(CIRCULARSTRING(5 5,4.12 2.878,2 2,-0.121 " +"7.1213,7 9,9 11,5 5)),POINT(2 5))" msgstr "" #. Tag: para @@ -2464,26 +2538,30 @@ msgstr "" #: reference_editor.xml:1582 #, no-c-format msgid "" -"ST_TransScale(geomA, deltaX, deltaY, XFactor, YFactor) is " -"short-hand for ST_Affine(geomA, XFactor, 0, 0, 0, YFactor, 0, 0, 0, 1," -" deltaX*XFactor, deltaY*YFactor, 0)." +"ST_TransScale(geomA, deltaX, deltaY, XFactor, YFactor) is short-" +"hand for ST_Affine(geomA, XFactor, 0, 0, 0, YFactor, 0, 0, 0, 1, " +"deltaX*XFactor, deltaY*YFactor, 0)." msgstr "" #. Tag: programlisting #: reference_editor.xml:1598 #, no-c-format msgid "" -"SELECT ST_AsEWKT(ST_TransScale(ST_GeomFromEWKT('LINESTRING(1 2 3, 1 1 1)'), 0.5, 1, 1, 2));\n" +"SELECT ST_AsEWKT(ST_TransScale(ST_GeomFromEWKT('LINESTRING(1 2 3, 1 1 1)'), " +"0.5, 1, 1, 2));\n" " st_asewkt\n" "-----------------------------\n" " LINESTRING(1.5 6 3,1.5 4 1)\n" "\n" "\n" -"--Buffer a point to get an approximation of a circle, convert to curve and then translate 1,2 and scale it 3,4\n" -" SELECT ST_AsText(ST_Transscale(ST_LineToCurve(ST_Buffer('POINT(234 567)', 3)),1,2,3,4));\n" +"--Buffer a point to get an approximation of a circle, convert to curve and " +"then translate 1,2 and scale it 3,4\n" +" SELECT ST_AsText(ST_Transscale(ST_LineToCurve(ST_Buffer('POINT(234 567)', " +"3)),1,2,3,4));\n" " st_astext\n" "------------------------------------------------------------------------------------------------------------------------------\n" -" CURVEPOLYGON(CIRCULARSTRING(714 2276,711.363961030679 2267.51471862576,705 2264,698.636038969321 2284.48528137424,714 2276))" +" CURVEPOLYGON(CIRCULARSTRING(714 2276,711.363961030679 2267.51471862576,705 " +"2264,698.636038969321 2284.48528137424,714 2276))" msgstr "" #. Tag: para diff --git a/doc/po/de_DE/reference_exception.xml.po b/doc/po/de_DE/reference_exception.xml.po index ac7a877ab..d78154906 100644 --- a/doc/po/de_DE/reference_exception.xml.po +++ b/doc/po/de_DE/reference_exception.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2012-09-14 17:50+0000\n" "PO-Revision-Date: 2015-09-29 11:54+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -61,8 +62,8 @@ msgstr "Beschreibung" #: 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." +"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 @@ -138,8 +139,8 @@ 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." +"when your ST_Intersects and other relation queries leave out geometries that " +"rightfully should return true." msgstr "" #. Tag: para @@ -161,7 +162,9 @@ msgstr "" #, 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" +" --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" @@ -203,8 +206,8 @@ msgstr "" #, no-c-format msgid "" "Returns TRUE if the bbox of this geometry is cached, FALSE otherwise. Use " -" and " -" to control caching." +" and " +"to control caching." msgstr "" #. Tag: programlisting diff --git a/doc/po/de_DE/reference_guc.xml.po b/doc/po/de_DE/reference_guc.xml.po index 95ae052f6..bf638424e 100644 --- a/doc/po/de_DE/reference_guc.xml.po +++ b/doc/po/de_DE/reference_guc.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,20 +8,21 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:23+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: para #: reference_guc.xml:5 #, no-c-format msgid "" -"This section lists custom PostGIS Grand Unified Custom Variables(GUC). These" -" can be set globally, by database, by session or by transaction. Best set at" -" global or database level." +"This section lists custom PostGIS Grand Unified Custom Variables(GUC). These " +"can be set globally, by database, by session or by transaction. Best set at " +"global or database level." msgstr "" #. Tag: title @@ -155,9 +156,9 @@ msgstr "" #: reference_guc.xml:61 #, no-c-format msgid "" -"Additional information about GDAL_DATA is available at GDAL's Configuration " -"Options." +"Additional information about GDAL_DATA is available at GDAL's Configuration Options." msgstr "" #. Tag: para @@ -233,18 +234,17 @@ msgstr "" #, no-c-format msgid "" "Enabled GDAL specified drivers can be specified by the driver's short-name " -"or code. Driver short-names or codes can be found at GDAL Raster Formats. " -"Multiple drivers can be specified by putting a space between each driver." +"or code. Driver short-names or codes can be found at GDAL Raster Formats. Multiple drivers " +"can be specified by putting a space between each driver." msgstr "" #. Tag: para #: reference_guc.xml:109 #, no-c-format msgid "" -"There are three special codes available for " -"postgis.gdal_enabled_drivers. The codes are case-" -"sensitive." +"There are three special codes available for postgis." +"gdal_enabled_drivers. The codes are case-sensitive." msgstr "" #. Tag: para @@ -283,17 +283,17 @@ msgstr "" #: reference_guc.xml:130 #, no-c-format msgid "" -"In the standard PostGIS installation, " -"postgis.gdal_enabled_drivers is set to DISABLE_ALL." +"In the standard PostGIS installation, postgis.gdal_enabled_drivers is set to DISABLE_ALL." msgstr "" #. Tag: para #: reference_guc.xml:136 #, no-c-format msgid "" -"Additional information about GDAL_SKIP is available at GDAL's Configuration " -"Options." +"Additional information about GDAL_SKIP is available at GDAL's Configuration Options." msgstr "" #. Tag: para @@ -382,16 +382,15 @@ msgstr "" #. Tag: refpurpose #: reference_guc.xml:181 #, no-c-format -msgid "" -"A boolean configuration option to enable access to out-db raster bands." +msgid "A boolean configuration option to enable access to out-db raster bands." msgstr "" #. Tag: para #: reference_guc.xml:188 #, no-c-format msgid "" -"A boolean configuration option to enable access to out-db raster bands. This" -" option can be set in PostgreSQL's configuration file: postgresql.conf. It " +"A boolean configuration option to enable access to out-db raster bands. This " +"option can be set in PostgreSQL's configuration file: postgresql.conf. It " "can also be set by connection or transaction." msgstr "" @@ -401,8 +400,8 @@ msgstr "" msgid "" "The initial value of postgis.enable_outdb_rasters may " "also be set by passing the environment variable " -"POSTGIS_ENABLE_OUTDB_RASTERS with a non-zero value to the" -" process starting PostgreSQL." +"POSTGIS_ENABLE_OUTDB_RASTERS with a non-zero value to the " +"process starting PostgreSQL." msgstr "" #. Tag: para @@ -418,8 +417,8 @@ msgstr "" #: reference_guc.xml:203 #, no-c-format msgid "" -"In the standard PostGIS installation, " -"postgis.enable_outdb_rasters is set to False." +"In the standard PostGIS installation, postgis.enable_outdb_rasters is set to False." msgstr "" #. Tag: para diff --git a/doc/po/de_DE/reference_lrs.xml.po b/doc/po/de_DE/reference_lrs.xml.po index 9cbd8299b..bf4e9c440 100644 --- a/doc/po/de_DE/reference_lrs.xml.po +++ b/doc/po/de_DE/reference_lrs.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:23+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -41,9 +42,9 @@ msgstr "" #, no-c-format msgid "" "geometry ST_LineInterpolatePoint " -"geometry " -"a_linestring float8 " -" a_fraction" +"geometry a_linestring float8 a_fraction" msgstr "" #. Tag: title @@ -118,7 +119,8 @@ msgstr "" msgid "" "--Return point 20% along 2d line\n" "SELECT ST_AsEWKT(ST_LineInterpolatePoint(the_line, 0.20))\n" -" FROM (SELECT ST_GeomFromEWKT('LINESTRING(25 50, 100 125, 150 190)') as the_line) As foo;\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)" @@ -130,7 +132,8 @@ msgstr "" msgid "" "--Return point mid-way of 3d line\n" "SELECT ST_AsEWKT(ST_LineInterpolatePoint(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" +" 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" @@ -138,8 +141,10 @@ msgid "" "\n" "\n" "--find closest point on a line to a point or other geometry\n" -" SELECT ST_AsText(ST_LineInterpolatePoint(foo.the_line, ST_LineLocatePoint(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" +" SELECT ST_AsText(ST_LineInterpolatePoint(foo.the_line, " +"ST_LineLocatePoint(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)" @@ -181,9 +186,9 @@ msgstr "" #, no-c-format msgid "" "float8 ST_LineLocatePoint " -"geometry " -"a_linestring geometry " -" a_point" +"geometry a_linestring geometry a_point" msgstr "" #. Tag: para @@ -191,17 +196,17 @@ msgstr "" #, 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." +"point on LineString to the given Point, as a fraction of total 2d line length." msgstr "" #. Tag: para #: reference_lrs.xml:92 #, no-c-format msgid "" -"You can use the returned location to extract a Point () or a substring ()." +"You can use the returned location to extract a Point () or a substring ()." msgstr "" #. Tag: para @@ -226,7 +231,8 @@ msgstr "" #: reference_lrs.xml:105 #, no-c-format msgid "" -"--Rough approximation of finding the street number of a point along the street\n" +"--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" @@ -234,7 +240,8 @@ msgid "" "SELECT ST_AsText(house_loc) As as_text_house_loc,\n" " startstreet_num +\n" " CAST( (endstreet_num - startstreet_num)\n" -" * ST_LineLocatePoint(street_line, house_loc) As integer) As street_num\n" +" * ST_LineLocatePoint(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" @@ -250,8 +257,10 @@ msgid "" " 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_LineInterpolatePoint(foo.the_line, ST_LineLocatePoint(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" +" SELECT ST_AsText(ST_LineInterpolatePoint(foo.the_line, " +"ST_LineLocatePoint(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)" @@ -261,8 +270,8 @@ msgstr "" #: reference_lrs.xml:112 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -285,10 +294,10 @@ msgstr "" #, no-c-format msgid "" "geometry ST_LineSubstring " -"geometry " -"a_linestring float8 " -" startfraction " -"float8 endfraction" +"geometry a_linestring float8 startfraction float8 endfraction" msgstr "" #. Tag: para @@ -297,17 +306,17 @@ msgstr "" 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 ." +"float8 values between 0 and 1. This only works with LINESTRINGs. To use with " +"contiguous MULTILINESTRINGs use in conjunction with ." msgstr "" #. Tag: para #: reference_lrs.xml:146 #, no-c-format msgid "" -"If 'start' and 'end' have the same value this is equivalent to ." +"If 'start' and 'end' have the same value this is equivalent to ." msgstr "" #. Tag: para @@ -341,18 +350,21 @@ msgstr "" #, 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" +"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" +"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" +"-- 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" @@ -376,8 +388,8 @@ msgstr "" #: reference_lrs.xml:180 #, no-c-format msgid "" -", , " +", , " msgstr "" #. Tag: refname @@ -391,8 +403,8 @@ msgstr "" #, no-c-format msgid "" "Return a derived geometry collection value with elements that " -"match the specified measure. Polygonal elements are not " -"supported." +"match the specified measure. Polygonal elements are not supported." msgstr "" #. Tag: funcprototype @@ -400,10 +412,10 @@ msgstr "" #, no-c-format msgid "" "geometry ST_LocateAlong " -"geometry " -"ageom_with_measure float8 " -" a_measure float8 offset" +"geometry ageom_with_measure float8 a_measure float8 offset" msgstr "" #. Tag: para @@ -427,8 +439,8 @@ msgstr "" #: reference_lrs.xml:216 reference_lrs.xml:269 #, no-c-format msgid "" -"Semantic is specified by: ISO/IEC CD 13249-3:200x(E) - Text for Continuation" -" CD Editing Meeting" +"Semantic is specified by: ISO/IEC CD 13249-3:200x(E) - Text for Continuation " +"CD Editing Meeting" msgstr "" #. Tag: para @@ -465,7 +477,8 @@ 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" +" 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" @@ -477,7 +490,8 @@ msgid "" "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" +" 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" @@ -514,10 +528,10 @@ msgstr "" msgid "" "geometry ST_LocateBetween " "geometry geomA " -"float8 " -"measure_start float8 " -" measure_end float8 offset" +"float8 measure_start float8 measure_end float8 offset" msgstr "" #. Tag: para @@ -551,7 +565,8 @@ 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" +" 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" @@ -563,7 +578,8 @@ msgid "" "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" +" 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" @@ -598,10 +614,10 @@ msgstr "" #, no-c-format msgid "" "geometry ST_LocateBetweenElevations " -"geometry " -"geom_mline float8 " -"elevation_start float8 " -" elevation_end" +"geometry geom_mline float8 elevation_start float8 " +"elevation_end" msgstr "" #. Tag: para @@ -624,13 +640,15 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_AsEWKT(ST_LocateBetweenElevations(\n" -" ST_GeomFromEWKT('LINESTRING(1 2 3, 4 5 6)'),2,4)) As ewelev;\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" +" ST_GeomFromEWKT('LINESTRING(1 2 6, 4 5 -1, 7 8 " +"9)'),6,9)) As ewelev;\n" "\n" " ewelev\n" "----------------------------------------------------------------\n" @@ -641,7 +659,8 @@ msgid "" "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" +" 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" @@ -699,7 +718,8 @@ msgstr "" #. Tag: para #: reference_lrs.xml:377 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -721,10 +741,10 @@ msgstr "" #, no-c-format msgid "" "geometry ST_AddMeasure " -"geometry " -"geom_mline float8 " -"measure_start float8 " -" measure_end" +"geometry geom_mline float8 measure_start float8 measure_end" msgstr "" #. Tag: para @@ -766,7 +786,8 @@ msgid "" " 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" +"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))" diff --git a/doc/po/de_DE/reference_management.xml.po b/doc/po/de_DE/reference_management.xml.po index bf3008736..b31e24c8f 100644 --- a/doc/po/de_DE/reference_management.xml.po +++ b/doc/po/de_DE/reference_management.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:23+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -40,38 +41,34 @@ msgstr "" #: reference_management.xml:15 #, no-c-format msgid "" -" text " -"AddGeometryColumn varchar " -" table_name varchar" -" column_name " -"integer srid " -"varchar type " -"integer dimension " -"boolean " +" text AddGeometryColumn varchar table_name varchar column_name integer srid varchar type integer dimension boolean " "use_typmod=true " -" text " -"AddGeometryColumn varchar " -" schema_name " -"varchar table_name" -" varchar " -"column_name integer " -" srid varchar " -" type integer " -" dimension boolean " +" text AddGeometryColumn varchar schema_name varchar table_name varchar column_name integer srid varchar type integer dimension boolean " "use_typmod=true " -" text " -"AddGeometryColumn varchar " -" catalog_name " -"varchar " -"schema_name varchar " -" table_name varchar" -" column_name " -"integer srid " -"varchar type " -"integer dimension " -"boolean " -"use_typmod=true " +" text AddGeometryColumn varchar catalog_name varchar " +"schema_name varchar table_name varchar column_name integer " +" srid varchar type integer " +"dimension boolean use_typmod=true " msgstr "" #. Tag: title @@ -109,8 +106,8 @@ msgid "" "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: ALTER TABLE some_table" -" ADD COLUMN geom geometry(Point,4326);" +"column with this function is now equivalent to: ALTER TABLE some_table " +"ADD COLUMN geom geometry(Point,4326);" msgstr "" #. Tag: para @@ -131,8 +128,8 @@ msgid "" "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 ." +"registered correctly in geometry_columns. Refer to ." msgstr "" #. Tag: para @@ -187,19 +184,25 @@ msgid "" "\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" +" 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" +" 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" +"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" +"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" +"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" @@ -209,24 +212,30 @@ msgid "" "(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" +" 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_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" +" WHERE f_table_name = 'my_spatial_table' AND f_table_schema = " +"'my_schema';\n" "\n" " col_name | type | srid | ndims \n" "----------+--------------+------+-------\n" @@ -251,9 +260,8 @@ msgstr "Siehe auch" #: reference_management.xml:132 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -272,23 +280,20 @@ msgstr "" #: reference_management.xml:145 #, no-c-format msgid "" -" text " -"DropGeometryColumn varchar " -" table_name varchar" -" column_name " -" text " -"DropGeometryColumn varchar " -" schema_name " -"varchar table_name" -" varchar " -"column_name " -" text " -"DropGeometryColumn varchar " -" catalog_name " -"varchar " -"schema_name varchar " -" table_name varchar" -" column_name " +" text DropGeometryColumn varchar table_name varchar column_name text " +"DropGeometryColumn varchar schema_name varchar " +" table_name varchar " +" column_name " +" text DropGeometryColumn varchar catalog_name varchar " +"schema_name varchar table_name varchar column_name " msgstr "" #. Tag: para @@ -328,7 +333,8 @@ msgstr "" #. Tag: para #: reference_management.xml:210 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -347,19 +353,17 @@ msgstr "" #: reference_management.xml:223 #, no-c-format msgid "" -" boolean " -"DropGeometryTable varchar " +" boolean DropGeometryTable varchar table_name boolean " +"DropGeometryTable varchar schema_name varchar " " table_name " -" boolean " -"DropGeometryTable varchar " -" schema_name " -"varchar table_name" -" boolean " -"DropGeometryTable varchar " -" catalog_name " -"varchar " -"schema_name varchar " -" table_name " +" boolean DropGeometryTable varchar catalog_name varchar " +"schema_name varchar table_name " msgstr "" #. Tag: para @@ -377,8 +381,8 @@ msgstr "" 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 DROP" -" TABLE" +"can drop a table with geometry columns like any other table using DROP " +"TABLE" msgstr "" #. Tag: programlisting @@ -396,7 +400,9 @@ msgstr "" #. Tag: para #: reference_management.xml:274 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -435,8 +441,10 @@ msgid "" "SELECT PostGIS_Full_Version();\n" " postgis_full_version\n" "----------------------------------------------------------------------------------\n" -"POSTGIS=\"2.2.0dev r12699\" GEOS=\"3.5.0dev-CAPI-1.9.0 r3989\" SFCGAL=\"1.0.4\" PROJ=\"Rel. 4.8.0, 6 March 2012\" \n" -"GDAL=\"GDAL 1.11.0, released 2014/04/16\" LIBXML=\"2.7.8\" LIBJSON=\"0.12\" RASTER\n" +"POSTGIS=\"2.2.0dev r12699\" GEOS=\"3.5.0dev-CAPI-1.9.0 r3989\" SFCGAL=" +"\"1.0.4\" PROJ=\"Rel. 4.8.0, 6 March 2012\" \n" +"GDAL=\"GDAL 1.11.0, released 2014/04/16\" LIBXML=\"2.7.8\" LIBJSON=\"0.12\" " +"RASTER\n" "(1 row)" msgstr "" @@ -444,9 +452,8 @@ msgstr "" #: reference_management.xml:314 #, no-c-format msgid "" -", , , , , , , , " msgstr "" @@ -493,9 +500,9 @@ msgstr "" #: reference_management.xml:359 #, no-c-format msgid "" -", , , , " +", , , , " +"" msgstr "" #. Tag: refname @@ -545,9 +552,9 @@ msgstr "" #: reference_management.xml:401 #, no-c-format msgid "" -", , , , " +", , , , " msgstr "" #. Tag: refname @@ -604,8 +611,8 @@ msgstr "" #: reference_management.xml:449 #, no-c-format msgid "" -"text PostGIS_Lib_Version " -"" +"text PostGIS_Lib_Version " msgstr "" #. Tag: para @@ -629,9 +636,9 @@ msgstr "" #: reference_management.xml:472 #, no-c-format msgid "" -", , , , " +", , , , " +"" msgstr "" #. Tag: refname @@ -677,9 +684,9 @@ msgstr "" #: reference_management.xml:514 reference_management.xml:556 #, no-c-format msgid "" -", , , , " +", , , , " msgstr "" #. Tag: refname @@ -751,18 +758,18 @@ msgstr "" #: reference_management.xml:585 #, no-c-format msgid "" -"Returns version of the postgis scripts installed in this " -"database." +"Returns version of the postgis scripts installed in this database." msgstr "" #. Tag: para #: reference_management.xml:589 #, no-c-format msgid "" -"If the output of this function doesn't match the output of you probably missed to properly " -"upgrade an existing database. See the Upgrading section for more info." +"If the output of this function doesn't match the output of you probably missed to properly upgrade an " +"existing database. See the Upgrading " +"section for more info." msgstr "" #. Tag: para @@ -786,8 +793,8 @@ msgstr "" #: reference_management.xml:608 #, no-c-format msgid "" -", , " +", , " msgstr "" #. Tag: refname @@ -816,8 +823,8 @@ msgstr "" #: reference_management.xml:633 #, no-c-format msgid "" -"Returns the version number of the postgis.sql script released with the" -" installed postgis lib." +"Returns the version number of the postgis.sql script released with the " +"installed postgis lib." msgstr "" #. Tag: para @@ -843,8 +850,8 @@ msgstr "" #: reference_management.xml:654 #, no-c-format msgid "" -", , " +", , " msgstr "" #. Tag: refname @@ -857,16 +864,16 @@ msgstr "" #: reference_management.xml:662 #, no-c-format msgid "" -"Returns PostGIS version number and compile-time " -"options." +"Returns PostGIS version number and compile-time options." msgstr "" #. Tag: funcprototype #: reference_management.xml:668 #, no-c-format msgid "" -"text PostGIS_Version " -"" +"text PostGIS_Version " msgstr "" #. Tag: para @@ -890,9 +897,8 @@ msgstr "" #: reference_management.xml:691 #, no-c-format msgid "" -", , , , , , , " msgstr "" @@ -906,8 +912,8 @@ msgstr "" #: 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 " +"Ensures geometry columns are defined with type modifiers or have appropriate " +"spatial constraints This ensures they will be registered correctly in " "geometry_columns view. By default will convert all " "geometry columns with no type modifier to ones with type modifiers. To get " "old behavior set use_typmod=false" @@ -917,15 +923,13 @@ msgstr "" #: reference_management.xml:709 #, no-c-format msgid "" -" text " -"Populate_Geometry_Columns " -"boolean " +" text Populate_Geometry_Columns boolean " "use_typmod=true " -" int " -"Populate_Geometry_Columns " -"oid relation_oid " -"boolean " -"use_typmod=true " +" int Populate_Geometry_Columns oid relation_oid boolean use_typmod=true " msgstr "" #. Tag: para @@ -945,8 +949,8 @@ msgid "" "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 " -"use_typmod=false. When this is done geometry columns will" -" be created with no type modifiers but will have 3 constraints defined. In " +"use_typmod=false. 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 "" @@ -982,8 +986,8 @@ msgid "" "If a table oid 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." +"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 @@ -1003,12 +1007,12 @@ msgstr "" 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 " +"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 " "geometry_columns table. The parameterized version simply " -"returns the number of rows inserted into the " -"geometry_columns table." +"returns the number of rows inserted into the geometry_columns table." msgstr "" #. Tag: para @@ -1041,8 +1045,10 @@ msgstr "" #, 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" +"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" @@ -1053,9 +1059,12 @@ msgid "" "\\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" +" Column | Type | " +"Modifiers \n" +"--------+---------------------------" +"+---------------------------------------------------------------\n" +" gid | integer | not null default " +"nextval('myspatial_table_gid_seq'::regclass)\n" " geom | geometry(LineString,4326) |" msgstr "" @@ -1063,24 +1072,31 @@ msgstr "" #: 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" +"-- 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" +"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" +" 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_geotype_geom\" CHECK (geometrytype(geom) = 'LINESTRING'::text " +"OR geom IS NULL)\n" " \"enforce_srid_geom\" CHECK (st_srid(geom) = 4326)" msgstr "" @@ -1095,8 +1111,8 @@ msgstr "" #, no-c-format msgid "" "Updates the SRID of all features in a geometry column, geometry_columns " -"metadata and srid. If it was enforced with constraints, the constraints will" -" be updated with new srid constraint. If the old was enforced by type " +"metadata and srid. If it was enforced with constraints, the constraints will " +"be updated with new srid constraint. If the old was enforced by type " "definition, the type definition will be changed." msgstr "" @@ -1104,27 +1120,23 @@ msgstr "" #: reference_management.xml:811 #, no-c-format msgid "" -" text " -"UpdateGeometrySRID varchar " -" table_name varchar" -" column_name " -"integer srid " -" text " -"UpdateGeometrySRID varchar " -" schema_name " -"varchar table_name" -" varchar " -"column_name integer " -" srid " -" text " -"UpdateGeometrySRID varchar " -" catalog_name " -"varchar " -"schema_name varchar " -" table_name varchar" -" column_name " -"integer srid " -"" +" text UpdateGeometrySRID varchar table_name varchar column_name integer srid text " +"UpdateGeometrySRID varchar schema_name varchar " +" table_name varchar " +" column_name " +"integer srid text UpdateGeometrySRID varchar catalog_name varchar " +"schema_name varchar table_name varchar column_name integer " +" srid " msgstr "" #. Tag: para @@ -1170,8 +1182,8 @@ msgstr "" #, no-c-format msgid "" "If you got the projection wrong (or brought it in as unknown) in load and " -"you wanted to transform to web mercator all in one shot You can do this with" -" DDL but there is no equivalent PostGIS management function to do so in one " +"you wanted to transform to web mercator all in one shot You can do this with " +"DDL but there is no equivalent PostGIS management function to do so in one " "go." msgstr "" @@ -1180,7 +1192,8 @@ msgstr "" #, no-c-format msgid "" "ALTER TABLE roads \n" -" ALTER COLUMN geom TYPE geometry(MULTILINESTRING, 3857) USING ST_Transform(ST_SetSRID(geom,4326),3857) ;" +" ALTER COLUMN geom TYPE geometry(MULTILINESTRING, 3857) USING " +"ST_Transform(ST_SetSRID(geom,4326),3857) ;" msgstr "" #. Tag: para diff --git a/doc/po/de_DE/reference_measure.xml.po b/doc/po/de_DE/reference_measure.xml.po index a38eb6e5a..13d403ee6 100644 --- a/doc/po/de_DE/reference_measure.xml.po +++ b/doc/po/de_DE/reference_measure.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:24+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -149,13 +150,17 @@ msgid "" "SELECT ST_AsEWKT(ST_3DClosestPoint(line,pt)) AS cp3d_line_pt, \n" " ST_AsEWKT(ST_ClosestPoint(line,pt)) As cp2d_line_pt\n" " FROM (SELECT 'POINT(100 100 30)'::geometry As pt, \n" -" 'LINESTRING (20 80 20, 98 190 1, 110 180 3, 50 75 1000)'::geometry As line\n" +" 'LINESTRING (20 80 20, 98 190 1, 110 180 3, 50 75 " +"1000)'::geometry As line\n" " ) As foo;\n" " \n" " \n" -" cp3d_line_pt | cp2d_line_pt\n" -"-----------------------------------------------------------+------------------------------------------\n" -" POINT(54.6993798867619 128.935022917228 11.5475869506606) | POINT(73.0769230769231 115.384615384615)" +" cp3d_line_pt " +"| cp2d_line_pt\n" +"-----------------------------------------------------------" +"+------------------------------------------\n" +" POINT(54.6993798867619 128.935022917228 11.5475869506606) | " +"POINT(73.0769230769231 115.384615384615)" msgstr "" #. Tag: para @@ -171,7 +176,8 @@ msgid "" "SELECT ST_AsEWKT(ST_3DClosestPoint(line,pt)) AS cp3d_line_pt, \n" " ST_AsEWKT(ST_ClosestPoint(line,pt)) As cp2d_line_pt\n" " FROM (SELECT 'MULTIPOINT(100 100 30, 50 74 1000)'::geometry As pt, \n" -" 'LINESTRING (20 80 20, 98 190 1, 110 180 3, 50 75 900)'::geometry As line\n" +" 'LINESTRING (20 80 20, 98 190 1, 110 180 3, 50 75 " +"900)'::geometry As line\n" " ) As foo;\n" " \n" " \n" @@ -192,8 +198,10 @@ msgstr "" msgid "" "SELECT ST_AsEWKT(ST_3DClosestPoint(poly, mline)) As cp3d,\n" " ST_AsEWKT(ST_ClosestPoint(poly, mline)) As cp2d \n" -" FROM (SELECT ST_GeomFromEWKT('POLYGON((175 150 5, 20 40 5, 35 45 5, 50 60 5, 100 100 5, 175 150 5))') As poly,\n" -" ST_GeomFromEWKT('MULTILINESTRING((175 155 2, 20 40 20, 50 60 -2, 125 100 1, 175 155 1),\n" +" FROM (SELECT ST_GeomFromEWKT('POLYGON((175 150 5, 20 40 5, 35 45 5, " +"50 60 5, 100 100 5, 175 150 5))') As poly,\n" +" ST_GeomFromEWKT('MULTILINESTRING((175 155 2, 20 40 20, 50 60 " +"-2, 125 100 1, 175 155 1),\n" " (1 10 2, 5 20 1))') As mline ) As foo;\n" " cp3d | cp2d\n" "-------------------------------------------+--------------\n" @@ -284,15 +292,21 @@ msgstr "" #: reference_measure.xml:109 #, no-c-format msgid "" -"-- Geometry example - units in meters (SRID: 2163 US National Atlas Equal area) (3D point and line compared 2D point and line)\n" -"-- Note: currently no vertical datum support so Z is not transformed and assumed to be same units as final.\n" +"-- Geometry example - units in meters (SRID: 2163 US National Atlas Equal " +"area) (3D point and line compared 2D point and line)\n" +"-- Note: currently no vertical datum support so Z is not transformed and " +"assumed to be same units as final.\n" "SELECT ST_3DDistance(\n" -" ST_Transform(ST_GeomFromEWKT('SRID=4326;POINT(-72.1235 42.3521 4)'),2163),\n" -" ST_Transform(ST_GeomFromEWKT('SRID=4326;LINESTRING(-72.1260 42.45 15, -72.123 42.1546 20)'),2163)\n" +" ST_Transform(ST_GeomFromEWKT('SRID=4326;" +"POINT(-72.1235 42.3521 4)'),2163),\n" +" ST_Transform(ST_GeomFromEWKT('SRID=4326;" +"LINESTRING(-72.1260 42.45 15, -72.123 42.1546 20)'),2163)\n" " ) As dist_3d,\n" " ST_Distance(\n" -" ST_Transform(ST_GeomFromText('POINT(-72.1235 42.3521)',4326),2163),\n" -" ST_Transform(ST_GeomFromText('LINESTRING(-72.1260 42.45, -72.123 42.1546)', 4326),2163)\n" +" ST_Transform(ST_GeomFromText('POINT(-72.1235 " +"42.3521)',4326),2163),\n" +" ST_Transform(ST_GeomFromText('LINESTRING(-72.1260 " +"42.45, -72.123 42.1546)', 4326),2163)\n" " ) As dist_2d;\n" "\n" " dist_3d | dist_2d\n" @@ -308,8 +322,10 @@ msgid "" "-- Same example as 3D closest point example\n" "SELECT ST_3DDistance(poly, mline) As dist3d,\n" " ST_Distance(poly, mline) As dist2d \n" -" FROM (SELECT ST_GeomFromEWKT('POLYGON((175 150 5, 20 40 5, 35 45 5, 50 60 5, 100 100 5, 175 150 5))') As poly,\n" -" ST_GeomFromEWKT('MULTILINESTRING((175 155 2, 20 40 20, 50 60 -2, 125 100 1, 175 155 1),\n" +" FROM (SELECT ST_GeomFromEWKT('POLYGON((175 150 5, 20 40 5, 35 45 5, " +"50 60 5, 100 100 5, 175 150 5))') As poly,\n" +" ST_GeomFromEWKT('MULTILINESTRING((175 155 2, 20 40 20, 50 60 " +"-2, 125 100 1, 175 155 1),\n" " (1 10 2, 5 20 1))') As mline ) As foo;\n" " dist3d | dist2d\n" "-------------------+--------\n" @@ -321,8 +337,8 @@ msgstr "" #, no-c-format msgid "" ", , , " -", ," -" " +", , " +"" msgstr "" #. Tag: refname @@ -346,8 +362,8 @@ msgid "" "boolean ST_3DDWithin " "geometry g1 " "geometry g2 " -"double precision " -"distance_of_srid" +"double precision distance_of_srid" msgstr "" #. Tag: para @@ -362,16 +378,22 @@ msgstr "" #: reference_measure.xml:160 #, no-c-format msgid "" -"-- Geometry example - units in meters (SRID: 2163 US National Atlas Equal area) (3D point and line compared 2D point and line)\n" -"-- Note: currently no vertical datum support so Z is not transformed and assumed to be same units as final.\n" +"-- Geometry example - units in meters (SRID: 2163 US National Atlas Equal " +"area) (3D point and line compared 2D point and line)\n" +"-- Note: currently no vertical datum support so Z is not transformed and " +"assumed to be same units as final.\n" "SELECT ST_3DDWithin(\n" -" ST_Transform(ST_GeomFromEWKT('SRID=4326;POINT(-72.1235 42.3521 4)'),2163),\n" -" ST_Transform(ST_GeomFromEWKT('SRID=4326;LINESTRING(-72.1260 42.45 15, -72.123 42.1546 20)'),2163),\n" +" ST_Transform(ST_GeomFromEWKT('SRID=4326;" +"POINT(-72.1235 42.3521 4)'),2163),\n" +" ST_Transform(ST_GeomFromEWKT('SRID=4326;" +"LINESTRING(-72.1260 42.45 15, -72.123 42.1546 20)'),2163),\n" " 126.8\n" " ) As within_dist_3d,\n" "ST_DWithin(\n" -" ST_Transform(ST_GeomFromEWKT('SRID=4326;POINT(-72.1235 42.3521 4)'),2163),\n" -" ST_Transform(ST_GeomFromEWKT('SRID=4326;LINESTRING(-72.1260 42.45 15, -72.123 42.1546 20)'),2163),\n" +" ST_Transform(ST_GeomFromEWKT('SRID=4326;" +"POINT(-72.1235 42.3521 4)'),2163),\n" +" ST_Transform(ST_GeomFromEWKT('SRID=4326;" +"LINESTRING(-72.1260 42.45 15, -72.123 42.1546 20)'),2163),\n" " 126.8\n" " ) As within_dist_2d;\n" "\n" @@ -409,19 +431,19 @@ msgid "" "boolean ST_3DDFullyWithin " "geometry g1 " "geometry g2 " -"double precision " -"distance" +"double precision distance" msgstr "" #. Tag: para #: reference_measure.xml:198 #, no-c-format msgid "" -"Returns true if the 3D geometries are fully within the specified distance of" -" one another. The distance is specified in units defined by the spatial " +"Returns true if the 3D geometries are fully within the specified distance of " +"one another. The distance is specified in units defined by the spatial " "reference system of the geometries. For this function to make sense, the " -"source geometries must both be of the same coordinate projection, having the" -" same SRID." +"source geometries must both be of the same coordinate projection, having the " +"same SRID." msgstr "" #. Tag: para @@ -430,21 +452,25 @@ msgstr "" #: reference_measure.xml:1945 reference_measure.xml:2120 #, no-c-format msgid "" -"This function call will automatically include a bounding box comparison that" -" will make use of any indexes that are available on the geometries." +"This function call will automatically include a bounding box comparison that " +"will make use of any indexes that are available on the geometries." msgstr "" #. Tag: programlisting #: reference_measure.xml:219 #, no-c-format msgid "" -"-- This compares the difference between fully within and distance within as well\n" -" -- as the distance fully within for the 2D footprint of the line/point vs. the 3d fully within\n" -" SELECT ST_3DDFullyWithin(geom_a, geom_b, 10) as D3DFullyWithin10, ST_3DDWithin(geom_a, geom_b, 10) as D3DWithin10, \n" +"-- This compares the difference between fully within and distance within as " +"well\n" +" -- as the distance fully within for the 2D footprint of the " +"line/point vs. the 3d fully within\n" +" SELECT ST_3DDFullyWithin(geom_a, geom_b, 10) as " +"D3DFullyWithin10, ST_3DDWithin(geom_a, geom_b, 10) as D3DWithin10, \n" " ST_DFullyWithin(geom_a, geom_b, 20) as D2DFullyWithin20, \n" " ST_3DDFullyWithin(geom_a, geom_b, 20) as D3DFullyWithin20 from \n" " (select ST_GeomFromEWKT('POINT(1 1 2)') as geom_a,\n" -" ST_GeomFromEWKT('LINESTRING(1 5 2, 2 7 20, 1 9 100, 14 12 3)') as geom_b) t1;\n" +" ST_GeomFromEWKT('LINESTRING(1 5 2, 2 7 20, 1 9 100, 14 12 " +"3)') as geom_b) t1;\n" " d3dfullywithin10 | d3dwithin10 | d2dfullywithin20 | d3dfullywithin20\n" "------------------+-------------+------------------+------------------\n" " f | t | t | f" @@ -496,10 +522,10 @@ msgstr "" #, no-c-format msgid "" "In order to take advantage of support for TINS, you need to enable the " -"SFCGAL backend. This can be done at session time with: set " -"postgis.backend = sfcgal; or at the database or system level. " -"Database level can be done with ALTER DATABASE gisdb SET " -"postgis.backend = sfcgal;." +"SFCGAL backend. This can be done at session time with: set postgis." +"backend = sfcgal; or at the database or system level. Database level " +"can be done with ALTER DATABASE gisdb SET postgis.backend = sfcgal;." msgstr "" #. Tag: para @@ -545,7 +571,8 @@ msgstr "" #, no-c-format msgid "" "set postgis.backend = sfcgal;\n" -"SELECT ST_3DIntersects('TIN(((0 0,1 0,0 1,0 0)))'::geometry, 'POINT(.1 .1)'::geometry);\n" +"SELECT ST_3DIntersects('TIN(((0 0,1 0,0 1,0 0)))'::geometry, 'POINT(.1 .1)'::" +"geometry);\n" " st_3dintersects \n" "-----------------\n" " t" @@ -579,8 +606,8 @@ msgid "" "Returns the 3-dimensional longest line between two geometries. The function " "will only return the first longest line if more than one. The line returned " "will always start in g1 and end in g2. The 3D length of the line this " -"function returns will always be the same as returns for g1 and g2." +"function returns will always be the same as returns for g1 and g2." msgstr "" #. Tag: para @@ -596,7 +623,8 @@ msgid "" "SELECT ST_AsEWKT(ST_3DLongestLine(line,pt)) AS lol3d_line_pt, \n" " ST_AsEWKT(ST_LongestLine(line,pt)) As lol2d_line_pt\n" " FROM (SELECT 'POINT(100 100 30)'::geometry As pt, \n" -" 'LINESTRING (20 80 20, 98 190 1, 110 180 3, 50 75 1000)'::geometry As line\n" +" 'LINESTRING (20 80 20, 98 190 1, 110 180 3, 50 75 " +"1000)'::geometry As line\n" " ) As foo;\n" " \n" " \n" @@ -618,7 +646,8 @@ msgid "" "SELECT ST_AsEWKT(ST_3DLongestLine(line,pt)) AS lol3d_line_pt, \n" " ST_AsEWKT(ST_LongestLine(line,pt)) As lol2d_line_pt\n" " FROM (SELECT 'MULTIPOINT(100 100 30, 50 74 1000)'::geometry As pt, \n" -" 'LINESTRING (20 80 20, 98 190 1, 110 180 3, 50 75 900)'::geometry As line\n" +" 'LINESTRING (20 80 20, 98 190 1, 110 180 3, 50 75 " +"900)'::geometry As line\n" " ) As foo;\n" " \n" " \n" @@ -639,8 +668,10 @@ msgstr "" msgid "" "SELECT ST_AsEWKT(ST_3DLongestLine(poly, mline)) As lol3d,\n" " ST_AsEWKT(ST_LongestLine(poly, mline)) As lol2d \n" -" FROM (SELECT ST_GeomFromEWKT('POLYGON((175 150 5, 20 40 5, 35 45 5, 50 60 5, 100 100 5, 175 150 5))') As poly,\n" -" ST_GeomFromEWKT('MULTILINESTRING((175 155 2, 20 40 20, 50 60 -2, 125 100 1, 175 155 1),\n" +" FROM (SELECT ST_GeomFromEWKT('POLYGON((175 150 5, 20 40 5, 35 45 5, " +"50 60 5, 100 100 5, 175 150 5))') As poly,\n" +" ST_GeomFromEWKT('MULTILINESTRING((175 155 2, 20 40 20, 50 60 " +"-2, 125 100 1, 175 155 1),\n" " (1 10 2, 5 20 1))') As mline ) As foo;\n" " lol3d | lol2d\n" "------------------------------+--------------------------\n" @@ -690,15 +721,21 @@ msgstr "" #: reference_measure.xml:395 #, no-c-format msgid "" -"-- Geometry example - units in meters (SRID: 2163 US National Atlas Equal area) (3D point and line compared 2D point and line)\n" -"-- Note: currently no vertical datum support so Z is not transformed and assumed to be same units as final.\n" +"-- Geometry example - units in meters (SRID: 2163 US National Atlas Equal " +"area) (3D point and line compared 2D point and line)\n" +"-- Note: currently no vertical datum support so Z is not transformed and " +"assumed to be same units as final.\n" "SELECT ST_3DMaxDistance(\n" -" ST_Transform(ST_GeomFromEWKT('SRID=4326;POINT(-72.1235 42.3521 10000)'),2163),\n" -" ST_Transform(ST_GeomFromEWKT('SRID=4326;LINESTRING(-72.1260 42.45 15, -72.123 42.1546 20)'),2163)\n" +" ST_Transform(ST_GeomFromEWKT('SRID=4326;" +"POINT(-72.1235 42.3521 10000)'),2163),\n" +" ST_Transform(ST_GeomFromEWKT('SRID=4326;" +"LINESTRING(-72.1260 42.45 15, -72.123 42.1546 20)'),2163)\n" " ) As dist_3d,\n" " ST_MaxDistance(\n" -" ST_Transform(ST_GeomFromEWKT('SRID=4326;POINT(-72.1235 42.3521 10000)'),2163),\n" -" ST_Transform(ST_GeomFromEWKT('SRID=4326;LINESTRING(-72.1260 42.45 15, -72.123 42.1546 20)'),2163)\n" +" ST_Transform(ST_GeomFromEWKT('SRID=4326;" +"POINT(-72.1235 42.3521 10000)'),2163),\n" +" ST_Transform(ST_GeomFromEWKT('SRID=4326;" +"LINESTRING(-72.1260 42.45 15, -72.123 42.1546 20)'),2163)\n" " ) As dist_2d;\n" "\n" " dist_3d | dist_2d\n" @@ -739,12 +776,12 @@ msgstr "" #: reference_measure.xml:428 #, no-c-format msgid "" -"Returns the 3-dimensional shortest line between two geometries. The function" -" will only return the first shortest line if more than one, that the " -"function finds. If g1 and g2 intersects in just one point the function will " -"return a line with both start and end in that intersection-point. If g1 and " -"g2 are intersecting with more than one point the function will return a line" -" with start and end in the same point but it can be any of the intersecting " +"Returns the 3-dimensional shortest line between two geometries. The function " +"will only return the first shortest line if more than one, that the function " +"finds. If g1 and g2 intersects in just one point the function will return a " +"line with both start and end in that intersection-point. If g1 and g2 are " +"intersecting with more than one point the function will return a line with " +"start and end in the same point but it can be any of the intersecting " "points. The line returned will always start in g1 and end in g2. The 3D " "length of the line this function returns will always be the same as returns for g1 and g2." @@ -763,13 +800,17 @@ msgid "" "SELECT ST_AsEWKT(ST_3DShortestLine(line,pt)) AS shl3d_line_pt, \n" " ST_AsEWKT(ST_ShortestLine(line,pt)) As shl2d_line_pt\n" " FROM (SELECT 'POINT(100 100 30)'::geometry As pt, \n" -" 'LINESTRING (20 80 20, 98 190 1, 110 180 3, 50 75 1000)'::geometry As line\n" +" 'LINESTRING (20 80 20, 98 190 1, 110 180 3, 50 75 " +"1000)'::geometry As line\n" " ) As foo;\n" " \n" " \n" -" shl3d_line_pt | shl2d_line_pt\n" -"----------------------------------------------------------------------------+------------------------------------------------------\n" -" LINESTRING(54.6993798867619 128.935022917228 11.5475869506606,100 100 30) | LINESTRING(73.0769230769231 115.384615384615,100 100)" +" shl3d_line_pt " +"| shl2d_line_pt\n" +"----------------------------------------------------------------------------" +"+------------------------------------------------------\n" +" LINESTRING(54.6993798867619 128.935022917228 11.5475869506606,100 100 30) " +"| LINESTRING(73.0769230769231 115.384615384615,100 100)" msgstr "" #. Tag: para @@ -785,13 +826,17 @@ msgid "" "SELECT ST_AsEWKT(ST_3DShortestLine(line,pt)) AS shl3d_line_pt, \n" " ST_AsEWKT(ST_ShortestLine(line,pt)) As shl2d_line_pt\n" " FROM (SELECT 'MULTIPOINT(100 100 30, 50 74 1000)'::geometry As pt, \n" -" 'LINESTRING (20 80 20, 98 190 1, 110 180 3, 50 75 900)'::geometry As line\n" +" 'LINESTRING (20 80 20, 98 190 1, 110 180 3, 50 75 " +"900)'::geometry As line\n" " ) As foo;\n" " \n" " \n" -" shl3d_line_pt | shl2d_line_pt\n" -"---------------------------------------------------------------------------+------------------------\n" -" LINESTRING(54.6993798867619 128.935022917228 11.5475869506606,100 100 30) | LINESTRING(50 75,50 74)" +" shl3d_line_pt | " +"shl2d_line_pt\n" +"---------------------------------------------------------------------------" +"+------------------------\n" +" LINESTRING(54.6993798867619 128.935022917228 11.5475869506606,100 100 30) | " +"LINESTRING(50 75,50 74)" msgstr "" #. Tag: para @@ -806,12 +851,17 @@ msgstr "" msgid "" "SELECT ST_AsEWKT(ST_3DShortestLine(poly, mline)) As shl3d,\n" " ST_AsEWKT(ST_ShortestLine(poly, mline)) As shl2d \n" -" FROM (SELECT ST_GeomFromEWKT('POLYGON((175 150 5, 20 40 5, 35 45 5, 50 60 5, 100 100 5, 175 150 5))') As poly,\n" -" ST_GeomFromEWKT('MULTILINESTRING((175 155 2, 20 40 20, 50 60 -2, 125 100 1, 175 155 1),\n" +" FROM (SELECT ST_GeomFromEWKT('POLYGON((175 150 5, 20 40 5, 35 45 5, " +"50 60 5, 100 100 5, 175 150 5))') As poly,\n" +" ST_GeomFromEWKT('MULTILINESTRING((175 155 2, 20 40 20, 50 60 " +"-2, 125 100 1, 175 155 1),\n" " (1 10 2, 5 20 1))') As mline ) As foo;\n" -" shl3d | shl2d\n" -"---------------------------------------------------------------------------------------------------+------------------------\n" -" LINESTRING(39.993580415989 54.1889925532825 5,40.4078575708294 53.6052383805529 5.03423778139177) | LINESTRING(20 40,20 40)" +" shl3d " +"| shl2d\n" +"---------------------------------------------------------------------------------------------------" +"+------------------------\n" +" LINESTRING(39.993580415989 54.1889925532825 5,40.4078575708294 " +"53.6052383805529 5.03423778139177) | LINESTRING(20 40,20 40)" msgstr "" #. Tag: para @@ -843,12 +893,11 @@ msgstr "" #, no-c-format msgid "" " float ST_Area " -"geometry g1 " -" float " -"ST_Area geography " -"geog boolean " -"use_spheroid=true " +"geometry g1 float ST_Area geography geog boolean use_spheroid=true " msgstr "" #. Tag: para @@ -859,8 +908,8 @@ msgid "" "the area measurement of an ST_Surface or ST_MultiSurface value. For " "geometry, a 2D Cartesian area is determined with units specified by the " "SRID. For geography, by default area is determined on a spheroid with units " -"in square meters. To measure around the faster but less accurate sphere, use" -" ST_Area(geog,false)." +"in square meters. To measure around the faster but less accurate sphere, use " +"ST_Area(geog,false)." msgstr "" #. Tag: para @@ -915,7 +964,8 @@ msgid "" "SELECT ST_Area(the_geom) As sqft, ST_Area(the_geom)*POWER(0.3048,2) As sqm\n" " FROM (SELECT\n" " ST_GeomFromText('POLYGON((743238 2967416,743238 2967450,\n" -" 743265 2967450,743265.625 2967416,743238 2967416))',2249) ) As foo(the_geom);\n" +" 743265 2967450,743265.625 2967416,743238 " +"2967416))',2249) ) As foo(the_geom);\n" " sqft | sqm\n" "---------+-------------\n" " 928.625 | 86.27208552" @@ -935,10 +985,12 @@ msgstr "" #: reference_measure.xml:524 #, no-c-format msgid "" -"SELECT ST_Area(the_geom) As sqft, ST_Area(ST_Transform(the_geom,26986)) As sqm\n" +"SELECT ST_Area(the_geom) As sqft, ST_Area(ST_Transform(the_geom,26986)) As " +"sqm\n" " FROM (SELECT\n" " ST_GeomFromText('POLYGON((743238 2967416,743238 2967450,\n" -" 743265 2967450,743265.625 2967416,743238 2967416))',2249) ) As foo(the_geom);\n" +" 743265 2967450,743265.625 2967416,743238 " +"2967416))',2249) ) As foo(the_geom);\n" " sqft | sqm\n" "---------+------------------\n" " 928.625 | 86.2724304199219" @@ -950,20 +1002,22 @@ msgstr "" msgid "" "Return area square feet and square meters using geography data type. Note " "that we transform to our geometry to geography (before you can do that make " -"sure your geometry is in WGS 84 long lat 4326). Geography always measures in" -" meters. This is just for demonstration to compare. Normally your table will" -" be stored in geography data type already." +"sure your geometry is in WGS 84 long lat 4326). Geography always measures in " +"meters. This is just for demonstration to compare. Normally your table will " +"be stored in geography data type already." msgstr "" #. Tag: programlisting #: reference_measure.xml:529 #, no-c-format msgid "" -"SELECT ST_Area(the_geog)/POWER(0.3048,2) As sqft_spheroid, ST_Area(the_geog,false)/POWER(0.3048,2) As sqft_sphere, ST_Area(the_geog) As sqm_spheroid\n" +"SELECT ST_Area(the_geog)/POWER(0.3048,2) As sqft_spheroid, ST_Area(the_geog," +"false)/POWER(0.3048,2) As sqft_sphere, ST_Area(the_geog) As sqm_spheroid\n" " FROM (SELECT\n" " geography(\n" " ST_Transform(\n" -" ST_GeomFromText('POLYGON((743238 2967416,743238 2967450,743265 2967450,743265.625 2967416,743238 2967416))',\n" +" ST_GeomFromText('POLYGON((743238 2967416,743238 " +"2967450,743265 2967450,743265.625 2967416,743238 2967416))',\n" " 2249\n" " ) ,4326\n" " )\n" @@ -974,7 +1028,8 @@ msgid "" " 928.684403538925 | 927.049336105925 | 86.2776042893529\n" "\n" " --if your data is in geography already\n" -" SELECT ST_Area(the_geog)/POWER(0.3048,2) As sqft, ST_Area(the_geog) As sqm\n" +" SELECT ST_Area(the_geog)/POWER(0.3048,2) As sqft, ST_Area(the_geog) As " +"sqm\n" " FROM somegeogtable;" msgstr "" @@ -1006,11 +1061,11 @@ msgstr "" msgid "" " float ST_Azimuth " "geometry pointA " -"geometry pointB " -" float " -"ST_Azimuth geography " -"pointA geography " -"pointB " +"geometry pointB float ST_Azimuth geography pointA geography pointB " msgstr "" #. Tag: para @@ -1027,17 +1082,17 @@ msgstr "" #: reference_measure.xml:562 #, no-c-format msgid "" -"For the geography type, the forward azimuth is solved as part of the inverse" -" geodesic problem." +"For the geography type, the forward azimuth is solved as part of the inverse " +"geodesic problem." msgstr "" #. Tag: para #: reference_measure.xml:563 #, no-c-format msgid "" -"The azimuth is mathematical concept defined as the angle between a reference" -" plane and a point, with angular units in radians. Units can be converted to" -" degrees using a built-in PostgreSQL function degrees(), as shown in the " +"The azimuth is mathematical concept defined as the angle between a reference " +"plane and a point, with angular units in radians. Units can be converted to " +"degrees using a built-in PostgreSQL function degrees(), as shown in the " "example." msgstr "" @@ -1066,9 +1121,9 @@ msgstr "" #, no-c-format msgid "" "Azimuth is especially useful in conjunction with ST_Translate for shifting " -"an object along its perpendicular axis. See upgis_lineshift Plpgsqlfunctions" -" PostGIS wiki section for example of this." +"an object along its perpendicular axis. See upgis_lineshift Plpgsqlfunctions PostGIS wiki section for example of this." msgstr "" #. Tag: para @@ -1082,7 +1137,8 @@ msgstr "" #, no-c-format msgid "" "SELECT degrees(ST_Azimuth(ST_Point(25, 45), ST_Point(75, 100))) AS degA_B,\n" -" degrees(ST_Azimuth(ST_Point(75, 100), ST_Point(25, 45))) AS degB_A;\n" +" degrees(ST_Azimuth(ST_Point(75, 100), ST_Point(25, 45))) AS " +"degB_A;\n" "\n" " dega_b | degb_a\n" "------------------+------------------\n" @@ -1101,8 +1157,8 @@ msgstr "" #: reference_measure.xml:595 #, no-c-format msgid "" -"Green: the start Point(75,100) with its vertical. Yellow: degB_A as the path" -" to travel (azimuth)." +"Green: the start Point(75,100) with its vertical. Yellow: degB_A as the path " +"to travel (azimuth)." msgstr "" #. Tag: para @@ -1110,8 +1166,8 @@ msgstr "" #, no-c-format msgid "" ", , , PostgreSQL Math Functions" +"url=\"http://www.postgresql.org/docs/current/interactive/functions-math.html" +"\">PostgreSQL Math Functions" msgstr "" #. Tag: refname @@ -1139,15 +1195,14 @@ msgstr "" #, no-c-format msgid "" "Computes the geometric center of a geometry, or equivalently, the center of " -"mass of the geometry as a POINT. For " -"[MULTI]POINTs, this is computed as the" -" arithmetic mean of the input coordinates. For " -"[MULTI]LINESTRINGs, this is computed " -"as the weighted length of each line segment. For " -"[MULTI]POLYGONs, \"weight\" is thought" -" in terms of area. If an empty geometry is supplied, an empty " -"GEOMETRYCOLLECTION is returned. If " -"NULL is supplied, NULL is returned." +"mass of the geometry as a POINT. For [MULTI]POINTs, this is computed as the arithmetic mean " +"of the input coordinates. For [MULTI]LINESTRINGs, this is computed as the weighted length of each line segment. For " +"[MULTI]POLYGONs, \"weight\" is thought " +"in terms of area. If an empty geometry is supplied, an empty " +"GEOMETRYCOLLECTION is returned. If NULL is supplied, NULL is returned." msgstr "" #. Tag: para @@ -1177,8 +1232,8 @@ msgstr "" #: reference_measure.xml:658 #, no-c-format msgid "" -"In each of the following illustrations, the blue dot represents the centroid" -" of the source geometry." +"In each of the following illustrations, the blue dot represents the centroid " +"of the source geometry." msgstr "" #. Tag: para @@ -1209,7 +1264,8 @@ msgstr "" #: reference_measure.xml:715 #, no-c-format msgid "" -"SELECT ST_AsText(ST_Centroid('MULTIPOINT ( -1 0, -1 2, -1 3, -1 4, -1 7, 0 1, 0 3, 1 1, 2 0, 6 0, 7 8, 9 8, 10 6 )'));\n" +"SELECT ST_AsText(ST_Centroid('MULTIPOINT ( -1 0, -1 2, -1 3, -1 4, -1 7, 0 " +"1, 0 3, 1 1, 2 0, 6 0, 7 8, 9 8, 10 6 )'));\n" " st_astext\n" "------------------------------------------\n" " POINT(2.30769230769231 3.30769230769231)\n" @@ -1251,8 +1307,8 @@ msgstr "" #: reference_measure.xml:753 #, no-c-format msgid "" -"If you have a 3D Geometry, you may prefer to use ." +"If you have a 3D Geometry, you may prefer to use ." msgstr "" #. Tag: para @@ -1278,7 +1334,8 @@ msgid "" "SELECT ST_AsText(ST_ClosestPoint(pt,line)) AS cp_pt_line, \n" " ST_AsText(ST_ClosestPoint(line,pt)) As cp_line_pt\n" "FROM (SELECT 'POINT(100 100)'::geometry As pt, \n" -" 'LINESTRING (20 80, 98 190, 110 180, 50 75 )'::geometry As line\n" +" 'LINESTRING (20 80, 98 190, 110 180, 50 75 )'::geometry As " +"line\n" " ) As foo;\n" "\n" " \n" @@ -1299,7 +1356,8 @@ msgstr "" msgid "" "SELECT ST_AsText(\n" " ST_ClosestPoint(\n" -" ST_GeomFromText('POLYGON((175 150, 20 40, 50 60, 125 100, 175 150))'),\n" +" ST_GeomFromText('POLYGON((175 150, 20 40, 50 60, 125 " +"100, 175 150))'),\n" " ST_Buffer(ST_GeomFromText('POINT(110 170)'), 20)\n" " ) \n" " ) As ptwkt;\n" @@ -1348,8 +1406,8 @@ msgid "" "exterior of A, and at least one point of the interior of B lies in the " "interior of A. An important subtlety of this definition is that A does not " "contain its boundary, but A does contain itself. Contrast that to where geometry A does not Contain Properly" -" itself." +"linkend=\"ST_ContainsProperly\"/> where geometry A does not Contain Properly " +"itself." msgstr "" #. Tag: para @@ -1379,8 +1437,7 @@ msgstr "" #: reference_measure.xml:1248 reference_measure.xml:1503 #: reference_measure.xml:3096 reference_measure.xml:3218 #, no-c-format -msgid "" -"Do not call with a GEOMETRYCOLLECTION as an argument" +msgid "Do not call with a GEOMETRYCOLLECTION as an argument" msgstr "" #. Tag: para @@ -1397,9 +1454,9 @@ msgstr "" #: reference_measure.xml:842 #, no-c-format msgid "" -"This function call will automatically include a bounding box comparison that" -" will make use of any indexes that are available on the geometries. To avoid" -" index use, use the function _ST_Contains." +"This function call will automatically include a bounding box comparison that " +"will make use of any indexes that are available on the geometries. To avoid " +"index use, use the function _ST_Contains." msgstr "" #. Tag: para @@ -1434,16 +1491,16 @@ msgstr "" msgid "" "There are certain subtleties to ST_Contains and ST_Within that are not " "intuitively obvious. For details check out Subtleties of OGC Covers, Contains, Within" +"inking.blogspot.com/2007/06/subtleties-of-ogc-covers-spatial.html" +"\">Subtleties of OGC Covers, Contains, Within" msgstr "" #. Tag: para #: reference_measure.xml:861 #, no-c-format msgid "" -"The ST_Contains predicate returns " -"TRUE in all the following illustrations." +"The ST_Contains predicate returns TRUE in all the following illustrations." msgstr "" #. Tag: para @@ -1476,8 +1533,8 @@ msgstr "" #: reference_measure.xml:912 #, no-c-format msgid "" -"The ST_Contains predicate returns " -"FALSE in all the following illustrations." +"The ST_Contains predicate returns FALSE in all the following illustrations." msgstr "" #. Tag: para @@ -1498,23 +1555,30 @@ msgid "" " ST_Covers(bigc, ST_ExteriorRing(bigc)) As bigcoversexterior,\n" " ST_Contains(bigc, ST_ExteriorRing(bigc)) As bigcontainsexterior\n" "FROM (SELECT ST_Buffer(ST_GeomFromText('POINT(1 2)'), 10) As smallc,\n" -" ST_Buffer(ST_GeomFromText('POINT(1 2)'), 20) As bigc) As foo;\n" +" ST_Buffer(ST_GeomFromText('POINT(1 2)'), 20) As " +"bigc) As foo;\n" "\n" "-- Result\n" -" smallcontainsbig | bigcontainssmall | bigcontainsunion | bigisunion | bigcoversexterior | bigcontainsexterior\n" -"------------------+------------------+------------------+------------+-------------------+---------------------\n" -" f | t | t | t | t | f\n" +" smallcontainsbig | bigcontainssmall | bigcontainsunion | bigisunion | " +"bigcoversexterior | bigcontainsexterior\n" +"------------------+------------------+------------------+------------" +"+-------------------+---------------------\n" +" f | t | t | t | " +"t | f\n" "\n" "-- Example demonstrating difference between contains and contains properly\n" -"SELECT ST_GeometryType(geomA) As geomtype, ST_Contains(geomA,geomA) AS acontainsa, ST_ContainsProperly(geomA, geomA) AS acontainspropa,\n" -" ST_Contains(geomA, ST_Boundary(geomA)) As acontainsba, ST_ContainsProperly(geomA, ST_Boundary(geomA)) As acontainspropba\n" +"SELECT ST_GeometryType(geomA) As geomtype, ST_Contains(geomA,geomA) AS " +"acontainsa, ST_ContainsProperly(geomA, geomA) AS acontainspropa,\n" +" ST_Contains(geomA, ST_Boundary(geomA)) As acontainsba, " +"ST_ContainsProperly(geomA, ST_Boundary(geomA)) As acontainspropba\n" "FROM (VALUES ( ST_Buffer(ST_Point(1,1), 5,1) ),\n" " ( ST_MakeLine(ST_Point(1,1), ST_Point(-1,-1) ) ),\n" " ( ST_Point(1,1) )\n" " ) As foo(geomA);\n" "\n" " geomtype | acontainsa | acontainspropa | acontainsba | acontainspropba\n" -"--------------+------------+----------------+-------------+-----------------\n" +"--------------+------------+----------------+-------------" +"+-----------------\n" "ST_Polygon | t | f | f | f\n" "ST_LineString | t | f | f | f\n" "ST_Point | t | t | f | f" @@ -1606,9 +1670,9 @@ msgstr "" #: reference_measure.xml:1004 #, no-c-format msgid "" -"This function call will automatically include a bounding box comparison that" -" will make use of any indexes that are available on the geometries. To avoid" -" index use, use the function _ST_ContainsProperly." +"This function call will automatically include a bounding box comparison that " +"will make use of any indexes that are available on the geometries. To avoid " +"index use, use the function _ST_ContainsProperly." msgstr "" #. Tag: programlisting @@ -1618,27 +1682,36 @@ msgid "" "--a circle within a circle\n" " SELECT ST_ContainsProperly(smallc, bigc) As smallcontainspropbig,\n" " ST_ContainsProperly(bigc,smallc) As bigcontainspropsmall,\n" -" ST_ContainsProperly(bigc, ST_Union(smallc, bigc)) as bigcontainspropunion,\n" +" ST_ContainsProperly(bigc, ST_Union(smallc, bigc)) as " +"bigcontainspropunion,\n" " ST_Equals(bigc, ST_Union(smallc, bigc)) as bigisunion,\n" " ST_Covers(bigc, ST_ExteriorRing(bigc)) As bigcoversexterior,\n" -" ST_ContainsProperly(bigc, ST_ExteriorRing(bigc)) As bigcontainsexterior\n" -" FROM (SELECT ST_Buffer(ST_GeomFromText('POINT(1 2)'), 10) As smallc,\n" +" ST_ContainsProperly(bigc, ST_ExteriorRing(bigc)) As " +"bigcontainsexterior\n" +" FROM (SELECT ST_Buffer(ST_GeomFromText('POINT(1 2)'), 10) As " +"smallc,\n" " ST_Buffer(ST_GeomFromText('POINT(1 2)'), 20) As bigc) As foo;\n" " --Result\n" -" smallcontainspropbig | bigcontainspropsmall | bigcontainspropunion | bigisunion | bigcoversexterior | bigcontainsexterior\n" -"------------------+------------------+------------------+------------+-------------------+---------------------\n" -" f | t | f | t | t | f\n" +" smallcontainspropbig | bigcontainspropsmall | bigcontainspropunion | " +"bigisunion | bigcoversexterior | bigcontainsexterior\n" +"------------------+------------------+------------------+------------" +"+-------------------+---------------------\n" +" f | t | f | " +"t | t | f\n" "\n" " --example demonstrating difference between contains and contains properly\n" -" SELECT ST_GeometryType(geomA) As geomtype, ST_Contains(geomA,geomA) AS acontainsa, ST_ContainsProperly(geomA, geomA) AS acontainspropa,\n" -" ST_Contains(geomA, ST_Boundary(geomA)) As acontainsba, ST_ContainsProperly(geomA, ST_Boundary(geomA)) As acontainspropba\n" +" SELECT ST_GeometryType(geomA) As geomtype, ST_Contains(geomA,geomA) AS " +"acontainsa, ST_ContainsProperly(geomA, geomA) AS acontainspropa,\n" +" ST_Contains(geomA, ST_Boundary(geomA)) As acontainsba, " +"ST_ContainsProperly(geomA, ST_Boundary(geomA)) As acontainspropba\n" " FROM (VALUES ( ST_Buffer(ST_Point(1,1), 5,1) ),\n" " ( ST_MakeLine(ST_Point(1,1), ST_Point(-1,-1) ) ),\n" " ( ST_Point(1,1) )\n" " ) As foo(geomA);\n" "\n" " geomtype | acontainsa | acontainspropa | acontainsba | acontainspropba\n" -"--------------+------------+----------------+-------------+-----------------\n" +"--------------+------------+----------------+-------------" +"+-----------------\n" "ST_Polygon | t | f | f | f\n" "ST_LineString | t | f | f | f\n" "ST_Point | t | t | f | f" @@ -1649,9 +1722,8 @@ msgstr "" #, no-c-format msgid "" ", , , , , , , " +"linkend=\"ST_Covers\"/>, , , , " msgstr "" #. Tag: refname @@ -1672,19 +1744,19 @@ msgstr "" msgid "" " boolean ST_Covers " "geometry geomA " -"geometry geomB " -" boolean " -"ST_Covers geography " -"geogpolyA geography " -" geogpointB " +"geometry geomB boolean ST_Covers geography geogpolyA geography " +"geogpointB " msgstr "" #. Tag: para #: reference_measure.xml:1056 #, no-c-format msgid "" -"Returns 1 (TRUE) if no point in Geometry/Geography B is outside " -"Geometry/Geography A" +"Returns 1 (TRUE) if no point in Geometry/Geography B is outside Geometry/" +"Geography A" msgstr "" #. Tag: para @@ -1697,9 +1769,9 @@ msgstr "" #: reference_measure.xml:1073 #, no-c-format msgid "" -"This function call will automatically include a bounding box comparison that" -" will make use of any indexes that are available on the geometries. To avoid" -" index use, use the function _ST_Covers." +"This function call will automatically include a bounding box comparison that " +"will make use of any indexes that are available on the geometries. To avoid " +"index use, use the function _ST_Covers." msgstr "" #. Tag: para @@ -1754,11 +1826,14 @@ msgstr "" #: reference_measure.xml:1094 #, no-c-format msgid "" -"-- a point with a 300 meter buffer compared to a point, a point and its 10 meter buffer\n" +"-- a point with a 300 meter buffer compared to a point, a point and its 10 " +"meter buffer\n" "SELECT ST_Covers(geog_poly, geog_pt) As poly_covers_pt, \n" " ST_Covers(ST_Buffer(geog_pt,10), geog_pt) As buff_10m_covers_cent\n" -" FROM (SELECT ST_Buffer(ST_GeogFromText('SRID=4326;POINT(-99.327 31.4821)'), 300) As geog_poly,\n" -" ST_GeogFromText('SRID=4326;POINT(-99.33 31.483)') As geog_pt ) As foo;\n" +" FROM (SELECT ST_Buffer(ST_GeogFromText('SRID=4326;POINT(-99.327 " +"31.4821)'), 300) As geog_poly,\n" +" ST_GeogFromText('SRID=4326;POINT(-99.33 " +"31.483)') As geog_pt ) As foo;\n" " \n" " poly_covers_pt | buff_10m_covers_cent\n" "----------------+------------------\n" @@ -1789,13 +1864,13 @@ msgstr "" #: reference_measure.xml:1112 #, no-c-format msgid "" -" boolean ST_CoveredBy" -" geometry geomA " -"geometry geomB " -" boolean " -"ST_CoveredBy geography " -" geogA geography " -" geogB " +" boolean ST_CoveredBy " +"geometry geomA " +"geometry geomB boolean ST_CoveredBy geography geogA geography geogB " msgstr "" #. Tag: para @@ -1810,9 +1885,9 @@ msgstr "" #: reference_measure.xml:1151 #, no-c-format msgid "" -"This function call will automatically include a bounding box comparison that" -" will make use of any indexes that are available on the geometries. To avoid" -" index use, use the function _ST_CoveredBy." +"This function call will automatically include a bounding box comparison that " +"will make use of any indexes that are available on the geometries. To avoid " +"index use, use the function _ST_CoveredBy." msgstr "" #. Tag: programlisting @@ -1828,7 +1903,8 @@ msgid "" " ST_Buffer(ST_GeomFromText('POINT(1 2)'), 20) As bigc) As foo;\n" " --Result\n" " smallinsmall | smallcoveredbybig | exteriorcoveredbybig | exeriorwithinbig\n" -"--------------+-------------------+----------------------+------------------\n" +"--------------+-------------------+----------------------" +"+------------------\n" " t | t | t | f\n" "(1 row)" msgstr "" @@ -1888,8 +1964,8 @@ msgstr "" #: reference_measure.xml:1209 #, no-c-format msgid "" -"TODO: Insert appropriate MathML markup here or use a gif. Simple HTML markup" -" does not work well in both IE and Firefox." +"TODO: Insert appropriate MathML markup here or use a gif. Simple HTML markup " +"does not work well in both IE and Firefox." msgstr "" #. Tag: para @@ -2035,8 +2111,8 @@ msgstr "" #: reference_measure.xml:1348 #, no-c-format msgid "" -"Given 2 linestrings, returns a number between -3 and 3 denoting what kind of" -" crossing behavior. 0 is no crossing." +"Given 2 linestrings, returns a number between -3 and 3 denoting what kind of " +"crossing behavior. 0 is no crossing." msgstr "" #. Tag: funcprototype @@ -2044,17 +2120,17 @@ msgstr "" #, no-c-format msgid "" "integer ST_LineCrossingDirection " -"geometry " -"linestringA geometry " -" linestringB" +"geometry linestringA geometry linestringB" msgstr "" #. Tag: para #: reference_measure.xml:1364 #, no-c-format msgid "" -"Given 2 linestrings, returns a number between -3 and 3 denoting what kind of" -" crossing behavior. 0 is no crossing. This is only supported for " +"Given 2 linestrings, returns a number between -3 and 3 denoting what kind of " +"crossing behavior. 0 is no crossing. This is only supported for " "LINESTRING" msgstr "" @@ -2155,7 +2231,8 @@ msgid "" "FROM (\n" " SELECT\n" " ST_GeomFromText('LINESTRING(25 169,89 114,40 70,86 43)') As line1,\n" -" ST_GeomFromText('LINESTRING (171 154, 20 140, 71 74, 2.99 90.16)') As line2\n" +" ST_GeomFromText('LINESTRING (171 154, 20 140, 71 74, 2.99 90.16)') As " +"line2\n" ") As foo;\n" "\n" " l1_cross_l2 | l2_cross_l1\n" @@ -2189,7 +2266,8 @@ msgid "" " ST_LineCrossingDirection(foo.line2, foo.line1) As l2_cross_l1\n" "FROM (SELECT\n" " ST_GeomFromText('LINESTRING(25 169,89 114,40 70,86 43)') As line1,\n" -" ST_GeomFromText('LINESTRING(2.99 90.16,71 74,20 140,171 154)') As line2\n" +" ST_GeomFromText('LINESTRING(2.99 90.16,71 74,20 140,171 154)') As " +"line2\n" " ) As foo;\n" "\n" " l1_cross_l2 | l2_cross_l1\n" @@ -2202,7 +2280,8 @@ msgstr "" #, no-c-format msgid "" "SELECT s1.gid, s2.gid, ST_LineCrossingDirection(s1.the_geom, s2.the_geom)\n" -" FROM streets s1 CROSS JOIN streets s2 ON (s1.gid != s2.gid AND s1.the_geom && s2.the_geom )\n" +" FROM streets s1 CROSS JOIN streets s2 ON (s1.gid != s2.gid AND s1." +"the_geom && s2.the_geom )\n" "WHERE ST_CrossingDirection(s1.the_geom, s2.the_geom) > 0;" msgstr "" @@ -2260,12 +2339,14 @@ msgstr "" #: reference_measure.xml:1522 #, no-c-format msgid "" -"SELECT ST_Disjoint('POINT(0 0)'::geometry, 'LINESTRING ( 2 0, 0 2 )'::geometry);\n" +"SELECT ST_Disjoint('POINT(0 0)'::geometry, 'LINESTRING ( 2 0, 0 2 )'::" +"geometry);\n" " st_disjoint\n" "---------------\n" " t\n" "(1 row)\n" -"SELECT ST_Disjoint('POINT(0 0)'::geometry, 'LINESTRING ( 0 0, 0 2 )'::geometry);\n" +"SELECT ST_Disjoint('POINT(0 0)'::geometry, 'LINESTRING ( 0 0, 0 2 )'::" +"geometry);\n" " st_disjoint\n" "---------------\n" " f\n" @@ -2299,15 +2380,14 @@ msgstr "" msgid "" " float ST_Distance " "geometry g1 " -"geometry g2 " -" float " -"ST_Distance geography " -" gg1 geography " -"gg2 " -"float ST_Distance " -"geography gg1 " -"geography gg2 " -"boolean " +"geometry g2 float ST_Distance geography gg1 geography gg2 float " +"ST_Distance geography " +"gg1 geography " +"gg2 boolean " "use_spheroid " msgstr "" @@ -2346,9 +2426,9 @@ msgstr "" #: reference_measure.xml:1587 #, no-c-format msgid "" -"Enhanced: 2.1.0 improved speed for geography. See Making " -"Geography faster for details." +"Enhanced: 2.1.0 improved speed for geography. See Making Geography faster for details." msgstr "" #. Tag: para @@ -2367,28 +2447,36 @@ msgstr "" #: reference_measure.xml:1595 #, no-c-format msgid "" -"--Geometry example - units in planar degrees 4326 is WGS 84 long lat unit=degrees\n" +"--Geometry example - units in planar degrees 4326 is WGS 84 long lat " +"unit=degrees\n" "SELECT ST_Distance(\n" " ST_GeomFromText('POINT(-72.1235 42.3521)',4326),\n" -" ST_GeomFromText('LINESTRING(-72.1260 42.45, -72.123 42.1546)', 4326)\n" +" ST_GeomFromText('LINESTRING(-72.1260 42.45, -72.123 " +"42.1546)', 4326)\n" " );\n" "st_distance\n" "-----------------\n" "0.00150567726382282\n" "\n" -"-- Geometry example - units in meters (SRID: 26986 Massachusetts state plane meters) (most accurate for Massachusetts)\n" +"-- Geometry example - units in meters (SRID: 26986 Massachusetts state plane " +"meters) (most accurate for Massachusetts)\n" "SELECT ST_Distance(\n" -" ST_Transform(ST_GeomFromText('POINT(-72.1235 42.3521)',4326),26986),\n" -" ST_Transform(ST_GeomFromText('LINESTRING(-72.1260 42.45, -72.123 42.1546)', 4326),26986)\n" +" ST_Transform(ST_GeomFromText('POINT(-72.1235 " +"42.3521)',4326),26986),\n" +" ST_Transform(ST_GeomFromText('LINESTRING(-72.1260 " +"42.45, -72.123 42.1546)', 4326),26986)\n" " );\n" "st_distance\n" "-----------------\n" "123.797937878454\n" "\n" -"-- Geometry example - units in meters (SRID: 2163 US National Atlas Equal area) (least accurate)\n" +"-- Geometry example - units in meters (SRID: 2163 US National Atlas Equal " +"area) (least accurate)\n" "SELECT ST_Distance(\n" -" ST_Transform(ST_GeomFromText('POINT(-72.1235 42.3521)',4326),2163),\n" -" ST_Transform(ST_GeomFromText('LINESTRING(-72.1260 42.45, -72.123 42.1546)', 4326),2163)\n" +" ST_Transform(ST_GeomFromText('POINT(-72.1235 " +"42.3521)',4326),2163),\n" +" ST_Transform(ST_GeomFromText('LINESTRING(-72.1260 " +"42.45, -72.123 42.1546)', 4326),2163)\n" " );\n" "\n" "st_distance\n" @@ -2407,11 +2495,14 @@ msgstr "" #: reference_measure.xml:1599 #, no-c-format msgid "" -"-- same as geometry example but note units in meters - use sphere for slightly faster less accurate\n" -"SELECT ST_Distance(gg1, gg2) As spheroid_dist, ST_Distance(gg1, gg2, false) As sphere_dist \n" +"-- same as geometry example but note units in meters - use sphere for " +"slightly faster less accurate\n" +"SELECT ST_Distance(gg1, gg2) As spheroid_dist, ST_Distance(gg1, gg2, false) " +"As sphere_dist \n" "FROM (SELECT\n" " ST_GeographyFromText('SRID=4326;POINT(-72.1235 42.3521)') As gg1,\n" -" ST_GeographyFromText('SRID=4326;LINESTRING(-72.1260 42.45, -72.123 42.1546)') As gg2\n" +" ST_GeographyFromText('SRID=4326;LINESTRING(-72.1260 42.45, -72.123 " +"42.1546)') As gg2\n" " ) As foo ;\n" "\n" " spheroid_dist | sphere_dist\n" @@ -2424,8 +2515,8 @@ msgstr "" #, no-c-format msgid "" ", , , " -", , " +", , " msgstr "" #. Tag: refname @@ -2439,22 +2530,21 @@ msgstr "" #, no-c-format msgid "" "Returns the Hausdorff distance between two geometries. Basically a measure " -"of how similar or dissimilar 2 geometries are. Units are in the units of the" -" spatial reference system of the geometries." +"of how similar or dissimilar 2 geometries are. Units are in the units of the " +"spatial reference system of the geometries." msgstr "" #. Tag: funcsynopsis #: reference_measure.xml:1620 #, no-c-format msgid "" -" float " -"ST_HausdorffDistance geometry" -" g1 geometry " -" g2 " -" float " -"ST_HausdorffDistance geometry" -" g1 geometry " -" g2 float " +" float ST_HausdorffDistance geometry g1 geometry g2 float " +"ST_HausdorffDistance geometry " +" g1 geometry g2 float " "densifyFrac " msgstr "" @@ -2462,14 +2552,14 @@ msgstr "" #: reference_measure.xml:1648 #, no-c-format msgid "" -"Implements algorithm for computing a distance metric which can be thought of" -" as the \"Discrete Hausdorff Distance\". This is the Hausdorff distance " -"restricted to discrete points for one of the geometries. Wikipedia article on" -" Hausdorff distance Martin " -"Davis note on how Hausdorff Distance calculation was used to prove " -"correctness of the CascadePolygonUnion approach." +"Implements algorithm for computing a distance metric which can be thought of " +"as the \"Discrete Hausdorff Distance\". This is the Hausdorff distance " +"restricted to discrete points for one of the geometries. Wikipedia article on Hausdorff " +"distance Martin Davis note on how Hausdorff " +"Distance calculation was used to prove correctness of the " +"CascadePolygonUnion approach." msgstr "" #. Tag: para @@ -2487,8 +2577,8 @@ msgstr "" #: reference_measure.xml:1656 #, no-c-format msgid "" -"The current implementation supports only vertices as the discrete locations." -" This could be extended to allow an arbitrary density of points to be used." +"The current implementation supports only vertices as the discrete locations. " +"This could be extended to allow an arbitrary density of points to be used." msgstr "" #. Tag: para @@ -2512,8 +2602,8 @@ msgstr "" #: reference_measure.xml:1672 #, no-c-format msgid "" -"For each building, find the parcel that best represents it. First we require" -" the parcel intersect with the geometry. DISTINCT ON guarantees we get each " +"For each building, find the parcel that best represents it. First we require " +"the parcel intersect with the geometry. DISTINCT ON guarantees we get each " "building listed only once, the ORDER BY .. ST_HausdorffDistance gives us a " "preference of parcel that is most similar to the building." msgstr "" @@ -2523,8 +2613,10 @@ msgstr "" #, no-c-format msgid "" "SELECT DISTINCT ON(buildings.gid) buildings.gid, parcels.parcel_id \n" -" FROM buildings INNER JOIN parcels ON ST_Intersects(buildings.geom,parcels.geom) \n" -" ORDER BY buildings.gid, ST_HausdorffDistance(buildings.geom, parcels.geom);" +" FROM buildings INNER JOIN parcels ON ST_Intersects(buildings.geom,parcels." +"geom) \n" +" ORDER BY buildings.gid, ST_HausdorffDistance(buildings.geom, parcels." +"geom);" msgstr "" #. Tag: programlisting @@ -2544,7 +2636,8 @@ msgstr "" #: reference_measure.xml:1677 #, no-c-format msgid "" -"postgis=# SELECT st_hausdorffdistance('LINESTRING (130 0, 0 0, 0 150)'::geometry, 'LINESTRING (10 10, 10 150, 130 10)'::geometry, 0.5);\n" +"postgis=# SELECT st_hausdorffdistance('LINESTRING (130 0, 0 0, 0 150)'::" +"geometry, 'LINESTRING (10 10, 10 150, 130 10)'::geometry, 0.5);\n" " st_hausdorffdistance\n" " ----------------------\n" " 70\n" @@ -2594,13 +2687,15 @@ msgstr "" #: reference_measure.xml:1716 #, no-c-format msgid "" -"postgis=# SELECT ST_MaxDistance('POINT(0 0)'::geometry, 'LINESTRING ( 2 0, 0 2 )'::geometry);\n" +"postgis=# SELECT ST_MaxDistance('POINT(0 0)'::geometry, 'LINESTRING ( 2 0, 0 " +"2 )'::geometry);\n" " st_maxdistance\n" "-----------------\n" " 2\n" "(1 row)\n" "\n" -"postgis=# SELECT ST_MaxDistance('POINT(0 0)'::geometry, 'LINESTRING ( 2 2, 2 2 )'::geometry);\n" +"postgis=# SELECT ST_MaxDistance('POINT(0 0)'::geometry, 'LINESTRING ( 2 2, 2 " +"2 )'::geometry);\n" " st_maxdistance \n" "------------------\n" " 2.82842712474619\n" @@ -2610,7 +2705,8 @@ msgstr "" #. Tag: para #: reference_measure.xml:1722 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -2626,8 +2722,7 @@ msgid "" "Returns minimum distance in meters between two lon/lat geometries. Uses a " "spherical earth and radius derived from the spheroid defined by the SRID. " "Faster than ST_DistanceSpheroid , " -"but less accurate. PostGIS versions prior to 1.5 only implemented for " -"points." +"but less accurate. PostGIS versions prior to 1.5 only implemented for points." msgstr "" #. Tag: funcprototype @@ -2635,9 +2730,9 @@ msgstr "" #, no-c-format msgid "" "float ST_DistanceSphere " -"geometry " -"geomlonlatA geometry " -" geomlonlatB" +"geometry geomlonlatA geometry geomlonlatB" msgstr "" #. Tag: para @@ -2669,17 +2764,25 @@ msgstr "" #: reference_measure.xml:1764 #, no-c-format msgid "" -"SELECT round(CAST(ST_DistanceSphere(ST_Centroid(the_geom), ST_GeomFromText('POINT(-118 38)',4326)) As numeric),2) As dist_meters,\n" +"SELECT round(CAST(ST_DistanceSphere(ST_Centroid(the_geom), " +"ST_GeomFromText('POINT(-118 38)',4326)) As numeric),2) As dist_meters,\n" "round(CAST(ST_Distance(ST_Transform(ST_Centroid(the_geom),32611),\n" -" ST_Transform(ST_GeomFromText('POINT(-118 38)', 4326),32611)) As numeric),2) As dist_utm11_meters,\n" -"round(CAST(ST_Distance(ST_Centroid(the_geom), ST_GeomFromText('POINT(-118 38)', 4326)) As numeric),5) As dist_degrees,\n" +" ST_Transform(ST_GeomFromText('POINT(-118 38)', 4326),32611)) " +"As numeric),2) As dist_utm11_meters,\n" +"round(CAST(ST_Distance(ST_Centroid(the_geom), ST_GeomFromText('POINT(-118 " +"38)', 4326)) As numeric),5) As dist_degrees,\n" "round(CAST(ST_Distance(ST_Transform(the_geom,32611),\n" -" ST_Transform(ST_GeomFromText('POINT(-118 38)', 4326),32611)) As numeric),2) As min_dist_line_point_meters\n" +" ST_Transform(ST_GeomFromText('POINT(-118 38)', 4326),32611)) " +"As numeric),2) As min_dist_line_point_meters\n" "FROM\n" -" (SELECT ST_GeomFromText('LINESTRING(-118.584 38.374,-118.583 38.5)', 4326) As the_geom) as foo;\n" -" dist_meters | dist_utm11_meters | dist_degrees | min_dist_line_point_meters\n" -" -------------+-------------------+--------------+----------------------------\n" -" 70424.47 | 70438.00 | 0.72900 | 65871.18" +" (SELECT ST_GeomFromText('LINESTRING(-118.584 38.374,-118.583 38.5)', " +"4326) As the_geom) as foo;\n" +" dist_meters | dist_utm11_meters | dist_degrees | " +"min_dist_line_point_meters\n" +" -------------+-------------------+--------------" +"+----------------------------\n" +" 70424.47 | 70438.00 | 0.72900 " +"| 65871.18" msgstr "" #. Tag: para @@ -2707,10 +2810,9 @@ msgstr "" #, no-c-format msgid "" "float ST_DistanceSpheroid " -"geometry " -"geomlonlatA geometry " -" geomlonlatB " -"spheroid " +"geometry geomlonlatA geometry geomlonlatB spheroid " "measurement_spheroid" msgstr "" @@ -2745,13 +2847,19 @@ msgstr "" #, no-c-format msgid "" "SELECT round(CAST(\n" -" ST_DistanceSpheroid(ST_Centroid(the_geom), ST_GeomFromText('POINT(-118 38)',4326), 'SPHEROID[\"WGS 84\",6378137,298.257223563]')\n" +" ST_DistanceSpheroid(ST_Centroid(the_geom), " +"ST_GeomFromText('POINT(-118 38)',4326), 'SPHEROID[\"WGS " +"84\",6378137,298.257223563]')\n" " As numeric),2) As dist_meters_spheroid,\n" -" round(CAST(ST_DistanceSphere(ST_Centroid(the_geom), ST_GeomFromText('POINT(-118 38)',4326)) As numeric),2) As dist_meters_sphere,\n" +" round(CAST(ST_DistanceSphere(ST_Centroid(the_geom), " +"ST_GeomFromText('POINT(-118 38)',4326)) As numeric),2) As " +"dist_meters_sphere,\n" "round(CAST(ST_Distance(ST_Transform(ST_Centroid(the_geom),32611),\n" -" ST_Transform(ST_GeomFromText('POINT(-118 38)', 4326),32611)) As numeric),2) As dist_utm11_meters\n" +" ST_Transform(ST_GeomFromText('POINT(-118 38)', 4326),32611)) " +"As numeric),2) As dist_utm11_meters\n" "FROM\n" -" (SELECT ST_GeomFromText('LINESTRING(-118.584 38.374,-118.583 38.5)', 4326) As the_geom) as foo;\n" +" (SELECT ST_GeomFromText('LINESTRING(-118.584 38.374,-118.583 38.5)', " +"4326) As the_geom) as foo;\n" " dist_meters_spheroid | dist_meters_sphere | dist_utm11_meters\n" "----------------------+--------------------+-------------------\n" " 70454.92 | 70424.47 | 70438.00" @@ -2784,27 +2892,30 @@ msgid "" "boolean ST_DFullyWithin " "geometry g1 " "geometry g2 " -"double precision " -"distance" +"double precision distance" msgstr "" #. Tag: para #: reference_measure.xml:1852 #, no-c-format msgid "" -"Returns true if the geometries is fully within the specified distance of one" -" another. The distance is specified in units defined by the spatial " -"reference system of the geometries. For this function to make sense, the " -"source geometries must both be of the same coordinate projection, having the" -" same SRID." +"Returns true if the geometries is fully within the specified distance of one " +"another. The distance is specified in units defined by the spatial reference " +"system of the geometries. For this function to make sense, the source " +"geometries must both be of the same coordinate projection, having the same " +"SRID." msgstr "" #. Tag: programlisting #: reference_measure.xml:1869 #, no-c-format msgid "" -"postgis=# SELECT ST_DFullyWithin(geom_a, geom_b, 10) as DFullyWithin10, ST_DWithin(geom_a, geom_b, 10) as DWithin10, ST_DFullyWithin(geom_a, geom_b, 20) as DFullyWithin20 from \n" -" (select ST_GeomFromText('POINT(1 1)') as geom_a,ST_GeomFromText('LINESTRING(1 5, 2 7, 1 9, 14 12)') as geom_b) t1;\n" +"postgis=# SELECT ST_DFullyWithin(geom_a, geom_b, 10) as DFullyWithin10, " +"ST_DWithin(geom_a, geom_b, 10) as DWithin10, ST_DFullyWithin(geom_a, geom_b, " +"20) as DFullyWithin20 from \n" +" (select ST_GeomFromText('POINT(1 1)') as geom_a," +"ST_GeomFromText('LINESTRING(1 5, 2 7, 1 9, 14 12)') as geom_b) t1;\n" " \n" "-----------------\n" " DFullyWithin10 | DWithin10 | DFullyWithin20 |\n" @@ -2842,19 +2953,18 @@ msgid "" " boolean ST_DWithin " "geometry g1 " "geometry g2 " -"double precision " -"distance_of_srid " -" boolean ST_DWithin " -"geography gg1 " -"geography gg2 " -"double precision " -"distance_meters " +"double precision distance_of_srid boolean " +"ST_DWithin geography " +"gg1 geography " +"gg2 double precision distance_meters " " boolean ST_DWithin " "geography gg1 " "geography gg2 " -"double precision " -"distance_meters boolean " -" use_spheroid " +"double precision distance_meters boolean " +"use_spheroid " msgstr "" #. Tag: para @@ -2871,8 +2981,8 @@ msgstr "" msgid "" "For Geometries: The distance is specified in units defined by the spatial " "reference system of the geometries. For this function to make sense, the " -"source geometries must both be of the same coordinate projection, having the" -" same SRID." +"source geometries must both be of the same coordinate projection, having the " +"same SRID." msgstr "" #. Tag: para @@ -2888,8 +2998,8 @@ msgstr "" #: reference_measure.xml:1951 #, no-c-format msgid "" -"Prior to 1.3, ST_Expand was commonly used in conjunction with && and" -" ST_Distance to achieve the same effect and in pre-1.3.4 this function was " +"Prior to 1.3, ST_Expand was commonly used in conjunction with && and " +"ST_Distance to achieve the same effect and in pre-1.3.4 this function was " "basically short-hand for that construct. From 1.3.4, ST_DWithin uses a more " "short-circuit distance function which should make it more efficient than " "prior versions for larger buffer regions." @@ -2911,9 +3021,9 @@ msgstr "" #: reference_measure.xml:1961 #, no-c-format msgid "" -"Enhanced: 2.1.0 improved speed for geography. See Making " -"Geography faster for details." +"Enhanced: 2.1.0 improved speed for geography. See Making Geography faster for details." msgstr "" #. Tag: para @@ -2930,18 +3040,23 @@ msgid "" "--that is within 3000 units of the school.\n" "-- We do an ST_DWithin search to utilize indexes to limit our search list\n" "-- that the non-indexable ST_Distance needs to process\n" -"--If the units of the spatial reference is meters then units would be meters\n" -"SELECT DISTINCT ON (s.gid) s.gid, s.school_name, s.the_geom, h.hospital_name\n" +"--If the units of the spatial reference is meters then units would be " +"meters\n" +"SELECT DISTINCT ON (s.gid) s.gid, s.school_name, s.the_geom, h." +"hospital_name\n" " FROM schools s\n" -" LEFT JOIN hospitals h ON ST_DWithin(s.the_geom, h.the_geom, 3000)\n" +" LEFT JOIN hospitals h ON ST_DWithin(s.the_geom, h.the_geom, " +"3000)\n" " ORDER BY s.gid, ST_Distance(s.the_geom, h.the_geom);\n" "\n" "--The schools with no close hospitals\n" "--Find all schools with no hospital within 3000 units\n" -"--away from the school. Units is in units of spatial ref (e.g. meters, feet, degrees)\n" +"--away from the school. Units is in units of spatial ref (e.g. meters, " +"feet, degrees)\n" "SELECT s.gid, s.school_name\n" " FROM schools s\n" -" LEFT JOIN hospitals h ON ST_DWithin(s.the_geom, h.the_geom, 3000)\n" +" LEFT JOIN hospitals h ON ST_DWithin(s.the_geom, h.the_geom, " +"3000)\n" " WHERE h.gid IS NULL;" msgstr "" @@ -2978,8 +3093,8 @@ msgstr "" #: reference_measure.xml:1998 #, no-c-format msgid "" -"Returns TRUE if the given Geometries are \"spatially equal\". Use this for a" -" 'better' answer than '='. Note by spatially equal we mean ST_Within(A,B) = " +"Returns TRUE if the given Geometries are \"spatially equal\". Use this for a " +"'better' answer than '='. Note by spatially equal we mean ST_Within(A,B) = " "true and ST_Within(B,A) = true and also mean ordering of points can be " "different but represent the same geometry structure. To verify the order of " "points is consistent, use ST_OrderingEquals (it must be noted " @@ -3074,7 +3189,8 @@ msgstr "" #: reference_measure.xml:2058 #, no-c-format msgid "" -"SELECT ST_HasArc(ST_Collect('LINESTRING(1 2, 3 4, 5 6)', 'CIRCULARSTRING(1 1, 2 3, 4 5, 6 7, 5 6)'));\n" +"SELECT ST_HasArc(ST_Collect('LINESTRING(1 2, 3 4, 5 6)', 'CIRCULARSTRING(1 " +"1, 2 3, 4 5, 6 7, 5 6)'));\n" " st_hasarc\n" " --------\n" " t" @@ -3106,15 +3222,13 @@ msgstr "" #: reference_measure.xml:2079 #, no-c-format msgid "" -" boolean " -"ST_Intersects " -"geometry geomA " -"geometry geomB " -" boolean " -"ST_Intersects " -"geography geogA " -"geography geogB " -"" +" boolean ST_Intersects geometry geomA geometry geomB boolean " +"ST_Intersects geography geogA geography geogB " msgstr "" #. Tag: para @@ -3173,12 +3287,14 @@ msgstr "" #: reference_measure.xml:2140 #, no-c-format msgid "" -"SELECT ST_Intersects('POINT(0 0)'::geometry, 'LINESTRING ( 2 0, 0 2 )'::geometry);\n" +"SELECT ST_Intersects('POINT(0 0)'::geometry, 'LINESTRING ( 2 0, 0 2 )'::" +"geometry);\n" " st_intersects\n" "---------------\n" " f\n" "(1 row)\n" -"SELECT ST_Intersects('POINT(0 0)'::geometry, 'LINESTRING ( 0 0, 0 2 )'::geometry);\n" +"SELECT ST_Intersects('POINT(0 0)'::geometry, 'LINESTRING ( 0 0, 0 2 )'::" +"geometry);\n" " st_intersects\n" "---------------\n" " t\n" @@ -3190,8 +3306,10 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_Intersects(\n" -" ST_GeographyFromText('SRID=4326;LINESTRING(-43.23456 72.4567,-43.23456 72.4568)'),\n" -" ST_GeographyFromText('SRID=4326;POINT(-43.23456 72.4567772)')\n" +" ST_GeographyFromText('SRID=4326;LINESTRING(-43.23456 " +"72.4567,-43.23456 72.4568)'),\n" +" ST_GeographyFromText('SRID=4326;POINT(-43.23456 " +"72.4567772)')\n" " );\n" "\n" " st_intersects\n" @@ -3225,12 +3343,12 @@ msgstr "" #, no-c-format msgid "" " float ST_Length " -"geometry " -"a_2dlinestring " -" float ST_Length " -"geography geog " -"boolean " -"use_spheroid=true " +"geometry a_2dlinestring float " +"ST_Length geography geog boolean use_spheroid=true " +"" msgstr "" #. Tag: para @@ -3239,8 +3357,8 @@ msgstr "" msgid "" "For geometry: Returns the 2D Cartesian length of the geometry if it is a " "LineString, MultiLineString, ST_Curve, ST_MultiCurve. 0 is returned for " -"areal geometries. For areal geometries use ." -" For geometry types, units for length measures are specified by the spatial " +"areal geometries. For areal geometries use . " +"For geometry types, units for length measures are specified by the spatial " "reference system of the geometry." msgstr "" @@ -3251,28 +3369,27 @@ msgid "" "For geography types, the calculations are performed using the inverse " "geodesic problem, where length units are in meters. If PostGIS is compiled " "with PROJ version 4.8.0 or later, the spheroid is specified by the SRID, " -"otherwise it is exclusive to WGS84. If " -"use_spheroid=false, then calculations will approximate a " -"sphere instead of a spheroid." +"otherwise it is exclusive to WGS84. If use_spheroid=false, then calculations will approximate a sphere instead of a spheroid." msgstr "" #. Tag: para #: reference_measure.xml:2180 #, no-c-format msgid "" -"Currently for geometry this is an alias for ST_Length2D, but this may change" -" to support higher dimensions." +"Currently for geometry this is an alias for ST_Length2D, but this may change " +"to support higher dimensions." msgstr "" #. Tag: para #: reference_measure.xml:2181 #, no-c-format msgid "" -"Changed: 2.0.0 Breaking change -- in prior versions applying this to a " -"MULTI/POLYGON of type geography would give you the perimeter of the " -"POLYGON/MULTIPOLYGON. In 2.0.0 this was changed to return 0 to be in line " -"with geometry behavior. Please use ST_Perimeter if you want the perimeter of" -" a polygon" +"Changed: 2.0.0 Breaking change -- in prior versions applying this to a MULTI/" +"POLYGON of type geography would give you the perimeter of the POLYGON/" +"MULTIPOLYGON. In 2.0.0 this was changed to return 0 to be in line with " +"geometry behavior. Please use ST_Perimeter if you want the perimeter of a " +"polygon" msgstr "" #. Tag: para @@ -3313,7 +3430,8 @@ msgstr "" #: reference_measure.xml:2194 #, no-c-format msgid "" -"SELECT ST_Length(ST_GeomFromText('LINESTRING(743238 2967416,743238 2967450,743265 2967450,\n" +"SELECT ST_Length(ST_GeomFromText('LINESTRING(743238 2967416,743238 " +"2967450,743265 2967450,\n" "743265.625 2967416,743238 2967416)',2249));\n" "st_length\n" "---------\n" @@ -3323,7 +3441,8 @@ msgid "" "--Transforming WGS 84 LineString to Massachusetts state plane meters\n" "SELECT ST_Length(\n" " ST_Transform(\n" -" ST_GeomFromEWKT('SRID=4326;LINESTRING(-72.1260 42.45, -72.1240 42.45666, -72.123 42.1546)'),\n" +" ST_GeomFromEWKT('SRID=4326;LINESTRING(-72.1260 42.45, " +"-72.1240 42.45666, -72.123 42.1546)'),\n" " 26986\n" " )\n" ");\n" @@ -3343,9 +3462,11 @@ msgstr "" #, no-c-format msgid "" "-- default calculation is using a sphere rather than spheroid\n" -"SELECT ST_Length(the_geog) As length_spheroid, ST_Length(the_geog,false) As length_sphere\n" +"SELECT ST_Length(the_geog) As length_spheroid, ST_Length(the_geog,false) As " +"length_sphere\n" "FROM (SELECT ST_GeographyFromText(\n" -"'SRID=4326;LINESTRING(-72.1260 42.45, -72.1240 42.45666, -72.123 42.1546)') As the_geog)\n" +"'SRID=4326;LINESTRING(-72.1260 42.45, -72.1240 42.45666, -72.123 42.1546)') " +"As the_geog)\n" " As foo;\n" " length_spheroid | length_sphere\n" "------------------+------------------\n" @@ -3356,9 +3477,8 @@ msgstr "" #: reference_measure.xml:2203 #, no-c-format msgid "" -", , , , " +", , , , " msgstr "" #. Tag: refname @@ -3372,8 +3492,8 @@ msgstr "" #, no-c-format msgid "" "Returns the 2-dimensional length of the geometry if it is a " -"linestring or multi-linestring. This is an alias for " -"ST_Length" +"linestring or multi-linestring. This is an alias for ST_Length" msgstr "" #. Tag: funcprototype @@ -3381,17 +3501,16 @@ msgstr "" #, no-c-format msgid "" "float ST_Length2D " -"geometry " -"a_2dlinestring" +"geometry a_2dlinestring" msgstr "" #. Tag: para #: reference_measure.xml:2227 #, no-c-format msgid "" -"Returns the 2-dimensional length of the geometry if it is a linestring" -" or multi-linestring. This is an alias for " -"ST_Length" +"Returns the 2-dimensional length of the geometry if it is a linestring " +"or multi-linestring. This is an alias for ST_Length" msgstr "" #. Tag: para @@ -3410,8 +3529,8 @@ msgstr "" #: reference_measure.xml:2244 #, no-c-format msgid "" -"Returns the 3-dimensional or 2-dimensional length of the geometry if it is a" -" linestring or multi-linestring." +"Returns the 3-dimensional or 2-dimensional length of the geometry if it is a " +"linestring or multi-linestring." msgstr "" #. Tag: funcprototype @@ -3419,16 +3538,16 @@ msgstr "" #, no-c-format msgid "" "float ST_3DLength " -"geometry " -"a_3dlinestring" +"geometry a_3dlinestring" msgstr "" #. Tag: para #: reference_measure.xml:2260 #, no-c-format msgid "" -"Returns the 3-dimensional or 2-dimensional length of the geometry if it is a" -" linestring or multi-linestring. For 2-d lines it will just return the 2-d " +"Returns the 3-dimensional or 2-dimensional length of the geometry if it is a " +"linestring or multi-linestring. For 2-d lines it will just return the 2-d " "length (same as ST_Length and ST_Length2D)" msgstr "" @@ -3442,15 +3561,16 @@ msgstr "" #: reference_measure.xml:2270 #, no-c-format msgid "" -"Return length in feet for a 3D cable. Note this is in feet because EPSG:2249" -" is Massachusetts State Plane Feet" +"Return length in feet for a 3D cable. Note this is in feet because EPSG:2249 " +"is Massachusetts State Plane Feet" msgstr "" #. Tag: programlisting #: reference_measure.xml:2272 #, no-c-format msgid "" -"SELECT ST_3DLength(ST_GeomFromText('LINESTRING(743238 2967416 1,743238 2967450 1,743265 2967450 3,\n" +"SELECT ST_3DLength(ST_GeomFromText('LINESTRING(743238 2967416 1,743238 " +"2967450 1,743265 2967450 3,\n" "743265.625 2967416 3,743238 2967416 3)',2249));\n" "ST_3DLength\n" "-----------\n" @@ -3483,9 +3603,9 @@ msgstr "" #, no-c-format msgid "" "float ST_LengthSpheroid " -"geometry " -"a_linestring spheroid " -" a_spheroid" +"geometry a_linestring spheroid a_spheroid" msgstr "" #. Tag: para @@ -3543,9 +3663,11 @@ msgid "" "SELECT ST_LengthSpheroid( the_geom, sph_m ) As tot_len,\n" "ST_LengthSpheroid(ST_GeometryN(the_geom,1), sph_m) As len_line1,\n" "ST_LengthSpheroid(ST_GeometryN(the_geom,2), sph_m) As len_line2\n" -" FROM (SELECT ST_GeomFromText('MULTILINESTRING((-118.584 38.374,-118.583 38.5),\n" +" FROM (SELECT " +"ST_GeomFromText('MULTILINESTRING((-118.584 38.374,-118.583 38.5),\n" " (-71.05957 42.3589 , -71.061 43))') As the_geom,\n" -"CAST('SPHEROID[\"GRS_1980\",6378137,298.257222101]' As spheroid) As sph_m) as foo;\n" +"CAST('SPHEROID[\"GRS_1980\",6378137,298.257222101]' As spheroid) As sph_m) " +"as foo;\n" " tot_len | len_line1 | len_line2\n" "------------------+------------------+------------------\n" " 85204.5207562955 | 13986.8725229309 | 71217.6482333646\n" @@ -3554,9 +3676,11 @@ msgid "" "SELECT ST_LengthSpheroid( the_geom, sph_m ) As tot_len,\n" "ST_LengthSpheroid(ST_GeometryN(the_geom,1), sph_m) As len_line1,\n" "ST_LengthSpheroid(ST_GeometryN(the_geom,2), sph_m) As len_line2\n" -" FROM (SELECT ST_GeomFromEWKT('MULTILINESTRING((-118.584 38.374 20,-118.583 38.5 30),\n" +" FROM (SELECT " +"ST_GeomFromEWKT('MULTILINESTRING((-118.584 38.374 20,-118.583 38.5 30),\n" " (-71.05957 42.3589 75, -71.061 43 90))') As the_geom,\n" -"CAST('SPHEROID[\"GRS_1980\",6378137,298.257222101]' As spheroid) As sph_m) as foo;\n" +"CAST('SPHEROID[\"GRS_1980\",6378137,298.257222101]' As spheroid) As sph_m) " +"as foo;\n" "\n" " tot_len | len_line1 | len_line2\n" "------------------+-----------------+------------------\n" @@ -3589,9 +3713,9 @@ msgstr "" #, no-c-format msgid "" "float ST_Length2D_Spheroid " -"geometry " -"a_linestring spheroid " -" a_spheroid" +"geometry a_linestring spheroid a_spheroid" msgstr "" #. Tag: para @@ -3623,9 +3747,11 @@ msgid "" "SELECT ST_Length2D_Spheroid( the_geom, sph_m ) As tot_len,\n" "ST_Length2D_Spheroid(ST_GeometryN(the_geom,1), sph_m) As len_line1,\n" "ST_Length2D_Spheroid(ST_GeometryN(the_geom,2), sph_m) As len_line2\n" -" FROM (SELECT ST_GeomFromText('MULTILINESTRING((-118.584 38.374,-118.583 38.5),\n" +" FROM (SELECT " +"ST_GeomFromText('MULTILINESTRING((-118.584 38.374,-118.583 38.5),\n" " (-71.05957 42.3589 , -71.061 43))') As the_geom,\n" -"CAST('SPHEROID[\"GRS_1980\",6378137,298.257222101]' As spheroid) As sph_m) as foo;\n" +"CAST('SPHEROID[\"GRS_1980\",6378137,298.257222101]' As spheroid) As sph_m) " +"as foo;\n" " tot_len | len_line1 | len_line2\n" "------------------+------------------+------------------\n" " 85204.5207562955 | 13986.8725229309 | 71217.6482333646\n" @@ -3634,9 +3760,11 @@ msgid "" "SELECT ST_Length2D_Spheroid( the_geom, sph_m ) As tot_len,\n" "ST_Length2D_Spheroid(ST_GeometryN(the_geom,1), sph_m) As len_line1,\n" "ST_Length2D_Spheroid(ST_GeometryN(the_geom,2), sph_m) As len_line2\n" -" FROM (SELECT ST_GeomFromEWKT('MULTILINESTRING((-118.584 38.374 20,-118.583 38.5 30),\n" +" FROM (SELECT " +"ST_GeomFromEWKT('MULTILINESTRING((-118.584 38.374 20,-118.583 38.5 30),\n" " (-71.05957 42.3589 75, -71.061 43 90))') As the_geom,\n" -"CAST('SPHEROID[\"GRS_1980\",6378137,298.257222101]' As spheroid) As sph_m) as foo;\n" +"CAST('SPHEROID[\"GRS_1980\",6378137,298.257222101]' As spheroid) As sph_m) " +"as foo;\n" "\n" " tot_len | len_line1 | len_line2\n" "------------------+------------------+------------------\n" @@ -3661,8 +3789,8 @@ msgstr "" msgid "" "Returns the 2-dimensional longest line points of two geometries. The " "function will only return the first longest line if more than one, that the " -"function finds. The line returned will always start in g1 and end in g2. The" -" length of the line this function returns will always be the same as " +"function finds. The line returned will always start in g1 and end in g2. The " +"length of the line this function returns will always be the same as " "st_maxdistance returns for g1 and g2." msgstr "" @@ -3742,7 +3870,8 @@ msgid "" " ST_MaxDistance(c.the_geom,c.the_geom) As max_dist, \n" " ST_Length(ST_LongestLine(c.the_geom, c.the_geom)) As lenll \n" "FROM (SELECT ST_BuildArea(ST_Collect(the_geom)) As the_geom\n" -" FROM (SELECT ST_Translate(ST_SnapToGrid(ST_Buffer(ST_Point(50 ,generate_series(50,190, 50) \n" +" FROM (SELECT ST_Translate(ST_SnapToGrid(ST_Buffer(ST_Point(50 ," +"generate_series(50,190, 50) \n" " ),40, 'quad_segs=2'),1), x, 0) As the_geom \n" " FROM generate_series(1,100,50) As x) AS foo\n" ") As c;\n" @@ -3755,7 +3884,8 @@ msgstr "" #. Tag: para #: reference_measure.xml:2479 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -3786,17 +3916,17 @@ msgstr "" #, no-c-format msgid "" "ST_OrderingEquals compares two geometries and returns t (TRUE) if the " -"geometries are equal and the coordinates are in the same order; otherwise it" -" returns f (FALSE)." +"geometries are equal and the coordinates are in the same order; otherwise it " +"returns f (FALSE)." msgstr "" #. Tag: para #: reference_measure.xml:2509 #, no-c-format msgid "" -"This function is implemented as per the ArcSDE SQL specification rather than" -" SQL-MM. " -"http://edndoc.esri.com/arcsde/9.1/sql_api/sqlapi3.htm#ST_OrderingEquals" +"This function is implemented as per the ArcSDE SQL specification rather than " +"SQL-MM. http://edndoc.esri.com/arcsde/9.1/sql_api/sqlapi3." +"htm#ST_OrderingEquals" msgstr "" #. Tag: para @@ -3823,7 +3953,8 @@ msgid "" " t\n" "(1 row)\n" "\n" -"SELECT ST_OrderingEquals(ST_Reverse(ST_GeomFromText('LINESTRING(0 0, 10 10)')),\n" +"SELECT ST_OrderingEquals(ST_Reverse(ST_GeomFromText('LINESTRING(0 0, 10 " +"10)')),\n" " ST_GeomFromText('LINESTRING(0 0, 0 0, 10 10)'));\n" " st_orderingequals\n" "-----------\n" @@ -3879,9 +4010,9 @@ msgstr "" #: reference_measure.xml:2554 #, no-c-format msgid "" -"This function call will automatically include a bounding box comparison that" -" will make use of any indexes that are available on the geometries. To avoid" -" index use, use the function _ST_Overlaps." +"This function call will automatically include a bounding box comparison that " +"will make use of any indexes that are available on the geometries. To avoid " +"index use, use the function _ST_Overlaps." msgstr "" #. Tag: para @@ -3907,46 +4038,59 @@ msgstr "" #: reference_measure.xml:2603 #, no-c-format msgid "" -"--a point on a line is contained by the line and is of a lower dimension, and therefore does not overlap the line\n" +"--a point on a line is contained by the line and is of a lower dimension, " +"and therefore does not overlap the line\n" " nor crosses\n" "\n" "SELECT ST_Overlaps(a,b) As a_overlap_b,\n" " ST_Crosses(a,b) As a_crosses_b,\n" -" ST_Intersects(a, b) As a_intersects_b, ST_Contains(b,a) As b_contains_a\n" -"FROM (SELECT ST_GeomFromText('POINT(1 0.5)') As a, ST_GeomFromText('LINESTRING(1 0, 1 1, 3 5)') As b)\n" +" ST_Intersects(a, b) As a_intersects_b, ST_Contains(b,a) As " +"b_contains_a\n" +"FROM (SELECT ST_GeomFromText('POINT(1 0.5)') As a, " +"ST_GeomFromText('LINESTRING(1 0, 1 1, 3 5)') As b)\n" " As foo\n" "\n" "a_overlap_b | a_crosses_b | a_intersects_b | b_contains_a\n" "------------+-------------+----------------+--------------\n" "f | f | t | t\n" "\n" -"--a line that is partly contained by circle, but not fully is defined as intersecting and crossing,\n" +"--a line that is partly contained by circle, but not fully is defined as " +"intersecting and crossing,\n" "-- but since of different dimension it does not overlap\n" "SELECT ST_Overlaps(a,b) As a_overlap_b, ST_Crosses(a,b) As a_crosses_b,\n" " ST_Intersects(a, b) As a_intersects_b,\n" " ST_Contains(a,b) As a_contains_b\n" -"FROM (SELECT ST_Buffer(ST_GeomFromText('POINT(1 0.5)'), 3) As a, ST_GeomFromText('LINESTRING(1 0, 1 1, 3 5)') As b)\n" +"FROM (SELECT ST_Buffer(ST_GeomFromText('POINT(1 0.5)'), 3) As a, " +"ST_GeomFromText('LINESTRING(1 0, 1 1, 3 5)') As b)\n" " As foo;\n" "\n" " a_overlap_b | a_crosses_b | a_intersects_b | a_contains_b\n" "-------------+-------------+----------------+--------------\n" " f | t | t | f\n" "\n" -" -- a 2-dimensional bent hot dog (aka buffered line string) that intersects a circle,\n" -" -- but is not fully contained by the circle is defined as overlapping since they are of the same dimension,\n" -"-- but it does not cross, because the intersection of the 2 is of the same dimension\n" +" -- a 2-dimensional bent hot dog (aka buffered line string) that intersects " +"a circle,\n" +" -- but is not fully contained by the circle is defined as " +"overlapping since they are of the same dimension,\n" +"-- but it does not cross, because the intersection of the 2 is of the " +"same dimension\n" "-- as the maximum dimension of the 2\n" "\n" -"SELECT ST_Overlaps(a,b) As a_overlap_b, ST_Crosses(a,b) As a_crosses_b, ST_Intersects(a, b) As a_intersects_b,\n" +"SELECT ST_Overlaps(a,b) As a_overlap_b, ST_Crosses(a,b) As a_crosses_b, " +"ST_Intersects(a, b) As a_intersects_b,\n" "ST_Contains(b,a) As b_contains_a,\n" -"ST_Dimension(a) As dim_a, ST_Dimension(b) as dim_b, ST_Dimension(ST_Intersection(a,b)) As dima_intersection_b\n" +"ST_Dimension(a) As dim_a, ST_Dimension(b) as dim_b, " +"ST_Dimension(ST_Intersection(a,b)) As dima_intersection_b\n" "FROM (SELECT ST_Buffer(ST_GeomFromText('POINT(1 0.5)'), 3) As a,\n" " ST_Buffer(ST_GeomFromText('LINESTRING(1 0, 1 1, 3 5)'),0.5) As b)\n" " As foo;\n" "\n" -" a_overlap_b | a_crosses_b | a_intersects_b | b_contains_a | dim_a | dim_b | dima_intersection_b\n" -"-------------+-------------+----------------+--------------+-------+-------+---------------------\n" -" t | f | t | f | 2 | 2 | 2" +" a_overlap_b | a_crosses_b | a_intersects_b | b_contains_a | dim_a | dim_b | " +"dima_intersection_b\n" +"-------------+-------------+----------------+--------------+-------+-------" +"+---------------------\n" +" t | f | t | f | 2 | 2 " +"| 2" msgstr "" #. Tag: para @@ -3977,12 +4121,11 @@ msgstr "" #, no-c-format msgid "" " float ST_Perimeter " -"geometry g1 " -" float " -"ST_Perimeter geography " -"geog boolean " -"use_spheroid=true " +"geometry g1 float ST_Perimeter geography geog boolean use_spheroid=true " msgstr "" #. Tag: para @@ -4003,9 +4146,8 @@ msgid "" "For geography types, the calculations are performed using the inverse " "geodesic problem, where perimeter units are in meters. If PostGIS is " "compiled with PROJ version 4.8.0 or later, the spheroid is specified by the " -"SRID, otherwise it is exclusive to WGS84. If " -"use_spheroid=false, then calculations will approximate a " -"sphere instead of a spheroid." +"SRID, otherwise it is exclusive to WGS84. If use_spheroid=false, then calculations will approximate a sphere instead of a spheroid." msgstr "" #. Tag: para @@ -4046,14 +4188,16 @@ msgstr "" #: reference_measure.xml:2656 #, no-c-format msgid "" -"SELECT ST_Perimeter(ST_GeomFromText('POLYGON((743238 2967416,743238 2967450,743265 2967450,\n" +"SELECT ST_Perimeter(ST_GeomFromText('POLYGON((743238 2967416,743238 " +"2967450,743265 2967450,\n" "743265.625 2967416,743238 2967416))', 2249));\n" "st_perimeter\n" "---------\n" " 122.630744000095\n" "(1 row)\n" "\n" -"SELECT ST_Perimeter(ST_GeomFromText('MULTIPOLYGON(((763104.471273676 2949418.44119003,\n" +"SELECT ST_Perimeter(ST_GeomFromText('MULTIPOLYGON(((763104.471273676 " +"2949418.44119003,\n" "763104.477769673 2949418.42538203,\n" "763104.189609677 2949418.22343004,763104.471273676 2949418.44119003)),\n" "((763104.471273676 2949418.44119003,763095.804579742 2949436.33850239,\n" @@ -4088,9 +4232,12 @@ msgstr "" #: reference_measure.xml:2661 #, no-c-format msgid "" -"SELECT ST_Perimeter(geog) As per_meters, ST_Perimeter(geog)/0.3048 As per_ft \n" -"FROM ST_GeogFromText('POLYGON((-71.1776848522251 42.3902896512902,-71.1776843766326 42.3903829478009,\n" -"-71.1775844305465 42.3903826677917,-71.1775825927231 42.3902893647987,-71.1776848522251 42.3902896512902))') As geog;\n" +"SELECT ST_Perimeter(geog) As per_meters, ST_Perimeter(geog)/0.3048 As " +"per_ft \n" +"FROM ST_GeogFromText('POLYGON((-71.1776848522251 " +"42.3902896512902,-71.1776843766326 42.3903829478009,\n" +"-71.1775844305465 42.3903826677917,-71.1775825927231 " +"42.3902893647987,-71.1776848522251 42.3902896512902))') As geog;\n" "\n" " per_meters | per_ft\n" "-----------------+------------------\n" @@ -4098,15 +4245,21 @@ msgid "" "\n" "\n" "-- MultiPolygon example --\n" -"SELECT ST_Perimeter(geog) As per_meters, ST_Perimeter(geog,false) As per_sphere_meters, ST_Perimeter(geog)/0.3048 As per_ft \n" -"FROM ST_GeogFromText('MULTIPOLYGON(((-71.1044543107478 42.340674480411,-71.1044542869917 42.3406744369506,\n" +"SELECT ST_Perimeter(geog) As per_meters, ST_Perimeter(geog,false) As " +"per_sphere_meters, ST_Perimeter(geog)/0.3048 As per_ft \n" +"FROM ST_GeogFromText('MULTIPOLYGON(((-71.1044543107478 " +"42.340674480411,-71.1044542869917 42.3406744369506,\n" "-71.1044553562977 42.340673886454,-71.1044543107478 42.340674480411)),\n" -"((-71.1044543107478 42.340674480411,-71.1044860600303 42.3407237015564,-71.1045215770124 42.3407653385914,\n" -"-71.1045498002983 42.3407946553165,-71.1045611902745 42.3408058316308,-71.1046016507427 42.340837442371,\n" -"-71.104617893173 42.3408475056957,-71.1048586153981 42.3409875993595,-71.1048736143677 42.3409959528211,\n" +"((-71.1044543107478 42.340674480411,-71.1044860600303 " +"42.3407237015564,-71.1045215770124 42.3407653385914,\n" +"-71.1045498002983 42.3407946553165,-71.1045611902745 " +"42.3408058316308,-71.1046016507427 42.340837442371,\n" +"-71.104617893173 42.3408475056957,-71.1048586153981 " +"42.3409875993595,-71.1048736143677 42.3409959528211,\n" "-71.1048878050242 42.3410084812078,-71.1044020965803 42.3414730072048,\n" "-71.1039672113619 42.3412202916693,-71.1037740497748 42.3410666421308,\n" -"-71.1044280218456 42.3406894151355,-71.1044543107478 42.340674480411)))') As geog;\n" +"-71.1044280218456 42.3406894151355,-71.1044543107478 42.340674480411)))') As " +"geog;\n" "\n" " per_meters | per_sphere_meters | per_ft\n" "------------------+-------------------+------------------\n" @@ -4153,8 +4306,8 @@ msgstr "" #: reference_measure.xml:2694 #, no-c-format msgid "" -"This is currently an alias for ST_Perimeter. In future versions ST_Perimeter" -" may return the highest dimension perimeter for a geometry. This is still " +"This is currently an alias for ST_Perimeter. In future versions ST_Perimeter " +"may return the highest dimension perimeter for a geometry. This is still " "under consideration" msgstr "" @@ -4207,8 +4360,10 @@ msgstr "" #: reference_measure.xml:2736 #, no-c-format msgid "" -"SELECT ST_3DPerimeter(the_geom), ST_Perimeter2d(the_geom), ST_Perimeter(the_geom) FROM\n" -" (SELECT ST_GeomFromEWKT('SRID=2249;POLYGON((743238 2967416 2,743238 2967450 1,\n" +"SELECT ST_3DPerimeter(the_geom), ST_Perimeter2d(the_geom), " +"ST_Perimeter(the_geom) FROM\n" +" (SELECT ST_GeomFromEWKT('SRID=2249;POLYGON((743238 " +"2967416 2,743238 2967450 1,\n" "743265.625 2967416 1,743238 2967416 2))') As the_geom) As foo;\n" "\n" " ST_3DPerimeter | st_perimeter2d | st_perimeter\n" @@ -4282,13 +4437,15 @@ msgid "" " POINT(0 5)\n" "(1 row)\n" "\n" -"SELECT ST_AsText(ST_PointOnSurface('POLYGON((0 0, 0 5, 5 5, 5 0, 0 0))'::geometry));\n" +"SELECT ST_AsText(ST_PointOnSurface('POLYGON((0 0, 0 5, 5 5, 5 0, 0 0))'::" +"geometry));\n" " st_astext\n" "----------------\n" " POINT(2.5 2.5)\n" "(1 row)\n" "\n" -"SELECT ST_AsEWKT(ST_PointOnSurface(ST_GeomFromEWKT('LINESTRING(0 5 1, 0 0 1, 0 10 2)')));\n" +"SELECT ST_AsEWKT(ST_PointOnSurface(ST_GeomFromEWKT('LINESTRING(0 5 1, 0 0 1, " +"0 10 2)')));\n" " st_asewkt\n" "----------------\n" " POINT(0 0 1)\n" @@ -4338,8 +4495,8 @@ msgstr "" #: reference_measure.xml:2816 #, no-c-format msgid "" -"The azimuth is sometimes called the heading or the bearing in navigation. It" -" is measured relative to true north (azimuth zero). East is azimuth 90 " +"The azimuth is sometimes called the heading or the bearing in navigation. It " +"is measured relative to true north (azimuth zero). East is azimuth 90 " "(π/2), south is azimuth 180 (π), west is azimuth 270 " "(3π/2)." msgstr "" @@ -4362,7 +4519,8 @@ msgstr "" #: reference_measure.xml:2826 #, no-c-format msgid "" -"SELECT ST_AsText(ST_Project('POINT(0 0)'::geography, 100000, radians(45.0)));\n" +"SELECT ST_AsText(ST_Project('POINT(0 0)'::geography, 100000, " +"radians(45.0)));\n" "\n" " st_astext\n" "--------------------------------------------\n" @@ -4374,9 +4532,9 @@ msgstr "" #: reference_measure.xml:2832 #, no-c-format msgid "" -", , PostgreSQL Math Functions" +", , PostgreSQL Math Functions" msgstr "" #. Tag: refname @@ -4390,9 +4548,9 @@ msgstr "" #, no-c-format msgid "" "Returns true if this Geometry is spatially related to anotherGeometry, by " -"testing for intersections between the Interior, Boundary and Exterior of the" -" two geometries as specified by the values in the intersectionMatrixPattern." -" If no intersectionMatrixPattern is passed in, then returns the maximum " +"testing for intersections between the Interior, Boundary and Exterior of the " +"two geometries as specified by the values in the intersectionMatrixPattern. " +"If no intersectionMatrixPattern is passed in, then returns the maximum " "intersectionMatrixPattern that relates the 2 geometries." msgstr "" @@ -4403,16 +4561,16 @@ msgid "" " boolean ST_Relate " "geometry geomA " "geometry geomB " -"text " -"intersectionMatrixPattern " -" text ST_Relate " -"geometry geomA " -"geometry geomB " -" text " +"text intersectionMatrixPattern text " "ST_Relate geometry " "geomA geometry " -"geomB integer " -"BoundaryNodeRule " +"geomB " +"text ST_Relate " +"geometry geomA " +"geometry geomB " +"integer BoundaryNodeRule " msgstr "" #. Tag: para @@ -4422,8 +4580,8 @@ msgid "" "Version 1: Takes geomA, geomB, intersectionMatrix and Returns 1 (TRUE) if " "this Geometry is spatially related to anotherGeometry, by testing for " "intersections between the Interior, Boundary and Exterior of the two " -"geometries as specified by the values in the DE-9IM matrix pattern." +"geometries as specified by the values in the DE-9IM matrix pattern." msgstr "" #. Tag: para @@ -4462,8 +4620,8 @@ msgstr "" #: reference_measure.xml:2892 #, no-c-format msgid "" -"Version 3: same as version 2, but allows to specify a boundary node rule " -"(1:OGC/MOD2, 2:Endpoint, 3:MultivalentEndpoint, 4:MonovalentEndpoint)" +"Version 3: same as version 2, but allows to specify a boundary node rule (1:" +"OGC/MOD2, 2:Endpoint, 3:MultivalentEndpoint, 4:MonovalentEndpoint)" msgstr "" #. Tag: para @@ -4490,30 +4648,35 @@ msgstr "" #: reference_measure.xml:2909 #, no-c-format msgid "" -"--Find all compounds that intersect and not touch a poly (interior intersects)\n" +"--Find all compounds that intersect and not touch a poly (interior " +"intersects)\n" "SELECT l.* , b.name As poly_name\n" " FROM polys As b\n" "INNER JOIN compounds As l\n" "ON (p.the_geom && b.the_geom\n" "AND ST_Relate(l.the_geom, b.the_geom,'T********'));\n" "\n" -"SELECT ST_Relate(ST_GeometryFromText('POINT(1 2)'), ST_Buffer(ST_GeometryFromText('POINT(1 2)'),2));\n" +"SELECT ST_Relate(ST_GeometryFromText('POINT(1 2)'), " +"ST_Buffer(ST_GeometryFromText('POINT(1 2)'),2));\n" "st_relate\n" "-----------\n" "0FFFFF212\n" "\n" -"SELECT ST_Relate(ST_GeometryFromText('LINESTRING(1 2, 3 4)'), ST_GeometryFromText('LINESTRING(5 6, 7 8)'));\n" +"SELECT ST_Relate(ST_GeometryFromText('LINESTRING(1 2, 3 4)'), " +"ST_GeometryFromText('LINESTRING(5 6, 7 8)'));\n" "st_relate\n" "-----------\n" "FF1FF0102\n" "\n" "\n" -"SELECT ST_Relate(ST_GeometryFromText('POINT(1 2)'), ST_Buffer(ST_GeometryFromText('POINT(1 2)'),2), '0FFFFF212');\n" +"SELECT ST_Relate(ST_GeometryFromText('POINT(1 2)'), " +"ST_Buffer(ST_GeometryFromText('POINT(1 2)'),2), '0FFFFF212');\n" "st_relate\n" "-----------\n" "t\n" "\n" -"SELECT ST_Relate(ST_GeometryFromText('POINT(1 2)'), ST_Buffer(ST_GeometryFromText('POINT(1 2)'),2), '*FF*FF212');\n" +"SELECT ST_Relate(ST_GeometryFromText('POINT(1 2)'), " +"ST_Buffer(ST_GeometryFromText('POINT(1 2)'),2), '*FF*FF212');\n" "st_relate\n" "-----------\n" "t" @@ -4523,8 +4686,8 @@ msgstr "" #: reference_measure.xml:2916 #, no-c-format msgid "" -", , , , " +", , , , " msgstr "" #. Tag: refname @@ -4546,9 +4709,9 @@ msgstr "" #, no-c-format msgid "" "boolean ST_RelateMatch " -"text " -"intersectionMatrix text " -" intersectionMatrixPattern" +"text intersectionMatrix text intersectionMatrixPattern" msgstr "" #. Tag: para @@ -4574,7 +4737,8 @@ msgid "" "-- result --\n" "t\n" "--example of common intersection matrix patterns and example matrices\n" -"-- comparing relationships of involving one invalid geometry and ( a line and polygon that intersect at interior and boundary)\n" +"-- comparing relationships of involving one invalid geometry and ( a line " +"and polygon that intersect at interior and boundary)\n" "SELECT mat.name, pat.name, ST_RelateMatch(mat.val, pat.val) As satisfied\n" " FROM \n" " ( VALUES ('Equality', 'T1FF1FFF1'),\n" @@ -4619,12 +4783,12 @@ msgstr "" #: reference_measure.xml:2983 #, no-c-format msgid "" -"Returns the 2-dimensional shortest line between two geometries. The function" -" will only return the first shortest line if more than one, that the " -"function finds. If g1 and g2 intersects in just one point the function will " -"return a line with both start and end in that intersection-point. If g1 and " -"g2 are intersecting with more than one point the function will return a line" -" with start and end in the same point but it can be any of the intersecting " +"Returns the 2-dimensional shortest line between two geometries. The function " +"will only return the first shortest line if more than one, that the function " +"finds. If g1 and g2 intersects in just one point the function will return a " +"line with both start and end in that intersection-point. If g1 and g2 are " +"intersecting with more than one point the function will return a line with " +"start and end in the same point but it can be any of the intersecting " "points. The line returned will always start in g1 and end in g2. The length " "of the line this function returns will always be the same as ST_Distance " "returns for g1 and g2." @@ -4663,20 +4827,22 @@ msgstr "" msgid "" "SELECT ST_AsText(\n" " ST_ShortestLine(\n" -" ST_GeomFromText('POLYGON((175 150, 20 40, 50 60, 125 100, 175 150))'),\n" +" ST_GeomFromText('POLYGON((175 150, 20 40, 50 60, 125 " +"100, 175 150))'),\n" " ST_Buffer(ST_GeomFromText('POINT(110 170)'), 20)\n" " ) \n" " ) As slinewkt;\n" " \n" -" LINESTRING(140.752120669087 125.695053378061,121.111404660392 153.370607753949)" +" LINESTRING(140.752120669087 125.695053378061,121.111404660392 " +"153.370607753949)" msgstr "" #. Tag: para #: reference_measure.xml:3033 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -4689,8 +4855,8 @@ msgstr "" #: reference_measure.xml:3041 #, no-c-format msgid "" -"Returns TRUE if the geometries have at least one point in" -" common, but their interiors do not intersect." +"Returns TRUE if the geometries have at least one point in " +"common, but their interiors do not intersect." msgstr "" #. Tag: funcprototype @@ -4709,8 +4875,8 @@ msgid "" "Returns TRUE if the only points in common between " "g1 and g2 lie in the union of " "the boundaries of g1 and g2. " -"The ST_Touches relation applies to all Area/Area, " -"Line/Line, Line/Area, Point/Area and Point/Line pairs of relationships, but " +"The ST_Touches relation applies to all Area/Area, Line/" +"Line, Line/Area, Point/Area and Point/Line pairs of relationships, but " "not to the Point/Point pair." msgstr "" @@ -4748,9 +4914,9 @@ msgstr "" #: reference_measure.xml:3100 #, no-c-format msgid "" -"This function call will automatically include a bounding box comparison that" -" will make use of any indexes that are available on the geometries. To avoid" -" using an index, use _ST_Touches instead." +"This function call will automatically include a bounding box comparison that " +"will make use of any indexes that are available on the geometries. To avoid " +"using an index, use _ST_Touches instead." msgstr "" #. Tag: para @@ -4763,21 +4929,23 @@ msgstr "" #: reference_measure.xml:3112 #, no-c-format msgid "" -"The ST_Touches predicate returns " -"TRUE in all the following illustrations." +"The ST_Touches predicate returns TRUE in all the following illustrations." msgstr "" #. Tag: programlisting #: reference_measure.xml:3182 #, no-c-format msgid "" -"SELECT ST_Touches('LINESTRING(0 0, 1 1, 0 2)'::geometry, 'POINT(1 1)'::geometry);\n" +"SELECT ST_Touches('LINESTRING(0 0, 1 1, 0 2)'::geometry, 'POINT(1 1)'::" +"geometry);\n" " st_touches\n" "------------\n" " f\n" "(1 row)\n" "\n" -"SELECT ST_Touches('LINESTRING(0 0, 1 1, 0 2)'::geometry, 'POINT(0 2)'::geometry);\n" +"SELECT ST_Touches('LINESTRING(0 0, 1 1, 0 2)'::geometry, 'POINT(0 2)'::" +"geometry);\n" " st_touches\n" "------------\n" " t\n" @@ -4820,9 +4988,9 @@ msgstr "" #: reference_measure.xml:3225 #, no-c-format msgid "" -"This function call will automatically include a bounding box comparison that" -" will make use of any indexes that are available on the geometries. To avoid" -" index use, use the function _ST_Within." +"This function call will automatically include a bounding box comparison that " +"will make use of any indexes that are available on the geometries. To avoid " +"index use, use the function _ST_Within." msgstr "" #. Tag: para @@ -4853,8 +5021,10 @@ msgid "" "SELECT ST_Buffer(ST_GeomFromText('POINT(50 50)'), 20) As smallc,\n" " ST_Buffer(ST_GeomFromText('POINT(50 50)'), 40) As bigc) As foo;\n" "--Result\n" -" smallinsmall | smallinbig | biginsmall | unioninbig | biginunion | bigisunion\n" -"--------------+------------+------------+------------+------------+------------\n" +" smallinsmall | smallinbig | biginsmall | unioninbig | biginunion | " +"bigisunion\n" +"--------------+------------+------------+------------+------------" +"+------------\n" " t | t | f | t | t | t\n" "(1 row)" msgstr "" diff --git a/doc/po/de_DE/reference_misc.xml.po b/doc/po/de_DE/reference_misc.xml.po index b4395a9c8..526934fac 100644 --- a/doc/po/de_DE/reference_misc.xml.po +++ b/doc/po/de_DE/reference_misc.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:24+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -38,8 +39,8 @@ msgstr "" #, no-c-format msgid "" "geometry[] ST_Accum " -"geometry set " -"geomfield" +"geometry set geomfield" msgstr "" #. Tag: title @@ -109,14 +110,18 @@ msgstr "Beispiele" #: 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" +"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 (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" "\n" " {0101000080000000000000144000000000000024400000000000001040:\n" " 0101000080000000000\n" @@ -148,24 +153,24 @@ msgstr "" #: reference_misc.xml:51 #, no-c-format msgid "" -"Returns a BOX2D representing the maximum extents of the " -"geometry." +"Returns a BOX2D representing the maximum extents of the geometry." +"" msgstr "" #. Tag: funcprototype #: reference_misc.xml:56 #, no-c-format msgid "" -"box2d Box2D geometry" -" geomA" +"box2d Box2D geometry " +" geomA" msgstr "" #. Tag: para #: reference_misc.xml:66 #, no-c-format msgid "" -"Returns a BOX2D representing the maximum extents of the " -"geometry." +"Returns a BOX2D representing the maximum extents of the geometry." msgstr "" #. Tag: programlisting @@ -177,7 +182,8 @@ msgid "" " ---------\n" " BOX(1 2,5 6)\n" "\n" -" SELECT Box2D(ST_GeomFromText('CIRCULARSTRING(220268 150415,220227 150505,220227 150406)'));\n" +" SELECT Box2D(ST_GeomFromText('CIRCULARSTRING(220268 150415,220227 " +"150505,220227 150406)'));\n" " box2d\n" " --------\n" " BOX(220186.984375 150406,220288.25 150506.140625)" @@ -199,24 +205,24 @@ msgstr "" #: reference_misc.xml:93 #, no-c-format msgid "" -"Returns a BOX3D representing the maximum extents of the " -"geometry." +"Returns a BOX3D representing the maximum extents of the geometry." +"" msgstr "" #. Tag: funcprototype #: reference_misc.xml:98 #, no-c-format msgid "" -"box3d Box3D geometry" -" geomA" +"box3d Box3D geometry " +" geomA" msgstr "" #. Tag: para #: reference_misc.xml:108 #, no-c-format msgid "" -"Returns a BOX3D representing the maximum extents of the " -"geometry." +"Returns a BOX3D representing the maximum extents of the geometry." msgstr "" #. Tag: programlisting @@ -228,7 +234,8 @@ msgid "" " ---------\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" +" 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)" @@ -251,23 +258,22 @@ msgstr "" #, no-c-format msgid "" "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." +"estimated is taken from the geometry column's statistics. The current schema " +"will be used if not specified." msgstr "" #. Tag: funcsynopsis #: reference_misc.xml:141 #, no-c-format msgid "" -" box2d " -"ST_EstimatedExtent text " -" schema_name text " -" table_name text " -" geocolumn_name " -" box2d " -"ST_EstimatedExtent text " -" table_name text " -" geocolumn_name " +" box2d ST_EstimatedExtent text schema_name text table_name text geocolumn_name box2d " +"ST_EstimatedExtent text table_name text geocolumn_name " msgstr "" #. Tag: para @@ -275,8 +281,8 @@ msgstr "" #, no-c-format msgid "" "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." +"estimated is taken from the geometry column's statistics. The current schema " +"will be used if not specified." msgstr "" #. Tag: para @@ -338,8 +344,8 @@ msgstr "" #: 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" +"Returns bounding box expanded in all directions from the bounding box of the " +"input geometry. Uses double-precision" msgstr "" #. Tag: funcsynopsis @@ -348,16 +354,15 @@ msgstr "" msgid "" " geometry ST_Expand " "geometry g1 " -"float " -"units_to_expand " -" box2d ST_Expand " -"box2d g1 " -"float " +"float units_to_expand box2d " +"ST_Expand box2d " +"g1 float " "units_to_expand " " box3d ST_Expand " "box3d g1 " -"float " -"units_to_expand " +"float units_to_expand " msgstr "" #. Tag: para @@ -375,25 +380,25 @@ msgstr "" #, 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." +"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." +"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" +"Units are in the units of the spatial reference system in use denoted by the " +"SRID" msgstr "" #. Tag: para @@ -401,9 +406,9 @@ msgstr "" #, no-c-format msgid "" "Pre 1.3, ST_Expand was used in conjunction with distance to do indexable " -"queries. Something of the form the_geom && ST_Expand('POINT(10" -" 20)', 10) AND ST_Distance(the_geom, 'POINT(10 20)') < 10 Post " -"1.2, this was replaced with the easier ST_DWithin construct." +"queries. Something of the form the_geom && ST_Expand('POINT(10 " +"20)', 10) AND ST_Distance(the_geom, 'POINT(10 20)') < 10 Post 1.2, " +"this was replaced with the easier ST_DWithin construct." msgstr "" #. Tag: para @@ -418,8 +423,8 @@ msgstr "" #: reference_misc.xml:259 #, no-c-format msgid "" -"Examples below use US National Atlas Equal Area (SRID=2163) which is a meter" -" projection" +"Examples below use US National Atlas Equal Area (SRID=2163) which is a meter " +"projection" msgstr "" #. Tag: programlisting @@ -428,22 +433,26 @@ msgstr "" msgid "" "\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" +"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" +"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" +" 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))" +" SRID=2163;POLYGON((2312970 110666,2312970 110686,2312990 110686,2312990 " +"110666,2312970 110666))" msgstr "" #. Tag: para @@ -474,8 +483,8 @@ msgstr "" #, no-c-format msgid "" "box2d ST_Extent " -"geometry set " -"geomfield" +"geometry set geomfield" msgstr "" #. Tag: para @@ -516,8 +525,8 @@ msgstr "" #: reference_misc.xml:298 #, 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." +"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 @@ -547,7 +556,8 @@ msgid "" "FROM sometable\n" "GROUP BY category ORDER BY category;\n" "\n" -" bextent | name\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" @@ -559,7 +569,8 @@ msgid "" "\n" " bextent\n" "--------------------------------------------------------------------------------\n" -" SRID=2249;POLYGON((739651.875 2908247.25,739651.875 2970042.75,794875.8125 2970042.75,\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 "" @@ -590,8 +601,8 @@ msgstr "" #, no-c-format msgid "" "box3d ST_3DExtent " -"geometry set " -"geomfield" +"geometry set geomfield" msgstr "" #. Tag: para @@ -634,7 +645,9 @@ msgid "" "\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 (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" @@ -670,10 +683,9 @@ msgstr "" #, no-c-format msgid "" "integer Find_SRID " -"varchar " -"a_schema_name varchar " -" a_table_name " -"varchar " +"varchar a_schema_name varchar a_table_name varchar " "a_geomfield_name" msgstr "" @@ -683,8 +695,8 @@ msgstr "" msgid "" "The syntax is find_srid(<db/schema>, <table>, <column>) " "and the function returns the integer SRID of the specified column by " -"searching through the GEOMETRY_COLUMNS table. If the geometry column has not" -" been properly added with the AddGeometryColumns() function, this function " +"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 "" @@ -708,8 +720,8 @@ msgstr "" #: reference_misc.xml:421 #, no-c-format msgid "" -"Returns the amount of space (in bytes) the geometry " -"takes." +"Returns the amount of space (in bytes) the geometry takes." msgstr "" #. Tag: funcprototype @@ -723,8 +735,7 @@ msgstr "" #. Tag: para #: reference_misc.xml:436 #, no-c-format -msgid "" -"Returns the amount of space (in bytes) the geometry takes." +msgid "Returns the amount of space (in bytes) the geometry takes." msgstr "" #. Tag: para @@ -740,8 +751,8 @@ msgstr "" #, no-c-format msgid "" "pg_relation_size which gives the byte size of a table may return byte size " -"lower than ST_MemSize. This is because pg_relation_size does not add toasted" -" table contribution and large geometries are stored in TOAST tables." +"lower than ST_MemSize. This is because pg_relation_size does not add toasted " +"table contribution and large geometries are stored in TOAST tables." msgstr "" #. Tag: para @@ -775,8 +786,10 @@ msgstr "" msgid "" "--Return how much byte space Boston takes up in our Mass data set\n" "SELECT pg_size_pretty(SUM(ST_MemSize(the_geom))) as totgeomsum,\n" -"pg_size_pretty(SUM(CASE WHEN town = 'BOSTON' THEN ST_MemSize(the_geom) ELSE 0 END)) As bossum,\n" -"CAST(SUM(CASE WHEN town = 'BOSTON' THEN ST_MemSize(the_geom) ELSE 0 END)*1.00 /\n" +"pg_size_pretty(SUM(CASE WHEN town = 'BOSTON' THEN ST_MemSize(the_geom) ELSE " +"0 END)) As bossum,\n" +"CAST(SUM(CASE WHEN town = 'BOSTON' THEN ST_MemSize(the_geom) ELSE 0 " +"END)*1.00 /\n" " SUM(ST_MemSize(the_geom))*100 As numeric(10,2)) As perbos\n" "FROM towns;\n" "\n" @@ -785,14 +798,17 @@ msgid "" "1522 kB 30 kB 1.99\n" "\n" "\n" -"SELECT ST_MemSize(ST_GeomFromText('CIRCULARSTRING(220268 150415,220227 150505,220227 150406)'));\n" +"SELECT ST_MemSize(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_MemSize(the_geom)) As geomsize,\n" -"sum(ST_MemSize(the_geom))*1.00/pg_total_relation_size('public.neighborhoods')*100 As pergeom\n" +"SELECT pg_total_relation_size('public.neighborhoods') As fulltable_size, " +"sum(ST_MemSize(the_geom)) As geomsize,\n" +"sum(ST_MemSize(the_geom))*1.00/pg_total_relation_size('public." +"neighborhoods')*100 As pergeom\n" "FROM neighborhoods;\n" "fulltable_size geomsize pergeom\n" "------------------------------------------------\n" @@ -827,10 +843,10 @@ msgstr "" #: reference_misc.xml:488 #, no-c-format msgid "" -"The syntax for this functions is " -"ST_PointInsideCircle(<geometry>,<circle_center_x>,<circle_center_y>,<radius>)." -" Returns the true if the geometry is a point and is inside the circle. " -"Returns false otherwise." +"The syntax for this functions is ST_PointInsideCircle(<geometry>,<" +"circle_center_x>,<circle_center_y>,<radius>). Returns the " +"true if the geometry is a point and is inside the circle. Returns false " +"otherwise." msgstr "" #. Tag: para diff --git a/doc/po/de_DE/reference_operator.xml.po b/doc/po/de_DE/reference_operator.xml.po index deff54bd0..ab9e8ea7f 100644 --- a/doc/po/de_DE/reference_operator.xml.po +++ b/doc/po/de_DE/reference_operator.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:24+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -41,11 +42,11 @@ msgstr "" msgid "" " boolean && " " geometry A " -" geometry B " -" boolean " -"&& geography " -" A geography " -"B " +" geometry B boolean && geography A geography B " msgstr "" #. Tag: title @@ -130,7 +131,8 @@ msgstr "Beispiele" #: reference_operator.xml:66 #, no-c-format msgid "" -"SELECT tbl1.column1, tbl2.column1, tbl1.column2 && tbl2.column2 AS overlaps\n" +"SELECT tbl1.column1, tbl2.column1, tbl1.column2 && tbl2.column2 AS " +"overlaps\n" "FROM ( VALUES\n" " (1, 'LINESTRING(0 0, 3 3)'::geometry),\n" " (2, 'LINESTRING(0 1, 0 5)'::geometry)) AS tbl1,\n" @@ -163,10 +165,9 @@ msgstr "Siehe auch" #: reference_operator.xml:73 #, no-c-format msgid "" -", , , , ," -" " +", , , , , " msgstr "" #. Tag: refname @@ -196,9 +197,9 @@ msgstr "" #: reference_operator.xml:113 #, no-c-format msgid "" -"The &&& operator returns " -"TRUE if the n-D bounding box of geometry A intersects the" -" n-D bounding box of geometry B." +"The &&& operator returns TRUE if the n-D bounding box of geometry A intersects the n-D bounding " +"box of geometry B." msgstr "" #. Tag: para @@ -229,8 +230,10 @@ msgstr "" #: reference_operator.xml:128 #, no-c-format msgid "" -"SELECT tbl1.column1, tbl2.column1, tbl1.column2 &&& tbl2.column2 AS overlaps_3d, \n" -" tbl1.column2 && tbl2.column2 AS overlaps_2d\n" +"SELECT tbl1.column1, tbl2.column1, tbl1.column2 &&& tbl2.column2 " +"AS overlaps_3d, \n" +" tbl1.column2 && tbl2.column2 AS " +"overlaps_2d\n" "FROM ( VALUES\n" " (1, 'LINESTRING Z(0 0 1, 3 3 2)'::geometry),\n" " (2, 'LINESTRING Z(1 2 0, 0 5 -1)'::geometry)) AS tbl1,\n" @@ -253,8 +256,10 @@ msgstr "" #: reference_operator.xml:134 #, no-c-format msgid "" -"SELECT tbl1.column1, tbl2.column1, tbl1.column2 &&& tbl2.column2 AS overlaps_3zm, \n" -" tbl1.column2 && tbl2.column2 AS overlaps_2d\n" +"SELECT tbl1.column1, tbl2.column1, tbl1.column2 &&& tbl2.column2 " +"AS overlaps_3zm, \n" +" tbl1.column2 && tbl2.column2 AS " +"overlaps_2d\n" "FROM ( VALUES\n" " (1, 'LINESTRING M(0 0 1, 3 3 2)'::geometry),\n" " (2, 'LINESTRING M(1 2 0, 0 5 -1)'::geometry)) AS tbl1,\n" @@ -294,8 +299,8 @@ msgstr "" #: reference_operator.xml:178 #, no-c-format msgid "" -"The &< operator returns TRUE if" -" the bounding box of geometry A overlaps or is to the left of the bounding " +"The &< operator returns TRUE if " +"the bounding box of geometry A overlaps or is to the left of the bounding " "box of geometry B, or more accurately, overlaps or is NOT to the right of " "the bounding box of geometry B." msgstr "" @@ -304,7 +309,8 @@ msgstr "" #: reference_operator.xml:189 #, no-c-format msgid "" -"SELECT tbl1.column1, tbl2.column1, tbl1.column2 &< tbl2.column2 AS overleft\n" +"SELECT tbl1.column1, tbl2.column1, tbl1.column2 &< tbl2.column2 AS " +"overleft\n" "FROM\n" " ( VALUES\n" " (1, 'LINESTRING(1 2, 4 6)'::geometry)) AS tbl1,\n" @@ -325,9 +331,8 @@ msgstr "" #: reference_operator.xml:195 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -340,8 +345,7 @@ msgstr "" #: reference_operator.xml:207 #, no-c-format msgid "" -"Returns TRUE if A's bounding box overlaps or is below " -"B's." +"Returns TRUE if A's bounding box overlaps or is below B's." msgstr "" #. Tag: funcprototype @@ -359,15 +363,16 @@ msgstr "" msgid "" "The &<| operator returns TRUE " "if the bounding box of geometry A overlaps or is below of the bounding box " -"of geometry B, or more accurately, overlaps or is NOT above the bounding box" -" of geometry B." +"of geometry B, or more accurately, overlaps or is NOT above the bounding box " +"of geometry B." msgstr "" #. Tag: programlisting #: reference_operator.xml:250 #, no-c-format msgid "" -"SELECT tbl1.column1, tbl2.column1, tbl1.column2 &<| tbl2.column2 AS overbelow\n" +"SELECT tbl1.column1, tbl2.column1, tbl1.column2 &<| tbl2.column2 AS " +"overbelow\n" "FROM\n" " ( VALUES\n" " (1, 'LINESTRING(6 0, 6 4)'::geometry)) AS tbl1,\n" @@ -388,9 +393,8 @@ msgstr "" #: reference_operator.xml:256 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -420,17 +424,18 @@ msgstr "" #: reference_operator.xml:297 #, no-c-format msgid "" -"The &> operator returns TRUE if" -" the bounding box of geometry A overlaps or is to the right of the bounding " -"box of geometry B, or more accurately, overlaps or is NOT to the left of the" -" bounding box of geometry B." +"The &> operator returns TRUE if " +"the bounding box of geometry A overlaps or is to the right of the bounding " +"box of geometry B, or more accurately, overlaps or is NOT to the left of the " +"bounding box of geometry B." msgstr "" #. Tag: programlisting #: reference_operator.xml:308 #, no-c-format msgid "" -"SELECT tbl1.column1, tbl2.column1, tbl1.column2 &> tbl2.column2 AS overright\n" +"SELECT tbl1.column1, tbl2.column1, tbl1.column2 &> tbl2.column2 AS " +"overright\n" "FROM\n" " ( VALUES\n" " (1, 'LINESTRING(1 2, 4 6)'::geometry)) AS tbl1,\n" @@ -451,9 +456,8 @@ msgstr "" #: reference_operator.xml:314 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -492,7 +496,8 @@ msgstr "" #: reference_operator.xml:365 #, no-c-format msgid "" -"SELECT tbl1.column1, tbl2.column1, tbl1.column2 << tbl2.column2 AS left\n" +"SELECT tbl1.column1, tbl2.column1, tbl1.column2 << tbl2.column2 AS " +"left\n" "FROM\n" " ( VALUES\n" " (1, 'LINESTRING (1 2, 1 5)'::geometry)) AS tbl1,\n" @@ -512,7 +517,9 @@ msgstr "" #. Tag: para #: reference_operator.xml:371 reference_operator.xml:564 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -541,8 +548,8 @@ msgstr "" #: reference_operator.xml:408 #, no-c-format msgid "" -"The <<| operator returns TRUE if" -" the bounding box of geometry A is strictly below the bounding box of " +"The <<| operator returns TRUE if " +"the bounding box of geometry A is strictly below the bounding box of " "geometry B." msgstr "" @@ -550,7 +557,8 @@ msgstr "" #: reference_operator.xml:418 #, no-c-format msgid "" -"SELECT tbl1.column1, tbl2.column1, tbl1.column2 <<| tbl2.column2 AS below\n" +"SELECT tbl1.column1, tbl2.column1, tbl1.column2 <<| tbl2.column2 AS " +"below\n" "FROM\n" " ( VALUES\n" " (1, 'LINESTRING (0 0, 4 3)'::geometry)) AS tbl1,\n" @@ -570,7 +578,9 @@ msgstr "" #. Tag: para #: reference_operator.xml:424 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -583,8 +593,8 @@ msgstr "" #: reference_operator.xml:432 #, no-c-format msgid "" -"Returns TRUE if A's bounding box is the same as B's. Uses" -" double precision bounding box." +"Returns TRUE if A's bounding box is the same as B's. Uses " +"double precision bounding box." msgstr "" #. Tag: funcsynopsis @@ -593,19 +603,19 @@ msgstr "" msgid "" " boolean = " " geometry A " -" geometry B " -" boolean " -"= geography " -"A geography " -"B " +" geometry B boolean = geography A geography B " msgstr "" #. Tag: para #: reference_operator.xml:477 #, no-c-format msgid "" -"The = operator returns TRUE if the" -" bounding box of geometry/geography A is the same as the bounding box of " +"The = operator returns TRUE if the " +"bounding box of geometry/geography A is the same as the bounding box of " "geometry/geography B. PostgreSQL uses the =, <, and > operators " "defined for geometries to perform internal orderings and comparison of " "geometries (ie. in a GROUP BY or ORDER BY clause)." @@ -615,10 +625,10 @@ msgstr "" #: reference_operator.xml:482 #, no-c-format msgid "" -"This is cause for a lot of confusion. When you compare geometryA = geometryB" -" it will return true even when the geometries are clearly different IF their" -" bounding boxes are the same. To check for true equality use or " +"This is cause for a lot of confusion. When you compare geometryA = geometryB " +"it will return true even when the geometries are clearly different IF their " +"bounding boxes are the same. To check for true equality use or " msgstr "" #. Tag: para @@ -635,8 +645,8 @@ msgstr "" msgid "" "Changed: 2.0.0 , the bounding box of geometries was changed to use double " "precision instead of float4 precision of prior. The side effect of this is " -"that in particular points in prior versions that were a little different may" -" have returned true in prior versions and false in 2.0+ since their float4 " +"that in particular points in prior versions that were a little different may " +"have returned true in prior versions and false in 2.0+ since their float4 " "boxes would be the same but there float8 (double precision), would be " "different." msgstr "" @@ -645,7 +655,8 @@ msgstr "" #: reference_operator.xml:504 #, no-c-format msgid "" -"SELECT 'LINESTRING(0 0, 0 1, 1 0)'::geometry = 'LINESTRING(1 1, 0 0)'::geometry;\n" +"SELECT 'LINESTRING(0 0, 0 1, 1 0)'::geometry = 'LINESTRING(1 1, 0 0)'::" +"geometry;\n" " ?column?\n" "----------\n" " t\n" @@ -696,8 +707,8 @@ msgstr "" #: reference_operator.xml:519 #, no-c-format msgid "" -"Returns TRUE if A's bounding box is strictly to the right" -" of B's." +"Returns TRUE if A's bounding box is strictly to the right " +"of B's." msgstr "" #. Tag: funcprototype @@ -722,7 +733,8 @@ msgstr "" #: reference_operator.xml:558 #, no-c-format msgid "" -"SELECT tbl1.column1, tbl2.column1, tbl1.column2 >> tbl2.column2 AS right\n" +"SELECT tbl1.column1, tbl2.column1, tbl1.column2 >> tbl2.column2 AS " +"right\n" "FROM\n" " ( VALUES\n" " (1, 'LINESTRING (2 3, 5 6)'::geometry)) AS tbl1,\n" @@ -757,8 +769,8 @@ msgstr "" #, no-c-format msgid "" "boolean @ geometry " -" A geometry " -" B " +" A geometry B " msgstr "" #. Tag: para @@ -807,8 +819,7 @@ msgstr "" #: reference_operator.xml:627 #, no-c-format msgid "" -"Returns TRUE if A's bounding box overlaps or is above " -"B's." +"Returns TRUE if A's bounding box overlaps or is above B's." msgstr "" #. Tag: funcprototype @@ -826,15 +837,16 @@ msgstr "" msgid "" "The |&> operator returns TRUE " "if the bounding box of geometry A overlaps or is above the bounding box of " -"geometry B, or more accurately, overlaps or is NOT below the bounding box of" -" geometry B." +"geometry B, or more accurately, overlaps or is NOT below the bounding box of " +"geometry B." msgstr "" #. Tag: programlisting #: reference_operator.xml:667 #, no-c-format msgid "" -"SELECT tbl1.column1, tbl2.column1, tbl1.column2 |&> tbl2.column2 AS overabove\n" +"SELECT tbl1.column1, tbl2.column1, tbl1.column2 |&> tbl2.column2 AS " +"overabove\n" "FROM\n" " ( VALUES\n" " (1, 'LINESTRING(6 0, 6 4)'::geometry)) AS tbl1,\n" @@ -855,9 +867,8 @@ msgstr "" #: reference_operator.xml:673 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -886,16 +897,17 @@ msgstr "" #: reference_operator.xml:714 #, no-c-format msgid "" -"The |>> operator returns TRUE if" -" the bounding box of geometry A is strictly to the right of the bounding box" -" of geometry B." +"The |>> operator returns TRUE if " +"the bounding box of geometry A is strictly to the right of the bounding box " +"of geometry B." msgstr "" #. Tag: programlisting #: reference_operator.xml:724 #, no-c-format msgid "" -"SELECT tbl1.column1, tbl2.column1, tbl1.column2 |>> tbl2.column2 AS above\n" +"SELECT tbl1.column1, tbl2.column1, tbl1.column2 |>> tbl2.column2 AS " +"above\n" "FROM\n" " ( VALUES\n" " (1, 'LINESTRING (1 4, 1 7)'::geometry)) AS tbl1,\n" @@ -915,7 +927,9 @@ msgstr "" #. Tag: para #: reference_operator.xml:730 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -935,8 +949,8 @@ msgstr "" #, no-c-format msgid "" "boolean ~ geometry " -" A geometry " -" B " +" A geometry B " msgstr "" #. Tag: para @@ -978,17 +992,16 @@ msgstr "" #. Tag: refpurpose #: reference_operator.xml:791 #, no-c-format -msgid "" -"Returns TRUE if A's bounding box is the same as B's." +msgid "Returns TRUE if A's bounding box is the same as B's." msgstr "" #. Tag: funcprototype #: reference_operator.xml:796 #, no-c-format msgid "" -"boolean ~= geometry" -" A geometry " -" B " +"boolean ~= geometry " +" A geometry B " msgstr "" #. Tag: para @@ -1011,20 +1024,21 @@ msgstr "" #, no-c-format msgid "" "This operator has changed behavior in PostGIS 1.5 from testing for actual " -"geometric equality to only checking for bounding box equality. To complicate" -" things it also depends on if you have done a hard or soft upgrade which " -"behavior your database has. To find out which behavior your database has you" -" can run the query below. To check for true equality use or and to " -"check for bounding box equality ; operator" -" is a safer option." +"geometric equality to only checking for bounding box equality. To complicate " +"things it also depends on if you have done a hard or soft upgrade which " +"behavior your database has. To find out which behavior your database has you " +"can run the query below. To check for true equality use or and to check for " +"bounding box equality ; operator is a " +"safer option." msgstr "" #. Tag: programlisting #: reference_operator.xml:844 #, no-c-format msgid "" -"select 'LINESTRING(0 0, 1 1)'::geometry ~= 'LINESTRING(0 1, 1 0)'::geometry as equality;\n" +"select 'LINESTRING(0 0, 1 1)'::geometry ~= 'LINESTRING(0 1, 1 0)'::geometry " +"as equality;\n" " equality |\n" "-----------------+\n" " t |" @@ -1041,7 +1055,8 @@ msgstr "" #. Tag: para #: reference_operator.xml:849 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -1060,14 +1075,13 @@ msgstr "" #: reference_operator.xml:863 #, no-c-format msgid "" -" double precision " -"<-> geometry " -"A geometry " -"B " -"double precision <-> " -" geography A " -" geography B " -"" +" double precision <-> geometry A geometry B double precision " +"<-> geography " +"A geography " +"B " msgstr "" #. Tag: para @@ -1087,8 +1101,8 @@ msgstr "" #, no-c-format msgid "" "This operand will make use of 2D GiST indexes that may be available on the " -"geometries. It is different from other operators that use spatial indexes in" -" that the spatial index is only used when the operator is in the ORDER BY " +"geometries. It is different from other operators that use spatial indexes in " +"that the spatial index is only used when the operator is in the ORDER BY " "clause." msgstr "" @@ -1097,17 +1111,17 @@ msgstr "" #, no-c-format msgid "" "Index only kicks in if one of the geometries is a constant (not in a " -"subquery/cte). e.g. 'SRID=3005;POINT(1011102 450541)'::geometry instead of " -"a.geom" +"subquery/cte). e.g. 'SRID=3005;POINT(1011102 450541)'::geometry instead of a." +"geom" msgstr "" #. Tag: para #: reference_operator.xml:912 #, no-c-format msgid "" -"Refer to OpenGeo workshop: Nearest-Neighbour Searching for " -"real live example." +"Refer to OpenGeo workshop: Nearest-Neighbour Searching for real live " +"example." msgstr "" #. Tag: para @@ -1115,26 +1129,26 @@ msgstr "" #, no-c-format msgid "" "Enhanced: 2.2.0 -- True KNN (\"K nearest neighbor\") behavior for geometry " -"and geography for PostgreSQL 9.5+. Note for geography KNN is based on sphere" -" rather than spheroid. For PostgreSQL 9.4 and below, geography support is " -"new but only supports centroid box." +"and geography for PostgreSQL 9.5+. Note for geography KNN is based on sphere " +"rather than spheroid. For PostgreSQL 9.4 and below, geography support is new " +"but only supports centroid box." msgstr "" #. Tag: para #: reference_operator.xml:915 #, no-c-format msgid "" -"Changed: 2.2.0 -- For PostgreSQL 9.5 users, old Hybrid syntax may be slower," -" so you'll want to get rid of that hack if you are running your code only on" -" PostGIS 2.2+ 9.5+. See examples below." +"Changed: 2.2.0 -- For PostgreSQL 9.5 users, old Hybrid syntax may be slower, " +"so you'll want to get rid of that hack if you are running your code only on " +"PostGIS 2.2+ 9.5+. See examples below." msgstr "" #. Tag: para #: reference_operator.xml:916 #, no-c-format msgid "" -"Availability: 2.0.0 -- Weak KNN provides nearest neighbors based on geometry" -" centroid distances instead of true distances. Exact results for points, " +"Availability: 2.0.0 -- Weak KNN provides nearest neighbors based on geometry " +"centroid distances instead of true distances. Exact results for points, " "inexact for all other types. Available for PostgreSQL 9.1+" msgstr "" @@ -1142,7 +1156,8 @@ msgstr "" #: reference_operator.xml:923 #, no-c-format msgid "" -"\n" "\n" @@ -1171,7 +1186,8 @@ msgstr "" #: reference_operator.xml:927 #, no-c-format msgid "" -" 'SRID=3005;POINT(1011102 450541)'::geometry limit 10;]]>\n" "\n" @@ -1203,8 +1219,8 @@ msgstr "" #, no-c-format msgid "" "For users running with PostgreSQL < 9.5, use a hybrid query to find the " -"true nearest neighbors. First a CTE query using the index-assisted KNN, then" -" an exact query to get correct ordering:" +"true nearest neighbors. First a CTE query using the index-assisted KNN, then " +"an exact query to get correct ordering:" msgstr "" #. Tag: programlisting @@ -1212,7 +1228,8 @@ msgstr "" #, no-c-format msgid "" " 'SRID=3005;POINT(1011102 450541)'::geometry LIMIT 100) \n" " SELECT * \n" @@ -1237,7 +1254,8 @@ msgstr "" #. Tag: para #: reference_operator.xml:939 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -1269,9 +1287,9 @@ msgstr "" msgid "" "The |=| operator returns the 3D distance between two " "trajectories (See ). This is the " -"same as but as an operator it can be used" -" for doing nearest neightbor searches using an N-dimensional index (requires" -" PostgreSQL 9.5.0 or higher)." +"same as but as an operator it can be used " +"for doing nearest neightbor searches using an N-dimensional index (requires " +"PostgreSQL 9.5.0 or higher)." msgstr "" #. Tag: para @@ -1279,8 +1297,8 @@ msgstr "" #, no-c-format msgid "" "This operand will make use of ND GiST indexes that may be available on the " -"geometries. It is different from other operators that use spatial indexes in" -" that the spatial index is only used when the operator is in the ORDER BY " +"geometries. It is different from other operators that use spatial indexes in " +"that the spatial index is only used when the operator is in the ORDER BY " "clause." msgstr "" @@ -1296,8 +1314,7 @@ msgstr "" #. Tag: para #: reference_operator.xml:987 #, no-c-format -msgid "" -"Availability: 2.2.0. Index-supported only available for PostgreSQL 9.5+" +msgid "Availability: 2.2.0. Index-supported only available for PostgreSQL 9.5+" msgstr "" #. Tag: programlisting @@ -1305,7 +1322,8 @@ msgstr "" #, no-c-format msgid "" "-- Save a literal query trajectory in a psql variable...\n" -"\\set qt 'ST_AddMeasure(ST_MakeLine(ST_MakePointM(-350,300,0),ST_MakePointM(-410,490,0)),10,20)'\n" +"\\set qt 'ST_AddMeasure(ST_MakeLine(ST_MakePointM(-350,300,0)," +"ST_MakePointM(-410,490,0)),10,20)'\n" "-- Run the query !\n" "SELECT track_id, dist FROM (\n" " SELECT track_id, ST_DistanceCPA(tr,:qt) dist\n" @@ -1327,8 +1345,8 @@ msgstr "" #: reference_operator.xml:997 #, no-c-format msgid "" -", , " +", , " msgstr "" #. Tag: refname @@ -1358,8 +1376,8 @@ msgstr "" msgid "" "The <#> operator returns distance between two " "floating point bounding boxes, possibly reading them from a spatial index " -"(PostgreSQL 9.1+ required). Useful for doing nearest neighbor approximate distance ordering." +"(PostgreSQL 9.1+ required). Useful for doing nearest neighbor approximate distance ordering." msgstr "" #. Tag: para @@ -1367,8 +1385,8 @@ msgstr "" #, no-c-format msgid "" "This operand will make use of any indexes that may be available on the " -"geometries. It is different from other operators that use spatial indexes in" -" that the spatial index is only used when the operator is in the ORDER BY " +"geometries. It is different from other operators that use spatial indexes in " +"that the spatial index is only used when the operator is in the ORDER BY " "clause." msgstr "" @@ -1393,10 +1411,12 @@ msgid "" " ST_GeomFromText('LINESTRING(746149 2948672,745954 2948576,\n" +" b.geom <#> ST_GeomFromText('LINESTRING(746149 2948672,745954 " +"2948576,\n" " 745787 2948499,745740 2948468,745712 2948438,\n" " 745690 2948384,745677 2948319)',2249) As b_dist, \n" -" ST_Distance(b.geom, ST_GeomFromText('LINESTRING(746149 2948672,745954 2948576,\n" +" ST_Distance(b.geom, ST_GeomFromText('LINESTRING(746149 " +"2948672,745954 2948576,\n" " 745787 2948499,745740 2948468,745712 2948438,\n" " 745690 2948384,745677 2948319)',2249)) As act_dist\n" " FROM bos_roads As b \n" @@ -1422,7 +1442,8 @@ msgstr "" #. Tag: para #: reference_operator.xml:1054 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -1453,8 +1474,8 @@ msgstr "" msgid "" "The <<->> operator returns the n-D " "(euclidean) distance between the centroids of the bounding boxes of two " -"geometries. Useful for doing nearest neighbor approximate distance ordering." +"geometries. Useful for doing nearest neighbor approximate distance ordering." msgstr "" #. Tag: para @@ -1462,8 +1483,8 @@ msgstr "" #, no-c-format msgid "" "This operand will make use of n-D GiST indexes that may be available on the " -"geometries. It is different from other operators that use spatial indexes in" -" that the spatial index is only used when the operator is in the ORDER BY " +"geometries. It is different from other operators that use spatial indexes in " +"that the spatial index is only used when the operator is in the ORDER BY " "clause." msgstr "" diff --git a/doc/po/de_DE/reference_output.xml.po b/doc/po/de_DE/reference_output.xml.po index e41399862..6cfe5138b 100644 --- a/doc/po/de_DE/reference_output.xml.po +++ b/doc/po/de_DE/reference_output.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:24+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -40,17 +41,17 @@ msgstr "" #, no-c-format msgid "" " bytea ST_AsBinary " -"geometry g1 " -" bytea " -"ST_AsBinary geometry " -"g1 text " -"NDR_or_XDR " -" bytea ST_AsBinary " +"geometry g1 bytea ST_AsBinary geometry g1 text NDR_or_XDR bytea " +"ST_AsBinary geography " +"g1 " +"bytea ST_AsBinary " "geography g1 " -" bytea " -"ST_AsBinary geography " -" g1 text " -"NDR_or_XDR " +"text NDR_or_XDR " msgstr "" #. Tag: title @@ -104,9 +105,9 @@ msgstr "" #, no-c-format msgid "" "The default behavior in PostgreSQL 9.0 has been changed to output bytea in " -"hex encoding. ST_AsBinary is the reverse of for geometry. If your GUI tools require the old" -" behavior, then SET bytea_output='escape' in your database." +"hex encoding. ST_AsBinary is the reverse of for geometry. If your GUI tools require the old behavior, then SET " +"bytea_output='escape' in your database." msgstr "" #. Tag: para @@ -223,13 +224,16 @@ msgstr "" #: reference_output.xml:74 #, no-c-format msgid "" -"SELECT ST_AsBinary(ST_GeomFromText('POLYGON((0 0,0 1,1 1,1 0,0 0))',4326), 'XDR');\n" +"SELECT ST_AsBinary(ST_GeomFromText('POLYGON((0 0,0 1,1 1,1 0,0 0))',4326), " +"'XDR');\n" " st_asbinary\n" "--------------------------------\n" "\\000\\000\\000\\000\\003\\000\\000\\000\\001\\000\\000\\000\\005\\000\\000\\000\\000\\000\n" "\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\n" -"\\000?\\360\\000\\000\\000\\000\\000\\000?\\360\\000\\000\\000\\000\\000\\000?\\360\\000\\000\n" -"\\000\\000\\000\\000?\\360\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\n" +"\\000?\\360\\000\\000\\000\\000\\000\\000?" +"\\360\\000\\000\\000\\000\\000\\000?\\360\\000\\000\n" +"\\000\\000\\000\\000?" +"\\360\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\n" "\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\n" "(1 row)" msgstr "" @@ -269,11 +273,11 @@ msgstr "" #, no-c-format msgid "" " bytea ST_AsEWKB " -"geometry g1 " -" bytea " -"ST_AsEWKB geometry " -"g1 text " -"NDR_or_XDR " +"geometry g1 bytea ST_AsEWKB geometry g1 text NDR_or_XDR " msgstr "" #. Tag: para @@ -327,13 +331,17 @@ msgstr "" #: reference_output.xml:133 #, no-c-format msgid "" -"SELECT ST_AsEWKB(ST_GeomFromText('POLYGON((0 0,0 1,1 1,1 0,0 0))',4326), 'XDR');\n" +"SELECT ST_AsEWKB(ST_GeomFromText('POLYGON((0 0,0 1,1 1,1 0,0 0))',4326), " +"'XDR');\n" " st_asewkb\n" "--------------------------------\n" -"\\000 \\000\\000\\003\\000\\000\\020\\346\\000\\000\\000\\001\\000\\000\\000\\005\\000\\000\\000\\000\\\n" +"\\000 " +"\\000\\000\\003\\000\\000\\020\\346\\000\\000\\000\\001\\000\\000\\000\\005\\000\\000\\000\\000\\\n" "000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000?\n" -"\\360\\000\\000\\000\\000\\000\\000?\\360\\000\\000\\000\\000\\000\\000?\\360\\000\\000\\000\\000\n" -"\\000\\000?\\360\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\n" +"\\360\\000\\000\\000\\000\\000\\000?\\360\\000\\000\\000\\000\\000\\000?" +"\\360\\000\\000\\000\\000\n" +"\\000\\000?" +"\\360\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\n" "\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000" msgstr "" @@ -364,18 +372,18 @@ msgstr "" #, no-c-format msgid "" " text ST_AsEWKT " -"geometry g1 " -" text " -"ST_AsEWKT geography " -"g1 " +"geometry g1 text ST_AsEWKT geography g1 " msgstr "" #. Tag: para #: reference_output.xml:164 #, no-c-format msgid "" -"Returns the Well-Known Text representation of the geometry prefixed with the" -" SRID." +"Returns the Well-Known Text representation of the geometry prefixed with the " +"SRID." msgstr "" #. Tag: para @@ -418,14 +426,16 @@ msgid "" "SELECT ST_AsEWKT('0103000020E61000000100000005000000000000\n" " 000000000000000000000000000000000000000000000000000000\n" " F03F000000000000F03F000000000000F03F000000000000F03\n" -" F000000000000000000000000000000000000000000000000'::geometry);\n" +" F000000000000000000000000000000000000000000000000'::" +"geometry);\n" "\n" " st_asewkt\n" "--------------------------------\n" "SRID=4326;POLYGON((0 0,0 1,1 1,1 0,0 0))\n" "(1 row)\n" "\n" -"SELECT ST_AsEWKT('0108000080030000000000000060E30A4100000000785C0241000000000000F03F0000000018\n" +"SELECT " +"ST_AsEWKT('0108000080030000000000000060E30A4100000000785C0241000000000000F03F0000000018\n" "E20A4100000000485F024100000000000000400000000018\n" "E20A4100000000305C02410000000000000840')\n" "\n" @@ -460,29 +470,26 @@ msgid "" " text ST_AsGeoJSON " "geometry geom " "integer " -"maxdecimaldigits=15 integer " -"options=0 " -" text ST_AsGeoJSON " -"geography geog " -"integer " -"maxdecimaldigits=15 integer " -"options=0 " -" text ST_AsGeoJSON " -"integer gj_version" -" geometry geom " -"integer " -"maxdecimaldigits=15 integer " -"options=0 " -" text ST_AsGeoJSON " -"integer gj_version" -" geography geog " -"integer " -"maxdecimaldigits=15 integer " -"options=0 " +"maxdecimaldigits=15 integer options=0 text ST_AsGeoJSON geography geog integer " +"maxdecimaldigits=15 integer options=0 text ST_AsGeoJSON integer gj_version geometry geom integer " +"maxdecimaldigits=15 integer options=0 text ST_AsGeoJSON integer gj_version geography geog integer " +"maxdecimaldigits=15 integer options=0 " msgstr "" #. Tag: para @@ -597,9 +604,8 @@ msgstr "" msgid "" "GeoJSON format is generally more efficient than other formats for use in " "ajax mapping. One popular javascript client that supports this is Open " -"Layers. Example of its use is OpenLayers " -"GeoJSON Example" +"Layers. Example of its use is OpenLayers GeoJSON Example" msgstr "" #. Tag: programlisting @@ -610,7 +616,8 @@ msgid "" " st_asgeojson\n" "-----------------------------------------------------------------------------------------------------------\n" "\n" -"{\"type\":\"MultiLineString\",\"coordinates\":[[[-89.734634999999997,31.492072000000000],\n" +"{\"type\":\"MultiLineString\",\"coordinates\":" +"[[[-89.734634999999997,31.492072000000000],\n" "[-89.734955999999997,31.492237999999997]]]}\n" "(1 row)\n" "--3d point\n" @@ -640,37 +647,31 @@ msgid "" " text ST_AsGML " "geometry geom " "integer " -"maxdecimaldigits=15 integer " -"options=0 " -" text ST_AsGML " -"geography geog " -"integer " -"maxdecimaldigits=15 integer " -"options=0 " -" text ST_AsGML " +"maxdecimaldigits=15 integer options=0 text ST_AsGML geography geog integer " +"maxdecimaldigits=15 integer options=0 text ST_AsGML integer version geometry geom integer " +"maxdecimaldigits=15 integer options=0 " +"text nprefix=null text " +"id=null " +"text ST_AsGML " "integer version " -"geometry geom " +"geography geog " "integer " -"maxdecimaldigits=15 integer " -"options=0 text " -"nprefix=null text id=null " -" text " -"ST_AsGML integer " -"version geography " -"geog integer " -"maxdecimaldigits=15 integer " -"options=0 text " -"nprefix=null text id=null " -"" +"maxdecimaldigits=15 integer options=0 " +"text nprefix=null text " +"id=null " msgstr "" #. Tag: para @@ -792,10 +793,13 @@ msgstr "" #: reference_output.xml:396 #, no-c-format msgid "" -"0,0 0,1 1,1 1,0 0,0]]>" +" 0,0 0,1 1,1 1,0 0,0]]>" msgstr "" #. Tag: title @@ -809,10 +813,12 @@ msgstr "" #, no-c-format msgid "" "-- Flip coordinates and output extended EPSG (16 | 1)--\n" -"6.34535 5.23423]]>" +" 6.34535 5.23423]]>" msgstr "" #. Tag: programlisting @@ -820,7 +826,8 @@ msgstr "" #, no-c-format msgid "" "-- Output the envelope (32) --\n" -"\n" @@ -833,8 +840,10 @@ msgstr "" #: reference_output.xml:403 #, no-c-format msgid "" -"-- Output the envelope (32) , reverse (lat lon instead of lon lat) (16), long srs (1)= 32 | 16 | 1 = 49 --\n" -"\n" @@ -848,10 +857,13 @@ msgstr "" #, no-c-format msgid "" "-- Polyhedral Example --\n" -"SELECT ST_AsGML(3, ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)), \n" -"((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 0)), \n" +"SELECT ST_AsGML(3, ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 " +"1, 0 1 0, 0 0 0)), \n" +"((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 " +"0)), \n" "((1 1 0, 1 1 1, 1 0 1, 1 0 0, 1 1 0)), \n" -"((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 1)) )'));\n" +"((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 " +"1)) )'));\n" " st_asgml\n" " --------\n" "\n" @@ -859,42 +871,48 @@ msgid "" " \n" " \n" " \n" -" 0 0 0 0 0 1 0 1 1 0 1 0 0 0 0\n" +" 0 0 0 0 0 " +"1 0 1 1 0 1 0 0 0 0\n" " \n" " \n" " \n" " \n" " \n" " \n" -" 0 0 0 0 1 0 1 1 0 1 0 0 0 0 0\n" +" 0 0 0 0 1 " +"0 1 1 0 1 0 0 0 0 0\n" " \n" " \n" " \n" " \n" " \n" " \n" -" 0 0 0 1 0 0 1 0 1 0 0 1 0 0 0\n" +" 0 0 0 1 0 " +"0 1 0 1 0 0 1 0 0 0\n" " \n" " \n" " \n" " \n" " \n" " \n" -" 1 1 0 1 1 1 1 0 1 1 0 0 1 1 0\n" +" 1 1 0 1 1 " +"1 1 0 1 1 0 0 1 1 0\n" " \n" " \n" " \n" " \n" " \n" " \n" -" 0 1 0 0 1 1 1 1 1 1 1 0 0 1 0\n" +" 0 1 0 0 1 " +"1 1 1 1 1 1 0 0 1 0\n" " \n" " \n" " \n" " \n" " \n" " \n" -" 0 0 1 1 0 1 1 1 1 0 1 1 0 0 1\n" +" 0 0 1 1 0 " +"1 1 1 1 0 1 1 0 0 1\n" " \n" " \n" " \n" @@ -922,10 +940,10 @@ msgstr "" msgid "" " text ST_AsHEXEWKB " "geometry g1 " -"text NDRorXDR " -" text " -"ST_AsHEXEWKB geometry " -" g1 " +"text NDRorXDR text ST_AsHEXEWKB geometry g1 " msgstr "" #. Tag: para @@ -933,8 +951,8 @@ msgstr "" #, no-c-format msgid "" "Returns a Geometry in HEXEWKB format (as text) using either little-endian " -"(NDR) or big-endian (XDR) encoding. If no encoding is specified, then NDR is" -" used." +"(NDR) or big-endian (XDR) encoding. If no encoding is specified, then NDR is " +"used." msgstr "" #. Tag: para @@ -947,10 +965,12 @@ msgstr "" #: reference_output.xml:454 #, no-c-format msgid "" -"SELECT ST_AsHEXEWKB(ST_GeomFromText('POLYGON((0 0,0 1,1 1,1 0,0 0))',4326));\n" +"SELECT ST_AsHEXEWKB(ST_GeomFromText('POLYGON((0 0,0 1,1 1,1 0,0 " +"0))',4326));\n" " which gives same answer as\n" "\n" -" SELECT ST_GeomFromText('POLYGON((0 0,0 1,1 1,1 0,0 0))',4326)::text;\n" +" SELECT ST_GeomFromText('POLYGON((0 0,0 1,1 1,1 0,0 " +"0))',4326)::text;\n" "\n" " st_ashexewkb\n" " --------\n" @@ -991,16 +1011,15 @@ msgid "" "integer version " "geometry geom " "integer " -"maxdecimaldigits=15 text " -"nprefix=NULL " -" text ST_AsKML " -"integer version " -"geography geog " -"integer " -"maxdecimaldigits=15 text " -"nprefix=NULL " +"maxdecimaldigits=15 text nprefix=NULL text ST_AsKML integer version geography geog integer " +"maxdecimaldigits=15 text nprefix=NULL " msgstr "" #. Tag: para @@ -1033,17 +1052,15 @@ msgstr "" #: reference_output.xml:506 #, no-c-format msgid "" -"Requires PostGIS be compiled with Proj support. Use to confirm you have proj support compiled" -" in." +"Requires PostGIS be compiled with Proj support. Use to confirm you have proj support compiled in." msgstr "" #. Tag: para #: reference_output.xml:510 #, no-c-format msgid "" -"Availability: 1.2.2 - later variants that include version param came in " -"1.3.2" +"Availability: 1.2.2 - later variants that include version param came in 1.3.2" msgstr "" #. Tag: para @@ -1068,15 +1085,18 @@ msgstr "" #: reference_output.xml:528 #, no-c-format msgid "" -"0,0 0,1 1,1 1,0 0,0\n" +" 0,0 0,1 " +"1,1 1,0 0,0\n" "\n" " --3d linestring\n" " SELECT ST_AsKML('SRID=4326;LINESTRING(1 2 3, 4 5 6)');\n" -" 1,2,3 4,5,6\n" +" 1,2,3 4,5,6\n" " ]]>" msgstr "" @@ -1105,15 +1125,13 @@ msgstr "" msgid "" " text ST_AsSVG " "geometry geom " -"integer " -"rel=0 integer " +"integer rel=0 integer " "maxdecimaldigits=15 " " text ST_AsSVG " "geography geog " -"integer " -"rel=0 integer " +"integer rel=0 integer " "maxdecimaldigits=15 " msgstr "" @@ -1123,10 +1141,10 @@ msgstr "" msgid "" "Return the geometry as Scalar Vector Graphics (SVG) path data. Use 1 as " "second argument to have the path data implemented in terms of relative " -"moves, the default (or 0) uses absolute moves. Third argument may be used to" -" reduce the maximum number of decimal digits used in output (defaults to " -"15). Point geometries will be rendered as cx/cy when 'rel' arg is 0, x/y " -"when 'rel' is 1. Multipoint geometries are delimited by commas (\",\"), " +"moves, the default (or 0) uses absolute moves. Third argument may be used to " +"reduce the maximum number of decimal digits used in output (defaults to 15). " +"Point geometries will be rendered as cx/cy when 'rel' arg is 0, x/y when " +"'rel' is 1. Multipoint geometries are delimited by commas (\",\"), " "GeometryCollection geometries are delimited by semicolons (\";\")." msgstr "" @@ -1134,9 +1152,10 @@ msgstr "" #: reference_output.xml:573 #, no-c-format msgid "" -"Availability: 1.2.2. Availability: 1.4.0 Changed in PostGIS 1.4.0 to include" -" L command in absolute path to conform to http://www.w3.org/TR/SVG/paths.html#PathDataBNF" +"Availability: 1.2.2. Availability: 1.4.0 Changed in PostGIS 1.4.0 to include " +"L command in absolute path to conform to http://www.w3.org/TR/SVG/paths." +"html#PathDataBNF" msgstr "" #. Tag: para @@ -1166,8 +1185,8 @@ msgstr "" #: reference_output.xml:589 #, no-c-format msgid "" -"Returns a Geometry in X3D xml node element format: ISO-IEC-19776-1.2" -"-X3DEncodings-XML" +"Returns a Geometry in X3D xml node element format: ISO-IEC-19776-1.2-" +"X3DEncodings-XML" msgstr "" #. Tag: funcprototype @@ -1177,19 +1196,18 @@ msgid "" "text ST_AsX3D " "geometry g1 " "integer " -"maxdecimaldigits=15 integer " -"options=0" +"maxdecimaldigits=15 integer options=0" msgstr "" #. Tag: para #: reference_output.xml:606 #, no-c-format msgid "" -"Returns a geometry as an X3D xml formatted node element http://www.web3d.org/standards/number/19776-1." -" If maxdecimaldigits (precision) is not specified then " -"defaults to 15." +"Returns a geometry as an X3D xml formatted node element http://www.web3d.org/standards/" +"number/19776-1. If maxdecimaldigits (precision) " +"is not specified then defaults to 15." msgstr "" #. Tag: para @@ -1199,9 +1217,9 @@ msgid "" "There are various options for translating PostGIS geometries to X3D since " "X3D geometry types don't map directly to PostGIS geometry types and some " "newer X3D types that might be better mappings we have avoided since most " -"rendering tools don't currently support them. These are the mappings we have" -" settled on. Feel free to post a bug ticket if you have thoughts on the idea" -" or ways we can allow people to denote their preferred mappings." +"rendering tools don't currently support them. These are the mappings we have " +"settled on. Feel free to post a bug ticket if you have thoughts on the idea " +"or ways we can allow people to denote their preferred mappings." msgstr "" #. Tag: para @@ -1216,9 +1234,9 @@ msgstr "" msgid "" "The 'options' argument is a bitfield. For PostGIS 2.2+, this is used to " "denote whether to represent coordinates with X3D GeoCoordinates Geospatial " -"node and also whether to flip the x/y axis. By default, " -"ST_AsX3D outputs in database form (long,lat or X,Y), but X3D " -"default of lat/lon, y/x may be preferred." +"node and also whether to flip the x/y axis. By default, ST_AsX3D outputs in database form (long,lat or X,Y), but X3D default of lat/" +"lon, y/x may be preferred." msgstr "" #. Tag: para @@ -1226,8 +1244,7 @@ msgstr "" #, no-c-format msgid "" "0: X/Y in database order (e.g. long/lat = X,Y is standard database order), " -"default value, and non-spatial coordinates (just regular old Coordinate " -"tag)." +"default value, and non-spatial coordinates (just regular old Coordinate tag)." msgstr "" #. Tag: para @@ -1245,13 +1262,13 @@ msgstr "" msgid "" "2: Output coordinates in GeoSpatial GeoCoordinates. This option will throw " "an error if geometries are not in WGS 84 long lat (srid: 4326). This is " -"currenlty the only GeoCoordinate type supported. Refer" -" to X3D specs specifying a spatial reference system.. Default output" -" will be GeoCoordinate geoSystem='\"GD\" \"WE\" " -"\"longitude_first\"'. If you prefer the X3D default of " -"GeoCoordinate geoSystem='\"GD\" \"WE\" \"latitude_first\"' use " -"(2 + 1) = 3" +"currenlty the only GeoCoordinate type supported. Refer to X3D specs specifying a spatial " +"reference system.. Default output will be GeoCoordinate " +"geoSystem='\"GD\" \"WE\" \"longitude_first\"'. If you prefer the X3D " +"default of GeoCoordinate geoSystem='\"GD\" \"WE\" \"latitude_first\"' use (2 + 1) = 3" msgstr "" #. Tag: entry @@ -1380,9 +1397,9 @@ msgstr "" #: reference_output.xml:675 #, no-c-format msgid "" -"Lots of advancements happening in 3D space particularly with X3D" -" Integration with HTML5" +"Lots of advancements happening in 3D space particularly with X3D Integration with HTML5" msgstr "" #. Tag: para @@ -1390,20 +1407,19 @@ msgstr "" #, no-c-format msgid "" "There is also a nice open source X3D viewer you can use to view rendered " -"geometries. Free Wrl http://freewrl.sourceforge.net/" -" binaries available for Mac, Linux, and Windows. Use the FreeWRL_Launcher " -"packaged to view the geometries." +"geometries. Free Wrl http://" +"freewrl.sourceforge.net/ binaries available for Mac, Linux, and " +"Windows. Use the FreeWRL_Launcher packaged to view the geometries." msgstr "" #. Tag: para #: reference_output.xml:677 #, no-c-format msgid "" -"Also check out PostGIS minimalist X3D " -"viewer that utilizes this function and x3dDom html/js open source toolkit." +"Also check out PostGIS minimalist X3D viewer that utilizes this function and " +"x3dDom html/js open source toolkit." msgstr "" #. Tag: para @@ -1433,7 +1449,8 @@ msgstr "" #, no-c-format msgid "" "\n" -"\n" +"\n" "\n" " \n" " \n" @@ -1441,10 +1458,13 @@ msgid "" " \n" " \n" " ' || \n" -" ST_AsX3D( ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)), \n" -"((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 0)), \n" +" ST_AsX3D( ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 1, " +"0 1 0, 0 0 0)), \n" +"((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 " +"0)), \n" "((1 1 0, 1 1 1, 1 0 1, 1 0 0, 1 1 0)), \n" -"((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 1)) )')) ||\n" +"((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 " +"1)) )')) ||\n" " '\n" " \n" " \n" @@ -1453,7 +1473,8 @@ msgid "" " x3ddoc\n" " --------\n" "\n" -"\n" +"\n" "\n" " \n" " \n" @@ -1461,8 +1482,11 @@ msgid "" " \n" " \n" " \n" -" \n" -" \n" +" \n" +" \n" " \n" " \n" " \n" @@ -1490,7 +1514,8 @@ msgid "" "x3dfrag\n" "--------\n" "\n" -" \n" +" \n" "]]>" msgstr "" @@ -1519,7 +1544,8 @@ msgid "" "\n" " x3dfrag\n" " --------\n" -"]]>" +"]]>" msgstr "" #. Tag: title @@ -1533,14 +1559,19 @@ msgstr "" #, no-c-format msgid "" "\n" "\n" " x3dfrag\n" " --------\n" -"\n" -" \n" +"\n" +" \n" " ]]>" msgstr "" @@ -1570,12 +1601,11 @@ msgstr "" #: reference_output.xml:728 #, no-c-format msgid "" -"Return a GeoHash representation (http://en.wikipedia.org/wiki/Geohash)" -" of the geometry. A GeoHash encodes a point into a text form that is " -"sortable and searchable based on prefixing. A shorter GeoHash is a less " -"precise representation of a point. It can also be thought of as a box, that " -"contains the actual point." +"Return a GeoHash representation (http://en.wikipedia.org/wiki/Geohash) of the geometry. A " +"GeoHash encodes a point into a text form that is sortable and searchable " +"based on prefixing. A shorter GeoHash is a less precise representation of a " +"point. It can also be thought of as a box, that contains the actual point." msgstr "" #. Tag: para @@ -1585,8 +1615,8 @@ msgid "" "If no maxchars is specficified ST_GeoHash returns a " "GeoHash based on full precision of the input geometry type. Points return a " "GeoHash with 20 characters of precision (about enough to hold the full " -"double precision of the input). Other types return a GeoHash with a variable" -" amount of precision, based on the size of the feature. Larger features are " +"double precision of the input). Other types return a GeoHash with a variable " +"amount of precision, based on the size of the feature. Larger features are " "represented with less precision, smaller features with more precision. The " "idea is that the box implied by the GeoHash will always contain the input " "feature." @@ -1612,8 +1642,8 @@ msgstr "" #: reference_output.xml:737 #, no-c-format msgid "" -"ST_GeoHash will not work with geometries that are not in geographic " -"(lon/lat) coordinates." +"ST_GeoHash will not work with geometries that are not in geographic (lon/" +"lat) coordinates." msgstr "" #. Tag: programlisting @@ -1653,10 +1683,10 @@ msgstr "" #, no-c-format msgid "" " text ST_AsText " -"geometry g1 " -" text " -"ST_AsText geography " -"g1 " +"geometry g1 text ST_AsText geography g1 " msgstr "" #. Tag: para @@ -1669,8 +1699,8 @@ msgstr "" #: reference_output.xml:779 #, no-c-format msgid "" -"The WKT spec does not include the SRID. To get the SRID as part of the data," -" use the non-standard PostGIS " +"The WKT spec does not include the SRID. To get the SRID as part of the data, " +"use the non-standard PostGIS " msgstr "" #. Tag: para @@ -1726,8 +1756,7 @@ msgstr "" #. Tag: refpurpose #: reference_output.xml:814 #, no-c-format -msgid "" -"Return the Degrees, Minutes, Seconds representation of the given point." +msgid "Return the Degrees, Minutes, Seconds representation of the given point." msgstr "" #. Tag: funcprototype @@ -1769,8 +1798,8 @@ msgstr "" #: reference_output.xml:841 #, no-c-format msgid "" -"\"M\", \"S\", and \"C\" are optional. If \"C\" is omitted, degrees are shown" -" with a \"-\" sign if south or west. If \"S\" is omitted, minutes will be " +"\"M\", \"S\", and \"C\" are optional. If \"C\" is omitted, degrees are shown " +"with a \"-\" sign if south or west. If \"S\" is omitted, minutes will be " "shown as decimal with as many digits of precision as you specify. If \"M\" " "is also omitted, degrees are shown as decimal with as many digits precision " "as you specify." @@ -1832,10 +1861,12 @@ msgstr "" #: reference_output.xml:863 #, no-c-format msgid "" -"SELECT (ST_AsLatLonText('POINT (-3.2342342 -2.32498)', 'D degrees, M minutes, S seconds to the C'));\n" +"SELECT (ST_AsLatLonText('POINT (-3.2342342 -2.32498)', 'D degrees, M " +"minutes, S seconds to the C'));\n" " st_aslatlontext \n" "--------------------------------------------------------------------------------------\n" -" 2 degrees, 19 minutes, 30 seconds to the S 3 degrees, 14 minutes, 3 seconds to the W" +" 2 degrees, 19 minutes, 30 seconds to the S 3 degrees, 14 minutes, 3 seconds " +"to the W" msgstr "" #. Tag: para @@ -1864,7 +1895,8 @@ msgstr "" #: reference_output.xml:867 #, no-c-format msgid "" -"SELECT (ST_AsLatLonText('POINT (-3.2342342 -2.32498)', 'D.DDDD degrees C'));\n" +"SELECT (ST_AsLatLonText('POINT (-3.2342342 -2.32498)', 'D.DDDD degrees " +"C'));\n" " st_aslatlontext \n" "-----------------------------------\n" " 2.3250 degrees S 3.2342 degrees W" @@ -1904,27 +1936,23 @@ msgstr "" msgid "" " bytea ST_AsTWKB " "geometry g1 " -"integer " -"decimaldigits_xy=0 integer" -" decimaldigits_z=0 " -"integer " +"integer decimaldigits_xy=0 integer decimaldigits_z=0 integer " "decimaldigits_m=0 boolean " " include_sizes=false " -"boolean include_bounding " -"boxes=false " -"bytea ST_AsTWKB " -"geometry[] " -"geometries bigint[] " -" unique_ids integer" -" decimaldigits_xy=0 " -"integer " -"decimaldigits_z=0 integer " -" decimaldigits_m=0 " -"boolean " +"boolean include_bounding boxes=false bytea " +"ST_AsTWKB geometry[] " +"geometries bigint[] unique_ids integer decimaldigits_xy=0 " +"integer decimaldigits_z=0 integer decimaldigits_m=0 boolean " "include_sizes=false " -"boolean " -"include_bounding_boxes=false " -"" +"boolean include_bounding_boxes=false " msgstr "" #. Tag: para @@ -1932,9 +1960,9 @@ msgstr "" #, no-c-format msgid "" "Returns the geometry in TWKB (Tiny Well-Known Binary) format. TWKB is a " -"compressed" -" binary format with a focus on minimizing the size of the output." +"compressed binary format with a focus on minimizing the size of " +"the output." msgstr "" #. Tag: para @@ -1952,8 +1980,8 @@ msgstr "" #: reference_output.xml:908 #, no-c-format msgid "" -"The sizes and bounding boxes parameters control whether optional information" -" about the encoded length of the object and the bounds of the object are " +"The sizes and bounding boxes parameters control whether optional information " +"about the encoded length of the object and the bounds of the object are " "included in the output. By default they are not. Do not turn them on unless " "your client software has a use for them, as they just use up space (and " "saving space is the point of TWKB)." @@ -1966,20 +1994,20 @@ msgid "" "The array-input form of the function is used to convert a collection of " "geometries and unique identifiers into a TWKB collection that preserves the " "identifiers. This is useful for clients that expect to unpack a collection " -"and then access further information about the objects inside. You can create" -" the arrays using the array_agg function. The other parameters" -" operate the same as for the simple form of the function." +"and then access further information about the objects inside. You can create " +"the arrays using the array_agg function. The other parameters " +"operate the same as for the simple form of the function." msgstr "" #. Tag: para #: reference_output.xml:911 #, no-c-format msgid "" -"The format specification is available online at https://github.com/TWKB/Specification," -" and code for building a JavaScript client can be found at https://github.com/TWKB/twkb.js." +"The format specification is available online at https://github.com/TWKB/Specification, and " +"code for building a JavaScript client can be found at https://github.com/TWKB/twkb.js." msgstr "" #. Tag: para @@ -2035,8 +2063,8 @@ msgstr "" msgid "" "text ST_AsEncodedPolyline " "geometry geom " -"integer " -"precision=5" +"integer precision=5" msgstr "" #. Tag: para @@ -2049,7 +2077,8 @@ msgstr "" #: reference_output.xml:962 #, no-c-format msgid "" -"ST_AsEncodedPolyline(GeomFromEWKT('SRID=4326;LINESTRING(-120.2 38.5,-120.95 40.7,-126.453 43.252)'));\n" +"ST_AsEncodedPolyline(GeomFromEWKT('SRID=4326;LINESTRING(-120.2 38.5,-120.95 " +"40.7,-126.453 43.252)'));\n" "--result--\n" "|_p~iF~ps|U_ulLnnqC_mqNvxq`@" msgstr "" diff --git a/doc/po/de_DE/reference_processing.xml.po b/doc/po/de_DE/reference_processing.xml.po index 1087223b9..308007bc2 100644 --- a/doc/po/de_DE/reference_processing.xml.po +++ b/doc/po/de_DE/reference_processing.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:24+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -41,23 +42,21 @@ msgstr "" msgid "" " geometry ST_Buffer " "geometry g1 " -"float " -"radius_of_buffer " -" geometry ST_Buffer " -"geometry g1 " -"float " -"radius_of_buffer integer " -" num_seg_quarter_circle " -" geometry " +"float radius_of_buffer geometry " "ST_Buffer geometry " "g1 float " -"radius_of_buffer text " -" buffer_style_parameters " -" geography " -"ST_Buffer geography " -"g1 float " -"radius_of_buffer_in_meters " -"" +"radius_of_buffer integer num_seg_quarter_circle geometry ST_Buffer geometry g1 float " +"radius_of_buffer text buffer_style_parameters geography ST_Buffer geography g1 float " +"radius_of_buffer_in_meters " msgstr "" #. Tag: title @@ -113,8 +112,8 @@ msgstr "" #, no-c-format msgid "" "Geography: For geography this is really a thin wrapper around the geometry " -"implementation. It first determines the best SRID that fits the bounding box" -" of the geography object (favoring UTM, Lambert Azimuthal Equal Area (LAEA) " +"implementation. It first determines the best SRID that fits the bounding box " +"of the geography object (favoring UTM, Lambert Azimuthal Equal Area (LAEA) " "north/south pole, and falling back on mercator in worst case scenario) and " "then buffers in that planar spatial ref and retransforms back to WGS84 " "geography." @@ -135,16 +134,16 @@ msgid "" "Availability: 1.5 - ST_Buffer was enhanced to support different endcaps and " "join types. These are useful for example to convert road linestrings into " "polygon roads with flat or square edges instead of rounded edges. Thin " -"wrapper for geography was added. - requires GEOS >= 3.2 to take advantage" -" of advanced geometry functionality." +"wrapper for geography was added. - requires GEOS >= 3.2 to take advantage " +"of advanced geometry functionality." msgstr "" #. Tag: para #: reference_processing.xml:61 #, no-c-format msgid "" -"The optional third parameter (currently only applies to geometry) can either" -" specify number of segments used to approximate a quarter circle (integer " +"The optional third parameter (currently only applies to geometry) can either " +"specify number of segments used to approximate a quarter circle (integer " "case, defaults to 8) or a list of blank-separated key=value pairs (string " "case) to tweak operations as follows:" msgstr "" @@ -170,9 +169,9 @@ msgstr "" #: reference_processing.xml:71 #, no-c-format msgid "" -"'join=round|mitre|bevel' : join style (defaults to \"round\", needs GEOS-3.2" -" or higher for a different value). 'miter' is also accepted as a synonym for" -" 'mitre'." +"'join=round|mitre|bevel' : join style (defaults to \"round\", needs GEOS-3.2 " +"or higher for a different value). 'miter' is also accepted as a synonym for " +"'mitre'." msgstr "" #. Tag: para @@ -232,8 +231,8 @@ msgstr "" #, no-c-format msgid "" "People often make the mistake of using this function to try to do radius " -"searches. Creating a buffer to to a radius search is slow and pointless. Use" -" instead." +"searches. Creating a buffer to to a radius search is slow and pointless. Use " +" instead." msgstr "" #. Tag: title @@ -387,8 +386,10 @@ msgid "" "--A buffered point approximates a circle\n" "-- A buffered point forcing approximation of (see diagram)\n" "-- 2 points per circle is poly with 8 sides (see diagram)\n" -"SELECT ST_NPoints(ST_Buffer(ST_GeomFromText('POINT(100 90)'), 50)) As promisingcircle_pcount,\n" -"ST_NPoints(ST_Buffer(ST_GeomFromText('POINT(100 90)'), 50, 2)) As lamecircle_pcount;\n" +"SELECT ST_NPoints(ST_Buffer(ST_GeomFromText('POINT(100 90)'), 50)) As " +"promisingcircle_pcount,\n" +"ST_NPoints(ST_Buffer(ST_GeomFromText('POINT(100 90)'), 50, 2)) As " +"lamecircle_pcount;\n" "\n" "promisingcircle_pcount | lamecircle_pcount\n" "------------------------+-------------------\n" @@ -404,9 +405,12 @@ msgid "" "ST_SetSRID(ST_MakePoint(-71.063526, 42.35785),4269), 26986)\n" ",100,2)) As octagon;\n" "----------------------\n" -"POLYGON((236057.59057465 900908.759918696,236028.301252769 900838.049240578,235\n" -"957.59057465 900808.759918696,235886.879896532 900838.049240578,235857.59057465\n" -"900908.759918696,235886.879896532 900979.470596815,235957.59057465 901008.759918\n" +"POLYGON((236057.59057465 900908.759918696,236028.301252769 " +"900838.049240578,235\n" +"957.59057465 900808.759918696,235886.879896532 " +"900838.049240578,235857.59057465\n" +"900908.759918696,235886.879896532 900979.470596815,235957.59057465 " +"901008.759918\n" "696,236028.301252769 900979.470596815,236057.59057465 900908.759918696))" msgstr "" @@ -542,8 +546,8 @@ msgstr "" #: reference_processing.xml:273 #, no-c-format msgid "" -", , ," -" wrappers to this function with " +", , , " +"wrappers to this function with " "standard OGC interface" msgstr "" @@ -573,8 +577,8 @@ msgstr "" #, no-c-format msgid "" "Clips a geometry by a 2D box in a fast but possibly dirty way. The output " -"geometry is not guaranteed to be valid (self-intersections for a polygon may" -" be introduced). Topologically invalid input geometries do not result in " +"geometry is not guaranteed to be valid (self-intersections for a polygon may " +"be introduced). Topologically invalid input geometries do not result in " "exceptions being thrown." msgstr "" @@ -622,14 +626,14 @@ msgstr "" #, no-c-format msgid "" " geometry ST_Collect " -"geometry set " -"g1field " +"geometry set g1field geometry " +"ST_Collect geometry " +"g1 geometry " +"g2 " "geometry ST_Collect " -"geometry g1 " -"geometry g2 " -" geometry " -"ST_Collect geometry[] " -"g1_array " +"geometry[] g1_array " +"" msgstr "" #. Tag: para @@ -646,12 +650,11 @@ msgstr "" #, no-c-format msgid "" "Aggregate version: This function returns a GEOMETRYCOLLECTION or a MULTI " -"object from a set of geometries. The ST_Collect() function is an " -"\"aggregate\" function in the terminology of PostgreSQL. That means that it " -"operates on rows of data, in the same way the SUM() and AVG() functions do. " -"For example, \"SELECT ST_Collect(GEOM) FROM GEOMTABLE GROUP BY ATTRCOLUMN\" " -"will return a separate GEOMETRYCOLLECTION for each distinct value of " -"ATTRCOLUMN." +"object from a set of geometries. The ST_Collect() function is an \"aggregate" +"\" function in the terminology of PostgreSQL. That means that it operates on " +"rows of data, in the same way the SUM() and AVG() functions do. For example, " +"\"SELECT ST_Collect(GEOM) FROM GEOMTABLE GROUP BY ATTRCOLUMN\" will return a " +"separate GEOMETRYCOLLECTION for each distinct value of ATTRCOLUMN." msgstr "" #. Tag: para @@ -659,8 +662,7 @@ msgstr "" #, no-c-format msgid "" "Non-Aggregate version: This function returns a geometry being a collection " -"of two input geometries. Output type can be a MULTI* or a " -"GEOMETRYCOLLECTION." +"of two input geometries. Output type can be a MULTI* or a GEOMETRYCOLLECTION." msgstr "" #. Tag: para @@ -668,15 +670,14 @@ msgstr "" #, no-c-format msgid "" "ST_Collect and ST_Union are often interchangeable. ST_Collect is in general " -"orders of magnitude faster than ST_Union because it does not try to dissolve" -" boundaries or validate that a constructed MultiPolgon doesn't have " +"orders of magnitude faster than ST_Union because it does not try to dissolve " +"boundaries or validate that a constructed MultiPolgon doesn't have " "overlapping regions. It merely rolls up single geometries into MULTI and " "MULTI or mixed geometry types into Geometry Collections. Unfortunately " "geometry collections are not well-supported by GIS tools. To prevent " "ST_Collect from returning a Geometry Collection when collecting MULTI " -"geometries, one can use the below trick that utilizes to expand the MULTIs out to singles and then regroup " -"them." +"geometries, one can use the below trick that utilizes to expand the MULTIs out to singles and then regroup them." msgstr "" #. Tag: para @@ -713,10 +714,9 @@ msgstr "" #: reference_processing.xml:391 #, no-c-format msgid "" -"Aggregate example (http://postgis.refractions.net/pipermail" -"/postgis-users/2008-June/020331.html)" +"Aggregate example (http://postgis.refractions.net/" +"pipermail/postgis-users/2008-June/020331.html)" msgstr "" #. Tag: programlisting @@ -765,18 +765,22 @@ msgid "" " MULTIPOINT(1 2 3,1 2 4)\n" "\n" " --Example with curves\n" -"SELECT ST_AsText(ST_Collect(ST_GeomFromText('CIRCULARSTRING(220268 150415,220227 150505,220227 150406)'),\n" -"ST_GeomFromText('CIRCULARSTRING(220227 150406,2220227 150407,220227 150406)')));\n" +"SELECT ST_AsText(ST_Collect(ST_GeomFromText('CIRCULARSTRING(220268 " +"150415,220227 150505,220227 150406)'),\n" +"ST_GeomFromText('CIRCULARSTRING(220227 150406,2220227 150407,220227 " +"150406)')));\n" " st_astext\n" "------------------------------------------------------------------------------------\n" -" GEOMETRYCOLLECTION(CIRCULARSTRING(220268 150415,220227 150505,220227 150406),\n" +" GEOMETRYCOLLECTION(CIRCULARSTRING(220268 150415,220227 150505,220227 " +"150406),\n" " CIRCULARSTRING(220227 150406,2220227 150407,220227 150406))\n" "\n" "--New ST_Collect array construct\n" "SELECT ST_Collect(ARRAY(SELECT the_geom FROM sometable));\n" "\n" "SELECT ST_AsText(ST_Collect(ARRAY[ST_GeomFromText('LINESTRING(1 2, 3 4)'),\n" -" ST_GeomFromText('LINESTRING(3 4, 4 5)')])) As wktcollect;\n" +" ST_GeomFromText('LINESTRING(3 4, 4 5)')])) As " +"wktcollect;\n" "\n" "--wkt collect --\n" "MULTILINESTRING((1 2,3 4),(3 4,4 5))" @@ -809,9 +813,8 @@ msgstr "" msgid "" "geometry ST_ConcaveHull " "geometry geomA " -"float " -"target_percent boolean " +"float target_percent boolean " "allow_holes=false" msgstr "" @@ -833,8 +836,8 @@ msgid "" "the concave hull as the geometry you get by vacuum sealing a set of " "geometries. The target_percent of 1 will give you the same answer as the " "convex hull. A target_percent between 0 and 0.99 will give you something " -"that should have a smaller area than the convex hull. This is different from" -" a convex hull which is more like wrapping a rubber band around the set of " +"that should have a smaller area than the convex hull. This is different from " +"a convex hull which is more like wrapping a rubber band around the set of " "geometries." msgstr "" @@ -878,17 +881,16 @@ msgstr "" #, no-c-format msgid "" "Note - The smaller you make the target percent, the longer it takes to " -"process the concave hull and more likely to run into topological exceptions." -" Also the more floating points and number of points you accrue. First try a " +"process the concave hull and more likely to run into topological exceptions. " +"Also the more floating points and number of points you accrue. First try a " "0.99 which does a first hop, is usually very fast, sometimes as fast as " "computing the convex hull, and usually gives much better than 99% of shrink " -"since it almost always overshoots. Second hope of 0.98 it slower, others get" -" slower usually quadratically. To reduce precision and float points, use " -" or after ST_ConcaveHull. ST_SnapToGrid is a bit " -"faster, but could result in invalid geometries where as " -"ST_SimplifyPreserveTopology almost always preserves the validity of the " -"geometry." +"since it almost always overshoots. Second hope of 0.98 it slower, others get " +"slower usually quadratically. To reduce precision and float points, use " +" or after ST_ConcaveHull. ST_SnapToGrid is a bit faster, but " +"could result in invalid geometries where as ST_SimplifyPreserveTopology " +"almost always preserves the validity of the geometry." msgstr "" #. Tag: para @@ -896,8 +898,8 @@ msgstr "" #, no-c-format msgid "" "More real world examples and brief explanation of the technique are shown " -"http://www.bostongis.com/postgis_concavehull.snippet" +"http://" +"www.bostongis.com/postgis_concavehull.snippet" msgstr "" #. Tag: para @@ -905,13 +907,12 @@ msgstr "" #, no-c-format msgid "" "Also check out Simon Greener's article on demonstrating ConcaveHull " -"introduced in Oracle 11G R2. http://www.spatialdbadvisor.com/oracle_spatial_tips_tricks/172" -"/concave-hull-geometries-in-oracle-11gr2. The solution we get at " -"0.75 target percent of convex hull is similar to the shape Simon gets with " -"Oracle SDO_CONCAVEHULL_BOUNDARY." +"introduced in Oracle 11G R2. http://www.spatialdbadvisor.com/" +"oracle_spatial_tips_tricks/172/concave-hull-geometries-in-oracle-11gr2. The solution we get at 0.75 target percent of convex hull is similar " +"to the shape Simon gets with Oracle SDO_CONCAVEHULL_BOUNDARY." msgstr "" #. Tag: para @@ -935,8 +936,7 @@ msgstr "" #. Tag: para #: reference_processing.xml:469 #, no-c-format -msgid "" -"ST_ConcaveHull of 2 polygons encased in target 100% shrink concave hull" +msgid "ST_ConcaveHull of 2 polygons encased in target 100% shrink concave hull" msgstr "" #. Tag: programlisting @@ -944,7 +944,8 @@ msgstr "" #, no-c-format msgid "" "-- geometries overlaid with concavehull \n" -"-- at target 100% shrink (this is the same as convex hull - since no shrink)\n" +"-- at target 100% shrink (this is the same as convex hull - since no " +"shrink)\n" "SELECT \n" " ST_ConcaveHull(\n" " ST_Union(ST_GeomFromText('POLYGON((175 150, 20 40, \n" @@ -1038,15 +1039,16 @@ msgstr "" #: reference_processing.xml:534 #, no-c-format msgid "" -"multilinestring with overlaid with Concave hull of linestrings at 99% target" -" -- first hop" +"multilinestring with overlaid with Concave hull of linestrings at 99% target " +"-- first hop" msgstr "" #. Tag: programlisting #: reference_processing.xml:538 #, no-c-format msgid "" -"SELECT ST_ConcaveHull(ST_GeomFromText('MULTILINESTRING((106 164,30 112,74 70,82 112,130 94,\n" +"SELECT ST_ConcaveHull(ST_GeomFromText('MULTILINESTRING((106 164,30 112,74 " +"70,82 112,130 94,\n" " 130 62,122 40,156 32,162 76,172 88),\n" "(132 178,134 148,128 136,96 128,132 108,150 130,\n" "170 142,174 110,156 96,158 90,158 88),\n" @@ -1060,8 +1062,8 @@ msgstr "" #: reference_processing.xml:548 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -1151,8 +1153,10 @@ msgstr "" msgid "" "SELECT ST_AsText(ST_ConvexHull(\n" " ST_Collect(\n" -" ST_GeomFromText('MULTILINESTRING((100 190,10 8),(150 10, 20 30))'),\n" -" ST_GeomFromText('MULTIPOINT(50 5, 150 30, 50 10, 10 10)')\n" +" ST_GeomFromText('MULTILINESTRING((100 190,10 8),(150 10, 20 " +"30))'),\n" +" ST_GeomFromText('MULTIPOINT(50 5, 150 30, 50 10, 10 " +"10)')\n" " )) );\n" "---st_astext--\n" "POLYGON((50 5,10 8,10 10,100 190,150 30,150 10,50 5))" @@ -1162,8 +1166,8 @@ msgstr "" #: reference_processing.xml:611 #, no-c-format msgid "" -", , " +", , " msgstr "" #. Tag: refname @@ -1182,23 +1186,22 @@ msgstr "" #: reference_processing.xml:623 #, no-c-format msgid "" -" geometry " -"ST_CurveToLine " -"geometry curveGeom " -" geometry " -"ST_CurveToLine " -"geometry curveGeom " -"integer " -"segments_per_qtr_circle " +" geometry ST_CurveToLine geometry curveGeom geometry " +"ST_CurveToLine geometry curveGeom integer segments_per_qtr_circle " msgstr "" #. Tag: para #: reference_processing.xml:639 #, no-c-format msgid "" -"Converst a CIRCULAR STRING to regular LINESTRING or CURVEPOLYGON to POLYGON." -" Useful for outputting to devices that can't support CIRCULARSTRING geometry" -" types" +"Converst a CIRCULAR STRING to regular LINESTRING or CURVEPOLYGON to POLYGON. " +"Useful for outputting to devices that can't support CIRCULARSTRING geometry " +"types" msgstr "" #. Tag: para @@ -1240,60 +1243,106 @@ msgstr "" #: reference_processing.xml:653 #, no-c-format msgid "" -"SELECT ST_AsText(ST_CurveToLine(ST_GeomFromText('CIRCULARSTRING(220268 150415,220227 150505,220227 150406)')));\n" +"SELECT ST_AsText(ST_CurveToLine(ST_GeomFromText('CIRCULARSTRING(220268 " +"150415,220227 150505,220227 150406)')));\n" "\n" "--Result --\n" -" LINESTRING(220268 150415,220269.95064912 150416.539364228,220271.823415575 150418.17258804,220273.613787707 150419.895736857,\n" -" 220275.317452352 150421.704659462,220276.930305234 150423.594998003,220278.448460847 150425.562198489,\n" -" 220279.868261823 150427.60152176,220281.186287736 150429.708054909,220282.399363347 150431.876723113,\n" -" 220283.50456625 150434.10230186,220284.499233914 150436.379429536,220285.380970099 150438.702620341,220286.147650624 150441.066277505,\n" -" 220286.797428488 150443.464706771,220287.328738321 150445.892130112,220287.740300149 150448.342699654,\n" -" 220288.031122486 150450.810511759,220288.200504713 150453.289621251,220288.248038775 150455.77405574,\n" -" 220288.173610157 150458.257830005,220287.977398166 150460.734960415,220287.659875492 150463.199479347,\n" -" 220287.221807076 150465.64544956,220286.664248262 150468.066978495,220285.988542259 150470.458232479,220285.196316903 150472.81345077,\n" -" 220284.289480732 150475.126959442,220283.270218395 150477.39318505,220282.140985384 150479.606668057,\n" -" 220280.90450212 150481.762075989,220279.5637474 150483.85421628,220278.12195122 150485.87804878,\n" -" 220276.582586992 150487.828697901,220274.949363179 150489.701464356,220273.226214362 150491.491836488,\n" -" 220271.417291757 150493.195501133,220269.526953216 150494.808354014,220267.559752731 150496.326509628,\n" -" 220265.520429459 150497.746310603,220263.41389631 150499.064336517,220261.245228106 150500.277412127,\n" -" 220259.019649359 150501.38261503,220256.742521683 150502.377282695,220254.419330878 150503.259018879,\n" -" 220252.055673714 150504.025699404,220249.657244448 150504.675477269,220247.229821107 150505.206787101,\n" -" 220244.779251566 150505.61834893,220242.311439461 150505.909171266,220239.832329968 150506.078553494,\n" -" 220237.347895479 150506.126087555,220234.864121215 150506.051658938,220232.386990804 150505.855446946,\n" -" 220229.922471872 150505.537924272,220227.47650166 150505.099855856,220225.054972724 150504.542297043,\n" +" LINESTRING(220268 150415,220269.95064912 150416.539364228,220271.823415575 " +"150418.17258804,220273.613787707 150419.895736857,\n" +" 220275.317452352 150421.704659462,220276.930305234 " +"150423.594998003,220278.448460847 150425.562198489,\n" +" 220279.868261823 150427.60152176,220281.186287736 " +"150429.708054909,220282.399363347 150431.876723113,\n" +" 220283.50456625 150434.10230186,220284.499233914 " +"150436.379429536,220285.380970099 150438.702620341,220286.147650624 " +"150441.066277505,\n" +" 220286.797428488 150443.464706771,220287.328738321 " +"150445.892130112,220287.740300149 150448.342699654,\n" +" 220288.031122486 150450.810511759,220288.200504713 " +"150453.289621251,220288.248038775 150455.77405574,\n" +" 220288.173610157 150458.257830005,220287.977398166 " +"150460.734960415,220287.659875492 150463.199479347,\n" +" 220287.221807076 150465.64544956,220286.664248262 " +"150468.066978495,220285.988542259 150470.458232479,220285.196316903 " +"150472.81345077,\n" +" 220284.289480732 150475.126959442,220283.270218395 " +"150477.39318505,220282.140985384 150479.606668057,\n" +" 220280.90450212 150481.762075989,220279.5637474 " +"150483.85421628,220278.12195122 150485.87804878,\n" +" 220276.582586992 150487.828697901,220274.949363179 " +"150489.701464356,220273.226214362 150491.491836488,\n" +" 220271.417291757 150493.195501133,220269.526953216 " +"150494.808354014,220267.559752731 150496.326509628,\n" +" 220265.520429459 150497.746310603,220263.41389631 " +"150499.064336517,220261.245228106 150500.277412127,\n" +" 220259.019649359 150501.38261503,220256.742521683 " +"150502.377282695,220254.419330878 150503.259018879,\n" +" 220252.055673714 150504.025699404,220249.657244448 " +"150504.675477269,220247.229821107 150505.206787101,\n" +" 220244.779251566 150505.61834893,220242.311439461 " +"150505.909171266,220239.832329968 150506.078553494,\n" +" 220237.347895479 150506.126087555,220234.864121215 " +"150506.051658938,220232.386990804 150505.855446946,\n" +" 220229.922471872 150505.537924272,220227.47650166 " +"150505.099855856,220225.054972724 150504.542297043,\n" " 220222.663718741 150503.86659104,220220.308500449 150503.074365683,\n" " 220217.994991777 150502.167529512,220215.72876617 150501.148267175,\n" " 220213.515283163 150500.019034164,220211.35987523 150498.7825509,\n" " 220209.267734939 150497.441796181,220207.243902439 150496,\n" -" 220205.293253319 150494.460635772,220203.420486864 150492.82741196,220201.630114732 150491.104263143,\n" -" 220199.926450087 150489.295340538,220198.313597205 150487.405001997,220196.795441592 150485.437801511,\n" -" 220195.375640616 150483.39847824,220194.057614703 150481.291945091,220192.844539092 150479.123276887,220191.739336189 150476.89769814,\n" -" 220190.744668525 150474.620570464,220189.86293234 150472.297379659,220189.096251815 150469.933722495,\n" -" 220188.446473951 150467.535293229,220187.915164118 150465.107869888,220187.50360229 150462.657300346,\n" -" 220187.212779953 150460.189488241,220187.043397726 150457.710378749,220186.995863664 150455.22594426,\n" -" 220187.070292282 150452.742169995,220187.266504273 150450.265039585,220187.584026947 150447.800520653,\n" -" 220188.022095363 150445.35455044,220188.579654177 150442.933021505,220189.25536018 150440.541767521,\n" -" 220190.047585536 150438.18654923,220190.954421707 150435.873040558,220191.973684044 150433.60681495,\n" -" 220193.102917055 150431.393331943,220194.339400319 150429.237924011,220195.680155039 150427.14578372,220197.12195122 150425.12195122,\n" -" 220198.661315447 150423.171302099,220200.29453926 150421.298535644,220202.017688077 150419.508163512,220203.826610682 150417.804498867,\n" -" 220205.716949223 150416.191645986,220207.684149708 150414.673490372,220209.72347298 150413.253689397,220211.830006129 150411.935663483,\n" -" 220213.998674333 150410.722587873,220216.22425308 150409.61738497,220218.501380756 150408.622717305,220220.824571561 150407.740981121,\n" -" 220223.188228725 150406.974300596,220225.586657991 150406.324522731,220227 150406)\n" +" 220205.293253319 150494.460635772,220203.420486864 " +"150492.82741196,220201.630114732 150491.104263143,\n" +" 220199.926450087 150489.295340538,220198.313597205 " +"150487.405001997,220196.795441592 150485.437801511,\n" +" 220195.375640616 150483.39847824,220194.057614703 " +"150481.291945091,220192.844539092 150479.123276887,220191.739336189 " +"150476.89769814,\n" +" 220190.744668525 150474.620570464,220189.86293234 " +"150472.297379659,220189.096251815 150469.933722495,\n" +" 220188.446473951 150467.535293229,220187.915164118 " +"150465.107869888,220187.50360229 150462.657300346,\n" +" 220187.212779953 150460.189488241,220187.043397726 " +"150457.710378749,220186.995863664 150455.22594426,\n" +" 220187.070292282 150452.742169995,220187.266504273 " +"150450.265039585,220187.584026947 150447.800520653,\n" +" 220188.022095363 150445.35455044,220188.579654177 " +"150442.933021505,220189.25536018 150440.541767521,\n" +" 220190.047585536 150438.18654923,220190.954421707 " +"150435.873040558,220191.973684044 150433.60681495,\n" +" 220193.102917055 150431.393331943,220194.339400319 " +"150429.237924011,220195.680155039 150427.14578372,220197.12195122 " +"150425.12195122,\n" +" 220198.661315447 150423.171302099,220200.29453926 " +"150421.298535644,220202.017688077 150419.508163512,220203.826610682 " +"150417.804498867,\n" +" 220205.716949223 150416.191645986,220207.684149708 " +"150414.673490372,220209.72347298 150413.253689397,220211.830006129 " +"150411.935663483,\n" +" 220213.998674333 150410.722587873,220216.22425308 " +"150409.61738497,220218.501380756 150408.622717305,220220.824571561 " +"150407.740981121,\n" +" 220223.188228725 150406.974300596,220225.586657991 150406.324522731,220227 " +"150406)\n" "\n" "--3d example\n" -"SELECT ST_AsEWKT(ST_CurveToLine(ST_GeomFromEWKT('CIRCULARSTRING(220268 150415 1,220227 150505 2,220227 150406 3)')));\n" +"SELECT ST_AsEWKT(ST_CurveToLine(ST_GeomFromEWKT('CIRCULARSTRING(220268 " +"150415 1,220227 150505 2,220227 150406 3)')));\n" "Output\n" "------\n" -" LINESTRING(220268 150415 1,220269.95064912 150416.539364228 1.0181172856673,\n" -" 220271.823415575 150418.17258804 1.03623457133459,220273.613787707 150419.895736857 1.05435185700189,....AD INFINITUM ....\n" +" LINESTRING(220268 150415 1,220269.95064912 150416.539364228 " +"1.0181172856673,\n" +" 220271.823415575 150418.17258804 1.03623457133459,220273.613787707 " +"150419.895736857 1.05435185700189,....AD INFINITUM ....\n" " 220225.586657991 150406.324522731 1.32611114201132,220227 150406 3)\n" "\n" "--use only 2 segments to approximate quarter circle\n" -"SELECT ST_AsText(ST_CurveToLine(ST_GeomFromText('CIRCULARSTRING(220268 150415,220227 150505,220227 150406)'),2));\n" +"SELECT ST_AsText(ST_CurveToLine(ST_GeomFromText('CIRCULARSTRING(220268 " +"150415,220227 150505,220227 150406)'),2));\n" "st_astext\n" "------------------------------\n" -" LINESTRING(220268 150415,220287.740300149 150448.342699654,220278.12195122 150485.87804878,\n" -" 220244.779251566 150505.61834893,220207.243902439 150496,220187.50360229 150462.657300346,\n" +" LINESTRING(220268 150415,220287.740300149 150448.342699654,220278.12195122 " +"150485.87804878,\n" +" 220244.779251566 150505.61834893,220207.243902439 150496,220187.50360229 " +"150462.657300346,\n" " 220197.12195122 150425.12195122,220227 150406)" msgstr "" @@ -1323,12 +1372,11 @@ msgstr "" #: reference_processing.xml:687 #, no-c-format msgid "" -"Return a Delaunay " -"triangulation around the vertices of the input geometry. Output is a" -" COLLECTION of polygons (for flags=0) or a MULTILINESTRING (for flags=1) or " -"TIN (for flags=2). The tolerance, if any, is used to snap input vertices " -"togheter." +"Return a Delaunay triangulation around the vertices of the input geometry. " +"Output is a COLLECTION of polygons (for flags=0) or a MULTILINESTRING (for " +"flags=1) or TIN (for flags=2). The tolerance, if any, is used to snap input " +"vertices togheter." msgstr "" #. Tag: para @@ -1372,8 +1420,8 @@ msgstr "" #: reference_processing.xml:722 #, no-c-format msgid "" -"ST_DelaunayTriangles of 2 polygons: delaunay triangle polygons each triangle" -" themed in different color" +"ST_DelaunayTriangles of 2 polygons: delaunay triangle polygons each triangle " +"themed in different color" msgstr "" #. Tag: programlisting @@ -1544,7 +1592,8 @@ msgstr "" #: reference_processing.xml:835 #, no-c-format msgid "" -"--Safe for 2d. This is same geometries as what is shown for st_symdifference\n" +"--Safe for 2d. This is same geometries as what is shown for " +"st_symdifference\n" "SELECT ST_AsText(\n" " ST_Difference(\n" " ST_GeomFromText('LINESTRING(50 100, 50 200)'),\n" @@ -1562,7 +1611,9 @@ msgstr "" #, no-c-format msgid "" "--When used in 3d doesn't quite do the right thing\n" -"SELECT ST_AsEWKT(ST_Difference(ST_GeomFromEWKT('MULTIPOINT(-118.58 38.38 5,-118.60 38.329 6,-118.614 38.281 7)'), ST_GeomFromEWKT('POINT(-118.614 38.281 5)')));\n" +"SELECT ST_AsEWKT(ST_Difference(ST_GeomFromEWKT('MULTIPOINT(-118.58 38.38 " +"5,-118.60 38.329 6,-118.614 38.281 7)'), ST_GeomFromEWKT('POINT(-118.614 " +"38.281 5)')));\n" "st_asewkt\n" "---------\n" "MULTIPOINT(-118.6 38.329 6,-118.58 38.38 5)" @@ -1597,9 +1648,9 @@ msgid "" "rows, formed by a geometry (geom) and an array of integers (path). When the " "input geometry is a simple type (POINT,LINESTRING,POLYGON) a single record " "will be returned with an empty path array and the input geometry as geom. " -"When the input geometry is a collection or multi it will return a record for" -" each of the collection components, and the path will express the position " -"of the component inside the collection." +"When the input geometry is a collection or multi it will return a record for " +"each of the collection components, and the path will express the position of " +"the component inside the collection." msgstr "" #. Tag: para @@ -1655,10 +1706,12 @@ msgid "" " (ST_Dump(sometable.the_geom)).geom AS the_geom\n" "FROM sometable;\n" "\n" -"-- Break a compound curve into its constituent linestrings and circularstrings\n" +"-- Break a compound curve into its constituent linestrings and " +"circularstrings\n" "SELECT ST_AsEWKT(a.geom), ST_HasArc(a.geom)\n" " FROM ( SELECT (ST_Dump(p_geom)).geom AS geom\n" -" FROM (SELECT ST_GeomFromEWKT('COMPOUNDCURVE(CIRCULARSTRING(0 0, 1 1, 1 0),(1 0, 0 1))') AS p_geom) AS b\n" +" FROM (SELECT ST_GeomFromEWKT('COMPOUNDCURVE(CIRCULARSTRING(0 0, 1 " +"1, 1 0),(1 0, 0 1))') AS p_geom) AS b\n" " ) AS a;\n" " st_asewkt | st_hasarc\n" "-----------------------------+----------\n" @@ -1682,8 +1735,10 @@ msgid "" "SELECT (a.p_geom).path[1] As path, ST_AsEWKT((a.p_geom).geom) As geom_ewkt\n" " FROM (SELECT ST_Dump(ST_GeomFromEWKT('POLYHEDRALSURFACE( \n" "((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)), \n" -"((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 0)), ((1 1 0, 1 1 1, 1 0 1, 1 0 0, 1 1 0)), \n" -"((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 1)) \n" +"((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 " +"0)), ((1 1 0, 1 1 1, 1 0 1, 1 0 0, 1 1 0)), \n" +"((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 " +"1)) \n" ")') ) AS p_geom ) AS a;\n" "\n" " path | geom_ewkt\n" @@ -1728,9 +1783,9 @@ msgstr "" #: reference_processing.xml:902 #, no-c-format msgid "" -", , , , " +", , , , " msgstr "" #. Tag: refname @@ -1743,8 +1798,8 @@ msgstr "" #: reference_processing.xml:909 #, no-c-format msgid "" -"Returns a set of geometry_dump (geom,path) rows of all points that make up a" -" geometry." +"Returns a set of geometry_dump (geom,path) rows of all points that make up a " +"geometry." msgstr "" #. Tag: funcprototype @@ -1759,35 +1814,34 @@ msgstr "" #: reference_processing.xml:923 #, no-c-format msgid "" -"This set-returning function (SRF) returns a set of " -"geometry_dump rows formed by a geometry " -"(geom) and an array of integers " -"(path)." +"This set-returning function (SRF) returns a set of geometry_dump rows formed by a geometry (geom) and an array of " +"integers (path)." msgstr "" #. Tag: para #: reference_processing.xml:926 #, no-c-format msgid "" -"The geom component of " -"geometry_dump are all the POINTs that " -"make up the supplied geometry" +"The geom component of geometry_dump are all the POINTs that make up the supplied " +"geometry" msgstr "" #. Tag: para #: reference_processing.xml:929 #, no-c-format msgid "" -"The path component of " -"geometry_dump (an integer[]) is an " -"index reference enumerating the POINTs of the supplied " -"geometry. For example, if a LINESTRING is supplied, a " -"path of {i} is returned where i is the" -" nth coordinate in the LINESTRING. If " -"a POLYGON is supplied, a path of {i,j}" -" is returned where i is the ring number (1 is outer; " -"inner rings follow) and j enumerates the " -"POINTs (again 1-based index)." +"The path component of geometry_dump (an integer[]) is an index reference enumerating " +"the POINTs of the supplied geometry. For example, if a " +"LINESTRING is supplied, a path of {i} " +"is returned where i is the nth " +"coordinate in the LINESTRING. If a POLYGON is supplied, a path of {i,j} is returned where " +"i is the ring number (1 is outer; inner rings follow) and " +"j enumerates the POINTs (again 1-based " +"index)." msgstr "" #. Tag: para @@ -1814,10 +1868,12 @@ msgstr "" msgid "" "SELECT edge_id, (dp).path[1] As index, ST_AsText((dp).geom) As wktnode\n" "FROM (SELECT 1 As edge_id\n" -" , ST_DumpPoints(ST_GeomFromText('LINESTRING(1 2, 3 4, 10 10)')) AS dp\n" +" , ST_DumpPoints(ST_GeomFromText('LINESTRING(1 2, 3 4, 10 10)')) AS " +"dp\n" " UNION ALL\n" " SELECT 2 As edge_id\n" -" , ST_DumpPoints(ST_GeomFromText('LINESTRING(3 5, 5 6, 9 10)')) AS dp\n" +" , ST_DumpPoints(ST_GeomFromText('LINESTRING(3 5, 5 6, 9 10)')) AS " +"dp\n" " ) As foo;\n" " edge_id | index | wktnode\n" "---------+-------+--------------\n" @@ -1901,10 +1957,13 @@ msgid "" "SELECT (g.gdump).path, ST_AsEWKT((g.gdump).geom) as wkt\n" " FROM\n" " (SELECT \n" -" ST_DumpPoints(ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)), \n" -"((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 0)), \n" +" ST_DumpPoints(ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 " +"1, 0 1 0, 0 0 0)), \n" +"((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 " +"0)), \n" "((1 1 0, 1 1 1, 1 0 1, 1 0 0, 1 1 0)), \n" -"((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 1)) )') ) AS gdump\n" +"((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 " +"1)) )') ) AS gdump\n" " ) AS g;\n" "-- result --\n" " path | wkt\n" @@ -2005,8 +2064,8 @@ msgstr "" #: reference_processing.xml:970 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -2036,11 +2095,11 @@ msgstr "" #, no-c-format msgid "" "This is a set-returning function (SRF). It returns a set of " -"geometry_dump rows, defined as an " -"integer[] and a geometry, aliased " -"\"path\" and \"geom\" respectively. The \"path\" field holds the polygon " -"ring index containing a single integer: 0 for the shell, >0 for holes. The " -"\"geom\" field contains the corresponding ring as a polygon." +"geometry_dump rows, defined as an integer[] and a geometry, aliased \"path\" and \"geom\" " +"respectively. The \"path\" field holds the polygon ring index containing a " +"single integer: 0 for the shell, >0 for holes. The \"geom\" field contains " +"the corresponding ring as a polygon." msgstr "" #. Tag: para @@ -2066,29 +2125,37 @@ msgid "" "\n" "SELECT ST_AsEWKT(geom) As the_geom, path\n" " FROM ST_DumpRings(\n" -" ST_GeomFromEWKT('POLYGON((-8149064 5133092 1,-8149064 5132986 1,-8148996 5132839 1,-8148972 5132767 1,-8148958 5132508 1,-8148941 5132466 1,-8148924 5132394 1,\n" -" -8148903 5132210 1,-8148930 5131967 1,-8148992 5131978 1,-8149237 5132093 1,-8149404 5132211 1,-8149647 5132310 1,-8149757 5132394 1,\n" +" ST_GeomFromEWKT('POLYGON((-8149064 5133092 1,-8149064 " +"5132986 1,-8148996 5132839 1,-8148972 5132767 1,-8148958 5132508 1,-8148941 " +"5132466 1,-8148924 5132394 1,\n" +" -8148903 5132210 1,-8148930 5131967 1,-8148992 5131978 " +"1,-8149237 5132093 1,-8149404 5132211 1,-8149647 5132310 1,-8149757 5132394 " +"1,\n" " -8150305 5132788 1,-8149064 5133092 1),\n" -" (-8149362 5132394 1,-8149446 5132501 1,-8149548 5132597 1,-8149695 5132675 1,-8149362 5132394 1))')\n" +" (-8149362 5132394 1,-8149446 5132501 1,-8149548 5132597 " +"1,-8149695 5132675 1,-8149362 5132394 1))')\n" " ) as foo;\n" " path | the_geom\n" "----------------------------------------------------------------------------------------------------------------\n" -" {0} | POLYGON((-8149064 5133092 1,-8149064 5132986 1,-8148996 5132839 1,-8148972 5132767 1,-8148958 5132508 1,\n" +" {0} | POLYGON((-8149064 5133092 1,-8149064 5132986 1,-8148996 5132839 " +"1,-8148972 5132767 1,-8148958 5132508 1,\n" " | -8148941 5132466 1,-8148924 5132394 1,\n" " | -8148903 5132210 1,-8148930 5131967 1,\n" " | -8148992 5131978 1,-8149237 5132093 1,\n" -" | -8149404 5132211 1,-8149647 5132310 1,-8149757 5132394 1,-8150305 5132788 1,-8149064 5133092 1))\n" +" | -8149404 5132211 1,-8149647 5132310 1,-8149757 5132394 " +"1,-8150305 5132788 1,-8149064 5133092 1))\n" " {1} | POLYGON((-8149362 5132394 1,-8149446 5132501 1,\n" -" | -8149548 5132597 1,-8149695 5132675 1,-8149362 5132394 1))" +" | -8149548 5132597 1,-8149695 5132675 1,-8149362 5132394 " +"1))" msgstr "" #. Tag: para #: reference_processing.xml:1015 #, no-c-format msgid "" -", , , , " +", , , , " msgstr "" #. Tag: refname @@ -2223,15 +2290,13 @@ msgstr "" #: reference_processing.xml:1118 #, no-c-format msgid "" -" geometry " -"ST_Intersection " -"geometry geomA " -"geometry geomB " -" geography " -"ST_Intersection " -"geography geogA " -"geography geogB " -"" +" geometry ST_Intersection geometry geomA geometry geomB geography " +"ST_Intersection geography geogA geography geogB " msgstr "" #. Tag: para @@ -2264,8 +2329,8 @@ msgstr "" msgid "" "ST_Intersection in conjunction with ST_Intersects is very useful for " "clipping geometries such as in bounding box, buffer, region queries where " -"you only want to return that portion of a geometry that sits in a country or" -" region of interest." +"you only want to return that portion of a geometry that sits in a country or " +"region of interest." msgstr "" #. Tag: para @@ -2273,8 +2338,8 @@ msgstr "" #, no-c-format msgid "" "Geography: For geography this is really a thin wrapper around the geometry " -"implementation. It first determines the best SRID that fits the bounding box" -" of the 2 geography objects (if geography objects are within one half zone " +"implementation. It first determines the best SRID that fits the bounding box " +"of the 2 geography objects (if geography objects are within one half zone " "UTM but not same UTM will pick one of those) (favoring UTM or Lambert " "Azimuthal Equal Area (LAEA) north/south pole, and falling back on mercator " "in worst case scenario) and then intersection in that best fit planar " @@ -2284,8 +2349,7 @@ msgstr "" #. Tag: para #: reference_processing.xml:1159 #, no-c-format -msgid "" -"Do not call with a GEOMETRYCOLLECTION as an argument" +msgid "Do not call with a GEOMETRYCOLLECTION as an argument" msgstr "" #. Tag: para @@ -2296,9 +2360,9 @@ msgid "" "linkend=\"ST_3DIntersection\"/> which does a proper 3D intersection for 3D " "geometries. Although this function works with Z-coordinate, it does an " "averaging of Z-Coordinate values when postgis.backend=geos. " -"postgis.backend=sfcgal, it will return a 2D geometry regardless" -" ignoring the Z-Coordinate. Refer to for" -" details." +"postgis.backend=sfcgal, it will return a 2D geometry regardless " +"ignoring the Z-Coordinate. Refer to for " +"details." msgstr "" #. Tag: para @@ -2323,41 +2387,52 @@ msgstr "" #: reference_processing.xml:1174 #, no-c-format msgid "" -"SELECT ST_AsText(ST_Intersection('POINT(0 0)'::geometry, 'LINESTRING ( 2 0, 0 2 )'::geometry));\n" +"SELECT ST_AsText(ST_Intersection('POINT(0 0)'::geometry, 'LINESTRING ( 2 0, " +"0 2 )'::geometry));\n" " st_astext\n" "---------------\n" "GEOMETRYCOLLECTION EMPTY\n" "(1 row)\n" -"SELECT ST_AsText(ST_Intersection('POINT(0 0)'::geometry, 'LINESTRING ( 0 0, 0 2 )'::geometry));\n" +"SELECT ST_AsText(ST_Intersection('POINT(0 0)'::geometry, 'LINESTRING ( 0 0, " +"0 2 )'::geometry));\n" " st_astext\n" "---------------\n" "POINT(0 0)\n" "(1 row)\n" "\n" -"---Clip all lines (trails) by country (here we assume country geom are POLYGON or MULTIPOLYGONS)\n" -"-- NOTE: we are only keeping intersections that result in a LINESTRING or MULTILINESTRING because we don't\n" +"---Clip all lines (trails) by country (here we assume country geom are " +"POLYGON or MULTIPOLYGONS)\n" +"-- NOTE: we are only keeping intersections that result in a LINESTRING or " +"MULTILINESTRING because we don't\n" "-- care about trails that just share a point\n" -"-- the dump is needed to expand a geometry collection into individual single MULT* parts\n" -"-- the below is fairly generic and will work for polys, etc. by just changing the where clause\n" +"-- the dump is needed to expand a geometry collection into individual single " +"MULT* parts\n" +"-- the below is fairly generic and will work for polys, etc. by just " +"changing the where clause\n" "SELECT clipped.gid, clipped.f_name, clipped_geom\n" -"FROM (SELECT trails.gid, trails.f_name, (ST_Dump(ST_Intersection(country.the_geom, trails.the_geom))).geom As clipped_geom\n" +"FROM (SELECT trails.gid, trails.f_name, (ST_Dump(ST_Intersection(country." +"the_geom, trails.the_geom))).geom As clipped_geom\n" "FROM country\n" " INNER JOIN trails\n" " ON ST_Intersects(country.the_geom, trails.the_geom)) As clipped\n" " WHERE ST_Dimension(clipped.clipped_geom) = 1 ;\n" "\n" -"--For polys e.g. polygon landmarks, you can also use the sometimes faster hack that buffering anything by 0.0\n" +"--For polys e.g. polygon landmarks, you can also use the sometimes faster " +"hack that buffering anything by 0.0\n" "-- except a polygon results in an empty geometry collection\n" "--(so a geometry collection containing polys, lines and points)\n" -"-- buffered by 0.0 would only leave the polygons and dissolve the collection shell\n" +"-- buffered by 0.0 would only leave the polygons and dissolve the collection " +"shell\n" "SELECT poly.gid, ST_Multi(ST_Buffer(\n" -" ST_Intersection(country.the_geom, poly.the_geom),\n" +" ST_Intersection(country.the_geom, poly." +"the_geom),\n" " 0.0)\n" " ) As clipped_geom\n" "FROM country\n" " INNER JOIN poly\n" " ON ST_Intersects(country.the_geom, poly.the_geom)\n" -" WHERE Not ST_IsEmpty(ST_Buffer(ST_Intersection(country.the_geom, poly.the_geom),0.0));" +" WHERE Not ST_IsEmpty(ST_Buffer(ST_Intersection(country.the_geom, " +"poly.the_geom),0.0));" msgstr "" #. Tag: title @@ -2371,8 +2446,8 @@ msgstr "" #, no-c-format msgid "" "Geos is the default backend if not set. Note this is not a true " -"intersection, compare to the same example using ." +"intersection, compare to the same example using ." msgstr "" #. Tag: programlisting @@ -2381,8 +2456,10 @@ msgstr "" msgid "" "set postgis.backend=geos; \n" "select ST_AsText(ST_Intersection(linestring, polygon)) As wkt\n" -"from ST_GeomFromText('LINESTRING Z (2 2 6,1.5 1.5 7,1 1 8,0.5 0.5 8,0 0 10)') AS linestring\n" -" CROSS JOIN ST_GeomFromText('POLYGON((0 0 8, 0 1 8, 1 1 8, 1 0 8, 0 0 8))') AS polygon;\n" +"from ST_GeomFromText('LINESTRING Z (2 2 6,1.5 1.5 7,1 1 8,0.5 0.5 8,0 0 " +"10)') AS linestring\n" +" CROSS JOIN ST_GeomFromText('POLYGON((0 0 8, 0 1 8, 1 1 8, 1 0 8, 0 0 8))') " +"AS polygon;\n" "\n" " st_astext\n" "---------------------------------------\n" @@ -2405,8 +2482,10 @@ msgstr "" msgid "" "set postgis.backend=sfcgal; \n" "select ST_AsText(ST_Intersection(linestring, polygon)) As wkt\n" -"from ST_GeomFromText('LINESTRING Z (2 2 6,1.5 1.5 7,1 1 8,0.5 0.5 8,0 0 10)') AS linestring\n" -" CROSS JOIN ST_GeomFromText('POLYGON((0 0 8, 0 1 8, 1 1 8, 1 0 8, 0 0 8))') AS polygon;\n" +"from ST_GeomFromText('LINESTRING Z (2 2 6,1.5 1.5 7,1 1 8,0.5 0.5 8,0 0 " +"10)') AS linestring\n" +" CROSS JOIN ST_GeomFromText('POLYGON((0 0 8, 0 1 8, 1 1 8, 1 0 8, 0 0 8))') " +"AS polygon;\n" "\n" " wkt\n" "----------------------------------------------\n" @@ -2417,10 +2496,10 @@ msgstr "" #: reference_processing.xml:1188 #, no-c-format msgid "" -", , , , , , , " +", , , , , , , " msgstr "" #. Tag: refname @@ -2440,8 +2519,8 @@ msgstr "" #, no-c-format msgid "" "geometry ST_LineToCurve " -"geometry " -"geomANoncircular" +"geometry geomANoncircular" msgstr "" #. Tag: para @@ -2462,21 +2541,34 @@ msgstr "" #: reference_processing.xml:1222 #, no-c-format msgid "" -"SELECT ST_AsText(ST_LineToCurve(foo.the_geom)) As curvedastext,ST_AsText(foo.the_geom) As non_curvedastext\n" -" FROM (SELECT ST_Buffer('POINT(1 3)'::geometry, 3) As the_geom) As foo;\n" +"SELECT ST_AsText(ST_LineToCurve(foo.the_geom)) As curvedastext,ST_AsText(foo." +"the_geom) As non_curvedastext\n" +" FROM (SELECT ST_Buffer('POINT(1 3)'::geometry, 3) As the_geom) As " +"foo;\n" "\n" -"curvedatext non_curvedastext\n" +"curvedatext " +"non_curvedastext\n" "--------------------------------------------------------------------|-----------------------------------------------------------------\n" -"CURVEPOLYGON(CIRCULARSTRING(4 3,3.12132034355964 0.878679656440359, | POLYGON((4 3,3.94235584120969 2.41472903395162,3.77163859753386 1.85194970290473,\n" -"1 0,-1.12132034355965 5.12132034355963,4 3)) | 3.49440883690764 1.33328930094119,3.12132034355964 0.878679656440359,\n" -" | 2.66671069905881 0.505591163092366,2.14805029709527 0.228361402466141,\n" -" | 1.58527096604839 0.0576441587903094,1 0,\n" -" | 0.414729033951621 0.0576441587903077,-0.148050297095264 0.228361402466137,\n" -" | -0.666710699058802 0.505591163092361,-1.12132034355964 0.878679656440353,\n" -" | -1.49440883690763 1.33328930094119,-1.77163859753386 1.85194970290472\n" -" | --ETC-- ,3.94235584120969 3.58527096604839,4 3))\n" +"CURVEPOLYGON(CIRCULARSTRING(4 3,3.12132034355964 0.878679656440359, | " +"POLYGON((4 3,3.94235584120969 2.41472903395162,3.77163859753386 " +"1.85194970290473,\n" +"1 0,-1.12132034355965 5.12132034355963,4 3)) | " +"3.49440883690764 1.33328930094119,3.12132034355964 0.878679656440359,\n" +" | " +"2.66671069905881 0.505591163092366,2.14805029709527 0.228361402466141,\n" +" | " +"1.58527096604839 0.0576441587903094,1 0,\n" +" | " +"0.414729033951621 0.0576441587903077,-0.148050297095264 0.228361402466137,\n" +" | " +"-0.666710699058802 0.505591163092361,-1.12132034355964 0.878679656440353,\n" +" | " +"-1.49440883690763 1.33328930094119,-1.77163859753386 1.85194970290472\n" +" | --" +"ETC-- ,3.94235584120969 3.58527096604839,4 3))\n" "--3D example\n" -"SELECT ST_AsEWKT(ST_LineToCurve(ST_GeomFromEWKT('LINESTRING(1 2 3, 3 4 8, 5 6 4, 7 8 4, 9 10 4)')));\n" +"SELECT ST_AsEWKT(ST_LineToCurve(ST_GeomFromEWKT('LINESTRING(1 2 3, 3 4 8, 5 " +"6 4, 7 8 4, 9 10 4)')));\n" "\n" " st_asewkt\n" "------------------------------------\n" @@ -2524,8 +2616,8 @@ msgstr "" #: reference_processing.xml:1264 #, no-c-format msgid "" -"In case of full or partial dimensional collapses, the output geometry may be" -" a collection of lower-to-equal dimension geometries or a geometry of lower " +"In case of full or partial dimensional collapses, the output geometry may be " +"a collection of lower-to-equal dimension geometries or a geometry of lower " "dimension." msgstr "" @@ -2573,8 +2665,8 @@ msgstr "" #, no-c-format msgid "" "geometry ST_MemUnion " -"geometry set " -"geomfield" +"geometry set geomfield" msgstr "" #. Tag: para @@ -2589,8 +2681,8 @@ msgstr "" msgid "" "Same as ST_Union, only memory-friendly (uses less memory and more processor " "time). This aggregate function works by unioning the geometries one at a " -"time to previous result as opposed to ST_Union aggregate which first creates" -" an array and then unions" +"time to previous result as opposed to ST_Union aggregate which first creates " +"an array and then unions" msgstr "" #. Tag: programlisting @@ -2634,8 +2726,8 @@ msgstr "" #, no-c-format msgid "" "The circle is approximated by a polygon with a default of 48 segments per " -"quarter circle. This number can be increased with little performance penalty" -" to obtain a more accurate result." +"quarter circle. This number can be increased with little performance penalty " +"to obtain a more accurate result." msgstr "" #. Tag: para @@ -2643,8 +2735,8 @@ msgstr "" #, no-c-format msgid "" "It is often used with MULTI and Geometry Collections. Although it is not an " -"aggregate - you can use it in conjunction with ST_Collect to get the minimum" -" bounding circle of a set of geometries. " +"aggregate - you can use it in conjunction with ST_Collect to get the minimum " +"bounding circle of a set of geometries. " "ST_MinimumBoundingCircle(ST_Collect(somepointfield))." msgstr "" @@ -2691,10 +2783,25 @@ msgid "" " )) As wktmbc;\n" "wktmbc\n" "-----------\n" -"POLYGON((135.59714732062 115,134.384753327498 102.690357210921,130.79416296937 90.8537670908995,124.963360620072 79.9451031602111,117.116420743937 70.3835792560632,107.554896839789 62.5366393799277,96.6462329091006 56.70583703063,84.8096427890789 53.115246672502,72.5000000000001 51.9028526793802,60.1903572109213 53.1152466725019,48.3537670908996 56.7058370306299,37.4451031602112 62.5366393799276,27.8835792560632 70.383579256063,20.0366393799278 79.9451031602109,14.20583703063 90.8537670908993,10.615246672502 102.690357210921,9.40285267938019 115,10.6152466725019 127.309642789079,14.2058370306299 139.1462329091,20.0366393799275 150.054896839789,27.883579256063 159.616420743937,\n" -"37.4451031602108 167.463360620072,48.3537670908992 173.29416296937,60.190357210921 176.884753327498,\n" -"72.4999999999998 178.09714732062,84.8096427890786 176.884753327498,96.6462329091003 173.29416296937,107.554896839789 167.463360620072,\n" -"117.116420743937 159.616420743937,124.963360620072 150.054896839789,130.79416296937 139.146232909101,134.384753327498 127.309642789079,135.59714732062 115))" +"POLYGON((135.59714732062 115,134.384753327498 " +"102.690357210921,130.79416296937 90.8537670908995,124.963360620072 " +"79.9451031602111,117.116420743937 70.3835792560632,107.554896839789 " +"62.5366393799277,96.6462329091006 56.70583703063,84.8096427890789 " +"53.115246672502,72.5000000000001 51.9028526793802,60.1903572109213 " +"53.1152466725019,48.3537670908996 56.7058370306299,37.4451031602112 " +"62.5366393799276,27.8835792560632 70.383579256063,20.0366393799278 " +"79.9451031602109,14.20583703063 90.8537670908993,10.615246672502 " +"102.690357210921,9.40285267938019 115,10.6152466725019 " +"127.309642789079,14.2058370306299 139.1462329091,20.0366393799275 " +"150.054896839789,27.883579256063 159.616420743937,\n" +"37.4451031602108 167.463360620072,48.3537670908992 " +"173.29416296937,60.190357210921 176.884753327498,\n" +"72.4999999999998 178.09714732062,84.8096427890786 " +"176.884753327498,96.6462329091003 173.29416296937,107.554896839789 " +"167.463360620072,\n" +"117.116420743937 159.616420743937,124.963360620072 " +"150.054896839789,130.79416296937 139.146232909101,134.384753327498 " +"127.309642789079,135.59714732062 115))" msgstr "" #. Tag: para @@ -2721,13 +2828,11 @@ msgstr "" #: reference_processing.xml:1402 #, no-c-format msgid "" -" geometry " -"ST_Polygonize geometry " -"set geomfield " -" geometry " -"ST_Polygonize " -"geometry[] " -"geom_array " +" geometry ST_Polygonize geometry set geomfield geometry " +"ST_Polygonize geometry[] geom_array " msgstr "" #. Tag: para @@ -2764,12 +2869,15 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_AsEWKT(ST_Polygonize(the_geom_4269)) As geomtextrep\n" -"FROM (SELECT the_geom_4269 FROM ma.suffolk_edges ORDER BY tlid LIMIT 45) As foo;\n" +"FROM (SELECT the_geom_4269 FROM ma.suffolk_edges ORDER BY tlid LIMIT 45) As " +"foo;\n" "\n" "geomtextrep\n" "-------------------------------------\n" -" SRID=4269;GEOMETRYCOLLECTION(POLYGON((-71.040878 42.285678,-71.040943 42.2856,-71.04096 42.285752,-71.040878 42.285678)),\n" -" POLYGON((-71.17166 42.353675,-71.172026 42.354044,-71.17239 42.354358,-71.171794 42.354971,-71.170511 42.354855,\n" +" SRID=4269;GEOMETRYCOLLECTION(POLYGON((-71.040878 42.285678,-71.040943 " +"42.2856,-71.04096 42.285752,-71.040878 42.285678)),\n" +" POLYGON((-71.17166 42.353675,-71.172026 42.354044,-71.17239 " +"42.354358,-71.171794 42.354971,-71.170511 42.354855,\n" " -71.17112 42.354238,-71.17166 42.353675)))\n" "(1 row)\n" "\n" @@ -2781,10 +2889,13 @@ msgid "" "\n" "geomtextrep\n" "------------------------\n" -" SRID=4269;POLYGON((-71.040878 42.285678,-71.040943 42.2856,-71.04096 42.285752,\n" +" SRID=4269;POLYGON((-71.040878 42.285678,-71.040943 42.2856,-71.04096 " +"42.285752,\n" "-71.040878 42.285678))\n" -" SRID=4269;POLYGON((-71.17166 42.353675,-71.172026 42.354044,-71.17239 42.354358\n" -",-71.171794 42.354971,-71.170511 42.354855,-71.17112 42.354238,-71.17166 42.353675))\n" +" SRID=4269;POLYGON((-71.17166 42.353675,-71.172026 42.354044,-71.17239 " +"42.354358\n" +",-71.171794 42.354971,-71.170511 42.354855,-71.17112 42.354238,-71.17166 " +"42.353675))\n" "(2 rows)" msgstr "" @@ -2835,11 +2946,13 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_AsEWKT(\n" -" ST_Node('LINESTRINGZ(0 0 0, 10 10 10, 0 10 5, 10 0 3)'::geometry)\n" +" ST_Node('LINESTRINGZ(0 0 0, 10 10 10, 0 10 5, 10 0 3)'::" +"geometry)\n" " ) As output;\n" "output\n" "-----------\n" -"MULTILINESTRING((0 0 0,5 5 4.5),(5 5 4.5,10 10 10,0 10 5,5 5 4.5),(5 5 4.5,10 0 3))" +"MULTILINESTRING((0 0 0,5 5 4.5),(5 5 4.5,10 10 10,0 10 5,5 5 4.5),(5 5 " +"4.5,10 0 3))" msgstr "" #. Tag: refname @@ -2862,9 +2975,8 @@ msgstr "" msgid "" "geometry ST_OffsetCurve " "geometry line " -"float " -"signed_distance text " +"float signed_distance text " "style_parameters=''" msgstr "" @@ -2882,8 +2994,8 @@ msgstr "" #, no-c-format msgid "" "For positive distance the offset will be at the left side of the input line " -"and retain the same direction. For a negative distance it'll be at the right" -" side and in the opposite direction." +"and retain the same direction. For a negative distance it'll be at the right " +"side and in the opposite direction." msgstr "" #. Tag: para @@ -3003,8 +3115,8 @@ msgstr "" #: reference_processing.xml:1607 #, no-c-format msgid "" -"double-offset to get more curvy, note the first reverses direction, so -30 +" -" 15 = -15" +"double-offset to get more curvy, note the first reverses direction, so -30 + " +"15 = -15" msgstr "" #. Tag: programlisting @@ -3012,7 +3124,8 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_AsText(ST_OffsetCurve(ST_OffsetCurve(geom,\n" -" -30, 'quad_segs=4 join=round'), -15, 'quad_segs=4 join=round')) As morecurvy\n" +" -30, 'quad_segs=4 join=round'), -15, 'quad_segs=4 join=round')) As " +"morecurvy\n" " FROM ST_GeomFromText(\n" "'LINESTRING(164 16,144 16,124 16,104 16,84 16,64 16,\n" " 44 16,24 16,20 16,18 16,17 17,\n" @@ -3051,7 +3164,8 @@ msgid "" "MULTILINESTRING((164 1,18 1,12.2597485145237 2.1418070123307,\n" "7.39339828220179 5.39339828220179,5.39339828220179 7.39339828220179,\n" "2.14180701233067 12.2597485145237,1 18,1 195),\n" -"(164 31,46 31,40.2597485145236 32.1418070123307,35.3933982822018 35.3933982822018,\n" +"(164 31,46 31,40.2597485145236 32.1418070123307,35.3933982822018 " +"35.3933982822018,\n" "32.1418070123307 40.2597485145237,31 46,31 195))" msgstr "" @@ -3109,8 +3223,7 @@ msgstr "" #. Tag: refpurpose #: reference_processing.xml:1661 #, no-c-format -msgid "" -"Returns a version of the given geometry with duplicated points removed." +msgid "Returns a version of the given geometry with duplicated points removed." msgstr "" #. Tag: funcprototype @@ -3119,16 +3232,16 @@ msgstr "" msgid "" "geometry ST_RemoveRepeatedPoints " "geometry geom " -"float8 " -"tolerance" +"float8 tolerance" msgstr "" #. Tag: para #: reference_processing.xml:1677 #, no-c-format msgid "" -"Returns a version of the given geometry with duplicated points removed. Will" -" actually do something only with (multi)lines, (multi)polygons and " +"Returns a version of the given geometry with duplicated points removed. Will " +"actually do something only with (multi)lines, (multi)polygons and " "multipoints but you can safely call it with any kind of geometry. Since " "simplification occurs on a object-by-object basis you can also feed a " "GeometryCollection to this function." @@ -3138,8 +3251,8 @@ msgstr "" #: reference_processing.xml:1683 #, no-c-format msgid "" -"If the tolerance parameter is provided, vertices within the tolerance of one" -" another will be considered the \"same\" for the purposes of removal." +"If the tolerance parameter is provided, vertices within the tolerance of one " +"another will be considered the \"same\" for the purposes of removal." msgstr "" #. Tag: refname @@ -3152,8 +3265,8 @@ msgstr "" #: reference_processing.xml:1700 #, no-c-format msgid "" -"Returns a collection containing paths shared by the two input " -"linestrings/multilinestrings." +"Returns a collection containing paths shared by the two input linestrings/" +"multilinestrings." msgstr "" #. Tag: funcprototype @@ -3171,8 +3284,8 @@ msgstr "" msgid "" "Returns a collection containing paths shared by the two input geometries. " "Those going in the same direction are in the first element of the " -"collection, those going in the opposite direction are in the second element." -" The paths themselves are given in the direction of the first geometry." +"collection, those going in the opposite direction are in the second element. " +"The paths themselves are given in the direction of the first geometry." msgstr "" #. Tag: para @@ -3207,9 +3320,11 @@ msgstr "" msgid "" "SELECT ST_AsText(\n" " ST_SharedPaths(\n" -" ST_GeomFromText('MULTILINESTRING((26 125,26 200,126 200,126 125,26 125),\n" +" ST_GeomFromText('MULTILINESTRING((26 125,26 200,126 200,126 125,26 " +"125),\n" " (51 150,101 150,76 175,51 150))'),\n" -" ST_GeomFromText('LINESTRING(151 100,126 156.25,126 125,90 161, 76 175)')\n" +" ST_GeomFromText('LINESTRING(151 100,126 156.25,126 125,90 161, 76 " +"175)')\n" " )\n" " ) As wkt\n" "\n" @@ -3241,7 +3356,8 @@ msgstr "" #. Tag: para #: reference_processing.xml:1763 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -3295,8 +3411,7 @@ msgstr "" #. Tag: para #: reference_processing.xml:1804 #, no-c-format -msgid "" -"Enhanced: 2.0.0 support for Polyhedral surfaces and TIN was introduced." +msgid "Enhanced: 2.0.0 support for Polyhedral surfaces and TIN was introduced." msgstr "" #. Tag: para @@ -3310,14 +3425,17 @@ msgstr "" #, no-c-format msgid "" "--3d points\n" -"SELECT ST_AsEWKT(ST_ShiftLongitude(ST_GeomFromEWKT('SRID=4326;POINT(-118.58 38.38 10)'))) As geomA,\n" -" ST_AsEWKT(ST_ShiftLongitude(ST_GeomFromEWKT('SRID=4326;POINT(241.42 38.38 10)'))) As geomb\n" +"SELECT ST_AsEWKT(ST_ShiftLongitude(ST_GeomFromEWKT('SRID=4326;POINT(-118.58 " +"38.38 10)'))) As geomA,\n" +" ST_AsEWKT(ST_ShiftLongitude(ST_GeomFromEWKT('SRID=4326;POINT(241.42 " +"38.38 10)'))) As geomb\n" "geomA geomB\n" "---------- -----------\n" "SRID=4326;POINT(241.42 38.38 10) SRID=4326;POINT(-118.58 38.38 10)\n" "\n" "--regular line string\n" -"SELECT ST_AsText(ST_ShiftLongitude(ST_GeomFromText('LINESTRING(-118.58 38.38, -118.20 38.45)')))\n" +"SELECT ST_AsText(ST_ShiftLongitude(ST_GeomFromText('LINESTRING(-118.58 " +"38.38, -118.20 38.45)')))\n" "\n" "st_astext\n" "----------\n" @@ -3369,8 +3487,8 @@ msgstr "" #: reference_processing.xml:1987 #, no-c-format msgid "" -"Note that returned geometry might loose its simplicity (see )" +"Note that returned geometry might loose its simplicity (see )" msgstr "" #. Tag: para @@ -3378,8 +3496,8 @@ msgstr "" #: reference_processing.xml:1989 #, no-c-format msgid "" -"Note topology may not be preserved and may result in invalid geometries. Use" -" (see ) to preserve topology." +"Note topology may not be preserved and may result in invalid geometries. Use " +"(see ) to preserve topology." msgstr "" #. Tag: para @@ -3398,22 +3516,28 @@ msgstr "" #: reference_processing.xml:1860 #, no-c-format msgid "" -"SELECT ST_Npoints(the_geom) As np_before, ST_NPoints(ST_Simplify(the_geom,0.1)) As np01_notbadcircle, ST_NPoints(ST_Simplify(the_geom,0.5)) As np05_notquitecircle,\n" -"ST_NPoints(ST_Simplify(the_geom,1)) As np1_octagon, ST_NPoints(ST_Simplify(the_geom,10)) As np10_triangle,\n" +"SELECT ST_Npoints(the_geom) As np_before, " +"ST_NPoints(ST_Simplify(the_geom,0.1)) As np01_notbadcircle, " +"ST_NPoints(ST_Simplify(the_geom,0.5)) As np05_notquitecircle,\n" +"ST_NPoints(ST_Simplify(the_geom,1)) As np1_octagon, " +"ST_NPoints(ST_Simplify(the_geom,10)) As np10_triangle,\n" "(ST_Simplify(the_geom,100) is null) As np100_geometrygoesaway\n" "FROM (SELECT ST_Buffer('POINT(1 3)', 10,12) As the_geom) As foo;\n" "-result\n" -" np_before | np01_notbadcircle | np05_notquitecircle | np1_octagon | np10_triangle | np100_geometrygoesaway\n" -"-----------+-------------------+---------------------+-------------+---------------+------------------------\n" -" 49 | 33 | 17 | 9 | 4 | t" +" np_before | np01_notbadcircle | np05_notquitecircle | np1_octagon | " +"np10_triangle | np100_geometrygoesaway\n" +"-----------+-------------------+---------------------+-------------" +"+---------------+------------------------\n" +" 49 | 33 | 17 | 9 " +"| 4 | t" msgstr "" #. Tag: para #: reference_processing.xml:1864 #, no-c-format msgid "" -", , Topology " +", , Topology " msgstr "" #. Tag: refname @@ -3435,8 +3559,8 @@ msgstr "" #: reference_processing.xml:1878 #, no-c-format msgid "" -"geometry ST_SimplifyPreserveTopology" -" geometry geomA " +"geometry ST_SimplifyPreserveTopology " +"geometry geomA " "float tolerance" msgstr "" @@ -3447,8 +3571,8 @@ msgid "" "Returns a \"simplified\" version of the given geometry using the Douglas-" "Peucker algorithm. Will avoid creating derived geometries (polygons in " "particular) that are invalid. Will actually do something only with " -"(multi)lines and (multi)polygons but you can safely call it with any kind of" -" geometry. Since simplification occurs on a object-by-object basis you can " +"(multi)lines and (multi)polygons but you can safely call it with any kind of " +"geometry. Since simplification occurs on a object-by-object basis you can " "also feed a GeometryCollection to this function." msgstr "" @@ -3476,15 +3600,22 @@ msgstr "" #: reference_processing.xml:1904 #, no-c-format msgid "" -"SELECT ST_Npoints(the_geom) As np_before, ST_NPoints(ST_SimplifyPreserveTopology(the_geom,0.1)) As np01_notbadcircle, ST_NPoints(ST_SimplifyPreserveTopology(the_geom,0.5)) As np05_notquitecircle,\n" -"ST_NPoints(ST_SimplifyPreserveTopology(the_geom,1)) As np1_octagon, ST_NPoints(ST_SimplifyPreserveTopology(the_geom,10)) As np10_square,\n" +"SELECT ST_Npoints(the_geom) As np_before, " +"ST_NPoints(ST_SimplifyPreserveTopology(the_geom,0.1)) As np01_notbadcircle, " +"ST_NPoints(ST_SimplifyPreserveTopology(the_geom,0.5)) As " +"np05_notquitecircle,\n" +"ST_NPoints(ST_SimplifyPreserveTopology(the_geom,1)) As np1_octagon, " +"ST_NPoints(ST_SimplifyPreserveTopology(the_geom,10)) As np10_square,\n" "ST_NPoints(ST_SimplifyPreserveTopology(the_geom,100)) As np100_stillsquare\n" "FROM (SELECT ST_Buffer('POINT(1 3)', 10,12) As the_geom) As foo;\n" "\n" "--result--\n" -" np_before | np01_notbadcircle | np05_notquitecircle | np1_octagon | np10_square | np100_stillsquare\n" -"-----------+-------------------+---------------------+-------------+---------------+-------------------\n" -" 49 | 33 | 17 | 9 | 5 | 5" +" np_before | np01_notbadcircle | np05_notquitecircle | np1_octagon | " +"np10_square | np100_stillsquare\n" +"-----------+-------------------+---------------------+-------------" +"+---------------+-------------------\n" +" 49 | 33 | 17 | 9 " +"| 5 | 5" msgstr "" #. Tag: refname @@ -3497,8 +3628,8 @@ msgstr "" #: reference_processing.xml:1915 #, no-c-format msgid "" -"Returns a \"simplified\" version of the given geometry using the " -"Visvalingam-Whyatt algorithm" +"Returns a \"simplified\" version of the given geometry using the Visvalingam-" +"Whyatt algorithm" msgstr "" #. Tag: funcprototype @@ -3514,11 +3645,11 @@ msgstr "" #: reference_processing.xml:1930 #, no-c-format msgid "" -"Returns a \"simplified\" version of the given geometry using the " -"Visvalingam-Whyatt algorithm. Will actually do something only with " -"(multi)lines and (multi)polygons but you can safely call it with any kind of" -" geometry. Since simplification occurs on a object-by-object basis you can " -"also feed a GeometryCollection to this function." +"Returns a \"simplified\" version of the given geometry using the Visvalingam-" +"Whyatt algorithm. Will actually do something only with (multi)lines and " +"(multi)polygons but you can safely call it with any kind of geometry. Since " +"simplification occurs on a object-by-object basis you can also feed a " +"GeometryCollection to this function." msgstr "" #. Tag: para @@ -3532,8 +3663,8 @@ msgstr "" #: reference_processing.xml:1943 reference_processing.xml:1997 #, no-c-format msgid "" -"A linestring that get the efffective area calculated. All points is returned" -" since we give 0 as themin area threashold" +"A linestring that get the efffective area calculated. All points is returned " +"since we give 0 as themin area threashold" msgstr "" #. Tag: programlisting @@ -3541,7 +3672,8 @@ msgstr "" #, no-c-format msgid "" "select ST_AStext(ST_SimplifyVW(geom,30)) simplified\n" -"FROM (SELECT 'LINESTRING(5 2, 3 8, 6 20, 7 25, 10 10)'::geometry geom) As foo; \n" +"FROM (SELECT 'LINESTRING(5 2, 3 8, 6 20, 7 25, 10 10)'::geometry geom) As " +"foo; \n" "-result\n" " simplified\n" "-----------+-------------------+\n" @@ -3552,9 +3684,9 @@ msgstr "" #: reference_processing.xml:1948 #, no-c-format msgid "" -", , , Topology " +", , , Topology " msgstr "" #. Tag: refname @@ -3577,9 +3709,9 @@ msgstr "" msgid "" "geometry ST_SetEffectiveArea " "geometry geomA " -"float threashold = " -"0 integer set_area " -"= 1" +"float threashold = 0 integer set_area = 1" msgstr "" #. Tag: para @@ -3588,8 +3720,8 @@ msgstr "" msgid "" "Sets for each vertex point it's effective area from Visvalingam-Whyatt’s " "algorithm. The effective area is stored as the M-value of the geomtries. If " -"the second optional parameter is used, the resulting geometriy will be build" -" only on vertex points with an effective area greater than or equal to that " +"the second optional parameter is used, the resulting geometriy will be build " +"only on vertex points with an effective area greater than or equal to that " "threashold value. That will be a simplified geometry." msgstr "" @@ -3598,8 +3730,8 @@ msgstr "" #, no-c-format msgid "" "This function can be used for server side simplification by using the " -"threashold. Another option is to not give any threashold value. Then you get" -" the full geometry back, but with effective areas as M-values wich can be " +"threashold. Another option is to not give any threashold value. Then you get " +"the full geometry back, but with effective areas as M-values wich can be " "used by the client to simplify very fast." msgstr "" @@ -3609,15 +3741,14 @@ msgstr "" msgid "" "Will actually do something only with (multi)lines and (multi)polygons but " "you can safely call it with any kind of geometry. Since simplification " -"occurs on a object-by-object basis you can also feed a GeometryCollection to" -" this function." +"occurs on a object-by-object basis you can also feed a GeometryCollection to " +"this function." msgstr "" #. Tag: para #: reference_processing.xml:1990 #, no-c-format -msgid "" -"The output geoemtry will loose all previous information in the M-values" +msgid "The output geoemtry will loose all previous information in the M-values" msgstr "" #. Tag: para @@ -3632,12 +3763,16 @@ msgstr "" #: reference_processing.xml:1998 #, no-c-format msgid "" -"select ST_AStext(ST_SetEffectiveArea(geom)) all_pts, ST_AStext(ST_SetEffectiveArea(geom,30) ) thrshld_30\n" -"FROM (SELECT 'LINESTRING(5 2, 3 8, 6 20, 7 25, 10 10)'::geometry geom) As foo; \n" +"select ST_AStext(ST_SetEffectiveArea(geom)) all_pts, " +"ST_AStext(ST_SetEffectiveArea(geom,30) ) thrshld_30\n" +"FROM (SELECT 'LINESTRING(5 2, 3 8, 6 20, 7 25, 10 10)'::geometry geom) As " +"foo; \n" "-result\n" " all_pts | thrshld_30\n" "-----------+-------------------+\n" -"LINESTRING M (5 2 3.40282346638529e+38,3 8 29,6 20 1.5,7 25 49.5,10 10 3.40282346638529e+38) | LINESTRING M (5 2 3.40282346638529e+38,7 25 49.5,10 10 3.40282346638529e+38)" +"LINESTRING M (5 2 3.40282346638529e+38,3 8 29,6 20 1.5,7 25 49.5,10 10 " +"3.40282346638529e+38) | LINESTRING M (5 2 3.40282346638529e+38,7 25 49.5,10 " +"10 3.40282346638529e+38)" msgstr "" #. Tag: refname @@ -3691,12 +3826,12 @@ msgstr "" #: reference_processing.xml:2037 #, no-c-format msgid "" -"To improve the robustness of ST_Split it may be convenient to the input to the blade in advance using a very low " -"tolerance. Otherwise the internally used coordinate grid may cause tolerance" -" problems, where coordinates of input and blade do not fall onto each other " -"and the input is not being split correctly (see #2192)." +"To improve the robustness of ST_Split it may be convenient to the input to the blade in advance using a very low tolerance. " +"Otherwise the internally used coordinate grid may cause tolerance problems, " +"where coordinates of input and blade do not fall onto each other and the " +"input is not being split correctly (see #2192)." msgstr "" #. Tag: para @@ -3729,7 +3864,8 @@ msgstr "" #: reference_processing.xml:2080 #, no-c-format msgid "" -"-- this creates a geometry collection consisting of the 2 halves of the polygon\n" +"-- this creates a geometry collection consisting of the 2 halves of the " +"polygon\n" "-- this is similar to the example we demonstrated in ST_BuildArea\n" "SELECT ST_Split(circle, line)\n" "FROM (SELECT \n" @@ -3737,7 +3873,8 @@ msgid "" " ST_Buffer(ST_GeomFromText('POINT(100 90)'), 50) As circle) As foo;\n" " \n" "-- result --\n" -" GEOMETRYCOLLECTION(POLYGON((150 90,149.039264020162 80.2454838991936,146.193976625564 70.8658283817455,..), POLYGON(..)))\n" +" GEOMETRYCOLLECTION(POLYGON((150 90,149.039264020162 " +"80.2454838991936,146.193976625564 70.8658283817455,..), POLYGON(..)))\n" " \n" "-- To convert to individual polygons, you can use ST_Dump or ST_GeometryN\n" "SELECT ST_AsText((ST_Dump(ST_Split(circle, line))).geom) As wkt\n" @@ -3749,7 +3886,8 @@ msgid "" "wkt\n" "---------------\n" "POLYGON((150 90,149.039264020162 80.2454838991936,..))\n" -"POLYGON((60.1371179574584 60.1371179574584,58.4265193848728 62.2214883490198,53.8060233744357 ..))" +"POLYGON((60.1371179574584 60.1371179574584,58.4265193848728 " +"62.2214883490198,53.8060233744357 ..))" msgstr "" #. Tag: para @@ -3764,7 +3902,8 @@ msgstr "" msgid "" "SELECT ST_AsText(ST_Split(mline, pt)) As wktcut\n" " FROM (SELECT \n" -" ST_GeomFromText('MULTILINESTRING((10 10, 190 190), (15 15, 30 30, 100 90))') As mline,\n" +" ST_GeomFromText('MULTILINESTRING((10 10, 190 190), (15 15, 30 30, 100 " +"90))') As mline,\n" " ST_Point(30,30) As pt) As foo;\n" " \n" "wktcut\n" @@ -3782,8 +3921,8 @@ msgstr "" #, no-c-format msgid "" ", , , , , " +"linkend=\"ST_GeometryN\"/>, , " msgstr "" #. Tag: refname @@ -3797,8 +3936,8 @@ msgstr "" #, no-c-format msgid "" "Returns a geometry that represents the portions of A and B that do not " -"intersect. It is called a symmetric difference because ST_SymDifference(A,B)" -" = ST_SymDifference(B,A)." +"intersect. It is called a symmetric difference because ST_SymDifference(A,B) " +"= ST_SymDifference(B,A)." msgstr "" #. Tag: funcprototype @@ -3815,8 +3954,8 @@ msgstr "" #, no-c-format msgid "" "Returns a geometry that represents the portions of A and B that do not " -"intersect. It is called a symmetric difference because ST_SymDifference(A,B)" -" = ST_SymDifference(B,A). One can think of this as ST_Union(geomA,geomB) - " +"intersect. It is called a symmetric difference because ST_SymDifference(A,B) " +"= ST_SymDifference(B,A). One can think of this as ST_Union(geomA,geomB) - " "ST_Intersection(A,B)." msgstr "" @@ -3860,7 +3999,8 @@ msgstr "" #, no-c-format msgid "" "--When used in 3d doesn't quite do the right thing\n" -"SELECT ST_AsEWKT(ST_SymDifference(ST_GeomFromEWKT('LINESTRING(1 2 1, 1 4 2)'),\n" +"SELECT ST_AsEWKT(ST_SymDifference(ST_GeomFromEWKT('LINESTRING(1 2 1, 1 4 " +"2)'),\n" " ST_GeomFromEWKT('LINESTRING(1 1 3, 1 3 4)')))\n" "\n" "st_astext\n" @@ -3894,8 +4034,8 @@ msgstr "" msgid "" "setof geometry ST_Subdivide " "geometry geom " -"integer " -"max_vertices=256" +"integer max_vertices=256" msgstr "" #. Tag: para @@ -3906,9 +4046,9 @@ msgid "" "maximum allowed number of vertices. Useful for converting excessively large " "polygons and other objects into small portions that fit within the database " "page size. Uses the same envelope clipping as ST_ClipByBox2D does, " -"recursively subdividing the input geometry until all portions have less than" -" the maximum vertex count. Minimum vertice count allowed is 8 and if you try" -" to specify lower than 8, it will throw an error." +"recursively subdividing the input geometry until all portions have less than " +"the maximum vertex count. Minimum vertice count allowed is 8 and if you try " +"to specify lower than 8, it will throw an error." msgstr "" #. Tag: para @@ -3944,9 +4084,12 @@ msgstr "" #, no-c-format msgid "" "SELECT row_number() OVER() As rn, ST_AsText(geom) As wkt\n" -"FROM ( SELECT ST_SubDivide('POLYGON((132 10,119 23,85 35,68 29,66 28,49 42,32 56,22 64,32 110,40 119,36 150,\n" -"57 158,75 171,92 182,114 184,132 186,146 178,176 184,179 162,184 141,190 122,\n" -"190 100,185 79,186 56,186 52,178 34,168 18,147 13,132 10))'::geometry,10)) As f(geom);" +"FROM ( SELECT ST_SubDivide('POLYGON((132 10,119 23,85 35,68 29,66 28,49 " +"42,32 56,22 64,32 110,40 119,36 150,\n" +"57 158,75 171,92 182,114 184,132 186,146 178,176 184,179 162,184 141,190 " +"122,\n" +"190 100,185 79,186 56,186 52,178 34,168 18,147 13,132 10))'::geometry,10)) " +"As f(geom);" msgstr "" #. Tag: screen @@ -3954,17 +4097,24 @@ msgstr "" #, no-c-format msgid "" "rn | wkt\n" -"---+---------------------------------------------------------------------------\n" -" 1 | POLYGON((22 64,29.3913043478263 98.000000000001,106.000000000001 98.00000000001,\n" -" 106.000000000001 27.5882352941173,85 35,68 29,66 28,49 42,32 56,22 64))\n" +"---" +"+---------------------------------------------------------------------------\n" +" 1 | POLYGON((22 64,29.3913043478263 98.000000000001,106.000000000001 " +"98.00000000001,\n" +" 106.000000000001 27.5882352941173,85 35,68 29,66 28,49 42,32 56,22 " +"64))\n" " 2 | POLYGON((29.3913043478263 98.000000000001,32 110,40 119,36 150,57 158,\n" -" 75 11,92 182,106.000000000001 183.272727272727,106.000000000001 98.000000000001,\n" +" 75 11,92 182,106.000000000001 183.272727272727,106.000000000001 " +"98.000000000001,\n" " 29.913043478263 98.000000000001))\n" -" 3 | POLYGON((106.000000000001 27.5882352941173,106.000000000001 98.00000000000,\n" +" 3 | POLYGON((106.000000000001 27.5882352941173,106.000000000001 " +"98.00000000000,\n" " 189.52380952381 98.000000000001,185 79,186 56,186 52,178 34,168 18,147 13,\n" " 132 0,119 23,106.000000000001 27.5882352941173))\n" -" 4 | POLYGON((106.000000000001 98.000000000001,106.000000000001 183.27272727272,\n" -" 114 184,132 186,146 178,176 184,179 162,184 141,190 122,190 100,189.5238095238\n" +" 4 | POLYGON((106.000000000001 98.000000000001,106.000000000001 " +"183.27272727272,\n" +" 114 184,132 186,146 178,176 184,179 162,184 141,190 122,190 " +"100,189.5238095238\n" " 98.000000000001,106.000000000001 98.000000000001))" msgstr "" @@ -3988,10 +4138,23 @@ msgstr "" #: reference_processing.xml:2281 #, no-c-format msgid "" -"LINESTRING(0 0,7.07106781186547 7.07106781186547,14.1421356237309 14.1421356237309,21.2132034355964 21.2132034355964,28.2842712474619 28.2842712474619,35.3553390593274 35.3553390593274,37.499999999998 37.499999999998)\n" -"LINESTRING(37.499999999998 37.499999999998,42.4264068711929 42.4264068711929,49.4974746830583 49.4974746830583,56.5685424949238 56.5685424949238,63.6396103067893 63.6396103067893,70.7106781186548 70.7106781186548,74.999999999998 74.999999999998)\n" -"LINESTRING(74.999999999998 74.999999999998,77.7817459305202 77.7817459305202,84.8528137423857 84.8528137423857,91.9238815542512 91.9238815542512,98.9949493661167 98.9949493661167,100 100,107.071067811865 107.071067811865,112.499999999998 112.499999999998)\n" -"LINESTRING(112.499999999998 112.499999999998,114.142135623731 114.142135623731,121.213203435596 121.213203435596,128.284271247462 128.284271247462,135.355339059327 135.355339059327,142.426406871193 142.426406871193,149.497474683058 149.497474683058,149.999999999998 149.999999999998)" +"LINESTRING(0 0,7.07106781186547 7.07106781186547,14.1421356237309 " +"14.1421356237309,21.2132034355964 21.2132034355964,28.2842712474619 " +"28.2842712474619,35.3553390593274 35.3553390593274,37.499999999998 " +"37.499999999998)\n" +"LINESTRING(37.499999999998 37.499999999998,42.4264068711929 " +"42.4264068711929,49.4974746830583 49.4974746830583,56.5685424949238 " +"56.5685424949238,63.6396103067893 63.6396103067893,70.7106781186548 " +"70.7106781186548,74.999999999998 74.999999999998)\n" +"LINESTRING(74.999999999998 74.999999999998,77.7817459305202 " +"77.7817459305202,84.8528137423857 84.8528137423857,91.9238815542512 " +"91.9238815542512,98.9949493661167 98.9949493661167,100 100,107.071067811865 " +"107.071067811865,112.499999999998 112.499999999998)\n" +"LINESTRING(112.499999999998 112.499999999998,114.142135623731 " +"114.142135623731,121.213203435596 121.213203435596,128.284271247462 " +"128.284271247462,135.355339059327 135.355339059327,142.426406871193 " +"142.426406871193,149.497474683058 149.497474683058,149.999999999998 " +"149.999999999998)" msgstr "" #. Tag: para @@ -4020,14 +4183,14 @@ msgstr "" #, no-c-format msgid "" " geometry ST_Union " -"geometry set " -"g1field " +"geometry set g1field geometry " +"ST_Union geometry " +"g1 geometry " +"g2 " "geometry ST_Union " -"geometry g1 " -"geometry g2 " -" geometry " -"ST_Union geometry[] " -"g1_array " +"geometry[] g1_array " +"" msgstr "" #. Tag: para @@ -4046,18 +4209,18 @@ msgstr "" #, no-c-format msgid "" "Aggregate version: This function returns a MULTI geometry or NON-MULTI " -"geometry from a set of geometries. The ST_Union() function is an " -"\"aggregate\" function in the terminology of PostgreSQL. That means that it " -"operates on rows of data, in the same way the SUM() and AVG() functions do " -"and like most aggregates, it also ignores NULL geometries." +"geometry from a set of geometries. The ST_Union() function is an \"aggregate" +"\" function in the terminology of PostgreSQL. That means that it operates on " +"rows of data, in the same way the SUM() and AVG() functions do and like most " +"aggregates, it also ignores NULL geometries." msgstr "" #. Tag: para #: reference_processing.xml:2336 #, no-c-format msgid "" -"Non-Aggregate version: This function returns a geometry being a union of two" -" input geometries. Output type can be a MULTI*, NON-MULTI or " +"Non-Aggregate version: This function returns a geometry being a union of two " +"input geometries. Output type can be a MULTI*, NON-MULTI or " "GEOMETRYCOLLECTION. If any are NULL, then NULL is returned." msgstr "" @@ -4101,8 +4264,8 @@ msgstr "" #: reference_processing.xml:2356 #, no-c-format msgid "" -"&sqlmm_compliant; SQL-MM 3: 5.1.19 the z-index (elevation) when polygons are" -" involved." +"&sqlmm_compliant; SQL-MM 3: 5.1.19 the z-index (elevation) when polygons are " +"involved." msgstr "" #. Tag: para @@ -4153,7 +4316,8 @@ msgid "" "\n" "st_asewkt\n" "---------\n" -"GEOMETRYCOLLECTION(POINT(-2 3 1),LINESTRING(5 5 5,10 10 10),POLYGON((-7 4.2 5,-7.1 4.2 5,-7.1 4.3 5,-7 4.2 5)));\n" +"GEOMETRYCOLLECTION(POINT(-2 3 1),LINESTRING(5 5 5,10 10 10),POLYGON((-7 4.2 " +"5,-7.1 4.2 5,-7.1 4.3 5,-7 4.2 5)));\n" "\n" "--3d example not mixing dimensions\n" "SELECT ST_AsEWKT(st_union(the_geom))\n" @@ -4169,13 +4333,15 @@ msgid "" "\n" "st_asewkt\n" "---------\n" -"GEOMETRYCOLLECTION(POINT(-2 3 1),LINESTRING(5 5 5,10 10 10),POLYGON((-7 4.2 2,-7.1 4.2 3,-7.1 4.3 2,-7 4.2 2)))\n" +"GEOMETRYCOLLECTION(POINT(-2 3 1),LINESTRING(5 5 5,10 10 10),POLYGON((-7 4.2 " +"2,-7.1 4.2 3,-7.1 4.3 2,-7 4.2 2)))\n" "\n" "--Examples using new Array construct\n" "SELECT ST_Union(ARRAY(SELECT the_geom FROM sometable));\n" "\n" "SELECT ST_AsText(ST_Union(ARRAY[ST_GeomFromText('LINESTRING(1 2, 3 4)'),\n" -" ST_GeomFromText('LINESTRING(3 4, 4 5)')])) As wktunion;\n" +" ST_GeomFromText('LINESTRING(3 4, 4 5)')])) As " +"wktunion;\n" "\n" "--wktunion---\n" "MULTILINESTRING((3 4,4 5),(1 2,3 4))" @@ -4229,7 +4395,8 @@ msgid "" " 'LINESTRING (5 5, 4 4)'::geometry,\n" " 'LINESTRING (6 6, 7 7)'::geometry,\n" " 'LINESTRING (0 0, -1 -1)'::geometry,\n" -" 'POLYGON ((0 0, 4 0, 4 4, 0 4, 0 0))'::geometry]) AS geom)\n" +" 'POLYGON ((0 0, 4 0, 4 4, 0 4, 0 0))'::geometry]) AS " +"geom)\n" "\n" "SELECT ST_AsText(unnest(ST_ClusterWithin(geom, 1.4))) FROM testdata;\n" "\n" @@ -4237,7 +4404,8 @@ msgid "" "\n" "st_astext\n" "---------\n" -"GEOMETRYCOLLECTION(LINESTRING(0 0,1 1),LINESTRING(5 5,4 4),LINESTRING(0 0,-1 -1),POLYGON((0 0,4 0,4 4,0 4,0 0)))\n" +"GEOMETRYCOLLECTION(LINESTRING(0 0,1 1),LINESTRING(5 5,4 4),LINESTRING(0 0,-1 " +"-1),POLYGON((0 0,4 0,4 4,0 4,0 0)))\n" "GEOMETRYCOLLECTION(LINESTRING(6 6,7 7))" msgstr "" @@ -4281,7 +4449,8 @@ msgid "" " 'LINESTRING (5 5, 4 4)'::geometry,\n" " 'LINESTRING (6 6, 7 7)'::geometry,\n" " 'LINESTRING (0 0, -1 -1)'::geometry,\n" -" 'POLYGON ((0 0, 4 0, 4 4, 0 4, 0 0))'::geometry]) AS geom)\n" +" 'POLYGON ((0 0, 4 0, 4 4, 0 4, 0 0))'::geometry]) AS " +"geom)\n" "\n" "SELECT ST_AsText(unnest(ST_ClusterIntersecting(geom))) FROM testdata;\n" "\n" @@ -4289,7 +4458,8 @@ msgid "" "\n" "st_astext\n" "---------\n" -"GEOMETRYCOLLECTION(LINESTRING(0 0,1 1),LINESTRING(5 5,4 4),LINESTRING(0 0,-1 -1),POLYGON((0 0,4 0,4 4,0 4,0 0)))\n" +"GEOMETRYCOLLECTION(LINESTRING(0 0,1 1),LINESTRING(5 5,4 4),LINESTRING(0 0,-1 " +"-1),POLYGON((0 0,4 0,4 4,0 4,0 0)))\n" "GEOMETRYCOLLECTION(LINESTRING(6 6,7 7))" msgstr "" @@ -4318,9 +4488,9 @@ msgstr "" #, no-c-format msgid "" "Unlike ST_Union, ST_UnaryUnion does dissolve boundaries between components " -"of a multipolygon (invalid) and does perform union between the components of" -" a geometrycollection. Each components of the input geometry is assumed to " -"be valid, so you won't get a valid multipolygon out of a bow-tie polygon " +"of a multipolygon (invalid) and does perform union between the components of " +"a geometrycollection. Each components of the input geometry is assumed to be " +"valid, so you won't get a valid multipolygon out of a bow-tie polygon " "(invalid)." msgstr "" diff --git a/doc/po/de_DE/reference_raster.xml.po b/doc/po/de_DE/reference_raster.xml.po index 39f09e0ac..11891eca3 100644 --- a/doc/po/de_DE/reference_raster.xml.po +++ b/doc/po/de_DE/reference_raster.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:24+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -43,8 +44,8 @@ msgstr "" #: reference_raster.xml:10 #, no-c-format msgid "" -"For loading rasters from raster files please refer to " +"For loading rasters from raster files please refer to " msgstr "" #. Tag: para @@ -89,16 +90,18 @@ msgid "" "),\n" "-- Raster: 5 x 5 pixels, 3 bands, PT_8BUI pixel type, NODATA = 0\n" "(2, ('01000003009A9999999999A93F9A9999999999A9BF000000E02B274A' ||\n" -"'41000000007719564100000000000000000000000000000000FFFFFFFF050005000400FDFEFDFEFEFDFEFEFDF9FAFEF' ||\n" -"'EFCF9FBFDFEFEFDFCFAFEFEFE04004E627AADD16076B4F9FE6370A9F5FE59637AB0E54F58617087040046566487A1506CA2E3FA5A6CAFFBFE4D566DA4CB3E454C5665')::raster);" +"'41000000007719564100000000000000000000000000000000FFFFFFFF050005000400FDFEFDFEFEFDFEFEFDF9FAFEF' " +"||\n" +"'EFCF9FBFDFEFEFDFCFAFEFEFE04004E627AADD16076B4F9FE6370A9F5FE59637AB0E54F58617087040046566487A1506CA2E3FA5A6CAFFBFE4D566DA4CB3E454C5665')::" +"raster);" msgstr "" #. Tag: para #: reference_raster.xml:17 #, no-c-format msgid "" -"This section lists the PostgreSQL data types specifically created to support" -" raster functionality." +"This section lists the PostgreSQL data types specifically created to support " +"raster functionality." msgstr "" #. Tag: title @@ -328,8 +331,8 @@ msgstr "" #: reference_raster.xml:72 #, no-c-format msgid "" -"Pixel type of the new band. One of defined pixel types as described in ." +"Pixel type of the new band. One of defined pixel types as described in ." msgstr "" #. Tag: term @@ -553,8 +556,8 @@ msgstr "" #: reference_raster.xml:228 #, no-c-format msgid "" -"One of defined pixel types as described in " +"One of defined pixel types as described in " msgstr "" #. Tag: term @@ -708,23 +711,22 @@ msgstr "" #, no-c-format msgid "" "A composite type used as input into the ST_Union function " -"defining the bands to be processed and behavior of the UNION " -"operation." +"defining the bands to be processed and behavior of the UNION operation." msgstr "" #. Tag: para #: reference_raster.xml:355 #, no-c-format msgid "" -"A composite type used as input into the ST_Union function defining the" -" bands to be processed and behavior of the UNION operation." +"A composite type used as input into the ST_Union function defining the " +"bands to be processed and behavior of the UNION operation." msgstr "" #. Tag: para #: reference_raster.xml:365 #, no-c-format -msgid "" -"1-based value indicating the band of each input raster to be processed." +msgid "1-based value indicating the band of each input raster to be processed." msgstr "" #. Tag: term @@ -737,8 +739,8 @@ msgstr "" #: reference_raster.xml:377 #, no-c-format msgid "" -"Type of UNION operation. One of defined types as described in ." +"Type of UNION operation. One of defined types as described in ." msgstr "" #. Tag: title @@ -768,66 +770,57 @@ msgstr "" #: reference_raster.xml:408 #, no-c-format msgid "" -" boolean " -"AddRasterConstraints name " -" rasttable name " -" rastcolumn boolean" -" srid boolean " -" scale_x boolean " -" scale_y boolean " -" blocksize_x " -"boolean " -"blocksize_y boolean " -" same_alignment " -"boolean " -"regular_blocking boolean num_bands=true " -" boolean " -"pixel_types=true boolean " -"nodata_values=true boolean out_db=true " -" boolean " -"extent=true " -" boolean " -"AddRasterConstraints name " -" rasttable name " -" rastcolumn text[] " -" VARIADIC constraints " -" boolean " -"AddRasterConstraints name " -" rastschema name " -" rasttable name " -" rastcolumn text[] " -" VARIADIC constraints " -" boolean " -"AddRasterConstraints name " -" rastschema name " -" rasttable name " -" rastcolumn boolean " -"srid=true boolean " -"scale_x=true boolean " -"scale_y=true boolean " -"blocksize_x=true boolean " -"blocksize_y=true boolean " -"same_alignment=true boolean " -"regular_blocking=false boolean " -"num_bands=true boolean " -"pixel_types=true boolean " -"nodata_values=true boolean out_db=true " -" boolean " -"extent=true " +" boolean AddRasterConstraints name rasttable name rastcolumn boolean srid boolean scale_x boolean scale_y boolean blocksize_x boolean " +"blocksize_y boolean same_alignment " +"boolean regular_blocking boolean " +"num_bands=true boolean pixel_types=true " +"boolean " +"nodata_values=true boolean out_db=true " +"boolean extent=true boolean " +"AddRasterConstraints name rasttable name rastcolumn text[] VARIADIC constraints boolean " +"AddRasterConstraints name rastschema name rasttable name rastcolumn text[] VARIADIC constraints boolean " +"AddRasterConstraints name rastschema name rasttable name rastcolumn boolean srid=true " +"boolean scale_x=true boolean " +"scale_y=true boolean blocksize_x=true " +"boolean blocksize_y=true boolean " +"same_alignment=true boolean regular_blocking=false boolean " +"num_bands=true boolean pixel_types=true " +"boolean " +"nodata_values=true boolean out_db=true " +"boolean extent=true " msgstr "" #. Tag: para @@ -845,16 +838,16 @@ msgstr "" #: reference_raster.xml:543 #, no-c-format msgid "" -"raster2pgsql loader uses this function to register raster" -" tables" +"raster2pgsql loader uses this function to register raster " +"tables" msgstr "" #. Tag: para #: reference_raster.xml:544 #, no-c-format msgid "" -"Valid constraint names to pass in: refer to for more details." +"Valid constraint names to pass in: refer to for more details." msgstr "" #. Tag: para @@ -982,19 +975,24 @@ msgstr "" msgid "" "CREATE TABLE myrasters(rid SERIAL primary key, rast raster);\n" "INSERT INTO myrasters(rast)\n" -"SELECT ST_AddBand(ST_MakeEmptyRaster(1000, 1000, 0.3, -0.3, 2, 2, 0, 0,4326), 1, '8BSI'::text, -129, NULL);\n" +"SELECT ST_AddBand(ST_MakeEmptyRaster(1000, 1000, 0.3, -0.3, 2, 2, 0, " +"0,4326), 1, '8BSI'::text, -129, NULL);\n" "\n" "SELECT AddRasterConstraints('myrasters'::name, 'rast'::name);\n" "\n" "\n" "-- verify if registered correctly in the raster_columns view --\n" -"SELECT srid, scale_x, scale_y, blocksize_x, blocksize_y, num_bands, pixel_types, nodata_values\n" +"SELECT srid, scale_x, scale_y, blocksize_x, blocksize_y, num_bands, " +"pixel_types, nodata_values\n" " FROM raster_columns\n" " WHERE r_table_name = 'myrasters';\n" " \n" -" srid | scale_x | scale_y | blocksize_x | blocksize_y | num_bands | pixel_types| nodata_values\n" -"------+---------+---------+-------------+-------------+-----------+-------------+---------------\n" -" 4326 | 2 | 2 | 1000 | 1000 | 1 | {8BSI} | {0}" +" srid | scale_x | scale_y | blocksize_x | blocksize_y | num_bands | " +"pixel_types| nodata_values\n" +"------+---------+---------+-------------+-------------+-----------" +"+-------------+---------------\n" +" 4326 | 2 | 2 | 1000 | 1000 | 1 | " +"{8BSI} | {0}" msgstr "" #. Tag: title @@ -1009,9 +1007,11 @@ msgstr "" msgid "" "CREATE TABLE public.myrasters2(rid SERIAL primary key, rast raster);\n" "INSERT INTO myrasters2(rast)\n" -"SELECT ST_AddBand(ST_MakeEmptyRaster(1000, 1000, 0.3, -0.3, 2, 2, 0, 0,4326), 1, '8BSI'::text, -129, NULL);\n" +"SELECT ST_AddBand(ST_MakeEmptyRaster(1000, 1000, 0.3, -0.3, 2, 2, 0, " +"0,4326), 1, '8BSI'::text, -129, NULL);\n" "\n" -"SELECT AddRasterConstraints('public'::name, 'myrasters2'::name, 'rast'::name,'regular_blocking', 'blocksize');\n" +"SELECT AddRasterConstraints('public'::name, 'myrasters2'::name, 'rast'::" +"name,'regular_blocking', 'blocksize');\n" "-- get notice--\n" "NOTICE: Adding regular blocking constraint\n" "NOTICE: Adding blocksize-X constraint\n" @@ -1022,10 +1022,9 @@ msgstr "" #: reference_raster.xml:586 #, no-c-format msgid "" -", , , , , " +", , , , , " msgstr "" #. Tag: refname @@ -1038,69 +1037,59 @@ msgstr "" #: reference_raster.xml:594 #, no-c-format msgid "" -"Drops PostGIS raster constraints that refer to a raster table column. Useful" -" if you need to reload data or update your raster column data." +"Drops PostGIS raster constraints that refer to a raster table column. Useful " +"if you need to reload data or update your raster column data." msgstr "" #. Tag: funcsynopsis #: reference_raster.xml:598 #, no-c-format msgid "" -" boolean " -"DropRasterConstraints name " -" rasttable name " -" rastcolumn boolean" -" srid boolean " -" scale_x boolean " -" scale_y boolean " -" blocksize_x " -"boolean " -"blocksize_y boolean " -" same_alignment " -"boolean " -"regular_blocking boolean " -"num_bands=true boolean " -"pixel_types=true boolean " -"nodata_values=true boolean out_db=true " -" boolean " -"extent=true " -" boolean " -"DropRasterConstraints name " -" rastschema name " -" rasttable name " -" rastcolumn boolean " -"srid=true boolean " -"scale_x=true boolean " -"scale_y=true boolean " -"blocksize_x=true boolean " -"blocksize_y=true boolean " -"same_alignment=true boolean " -"regular_blocking=false boolean " -"num_bands=true boolean " -"pixel_types=true boolean " -"nodata_values=true boolean out_db=true " -" boolean " -"extent=true " -" boolean " -"DropRasterConstraints name " -" rastschema name " -" rasttable name " -" rastcolumn text[] " -" constraints " +" boolean DropRasterConstraints name rasttable name rastcolumn boolean srid boolean scale_x boolean scale_y boolean blocksize_x boolean " +"blocksize_y boolean same_alignment " +"boolean regular_blocking boolean " +"num_bands=true boolean pixel_types=true " +"boolean " +"nodata_values=true boolean out_db=true " +"boolean extent=true boolean " +"DropRasterConstraints name rastschema name rasttable name rastcolumn boolean srid=true " +"boolean scale_x=true boolean " +"scale_y=true boolean blocksize_x=true " +"boolean blocksize_y=true boolean " +"same_alignment=true boolean regular_blocking=false boolean " +"num_bands=true boolean pixel_types=true " +"boolean " +"nodata_values=true boolean out_db=true " +"boolean extent=true boolean " +"DropRasterConstraints name rastschema name rasttable name rastcolumn text[] constraints " msgstr "" #. Tag: para @@ -1109,8 +1098,8 @@ msgstr "" msgid "" "Drops PostGIS raster constraints that refer to a raster table column that " "were added by . Useful if you " -"need to load more data or update your raster column data. You do not need to" -" do this if you want to get rid of a raster table or a raster column." +"need to load more data or update your raster column data. You do not need to " +"do this if you want to get rid of a raster table or a raster column." msgstr "" #. Tag: para @@ -1216,13 +1205,17 @@ msgid "" "t\n" "\n" "-- verify change in raster_columns --\n" -"SELECT srid, scale_x, scale_y, blocksize_x, blocksize_y, num_bands, pixel_types, nodata_values\n" +"SELECT srid, scale_x, scale_y, blocksize_x, blocksize_y, num_bands, " +"pixel_types, nodata_values\n" " FROM raster_columns\n" " WHERE r_table_name = 'myrasters';\n" " \n" -" srid | scale_x | scale_y | blocksize_x | blocksize_y | num_bands | pixel_types| nodata_values\n" -"------+---------+---------+-------------+-------------+-----------+-------------+---------------\n" -" 0 | | | | | | |" +" srid | scale_x | scale_y | blocksize_x | blocksize_y | num_bands | " +"pixel_types| nodata_values\n" +"------+---------+---------+-------------+-------------+-----------" +"+-------------+---------------\n" +" 0 | | | | | " +"| |" msgstr "" #. Tag: refname @@ -1241,22 +1234,21 @@ msgstr "" #: reference_raster.xml:739 #, no-c-format msgid "" -" boolean " -"AddOverviewConstraints name " -" ovschema name " -" ovtable name " -" ovcolumn name " -" refschema name " -" reftable name " -" refcolumn int " -" ovfactor " -" boolean " -"AddOverviewConstraints name " -" ovtable name " -" ovcolumn name " -" reftable name " -" refcolumn int " -" ovfactor " +" boolean AddOverviewConstraints name ovschema name ovtable name ovcolumn name refschema name reftable name refcolumn int ovfactor boolean " +"AddOverviewConstraints name ovtable name " +"ovcolumn name " +"reftable name " +"refcolumn int " +"ovfactor " msgstr "" #. Tag: para @@ -1271,8 +1263,8 @@ msgstr "" #: reference_raster.xml:783 #, no-c-format msgid "" -"The ovfactor parameter represents the scale multiplier in" -" the overview column: higher overview factors have lower resolution." +"The ovfactor parameter represents the scale multiplier in " +"the overview column: higher overview factors have lower resolution." msgstr "" #. Tag: para @@ -1317,8 +1309,8 @@ msgstr "" #: reference_raster.xml:805 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -1337,15 +1329,14 @@ msgstr "" #: reference_raster.xml:822 #, no-c-format msgid "" -" boolean " -"DropOverviewConstraints name " -" ovschema name " -" ovtable name " -" ovcolumn " -" boolean " +" boolean DropOverviewConstraints name ovschema name ovtable name ovcolumn boolean " "DropOverviewConstraints name " -" ovtable name " -" ovcolumn " +" ovtable name ovcolumn " msgstr "" #. Tag: para @@ -1369,8 +1360,8 @@ msgstr "" #: reference_raster.xml:865 #, no-c-format msgid "" -", , " +", , " msgstr "" #. Tag: refname @@ -1457,8 +1448,8 @@ msgstr "" #: reference_raster.xml:946 #, no-c-format msgid "" -"Reports full raster version and build configuration " -"infos." +"Reports full raster version and build configuration infos." msgstr "" #. Tag: funcprototype @@ -1472,8 +1463,7 @@ msgstr "" #. Tag: para #: reference_raster.xml:963 #, no-c-format -msgid "" -"Reports full raster version and build configuration infos." +msgid "Reports full raster version and build configuration infos." msgstr "" #. Tag: programlisting @@ -1506,24 +1496,24 @@ msgstr "" msgid "" "setof record ST_GDALDrivers " "integer OUT idx " -"text OUT " -"short_name text " -"OUT long_name text " -" OUT create_options" +"text OUT short_name text OUT long_name text OUT create_options" msgstr "" #. Tag: para #: reference_raster.xml:1004 #, no-c-format msgid "" -"Returns a list of raster formats short_name,long_name and creator options of" -" each format supported by your lib gdal. Use the short_name as input in the " -"format parameter of . Options vary depending on what drivers " -"your libgdal was compiled with. create_options returns an" -" xml formatted set of CreationOptionList/Option consisting of name and " -"optional type, description and set of " -"VALUE for each creator option for the specific driver." +"Returns a list of raster formats short_name,long_name and creator options of " +"each format supported by your lib gdal. Use the short_name as input in the " +"format parameter of . Options vary depending on what drivers your libgdal was compiled with. " +"create_options returns an xml formatted set of " +"CreationOptionList/Option consisting of name and optional type, description and set of VALUE " +"for each creator option for the specific driver." msgstr "" #. Tag: para @@ -1603,23 +1593,27 @@ msgstr "" #, no-c-format msgid "" "-- Output the create options XML column of JPEG as a table --\n" -"-- Note you can use these creator options in ST_AsGDALRaster options argument\n" +"-- Note you can use these creator options in ST_AsGDALRaster options " +"argument\n" "SELECT (xpath('@name', g.opt))[1]::text As oname,\n" " (xpath('@type', g.opt))[1]::text As otype,\n" " (xpath('@description', g.opt))[1]::text As descrip\n" -"FROM (SELECT unnest(xpath('/CreationOptionList/Option', create_options::xml)) As opt\n" +"FROM (SELECT unnest(xpath('/CreationOptionList/Option', create_options::" +"xml)) As opt\n" "FROM st_gdaldrivers()\n" "WHERE short_name = 'JPEG') As g;\n" "\n" " oname | otype | descrip\n" -"--------------------+---------+-------------------------------------------------\n" +"--------------------+---------" +"+-------------------------------------------------\n" " PROGRESSIVE | boolean | whether to generate a progressive JPEG\n" " QUALITY | int | good=100, bad=0, default=75\n" " WORLDFILE | boolean | whether to geneate a worldfile\n" " INTERNAL_MASK | boolean | whether to generate a validity mask\n" " COMMENT | string | Comment\n" " SOURCE_ICC_PROFILE | string | ICC profile encoded in Base64\n" -" EXIF_THUMBNAIL | boolean | whether to generate an EXIF thumbnail(overview).\n" +" EXIF_THUMBNAIL | boolean | whether to generate an EXIF " +"thumbnail(overview).\n" " By default its max dimension will be 128\n" " THUMBNAIL_WIDTH | int | Forced thumbnail width\n" " THUMBNAIL_HEIGHT | int | Forced thumbnail height\n" @@ -1646,19 +1640,27 @@ msgid "" " CCITTFAX4\n" " DEFLATE\n" " \n" -" \n" -" \n" -" \n" -" \n" -" \n" -" integer[] outdbindex double precision nodataval=NULL (7) raster " "ST_AddBand raster " "rast text " -"outdbfile integer[] " -" outdbindex integer " -"index=at_end double precision " +"outdbfile integer[] outdbindex integer index=at_end " +"double precision " "nodataval=NULL " msgstr "" @@ -1966,11 +1990,11 @@ msgid "" "type, of given initial value, and of given nodata value. If no index is " "specified, the band is added to the end. If no fromband " "is specified, band 1 is assumed. Pixel type is a string representation of " -"one of the pixel types specified in ." -" If an existing index is specified all subsequent bands >= that index are " -"incremented by 1. If an initial value greater than the max of the pixel type" -" is specified, then the initial value is set to the highest value allowed by" -" the pixel type." +"one of the pixel types specified in . " +"If an existing index is specified all subsequent bands >= that index are " +"incremented by 1. If an initial value greater than the max of the pixel type " +"is specified, then the initial value is set to the highest value allowed by " +"the pixel type." msgstr "" #. Tag: para @@ -1979,8 +2003,8 @@ msgstr "" msgid "" "For the variant that takes an array of " "(Variant 1), a specific addbandarg's index value is relative to the raster " -"at the time when the band described by that addbandarg is being added to the" -" raster. See the Multiple New Bands example below." +"at the time when the band described by that addbandarg is being added to the " +"raster. See the Multiple New Bands example below." msgstr "" #. Tag: para @@ -2023,7 +2047,8 @@ msgstr "" #: reference_raster.xml:1236 #, no-c-format msgid "" -"-- Add another band of type 8 bit unsigned integer with pixels initialized to 200\n" +"-- Add another band of type 8 bit unsigned integer with pixels initialized " +"to 200\n" "UPDATE dummy_rast\n" " SET rast = ST_AddBand(rast,'8BUI'::text,200) \n" "WHERE rid = 1;" @@ -2033,10 +2058,12 @@ msgstr "" #: reference_raster.xml:1238 #, no-c-format msgid "" -"-- Create an empty raster 100x100 units, with upper left right at 0, add 2 bands (band 1 is 0/1 boolean bit switch, band2 allows values 0-15)\n" +"-- Create an empty raster 100x100 units, with upper left right at 0, add 2 " +"bands (band 1 is 0/1 boolean bit switch, band2 allows values 0-15)\n" "-- uses addbandargs\n" "INSERT INTO dummy_rast(rid,rast)\n" -" VALUES(10, ST_AddBand(ST_MakeEmptyRaster(100, 100, 0, 0, 1, -1, 0, 0, 0), \n" +" VALUES(10, ST_AddBand(ST_MakeEmptyRaster(100, 100, 0, 0, 1, -1, 0, 0, " +"0), \n" " ARRAY[\n" " ROW(1, '1BB'::text, 0, NULL),\n" " ROW(2, '4BUI'::text, 0, NULL)\n" @@ -2060,9 +2087,12 @@ msgid "" "FROM (SELECT ST_MetaData(rast) As rmd \n" " FROM dummy_rast WHERE rid = 10) AS foo;\n" "-- result --\n" -" upperleftx | upperlefty | width | height | scalex | scaley | skewx | skewy | srid | numbands\n" -"------------+------------+-------+--------+------------+------------+-------+-------+------+----------\n" -" 0 | 0 | 100 | 100 | 1 | -1 | 0 | 0 | 0 | 2" +" upperleftx | upperlefty | width | height | scalex | scaley | skewx | skewy " +"| srid | numbands\n" +"------------+------------+-------+--------+------------+------------+-------" +"+-------+------+----------\n" +" 0 | 0 | 100 | 100 | 1 | -1 | 0 | 0 " +"| 0 | 2" msgstr "" #. Tag: title @@ -2103,10 +2133,13 @@ msgstr "" #, no-c-format msgid "" "-- Aggregate the 1st band of a table of like rasters into a single raster \n" -"-- with as many bands as there are test_types and as many rows (new rasters) as there are mice\n" +"-- with as many bands as there are test_types and as many rows (new rasters) " +"as there are mice\n" "-- NOTE: The ORDER BY test_type is only supported in PostgreSQL 9.0+\n" -"-- for 8.4 and below it usually works to order your data in a subselect (but not guaranteed)\n" -"-- The resulting raster will have a band for each test_type alphabetical by test_type\n" +"-- for 8.4 and below it usually works to order your data in a subselect (but " +"not guaranteed)\n" +"-- The resulting raster will have a band for each test_type alphabetical by " +"test_type\n" "-- For mouse lovers: No mice were harmed in this exercise\n" "SELECT\n" " mouse,\n" @@ -2137,8 +2170,10 @@ msgid "" "\n" " bandnum | pixeltype | nodatavalue | isoutdb | path \n" "---------+-----------+-------------+---------+------\n" -" 1 | 8BUI | | t | /home/raster/mytestraster.tif\n" -" 2 | 8BUI | | t | /home/raster/mytestraster.tif\n" +" 1 | 8BUI | | t | /home/raster/mytestraster." +"tif\n" +" 2 | 8BUI | | t | /home/raster/mytestraster." +"tif\n" " 3 | 8BUI | | t | /home/raster/mytestraster.tif" msgstr "" @@ -2146,9 +2181,9 @@ msgstr "" #: reference_raster.xml:1256 #, no-c-format msgid "" -", , , , " -", " +", , , , , " msgstr "" #. Tag: refname @@ -2171,176 +2206,141 @@ msgid "" "geometry geom " "raster ref " "text pixeltype " -"double precision " -"value=1 double precision " -"nodataval=0 boolean " -"touched=false " -" raster ST_AsRaster " -"geometry geom " -"raster ref " -"text[] " -"pixeltype=ARRAY['8BUI'] double precision[] " -"value=ARRAY[1] double precision[] " -"nodataval=ARRAY[0] boolean " -"touched=false " -" raster ST_AsRaster " -"geometry geom " -"double precision " -"scalex double precision " -" scaley double " -"precision gridx " -"double precision " -"gridy text " -"pixeltype double precision " -"value=1 double precision " -"nodataval=0 double precision " -"skewx=0 double precision " -"skewy=0 boolean " -"touched=false " -" raster ST_AsRaster " -"geometry geom " -"double precision " -"scalex double precision " -" scaley double precision " -"gridx=NULL double precision " -"gridy=NULL text[] " -"pixeltype=ARRAY['8BUI'] double precision[] " -"value=ARRAY[1] double precision[] " -"nodataval=ARRAY[0] double precision " -"skewx=0 double precision " -"skewy=0 boolean " -"touched=false " -" raster ST_AsRaster " -"geometry geom " -"double precision " -"scalex double precision " -" scaley text " -" pixeltype double precision " -"value=1 double precision " -"nodataval=0 double precision " -"upperleftx=NULL double precision " -"upperlefty=NULL double precision " -"skewx=0 double precision " -"skewy=0 boolean " -"touched=false " -" raster ST_AsRaster " -"geometry geom " -"double precision " -"scalex double precision " -" scaley text[] " -" pixeltype double precision[] " -"value=ARRAY[1] double precision[] " -"nodataval=ARRAY[0] double precision " -"upperleftx=NULL double precision " -"upperlefty=NULL double precision " -"skewx=0 double precision " -"skewy=0 boolean " +"double precision value=1 double precision nodataval=0 boolean touched=false raster ST_AsRaster geometry geom raster ref text[] " +"pixeltype=ARRAY['8BUI'] double precision[] value=ARRAY[1] double precision[] nodataval=ARRAY[0] boolean touched=false raster " +"ST_AsRaster geometry " +"geom double precision scalex double " +"precision scaley " +"double precision gridx double precision gridy text pixeltype double precision value=1 double precision nodataval=0 double precision " +"skewx=0 double precision skewy=0 " +"boolean touched=false raster " +"ST_AsRaster geometry " +"geom double precision scalex double " +"precision scaley double precision gridx=NULL double precision " +"gridy=NULL text[] pixeltype=ARRAY['8BUI'] double precision[] " +"value=ARRAY[1] double precision[] nodataval=ARRAY[0] double precision skewx=0 double precision skewy=0 " +"boolean touched=false raster " +"ST_AsRaster geometry " +"geom double precision scalex double " +"precision scaley " +"text pixeltype " +"double precision value=1 double precision nodataval=0 double precision upperleftx=NULL double precision " +"upperlefty=NULL double precision skewx=0 " +"double precision skewy=0 boolean " "touched=false " " raster ST_AsRaster " "geometry geom " -"integer width " -"integer height " -"double precision " -"gridx double precision " -" gridy text " -" pixeltype double precision " -"value=1 double precision " -"nodataval=0 double precision " -"skewx=0 double precision " -"skewy=0 boolean " +"double precision scalex double precision scaley text[] pixeltype double precision[] value=ARRAY[1] double precision[] nodataval=ARRAY[0] double precision upperleftx=NULL double precision upperlefty=NULL double precision skewx=0 double precision skewy=0 " +"boolean touched=false raster " +"ST_AsRaster geometry " +"geom integer " +"width integer " +"height double precision gridx double " +"precision gridy " +"text pixeltype " +"double precision value=1 double precision nodataval=0 double precision skewx=0 " +"double precision skewy=0 boolean " "touched=false " " raster ST_AsRaster " "geometry geom " "integer width " "integer height " "double precision " -"gridx=NULL double precision " -"gridy=NULL text[] " -"pixeltype=ARRAY['8BUI'] double precision[] " -"value=ARRAY[1] double precision[] " -"nodataval=ARRAY[0] double precision " -"skewx=0 double precision " -"skewy=0 boolean " -"touched=false " -" raster ST_AsRaster " -"geometry geom " -"integer width " -"integer height " -"text pixeltype " +"gridx=NULL double precision gridy=NULL text[] pixeltype=ARRAY['8BUI'] double precision[] value=ARRAY[1] double precision[] nodataval=ARRAY[0] double precision skewx=0 double precision skewy=0 " +"boolean touched=false raster " +"ST_AsRaster geometry " +"geom integer " +"width integer " +"height text " +"pixeltype double precision value=1 " "double precision " -"value=1 double precision " -"nodataval=0 double precision " -"upperleftx=NULL double precision " -"upperlefty=NULL double precision " -"skewx=0 double precision " -"skewy=0 boolean " +"nodataval=0 double precision upperleftx=NULL double precision " +"upperlefty=NULL double precision skewx=0 " +"double precision skewy=0 boolean " "touched=false " " raster ST_AsRaster " "geometry geom " "integer width " "integer height " "text[] pixeltype " -"double precision[] " -"value=ARRAY[1] double " -"precision[] nodataval=ARRAY[0] " -"double precision " -"upperleftx=NULL double precision " -"upperlefty=NULL double precision " -"skewx=0 double precision " -"skewy=0 boolean " +"double precision[] value=ARRAY[1] double precision[] " +"nodataval=ARRAY[0] double precision upperleftx=NULL double precision " +"upperlefty=NULL double precision skewx=0 " +"double precision skewy=0 boolean " "touched=false " msgstr "" @@ -2349,20 +2349,20 @@ msgstr "" #, no-c-format msgid "" "Converts a PostGIS geometry to a PostGIS raster. The many variants offers " -"three groups of possibilities for setting the alignment and pixelsize of the" -" resulting raster." +"three groups of possibilities for setting the alignment and pixelsize of the " +"resulting raster." msgstr "" #. Tag: para #: reference_raster.xml:1424 #, no-c-format msgid "" -"The first group, composed of the two first variants, produce a raster having" -" the same alignment (scalex, scaley, " +"The first group, composed of the two first variants, produce a raster having " +"the same alignment (scalex, scaley, " "gridx and gridy), pixel type and " "nodata value as the provided reference raster. You generally pass this " -"reference raster by joining the table containing the geometry with the table" -" containing the reference raster." +"reference raster by joining the table containing the geometry with the table " +"containing the reference raster." msgstr "" #. Tag: para @@ -2370,14 +2370,13 @@ msgstr "" #, no-c-format msgid "" "The second group, composed of four variants, let you set the dimensions of " -"the raster by providing the parameters of a pixel size " -"(scalex & scaley and " -"skewx & skewy). The " -"width & height of the resulting " -"raster will be adjusted to fit the extent of the geometry. In most cases, " -"you must cast integer scalex & " -"scaley arguments to double precision so that PostgreSQL " -"choose the right variant." +"the raster by providing the parameters of a pixel size (scalex & scaley and skewx & " +"skewy). The width & " +"height of the resulting raster will be adjusted to fit " +"the extent of the geometry. In most cases, you must cast integer " +"scalex & scaley arguments to " +"double precision so that PostgreSQL choose the right variant." msgstr "" #. Tag: para @@ -2385,11 +2384,11 @@ msgstr "" #, no-c-format msgid "" "The third group, composed of four variants, let you fix the dimensions of " -"the raster by providing the dimensions of the raster " -"(width & height). The parameters " -"of the pixel size (scalex & scaley" -" and skewx & skewy) of the " -"resulting raster will be adjusted to fit the extent of the geometry." +"the raster by providing the dimensions of the raster (width & height). The parameters of the pixel size " +"(scalex & scaley and " +"skewx & skewy) of the resulting " +"raster will be adjusted to fit the extent of the geometry." msgstr "" #. Tag: para @@ -2397,22 +2396,22 @@ msgstr "" #, no-c-format msgid "" "The two first variants of each of those two last groups let you specify the " -"alignment with an arbitrary corner of the alignment grid " -"(gridx & gridy) and the two last " -"variants takes the upper left corner (upperleftx & " -"upperlefty)." +"alignment with an arbitrary corner of the alignment grid (gridx & gridy) and the two last variants takes the " +"upper left corner (upperleftx & upperlefty)." msgstr "" #. Tag: para #: reference_raster.xml:1432 #, no-c-format msgid "" -"Each group of variant allows producing a one band raster or a multiple bands" -" raster. To produce a multiple bands raster, you must provide an array of " +"Each group of variant allows producing a one band raster or a multiple bands " +"raster. To produce a multiple bands raster, you must provide an array of " "pixel types (pixeltype[]), an array of initial values " "(value) and an array of nodata values " -"(nodataval). If not provided pixeltyped defaults to 8BUI," -" values to 1 and nodataval to 0." +"(nodataval). If not provided pixeltyped defaults to 8BUI, " +"values to 1 and nodataval to 0." msgstr "" #. Tag: para @@ -2429,8 +2428,8 @@ msgstr "" #: reference_raster.xml:1436 #, no-c-format msgid "" -"The optional touched parameter defaults to false and maps" -" to the GDAL ALL_TOUCHED rasterization option, which determines if pixels " +"The optional touched parameter defaults to false and maps " +"to the GDAL ALL_TOUCHED rasterization option, which determines if pixels " "touched by lines or polygons will be burned. Not just those on the line " "render path, or whose center point is within the polygon." msgstr "" @@ -2440,9 +2439,9 @@ msgstr "" #, no-c-format msgid "" "This is particularly useful for rendering jpegs and pngs of geometries " -"directly from the database when using in combination with and other " -"family of functions." +"directly from the database when using in combination with and other family of " +"functions." msgstr "" #. Tag: para @@ -2487,8 +2486,10 @@ msgid "" "SELECT ST_AsPNG(\n" " ST_AsRaster(\n" " ST_Buffer(\n" -" ST_GeomFromText('LINESTRING(50 50,150 150,150 50)'), 10,'join=bevel'), \n" -" 200,200,ARRAY['8BUI', '8BUI', '8BUI'], ARRAY[118,154,118], ARRAY[0,0,0]));" +" ST_GeomFromText('LINESTRING(50 50,150 150,150 50)'), " +"10,'join=bevel'), \n" +" 200,200,ARRAY['8BUI', '8BUI', '8BUI'], " +"ARRAY[118,154,118], ARRAY[0,0,0]));" msgstr "" #. Tag: para @@ -2524,12 +2525,11 @@ msgid "" "ARRAY[1] " "raster ST_Band " "raster rast " -"integer nband " -" raster " -"ST_Band raster " -"rast text " -"nbands character " +"integer nband raster ST_Band raster rast text nbands character " "delimiter=, " msgstr "" @@ -2540,8 +2540,8 @@ msgid "" "Returns one or more bands of an existing raster as a new raster. Useful for " "building new rasters from existing rasters or export of only selected bands " "of a raster or rearranging the order of bands in a raster. If no band is " -"specified, band 1 is assumed. Used as a helper function in various functions" -" such as for deleting a band." +"specified, band 1 is assumed. Used as a helper function in various functions " +"such as for deleting a band." msgstr "" #. Tag: para @@ -2549,8 +2549,8 @@ msgstr "" #, no-c-format msgid "" "For the nbands as text variant of function, the default " -"delimiter is , which means you can ask for '1,2,3'" -" and if you wanted to use a different delimeter you would do " +"delimiter is , which means you can ask for '1,2,3' " +"and if you wanted to use a different delimeter you would do " "ST_Band(rast, '1@2@3', '@'). For asking for multiple bands, we " "strongly suggest you use the array form of this function e.g. " "ST_Band(rast, '{1,2,3}'::int[]); since the text " @@ -2561,11 +2561,13 @@ msgstr "" #: reference_raster.xml:1519 #, no-c-format msgid "" -"-- Make 2 new rasters: 1 containing band 1 of dummy, second containing band 2 of dummy and then reclassified as a 2BUI\n" +"-- Make 2 new rasters: 1 containing band 1 of dummy, second containing band " +"2 of dummy and then reclassified as a 2BUI\n" "SELECT ST_NumBands(rast1) As numb1, ST_BandPixelType(rast1) As pix1, \n" " ST_NumBands(rast2) As numb2, ST_BandPixelType(rast2) As pix2\n" "FROM (\n" -" SELECT ST_Band(rast) As rast1, ST_Reclass(ST_Band(rast,3), '100-200):1, [200-254:2', '2BUI') As rast2\n" +" SELECT ST_Band(rast) As rast1, ST_Reclass(ST_Band(rast,3), '100-200):1, " +"[200-254:2', '2BUI') As rast2\n" " FROM dummy_rast\n" " WHERE rid = 2) As foo;\n" " \n" @@ -2651,28 +2653,26 @@ msgstr "" #: reference_raster.xml:1574 #, no-c-format msgid "" -" raster " -"ST_MakeEmptyRaster raster " -" rast " -" raster " -"ST_MakeEmptyRaster integer " -" width integer " -" height float8 " -" upperleftx float8 " -" upperlefty float8 " -" scalex float8 " -" scaley float8 " -" skewx float8 " -" skewy integer " -"srid=unknown " -" raster " -"ST_MakeEmptyRaster integer " -" width integer " -" height float8 " -" upperleftx float8 " -" upperlefty float8 " -" pixelsize " +" raster ST_MakeEmptyRaster raster rast raster " +"ST_MakeEmptyRaster integer width integer height float8 upperleftx float8 upperlefty float8 scalex float8 scaley float8 skewx float8 " +"skewy integer srid=unknown raster ST_MakeEmptyRaster integer width integer height float8 upperleftx float8 upperlefty float8 pixelsize " msgstr "" #. Tag: para @@ -2708,8 +2708,8 @@ msgstr "" msgid "" "If no srid is specified it defaults to 0. After you create an empty raster " "you probably want to add bands to it and maybe edit it. Refer to to define bands and to set initial pixel values." +"linkend=\"RT_ST_AddBand\"/> to define bands and to set initial pixel values." msgstr "" #. Tag: programlisting @@ -2717,7 +2717,8 @@ msgstr "" #, no-c-format msgid "" "INSERT INTO dummy_rast(rid,rast)\n" -"VALUES(3, ST_MakeEmptyRaster( 100, 100, 0.0005, 0.0005, 1, 1, 0, 0, 4326) );\n" +"VALUES(3, ST_MakeEmptyRaster( 100, 100, 0.0005, 0.0005, 1, 1, 0, 0, " +"4326) );\n" "\n" "--use an existing raster as template for new raster\n" "INSERT INTO dummy_rast(rid,rast)\n" @@ -2731,10 +2732,14 @@ msgid "" " WHERE rid IN(3,4)) As foo;\n" " \n" "-- output --\n" -" rid | upperleftx | upperlefty | width | height | scalex | scaley | skewx | skewy | srid | numbands\n" -"-----+------------+------------+-------+--------+------------+------------+-------+-------+------+----------\n" -" 3 | 0.0005 | 0.0005 | 100 | 100 | 1 | 1 | 0 | 0 | 4326 | 0\n" -" 4 | 0.0005 | 0.0005 | 100 | 100 | 1 | 1 | 0 | 0 | 4326 | 0" +" rid | upperleftx | upperlefty | width | height | scalex | scaley | skewx | " +"skewy | srid | numbands\n" +"-----+------------+------------+-------+--------+------------+------------" +"+-------+-------+------+----------\n" +" 3 | 0.0005 | 0.0005 | 100 | 100 | 1 | 1 " +"| 0 | 0 | 4326 | 0\n" +" 4 | 0.0005 | 0.0005 | 100 | 100 | 1 | 1 " +"| 0 | 0 | 4326 | 0" msgstr "" #. Tag: para @@ -2764,32 +2769,31 @@ msgstr "" #: reference_raster.xml:1636 #, no-c-format msgid "" -" setof raster ST_Tile" -" raster rast " +" setof raster ST_Tile " +"raster rast " "int[] nband " "integer width " "integer height " "boolean " -"padwithnodata=FALSE double precision " -"nodataval=NULL " -" setof raster ST_Tile" -" raster rast " -"integer nband " -"integer width " -"integer height " -"boolean " -"padwithnodata=FALSE double precision " +"padwithnodata=FALSE double precision nodataval=NULL setof raster " +"ST_Tile raster " +"rast integer " +"nband integer " +"width integer " +"height boolean padwithnodata=FALSE double precision " "nodataval=NULL " -" setof raster ST_Tile" -" raster rast " +" setof raster ST_Tile " +"raster rast " "integer width " "integer height " "boolean " -"padwithnodata=FALSE double precision " -"nodataval=NULL " +"padwithnodata=FALSE double precision nodataval=NULL " msgstr "" #. Tag: para @@ -2816,8 +2820,8 @@ msgstr "" #: reference_raster.xml:1681 #, no-c-format msgid "" -"If a specified band of the input raster is out-of-db, the corresponding band" -" in the output rasters will also be out-of-db." +"If a specified band of the input raster is out-of-db, the corresponding band " +"in the output rasters will also be out-of-db." msgstr "" #. Tag: programlisting @@ -2825,17 +2829,26 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, 0), 1, '8BUI', 1, 0), 2, '8BUI', 10, 0) AS rast UNION ALL\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 3, 0, 1, -1, 0, 0, 0), 1, '8BUI', 2, 0), 2, '8BUI', 20, 0) AS rast UNION ALL\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 6, 0, 1, -1, 0, 0, 0), 1, '8BUI', 3, 0), 2, '8BUI', 30, 0) AS rast UNION ALL\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, " +"0, 0, 0), 1, '8BUI', 1, 0), 2, '8BUI', 10, 0) AS rast UNION ALL\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 3, 0, 1, -1, " +"0, 0, 0), 1, '8BUI', 2, 0), 2, '8BUI', 20, 0) AS rast UNION ALL\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 6, 0, 1, -1, " +"0, 0, 0), 1, '8BUI', 3, 0), 2, '8BUI', 30, 0) AS rast UNION ALL\n" "\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, -3, 1, -1, 0, 0, 0), 1, '8BUI', 4, 0), 2, '8BUI', 40, 0) AS rast UNION ALL\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 3, -3, 1, -1, 0, 0, 0), 1, '8BUI', 5, 0), 2, '8BUI', 50, 0) AS rast UNION ALL\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 6, -3, 1, -1, 0, 0, 0), 1, '8BUI', 6, 0), 2, '8BUI', 60, 0) AS rast UNION ALL\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, -3, 1, -1, " +"0, 0, 0), 1, '8BUI', 4, 0), 2, '8BUI', 40, 0) AS rast UNION ALL\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 3, -3, 1, -1, " +"0, 0, 0), 1, '8BUI', 5, 0), 2, '8BUI', 50, 0) AS rast UNION ALL\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 6, -3, 1, -1, " +"0, 0, 0), 1, '8BUI', 6, 0), 2, '8BUI', 60, 0) AS rast UNION ALL\n" "\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, -6, 1, -1, 0, 0, 0), 1, '8BUI', 7, 0), 2, '8BUI', 70, 0) AS rast UNION ALL\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 3, -6, 1, -1, 0, 0, 0), 1, '8BUI', 8, 0), 2, '8BUI', 80, 0) AS rast UNION ALL\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 6, -6, 1, -1, 0, 0, 0), 1, '8BUI', 9, 0), 2, '8BUI', 90, 0) AS rast\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, -6, 1, -1, " +"0, 0, 0), 1, '8BUI', 7, 0), 2, '8BUI', 70, 0) AS rast UNION ALL\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 3, -6, 1, -1, " +"0, 0, 0), 1, '8BUI', 8, 0), 2, '8BUI', 80, 0) AS rast UNION ALL\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 6, -6, 1, -1, " +"0, 0, 0), 1, '8BUI', 9, 0), 2, '8BUI', 90, 0) AS rast\n" "), bar AS (\n" " SELECT ST_Union(rast) AS rast FROM foo\n" "), baz AS (\n" @@ -2873,17 +2886,26 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, 0), 1, '8BUI', 1, 0), 2, '8BUI', 10, 0) AS rast UNION ALL\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 3, 0, 1, -1, 0, 0, 0), 1, '8BUI', 2, 0), 2, '8BUI', 20, 0) AS rast UNION ALL\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 6, 0, 1, -1, 0, 0, 0), 1, '8BUI', 3, 0), 2, '8BUI', 30, 0) AS rast UNION ALL\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, " +"0, 0, 0), 1, '8BUI', 1, 0), 2, '8BUI', 10, 0) AS rast UNION ALL\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 3, 0, 1, -1, " +"0, 0, 0), 1, '8BUI', 2, 0), 2, '8BUI', 20, 0) AS rast UNION ALL\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 6, 0, 1, -1, " +"0, 0, 0), 1, '8BUI', 3, 0), 2, '8BUI', 30, 0) AS rast UNION ALL\n" "\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, -3, 1, -1, 0, 0, 0), 1, '8BUI', 4, 0), 2, '8BUI', 40, 0) AS rast UNION ALL\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 3, -3, 1, -1, 0, 0, 0), 1, '8BUI', 5, 0), 2, '8BUI', 50, 0) AS rast UNION ALL\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 6, -3, 1, -1, 0, 0, 0), 1, '8BUI', 6, 0), 2, '8BUI', 60, 0) AS rast UNION ALL\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, -3, 1, -1, " +"0, 0, 0), 1, '8BUI', 4, 0), 2, '8BUI', 40, 0) AS rast UNION ALL\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 3, -3, 1, -1, " +"0, 0, 0), 1, '8BUI', 5, 0), 2, '8BUI', 50, 0) AS rast UNION ALL\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 6, -3, 1, -1, " +"0, 0, 0), 1, '8BUI', 6, 0), 2, '8BUI', 60, 0) AS rast UNION ALL\n" "\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, -6, 1, -1, 0, 0, 0), 1, '8BUI', 7, 0), 2, '8BUI', 70, 0) AS rast UNION ALL\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 3, -6, 1, -1, 0, 0, 0), 1, '8BUI', 8, 0), 2, '8BUI', 80, 0) AS rast UNION ALL\n" -" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 6, -6, 1, -1, 0, 0, 0), 1, '8BUI', 9, 0), 2, '8BUI', 90, 0) AS rast\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, -6, 1, -1, " +"0, 0, 0), 1, '8BUI', 7, 0), 2, '8BUI', 70, 0) AS rast UNION ALL\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 3, -6, 1, -1, " +"0, 0, 0), 1, '8BUI', 8, 0), 2, '8BUI', 80, 0) AS rast UNION ALL\n" +" SELECT ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 6, -6, 1, -1, " +"0, 0, 0), 1, '8BUI', 9, 0), 2, '8BUI', 90, 0) AS rast\n" "), bar AS (\n" " SELECT ST_Union(rast) AS rast FROM foo\n" "), baz AS (\n" @@ -2938,8 +2960,8 @@ msgid "" "float8 sfy " "int tw " "int th text " -"algo='NearestNeighbor'" +"choice=\"opt\">text algo='NearestNeighbor'" msgstr "" #. Tag: para @@ -2947,10 +2969,10 @@ msgstr "" #, no-c-format msgid "" "Return a set of tiles having the specified scale (sfx, " -"sfy) and max size (tw, " -"th) and covering the specified extent " -"(ext) with data coming from the specified raster coverage" -" (tab, col)." +"sfy) and max size (tw, th) and covering the specified extent (ext) with " +"data coming from the specified raster coverage (tab, " +"col)." msgstr "" #. Tag: refname @@ -2971,17 +2993,16 @@ msgstr "" msgid "" "raster ST_FromGDALRaster " "bytea gdaldata " -"integer " -"srid=NULL" +"integer srid=NULL" msgstr "" #. Tag: para #: reference_raster.xml:1779 #, no-c-format msgid "" -"Returns a raster from a supported GDAL raster file. " -"gdaldata is of type bytea and should be the contents of " -"the GDAL raster file." +"Returns a raster from a supported GDAL raster file. gdaldata is of type bytea and should be the contents of the GDAL raster file." msgstr "" #. Tag: para @@ -2998,7 +3019,10 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT ST_AsPNG(ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 0.1, -0.1, 0, 0, 4326), 1, '8BUI', 1, 0), 2, '8BUI', 2, 0), 3, '8BUI', 3, 0)) AS png\n" +" SELECT " +"ST_AsPNG(ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, " +"0.1, -0.1, 0, 0, 4326), 1, '8BUI', 1, 0), 2, '8BUI', 2, 0), 3, '8BUI', 3, " +"0)) AS png\n" "),\n" "bar AS (\n" " SELECT 1 AS rid, ST_FromGDALRaster(png) AS rast FROM foo\n" @@ -3014,10 +3038,14 @@ msgid "" "FROM bar\n" "ORDER BY rid;\n" "\n" -" rid | metadata | stats1 | stats2 | stats3 \n" -"-----+---------------------------+---------------+---------------+----------------\n" -" 1 | (0,0,2,2,1,-1,0,0,0,3) | (4,4,1,0,1,1) | (4,8,2,0,2,2) | (4,12,3,0,3,3)\n" -" 2 | (0,0,2,2,1,-1,0,0,3310,3) | (4,4,1,0,1,1) | (4,8,2,0,2,2) | (4,12,3,0,3,3)\n" +" rid | metadata | stats1 | stats2 | " +"stats3 \n" +"-----+---------------------------+---------------+---------------" +"+----------------\n" +" 1 | (0,0,2,2,1,-1,0,0,0,3) | (4,4,1,0,1,1) | (4,8,2,0,2,2) | " +"(4,12,3,0,3,3)\n" +" 2 | (0,0,2,2,1,-1,0,0,3310,3) | (4,4,1,0,1,1) | (4,8,2,0,2,2) | " +"(4,12,3,0,3,3)\n" "(2 rows)" msgstr "" @@ -3047,18 +3075,18 @@ msgstr "" msgid "" "text ST_GeoReference " "raster rast " -"text " -"format=GDAL" +"text format=GDAL" msgstr "" #. Tag: para #: reference_raster.xml:1829 #, no-c-format msgid "" -"Returns the georeference meta data including carriage return in GDAL or ESRI" -" format as commonly seen in a world file. Default " -"is GDAL if no type specified. type is string 'GDAL' or 'ESRI'." +"Returns the georeference meta data including carriage return in GDAL or ESRI " +"format as commonly seen in a world file. Default is GDAL if no type specified. type " +"is string 'GDAL' or 'ESRI'." msgstr "" #. Tag: para @@ -3107,7 +3135,8 @@ msgstr "" #: reference_raster.xml:1841 #, no-c-format msgid "" -"SELECT ST_GeoReference(rast, 'ESRI') As esri_ref, ST_GeoReference(rast, 'GDAL') As gdal_ref\n" +"SELECT ST_GeoReference(rast, 'ESRI') As esri_ref, ST_GeoReference(rast, " +"'GDAL') As gdal_ref\n" " FROM dummy_rast WHERE rid=1;\n" "\n" " esri_ref | gdal_ref\n" @@ -3221,8 +3250,8 @@ msgstr "" #: reference_raster.xml:1924 #, no-c-format msgid "" -"Returns the amount of space (in bytes) the raster " -"takes." +"Returns the amount of space (in bytes) the raster takes." msgstr "" #. Tag: funcprototype @@ -3252,8 +3281,8 @@ msgstr "" #, no-c-format msgid "" "pg_relation_size which gives the byte size of a table may return byte size " -"lower than ST_MemSize. This is because pg_relation_size does not add toasted" -" table contribution and large geometries are stored in TOAST tables. " +"lower than ST_MemSize. This is because pg_relation_size does not add toasted " +"table contribution and large geometries are stored in TOAST tables. " "pg_column_size might return lower because it returns the compressed size." msgstr "" @@ -3269,7 +3298,8 @@ msgstr "" #: reference_raster.xml:1953 #, no-c-format msgid "" -"SELECT ST_MemSize(ST_AsRaster(ST_Buffer(ST_Point(1,5),10,1000),150, 150, '8BUI')) As rast_mem;\n" +"SELECT ST_MemSize(ST_AsRaster(ST_Buffer(ST_Point(1,5),10,1000),150, 150, " +"'8BUI')) As rast_mem;\n" " \n" " rast_mem\n" " --------\n" @@ -3315,10 +3345,14 @@ msgid "" " FROM (SELECT rid, ST_MetaData(rast) As md\n" "FROM dummy_rast) As foo;\n" "\n" -" rid | upperleftx | upperlefty | width | height | scalex | scaley | skewx | skewy | srid | numbands\n" -" ----+------------+------------+-------+--------+--------+-----------+-------+-------+------+-------\n" -" 1 | 0.5 | 0.5 | 10 | 20 | 2 | 3 | 0 | 0 | 0 | 0\n" -" 2 | 3427927.75 | 5793244 | 5 | 5 | 0.05 | -0.05 | 0 | 0 | 0 | 3" +" rid | upperleftx | upperlefty | width | height | scalex | scaley | skewx | " +"skewy | srid | numbands\n" +" ----+------------+------------+-------+--------+--------+-----------+-------" +"+-------+------+-------\n" +" 1 | 0.5 | 0.5 | 10 | 20 | 2 | 3 " +"| 0 | 0 | 0 | 0\n" +" 2 | 3427927.75 | 5793244 | 5 | 5 | 0.05 | -0.05 " +"| 0 | 0 | 0 | 3" msgstr "" #. Tag: para @@ -3416,7 +3450,8 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_Height(rast) As rastheight, ST_PixelHeight(rast) As pixheight,\n" -" ST_ScaleX(rast) As scalex, ST_ScaleY(rast) As scaley, ST_SkewX(rast) As skewx,\n" +" ST_ScaleX(rast) As scalex, ST_ScaleY(rast) As scaley, ST_SkewX(rast) As " +"skewx,\n" " ST_SkewY(rast) As skewy\n" "FROM dummy_rast;\n" "\n" @@ -3437,7 +3472,8 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_Height(rast) As rastheight, ST_PixelHeight(rast) As pixheight,\n" -" ST_ScaleX(rast) As scalex, ST_ScaleY(rast) As scaley, ST_SkewX(rast) As skewx,\n" +" ST_ScaleX(rast) As scalex, ST_ScaleY(rast) As scaley, ST_SkewX(rast) As " +"skewx,\n" " ST_SkewY(rast) As skewy\n" "FROM (SELECT ST_SetSKew(rast,0.5,0.5) As rast\n" " FROM dummy_rast) As skewed;\n" @@ -3510,7 +3546,8 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_Width(rast) As rastwidth, ST_PixelWidth(rast) As pixwidth,\n" -" ST_ScaleX(rast) As scalex, ST_ScaleY(rast) As scaley, ST_SkewX(rast) As skewx,\n" +" ST_ScaleX(rast) As scalex, ST_ScaleY(rast) As scaley, ST_SkewX(rast) " +"As skewx,\n" " ST_SkewY(rast) As skewy\n" " FROM dummy_rast;\n" " \n" @@ -3525,13 +3562,15 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_Width(rast) As rastwidth, ST_PixelWidth(rast) As pixwidth,\n" -" ST_ScaleX(rast) As scalex, ST_ScaleY(rast) As scaley, ST_SkewX(rast) As skewx,\n" +" ST_ScaleX(rast) As scalex, ST_ScaleY(rast) As scaley, ST_SkewX(rast) " +"As skewx,\n" " ST_SkewY(rast) As skewy\n" " FROM (SELECT ST_SetSkew(rast,0.5,0.5) As rast\n" " FROM dummy_rast) As skewed;\n" " \n" " rastwidth | pixwidth | scalex | scaley | skewx | skewy\n" -" -----------+-------------------+--------+--------+-------+----------\n" +" -----------+-------------------+--------+--------+-------" +"+----------\n" " 10 | 2.06155281280883 | 2 | 3 | 0.5 | 0.5\n" " 5 | 0.502493781056044 | 0.05 | -0.05 | 0.5 | 0.5" msgstr "" @@ -3563,9 +3602,8 @@ msgstr "" #, no-c-format msgid "" "Returns the X component of the pixel width in units of coordinate reference " -"system. Refer to World File for more " -"details." +"system. Refer to World File for more details." msgstr "" #. Tag: para @@ -3597,8 +3635,8 @@ msgstr "" #: reference_raster.xml:2177 #, no-c-format msgid "" -"Returns the Y component of the pixel height in units of coordinate reference" -" system." +"Returns the Y component of the pixel height in units of coordinate reference " +"system." msgstr "" #. Tag: funcprototype @@ -3613,10 +3651,9 @@ msgstr "" #: reference_raster.xml:2192 #, no-c-format msgid "" -"Returns the Y component of the pixel height in units of coordinate reference" -" system. May be negative. Refer to World File for more " -"details." +"Returns the Y component of the pixel height in units of coordinate reference " +"system. May be negative. Refer to World File for more details." msgstr "" #. Tag: para @@ -3718,8 +3755,8 @@ msgstr "" #: reference_raster.xml:2253 #, no-c-format msgid "" -", , " +", , " msgstr "" #. Tag: refname @@ -3740,15 +3777,14 @@ msgstr "" #: reference_raster.xml:2269 #, no-c-format msgid "" -" float8 " -"ST_RasterToWorldCoordX raster" -" rast integer " -" xcolumn " -" float8 " -"ST_RasterToWorldCoordX raster" -" rast integer " -" xcolumn integer " -" yrow " +" float8 ST_RasterToWorldCoordX raster rast integer xcolumn float8 " +"ST_RasterToWorldCoordX raster " +" rast integer xcolumn integer yrow " msgstr "" #. Tag: para @@ -3756,11 +3792,11 @@ msgstr "" #, no-c-format msgid "" "Returns the upper left X coordinate of a raster column row in geometric " -"units of the georeferenced raster. Numbering of columns and rows starts at 1" -" but if you pass in a negative number or number higher than number of " -"columns in raster, it will give you coordinates outside of the raster file " -"to left or right with the assumption that the skew and pixel sizes are same " -"as selected raster." +"units of the georeferenced raster. Numbering of columns and rows starts at 1 " +"but if you pass in a negative number or number higher than number of columns " +"in raster, it will give you coordinates outside of the raster file to left " +"or right with the assumption that the skew and pixel sizes are same as " +"selected raster." msgstr "" #. Tag: para @@ -3776,15 +3812,15 @@ msgstr "" #. Tag: para #: reference_raster.xml:2296 #, no-c-format -msgid "" -"Changed: 2.1.0 In prior versions, this was called ST_Raster2WorldCoordX" +msgid "Changed: 2.1.0 In prior versions, this was called ST_Raster2WorldCoordX" msgstr "" #. Tag: programlisting #: reference_raster.xml:2303 #, no-c-format msgid "" -"-- non-skewed raster providing column is sufficient \n" +"-- non-skewed raster providing column is " +"sufficient \n" "SELECT rid, ST_RasterToWorldCoordX(rast,1) As x1coord, \n" " ST_RasterToWorldCoordX(rast,2) As x2coord,\n" " ST_ScaleX(rast) As pixelx\n" @@ -3804,7 +3840,8 @@ msgid "" "SELECT rid, ST_RasterToWorldCoordX(rast, 1, 1) As x1coord, \n" " ST_RasterToWorldCoordX(rast, 2, 3) As x2coord,\n" " ST_ScaleX(rast) As pixelx\n" -"FROM (SELECT rid, ST_SetSkew(rast, 100.5, 0) As rast FROM dummy_rast) As foo;\n" +"FROM (SELECT rid, ST_SetSkew(rast, 100.5, 0) As rast FROM dummy_rast) As " +"foo;\n" "\n" " rid | x1coord | x2coord | pixelx\n" "-----+------------+-----------+--------\n" @@ -3816,8 +3853,8 @@ msgstr "" #: reference_raster.xml:2312 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -3830,23 +3867,22 @@ msgstr "" #: reference_raster.xml:2319 #, no-c-format msgid "" -"Returns the geometric Y coordinate upper left corner of a raster, column and" -" row. Numbering of columns and rows starts at 1." +"Returns the geometric Y coordinate upper left corner of a raster, column and " +"row. Numbering of columns and rows starts at 1." msgstr "" #. Tag: funcsynopsis #: reference_raster.xml:2324 #, no-c-format msgid "" -" float8 " -"ST_RasterToWorldCoordY raster" -" rast integer " -" yrow " -" float8 " -"ST_RasterToWorldCoordY raster" -" rast integer " -" xcolumn integer " -" yrow " +" float8 ST_RasterToWorldCoordY raster rast integer yrow float8 " +"ST_RasterToWorldCoordY raster " +" rast integer xcolumn integer yrow " msgstr "" #. Tag: para @@ -3854,11 +3890,11 @@ msgstr "" #, no-c-format msgid "" "Returns the upper left Y coordinate of a raster column row in geometric " -"units of the georeferenced raster. Numbering of columns and rows starts at 1" -" but if you pass in a negative number or number higher than number of " -"columns/rows in raster, it will give you coordinates outside of the raster " -"file to left or right with the assumption that the skew and pixel sizes are " -"same as selected raster tile." +"units of the georeferenced raster. Numbering of columns and rows starts at 1 " +"but if you pass in a negative number or number higher than number of columns/" +"rows in raster, it will give you coordinates outside of the raster file to " +"left or right with the assumption that the skew and pixel sizes are same as " +"selected raster tile." msgstr "" #. Tag: para @@ -3874,15 +3910,15 @@ msgstr "" #. Tag: para #: reference_raster.xml:2351 #, no-c-format -msgid "" -"Changed: 2.1.0 In prior versions, this was called ST_Raster2WorldCoordY" +msgid "Changed: 2.1.0 In prior versions, this was called ST_Raster2WorldCoordY" msgstr "" #. Tag: programlisting #: reference_raster.xml:2357 #, no-c-format msgid "" -"-- non-skewed raster providing row is sufficient \n" +"-- non-skewed raster providing row is " +"sufficient \n" "SELECT rid, ST_RasterToWorldCoordY(rast,1) As y1coord, \n" " ST_RasterToWorldCoordY(rast,3) As y2coord,\n" " ST_ScaleY(rast) As pixely\n" @@ -3914,8 +3950,8 @@ msgstr "" #: reference_raster.xml:2366 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -3943,16 +3979,16 @@ msgstr "" #, no-c-format msgid "" "Returns the uniform rotation of the raster in radian. If a raster does not " -"have uniform rotation, NaN is returned. Refer to World File for more " -"details." +"have uniform rotation, NaN is returned. Refer to World File for more details." msgstr "" #. Tag: programlisting #: reference_raster.xml:2395 #, no-c-format msgid "" -"SELECT rid, ST_Rotation(ST_SetScale(ST_SetSkew(rast, sqrt(2)), sqrt(2))) as rot FROM dummy_rast;\n" +"SELECT rid, ST_Rotation(ST_SetScale(ST_SetSkew(rast, sqrt(2)), sqrt(2))) as " +"rot FROM dummy_rast;\n" "\n" " rid | rot \n" "-----+-------------------\n" @@ -3990,8 +4026,8 @@ msgstr "" #: reference_raster.xml:2423 #, no-c-format msgid "" -"Returns the georeference X skew (or rotation parameter). Refer to World File for more " +"Returns the georeference X skew (or rotation parameter). Refer to World File for more " "details." msgstr "" @@ -4050,8 +4086,8 @@ msgstr "" #: reference_raster.xml:2459 #, no-c-format msgid "" -"Returns the georeference Y skew (or rotation parameter). Refer to World File for more " +"Returns the georeference Y skew (or rotation parameter). Refer to World File for more " "details." msgstr "" @@ -4127,8 +4163,8 @@ msgstr "" #: reference_raster.xml:2515 #, no-c-format msgid "" -"Returns a text summary of the contents of the " -"raster." +"Returns a text summary of the contents of the raster." msgstr "" #. Tag: funcprototype @@ -4153,7 +4189,8 @@ msgid "" " ST_AddBand(\n" " ST_AddBand(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(10, 10, 0, 0, 1, -1, 0, 0, 0)\n" +" ST_MakeEmptyRaster(10, 10, 0, 0, 1, -1, 0, " +"0, 0)\n" " , 1, '8BUI', 1, 0\n" " )\n" " , 2, '32BF', 0, -9999\n" @@ -4205,8 +4242,8 @@ msgstr "" #: reference_raster.xml:2569 #, no-c-format msgid "" -"Returns the upper left X coordinate of raster in projected spatial " -"ref." +"Returns the upper left X coordinate of raster in projected spatial ref." +"" msgstr "" #. Tag: programlisting @@ -4254,8 +4291,8 @@ msgstr "" #: reference_raster.xml:2603 #, no-c-format msgid "" -"Returns the upper left Y coordinate of raster in projected spatial " -"ref." +"Returns the upper left Y coordinate of raster in projected spatial ref." +"" msgstr "" #. Tag: programlisting @@ -4328,16 +4365,15 @@ msgstr "" #: reference_raster.xml:2662 #, no-c-format msgid "" -" record " -"ST_WorldToRasterCoord raster " -" rast geometry " -" pt " -" record " +" record ST_WorldToRasterCoord raster rast geometry pt record " "ST_WorldToRasterCoord raster " " rast double " "precision longitude " -"double precision " -"latitude " +"double precision latitude " msgstr "" #. Tag: para @@ -4345,8 +4381,8 @@ msgstr "" #, no-c-format msgid "" "Returns the upper left corner as column and row given geometric X and Y " -"(longitude and latitude) or a point geometry. This function works regardless" -" of whether or not the geometric X and Y or point geometry is outside the " +"(longitude and latitude) or a point geometry. This function works regardless " +"of whether or not the geometric X and Y or point geometry is outside the " "extent of the raster. Geometric X and Y must be expressed in the spatial " "reference coordinate system of the raster." msgstr "" @@ -4358,7 +4394,8 @@ msgid "" "SELECT\n" " rid,\n" " (ST_WorldToRasterCoord(rast,3427927.8,20.5)).*,\n" -" (ST_WorldToRasterCoord(rast,ST_GeomFromText('POINT(3427927.8 20.5)',ST_SRID(rast)))).*\n" +" (ST_WorldToRasterCoord(rast,ST_GeomFromText('POINT(3427927.8 20.5)'," +"ST_SRID(rast)))).*\n" "FROM dummy_rast;\n" "\n" " rid | columnx | rowy | columnx | rowy \n" @@ -4371,9 +4408,9 @@ msgstr "" #: reference_raster.xml:2700 #, no-c-format msgid "" -", , , , " +", , , , " msgstr "" #. Tag: refname @@ -4395,20 +4432,18 @@ msgstr "" #: reference_raster.xml:2718 #, no-c-format msgid "" -" integer " -"ST_WorldToRasterCoordX raster" -" rast geometry " -" pt " -" integer " -"ST_WorldToRasterCoordX raster" -" rast double " +" integer ST_WorldToRasterCoordX raster rast geometry pt integer " +"ST_WorldToRasterCoordX raster " +" rast double " "precision xw " -" integer " -"ST_WorldToRasterCoordX raster" -" rast double " -"precision xw " -"double precision " -"yw " +" integer ST_WorldToRasterCoordX raster rast double precision " +"xw double precision yw " msgstr "" #. Tag: para @@ -4416,17 +4451,16 @@ msgstr "" #, no-c-format msgid "" "Returns the column in the raster of the point geometry (pt) or a X and Y " -"world coordinate (xw, yw). A point, or (both xw and yw world coordinates are" -" required if a raster is skewed). If a raster is not skewed then xw is " -"sufficient. World coordinates are in the spatial reference coordinate system" -" of the raster." +"world coordinate (xw, yw). A point, or (both xw and yw world coordinates are " +"required if a raster is skewed). If a raster is not skewed then xw is " +"sufficient. World coordinates are in the spatial reference coordinate system " +"of the raster." msgstr "" #. Tag: para #: reference_raster.xml:2745 #, no-c-format -msgid "" -"Changed: 2.1.0 In prior versions, this was called ST_World2RasterCoordX" +msgid "Changed: 2.1.0 In prior versions, this was called ST_World2RasterCoordX" msgstr "" #. Tag: programlisting @@ -4434,8 +4468,10 @@ msgstr "" #, no-c-format msgid "" "SELECT rid, ST_WorldToRasterCoordX(rast,3427927.8) As xcoord, \n" -" ST_WorldToRasterCoordX(rast,3427927.8,20.5) As xcoord_xwyw, \n" -" ST_WorldToRasterCoordX(rast,ST_GeomFromText('POINT(3427927.8 20.5)',ST_SRID(rast))) As ptxcoord\n" +" ST_WorldToRasterCoordX(rast,3427927.8,20.5) As " +"xcoord_xwyw, \n" +" ST_WorldToRasterCoordX(rast,ST_GeomFromText('POINT(3427927.8 " +"20.5)',ST_SRID(rast))) As ptxcoord\n" "FROM dummy_rast;\n" "\n" " rid | xcoord | xcoord_xwyw | ptxcoord\n" @@ -4448,8 +4484,8 @@ msgstr "" #: reference_raster.xml:2757 reference_raster.xml:2812 #, no-c-format msgid "" -", , " +", , " msgstr "" #. Tag: refname @@ -4470,20 +4506,18 @@ msgstr "" #: reference_raster.xml:2773 #, no-c-format msgid "" -" integer " -"ST_WorldToRasterCoordY raster" -" rast geometry " -" pt " -" integer " -"ST_WorldToRasterCoordY raster" -" rast double " +" integer ST_WorldToRasterCoordY raster rast geometry pt integer " +"ST_WorldToRasterCoordY raster " +" rast double " "precision xw " -" integer " -"ST_WorldToRasterCoordY raster" -" rast double " -"precision xw " -"double precision " -"yw " +" integer ST_WorldToRasterCoordY raster rast double precision " +"xw double precision yw " msgstr "" #. Tag: para @@ -4493,15 +4527,14 @@ msgid "" "Returns the row in the raster of the point geometry (pt) or a X and Y world " "coordinate (xw, yw). A point, or (both xw and yw world coordinates are " "required if a raster is skewed). If a raster is not skewed then xw is " -"sufficient. World coordinates are in the spatial reference coordinate system" -" of the raster." +"sufficient. World coordinates are in the spatial reference coordinate system " +"of the raster." msgstr "" #. Tag: para #: reference_raster.xml:2800 #, no-c-format -msgid "" -"Changed: 2.1.0 In prior versions, this was called ST_World2RasterCoordY" +msgid "Changed: 2.1.0 In prior versions, this was called ST_World2RasterCoordY" msgstr "" #. Tag: programlisting @@ -4509,8 +4542,10 @@ msgstr "" #, no-c-format msgid "" "SELECT rid, ST_WorldToRasterCoordY(rast,20.5) As ycoord, \n" -" ST_WorldToRasterCoordY(rast,3427927.8,20.5) As ycoord_xwyw, \n" -" ST_WorldToRasterCoordY(rast,ST_GeomFromText('POINT(3427927.8 20.5)',ST_SRID(rast))) As ptycoord\n" +" ST_WorldToRasterCoordY(rast,3427927.8,20.5) As " +"ycoord_xwyw, \n" +" ST_WorldToRasterCoordY(rast,ST_GeomFromText('POINT(3427927.8 " +"20.5)',ST_SRID(rast))) As ptycoord\n" "FROM dummy_rast;\n" "\n" " rid | ycoord | ycoord_xwyw | ptycoord\n" @@ -4535,8 +4570,8 @@ msgstr "" #: reference_raster.xml:2823 #, no-c-format msgid "" -"Returns basic meta data for a specific raster band. band num 1 is assumed if" -" none-specified." +"Returns basic meta data for a specific raster band. band num 1 is assumed if " +"none-specified." msgstr "" #. Tag: funcprototype @@ -4545,8 +4580,8 @@ msgstr "" msgid "" "record ST_BandMetaData " "raster rast " -"integer " -"bandnum=1" +"integer bandnum=1" msgstr "" #. Tag: para @@ -4608,8 +4643,8 @@ msgstr "" msgid "" "double precision ST_BandNoDataValue " "raster rast " -"integer " -"bandnum=1" +"integer bandnum=1" msgstr "" #. Tag: para @@ -4623,7 +4658,8 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_BandNoDataValue(rast,1) As bnval1, \n" -" ST_BandNoDataValue(rast,2) As bnval2, ST_BandNoDataValue(rast,3) As bnval3\n" +" ST_BandNoDataValue(rast,2) As bnval2, ST_BandNoDataValue(rast,3) As " +"bnval3\n" "FROM dummy_rast\n" "WHERE rid = 2;\n" "\n" @@ -4648,16 +4684,14 @@ msgstr "" #: reference_raster.xml:2910 #, no-c-format msgid "" -" boolean " -"ST_BandIsNoData raster " -" rast integer " -" band boolean " +" boolean ST_BandIsNoData raster rast integer band boolean " "forceChecking=true " -" boolean " -"ST_BandIsNoData raster " -" rast boolean " +" boolean ST_BandIsNoData raster rast boolean " "forceChecking=true " msgstr "" @@ -4677,9 +4711,9 @@ msgstr "" #, no-c-format msgid "" "If the flag is dirty (this is, the result is different using TRUE as last " -"parameter and not using it) you should update the raster to set this flag to" -" true, by using ST_SetBandIsNodata(), or ST_SetBandNodataValue() with TRUE " -"as last argument. See ." +"parameter and not using it) you should update the raster to set this flag to " +"true, by using ST_SetBandIsNodata(), or ST_SetBandNodataValue() with TRUE as " +"last argument. See ." msgstr "" #. Tag: programlisting @@ -4689,7 +4723,8 @@ msgid "" "-- Create dummy table with one raster column\n" "create table dummy_rast (rid integer, rast raster);\n" "\n" -"-- Add raster with two bands, one pixel/band. In the first band, nodatavalue = pixel value = 3.\n" +"-- Add raster with two bands, one pixel/band. In the first band, nodatavalue " +"= pixel value = 3.\n" "-- In the second band, nodatavalue = 13, pixel value = 4\n" "insert into dummy_rast values(1,\n" "(\n" @@ -4735,17 +4770,18 @@ msgid "" ")::raster\n" ");\n" "\n" -"select st_bandisnodata(rast, 1) from dummy_rast where rid = 1; -- Expected true\n" -"select st_bandisnodata(rast, 2) from dummy_rast where rid = 1; -- Expected false" +"select st_bandisnodata(rast, 1) from dummy_rast where rid = 1; -- Expected " +"true\n" +"select st_bandisnodata(rast, 2) from dummy_rast where rid = 1; -- Expected " +"false" msgstr "" #. Tag: para #: reference_raster.xml:2953 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -4768,8 +4804,8 @@ msgstr "" msgid "" "text ST_BandPath " "raster rast " -"integer " -"bandnum=1" +"integer bandnum=1" msgstr "" #. Tag: para @@ -4806,8 +4842,8 @@ msgstr "" msgid "" "text ST_BandPixelType " "raster rast " -"integer " -"bandnum=1" +"integer bandnum=1" msgstr "" #. Tag: para @@ -4991,20 +5027,22 @@ msgid "" "WHERE rid=2;\n" "\n" " i | j | b1pgeom\n" -"---+---+-----------------------------------------------------------------------------\n" -" 1 | 1 | POLYGON((3427927.75 5793244,3427927.8 5793244,3427927.8 5793243.95,...\n" -" 2 | 1 | POLYGON((3427927.8 5793244,3427927.85 5793244,3427927.85 5793243.95, .." +"---+---" +"+-----------------------------------------------------------------------------\n" +" 1 | 1 | POLYGON((3427927.75 5793244,3427927.8 5793244,3427927.8 " +"5793243.95,...\n" +" 2 | 1 | POLYGON((3427927.8 5793244,3427927.85 5793244,3427927.85 " +"5793243.95, .." msgstr "" #. Tag: para #: reference_raster.xml:3145 #, no-c-format msgid "" -", , , , " -", , , " +", , , , , , , " msgstr "" #. Tag: refname @@ -5027,9 +5065,8 @@ msgstr "" msgid "" "setof record ST_PixelAsPolygons " "raster rast " -"integer " -"band=1 boolean " +"integer band=1 boolean " "exclude_nodata_value=TRUE" msgstr "" @@ -5079,7 +5116,8 @@ msgid "" "-- get raster pixel polygon\n" "SELECT (gv).x, (gv).y, (gv).val, ST_AsText((gv).geom) geom\n" "FROM (SELECT ST_PixelAsPolygons(\n" -" ST_SetValue(ST_SetValue(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 0.001, -0.001, 0.001, 0.001, 4269), \n" +" ST_SetValue(ST_SetValue(ST_AddBand(ST_MakeEmptyRaster(2, 2, " +"0, 0, 0.001, -0.001, 0.001, 0.001, 4269), \n" " '8BUI'::text, 1, 0), \n" " 2, 2, 10), \n" " 1, 1, NULL)\n" @@ -5087,10 +5125,13 @@ msgid "" ") foo;\n" "\n" " x | y | val | geom\n" -"---+---+-----------------------------------------------------------------------------\n" +"---+---" +"+-----------------------------------------------------------------------------\n" " 1 | 1 | | POLYGON((0 0,0.001 0.001,0.002 0,0.001 -0.001,0 0))\n" -" 1 | 2 | 1 | POLYGON((0.001 -0.001,0.002 0,0.003 -0.001,0.002 -0.002,0.001 -0.001))\n" -" 2 | 1 | 1 | POLYGON((0.001 0.001,0.002 0.002,0.003 0.001,0.002 0,0.001 0.001))\n" +" 1 | 2 | 1 | POLYGON((0.001 -0.001,0.002 0,0.003 -0.001,0.002 -0.002,0.001 " +"-0.001))\n" +" 2 | 1 | 1 | POLYGON((0.001 0.001,0.002 0.002,0.003 0.001,0.002 0,0.001 " +"0.001))\n" " 2 | 2 | 10 | POLYGON((0.002 0,0.003 0.001,0.004 0,0.003 -0.001,0.002 0))" msgstr "" @@ -5098,10 +5139,10 @@ msgstr "" #: reference_raster.xml:3203 #, no-c-format msgid "" -", , , , " -", , " +", , , , , , " msgstr "" #. Tag: refname @@ -5114,8 +5155,8 @@ msgstr "" #: reference_raster.xml:3218 #, no-c-format msgid "" -"Returns a point geometry of the pixel's upper-left " -"corner." +"Returns a point geometry of the pixel's upper-left corner." msgstr "" #. Tag: funcprototype @@ -5131,15 +5172,15 @@ msgstr "" #. Tag: para #: reference_raster.xml:3235 #, no-c-format -msgid "" -"Returns a point geometry of the pixel's upper-left corner." +msgid "Returns a point geometry of the pixel's upper-left corner." msgstr "" #. Tag: programlisting #: reference_raster.xml:3241 #, no-c-format msgid "" -"SELECT ST_AsText(ST_PixelAsPoint(rast, 1, 1)) FROM dummy_rast WHERE rid = 1;\n" +"SELECT ST_AsText(ST_PixelAsPoint(rast, 1, 1)) FROM dummy_rast WHERE rid = " +"1;\n" "\n" " st_astext \n" "----------------\n" @@ -5150,11 +5191,10 @@ msgstr "" #: reference_raster.xml:3246 #, no-c-format msgid "" -", , , , , " +", , , , , " msgstr "" #. Tag: refname @@ -5169,8 +5209,8 @@ msgstr "" msgid "" "Returns a point geometry for each pixel of a raster band along " "with the value, the X and the Y raster coordinates of each pixel. The " -"coordinates of the point geometry are of the pixel's upper-left " -"corner." +"coordinates of the point geometry are of the pixel's upper-left corner." msgstr "" #. Tag: funcprototype @@ -5179,9 +5219,8 @@ msgstr "" msgid "" "geometry ST_PixelAsPoints " "raster rast " -"integer " -"band=1 boolean " +"integer band=1 boolean " "exclude_nodata_value=TRUE" msgstr "" @@ -5190,8 +5229,8 @@ msgstr "" #, no-c-format msgid "" "Returns a point geometry for each pixel of a raster band along with " -"the value, the X and the Y raster coordinates of each pixel. The coordinates" -" of the point geometry are of the pixel's upper-left corner." +"the value, the X and the Y raster coordinates of each pixel. The coordinates " +"of the point geometry are of the pixel's upper-left corner." msgstr "" #. Tag: para @@ -5206,7 +5245,8 @@ msgstr "" #: reference_raster.xml:3292 #, no-c-format msgid "" -"SELECT x, y, val, ST_AsText(geom) FROM (SELECT (ST_PixelAsPoints(rast, 1)).* FROM dummy_rast WHERE rid = 2) foo;\n" +"SELECT x, y, val, ST_AsText(geom) FROM (SELECT (ST_PixelAsPoints(rast, 1)).* " +"FROM dummy_rast WHERE rid = 2) foo;\n" "\n" " x | y | val | st_astext \n" "---+---+-----+------------------------------\n" @@ -5241,10 +5281,10 @@ msgstr "" #: reference_raster.xml:3297 #, no-c-format msgid "" -", , , ," -" , " +", , , , , " msgstr "" #. Tag: refname @@ -5257,8 +5297,8 @@ msgstr "" #: reference_raster.xml:3312 #, no-c-format msgid "" -"Returns the centroid (point geometry) of the area represented by" -" a pixel." +"Returns the centroid (point geometry) of the area represented by " +"a pixel." msgstr "" #. Tag: funcprototype @@ -5283,7 +5323,8 @@ msgstr "" #: reference_raster.xml:3335 #, no-c-format msgid "" -"SELECT ST_AsText(ST_PixelAsCentroid(rast, 1, 1)) FROM dummy_rast WHERE rid = 1;\n" +"SELECT ST_AsText(ST_PixelAsCentroid(rast, 1, 1)) FROM dummy_rast WHERE rid = " +"1;\n" "\n" " st_astext \n" "--------------\n" @@ -5294,10 +5335,9 @@ msgstr "" #: reference_raster.xml:3340 #, no-c-format msgid "" -", , , ," -" , " +", , , , , " msgstr "" #. Tag: refname @@ -5310,10 +5350,10 @@ msgstr "" #: reference_raster.xml:3355 #, no-c-format msgid "" -"Returns the centroid (point geometry) for each pixel of a raster" -" band along with the value, the X and the Y raster coordinates of each " -"pixel. The point geometry is the centroid of the area represented by a " -"pixel." +"Returns the centroid (point geometry) for each pixel of a raster " +"band along with the value, the X and the Y raster coordinates of each pixel. " +"The point geometry is the centroid of the area represented by a pixel." msgstr "" #. Tag: funcprototype @@ -5322,9 +5362,8 @@ msgstr "" msgid "" "geometry ST_PixelAsCentroids " "raster rast " -"integer " -"band=1 boolean " +"integer band=1 boolean " "exclude_nodata_value=TRUE" msgstr "" @@ -5341,7 +5380,8 @@ msgstr "" #: reference_raster.xml:3386 #, no-c-format msgid "" -"SELECT x, y, val, ST_AsText(geom) FROM (SELECT (ST_PixelAsCentroids(rast, 1)).* FROM dummy_rast WHERE rid = 2) foo;\n" +"SELECT x, y, val, ST_AsText(geom) FROM (SELECT (ST_PixelAsCentroids(rast, " +"1)).* FROM dummy_rast WHERE rid = 2) foo;\n" " x | y | val | st_astext \n" "---+---+-----+--------------------------------\n" " 1 | 1 | 253 | POINT(3427927.775 5793243.975)\n" @@ -5375,10 +5415,9 @@ msgstr "" #: reference_raster.xml:3391 #, no-c-format msgid "" -", , , ," -" , " +", , , , , " msgstr "" #. Tag: refname @@ -5403,31 +5442,29 @@ msgstr "" #: reference_raster.xml:3410 #, no-c-format msgid "" -" double precision " -"ST_Value raster " -"rast geometry " -"pt boolean " -" exclude_nodata_value=true " -" double precision " -"ST_Value raster " -"rast integer " -"bandnum geometry " -"pt boolean " -" exclude_nodata_value=true " -" double precision " -"ST_Value raster " -"rast integer " -"columnx integer " -"rowy boolean " -"exclude_nodata_value=true " -" double precision " -"ST_Value raster " -"rast integer " -"bandnum integer " -"columnx integer " -"rowy boolean " +" double precision ST_Value raster rast geometry pt boolean " +"exclude_nodata_value=true " +" double precision ST_Value raster rast integer bandnum geometry pt boolean " +"exclude_nodata_value=true " +" double precision ST_Value raster rast integer columnx integer rowy boolean " +"exclude_nodata_value=true " +" double precision ST_Value raster rast integer bandnum integer columnx integer rowy boolean " "exclude_nodata_value=true " msgstr "" @@ -5436,11 +5473,11 @@ msgstr "" #, no-c-format msgid "" "Returns the value of a given band in a given columnx, rowy pixel or at a " -"given geometry point. Band numbers start at 1 and band is assumed to be 1 if" -" not specified. If exclude_nodata_value is set to true, " +"given geometry point. Band numbers start at 1 and band is assumed to be 1 if " +"not specified. If exclude_nodata_value is set to true, " "then only non nodata pixels are considered. If " -"exclude_nodata_value is set to false, then all pixels are" -" considered." +"exclude_nodata_value is set to false, then all pixels are " +"considered." msgstr "" #. Tag: para @@ -5455,8 +5492,10 @@ msgstr "" msgid "" "-- get raster values at particular postgis geometry points\n" "-- the srid of your geometry should be same as for your raster\n" -"SELECT rid, ST_Value(rast, foo.pt_geom) As b1pval, ST_Value(rast, 2, foo.pt_geom) As b2pval\n" -"FROM dummy_rast CROSS JOIN (SELECT ST_SetSRID(ST_Point(3427927.77, 5793243.76), 0) As pt_geom) As foo\n" +"SELECT rid, ST_Value(rast, foo.pt_geom) As b1pval, ST_Value(rast, 2, foo." +"pt_geom) As b2pval\n" +"FROM dummy_rast CROSS JOIN (SELECT ST_SetSRID(ST_Point(3427927.77, " +"5793243.76), 0) As pt_geom) As foo\n" "WHERE rid=2;\n" "\n" " rid | b1pval | b2pval\n" @@ -5512,7 +5551,8 @@ msgstr "" #: reference_raster.xml:3458 #, no-c-format msgid "" -"--- Get all values in bands 1,2,3 of each pixel same as above but returning the upper left point point of each pixel --\n" +"--- Get all values in bands 1,2,3 of each pixel same as above but returning " +"the upper left point point of each pixel --\n" "SELECT ST_AsText(ST_SetSRID(\n" " ST_Point(ST_UpperLeftX(rast) + ST_ScaleX(rast)*x, \n" " ST_UpperLeftY(rast) + ST_ScaleY(rast)*y), \n" @@ -5536,7 +5576,8 @@ msgstr "" #, no-c-format msgid "" "--- Get a polygon formed by union of all pixels \n" -" that fall in a particular value range and intersect particular polygon --\n" +" that fall in a particular value range and intersect particular " +"polygon --\n" "SELECT ST_AsText(ST_Union(pixpolyg)) As shadow\n" "FROM (SELECT ST_Translate(ST_MakeEnvelope(\n" " ST_UpperLeftX(rast), ST_UpperLeftY(rast), \n" @@ -5551,21 +5592,31 @@ msgid "" "WHERE \n" " ST_Intersects(\n" " pixpolyg, \n" -" ST_GeomFromText('POLYGON((3427928 5793244,3427927.75 5793243.75,3427928 5793243.75,3427928 5793244))',0)\n" +" ST_GeomFromText('POLYGON((3427928 5793244,3427927.75 " +"5793243.75,3427928 5793243.75,3427928 5793244))',0)\n" " ) AND b2val != 254;\n" "\n" "\n" " shadow\n" "------------------------------------------------------------------------------------\n" -" MULTIPOLYGON(((3427928 5793243.9,3427928 5793243.85,3427927.95 5793243.85,3427927.95 5793243.9,\n" -" 3427927.95 5793243.95,3427928 5793243.95,3427928.05 5793243.95,3427928.05 5793243.9,3427928 5793243.9)),((3427927.95 5793243.9,3427927.95 579324\n" -"3.85,3427927.9 5793243.85,3427927.85 5793243.85,3427927.85 5793243.9,3427927.9 5793243.9,3427927.9 5793243.95,\n" -"3427927.95 5793243.95,3427927.95 5793243.9)),((3427927.85 5793243.75,3427927.85 5793243.7,3427927.8 5793243.7,3427927.8 5793243.75\n" -",3427927.8 5793243.8,3427927.8 5793243.85,3427927.85 5793243.85,3427927.85 5793243.8,3427927.85 5793243.75)),\n" -"((3427928.05 5793243.75,3427928.05 5793243.7,3427928 5793243.7,3427927.95 5793243.7,3427927.95 5793243.75,3427927.95 5793243.8,3427\n" -"927.95 5793243.85,3427928 5793243.85,3427928 5793243.8,3427928.05 5793243.8,\n" -"3427928.05 5793243.75)),((3427927.95 5793243.75,3427927.95 5793243.7,3427927.9 5793243.7,3427927.85 5793243.7,\n" -"3427927.85 5793243.75,3427927.85 5793243.8,3427927.85 5793243.85,3427927.9 5793243.85,\n" +" MULTIPOLYGON(((3427928 5793243.9,3427928 5793243.85,3427927.95 " +"5793243.85,3427927.95 5793243.9,\n" +" 3427927.95 5793243.95,3427928 5793243.95,3427928.05 5793243.95,3427928.05 " +"5793243.9,3427928 5793243.9)),((3427927.95 5793243.9,3427927.95 579324\n" +"3.85,3427927.9 5793243.85,3427927.85 5793243.85,3427927.85 " +"5793243.9,3427927.9 5793243.9,3427927.9 5793243.95,\n" +"3427927.95 5793243.95,3427927.95 5793243.9)),((3427927.85 " +"5793243.75,3427927.85 5793243.7,3427927.8 5793243.7,3427927.8 5793243.75\n" +",3427927.8 5793243.8,3427927.8 5793243.85,3427927.85 5793243.85,3427927.85 " +"5793243.8,3427927.85 5793243.75)),\n" +"((3427928.05 5793243.75,3427928.05 5793243.7,3427928 5793243.7,3427927.95 " +"5793243.7,3427927.95 5793243.75,3427927.95 5793243.8,3427\n" +"927.95 5793243.85,3427928 5793243.85,3427928 5793243.8,3427928.05 " +"5793243.8,\n" +"3427928.05 5793243.75)),((3427927.95 5793243.75,3427927.95 " +"5793243.7,3427927.9 5793243.7,3427927.85 5793243.7,\n" +"3427927.85 5793243.75,3427927.85 5793243.8,3427927.85 5793243.85,3427927.9 " +"5793243.85,\n" "3427927.95 5793243.85,3427927.95 5793243.8,3427927.95 5793243.75)))" msgstr "" @@ -5574,9 +5625,12 @@ msgstr "" #, no-c-format msgid "" "--- Checking all the pixels of a large raster tile can take a long time.\n" -"--- You can dramatically improve speed at some lose of precision by orders of magnitude \n" -"-- by sampling pixels using the step optional parameter of generate_series. \n" -"-- This next example does the same as previous but by checking 1 for every 4 (2x2) pixels and putting in the last checked\n" +"--- You can dramatically improve speed at some lose of precision by orders " +"of magnitude \n" +"-- by sampling pixels using the step optional parameter of " +"generate_series. \n" +"-- This next example does the same as previous but by checking 1 for every " +"4 (2x2) pixels and putting in the last checked\n" "-- putting in the checked pixel as the value for subsequent 4\n" " \n" "SELECT ST_AsText(ST_Union(pixpolyg)) As shadow\n" @@ -5593,28 +5647,33 @@ msgid "" "WHERE \n" " ST_Intersects(\n" " pixpolyg, \n" -" ST_GeomFromText('POLYGON((3427928 5793244,3427927.75 5793243.75,3427928 5793243.75,3427928 5793244))',0)\n" +" ST_GeomFromText('POLYGON((3427928 5793244,3427927.75 " +"5793243.75,3427928 5793243.75,3427928 5793244))',0)\n" " ) AND b2val != 254;\n" "\n" " shadow\n" "------------------------------------------------------------------------------------\n" -" MULTIPOLYGON(((3427927.9 5793243.85,3427927.8 5793243.85,3427927.8 5793243.95,\n" -" 3427927.9 5793243.95,3427928 5793243.95,3427928.1 5793243.95,3427928.1 5793243.85,3427928 5793243.85,3427927.9 5793243.85)),\n" -" ((3427927.9 5793243.65,3427927.8 5793243.65,3427927.8 5793243.75,3427927.8 5793243.85,3427927.9 5793243.85,\n" -" 3427928 5793243.85,3427928 5793243.75,3427928.1 5793243.75,3427928.1 5793243.65,3427928 5793243.65,3427927.9 5793243.65)))" +" MULTIPOLYGON(((3427927.9 5793243.85,3427927.8 5793243.85,3427927.8 " +"5793243.95,\n" +" 3427927.9 5793243.95,3427928 5793243.95,3427928.1 5793243.95,3427928.1 " +"5793243.85,3427928 5793243.85,3427927.9 5793243.85)),\n" +" ((3427927.9 5793243.65,3427927.8 5793243.65,3427927.8 5793243.75,3427927.8 " +"5793243.85,3427927.9 5793243.85,\n" +" 3427928 5793243.85,3427928 5793243.75,3427928.1 5793243.75,3427928.1 " +"5793243.65,3427928 5793243.65,3427927.9 5793243.65)))" msgstr "" #. Tag: para #: reference_raster.xml:3466 #, no-c-format msgid "" -", , , , " -", , , , , , , , , " +", , , , , , , " +", , , , , , " msgstr "" #. Tag: refname @@ -5636,33 +5695,29 @@ msgstr "" #: reference_raster.xml:3494 #, no-c-format msgid "" -" double precision " -"ST_NearestValue raster " -" rast integer " -" bandnum geometry " -" pt boolean " -"exclude_nodata_value=true " -" double precision " -"ST_NearestValue raster " -" rast geometry " -" pt boolean " -"exclude_nodata_value=true " -" double precision " -"ST_NearestValue raster " -" rast integer " -" bandnum integer " -" columnx integer " -" rowy boolean " -"exclude_nodata_value=true " -" double precision " -"ST_NearestValue raster " -" rast integer " -" columnx integer " -" rowy boolean " +" double precision ST_NearestValue raster rast integer bandnum geometry pt boolean " +"exclude_nodata_value=true " +" double precision ST_NearestValue raster rast geometry pt boolean " +"exclude_nodata_value=true " +" double precision ST_NearestValue raster rast integer bandnum integer columnx integer rowy boolean " +"exclude_nodata_value=true " +" double precision ST_NearestValue raster rast integer columnx integer rowy boolean " "exclude_nodata_value=true " msgstr "" @@ -5670,20 +5725,19 @@ msgstr "" #: reference_raster.xml:3531 #, no-c-format msgid "" -"Returns the nearest non-NODATA value of a given band in a" -" given columnx, rowy pixel or at a specific geometric point. If the columnx," -" rowy pixel or the pixel at the specified geometric point is " -"NODATA, the function will find the nearest pixel to the " -"columnx, rowy pixel or geometric point whose value is not " -"NODATA." +"Returns the nearest non-NODATA value of a given band in a " +"given columnx, rowy pixel or at a specific geometric point. If the columnx, " +"rowy pixel or the pixel at the specified geometric point is NODATA, the function will find the nearest pixel to the columnx, rowy " +"pixel or geometric point whose value is not NODATA." msgstr "" #. Tag: para #: reference_raster.xml:3534 reference_raster.xml:3621 #, no-c-format msgid "" -"Band numbers start at 1 and bandnum is assumed to be 1 if" -" not specified. If exclude_nodata_value is set to false, " +"Band numbers start at 1 and bandnum is assumed to be 1 if " +"not specified. If exclude_nodata_value is set to false, " "then all pixels include nodata pixels are considered to " "intersect and return value. If exclude_nodata_value is " "not passed in then reads it from metadata of raster." @@ -5711,8 +5765,10 @@ msgid "" " ST_SetValue(\n" " ST_SetValue(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(5, 5, -2, 2, 1, -1, 0, 0, 0),\n" -" '8BUI'::text, 1, 0\n" +" ST_MakeEmptyRaster(5, " +"5, -2, 2, 1, -1, 0, 0, 0),\n" +" '8BUI'::" +"text, 1, 0\n" " ),\n" " 1, 1, 0.\n" " ),\n" @@ -5747,8 +5803,10 @@ msgid "" " ST_SetValue(\n" " ST_SetValue(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(5, 5, -2, 2, 1, -1, 0, 0, 0),\n" -" '8BUI'::text, 1, 0\n" +" ST_MakeEmptyRaster(5, " +"5, -2, 2, 1, -1, 0, 0, 0),\n" +" '8BUI'::" +"text, 1, 0\n" " ),\n" " 1, 1, 0.\n" " ),\n" @@ -5784,50 +5842,46 @@ msgstr "" #, no-c-format msgid "" "Returns a 2-D double precision array of the non-NODATA " -"values around a given band's pixel specified by either a columnX and rowY or" -" a geometric point expressed in the same spatial reference coordinate system" -" as the raster." +"values around a given band's pixel specified by either a columnX and rowY or " +"a geometric point expressed in the same spatial reference coordinate system " +"as the raster." msgstr "" #. Tag: funcsynopsis #: reference_raster.xml:3573 #, no-c-format msgid "" -" double precision[][] " -"ST_Neighborhood raster " -" rast integer " -" bandnum integer " -" columnX integer " -" rowY integer " -" distanceX integer " -" distanceY boolean " -"exclude_nodata_value=true " -" double precision[][] " -"ST_Neighborhood raster " -" rast integer " -" columnX integer " -" rowY integer " -" distanceX integer " -" distanceY boolean " -"exclude_nodata_value=true " -" double precision[][] " -"ST_Neighborhood raster " -" rast integer " -" bandnum geometry " -" pt integer " -" distanceX integer " -" distanceY boolean " -"exclude_nodata_value=true " -" double precision[][] " -"ST_Neighborhood raster " -" rast geometry " -" pt integer " -" distanceX integer " -" distanceY boolean " +" double precision[][] ST_Neighborhood raster rast integer bandnum integer columnX integer rowY integer distanceX integer distanceY boolean " +"exclude_nodata_value=true " +" double precision[][] ST_Neighborhood raster rast integer columnX integer rowY integer distanceX integer distanceY boolean " +"exclude_nodata_value=true " +" double precision[][] ST_Neighborhood raster rast integer bandnum geometry pt integer distanceX integer distanceY boolean " +"exclude_nodata_value=true " +" double precision[][] ST_Neighborhood raster rast geometry pt integer distanceX integer distanceY boolean " "exclude_nodata_value=true " msgstr "" @@ -5836,14 +5890,14 @@ msgstr "" #, no-c-format msgid "" "Returns a 2-D double precision array of the non-NODATA " -"values around a given band's pixel specified by either a columnX and rowY or" -" a geometric point expressed in the same spatial reference coordinate system" -" as the raster. The distanceX and " -"distanceY parameters define the number of pixels around " -"the specified pixel in the X and Y axes, e.g. I want all values within 3 " -"pixel distance along the X axis and 2 pixel distance along the Y axis around" -" my pixel of interest. The center value of the 2-D array will be the value " -"at the pixel specified by the columnX and rowY or the geometric point." +"values around a given band's pixel specified by either a columnX and rowY or " +"a geometric point expressed in the same spatial reference coordinate system " +"as the raster. The distanceX and distanceY parameters define the number of pixels around the specified pixel " +"in the X and Y axes, e.g. I want all values within 3 pixel distance along " +"the X axis and 2 pixel distance along the Y axis around my pixel of " +"interest. The center value of the 2-D array will be the value at the pixel " +"specified by the columnX and rowY or the geometric point." msgstr "" #. Tag: para @@ -5875,7 +5929,8 @@ msgid "" " SELECT\n" " ST_SetValues(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(5, 5, -2, 2, 1, -1, 0, 0, 0),\n" +" ST_MakeEmptyRaster(5, 5, -2, 2, 1, -1, 0, 0, " +"0),\n" " '8BUI'::text, 1, 0\n" " ),\n" " 1, 1, 1, ARRAY[\n" @@ -5905,7 +5960,8 @@ msgid "" " SELECT\n" " ST_SetValues(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(5, 5, -2, 2, 1, -1, 0, 0, 0),\n" +" ST_MakeEmptyRaster(5, 5, -2, 2, 1, -1, 0, 0, " +"0),\n" " '8BUI'::text, 1, 0\n" " ),\n" " 1, 1, 1, ARRAY[\n" @@ -5935,7 +5991,8 @@ msgid "" "FROM (\n" " ST_SetValues(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(5, 5, -2, 2, 1, -1, 0, 0, 0),\n" +" ST_MakeEmptyRaster(5, 5, -2, 2, 1, -1, 0, 0, " +"0),\n" " '8BUI'::text, 1, 0\n" " ),\n" " 1, 1, 1, ARRAY[\n" @@ -5959,9 +6016,9 @@ msgstr "" #, no-c-format msgid "" ", , , , , , , " +"linkend=\"RT_ST_Sum4ma\"/>, , , , " msgstr "" #. Tag: refname @@ -5987,26 +6044,24 @@ msgid "" "raster rast " "integer bandnum " "geometry geom " -"double precision " -"newvalue " -"raster ST_SetValue " -"raster rast " -"geometry geom " -"double precision " -"newvalue " -"raster ST_SetValue " +"double precision newvalue raster " +"ST_SetValue raster " +"rast geometry " +"geom double precision newvalue " +" raster ST_SetValue " "raster rast " "integer bandnum " "integer columnx " "integer rowy " -"double precision " -"newvalue " -"raster ST_SetValue " -"raster rast " -"integer columnx " -"integer rowy " -"double precision " -"newvalue " +"double precision newvalue raster " +"ST_SetValue raster " +"rast integer " +"columnx integer " +"rowy double precision newvalue " msgstr "" #. Tag: para @@ -6023,8 +6078,8 @@ msgstr "" #, no-c-format msgid "" "Enhanced: 2.1.0 Geometry variant of ST_SetValue() now supports any geometry " -"type, not just point. The geometry variant is a wrapper around the geomval[]" -" variant of ST_SetValues()" +"type, not just point. The geometry variant is a wrapper around the geomval[] " +"variant of ST_SetValues()" msgstr "" #. Tag: programlisting @@ -6045,7 +6100,8 @@ msgid "" "\n" " val | st_astext\n" "-----+-------------------------------------------------------------------\n" -" 50 | POLYGON((3427927.75 5793244,3427927.75 5793243.95,3427927.8 579324 ...\n" +" 50 | POLYGON((3427927.75 5793244,3427927.75 5793243.95,3427927.8 " +"579324 ...\n" " 249 | POLYGON((3427927.95 5793243.95,3427927.95 5793243.85,3427928 57932 ..." msgstr "" @@ -6054,7 +6110,8 @@ msgstr "" #, no-c-format msgid "" "-- Store the changed raster --\n" -" UPDATE dummy_rast SET rast = ST_SetValue(rast,1, ST_Point(3427927.75, 5793243.95),100)\n" +" UPDATE dummy_rast SET rast = ST_SetValue(rast,1, " +"ST_Point(3427927.75, 5793243.95),100)\n" " WHERE rid = 2 ;" msgstr "" @@ -6086,45 +6143,43 @@ msgid "" "integer nband " "integer columnx " "integer rowy " -"double precision[][] " -"newvalueset boolean[][] " -" noset=NULL boolean" -" keepnodata=FALSE " -" raster ST_SetValues" -" raster rast " -"integer nband " -"integer columnx " -"integer rowy " -"double precision[][] " -"newvalueset double " -"precision nosetvalue " -"boolean " +"double precision[][] newvalueset boolean[][] " +"noset=NULL boolean " "keepnodata=FALSE " " raster ST_SetValues " "raster rast " "integer nband " "integer columnx " "integer rowy " -"integer width " -"integer height " -"double precision " -"newvalue boolean " +"double precision[][] newvalueset double precision " +"nosetvalue boolean " "keepnodata=FALSE " " raster ST_SetValues " "raster rast " +"integer nband " "integer columnx " "integer rowy " "integer width " "integer height " -"double precision " -"newvalue boolean " -"keepnodata=FALSE " +"double precision newvalue boolean keepnodata=FALSE raster " +"ST_SetValues raster " +"rast integer " +"columnx integer " +"rowy integer " +"width integer " +"height double precision newvalue boolean keepnodata=FALSE " " raster ST_SetValues " "raster rast " "integer nband " -"geomval[] " -"geomvalset boolean " -" keepnodata=FALSE " +"geomval[] geomvalset boolean keepnodata=FALSE " msgstr "" #. Tag: para @@ -6140,8 +6195,8 @@ msgstr "" #, no-c-format msgid "" "If keepnodata is TRUE, those pixels whose values are " -"NODATA will not be set with the corresponding value in " -"newvalueset." +"NODATA will not be set with the corresponding value in newvalueset." msgstr "" #. Tag: para @@ -6150,9 +6205,9 @@ msgstr "" msgid "" "For Variant 1, the specific pixels to be set are determined by the " "columnx, rowy pixel coordinates and " -"the dimensions of the newvalueset array. " -"noset can be used to prevent pixels with values present " -"in newvalueset from being set (due to PostgreSQL not " +"the dimensions of the newvalueset array. noset can be used to prevent pixels with values present in " +"newvalueset from being set (due to PostgreSQL not " "permitting ragged/jagged arrays). See example Variant 1." msgstr "" @@ -6228,10 +6283,12 @@ msgid "" " ST_PixelAsPolygons(\n" " ST_SetValues(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, 0),\n" +" ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, " +"0),\n" " 1, '8BUI', 1, 0\n" " ),\n" -" 1, 2, 2, ARRAY[[9, 9], [9, 9]]::double precision[][]\n" +" 1, 2, 2, ARRAY[[9, 9], [9, 9]]::double precision[]" +"[]\n" " )\n" " ) AS poly\n" ") foo\n" @@ -6274,10 +6331,12 @@ msgid "" " ST_PixelAsPolygons(\n" " ST_SetValues(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, 0),\n" +" ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, " +"0),\n" " 1, '8BUI', 1, 0\n" " ),\n" -" 1, 1, 1, ARRAY[[9, 9, 9], [9, NULL, 9], [9, 9, 9]]::double precision[][]\n" +" 1, 1, 1, ARRAY[[9, 9, 9], [9, NULL, 9], [9, 9, 9]]::" +"double precision[][]\n" " )\n" " ) AS poly\n" ") foo\n" @@ -6320,11 +6379,13 @@ msgid "" " ST_PixelAsPolygons(\n" " ST_SetValues(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, 0),\n" +" ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, " +"0),\n" " 1, '8BUI', 1, 0\n" " ),\n" " 1, 1, 1,\n" -" ARRAY[[9, 9, 9], [9, NULL, 9], [9, 9, 9]]::double precision[][],\n" +" ARRAY[[9, 9, 9], [9, NULL, 9], [9, 9, 9]]::" +"double precision[][],\n" " ARRAY[[false], [true]]::boolean[][]\n" " )\n" " ) AS poly\n" @@ -6369,13 +6430,15 @@ msgid "" " ST_SetValues(\n" " ST_SetValue(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, 0),\n" +" ST_MakeEmptyRaster(3, 3, 0, 0, 1, " +"-1, 0, 0, 0),\n" " 1, '8BUI', 1, 0\n" " ),\n" " 1, 1, 1, NULL\n" " ),\n" " 1, 1, 1,\n" -" ARRAY[[9, 9, 9], [9, NULL, 9], [9, 9, 9]]::double precision[][],\n" +" ARRAY[[9, 9, 9], [9, NULL, 9], [9, 9, 9]]::" +"double precision[][],\n" " ARRAY[[false], [true]]::boolean[][],\n" " TRUE\n" " )\n" @@ -6428,10 +6491,12 @@ msgid "" " ST_PixelAsPolygons(\n" " ST_SetValues(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, 0),\n" +" ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, " +"0),\n" " 1, '8BUI', 1, 0\n" " ),\n" -" 1, 1, 1, ARRAY[[-1, -1, -1], [-1, 9, 9], [-1, 9, 9]]::double precision[][], -1\n" +" 1, 1, 1, ARRAY[[-1, -1, -1], [-1, 9, 9], [-1, 9, " +"9]]::double precision[][], -1\n" " )\n" " ) AS poly\n" ") foo\n" @@ -6455,7 +6520,8 @@ msgstr "" #, no-c-format msgid "" "/*\n" -"This example is like the previous one. Instead of nosetvalue = -1, nosetvalue = NULL\n" +"This example is like the previous one. Instead of nosetvalue = -1, " +"nosetvalue = NULL\n" "\n" "The ST_SetValues() does the following...\n" "\n" @@ -6476,10 +6542,12 @@ msgid "" " ST_PixelAsPolygons(\n" " ST_SetValues(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, 0),\n" +" ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, " +"0),\n" " 1, '8BUI', 1, 0\n" " ),\n" -" 1, 1, 1, ARRAY[[NULL, NULL, NULL], [NULL, 9, 9], [NULL, 9, 9]]::double precision[][], NULL::double precision\n" +" 1, 1, 1, ARRAY[[NULL, NULL, NULL], [NULL, 9, 9], " +"[NULL, 9, 9]]::double precision[][], NULL::double precision\n" " )\n" " ) AS poly\n" ") foo\n" @@ -6528,7 +6596,8 @@ msgid "" " ST_PixelAsPolygons(\n" " ST_SetValues(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, 0),\n" +" ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, " +"0),\n" " 1, '8BUI', 1, 0\n" " ),\n" " 1, 2, 2, 2, 2, 9\n" @@ -6575,7 +6644,8 @@ msgid "" " ST_SetValues(\n" " ST_SetValue(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, 0),\n" +" ST_MakeEmptyRaster(3, 3, 0, 0, 1, " +"-1, 0, 0, 0),\n" " 1, '8BUI', 1, 0\n" " ),\n" " 1, 2, 2, NULL\n" @@ -6610,11 +6680,14 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT 1 AS rid, ST_AddBand(ST_MakeEmptyRaster(5, 5, 0, 0, 1, -1, 0, 0, 0), 1, '8BUI', 0, 0) AS rast\n" +" SELECT 1 AS rid, ST_AddBand(ST_MakeEmptyRaster(5, 5, 0, 0, 1, -1, 0, " +"0, 0), 1, '8BUI', 0, 0) AS rast\n" "), bar AS (\n" " SELECT 1 AS gid, 'SRID=0;POINT(2.5 -2.5)'::geometry geom UNION ALL\n" -" SELECT 2 AS gid, 'SRID=0;POLYGON((1 -1, 4 -1, 4 -4, 1 -4, 1 -1))'::geometry geom UNION ALL\n" -" SELECT 3 AS gid, 'SRID=0;POLYGON((0 0, 5 0, 5 -1, 1 -1, 1 -4, 0 -4, 0 0))'::geometry geom UNION ALL\n" +" SELECT 2 AS gid, 'SRID=0;POLYGON((1 -1, 4 -1, 4 -4, 1 -4, 1 -1))'::" +"geometry geom UNION ALL\n" +" SELECT 3 AS gid, 'SRID=0;POLYGON((0 0, 5 0, 5 -1, 1 -1, 1 -4, 0 -4, " +"0 0))'::geometry geom UNION ALL\n" " SELECT 4 AS gid, 'SRID=0;MULTIPOINT(0 0, 4 4, 4 -4)'::geometry\n" ")\n" "SELECT\n" @@ -6623,12 +6696,19 @@ msgid "" "CROSS JOIN bar t2\n" "ORDER BY rid, gid;\n" "\n" -" rid | gid | st_dumpvalues \n" -"-----+-----+---------------------------------------------------------------------------------------------------------------------------------------------\n" -" 1 | 1 | (1,\"{{NULL,NULL,NULL,NULL,NULL},{NULL,NULL,NULL,NULL,NULL},{NULL,NULL,1,NULL,NULL},{NULL,NULL,NULL,NULL,NULL},{NULL,NULL,NULL,NULL,NULL}}\")\n" -" 1 | 2 | (1,\"{{NULL,NULL,NULL,NULL,NULL},{NULL,2,2,2,NULL},{NULL,2,2,2,NULL},{NULL,2,2,2,NULL},{NULL,NULL,NULL,NULL,NULL}}\")\n" -" 1 | 3 | (1,\"{{3,3,3,3,3},{3,NULL,NULL,NULL,NULL},{3,NULL,NULL,NULL,NULL},{3,NULL,NULL,NULL,NULL},{NULL,NULL,NULL,NULL,NULL}}\")\n" -" 1 | 4 | (1,\"{{4,NULL,NULL,NULL,NULL},{NULL,NULL,NULL,NULL,NULL},{NULL,NULL,NULL,NULL,NULL},{NULL,NULL,NULL,NULL,NULL},{NULL,NULL,NULL,NULL,4}}\")\n" +" rid | gid | " +"st_dumpvalues \n" +"-----+-----" +"+---------------------------------------------------------------------------------------------------------------------------------------------\n" +" 1 | 1 | (1,\"{{NULL,NULL,NULL,NULL,NULL},{NULL,NULL,NULL,NULL,NULL}," +"{NULL,NULL,1,NULL,NULL},{NULL,NULL,NULL,NULL,NULL},{NULL,NULL,NULL,NULL," +"NULL}}\")\n" +" 1 | 2 | (1,\"{{NULL,NULL,NULL,NULL,NULL},{NULL,2,2,2,NULL},{NULL,2,2,2," +"NULL},{NULL,2,2,2,NULL},{NULL,NULL,NULL,NULL,NULL}}\")\n" +" 1 | 3 | (1,\"{{3,3,3,3,3},{3,NULL,NULL,NULL,NULL},{3,NULL,NULL,NULL," +"NULL},{3,NULL,NULL,NULL,NULL},{NULL,NULL,NULL,NULL,NULL}}\")\n" +" 1 | 4 | (1,\"{{4,NULL,NULL,NULL,NULL},{NULL,NULL,NULL,NULL,NULL},{NULL," +"NULL,NULL,NULL,NULL},{NULL,NULL,NULL,NULL,NULL},{NULL,NULL,NULL,NULL,4}}\")\n" "(4 rows)" msgstr "" @@ -6645,15 +6725,19 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT 1 AS rid, ST_AddBand(ST_MakeEmptyRaster(5, 5, 0, 0, 1, -1, 0, 0, 0), 1, '8BUI', 0, 0) AS rast\n" +" SELECT 1 AS rid, ST_AddBand(ST_MakeEmptyRaster(5, 5, 0, 0, 1, -1, 0, " +"0, 0), 1, '8BUI', 0, 0) AS rast\n" "), bar AS (\n" " SELECT 1 AS gid, 'SRID=0;POINT(2.5 -2.5)'::geometry geom UNION ALL\n" -" SELECT 2 AS gid, 'SRID=0;POLYGON((1 -1, 4 -1, 4 -4, 1 -4, 1 -1))'::geometry geom UNION ALL\n" -" SELECT 3 AS gid, 'SRID=0;POLYGON((0 0, 5 0, 5 -1, 1 -1, 1 -4, 0 -4, 0 0))'::geometry geom UNION ALL\n" +" SELECT 2 AS gid, 'SRID=0;POLYGON((1 -1, 4 -1, 4 -4, 1 -4, 1 -1))'::" +"geometry geom UNION ALL\n" +" SELECT 3 AS gid, 'SRID=0;POLYGON((0 0, 5 0, 5 -1, 1 -1, 1 -4, 0 -4, " +"0 0))'::geometry geom UNION ALL\n" " SELECT 4 AS gid, 'SRID=0;MULTIPOINT(0 0, 4 4, 4 -4)'::geometry\n" ")\n" "SELECT\n" -" t1.rid, t2.gid, t3.gid, ST_DumpValues(ST_SetValues(rast, 1, ARRAY[ROW(t2.geom, t2.gid), ROW(t3.geom, t3.gid)]::geomval[]))\n" +" t1.rid, t2.gid, t3.gid, ST_DumpValues(ST_SetValues(rast, 1, " +"ARRAY[ROW(t2.geom, t2.gid), ROW(t3.geom, t3.gid)]::geomval[]))\n" "FROM foo t1\n" "CROSS JOIN bar t2\n" "CROSS JOIN bar t3\n" @@ -6661,9 +6745,12 @@ msgid "" " AND t3.gid = 2\n" "ORDER BY t1.rid, t2.gid, t3.gid;\n" "\n" -" rid | gid | gid | st_dumpvalues \n" -"-----+-----+-----+---------------------------------------------------------------------------------------------------------------------\n" -" 1 | 1 | 2 | (1,\"{{NULL,NULL,NULL,NULL,NULL},{NULL,2,2,2,NULL},{NULL,2,2,2,NULL},{NULL,2,2,2,NULL},{NULL,NULL,NULL,NULL,NULL}}\")\n" +" rid | gid | gid | " +"st_dumpvalues \n" +"-----+-----+-----" +"+---------------------------------------------------------------------------------------------------------------------\n" +" 1 | 1 | 2 | (1,\"{{NULL,NULL,NULL,NULL,NULL},{NULL,2,2,2,NULL}," +"{NULL,2,2,2,NULL},{NULL,2,2,2,NULL},{NULL,NULL,NULL,NULL,NULL}}\")\n" "(1 row)" msgstr "" @@ -6678,15 +6765,19 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT 1 AS rid, ST_AddBand(ST_MakeEmptyRaster(5, 5, 0, 0, 1, -1, 0, 0, 0), 1, '8BUI', 0, 0) AS rast\n" +" SELECT 1 AS rid, ST_AddBand(ST_MakeEmptyRaster(5, 5, 0, 0, 1, -1, 0, " +"0, 0), 1, '8BUI', 0, 0) AS rast\n" "), bar AS (\n" " SELECT 1 AS gid, 'SRID=0;POINT(2.5 -2.5)'::geometry geom UNION ALL\n" -" SELECT 2 AS gid, 'SRID=0;POLYGON((1 -1, 4 -1, 4 -4, 1 -4, 1 -1))'::geometry geom UNION ALL\n" -" SELECT 3 AS gid, 'SRID=0;POLYGON((0 0, 5 0, 5 -1, 1 -1, 1 -4, 0 -4, 0 0))'::geometry geom UNION ALL\n" +" SELECT 2 AS gid, 'SRID=0;POLYGON((1 -1, 4 -1, 4 -4, 1 -4, 1 -1))'::" +"geometry geom UNION ALL\n" +" SELECT 3 AS gid, 'SRID=0;POLYGON((0 0, 5 0, 5 -1, 1 -1, 1 -4, 0 -4, " +"0 0))'::geometry geom UNION ALL\n" " SELECT 4 AS gid, 'SRID=0;MULTIPOINT(0 0, 4 4, 4 -4)'::geometry\n" ")\n" "SELECT\n" -" t1.rid, t2.gid, t3.gid, ST_DumpValues(ST_SetValues(rast, 1, ARRAY[ROW(t2.geom, t2.gid), ROW(t3.geom, t3.gid)]::geomval[]))\n" +" t1.rid, t2.gid, t3.gid, ST_DumpValues(ST_SetValues(rast, 1, " +"ARRAY[ROW(t2.geom, t2.gid), ROW(t3.geom, t3.gid)]::geomval[]))\n" "FROM foo t1\n" "CROSS JOIN bar t2\n" "CROSS JOIN bar t3\n" @@ -6694,9 +6785,12 @@ msgid "" " AND t3.gid = 1\n" "ORDER BY t1.rid, t2.gid, t3.gid;\n" "\n" -" rid | gid | gid | st_dumpvalues \n" -"-----+-----+-----+---------------------------------------------------------------------------------------------------------------------\n" -" 1 | 2 | 1 | (1,\"{{NULL,NULL,NULL,NULL,NULL},{NULL,2,2,2,NULL},{NULL,2,1,2,NULL},{NULL,2,2,2,NULL},{NULL,NULL,NULL,NULL,NULL}}\")\n" +" rid | gid | gid | " +"st_dumpvalues \n" +"-----+-----+-----" +"+---------------------------------------------------------------------------------------------------------------------\n" +" 1 | 2 | 1 | (1,\"{{NULL,NULL,NULL,NULL,NULL},{NULL,2,2,2,NULL}," +"{NULL,2,1,2,NULL},{NULL,2,2,2,NULL},{NULL,NULL,NULL,NULL,NULL}}\")\n" "(1 row)" msgstr "" @@ -6704,8 +6798,8 @@ msgstr "" #: reference_raster.xml:3870 #, no-c-format msgid "" -", , " +", , " msgstr "" #. Tag: refname @@ -6724,17 +6818,16 @@ msgstr "" #: reference_raster.xml:3887 #, no-c-format msgid "" -" setof record " -"ST_DumpValues raster " -" rast integer[] " -"nband=NULL boolean " -" exclude_nodata_value=true " -" double precision[][] " -"ST_DumpValues raster " -" rast integer " +" setof record ST_DumpValues raster rast integer[] nband=NULL boolean " +"exclude_nodata_value=true double precision[][] " +"ST_DumpValues raster " +"rast integer " "nband boolean " -"exclude_nodata_value=true " -"" +"exclude_nodata_value=true " msgstr "" #. Tag: para @@ -6742,8 +6835,8 @@ msgstr "" #, no-c-format msgid "" "Get the values of the specified band as a 2-dimension array (first index is " -"row, second is column). If nband is NULL or not provided," -" all raster bands are processed." +"row, second is column). If nband is NULL or not provided, " +"all raster bands are processed." msgstr "" #. Tag: programlisting @@ -6751,7 +6844,9 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, 0), 1, '8BUI', 1, 0), 2, '32BF', 3, -9999), 3, '16BSI', 0, 0) AS rast\n" +" SELECT ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, " +"0, 1, -1, 0, 0, 0), 1, '8BUI', 1, 0), 2, '32BF', 3, -9999), 3, '16BSI', 0, " +"0) AS rast\n" ")\n" "SELECT\n" " (ST_DumpValues(rast)).*\n" @@ -6770,7 +6865,9 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, 0), 1, '8BUI', 1, 0), 2, '32BF', 3, -9999), 3, '16BSI', 0, 0) AS rast\n" +" SELECT ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, " +"0, 1, -1, 0, 0, 0), 1, '8BUI', 1, 0), 2, '32BF', 3, -9999), 3, '16BSI', 0, " +"0) AS rast\n" ")\n" "SELECT\n" " (ST_DumpValues(rast, ARRAY[3, 1])).*\n" @@ -6788,7 +6885,8 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT ST_SetValue(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, 0, 0, 0), 1, '8BUI', 1, 0), 1, 2, 5) AS rast\n" +" SELECT ST_SetValue(ST_AddBand(ST_MakeEmptyRaster(3, 3, 0, 0, 1, -1, " +"0, 0, 0), 1, '8BUI', 1, 0), 1, 2, 5) AS rast\n" ")\n" "SELECT\n" " (ST_DumpValues(rast, 1))[2][1]\n" @@ -6803,7 +6901,8 @@ msgstr "" #. Tag: para #: reference_raster.xml:3936 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -6816,45 +6915,45 @@ msgstr "" #: reference_raster.xml:3948 #, no-c-format msgid "" -"Get the columnx, rowy coordinates of the pixel whose value equals the search" -" value." +"Get the columnx, rowy coordinates of the pixel whose value equals the search " +"value." msgstr "" #. Tag: funcsynopsis #: reference_raster.xml:3954 #, no-c-format msgid "" -" setof record " -"ST_PixelOfValue raster " -" rast integer " -" nband double " -"precision[] search " -"boolean exclude_nodata_value=true " -" setof record " -"ST_PixelOfValue raster " -" rast double " +" setof record ST_PixelOfValue raster rast integer nband double precision[] search boolean " +"exclude_nodata_value=true setof record " +"ST_PixelOfValue raster rast double " "precision[] search " -"boolean exclude_nodata_value=true " -" setof record " -"ST_PixelOfValue raster " -" rast integer " -" nband double " +"boolean exclude_nodata_value=true setof record " +"ST_PixelOfValue raster rast integer nband double " "precision search " -"boolean exclude_nodata_value=true " -" setof record " -"ST_PixelOfValue raster " -" rast double " +"boolean exclude_nodata_value=true setof record " +"ST_PixelOfValue raster rast double " "precision search " -"boolean exclude_nodata_value=true " -" " +"boolean exclude_nodata_value=true " msgstr "" #. Tag: para #: reference_raster.xml:4015 #, no-c-format msgid "" -"Get the columnx, rowy coordinates of the pixel whose value equals the search" -" value. If no band is specified, then band 1 is assumed." +"Get the columnx, rowy coordinates of the pixel whose value equals the search " +"value. If no band is specified, then band 1 is assumed." msgstr "" #. Tag: programlisting @@ -6872,8 +6971,10 @@ msgid "" " ST_SetValue(\n" " ST_SetValue(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(5, 5, -2, 2, 1, -1, 0, 0, 0),\n" -" '8BUI'::text, 1, 0\n" +" ST_MakeEmptyRaster(5, " +"5, -2, 2, 1, -1, 0, 0, 0),\n" +" '8BUI'::" +"text, 1, 0\n" " ),\n" " 1, 1, 0\n" " ),\n" @@ -6938,23 +7039,21 @@ msgstr "" #: reference_raster.xml:4041 #, no-c-format msgid "" -" raster " -"ST_SetGeoReference raster " -" rast text " -"georefcoords text " +" raster ST_SetGeoReference raster rast text georefcoords text " "format=GDAL " -" raster " -"ST_SetGeoReference raster " -" rast double " -"precision upperleftx " -"double precision " +" raster ST_SetGeoReference raster rast double precision upperleftx double precision " "upperlefty double " "precision scalex " -"double precision " -"scaley double precision " -" skewx double " -"precision skewy " +"double precision scaley double precision skewx double precision " +"skewy " msgstr "" #. Tag: para @@ -6991,8 +7090,8 @@ msgstr "" #: reference_raster.xml:4080 #, no-c-format msgid "" -"Enhanced: 2.1.0 Addition of ST_SetGeoReference(raster, double precision, " -"...) variant" +"Enhanced: 2.1.0 Addition of ST_SetGeoReference(raster, double " +"precision, ...) variant" msgstr "" #. Tag: programlisting @@ -7007,23 +7106,32 @@ msgid "" "FROM foo\n" "UNION ALL\n" "SELECT\n" -" 1, (ST_Metadata(ST_SetGeoReference(rast, '10 0 0 -10 0.1 0.1', 'GDAL'))).*\n" +" 1, (ST_Metadata(ST_SetGeoReference(rast, '10 0 0 -10 0.1 0.1', " +"'GDAL'))).*\n" "FROM foo\n" "UNION ALL\n" "SELECT\n" -" 2, (ST_Metadata(ST_SetGeoReference(rast, '10 0 0 -10 5.1 -4.9', 'ESRI'))).*\n" +" 2, (ST_Metadata(ST_SetGeoReference(rast, '10 0 0 -10 5.1 -4.9', " +"'ESRI'))).*\n" "FROM foo\n" "UNION ALL\n" "SELECT\n" -" 3, (ST_Metadata(ST_SetGeoReference(rast, 1, 1, 10, -10, 0.001, 0.001))).*\n" +" 3, (ST_Metadata(ST_SetGeoReference(rast, 1, 1, 10, -10, 0.001, " +"0.001))).*\n" "FROM foo\n" "\n" -" rid | upperleftx | upperlefty | width | height | scalex | scaley | skewx | skewy | srid | numbands \n" -"-----+--------------------+--------------------+-------+--------+--------+--------+-------+-------+------+----------\n" -" 0 | 0 | 0 | 5 | 5 | 1 | -1 | 0 | 0 | 0 | 0\n" -" 1 | 0.1 | 0.1 | 5 | 5 | 10 | -10 | 0 | 0 | 0 | 0\n" -" 2 | 0.0999999999999996 | 0.0999999999999996 | 5 | 5 | 10 | -10 | 0 | 0 | 0 | 0\n" -" 3 | 1 | 1 | 5 | 5 | 10 | -10 | 0.001 | 0.001 | 0 | 0" +" rid | upperleftx | upperlefty | width | height | scalex | " +"scaley | skewx | skewy | srid | numbands \n" +"-----+--------------------+--------------------+-------+--------+--------" +"+--------+-------+-------+------+----------\n" +" 0 | 0 | 0 | 5 | 5 | 1 " +"| -1 | 0 | 0 | 0 | 0\n" +" 1 | 0.1 | 0.1 | 5 | 5 | 10 " +"| -10 | 0 | 0 | 0 | 0\n" +" 2 | 0.0999999999999996 | 0.0999999999999996 | 5 | 5 | 10 " +"| -10 | 0 | 0 | 0 | 0\n" +" 3 | 1 | 1 | 5 | 5 | 10 " +"| -10 | 0.001 | 0.001 | 0 | 0" msgstr "" #. Tag: para @@ -7059,8 +7167,8 @@ msgstr "" #: reference_raster.xml:4115 #, no-c-format msgid "" -"Uniformly rotate the raster. Rotation is in radian. Refer to World File for more " +"Uniformly rotate the raster. Rotation is in radian. Refer to World File for more " "details." msgstr "" @@ -7074,10 +7182,14 @@ msgid "" "FROM (\n" " SELECT ST_SetRotation(rast, 15) AS rast1, rast as rast2 FROM dummy_rast\n" ") AS foo;\n" -" st_scalex | st_scaley | st_skewx | st_skewy | st_scalex | st_scaley | st_skewx | st_skewy\n" -"---------------------+---------------------+--------------------+--------------------+-----------+-----------+----------+----------\n" -" -1.51937582571764 | -2.27906373857646 | 1.95086352047135 | 1.30057568031423 | 2 | 3 | 0 | 0\n" -" -0.0379843956429411 | -0.0379843956429411 | 0.0325143920078558 | 0.0325143920078558 | 0.05 | -0.05 | 0 | 0" +" st_scalex | st_scaley | st_skewx | " +"st_skewy | st_scalex | st_scaley | st_skewx | st_skewy\n" +"---------------------+---------------------+--------------------" +"+--------------------+-----------+-----------+----------+----------\n" +" -1.51937582571764 | -2.27906373857646 | 1.95086352047135 | " +"1.30057568031423 | 2 | 3 | 0 | 0\n" +" -0.0379843956429411 | -0.0379843956429411 | 0.0325143920078558 | " +"0.0325143920078558 | 0.05 | -0.05 | 0 | 0" msgstr "" #. Tag: refname @@ -7100,12 +7212,12 @@ msgstr "" msgid "" " raster ST_SetScale " "raster rast " -"float8 xy " -" raster " -"ST_SetScale raster " -"rast float8 " -"x float8 " -"y " +"float8 xy raster ST_SetScale raster rast float8 x float8 y " msgstr "" #. Tag: para @@ -7113,8 +7225,8 @@ msgstr "" #, no-c-format msgid "" "Sets the X and Y size of pixels in units of coordinate reference system. " -"Number units/pixel width/height. If only one unit passed in, assumed X and Y" -" are the same number." +"Number units/pixel width/height. If only one unit passed in, assumed X and Y " +"are the same number." msgstr "" #. Tag: para @@ -7146,7 +7258,8 @@ msgid "" " SET rast = ST_SetScale(rast, 1.5)\n" "WHERE rid = 2;\n" "\n" -"SELECT ST_ScaleX(rast) As pixx, ST_ScaleY(rast) As pixy, Box3D(rast) As newbox\n" +"SELECT ST_ScaleX(rast) As pixx, ST_ScaleY(rast) As pixy, Box3D(rast) As " +"newbox\n" "FROM dummy_rast\n" "WHERE rid = 2;\n" "\n" @@ -7163,7 +7276,8 @@ msgid "" " SET rast = ST_SetScale(rast, 1.5, 0.55)\n" "WHERE rid = 2;\n" "\n" -"SELECT ST_ScaleX(rast) As pixx, ST_ScaleY(rast) As pixy, Box3D(rast) As newbox\n" +"SELECT ST_ScaleX(rast) As pixx, ST_ScaleY(rast) As pixy, Box3D(rast) As " +"newbox\n" "FROM dummy_rast\n" "WHERE rid = 2;\n" "\n" @@ -7198,12 +7312,12 @@ msgstr "" msgid "" " raster ST_SetSkew " "raster rast " -"float8 skewxy " -" raster " -"ST_SetSkew raster " -"rast float8 " -"skewx float8 " -"skewy " +"float8 skewxy raster ST_SetSkew raster rast float8 skewx float8 skewy " msgstr "" #. Tag: para @@ -7211,9 +7325,8 @@ msgstr "" #, no-c-format msgid "" "Sets the georeference X and Y skew (or rotation parameter). If only one is " -"passed in, sets X and Y to the same value. Refer to World File for more " -"details." +"passed in, sets X and Y to the same value. Refer to World File for more details." msgstr "" #. Tag: programlisting @@ -7260,8 +7373,8 @@ msgstr "" #: reference_raster.xml:4221 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -7297,8 +7410,8 @@ msgstr "" #: reference_raster.xml:4252 #, no-c-format msgid "" -"This function does not transform the raster in any way - it simply sets meta" -" data defining the spatial ref of the coordinate reference system that it's " +"This function does not transform the raster in any way - it simply sets meta " +"data defining the spatial ref of the coordinate reference system that it's " "currently in. Useful for transformations later." msgstr "" @@ -7328,9 +7441,8 @@ msgstr "" msgid "" "raster ST_SetUpperLeft " "raster rast " -"double precision x" -" double precision " -"y" +"double precision x " +"double precision y" msgstr "" #. Tag: para @@ -7366,9 +7478,9 @@ msgstr "" #: reference_raster.xml:4306 #, no-c-format msgid "" -"Resample a raster using a specified resampling algorithm, new dimensions, an" -" arbitrary grid corner and a set of raster georeferencing attributes defined" -" or borrowed from another raster." +"Resample a raster using a specified resampling algorithm, new dimensions, an " +"arbitrary grid corner and a set of raster georeferencing attributes defined " +"or borrowed from another raster." msgstr "" #. Tag: funcsynopsis @@ -7380,43 +7492,35 @@ msgid "" "integer width " "integer height " "double precision " -"gridx=NULL double precision " -"gridy=NULL double precision " -"skewx=0 double precision " -"skewy=0 text " -"algorithm=NearestNeighbour double precision " -"maxerr=0.125 " -" raster ST_Resample " -"raster rast " -"double precision " -"scalex=0 double precision " -"scaley=0 double precision " -"gridx=NULL double precision " -"gridy=NULL double precision " -"skewx=0 double precision " -"skewy=0 text " -"algorithm=NearestNeighbor double precision " -"maxerr=0.125 " -" raster ST_Resample " -"raster rast " -"raster ref " +"gridx=NULL double precision gridy=NULL double precision " +"skewx=0 double precision skewy=0 " "text " "algorithm=NearestNeighbour double precision " -"maxerr=0.125 boolean " +"choice=\"opt\">double precision maxerr=0.125 raster " +"ST_Resample raster " +"rast double " +"precision scalex=0 double precision scaley=0 double precision gridx=NULL double precision gridy=NULL double precision " +"skewx=0 double precision skewy=0 " +"text " +"algorithm=NearestNeighbor double precision maxerr=0.125 raster " +"ST_Resample raster " +"rast raster " +"ref text algorithm=NearestNeighbour double precision maxerr=0.125 boolean " "usescale=true " " raster ST_Resample " "raster rast " @@ -7424,8 +7528,8 @@ msgid "" "boolean usescale " "text " "algorithm=NearestNeighbour double precision " -"maxerr=0.125 " +"choice=\"opt\">double precision maxerr=0.125 " msgstr "" #. Tag: para @@ -7443,8 +7547,8 @@ msgstr "" #: reference_raster.xml:4366 #, no-c-format msgid "" -"New pixel values are computed using the NearestNeighbor (English or American" -" spelling), Bilinear, Cubic, CubicSpline or Lanczos resampling algorithm. " +"New pixel values are computed using the NearestNeighbor (English or American " +"spelling), Bilinear, Cubic, CubicSpline or Lanczos resampling algorithm. " "Default is NearestNeighbor which is the fastest but produce the worst " "interpolation." msgstr "" @@ -7497,7 +7601,8 @@ msgid "" " FROM aerials.boston \n" " WHERE ST_Intersects(rast,\n" " ST_Transform(\n" -" ST_MakeEnvelope(-71.128, 42.2392,-71.1277, 42.2397, 4326),26986)\n" +" ST_MakeEnvelope(-71.128, 42.2392,-71.1277, 42.2397, " +"4326),26986)\n" " )\n" " LIMIT 1\n" ") AS foo;\n" @@ -7535,21 +7640,18 @@ msgstr "" msgid "" " raster ST_Rescale " "raster rast " -"double precision " -"scalexy text " -"algorithm=NearestNeighbour double precision " -"maxerr=0.125 " -" raster ST_Rescale " -"raster rast " -"double precision " -"scalex double precision " -" scaley text " +"double precision scalexy text " "algorithm=NearestNeighbour double precision " -"maxerr=0.125 " +"choice=\"opt\">double precision maxerr=0.125 raster " +"ST_Rescale raster " +"rast double precision scalex double " +"precision scaley text algorithm=NearestNeighbour double precision maxerr=0.125 " msgstr "" #. Tag: para @@ -7558,8 +7660,8 @@ msgstr "" msgid "" "Resample a raster by adjusting only its scale (or pixel size). New pixel " "values are computed using the NearestNeighbor (english or american " -"spelling), Bilinear, Cubic, CubicSpline or Lanczos resampling algorithm. The" -" default is NearestNeighbor which is the fastest but results in the worst " +"spelling), Bilinear, Cubic, CubicSpline or Lanczos resampling algorithm. The " +"default is NearestNeighbor which is the fastest but results in the worst " "interpolation." msgstr "" @@ -7567,8 +7669,8 @@ msgstr "" #: reference_raster.xml:4433 #, no-c-format msgid "" -"scalex and scaley define the new pixel" -" size. scaley must often be negative to get well oriented raster." +"scalex and scaley define the new pixel " +"size. scaley must often be negative to get well oriented raster." msgstr "" #. Tag: para @@ -7590,8 +7692,8 @@ msgid "" "ST_SetScale only changes the metadata (or georeference) of the raster to " "correct an originally mis-specified scaling. ST_Rescale results in a raster " "having different width and height computed to fit the geographic extent of " -"the input raster. ST_SetScale do not modify the width, nor the height of the" -" raster." +"the input raster. ST_SetScale do not modify the width, nor the height of the " +"raster." msgstr "" #. Tag: para @@ -7614,14 +7716,16 @@ msgstr "" #, no-c-format msgid "" "-- the original raster pixel size\n" -"SELECT ST_PixelWidth(ST_AddBand(ST_MakeEmptyRaster(100, 100, 0, 0, 0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0)) width\n" +"SELECT ST_PixelWidth(ST_AddBand(ST_MakeEmptyRaster(100, 100, 0, 0, 0.001, " +"-0.001, 0, 0, 4269), '8BUI'::text, 1, 0)) width\n" "\n" " width\n" "----------\n" "0.001\n" "\n" "-- the rescaled raster raster pixel size\n" -"SELECT ST_PixelWidth(ST_Rescale(ST_AddBand(ST_MakeEmptyRaster(100, 100, 0, 0, 0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0), 0.0015)) width\n" +"SELECT ST_PixelWidth(ST_Rescale(ST_AddBand(ST_MakeEmptyRaster(100, 100, 0, " +"0, 0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0), 0.0015)) width\n" "\n" " width\n" "----------\n" @@ -7659,20 +7763,18 @@ msgstr "" msgid "" " raster ST_Reskew " "raster rast " -"double precision " -"skewxy text" -" algorithm=NearestNeighbour " -"double precision " -"maxerr=0.125 " -" raster ST_Reskew " -"raster rast " -"double precision " -"skewx double precision " -" skewy text " +"double precision skewxy text " "algorithm=NearestNeighbour double precision " -"maxerr=0.125 " +"choice=\"opt\">double precision maxerr=0.125 raster " +"ST_Reskew raster " +"rast double precision skewx double " +"precision skewy text algorithm=NearestNeighbour double precision maxerr=0.125 " msgstr "" #. Tag: para @@ -7681,8 +7783,8 @@ msgstr "" msgid "" "Resample a raster by adjusting only its skew (or rotation parameters). New " "pixel values are computed using the NearestNeighbor (english or american " -"spelling), Bilinear, Cubic, CubicSpline or Lanczos resampling algorithm. The" -" default is NearestNeighbor which is the fastest but results in the worst " +"spelling), Bilinear, Cubic, CubicSpline or Lanczos resampling algorithm. The " +"default is NearestNeighbor which is the fastest but results in the worst " "interpolation." msgstr "" @@ -7713,8 +7815,8 @@ msgstr "" #, no-c-format msgid "" "ST_Reskew is different from in that " -"ST_SetSkew do not resample the raster to match the raster extent. ST_SetSkew" -" only changes the metadata (or georeference) of the raster to correct an " +"ST_SetSkew do not resample the raster to match the raster extent. ST_SetSkew " +"only changes the metadata (or georeference) of the raster to correct an " "originally mis-specified skew. ST_Reskew results in a raster having " "different width and height computed to fit the geographic extent of the " "input raster. ST_SetSkew do not modify the width, nor the height of the " @@ -7733,10 +7835,12 @@ msgstr "" #, no-c-format msgid "" "-- the original raster pixel size\n" -"SELECT ST_Rotation(ST_AddBand(ST_MakeEmptyRaster(100, 100, 0, 0, 0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0))\n" +"SELECT ST_Rotation(ST_AddBand(ST_MakeEmptyRaster(100, 100, 0, 0, 0.001, " +"-0.001, 0, 0, 4269), '8BUI'::text, 1, 0))\n" " \n" "-- the rescaled raster raster pixel size\n" -"SELECT ST_Rotation(ST_Reskew(ST_AddBand(ST_MakeEmptyRaster(100, 100, 0, 0, 0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0), 0.0015))" +"SELECT ST_Rotation(ST_Reskew(ST_AddBand(ST_MakeEmptyRaster(100, 100, 0, 0, " +"0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0), 0.0015))" msgstr "" #. Tag: para @@ -7767,39 +7871,36 @@ msgstr "" #: reference_raster.xml:4537 #, no-c-format msgid "" -" raster ST_SnapToGrid" -" raster rast " -"double precision " -"gridx double precision " -" gridy text " +" raster ST_SnapToGrid " +"raster rast " +"double precision gridx double precision gridy text " "algorithm=NearestNeighbour double precision " -"maxerr=0.125 double precision scalex=DEFAULT " -"0 double precision " -" scaley=DEFAULT 0 " -" raster ST_SnapToGrid" -" raster rast " -"double precision " -"gridx double precision " -" gridy double " -"precision scalex " -"double precision " -"scaley text" -" algorithm=NearestNeighbour " -"double precision " -"maxerr=0.125 " -" raster ST_SnapToGrid" -" raster rast " -"double precision " -"gridx double precision " -" gridy double " -"precision scalexy text " +"choice=\"opt\">double precision maxerr=0.125 double precision scalex=DEFAULT 0 double precision scaley=DEFAULT 0 raster " +"ST_SnapToGrid raster " +"rast double precision gridx double " +"precision gridy " +"double precision scalex double precision scaley text " +"algorithm=NearestNeighbour double precision maxerr=0.125 raster " +"ST_SnapToGrid raster " +"rast double precision gridx double " +"precision gridy " +"double precision scalexy text " "algorithm=NearestNeighbour double precision " -"maxerr=0.125 " +"choice=\"opt\">double precision maxerr=0.125 " msgstr "" #. Tag: para @@ -7808,8 +7909,8 @@ msgstr "" msgid "" "Resample a raster by snapping it to a grid defined by an arbitrary pixel " "corner (gridx & gridy) and optionally a pixel size (scalex & " -"scaley). New pixel values are computed using the NearestNeighbor (english or" -" american spelling), Bilinear, Cubic, CubicSpline or Lanczos resampling " +"scaley). New pixel values are computed using the NearestNeighbor (english or " +"american spelling), Bilinear, Cubic, CubicSpline or Lanczos resampling " "algorithm. The default is NearestNeighbor which is the fastest but results " "in the worst interpolation." msgstr "" @@ -7851,10 +7952,12 @@ msgstr "" #, no-c-format msgid "" "-- the original raster pixel size\n" -"SELECT ST_UpperLeftX(ST_AddBand(ST_MakeEmptyRaster(10, 10, 0, 0, 0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0))\n" +"SELECT ST_UpperLeftX(ST_AddBand(ST_MakeEmptyRaster(10, 10, 0, 0, 0.001, " +"-0.001, 0, 0, 4269), '8BUI'::text, 1, 0))\n" " \n" "-- the rescaled raster raster pixel size\n" -"SELECT ST_UpperLeftX(ST_SnapToGrid(ST_AddBand(ST_MakeEmptyRaster(10, 10, 0, 0, 0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0), 0.0002, 0.0002))" +"SELECT ST_UpperLeftX(ST_SnapToGrid(ST_AddBand(ST_MakeEmptyRaster(10, 10, 0, " +"0, 0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0), 0.0002, 0.0002))" msgstr "" #. Tag: para @@ -7886,46 +7989,44 @@ msgid "" "integer width " "integer height " "text " -"algorithm=NearestNeighbor double precision " -"maxerr=0.125 " -" raster ST_Resize " -"raster rast " -"double precision " -"percentwidth double " +"algorithm=NearestNeighbor double precision maxerr=0.125 raster " +"ST_Resize raster " +"rast double precision percentwidth double " "precision percentheight text " -"algorithm=NearestNeighbor double precision " -"maxerr=0.125 " +"choice=\"opt\">text algorithm=NearestNeighbor double precision maxerr=0.125 " " raster ST_Resize " "raster rast " "text width " "text height " "text " -"algorithm=NearestNeighbor double precision " -"maxerr=0.125 " +"algorithm=NearestNeighbor double precision maxerr=0.125 " msgstr "" #. Tag: para #: reference_raster.xml:4648 #, no-c-format msgid "" -"Resize a raster to a new width/height. The new width/height can be specified" -" in exact number of pixels or a percentage of the raster's width/height. The" -" extent of the the new raster will be the same as the extent of the provided" -" raster." +"Resize a raster to a new width/height. The new width/height can be specified " +"in exact number of pixels or a percentage of the raster's width/height. The " +"extent of the the new raster will be the same as the extent of the provided " +"raster." msgstr "" #. Tag: para #: reference_raster.xml:4652 #, no-c-format msgid "" -"New pixel values are computed using the NearestNeighbor (english or american" -" spelling), Bilinear, Cubic, CubicSpline or Lanczos resampling algorithm. " -"The default is NearestNeighbor which is the fastest but results in the worst" -" interpolation." +"New pixel values are computed using the NearestNeighbor (english or american " +"spelling), Bilinear, Cubic, CubicSpline or Lanczos resampling algorithm. The " +"default is NearestNeighbor which is the fastest but results in the worst " +"interpolation." msgstr "" #. Tag: para @@ -7938,8 +8039,8 @@ msgstr "" #: reference_raster.xml:4660 #, no-c-format msgid "" -"Variant 2 expects decimal values between zero (0) and one (1) indicating the" -" percentage of the input raster's width/height." +"Variant 2 expects decimal values between zero (0) and one (1) indicating the " +"percentage of the input raster's width/height." msgstr "" #. Tag: para @@ -7947,8 +8048,8 @@ msgstr "" #, no-c-format msgid "" "Variant 3 takes either the actual width/height of the output raster or a " -"textual percentage (\"20%\") indicating the percentage of the input raster's" -" width/height." +"textual percentage (\"20%\") indicating the percentage of the input raster's " +"width/height." msgstr "" #. Tag: para @@ -7966,7 +8067,8 @@ msgid "" " 1 AS rid, \n" " ST_Resize(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(1000, 1000, 0, 0, 1, -1, 0, 0, 0)\n" +" ST_MakeEmptyRaster(1000, 1000, 0, 0, 1, -1, 0, 0, " +"0)\n" " , 1, '8BUI', 255, 0\n" " )\n" " , '50%', '500') AS rast\n" @@ -7975,7 +8077,8 @@ msgid "" " 2 AS rid, \n" " ST_Resize(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(1000, 1000, 0, 0, 1, -1, 0, 0, 0)\n" +" ST_MakeEmptyRaster(1000, 1000, 0, 0, 1, -1, 0, 0, " +"0)\n" " , 1, '8BUI', 255, 0\n" " )\n" " , 500, 100) AS rast\n" @@ -7984,7 +8087,8 @@ msgid "" " 3 AS rid, \n" " ST_Resize(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(1000, 1000, 0, 0, 1, -1, 0, 0, 0)\n" +" ST_MakeEmptyRaster(1000, 1000, 0, 0, 1, -1, 0, 0, " +"0)\n" " , 1, '8BUI', 255, 0\n" " )\n" " , 0.25, 0.9) AS rast\n" @@ -7993,11 +8097,16 @@ msgid "" ")\n" "SELECT rid, (meta).* FROM bar\n" "\n" -" rid | upperleftx | upperlefty | width | height | scalex | scaley | skewx | skewy | srid | numbands \n" -"-----+------------+------------+-------+--------+--------+--------+-------+-------+------+----------\n" -" 1 | 0 | 0 | 500 | 500 | 1 | -1 | 0 | 0 | 0 | 1\n" -" 2 | 0 | 0 | 500 | 100 | 1 | -1 | 0 | 0 | 0 | 1\n" -" 3 | 0 | 0 | 250 | 900 | 1 | -1 | 0 | 0 | 0 | 1\n" +" rid | upperleftx | upperlefty | width | height | scalex | scaley | skewx | " +"skewy | srid | numbands \n" +"-----+------------+------------+-------+--------+--------+--------+-------" +"+-------+------+----------\n" +" 1 | 0 | 0 | 500 | 500 | 1 | -1 | 0 " +"| 0 | 0 | 1\n" +" 2 | 0 | 0 | 500 | 100 | 1 | -1 | 0 " +"| 0 | 0 | 1\n" +" 3 | 0 | 0 | 250 | 900 | 1 | -1 | 0 " +"| 0 | 0 | 1\n" "(3 rows)" msgstr "" @@ -8005,8 +8114,8 @@ msgstr "" #: reference_raster.xml:4677 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -8033,30 +8142,27 @@ msgid "" "raster rast " "integer srid " "text " -"algorithm=NearestNeighbor double precision " -"maxerr=0.125 double precision " -"scalex double precision " -"scaley " -"raster ST_Transform " -"raster rast " -"integer srid " -"double precision " -"scalex double precision " -" scaley text " -"algorithm=NearestNeighbor double precision " +"algorithm=NearestNeighbor double precision maxerr=0.125 double precision " +"scalex double precision scaley raster ST_Transform raster rast integer srid double precision " +"scalex double precision scaley text algorithm=NearestNeighbor double precision " "maxerr=0.125 " " raster ST_Transform " "raster rast " "raster alignto " "text " -"algorithm=NearestNeighbor double precision " -"maxerr=0.125 " +"algorithm=NearestNeighbor double precision maxerr=0.125 " msgstr "" #. Tag: para @@ -8065,8 +8171,8 @@ msgstr "" msgid "" "Reprojects a raster in a known spatial reference system to another known " "spatial reference system using specified pixel warping algorithm. Uses " -"'NearestNeighbor' if no algorithm is specified and maxerror percent of 0.125" -" if no maxerr is specified." +"'NearestNeighbor' if no algorithm is specified and maxerror percent of 0.125 " +"if no maxerr is specified." msgstr "" #. Tag: para @@ -8094,12 +8200,12 @@ msgstr "" #, no-c-format msgid "" "If you find your transformation support is not working right, you may need " -"to set the environment variable PROJSO to the .so or .dll projection library" -" your PostGIS is using. This just needs to have the name of the file. So for" -" example on windows, you would in Control Panel -> System -> Environment " +"to set the environment variable PROJSO to the .so or .dll projection library " +"your PostGIS is using. This just needs to have the name of the file. So for " +"example on windows, you would in Control Panel -> System -> Environment " "Variables add a system variable called PROJSO and set it " -"to libproj.dll (if you are using proj 4.6.1). You'll have" -" to restart your PostgreSQL service/daemon after this change." +"to libproj.dll (if you are using proj 4.6.1). You'll have " +"to restart your PostgreSQL service/daemon after this change." msgstr "" #. Tag: para @@ -8119,7 +8225,8 @@ msgid "" " , ST_Transform(rast,4326, 'Bilinear') AS wgs_84_bilin\n" " FROM aerials.o_2_boston \n" " WHERE ST_Intersects(rast,\n" -" ST_Transform(ST_MakeEnvelope(-71.128, 42.2392,-71.1277, 42.2397, 4326),26986) )\n" +" ST_Transform(ST_MakeEnvelope(-71.128, " +"42.2392,-71.1277, 42.2397, 4326),26986) )\n" " LIMIT 1) As foo;\n" " \n" " w_before | w_after | h_before | h_after\n" @@ -8160,17 +8267,26 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT 0 AS rid, ST_AddBand(ST_MakeEmptyRaster(2, 2, -500000, 600000, 100, -100, 0, 0, 2163), 1, '16BUI', 1, 0) AS rast UNION ALL\n" -" SELECT 1, ST_AddBand(ST_MakeEmptyRaster(2, 2, -499800, 600000, 100, -100, 0, 0, 2163), 1, '16BUI', 2, 0) AS rast UNION ALL\n" -" SELECT 2, ST_AddBand(ST_MakeEmptyRaster(2, 2, -499600, 600000, 100, -100, 0, 0, 2163), 1, '16BUI', 3, 0) AS rast UNION ALL\n" +" SELECT 0 AS rid, ST_AddBand(ST_MakeEmptyRaster(2, 2, -500000, " +"600000, 100, -100, 0, 0, 2163), 1, '16BUI', 1, 0) AS rast UNION ALL\n" +" SELECT 1, ST_AddBand(ST_MakeEmptyRaster(2, 2, -499800, 600000, 100, " +"-100, 0, 0, 2163), 1, '16BUI', 2, 0) AS rast UNION ALL\n" +" SELECT 2, ST_AddBand(ST_MakeEmptyRaster(2, 2, -499600, 600000, 100, " +"-100, 0, 0, 2163), 1, '16BUI', 3, 0) AS rast UNION ALL\n" "\n" -" SELECT 3, ST_AddBand(ST_MakeEmptyRaster(2, 2, -500000, 599800, 100, -100, 0, 0, 2163), 1, '16BUI', 10, 0) AS rast UNION ALL\n" -" SELECT 4, ST_AddBand(ST_MakeEmptyRaster(2, 2, -499800, 599800, 100, -100, 0, 0, 2163), 1, '16BUI', 20, 0) AS rast UNION ALL\n" -" SELECT 5, ST_AddBand(ST_MakeEmptyRaster(2, 2, -499600, 599800, 100, -100, 0, 0, 2163), 1, '16BUI', 30, 0) AS rast UNION ALL\n" +" SELECT 3, ST_AddBand(ST_MakeEmptyRaster(2, 2, -500000, 599800, 100, " +"-100, 0, 0, 2163), 1, '16BUI', 10, 0) AS rast UNION ALL\n" +" SELECT 4, ST_AddBand(ST_MakeEmptyRaster(2, 2, -499800, 599800, 100, " +"-100, 0, 0, 2163), 1, '16BUI', 20, 0) AS rast UNION ALL\n" +" SELECT 5, ST_AddBand(ST_MakeEmptyRaster(2, 2, -499600, 599800, 100, " +"-100, 0, 0, 2163), 1, '16BUI', 30, 0) AS rast UNION ALL\n" "\n" -" SELECT 6, ST_AddBand(ST_MakeEmptyRaster(2, 2, -500000, 599600, 100, -100, 0, 0, 2163), 1, '16BUI', 100, 0) AS rast UNION ALL\n" -" SELECT 7, ST_AddBand(ST_MakeEmptyRaster(2, 2, -499800, 599600, 100, -100, 0, 0, 2163), 1, '16BUI', 200, 0) AS rast UNION ALL\n" -" SELECT 8, ST_AddBand(ST_MakeEmptyRaster(2, 2, -499600, 599600, 100, -100, 0, 0, 2163), 1, '16BUI', 300, 0) AS rast\n" +" SELECT 6, ST_AddBand(ST_MakeEmptyRaster(2, 2, -500000, 599600, 100, " +"-100, 0, 0, 2163), 1, '16BUI', 100, 0) AS rast UNION ALL\n" +" SELECT 7, ST_AddBand(ST_MakeEmptyRaster(2, 2, -499800, 599600, 100, " +"-100, 0, 0, 2163), 1, '16BUI', 200, 0) AS rast UNION ALL\n" +" SELECT 8, ST_AddBand(ST_MakeEmptyRaster(2, 2, -499600, 599600, 100, " +"-100, 0, 0, 2163), 1, '16BUI', 300, 0) AS rast\n" "), bar AS (\n" " SELECT\n" " ST_Transform(rast, 4269) AS alignto\n" @@ -8218,8 +8334,8 @@ msgstr "" #: reference_raster.xml:4810 #, no-c-format msgid "" -"Sets the value for the given band that represents no data. Band 1 is assumed" -" if no band is specified. To mark a band as having no nodata value, set the " +"Sets the value for the given band that represents no data. Band 1 is assumed " +"if no band is specified. To mark a band as having no nodata value, set the " "nodata value = NULL." msgstr "" @@ -8227,17 +8343,16 @@ msgstr "" #: reference_raster.xml:4814 #, no-c-format msgid "" -" raster " -"ST_SetBandNoDataValue raster " -" rast double " -"precision nodatavalue " -" raster " +" raster ST_SetBandNoDataValue raster rast double precision nodatavalue raster " "ST_SetBandNoDataValue raster " -" rast integer " -" band double " +" rast integer band double " "precision nodatavalue boolean " -"forcechecking=false " +"choice=\"opt\">boolean forcechecking=false " msgstr "" #. Tag: para @@ -8245,9 +8360,9 @@ msgstr "" #, no-c-format msgid "" "Sets the value that represents no data for the band. Band 1 is assumed if " -"not specified. This will affect results from , , and " -"the ST_PixelAs...() functions." +"not specified. This will affect results from , , and the ST_PixelAs...() " +"functions." msgstr "" #. Tag: programlisting @@ -8270,7 +8385,8 @@ msgid "" " 3,108) \n" " WHERE rid = 2;\n" " \n" -"-- wipe out the nodata value this will ensure all pixels are considered for all processing functions\n" +"-- wipe out the nodata value this will ensure all pixels are considered for " +"all processing functions\n" "UPDATE dummy_rast \n" " SET rast = ST_SetBandNoDataValue(rast,1, NULL) \n" "WHERE rid = 2;" @@ -8294,8 +8410,8 @@ msgstr "" msgid "" "raster ST_SetBandIsNoData " "raster rast " -"integer " -"band=1" +"integer band=1" msgstr "" #. Tag: para @@ -8304,9 +8420,8 @@ msgstr "" msgid "" "Sets the isnodata flag for the band to true. Band 1 is assumed if not " "specified. This function should be called only when the flag is considered " -"dirty. That is, when the result calling is different using TRUE as last argument " -"and without using it" +"dirty. That is, when the result calling is different using TRUE as last argument and without using it" msgstr "" #. Tag: programlisting @@ -8316,7 +8431,8 @@ msgid "" "-- Create dummy table with one raster column\n" "create table dummy_rast (rid integer, rast raster);\n" "\n" -"-- Add raster with two bands, one pixel/band. In the first band, nodatavalue = pixel value = 3.\n" +"-- Add raster with two bands, one pixel/band. In the first band, nodatavalue " +"= pixel value = 3.\n" "-- In the second band, nodatavalue = 13, pixel value = 4\n" "insert into dummy_rast values(1,\n" "(\n" @@ -8344,7 +8460,8 @@ msgid "" "||\n" "'0100' -- height (uint16 1)\n" "||\n" -"'4' -- hasnodatavalue set to true, isnodata value set to false (when it should be true)\n" +"'4' -- hasnodatavalue set to true, isnodata value set to false (when it " +"should be true)\n" "||\n" "'2' -- first band type (4BUI) \n" "||\n" @@ -8362,23 +8479,25 @@ msgid "" ")::raster\n" ");\n" "\n" -"select st_bandisnodata(rast, 1) from dummy_rast where rid = 1; -- Expected false\n" -"select st_bandisnodata(rast, 1, TRUE) from dummy_rast where rid = 1; -- Expected true\n" +"select st_bandisnodata(rast, 1) from dummy_rast where rid = 1; -- Expected " +"false\n" +"select st_bandisnodata(rast, 1, TRUE) from dummy_rast where rid = 1; -- " +"Expected true\n" "\n" "-- The isnodata flag is dirty. We are going to set it to true\n" "update dummy_rast set rast = st_setbandisnodata(rast, 1) where rid = 1;\n" "\n" "\n" -"select st_bandisnodata(rast, 1) from dummy_rast where rid = 1; -- Expected true" +"select st_bandisnodata(rast, 1) from dummy_rast where rid = 1; -- Expected " +"true" msgstr "" #. Tag: para #: reference_raster.xml:4888 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: title @@ -8397,8 +8516,8 @@ msgstr "" #: reference_raster.xml:4902 #, no-c-format msgid "" -"Returns the number of pixels in a given band of a raster or raster coverage." -" If no band is specified defaults to band 1. If exclude_nodata_value is set " +"Returns the number of pixels in a given band of a raster or raster coverage. " +"If no band is specified defaults to band 1. If exclude_nodata_value is set " "to true, will only count pixels that are not equal to the nodata value." msgstr "" @@ -8408,34 +8527,31 @@ msgstr "" msgid "" " bigint ST_Count " "raster rast " -"integer " -"nband=1 boolean " -"exclude_nodata_value=true " -" bigint ST_Count " -"raster rast " -"boolean " -"exclude_nodata_value " +"integer nband=1 boolean " +"exclude_nodata_value=true " " bigint ST_Count " -"text rastertable " -"text rastercolumn " -"integer " -"nband=1 boolean " -"exclude_nodata_value=true " -" bigint ST_Count " -"text rastertable " -"text rastercolumn " -"boolean " -"exclude_nodata_value " +"raster rast " +"boolean exclude_nodata_value bigint " +"ST_Count text " +"rastertable text " +"rastercolumn integer nband=1 boolean exclude_nodata_value=true bigint " +"ST_Count text " +"rastertable text " +"rastercolumn boolean exclude_nodata_value " msgstr "" #. Tag: para #: reference_raster.xml:4937 #, no-c-format msgid "" -"Returns the number of pixels in a given band of a raster or raster coverage." -" If no band is specified nband defaults to 1." +"Returns the number of pixels in a given band of a raster or raster coverage. " +"If no band is specified nband defaults to 1." msgstr "" #. Tag: para @@ -8474,8 +8590,8 @@ msgstr "" #: reference_raster.xml:4957 reference_raster.xml:5018 #, no-c-format msgid "" -", , " +", , " msgstr "" #. Tag: refname @@ -8488,8 +8604,8 @@ msgstr "" #: reference_raster.xml:4968 #, no-c-format msgid "" -"Aggregate. Returns the number of pixels in a given band of a set of rasters." -" If no band is specified defaults to band 1. If exclude_nodata_value is set " +"Aggregate. Returns the number of pixels in a given band of a set of rasters. " +"If no band is specified defaults to band 1. If exclude_nodata_value is set " "to true, will only count pixels that are not equal to the NODATA value." msgstr "" @@ -8500,18 +8616,16 @@ msgid "" " bigint ST_CountAgg " "raster rast " "integer nband " -"boolean " -"exclude_nodata_value " -"double precision " +"boolean exclude_nodata_value double precision " "sample_percent " " bigint ST_CountAgg " "raster rast " "integer nband " -"boolean " -"exclude_nodata_value " -" bigint ST_CountAgg " -"raster rast " -"boolean " +"boolean exclude_nodata_value bigint " +"ST_CountAgg raster " +"rast boolean " "exclude_nodata_value " msgstr "" @@ -8519,8 +8633,8 @@ msgstr "" #: reference_raster.xml:5002 #, no-c-format msgid "" -"Returns the number of pixels in a given band of a set of rasters. If no band" -" is specified nband defaults to 1." +"Returns the number of pixels in a given band of a set of rasters. If no band " +"is specified nband defaults to 1." msgstr "" #. Tag: para @@ -8553,7 +8667,8 @@ msgid "" " ST_SetValue(\n" " ST_SetValue(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(10, 10, 10, 10, 2, 2, 0, 0,0)\n" +" ST_MakeEmptyRaster(10, 10, " +"10, 10, 2, 2, 0, 0,0)\n" " , 1, '64BF', 0, 0\n" " )\n" " , 1, 1, 1, -10\n" @@ -8597,78 +8712,68 @@ msgstr "" #: reference_raster.xml:5033 #, no-c-format msgid "" -" SETOF record " -"ST_Histogram raster " -"rast integer " -"nband=1 boolean " -"exclude_nodata_value=true integer " -"bins=autocomputed double precision[] " -"width=NULL boolean " -"right=false " -" SETOF record " -"ST_Histogram raster " -"rast integer " -"nband integer " -"bins double" -" precision[] width=NULL boolean " -"right=false " -" SETOF record " -"ST_Histogram raster " -"rast integer " -"nband boolean " +" SETOF record ST_Histogram raster rast integer nband=1 boolean " +"exclude_nodata_value=true integer bins=autocomputed double precision[] " +"width=NULL boolean right=false SETOF record ST_Histogram raster rast integer nband integer bins double precision[] width=NULL boolean right=false SETOF record ST_Histogram raster rast integer nband boolean " "exclude_nodata_value " "integer bins " -"boolean right " -" SETOF record " -"ST_Histogram raster " -"rast integer " -"nband integer " -"bins boolean " +"boolean right SETOF record ST_Histogram raster rast integer nband integer bins boolean right SETOF record " +"ST_Histogram text " +"rastertable text " +"rastercolumn integer nband integer bins boolean " "right " "SETOF record ST_Histogram " "text rastertable " "text rastercolumn " "integer nband " -"integer bins " -"boolean right " -" SETOF record " +"boolean exclude_nodata_value integer bins boolean right SETOF record " "ST_Histogram text " "rastertable text " -"rastercolumn integer " -" nband boolean " -" exclude_nodata_value " -"integer bins " -"boolean right " -" SETOF record " -"ST_Histogram text " -"rastertable text " -"rastercolumn integer " -"nband=1 boolean " -"exclude_nodata_value=true integer " -"bins=autocomputed double precision[] " -"width=NULL boolean " +"rastercolumn integer nband=1 boolean exclude_nodata_value=true integer " +"bins=autocomputed double precision[] width=NULL boolean " "right=false " -" SETOF record " -"ST_Histogram text " -"rastertable text " -"rastercolumn integer " -"nband=1 integer " -"bins double" -" precision[] width=NULL boolean " -"right=false " +" SETOF record ST_Histogram text rastertable text rastercolumn integer nband=1 integer bins double precision[] width=NULL boolean right=false " msgstr "" #. Tag: para @@ -8684,9 +8789,9 @@ msgstr "" #: reference_raster.xml:5116 #, no-c-format msgid "" -"By default only considers pixel values not equal to the " -"nodata value . Set " -"exclude_nodata_value to false to get count all pixels." +"By default only considers pixel values not equal to the nodata value . Set exclude_nodata_value to false to get " +"count all pixels." msgstr "" #. Tag: term @@ -8801,7 +8906,8 @@ msgid "" " 224.666667 | 254 | 5 | 0.2\n" "(6 rows)\n" " \n" -"-- Same as previous but we explicitly control the pixel value range of each bin. \n" +"-- Same as previous but we explicitly control the pixel value range of each " +"bin. \n" "SELECT (stats).*\n" "FROM (SELECT rid, ST_Histogram(rast, 2,6,ARRAY[0.5,1,4,100,5]) As stats\n" " FROM dummy_rast \n" @@ -8822,8 +8928,8 @@ msgstr "" #: reference_raster.xml:5149 #, no-c-format msgid "" -", , " +", , " msgstr "" #. Tag: refname @@ -8845,75 +8951,66 @@ msgstr "" #: reference_raster.xml:5164 #, no-c-format msgid "" -" SETOF record " +" SETOF record ST_Quantile raster rast integer nband=1 boolean " +"exclude_nodata_value=true double precision[] quantiles=NULL SETOF record " "ST_Quantile raster " -"rast integer " -"nband=1 boolean " -"exclude_nodata_value=true double precision[] " -"quantiles=NULL " -" SETOF record " -"ST_Quantile raster " -"rast double precision[] " -" quantiles " -" SETOF record " -"ST_Quantile raster " -"rast integer " -"nband double precision[] " -" quantiles " -" double precision " -"ST_Quantile raster " -"rast double precision " -" quantile " -" double precision " +"rast double precision[] quantiles " +" SETOF record ST_Quantile raster rast integer nband double precision[] quantiles double " +"precision ST_Quantile raster " +" rast double " +"precision quantile double precision " "ST_Quantile raster " "rast boolean " -"exclude_nodata_value double precision " -"quantile=NULL " -" double precision " +"exclude_nodata_value double precision quantile=NULL double precision " "ST_Quantile raster " "rast integer " -"nband double precision " -" quantile " -" double precision " -"ST_Quantile raster " -"rast integer " -"nband boolean " -"exclude_nodata_value " -"double precision " +"nband double precision quantile " +" double precision ST_Quantile raster rast integer nband boolean exclude_nodata_value double precision " "quantile " "double precision ST_Quantile " "raster rast " "integer nband " -"double precision " -"quantile " -"SETOF record ST_Quantile " -"text rastertable " -"text rastercolumn " -"integer " -"nband=1 boolean " -"exclude_nodata_value=true double precision[] " -"quantiles=NULL " -" SETOF record " +"double precision quantile SETOF record " "ST_Quantile text " "rastertable text " -"rastercolumn integer " -" nband double " -"precision[] quantiles " -"" +"rastercolumn integer nband=1 boolean exclude_nodata_value=true double precision[] quantiles=NULL " +" SETOF record ST_Quantile text rastertable text rastercolumn integer nband double precision[] quantiles " msgstr "" #. Tag: para #: reference_raster.xml:5236 #, no-c-format msgid "" -"Compute quantiles for a raster or raster table coverage in the context" -" of the sample or population. Thus, a value could be examined to be at the " +"Compute quantiles for a raster or raster table coverage in the context " +"of the sample or population. Thus, a value could be examined to be at the " "raster's 25%, 50%, 75% percentile." msgstr "" @@ -8930,7 +9027,8 @@ msgstr "" #, no-c-format msgid "" "UPDATE dummy_rast SET rast = ST_SetBandNoDataValue(rast,249) WHERE rid=2;\n" -"--Example will consider only pixels of band 1 that are not 249 and in named quantiles --\n" +"--Example will consider only pixels of band 1 that are not 249 and in named " +"quantiles --\n" "\n" "SELECT (pvq).*\n" "FROM (SELECT ST_Quantile(rast, ARRAY[0.25,0.75]) As pvq\n" @@ -8954,11 +9052,13 @@ msgstr "" #: reference_raster.xml:5245 #, no-c-format msgid "" -"--real live example. Quantile of all pixels in band 2 intersecting a geometry\n" +"--real live example. Quantile of all pixels in band 2 intersecting a " +"geometry\n" "SELECT rid, (ST_Quantile(rast,2)).* As pvc\n" " FROM o_4_boston \n" " WHERE ST_Intersects(rast, \n" -" ST_GeomFromText('POLYGON((224486 892151,224486 892200,224706 892200,224706 892151,224486 892151))',26986)\n" +" ST_GeomFromText('POLYGON((224486 892151,224486 892200,224706 " +"892200,224706 892151,224486 892151))',26986)\n" " )\n" "ORDER BY value, quantile,rid\n" ";\n" @@ -8992,9 +9092,8 @@ msgstr "" #: reference_raster.xml:5250 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -9016,28 +9115,25 @@ msgstr "" #: reference_raster.xml:5266 #, no-c-format msgid "" -" summarystats " -"ST_SummaryStats raster " -" rast boolean " -" exclude_nodata_value " -" summarystats " -"ST_SummaryStats raster " -" rast integer " -" nband boolean " -" exclude_nodata_value " -" summarystats " -"ST_SummaryStats text " -"rastertable text " -"rastercolumn boolean " -" exclude_nodata_value " -" summarystats " +" summarystats ST_SummaryStats raster rast boolean exclude_nodata_value summarystats " +"ST_SummaryStats raster rast integer " +"nband boolean " +"exclude_nodata_value " +" summarystats ST_SummaryStats text rastertable text rastercolumn boolean exclude_nodata_value summarystats " "ST_SummaryStats text " "rastertable text " -"rastercolumn integer " -"nband=1 boolean " -"exclude_nodata_value=true " +"rastercolumn integer nband=1 boolean exclude_nodata_value=true " msgstr "" #. Tag: para @@ -9053,9 +9149,9 @@ msgstr "" #: reference_raster.xml:5304 #, no-c-format msgid "" -"By default only considers pixel values not equal to the " -"nodata value. Set exclude_nodata_value" -" to false to get count of all pixels." +"By default only considers pixel values not equal to the nodata value. Set exclude_nodata_value to false to get " +"count of all pixels." msgstr "" #. Tag: para @@ -9117,7 +9213,8 @@ msgstr "" msgid "" "WITH \n" "-- our features of interest\n" -" feat AS (SELECT gid As building_id, geom_26986 As geom FROM buildings AS b \n" +" feat AS (SELECT gid As building_id, geom_26986 As geom FROM buildings AS " +"b \n" " WHERE gid IN(100, 103,150)\n" " ),\n" "-- clip band 2 of raster tiles to boundaries of builds\n" @@ -9170,7 +9267,8 @@ msgid "" "-- For a table -- will get better speed if set sampling to less than 100%\n" "-- Here we set to 25% and get a much faster answer\n" "SELECT band, (stats).*\n" -"FROM (SELECT band, ST_SummaryStats('o_4_boston','rast', band,true,0.25) As stats\n" +"FROM (SELECT band, ST_SummaryStats('o_4_boston','rast', band,true,0.25) As " +"stats\n" " FROM generate_series(1,3) As band) As foo;\n" " \n" " band | count | sum | mean | stddev | min | max\n" @@ -9184,8 +9282,8 @@ msgstr "" #: reference_raster.xml:5337 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -9198,43 +9296,40 @@ msgstr "" #: reference_raster.xml:5349 #, no-c-format msgid "" -"Aggregate. Returns summarystats consisting of count, sum, mean, stddev, min," -" max for a given raster band of a set of raster. Band 1 is assumed is no " -"band is specified." +"Aggregate. Returns summarystats consisting of count, sum, mean, stddev, min, " +"max for a given raster band of a set of raster. Band 1 is assumed is no band " +"is specified." msgstr "" #. Tag: funcsynopsis #: reference_raster.xml:5353 #, no-c-format msgid "" -" summarystats " -"ST_SummaryStatsAgg raster " -" rast integer " -" nband boolean " -" exclude_nodata_value " -"double precision " -"sample_percent " -" summarystats " -"ST_SummaryStatsAgg raster " -" rast boolean " -" exclude_nodata_value " -"double precision " -"sample_percent " -" summarystats " -"ST_SummaryStatsAgg raster " -" rast integer " -" nband boolean " -" exclude_nodata_value " -"" +" summarystats ST_SummaryStatsAgg raster rast integer nband boolean " +"exclude_nodata_value " +"double precision sample_percent summarystats " +"ST_SummaryStatsAgg raster rast boolean " +"exclude_nodata_value " +"double precision sample_percent summarystats " +"ST_SummaryStatsAgg raster rast integer " +"nband boolean " +"exclude_nodata_value " msgstr "" #. Tag: para #: reference_raster.xml:5383 #, no-c-format msgid "" -"By default only considers pixel values not equal to the " -"NODATA value. Set exclude_nodata_value" -" to False to get count of all pixels." +"By default only considers pixel values not equal to the NODATA value. Set exclude_nodata_value to False to get " +"count of all pixels." msgstr "" #. Tag: para @@ -9257,7 +9352,8 @@ msgid "" " ST_SetValue(\n" " ST_SetValue(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(10, 10, 10, 10, 2, 2, 0, 0,0)\n" +" ST_MakeEmptyRaster(10, 10, " +"10, 10, 2, 2, 0, 0,0)\n" " , 1, '64BF', 0, 0\n" " )\n" " , 1, 1, 1, -10\n" @@ -9320,114 +9416,100 @@ msgstr "" #: reference_raster.xml:5414 #, no-c-format msgid "" -" SETOF record " -"ST_ValueCount raster " -"rast integer " -"nband=1 boolean " -"exclude_nodata_value=true double precision[] " -"searchvalues=NULL double precision " -"roundto=0 double precision" -" OUT value integer" -" OUT count " -" SETOF record " +" SETOF record ST_ValueCount raster rast integer nband=1 boolean " +"exclude_nodata_value=true double precision[] searchvalues=NULL double precision roundto=0 double " +"precision OUT value " +"integer OUT count " +" SETOF record " "ST_ValueCount raster " "rast integer " -"nband double precision[] " -" searchvalues double precision " -"roundto=0 double precision" -" OUT value integer" -" OUT count " -" SETOF record " +"nband double precision[] searchvalues double precision roundto=0 double precision OUT value integer OUT count SETOF record " "ST_ValueCount raster " -"rast double precision[] " -" searchvalues double precision " -"roundto=0 double precision" -" OUT value integer" -" OUT count " -" bigint ST_ValueCount" -" raster rast " -"double precision " -"searchvalue double precision " -"roundto=0 " -" bigint ST_ValueCount " -"raster rast " -"integer nband " -"boolean " +"rast double precision[] searchvalues double precision roundto=0 double precision OUT value integer OUT count bigint " +"ST_ValueCount raster " +"rast double precision searchvalue double precision roundto=0 bigint " +"ST_ValueCount raster " +"rast integer " +"nband boolean " "exclude_nodata_value " -"double precision " -"searchvalue double precision " -"roundto=0 " -" bigint ST_ValueCount " +"double precision searchvalue double precision " +"roundto=0 " +"bigint ST_ValueCount " "raster rast " "integer nband " -"double precision " -"searchvalue double precision " -"roundto=0 " -" SETOF record ST_ValueCount " +"double precision searchvalue double precision " +"roundto=0 " +"SETOF record ST_ValueCount " "text rastertable " "text rastercolumn " -"integer " -"nband=1 boolean " -"exclude_nodata_value=true double precision[] " -"searchvalues=NULL double precision " -"roundto=0 double precision" -" OUT value integer" -" OUT count " -" SETOF record " +"integer nband=1 boolean " +"exclude_nodata_value=true double precision[] searchvalues=NULL double precision roundto=0 double " +"precision OUT value " +"integer OUT count " +" SETOF record " "ST_ValueCount text " "rastertable text " "rastercolumn double " -"precision[] searchvalues double precision " -"roundto=0 double precision" -" OUT value integer" -" OUT count " -" SETOF record " -"ST_ValueCount text " -"rastertable text " -"rastercolumn integer " -" nband double " -"precision[] searchvalues double precision " -"roundto=0 double precision" -" OUT value integer" -" OUT count " -" bigintST_ValueCount " +"precision[] searchvalues double precision roundto=0 double precision " +"OUT value integer " +"OUT count " +"SETOF record ST_ValueCount " "text rastertable " "text rastercolumn " "integer nband " -"boolean " +"double precision[] searchvalues double precision roundto=0 double " +"precision OUT value " +"integer OUT count " +" bigintST_ValueCount text rastertable text rastercolumn integer nband boolean " "exclude_nodata_value " -"double precision " -"searchvalue double precision " -"roundto=0 " -" bigint ST_ValueCount " +"double precision searchvalue double precision " +"roundto=0 " +"bigint ST_ValueCount " "text rastertable " "text rastercolumn " -"double precision " -"searchvalue double precision " -"roundto=0 " -" bigint ST_ValueCount " +"double precision searchvalue double precision " +"roundto=0 " +"bigint ST_ValueCount " "text rastertable " "text rastercolumn " "integer nband " -"double precision " -"searchvalue double precision " +"double precision searchvalue double precision " "roundto=0 " msgstr "" @@ -9509,13 +9591,15 @@ msgstr "" #: reference_raster.xml:5537 #, no-c-format msgid "" -"--real live example. Count all the pixels in an aerial raster tile band 2 intersecting a geometry \n" +"--real live example. Count all the pixels in an aerial raster tile band 2 " +"intersecting a geometry \n" "-- and return only the pixel band values that have a count > 500\n" "SELECT (pvc).value, SUM((pvc).count) As total\n" "FROM (SELECT ST_ValueCount(rast,2) As pvc\n" " FROM o_4_boston \n" " WHERE ST_Intersects(rast, \n" -" ST_GeomFromText('POLYGON((224486 892151,224486 892200,224706 892200,224706 892151,224486 892151))',26986)\n" +" ST_GeomFromText('POLYGON((224486 892151,224486 892200,224706 " +"892200,224706 892151,224486 892151))',26986)\n" " ) \n" " ) As foo\n" " GROUP BY (pvc).value\n" @@ -9532,11 +9616,13 @@ msgstr "" #: reference_raster.xml:5539 #, no-c-format msgid "" -"-- Just return count of pixels in each raster tile that have value of 100 of tiles that intersect a specific geometry --\n" +"-- Just return count of pixels in each raster tile that have value of 100 of " +"tiles that intersect a specific geometry --\n" "SELECT rid, ST_ValueCount(rast,2,100) As count\n" " FROM o_4_boston \n" " WHERE ST_Intersects(rast, \n" -" ST_GeomFromText('POLYGON((224486 892151,224486 892200,224706 892200,224706 892151,224486 892151))',26986)\n" +" ST_GeomFromText('POLYGON((224486 892151,224486 892200,224706 " +"892200,224706 892151,224486 892151))',26986)\n" " ) ;\n" "\n" " rid | count\n" @@ -9569,8 +9655,8 @@ msgstr "" #: reference_raster.xml:5554 #, no-c-format msgid "" -"Return the Well-Known Binary (WKB) representation of the raster without SRID" -" meta data." +"Return the Well-Known Binary (WKB) representation of the raster without SRID " +"meta data." msgstr "" #. Tag: funcprototype @@ -9579,16 +9665,16 @@ msgstr "" msgid "" "bytea ST_AsBinary " "raster rast " -"boolean " -"outasin=FALSE" +"boolean outasin=FALSE" msgstr "" #. Tag: para #: reference_raster.xml:5570 #, no-c-format msgid "" -"Returns the Binary representation of the raster. If " -"outasin is TRUE, out-db bands are treated as in-db." +"Returns the Binary representation of the raster. If outasin is TRUE, out-db bands are treated as in-db." msgstr "" #. Tag: para @@ -9622,8 +9708,10 @@ msgid "" "\n" " rastbin\n" "---------------------------------------------------------------------------------\n" -"\\001\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000@\\000\\000\\000\\000\\000\\000\\010@\\\n" -"000\\000\\000\\000\\000\\000\\340?\\000\\000\\000\\000\\000\\000\\340?\\000\\000\\000\\000\\000\\00\n" +"\\001\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000@" +"\\000\\000\\000\\000\\000\\000\\010@\\\n" +"000\\000\\000\\000\\000\\000\\340?\\000\\000\\000\\000\\000\\000\\340?" +"\\000\\000\\000\\000\\000\\00\n" "0\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\012\\000\\000\\000\\012\\000\\024\\000" msgstr "" @@ -9638,8 +9726,8 @@ msgstr "" #, no-c-format msgid "" "Return the raster tile in the designated GDAL Raster format. Raster formats " -"are one of those supported by your compiled library. Use ST_GDALRasters() to" -" get a list of formats supported by your library." +"are one of those supported by your compiled library. Use ST_GDALRasters() to " +"get a list of formats supported by your library." msgstr "" #. Tag: funcprototype @@ -9649,9 +9737,8 @@ msgid "" "bytea ST_AsGDALRaster " "raster rast " "text format " -"text[] " -"options=NULL integer " +"text[] options=NULL integer " "srid=sameassource" msgstr "" @@ -9667,8 +9754,8 @@ msgstr "" #: reference_raster.xml:5619 #, no-c-format msgid "" -"format format to output. This is dependent on the drivers" -" compiled in your libgdal library. Generally available are 'JPEG', 'GTIff', " +"format format to output. This is dependent on the drivers " +"compiled in your libgdal library. Generally available are 'JPEG', 'GTIff', " "'PNG'. Use to get a list of formats " "supported by your library." msgstr "" @@ -9678,9 +9765,8 @@ msgstr "" #, no-c-format msgid "" "options text array of GDAL options. Valid options are " -"dependent on the format. Refer to GDAL Raster format " -"options for more details." +"dependent on the format. Refer to GDAL Raster format options for more details." msgstr "" #. Tag: para @@ -9744,10 +9830,10 @@ msgstr "" #: reference_raster.xml:5661 #, no-c-format msgid "" -"Return the raster tile selected bands as a single Joint Photographic Exports" -" Group (JPEG) image (byte array). If no band is specified and 1 or more than" -" 3 bands, then only the first band is used. If only 3 bands then all 3 bands" -" are used and mapped to RGB." +"Return the raster tile selected bands as a single Joint Photographic Exports " +"Group (JPEG) image (byte array). If no band is specified and 1 or more than " +"3 bands, then only the first band is used. If only 3 bands then all 3 bands " +"are used and mapped to RGB." msgstr "" #. Tag: funcsynopsis @@ -9756,28 +9842,26 @@ msgstr "" msgid "" " bytea ST_AsJPEG " "raster rast " -"text[] " -"options=NULL " -" bytea ST_AsJPEG " -"raster rast " -"integer nband " -"integer quality " -" bytea " +"text[] options=NULL bytea " "ST_AsJPEG raster " "rast integer " -"nband text[] " -"options=NULL " -" bytea ST_AsJPEG " -"raster rast " -"integer[] nbands " -"text[] " -"options=NULL " -" bytea ST_AsJPEG " +"nband integer " +"quality " +"bytea ST_AsJPEG " "raster rast " -"integer[] nbands " -"integer quality " -"" +"integer nband " +"text[] options=NULL bytea " +"ST_AsJPEG raster " +"rast integer[] " +"nbands text[] options=NULL bytea ST_AsJPEG raster rast integer[] nbands integer quality " msgstr "" #. Tag: para @@ -9802,9 +9886,9 @@ msgstr "" #: reference_raster.xml:5709 #, no-c-format msgid "" -"nbands is an array of bands to export (note that max is 3" -" for JPEG) and the order of the bands is RGB. e.g ARRAY[3,2,1] means map " -"band 3 to Red, band 2 to green and band 1 to blue" +"nbands is an array of bands to export (note that max is 3 " +"for JPEG) and the order of the bands is RGB. e.g ARRAY[3,2,1] means map band " +"3 to Red, band 2 to green and band 1 to blue" msgstr "" #. Tag: para @@ -9820,10 +9904,10 @@ msgstr "" #, no-c-format msgid "" "options text Array of GDAL options as defined for JPEG " -"(look at create_options for JPEG ). For" -" JPEG valid ones are PROGRESSIVE ON or OFF and " -"QUALITY a range from 0 to 100 and default to 75. Refer to" -" GDAL Raster format " +"(look at create_options for JPEG ). For " +"JPEG valid ones are PROGRESSIVE ON or OFF and " +"QUALITY a range from 0 to 100 and default to 75. Refer to " +"GDAL Raster format " "options for more details." msgstr "" @@ -9845,8 +9929,10 @@ msgid "" "SELECT ST_AsJPEG(rast,1,90) As rastjpg\n" " FROM dummy_rast WHERE rid=2;\n" " \n" -"-- output first 3 bands (but make band 2 Red, band 1 green, and band 3 blue, progressive and 90% quality\n" -"SELECT ST_AsJPEG(rast,ARRAY[2,1,3],ARRAY['QUALITY=90','PROGRESSIVE=ON']) As rastjpg\n" +"-- output first 3 bands (but make band 2 Red, band 1 green, and band 3 blue, " +"progressive and 90% quality\n" +"SELECT ST_AsJPEG(rast,ARRAY[2,1,3],ARRAY['QUALITY=90','PROGRESSIVE=ON']) As " +"rastjpg\n" " FROM dummy_rast WHERE rid=2;" msgstr "" @@ -9854,9 +9940,8 @@ msgstr "" #: reference_raster.xml:5745 #, no-c-format msgid "" -", , , , " +", , , , " msgstr "" #. Tag: refname @@ -9882,28 +9967,26 @@ msgstr "" msgid "" " bytea ST_AsPNG " "raster rast " -"text[] " -"options=NULL " -" bytea ST_AsPNG " -"raster rast " -"integer nband " -"integer " +"text[] options=NULL bytea " +"ST_AsPNG raster " +"rast integer " +"nband integer " "compression " " bytea ST_AsPNG " "raster rast " "integer nband " -"text[] " -"options=NULL " -" bytea ST_AsPNG " -"raster rast " -"integer[] nbands " -"integer " +"text[] options=NULL bytea " +"ST_AsPNG raster " +"rast integer[] " +"nbands integer " "compression " " bytea ST_AsPNG " "raster rast " "integer[] nbands " -"text[] " -"options=NULL " +"text[] options=NULL " msgstr "" #. Tag: para @@ -9911,8 +9994,8 @@ msgstr "" #, no-c-format msgid "" "Returns the selected bands of the raster as a single Portable Network " -"Graphics Image (PNG). Use if you need" -" to export as less common raster types. If no band is specified, then the " +"Graphics Image (PNG). Use if you need " +"to export as less common raster types. If no band is specified, then the " "first 3 bands are exported. There are many variants of the function with " "many options. If no srid is specified then then srid of " "the raster is used. These are itemized below:" @@ -9922,17 +10005,17 @@ msgstr "" #: reference_raster.xml:5800 reference_raster.xml:5883 #, no-c-format msgid "" -"nbands is an array of bands to export (note that max is 3" -" for PNG) and the order of the bands is RGB. e.g ARRAY[3,2,1] means map band" -" 3 to Red, band 2 to green and band 1 to blue" +"nbands is an array of bands to export (note that max is 3 " +"for PNG) and the order of the bands is RGB. e.g ARRAY[3,2,1] means map band " +"3 to Red, band 2 to green and band 1 to blue" msgstr "" #. Tag: para #: reference_raster.xml:5805 #, no-c-format msgid "" -"compression number from 1 to 9. The higher the number the" -" greater the compression." +"compression number from 1 to 9. The higher the number the " +"greater the compression." msgstr "" #. Tag: para @@ -9943,9 +10026,9 @@ msgid "" "(look at create_options for PNG of ). " "For PNG valid one is only ZLEVEL (amount of time to spend on compression -- " "default 6) e.g. ARRAY['ZLEVEL=9']. WORLDFILE is not allowed since the " -"function would have to output two outputs. Refer to GDAL Raster format " -"options for more details." +"function would have to output two outputs. Refer to GDAL Raster format options for more " +"details." msgstr "" #. Tag: programlisting @@ -9955,7 +10038,8 @@ msgid "" "SELECT ST_AsPNG(rast) As rastpng\n" "FROM dummy_rast WHERE rid=2;\n" "\n" -"-- export the first 3 bands and map band 3 to Red, band 1 to Green, band 2 to blue\n" +"-- export the first 3 bands and map band 3 to Red, band 1 to Green, band 2 " +"to blue\n" "SELECT ST_AsPNG(rast, ARRAY[3,1,2]) As rastpng\n" "FROM dummy_rast WHERE rid=2;" msgstr "" @@ -9964,8 +10048,8 @@ msgstr "" #: reference_raster.xml:5836 #, no-c-format msgid "" -", , ," -" " +", , , " +"" msgstr "" #. Tag: refname @@ -9988,28 +10072,26 @@ msgstr "" msgid "" " bytea ST_AsTIFF " "raster rast " -"text[] " -"options='' integer " -" srid=sameassource " +"text[] options='' integer " +"srid=sameassource " " bytea ST_AsTIFF " "raster rast " -"text " -"compression='' integer " +"text compression='' integer " "srid=sameassource " " bytea ST_AsTIFF " "raster rast " "integer[] nbands " -"text " -"compression='' integer " +"text compression='' integer " "srid=sameassource " " bytea ST_AsTIFF " "raster rast " "integer[] nbands " "text[] options " -"integer " -"srid=sameassource " +"integer srid=sameassource " msgstr "" #. Tag: para @@ -10017,12 +10099,12 @@ msgstr "" #, no-c-format msgid "" "Returns the selected bands of the raster as a single Tagged Image File " -"Format (TIFF). If no band is specified, will try to use all bands. This is a" -" wrapper around . Use if you need to export as less common raster" -" types. There are many variants of the function with many options. If no " -"spatial reference SRS text is present, the spatial reference of the raster " -"is used. These are itemized below:" +"Format (TIFF). If no band is specified, will try to use all bands. This is a " +"wrapper around . Use if you need to export as less common raster types. " +"There are many variants of the function with many options. If no spatial " +"reference SRS text is present, the spatial reference of the raster is used. " +"These are itemized below:" msgstr "" #. Tag: para @@ -10038,10 +10120,9 @@ msgstr "" #, no-c-format msgid "" "options text Array of GDAL create options as defined for " -"GTiff (look at create_options for GTiff of ). or refer to GDAL Raster format " -"options for more details." +"GTiff (look at create_options for GTiff of ). or refer to GDAL " +"Raster format options for more details." msgstr "" #. Tag: para @@ -10069,7 +10150,8 @@ msgstr "" #. Tag: para #: reference_raster.xml:5916 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: title @@ -10108,50 +10190,45 @@ msgid "" "integer[] nband " "geometry geom " "double precision[] " -"nodataval=NULL boolean " -"crop=TRUE " -" raster ST_Clip " -"raster rast " -"integer nband " -"geometry geom " -"double precision " -"nodataval boolean " -"crop=TRUE " -" raster ST_Clip " +"nodataval=NULL boolean crop=TRUE raster ST_Clip raster rast integer nband geometry geom double precision nodataval boolean " +"crop=TRUE " +"raster ST_Clip " "raster rast " "integer nband " "geometry geom " -"boolean crop " -" raster " -"ST_Clip raster " -"rast geometry " -"geom double" -" precision[] nodataval=NULL " -"boolean " -"crop=TRUE " -" raster ST_Clip " -"raster rast " -"geometry geom " -"double precision " -"nodataval boolean " -"crop=TRUE " -" raster ST_Clip " +"boolean crop raster ST_Clip raster rast geometry geom double precision[] " +"nodataval=NULL boolean crop=TRUE raster ST_Clip raster rast geometry geom double precision nodataval boolean " +"crop=TRUE " +"raster ST_Clip " "raster rast " "geometry geom " -"boolean crop " -"" +"boolean crop " msgstr "" #. Tag: para #: reference_raster.xml:5991 #, no-c-format msgid "" -"Returns a raster that is clipped by the input geometry " -"geom. If band index is not specified, all bands are " -"processed." +"Returns a raster that is clipped by the input geometry geom. If band index is not specified, all bands are processed." msgstr "" #. Tag: para @@ -10159,13 +10236,13 @@ msgstr "" #, no-c-format msgid "" "Rasters resulting from ST_Clip must have a nodata value assigned for areas " -"clipped, one for each band. If none are provided and the input raster do not" -" have a nodata value defined, nodata values of the resulting raster are set " +"clipped, one for each band. If none are provided and the input raster do not " +"have a nodata value defined, nodata values of the resulting raster are set " "to ST_MinPossibleValue(ST_BandPixelType(rast, band)). When the number of " "nodata value in the array is smaller than the number of band, the last one " "in the array is used for the remaining bands. If the number of nodata value " -"is greater than the number of band, the extra nodata values are ignored. All" -" variants accepting an array of nodata values also accept a single value " +"is greater than the number of band, the extra nodata values are ignored. All " +"variants accepting an array of nodata values also accept a single value " "which will be assigned to each band." msgstr "" @@ -10174,10 +10251,9 @@ msgstr "" #, no-c-format msgid "" "If crop is not specified, true is assumed meaning the " -"output raster is cropped to the intersection of the " -"geomand rast extents. If " -"crop is set to false, the new raster gets the same extent" -" as rast." +"output raster is cropped to the intersection of the geomand rast extents. If crop is " +"set to false, the new raster gets the same extent as rast." msgstr "" #. Tag: para @@ -10190,9 +10266,9 @@ msgstr "" #: reference_raster.xml:6007 #, no-c-format msgid "" -"Examples here use Massachusetts aerial data available on MassGIS site MassGIS Aerial " -"Orthos. Coordinates are in Massachusetts State Plane Meters." +"Examples here use Massachusetts aerial data available on MassGIS site MassGIS Aerial Orthos. Coordinates are in Massachusetts State Plane Meters." msgstr "" #. Tag: title @@ -10219,9 +10295,11 @@ msgid "" "-- Demonstrate effect of crop on final dimensions of raster\n" "-- Note how final extent is clipped to that of the geometry\n" "-- if crop = true\n" -"SELECT ST_XMax(ST_Envelope(ST_Clip(rast, 1, clipper, true))) As xmax_w_trim,\n" +"SELECT ST_XMax(ST_Envelope(ST_Clip(rast, 1, clipper, true))) As " +"xmax_w_trim,\n" " ST_XMax(clipper) As xmax_clipper,\n" -" ST_XMax(ST_Envelope(ST_Clip(rast, 1, clipper, false))) As xmax_wo_trim,\n" +" ST_XMax(ST_Envelope(ST_Clip(rast, 1, clipper, false))) As " +"xmax_wo_trim,\n" " ST_XMax(ST_Envelope(rast)) As xmax_rast_orig\n" "FROM (SELECT rast, ST_Buffer(ST_Centroid(ST_Envelope(rast)),6) As clipper\n" " FROM aerials.boston\n" @@ -10256,7 +10334,8 @@ msgstr "" #: reference_raster.xml:6060 #, no-c-format msgid "" -"-- Same example as before, but we need to set crop to false to be able to use ST_AddBand\n" +"-- Same example as before, but we need to set crop to false to be able to " +"use ST_AddBand\n" "-- because ST_AddBand requires all bands be the same Width and height\n" "SELECT ST_AddBand(ST_Clip(rast, 1,\n" " ST_Buffer(ST_Centroid(ST_Envelope(rast)),20),false\n" @@ -10293,7 +10372,9 @@ msgstr "" #. Tag: para #: reference_raster.xml:6146 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -10316,12 +10397,10 @@ msgstr "" msgid "" "raster ST_ColorMap " "raster rast " -"integer " -"nband=1 text " -"colormap=grayscale text " -"method=INTERPOLATE" +"integer nband=1 text " +"colormap=grayscale text method=INTERPOLATE" msgstr "" #. Tag: funcprototype @@ -10331,8 +10410,8 @@ msgid "" "raster ST_ColorMap " "raster rast " "text colormap " -"text " -"method=INTERPOLATE" +"text method=INTERPOLATE" msgstr "" #. Tag: para @@ -10385,8 +10464,8 @@ msgstr "" #: reference_raster.xml:6210 #, no-c-format msgid "" -"fire for a four 8BUI (RGBA) band raster with colors going" -" from black to red to pale yellow." +"fire for a four 8BUI (RGBA) band raster with colors going " +"from black to red to pale yellow." msgstr "" #. Tag: para @@ -10401,16 +10480,15 @@ msgstr "" #: reference_raster.xml:6221 #, no-c-format msgid "" -"Users can pass a set of entries (one per line) to " -"colormap to specify custom colormaps. Each entry " -"generally consists of five values: the pixel value and corresponding Red, " -"Green, Blue, Alpha components (color components between 0 and 255). Percent " -"values can be used instead of pixel values where 0% and 100% are the minimum" -" and maximum values found in the raster band. Values can be separated with " -"commas (','), tabs, colons (':') and/or spaces. The pixel value can be set " -"to nv, null or " -"nodata for the NODATA value. An example is provided " -"below." +"Users can pass a set of entries (one per line) to colormap to specify custom colormaps. Each entry generally consists of five " +"values: the pixel value and corresponding Red, Green, Blue, Alpha components " +"(color components between 0 and 255). Percent values can be used instead of " +"pixel values where 0% and 100% are the minimum and maximum values found in " +"the raster band. Values can be separated with commas (','), tabs, colons " +"(':') and/or spaces. The pixel value can be set to nv, " +"null or nodata for the NODATA " +"value. An example is provided below." msgstr "" #. Tag: programlisting @@ -10429,8 +10507,8 @@ msgstr "" #, no-c-format msgid "" "The syntax of colormap is similar to that of the color-" -"relief mode of GDAL gdaldem." +"relief mode of GDAL gdaldem." msgstr "" #. Tag: para @@ -10443,17 +10521,17 @@ msgstr "" #: reference_raster.xml:6237 #, no-c-format msgid "" -"INTERPOLATE to use linear interpolation to smoothly blend" -" the colors between the given pixel values" +"INTERPOLATE to use linear interpolation to smoothly blend " +"the colors between the given pixel values" msgstr "" #. Tag: para #: reference_raster.xml:6242 #, no-c-format msgid "" -"EXACT to strictly match only those pixels values found in" -" the colormap. Pixels whose value does not match a colormap entry will be " -"set to 0 0 0 0 (RGBA)" +"EXACT to strictly match only those pixels values found in " +"the colormap. Pixels whose value does not match a colormap entry will be set " +"to 0 0 0 0 (RGBA)" msgstr "" #. Tag: para @@ -10468,8 +10546,8 @@ msgstr "" #: reference_raster.xml:6254 #, no-c-format msgid "" -"A great reference for colormaps is ColorBrewer." +"A great reference for colormaps is ColorBrewer." msgstr "" #. Tag: para @@ -10506,7 +10584,8 @@ msgid "" " ST_AsRaster(\n" " ST_Rotate(\n" " ST_Buffer(\n" -" ST_GeomFromText('LINESTRING(0 2,50 50,150 150,125 50)'),\n" +" ST_GeomFromText('LINESTRING(0 2,50 " +"50,150 150,125 50)'),\n" " i*2\n" " ),\n" " pi() * i * 0.125, ST_Point(50,50)\n" @@ -10618,8 +10697,8 @@ msgstr "" #, no-c-format msgid "" ", , " -", , , " +", , , " msgstr "" #. Tag: refname @@ -10641,51 +10720,45 @@ msgstr "" #: reference_raster.xml:6399 #, no-c-format msgid "" -" setof geomval " -"ST_Intersection geometry " -" geom raster " -" rast integer " +" setof geomval ST_Intersection geometry geom raster rast integer " "band_num=1 " -" setof geomval " -"ST_Intersection raster " -" rast geometry " -" geom " -" setof geomval " -"ST_Intersection raster " -" rast integer " -" band_num geometry " -" geom " -" raster " -"ST_Intersection raster " -" rast1 raster " -" rast2 double " -"precision[] nodataval " -" raster " -"ST_Intersection raster " -" rast1 raster " -" rast2 text " -"returnband='BOTH' double precision[] " -"nodataval=NULL " -" raster " -"ST_Intersection raster " -" rast1 integer " -" band_num1 raster " -" rast2 integer " -" band_num2 double " -"precision[] nodataval " -" raster " -"ST_Intersection raster " -" rast1 integer " -" band_num1 raster " -" rast2 integer " -" band_num2 text " -"returnband='BOTH' double precision[] " -"nodataval=NULL " +" setof geomval ST_Intersection raster rast geometry geom setof geomval " +"ST_Intersection raster rast integer " +"band_num geometry " +"geom " +"raster ST_Intersection " +"raster rast1 " +"raster rast2 " +"double precision[] nodataval raster " +"ST_Intersection raster rast1 raster " +"rast2 text " +" returnband='BOTH' double precision[] nodataval=NULL raster " +"ST_Intersection raster rast1 integer band_num1 raster rast2 integer band_num2 double " +"precision[] nodataval raster ST_Intersection raster rast1 integer band_num1 raster rast2 integer band_num2 text " +"returnband='BOTH' double precision[] nodataval=NULL " msgstr "" #. Tag: para @@ -10703,11 +10776,11 @@ msgstr "" msgid "" "The first three variants, returning a setof geomval, works in vector space. " "The raster is first vectorized (using ST_DumpAsPolygon) into a set of " -"geomval rows and those rows are then intersected with the geometry using the" -" ST_Intersection(geometry, geometry) PostGIS function. Geometries " +"geomval rows and those rows are then intersected with the geometry using the " +"ST_Intersection(geometry, geometry) PostGIS function. Geometries " "intersecting only with a nodata value area of a raster returns an empty " -"geometry. They are normally excluded from the results by the proper usage of" -" ST_Intersect in the WHERE clause." +"geometry. They are normally excluded from the results by the proper usage of " +"ST_Intersect in the WHERE clause." msgstr "" #. Tag: para @@ -10715,8 +10788,8 @@ msgstr "" #, no-c-format msgid "" "You can access the geometry and the value parts of the resulting set of " -"geomval by surrounding them with parenthesis and adding '.geom' or '.val' at" -" the end of the expression. e.g. (ST_Intersection(rast, geom)).geom" +"geomval by surrounding them with parenthesis and adding '.geom' or '.val' at " +"the end of the expression. e.g. (ST_Intersection(rast, geom)).geom" msgstr "" #. Tag: para @@ -10745,16 +10818,16 @@ msgstr "" #: reference_raster.xml:6479 #, no-c-format msgid "" -"Rasters resulting from ST_Intersection must have a nodata value assigned for" -" areas not intersecting. You can define or replace the nodata value for any " -"resulting band by providing a nodataval[] array of one or" -" two nodata values depending if you request 'BAND1', 'BAND2' or 'BOTH' " -"bands. The first value in the array replace the nodata value in the first " -"band and the second value replace the nodata value in the second band. If " -"one input band do not have a nodata value defined and none are provided as " -"an array, one is chosen using the ST_MinPossibleValue function. All variant " -"accepting an array of nodata value can also accept a single value which will" -" be assigned to each requested band." +"Rasters resulting from ST_Intersection must have a nodata value assigned for " +"areas not intersecting. You can define or replace the nodata value for any " +"resulting band by providing a nodataval[] array of one or " +"two nodata values depending if you request 'BAND1', 'BAND2' or 'BOTH' bands. " +"The first value in the array replace the nodata value in the first band and " +"the second value replace the nodata value in the second band. If one input " +"band do not have a nodata value defined and none are provided as an array, " +"one is chosen using the ST_MinPossibleValue function. All variant accepting " +"an array of nodata value can also accept a single value which will be " +"assigned to each requested band." msgstr "" #. Tag: para @@ -10768,8 +10841,8 @@ msgstr "" #, no-c-format msgid "" "To get more control on the resulting extent or on what to return when " -"encountering a nodata value, use the two rasters version of ." +"encountering a nodata value, use the two rasters version of ." msgstr "" #. Tag: para @@ -10794,8 +10867,8 @@ msgstr "" #, no-c-format msgid "" "Enhanced: 2.0.0 - Intersection in the raster space was introduced. In " -"earlier pre-2.0.0 versions, only intersection performed in vector space were" -" supported." +"earlier pre-2.0.0 versions, only intersection performed in vector space were " +"supported." msgstr "" #. Tag: title @@ -10822,21 +10895,37 @@ msgid "" " CROSS JOIN (\n" " VALUES\n" " (1, ST_Point(3427928, 5793243.85) ),\n" -" (2, ST_GeomFromText('LINESTRING(3427927.85 5793243.75,3427927.8 5793243.75,3427927.8 5793243.8)')),\n" +" (2, ST_GeomFromText('LINESTRING(3427927.85 " +"5793243.75,3427927.8 5793243.75,3427927.8 5793243.8)')),\n" " (3, ST_GeomFromText('LINESTRING(1 2, 3 4)'))\n" " ) As g(gid,geom)\n" " WHERE A.rid = 2\n" ") As foo;\n" "\n" -" rid | gid | geomwkt | val\n" -"-----+-----+---------------------------------------------------------------------------------------------\n" -" 2 | 1 | POINT(3427928 5793243.85) | 249\n" -" 2 | 1 | POINT(3427928 5793243.85) | 253\n" -" 2 | 2 | POINT(3427927.85 5793243.75) | 254\n" -" 2 | 2 | POINT(3427927.8 5793243.8) | 251\n" -" 2 | 2 | POINT(3427927.8 5793243.8) | 253\n" -" 2 | 2 | LINESTRING(3427927.8 5793243.75,3427927.8 5793243.8) | 252\n" -" 2 | 2 | MULTILINESTRING((3427927.8 5793243.8,3427927.8 5793243.75),...) | 250\n" +" rid | gid | " +"geomwkt " +"| val\n" +"-----+-----" +"+---------------------------------------------------------------------------------------------\n" +" 2 | 1 | POINT(3427928 " +"5793243.85) " +"| 249\n" +" 2 | 1 | POINT(3427928 " +"5793243.85) " +"| 253\n" +" 2 | 2 | POINT(3427927.85 " +"5793243.75) | " +"254\n" +" 2 | 2 | POINT(3427927.8 " +"5793243.8) " +"| 251\n" +" 2 | 2 | POINT(3427927.8 " +"5793243.8) " +"| 253\n" +" 2 | 2 | LINESTRING(3427927.8 5793243.75,3427927.8 5793243.8) " +"| 252\n" +" 2 | 2 | MULTILINESTRING((3427927.8 5793243.8,3427927.8 5793243.75),...) " +"| 250\n" " 2 | 3 | GEOMETRYCOLLECTION EMPTY" msgstr "" @@ -10856,9 +10945,9 @@ msgstr "" #: reference_raster.xml:6524 #, no-c-format msgid "" -", , , , " +", , , , " msgstr "" #. Tag: refname @@ -10879,76 +10968,59 @@ msgstr "" #: reference_raster.xml:6543 #, no-c-format msgid "" -" raster ST_MapAlgebra" -" rastbandarg[] " -"rastbandargset " -"regprocedure " -"callbackfunc text " -"pixeltype=NULL text " -"extenttype=INTERSECTION raster " -"customextent=NULL integer " -"distancex=0 integer " -"distancey=0 text[] VARIADIC " -"userargs=NULL " -"raster ST_MapAlgebra " +" raster ST_MapAlgebra " +"rastbandarg[] rastbandargset regprocedure callbackfunc text " +"pixeltype=NULL text extenttype=INTERSECTION raster " +"customextent=NULL integer distancex=0 " +"integer distancey=0 text[] " +"VARIADIC userargs=NULL " +" raster ST_MapAlgebra " "raster rast " "integer[] nband " -"regprocedure " -"callbackfunc text " -"pixeltype=NULL text " -"extenttype=FIRST raster " -"customextent=NULL integer " -"distancex=0 integer " -"distancey=0 text[] VARIADIC " +"regprocedure callbackfunc text " +"pixeltype=NULL text extenttype=FIRST " +"raster customextent=NULL integer " +"distancex=0 integer distancey=0 " +"text[] VARIADIC " "userargs=NULL " "raster ST_MapAlgebra " "raster rast " "integer nband " -"regprocedure " -"callbackfunc text " -"pixeltype=NULL text " -"extenttype=FIRST raster " -"customextent=NULL integer " -"distancex=0 integer " -"distancey=0 text[] VARIADIC " +"regprocedure callbackfunc text " +"pixeltype=NULL text extenttype=FIRST " +"raster customextent=NULL integer " +"distancex=0 integer distancey=0 " +"text[] VARIADIC " "userargs=NULL " "raster ST_MapAlgebra " "raster rast1 " "integer nband1 " "raster rast2 " "integer nband2 " -"regprocedure " -"callbackfunc text " -"pixeltype=NULL text " -"extenttype=INTERSECTION raster " -"customextent=NULL integer " -"distancex=0 integer " -"distancey=0 text[] VARIADIC " -"userargs=NULL " +"regprocedure callbackfunc text " +"pixeltype=NULL text extenttype=INTERSECTION raster " +"customextent=NULL integer distancex=0 " +"integer distancey=0 text[] " +"VARIADIC userargs=NULL " msgstr "" #. Tag: para @@ -11004,24 +11076,45 @@ msgstr "" #: reference_raster.xml:6628 #, no-c-format msgid "" -"The callbackfunc parameter must be the name and signature of an SQL or PL/pgSQL function, cast to a regprocedure. An example PL/pgSQL function example is: \n" -"CREATE OR REPLACE FUNCTION sample_callbackfunc(value double precision[][][], position integer[][], VARIADIC userargs text[])\n" +"The callbackfunc parameter must be the name and signature " +"of an SQL or PL/pgSQL function, cast to a regprocedure. An example PL/pgSQL " +"function example is: \n" +"CREATE OR REPLACE FUNCTION sample_callbackfunc(value double precision[][][], " +"position integer[][], VARIADIC userargs text[])\n" " RETURNS double precision\n" " AS $$\n" " BEGIN\n" " RETURN 0;\n" " END;\n" " $$ LANGUAGE 'plpgsql' IMMUTABLE;\n" -" The callbackfunc must have three arguments: a 3-dimension double precision array, a 2-dimension integer array and a variadic 1-dimension text array. The first argument value is the set of values (as double precision) from all input rasters. The three dimensions (where indexes are 1-based) are: raster #, row y, column x. The second argument position is the set of pixel positions from the output raster and input rasters. The outer dimension (where indexes are 0-based) is the raster #. The position at outer dimension index 0 is the output raster's pixel position. For each outer dimension, there are two elements in the inner dimension for X and Y. The third argument userargs is for passing through any user-specified arguments." +" The callbackfunc must have three " +"arguments: a 3-dimension double precision array, a 2-dimension integer array " +"and a variadic 1-dimension text array. The first argument value is the set of values (as double precision) from all input rasters. " +"The three dimensions (where indexes are 1-based) are: raster #, row y, " +"column x. The second argument position is the set of " +"pixel positions from the output raster and input rasters. The outer " +"dimension (where indexes are 0-based) is the raster #. The position at outer " +"dimension index 0 is the output raster's pixel position. For each outer " +"dimension, there are two elements in the inner dimension for X and Y. The " +"third argument userargs is for passing through any user-" +"specified arguments." msgstr "" #. Tag: para #: reference_raster.xml:6635 #, no-c-format msgid "" -"Passing a regprocedure argument to a SQL function requires the full function signature to be passed, then cast to a regprocedure type. To pass the above example PL/pgSQL function as an argument, the SQL for the argument is: \n" +"Passing a regprocedure argument to a SQL function requires the " +"full function signature to be passed, then cast to a regprocedure type. To pass the above example PL/pgSQL function as an argument, the " +"SQL for the argument is: \n" "'sample_callbackfunc(double precision[], integer[], text[])'::regprocedure\n" -" Note that the argument contains the name of the function, the types of the function arguments, quotes around the name and argument types, and a cast to a regprocedure." +" Note that the argument contains the name of the function, " +"the types of the function arguments, quotes around the name and argument " +"types, and a cast to a regprocedure." msgstr "" #. Tag: term @@ -11035,10 +11128,10 @@ msgstr "" #: reference_raster.xml:6649 #, no-c-format msgid "" -"If pixeltype is passed in, the one band of the new raster" -" will be of that pixeltype. If pixeltype is passed NULL or left out, the new" -" raster band will have the same pixeltype as the specified band of the first" -" raster (for extent types: INTERSECTION, UNION, FIRST, CUSTOM) or the " +"If pixeltype is passed in, the one band of the new raster " +"will be of that pixeltype. If pixeltype is passed NULL or left out, the new " +"raster band will have the same pixeltype as the specified band of the first " +"raster (for extent types: INTERSECTION, UNION, FIRST, CUSTOM) or the " "specified band of the appropriate raster (for extent types: SECOND, LAST). " "If in doubt, always specify pixeltype." msgstr "" @@ -11090,8 +11183,8 @@ msgstr "" #: reference_raster.xml:6679 #, no-c-format msgid "" -"The distance in pixels from the reference cell. So width of resulting matrix" -" would be 2*distancex + 1.If not specified only the reference " +"The distance in pixels from the reference cell. So width of resulting matrix " +"would be 2*distancex + 1.If not specified only the reference " "cell is considered (neighborhood of 0)." msgstr "" @@ -11133,9 +11226,8 @@ msgstr "" msgid "" "For more information about the VARIADIC keyword, please refer to the " "PostgreSQL documentation and the \"SQL Functions with Variable Numbers of " -"Arguments\" section of Query " -"Language (SQL) Functions." +"Arguments\" section of Query Language (SQL) Functions." msgstr "" #. Tag: para @@ -11183,12 +11275,14 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT 1 AS rid, ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, 0, 0), 1, '16BUI', 1, 0) AS rast\n" +" SELECT 1 AS rid, ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, " +"0, 0), 1, '16BUI', 1, 0) AS rast\n" ")\n" "SELECT\n" " ST_MapAlgebra(\n" " ARRAY[ROW(rast, 1)]::rastbandarg[],\n" -" 'sample_callbackfunc(double precision[], int[], text[])'::regprocedure\n" +" 'sample_callbackfunc(double precision[], int[], text[])'::" +"regprocedure\n" " ) AS rast\n" "FROM foo" msgstr "" @@ -11204,12 +11298,16 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT 1 AS rid, ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, 0, 0), 1, '16BUI', 1, 0), 2, '8BUI', 10, 0), 3, '32BUI', 100, 0) AS rast\n" +" SELECT 1 AS rid, " +"ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, 0, " +"0), 1, '16BUI', 1, 0), 2, '8BUI', 10, 0), 3, '32BUI', 100, 0) AS rast\n" ")\n" "SELECT\n" " ST_MapAlgebra(\n" -" ARRAY[ROW(rast, 3), ROW(rast, 1), ROW(rast, 3), ROW(rast, 2)]::rastbandarg[],\n" -" 'sample_callbackfunc(double precision[], int[], text[])'::regprocedure\n" +" ARRAY[ROW(rast, 3), ROW(rast, 1), ROW(rast, 3), ROW(rast, " +"2)]::rastbandarg[],\n" +" 'sample_callbackfunc(double precision[], int[], text[])'::" +"regprocedure\n" " ) AS rast\n" "FROM foo" msgstr "" @@ -11225,13 +11323,20 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT 1 AS rid, ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, 0, 0), 1, '16BUI', 1, 0), 2, '8BUI', 10, 0), 3, '32BUI', 100, 0) AS rast UNION ALL\n" -" SELECT 2 AS rid, ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 1, 1, -1, 0, 0, 0), 1, '16BUI', 2, 0), 2, '8BUI', 20, 0), 3, '32BUI', 300, 0) AS rast\n" +" SELECT 1 AS rid, " +"ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, 0, " +"0), 1, '16BUI', 1, 0), 2, '8BUI', 10, 0), 3, '32BUI', 100, 0) AS rast UNION " +"ALL\n" +" SELECT 2 AS rid, " +"ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 1, 1, -1, 0, 0, " +"0), 1, '16BUI', 2, 0), 2, '8BUI', 20, 0), 3, '32BUI', 300, 0) AS rast\n" ")\n" "SELECT\n" " ST_MapAlgebra(\n" -" ARRAY[ROW(t1.rast, 3), ROW(t2.rast, 1), ROW(t2.rast, 3), ROW(t1.rast, 2)]::rastbandarg[],\n" -" 'sample_callbackfunc(double precision[], int[], text[])'::regprocedure\n" +" ARRAY[ROW(t1.rast, 3), ROW(t2.rast, 1), ROW(t2.rast, 3), " +"ROW(t1.rast, 2)]::rastbandarg[],\n" +" 'sample_callbackfunc(double precision[], int[], text[])'::" +"regprocedure\n" " ) AS rast\n" "FROM foo t1\n" "CROSS JOIN foo t2\n" @@ -11252,23 +11357,33 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT 0 AS rid, ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, 0, 0), 1, '16BUI', 1, 0) AS rast UNION ALL\n" -" SELECT 1, ST_AddBand(ST_MakeEmptyRaster(2, 2, 2, 0, 1, -1, 0, 0, 0), 1, '16BUI', 2, 0) AS rast UNION ALL\n" -" SELECT 2, ST_AddBand(ST_MakeEmptyRaster(2, 2, 4, 0, 1, -1, 0, 0, 0), 1, '16BUI', 3, 0) AS rast UNION ALL\n" +" SELECT 0 AS rid, ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, " +"0, 0), 1, '16BUI', 1, 0) AS rast UNION ALL\n" +" SELECT 1, ST_AddBand(ST_MakeEmptyRaster(2, 2, 2, 0, 1, -1, 0, 0, 0), " +"1, '16BUI', 2, 0) AS rast UNION ALL\n" +" SELECT 2, ST_AddBand(ST_MakeEmptyRaster(2, 2, 4, 0, 1, -1, 0, 0, 0), " +"1, '16BUI', 3, 0) AS rast UNION ALL\n" "\n" -" SELECT 3, ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, -2, 1, -1, 0, 0, 0), 1, '16BUI', 10, 0) AS rast UNION ALL\n" -" SELECT 4, ST_AddBand(ST_MakeEmptyRaster(2, 2, 2, -2, 1, -1, 0, 0, 0), 1, '16BUI', 20, 0) AS rast UNION ALL\n" -" SELECT 5, ST_AddBand(ST_MakeEmptyRaster(2, 2, 4, -2, 1, -1, 0, 0, 0), 1, '16BUI', 30, 0) AS rast UNION ALL\n" +" SELECT 3, ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, -2, 1, -1, 0, 0, " +"0), 1, '16BUI', 10, 0) AS rast UNION ALL\n" +" SELECT 4, ST_AddBand(ST_MakeEmptyRaster(2, 2, 2, -2, 1, -1, 0, 0, " +"0), 1, '16BUI', 20, 0) AS rast UNION ALL\n" +" SELECT 5, ST_AddBand(ST_MakeEmptyRaster(2, 2, 4, -2, 1, -1, 0, 0, " +"0), 1, '16BUI', 30, 0) AS rast UNION ALL\n" "\n" -" SELECT 6, ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, -4, 1, -1, 0, 0, 0), 1, '16BUI', 100, 0) AS rast UNION ALL\n" -" SELECT 7, ST_AddBand(ST_MakeEmptyRaster(2, 2, 2, -4, 1, -1, 0, 0, 0), 1, '16BUI', 200, 0) AS rast UNION ALL\n" -" SELECT 8, ST_AddBand(ST_MakeEmptyRaster(2, 2, 4, -4, 1, -1, 0, 0, 0), 1, '16BUI', 300, 0) AS rast\n" +" SELECT 6, ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, -4, 1, -1, 0, 0, " +"0), 1, '16BUI', 100, 0) AS rast UNION ALL\n" +" SELECT 7, ST_AddBand(ST_MakeEmptyRaster(2, 2, 2, -4, 1, -1, 0, 0, " +"0), 1, '16BUI', 200, 0) AS rast UNION ALL\n" +" SELECT 8, ST_AddBand(ST_MakeEmptyRaster(2, 2, 4, -4, 1, -1, 0, 0, " +"0), 1, '16BUI', 300, 0) AS rast\n" ")\n" "SELECT\n" " t1.rid,\n" " ST_MapAlgebra(\n" " ARRAY[ROW(ST_Union(t2.rast), 1)]::rastbandarg[],\n" -" 'sample_callbackfunc(double precision[], int[], text[])'::regprocedure,\n" +" 'sample_callbackfunc(double precision[], int[], text[])'::" +"regprocedure,\n" " '32BUI',\n" " 'CUSTOM', t1.rast,\n" " 1, 1\n" @@ -11294,17 +11409,26 @@ msgstr "" #, no-c-format msgid "" "WITH src AS (\n" -" SELECT 0 AS rid, ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, 0, 0), 1, '16BUI', 1, 0) AS rast UNION ALL\n" -" SELECT 1, ST_AddBand(ST_MakeEmptyRaster(2, 2, 2, 0, 1, -1, 0, 0, 0), 1, '16BUI', 2, 0) AS rast UNION ALL\n" -" SELECT 2, ST_AddBand(ST_MakeEmptyRaster(2, 2, 4, 0, 1, -1, 0, 0, 0), 1, '16BUI', 3, 0) AS rast UNION ALL\n" +" SELECT 0 AS rid, ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, " +"0, 0), 1, '16BUI', 1, 0) AS rast UNION ALL\n" +" SELECT 1, ST_AddBand(ST_MakeEmptyRaster(2, 2, 2, 0, 1, -1, 0, 0, 0), " +"1, '16BUI', 2, 0) AS rast UNION ALL\n" +" SELECT 2, ST_AddBand(ST_MakeEmptyRaster(2, 2, 4, 0, 1, -1, 0, 0, 0), " +"1, '16BUI', 3, 0) AS rast UNION ALL\n" "\n" -" SELECT 3, ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, -2, 1, -1, 0, 0, 0), 1, '16BUI', 10, 0) AS rast UNION ALL\n" -" SELECT 4, ST_AddBand(ST_MakeEmptyRaster(2, 2, 2, -2, 1, -1, 0, 0, 0), 1, '16BUI', 20, 0) AS rast UNION ALL\n" -" SELECT 5, ST_AddBand(ST_MakeEmptyRaster(2, 2, 4, -2, 1, -1, 0, 0, 0), 1, '16BUI', 30, 0) AS rast UNION ALL\n" +" SELECT 3, ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, -2, 1, -1, 0, 0, " +"0), 1, '16BUI', 10, 0) AS rast UNION ALL\n" +" SELECT 4, ST_AddBand(ST_MakeEmptyRaster(2, 2, 2, -2, 1, -1, 0, 0, " +"0), 1, '16BUI', 20, 0) AS rast UNION ALL\n" +" SELECT 5, ST_AddBand(ST_MakeEmptyRaster(2, 2, 4, -2, 1, -1, 0, 0, " +"0), 1, '16BUI', 30, 0) AS rast UNION ALL\n" "\n" -" SELECT 6, ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, -4, 1, -1, 0, 0, 0), 1, '16BUI', 100, 0) AS rast UNION ALL\n" -" SELECT 7, ST_AddBand(ST_MakeEmptyRaster(2, 2, 2, -4, 1, -1, 0, 0, 0), 1, '16BUI', 200, 0) AS rast UNION ALL\n" -" SELECT 8, ST_AddBand(ST_MakeEmptyRaster(2, 2, 4, -4, 1, -1, 0, 0, 0), 1, '16BUI', 300, 0) AS rast\n" +" SELECT 6, ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, -4, 1, -1, 0, 0, " +"0), 1, '16BUI', 100, 0) AS rast UNION ALL\n" +" SELECT 7, ST_AddBand(ST_MakeEmptyRaster(2, 2, 2, -4, 1, -1, 0, 0, " +"0), 1, '16BUI', 200, 0) AS rast UNION ALL\n" +" SELECT 8, ST_AddBand(ST_MakeEmptyRaster(2, 2, 4, -4, 1, -1, 0, 0, " +"0), 1, '16BUI', 300, 0) AS rast\n" ")\n" "WITH foo AS (\n" " SELECT\n" @@ -11321,7 +11445,8 @@ msgid "" " t1.rid,\n" " ST_MapAlgebra(\n" " ARRAY[ROW(t2.rast, 1)]::rastbandarg[],\n" -" 'raster_nmapalgebra_test(double precision[], int[], text[])'::regprocedure,\n" +" 'raster_nmapalgebra_test(double precision[], int[], " +"text[])'::regprocedure,\n" " '32BUI',\n" " 'CUSTOM', t1.rast,\n" " 1, 1\n" @@ -11349,12 +11474,15 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT 1 AS rid, ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, 0, 0), 1, '16BUI', 1, 0), 2, '8BUI', 10, 0), 3, '32BUI', 100, 0) AS rast\n" +" SELECT 1 AS rid, " +"ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, 0, " +"0), 1, '16BUI', 1, 0), 2, '8BUI', 10, 0), 3, '32BUI', 100, 0) AS rast\n" ")\n" "SELECT\n" " ST_MapAlgebra(\n" " rast, ARRAY[3, 1, 3, 2]::integer[],\n" -" 'sample_callbackfunc(double precision[], int[], text[])'::regprocedure\n" +" 'sample_callbackfunc(double precision[], int[], text[])'::" +"regprocedure\n" " ) AS rast\n" "FROM foo" msgstr "" @@ -11364,12 +11492,15 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT 1 AS rid, ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, 0, 0), 1, '16BUI', 1, 0), 2, '8BUI', 10, 0), 3, '32BUI', 100, 0) AS rast\n" +" SELECT 1 AS rid, " +"ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, 0, " +"0), 1, '16BUI', 1, 0), 2, '8BUI', 10, 0), 3, '32BUI', 100, 0) AS rast\n" ")\n" "SELECT\n" " ST_MapAlgebra(\n" " rast, 2,\n" -" 'sample_callbackfunc(double precision[], int[], text[])'::regprocedure\n" +" 'sample_callbackfunc(double precision[], int[], text[])'::" +"regprocedure\n" " ) AS rast\n" "FROM foo" msgstr "" @@ -11391,14 +11522,20 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT 1 AS rid, ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, 0, 0), 1, '16BUI', 1, 0), 2, '8BUI', 10, 0), 3, '32BUI', 100, 0) AS rast UNION ALL\n" -" SELECT 2 AS rid, ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 1, 1, -1, 0, 0, 0), 1, '16BUI', 2, 0), 2, '8BUI', 20, 0), 3, '32BUI', 300, 0) AS rast\n" +" SELECT 1 AS rid, " +"ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, 0, " +"0), 1, '16BUI', 1, 0), 2, '8BUI', 10, 0), 3, '32BUI', 100, 0) AS rast UNION " +"ALL\n" +" SELECT 2 AS rid, " +"ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 1, 1, -1, 0, 0, " +"0), 1, '16BUI', 2, 0), 2, '8BUI', 20, 0), 3, '32BUI', 300, 0) AS rast\n" ")\n" "SELECT\n" " ST_MapAlgebra(\n" " t1.rast, 2,\n" " t2.rast, 1,\n" -" 'sample_callbackfunc(double precision[], int[], text[])'::regprocedure\n" +" 'sample_callbackfunc(double precision[], int[], text[])'::" +"regprocedure\n" " ) AS rast\n" "FROM foo t1\n" "CROSS JOIN foo t2\n" @@ -11409,7 +11546,8 @@ msgstr "" #. Tag: para #: reference_raster.xml:6772 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refpurpose @@ -11417,57 +11555,53 @@ msgstr "" #, no-c-format msgid "" "Expression version - Returns a one-band raster given one or two " -"input rasters, band indexes and one or more user-specified SQL " -"expressions." +"input rasters, band indexes and one or more user-specified SQL expressions." msgstr "" #. Tag: funcsynopsis #: reference_raster.xml:6790 #, no-c-format msgid "" -" raster ST_MapAlgebra" -" raster rast " +" raster ST_MapAlgebra " +"raster rast " "integer nband " "text pixeltype " "text expression " "double precision " "nodataval=NULL " -" raster ST_MapAlgebra" -" raster rast " +" raster ST_MapAlgebra " +"raster rast " "text pixeltype " "text expression " "double precision " "nodataval=NULL " -" raster ST_MapAlgebra" -" raster rast1 " +" raster ST_MapAlgebra " +"raster rast1 " "integer nband1 " "raster rast2 " "integer nband2 " "text expression " +"text pixeltype=NULL text " +"extenttype=INTERSECTION text nodata1expr=NULL text " +"nodata2expr=NULL double precision nodatanodataval=NULL raster " +"ST_MapAlgebra raster " +"rast1 raster " +"rast2 text " +"expression text pixeltype=NULL " "text " -"pixeltype=NULL text " -"extenttype=INTERSECTION text " -"nodata1expr=NULL text " -"nodata2expr=NULL double precision " -"nodatanodataval=NULL " -" raster ST_MapAlgebra" -" raster rast1 " -"raster rast2 " -"text expression " -"text " -"pixeltype=NULL text " -"extenttype=INTERSECTION text " -"nodata1expr=NULL text " -"nodata2expr=NULL double precision " -"nodatanodataval=NULL " +"extenttype=INTERSECTION text nodata1expr=NULL text " +"nodata2expr=NULL double precision nodatanodataval=NULL " msgstr "" #. Tag: para @@ -11491,8 +11625,8 @@ msgid "" "Creates a new one band raster formed by applying a valid PostgreSQL " "algebraic operation defined by the expression on the " "input raster (rast). If nband is not " -"provided, band 1 is assumed. The new raster will have the same georeference," -" width, and height as the original raster but will only have one band." +"provided, band 1 is assumed. The new raster will have the same georeference, " +"width, and height as the original raster but will only have one band." msgstr "" #. Tag: para @@ -11548,13 +11682,13 @@ msgstr "" #, no-c-format msgid "" "Creates a new one band raster formed by applying a valid PostgreSQL " -"algebraic operation to the two bands defined by the " -"expression on the two input raster bands " -"rast1, (rast2). If no " -"band1, band2 is specified band 1 is " -"assumed. The resulting raster will be aligned (scale, skew and pixel " -"corners) on the grid defined by the first raster. The resulting raster will " -"have the extent defined by the extenttype parameter." +"algebraic operation to the two bands defined by the expression on the two input raster bands rast1, " +"(rast2). If no band1, band2 is specified band 1 is assumed. The resulting raster will be " +"aligned (scale, skew and pixel corners) on the grid defined by the first " +"raster. The resulting raster will have the extent defined by the " +"extenttype parameter." msgstr "" #. Tag: term @@ -11577,8 +11711,8 @@ msgstr "" #, no-c-format msgid "" "The resulting pixel type of the output raster. Must be one listed in , left out or set to NULL. If not passed in" -" or set to NULL, will default to the pixeltype of the first raster." +"linkend=\"RT_ST_BandPixelType\"/>, left out or set to NULL. If not passed in " +"or set to NULL, will default to the pixeltype of the first raster." msgstr "" #. Tag: para @@ -11630,8 +11764,8 @@ msgstr "" #, no-c-format msgid "" "An algebraic expression involving only rast2 or a " -"constant that defines what to return when pixels of rast1" -" are nodata values and spatially corresponding rast2 pixels have values." +"constant that defines what to return when pixels of rast1 " +"are nodata values and spatially corresponding rast2 pixels have values." msgstr "" #. Tag: term @@ -11645,8 +11779,8 @@ msgstr "" #, no-c-format msgid "" "An algebraic expression involving only rast1 or a " -"constant that defines what to return when pixels of rast2" -" are nodata values and spatially corresponding rast1 pixels have values." +"constant that defines what to return when pixels of rast2 " +"are nodata values and spatially corresponding rast1 pixels have values." msgstr "" #. Tag: term @@ -11667,8 +11801,8 @@ msgstr "" #: reference_raster.xml:6962 #, no-c-format msgid "" -"Keywords permitted in expression, " -"nodata1expr and nodata2expr" +"Keywords permitted in expression, nodata1expr and nodata2expr" msgstr "" #. Tag: para @@ -11691,8 +11825,8 @@ msgstr "" #: reference_raster.xml:6971 #, no-c-format msgid "" -"[rast1.x] - 1-based pixel column of the pixel of interest" -" from rast1" +"[rast1.x] - 1-based pixel column of the pixel of interest " +"from rast1" msgstr "" #. Tag: para @@ -11723,8 +11857,8 @@ msgstr "" #: reference_raster.xml:6983 #, no-c-format msgid "" -"[rast2.x] - 1-based pixel column of the pixel of interest" -" from rast2" +"[rast2.x] - 1-based pixel column of the pixel of interest " +"from rast2" msgstr "" #. Tag: para @@ -11746,10 +11880,12 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT ST_AddBand(ST_MakeEmptyRaster(10, 10, 0, 0, 1, 1, 0, 0, 0), '32BF', 1, -1) AS rast\n" +" SELECT ST_AddBand(ST_MakeEmptyRaster(10, 10, 0, 0, 1, 1, 0, 0, 0), " +"'32BF', 1, -1) AS rast\n" ")\n" "SELECT\n" -" ST_MapAlgebra(rast, 1, NULL, 'ceil([rast]*[rast.x]/[rast.y]+[rast.val])')\n" +" ST_MapAlgebra(rast, 1, NULL, 'ceil([rast]*[rast.x]/[rast.y]+[rast." +"val])')\n" "FROM foo" msgstr "" @@ -11764,8 +11900,13 @@ msgstr "" #, no-c-format msgid "" "WITH foo AS (\n" -" SELECT 1 AS rid, ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, 0, 0), 1, '16BUI', 1, 0), 2, '8BUI', 10, 0), 3, '32BUI', 100, 0) AS rast UNION ALL\n" -" SELECT 2 AS rid, ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 1, 1, -1, 0, 0, 0), 1, '16BUI', 2, 0), 2, '8BUI', 20, 0), 3, '32BUI', 300, 0) AS rast\n" +" SELECT 1 AS rid, " +"ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 0, 1, -1, 0, 0, " +"0), 1, '16BUI', 1, 0), 2, '8BUI', 10, 0), 3, '32BUI', 100, 0) AS rast UNION " +"ALL\n" +" SELECT 2 AS rid, " +"ST_AddBand(ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(2, 2, 0, 1, 1, -1, 0, 0, " +"0), 1, '16BUI', 2, 0), 2, '8BUI', 20, 0), 3, '32BUI', 300, 0) AS rast\n" ")\n" "SELECT\n" " ST_MapAlgebra(\n" @@ -11804,20 +11945,18 @@ msgstr "" #: reference_raster.xml:7023 #, no-c-format msgid "" -" raster " -"ST_MapAlgebraExpr raster " -" rast integer " -" band text " -"pixeltype text " -"expression double precision " +" raster ST_MapAlgebraExpr raster rast integer band text pixeltype text expression double precision " "nodataval=NULL " -" raster " -"ST_MapAlgebraExpr raster " -" rast text " -"pixeltype text " -"expression double precision " +" raster ST_MapAlgebraExpr raster rast text pixeltype text expression double precision " "nodataval=NULL " msgstr "" @@ -11836,16 +11975,16 @@ msgid "" "Creates a new one band raster formed by applying a valid PostgreSQL " "algebraic operation defined by the expression on the " "input raster (rast). If no band is " -"specified band 1 is assumed. The new raster will have the same georeference," -" width, and height as the original raster but will only have one band." +"specified band 1 is assumed. The new raster will have the same georeference, " +"width, and height as the original raster but will only have one band." msgstr "" #. Tag: para #: reference_raster.xml:7061 #, no-c-format msgid "" -"In the expression you can use the term [rast] to refer to" -" the pixel value of the original band, [rast.x] to refer " +"In the expression you can use the term [rast] to refer to " +"the pixel value of the original band, [rast.x] to refer " "to the 1-based pixel column index, [rast.y] to refer to " "the 1-based pixel row index." msgstr "" @@ -11864,7 +12003,8 @@ msgstr "" #, no-c-format msgid "" "ALTER TABLE dummy_rast ADD COLUMN map_rast raster;\n" -"UPDATE dummy_rast SET map_rast = ST_MapAlgebraExpr(rast,NULL,'mod([rast],2)') WHERE rid = 2;\n" +"UPDATE dummy_rast SET map_rast = ST_MapAlgebraExpr(rast," +"NULL,'mod([rast],2)') WHERE rid = 2;\n" "\n" "SELECT\n" " ST_Value(rast,1,i,j) As origval,\n" @@ -11901,7 +12041,9 @@ msgstr "" msgid "" "ALTER TABLE dummy_rast ADD COLUMN map_rast2 raster;\n" "UPDATE dummy_rast SET\n" -" map_rast2 = ST_MapAlgebraExpr(rast,'2BUI','CASE WHEN [rast] BETWEEN 100 and 250 THEN 1 WHEN [rast] = 252 THEN 2 WHEN [rast] BETWEEN 253 and 254 THEN 3 ELSE 0 END', '0')\n" +" map_rast2 = ST_MapAlgebraExpr(rast,'2BUI','CASE WHEN [rast] BETWEEN " +"100 and 250 THEN 1 WHEN [rast] = 252 THEN 2 WHEN [rast] BETWEEN 253 and 254 " +"THEN 3 ELSE 0 END', '0')\n" "WHERE rid = 2;\n" "\n" "SELECT DISTINCT\n" @@ -11960,7 +12102,8 @@ msgid "" " ST_AddBand(\n" " ST_AddBand(\n" " ST_MakeEmptyRaster(rast_view),\n" -" ST_MapAlgebraExpr(rast_view,1,NULL,'tan([rast])*[rast]')\n" +" ST_MapAlgebraExpr(rast_view,1," +"NULL,'tan([rast])*[rast]')\n" " ), \n" " ST_Band(rast_view,2)\n" " ),\n" @@ -11974,9 +12117,9 @@ msgstr "" #: reference_raster.xml:7120 #, no-c-format msgid "" -", , , , " -"" +", , , , " msgstr "" #. Tag: refpurpose @@ -11987,8 +12130,8 @@ msgid "" "valid PostgreSQL algebraic operation on the two input raster bands and of " "pixeltype provided. band 1 of each raster is assumed if no band numbers are " "specified. The resulting raster will be aligned (scale, skew and pixel " -"corners) on the grid defined by the first raster and have its extent defined" -" by the \"extenttype\" parameter. Values for \"extenttype\" can be: " +"corners) on the grid defined by the first raster and have its extent defined " +"by the \"extenttype\" parameter. Values for \"extenttype\" can be: " "INTERSECTION, UNION, FIRST, SECOND." msgstr "" @@ -11996,37 +12139,31 @@ msgstr "" #: reference_raster.xml:7139 #, no-c-format msgid "" -" raster " -"ST_MapAlgebraExpr raster " -" rast1 raster " -" rast2 text " -" expression text " +" raster ST_MapAlgebraExpr raster rast1 raster rast2 text expression text " "pixeltype=same_as_rast1_band text " -"extenttype=INTERSECTION text " -"nodata1expr=NULL text " -"nodata2expr=NULL double precision " +"choice=\"opt\">text extenttype=INTERSECTION text " +"nodata1expr=NULL text nodata2expr=NULL " +"double precision " "nodatanodataval=NULL " -" raster " -"ST_MapAlgebraExpr raster " -" rast1 integer " -" band1 raster " -" rast2 integer " -" band2 text " -" expression text " +" raster ST_MapAlgebraExpr raster rast1 integer band1 raster rast2 integer band2 text expression text " "pixeltype=same_as_rast1_band text " -"extenttype=INTERSECTION text " -"nodata1expr=NULL text " -"nodata2expr=NULL double precision " +"choice=\"opt\">text extenttype=INTERSECTION text " +"nodata1expr=NULL text nodata2expr=NULL " +"double precision " "nodatanodataval=NULL " msgstr "" @@ -12045,9 +12182,9 @@ msgstr "" #, no-c-format msgid "" "Use the term [rast1.val] [rast2.val] " -"to refer to the pixel value of the original raster bands and " -"[rast1.x], [rast1.y] etc. to refer to " -"the column / row positions of the pixels." +"to refer to the pixel value of the original raster bands and [rast1." +"x], [rast1.y] etc. to refer to the column / row " +"positions of the pixels." msgstr "" #. Tag: title @@ -12062,31 +12199,39 @@ msgstr "" msgid "" "--Create a cool set of rasters --\n" "DROP TABLE IF EXISTS fun_shapes; \n" -"CREATE TABLE fun_shapes(rid serial PRIMARY KEY, fun_name text, rast raster);\n" +"CREATE TABLE fun_shapes(rid serial PRIMARY KEY, fun_name text, rast " +"raster);\n" "\n" -"-- Insert some cool shapes around Boston in Massachusetts state plane meters --\n" +"-- Insert some cool shapes around Boston in Massachusetts state plane meters " +"--\n" "INSERT INTO fun_shapes(fun_name, rast)\n" -"VALUES ('ref', ST_AsRaster(ST_MakeEnvelope(235229, 899970, 237229, 901930,26986),200,200,'8BUI',0,0));\n" +"VALUES ('ref', ST_AsRaster(ST_MakeEnvelope(235229, 899970, 237229, " +"901930,26986),200,200,'8BUI',0,0));\n" "\n" "INSERT INTO fun_shapes(fun_name,rast)\n" "WITH ref(rast) AS (SELECT rast FROM fun_shapes WHERE fun_name = 'ref' ) \n" -"SELECT 'area' AS fun_name, ST_AsRaster(ST_Buffer(ST_SetSRID(ST_Point(236229, 900930),26986), 1000), \n" +"SELECT 'area' AS fun_name, ST_AsRaster(ST_Buffer(ST_SetSRID(ST_Point(236229, " +"900930),26986), 1000), \n" " ref.rast,'8BUI', 10, 0) As rast\n" "FROM ref\n" "UNION ALL\n" "SELECT 'rand bubbles', \n" " ST_AsRaster( \n" " (SELECT ST_Collect(geom)\n" -" FROM (SELECT ST_Buffer(ST_SetSRID(ST_Point(236229 + i*random()*100, 900930 + j*random()*100),26986), random()*20) As geom\n" -" FROM generate_series(1,10) As i, generate_series(1,10) As j\n" +" FROM (SELECT ST_Buffer(ST_SetSRID(ST_Point(236229 + i*random()*100, " +"900930 + j*random()*100),26986), random()*20) As geom\n" +" FROM generate_series(1,10) As i, " +"generate_series(1,10) As j\n" " ) As foo ), ref.rast,'8BUI', 200, 0) \n" "FROM ref;\n" "\n" "--map them -\n" "SELECT ST_MapAlgebraExpr(\n" -" area.rast, bub.rast, '[rast2.val]', '8BUI', 'INTERSECTION', '[rast2.val]', '[rast1.val]') As interrast,\n" +" area.rast, bub.rast, '[rast2.val]', '8BUI', 'INTERSECTION', " +"'[rast2.val]', '[rast1.val]') As interrast,\n" " ST_MapAlgebraExpr(\n" -" area.rast, bub.rast, '[rast2.val]', '8BUI', 'UNION', '[rast2.val]', '[rast1.val]') As unionrast\n" +" area.rast, bub.rast, '[rast2.val]', '8BUI', 'UNION', " +"'[rast2.val]', '[rast1.val]') As unionrast\n" "FROM \n" " (SELECT rast FROM fun_shapes WHERE\n" " fun_name = 'area') As area\n" @@ -12122,27 +12267,33 @@ msgid "" " AS ( SELECT 2 As bnum, ST_Buffer(ST_Point(1,5),10) As geom\n" " UNION ALL\n" " SELECT 3 AS bnum, \n" -" ST_Buffer(ST_GeomFromText('LINESTRING(50 50,150 150,150 50)'), 10,'join=bevel') As geom\n" +" ST_Buffer(ST_GeomFromText('LINESTRING(50 50,150 150,150 " +"50)'), 10,'join=bevel') As geom\n" " UNION ALL\n" " SELECT 1 As bnum, \n" -" ST_Buffer(ST_GeomFromText('LINESTRING(60 50,150 150,150 50)'), 5,'join=bevel') As geom\n" +" ST_Buffer(ST_GeomFromText('LINESTRING(60 50,150 150,150 " +"50)'), 5,'join=bevel') As geom\n" " ),\n" " -- define our canvas to be 1 to 1 pixel to geometry\n" " canvas\n" " AS (SELECT ST_AddBand(ST_MakeEmptyRaster(200, \n" " 200, \n" -" ST_XMin(e)::integer, ST_YMax(e)::integer, 1, -1, 0, 0) , '8BUI'::text,0) As rast\n" +" ST_XMin(e)::integer, ST_YMax(e)::integer, 1, -1, 0, 0) , '8BUI'::" +"text,0) As rast\n" " FROM (SELECT ST_Extent(geom) As e,\n" " Max(ST_SRID(geom)) As srid \n" " from mygeoms \n" " ) As foo\n" " ),\n" -" rbands AS (SELECT ARRAY(SELECT ST_MapAlgebraExpr(canvas.rast, ST_AsRaster(m.geom, canvas.rast, '8BUI', 100),\n" -" '[rast2.val]', '8BUI', 'FIRST', '[rast2.val]', '[rast1.val]') As rast\n" +" rbands AS (SELECT ARRAY(SELECT ST_MapAlgebraExpr(canvas.rast, " +"ST_AsRaster(m.geom, canvas.rast, '8BUI', 100),\n" +" '[rast2.val]', '8BUI', 'FIRST', '[rast2.val]', '[rast1." +"val]') As rast\n" " FROM mygeoms AS m CROSS JOIN canvas\n" " ORDER BY m.bnum) As rasts\n" " )\n" -" SELECT rasts[1] As rast1 , rasts[2] As rast2, rasts[3] As rast3, ST_AddBand(\n" +" SELECT rasts[1] As rast1 , rasts[2] As rast2, rasts[3] As rast3, " +"ST_AddBand(\n" " ST_AddBand(rasts[1],rasts[2]), rasts[3]) As final_rast\n" " FROM rbands;" msgstr "" @@ -12182,30 +12333,38 @@ msgstr "" #: reference_raster.xml:7384 #, no-c-format msgid "" -"-- Create new 3 band raster composed of first 2 clipped bands, and overlay of 3rd band with our geometry\n" +"-- Create new 3 band raster composed of first 2 clipped bands, and overlay " +"of 3rd band with our geometry\n" "-- This query took 3.6 seconds on PostGIS windows 64-bit install\n" "WITH pr AS\n" -"-- Note the order of operation: we clip all the rasters to dimensions of our region\n" +"-- Note the order of operation: we clip all the rasters to dimensions of our " +"region\n" "(SELECT ST_Clip(rast,ST_Expand(geom,50) ) As rast, g.geom\n" " FROM aerials.o_2_boston AS r INNER JOIN\n" -"-- union our parcels of interest so they form a single geometry we can later intersect with\n" +"-- union our parcels of interest so they form a single geometry we can later " +"intersect with\n" " (SELECT ST_Union(ST_Transform(the_geom,26986)) AS geom \n" -" FROM landparcels WHERE pid IN('0303890000', '0303900000')) As g\n" +" FROM landparcels WHERE pid IN('0303890000', '0303900000')) " +"As g\n" " ON ST_Intersects(rast::geometry, ST_Expand(g.geom,50))\n" "),\n" "-- we then union the raster shards together\n" -"-- ST_Union on raster is kinda of slow but much faster the smaller you can get the rasters\n" +"-- ST_Union on raster is kinda of slow but much faster the smaller you can " +"get the rasters\n" "-- therefore we want to clip first and then union\n" "prunion AS\n" -"(SELECT ST_AddBand(NULL, ARRAY[ST_Union(rast,1),ST_Union(rast,2),ST_Union(rast,3)] ) As clipped,geom\n" +"(SELECT ST_AddBand(NULL, ARRAY[ST_Union(rast,1),ST_Union(rast,2)," +"ST_Union(rast,3)] ) As clipped,geom\n" "FROM pr\n" "GROUP BY geom)\n" "-- return our final raster which is the unioned shard with \n" "-- with the overlay of our parcel boundaries\n" "-- add first 2 bands, then mapalgebra of 3rd band + geometry\n" "SELECT ST_AddBand(ST_Band(clipped,ARRAY[1,2])\n" -" , ST_MapAlgebraExpr(ST_Band(clipped,3), ST_AsRaster(ST_Buffer(ST_Boundary(geom),2),clipped, '8BUI',250),\n" -" '[rast2.val]', '8BUI', 'FIRST', '[rast2.val]', '[rast1.val]') ) As rast\n" +" , ST_MapAlgebraExpr(ST_Band(clipped,3), " +"ST_AsRaster(ST_Buffer(ST_Boundary(geom),2),clipped, '8BUI',250),\n" +" '[rast2.val]', '8BUI', 'FIRST', '[rast2.val]', '[rast1.val]') ) As " +"rast\n" "FROM prunion;" msgstr "" @@ -12220,8 +12379,8 @@ msgstr "" #, no-c-format msgid "" ", , , , , , , " +"linkend=\"RT_ST_AsRaster\"/>, , , , " ", , " msgstr "" @@ -12237,66 +12396,54 @@ msgstr "" #, no-c-format msgid "" "1 band version - Creates a new one band raster formed by applying a valid " -"PostgreSQL function on the input raster band and of pixeltype prodived. Band" -" 1 is assumed if no band is specified." +"PostgreSQL function on the input raster band and of pixeltype prodived. Band " +"1 is assumed if no band is specified." msgstr "" #. Tag: funcsynopsis #: reference_raster.xml:7434 #, no-c-format msgid "" -" raster " -"ST_MapAlgebraFct " -"raster rast " -"regprocedure " -"onerasteruserfunc " -" raster " -"ST_MapAlgebraFct " -"raster rast " -"regprocedure " -"onerasteruserfunc " -"text[] VARIADIC " -"args raster" -" ST_MapAlgebraFct " -"raster rast " -"text pixeltype " -"regprocedure " +" raster ST_MapAlgebraFct raster rast regprocedure onerasteruserfunc raster " +"ST_MapAlgebraFct raster rast regprocedure onerasteruserfunc " +"text[] VARIADIC args raster " +"ST_MapAlgebraFct raster rast text " +"pixeltype regprocedure onerasteruserfunc " +" raster ST_MapAlgebraFct raster rast text pixeltype regprocedure onerasteruserfunc text[] VARIADIC " +"args raster " +"ST_MapAlgebraFct raster rast integer " +"band regprocedure " "onerasteruserfunc " -" raster " -"ST_MapAlgebraFct " -"raster rast " -"text pixeltype " -"regprocedure " -"onerasteruserfunc " -"text[] VARIADIC " -"args raster" -" ST_MapAlgebraFct " -"raster rast " -"integer band " -"regprocedure " -"onerasteruserfunc " -" raster " -"ST_MapAlgebraFct " -"raster rast " -"integer band " -"regprocedure " -"onerasteruserfunc " -"text[] VARIADIC " -"args raster" -" ST_MapAlgebraFct " -"raster rast " -"integer band " -"text pixeltype " -"regprocedure " -"onerasteruserfunc " -" raster " -"ST_MapAlgebraFct " -"raster rast " -"integer band " -"text pixeltype " -"regprocedure " -"onerasteruserfunc " -"text[] VARIADIC " +" raster ST_MapAlgebraFct raster rast integer band regprocedure onerasteruserfunc text[] VARIADIC " +"args raster " +"ST_MapAlgebraFct raster rast integer " +"band text " +"pixeltype regprocedure onerasteruserfunc " +" raster ST_MapAlgebraFct raster rast integer band text pixeltype regprocedure onerasteruserfunc text[] VARIADIC " "args " msgstr "" @@ -12312,8 +12459,8 @@ msgstr "" #: reference_raster.xml:7503 #, no-c-format msgid "" -"Creates a new one band raster formed by applying a valid PostgreSQL function" -" specified by the onerasteruserfunc on the input raster " +"Creates a new one band raster formed by applying a valid PostgreSQL function " +"specified by the onerasteruserfunc on the input raster " "(rast). If no band is specified, band " "1 is assumed. The new raster will have the same georeference, width, and " "height as the original raster but will only have one band." @@ -12323,12 +12470,23 @@ msgstr "" #: reference_raster.xml:7507 #, no-c-format msgid "" -"The onerasteruserfunc parameter must be the name and signature of a SQL or PL/pgSQL function, cast to a regprocedure. A very simple and quite useless PL/pgSQL function example is: CREATE OR REPLACE FUNCTION simple_function(pixel FLOAT, pos INTEGER[], VARIADIC args TEXT[])\n" +"The onerasteruserfunc parameter must be the name and " +"signature of a SQL or PL/pgSQL function, cast to a regprocedure. A very " +"simple and quite useless PL/pgSQL function example is: " +"CREATE OR REPLACE FUNCTION simple_function(pixel FLOAT, pos " +"INTEGER[], VARIADIC args TEXT[])\n" " RETURNS FLOAT\n" " AS $$ BEGIN\n" " RETURN 0.0;\n" " END; $$\n" -" LANGUAGE 'plpgsql' IMMUTABLE; The userfunction may accept two or three arguments: a float value, an optional integer array, and a variadic text array. The first argument is the value of an individual raster cell (regardless of the raster datatype). The second argument is the position of the current processing cell in the form '{x,y}'. The third argument indicates that all remaining parameters to shall be passed through to the userfunction." +" LANGUAGE 'plpgsql' IMMUTABLE; The " +"userfunction may accept two or three arguments: a float " +"value, an optional integer array, and a variadic text array. The first " +"argument is the value of an individual raster cell (regardless of the raster " +"datatype). The second argument is the position of the current processing " +"cell in the form '{x,y}'. The third argument indicates that all remaining " +"parameters to shall be passed " +"through to the userfunction." msgstr "" #. Tag: para @@ -12336,13 +12494,12 @@ msgstr "" #, no-c-format msgid "" "Passing a regprodedure argument to a SQL function requires the " -"full function signature to be passed, then cast to a " -"regprocedure type. To pass the above example PL/pgSQL function " -"as an argument, the SQL for the argument " -"is:'simple_function(float,integer[],text[])'::regprocedureNote" -" that the argument contains the name of the function, the types of the " -"function arguments, quotes around the name and argument types, and a cast to" -" a regprocedure." +"full function signature to be passed, then cast to a regprocedure type. To pass the above example PL/pgSQL function as an argument, the " +"SQL for the argument is:'simple_function(float,integer[]," +"text[])'::regprocedureNote that the argument contains the " +"name of the function, the types of the function arguments, quotes around the " +"name and argument types, and a cast to a regprocedure." msgstr "" #. Tag: para @@ -12352,8 +12509,8 @@ msgid "" "The third argument to the userfunction is a " "variadic text array. All trailing text arguments to any call are passed through to the specified " -"userfunction, and are contained in the " -"args argument." +"userfunction, and are contained in the args argument." msgstr "" #. Tag: para @@ -12379,10 +12536,13 @@ msgid "" "$$\n" "LANGUAGE 'plpgsql' IMMUTABLE;\n" "\n" -"UPDATE dummy_rast SET map_rast = ST_MapAlgebraFct(rast,NULL,'mod_fct(float,integer[],text[])'::regprocedure) WHERE rid = 2;\n" +"UPDATE dummy_rast SET map_rast = ST_MapAlgebraFct(rast,NULL,'mod_fct(float," +"integer[],text[])'::regprocedure) WHERE rid = 2;\n" "\n" -"SELECT ST_Value(rast,1,i,j) As origval, ST_Value(map_rast, 1, i, j) As mapval\n" -"FROM dummy_rast CROSS JOIN generate_series(1, 3) AS i CROSS JOIN generate_series(1,3) AS j\n" +"SELECT ST_Value(rast,1,i,j) As origval, ST_Value(map_rast, 1, i, j) As " +"mapval\n" +"FROM dummy_rast CROSS JOIN generate_series(1, 3) AS i CROSS JOIN " +"generate_series(1,3) AS j\n" "WHERE rid = 2;\n" "\n" " origval | mapval\n" @@ -12412,7 +12572,8 @@ msgstr "" #, no-c-format msgid "" "ALTER TABLE dummy_rast ADD COLUMN map_rast2 raster;\n" -"CREATE FUNCTION classify_fct(pixel float, pos integer[], variadic args text[])\n" +"CREATE FUNCTION classify_fct(pixel float, pos integer[], variadic args " +"text[])\n" "RETURNS float\n" "AS\n" "$$\n" @@ -12434,10 +12595,14 @@ msgid "" "END;\n" "$$\n" "LANGUAGE 'plpgsql';\n" -"UPDATE dummy_rast SET map_rast2 = ST_MapAlgebraFct(rast,'2BUI','classify_fct(float,integer[],text[])'::regprocedure, '0') WHERE rid = 2;\n" +"UPDATE dummy_rast SET map_rast2 = " +"ST_MapAlgebraFct(rast,'2BUI','classify_fct(float,integer[],text[])'::" +"regprocedure, '0') WHERE rid = 2;\n" "\n" -"SELECT DISTINCT ST_Value(rast,1,i,j) As origval, ST_Value(map_rast2, 1, i, j) As mapval\n" -"FROM dummy_rast CROSS JOIN generate_series(1, 5) AS i CROSS JOIN generate_series(1,5) AS j\n" +"SELECT DISTINCT ST_Value(rast,1,i,j) As origval, ST_Value(map_rast2, 1, i, " +"j) As mapval\n" +"FROM dummy_rast CROSS JOIN generate_series(1, 5) AS i CROSS JOIN " +"generate_series(1,5) AS j\n" "WHERE rid = 2;\n" "\n" " origval | mapval\n" @@ -12461,7 +12626,8 @@ msgstr "" #: reference_raster.xml:7566 #, no-c-format msgid "" -"CREATE FUNCTION rast_plus_tan(pixel float, pos integer[], variadic args text[])\n" +"CREATE FUNCTION rast_plus_tan(pixel float, pos integer[], variadic args " +"text[])\n" "RETURNS float\n" "AS\n" "$$\n" @@ -12475,7 +12641,8 @@ msgid "" " ST_AddBand(\n" " ST_AddBand(\n" " ST_MakeEmptyRaster(rast_view),\n" -" ST_MapAlgebraFct(rast_view,1,NULL,'rast_plus_tan(float,integer[],text[])'::regprocedure)\n" +" ST_MapAlgebraFct(rast_view,1," +"NULL,'rast_plus_tan(float,integer[],text[])'::regprocedure)\n" " ), \n" " ST_Band(rast_view,2)\n" " ),\n" @@ -12489,8 +12656,8 @@ msgstr "" #: reference_raster.xml:7571 reference_raster.xml:7694 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refpurpose @@ -12507,43 +12674,38 @@ msgstr "" #: reference_raster.xml:7587 #, no-c-format msgid "" -" raster " -"ST_MapAlgebraFct " -"raster rast1 " -"raster rast2 " -"regprocedure " -"tworastuserfunc text " -"pixeltype=same_as_rast1 text " -"extenttype=INTERSECTION " -"text[] VARIADIC " -"userargs " -"raster ST_MapAlgebraFct " -"raster rast1 " -"integer band1 " -"raster rast2 " -"integer band2 " -"regprocedure " -"tworastuserfunc text " -"pixeltype=same_as_rast1 text " +" raster ST_MapAlgebraFct raster rast1 raster rast2 regprocedure tworastuserfunc text " +"pixeltype=same_as_rast1 text extenttype=INTERSECTION text[] VARIADIC userargs raster " +"ST_MapAlgebraFct raster rast1 integer " +"band1 raster " +"rast2 integer " +"band2 regprocedure " +"tworastuserfunc text pixeltype=same_as_rast1 text " "extenttype=INTERSECTION " -"text[] VARIADIC " -"userargs " +"text[] VARIADIC userargs " msgstr "" #. Tag: para #: reference_raster.xml:7621 #, no-c-format msgid "" -"Creates a new one band raster formed by applying a valid PostgreSQL function" -" specified by the tworastuserfunc on the input raster " -"rast1, rast2. If no " -"band1 or band2 is specified, band 1 is" -" assumed. The new raster will have the same georeference, width, and height " -"as the original rasters but will only have one band." +"Creates a new one band raster formed by applying a valid PostgreSQL function " +"specified by the tworastuserfunc on the input raster " +"rast1, rast2. If no band1 or band2 is specified, band 1 is assumed. The " +"new raster will have the same georeference, width, and height as the " +"original rasters but will only have one band." msgstr "" #. Tag: para @@ -12552,20 +12714,33 @@ msgstr "" msgid "" "If pixeltype is passed in, then the new raster will have " "a band of that pixeltype. If pixeltype is passed NULL or left out, then the " -"new raster band will have the same pixeltype as the input " -"rast1 band." +"new raster band will have the same pixeltype as the input rast1 band." msgstr "" #. Tag: para #: reference_raster.xml:7627 #, no-c-format msgid "" -"The tworastuserfunc parameter must be the name and signature of an SQL or PL/pgSQL function, cast to a regprocedure. An example PL/pgSQL function example is: CREATE OR REPLACE FUNCTION simple_function_for_two_rasters(pixel1 FLOAT, pixel2 FLOAT, pos INTEGER[], VARIADIC args TEXT[])\n" +"The tworastuserfunc parameter must be the name and " +"signature of an SQL or PL/pgSQL function, cast to a regprocedure. An example " +"PL/pgSQL function example is: CREATE OR REPLACE FUNCTION " +"simple_function_for_two_rasters(pixel1 FLOAT, pixel2 FLOAT, pos INTEGER[], " +"VARIADIC args TEXT[])\n" " RETURNS FLOAT\n" " AS $$ BEGIN\n" " RETURN 0.0;\n" " END; $$\n" -" LANGUAGE 'plpgsql' IMMUTABLE; The tworastuserfunc may accept three or four arguments: a double precision value, a double precision value, an optional integer array, and a variadic text array. The first argument is the value of an individual raster cell in rast1 (regardless of the raster datatype). The second argument is an individual raster cell value in rast2. The third argument is the position of the current processing cell in the form '{x,y}'. The fourth argument indicates that all remaining parameters to shall be passed through to the tworastuserfunc." +" LANGUAGE 'plpgsql' IMMUTABLE; The " +"tworastuserfunc may accept three or four arguments: a " +"double precision value, a double precision value, an optional integer array, " +"and a variadic text array. The first argument is the value of an individual " +"raster cell in rast1 (regardless of the raster datatype). " +"The second argument is an individual raster cell value in rast2. The third argument is the position of the current processing cell " +"in the form '{x,y}'. The fourth argument indicates that all remaining " +"parameters to shall be passed " +"through to the tworastuserfunc." msgstr "" #. Tag: para @@ -12573,14 +12748,13 @@ msgstr "" #, no-c-format msgid "" "Passing a regprodedure argument to a SQL function requires the " -"full function signature to be passed, then cast to a " -"regprocedure type. To pass the above example PL/pgSQL function " -"as an argument, the SQL for the argument " -"is:'simple_function(double precision, double precision, " -"integer[], text[])'::regprocedureNote that the argument " -"contains the name of the function, the types of the function arguments, " -"quotes around the name and argument types, and a cast to a " -"regprocedure." +"full function signature to be passed, then cast to a regprocedure type. To pass the above example PL/pgSQL function as an argument, the " +"SQL for the argument is:'simple_function(double precision, " +"double precision, integer[], text[])'::regprocedureNote " +"that the argument contains the name of the function, the types of the " +"function arguments, quotes around the name and argument types, and a cast to " +"a regprocedure." msgstr "" #. Tag: para @@ -12635,22 +12809,27 @@ msgid "" "\n" "-- prep our test table of rasters\n" "DROP TABLE IF EXISTS map_shapes;\n" -"CREATE TABLE map_shapes(rid serial PRIMARY KEY, rast raster, bnum integer, descrip text);\n" +"CREATE TABLE map_shapes(rid serial PRIMARY KEY, rast raster, bnum integer, " +"descrip text);\n" "INSERT INTO map_shapes(rast,bnum, descrip)\n" "WITH mygeoms \n" -" AS ( SELECT 2 As bnum, ST_Buffer(ST_Point(90,90),30) As geom, 'circle' As descrip\n" +" AS ( SELECT 2 As bnum, ST_Buffer(ST_Point(90,90),30) As geom, 'circle' " +"As descrip\n" " UNION ALL\n" " SELECT 3 AS bnum, \n" -" ST_Buffer(ST_GeomFromText('LINESTRING(50 50,150 150,150 50)'), 15) As geom, 'big road' As descrip\n" +" ST_Buffer(ST_GeomFromText('LINESTRING(50 50,150 150,150 " +"50)'), 15) As geom, 'big road' As descrip\n" " UNION ALL\n" " SELECT 1 As bnum, \n" -" ST_Translate(ST_Buffer(ST_GeomFromText('LINESTRING(60 50,150 150,150 50)'), 8,'join=bevel'), 10,-6) As geom, 'small road' As descrip\n" +" ST_Translate(ST_Buffer(ST_GeomFromText('LINESTRING(60 50,150 " +"150,150 50)'), 8,'join=bevel'), 10,-6) As geom, 'small road' As descrip\n" " ),\n" " -- define our canvas to be 1 to 1 pixel to geometry\n" " canvas\n" " AS ( SELECT ST_AddBand(ST_MakeEmptyRaster(250, \n" " 250, \n" -" ST_XMin(e)::integer, ST_YMax(e)::integer, 1, -1, 0, 0 ) , '8BUI'::text,0) As rast\n" +" ST_XMin(e)::integer, ST_YMax(e)::integer, 1, -1, 0, 0 ) , '8BUI'::" +"text,0) As rast\n" " FROM (SELECT ST_Extent(geom) As e,\n" " Max(ST_SRID(geom)) As srid \n" " from mygeoms \n" @@ -12665,11 +12844,14 @@ msgid "" "\n" "-- Map algebra on single band rasters and then collect with ST_AddBand\n" "INSERT INTO map_shapes(rast,bnum,descrip)\n" -"SELECT ST_AddBand(ST_AddBand(rasts[1], rasts[2]),rasts[3]), 4, 'map bands overlay fct union (canvas)'\n" +"SELECT ST_AddBand(ST_AddBand(rasts[1], rasts[2]),rasts[3]), 4, 'map bands " +"overlay fct union (canvas)'\n" " FROM (SELECT ARRAY(SELECT ST_MapAlgebraFct(m1.rast, m2.rast, \n" -" 'raster_mapalgebra_union(double precision, double precision, integer[], text[])'::regprocedure, '8BUI', 'FIRST')\n" +" 'raster_mapalgebra_union(double precision, double " +"precision, integer[], text[])'::regprocedure, '8BUI', 'FIRST')\n" " FROM map_shapes As m1 CROSS JOIN map_shapes As m2\n" -" WHERE m1.descrip = 'canvas' AND m2.descrip <> 'canvas' ORDER BY m2.bnum) As rasts) As foo;" +" WHERE m1.descrip = 'canvas' AND m2.descrip <> " +"'canvas' ORDER BY m2.bnum) As rasts) As foo;" msgstr "" #. Tag: para @@ -12700,13 +12882,16 @@ msgid "" " BEGIN\n" " CASE\n" " WHEN rast1 IS NOT NULL AND rast2 IS NOT NULL THEN\n" -" RETURN least(userargs[1]::integer,(rast1 + rast2)/2.);\n" +" RETURN least(userargs[1]::integer,(rast1 + " +"rast2)/2.);\n" " WHEN rast1 IS NULL AND rast2 IS NULL THEN\n" " RETURN userargs[2]::integer;\n" " WHEN rast1 IS NULL THEN\n" -" RETURN greatest(rast2,random()*userargs[3]::integer)::integer;\n" +" RETURN greatest(rast2,random()*userargs[3]::" +"integer)::integer;\n" " ELSE\n" -" RETURN greatest(rast1, random()*userargs[4]::integer)::integer;\n" +" RETURN greatest(rast1, random()*userargs[4]::" +"integer)::integer;\n" " END CASE;\n" "\n" " RETURN NULL;\n" @@ -12714,10 +12899,13 @@ msgid "" " $$ LANGUAGE 'plpgsql' VOLATILE COST 1000;\n" " \n" "SELECT ST_MapAlgebraFct(m1.rast, 1, m1.rast, 3,\n" -" 'raster_mapalgebra_userargs(double precision, double precision, integer[], text[])'::regprocedure,\n" -" '8BUI', 'INTERSECT', '100','200','200','0') \n" +" 'raster_mapalgebra_userargs(double precision, double " +"precision, integer[], text[])'::regprocedure,\n" +" '8BUI', 'INTERSECT', " +"'100','200','200','0') \n" " FROM map_shapes As m1\n" -" WHERE m1.descrip = 'map bands overlay fct union (canvas)';" +" WHERE m1.descrip = 'map bands overlay fct union " +"(canvas)';" msgstr "" #. Tag: para @@ -12751,10 +12939,10 @@ msgid "" "text pixeltype " "integer ngbwidth " "integer ngbheight " -"regprocedure " -"onerastngbuserfunc text " -" nodatamode text[] " -" VARIADIC args" +"regprocedure onerastngbuserfunc text nodatamode text[] VARIADIC " +"args" msgstr "" #. Tag: para @@ -12764,9 +12952,8 @@ msgid "" "(one raster version) Return a raster which values are the result of a " "PLPGSQL user function involving a neighborhood of values from the input " "raster band. The user function takes the neighborhood of pixel values as an " -"array of numbers, for each pixel, returns the result from the user function," -" replacing pixel value of currently inspected pixel with the function " -"result." +"array of numbers, for each pixel, returns the result from the user function, " +"replacing pixel value of currently inspected pixel with the function result." msgstr "" #. Tag: term @@ -12799,9 +12986,9 @@ msgstr "" msgid "" "The resulting pixel type of the output raster. Must be one listed in or left out or set to NULL. If not passed " -"in or set to NULL, will default to the pixeltype of the " -"rast. Results are truncated if they are larger than what " -"is allowed for the pixeltype." +"in or set to NULL, will default to the pixeltype of the rast. Results are truncated if they are larger than what is allowed for " +"the pixeltype." msgstr "" #. Tag: term @@ -12862,8 +13049,8 @@ msgstr "" #, no-c-format msgid "" "'ignore': any NODATA values encountered in the neighborhood are ignored by " -"the computation -- this flag must be sent to the user callback function, and" -" the user function decides how to ignore it." +"the computation -- this flag must be sent to the user callback function, and " +"the user function decides how to ignore it." msgstr "" #. Tag: para @@ -12902,9 +13089,9 @@ msgstr "" #, no-c-format msgid "" "Examples utilize the katrina raster loaded as a single tile described in " -"http://trac.osgeo.org/gdal/wiki/frmts_wtkraster.html" -" and then prepared in the examples" +"http://" +"trac.osgeo.org/gdal/wiki/frmts_wtkraster.html and then prepared in " +"the examples" msgstr "" #. Tag: programlisting @@ -12912,9 +13099,11 @@ msgstr "" #, no-c-format msgid "" "--\n" -"-- A simple 'callback' user function that averages up all the values in a neighborhood.\n" +"-- A simple 'callback' user function that averages up all the values in a " +"neighborhood.\n" "--\n" -"CREATE OR REPLACE FUNCTION rast_avg(matrix float[][], nodatamode text, variadic args text[])\n" +"CREATE OR REPLACE FUNCTION rast_avg(matrix float[][], nodatamode text, " +"variadic args text[])\n" " RETURNS float AS\n" " $$\n" " DECLARE\n" @@ -12932,14 +13121,17 @@ msgid "" " sum := sum + _matrix[x][y];\n" " END LOOP;\n" " END LOOP;\n" -" RETURN (sum*1.0/(array_upper(matrix,1)*array_upper(matrix,2) ))::integer ;\n" +" RETURN (sum*1.0/(array_upper(matrix,1)*array_upper(matrix,2) ))::" +"integer ;\n" " END;\n" " $$\n" "LANGUAGE 'plpgsql' IMMUTABLE COST 1000;\n" " \n" -"-- now we apply to our raster averaging pixels within 2 pixels of each other in X and Y direction --\n" +"-- now we apply to our raster averaging pixels within 2 pixels of each other " +"in X and Y direction --\n" "SELECT ST_MapAlgebraFctNgb(rast, 1, '8BUI', 4,4,\n" -" 'rast_avg(float[][], text, text[])'::regprocedure, 'NULL', NULL) As nn_with_border\n" +" 'rast_avg(float[][], text, text[])'::regprocedure, 'NULL', " +"NULL) As nn_with_border\n" " FROM katrinas_rescaled \n" " limit 1;" msgstr "" @@ -12959,7 +13151,8 @@ msgstr "" #. Tag: para #: reference_raster.xml:7827 #, no-c-format -msgid ", , " +msgid "" +", , " msgstr "" #. Tag: refname @@ -12991,13 +13184,12 @@ msgid "" "nodataval=NULL " " raster ST_Reclass " "raster rast " -"reclassarg[] VARIADIC " -"reclassargset " -"raster ST_Reclass " -"raster rast " -"text reclassexpr " -"text pixeltype " -"" +"reclassarg[] VARIADIC reclassargset raster " +"ST_Reclass raster " +"rast text " +"reclassexpr text " +"pixeltype " msgstr "" #. Tag: para @@ -13006,8 +13198,8 @@ msgstr "" msgid "" "Creates a new raster formed by applying a valid PostgreSQL algebraic " "operation defined by the reclassexpr on the input raster " -"(rast). If no band is specified band 1" -" is assumed. The new raster will have the same georeference, width, and " +"(rast). If no band is specified band 1 " +"is assumed. The new raster will have the same georeference, width, and " "height as the original raster. Bands not designated will come back " "unchanged. Refer to for description of valid " "reclassification expressions." @@ -13017,9 +13209,9 @@ msgstr "" #: reference_raster.xml:7872 #, no-c-format msgid "" -"The bands of the new raster will have pixel type of " -"pixeltype. If reclassargset is passed " -"in then each reclassarg defines behavior of each band generated." +"The bands of the new raster will have pixel type of pixeltype. If reclassargset is passed in then each " +"reclassarg defines behavior of each band generated." msgstr "" #. Tag: title @@ -13032,8 +13224,8 @@ msgstr "" #: reference_raster.xml:7879 #, no-c-format msgid "" -"Create a new raster from the original where band 2 is converted from 8BUI to" -" 4BUI and all values from 101-254 are set to nodata value." +"Create a new raster from the original where band 2 is converted from 8BUI to " +"4BUI and all values from 101-254 are set to nodata value." msgstr "" #. Tag: programlisting @@ -13041,12 +13233,14 @@ msgstr "" #, no-c-format msgid "" "ALTER TABLE dummy_rast ADD COLUMN reclass_rast raster;\n" -"UPDATE dummy_rast SET reclass_rast = ST_Reclass(rast,2,'0-87:1-10, 88-100:11-15, 101-254:0-0', '4BUI',0) WHERE rid = 2;\n" +"UPDATE dummy_rast SET reclass_rast = ST_Reclass(rast,2,'0-87:1-10, " +"88-100:11-15, 101-254:0-0', '4BUI',0) WHERE rid = 2;\n" "\n" "SELECT i as col, j as row, ST_Value(rast,2,i,j) As origval, \n" " ST_Value(reclass_rast, 2, i, j) As reclassval, \n" " ST_Value(reclass_rast, 2, i, j, false) As reclassval_include_nodata\n" -"FROM dummy_rast CROSS JOIN generate_series(1, 3) AS i CROSS JOIN generate_series(1,3) AS j\n" +"FROM dummy_rast CROSS JOIN generate_series(1, 3) AS i CROSS JOIN " +"generate_series(1,3) AS j\n" "WHERE rid = 2;\n" "\n" " col | row | origval | reclassval | reclassval_include_nodata\n" @@ -13074,8 +13268,8 @@ msgstr "" msgid "" "Create a new raster from the original where band 1,2,3 is converted to " "1BB,4BUI, 4BUI respectively and reclassified. Note this uses the variadic " -"reclassarg argument which can take as input an indefinite" -" number of reclassargs (theoretically as many bands as you have)" +"reclassarg argument which can take as input an indefinite " +"number of reclassargs (theoretically as many bands as you have)" msgstr "" #. Tag: programlisting @@ -13084,15 +13278,19 @@ msgstr "" msgid "" "UPDATE dummy_rast SET reclass_rast = \n" " ST_Reclass(rast,\n" -" ROW(2,'0-87]:1-10, (87-100]:11-15, (101-254]:0-0', '4BUI',NULL)::reclassarg,\n" +" ROW(2,'0-87]:1-10, (87-100]:11-15, (101-254]:0-0', '4BUI',NULL)::" +"reclassarg,\n" " ROW(1,'0-253]:1, 254:0', '1BB', NULL)::reclassarg,\n" -" ROW(3,'0-70]:1, (70-86:2, [86-150):3, [150-255:4', '4BUI', NULL)::reclassarg\n" +" ROW(3,'0-70]:1, (70-86:2, [86-150):3, [150-255:4', '4BUI', NULL)::" +"reclassarg\n" " ) WHERE rid = 2;\n" "\n" -"SELECT i as col, j as row,ST_Value(rast,1,i,j) As ov1, ST_Value(reclass_rast, 1, i, j) As rv1, \n" +"SELECT i as col, j as row,ST_Value(rast,1,i,j) As ov1, " +"ST_Value(reclass_rast, 1, i, j) As rv1, \n" " ST_Value(rast,2,i,j) As ov2, ST_Value(reclass_rast, 2, i, j) As rv2, \n" " ST_Value(rast,3,i,j) As ov3, ST_Value(reclass_rast, 3, i, j) As rv3\n" -"FROM dummy_rast CROSS JOIN generate_series(1, 3) AS i CROSS JOIN generate_series(1,3) AS j\n" +"FROM dummy_rast CROSS JOIN generate_series(1, 3) AS i CROSS JOIN " +"generate_series(1,3) AS j\n" "WHERE rid = 2;\n" "\n" "col | row | ov1 | rv1 | ov2 | rv2 | ov3 | rv3\n" @@ -13131,9 +13329,12 @@ msgid "" "UPDATE wind \n" " set rast_view = ST_AddBand( NULL,\n" " ARRAY[\n" -" ST_Reclass(rast, 1,'0.1-10]:1-10,9-10]:11,(11-33:0'::text, '8BUI'::text,0),\n" -" ST_Reclass(rast,1, '11-33):0-255,[0-32:0,(34-1000:0'::text, '8BUI'::text,0), \n" -" ST_Reclass(rast,1,'0-32]:0,(32-100:100-255'::text, '8BUI'::text,0)\n" +" ST_Reclass(rast, 1,'0.1-10]:1-10,9-10]:11,(11-33:0'::text, " +"'8BUI'::text,0),\n" +" ST_Reclass(rast,1, '11-33):0-255,[0-32:0,(34-1000:0'::text, " +"'8BUI'::text,0), \n" +" ST_Reclass(rast,1,'0-32]:0,(32-100:100-255'::text, '8BUI'::" +"text,0)\n" " ]\n" " );" msgstr "" @@ -13175,8 +13376,8 @@ msgstr "" msgid "" "raster ST_Union " "setof raster rast " -"unionarg[] " -"unionargset" +"unionarg[] unionargset" msgstr "" #. Tag: funcprototype @@ -13223,10 +13424,10 @@ msgstr "" #, no-c-format msgid "" "In order for rasters to be unioned, they most all have the same alignment. " -"Use and for more details and help. One " -"way to fix alignment issues is to use and" -" use the same reference raster for alignment." +"Use and for more details and help. One way to fix " +"alignment issues is to use and use the " +"same reference raster for alignment." msgstr "" #. Tag: para @@ -13277,39 +13478,45 @@ msgstr "" #: reference_raster.xml:7974 reference_raster.xml:7978 #, no-c-format msgid "" -"Examples: Return a multi-band raster that is the union of tiles intersecting" -" geometry" +"Examples: Return a multi-band raster that is the union of tiles intersecting " +"geometry" msgstr "" #. Tag: programlisting #: reference_raster.xml:7975 #, no-c-format msgid "" -"-- this creates a multi band raster collecting all the tiles that intersect a line\n" +"-- this creates a multi band raster collecting all the tiles that intersect " +"a line\n" "-- Note: In 2.0, this would have just returned a single band raster\n" "-- , new union works on all bands by default\n" -"-- this is equivalent to unionarg: ARRAY[ROW(1, 'LAST'), ROW(2, 'LAST'), ROW(3, 'LAST')]::unionarg[]\n" +"-- this is equivalent to unionarg: ARRAY[ROW(1, 'LAST'), ROW(2, 'LAST'), " +"ROW(3, 'LAST')]::unionarg[]\n" "SELECT ST_Union(rast)\n" "FROM aerials.boston\n" -"WHERE ST_Intersects(rast, ST_GeomFromText('LINESTRING(230486 887771, 230500 88772)',26986) );" +"WHERE ST_Intersects(rast, ST_GeomFromText('LINESTRING(230486 887771, 230500 " +"88772)',26986) );" msgstr "" #. Tag: para #: reference_raster.xml:7979 #, no-c-format msgid "" -"Here we use the longer syntax if we only wanted a subset of bands or we want" -" to change order of bands" +"Here we use the longer syntax if we only wanted a subset of bands or we want " +"to change order of bands" msgstr "" #. Tag: programlisting #: reference_raster.xml:7980 #, no-c-format msgid "" -"-- this creates a multi band raster collecting all the tiles that intersect a line\n" -"SELECT ST_Union(rast,ARRAY[ROW(2, 'LAST'), ROW(1, 'LAST'), ROW(3, 'LAST')]::unionarg[])\n" +"-- this creates a multi band raster collecting all the tiles that intersect " +"a line\n" +"SELECT ST_Union(rast,ARRAY[ROW(2, 'LAST'), ROW(1, 'LAST'), ROW(3, 'LAST')]::" +"unionarg[])\n" "FROM aerials.boston\n" -"WHERE ST_Intersects(rast, ST_GeomFromText('LINESTRING(230486 887771, 230500 88772)',26986) );" +"WHERE ST_Intersects(rast, ST_GeomFromText('LINESTRING(230486 887771, 230500 " +"88772)',26986) );" msgstr "" #. Tag: para @@ -13336,25 +13543,24 @@ msgstr "" #: reference_raster.xml:8004 #, no-c-format msgid "" -"Raster processing function that calculates the number of unique pixel values" -" in a neighborhood." +"Raster processing function that calculates the number of unique pixel values " +"in a neighborhood." msgstr "" #. Tag: funcsynopsis #: reference_raster.xml:8008 #, no-c-format msgid "" -" float8 " -"ST_Distinct4ma " -"float8[][] matrix " -"text nodatamode " -"text[] VARIADIC " -"args double" -" precision ST_Distinct4ma " -"double precision[][][] " -"value integer[][] " -"pos text[] " -"VARIADIC userargs " +" float8 ST_Distinct4ma float8[][] matrix text nodatamode text[] VARIADIC args double " +"precision ST_Distinct4ma " +"double precision[][][] value integer[][] pos text[] VARIADIC userargs " msgstr "" #. Tag: para @@ -13371,8 +13577,8 @@ msgstr "" #: reference_raster.xml:8601 #, no-c-format msgid "" -"Variant 1 is a specialized callback function for use as a callback parameter" -" to ." +"Variant 1 is a specialized callback function for use as a callback parameter " +"to ." msgstr "" #. Tag: para @@ -13382,8 +13588,8 @@ msgstr "" #: reference_raster.xml:8605 #, no-c-format msgid "" -"Variant 2 is a specialized callback function for use as a callback parameter" -" to ." +"Variant 2 is a specialized callback function for use as a callback parameter " +"to ." msgstr "" #. Tag: para @@ -13393,8 +13599,8 @@ msgstr "" #: reference_raster.xml:8611 #, no-c-format msgid "" -"Use of Variant 1 is discouraged since has been deprecated as of 2.1.0." +"Use of Variant 1 is discouraged since has been deprecated as of 2.1.0." msgstr "" #. Tag: para @@ -13413,7 +13619,8 @@ msgid "" "SELECT \n" " rid,\n" " st_value(\n" -" st_mapalgebrafctngb(rast, 1, NULL, 1, 1, 'st_distinct4ma(float[][],text,text[])'::regprocedure, 'ignore', NULL), 2, 2\n" +" st_mapalgebrafctngb(rast, 1, NULL, 1, 1, 'st_distinct4ma(float[][]," +"text,text[])'::regprocedure, 'ignore', NULL), 2, 2\n" " ) \n" "FROM dummy_rast \n" "WHERE rid = 2;\n" @@ -13452,11 +13659,11 @@ msgstr "" #: reference_raster.xml:8080 #, no-c-format msgid "" -"double precision ST_InvDistWeight4ma" -" double precision[][][] " -"value integer[][] " -"pos text[] " -"VARIADIC userargs" +"double precision ST_InvDistWeight4ma " +"double precision[][][] value integer[][] pos text[] VARIADIC userargs" msgstr "" #. Tag: para @@ -13474,9 +13681,9 @@ msgid "" "There are two optional parameters that can be passed through " "userargs. The first parameter is the power factor " "(variable k in the equation below) between 0 and 1 used in the Inverse " -"Distance Weighted equation. If not specified, default value is 1. The second" -" parameter is the weight percentage applied only when the value of the pixel" -" of interest is included with the interpolated value from the neighborhood. " +"Distance Weighted equation. If not specified, default value is 1. The second " +"parameter is the weight percentage applied only when the value of the pixel " +"of interest is included with the interpolated value from the neighborhood. " "If not specified and the pixel of interest has a value, that value is " "returned." msgstr "" @@ -13534,13 +13741,12 @@ msgid "" " float8 ST_Max4ma " "float8[][] matrix " "text nodatamode " -"text[] VARIADIC " -"args double" -" precision ST_Max4ma double " -"precision[][][] value " -"integer[][] pos " -"text[] VARIADIC " -"userargs " +"text[] VARIADIC args double precision " +"ST_Max4ma double precision[][]" +"[] value integer[]" +"[] pos text[] VARIADIC userargs " msgstr "" #. Tag: para @@ -13566,7 +13772,8 @@ msgid "" "SELECT \n" " rid,\n" " st_value(\n" -" st_mapalgebrafctngb(rast, 1, NULL, 1, 1, 'st_max4ma(float[][],text,text[])'::regprocedure, 'ignore', NULL), 2, 2\n" +" st_mapalgebrafctngb(rast, 1, NULL, 1, 1, 'st_max4ma(float[][],text," +"text[])'::regprocedure, 'ignore', NULL), 2, 2\n" " ) \n" "FROM dummy_rast \n" "WHERE rid = 2;\n" @@ -13607,13 +13814,12 @@ msgid "" " float8 ST_Mean4ma " "float8[][] matrix " "text nodatamode " -"text[] VARIADIC " -"args double" -" precision ST_Mean4ma double " -"precision[][][] value " -"integer[][] pos " -"text[] VARIADIC " -"userargs " +"text[] VARIADIC args double precision " +"ST_Mean4ma double precision[]" +"[][] value integer[]" +"[] pos text[] VARIADIC userargs " msgstr "" #. Tag: para @@ -13629,7 +13835,8 @@ msgid "" "SELECT \n" " rid,\n" " st_value(\n" -" st_mapalgebrafctngb(rast, 1, '32BF', 1, 1, 'st_mean4ma(float[][],text,text[])'::regprocedure, 'ignore', NULL), 2, 2\n" +" st_mapalgebrafctngb(rast, 1, '32BF', 1, 1, 'st_mean4ma(float[][]," +"text,text[])'::regprocedure, 'ignore', NULL), 2, 2\n" " ) \n" "FROM dummy_rast \n" "WHERE rid = 2;\n" @@ -13646,7 +13853,8 @@ msgid "" "SELECT \n" " rid,\n" " st_value(\n" -" ST_MapAlgebra(rast, 1, 'st_mean4ma(double precision[][][], integer[][], text[])'::regprocedure,'32BF', 'FIRST', NULL, 1, 1)\n" +" ST_MapAlgebra(rast, 1, 'st_mean4ma(double precision[][][], " +"integer[][], text[])'::regprocedure,'32BF', 'FIRST', NULL, 1, 1)\n" " , 2, 2)\n" " FROM dummy_rast \n" " WHERE rid = 2;\n" @@ -13686,13 +13894,12 @@ msgid "" " float8 ST_Min4ma " "float8[][] matrix " "text nodatamode " -"text[] VARIADIC " -"args double" -" precision ST_Min4ma double " -"precision[][][] value " -"integer[][] pos " -"text[] VARIADIC " -"userargs " +"text[] VARIADIC args double precision " +"ST_Min4ma double precision[][]" +"[] value integer[]" +"[] pos text[] VARIADIC userargs " msgstr "" #. Tag: para @@ -13708,7 +13915,8 @@ msgid "" "SELECT \n" " rid,\n" " st_value(\n" -" st_mapalgebrafctngb(rast, 1, NULL, 1, 1, 'st_min4ma(float[][],text,text[])'::regprocedure, 'ignore', NULL), 2, 2\n" +" st_mapalgebrafctngb(rast, 1, NULL, 1, 1, 'st_min4ma(float[][],text," +"text[])'::regprocedure, 'ignore', NULL), 2, 2\n" " ) \n" "FROM dummy_rast \n" "WHERE rid = 2;\n" @@ -13747,10 +13955,10 @@ msgstr "" #, no-c-format msgid "" "double precision ST_MinDist4ma " -"double precision[][][] " -"value integer[][] " -"pos text[] " -"VARIADIC userargs" +"double precision[][][] value integer[][] pos text[] VARIADIC userargs" msgstr "" #. Tag: para @@ -13798,13 +14006,12 @@ msgid "" " float8 ST_Range4ma " "float8[][] matrix " "text nodatamode " -"text[] VARIADIC " -"args double" -" precision ST_Range4ma double" -" precision[][][] value " -"integer[][] pos " -"text[] VARIADIC " -"userargs " +"text[] VARIADIC args double precision " +"ST_Range4ma double precision[]" +"[][] value integer[]" +"[] pos text[] VARIADIC userargs " msgstr "" #. Tag: para @@ -13820,7 +14027,8 @@ msgid "" "SELECT \n" " rid,\n" " st_value(\n" -" st_mapalgebrafctngb(rast, 1, NULL, 1, 1, 'st_range4ma(float[][],text,text[])'::regprocedure, 'ignore', NULL), 2, 2\n" +" st_mapalgebrafctngb(rast, 1, NULL, 1, 1, 'st_range4ma(float[][],text," +"text[])'::regprocedure, 'ignore', NULL), 2, 2\n" " ) \n" "FROM dummy_rast \n" "WHERE rid = 2;\n" @@ -13851,21 +14059,20 @@ msgid "" " float8 ST_StdDev4ma " "float8[][] matrix " "text nodatamode " -"text[] VARIADIC " -"args double" -" precision ST_StdDev4ma " -"double precision[][][] " -"value integer[][] " -"pos text[] " -"VARIADIC userargs " +"text[] VARIADIC args double precision " +"ST_StdDev4ma double " +"precision[][][] value " +"integer[][] pos " +"text[] VARIADIC userargs " msgstr "" #. Tag: para #: reference_raster.xml:8523 #, no-c-format msgid "" -"Calculate the standard deviation of pixel values in a neighborhood of " -"pixels." +"Calculate the standard deviation of pixel values in a neighborhood of pixels." msgstr "" #. Tag: programlisting @@ -13875,7 +14082,8 @@ msgid "" "SELECT \n" " rid,\n" " st_value(\n" -" st_mapalgebrafctngb(rast, 1, '32BF', 1, 1, 'st_stddev4ma(float[][],text,text[])'::regprocedure, 'ignore', NULL), 2, 2\n" +" st_mapalgebrafctngb(rast, 1, '32BF', 1, 1, 'st_stddev4ma(float[][]," +"text,text[])'::regprocedure, 'ignore', NULL), 2, 2\n" " ) \n" "FROM dummy_rast \n" "WHERE rid = 2;\n" @@ -13906,13 +14114,12 @@ msgid "" " float8 ST_Sum4ma " "float8[][] matrix " "text nodatamode " -"text[] VARIADIC " -"args double" -" precision ST_Sum4ma double " -"precision[][][] value " -"integer[][] pos " -"text[] VARIADIC " -"userargs " +"text[] VARIADIC args double precision " +"ST_Sum4ma double precision[][]" +"[] value integer[]" +"[] pos text[] VARIADIC userargs " msgstr "" #. Tag: para @@ -13928,7 +14135,8 @@ msgid "" "SELECT \n" " rid,\n" " st_value(\n" -" st_mapalgebrafctngb(rast, 1, '32BF', 1, 1, 'st_sum4ma(float[][],text,text[])'::regprocedure, 'ignore', NULL), 2, 2\n" +" st_mapalgebrafctngb(rast, 1, '32BF', 1, 1, 'st_sum4ma(float[][],text," +"text[])'::regprocedure, 'ignore', NULL), 2, 2\n" " ) \n" "FROM dummy_rast \n" "WHERE rid = 2;\n" @@ -13974,23 +14182,20 @@ msgstr "" msgid "" " raster ST_Aspect " "raster rast " -"integer " -"band=1 text" -" pixeltype=32BF text " -"units=DEGREES boolean " +"integer band=1 text " +"pixeltype=32BF text units=DEGREES " +"boolean " "interpolate_nodata=FALSE " " raster ST_Aspect " "raster rast " "integer band " -"raster " -"customextent text " -"pixeltype=32BF text " -"units=DEGREES boolean " +"raster customextent text " +"pixeltype=32BF text units=DEGREES " +"boolean " "interpolate_nodata=FALSE " msgstr "" @@ -14037,11 +14242,11 @@ msgstr "" #, no-c-format msgid "" "For more information about Slope, Aspect and Hillshade, please refer to " -"ESRI" -" - How hillshade works and ERDAS" -" Field Guide - Aspect Images." +"ESRI - How hillshade works and " +"ERDAS Field Guide - Aspect Images." msgstr "" #. Tag: para @@ -14056,8 +14261,8 @@ msgstr "" #: reference_raster.xml:8704 reference_raster.xml:8928 #, no-c-format msgid "" -"Changed: 2.1.0 In prior versions, return values were in radians. Now, return" -" values default to degrees" +"Changed: 2.1.0 In prior versions, return values were in radians. Now, return " +"values default to degrees" msgstr "" #. Tag: programlisting @@ -14066,7 +14271,8 @@ msgstr "" msgid "" "WITH foo AS (\n" " SELECT ST_SetValues(\n" -" ST_AddBand(ST_MakeEmptyRaster(5, 5, 0, 0, 1, -1, 0, 0, 0), 1, '32BF', 0, -9999),\n" +" ST_AddBand(ST_MakeEmptyRaster(5, 5, 0, 0, 1, -1, 0, 0, 0), " +"1, '32BF', 0, -9999),\n" " 1, 1, 1, ARRAY[\n" " [1, 1, 1, 1, 1],\n" " [1, 2, 2, 2, 1],\n" @@ -14084,7 +14290,9 @@ msgid "" " \n" "------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\n" "----------------------------------\n" -" (1,\"{{315,341.565063476562,0,18.4349479675293,45},{288.434936523438,315,0,45,71.5650482177734},{270,270,-1,90,90},{251.565048217773,225,180,135,108.434951782227},{225,198.43495178\n" +" (1,\"{{315,341.565063476562,0,18.4349479675293,45}," +"{288.434936523438,315,0,45,71.5650482177734},{270,270,-1,90,90}," +"{251.565048217773,225,180,135,108.434951782227},{225,198.43495178\n" "2227,180,161.565048217773,135}}\")\n" "(1 row)" msgstr "" @@ -14106,7 +14314,8 @@ msgid "" " SELECT ST_Tile(\n" " ST_SetValues(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(6, 6, 0, 0, 1, -1, 0, 0, 0),\n" +" ST_MakeEmptyRaster(6, 6, 0, 0, 1, -1, 0, 0, " +"0),\n" " 1, '32BF', 0, -9999\n" " ),\n" " 1, 1, 1, ARRAY[\n" @@ -14159,35 +14368,29 @@ msgstr "" msgid "" " raster ST_HillShade " "raster rast " -"integer " -"band=1 text" -" pixeltype=32BF double precision " -"azimuth=315 double precision " -"altitude=45 double precision " -"max_bright=255 double precision " -"scale=1.0 boolean " -"interpolate_nodata=FALSE " -" raster ST_HillShade " -"raster rast " -"integer band " -"raster " -"customextent text " -"pixeltype=32BF double precision " -"azimuth=315 double precision " -"altitude=45 double precision " -"max_bright=255 double precision " -"scale=1.0 boolean " +"integer band=1 text " +"pixeltype=32BF double precision azimuth=315 double precision " +"altitude=45 double precision max_bright=255 double precision " +"scale=1.0 boolean interpolate_nodata=FALSE raster " +"ST_HillShade raster " +"rast integer " +"band raster " +"customextent text pixeltype=32BF " +"double precision " +"azimuth=315 double precision altitude=45 double precision " +"max_bright=255 double precision scale=1.0 boolean " "interpolate_nodata=FALSE " msgstr "" @@ -14238,18 +14441,17 @@ msgstr "" #, no-c-format msgid "" "If interpolate_nodata is TRUE, values for NODATA pixels " -"from the input raster will be interpolated using before computing the hillshade " -"illumination." +"from the input raster will be interpolated using before computing the hillshade illumination." msgstr "" #. Tag: para #: reference_raster.xml:8793 #, no-c-format msgid "" -"For more information about Hillshade, please refer to How" -" hillshade works." +"For more information about Hillshade, please refer to How hillshade works." msgstr "" #. Tag: para @@ -14266,7 +14468,8 @@ msgstr "" msgid "" "WITH foo AS (\n" " SELECT ST_SetValues(\n" -" ST_AddBand(ST_MakeEmptyRaster(5, 5, 0, 0, 1, -1, 0, 0, 0), 1, '32BF', 0, -9999),\n" +" ST_AddBand(ST_MakeEmptyRaster(5, 5, 0, 0, 1, -1, 0, 0, 0), " +"1, '32BF', 0, -9999),\n" " 1, 1, 1, ARRAY[\n" " [1, 1, 1, 1, 1],\n" " [1, 2, 2, 2, 1],\n" @@ -14284,7 +14487,10 @@ msgid "" " \n" "------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\n" "-----------------------------------------------------------------------\n" -" (1,\"{{NULL,NULL,NULL,NULL,NULL},{NULL,251.32763671875,220.749786376953,147.224319458008,NULL},{NULL,220.749786376953,180.312225341797,67.7497863769531,NULL},{NULL,147.224319458008\n" +" (1,\"{{NULL,NULL,NULL,NULL,NULL}," +"{NULL,251.32763671875,220.749786376953,147.224319458008,NULL}," +"{NULL,220.749786376953,180.312225341797,67.7497863769531,NULL}," +"{NULL,147.224319458008\n" ",67.7497863769531,43.1210060119629,NULL},{NULL,NULL,NULL,NULL,NULL}}\")\n" "(1 row)" msgstr "" @@ -14297,7 +14503,8 @@ msgid "" " SELECT ST_Tile(\n" " ST_SetValues(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(6, 6, 0, 0, 1, -1, 0, 0, 0),\n" +" ST_MakeEmptyRaster(6, 6, 0, 0, 1, -1, 0, 0, " +"0),\n" " 1, '32BF', 0, -9999\n" " ),\n" " 1, 1, 1, ARRAY[\n" @@ -14349,11 +14556,10 @@ msgid "" "raster ST_Roughness " "raster rast " "integer nband " -"raster " -"customextent text pixeltype=\"32BF\" " -" boolean " -"interpolate_nodata=FALSE " +"raster customextent text pixeltype=" +"\"32BF\" boolean interpolate_nodata=FALSE " msgstr "" #. Tag: para @@ -14400,29 +14606,24 @@ msgstr "" msgid "" " raster ST_Slope " "raster rast " -"integer " -"nband=1 text " -"pixeltype=32BF text " -"units=DEGREES double precision " -"scale=1.0 boolean " -"interpolate_nodata=FALSE " -" raster ST_Slope " -"raster rast " -"integer nband " -"raster " -"customextent text " -"pixeltype=32BF text " -"units=DEGREES double precision " -"scale=1.0 boolean " -"interpolate_nodata=FALSE " +"integer nband=1 text " +"pixeltype=32BF text units=DEGREES " +"double precision " +"scale=1.0 boolean interpolate_nodata=FALSE raster " +"ST_Slope raster " +"rast integer " +"nband raster " +"customextent text pixeltype=32BF " +"text units=DEGREES double precision scale=1.0 boolean interpolate_nodata=FALSE " msgstr "" #. Tag: para @@ -14446,8 +14647,8 @@ msgstr "" #, no-c-format msgid "" "If interpolate_nodata is TRUE, values for NODATA pixels " -"from the input raster will be interpolated using before computing the surface slope." +"from the input raster will be interpolated using before computing the surface slope." msgstr "" #. Tag: para @@ -14455,20 +14656,20 @@ msgstr "" #, no-c-format msgid "" "For more information about Slope, Aspect and Hillshade, please refer to " -"ESRI" -" - How hillshade works and ERDAS" -" Field Guide - Slope Images." +"ESRI - How hillshade works and " +"ERDAS " +"Field Guide - Slope Images." msgstr "" #. Tag: para #: reference_raster.xml:8927 #, no-c-format msgid "" -"Enhanced: 2.1.0 Uses ST_MapAlgebra() and added optional " -"units, scale, " -"interpolate_nodata function parameters" +"Enhanced: 2.1.0 Uses ST_MapAlgebra() and added optional units, scale, interpolate_nodata " +"function parameters" msgstr "" #. Tag: programlisting @@ -14477,7 +14678,8 @@ msgstr "" msgid "" "WITH foo AS (\n" " SELECT ST_SetValues(\n" -" ST_AddBand(ST_MakeEmptyRaster(5, 5, 0, 0, 1, -1, 0, 0, 0), 1, '32BF', 0, -9999),\n" +" ST_AddBand(ST_MakeEmptyRaster(5, 5, 0, 0, 1, -1, 0, 0, 0), " +"1, '32BF', 0, -9999),\n" " 1, 1, 1, ARRAY[\n" " [1, 1, 1, 1, 1],\n" " [1, 2, 2, 2, 1],\n" @@ -14496,8 +14698,12 @@ msgid "" "------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\n" "------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\n" "---------------------------------------------------------------------\n" -" (1,\"{{10.0249881744385,21.5681285858154,26.5650520324707,21.5681285858154,10.0249881744385},{21.5681285858154,35.2643890380859,36.8698959350586,35.2643890380859,21.5681285858154},\n" -"{26.5650520324707,36.8698959350586,0,36.8698959350586,26.5650520324707},{21.5681285858154,35.2643890380859,36.8698959350586,35.2643890380859,21.5681285858154},{10.0249881744385,21.\n" +" (1," +"\"{{10.0249881744385,21.5681285858154,26.5650520324707,21.5681285858154,10.0249881744385}," +"{21.5681285858154,35.2643890380859,36.8698959350586,35.2643890380859,21.5681285858154},\n" +"{26.5650520324707,36.8698959350586,0,36.8698959350586,26.5650520324707}," +"{21.5681285858154,35.2643890380859,36.8698959350586,35.2643890380859,21.5681285858154}," +"{10.0249881744385,21.\n" "5681285858154,26.5650520324707,21.5681285858154,10.0249881744385}}\")\n" "(1 row)" msgstr "" @@ -14510,7 +14716,8 @@ msgid "" " SELECT ST_Tile(\n" " ST_SetValues(\n" " ST_AddBand(\n" -" ST_MakeEmptyRaster(6, 6, 0, 0, 1, -1, 0, 0, 0),\n" +" ST_MakeEmptyRaster(6, 6, 0, 0, 1, -1, 0, 0, " +"0),\n" " 1, '32BF', 0, -9999\n" " ),\n" " 1, 1, 1, ARRAY[\n" @@ -14559,12 +14766,12 @@ msgstr "" #: reference_raster.xml:8966 #, no-c-format msgid "" -"raster ST_TPI raster" -" rast integer " -" nband raster " -" customextent text pixeltype=\"32BF\" " -" boolean " +"raster ST_TPI raster " +" rast integer nband raster " +"customextent text pixeltype=\"32BF\" " +"boolean " "interpolate_nodata=FALSE " msgstr "" @@ -14607,12 +14814,12 @@ msgstr "" #: reference_raster.xml:9014 #, no-c-format msgid "" -"raster ST_TRI raster" -" rast integer " -" nband raster " -" customextent text pixeltype=\"32BF\" " -" boolean " +"raster ST_TRI raster " +" rast integer nband raster " +"customextent text pixeltype=\"32BF\" " +"boolean " "interpolate_nodata=FALSE " msgstr "" @@ -14620,9 +14827,9 @@ msgstr "" #: reference_raster.xml:9028 #, no-c-format msgid "" -"Terrain Ruggedness Index is calculated by comparing a central pixel with its" -" neighbors, taking the absolute values of the differences, and averaging the" -" result." +"Terrain Ruggedness Index is calculated by comparing a central pixel with its " +"neighbors, taking the absolute values of the differences, and averaging the " +"result." msgstr "" #. Tag: para @@ -14656,8 +14863,8 @@ msgstr "" #: reference_raster.xml:9070 #, no-c-format msgid "" -"box3d Box3D raster " -" rast" +"box3d Box3D raster rast" msgstr "" #. Tag: para @@ -14671,8 +14878,8 @@ msgstr "" #, no-c-format msgid "" "The polygon is defined by the corner points of the bounding box " -"((MINX, MINY), " -"(MAXX, MAXY))" +"((MINX, MINY), (MAXX, MAXY))" msgstr "" #. Tag: para @@ -14728,8 +14935,8 @@ msgstr "" msgid "" "Return the convex hull geometry of the raster including the NoDataBandValue " "band pixels. For regular shaped and non-skewed rasters, this gives more or " -"less the same result as ST_Envelope so only useful for irregularly shaped or" -" skewed rasters." +"less the same result as ST_Envelope so only useful for irregularly shaped or " +"skewed rasters." msgstr "" #. Tag: para @@ -14745,9 +14952,9 @@ msgstr "" #: reference_raster.xml:9133 #, no-c-format msgid "" -"Refer to PostGIS" -" Raster Specification for a diagram of this." +"Refer to PostGIS Raster Specification for a diagram " +"of this." msgstr "" #. Tag: programlisting @@ -14759,9 +14966,12 @@ msgid "" " ST_AsText(ST_Envelope(rast)) As env\n" "FROM dummy_rast WHERE rid=1;\n" "\n" -" convhull | env\n" -"--------------------------------------------------------+------------------------------------\n" -" POLYGON((0.5 0.5,20.5 0.5,20.5 60.5,0.5 60.5,0.5 0.5)) | POLYGON((0 0,20 0,20 60,0 60,0 0))" +" convhull | " +"env\n" +"--------------------------------------------------------" +"+------------------------------------\n" +" POLYGON((0.5 0.5,20.5 0.5,20.5 60.5,0.5 60.5,0.5 0.5)) | POLYGON((0 0,20 " +"0,20 60,0 60,0 0))" msgstr "" #. Tag: programlisting @@ -14775,17 +14985,20 @@ msgid "" "FROM (SELECT ST_SetRotation(rast, 0.1, 0.1) As rast \n" " FROM dummy_rast WHERE rid=1) As foo;\n" " \n" -" convhull | env\n" -"--------------------------------------------------------+------------------------------------\n" -" POLYGON((0.5 0.5,20.5 1.5,22.5 61.5,2.5 60.5,0.5 0.5)) | POLYGON((0 0,22 0,22 61,0 61,0 0))" +" convhull | " +"env\n" +"--------------------------------------------------------" +"+------------------------------------\n" +" POLYGON((0.5 0.5,20.5 1.5,22.5 61.5,2.5 60.5,0.5 0.5)) | POLYGON((0 0,22 " +"0,22 61,0 61,0 0))" msgstr "" #. Tag: para #: reference_raster.xml:9141 #, no-c-format msgid "" -", , , " +", , , " msgstr "" #. Tag: refname @@ -14808,9 +15021,8 @@ msgstr "" msgid "" "setof geomval ST_DumpAsPolygons " "raster rast " -"integer " -"band_num=1 boolean " +"integer band_num=1 boolean " "exclude_nodata_value=TRUE" msgstr "" @@ -14820,8 +15032,8 @@ msgstr "" msgid "" "This is a set-returning function (SRF). It returns a set of geomval rows, " "formed by a geometry (geom) and a pixel band value (val). Each polygon is " -"the union of all pixels for that band that have the same pixel value denoted" -" by val." +"the union of all pixels for that band that have the same pixel value denoted " +"by val." msgstr "" #. Tag: para @@ -14829,8 +15041,8 @@ msgstr "" #, no-c-format msgid "" "ST_DumpAsPolygon is useful for polygonizing rasters. It is the reverse of a " -"GROUP BY in that it creates new rows. For example it can be used to expand a" -" single raster into multiple POLYGONS/MULTIPOLYGONS." +"GROUP BY in that it creates new rows. For example it can be used to expand a " +"single raster into multiple POLYGONS/MULTIPOLYGONS." msgstr "" #. Tag: para @@ -14851,16 +15063,16 @@ msgstr "" #: reference_raster.xml:9179 #, no-c-format msgid "" -"If you only care about count of pixels with a given value in a raster, it is" -" faster to use ." +"If you only care about count of pixels with a given value in a raster, it is " +"faster to use ." msgstr "" #. Tag: para #: reference_raster.xml:9181 #, no-c-format msgid "" -"This is different than ST_PixelAsPolygons where one geometry is returned for" -" each pixel regardless of pixel value." +"This is different than ST_PixelAsPolygons where one geometry is returned for " +"each pixel regardless of pixel value." msgstr "" #. Tag: programlisting @@ -14877,14 +15089,19 @@ msgid "" "ORDER BY val;\n" "\n" " val | geomwkt\n" -"-----+--------------------------------------------------------------------------\n" -" 249 | POLYGON((3427927.95 5793243.95,3427927.95 5793243.85,3427928 5793243.85,\n" +"-----" +"+--------------------------------------------------------------------------\n" +" 249 | POLYGON((3427927.95 5793243.95,3427927.95 5793243.85,3427928 " +"5793243.85,\n" " 3427928 5793243.95,3427927.95 5793243.95))\n" -" 250 | POLYGON((3427927.75 5793243.9,3427927.75 5793243.85,3427927.8 5793243.85,\n" +" 250 | POLYGON((3427927.75 5793243.9,3427927.75 5793243.85,3427927.8 " +"5793243.85,\n" " 3427927.8 5793243.9,3427927.75 5793243.9))\n" -" 250 | POLYGON((3427927.8 5793243.8,3427927.8 5793243.75,3427927.85 5793243.75,\n" +" 250 | POLYGON((3427927.8 5793243.8,3427927.8 5793243.75,3427927.85 " +"5793243.75,\n" " 3427927.85 5793243.8, 3427927.8 5793243.8))\n" -" 251 | POLYGON((3427927.75 5793243.85,3427927.75 5793243.8,3427927.8 5793243.8,\n" +" 251 | POLYGON((3427927.75 5793243.85,3427927.75 5793243.8,3427927.8 " +"5793243.8,\n" " 3427927.8 5793243.85,3427927.75 5793243.85))" msgstr "" @@ -14930,10 +15147,9 @@ msgstr "" #, no-c-format msgid "" "The polygon is defined by the corner points of the bounding box " -"((MINX, MINY), " -"(MINX, MAXY), " -"(MAXX, MAXY), " -"(MAXX, MINY), " +"((MINX, MINY), (MINX, MAXY), (MAXX, MAXY), (MAXX, MINY), " "(MINX, MINY))" msgstr "" @@ -14975,8 +15191,8 @@ msgstr "" msgid "" "geometry ST_MinConvexHull " "raster rast " -"integer " -"nband=NULL" +"integer nband=NULL" msgstr "" #. Tag: para @@ -14995,7 +15211,8 @@ msgid "" " SELECT\n" " ST_SetValues(\n" " ST_SetValues(\n" -" ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(9, 9, 0, 0, 1, -1, 0, 0, 0), 1, '8BUI', 0, 0), 2, '8BUI', 1, 0),\n" +" ST_AddBand(ST_AddBand(ST_MakeEmptyRaster(9, " +"9, 0, 0, 1, -1, 0, 0, 0), 1, '8BUI', 0, 0), 2, '8BUI', 1, 0),\n" " 1, 1, 1,\n" " ARRAY[\n" " [0, 0, 0, 0, 0, 0, 0, 0, 0],\n" @@ -15030,9 +15247,14 @@ msgid "" " ST_AsText(ST_MinConvexHull(rast, 2)) AS mhull_2\n" "FROM foo\n" "\n" -" hull | mhull | mhull_1 | mhull_2 \n" -"----------------------------------+-------------------------------------+-------------------------------------+-------------------------------------\n" -" POLYGON((0 0,9 0,9 -9,0 -9,0 0)) | POLYGON((0 -3,9 -3,9 -9,0 -9,0 -3)) | POLYGON((3 -3,9 -3,9 -6,3 -6,3 -3)) | POLYGON((0 -3,6 -3,6 -9,0 -9,0 -3))" +" hull | mhull " +"| mhull_1 | " +"mhull_2 \n" +"----------------------------------+-------------------------------------" +"+-------------------------------------" +"+-------------------------------------\n" +" POLYGON((0 0,9 0,9 -9,0 -9,0 0)) | POLYGON((0 -3,9 -3,9 -9,0 -9,0 -3)) | " +"POLYGON((3 -3,9 -3,9 -6,3 -6,3 -3)) | POLYGON((0 -3,6 -3,6 -9,0 -9,0 -3))" msgstr "" #. Tag: para @@ -15064,8 +15286,8 @@ msgstr "" msgid "" "geometry ST_Polygon " "raster rast " -"integer " -"band_num=1" +"integer band_num=1" msgstr "" #. Tag: para @@ -15094,14 +15316,16 @@ msgstr "" #: reference_raster.xml:9317 #, no-c-format msgid "" -"-- by default no data band value is 0 or not set, so polygon will return a square polygon \n" +"-- by default no data band value is 0 or not set, so polygon will return a " +"square polygon \n" "SELECT ST_AsText(ST_Polygon(rast)) As geomwkt\n" "FROM dummy_rast\n" "WHERE rid = 2;\n" "\n" "geomwkt\n" "--------------------------------------------\n" -"MULTIPOLYGON(((3427927.75 5793244,3427928 5793244,3427928 5793243.75,3427927.75 5793243.75,3427927.75 5793244)))\n" +"MULTIPOLYGON(((3427927.75 5793244,3427928 5793244,3427928 " +"5793243.75,3427927.75 5793243.75,3427927.75 5793244)))\n" " \n" " \n" "-- now we change the no data value of first band\n" @@ -15117,7 +15341,16 @@ msgid "" "\n" "geomwkt\n" "---------------------------------------------------------\n" -"MULTIPOLYGON(((3427927.9 5793243.95,3427927.85 5793243.95,3427927.85 5793244,3427927.9 5793244,3427927.9 5793243.95)),((3427928 5793243.85,3427928 5793243.8,3427927.95 5793243.8,3427927.95 5793243.85,3427927.9 5793243.85,3427927.9 5793243.9,3427927.9 5793243.95,3427927.95 5793243.95,3427928 5793243.95,3427928 5793243.85)),((3427927.8 5793243.75,3427927.75 5793243.75,3427927.75 5793243.8,3427927.75 5793243.85,3427927.75 5793243.9,3427927.75 5793244,3427927.8 5793244,3427927.8 5793243.9,3427927.8 5793243.85,3427927.85 5793243.85,3427927.85 5793243.8,3427927.85 5793243.75,3427927.8 5793243.75)))\n" +"MULTIPOLYGON(((3427927.9 5793243.95,3427927.85 5793243.95,3427927.85 " +"5793244,3427927.9 5793244,3427927.9 5793243.95)),((3427928 " +"5793243.85,3427928 5793243.8,3427927.95 5793243.8,3427927.95 " +"5793243.85,3427927.9 5793243.85,3427927.9 5793243.9,3427927.9 " +"5793243.95,3427927.95 5793243.95,3427928 5793243.95,3427928 5793243.85))," +"((3427927.8 5793243.75,3427927.75 5793243.75,3427927.75 5793243.8,3427927.75 " +"5793243.85,3427927.75 5793243.9,3427927.75 5793244,3427927.8 " +"5793244,3427927.8 5793243.9,3427927.8 5793243.85,3427927.85 " +"5793243.85,3427927.85 5793243.8,3427927.85 5793243.75,3427927.8 " +"5793243.75)))\n" "\n" "-- Or if you want the no data value different for just one time\n" "\n" @@ -15131,7 +15364,13 @@ msgid "" "\n" "geomwkt\n" "---------------------------------\n" -"MULTIPOLYGON(((3427928 5793243.85,3427928 5793243.8,3427928 5793243.75,3427927.85 5793243.75,3427927.8 5793243.75,3427927.8 5793243.8,3427927.75 5793243.8,3427927.75 5793243.85,3427927.75 5793243.9,3427927.75 5793244,3427927.8 5793244,3427927.85 5793244,3427927.9 5793244,3427928 5793244,3427928 5793243.95,3427928 5793243.85),(3427927.9 5793243.9,3427927.9 5793243.85,3427927.95 5793243.85,3427927.95 5793243.9,3427927.9 5793243.9)))" +"MULTIPOLYGON(((3427928 5793243.85,3427928 5793243.8,3427928 " +"5793243.75,3427927.85 5793243.75,3427927.8 5793243.75,3427927.8 " +"5793243.8,3427927.75 5793243.8,3427927.75 5793243.85,3427927.75 " +"5793243.9,3427927.75 5793244,3427927.8 5793244,3427927.85 5793244,3427927.9 " +"5793244,3427928 5793244,3427928 5793243.95,3427928 5793243.85),(3427927.9 " +"5793243.9,3427927.9 5793243.85,3427927.95 5793243.85,3427927.95 " +"5793243.9,3427927.9 5793243.9)))" msgstr "" #. Tag: title @@ -15160,14 +15399,14 @@ msgstr "" msgid "" " boolean && " " raster A " -" raster B " -" boolean " -"&& raster " -"A geometry " -"B " -"boolean && " -"geometry B " -"raster A " +" raster B boolean && raster A " +" geometry B boolean &" +"& geometry B raster A " msgstr "" #. Tag: para @@ -15193,7 +15432,8 @@ msgstr "" #: reference_raster.xml:9396 #, no-c-format msgid "" -"SELECT A.rid As a_rid, B.rid As b_rid, A.rast && B.rast As intersect\n" +"SELECT A.rid As a_rid, B.rid As b_rid, A.rast && B.rast As " +"intersect\n" " FROM dummy_rast AS A CROSS JOIN dummy_rast AS B LIMIT 3;\n" "\n" " a_rid | b_rid | intersect\n" @@ -15229,9 +15469,9 @@ msgstr "" #: reference_raster.xml:9430 #, no-c-format msgid "" -"The &< operator returns TRUE if" -" the bounding box of raster A overlaps or is to the left of the bounding box" -" of raster B, or more accurately, overlaps or is NOT to the right of the " +"The &< operator returns TRUE if " +"the bounding box of raster A overlaps or is to the left of the bounding box " +"of raster B, or more accurately, overlaps or is NOT to the right of the " "bounding box of raster B." msgstr "" @@ -15289,9 +15529,9 @@ msgstr "" #: reference_raster.xml:9475 #, no-c-format msgid "" -"The &> operator returns TRUE if" -" the bounding box of raster A overlaps or is to the right of the bounding " -"box of raster B, or more accurately, overlaps or is NOT to the left of the " +"The &> operator returns TRUE if " +"the bounding box of raster A overlaps or is to the right of the bounding box " +"of raster B, or more accurately, overlaps or is NOT to the left of the " "bounding box of raster B." msgstr "" @@ -15325,8 +15565,8 @@ msgstr "" #: reference_raster.xml:9494 #, no-c-format msgid "" -"Returns TRUE if A's bounding box is the same as B's. Uses" -" double precision bounding box." +"Returns TRUE if A's bounding box is the same as B's. Uses " +"double precision bounding box." msgstr "" #. Tag: funcprototype @@ -15342,8 +15582,8 @@ msgstr "" #: reference_raster.xml:9520 #, no-c-format msgid "" -"The = operator returns TRUE if the" -" bounding box of raster A is the same as the bounding box of raster B. " +"The = operator returns TRUE if the " +"bounding box of raster A is the same as the bounding box of raster B. " "PostgreSQL uses the =, <, and > operators defined for rasters to " "perform internal orderings and comparison of rasters (ie. in a GROUP BY or " "ORDER BY clause)." @@ -15376,14 +15616,14 @@ msgstr "" #: reference_raster.xml:9546 #, no-c-format msgid "" -" boolean @ " -" raster A " +" boolean @ " +"raster A " "raster B " -" boolean @ " -" geometry A " +" boolean @ " +"geometry A " "raster B " -" boolean @ " -" raster B " +" boolean @ " +"raster B " "geometry A " msgstr "" @@ -15392,8 +15632,8 @@ msgstr "" #, no-c-format msgid "" "The @ operator returns TRUE if the " -"bounding box of raster/geometry A is contained by bounding box of " -"raster/geometr B." +"bounding box of raster/geometry A is contained by bounding box of raster/" +"geometr B." msgstr "" #. Tag: para @@ -15423,17 +15663,16 @@ msgstr "" #. Tag: refpurpose #: reference_raster.xml:9610 #, no-c-format -msgid "" -"Returns TRUE if A's bounding box is the same as B's." +msgid "Returns TRUE if A's bounding box is the same as B's." msgstr "" #. Tag: funcprototype #: reference_raster.xml:9615 #, no-c-format msgid "" -"boolean ~= raster " -" A raster " -" B " +"boolean ~= raster A raster " +"B " msgstr "" #. Tag: para @@ -15485,14 +15724,14 @@ msgstr "" #: reference_raster.xml:9666 #, no-c-format msgid "" -" boolean ~ " -" raster A " +" boolean ~ " +"raster A " "raster B " -" boolean ~ " -" geometry A " +" boolean ~ " +"geometry A " "raster B " -" boolean ~ " -" raster B " +" boolean ~ " +"raster B " "geometry A " msgstr "" @@ -15501,8 +15740,8 @@ msgstr "" #, no-c-format msgid "" "The ~ operator returns TRUE if the " -"bounding box of raster/geometry A is contains bounding box of raster/geometr" -" B." +"bounding box of raster/geometry A is contains bounding box of raster/geometr " +"B." msgstr "" #. Tag: title @@ -15521,8 +15760,8 @@ msgstr "" #: reference_raster.xml:9732 #, no-c-format msgid "" -"Return true if no points of raster rastB lie in the exterior of raster rastA" -" and at least one point of the interior of rastB lies in the interior of " +"Return true if no points of raster rastB lie in the exterior of raster rastA " +"and at least one point of the interior of rastB lies in the interior of " "rastA." msgstr "" @@ -15534,11 +15773,11 @@ msgid "" " raster rastA " " integer nbandA " " raster rastB " -" integer nbandB " -" boolean " -"ST_Contains raster " -"rastA raster " -"rastB " +" integer nbandB boolean ST_Contains raster rastA raster rastB " msgstr "" #. Tag: para @@ -15549,8 +15788,8 @@ msgid "" "exterior of rastA and at least one point of the interior of rastB lies in " "the interior of rastA. If the band number is not provided (or set to NULL), " "only the convex hull of the raster is considered in the test. If the band " -"number is provided, only those pixels with value (not NODATA) are considered" -" in the test." +"number is provided, only those pixels with value (not NODATA) are considered " +"in the test." msgstr "" #. Tag: para @@ -15586,7 +15825,8 @@ msgstr "" #, no-c-format msgid "" "-- specified band numbers\n" -"SELECT r1.rid, r2.rid, ST_Contains(r1.rast, 1, r2.rast, 1) FROM dummy_rast r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 1;\n" +"SELECT r1.rid, r2.rid, ST_Contains(r1.rast, 1, r2.rast, 1) FROM dummy_rast " +"r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 1;\n" "\n" "NOTICE: The first raster provided has no bands\n" " rid | rid | st_contains \n" @@ -15600,7 +15840,8 @@ msgstr "" #, no-c-format msgid "" "-- no band numbers specified\n" -"SELECT r1.rid, r2.rid, ST_Contains(r1.rast, r2.rast) FROM dummy_rast r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 1;\n" +"SELECT r1.rid, r2.rid, ST_Contains(r1.rast, r2.rast) FROM dummy_rast r1 " +"CROSS JOIN dummy_rast r2 WHERE r1.rid = 1;\n" " rid | rid | st_contains \n" "-----+-----+-------------\n" " 1 | 1 | t\n" @@ -15631,16 +15872,15 @@ msgstr "" #: reference_raster.xml:9827 #, no-c-format msgid "" -" boolean " -"ST_ContainsProperly raster " -" rastA integer " -" nbandA raster " -" rastB integer " -" nbandB " -" boolean " -"ST_ContainsProperly raster " -" rastA raster " -" rastB " +" boolean ST_ContainsProperly raster rastA integer nbandA raster rastB integer nbandB boolean " +"ST_ContainsProperly raster rastA raster rastB " msgstr "" #. Tag: para @@ -15673,7 +15913,8 @@ msgstr "" #: reference_raster.xml:9892 #, no-c-format msgid "" -"SELECT r1.rid, r2.rid, ST_ContainsProperly(r1.rast, 1, r2.rast, 1) FROM dummy_rast r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" +"SELECT r1.rid, r2.rid, ST_ContainsProperly(r1.rast, 1, r2.rast, 1) FROM " +"dummy_rast r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" "\n" " rid | rid | st_containsproperly \n" "-----+-----+---------------------\n" @@ -15707,11 +15948,11 @@ msgid "" " raster rastA " " integer nbandA " " raster rastB " -" integer nbandB " -" boolean " -"ST_Covers raster " -"rastA raster " -"rastB " +" integer nbandB boolean ST_Covers raster rastA raster rastB " msgstr "" #. Tag: para @@ -15719,10 +15960,10 @@ msgstr "" #, no-c-format msgid "" "Raster rastA covers rastB if and only if no points of rastB lie in the " -"exterior of rastA. If the band number is not provided (or set to NULL), only" -" the convex hull of the raster is considered in the test. If the band number" -" is provided, only those pixels with value (not NODATA) are considered in " -"the test." +"exterior of rastA. If the band number is not provided (or set to NULL), only " +"the convex hull of the raster is considered in the test. If the band number " +"is provided, only those pixels with value (not NODATA) are considered in the " +"test." msgstr "" #. Tag: para @@ -15738,7 +15979,8 @@ msgstr "" #: reference_raster.xml:9973 #, no-c-format msgid "" -"SELECT r1.rid, r2.rid, ST_Covers(r1.rast, 1, r2.rast, 1) FROM dummy_rast r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" +"SELECT r1.rid, r2.rid, ST_Covers(r1.rast, 1, r2.rast, 1) FROM dummy_rast r1 " +"CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" "\n" " rid | rid | st_covers \n" "-----+-----+-----------\n" @@ -15768,15 +16010,15 @@ msgstr "" #: reference_raster.xml:9993 #, no-c-format msgid "" -" boolean ST_CoveredBy" -" raster rastA " +" boolean ST_CoveredBy " +" raster rastA " " integer nbandA " " raster rastB " -" integer nbandB " -" boolean " -"ST_CoveredBy raster " -"rastA raster " -"rastB " +" integer nbandB boolean ST_CoveredBy raster rastA raster rastB " msgstr "" #. Tag: para @@ -15786,8 +16028,8 @@ msgid "" "Raster rastA is covered by rastB if and only if no points of rastA lie in " "the exterior of rastB. If the band number is not provided (or set to NULL), " "only the convex hull of the raster is considered in the test. If the band " -"number is provided, only those pixels with value (not NODATA) are considered" -" in the test." +"number is provided, only those pixels with value (not NODATA) are considered " +"in the test." msgstr "" #. Tag: para @@ -15803,7 +16045,8 @@ msgstr "" #: reference_raster.xml:10054 #, no-c-format msgid "" -"SELECT r1.rid, r2.rid, ST_CoveredBy(r1.rast, 1, r2.rast, 1) FROM dummy_rast r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" +"SELECT r1.rid, r2.rid, ST_CoveredBy(r1.rast, 1, r2.rast, 1) FROM dummy_rast " +"r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" "\n" " rid | rid | st_coveredby \n" "-----+-----+--------------\n" @@ -15837,11 +16080,11 @@ msgid "" " raster rastA " " integer nbandA " " raster rastB " -" integer nbandB " -" boolean " -"ST_Disjoint raster " -"rastA raster " -"rastB " +" integer nbandB boolean ST_Disjoint raster rastA raster rastB " msgstr "" #. Tag: para @@ -15873,8 +16116,10 @@ msgstr "" #: reference_raster.xml:10135 #, no-c-format msgid "" -"-- rid = 1 has no bands, hence the NOTICE and the NULL value for st_disjoint\n" -"SELECT r1.rid, r2.rid, ST_Disjoint(r1.rast, 1, r2.rast, 1) FROM dummy_rast r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" +"-- rid = 1 has no bands, hence the NOTICE and the NULL value for " +"st_disjoint\n" +"SELECT r1.rid, r2.rid, ST_Disjoint(r1.rast, 1, r2.rast, 1) FROM dummy_rast " +"r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" "\n" "NOTICE: The second raster provided has no bands\n" " rid | rid | st_disjoint \n" @@ -15888,7 +16133,8 @@ msgstr "" #, no-c-format msgid "" "-- this time, without specifying band numbers\n" -"SELECT r1.rid, r2.rid, ST_Disjoint(r1.rast, r2.rast) FROM dummy_rast r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" +"SELECT r1.rid, r2.rid, ST_Disjoint(r1.rast, r2.rast) FROM dummy_rast r1 " +"CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" "\n" " rid | rid | st_disjoint \n" "-----+-----+-------------\n" @@ -15912,30 +16158,29 @@ msgstr "" #: reference_raster.xml:10155 #, no-c-format msgid "" -" boolean " -"ST_Intersects raster " -" rastA integer " -"nbandA raster " -"rastB integer " -"nbandB " -"boolean ST_Intersects " -"raster rastA " -"raster rastB " -" boolean " -"ST_Intersects raster " -" rast integer " -"nband geometry " -"geommin " +" boolean ST_Intersects raster rastA integer nbandA raster rastB integer nbandB boolean " +"ST_Intersects raster " +"rastA raster " +"rastB " "boolean ST_Intersects " "raster rast " -"geometry geommin integer nband=NULL " -" boolean " -"ST_Intersects geometry " -" geommin raster " -" rast " -"integer nband=NULL " -"" +"integer nband " +"geometry geommin boolean ST_Intersects raster rast geometry geommin integer " +"nband=NULL " +" boolean ST_Intersects geometry geommin raster rast integer " +"nband=NULL " msgstr "" #. Tag: para @@ -15944,8 +16189,8 @@ msgstr "" msgid "" "Return true if raster rastA spatially intersects raster rastB. If the band " "number is not provided (or set to NULL), only the convex hull of the raster " -"is considered in the test. If the band number is provided, only those pixels" -" with value (not NODATA) are considered in the test." +"is considered in the test. If the band number is provided, only those pixels " +"with value (not NODATA) are considered in the test." msgstr "" #. Tag: para @@ -16002,20 +16247,20 @@ msgid "" " raster rastA " " integer nbandA " " raster rastB " -" integer nbandB " -" boolean " -"ST_Overlaps raster " -"rastA raster " -"rastB " +" integer nbandB boolean ST_Overlaps raster rastA raster rastB " msgstr "" #. Tag: para #: reference_raster.xml:10326 #, no-c-format msgid "" -"Return true if raster rastA spatially overlaps raster rastB. This means that" -" rastA and rastB intersect but one does not completely contain the other. If" -" the band number is not provided (or set to NULL), only the convex hull of " +"Return true if raster rastA spatially overlaps raster rastB. This means that " +"rastA and rastB intersect but one does not completely contain the other. If " +"the band number is not provided (or set to NULL), only the convex hull of " "the raster is considered in the test. If the band number is provided, only " "those pixels with value (not NODATA) are considered in the test." msgstr "" @@ -16062,11 +16307,11 @@ msgid "" " raster rastA " " integer nbandA " " raster rastB " -" integer nbandB " -" boolean " -"ST_Touches raster " -"rastA raster " -"rastB " +" integer nbandB boolean ST_Touches raster rastA raster rastB " msgstr "" #. Tag: para @@ -16074,8 +16319,8 @@ msgstr "" #, no-c-format msgid "" "Return true if raster rastA spatially touches raster rastB. This means that " -"rastA and rastB have at least one point in common but their interiors do not" -" intersect. If the band number is not provided (or set to NULL), only the " +"rastA and rastB have at least one point in common but their interiors do not " +"intersect. If the band number is not provided (or set to NULL), only the " "convex hull of the raster is considered in the test. If the band number is " "provided, only those pixels with value (not NODATA) are considered in the " "test." @@ -16093,7 +16338,8 @@ msgstr "" #: reference_raster.xml:10428 #, no-c-format msgid "" -"SELECT r1.rid, r2.rid, ST_Touches(r1.rast, 1, r2.rast, 1) FROM dummy_rast r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" +"SELECT r1.rid, r2.rid, ST_Touches(r1.rast, 1, r2.rast, 1) FROM dummy_rast r1 " +"CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" "\n" " rid | rid | st_touches \n" "-----+-----+------------\n" @@ -16120,29 +16366,28 @@ msgstr "" #: reference_raster.xml:10446 #, no-c-format msgid "" -" boolean " -"ST_SameAlignment raster " -" rastA raster " -" rastB " -" boolean " +" boolean ST_SameAlignment raster rastA raster rastB boolean " "ST_SameAlignment double " "precision ulx1 " "double precision uly1 " -" double precision scalex1 " -" double precision " -"scaley1 double precision" -" skewx1 double " -"precision skewy1 " -"double precision ulx2 " -" double precision uly2 " -" double precision " -"scalex2 double precision" -" scaley2 double " -"precision skewx2 " -"double precision skewy2 " -" boolean " -"ST_SameAlignment raster set " -" rastfield " +" double precision scalex1 double precision scaley1 double precision " +"skewx1 double precision " +" skewy1 double " +"precision ulx2 " +"double precision uly2 " +" double precision scalex2 double precision scaley2 double precision " +"skewx2 double precision " +" skewy2 " +" boolean ST_SameAlignment raster set rastfield " msgstr "" #. Tag: para @@ -16214,8 +16459,8 @@ msgstr "" #: reference_raster.xml:10545 #, no-c-format msgid "" -", , " +", , " msgstr "" #. Tag: refname @@ -16294,8 +16539,8 @@ msgstr "" #: reference_raster.xml:10599 #, no-c-format msgid "" -"Return true if no points of raster rastA lie in the exterior of raster rastB" -" and at least one point of the interior of rastA lies in the interior of " +"Return true if no points of raster rastA lie in the exterior of raster rastB " +"and at least one point of the interior of rastA lies in the interior of " "rastB." msgstr "" @@ -16307,11 +16552,11 @@ msgid "" " raster rastA " " integer nbandA " " raster rastB " -" integer nbandB " -" boolean " -"ST_Within raster " -"rastA raster " -"rastB " +" integer nbandB boolean ST_Within raster rastA raster rastB " msgstr "" #. Tag: para @@ -16322,8 +16567,8 @@ msgid "" "exterior of rastB and at least one point of the interior of rastA lies in " "the interior of rastB. If the band number is not provided (or set to NULL), " "only the convex hull of the raster is considered in the test. If the band " -"number is provided, only those pixels with value (not NODATA) are considered" -" in the test." +"number is provided, only those pixels with value (not NODATA) are considered " +"in the test." msgstr "" #. Tag: para @@ -16347,7 +16592,8 @@ msgstr "" #: reference_raster.xml:10672 #, no-c-format msgid "" -"SELECT r1.rid, r2.rid, ST_Within(r1.rast, 1, r2.rast, 1) FROM dummy_rast r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" +"SELECT r1.rid, r2.rid, ST_Within(r1.rast, 1, r2.rast, 1) FROM dummy_rast r1 " +"CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" "\n" " rid | rid | st_within \n" "-----+-----+-----------\n" @@ -16386,13 +16632,12 @@ msgid "" " integer nbandA " " raster rastB " " integer nbandB " -" double precision " -"distance_of_srid " -" boolean ST_DWithin " -" raster rastA " -" raster rastB " -" double precision " -"distance_of_srid " +" double precision distance_of_srid boolean " +"ST_DWithin raster " +"rastA raster " +"rastB double precision distance_of_srid " msgstr "" #. Tag: para @@ -16427,7 +16672,8 @@ msgstr "" #: reference_raster.xml:10767 #, no-c-format msgid "" -"SELECT r1.rid, r2.rid, ST_DWithin(r1.rast, 1, r2.rast, 1, 3.14) FROM dummy_rast r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" +"SELECT r1.rid, r2.rid, ST_DWithin(r1.rast, 1, r2.rast, 1, 3.14) FROM " +"dummy_rast r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" "\n" " rid | rid | st_dwithin \n" "-----+-----+------------\n" @@ -16459,19 +16705,18 @@ msgstr "" #: reference_raster.xml:10787 #, no-c-format msgid "" -" boolean " -"ST_DFullyWithin raster " -" rastA integer " -" nbandA raster " -" rastB integer " -" nbandB double " -"precision distance_of_srid " -" boolean " -"ST_DFullyWithin raster " -" rastA raster " -" rastB double " -"precision distance_of_srid " -"" +" boolean ST_DFullyWithin raster rastA integer nbandA raster rastB integer nbandB double precision " +"distance_of_srid " +" boolean ST_DFullyWithin raster rastA raster rastB double precision " +"distance_of_srid " msgstr "" #. Tag: para @@ -16479,10 +16724,10 @@ msgstr "" #, no-c-format msgid "" "Return true if rasters rastA and rastB are fully within the specified " -"distance of each other. If the band number is not provided (or set to NULL)," -" only the convex hull of the raster is considered in the test. If the band " -"number is provided, only those pixels with value (not NODATA) are considered" -" in the test." +"distance of each other. If the band number is not provided (or set to NULL), " +"only the convex hull of the raster is considered in the test. If the band " +"number is provided, only those pixels with value (not NODATA) are considered " +"in the test." msgstr "" #. Tag: para @@ -16497,7 +16742,8 @@ msgstr "" #: reference_raster.xml:10860 #, no-c-format msgid "" -"SELECT r1.rid, r2.rid, ST_DFullyWithin(r1.rast, 1, r2.rast, 1, 3.14) FROM dummy_rast r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" +"SELECT r1.rid, r2.rid, ST_DFullyWithin(r1.rast, 1, r2.rast, 1, 3.14) FROM " +"dummy_rast r1 CROSS JOIN dummy_rast r2 WHERE r1.rid = 2;\n" "\n" " rid | rid | st_dfullywithin \n" "-----+-----+-----------------\n" diff --git a/doc/po/de_DE/reference_sfcgal.xml.po b/doc/po/de_DE/reference_sfcgal.xml.po index 2ebd9420b..f64b80f63 100644 --- a/doc/po/de_DE/reference_sfcgal.xml.po +++ b/doc/po/de_DE/reference_sfcgal.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,19 +8,20 @@ msgstr "" "POT-Creation-Date: 2015-09-29 12:21+0000\n" "PO-Revision-Date: 2015-09-29 12:24+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: para #: reference_sfcgal.xml:5 #, no-c-format msgid "" -"SFCGAL is a C++ wrapper library around CGAL that provides advanced 2D and 3D" -" functions. For robustness, geometry coordinates have an exact rational " +"SFCGAL is a C++ wrapper library around CGAL that provides advanced 2D and 3D " +"functions. For robustness, geometry coordinates have an exact rational " "number representation." msgstr "" @@ -37,10 +38,10 @@ msgstr "" #: reference_sfcgal.xml:13 #, no-c-format msgid "" -"Some SFCGAL functions replace standard ones (ST_Intersects, ST_Intersection," -" ST_Difference, ST_Union, ST_Area and ST_Distance), to switch between " -"standard functions and SFCGAL function use: SET " -"postgis.backend = sfcgal; and" +"Some SFCGAL functions replace standard ones (ST_Intersects, ST_Intersection, " +"ST_Difference, ST_Union, ST_Area and ST_Distance), to switch between " +"standard functions and SFCGAL function use: SET postgis." +"backend = sfcgal; and" msgstr "" #. Tag: programlisting @@ -314,8 +315,8 @@ msgstr "" #: reference_sfcgal.xml:241 #, no-c-format msgid "" -"SELECT ST_ApproximateMedialAxis(ST_GeomFromText('POLYGON (( 190 190, 10 190," -" 10 10, 190 10, 190 20, 160 30, 60 30, 60 130, 190 140, 190 190 ))'));" +"SELECT ST_ApproximateMedialAxis(ST_GeomFromText('POLYGON (( 190 190, 10 190, " +"10 10, 190 10, 190 20, 160 30, 60 30, 60 130, 190 140, 190 190 ))'));" msgstr "" #. Tag: para @@ -425,8 +426,8 @@ msgstr "" #: reference_sfcgal.xml:377 #, no-c-format msgid "" -"This function performs a 2D minkowski sum of a point, line or polygon with a" -" polygon." +"This function performs a 2D minkowski sum of a point, line or polygon with a " +"polygon." msgstr "" #. Tag: para @@ -435,9 +436,8 @@ msgstr "" msgid "" "A minkowski sum of two geometries A and B is the set of all points that are " "the sum of any point in A and B. Minkowski sums are often used in motion " -"planning and computer-aided design. More details on Wikipedia Minkowski" -" addition." +"planning and computer-aided design. More details on Wikipedia Minkowski addition." msgstr "" #. Tag: para @@ -454,9 +454,8 @@ msgstr "" #: reference_sfcgal.xml:381 #, no-c-format msgid "" -"Implementation utilizes CGAL 2D " -"Minkowskisum." +"Implementation utilizes CGAL 2D Minkowskisum." msgstr "" #. Tag: para @@ -489,8 +488,24 @@ msgid "" " ST_Buffer(ST_GeomFromText('POINT(50 50)'), 30) As circle) As foo;\n" " \n" "-- wkt --\n" -"MULTIPOLYGON(((30 59.9999999999999,30.5764415879031 54.1472903395161,32.2836140246614 48.5194970290472,35.0559116309237 43.3328930094119,38.7867965644036 38.7867965644035,43.332893009412 35.0559116309236,48.5194970290474 32.2836140246614,54.1472903395162 30.5764415879031,60.0000000000001 30,65.8527096604839 30.5764415879031,71.4805029709527 32.2836140246614,76.6671069905881 35.0559116309237,81.2132034355964 38.7867965644036,171.213203435596 128.786796564404,174.944088369076 133.332893009412,177.716385975339 138.519497029047,179.423558412097 144.147290339516,180 150,179.423558412097 155.852709660484,177.716385975339 161.480502970953,174.944088369076 166.667106990588,171.213203435596 171.213203435596,166.667106990588 174.944088369076,\n" -"161.480502970953 177.716385975339,155.852709660484 179.423558412097,150 180,144.147290339516 179.423558412097,138.519497029047 177.716385975339,133.332893009412 174.944088369076,128.786796564403 171.213203435596,38.7867965644035 81.2132034355963,35.0559116309236 76.667106990588,32.2836140246614 71.4805029709526,30.5764415879031 65.8527096604838,30 59.9999999999999)))" +"MULTIPOLYGON(((30 59.9999999999999,30.5764415879031 " +"54.1472903395161,32.2836140246614 48.5194970290472,35.0559116309237 " +"43.3328930094119,38.7867965644036 38.7867965644035,43.332893009412 " +"35.0559116309236,48.5194970290474 32.2836140246614,54.1472903395162 " +"30.5764415879031,60.0000000000001 30,65.8527096604839 " +"30.5764415879031,71.4805029709527 32.2836140246614,76.6671069905881 " +"35.0559116309237,81.2132034355964 38.7867965644036,171.213203435596 " +"128.786796564404,174.944088369076 133.332893009412,177.716385975339 " +"138.519497029047,179.423558412097 144.147290339516,180 150,179.423558412097 " +"155.852709660484,177.716385975339 161.480502970953,174.944088369076 " +"166.667106990588,171.213203435596 171.213203435596,166.667106990588 " +"174.944088369076,\n" +"161.480502970953 177.716385975339,155.852709660484 179.423558412097,150 " +"180,144.147290339516 179.423558412097,138.519497029047 " +"177.716385975339,133.332893009412 174.944088369076,128.786796564403 " +"171.213203435596,38.7867965644035 81.2132034355963,35.0559116309236 " +"76.667106990588,32.2836140246614 71.4805029709526,30.5764415879031 " +"65.8527096604838,30 59.9999999999999)))" msgstr "" #. Tag: para @@ -555,8 +570,10 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_AsText(ST_3DIntersection(linestring, polygon)) As wkt\n" -"FROM ST_GeomFromText('LINESTRING Z (2 2 6,1.5 1.5 7,1 1 8,0.5 0.5 8,0 0 10)') AS linestring\n" -" CROSS JOIN ST_GeomFromText('POLYGON((0 0 8, 0 1 8, 1 1 8, 1 0 8, 0 0 8))') AS polygon;\n" +"FROM ST_GeomFromText('LINESTRING Z (2 2 6,1.5 1.5 7,1 1 8,0.5 0.5 8,0 0 " +"10)') AS linestring\n" +" CROSS JOIN ST_GeomFromText('POLYGON((0 0 8, 0 1 8, 1 1 8, 1 0 8, 0 0 8))') " +"AS polygon;\n" "\n" " wkt\n" "--------------------------------\n" @@ -574,10 +591,13 @@ msgstr "" #, no-c-format msgid "" "SELECT ST_AsText(ST_3DIntersection(\n" -" ST_GeomFromText('POLYHEDRALSURFACE Z( ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)), \n" -" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 0)), \n" +" ST_GeomFromText('POLYHEDRALSURFACE Z( ((0 0 0, 0 0 1, 0 1 1, " +"0 1 0, 0 0 0)), \n" +" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, " +"0 0 0)), \n" " ((1 1 0, 1 1 1, 1 0 1, 1 0 0, 1 1 0)), \n" -" ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 1)) )'), \n" +" ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, " +"0 0 1)) )'), \n" " 'POLYGON Z ((0 0 0, 0 0 0.5, 0 0.5 0.5, 0 0.5 0, 0 0 0))'::geometry))" msgstr "" @@ -585,8 +605,7 @@ msgstr "" #: reference_sfcgal.xml:495 #, no-c-format msgid "" -"TIN Z (((0 0 0,0 0 0.5,0 0.5 0.5,0 0 0)),((0 0.5 0,0 0 0,0 0.5 0.5,0 0.5 " -"0)))" +"TIN Z (((0 0 0,0 0 0.5,0 0.5 0.5,0 0 0)),((0 0.5 0,0 0 0,0 0.5 0.5,0 0.5 0)))" msgstr "" #. Tag: para @@ -601,7 +620,8 @@ msgstr "" #: reference_sfcgal.xml:498 #, no-c-format msgid "" -"SELECT ST_AsText(ST_3DIntersection( ST_Extrude(ST_Buffer('POINT(10 20)'::geometry,10,1),0,0,30),\n" +"SELECT ST_AsText(ST_3DIntersection( ST_Extrude(ST_Buffer('POINT(10 20)'::" +"geometry,10,1),0,0,30),\n" " ST_Extrude(ST_Buffer('POINT(10 20)'::geometry,10,1),2,0,10) ));" msgstr "" @@ -609,20 +629,33 @@ msgstr "" #: reference_sfcgal.xml:499 #, no-c-format msgid "" -"POLYHEDRALSURFACE Z (((13.3333333333333 13.3333333333333 10,20 20 0,20 20 10,13.3333333333333 13.3333333333333 10)),\n" -" ((20 20 10,16.6666666666667 23.3333333333333 10,13.3333333333333 13.3333333333333 10,20 20 10)),\n" +"POLYHEDRALSURFACE Z (((13.3333333333333 13.3333333333333 10,20 20 0,20 20 " +"10,13.3333333333333 13.3333333333333 10)),\n" +" ((20 20 10,16.6666666666667 23.3333333333333 10,13.3333333333333 " +"13.3333333333333 10,20 20 10)),\n" " ((20 20 0,16.6666666666667 23.3333333333333 10,20 20 10,20 20 0)),\n" -" ((13.3333333333333 13.3333333333333 10,10 10 0,20 20 0,13.3333333333333 13.3333333333333 10)),\n" -" ((16.6666666666667 23.3333333333333 10,12 28 10,13.3333333333333 13.3333333333333 10,16.6666666666667 23.3333333333333 10)),\n" -" ((20 20 0,9.99999999999995 30 0,16.6666666666667 23.3333333333333 10,20 20 0)),\n" -" ((10 10 0,9.99999999999995 30 0,20 20 0,10 10 0)),((13.3333333333333 13.3333333333333 10,12 12 10,10 10 0,13.3333333333333 13.3333333333333 10)),\n" -" ((12 28 10,12 12 10,13.3333333333333 13.3333333333333 10,12 28 10)),\n" -" ((16.6666666666667 23.3333333333333 10,9.99999999999995 30 0,12 28 10,16.6666666666667 23.3333333333333 10)),\n" +" ((13.3333333333333 13.3333333333333 10,10 10 0,20 20 " +"0,13.3333333333333 13.3333333333333 10)),\n" +" ((16.6666666666667 23.3333333333333 10,12 28 10,13.3333333333333 " +"13.3333333333333 10,16.6666666666667 23.3333333333333 10)),\n" +" ((20 20 0,9.99999999999995 30 0,16.6666666666667 23.3333333333333 " +"10,20 20 0)),\n" +" ((10 10 0,9.99999999999995 30 0,20 20 0,10 10 0))," +"((13.3333333333333 13.3333333333333 10,12 12 10,10 10 0,13.3333333333333 " +"13.3333333333333 10)),\n" +" ((12 28 10,12 12 10,13.3333333333333 13.3333333333333 10,12 28 " +"10)),\n" +" ((16.6666666666667 23.3333333333333 10,9.99999999999995 30 0,12 28 " +"10,16.6666666666667 23.3333333333333 10)),\n" " ((10 10 0,0 20 0,9.99999999999995 30 0,10 10 0)),\n" -" ((12 12 10,11 11 10,10 10 0,12 12 10)),((12 28 10,11 11 10,12 12 10,12 28 10)),\n" -" ((9.99999999999995 30 0,11 29 10,12 28 10,9.99999999999995 30 0)),((0 20 0,2 20 10,9.99999999999995 30 0,0 20 0)),\n" -" ((10 10 0,2 20 10,0 20 0,10 10 0)),((11 11 10,2 20 10,10 10 0,11 11 10)),((12 28 10,11 29 10,11 11 10,12 28 10)),\n" -" ((9.99999999999995 30 0,2 20 10,11 29 10,9.99999999999995 30 0)),((11 11 10,11 29 10,2 20 10,11 11 10)))" +" ((12 12 10,11 11 10,10 10 0,12 12 10)),((12 28 10,11 11 10,12 12 " +"10,12 28 10)),\n" +" ((9.99999999999995 30 0,11 29 10,12 28 10,9.99999999999995 30 0))," +"((0 20 0,2 20 10,9.99999999999995 30 0,0 20 0)),\n" +" ((10 10 0,2 20 10,0 20 0,10 10 0)),((11 11 10,2 20 10,10 10 0,11 11 " +"10)),((12 28 10,11 29 10,11 11 10,12 28 10)),\n" +" ((9.99999999999995 30 0,2 20 10,11 29 10,9.99999999999995 30 0))," +"((11 11 10,11 29 10,2 20 10,11 11 10)))" msgstr "" #. Tag: refname @@ -692,8 +725,7 @@ msgstr "" #, no-c-format msgid "" "Note: By default a PolyhedralSurface built from WKT is a surface geometry, " -"not solid. It therefore has surface area. Once converted to a solid, no " -"area." +"not solid. It therefore has surface area. Once converted to a solid, no area." msgstr "" #. Tag: programlisting @@ -732,8 +764,8 @@ msgstr "" #: reference_sfcgal.xml:604 #, no-c-format msgid "" -"Perform surface Tesselation of a polygon or polyhedralsurface and returns as" -" a TIN or collection of TINS" +"Perform surface Tesselation of a polygon or polyhedralsurface and returns as " +"a TIN or collection of TINS" msgstr "" #. Tag: funcprototype @@ -756,10 +788,13 @@ msgstr "" #: reference_sfcgal.xml:632 #, no-c-format msgid "" -"SELECT ST_GeomFromText('POLYHEDRALSURFACE Z( ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)), \n" -" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 0)), \n" +"SELECT ST_GeomFromText('POLYHEDRALSURFACE Z( ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 " +"0 0)), \n" +" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 " +"1, 0 0 1, 0 0 0)), \n" " ((1 1 0, 1 1 1, 1 0 1, 1 0 0, 1 1 0)), \n" -" ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 1)) )');" +" ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 " +"1, 0 1 1, 0 0 1)) )');" msgstr "" #. Tag: para @@ -772,10 +807,13 @@ msgstr "" #: reference_sfcgal.xml:643 #, no-c-format msgid "" -"SELECT ST_Tesselate(ST_GeomFromText('POLYHEDRALSURFACE Z( ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)), \n" -" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 0)), \n" +"SELECT ST_Tesselate(ST_GeomFromText('POLYHEDRALSURFACE Z( ((0 0 0, 0 0 1, 0 " +"1 1, 0 1 0, 0 0 0)), \n" +" ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, " +"0 0 0)), \n" " ((1 1 0, 1 1 1, 1 0 1, 1 0 0, 1 1 0)), \n" -" ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 1)) )'));" +" ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, " +"0 0 1)) )'));" msgstr "" #. Tag: para @@ -816,7 +854,8 @@ msgstr "" #, no-c-format msgid "" "SELECT \n" -" ST_Tesselate('POLYGON (( 10 190, 10 70, 80 70, 80 130, 50 160, 120 160, 120 190, 10 190 ))'::geometry);" +" ST_Tesselate('POLYGON (( 10 190, 10 70, 80 70, 80 130, 50 160, 120 " +"160, 120 190, 10 190 ))'::geometry);" msgstr "" #. Tag: para @@ -873,9 +912,8 @@ msgstr "" #, no-c-format msgid "" "When closed surfaces are created with WKT, they are treated as areal rather " -"than solid. To make them solid, you need to use . Areal geometries have no volume. Here is an " -"example to demonstrate." +"than solid. To make them solid, you need to use . Areal geometries have no volume. Here is an example to demonstrate." msgstr "" #. Tag: programlisting diff --git a/doc/po/de_DE/reference_temporal.xml.po b/doc/po/de_DE/reference_temporal.xml.po new file mode 100644 index 000000000..b4bc432db --- /dev/null +++ b/doc/po/de_DE/reference_temporal.xml.po @@ -0,0 +1,277 @@ +# SOME DESCRIPTIVE TITLE. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2015-09-29 12:15+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: reference_temporal.xml:3 +#, no-c-format +msgid "Temporal Support" +msgstr "" + +#. Tag: refname +#: reference_temporal.xml:8 +#, no-c-format +msgid "ST_IsValidTrajectory" +msgstr "" + +#. Tag: refpurpose +#: reference_temporal.xml:9 +#, no-c-format +msgid "Returns true if the geometry is a valid trajectory." +msgstr "" + +#. Tag: funcprototype +#: reference_temporal.xml:16 +#, no-c-format +msgid "boolean ST_IsValidTrajectory geometry line" +msgstr "" + +#. Tag: title +#: reference_temporal.xml:24 reference_temporal.xml:76 reference_temporal.xml:132 reference_temporal.xml:185 +#, no-c-format +msgid "Description" +msgstr "" + +#. Tag: para +#: reference_temporal.xml:26 +#, no-c-format +msgid "Tell if a geometry encodes a valid trajectory. Valid trajectories are encoded as LINESTRING with M value growing from each vertex to the next." +msgstr "" + +#. Tag: para +#: reference_temporal.xml:32 +#, no-c-format +msgid "Valid trajectories are expected as input to some spatio-temporal queries like " +msgstr "" + +#. Tag: para +#: reference_temporal.xml:37 reference_temporal.xml:90 reference_temporal.xml:141 reference_temporal.xml:197 +#, no-c-format +msgid "Availability: 2.2.0" +msgstr "" + +#. Tag: para +#: reference_temporal.xml:38 reference_temporal.xml:91 reference_temporal.xml:142 reference_temporal.xml:198 +#, no-c-format +msgid "&Z_support;" +msgstr "" + +#. Tag: title +#: reference_temporal.xml:43 reference_temporal.xml:96 reference_temporal.xml:147 reference_temporal.xml:203 +#, no-c-format +msgid "Examples" +msgstr "" + +#. Tag: programlisting +#: reference_temporal.xml:44 +#, no-c-format +msgid "" + "-- A valid trajectory\n" + "SELECT ST_IsValidTrajectory(ST_MakeLine(\n" + " ST_MakePointM(0,0,1),\n" + " ST_MakePointM(0,1,2))\n" + ");\n" + " t\n" + "\n" + "-- An invalid trajectory\n" + "SELECT ST_IsValidTrajectory(ST_MakeLine(ST_MakePointM(0,0,1), ST_MakePointM(0,1,0)));\n" + "NOTICE: Measure of vertex 1 (0) not bigger than measure of vertex 0 (1)\n" + " st_isvalidtrajectory\n" + "----------------------\n" + " f" +msgstr "" + +#. Tag: title +#: reference_temporal.xml:49 reference_temporal.xml:102 reference_temporal.xml:153 reference_temporal.xml:209 +#, no-c-format +msgid "See Also" +msgstr "" + +#. Tag: refname +#: reference_temporal.xml:59 +#, no-c-format +msgid "ST_ClosestPointOfApproach" +msgstr "" + +#. Tag: refpurpose +#: reference_temporal.xml:60 +#, no-c-format +msgid "Returns the measure at which points interpolated along two lines are closest." +msgstr "" + +#. Tag: funcprototype +#: reference_temporal.xml:67 +#, no-c-format +msgid "float8 ST_ClosestPointOfApproach geometry track1 geometry track2" +msgstr "" + +#. Tag: para +#: reference_temporal.xml:78 +#, no-c-format +msgid "Returns the smallest measure at which point interpolated along the given lines are at the smallest distance. Inputs must be valid trajectories as checked by . Null is returned if the trajectories do not overlap on the M range." +msgstr "" + +#. Tag: para +#: reference_temporal.xml:85 +#, no-c-format +msgid "See for getting the actual points at the given measure." +msgstr "" + +#. Tag: programlisting +#: reference_temporal.xml:97 +#, no-c-format +msgid "" + "-- Return the time in which two objects moving between 10:00 and 11:00\n" + "-- are closest to each other and their distance at that point\n" + "WITH inp AS ( SELECT\n" + " ST_AddMeasure('LINESTRING Z (0 0 0, 10 0 5)'::geometry,\n" + " extract(epoch from '2015-05-26 10:00'::timestamptz),\n" + " extract(epoch from '2015-05-26 11:00'::timestamptz)\n" + " ) a,\n" + " ST_AddMeasure('LINESTRING Z (0 2 10, 12 1 2)'::geometry,\n" + " extract(epoch from '2015-05-26 10:00'::timestamptz),\n" + " extract(epoch from '2015-05-26 11:00'::timestamptz)\n" + " ) b\n" + "), cpa AS (\n" + " SELECT ST_ClosestPointOfApproach(a,b) m FROM inp\n" + "), points AS (\n" + " SELECT ST_Force3DZ(ST_GeometryN(ST_LocateAlong(a,m),1)) pa,\n" + " ST_Force3DZ(ST_GeometryN(ST_LocateAlong(b,m),1)) pb\n" + " FROM inp, cpa\n" + ")\n" + "SELECT to_timestamp(m) t,\n" + " ST_Distance(pa,pb) distance\n" + "FROM points, cpa;\n" + "\n" + " t | distance\n" + "-------------------------------+------------------\n" + " 2015-05-26 10:45:31.034483+02 | 1.96036833151395" +msgstr "" + +#. Tag: para +#: reference_temporal.xml:103 +#, no-c-format +msgid ", , , " +msgstr "" + +#. Tag: refname +#: reference_temporal.xml:115 +#, no-c-format +msgid "ST_DistanceCPA" +msgstr "" + +#. Tag: refpurpose +#: reference_temporal.xml:116 +#, no-c-format +msgid "Returns the distance between closest points of approach in two trajectories." +msgstr "" + +#. Tag: funcprototype +#: reference_temporal.xml:123 +#, no-c-format +msgid "float8 ST_DistanceCPA geometry track1 geometry track2" +msgstr "" + +#. Tag: para +#: reference_temporal.xml:134 +#, no-c-format +msgid "Returns the minimum distance two moving objects have ever been each-other. Inputs must be valid trajectories as checked by . Null is returned if the trajectories do not overlap on the M range." +msgstr "" + +#. Tag: programlisting +#: reference_temporal.xml:148 +#, no-c-format +msgid "" + "-- Return the minimum distance of two objects moving between 10:00 and 11:00\n" + "WITH inp AS ( SELECT\n" + " ST_AddMeasure('LINESTRING Z (0 0 0, 10 0 5)'::geometry,\n" + " extract(epoch from '2015-05-26 10:00'::timestamptz),\n" + " extract(epoch from '2015-05-26 11:00'::timestamptz)\n" + " ) a,\n" + " ST_AddMeasure('LINESTRING Z (0 2 10, 12 1 2)'::geometry,\n" + " extract(epoch from '2015-05-26 10:00'::timestamptz),\n" + " extract(epoch from '2015-05-26 11:00'::timestamptz)\n" + " ) b\n" + ")\n" + "SELECT ST_DistanceCPA(a,b) distance FROM inp;\n" + "\n" + " distance\n" + "------------------\n" + " 1.96036833151395" +msgstr "" + +#. Tag: para +#: reference_temporal.xml:154 +#, no-c-format +msgid ", , , " +msgstr "" + +#. Tag: refname +#: reference_temporal.xml:166 +#, no-c-format +msgid "ST_CPAWithin" +msgstr "" + +#. Tag: refpurpose +#: reference_temporal.xml:167 +#, no-c-format +msgid "Returns true if the trajectories' closest points of approach are within the specified distance." +msgstr "" + +#. Tag: funcprototype +#: reference_temporal.xml:175 +#, no-c-format +msgid "float8 ST_CPAWithin geometry track1 geometry track2 float8 maxdist" +msgstr "" + +#. Tag: para +#: reference_temporal.xml:187 +#, no-c-format +msgid "Checks whether two moving objects have ever been within the specified max distance." +msgstr "" + +#. Tag: para +#: reference_temporal.xml:191 +#, no-c-format +msgid "Inputs must be valid trajectories as checked by . False is returned if the trajectories do not overlap on the M range." +msgstr "" + +#. Tag: programlisting +#: reference_temporal.xml:204 +#, no-c-format +msgid "" + "WITH inp AS ( SELECT\n" + " ST_AddMeasure('LINESTRING Z (0 0 0, 10 0 5)'::geometry,\n" + " extract(epoch from '2015-05-26 10:00'::timestamptz),\n" + " extract(epoch from '2015-05-26 11:00'::timestamptz)\n" + " ) a,\n" + " ST_AddMeasure('LINESTRING Z (0 2 10, 12 1 2)'::geometry,\n" + " extract(epoch from '2015-05-26 10:00'::timestamptz),\n" + " extract(epoch from '2015-05-26 11:00'::timestamptz)\n" + " ) b\n" + ")\n" + "SELECT ST_CPAWithin(a,b,2), ST_DistanceCPA(a,b) distance FROM inp;\n" + "\n" + " st_cpawithin | distance\n" + "--------------+------------------\n" + " t | 1.96521473776207" +msgstr "" + +#. Tag: para +#: reference_temporal.xml:210 +#, no-c-format +msgid ", , , " +msgstr "" + diff --git a/doc/po/de_DE/reference_transaction.xml.po b/doc/po/de_DE/reference_transaction.xml.po index f677c4c82..13430a26c 100644 --- a/doc/po/de_DE/reference_transaction.xml.po +++ b/doc/po/de_DE/reference_transaction.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2012-09-14 17:50+0000\n" "PO-Revision-Date: 2015-09-29 11:54+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: title @@ -26,17 +27,16 @@ msgstr "" #, no-c-format msgid "" "This module and associated pl/pgsql functions have been implemented to " -"provide long locking support required by Web Feature " -"Service specification." +"provide long locking support required by Web Feature Service specification." msgstr "" #. Tag: para #: reference_transaction.xml:10 #, no-c-format msgid "" -"Users must use serializable transaction level otherwise " +"Users must use serializable transaction level otherwise " "locking mechanism would break." msgstr "" @@ -50,16 +50,16 @@ msgstr "" #: reference_transaction.xml:20 #, no-c-format msgid "" -"Add an authorization token to be used in current " -"transaction." +"Add an authorization token to be used in current transaction." msgstr "" #. Tag: funcprototype #: reference_transaction.xml:25 #, no-c-format msgid "" -"boolean AddAuth text" -" auth_token" +"boolean AddAuth text " +" auth_token" msgstr "" #. Tag: title @@ -108,12 +108,14 @@ 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" +" 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'" +" ERROR: UPDATE where \"gid\" = '353' requires authorization " +"'priscilla'" msgstr "" #. Tag: title @@ -143,13 +145,12 @@ msgstr "" #, no-c-format msgid "" " integer CheckAuth " -"text a_schema_name" -" text a_table_name" -" text " -"a_key_column_name " -" integer CheckAuth " +"text a_schema_name " "text a_table_name " -"text " +"text a_key_column_name integer " +"CheckAuth text " +"a_table_name text " "a_key_column_name " msgstr "" @@ -165,8 +166,7 @@ msgstr "" #: reference_transaction.xml:87 #, no-c-format msgid "" -"If a_schema_name is not passed in, then searches for table in current " -"schema." +"If a_schema_name is not passed in, then searches for table in current schema." msgstr "" #. Tag: para @@ -202,9 +202,9 @@ msgstr "" #: reference_transaction.xml:115 #, no-c-format msgid "" -"Disable long transaction support. This function removes the long" -" transaction support metadata tables, and drops all triggers attached to " -"lock-checked tables." +"Disable long transaction support. This function removes the long " +"transaction support metadata tables, and drops all triggers attached to lock-" +"checked tables." msgstr "" #. Tag: funcprototype @@ -220,8 +220,8 @@ msgstr "" #, no-c-format msgid "" "Disable long transaction support. This function removes the long " -"transaction support metadata tables, and drops all triggers attached to " -"lock-checked tables." +"transaction support metadata tables, and drops all triggers attached to lock-" +"checked tables." msgstr "" #. Tag: para @@ -270,8 +270,8 @@ msgstr "" #, no-c-format msgid "" "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." +"metadata tables, needs to be called once before using the other functions in " +"this section. Calling it twice is harmless." msgstr "" #. Tag: para @@ -308,18 +308,17 @@ msgstr "" #, no-c-format msgid "" " integer LockRow " -"text a_schema_name" -" text a_table_name" -" text a_row_key " +"text a_schema_name " +"text a_table_name " +"text a_row_key " "text an_auth_token " -"timestamp expire_dt" -" integer " -"LockRow text " -"a_table_name text " -"a_row_key text " -"an_auth_token " -"timestamp expire_dt" -" integer " +"timestamp expire_dt " +" integer LockRow text a_table_name text a_row_key text an_auth_token timestamp expire_dt integer " "LockRow text " "a_table_name text " "a_row_key text " @@ -361,8 +360,8 @@ msgstr "" #: reference_transaction.xml:270 #, no-c-format msgid "" -"Remove all locks held by specified authorization id. Returns the" -" number of locks released." +"Remove all locks held by specified authorization id. Returns the " +"number of locks released." msgstr "" #. Tag: funcprototype diff --git a/doc/po/de_DE/reference_type.xml.po b/doc/po/de_DE/reference_type.xml.po index c05639752..5c100bf22 100644 --- a/doc/po/de_DE/reference_type.xml.po +++ b/doc/po/de_DE/reference_type.xml.po @@ -1,5 +1,5 @@ # SOME DESCRIPTIVE TITLE. -# +# # Translators: msgid "" msgstr "" @@ -8,11 +8,12 @@ msgstr "" "POT-Creation-Date: 2012-09-14 21:04+0000\n" "PO-Revision-Date: 2015-09-29 11:54+0000\n" "Last-Translator: Sandro Santilli \n" -"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/language/de_DE/)\n" +"Language-Team: German (Germany) (http://www.transifex.com/postgis/postgis/" +"language/de_DE/)\n" +"Language: de_DE\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: de_DE\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. Tag: para @@ -31,8 +32,8 @@ 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 " +"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 "" @@ -42,9 +43,9 @@ msgstr "" 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 " +"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 "" diff --git a/doc/po/de_DE/release_notes.xml.po b/doc/po/de_DE/release_notes.xml.po new file mode 100644 index 000000000..640cba006 --- /dev/null +++ b/doc/po/de_DE/release_notes.xml.po @@ -0,0 +1,6352 @@ +# SOME DESCRIPTIVE TITLE. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2015-09-29 12:21+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: release_notes.xml:3 +#, no-c-format +msgid "Appendix" +msgstr "" + +#. Tag: subtitle +#: release_notes.xml:4 +#, no-c-format +msgid "Release Notes" +msgstr "" + +#. Tag: title +#: release_notes.xml:7 +#, no-c-format +msgid "Release 2.2.0" +msgstr "" + +#. Tag: para +#: release_notes.xml:8 +#, no-c-format +msgid "Release date: 2015/10/DD" +msgstr "" + +#. Tag: para +#: release_notes.xml:9 +#, no-c-format +msgid "This is a new feature release, with new functions, improved performance, and other goodies." +msgstr "" + +#. Tag: title +#: release_notes.xml:11 release_notes.xml:297 release_notes.xml:756 release_notes.xml:956 release_notes.xml:1020 release_notes.xml:1317 +#, no-c-format +msgid "New Features" +msgstr "" + +#. Tag: para +#: release_notes.xml:12 +#, no-c-format +msgid "Topology API in liblwgeom (Sandro Santilli / Regione Toscana - SITA)" +msgstr "" + +#. Tag: para +#: release_notes.xml:13 +#, no-c-format +msgid "New lwgeom_unaryunion method in liblwgeom" +msgstr "" + +#. Tag: para +#: release_notes.xml:14 +#, no-c-format +msgid "New lwgeom_linemerge method in liblwgeom" +msgstr "" + +#. Tag: para +#: release_notes.xml:15 +#, no-c-format +msgid "New lwgeom_is_simple method in liblwgeom" +msgstr "" + +#. Tag: para +#: release_notes.xml:16 +#, no-c-format +msgid "#3169, Add SFCGAL 1.1 support: add ST_3DDifference, ST_3DUnion, ST_Volume, ST_MakeSolid, ST_IsSolid (Vincent Mora / Oslandia)" +msgstr "" + +#. Tag: para +#: release_notes.xml:17 +#, no-c-format +msgid "#3169, ST_ApproximateMedialAxis (Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:18 +#, no-c-format +msgid "ST_CPAWithin (Sandro Santilli / Boundless)" +msgstr "" + +#. Tag: para +#: release_notes.xml:19 +#, no-c-format +msgid "Add |=| operator with CPA semantic and KNN support with PgSQL 9.5+ (Sandro Santilli / Boundless)" +msgstr "" + +#. Tag: para +#: release_notes.xml:20 +#, no-c-format +msgid "#3131, KNN support for the geography type (Paul Ramsey / CartoDB)" +msgstr "" + +#. Tag: para +#: release_notes.xml:21 +#, no-c-format +msgid "#3023, ST_ClusterIntersecting / ST_ClusterWithin (Dan Baston)" +msgstr "" + +#. Tag: para +#: release_notes.xml:22 +#, no-c-format +msgid "#2703, Exact KNN results for all geometry types, aka \"KNN re-check\" (Paul Ramsey / CartoDB)" +msgstr "" + +#. Tag: para +#: release_notes.xml:23 +#, no-c-format +msgid "#1137, Allow a tolerance value in ST_RemoveRepeatedPoints (Paul Ramsey / CartoDB)" +msgstr "" + +#. Tag: para +#: release_notes.xml:24 +#, no-c-format +msgid "#3062, Allow passing M factor to ST_Scale (Sandro Santilli / Boundless)" +msgstr "" + +#. Tag: para +#: release_notes.xml:25 +#, no-c-format +msgid "#3139, ST_BoundingDiagonal (Sandro Santilli / Boundless)" +msgstr "" + +#. Tag: para +#: release_notes.xml:26 +#, no-c-format +msgid "#3129, ST_IsValidTrajectory (Sandro Santilli / Boundless)" +msgstr "" + +#. Tag: para +#: release_notes.xml:27 +#, no-c-format +msgid "#3128, ST_ClosestPointOfApproach (Sandro Santilli / Boundless)" +msgstr "" + +#. Tag: para +#: release_notes.xml:28 +#, no-c-format +msgid "#3152, ST_DistanceCPA (Sandro Santilli / Boundless)" +msgstr "" + +#. Tag: para +#: release_notes.xml:29 +#, no-c-format +msgid "Canonical output for index key types" +msgstr "" + +#. Tag: para +#: release_notes.xml:30 +#, no-c-format +msgid "ST_SwapOrdinates (Sandro Santilli / Boundless)" +msgstr "" + +#. Tag: para +#: release_notes.xml:31 +#, no-c-format +msgid "#2918, Use GeographicLib functions for geodetics (Mike Toews)" +msgstr "" + +#. Tag: para +#: release_notes.xml:32 +#, no-c-format +msgid "#3074, ST_Subdivide to break up large geometry (Paul Ramsey / CartoDB)" +msgstr "" + +#. Tag: para +#: release_notes.xml:33 +#, no-c-format +msgid "#3040, KNN GiST index based centroid (<<->>) n-D distance operators (Sandro Santilli / Boundless)" +msgstr "" + +#. Tag: para +#: release_notes.xml:34 +#, no-c-format +msgid "Interruptibility API for liblwgeom (Sandro Santilli / CartoDB)" +msgstr "" + +#. Tag: para +#: release_notes.xml:35 +#, no-c-format +msgid "#2939, ST_ClipByBox2D (Sandro Santilli / CartoDB)" +msgstr "" + +#. Tag: para +#: release_notes.xml:36 +#, no-c-format +msgid "#2247, ST_Retile and ST_CreateOverview: in-db raster overviews creation (Sandro Santilli / Vizzuality)" +msgstr "" + +#. Tag: para +#: release_notes.xml:37 +#, no-c-format +msgid "#899, -m shp2pgsql attribute names mapping -m switch (Regina Obe / Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:38 +#, no-c-format +msgid "#1678, Added GUC postgis.gdal_datapath to specify GDAL config variable GDAL_DATA" +msgstr "" + +#. Tag: para +#: release_notes.xml:39 +#, no-c-format +msgid "#2843, Support reprojection on raster import (Sandro Santilli / Vizzuality)" +msgstr "" + +#. Tag: para +#: release_notes.xml:40 +#, no-c-format +msgid "#2349, Support for encoded_polyline input/output (Kashif Rasul)" +msgstr "" + +#. Tag: para +#: release_notes.xml:41 +#, no-c-format +msgid "#2159, report libjson version from postgis_full_version()" +msgstr "" + +#. Tag: para +#: release_notes.xml:42 +#, no-c-format +msgid "#2770, ST_MemSize(raster)" +msgstr "" + +#. Tag: para +#: release_notes.xml:43 +#, no-c-format +msgid "Add postgis_noop(raster)" +msgstr "" + +#. Tag: para +#: release_notes.xml:44 +#, no-c-format +msgid "Added missing variants of ST_TPI(), ST_TRI() and ST_Roughness()" +msgstr "" + +#. Tag: para +#: release_notes.xml:45 +#, no-c-format +msgid "Added GUC postgis.gdal_enabled_drivers to specify GDAL config variable GDAL_SKIP" +msgstr "" + +#. Tag: para +#: release_notes.xml:46 +#, no-c-format +msgid "Added GUC postgis.enable_outdb_rasters to enable access to rasters with out-db bands" +msgstr "" + +#. Tag: para +#: release_notes.xml:47 +#, no-c-format +msgid "#2387, address_standardizer extension as part of PostGIS (Stephen Woodbridge / imaptools.com, Walter Sinclair, Regina Obe)" +msgstr "" + +#. Tag: para +#: release_notes.xml:48 +#, no-c-format +msgid "#2816, address_standardizer_data_us extension provides reference lex,gaz,rules for address_standardizer (Stephen Woodbridge / imaptools.com, Walter Sinclair, Regina Obe)" +msgstr "" + +#. Tag: para +#: release_notes.xml:49 +#, no-c-format +msgid "#2341, New mask parameter for ST_MapAlgebra" +msgstr "" + +#. Tag: para +#: release_notes.xml:50 +#, no-c-format +msgid "#2397, read encoding info automatically in shapefile loader" +msgstr "" + +#. Tag: para +#: release_notes.xml:51 +#, no-c-format +msgid "#2430, ST_ForceCurve" +msgstr "" + +#. Tag: para +#: release_notes.xml:52 +#, no-c-format +msgid "#2565, ST_SummaryStatsAgg()" +msgstr "" + +#. Tag: para +#: release_notes.xml:53 +#, no-c-format +msgid "#2567, ST_CountAgg()" +msgstr "" + +#. Tag: para +#: release_notes.xml:54 +#, no-c-format +msgid "#2632, ST_AsGML() support for curved features" +msgstr "" + +#. Tag: para +#: release_notes.xml:55 +#, no-c-format +msgid "#2652, Add --upgrade-path switch to run_test.pl" +msgstr "" + +#. Tag: para +#: release_notes.xml:56 +#, no-c-format +msgid "#2754, sfcgal wrapped as an extension" +msgstr "" + +#. Tag: para +#: release_notes.xml:57 +#, no-c-format +msgid "#2227, Simplification with Visvalingam-Whyatt algorithm ST_SimplifyVW, ST_SetEffectiveArea (Nicklas Avén)" +msgstr "" + +#. Tag: para +#: release_notes.xml:58 +#, no-c-format +msgid "Functions to encode and decode TWKB ST_AsTWKB, ST_GeomFromTWKB (Paul Ramsey / Nicklas Avén / CartoDB)" +msgstr "" + +#. Tag: title +#: release_notes.xml:61 release_notes.xml:89 release_notes.xml:110 release_notes.xml:219 release_notes.xml:247 release_notes.xml:366 release_notes.xml:544 release_notes.xml:572 release_notes.xml:631 release_notes.xml:693 release_notes.xml:783 release_notes.xml:984 release_notes.xml:1039 +#, no-c-format +msgid "Enhancements" +msgstr "" + +#. Tag: para +#: release_notes.xml:62 +#, no-c-format +msgid "#3223, Add memcmp short-circuit to ST_Equals (Daniel Baston)" +msgstr "" + +#. Tag: para +#: release_notes.xml:63 +#, no-c-format +msgid "#3227, Tiger geocoder upgraded to support Tiger 2015 census" +msgstr "" + +#. Tag: para +#: release_notes.xml:64 +#, no-c-format +msgid "#2278, Make liblwgeom compatible between minor releases" +msgstr "" + +#. Tag: para +#: release_notes.xml:65 +#, no-c-format +msgid "#897, ST_AsX3D support for GeoCoordinates and systems \"GD\" \"WE\" ability to flip x/y axis (use option = 2, 3)" +msgstr "" + +#. Tag: para +#: release_notes.xml:66 +#, no-c-format +msgid "ST_Split: allow splitting lines by multilines, multipoints and (multi)polygon boundaries" +msgstr "" + +#. Tag: para +#: release_notes.xml:67 +#, no-c-format +msgid "#3070, Simplify geometry type constraint" +msgstr "" + +#. Tag: para +#: release_notes.xml:68 +#, no-c-format +msgid "#2839, Implement selectivity estimator for functional indexes, speeding up spatial queries on raster tables. (Sandro Santilli / Vizzuality)" +msgstr "" + +#. Tag: para +#: release_notes.xml:69 +#, no-c-format +msgid "#2361, Added spatial_index column to raster_columns view" +msgstr "" + +#. Tag: para +#: release_notes.xml:70 +#, no-c-format +msgid "#2390, Testsuite for pgsql2shp" +msgstr "" + +#. Tag: para +#: release_notes.xml:71 +#, no-c-format +msgid "#2527, Added -k flag to raster2pgsql to skip checking that band is NODATA" +msgstr "" + +#. Tag: para +#: release_notes.xml:72 +#, no-c-format +msgid "#2616, Reduce text casts during topology building and export" +msgstr "" + +#. Tag: para +#: release_notes.xml:73 +#, no-c-format +msgid "#2717, support startpoint, endpoint, pointn, numpoints for compoundcurve" +msgstr "" + +#. Tag: para +#: release_notes.xml:74 +#, no-c-format +msgid "#2747, Add support for GDAL 2.0" +msgstr "" + +#. Tag: para +#: release_notes.xml:75 +#, no-c-format +msgid "#2754, SFCGAL can now be installed with CREATE EXTENSION (Vincent Mora @ Oslandia)" +msgstr "" + +#. Tag: para +#: release_notes.xml:76 +#, no-c-format +msgid "#2828, Convert ST_Envelope(raster) from SQL to C" +msgstr "" + +#. Tag: para +#: release_notes.xml:77 release_notes.xml:115 +#, no-c-format +msgid "#2829, Shortcut ST_Clip(raster) if geometry fully contains the raster and no NODATA specified" +msgstr "" + +#. Tag: para +#: release_notes.xml:78 +#, no-c-format +msgid "#2906, Update tiger geocoder to handle tiger 2014 data" +msgstr "" + +#. Tag: para +#: release_notes.xml:79 +#, no-c-format +msgid "#3048, Speed up geometry simplification (J.Santana @ CartoDB)" +msgstr "" + +#. Tag: para +#: release_notes.xml:80 +#, no-c-format +msgid "#3092, Slow performance of geometry_columns with many tables" +msgstr "" + +#. Tag: title +#: release_notes.xml:85 +#, no-c-format +msgid "Release 2.1.5" +msgstr "" + +#. Tag: para +#: release_notes.xml:86 +#, no-c-format +msgid "Release date: 2014-12-18" +msgstr "" + +#. Tag: para +#: release_notes.xml:87 release_notes.xml:108 +#, no-c-format +msgid "This is a bug fix and performance improvement release." +msgstr "" + +#. Tag: para +#: release_notes.xml:90 +#, no-c-format +msgid "#2933, Speedup construction of large multi-geometry objects" +msgstr "" + +#. Tag: title +#: release_notes.xml:93 release_notes.xml:121 release_notes.xml:182 release_notes.xml:193 release_notes.xml:234 release_notes.xml:490 release_notes.xml:516 release_notes.xml:558 release_notes.xml:582 release_notes.xml:645 release_notes.xml:800 release_notes.xml:814 release_notes.xml:852 release_notes.xml:890 release_notes.xml:921 +#, no-c-format +msgid "Bug Fixes" +msgstr "" + +#. Tag: para +#: release_notes.xml:95 +#, no-c-format +msgid "#2947, Fix memory leak in lwgeom_make_valid for single-component collection input" +msgstr "" + +#. Tag: para +#: release_notes.xml:97 +#, no-c-format +msgid "#2949, Fix memory leak in lwgeom_mindistance2d for curve input" +msgstr "" + +#. Tag: para +#: release_notes.xml:98 +#, no-c-format +msgid "#2931, BOX representation is case sensitive" +msgstr "" + +#. Tag: para +#: release_notes.xml:99 +#, no-c-format +msgid "#2942, PostgreSQL 9.5 support" +msgstr "" + +#. Tag: para +#: release_notes.xml:100 +#, no-c-format +msgid "#2953, 2D stats not generated when Z/M values are extreme" +msgstr "" + +#. Tag: para +#: release_notes.xml:101 +#, no-c-format +msgid "#3009, Geography cast may effect underlying tuple" +msgstr "" + +#. Tag: title +#: release_notes.xml:106 +#, no-c-format +msgid "Release 2.1.4" +msgstr "" + +#. Tag: para +#: release_notes.xml:107 +#, no-c-format +msgid "Release date: 2014-09-10" +msgstr "" + +#. Tag: para +#: release_notes.xml:111 +#, no-c-format +msgid "#2745, Speedup ST_Simplify calls against points" +msgstr "" + +#. Tag: para +#: release_notes.xml:112 +#, no-c-format +msgid "#2747, Support for GDAL 2.0" +msgstr "" + +#. Tag: para +#: release_notes.xml:113 +#, no-c-format +msgid "#2749, Make rtpostgis_upgrade_20_21.sql ACID" +msgstr "" + +#. Tag: para +#: release_notes.xml:114 +#, no-c-format +msgid "#2811, Do not specify index names when loading shapefiles/rasters" +msgstr "" + +#. Tag: para +#: release_notes.xml:117 +#, no-c-format +msgid "#2895, Raise cost of ST_ConvexHull(raster) to 300 for better query plans" +msgstr "" + +#. Tag: para +#: release_notes.xml:122 +#, no-c-format +msgid "#2605, armel: _ST_Covers() returns true for point in hole" +msgstr "" + +#. Tag: para +#: release_notes.xml:123 +#, no-c-format +msgid "#2911, Fix output scale on ST_Rescale/ST_Resample/ST_Resize of rasters with scale 1/-1 and offset 0/0." +msgstr "" + +#. Tag: para +#: release_notes.xml:125 +#, no-c-format +msgid "Fix crash in ST_Union(raster)" +msgstr "" + +#. Tag: para +#: release_notes.xml:126 +#, no-c-format +msgid "#2704, ST_GeomFromGML() does not work properly with array of gml:pos (Even Roualt)" +msgstr "" + +#. Tag: para +#: release_notes.xml:128 +#, no-c-format +msgid "#2708, updategeometrysrid doesn't update srid check when schema not specified. Patch from Marc Jansen" +msgstr "" + +#. Tag: para +#: release_notes.xml:130 +#, no-c-format +msgid "#2720, lwpoly_add_ring should update maxrings after realloc" +msgstr "" + +#. Tag: para +#: release_notes.xml:131 +#, no-c-format +msgid "#2759, Fix postgis_restore.pl handling of multiline object comments embedding sql comments" +msgstr "" + +#. Tag: para +#: release_notes.xml:133 +#, no-c-format +msgid "#2774, fix undefined behavior in ptarray_calculate_gbox_geodetic" +msgstr "" + +#. Tag: para +#: release_notes.xml:134 +#, no-c-format +msgid "Fix potential memory fault in ST_MakeValid" +msgstr "" + +#. Tag: para +#: release_notes.xml:135 +#, no-c-format +msgid "#2784, Fix handling of bogus argument to --with-sfcgal" +msgstr "" + +#. Tag: para +#: release_notes.xml:136 +#, no-c-format +msgid "#2772, Premature memory free in RASTER_getBandPath (ST_BandPath)" +msgstr "" + +#. Tag: para +#: release_notes.xml:137 +#, no-c-format +msgid "#2755, Fix regressions tests against all versions of SFCGAL" +msgstr "" + +#. Tag: para +#: release_notes.xml:138 +#, no-c-format +msgid "#2775, lwline_from_lwmpoint leaks memory" +msgstr "" + +#. Tag: para +#: release_notes.xml:139 +#, no-c-format +msgid "#2802, ST_MapAlgebra checks for valid callback function return value" +msgstr "" + +#. Tag: para +#: release_notes.xml:140 +#, no-c-format +msgid "#2803, ST_MapAlgebra handles no userarg and STRICT callback function" +msgstr "" + +#. Tag: para +#: release_notes.xml:141 +#, no-c-format +msgid "#2834, ST_Estimated_Extent and mixedCase table names (regression bug)" +msgstr "" + +#. Tag: para +#: release_notes.xml:142 +#, no-c-format +msgid "#2845, Bad geometry created from ST_AddPoint" +msgstr "" + +#. Tag: para +#: release_notes.xml:143 +#, no-c-format +msgid "#2870, Binary insert into geography column results geometry being inserted" +msgstr "" + +#. Tag: para +#: release_notes.xml:144 +#, no-c-format +msgid "#2872, make install builds documentation (Greg Troxell)" +msgstr "" + +#. Tag: para +#: release_notes.xml:145 +#, no-c-format +msgid "#2819, find isfinite or replacement on Centos5 / Solaris" +msgstr "" + +#. Tag: para +#: release_notes.xml:146 +#, no-c-format +msgid "#2899, geocode limit 1 not returning best answer (tiger geocoder)" +msgstr "" + +#. Tag: para +#: release_notes.xml:147 +#, no-c-format +msgid "#2903, Unable to compile on FreeBSD" +msgstr "" + +#. Tag: para +#: release_notes.xml:148 +#, no-c-format +msgid "#2927 reverse_geocode not filling in direction prefix (tiger geocoder) get rid of deprecated ST_Line_Locate_Point called" +msgstr "" + +#. Tag: title +#: release_notes.xml:154 +#, no-c-format +msgid "Release 2.1.3" +msgstr "" + +#. Tag: para +#: release_notes.xml:155 +#, no-c-format +msgid "Release date: 2014/05/13" +msgstr "" + +#. Tag: para +#: release_notes.xml:156 +#, no-c-format +msgid "This is a bug fix and security release." +msgstr "" + +#. Tag: title +#: release_notes.xml:158 +#, no-c-format +msgid "Important changes" +msgstr "" + +#. Tag: para +#: release_notes.xml:159 +#, no-c-format +msgid "Starting with this version offline raster access and use of GDAL drivers are disabled by default." +msgstr "" + +#. Tag: para +#: release_notes.xml:164 +#, no-c-format +msgid "An environment variable is introduced to allow for enabling specific GDAL drivers: POSTGIS_GDAL_ENABLED_DRIVERS. By default, all GDAL drivers are disabled" +msgstr "" + +#. Tag: para +#: release_notes.xml:170 +#, no-c-format +msgid "An environment variable is introduced to allow for enabling out-db raster bands: POSTGIS_ENABLE_OUTDB_RASTERS. By default, out-db raster bands are disabled" +msgstr "" + +#. Tag: para +#: release_notes.xml:176 +#, no-c-format +msgid "The environment variables must be set for the PostgreSQL process, and determines the behavior of the whole cluster." +msgstr "" + +#. Tag: para +#: release_notes.xml:183 +#, no-c-format +msgid "#2697, invalid GeoJSON Polygon input crashes server process" +msgstr "" + +#. Tag: para +#: release_notes.xml:184 +#, no-c-format +msgid "#2700, Fix dumping of higher-dimension datasets with null rows" +msgstr "" + +#. Tag: para +#: release_notes.xml:185 +#, no-c-format +msgid "#2706, ST_DumpPoints of EMPTY geometries crashes server" +msgstr "" + +#. Tag: title +#: release_notes.xml:189 +#, no-c-format +msgid "Release 2.1.2" +msgstr "" + +#. Tag: para +#: release_notes.xml:190 release_notes.xml:487 +#, no-c-format +msgid "Release date: 2014/03/31" +msgstr "" + +#. Tag: para +#: release_notes.xml:191 +#, no-c-format +msgid "This is a bug fix release, addressing issues that have been filed since the 2.1.1 release." +msgstr "" + +#. Tag: para +#: release_notes.xml:194 +#, no-c-format +msgid "#2666, Error out at configure time if no SQL preprocessor can be found" +msgstr "" + +#. Tag: para +#: release_notes.xml:195 +#, no-c-format +msgid "#2534, st_distance returning incorrect results for large geographies" +msgstr "" + +#. Tag: para +#: release_notes.xml:196 +#, no-c-format +msgid "#2539, Check for json-c/json.h presence/usability before json/json.h" +msgstr "" + +#. Tag: para +#: release_notes.xml:197 +#, no-c-format +msgid "#2543, invalid join selectivity error from simple query" +msgstr "" + +#. Tag: para +#: release_notes.xml:198 +#, no-c-format +msgid "#2546, GeoJSON with string coordinates parses incorrectly" +msgstr "" + +#. Tag: para +#: release_notes.xml:199 +#, no-c-format +msgid "#2547, Fix ST_Simplify(TopoGeometry) for hierarchical topogeoms" +msgstr "" + +#. Tag: para +#: release_notes.xml:200 release_notes.xml:497 +#, no-c-format +msgid "#2552, Fix NULL raster handling in ST_AsPNG, ST_AsTIFF and ST_AsJPEG" +msgstr "" + +#. Tag: para +#: release_notes.xml:202 release_notes.xml:498 +#, no-c-format +msgid "#2555, Fix parsing issue of range arguments of ST_Reclass" +msgstr "" + +#. Tag: para +#: release_notes.xml:203 +#, no-c-format +msgid "#2556, geography ST_Intersects results depending on insert order" +msgstr "" + +#. Tag: para +#: release_notes.xml:204 +#, no-c-format +msgid "#2580, Do not allow installing postgis twice in the same database" +msgstr "" + +#. Tag: para +#: release_notes.xml:205 release_notes.xml:499 +#, no-c-format +msgid "#2589, Remove use of unnecessary void pointers" +msgstr "" + +#. Tag: para +#: release_notes.xml:206 +#, no-c-format +msgid "#2607, Cannot open more than 1024 out-db files in one process" +msgstr "" + +#. Tag: para +#: release_notes.xml:207 release_notes.xml:501 +#, no-c-format +msgid "#2610, Ensure face splitting algorithm uses the edge index" +msgstr "" + +#. Tag: para +#: release_notes.xml:208 +#, no-c-format +msgid "#2615, EstimatedExtent (and hence, underlying stats) gathering wrong bbox" +msgstr "" + +#. Tag: para +#: release_notes.xml:209 +#, no-c-format +msgid "#2619, Empty rings array in GeoJSON polygon causes crash" +msgstr "" + +#. Tag: para +#: release_notes.xml:210 +#, no-c-format +msgid "#2634, regression in sphere distance code" +msgstr "" + +#. Tag: para +#: release_notes.xml:211 release_notes.xml:503 +#, no-c-format +msgid "#2638, Geography distance on M geometries sometimes wrong" +msgstr "" + +#. Tag: para +#: release_notes.xml:212 +#, no-c-format +msgid "#2648, #2653, Fix topology functions when \"topology\" is not in search_path" +msgstr "" + +#. Tag: para +#: release_notes.xml:213 +#, no-c-format +msgid "#2654, Drop deprecated calls from topology" +msgstr "" + +#. Tag: para +#: release_notes.xml:214 +#, no-c-format +msgid "#2655, Let users without topology privileges call postgis_full_version()" +msgstr "" + +#. Tag: para +#: release_notes.xml:215 +#, no-c-format +msgid "#2674, Fix missing operator = and hash_raster_ops opclass on raster" +msgstr "" + +#. Tag: para +#: release_notes.xml:216 +#, no-c-format +msgid "#2675, #2534, #2636, #2634, #2638, Geography distance issues with tree optimization" +msgstr "" + +#. Tag: para +#: release_notes.xml:220 +#, no-c-format +msgid "#2494, avoid memcopy in GiST index (hayamiz)" +msgstr "" + +#. Tag: para +#: release_notes.xml:221 +#, no-c-format +msgid "#2560, soft upgrade: avoid drop/recreate of aggregates that hadn't changed" +msgstr "" + +#. Tag: title +#: release_notes.xml:226 +#, no-c-format +msgid "Release 2.1.1" +msgstr "" + +#. Tag: para +#: release_notes.xml:227 +#, no-c-format +msgid "Release date: 2013/11/06" +msgstr "" + +#. Tag: para +#: release_notes.xml:228 +#, no-c-format +msgid "This is a bug fix release, addressing issues that have been filed since the 2.1.0 release." +msgstr "" + +#. Tag: title +#: release_notes.xml:230 release_notes.xml:506 +#, no-c-format +msgid "Important Changes" +msgstr "" + +#. Tag: para +#: release_notes.xml:231 +#, no-c-format +msgid "#2514, Change raster license from GPL v3+ to v2+, allowing distribution of PostGIS Extension as GPLv2." +msgstr "" + +#. Tag: para +#: release_notes.xml:235 +#, no-c-format +msgid "#2396, Make regression tests more endian-agnostic" +msgstr "" + +#. Tag: para +#: release_notes.xml:236 +#, no-c-format +msgid "#2434, Fix ST_Intersection(geog,geog) regression in rare cases" +msgstr "" + +#. Tag: para +#: release_notes.xml:237 +#, no-c-format +msgid "#2454, Fix behavior of ST_PixelAsXXX functions regarding exclude_nodata_value parameter" +msgstr "" + +#. Tag: para +#: release_notes.xml:238 +#, no-c-format +msgid "#2489, Fix upgrades from 2.0 leaving stale function signatures" +msgstr "" + +#. Tag: para +#: release_notes.xml:239 +#, no-c-format +msgid "#2525, Fix handling of SRID in nested collections" +msgstr "" + +#. Tag: para +#: release_notes.xml:240 +#, no-c-format +msgid "#2449, Fix potential infinite loop in index building" +msgstr "" + +#. Tag: para +#: release_notes.xml:241 +#, no-c-format +msgid "#2493, Fix behavior of ST_DumpValues when passed an empty raster" +msgstr "" + +#. Tag: para +#: release_notes.xml:242 release_notes.xml:492 +#, no-c-format +msgid "#2502, Fix postgis_topology_scripts_installed() install schema" +msgstr "" + +#. Tag: para +#: release_notes.xml:243 release_notes.xml:493 +#, no-c-format +msgid "#2504, Fix segfault on bogus pgsql2shp call" +msgstr "" + +#. Tag: para +#: release_notes.xml:244 +#, no-c-format +msgid "#2512, Support for foreign tables and materialized views in raster_columns and raster_overviews" +msgstr "" + +#. Tag: para +#: release_notes.xml:248 +#, no-c-format +msgid "#2478, support for tiger 2013" +msgstr "" + +#. Tag: para +#: release_notes.xml:249 +#, no-c-format +msgid "#2463, support for exact length calculations on arc geometries" +msgstr "" + +#. Tag: title +#: release_notes.xml:255 +#, no-c-format +msgid "Release 2.1.0" +msgstr "" + +#. Tag: para +#: release_notes.xml:256 +#, no-c-format +msgid "Release date: 2013/08/17" +msgstr "" + +#. Tag: para +#: release_notes.xml:257 +#, no-c-format +msgid "This is a minor release addressing both bug fixes and performance and functionality enhancements addressing issues since 2.0.3 release. If you are upgrading from 2.0+, only a soft upgrade is required. If you are upgrading from 1.5 or earlier, a hard upgrade is required." +msgstr "" + +#. Tag: title +#: release_notes.xml:260 release_notes.xml:729 +#, no-c-format +msgid "Important / Breaking Changes" +msgstr "" + +#. Tag: para +#: release_notes.xml:261 +#, no-c-format +msgid "#1653, Removed srid parameter from ST_Resample(raster) and variants with reference raster no longer apply reference raster's SRID." +msgstr "" + +#. Tag: para +#: release_notes.xml:263 +#, no-c-format +msgid "#1962 ST_Segmentize - As a result of the introduction of geography support, The construct: SELECT ST_Segmentize('LINESTRING(1 2, 3 4)',0.5); will result in ambiguous function error" +msgstr "" + +#. Tag: para +#: release_notes.xml:267 +#, no-c-format +msgid "#2026, ST_Union(raster) now unions all bands of all rasters" +msgstr "" + +#. Tag: para +#: release_notes.xml:268 +#, no-c-format +msgid "#2089, liblwgeom: lwgeom_set_handlers replaces lwgeom_init_allocators." +msgstr "" + +#. Tag: para +#: release_notes.xml:269 +#, no-c-format +msgid "#2150, regular_blocking is no longer a constraint. column of same name in raster_columns now checks for existance of spatially_unique and coverage_tile constraints" +msgstr "" + +#. Tag: para +#: release_notes.xml:272 +#, no-c-format +msgid "ST_Intersects(raster, geometry) behaves in the same manner as ST_Intersects(geometry, raster)." +msgstr "" + +#. Tag: para +#: release_notes.xml:274 +#, no-c-format +msgid "point variant of ST_SetValue(raster) previously did not check SRID of input geometry and raster." +msgstr "" + +#. Tag: para +#: release_notes.xml:276 +#, no-c-format +msgid "ST_Hillshade parameters azimuth and altitude are now in degrees instead of radians." +msgstr "" + +#. Tag: para +#: release_notes.xml:278 +#, no-c-format +msgid "ST_Slope and ST_Aspect return pixel values in degrees instead of radians." +msgstr "" + +#. Tag: para +#: release_notes.xml:279 +#, no-c-format +msgid "#2104, ST_World2RasterCoord, ST_World2RasterCoordX and ST_World2RasterCoordY renamed to ST_WorldToRasterCoord, ST_WorldToRasterCoordX and ST_WorldToRasterCoordY. ST_Raster2WorldCoord, ST_Raster2WorldCoordX and ST_Raster2WorldCoordY renamed to ST_RasterToWorldCoord, ST_RasterToWorldCoordX and ST_RasterToWorldCoordY" +msgstr "" + +#. Tag: para +#: release_notes.xml:285 +#, no-c-format +msgid "ST_Estimated_Extent renamed to ST_EstimatedExtent" +msgstr "" + +#. Tag: para +#: release_notes.xml:286 +#, no-c-format +msgid "ST_Line_Interpolate_Point renamed to ST_LineInterpolatePoint" +msgstr "" + +#. Tag: para +#: release_notes.xml:287 +#, no-c-format +msgid "ST_Line_Substring renamed to ST_LineSubstring" +msgstr "" + +#. Tag: para +#: release_notes.xml:288 +#, no-c-format +msgid "ST_Line_Locate_Point renamed to ST_LineLocatePoint" +msgstr "" + +#. Tag: para +#: release_notes.xml:289 +#, no-c-format +msgid "ST_Force_XXX renamed to ST_ForceXXX" +msgstr "" + +#. Tag: para +#: release_notes.xml:290 +#, no-c-format +msgid "ST_MapAlgebraFctNgb and 1 and 2 raster variants of ST_MapAlgebraFct. Use ST_MapAlgebra instead" +msgstr "" + +#. Tag: para +#: release_notes.xml:292 +#, no-c-format +msgid "1 and 2 raster variants of ST_MapAlgebraExpr. Use expression variants of ST_MapAlgebra instead" +msgstr "" + +#. Tag: para +#: release_notes.xml:298 +#, no-c-format +msgid "- Refer to http://postgis.net/docs/manual-2.1/PostGIS_Special_Functions_Index.html#NewFunctions_2_1 for complete list of new functions" +msgstr "" + +#. Tag: para +#: release_notes.xml:300 +#, no-c-format +msgid "#310, ST_DumpPoints converted to a C function (Nathan Wagner) and much faster" +msgstr "" + +#. Tag: para +#: release_notes.xml:301 +#, no-c-format +msgid "#739, UpdateRasterSRID()" +msgstr "" + +#. Tag: para +#: release_notes.xml:302 +#, no-c-format +msgid "#945, improved join selectivity, N-D selectivity calculations, user accessible selectivity and stats reader functions for testing (Paul Ramsey / OpenGeo)" +msgstr "" + +#. Tag: para +#: release_notes.xml:305 +#, no-c-format +msgid "toTopoGeom with TopoGeometry sink (Sandro Santilli / Vizzuality)" +msgstr "" + +#. Tag: para +#: release_notes.xml:306 +#, no-c-format +msgid "clearTopoGeom (Sandro Santilli / Vizzuality)" +msgstr "" + +#. Tag: para +#: release_notes.xml:307 +#, no-c-format +msgid "ST_Segmentize(geography) (Paul Ramsey / OpenGeo)" +msgstr "" + +#. Tag: para +#: release_notes.xml:308 +#, no-c-format +msgid "ST_DelaunayTriangles (Sandro Santilli / Vizzuality)" +msgstr "" + +#. Tag: para +#: release_notes.xml:309 +#, no-c-format +msgid "ST_NearestValue, ST_Neighborhood (Bborie Park / UC Davis)" +msgstr "" + +#. Tag: para +#: release_notes.xml:310 +#, no-c-format +msgid "ST_PixelAsPoint, ST_PixelAsPoints (Bborie Park / UC Davis)" +msgstr "" + +#. Tag: para +#: release_notes.xml:311 +#, no-c-format +msgid "ST_PixelAsCentroid, ST_PixelAsCentroids (Bborie Park / UC Davis)" +msgstr "" + +#. Tag: para +#: release_notes.xml:312 +#, no-c-format +msgid "ST_Raster2WorldCoord, ST_World2RasterCoord (Bborie Park / UC Davis)" +msgstr "" + +#. Tag: para +#: release_notes.xml:313 +#, no-c-format +msgid "Additional raster/raster spatial relationship functions (ST_Contains, ST_ContainsProperly, ST_Covers, ST_CoveredBy, ST_Disjoint, ST_Overlaps, ST_Touches, ST_Within, ST_DWithin, ST_DFullyWithin) (Bborie Park / UC Davis)" +msgstr "" + +#. Tag: para +#: release_notes.xml:317 +#, no-c-format +msgid "Added array variants of ST_SetValues() to set many pixel values of a band in one call (Bborie Park / UC Davis)" +msgstr "" + +#. Tag: para +#: release_notes.xml:319 +#, no-c-format +msgid "#1293, ST_Resize(raster) to resize rasters based upon width/height" +msgstr "" + +#. Tag: para +#: release_notes.xml:320 +#, no-c-format +msgid "#1627, package tiger_geocoder as a PostgreSQL extension" +msgstr "" + +#. Tag: para +#: release_notes.xml:321 +#, no-c-format +msgid "#1643, #2076, Upgrade tiger geocoder to support loading tiger 2011 and 2012 (Regina Obe / Paragon Corporation) Funded by Hunter Systems Group" +msgstr "" + +#. Tag: para +#: release_notes.xml:323 +#, no-c-format +msgid "GEOMETRYCOLLECTION support for ST_MakeValid (Sandro Santilli / Vizzuality)" +msgstr "" + +#. Tag: para +#: release_notes.xml:324 +#, no-c-format +msgid "#1709, ST_NotSameAlignmentReason(raster, raster)" +msgstr "" + +#. Tag: para +#: release_notes.xml:325 +#, no-c-format +msgid "#1818, ST_GeomFromGeoHash and friends (Jason Smith (darkpanda))" +msgstr "" + +#. Tag: para +#: release_notes.xml:326 +#, no-c-format +msgid "#1856, reverse geocoder rating setting for prefer numbered highway name" +msgstr "" + +#. Tag: para +#: release_notes.xml:327 +#, no-c-format +msgid "ST_PixelOfValue (Bborie Park / UC Davis)" +msgstr "" + +#. Tag: para +#: release_notes.xml:328 +#, no-c-format +msgid "Casts to/from PostgreSQL geotypes (point/path/polygon)." +msgstr "" + +#. Tag: para +#: release_notes.xml:329 +#, no-c-format +msgid "Added geomval array variant of ST_SetValues() to set many pixel values of a band using a set of geometries and corresponding values in one call (Bborie Park / UC Davis)" +msgstr "" + +#. Tag: para +#: release_notes.xml:332 +#, no-c-format +msgid "ST_Tile(raster) to break up a raster into tiles (Bborie Park / UC Davis)" +msgstr "" + +#. Tag: para +#: release_notes.xml:333 +#, no-c-format +msgid "#1895, new r-tree node splitting algorithm (Alex Korotkov)" +msgstr "" + +#. Tag: para +#: release_notes.xml:334 +#, no-c-format +msgid "#2011, ST_DumpValues to output raster as array (Bborie Park / UC Davis)" +msgstr "" + +#. Tag: para +#: release_notes.xml:335 +#, no-c-format +msgid "#2018, ST_Distance support for CircularString, CurvePolygon, MultiCurve, MultiSurface, CompoundCurve" +msgstr "" + +#. Tag: para +#: release_notes.xml:337 +#, no-c-format +msgid "#2030, n-raster (and n-band) ST_MapAlgebra (Bborie Park / UC Davis)" +msgstr "" + +#. Tag: para +#: release_notes.xml:338 +#, no-c-format +msgid "#2193, Utilize PAGC parser as drop in replacement for tiger normalizer (Steve Woodbridge, Regina Obe)" +msgstr "" + +#. Tag: para +#: release_notes.xml:340 +#, no-c-format +msgid "#2210, ST_MinConvexHull(raster)" +msgstr "" + +#. Tag: para +#: release_notes.xml:341 +#, no-c-format +msgid "lwgeom_from_geojson in liblwgeom (Sandro Santilli / Vizzuality)" +msgstr "" + +#. Tag: para +#: release_notes.xml:342 +#, no-c-format +msgid "#1687, ST_Simplify for TopoGeometry (Sandro Santilli / Vizzuality)" +msgstr "" + +#. Tag: para +#: release_notes.xml:343 +#, no-c-format +msgid "#2228, TopoJSON output for TopoGeometry (Sandro Santilli / Vizzuality)" +msgstr "" + +#. Tag: para +#: release_notes.xml:344 +#, no-c-format +msgid "#2123, ST_FromGDALRaster" +msgstr "" + +#. Tag: para +#: release_notes.xml:345 +#, no-c-format +msgid "#613, ST_SetGeoReference with numerical parameters instead of text" +msgstr "" + +#. Tag: para +#: release_notes.xml:346 +#, no-c-format +msgid "#2276, ST_AddBand(raster) variant for out-db bands" +msgstr "" + +#. Tag: para +#: release_notes.xml:347 +#, no-c-format +msgid "#2280, ST_Summary(raster)" +msgstr "" + +#. Tag: para +#: release_notes.xml:348 +#, no-c-format +msgid "#2163, ST_TPI for raster (Nathaniel Clay)" +msgstr "" + +#. Tag: para +#: release_notes.xml:349 +#, no-c-format +msgid "#2164, ST_TRI for raster (Nathaniel Clay)" +msgstr "" + +#. Tag: para +#: release_notes.xml:350 +#, no-c-format +msgid "#2302, ST_Roughness for raster (Nathaniel Clay)" +msgstr "" + +#. Tag: para +#: release_notes.xml:351 +#, no-c-format +msgid "#2290, ST_ColorMap(raster) to generate RGBA bands" +msgstr "" + +#. Tag: para +#: release_notes.xml:352 +#, no-c-format +msgid "#2254, Add SFCGAL backend support. (Backend selection throught postgis.backend var) Functions available both throught GEOS or SFCGAL: ST_Intersects, ST_3DIntersects, ST_Intersection, ST_Area, ST_Distance, ST_3DDistance New functions available only with SFCGAL backend: ST_3DIntersection, ST_Tesselate, ST_3DArea, ST_Extrude, ST_ForceLHR ST_Orientation, ST_Minkowski, ST_StraightSkeleton postgis_sfcgal_version New function available in PostGIS: ST_ForceSFS (Olivier Courtin and Hugo Mercier / Oslandia)" +msgstr "" + +#. Tag: para +#: release_notes.xml:367 +#, no-c-format +msgid "For detail of new functions and function improvements, please refer to ." +msgstr "" + +#. Tag: para +#: release_notes.xml:368 +#, no-c-format +msgid "Much faster raster ST_Union, ST_Clip and many more function additions operations" +msgstr "" + +#. Tag: para +#: release_notes.xml:369 +#, no-c-format +msgid "For geometry/geography better planner selectivity and a lot more functions." +msgstr "" + +#. Tag: para +#: release_notes.xml:371 +#, no-c-format +msgid "#823, tiger geocoder: Make loader_generate_script download portion less greedy" +msgstr "" + +#. Tag: para +#: release_notes.xml:373 +#, no-c-format +msgid "#826, raster2pgsql no longer defaults to padding tiles. Flag -P can be used to pad tiles" +msgstr "" + +#. Tag: para +#: release_notes.xml:375 +#, no-c-format +msgid "#1363, ST_AddBand(raster, ...) array version rewritten in C" +msgstr "" + +#. Tag: para +#: release_notes.xml:376 +#, no-c-format +msgid "#1364, ST_Union(raster, ...) aggregate function rewritten in C" +msgstr "" + +#. Tag: para +#: release_notes.xml:377 +#, no-c-format +msgid "#1655, Additional default values for parameters of ST_Slope" +msgstr "" + +#. Tag: para +#: release_notes.xml:378 +#, no-c-format +msgid "#1661, Add aggregate variant of ST_SameAlignment" +msgstr "" + +#. Tag: para +#: release_notes.xml:379 +#, no-c-format +msgid "#1719, Add support for Point and GeometryCollection ST_MakeValid inputs" +msgstr "" + +#. Tag: para +#: release_notes.xml:380 +#, no-c-format +msgid "#1780, support ST_GeoHash for geography" +msgstr "" + +#. Tag: para +#: release_notes.xml:381 +#, no-c-format +msgid "#1796, Big performance boost for distance calculations in geography" +msgstr "" + +#. Tag: para +#: release_notes.xml:382 +#, no-c-format +msgid "#1802, improved function interruptibility." +msgstr "" + +#. Tag: para +#: release_notes.xml:383 +#, no-c-format +msgid "#1823, add parameter in ST_AsGML to use id column for GML 3 output (become mandatory since GML 3.2.1)" +msgstr "" + +#. Tag: para +#: release_notes.xml:385 +#, no-c-format +msgid "#1856, tiger geocoder: reverse geocoder rating setting for prefer numbered highway name" +msgstr "" + +#. Tag: para +#: release_notes.xml:387 +#, no-c-format +msgid "#1938, Refactor basic ST_AddBand to add multiple new bands in one call" +msgstr "" + +#. Tag: para +#: release_notes.xml:388 +#, no-c-format +msgid "#1978, wrong answer when calculating length of a closed circular arc (circle)" +msgstr "" + +#. Tag: para +#: release_notes.xml:390 release_notes.xml:600 +#, no-c-format +msgid "#1989, Preprocess input geometry to just intersection with raster to be clipped" +msgstr "" + +#. Tag: para +#: release_notes.xml:392 +#, no-c-format +msgid "#2021, Added multi-band support to ST_Union(raster, ...) aggregate function" +msgstr "" + +#. Tag: para +#: release_notes.xml:393 +#, no-c-format +msgid "#2006, better support of ST_Area(geography) over poles and dateline" +msgstr "" + +#. Tag: para +#: release_notes.xml:394 +#, no-c-format +msgid "#2065, ST_Clip(raster, ...) now a C function" +msgstr "" + +#. Tag: para +#: release_notes.xml:395 +#, no-c-format +msgid "#2069, Added parameters to ST_Tile(raster) to control padding of tiles" +msgstr "" + +#. Tag: para +#: release_notes.xml:396 +#, no-c-format +msgid "#2078, New variants of ST_Slope, ST_Aspect and ST_HillShade to provide solution to handling tiles in a coverage" +msgstr "" + +#. Tag: para +#: release_notes.xml:398 +#, no-c-format +msgid "#2097, Added RANGE uniontype option for ST_Union(raster)" +msgstr "" + +#. Tag: para +#: release_notes.xml:399 +#, no-c-format +msgid "#2105, Added ST_Transform(raster) variant for aligning output to reference raster" +msgstr "" + +#. Tag: para +#: release_notes.xml:401 +#, no-c-format +msgid "#2119, Rasters passed to ST_Resample(), ST_Rescale(), ST_Reskew(), and ST_SnapToGrid() no longer require an SRID" +msgstr "" + +#. Tag: para +#: release_notes.xml:403 release_notes.xml:573 +#, no-c-format +msgid "#2141, More verbose output when constraints fail to be added to a raster column" +msgstr "" + +#. Tag: para +#: release_notes.xml:405 +#, no-c-format +msgid "#2143, Changed blocksize constraint of raster to allow multiple values" +msgstr "" + +#. Tag: para +#: release_notes.xml:406 +#, no-c-format +msgid "#2148, Addition of coverage_tile constraint for raster" +msgstr "" + +#. Tag: para +#: release_notes.xml:407 +#, no-c-format +msgid "#2149, Addition of spatially_unique constraint for raster" +msgstr "" + +#. Tag: para +#: release_notes.xml:408 +#, no-c-format +msgid "TopologySummary output now includes unregistered layers and a count of missing TopoGeometry objects from their natural layer." +msgstr "" + +#. Tag: para +#: release_notes.xml:410 +#, no-c-format +msgid "ST_HillShade(), ST_Aspect() and ST_Slope() have one new optional parameter to interpolate NODATA pixels before running the operation." +msgstr "" + +#. Tag: para +#: release_notes.xml:413 +#, no-c-format +msgid "Point variant of ST_SetValue(raster) is now a wrapper around geomval variant of ST_SetValues(rast)." +msgstr "" + +#. Tag: para +#: release_notes.xml:415 +#, no-c-format +msgid "Proper support for raster band's isnodata flag in core API and loader." +msgstr "" + +#. Tag: para +#: release_notes.xml:416 +#, no-c-format +msgid "Additional default values for parameters of ST_Aspect and ST_HillShade" +msgstr "" + +#. Tag: para +#: release_notes.xml:417 +#, no-c-format +msgid "#2178, ST_Summary now advertises presence of known srid with an [S] flag" +msgstr "" + +#. Tag: para +#: release_notes.xml:418 +#, no-c-format +msgid "#2202, Make libjson-c optional (--without-json configure switch)" +msgstr "" + +#. Tag: para +#: release_notes.xml:419 +#, no-c-format +msgid "#2213, Add support libjson-c 0.10+" +msgstr "" + +#. Tag: para +#: release_notes.xml:420 +#, no-c-format +msgid "#2231, raster2pgsql supports user naming of filename column with -n" +msgstr "" + +#. Tag: para +#: release_notes.xml:421 +#, no-c-format +msgid "#2200, ST_Union(raster, uniontype) unions all bands of all rasters" +msgstr "" + +#. Tag: para +#: release_notes.xml:422 +#, no-c-format +msgid "#2264, postgis_restore.pl support for restoring into databases with postgis in a custom schema" +msgstr "" + +#. Tag: para +#: release_notes.xml:424 +#, no-c-format +msgid "#2244, emit warning when changing raster's georeference if raster has out-db bands" +msgstr "" + +#. Tag: para +#: release_notes.xml:426 +#, no-c-format +msgid "#2222, add parameter OutAsIn to flag whether ST_AsBinary should return out-db bands as in-db bands" +msgstr "" + +#. Tag: title +#: release_notes.xml:430 +#, no-c-format +msgid "Fixes" +msgstr "" + +#. Tag: para +#: release_notes.xml:431 release_notes.xml:675 +#, no-c-format +msgid "#1839, handling of subdatasets in GeoTIFF in raster2pgsql." +msgstr "" + +#. Tag: para +#: release_notes.xml:432 release_notes.xml:676 +#, no-c-format +msgid "#1840, fix logic of when to compute # of tiles in raster2pgsql." +msgstr "" + +#. Tag: para +#: release_notes.xml:433 +#, no-c-format +msgid "#1870, align the docs and actual behavior of raster's ST_Intersects" +msgstr "" + +#. Tag: para +#: release_notes.xml:434 release_notes.xml:682 +#, no-c-format +msgid "#1872, fix ST_ApproxSummarystats to prevent division by zero" +msgstr "" + +#. Tag: para +#: release_notes.xml:435 release_notes.xml:685 +#, no-c-format +msgid "#1875, ST_SummaryStats returns NULL for all parameters except count when count is zero" +msgstr "" + +#. Tag: para +#: release_notes.xml:437 +#, no-c-format +msgid "#1932, fix raster2pgsql of syntax for index tablespaces" +msgstr "" + +#. Tag: para +#: release_notes.xml:438 release_notes.xml:593 +#, no-c-format +msgid "#1936, ST_GeomFromGML on CurvePolygon causes server crash" +msgstr "" + +#. Tag: para +#: release_notes.xml:439 +#, no-c-format +msgid "#1939, remove custom data types: summarystats, histogram, quantile, valuecount" +msgstr "" + +#. Tag: para +#: release_notes.xml:441 +#, no-c-format +msgid "#1951, remove crash on zero-length linestrings" +msgstr "" + +#. Tag: para +#: release_notes.xml:442 release_notes.xml:595 +#, no-c-format +msgid "#1957, ST_Distance to a one-point LineString returns NULL" +msgstr "" + +#. Tag: para +#: release_notes.xml:443 release_notes.xml:596 +#, no-c-format +msgid "#1976, Geography point-in-ring code overhauled for more reliability" +msgstr "" + +#. Tag: para +#: release_notes.xml:444 +#, no-c-format +msgid "#1981, cleanup of unused variables causing warnings with gcc 4.6+" +msgstr "" + +#. Tag: para +#: release_notes.xml:445 release_notes.xml:603 +#, no-c-format +msgid "#1996, support POINT EMPTY in GeoJSON output" +msgstr "" + +#. Tag: para +#: release_notes.xml:446 +#, no-c-format +msgid "#2062, improve performance of distance calculations" +msgstr "" + +#. Tag: para +#: release_notes.xml:447 release_notes.xml:614 +#, no-c-format +msgid "#2057, Fixed linking issue for raster2psql to libpq" +msgstr "" + +#. Tag: para +#: release_notes.xml:448 +#, no-c-format +msgid "#2077, Fixed incorrect values returning from ST_Hillshade()" +msgstr "" + +#. Tag: para +#: release_notes.xml:449 release_notes.xml:607 +#, no-c-format +msgid "#2019, ST_FlipCoordinates does not update bbox" +msgstr "" + +#. Tag: para +#: release_notes.xml:450 +#, no-c-format +msgid "#2100, ST_AsRaster may not return raster with specified pixel type" +msgstr "" + +#. Tag: para +#: release_notes.xml:451 release_notes.xml:559 +#, no-c-format +msgid "#2126, Better handling of empty rasters from ST_ConvexHull()" +msgstr "" + +#. Tag: para +#: release_notes.xml:452 release_notes.xml:520 +#, no-c-format +msgid "#2165, ST_NumPoints regression failure with CircularString" +msgstr "" + +#. Tag: para +#: release_notes.xml:453 release_notes.xml:521 +#, no-c-format +msgid "#2168, ST_Distance is not always commutative" +msgstr "" + +#. Tag: para +#: release_notes.xml:454 +#, no-c-format +msgid "#2182, Fix issue with outdb rasters with no SRID and ST_Resize" +msgstr "" + +#. Tag: para +#: release_notes.xml:455 release_notes.xml:567 +#, no-c-format +msgid "#2188, Fix function parameter value overflow that caused problems when copying data from a GDAL dataset" +msgstr "" + +#. Tag: para +#: release_notes.xml:457 +#, no-c-format +msgid "#2198, Fix incorrect dimensions used when generating bands of out-db rasters in ST_Tile()" +msgstr "" + +#. Tag: para +#: release_notes.xml:459 release_notes.xml:523 +#, no-c-format +msgid "#2201, ST_GeoHash wrong on boundaries" +msgstr "" + +#. Tag: para +#: release_notes.xml:460 +#, no-c-format +msgid "#2203, Changed how rasters with unknown SRID and default geotransform are handled when passing to GDAL Warp API" +msgstr "" + +#. Tag: para +#: release_notes.xml:462 +#, no-c-format +msgid "#2215, Fixed raster exclusion constraint for conflicting name of implicit index" +msgstr "" + +#. Tag: para +#: release_notes.xml:464 +#, no-c-format +msgid "#2251, Fix bad dimensions when rescaling rasters with default geotransform matrix" +msgstr "" + +#. Tag: para +#: release_notes.xml:466 +#, no-c-format +msgid "#2133, Fix performance regression in expression variant of ST_MapAlgebra" +msgstr "" + +#. Tag: para +#: release_notes.xml:467 release_notes.xml:524 +#, no-c-format +msgid "#2257, GBOX variables not initialized when testing with empty geometries" +msgstr "" + +#. Tag: para +#: release_notes.xml:468 release_notes.xml:525 +#, no-c-format +msgid "#2271, Prevent parallel make of raster" +msgstr "" + +#. Tag: para +#: release_notes.xml:469 +#, no-c-format +msgid "#2282, Fix call to undefined function nd_stats_to_grid() in debug mode" +msgstr "" + +#. Tag: para +#: release_notes.xml:470 release_notes.xml:528 +#, no-c-format +msgid "#2307, ST_MakeValid outputs invalid geometries" +msgstr "" + +#. Tag: para +#: release_notes.xml:471 +#, no-c-format +msgid "#2309, Remove confusing INFO message when trying to get SRS info" +msgstr "" + +#. Tag: para +#: release_notes.xml:472 +#, no-c-format +msgid "#2336, FIPS 20 (KS) causes wildcard expansion to wget all files" +msgstr "" + +#. Tag: para +#: release_notes.xml:473 +#, no-c-format +msgid "#2348, Provide raster upgrade path for 2.0 to 2.1" +msgstr "" + +#. Tag: para +#: release_notes.xml:474 release_notes.xml:529 +#, no-c-format +msgid "#2351, st_distance between geographies wrong" +msgstr "" + +#. Tag: para +#: release_notes.xml:475 +#, no-c-format +msgid "#2359, Fix handling of schema name when adding overview constraints" +msgstr "" + +#. Tag: para +#: release_notes.xml:476 release_notes.xml:531 +#, no-c-format +msgid "#2371, Support GEOS versions with more than 1 digit in micro" +msgstr "" + +#. Tag: para +#: release_notes.xml:477 +#, no-c-format +msgid "#2383, Remove unsafe use of \\' from raster warning message" +msgstr "" + +#. Tag: para +#: release_notes.xml:478 +#, no-c-format +msgid "#2384, Incorrect variable datatypes for ST_Neighborhood" +msgstr "" + +#. Tag: title +#: release_notes.xml:480 release_notes.xml:548 +#, no-c-format +msgid "Known Issues" +msgstr "" + +#. Tag: para +#: release_notes.xml:481 release_notes.xml:549 +#, no-c-format +msgid "#2111, Raster bands can only reference the first 256 bands of out-db rasters" +msgstr "" + +#. Tag: title +#: release_notes.xml:486 +#, no-c-format +msgid "Release 2.0.5" +msgstr "" + +#. Tag: para +#: release_notes.xml:488 +#, no-c-format +msgid "This is a bug fix release, addressing issues that have been filed since the 2.0.4 release. If you are using PostGIS 2.0+ a soft upgrade is required. For users of PostGIS 1.5 or below, a hard upgrade is required." +msgstr "" + +#. Tag: para +#: release_notes.xml:491 +#, no-c-format +msgid "#2494, avoid memcpy in GIST index" +msgstr "" + +#. Tag: para +#: release_notes.xml:494 +#, no-c-format +msgid "#2528, Fix memory leak in ST_Split / lwline_split_by_line" +msgstr "" + +#. Tag: para +#: release_notes.xml:495 +#, no-c-format +msgid "#2532, Add missing raster/geometry commutator operators" +msgstr "" + +#. Tag: para +#: release_notes.xml:496 +#, no-c-format +msgid "#2533, Remove duplicated signatures" +msgstr "" + +#. Tag: para +#: release_notes.xml:500 +#, no-c-format +msgid "#2607, Cannot open more than 1024 out-db files in process" +msgstr "" + +#. Tag: para +#: release_notes.xml:502 +#, no-c-format +msgid "#2619, Empty ring array in GeoJSON polygon causes crash" +msgstr "" + +#. Tag: para +#: release_notes.xml:507 +#, no-c-format +msgid "##2514, Change raster license from GPL v3+ to v2+, allowing distribution of PostGIS Extension as GPLv2." +msgstr "" + +#. Tag: title +#: release_notes.xml:512 +#, no-c-format +msgid "Release 2.0.4" +msgstr "" + +#. Tag: para +#: release_notes.xml:513 +#, no-c-format +msgid "Release date: 2013/09/06" +msgstr "" + +#. Tag: para +#: release_notes.xml:514 +#, no-c-format +msgid "This is a bug fix release, addressing issues that have been filed since the 2.0.3 release. If you are using PostGIS 2.0+ a soft upgrade is required. For users of PostGIS 1.5 or below, a hard upgrade is required." +msgstr "" + +#. Tag: para +#: release_notes.xml:517 +#, no-c-format +msgid "#2110, Equality operator between EMPTY and point on origin" +msgstr "" + +#. Tag: para +#: release_notes.xml:518 +#, no-c-format +msgid "Allow adding points at precision distance with TopoGeo_addPoint" +msgstr "" + +#. Tag: para +#: release_notes.xml:519 +#, no-c-format +msgid "#1968, Fix missing edge from toTopoGeom return" +msgstr "" + +#. Tag: para +#: release_notes.xml:522 +#, no-c-format +msgid "#2186, gui progress bar updates too frequent" +msgstr "" + +#. Tag: para +#: release_notes.xml:526 +#, no-c-format +msgid "#2267, Server crash from analyze table" +msgstr "" + +#. Tag: para +#: release_notes.xml:527 +#, no-c-format +msgid "#2277, potential segfault removed" +msgstr "" + +#. Tag: para +#: release_notes.xml:530 +#, no-c-format +msgid "#2359, Incorrect handling of schema for overview constraints" +msgstr "" + +#. Tag: para +#: release_notes.xml:532 +#, no-c-format +msgid "#2372, Cannot parse space-padded KML coordinates" +msgstr "" + +#. Tag: para +#: release_notes.xml:533 +#, no-c-format +msgid "Fix build with systemwide liblwgeom installed" +msgstr "" + +#. Tag: para +#: release_notes.xml:534 +#, no-c-format +msgid "#2383, Fix unsafe use of \\' in warning message" +msgstr "" + +#. Tag: para +#: release_notes.xml:535 +#, no-c-format +msgid "#2410, Fix segmentize of collinear curve" +msgstr "" + +#. Tag: para +#: release_notes.xml:536 +#, no-c-format +msgid "#2412, ST_LineToCurve support for lines with less than 4 vertices" +msgstr "" + +#. Tag: para +#: release_notes.xml:537 +#, no-c-format +msgid "#2415, ST_Multi support for COMPOUNDCURVE and CURVEPOLYGON" +msgstr "" + +#. Tag: para +#: release_notes.xml:538 +#, no-c-format +msgid "#2420, ST_LineToCurve: require at least 8 edges to define a full circle" +msgstr "" + +#. Tag: para +#: release_notes.xml:539 +#, no-c-format +msgid "#2423, ST_LineToCurve: require all arc edges to form the same angle" +msgstr "" + +#. Tag: para +#: release_notes.xml:540 +#, no-c-format +msgid "#2424, ST_CurveToLine: add support for COMPOUNDCURVE in MULTICURVE" +msgstr "" + +#. Tag: para +#: release_notes.xml:541 +#, no-c-format +msgid "#2427, Make sure to retain first point of curves on ST_CurveToLine" +msgstr "" + +#. Tag: para +#: release_notes.xml:545 +#, no-c-format +msgid "#2269, Avoid uselessly detoasting full geometries on ANALYZE" +msgstr "" + +#. Tag: title +#: release_notes.xml:554 +#, no-c-format +msgid "Release 2.0.3" +msgstr "" + +#. Tag: para +#: release_notes.xml:555 +#, no-c-format +msgid "Release date: 2013/03/01" +msgstr "" + +#. Tag: para +#: release_notes.xml:556 +#, no-c-format +msgid "This is a bug fix release, addressing issues that have been filed since the 2.0.2 release. If you are using PostGIS 2.0+ a soft upgrade is required. For users of PostGIS 1.5 or below, a hard upgrade is required." +msgstr "" + +#. Tag: para +#: release_notes.xml:560 +#, no-c-format +msgid "#2134, Make sure to process SRS before passing it off to GDAL functions" +msgstr "" + +#. Tag: para +#: release_notes.xml:561 +#, no-c-format +msgid "Fix various memory leaks in liblwgeom" +msgstr "" + +#. Tag: para +#: release_notes.xml:562 +#, no-c-format +msgid "#2173, Fix robustness issue in splitting a line with own vertex also affecting topology building (#2172)" +msgstr "" + +#. Tag: para +#: release_notes.xml:563 +#, no-c-format +msgid "#2174, Fix usage of wrong function lwpoly_free()" +msgstr "" + +#. Tag: para +#: release_notes.xml:564 +#, no-c-format +msgid "#2176, Fix robustness issue with ST_ChangeEdgeGeom" +msgstr "" + +#. Tag: para +#: release_notes.xml:565 +#, no-c-format +msgid "#2184, Properly copy topologies with Z value" +msgstr "" + +#. Tag: para +#: release_notes.xml:566 +#, no-c-format +msgid "postgis_restore.pl support for mixed case geometry column name in dumps" +msgstr "" + +#. Tag: para +#: release_notes.xml:568 +#, no-c-format +msgid "#2216, More memory errors in MultiPolygon GeoJSON parsing (with holes)" +msgstr "" + +#. Tag: para +#: release_notes.xml:569 +#, no-c-format +msgid "Fix Memory leak in GeoJSON parser" +msgstr "" + +#. Tag: para +#: release_notes.xml:574 +#, no-c-format +msgid "Speedup ST_ChangeEdgeGeom" +msgstr "" + +#. Tag: title +#: release_notes.xml:578 +#, no-c-format +msgid "Release 2.0.2" +msgstr "" + +#. Tag: para +#: release_notes.xml:579 +#, no-c-format +msgid "Release date: 2012/12/03" +msgstr "" + +#. Tag: para +#: release_notes.xml:580 +#, no-c-format +msgid "This is a bug fix release, addressing issues that have been filed since the 2.0.1 release." +msgstr "" + +#. Tag: para +#: release_notes.xml:583 +#, no-c-format +msgid "#1287, Drop of \"gist_geometry_ops\" broke a few clients package of legacy_gist.sql for these cases" +msgstr "" + +#. Tag: para +#: release_notes.xml:585 +#, no-c-format +msgid "#1391, Errors during upgrade from 1.5" +msgstr "" + +#. Tag: para +#: release_notes.xml:586 +#, no-c-format +msgid "#1828, Poor selectivity estimate on ST_DWithin" +msgstr "" + +#. Tag: para +#: release_notes.xml:587 +#, no-c-format +msgid "#1838, error importing tiger/line data" +msgstr "" + +#. Tag: para +#: release_notes.xml:588 +#, no-c-format +msgid "#1869, ST_AsBinary is not unique added to legacy_minor/legacy.sql scripts" +msgstr "" + +#. Tag: para +#: release_notes.xml:589 +#, no-c-format +msgid "#1885, Missing field from tabblock table in tiger2010 census_loader.sql" +msgstr "" + +#. Tag: para +#: release_notes.xml:590 +#, no-c-format +msgid "#1891, Use LDFLAGS environment when building liblwgeom" +msgstr "" + +#. Tag: para +#: release_notes.xml:591 +#, no-c-format +msgid "#1900, Fix pgsql2shp for big-endian systems" +msgstr "" + +#. Tag: para +#: release_notes.xml:592 +#, no-c-format +msgid "#1932, Fix raster2pgsql for invalid syntax for setting index tablespace" +msgstr "" + +#. Tag: para +#: release_notes.xml:594 +#, no-c-format +msgid "#1955, ST_ModEdgeHeal and ST_NewEdgeHeal for doubly connected edges" +msgstr "" + +#. Tag: para +#: release_notes.xml:597 +#, no-c-format +msgid "#1978, wrong answer calculating length of closed circular arc (circle)" +msgstr "" + +#. Tag: para +#: release_notes.xml:598 +#, no-c-format +msgid "#1981, Remove unused but set variables as found with gcc 4.6+" +msgstr "" + +#. Tag: para +#: release_notes.xml:599 +#, no-c-format +msgid "#1987, Restore 1.5.x behaviour of ST_Simplify" +msgstr "" + +#. Tag: para +#: release_notes.xml:602 +#, no-c-format +msgid "#1991, geocode really slow on PostgreSQL 9.2" +msgstr "" + +#. Tag: para +#: release_notes.xml:604 +#, no-c-format +msgid "#1998, Fix ST_{Mod,New}EdgeHeal joining edges sharing both endpoints" +msgstr "" + +#. Tag: para +#: release_notes.xml:605 +#, no-c-format +msgid "#2001, ST_CurveToLine has no effect if the geometry doesn't actually contain an arc" +msgstr "" + +#. Tag: para +#: release_notes.xml:606 +#, no-c-format +msgid "#2015, ST_IsEmpty('POLYGON(EMPTY)') returns False" +msgstr "" + +#. Tag: para +#: release_notes.xml:608 +#, no-c-format +msgid "#2025, Fix side location conflict at TopoGeo_AddLineString" +msgstr "" + +#. Tag: para +#: release_notes.xml:609 +#, no-c-format +msgid "#2026, improve performance of distance calculations" +msgstr "" + +#. Tag: para +#: release_notes.xml:610 +#, no-c-format +msgid "#2033, Fix adding a splitting point into a 2.5d topology" +msgstr "" + +#. Tag: para +#: release_notes.xml:611 +#, no-c-format +msgid "#2051, Fix excess of precision in ST_AsGeoJSON output" +msgstr "" + +#. Tag: para +#: release_notes.xml:612 +#, no-c-format +msgid "#2052, Fix buffer overflow in lwgeom_to_geojson" +msgstr "" + +#. Tag: para +#: release_notes.xml:613 +#, no-c-format +msgid "#2056, Fixed lack of SRID check of raster and geometry in ST_SetValue()" +msgstr "" + +#. Tag: para +#: release_notes.xml:615 +#, no-c-format +msgid "#2060, Fix \"dimension\" check violation by GetTopoGeomElementArray" +msgstr "" + +#. Tag: para +#: release_notes.xml:616 +#, no-c-format +msgid "#2072, Removed outdated checks preventing ST_Intersects(raster) from working on out-db bands" +msgstr "" + +#. Tag: para +#: release_notes.xml:618 +#, no-c-format +msgid "#2077, Fixed incorrect answers from ST_Hillshade(raster)" +msgstr "" + +#. Tag: para +#: release_notes.xml:619 +#, no-c-format +msgid "#2092, Namespace issue with ST_GeomFromKML,ST_GeomFromGML for libxml 2.8+" +msgstr "" + +#. Tag: para +#: release_notes.xml:620 +#, no-c-format +msgid "#2099, Fix double free on exception in ST_OffsetCurve" +msgstr "" + +#. Tag: para +#: release_notes.xml:621 +#, no-c-format +msgid "#2100, ST_AsRaster() may not return raster with specified pixel type" +msgstr "" + +#. Tag: para +#: release_notes.xml:622 +#, no-c-format +msgid "#2108, Ensure ST_Line_Interpolate_Point always returns POINT" +msgstr "" + +#. Tag: para +#: release_notes.xml:623 +#, no-c-format +msgid "#2109, Ensure ST_Centroid always returns POINT" +msgstr "" + +#. Tag: para +#: release_notes.xml:624 +#, no-c-format +msgid "#2117, Ensure ST_PointOnSurface always returns POINT" +msgstr "" + +#. Tag: para +#: release_notes.xml:625 +#, no-c-format +msgid "#2129, Fix SRID in ST_Homogenize output with collection input" +msgstr "" + +#. Tag: para +#: release_notes.xml:626 +#, no-c-format +msgid "#2130, Fix memory error in MultiPolygon GeoJson parsing" +msgstr "" + +#. Tag: para +#: release_notes.xml:628 +#, no-c-format +msgid "Update URL of Maven jar" +msgstr "" + +#. Tag: para +#: release_notes.xml:632 +#, no-c-format +msgid "#1581, ST_Clip(raster, ...) no longer imposes NODATA on a band if the corresponding band from the source raster did not have NODATA" +msgstr "" + +#. Tag: para +#: release_notes.xml:634 +#, no-c-format +msgid "#1928, Accept array properties in GML input multi-geom input (Kashif Rasul and Shoaib Burq / SpacialDB)" +msgstr "" + +#. Tag: para +#: release_notes.xml:636 +#, no-c-format +msgid "#2082, Add indices on start_node and end_node of topology edge tables" +msgstr "" + +#. Tag: para +#: release_notes.xml:637 +#, no-c-format +msgid "#2087, Speedup topology.GetRingEdges using a recursive CTE" +msgstr "" + +#. Tag: title +#: release_notes.xml:641 +#, no-c-format +msgid "Release 2.0.1" +msgstr "" + +#. Tag: para +#: release_notes.xml:642 +#, no-c-format +msgid "Release date: 2012/06/22" +msgstr "" + +#. Tag: para +#: release_notes.xml:643 +#, no-c-format +msgid "This is a bug fix release, addressing issues that have been filed since the 2.0.0 release." +msgstr "" + +#. Tag: para +#: release_notes.xml:646 +#, no-c-format +msgid "#1264, fix st_dwithin(geog, geog, 0)." +msgstr "" + +#. Tag: para +#: release_notes.xml:647 +#, no-c-format +msgid "#1468 shp2pgsql-gui table column schema get shifted" +msgstr "" + +#. Tag: para +#: release_notes.xml:648 +#, no-c-format +msgid "#1694, fix building with clang. (vince)" +msgstr "" + +#. Tag: para +#: release_notes.xml:649 +#, no-c-format +msgid "#1708, improve restore of pre-PostGIS 2.0 backups." +msgstr "" + +#. Tag: para +#: release_notes.xml:650 +#, no-c-format +msgid "#1714, more robust handling of high topology tolerance." +msgstr "" + +#. Tag: para +#: release_notes.xml:651 +#, no-c-format +msgid "#1755, ST_GeographyFromText support for higher dimensions." +msgstr "" + +#. Tag: para +#: release_notes.xml:652 +#, no-c-format +msgid "#1759, loading transformed shapefiles in raster enabled db." +msgstr "" + +#. Tag: para +#: release_notes.xml:653 +#, no-c-format +msgid "#1761, handling of subdatasets in NetCDF, HDF4 and HDF5 in raster2pgsql." +msgstr "" + +#. Tag: para +#: release_notes.xml:654 +#, no-c-format +msgid "#1763, topology.toTopoGeom use with custom search_path." +msgstr "" + +#. Tag: para +#: release_notes.xml:655 +#, no-c-format +msgid "#1766, don't let ST_RemEdge* destroy peripheral TopoGeometry objects." +msgstr "" + +#. Tag: para +#: release_notes.xml:656 +#, no-c-format +msgid "#1774, Clearer error on setting an edge geometry to an invalid one." +msgstr "" + +#. Tag: para +#: release_notes.xml:657 +#, no-c-format +msgid "#1775, ST_ChangeEdgeGeom collision detection with 2-vertex target." +msgstr "" + +#. Tag: para +#: release_notes.xml:658 +#, no-c-format +msgid "#1776, fix ST_SymDifference(empty, geom) to return geom." +msgstr "" + +#. Tag: para +#: release_notes.xml:659 +#, no-c-format +msgid "#1779, install SQL comment files." +msgstr "" + +#. Tag: para +#: release_notes.xml:660 +#, no-c-format +msgid "#1782, fix spatial reference string handling in raster." +msgstr "" + +#. Tag: para +#: release_notes.xml:661 +#, no-c-format +msgid "#1789, fix false edge-node crossing report in ValidateTopology." +msgstr "" + +#. Tag: para +#: release_notes.xml:662 +#, no-c-format +msgid "#1790, fix toTopoGeom handling of duplicated primitives." +msgstr "" + +#. Tag: para +#: release_notes.xml:663 +#, no-c-format +msgid "#1791, fix ST_Azimuth with very close but distinct points." +msgstr "" + +#. Tag: para +#: release_notes.xml:664 +#, no-c-format +msgid "#1797, fix (ValidateTopology(xxx)).* syntax calls." +msgstr "" + +#. Tag: para +#: release_notes.xml:665 +#, no-c-format +msgid "#1805, put back the 900913 SRID entry." +msgstr "" + +#. Tag: para +#: release_notes.xml:666 +#, no-c-format +msgid "#1813, Only show readable relations in metadata tables." +msgstr "" + +#. Tag: para +#: release_notes.xml:667 +#, no-c-format +msgid "#1819, fix floating point issues with ST_World2RasterCoord and ST_Raster2WorldCoord variants." +msgstr "" + +#. Tag: para +#: release_notes.xml:669 +#, no-c-format +msgid "#1820 compilation on 9.2beta1." +msgstr "" + +#. Tag: para +#: release_notes.xml:670 +#, no-c-format +msgid "#1822, topology load on PostgreSQL 9.2beta1." +msgstr "" + +#. Tag: para +#: release_notes.xml:671 +#, no-c-format +msgid "#1825, fix prepared geometry cache lookup" +msgstr "" + +#. Tag: para +#: release_notes.xml:672 +#, no-c-format +msgid "#1829, fix uninitialized read in GeoJSON parser" +msgstr "" + +#. Tag: para +#: release_notes.xml:673 +#, no-c-format +msgid "#1834, revise postgis extension to only backup user specified spatial_ref_sys" +msgstr "" + +#. Tag: para +#: release_notes.xml:677 +#, no-c-format +msgid "#1851, fix spatial_ref_system parameters for EPSG:3844" +msgstr "" + +#. Tag: para +#: release_notes.xml:678 +#, no-c-format +msgid "#1857, fix failure to detect endpoint mismatch in ST_AddEdge*Face*" +msgstr "" + +#. Tag: para +#: release_notes.xml:679 +#, no-c-format +msgid "#1865, data loss in postgis_restore.pl when data rows have leading dashes." +msgstr "" + +#. Tag: para +#: release_notes.xml:681 +#, no-c-format +msgid "#1867, catch invalid topology name passed to topogeo_add*" +msgstr "" + +#. Tag: para +#: release_notes.xml:683 +#, no-c-format +msgid "#1873, fix ptarray_locate_point to return interpolated Z/M values for on-the-line case" +msgstr "" + +#. Tag: para +#: release_notes.xml:687 +#, no-c-format +msgid "#1881, shp2pgsql-gui -- editing a field sometimes triggers removing row" +msgstr "" + +#. Tag: para +#: release_notes.xml:689 +#, no-c-format +msgid "#1883, Geocoder install fails trying to run create_census_base_tables() (Brian Panulla)" +msgstr "" + +#. Tag: para +#: release_notes.xml:694 +#, no-c-format +msgid "More detailed exception message from topology editing functions." +msgstr "" + +#. Tag: para +#: release_notes.xml:695 +#, no-c-format +msgid "#1786, improved build dependencies" +msgstr "" + +#. Tag: para +#: release_notes.xml:696 +#, no-c-format +msgid "#1806, speedup of ST_BuildArea, ST_MakeValid and ST_GetFaceGeometry." +msgstr "" + +#. Tag: para +#: release_notes.xml:697 +#, no-c-format +msgid "#1812, Add lwgeom_normalize in LIBLWGEOM for more stable testing." +msgstr "" + +#. Tag: title +#: release_notes.xml:701 +#, no-c-format +msgid "Release 2.0.0" +msgstr "" + +#. Tag: para +#: release_notes.xml:702 +#, no-c-format +msgid "Release date: 2012/04/03" +msgstr "" + +#. Tag: para +#: release_notes.xml:703 +#, no-c-format +msgid "This is a major release. A hard upgrade is required. Yes this means a full dump reload and some special preparations if you are using obsolete functions. Refer to for details on upgrading. Refer to for more details and changed/new functions." +msgstr "" + +#. Tag: title +#: release_notes.xml:707 +#, no-c-format +msgid "Testers - Our unsung heroes" +msgstr "" + +#. Tag: para +#: release_notes.xml:708 +#, no-c-format +msgid "We are most indebted to the numerous members in the PostGIS community who were brave enough to test out the new features in this release. No major release can be successful without these folk." +msgstr "" + +#. Tag: para +#: release_notes.xml:711 +#, no-c-format +msgid "Below are those who have been most valiant, provided very detailed and thorough bug reports, and detailed analysis." +msgstr "" + +#. Tag: member +#: release_notes.xml:715 +#, no-c-format +msgid "Andrea Peri - Lots of testing on topology, checking for correctness" +msgstr "" + +#. Tag: member +#: release_notes.xml:716 +#, no-c-format +msgid "Andreas Forø Tollefsen - raster testing" +msgstr "" + +#. Tag: member +#: release_notes.xml:717 +#, no-c-format +msgid "Chris English - topology stress testing loader functions" +msgstr "" + +#. Tag: member +#: release_notes.xml:718 +#, no-c-format +msgid "Salvatore Larosa - topology robustness testing" +msgstr "" + +#. Tag: member +#: release_notes.xml:719 +#, no-c-format +msgid "Brian Hamlin - Benchmarking (also experimental experimental branches before they are folded into core) , general testing of various pieces including Tiger and Topology. Testing on various server VMs" +msgstr "" + +#. Tag: member +#: release_notes.xml:724 +#, no-c-format +msgid "Mike Pease - Tiger geocoder testing - very detailed reports of issues" +msgstr "" + +#. Tag: member +#: release_notes.xml:725 +#, no-c-format +msgid "Tom van Tilburg - raster testing" +msgstr "" + +#. Tag: para +#: release_notes.xml:730 +#, no-c-format +msgid "#722, #302, Most deprecated functions removed (over 250 functions) (Regina Obe, Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:731 +#, no-c-format +msgid "Unknown SRID changed from -1 to 0. (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:732 +#, no-c-format +msgid "-- (most deprecated in 1.2) removed non-ST variants buffer, length, intersects (and internal functions renamed) etc." +msgstr "" + +#. Tag: para +#: release_notes.xml:734 +#, no-c-format +msgid "-- If you have been using deprecated functions CHANGE your apps or suffer the consequences. If you don't see a function documented -- it ain't supported or it is an internal function. Some constraints in older tables were built with deprecated functions. If you restore you may need to rebuild table constraints with populate_geometry_columns(). If you have applications or tools that rely on deprecated functions, please refer to for more details." +msgstr "" + +#. Tag: para +#: release_notes.xml:739 +#, no-c-format +msgid "#944 geometry_columns is now a view instead of a table (Paul Ramsey, Regina Obe) for tables created the old way reads (srid, type, dims) constraints for geometry columns created with type modifiers reads rom column definition" +msgstr "" + +#. Tag: para +#: release_notes.xml:744 +#, no-c-format +msgid "#1081, #1082, #1084, #1088 - Mangement functions support typmod geometry column creation functions now default to typmod creation (Regina Obe)" +msgstr "" + +#. Tag: para +#: release_notes.xml:747 +#, no-c-format +msgid "#1083 probe_geometry_columns(), rename_geometry_table_constraints(), fix_geometry_columns(); removed - now obsolete with geometry_column view (Regina Obe)" +msgstr "" + +#. Tag: para +#: release_notes.xml:751 +#, no-c-format +msgid "#817 Renaming old 3D functions to the convention ST_3D (Nicklas Avén)" +msgstr "" + +#. Tag: para +#: release_notes.xml:752 +#, no-c-format +msgid "#548 (sorta), ST_NumGeometries,ST_GeometryN now returns 1 (or the geometry) instead of null for single geometries (Sandro Santilli, Maxime van Noppen)" +msgstr "" + +#. Tag: ulink +#: release_notes.xml:757 +#, no-c-format +msgid "KNN Gist index based centroid (<->) and box (<#>) distance operators (Paul Ramsey / funded by Vizzuality)" +msgstr "" + +#. Tag: para +#: release_notes.xml:758 +#, no-c-format +msgid "Support for TIN and PolyHedralSurface and enhancement of many functions to support 3D (Olivier Courtin / Oslandia)" +msgstr "" + +#. Tag: para +#: release_notes.xml:759 +#, no-c-format +msgid "Raster support integrated and documented (Pierre Racine, Jorge Arévalo, Mateusz Loskot, Sandro Santilli, David Zwarg, Regina Obe, Bborie Park) (Company developer and funding: University Laval, Deimos Space, CadCorp, Michigan Tech Research Institute, Azavea, Paragon Corporation, UC Davis Center for Vectorborne Diseases)" +msgstr "" + +#. Tag: para +#: release_notes.xml:762 +#, no-c-format +msgid "Making spatial indexes 3D aware - in progress (Paul Ramsey, Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:763 +#, no-c-format +msgid "Topology support improved (more functions), documented, testing (Sandro Santilli / Faunalia for RT-SIGTA), Andrea Peri, Regina Obe, Jose Carlos Martinez Llari" +msgstr "" + +#. Tag: para +#: release_notes.xml:764 +#, no-c-format +msgid "3D relationship and measurement support functions (Nicklas Avén)" +msgstr "" + +#. Tag: para +#: release_notes.xml:765 +#, no-c-format +msgid "ST_3DDistance, ST_3DClosestPoint, ST_3DIntersects, ST_3DShortestLine and more..." +msgstr "" + +#. Tag: para +#: release_notes.xml:766 +#, no-c-format +msgid "N-Dimensional spatial indexes (Paul Ramsey / OpenGeo)" +msgstr "" + +#. Tag: para +#: release_notes.xml:767 +#, no-c-format +msgid "ST_Split (Sandro Santilli / Faunalia for RT-SIGTA)" +msgstr "" + +#. Tag: para +#: release_notes.xml:768 +#, no-c-format +msgid "ST_IsValidDetail (Sandro Santilli / Faunalia for RT-SIGTA)" +msgstr "" + +#. Tag: para +#: release_notes.xml:769 +#, no-c-format +msgid "ST_MakeValid (Sandro Santilli / Faunalia for RT-SIGTA)" +msgstr "" + +#. Tag: para +#: release_notes.xml:770 +#, no-c-format +msgid "ST_RemoveRepeatedPoints (Sandro Santilli / Faunalia for RT-SIGTA)" +msgstr "" + +#. Tag: para +#: release_notes.xml:771 +#, no-c-format +msgid "ST_GeometryN and ST_NumGeometries support for non-collections (Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:772 +#, no-c-format +msgid "ST_IsCollection (Sandro Santilli, Maxime van Noppen)" +msgstr "" + +#. Tag: para +#: release_notes.xml:773 +#, no-c-format +msgid "ST_SharedPaths (Sandro Santilli / Faunalia for RT-SIGTA)" +msgstr "" + +#. Tag: para +#: release_notes.xml:774 +#, no-c-format +msgid "ST_Snap (Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:775 +#, no-c-format +msgid "ST_RelateMatch (Sandro Santilli / Faunalia for RT-SIGTA)" +msgstr "" + +#. Tag: para +#: release_notes.xml:776 +#, no-c-format +msgid "ST_ConcaveHull (Regina Obe and Leo Hsu / Paragon Corporation)" +msgstr "" + +#. Tag: para +#: release_notes.xml:777 +#, no-c-format +msgid "ST_UnaryUnion (Sandro Santilli / Faunalia for RT-SIGTA)" +msgstr "" + +#. Tag: para +#: release_notes.xml:778 +#, no-c-format +msgid "ST_AsX3D (Regina Obe / Arrival 3D funding)" +msgstr "" + +#. Tag: para +#: release_notes.xml:779 +#, no-c-format +msgid "ST_OffsetCurve (Sandro Santilli, Rafal Magda)" +msgstr "" + +#. Tag: ulink +#: release_notes.xml:780 +#, no-c-format +msgid "ST_GeomFromGeoJSON (Kashif Rasul, Paul Ramsey / Vizzuality funding)" +msgstr "" + +#. Tag: para +#: release_notes.xml:784 +#, no-c-format +msgid "Made shape file loader tolerant of truncated multibyte values found in some free worldwide shapefiles (Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:785 +#, no-c-format +msgid "Lots of bug fixes and enhancements to shp2pgsql Beefing up regression tests for loaders Reproject support for both geometry and geography during import (Jeff Adams / Azavea, Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:789 +#, no-c-format +msgid "pgsql2shp conversion from predefined list (Loic Dachary / Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:791 +#, no-c-format +msgid "Shp-pgsql GUI loader - support loading multiple files at a time. (Mark Leslie)" +msgstr "" + +#. Tag: para +#: release_notes.xml:792 +#, no-c-format +msgid "Extras - upgraded tiger_geocoder from using old TIGER format to use new TIGER shp and file structure format (Stephen Frost)" +msgstr "" + +#. Tag: para +#: release_notes.xml:793 +#, no-c-format +msgid "Extras - revised tiger_geocoder to work with TIGER census 2010 data, addition of reverse geocoder function, various bug fixes, accuracy enhancements, limit max result return, speed improvements, loading routines. (Regina Obe, Leo Hsu / Paragon Corporation / funding provided by Hunter Systems Group)" +msgstr "" + +#. Tag: para +#: release_notes.xml:796 +#, no-c-format +msgid "Overall Documentation proofreading and corrections. (Kasif Rasul)" +msgstr "" + +#. Tag: para +#: release_notes.xml:797 +#, no-c-format +msgid "Cleanup PostGIS JDBC classes, revise to use Maven build. (Maria Arias de Reyna, Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:801 +#, no-c-format +msgid "#1335 ST_AddPoint returns incorrect result on Linux (Even Rouault)" +msgstr "" + +#. Tag: title +#: release_notes.xml:804 +#, no-c-format +msgid "Release specific credits" +msgstr "" + +#. Tag: para +#: release_notes.xml:805 +#, no-c-format +msgid "We thank U.S Department of State Human Information Unit (HIU) and Vizzuality for general monetary support to get PostGIS 2.0 out the door." +msgstr "" + +#. Tag: title +#: release_notes.xml:810 +#, no-c-format +msgid "Release 1.5.4" +msgstr "" + +#. Tag: para +#: release_notes.xml:811 +#, no-c-format +msgid "Release date: 2012/05/07" +msgstr "" + +#. Tag: para +#: release_notes.xml:812 +#, no-c-format +msgid "This is a bug fix release, addressing issues that have been filed since the 1.5.3 release." +msgstr "" + +#. Tag: para +#: release_notes.xml:815 +#, no-c-format +msgid "#547, ST_Contains memory problems (Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:816 +#, no-c-format +msgid "#621, Problem finding intersections with geography (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:817 +#, no-c-format +msgid "#627, PostGIS/PostgreSQL process die on invalid geometry (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:818 +#, no-c-format +msgid "#810, Increase accuracy of area calculation (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:819 +#, no-c-format +msgid "#852, improve spatial predicates robustness (Sandro Santilli, Nicklas Avén)" +msgstr "" + +#. Tag: para +#: release_notes.xml:820 +#, no-c-format +msgid "#877, ST_Estimated_Extent returns NULL on empty tables (Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:821 +#, no-c-format +msgid "#1028, ST_AsSVG kills whole postgres server when fails (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:822 +#, no-c-format +msgid "#1056, Fix boxes of arcs and circle stroking code (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:823 +#, no-c-format +msgid "#1121, populate_geometry_columns using deprecated functions (Regin Obe, Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:824 +#, no-c-format +msgid "#1135, improve testsuite predictability (Andreas 'ads' Scherbaum)" +msgstr "" + +#. Tag: para +#: release_notes.xml:825 +#, no-c-format +msgid "#1146, images generator crashes (bronaugh)" +msgstr "" + +#. Tag: para +#: release_notes.xml:826 +#, no-c-format +msgid "#1170, North Pole intersection fails (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:827 +#, no-c-format +msgid "#1179, ST_AsText crash with bad value (kjurka)" +msgstr "" + +#. Tag: para +#: release_notes.xml:828 +#, no-c-format +msgid "#1184, honour DESTDIR in documentation Makefile (Bryce L Nordgren)" +msgstr "" + +#. Tag: para +#: release_notes.xml:829 +#, no-c-format +msgid "#1227, server crash on invalid GML" +msgstr "" + +#. Tag: para +#: release_notes.xml:830 +#, no-c-format +msgid "#1252, SRID appearing in WKT (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:831 +#, no-c-format +msgid "#1264, st_dwithin(g, g, 0) doesn't work (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:832 +#, no-c-format +msgid "#1344, allow exporting tables with invalid geometries (Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:833 +#, no-c-format +msgid "#1389, wrong proj4text for SRID 31300 and 31370 (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:834 +#, no-c-format +msgid "#1406, shp2pgsql crashes when loading into geography (Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:835 +#, no-c-format +msgid "#1595, fixed SRID redundancy in ST_Line_SubString (Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:836 +#, no-c-format +msgid "#1596, check SRID in UpdateGeometrySRID (Mike Toews, Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:837 +#, no-c-format +msgid "#1602, fix ST_Polygonize to retain Z (Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:838 +#, no-c-format +msgid "#1697, fix crash with EMPTY entries in GiST index (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:839 +#, no-c-format +msgid "#1772, fix ST_Line_Locate_Point with collapsed input (Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:840 +#, no-c-format +msgid "#1799, Protect ST_Segmentize from max_length=0 (Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:841 +#, no-c-format +msgid "Alter parameter order in 900913 (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:842 +#, no-c-format +msgid "Support builds with \"gmake\" (Greg Troxel)" +msgstr "" + +#. Tag: title +#: release_notes.xml:847 +#, no-c-format +msgid "Release 1.5.3" +msgstr "" + +#. Tag: para +#: release_notes.xml:848 +#, no-c-format +msgid "Release date: 2011/06/25" +msgstr "" + +#. Tag: para +#: release_notes.xml:849 +#, no-c-format +msgid "This is a bug fix release, addressing issues that have been filed since the 1.5.2 release. If you are running PostGIS 1.3+, a soft upgrade is sufficient otherwise a hard upgrade is recommended." +msgstr "" + +#. Tag: para +#: release_notes.xml:853 +#, no-c-format +msgid "#1056, produce correct bboxes for arc geometries, fixes index errors (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:855 +#, no-c-format +msgid "#1007, ST_IsValid crash fix requires GEOS 3.3.0+ or 3.2.3+ (Sandro Santilli, reported by Birgit Laggner)" +msgstr "" + +#. Tag: para +#: release_notes.xml:857 +#, no-c-format +msgid "#940, support for PostgreSQL 9.1 beta 1 (Regina Obe, Paul Ramsey, patch submitted by stl)" +msgstr "" + +#. Tag: para +#: release_notes.xml:859 +#, no-c-format +msgid "#845, ST_Intersects precision error (Sandro Santilli, Nicklas Avén) Reported by cdestigter" +msgstr "" + +#. Tag: para +#: release_notes.xml:861 +#, no-c-format +msgid "#884, Unstable results with ST_Within, ST_Intersects (Chris Hodgson)" +msgstr "" + +#. Tag: para +#: release_notes.xml:862 +#, no-c-format +msgid "#779, shp2pgsql -S option seems to fail on points (Jeff Adams)" +msgstr "" + +#. Tag: para +#: release_notes.xml:863 +#, no-c-format +msgid "#666, ST_DumpPoints is not null safe (Regina Obe)" +msgstr "" + +#. Tag: para +#: release_notes.xml:864 +#, no-c-format +msgid "#631, Update NZ projections for grid transformation support (jpalmer)" +msgstr "" + +#. Tag: para +#: release_notes.xml:865 +#, no-c-format +msgid "#630, Peculiar Null treatment in arrays in ST_Collect (Chris Hodgson) Reported by David Bitner" +msgstr "" + +#. Tag: para +#: release_notes.xml:867 +#, no-c-format +msgid "#624, Memory leak in ST_GeogFromText (ryang, Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:868 +#, no-c-format +msgid "#609, Bad source code in manual section 5.2 Java Clients (simoc, Regina Obe)" +msgstr "" + +#. Tag: para +#: release_notes.xml:869 +#, no-c-format +msgid "#604, shp2pgsql usage touchups (Mike Toews, Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:870 +#, no-c-format +msgid "#573 ST_Union fails on a group of linestrings Not a PostGIS bug, fixed in GEOS 3.3.0" +msgstr "" + +#. Tag: para +#: release_notes.xml:872 +#, no-c-format +msgid "#457 ST_CollectionExtract returns non-requested type (Nicklas Avén, Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:874 +#, no-c-format +msgid "#441 ST_AsGeoJson Bbox on GeometryCollection error (Olivier Courtin)" +msgstr "" + +#. Tag: para +#: release_notes.xml:875 +#, no-c-format +msgid "#411 Ability to backup invalid geometries (Sando Santilli) Reported by Regione Toscana" +msgstr "" + +#. Tag: para +#: release_notes.xml:877 +#, no-c-format +msgid "#409 ST_AsSVG - degraded (Olivier Courtin) Reported by Sdikiy" +msgstr "" + +#. Tag: para +#: release_notes.xml:879 +#, no-c-format +msgid "#373 Documentation syntax error in hard upgrade (Paul Ramsey) Reported by psvensso" +msgstr "" + +#. Tag: title +#: release_notes.xml:885 +#, no-c-format +msgid "Release 1.5.2" +msgstr "" + +#. Tag: para +#: release_notes.xml:886 +#, no-c-format +msgid "Release date: 2010/09/27" +msgstr "" + +#. Tag: para +#: release_notes.xml:887 +#, no-c-format +msgid "This is a bug fix release, addressing issues that have been filed since the 1.5.1 release. If you are running PostGIS 1.3+, a soft upgrade is sufficient otherwise a hard upgrade is recommended." +msgstr "" + +#. Tag: para +#: release_notes.xml:891 +#, no-c-format +msgid "Loader: fix handling of empty (0-verticed) geometries in shapefiles. (Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:892 +#, no-c-format +msgid "#536, Geography ST_Intersects, ST_Covers, ST_CoveredBy and Geometry ST_Equals not using spatial index (Regina Obe, Nicklas Aven)" +msgstr "" + +#. Tag: para +#: release_notes.xml:893 +#, no-c-format +msgid "#573, Improvement to ST_Contains geography (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:894 +#, no-c-format +msgid "Loader: Add support for command-q shutdown in Mac GTK build (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:895 +#, no-c-format +msgid "#393, Loader: Add temporary patch for large DBF files (Maxime Guillaud, Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:896 +#, no-c-format +msgid "#507, Fix wrong OGC URN in GeoJSON and GML output (Olivier Courtin)" +msgstr "" + +#. Tag: para +#: release_notes.xml:897 +#, no-c-format +msgid "spatial_ref_sys.sql Add datum conversion for projection SRID 3021 (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:898 +#, no-c-format +msgid "Geography - remove crash for case when all geographies are out of the estimate (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:899 +#, no-c-format +msgid "#469, Fix for array_aggregation error (Greg Stark, Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:900 +#, no-c-format +msgid "#532, Temporary geography tables showing up in other user sessions (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:901 +#, no-c-format +msgid "#562, ST_Dwithin errors for large geographies (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:902 +#, no-c-format +msgid "#513, shape loading GUI tries to make spatial index when loading DBF only mode (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:903 +#, no-c-format +msgid "#527, shape loading GUI should always append log messages (Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:904 +#, no-c-format +msgid "#504, shp2pgsql should rename xmin/xmax fields (Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:905 +#, no-c-format +msgid "#458, postgis_comments being installed in contrib instead of version folder (Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:906 +#, no-c-format +msgid "#474, Analyzing a table with geography column crashes server (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:907 +#, no-c-format +msgid "#581, LWGEOM-expand produces inconsistent results (Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:908 +#, no-c-format +msgid "#513, Add dbf filter to shp2pgsql-gui and allow uploading dbf only (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:909 +#, no-c-format +msgid "Fix further build issues against PostgreSQL 9.0 (Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:910 +#, no-c-format +msgid "#572, Password whitespace for Shape File (Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:911 +#, no-c-format +msgid "#603, shp2pgsql: \"-w\" produces invalid WKT for MULTI* objects. (Mark Cave-Ayland)" +msgstr "" + +#. Tag: title +#: release_notes.xml:916 +#, no-c-format +msgid "Release 1.5.1" +msgstr "" + +#. Tag: para +#: release_notes.xml:917 +#, no-c-format +msgid "Release date: 2010/03/11" +msgstr "" + +#. Tag: para +#: release_notes.xml:918 +#, no-c-format +msgid "This is a bug fix release, addressing issues that have been filed since the 1.4.1 release. If you are running PostGIS 1.3+, a soft upgrade is sufficient otherwise a hard upgrade is recommended." +msgstr "" + +#. Tag: para +#: release_notes.xml:922 +#, no-c-format +msgid "#410, update embedded bbox when applying ST_SetPoint, ST_AddPoint ST_RemovePoint to a linestring (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:923 +#, no-c-format +msgid "#411, allow dumping tables with invalid geometries (Sandro Santilli, for Regione Toscana-SIGTA)" +msgstr "" + +#. Tag: para +#: release_notes.xml:924 +#, no-c-format +msgid "#414, include geography_columns view when running upgrade scripts (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:925 +#, no-c-format +msgid "#419, allow support for multilinestring in ST_Line_Substring (Paul Ramsey, for Lidwala Consulting Engineers)" +msgstr "" + +#. Tag: para +#: release_notes.xml:926 +#, no-c-format +msgid "#421, fix computed string length in ST_AsGML() (Olivier Courtin)" +msgstr "" + +#. Tag: para +#: release_notes.xml:927 +#, no-c-format +msgid "#441, fix GML generation with heterogeneous collections (Olivier Courtin)" +msgstr "" + +#. Tag: para +#: release_notes.xml:928 +#, no-c-format +msgid "#443, incorrect coordinate reversal in GML 3 generation (Olivier Courtin)" +msgstr "" + +#. Tag: para +#: release_notes.xml:929 +#, no-c-format +msgid "#450, #451, wrong area calculation for geography features that cross the date line (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:930 +#, no-c-format +msgid "Ensure support for upcoming 9.0 PgSQL release (Paul Ramsey)" +msgstr "" + +#. Tag: title +#: release_notes.xml:935 +#, no-c-format +msgid "Release 1.5.0" +msgstr "" + +#. Tag: para +#: release_notes.xml:936 +#, no-c-format +msgid "Release date: 2010/02/04" +msgstr "" + +#. Tag: para +#: release_notes.xml:937 +#, no-c-format +msgid "This release provides support for geographic coordinates (lat/lon) via a new GEOGRAPHY type. Also performance enhancements, new input format support (GML,KML) and general upkeep." +msgstr "" + +#. Tag: title +#: release_notes.xml:940 release_notes.xml:1007 +#, no-c-format +msgid "API Stability" +msgstr "" + +#. Tag: para +#: release_notes.xml:941 +#, no-c-format +msgid "The public API of PostGIS will not change during minor (0.0.X) releases." +msgstr "" + +#. Tag: para +#: release_notes.xml:942 +#, no-c-format +msgid "The definition of the =~ operator has changed from an exact geometric equality check to a bounding box equality check." +msgstr "" + +#. Tag: title +#: release_notes.xml:946 release_notes.xml:1012 +#, no-c-format +msgid "Compatibility" +msgstr "" + +#. Tag: para +#: release_notes.xml:947 +#, no-c-format +msgid "GEOS, Proj4, and LibXML2 are now mandatory dependencies" +msgstr "" + +#. Tag: para +#: release_notes.xml:948 +#, no-c-format +msgid "The library versions below are the minimum requirements for PostGIS 1.5" +msgstr "" + +#. Tag: para +#: release_notes.xml:949 +#, no-c-format +msgid "PostgreSQL 8.3 and higher on all platforms" +msgstr "" + +#. Tag: para +#: release_notes.xml:950 +#, no-c-format +msgid "GEOS 3.1 and higher only (GEOS 3.2+ to take advantage of all features)" +msgstr "" + +#. Tag: para +#: release_notes.xml:951 +#, no-c-format +msgid "LibXML2 2.5+ related to new ST_GeomFromGML/KML functionality" +msgstr "" + +#. Tag: para +#: release_notes.xml:952 +#, no-c-format +msgid "Proj4 4.5 and higher only" +msgstr "" + +#. Tag: para +#: release_notes.xml:958 +#, no-c-format +msgid "Added Hausdorff distance calculations (#209) (Vincent Picavet)" +msgstr "" + +#. Tag: para +#: release_notes.xml:959 +#, no-c-format +msgid "Added parameters argument to ST_Buffer operation to support one-sided buffering and other buffering styles (Sandro Santilli)" +msgstr "" + +#. Tag: para +#: release_notes.xml:960 +#, no-c-format +msgid "Addition of other Distance related visualization and analysis functions (Nicklas Aven)" +msgstr "" + +#. Tag: para +#: release_notes.xml:962 +#, no-c-format +msgid "ST_ClosestPoint" +msgstr "" + +#. Tag: para +#: release_notes.xml:963 +#, no-c-format +msgid "ST_DFullyWithin" +msgstr "" + +#. Tag: para +#: release_notes.xml:964 +#, no-c-format +msgid "ST_LongestLine" +msgstr "" + +#. Tag: para +#: release_notes.xml:965 +#, no-c-format +msgid "ST_MaxDistance" +msgstr "" + +#. Tag: para +#: release_notes.xml:966 +#, no-c-format +msgid "ST_ShortestLine" +msgstr "" + +#. Tag: para +#: release_notes.xml:968 +#, no-c-format +msgid "ST_DumpPoints (Maxime van Noppen)" +msgstr "" + +#. Tag: para +#: release_notes.xml:969 +#, no-c-format +msgid "KML, GML input via ST_GeomFromGML and ST_GeomFromKML (Olivier Courtin)" +msgstr "" + +#. Tag: para +#: release_notes.xml:970 +#, no-c-format +msgid "Extract homogeneous collection with ST_CollectionExtract (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:971 +#, no-c-format +msgid "Add measure values to an existing linestring with ST_AddMeasure (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:972 +#, no-c-format +msgid "History table implementation in utils (George Silva)" +msgstr "" + +#. Tag: para +#: release_notes.xml:973 +#, no-c-format +msgid "Geography type and supporting functions" +msgstr "" + +#. Tag: para +#: release_notes.xml:975 +#, no-c-format +msgid "Spherical algorithms (Dave Skea)" +msgstr "" + +#. Tag: para +#: release_notes.xml:976 +#, no-c-format +msgid "Object/index implementation (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:977 +#, no-c-format +msgid "Selectivity implementation (Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:978 +#, no-c-format +msgid "Serializations to KML, GML and JSON (Olivier Courtin)" +msgstr "" + +#. Tag: para +#: release_notes.xml:979 +#, no-c-format +msgid "ST_Area, ST_Distance, ST_DWithin, ST_GeogFromText, ST_GeogFromWKB, ST_Intersects, ST_Covers, ST_Buffer (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:985 +#, no-c-format +msgid "Performance improvements to ST_Distance (Nicklas Aven)" +msgstr "" + +#. Tag: para +#: release_notes.xml:986 +#, no-c-format +msgid "Documentation updates and improvements (Regina Obe, Kevin Neufeld)" +msgstr "" + +#. Tag: para +#: release_notes.xml:987 +#, no-c-format +msgid "Testing and quality control (Regina Obe)" +msgstr "" + +#. Tag: para +#: release_notes.xml:988 +#, no-c-format +msgid "PostGIS 1.5 support PostgreSQL 8.5 trunk (Guillaume Lelarge)" +msgstr "" + +#. Tag: para +#: release_notes.xml:989 +#, no-c-format +msgid "Win32 support and improvement of core shp2pgsql-gui (Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:990 +#, no-c-format +msgid "In place 'make check' support (Paul Ramsey)" +msgstr "" + +#. Tag: title +#: release_notes.xml:994 release_notes.xml:1060 release_notes.xml:1245 release_notes.xml:1296 release_notes.xml:1347 release_notes.xml:1481 release_notes.xml:1547 release_notes.xml:1657 release_notes.xml:1764 release_notes.xml:1884 release_notes.xml:1949 release_notes.xml:1996 +#, no-c-format +msgid "Bug fixes" +msgstr "" + +#. Tag: ulink +#: release_notes.xml:995 +#, no-c-format +msgid "http://trac.osgeo.org/postgis/query?status=closed&milestone=PostGIS+1.5.0&order=priority" +msgstr "" + +#. Tag: title +#: release_notes.xml:1000 +#, no-c-format +msgid "Release 1.4.0" +msgstr "" + +#. Tag: para +#: release_notes.xml:1001 +#, no-c-format +msgid "Release date: 2009/07/24" +msgstr "" + +#. Tag: para +#: release_notes.xml:1002 +#, no-c-format +msgid "This release provides performance enhancements, improved internal structures and testing, new features, and upgraded documentation. If you are running PostGIS 1.1+, a soft upgrade is sufficient otherwise a hard upgrade is recommended." +msgstr "" + +#. Tag: para +#: release_notes.xml:1008 +#, no-c-format +msgid "As of the 1.4 release series, the public API of PostGIS will not change during minor releases." +msgstr "" + +#. Tag: para +#: release_notes.xml:1013 +#, no-c-format +msgid "The versions below are the *minimum* requirements for PostGIS 1.4" +msgstr "" + +#. Tag: para +#: release_notes.xml:1014 +#, no-c-format +msgid "PostgreSQL 8.2 and higher on all platforms" +msgstr "" + +#. Tag: para +#: release_notes.xml:1015 +#, no-c-format +msgid "GEOS 3.0 and higher only" +msgstr "" + +#. Tag: para +#: release_notes.xml:1016 +#, no-c-format +msgid "PROJ4 4.5 and higher only" +msgstr "" + +#. Tag: para +#: release_notes.xml:1021 +#, no-c-format +msgid "ST_Union() uses high-speed cascaded union when compiled against GEOS 3.1+ (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1023 +#, no-c-format +msgid "ST_ContainsProperly() requires GEOS 3.1+" +msgstr "" + +#. Tag: para +#: release_notes.xml:1024 +#, no-c-format +msgid "ST_Intersects(), ST_Contains(), ST_Within() use high-speed cached prepared geometry against GEOS 3.1+ (Paul Ramsey / funded by Zonar Systems)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1025 +#, no-c-format +msgid "Vastly improved documentation and reference manual (Regina Obe & Kevin Neufeld)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1026 +#, no-c-format +msgid "Figures and diagram examples in the reference manual (Kevin Neufeld)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1027 +#, no-c-format +msgid "ST_IsValidReason() returns readable explanations for validity failures (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1028 +#, no-c-format +msgid "ST_GeoHash() returns a geohash.org signature for geometries (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1029 +#, no-c-format +msgid "GTK+ multi-platform GUI for shape file loading (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1030 +#, no-c-format +msgid "ST_LineCrossingDirection() returns crossing directions (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1031 +#, no-c-format +msgid "ST_LocateBetweenElevations() returns sub-string based on Z-ordinate. (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1032 +#, no-c-format +msgid "Geometry parser returns explicit error message about location of syntax errors (Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1033 +#, no-c-format +msgid "ST_AsGeoJSON() return JSON formatted geometry (Olivier Courtin)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1034 +#, no-c-format +msgid "Populate_Geometry_Columns() -- automatically add records to geometry_columns for TABLES and VIEWS (Kevin Neufeld)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1035 +#, no-c-format +msgid "ST_MinimumBoundingCircle() -- returns the smallest circle polygon that can encompass a geometry (Bruce Rindahl)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1040 +#, no-c-format +msgid "Core geometry system moved into independent library, liblwgeom. (Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1041 +#, no-c-format +msgid "New build system uses PostgreSQL \"pgxs\" build bootstrapper. (Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1042 +#, no-c-format +msgid "Debugging framework formalized and simplified. (Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1043 +#, no-c-format +msgid "All build-time #defines generated at configure time and placed in headers for easier cross-platform support (Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1044 +#, no-c-format +msgid "Logging framework formalized and simplified (Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1045 +#, no-c-format +msgid "Expanded and more stable support for CIRCULARSTRING, COMPOUNDCURVE and CURVEPOLYGON, better parsing, wider support in functions (Mark Leslie & Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1046 +#, no-c-format +msgid "Improved support for OpenSolaris builds (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1047 +#, no-c-format +msgid "Improved support for MSVC builds (Mateusz Loskot)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1048 +#, no-c-format +msgid "Updated KML support (Olivier Courtin)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1049 +#, no-c-format +msgid "Unit testing framework for liblwgeom (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1050 +#, no-c-format +msgid "New testing framework to comprehensively exercise every PostGIS function (Regine Obe)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1051 +#, no-c-format +msgid "Performance improvements to all geometry aggregate functions (Paul Ramsey)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1052 +#, no-c-format +msgid "Support for the upcoming PostgreSQL 8.4 (Mark Cave-Ayland, Talha Bin Rizwan)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1053 +#, no-c-format +msgid "Shp2pgsql and pgsql2shp re-worked to depend on the common parsing/unparsing code in liblwgeom (Mark Cave-Ayland)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1054 +#, no-c-format +msgid "Use of PDF DbLatex to build PDF docs and preliminary instructions for build (Jean David Techer)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1055 +#, no-c-format +msgid "Automated User documentation build (PDF and HTML) and Developer Doxygen Documentation (Kevin Neufeld)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1056 +#, no-c-format +msgid "Automated build of document images using ImageMagick from WKT geometry text files (Kevin Neufeld)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1057 +#, no-c-format +msgid "More attractive CSS for HTML documentation (Dane Springmeyer)" +msgstr "" + +#. Tag: ulink +#: release_notes.xml:1061 +#, no-c-format +msgid "http://trac.osgeo.org/postgis/query?status=closed&milestone=PostGIS+1.4.0&order=priority" +msgstr "" + +#. Tag: title +#: release_notes.xml:1066 +#, no-c-format +msgid "Release 1.3.6" +msgstr "" + +#. Tag: para +#: release_notes.xml:1067 +#, no-c-format +msgid "Release date: 2009/05/04" +msgstr "" + +#. Tag: para +#: release_notes.xml:1068 +#, no-c-format +msgid "If you are running PostGIS 1.1+, a soft upgrade is sufficient otherwise a hard upgrade is recommended. This release adds support for PostgreSQL 8.4, exporting prj files from the database with shape data, some crash fixes for shp2pgsql, and several small bug fixes in the handling of \"curve\" types, logical error importing dbf only files, improved error handling of AddGeometryColumns." +msgstr "" + +#. Tag: title +#: release_notes.xml:1075 +#, no-c-format +msgid "Release 1.3.5" +msgstr "" + +#. Tag: para +#: release_notes.xml:1076 +#, no-c-format +msgid "Release date: 2008/12/15" +msgstr "" + +#. Tag: para +#: release_notes.xml:1077 +#, no-c-format +msgid "If you are running PostGIS 1.1+, a soft upgrade is sufficient otherwise a hard upgrade is recommended. This release is a bug fix release to address a failure in ST_Force_Collection and related functions that critically affects using MapServer with LINE layers." +msgstr "" + +#. Tag: title +#: release_notes.xml:1084 +#, no-c-format +msgid "Release 1.3.4" +msgstr "" + +#. Tag: para +#: release_notes.xml:1085 +#, no-c-format +msgid "Release date: 2008/11/24" +msgstr "" + +#. Tag: para +#: release_notes.xml:1086 +#, no-c-format +msgid "This release adds support for GeoJSON output, building with PostgreSQL 8.4, improves documentation quality and output aesthetics, adds function-level SQL documentation, and improves performance for some spatial predicates (point-in-polygon tests)." +msgstr "" + +#. Tag: para +#: release_notes.xml:1091 +#, no-c-format +msgid "Bug fixes include removal of crashers in handling circular strings for many functions, some memory leaks removed, a linear referencing failure for measures on vertices, and more. See the NEWS file for details." +msgstr "" + +#. Tag: title +#: release_notes.xml:1098 +#, no-c-format +msgid "Release 1.3.3" +msgstr "" + +#. Tag: para +#: release_notes.xml:1100 +#, no-c-format +msgid "Release date: 2008/04/12" +msgstr "" + +#. Tag: para +#: release_notes.xml:1102 +#, no-c-format +msgid "This release fixes bugs shp2pgsql, adds enhancements to SVG and KML support, adds a ST_SimplifyPreserveTopology function, makes the build more sensitive to GEOS versions, and fixes a handful of severe but rare failure cases." +msgstr "" + +#. Tag: title +#: release_notes.xml:1109 +#, no-c-format +msgid "Release 1.3.2" +msgstr "" + +#. Tag: para +#: release_notes.xml:1111 +#, no-c-format +msgid "Release date: 2007/12/01" +msgstr "" + +#. Tag: para +#: release_notes.xml:1113 +#, no-c-format +msgid "This release fixes bugs in ST_EndPoint() and ST_Envelope, improves support for JDBC building and OS/X, and adds better support for GML output with ST_AsGML(), including GML3 output." +msgstr "" + +#. Tag: title +#: release_notes.xml:1119 +#, no-c-format +msgid "Release 1.3.1" +msgstr "" + +#. Tag: para +#: release_notes.xml:1121 +#, no-c-format +msgid "Release date: 2007/08/13" +msgstr "" + +#. Tag: para +#: release_notes.xml:1123 +#, no-c-format +msgid "This release fixes some oversights in the previous release around version numbering, documentation, and tagging." +msgstr "" + +#. Tag: title +#: release_notes.xml:1128 +#, no-c-format +msgid "Release 1.3.0" +msgstr "" + +#. Tag: para +#: release_notes.xml:1130 +#, no-c-format +msgid "Release date: 2007/08/09" +msgstr "" + +#. Tag: para +#: release_notes.xml:1132 +#, no-c-format +msgid "This release provides performance enhancements to the relational functions, adds new relational functions and begins the migration of our function names to the SQL-MM convention, using the spatial type (SP) prefix." +msgstr "" + +#. Tag: title +#: release_notes.xml:1138 +#, no-c-format +msgid "Added Functionality" +msgstr "" + +#. Tag: para +#: release_notes.xml:1140 +#, no-c-format +msgid "JDBC: Added Hibernate Dialect (thanks to Norman Barker)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1142 +#, no-c-format +msgid "Added ST_Covers and ST_CoveredBy relational functions. Description and justification of these functions can be found at http://lin-ear-th-inking.blogspot.com/2007/06/subtleties-of-ogc-covers-spatial.html" +msgstr "" + +#. Tag: para +#: release_notes.xml:1146 +#, no-c-format +msgid "Added ST_DWithin relational function." +msgstr "" + +#. Tag: title +#: release_notes.xml:1150 +#, no-c-format +msgid "Performance Enhancements" +msgstr "" + +#. Tag: para +#: release_notes.xml:1152 +#, no-c-format +msgid "Added cached and indexed point-in-polygon short-circuits for the functions ST_Contains, ST_Intersects, ST_Within and ST_Disjoint" +msgstr "" + +#. Tag: para +#: release_notes.xml:1155 +#, no-c-format +msgid "Added inline index support for relational functions (except ST_Disjoint)" +msgstr "" + +#. Tag: title +#: release_notes.xml:1160 +#, no-c-format +msgid "Other Changes" +msgstr "" + +#. Tag: para +#: release_notes.xml:1162 +#, no-c-format +msgid "Extended curved geometry support into the geometry accessor and some processing functions" +msgstr "" + +#. Tag: para +#: release_notes.xml:1165 +#, no-c-format +msgid "Began migration of functions to the SQL-MM naming convention; using a spatial type (ST) prefix." +msgstr "" + +#. Tag: para +#: release_notes.xml:1168 +#, no-c-format +msgid "Added initial support for PostgreSQL 8.3" +msgstr "" + +#. Tag: title +#: release_notes.xml:1173 +#, no-c-format +msgid "Release 1.2.1" +msgstr "" + +#. Tag: para +#: release_notes.xml:1175 +#, no-c-format +msgid "Release date: 2007/01/11" +msgstr "" + +#. Tag: para +#: release_notes.xml:1177 +#, no-c-format +msgid "This release provides bug fixes in PostgreSQL 8.2 support and some small performance enhancements." +msgstr "" + +#. Tag: title +#: release_notes.xml:1181 release_notes.xml:1209 release_notes.xml:2431 +#, no-c-format +msgid "Changes" +msgstr "" + +#. Tag: para +#: release_notes.xml:1183 +#, no-c-format +msgid "Fixed point-in-polygon shortcut bug in Within()." +msgstr "" + +#. Tag: para +#: release_notes.xml:1185 +#, no-c-format +msgid "Fixed PostgreSQL 8.2 NULL handling for indexes." +msgstr "" + +#. Tag: para +#: release_notes.xml:1187 +#, no-c-format +msgid "Updated RPM spec files." +msgstr "" + +#. Tag: para +#: release_notes.xml:1189 +#, no-c-format +msgid "Added short-circuit for Transform() in no-op case." +msgstr "" + +#. Tag: para +#: release_notes.xml:1191 +#, no-c-format +msgid "JDBC: Fixed JTS handling for multi-dimensional geometries (thanks to Thomas Marti for hint and partial patch). Additionally, now JavaDoc is compiled and packaged. Fixed classpath problems with GCJ. Fixed pgjdbc 8.2 compatibility, losing support for jdk 1.3 and older." +msgstr "" + +#. Tag: title +#: release_notes.xml:1200 +#, no-c-format +msgid "Release 1.2.0" +msgstr "" + +#. Tag: para +#: release_notes.xml:1202 +#, no-c-format +msgid "Release date: 2006/12/08" +msgstr "" + +#. Tag: para +#: release_notes.xml:1204 +#, no-c-format +msgid "This release provides type definitions along with serialization/deserialization capabilities for SQL-MM defined curved geometries, as well as performance enhancements." +msgstr "" + +#. Tag: para +#: release_notes.xml:1211 +#, no-c-format +msgid "Added curved geometry type support for serialization/deserialization" +msgstr "" + +#. Tag: para +#: release_notes.xml:1214 +#, no-c-format +msgid "Added point-in-polygon shortcircuit to the Contains and Within functions to improve performance for these cases." +msgstr "" + +#. Tag: title +#: release_notes.xml:1220 +#, no-c-format +msgid "Release 1.1.6" +msgstr "" + +#. Tag: para +#: release_notes.xml:1222 +#, no-c-format +msgid "Release date: 2006/11/02" +msgstr "" + +#. Tag: para +#: release_notes.xml:1224 +#, no-c-format +msgid "This is a bugfix release, in particular fixing a critical error with GEOS interface in 64bit systems. Includes an updated of the SRS parameters and an improvement in reprojections (take Z in consideration). Upgrade is encouraged." +msgstr "" + +#. Tag: title +#: release_notes.xml:1230 release_notes.xml:1281 release_notes.xml:1332 release_notes.xml:1387 release_notes.xml:1466 release_notes.xml:1532 release_notes.xml:1605 release_notes.xml:1749 release_notes.xml:1806 release_notes.xml:1869 release_notes.xml:1927 release_notes.xml:1985 release_notes.xml:2025 release_notes.xml:2077 release_notes.xml:2129 release_notes.xml:2168 release_notes.xml:2205 release_notes.xml:2272 release_notes.xml:2369 release_notes.xml:2423 +#, no-c-format +msgid "Upgrading" +msgstr "" + +#. Tag: para +#: release_notes.xml:1232 release_notes.xml:1283 release_notes.xml:1334 release_notes.xml:1389 release_notes.xml:1468 release_notes.xml:1534 +#, no-c-format +msgid "If you are upgrading from release 1.0.3 or later follow the soft upgrade procedure." +msgstr "" + +#. Tag: para +#: release_notes.xml:1235 release_notes.xml:1286 release_notes.xml:1337 release_notes.xml:1392 release_notes.xml:1471 release_notes.xml:1537 release_notes.xml:1613 release_notes.xml:1754 release_notes.xml:1811 release_notes.xml:1874 +#, no-c-format +msgid "If you are upgrading from a release between 1.0.0RC6 and 1.0.2 (inclusive) and really want a live upgrade read the upgrade section of the 1.0.3 release notes chapter." +msgstr "" + +#. Tag: para +#: release_notes.xml:1240 release_notes.xml:1291 release_notes.xml:1342 release_notes.xml:1397 release_notes.xml:1476 release_notes.xml:1542 release_notes.xml:1618 release_notes.xml:1759 release_notes.xml:1816 release_notes.xml:1879 +#, no-c-format +msgid "Upgrade from any release prior to 1.0.0RC6 requires an hard upgrade." +msgstr "" + +#. Tag: para +#: release_notes.xml:1247 +#, no-c-format +msgid "fixed CAPI change that broke 64-bit platforms" +msgstr "" + +#. Tag: para +#: release_notes.xml:1249 +#, no-c-format +msgid "loader/dumper: fixed regression tests and usage output" +msgstr "" + +#. Tag: para +#: release_notes.xml:1251 +#, no-c-format +msgid "Fixed setSRID() bug in JDBC, thanks to Thomas Marti" +msgstr "" + +#. Tag: title +#: release_notes.xml:1255 release_notes.xml:1439 release_notes.xml:1510 release_notes.xml:1724 release_notes.xml:1850 release_notes.xml:2151 release_notes.xml:2188 release_notes.xml:2240 release_notes.xml:2342 release_notes.xml:2405 +#, no-c-format +msgid "Other changes" +msgstr "" + +#. Tag: para +#: release_notes.xml:1257 +#, no-c-format +msgid "use Z ordinate in reprojections" +msgstr "" + +#. Tag: para +#: release_notes.xml:1259 +#, no-c-format +msgid "spatial_ref_sys.sql updated to EPSG 6.11.1" +msgstr "" + +#. Tag: para +#: release_notes.xml:1261 +#, no-c-format +msgid "Simplified Version.config infrastructure to use a single pack of version variables for everything." +msgstr "" + +#. Tag: para +#: release_notes.xml:1264 +#, no-c-format +msgid "Include the Version.config in loader/dumper USAGE messages" +msgstr "" + +#. Tag: para +#: release_notes.xml:1267 +#, no-c-format +msgid "Replace hand-made, fragile JDBC version parser with Properties" +msgstr "" + +#. Tag: title +#: release_notes.xml:1273 +#, no-c-format +msgid "Release 1.1.5" +msgstr "" + +#. Tag: para +#: release_notes.xml:1275 +#, no-c-format +msgid "Release date: 2006/10/13" +msgstr "" + +#. Tag: para +#: release_notes.xml:1277 +#, no-c-format +msgid "This is an bugfix release, including a critical segfault on win32. Upgrade is encouraged." +msgstr "" + +#. Tag: para +#: release_notes.xml:1298 +#, no-c-format +msgid "Fixed MingW link error that was causing pgsql2shp to segfault on Win32 when compiled for PostgreSQL 8.2" +msgstr "" + +#. Tag: para +#: release_notes.xml:1301 +#, no-c-format +msgid "fixed nullpointer Exception in Geometry.equals() method in Java" +msgstr "" + +#. Tag: para +#: release_notes.xml:1304 +#, no-c-format +msgid "Added EJB3Spatial.odt to fulfill the GPL requirement of distributing the \"preferred form of modification\"" +msgstr "" + +#. Tag: para +#: release_notes.xml:1307 +#, no-c-format +msgid "Removed obsolete synchronization from JDBC Jts code." +msgstr "" + +#. Tag: para +#: release_notes.xml:1309 +#, no-c-format +msgid "Updated heavily outdated README files for shp2pgsql/pgsql2shp by merging them with the manpages." +msgstr "" + +#. Tag: para +#: release_notes.xml:1312 +#, no-c-format +msgid "Fixed version tag in jdbc code that still said \"1.1.3\" in the \"1.1.4\" release." +msgstr "" + +#. Tag: para +#: release_notes.xml:1319 +#, no-c-format +msgid "Added -S option for non-multi geometries to shp2pgsql" +msgstr "" + +#. Tag: title +#: release_notes.xml:1324 +#, no-c-format +msgid "Release 1.1.4" +msgstr "" + +#. Tag: para +#: release_notes.xml:1326 +#, no-c-format +msgid "Release date: 2006/09/27" +msgstr "" + +#. Tag: para +#: release_notes.xml:1328 +#, no-c-format +msgid "This is an bugfix release including some improvements in the Java interface. Upgrade is encouraged." +msgstr "" + +#. Tag: para +#: release_notes.xml:1349 +#, no-c-format +msgid "Fixed support for PostgreSQL 8.2" +msgstr "" + +#. Tag: para +#: release_notes.xml:1351 +#, no-c-format +msgid "Fixed bug in collect() function discarding SRID of input" +msgstr "" + +#. Tag: para +#: release_notes.xml:1353 +#, no-c-format +msgid "Added SRID match check in MakeBox2d and MakeBox3d" +msgstr "" + +#. Tag: para +#: release_notes.xml:1355 +#, no-c-format +msgid "Fixed regress tests to pass with GEOS-3.0.0" +msgstr "" + +#. Tag: para +#: release_notes.xml:1357 +#, no-c-format +msgid "Improved pgsql2shp run concurrency." +msgstr "" + +#. Tag: title +#: release_notes.xml:1361 +#, no-c-format +msgid "Java changes" +msgstr "" + +#. Tag: para +#: release_notes.xml:1363 +#, no-c-format +msgid "reworked JTS support to reflect new upstream JTS developers' attitude to SRID handling. Simplifies code and drops build depend on GNU trove." +msgstr "" + +#. Tag: para +#: release_notes.xml:1367 +#, no-c-format +msgid "Added EJB2 support generously donated by the \"Geodetix s.r.l. Company\" http://www.geodetix.it/" +msgstr "" + +#. Tag: para +#: release_notes.xml:1370 +#, no-c-format +msgid "Added EJB3 tutorial / examples donated by Norman Barker <nbarker@ittvis.com>" +msgstr "" + +#. Tag: para +#: release_notes.xml:1373 +#, no-c-format +msgid "Reorganized java directory layout a little." +msgstr "" + +#. Tag: title +#: release_notes.xml:1378 +#, no-c-format +msgid "Release 1.1.3" +msgstr "" + +#. Tag: para +#: release_notes.xml:1380 +#, no-c-format +msgid "Release date: 2006/06/30" +msgstr "" + +#. Tag: para +#: release_notes.xml:1382 +#, no-c-format +msgid "This is an bugfix release including also some new functionalities (most notably long transaction support) and portability enhancements. Upgrade is encouraged." +msgstr "" + +#. Tag: title +#: release_notes.xml:1402 +#, no-c-format +msgid "Bug fixes / correctness" +msgstr "" + +#. Tag: para +#: release_notes.xml:1404 +#, no-c-format +msgid "BUGFIX in distance(poly,poly) giving wrong results." +msgstr "" + +#. Tag: para +#: release_notes.xml:1406 +#, no-c-format +msgid "BUGFIX in pgsql2shp successful return code." +msgstr "" + +#. Tag: para +#: release_notes.xml:1408 +#, no-c-format +msgid "BUGFIX in shp2pgsql handling of MultiLine WKT." +msgstr "" + +#. Tag: para +#: release_notes.xml:1410 +#, no-c-format +msgid "BUGFIX in affine() failing to update bounding box." +msgstr "" + +#. Tag: para +#: release_notes.xml:1412 +#, no-c-format +msgid "WKT parser: forbidden construction of multigeometries with EMPTY elements (still supported for GEOMETRYCOLLECTION)." +msgstr "" + +#. Tag: title +#: release_notes.xml:1417 release_notes.xml:1493 release_notes.xml:1566 +#, no-c-format +msgid "New functionalities" +msgstr "" + +#. Tag: para +#: release_notes.xml:1419 +#, no-c-format +msgid "NEW Long Transactions support." +msgstr "" + +#. Tag: para +#: release_notes.xml:1421 +#, no-c-format +msgid "NEW DumpRings() function." +msgstr "" + +#. Tag: para +#: release_notes.xml:1423 +#, no-c-format +msgid "NEW AsHEXEWKB(geom, XDR|NDR) function." +msgstr "" + +#. Tag: title +#: release_notes.xml:1427 release_notes.xml:2318 +#, no-c-format +msgid "JDBC changes" +msgstr "" + +#. Tag: para +#: release_notes.xml:1429 +#, no-c-format +msgid "Improved regression tests: MultiPoint and scientific ordinates" +msgstr "" + +#. Tag: para +#: release_notes.xml:1432 +#, no-c-format +msgid "Fixed some minor bugs in jdbc code" +msgstr "" + +#. Tag: para +#: release_notes.xml:1434 +#, no-c-format +msgid "Added proper accessor functions for all fields in preparation of making those fields private later" +msgstr "" + +#. Tag: para +#: release_notes.xml:1441 +#, no-c-format +msgid "NEW regress test support for loader/dumper." +msgstr "" + +#. Tag: para +#: release_notes.xml:1443 +#, no-c-format +msgid "Added --with-proj-libdir and --with-geos-libdir configure switches." +msgstr "" + +#. Tag: para +#: release_notes.xml:1446 +#, no-c-format +msgid "Support for build Tru64 build." +msgstr "" + +#. Tag: para +#: release_notes.xml:1448 +#, no-c-format +msgid "Use Jade for generating documentation." +msgstr "" + +#. Tag: para +#: release_notes.xml:1450 +#, no-c-format +msgid "Don't link pgsql2shp to more libs then required." +msgstr "" + +#. Tag: para +#: release_notes.xml:1452 +#, no-c-format +msgid "Initial support for PostgreSQL 8.2." +msgstr "" + +#. Tag: title +#: release_notes.xml:1457 +#, no-c-format +msgid "Release 1.1.2" +msgstr "" + +#. Tag: para +#: release_notes.xml:1459 +#, no-c-format +msgid "Release date: 2006/03/30" +msgstr "" + +#. Tag: para +#: release_notes.xml:1461 +#, no-c-format +msgid "This is an bugfix release including some new functions and portability enhancements. Upgrade is encouraged." +msgstr "" + +#. Tag: para +#: release_notes.xml:1483 +#, no-c-format +msgid "BUGFIX in SnapToGrid() computation of output bounding box" +msgstr "" + +#. Tag: para +#: release_notes.xml:1485 +#, no-c-format +msgid "BUGFIX in EnforceRHR()" +msgstr "" + +#. Tag: para +#: release_notes.xml:1487 +#, no-c-format +msgid "jdbc2 SRID handling fixes in JTS code" +msgstr "" + +#. Tag: para +#: release_notes.xml:1489 +#, no-c-format +msgid "Fixed support for 64bit archs" +msgstr "" + +#. Tag: para +#: release_notes.xml:1495 +#, no-c-format +msgid "Regress tests can now be run *before* postgis installation" +msgstr "" + +#. Tag: para +#: release_notes.xml:1498 +#, no-c-format +msgid "New affine() matrix transformation functions" +msgstr "" + +#. Tag: para +#: release_notes.xml:1500 +#, no-c-format +msgid "New rotate{,X,Y,Z}() function" +msgstr "" + +#. Tag: para +#: release_notes.xml:1502 +#, no-c-format +msgid "Old translating and scaling functions now use affine() internally" +msgstr "" + +#. Tag: para +#: release_notes.xml:1505 +#, no-c-format +msgid "Embedded access control in estimated_extent() for builds against pgsql >= 8.0.0" +msgstr "" + +#. Tag: para +#: release_notes.xml:1512 +#, no-c-format +msgid "More portable ./configure script" +msgstr "" + +#. Tag: para +#: release_notes.xml:1514 +#, no-c-format +msgid "Changed ./run_test script to have more sane default behaviour" +msgstr "" + +#. Tag: title +#: release_notes.xml:1520 +#, no-c-format +msgid "Release 1.1.1" +msgstr "" + +#. Tag: para +#: release_notes.xml:1522 +#, no-c-format +msgid "Release date: 2006/01/23" +msgstr "" + +#. Tag: para +#: release_notes.xml:1524 +#, no-c-format +msgid "This is an important Bugfix release, upgrade is highly recommended. Previous version contained a bug in postgis_restore.pl preventing hard upgrade procedure to complete and a bug in GEOS-2.2+ connector preventing GeometryCollection objects to be used in topological operations." +msgstr "" + +#. Tag: para +#: release_notes.xml:1549 +#, no-c-format +msgid "Fixed a premature exit in postgis_restore.pl" +msgstr "" + +#. Tag: para +#: release_notes.xml:1551 +#, no-c-format +msgid "BUGFIX in geometrycollection handling of GEOS-CAPI connector" +msgstr "" + +#. Tag: para +#: release_notes.xml:1554 +#, no-c-format +msgid "Solaris 2.7 and MingW support improvements" +msgstr "" + +#. Tag: para +#: release_notes.xml:1556 +#, no-c-format +msgid "BUGFIX in line_locate_point()" +msgstr "" + +#. Tag: para +#: release_notes.xml:1558 +#, no-c-format +msgid "Fixed handling of postgresql paths" +msgstr "" + +#. Tag: para +#: release_notes.xml:1560 +#, no-c-format +msgid "BUGFIX in line_substring()" +msgstr "" + +#. Tag: para +#: release_notes.xml:1562 +#, no-c-format +msgid "Added support for localized cluster in regress tester" +msgstr "" + +#. Tag: para +#: release_notes.xml:1568 +#, no-c-format +msgid "New Z and M interpolation in line_substring()" +msgstr "" + +#. Tag: para +#: release_notes.xml:1570 +#, no-c-format +msgid "New Z and M interpolation in line_interpolate_point()" +msgstr "" + +#. Tag: para +#: release_notes.xml:1572 +#, no-c-format +msgid "added NumInteriorRing() alias due to OpenGIS ambiguity" +msgstr "" + +#. Tag: title +#: release_notes.xml:1577 +#, no-c-format +msgid "Release 1.1.0" +msgstr "" + +#. Tag: para +#: release_notes.xml:1579 +#, no-c-format +msgid "Release date: 2005/12/21" +msgstr "" + +#. Tag: para +#: release_notes.xml:1581 +#, no-c-format +msgid "This is a Minor release, containing many improvements and new things. Most notably: build procedure greatly simplified; transform() performance drastically improved; more stable GEOS connectivity (CAPI support); lots of new functions; draft topology support." +msgstr "" + +#. Tag: para +#: release_notes.xml:1586 +#, no-c-format +msgid "It is highly recommended that you upgrade to GEOS-2.2.x before installing PostGIS, this will ensure future GEOS upgrades won't require a rebuild of the PostGIS library." +msgstr "" + +#. Tag: title +#: release_notes.xml:1591 +#, no-c-format +msgid "Credits" +msgstr "" + +#. Tag: para +#: release_notes.xml:1593 +#, no-c-format +msgid "This release includes code from Mark Cave Ayland for caching of proj4 objects. Markus Schaber added many improvements in his JDBC2 code. Alex Bodnaru helped with PostgreSQL source dependency relief and provided Debian specfiles. Michael Fuhr tested new things on Solaris arch. David Techer and Gerald Fenoy helped testing GEOS C-API connector. Hartmut Tschauner provided code for the azimuth() function. Devrim GUNDUZ provided RPM specfiles. Carl Anderson helped with the new area building functions. See the credits section for more names." +msgstr "" + +#. Tag: para +#: release_notes.xml:1607 +#, no-c-format +msgid "If you are upgrading from release 1.0.3 or later you DO NOT need a dump/reload. Simply sourcing the new lwpostgis_upgrade.sql script in all your existing databases will work. See the soft upgrade chapter for more information." +msgstr "" + +#. Tag: title +#: release_notes.xml:1623 +#, no-c-format +msgid "New functions" +msgstr "" + +#. Tag: para +#: release_notes.xml:1625 +#, no-c-format +msgid "scale() and transscale() companion methods to translate()" +msgstr "" + +#. Tag: para +#: release_notes.xml:1627 +#, no-c-format +msgid "line_substring()" +msgstr "" + +#. Tag: para +#: release_notes.xml:1629 +#, no-c-format +msgid "line_locate_point()" +msgstr "" + +#. Tag: para +#: release_notes.xml:1631 +#, no-c-format +msgid "M(point)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1633 +#, no-c-format +msgid "LineMerge(geometry)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1635 +#, no-c-format +msgid "shift_longitude(geometry)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1637 +#, no-c-format +msgid "azimuth(geometry)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1639 +#, no-c-format +msgid "locate_along_measure(geometry, float8)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1641 +#, no-c-format +msgid "locate_between_measures(geometry, float8, float8)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1643 +#, no-c-format +msgid "SnapToGrid by point offset (up to 4d support)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1645 +#, no-c-format +msgid "BuildArea(any_geometry)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1647 +#, no-c-format +msgid "OGC BdPolyFromText(linestring_wkt, srid)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1649 +#, no-c-format +msgid "OGC BdMPolyFromText(linestring_wkt, srid)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1651 +#, no-c-format +msgid "RemovePoint(linestring, offset)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1653 +#, no-c-format +msgid "ReplacePoint(linestring, offset, point)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1659 +#, no-c-format +msgid "Fixed memory leak in polygonize()" +msgstr "" + +#. Tag: para +#: release_notes.xml:1661 +#, no-c-format +msgid "Fixed bug in lwgeom_as_anytype cast functions" +msgstr "" + +#. Tag: para +#: release_notes.xml:1663 +#, no-c-format +msgid "Fixed USE_GEOS, USE_PROJ and USE_STATS elements of postgis_version() output to always reflect library state." +msgstr "" + +#. Tag: title +#: release_notes.xml:1668 +#, no-c-format +msgid "Function semantic changes" +msgstr "" + +#. Tag: para +#: release_notes.xml:1670 +#, no-c-format +msgid "SnapToGrid doesn't discard higher dimensions" +msgstr "" + +#. Tag: para +#: release_notes.xml:1672 +#, no-c-format +msgid "Changed Z() function to return NULL if requested dimension is not available" +msgstr "" + +#. Tag: title +#: release_notes.xml:1677 +#, no-c-format +msgid "Performance improvements" +msgstr "" + +#. Tag: para +#: release_notes.xml:1679 +#, no-c-format +msgid "Much faster transform() function, caching proj4 objects" +msgstr "" + +#. Tag: para +#: release_notes.xml:1681 +#, no-c-format +msgid "Removed automatic call to fix_geometry_columns() in AddGeometryColumns() and update_geometry_stats()" +msgstr "" + +#. Tag: title +#: release_notes.xml:1686 +#, no-c-format +msgid "JDBC2 works" +msgstr "" + +#. Tag: para +#: release_notes.xml:1688 +#, no-c-format +msgid "Makefile improvements" +msgstr "" + +#. Tag: para +#: release_notes.xml:1690 release_notes.xml:1726 +#, no-c-format +msgid "JTS support improvements" +msgstr "" + +#. Tag: para +#: release_notes.xml:1692 +#, no-c-format +msgid "Improved regression test system" +msgstr "" + +#. Tag: para +#: release_notes.xml:1694 +#, no-c-format +msgid "Basic consistency check method for geometry collections" +msgstr "" + +#. Tag: para +#: release_notes.xml:1696 +#, no-c-format +msgid "Support for (Hex)(E)wkb" +msgstr "" + +#. Tag: para +#: release_notes.xml:1698 +#, no-c-format +msgid "Autoprobing DriverWrapper for HexWKB / EWKT switching" +msgstr "" + +#. Tag: para +#: release_notes.xml:1700 +#, no-c-format +msgid "fix compile problems in ValueSetter for ancient jdk releases." +msgstr "" + +#. Tag: para +#: release_notes.xml:1703 +#, no-c-format +msgid "fix EWKT constructors to accept SRID=4711; representation" +msgstr "" + +#. Tag: para +#: release_notes.xml:1705 +#, no-c-format +msgid "added preliminary read-only support for java2d geometries" +msgstr "" + +#. Tag: title +#: release_notes.xml:1709 +#, no-c-format +msgid "Other new things" +msgstr "" + +#. Tag: para +#: release_notes.xml:1711 +#, no-c-format +msgid "Full autoconf-based configuration, with PostgreSQL source dependency relief" +msgstr "" + +#. Tag: para +#: release_notes.xml:1714 +#, no-c-format +msgid "GEOS C-API support (2.2.0 and higher)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1716 +#, no-c-format +msgid "Initial support for topology modelling" +msgstr "" + +#. Tag: para +#: release_notes.xml:1718 +#, no-c-format +msgid "Debian and RPM specfiles" +msgstr "" + +#. Tag: para +#: release_notes.xml:1720 +#, no-c-format +msgid "New lwpostgis_upgrade.sql script" +msgstr "" + +#. Tag: para +#: release_notes.xml:1728 +#, no-c-format +msgid "Stricter mapping between DBF and SQL integer and string attributes" +msgstr "" + +#. Tag: para +#: release_notes.xml:1731 +#, no-c-format +msgid "Wider and cleaner regression test suite" +msgstr "" + +#. Tag: para +#: release_notes.xml:1733 +#, no-c-format +msgid "old jdbc code removed from release" +msgstr "" + +#. Tag: para +#: release_notes.xml:1735 +#, no-c-format +msgid "obsoleted direct use of postgis_proc_upgrade.pl" +msgstr "" + +#. Tag: para +#: release_notes.xml:1737 +#, no-c-format +msgid "scripts version unified with release version" +msgstr "" + +#. Tag: title +#: release_notes.xml:1742 +#, no-c-format +msgid "Release 1.0.6" +msgstr "" + +#. Tag: para +#: release_notes.xml:1744 +#, no-c-format +msgid "Release date: 2005/12/06" +msgstr "" + +#. Tag: para +#: release_notes.xml:1746 release_notes.xml:1982 +#, no-c-format +msgid "Contains a few bug fixes and improvements." +msgstr "" + +#. Tag: para +#: release_notes.xml:1751 release_notes.xml:1808 +#, no-c-format +msgid "If you are upgrading from release 1.0.3 or later you DO NOT need a dump/reload." +msgstr "" + +#. Tag: para +#: release_notes.xml:1766 +#, no-c-format +msgid "Fixed palloc(0) call in collection deserializer (only gives problem with --enable-cassert)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1769 +#, no-c-format +msgid "Fixed bbox cache handling bugs" +msgstr "" + +#. Tag: para +#: release_notes.xml:1771 +#, no-c-format +msgid "Fixed geom_accum(NULL, NULL) segfault" +msgstr "" + +#. Tag: para +#: release_notes.xml:1773 +#, no-c-format +msgid "Fixed segfault in addPoint()" +msgstr "" + +#. Tag: para +#: release_notes.xml:1775 +#, no-c-format +msgid "Fixed short-allocation in lwcollection_clone()" +msgstr "" + +#. Tag: para +#: release_notes.xml:1777 +#, no-c-format +msgid "Fixed bug in segmentize()" +msgstr "" + +#. Tag: para +#: release_notes.xml:1779 +#, no-c-format +msgid "Fixed bbox computation of SnapToGrid output" +msgstr "" + +#. Tag: title +#: release_notes.xml:1783 release_notes.xml:1901 release_notes.xml:1963 release_notes.xml:2009 +#, no-c-format +msgid "Improvements" +msgstr "" + +#. Tag: para +#: release_notes.xml:1785 +#, no-c-format +msgid "Initial support for postgresql 8.2" +msgstr "" + +#. Tag: para +#: release_notes.xml:1787 +#, no-c-format +msgid "Added missing SRID mismatch checks in GEOS ops" +msgstr "" + +#. Tag: title +#: release_notes.xml:1792 +#, no-c-format +msgid "Release 1.0.5" +msgstr "" + +#. Tag: para +#: release_notes.xml:1794 +#, no-c-format +msgid "Release date: 2005/11/25" +msgstr "" + +#. Tag: para +#: release_notes.xml:1796 +#, no-c-format +msgid "Contains memory-alignment fixes in the library, a segfault fix in loader's handling of UTF8 attributes and a few improvements and cleanups." +msgstr "" + +#. Tag: para +#: release_notes.xml:1801 +#, no-c-format +msgid "Return code of shp2pgsql changed from previous releases to conform to unix standards (return 0 on success)." +msgstr "" + +#. Tag: title +#: release_notes.xml:1821 release_notes.xml:2036 release_notes.xml:2088 release_notes.xml:2137 release_notes.xml:2179 release_notes.xml:2213 release_notes.xml:2280 release_notes.xml:2377 +#, no-c-format +msgid "Library changes" +msgstr "" + +#. Tag: para +#: release_notes.xml:1823 +#, no-c-format +msgid "Fixed memory alignment problems" +msgstr "" + +#. Tag: para +#: release_notes.xml:1825 +#, no-c-format +msgid "Fixed computation of null values fraction in analyzer" +msgstr "" + +#. Tag: para +#: release_notes.xml:1827 +#, no-c-format +msgid "Fixed a small bug in the getPoint4d_p() low-level function" +msgstr "" + +#. Tag: para +#: release_notes.xml:1830 +#, no-c-format +msgid "Speedup of serializer functions" +msgstr "" + +#. Tag: para +#: release_notes.xml:1832 +#, no-c-format +msgid "Fixed a bug in force_3dm(), force_3dz() and force_4d()" +msgstr "" + +#. Tag: title +#: release_notes.xml:1836 +#, no-c-format +msgid "Loader changes" +msgstr "" + +#. Tag: para +#: release_notes.xml:1838 +#, no-c-format +msgid "Fixed return code of shp2pgsql" +msgstr "" + +#. Tag: para +#: release_notes.xml:1840 +#, no-c-format +msgid "Fixed back-compatibility issue in loader (load of null shapefiles)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1843 +#, no-c-format +msgid "Fixed handling of trailing dots in dbf numerical attributes" +msgstr "" + +#. Tag: para +#: release_notes.xml:1846 +#, no-c-format +msgid "Segfault fix in shp2pgsql (utf8 encoding)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1852 +#, no-c-format +msgid "Schema aware postgis_proc_upgrade.pl, support for pgsql 7.2+" +msgstr "" + +#. Tag: para +#: release_notes.xml:1855 +#, no-c-format +msgid "New \"Reporting Bugs\" chapter in manual" +msgstr "" + +#. Tag: title +#: release_notes.xml:1860 +#, no-c-format +msgid "Release 1.0.4" +msgstr "" + +#. Tag: para +#: release_notes.xml:1862 +#, no-c-format +msgid "Release date: 2005/09/09" +msgstr "" + +#. Tag: para +#: release_notes.xml:1864 +#, no-c-format +msgid "Contains important bug fixes and a few improvements. In particular, it fixes a memory leak preventing successful build of GiST indexes for large spatial tables." +msgstr "" + +#. Tag: para +#: release_notes.xml:1871 +#, no-c-format +msgid "If you are upgrading from release 1.0.3 you DO NOT need a dump/reload." +msgstr "" + +#. Tag: para +#: release_notes.xml:1886 +#, no-c-format +msgid "Memory leak plugged in GiST indexing" +msgstr "" + +#. Tag: para +#: release_notes.xml:1888 +#, no-c-format +msgid "Segfault fix in transform() handling of proj4 errors" +msgstr "" + +#. Tag: para +#: release_notes.xml:1890 +#, no-c-format +msgid "Fixed some proj4 texts in spatial_ref_sys (missing +proj)" +msgstr "" + +#. Tag: para +#: release_notes.xml:1892 +#, no-c-format +msgid "Loader: fixed string functions usage, reworked NULL objects check, fixed segfault on MULTILINESTRING input." +msgstr "" + +#. Tag: para +#: release_notes.xml:1895 +#, no-c-format +msgid "Fixed bug in MakeLine dimension handling" +msgstr "" + +#. Tag: para +#: release_notes.xml:1897 +#, no-c-format +msgid "Fixed bug in translate() corrupting output bounding box" +msgstr "" + +#. Tag: para +#: release_notes.xml:1903 +#, no-c-format +msgid "Documentation improvements" +msgstr "" + +#. Tag: para +#: release_notes.xml:1905 +#, no-c-format +msgid "More robust selectivity estimator" +msgstr "" + +#. Tag: para +#: release_notes.xml:1907 +#, no-c-format +msgid "Minor speedup in distance()" +msgstr "" + +#. Tag: para +#: release_notes.xml:1909 +#, no-c-format +msgid "Minor cleanups" +msgstr "" + +#. Tag: para +#: release_notes.xml:1911 +#, no-c-format +msgid "GiST indexing cleanup" +msgstr "" + +#. Tag: para +#: release_notes.xml:1913 +#, no-c-format +msgid "Looser syntax acceptance in box3d parser" +msgstr "" + +#. Tag: title +#: release_notes.xml:1918 +#, no-c-format +msgid "Release 1.0.3" +msgstr "" + +#. Tag: para +#: release_notes.xml:1920 +#, no-c-format +msgid "Release date: 2005/08/08" +msgstr "" + +#. Tag: para +#: release_notes.xml:1922 +#, no-c-format +msgid "Contains some bug fixes - including a severe one affecting correctness of stored geometries - and a few improvements." +msgstr "" + +#. Tag: para +#: release_notes.xml:1929 +#, no-c-format +msgid "Due to a bug in a bounding box computation routine, the upgrade procedure requires special attention, as bounding boxes cached in the database could be incorrect." +msgstr "" + +#. Tag: para +#: release_notes.xml:1933 +#, no-c-format +msgid "An hard upgrade procedure (dump/reload) will force recomputation of all bounding boxes (not included in dumps). This is required if upgrading from releases prior to 1.0.0RC6." +msgstr "" + +#. Tag: para +#: release_notes.xml:1938 +#, no-c-format +msgid "If you are upgrading from versions 1.0.0RC6 or up, this release includes a perl script (utils/rebuild_bbox_caches.pl) to force recomputation of geometries' bounding boxes and invoke all operations required to propagate eventual changes in them (geometry statistics update, reindexing). Invoke the script after a make install (run with no args for syntax help). Optionally run utils/postgis_proc_upgrade.pl to refresh postgis procedures and functions signatures (see Soft upgrade)." +msgstr "" + +#. Tag: para +#: release_notes.xml:1951 +#, no-c-format +msgid "Severe bugfix in lwgeom's 2d bounding box computation" +msgstr "" + +#. Tag: para +#: release_notes.xml:1953 +#, no-c-format +msgid "Bugfix in WKT (-w) POINT handling in loader" +msgstr "" + +#. Tag: para +#: release_notes.xml:1955 +#, no-c-format +msgid "Bugfix in dumper on 64bit machines" +msgstr "" + +#. Tag: para +#: release_notes.xml:1957 +#, no-c-format +msgid "Bugfix in dumper handling of user-defined queries" +msgstr "" + +#. Tag: para +#: release_notes.xml:1959 +#, no-c-format +msgid "Bugfix in create_undef.pl script" +msgstr "" + +#. Tag: para +#: release_notes.xml:1965 +#, no-c-format +msgid "Small performance improvement in canonical input function" +msgstr "" + +#. Tag: para +#: release_notes.xml:1967 +#, no-c-format +msgid "Minor cleanups in loader" +msgstr "" + +#. Tag: para +#: release_notes.xml:1969 +#, no-c-format +msgid "Support for multibyte field names in loader" +msgstr "" + +#. Tag: para +#: release_notes.xml:1971 +#, no-c-format +msgid "Improvement in the postgis_restore.pl script" +msgstr "" + +#. Tag: para +#: release_notes.xml:1973 +#, no-c-format +msgid "New rebuild_bbox_caches.pl util script" +msgstr "" + +#. Tag: title +#: release_notes.xml:1978 +#, no-c-format +msgid "Release 1.0.2" +msgstr "" + +#. Tag: para +#: release_notes.xml:1980 +#, no-c-format +msgid "Release date: 2005/07/04" +msgstr "" + +#. Tag: para +#: release_notes.xml:1987 release_notes.xml:2027 +#, no-c-format +msgid "If you are upgrading from release 1.0.0RC6 or up you DO NOT need a dump/reload." +msgstr "" + +#. Tag: para +#: release_notes.xml:1990 release_notes.xml:2030 +#, no-c-format +msgid "Upgrading from older releases requires a dump/reload. See the upgrading chapter for more informations." +msgstr "" + +#. Tag: para +#: release_notes.xml:1998 +#, no-c-format +msgid "Fault tolerant btree ops" +msgstr "" + +#. Tag: para +#: release_notes.xml:2000 +#, no-c-format +msgid "Memory leak plugged in pg_error" +msgstr "" + +#. Tag: para +#: release_notes.xml:2002 +#, no-c-format +msgid "Rtree index fix" +msgstr "" + +#. Tag: para +#: release_notes.xml:2004 +#, no-c-format +msgid "Cleaner build scripts (avoided mix of CFLAGS and CXXFLAGS)" +msgstr "" + +#. Tag: para +#: release_notes.xml:2011 +#, no-c-format +msgid "New index creation capabilities in loader (-I switch)" +msgstr "" + +#. Tag: para +#: release_notes.xml:2013 +#, no-c-format +msgid "Initial support for postgresql 8.1dev" +msgstr "" + +#. Tag: title +#: release_notes.xml:2018 +#, no-c-format +msgid "Release 1.0.1" +msgstr "" + +#. Tag: para +#: release_notes.xml:2020 +#, no-c-format +msgid "Release date: 2005/05/24" +msgstr "" + +#. Tag: para +#: release_notes.xml:2022 +#, no-c-format +msgid "Contains a few bug fixes and some improvements." +msgstr "" + +#. Tag: para +#: release_notes.xml:2038 +#, no-c-format +msgid "BUGFIX in 3d computation of length_spheroid()" +msgstr "" + +#. Tag: para +#: release_notes.xml:2040 +#, no-c-format +msgid "BUGFIX in join selectivity estimator" +msgstr "" + +#. Tag: title +#: release_notes.xml:2044 release_notes.xml:2100 +#, no-c-format +msgid "Other changes/additions" +msgstr "" + +#. Tag: para +#: release_notes.xml:2046 +#, no-c-format +msgid "BUGFIX in shp2pgsql escape functions" +msgstr "" + +#. Tag: para +#: release_notes.xml:2048 +#, no-c-format +msgid "better support for concurrent postgis in multiple schemas" +msgstr "" + +#. Tag: para +#: release_notes.xml:2050 +#, no-c-format +msgid "documentation fixes" +msgstr "" + +#. Tag: para +#: release_notes.xml:2052 +#, no-c-format +msgid "jdbc2: compile with \"-target 1.2 -source 1.2\" by default" +msgstr "" + +#. Tag: para +#: release_notes.xml:2054 +#, no-c-format +msgid "NEW -k switch for pgsql2shp" +msgstr "" + +#. Tag: para +#: release_notes.xml:2056 +#, no-c-format +msgid "NEW support for custom createdb options in postgis_restore.pl" +msgstr "" + +#. Tag: para +#: release_notes.xml:2059 +#, no-c-format +msgid "BUGFIX in pgsql2shp attribute names unicity enforcement" +msgstr "" + +#. Tag: para +#: release_notes.xml:2061 +#, no-c-format +msgid "BUGFIX in Paris projections definitions" +msgstr "" + +#. Tag: para +#: release_notes.xml:2063 +#, no-c-format +msgid "postgis_restore.pl cleanups" +msgstr "" + +#. Tag: title +#: release_notes.xml:2068 +#, no-c-format +msgid "Release 1.0.0" +msgstr "" + +#. Tag: para +#: release_notes.xml:2070 +#, no-c-format +msgid "Release date: 2005/04/19" +msgstr "" + +#. Tag: para +#: release_notes.xml:2072 +#, no-c-format +msgid "Final 1.0.0 release. Contains a few bug fixes, some improvements in the loader (most notably support for older postgis versions), and more docs." +msgstr "" + +#. Tag: para +#: release_notes.xml:2079 +#, no-c-format +msgid "If you are upgrading from release 1.0.0RC6 you DO NOT need a dump/reload." +msgstr "" + +#. Tag: para +#: release_notes.xml:2082 release_notes.xml:2173 +#, no-c-format +msgid "Upgrading from any other precedent release requires a dump/reload. See the upgrading chapter for more informations." +msgstr "" + +#. Tag: para +#: release_notes.xml:2090 +#, no-c-format +msgid "BUGFIX in transform() releasing random memory address" +msgstr "" + +#. Tag: para +#: release_notes.xml:2092 +#, no-c-format +msgid "BUGFIX in force_3dm() allocating less memory then required" +msgstr "" + +#. Tag: para +#: release_notes.xml:2095 +#, no-c-format +msgid "BUGFIX in join selectivity estimator (defaults, leaks, tuplecount, sd)" +msgstr "" + +#. Tag: para +#: release_notes.xml:2102 +#, no-c-format +msgid "BUGFIX in shp2pgsql escape of values starting with tab or single-quote" +msgstr "" + +#. Tag: para +#: release_notes.xml:2105 +#, no-c-format +msgid "NEW manual pages for loader/dumper" +msgstr "" + +#. Tag: para +#: release_notes.xml:2107 +#, no-c-format +msgid "NEW shp2pgsql support for old (HWGEOM) postgis versions" +msgstr "" + +#. Tag: para +#: release_notes.xml:2109 +#, no-c-format +msgid "NEW -p (prepare) flag for shp2pgsql" +msgstr "" + +#. Tag: para +#: release_notes.xml:2111 +#, no-c-format +msgid "NEW manual chapter about OGC compliancy enforcement" +msgstr "" + +#. Tag: para +#: release_notes.xml:2113 +#, no-c-format +msgid "NEW autoconf support for JTS lib" +msgstr "" + +#. Tag: para +#: release_notes.xml:2115 +#, no-c-format +msgid "BUGFIX in estimator testers (support for LWGEOM and schema parsing)" +msgstr "" + +#. Tag: title +#: release_notes.xml:2121 +#, no-c-format +msgid "Release 1.0.0RC6" +msgstr "" + +#. Tag: para +#: release_notes.xml:2123 +#, no-c-format +msgid "Release date: 2005/03/30" +msgstr "" + +#. Tag: para +#: release_notes.xml:2125 +#, no-c-format +msgid "Sixth release candidate for 1.0.0. Contains a few bug fixes and cleanups." +msgstr "" + +#. Tag: para +#: release_notes.xml:2131 release_notes.xml:2207 release_notes.xml:2274 release_notes.xml:2371 release_notes.xml:2425 +#, no-c-format +msgid "You need a dump/reload to upgrade from precedent releases. See the upgrading chapter for more informations." +msgstr "" + +#. Tag: para +#: release_notes.xml:2139 +#, no-c-format +msgid "BUGFIX in multi()" +msgstr "" + +#. Tag: para +#: release_notes.xml:2141 +#, no-c-format +msgid "early return [when noop] from multi()" +msgstr "" + +#. Tag: title +#: release_notes.xml:2145 release_notes.xml:2231 release_notes.xml:2304 release_notes.xml:2396 +#, no-c-format +msgid "Scripts changes" +msgstr "" + +#. Tag: para +#: release_notes.xml:2147 +#, no-c-format +msgid "dropped {x,y}{min,max}(box2d) functions" +msgstr "" + +#. Tag: para +#: release_notes.xml:2153 +#, no-c-format +msgid "BUGFIX in postgis_restore.pl scrip" +msgstr "" + +#. Tag: para +#: release_notes.xml:2155 +#, no-c-format +msgid "BUGFIX in dumper's 64bit support" +msgstr "" + +#. Tag: title +#: release_notes.xml:2160 +#, no-c-format +msgid "Release 1.0.0RC5" +msgstr "" + +#. Tag: para +#: release_notes.xml:2162 +#, no-c-format +msgid "Release date: 2005/03/25" +msgstr "" + +#. Tag: para +#: release_notes.xml:2164 +#, no-c-format +msgid "Fifth release candidate for 1.0.0. Contains a few bug fixes and a improvements." +msgstr "" + +#. Tag: para +#: release_notes.xml:2170 +#, no-c-format +msgid "If you are upgrading from release 1.0.0RC4 you DO NOT need a dump/reload." +msgstr "" + +#. Tag: para +#: release_notes.xml:2181 +#, no-c-format +msgid "BUGFIX (segfaulting) in box3d computation (yes, another!)." +msgstr "" + +#. Tag: para +#: release_notes.xml:2184 +#, no-c-format +msgid "BUGFIX (segfaulting) in estimated_extent()." +msgstr "" + +#. Tag: para +#: release_notes.xml:2190 +#, no-c-format +msgid "Small build scripts and utilities refinements." +msgstr "" + +#. Tag: para +#: release_notes.xml:2192 +#, no-c-format +msgid "Additional performance tips documented." +msgstr "" + +#. Tag: title +#: release_notes.xml:2197 +#, no-c-format +msgid "Release 1.0.0RC4" +msgstr "" + +#. Tag: para +#: release_notes.xml:2199 +#, no-c-format +msgid "Release date: 2005/03/18" +msgstr "" + +#. Tag: para +#: release_notes.xml:2201 +#, no-c-format +msgid "Fourth release candidate for 1.0.0. Contains bug fixes and a few improvements." +msgstr "" + +#. Tag: para +#: release_notes.xml:2215 +#, no-c-format +msgid "BUGFIX (segfaulting) in geom_accum()." +msgstr "" + +#. Tag: para +#: release_notes.xml:2217 +#, no-c-format +msgid "BUGFIX in 64bit architectures support." +msgstr "" + +#. Tag: para +#: release_notes.xml:2219 +#, no-c-format +msgid "BUGFIX in box3d computation function with collections." +msgstr "" + +#. Tag: para +#: release_notes.xml:2221 +#, no-c-format +msgid "NEW subselects support in selectivity estimator." +msgstr "" + +#. Tag: para +#: release_notes.xml:2223 +#, no-c-format +msgid "Early return from force_collection." +msgstr "" + +#. Tag: para +#: release_notes.xml:2225 +#, no-c-format +msgid "Consistency check fix in SnapToGrid()." +msgstr "" + +#. Tag: para +#: release_notes.xml:2227 +#, no-c-format +msgid "Box2d output changed back to 15 significant digits." +msgstr "" + +#. Tag: para +#: release_notes.xml:2233 +#, no-c-format +msgid "NEW distance_sphere() function." +msgstr "" + +#. Tag: para +#: release_notes.xml:2235 +#, no-c-format +msgid "Changed get_proj4_from_srid implementation to use PL/PGSQL instead of SQL." +msgstr "" + +#. Tag: para +#: release_notes.xml:2242 +#, no-c-format +msgid "BUGFIX in loader and dumper handling of MultiLine shapes" +msgstr "" + +#. Tag: para +#: release_notes.xml:2244 +#, no-c-format +msgid "BUGFIX in loader, skipping all but first hole of polygons." +msgstr "" + +#. Tag: para +#: release_notes.xml:2247 +#, no-c-format +msgid "jdbc2: code cleanups, Makefile improvements" +msgstr "" + +#. Tag: para +#: release_notes.xml:2249 +#, no-c-format +msgid "FLEX and YACC variables set *after* pgsql Makefile.global is included and only if the pgsql *stripped* version evaluates to the empty string" +msgstr "" + +#. Tag: para +#: release_notes.xml:2253 +#, no-c-format +msgid "Added already generated parser in release" +msgstr "" + +#. Tag: para +#: release_notes.xml:2255 +#, no-c-format +msgid "Build scripts refinements" +msgstr "" + +#. Tag: para +#: release_notes.xml:2257 +#, no-c-format +msgid "improved version handling, central Version.config" +msgstr "" + +#. Tag: para +#: release_notes.xml:2259 +#, no-c-format +msgid "improvements in postgis_restore.pl" +msgstr "" + +#. Tag: title +#: release_notes.xml:2264 +#, no-c-format +msgid "Release 1.0.0RC3" +msgstr "" + +#. Tag: para +#: release_notes.xml:2266 +#, no-c-format +msgid "Release date: 2005/02/24" +msgstr "" + +#. Tag: para +#: release_notes.xml:2268 +#, no-c-format +msgid "Third release candidate for 1.0.0. Contains many bug fixes and improvements." +msgstr "" + +#. Tag: para +#: release_notes.xml:2282 +#, no-c-format +msgid "BUGFIX in transform(): missing SRID, better error handling." +msgstr "" + +#. Tag: para +#: release_notes.xml:2285 +#, no-c-format +msgid "BUGFIX in memory alignment handling" +msgstr "" + +#. Tag: para +#: release_notes.xml:2287 +#, no-c-format +msgid "BUGFIX in force_collection() causing mapserver connector failures on simple (single) geometry types." +msgstr "" + +#. Tag: para +#: release_notes.xml:2290 +#, no-c-format +msgid "BUGFIX in GeometryFromText() missing to add a bbox cache." +msgstr "" + +#. Tag: para +#: release_notes.xml:2292 +#, no-c-format +msgid "reduced precision of box2d output." +msgstr "" + +#. Tag: para +#: release_notes.xml:2294 +#, no-c-format +msgid "prefixed DEBUG macros with PGIS_ to avoid clash with pgsql one" +msgstr "" + +#. Tag: para +#: release_notes.xml:2297 +#, no-c-format +msgid "plugged a leak in GEOS2POSTGIS converter" +msgstr "" + +#. Tag: para +#: release_notes.xml:2299 +#, no-c-format +msgid "Reduced memory usage by early releasing query-context palloced one." +msgstr "" + +#. Tag: para +#: release_notes.xml:2306 +#, no-c-format +msgid "BUGFIX in 72 index bindings." +msgstr "" + +#. Tag: para +#: release_notes.xml:2308 +#, no-c-format +msgid "BUGFIX in probe_geometry_columns() to work with PG72 and support multiple geometry columns in a single table" +msgstr "" + +#. Tag: para +#: release_notes.xml:2311 +#, no-c-format +msgid "NEW bool::text cast" +msgstr "" + +#. Tag: para +#: release_notes.xml:2313 +#, no-c-format +msgid "Some functions made IMMUTABLE from STABLE, for performance improvement." +msgstr "" + +#. Tag: para +#: release_notes.xml:2320 +#, no-c-format +msgid "jdbc2: small patches, box2d/3d tests, revised docs and license." +msgstr "" + +#. Tag: para +#: release_notes.xml:2323 +#, no-c-format +msgid "jdbc2: bug fix and testcase in for pgjdbc 8.0 type autoregistration" +msgstr "" + +#. Tag: para +#: release_notes.xml:2326 +#, no-c-format +msgid "jdbc2: Removed use of jdk1.4 only features to enable build with older jdk releases." +msgstr "" + +#. Tag: para +#: release_notes.xml:2329 +#, no-c-format +msgid "jdbc2: Added support for building against pg72jdbc2.jar" +msgstr "" + +#. Tag: para +#: release_notes.xml:2331 +#, no-c-format +msgid "jdbc2: updated and cleaned makefile" +msgstr "" + +#. Tag: para +#: release_notes.xml:2333 +#, no-c-format +msgid "jdbc2: added BETA support for jts geometry classes" +msgstr "" + +#. Tag: para +#: release_notes.xml:2335 +#, no-c-format +msgid "jdbc2: Skip known-to-fail tests against older PostGIS servers." +msgstr "" + +#. Tag: para +#: release_notes.xml:2338 +#, no-c-format +msgid "jdbc2: Fixed handling of measured geometries in EWKT." +msgstr "" + +#. Tag: para +#: release_notes.xml:2344 +#, no-c-format +msgid "new performance tips chapter in manual" +msgstr "" + +#. Tag: para +#: release_notes.xml:2346 +#, no-c-format +msgid "documentation updates: pgsql72 requirement, lwpostgis.sql" +msgstr "" + +#. Tag: para +#: release_notes.xml:2348 +#, no-c-format +msgid "few changes in autoconf" +msgstr "" + +#. Tag: para +#: release_notes.xml:2350 +#, no-c-format +msgid "BUILDDATE extraction made more portable" +msgstr "" + +#. Tag: para +#: release_notes.xml:2352 +#, no-c-format +msgid "fixed spatial_ref_sys.sql to avoid vacuuming the whole database." +msgstr "" + +#. Tag: para +#: release_notes.xml:2355 +#, no-c-format +msgid "spatial_ref_sys: changed Paris entries to match the ones distributed with 0.x." +msgstr "" + +#. Tag: title +#: release_notes.xml:2361 +#, no-c-format +msgid "Release 1.0.0RC2" +msgstr "" + +#. Tag: para +#: release_notes.xml:2363 +#, no-c-format +msgid "Release date: 2005/01/26" +msgstr "" + +#. Tag: para +#: release_notes.xml:2365 +#, no-c-format +msgid "Second release candidate for 1.0.0 containing bug fixes and a few improvements." +msgstr "" + +#. Tag: para +#: release_notes.xml:2379 +#, no-c-format +msgid "BUGFIX in pointarray box3d computation" +msgstr "" + +#. Tag: para +#: release_notes.xml:2381 +#, no-c-format +msgid "BUGFIX in distance_spheroid definition" +msgstr "" + +#. Tag: para +#: release_notes.xml:2383 +#, no-c-format +msgid "BUGFIX in transform() missing to update bbox cache" +msgstr "" + +#. Tag: para +#: release_notes.xml:2385 +#, no-c-format +msgid "NEW jdbc driver (jdbc2)" +msgstr "" + +#. Tag: para +#: release_notes.xml:2387 +#, no-c-format +msgid "GEOMETRYCOLLECTION(EMPTY) syntax support for backward compatibility" +msgstr "" + +#. Tag: para +#: release_notes.xml:2390 +#, no-c-format +msgid "Faster binary outputs" +msgstr "" + +#. Tag: para +#: release_notes.xml:2392 +#, no-c-format +msgid "Stricter OGC WKB/WKT constructors" +msgstr "" + +#. Tag: para +#: release_notes.xml:2398 +#, no-c-format +msgid "More correct STABLE, IMMUTABLE, STRICT uses in lwpostgis.sql" +msgstr "" + +#. Tag: para +#: release_notes.xml:2401 +#, no-c-format +msgid "stricter OGC WKB/WKT constructors" +msgstr "" + +#. Tag: para +#: release_notes.xml:2407 +#, no-c-format +msgid "Faster and more robust loader (both i18n and not)" +msgstr "" + +#. Tag: para +#: release_notes.xml:2409 +#, no-c-format +msgid "Initial autoconf script" +msgstr "" + +#. Tag: title +#: release_notes.xml:2414 +#, no-c-format +msgid "Release 1.0.0RC1" +msgstr "" + +#. Tag: para +#: release_notes.xml:2416 +#, no-c-format +msgid "Release date: 2005/01/13" +msgstr "" + +#. Tag: para +#: release_notes.xml:2418 +#, no-c-format +msgid "This is the first candidate of a major postgis release, with internal storage of postgis types redesigned to be smaller and faster on indexed queries." +msgstr "" + +#. Tag: para +#: release_notes.xml:2433 +#, no-c-format +msgid "Faster canonical input parsing." +msgstr "" + +#. Tag: para +#: release_notes.xml:2435 +#, no-c-format +msgid "Lossless canonical output." +msgstr "" + +#. Tag: para +#: release_notes.xml:2437 +#, no-c-format +msgid "EWKB Canonical binary IO with PG>73." +msgstr "" + +#. Tag: para +#: release_notes.xml:2439 +#, no-c-format +msgid "Support for up to 4d coordinates, providing lossless shapefile->postgis->shapefile conversion." +msgstr "" + +#. Tag: para +#: release_notes.xml:2442 +#, no-c-format +msgid "New function: UpdateGeometrySRID(), AsGML(), SnapToGrid(), ForceRHR(), estimated_extent(), accum()." +msgstr "" + +#. Tag: para +#: release_notes.xml:2445 +#, no-c-format +msgid "Vertical positioning indexed operators." +msgstr "" + +#. Tag: para +#: release_notes.xml:2447 +#, no-c-format +msgid "JOIN selectivity function." +msgstr "" + +#. Tag: para +#: release_notes.xml:2449 +#, no-c-format +msgid "More geometry constructors / editors." +msgstr "" + +#. Tag: para +#: release_notes.xml:2451 +#, no-c-format +msgid "PostGIS extension API." +msgstr "" + +#. Tag: para +#: release_notes.xml:2453 +#, no-c-format +msgid "UTF8 support in loader." +msgstr "" + diff --git a/doc/po/de_DE/reporting.xml.po b/doc/po/de_DE/reporting.xml.po new file mode 100644 index 000000000..afa5c0ed7 --- /dev/null +++ b/doc/po/de_DE/reporting.xml.po @@ -0,0 +1,136 @@ +# SOME DESCRIPTIVE TITLE. +# FIRST AUTHOR , 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 \n" +"Language-Team: 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 SELECT postgis_full_version() [for postgis] and SELECT version() [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 release changelog first, to find out if your bug has already been fixed." +msgstr "" + +#. Tag: para +#: reporting.xml:21 +#, no-c-format +msgid "Using the PostGIS bug tracker 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 How to Report Bugs Effectively 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 PostGIS bug tracker." +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 Subversion 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 > doc.patch" +msgstr "" + +#. Tag: para +#: reporting.xml:83 +#, no-c-format +msgid "Attach the patch to a new issue in bug tracker." +msgstr "" + diff --git a/doc/po/de_DE/using_postgis_app.xml.po b/doc/po/de_DE/using_postgis_app.xml.po new file mode 100644 index 000000000..9609dceed --- /dev/null +++ b/doc/po/de_DE/using_postgis_app.xml.po @@ -0,0 +1,659 @@ +# SOME DESCRIPTIVE TITLE. +# FIRST AUTHOR , 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 \n" +"Language-Team: 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 http://mapserver.org." +msgstr "" + +#. Tag: para +#: using_postgis_app.xml:17 +#, no-c-format +msgid "The OpenGIS Web Map Specification is at http://www.opengeospatial.org/standards/wms." +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 libpq 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 >= 4\" \n" + " CLASS \n" + " # Make the superhighways brighter and 2 pixels wide\n" + " EXPRESSION ([numlanes] >= 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] < 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 <>):" +msgstr "" + +#. Tag: para +#: using_postgis_app.xml:80 +#, no-c-format +msgid "user=<username> password=<password> dbname=<username> hostname=<server> port=<5432>" +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 \"<geocolumn> from <tablename> using srid=<srid> using unique <primary key>\" 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 MapServer PostGIS Performance Tips 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 >= 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 EXPRESSION 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 lower case." +msgstr "" + +#. Tag: programlisting +#: using_postgis_app.xml:162 +#, no-c-format +msgid "EXPRESSION ([numlanes] >= 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 >= 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 USING UNIQUE clause in your DATA 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 DATA 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 USING 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 DATA definition) it is more difficult for mapserver to automatically determine a unique identifier for each row and also the SRID for the table. The USING 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 <uniqueid>" +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 USING UNIQUE. 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 DATA definition." +msgstr "" + +#. Tag: term +#: using_postgis_app.xml:282 +#, no-c-format +msgid "USING SRID=<srid>" +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 USING SRID= option allows the correct SRID to be specified in the DATA 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 FILTER 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 DATA 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 DATA 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 < pl.numRings(); r++) { \n" + " LinearRing rng = pl.getRing(r); \n" + " System.out.println(\"Ring: \" + r); \n" + " for( int p = 0; p < 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 "..." +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 "" + diff --git a/doc/po/de_DE/using_postgis_dataman.xml.po b/doc/po/de_DE/using_postgis_dataman.xml.po new file mode 100644 index 000000000..b29328600 --- /dev/null +++ b/doc/po/de_DE/using_postgis_dataman.xml.po @@ -0,0 +1,3110 @@ +# SOME DESCRIPTIVE TITLE. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2014-10-18 10:29+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: using_postgis_dataman.xml:3 +#, no-c-format +msgid "Using PostGIS: Data Management and Queries" +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:6 +#, no-c-format +msgid "GIS Objects" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:8 +#, no-c-format +msgid "The GIS objects supported by PostGIS are a superset of the \"Simple Features\" defined by the OpenGIS Consortium (OGC). As of version 0.9, PostGIS supports all the objects and functions specified in the OGC \"Simple Features for SQL\" specification." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:13 +#, no-c-format +msgid "PostGIS extends the standard with support for 3DZ,3DM and 4D coordinates." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:17 +#, no-c-format +msgid "OpenGIS WKB and WKT" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:19 +#, no-c-format +msgid "The OpenGIS specification defines two standard ways of expressing spatial objects: the Well-Known Text (WKT) form and the Well-Known Binary (WKB) form. Both WKT and WKB include information about the type of the object and the coordinates which form the object." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:24 +#, no-c-format +msgid "Examples of the text representations (WKT) of the spatial objects of the features are as follows:" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:29 +#, no-c-format +msgid "POINT(0 0)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:33 +#, no-c-format +msgid "LINESTRING(0 0,1 1,1 2)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:37 +#, no-c-format +msgid "POLYGON((0 0,4 0,4 4,0 4,0 0),(1 1, 2 1, 2 2, 1 2,1 1))" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:41 +#, no-c-format +msgid "MULTIPOINT((0 0),(1 2))" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:45 +#, no-c-format +msgid "MULTILINESTRING((0 0,1 1,1 2),(2 3,3 2,5 4))" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:49 +#, no-c-format +msgid "MULTIPOLYGON(((0 0,4 0,4 4,0 4,0 0),(1 1,2 1,2 2,1 2,1 1)), ((-1 -1,-1 -2,-2 -2,-2 -1,-1 -1)))" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:54 +#, no-c-format +msgid "GEOMETRYCOLLECTION(POINT(2 3),LINESTRING(2 3,3 4))" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:58 +#, no-c-format +msgid "The OpenGIS specification also requires that the internal storage format of spatial objects include a spatial referencing system identifier (SRID). The SRID is required when creating spatial objects for insertion into the database." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:63 using_postgis_dataman.xml:151 +#, no-c-format +msgid "Input/Output of these formats are available using the following interfaces:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:66 +#, no-c-format +msgid "" + "bytea WKB = ST_AsBinary(geometry);\n" + "text WKT = ST_AsText(geometry);\n" + "geometry = ST_GeomFromWKB(bytea WKB, SRID);\n" + "geometry = ST_GeometryFromText(text WKT, SRID);" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:68 +#, no-c-format +msgid "For example, a valid insert statement to create and insert an OGC spatial object would be:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:71 +#, no-c-format +msgid "" + "INSERT INTO geotable ( the_geom, the_name )\n" + " VALUES ( ST_GeomFromText('POINT(-126.4 45.32)', 312), 'A Place');" +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:75 +#, no-c-format +msgid "PostGIS EWKB, EWKT and Canonical Forms" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:77 +#, no-c-format +msgid "OGC formats only support 2d geometries, and the associated SRID is *never* embedded in the input/output representations." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:80 +#, no-c-format +msgid "PostGIS extended formats are currently superset of OGC one (every valid WKB/WKT is a valid EWKB/EWKT) but this might vary in the future, specifically if OGC comes out with a new format conflicting with our extensions. Thus you SHOULD NOT rely on this feature!" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:85 +#, no-c-format +msgid "PostGIS EWKB/EWKT add 3dm,3dz,4d coordinates support and embedded SRID information." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:88 +#, no-c-format +msgid "Examples of the text representations (EWKT) of the extended spatial objects of the features are as follows. The * ones are new in this version of PostGIS:" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:93 +#, no-c-format +msgid "POINT(0 0 0) -- XYZ" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:97 +#, no-c-format +msgid "SRID=32632;POINT(0 0) -- XY with SRID" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:101 +#, no-c-format +msgid "POINTM(0 0 0) -- XYM" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:105 +#, no-c-format +msgid "POINT(0 0 0 0) -- XYZM" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:109 +#, no-c-format +msgid "SRID=4326;MULTIPOINTM(0 0 0,1 2 1) -- XYM with SRID" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:113 +#, no-c-format +msgid "MULTILINESTRING((0 0 0,1 1 0,1 2 1),(2 3 1,3 2 1,5 4 1))" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:118 +#, no-c-format +msgid "POLYGON((0 0 0,4 0 0,4 4 0,0 4 0,0 0 0),(1 1 0,2 1 0,2 2 0,1 2 0,1 1 0))" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:123 +#, no-c-format +msgid "MULTIPOLYGON(((0 0 0,4 0 0,4 4 0,0 4 0,0 0 0),(1 1 0,2 1 0,2 2 0,1 2 0,1 1 0)),((-1 -1 0,-1 -2 0,-2 -2 0,-2 -1 0,-1 -1 0)))" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:128 +#, no-c-format +msgid "GEOMETRYCOLLECTIONM( POINTM(2 3 9), LINESTRINGM(2 3 4, 3 4 5) )" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:132 +#, no-c-format +msgid "MULTICURVE( (0 0, 5 5), CIRCULARSTRING(4 0, 4 4, 8 4) )" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:136 +#, no-c-format +msgid "POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)), ((0 0 0, 0 1 0, 1 1 0, 1 0 0, 0 0 0)), ((0 0 0, 1 0 0, 1 0 1, 0 0 1, 0 0 0)), ((1 1 0, 1 1 1, 1 0 1, 1 0 0, 1 1 0)), ((0 1 0, 0 1 1, 1 1 1, 1 1 0, 0 1 0)), ((0 0 1, 1 0 1, 1 1 1, 0 1 1, 0 0 1)) )" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:142 +#, no-c-format +msgid "TRIANGLE ((0 0, 0 9, 9 0, 0 0))" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:146 +#, no-c-format +msgid "TIN( ((0 0 0, 0 0 1, 0 1 0, 0 0 0)), ((0 0 0, 0 1 0, 1 1 0, 0 0 0)) )" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:154 +#, no-c-format +msgid "" + "bytea EWKB = ST_AsEWKB(geometry);\n" + "text EWKT = ST_AsEWKT(geometry);\n" + "geometry = ST_GeomFromEWKB(bytea EWKB);\n" + "geometry = ST_GeomFromEWKT(text EWKT);" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:156 +#, no-c-format +msgid "For example, a valid insert statement to create and insert a PostGIS spatial object would be:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:159 +#, no-c-format +msgid "" + "INSERT INTO geotable ( the_geom, the_name )\n" + " VALUES ( ST_GeomFromEWKT('SRID=312;POINTM(-126.4 45.32 15)'), 'A Place' )" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:161 +#, no-c-format +msgid "The \"canonical forms\" of a PostgreSQL type are the representations you get with a simple query (without any function call) and the one which is guaranteed to be accepted with a simple insert, update or copy. For the postgis 'geometry' type these are:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:164 +#, no-c-format +msgid "" + "- Output\n" + " - binary: EWKB\n" + " ascii: HEXEWKB (EWKB in hex form)\n" + "- Input\n" + " - binary: EWKB\n" + " ascii: HEXEWKB|EWKT" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:166 +#, no-c-format +msgid "For example this statement reads EWKT and returns HEXEWKB in the process of canonical ascii input/output:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:169 +#, no-c-format +msgid "" + "=# SELECT 'SRID=4;POINT(0 0)'::geometry;\n" + "\n" + "geometry\n" + "----------------------------------------------------\n" + "01010000200400000000000000000000000000000000000000\n" + "(1 row)" +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:172 +#, no-c-format +msgid "SQL-MM Part 3" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:174 +#, no-c-format +msgid "The SQL Multimedia Applications Spatial specification extends the simple features for SQL spec by defining a number of circularly interpolated curves." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:178 +#, no-c-format +msgid "The SQL-MM definitions include 3dm, 3dz and 4d coordinates, but do not allow the embedding of SRID information." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:181 +#, no-c-format +msgid "The well-known text extensions are not yet fully supported. Examples of some simple curved geometries are shown below:" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:186 +#, no-c-format +msgid "CIRCULARSTRING(0 0, 1 1, 1 0)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:187 +#, no-c-format +msgid "CIRCULARSTRING(0 0, 4 0, 4 4, 0 4, 0 0)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:188 +#, no-c-format +msgid "The CIRCULARSTRING is the basic curve type, similar to a LINESTRING in the linear world. A single segment required three points, the start and end points (first and third) and any other point on the arc. The exception to this is for a closed circle, where the start and end points are the same. In this case the second point MUST be the center of the arc, ie the opposite side of the circle. To chain arcs together, the last point of the previous arc becomes the first point of the next arc, just like in LINESTRING. This means that a valid circular string must have an odd number of points greated than 1." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:201 +#, no-c-format +msgid "COMPOUNDCURVE(CIRCULARSTRING(0 0, 1 1, 1 0),(1 0, 0 1))" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:202 +#, no-c-format +msgid "A compound curve is a single, continuous curve that has both curved (circular) segments and linear segments. That means that in addition to having well-formed components, the end point of every component (except the last) must be coincident with the start point of the following component." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:210 +#, no-c-format +msgid "CURVEPOLYGON(CIRCULARSTRING(0 0, 4 0, 4 4, 0 4, 0 0),(1 1, 3 3, 3 1, 1 1))" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:212 +#, no-c-format +msgid "Example compound curve in a curve polygon: CURVEPOLYGON(COMPOUNDCURVE(CIRCULARSTRING(0 0,2 0, 2 1, 2 3, 4 3),(4 3, 4 5, 1 4, 0 0)), CIRCULARSTRING(1.7 1, 1.4 0.4, 1.6 0.4, 1.6 0.5, 1.7 1) )" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:216 +#, no-c-format +msgid "A CURVEPOLYGON is just like a polygon, with an outer ring and zero or more inner rings. The difference is that a ring can take the form of a circular string, linear string or compound string." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:220 +#, no-c-format +msgid "As of PostGIS 1.4 PostGIS supports compound curves in a curve polygon." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:224 +#, no-c-format +msgid "MULTICURVE((0 0, 5 5),CIRCULARSTRING(4 0, 4 4, 8 4))" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:225 +#, no-c-format +msgid "The MULTICURVE is a collection of curves, which can include linear strings, circular strings or compound strings." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:230 +#, no-c-format +msgid "MULTISURFACE(CURVEPOLYGON(CIRCULARSTRING(0 0, 4 0, 4 4, 0 4, 0 0),(1 1, 3 3, 3 1, 1 1)),((10 10, 14 12, 11 10, 10 10),(11 11, 11.5 11, 11 11.5, 11 11)))" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:233 +#, no-c-format +msgid "This is a collection of surfaces, which can be (linear) polygons or curve polygons." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:239 +#, no-c-format +msgid "PostGIS prior to 1.4 does not support compound curves in a curve polygon, but PostGIS 1.4 and above do support the use of Compound Curves in a Curve Polygon." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:245 +#, no-c-format +msgid "All floating point comparisons within the SQL-MM implementation are performed to a specified tolerance, currently 1E-8." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:251 +#, no-c-format +msgid "PostGIS Geography Type" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:253 +#, no-c-format +msgid "The geography type provides native support for spatial features represented on \"geographic\" coordinates (sometimes called \"geodetic\" coordinates, or \"lat/lon\", or \"lon/lat\"). Geographic coordinates are spherical coordinates expressed in angular units (degrees)." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:255 +#, no-c-format +msgid "The basis for the PostGIS geometry type is a plane. The shortest path between two points on the plane is a straight line. That means calculations on geometries (areas, distances, lengths, intersections, etc) can be calculated using cartesian mathematics and straight line vectors." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:257 +#, no-c-format +msgid "The basis for the PostGIS geographic type is a sphere. The shortest path between two points on the sphere is a great circle arc. That means that calculations on geographies (areas, distances, lengths, intersections, etc) must be calculated on the sphere, using more complicated mathematics. For more accurate measurements, the calculations must take the actual spheroidal shape of the world into account, and the mathematics becomes very complicated indeed." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:259 +#, no-c-format +msgid "Because the underlying mathematics is much more complicated, there are fewer functions defined for the geography type than for the geometry type. Over time, as new algorithms are added, the capabilities of the geography type will expand." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:262 +#, no-c-format +msgid "One restriction is that it only supports WGS 84 long lat (SRID:4326). It uses a new data type called geography. None of the GEOS functions support this new type. As a workaround one can convert back and forth between geometry and geography types." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:266 +#, no-c-format +msgid "The new geography type uses the PostgreSQL 8.3+ typmod definition format so that a table with a geography field can be added in a single step. All the standard OGC formats except for curves are supported." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:270 +#, no-c-format +msgid "Geography Basics" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:271 +#, no-c-format +msgid "The geography type only supports the simplest of simple features. Standard geometry type data will autocast to geography if it is of SRID 4326. You can also use the EWKT and EWKB conventions to insert data." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:276 +#, no-c-format +msgid "POINT: Creating a table with 2d point geometry:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:277 +#, no-c-format +msgid "CREATE TABLE testgeog(gid serial PRIMARY KEY, the_geog geography(POINT,4326) );" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:278 +#, no-c-format +msgid "Creating a table with z coordinate point" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:279 +#, no-c-format +msgid "CREATE TABLE testgeog(gid serial PRIMARY KEY, the_geog geography(POINTZ,4326) );" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:282 +#, no-c-format +msgid "LINESTRING" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:285 +#, no-c-format +msgid "POLYGON" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:288 +#, no-c-format +msgid "MULTIPOINT" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:291 +#, no-c-format +msgid "MULTILINESTRING" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:294 +#, no-c-format +msgid "MULTIPOLYGON" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:297 +#, no-c-format +msgid "GEOMETRYCOLLECTION" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:301 +#, no-c-format +msgid "The new geography fields don't get registered in the geometry_columns. They get registered in a new view called geography_columns which is a view against the system catalogs so is always automatically kept up to date without need for an AddGeom... like function." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:305 +#, no-c-format +msgid "Now, check the \"geography_columns\" view and see that your table is listed." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:307 +#, no-c-format +msgid "You can create a new table with a GEOGRAPHY column using the CREATE TABLE syntax. Unlike GEOMETRY, there is no need to run a separate AddGeometryColumns() process to register the column in metadata." +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:311 +#, no-c-format +msgid "" + "CREATE TABLE global_points ( \n" + " id SERIAL PRIMARY KEY,\n" + " name VARCHAR(64),\n" + " location GEOGRAPHY(POINT,4326)\n" + " );" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:314 +#, no-c-format +msgid "Note that the location column has type GEOGRAPHY and that geography type supports two optional modifier: a type modifier that restricts the kind of shapes and dimensions allowed in the column; an SRID modifier that restricts the coordinate reference identifier to a particular number." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:315 +#, no-c-format +msgid "Allowable values for the type modifier are: POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON. The modifier also supports dimensionality restrictions through suffixes: Z, M and ZM. So, for example a modifier of 'LINESTRINGM' would only allow line strings with three dimensions in, and would treat the third dimension as a measure. Similarly, 'POINTZM' would expect four dimensional data." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:317 +#, no-c-format +msgid "The SRID modifier is currently of limited use: only 4326 (WGS84) is allowed as a value. If you do not specify an SRID, the a value 0 (undefined spheroid) will be used, and all calculations will proceed using WGS84 anyways." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:318 +#, no-c-format +msgid "In the future, alternate SRIDs will allow calculations on spheroids other than WGS84." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:319 +#, no-c-format +msgid "Once you have created your table, you can see it in the GEOGRAPHY_COLUMNS table:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:320 +#, no-c-format +msgid "" + "-- See the contents of the metadata view\n" + "SELECT * FROM geography_columns;" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:322 +#, no-c-format +msgid "You can insert data into the table the same as you would if it was using a GEOMETRY column:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:324 +#, no-c-format +msgid "" + "-- Add some data into the test table\n" + "INSERT INTO global_points (name, location) VALUES ('Town', ST_GeographyFromText('SRID=4326;POINT(-110 30)') );\n" + "INSERT INTO global_points (name, location) VALUES ('Forest', ST_GeographyFromText('SRID=4326;POINT(-109 29)') );\n" + "INSERT INTO global_points (name, location) VALUES ('London', ST_GeographyFromText('SRID=4326;POINT(0 49)') );" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:326 +#, no-c-format +msgid "Creating an index works the same as GEOMETRY. PostGIS will note that the column type is GEOGRAPHY and create an appropriate sphere-based index instead of the usual planar index used for GEOMETRY." +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:329 +#, no-c-format +msgid "" + "-- Index the test table with a spherical index\n" + " CREATE INDEX global_points_gix ON global_points USING GIST ( location );" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:332 +#, no-c-format +msgid "Query and measurement functions use units of meters. So distance parameters should be expressed in meters, and return values should be expected in meters (or square meters for areas)." +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:334 +#, no-c-format +msgid "" + "-- Show a distance query and note, London is outside the 1000km tolerance\n" + " SELECT name FROM global_points WHERE ST_DWithin(location, ST_GeographyFromText('SRID=4326;POINT(-110 29)'), 1000000);" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:337 +#, no-c-format +msgid "You can see the power of GEOGRAPHY in action by calculating the how close a plane flying from Seattle to London (LINESTRING(-122.33 47.606, 0.0 51.5)) comes to Reykjavik (POINT(-21.96 64.15))." +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:339 +#, no-c-format +msgid "" + "-- Distance calculation using GEOGRAPHY (122.2km)\n" + " SELECT ST_Distance('LINESTRING(-122.33 47.606, 0.0 51.5)'::geography, 'POINT(-21.96 64.15)':: geography);" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:342 +#, no-c-format +msgid "" + "-- Distance calculation using GEOMETRY (13.3 \"degrees\")\n" + " SELECT ST_Distance('LINESTRING(-122.33 47.606, 0.0 51.5)'::geometry, 'POINT(-21.96 64.15)':: geometry);" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:345 +#, no-c-format +msgid "The GEOGRAPHY type calculates the true shortest distance over the sphere between Reykjavik and the great circle flight path between Seattle and London." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:347 +#, no-c-format +msgid "Great Circle mapper The GEOMETRY type calculates a meaningless cartesian distance between Reykjavik and the straight line path from Seattle to London plotted on a flat map of the world. The nominal units of the result might be called \"degrees\", but the result doesn't correspond to any true angular difference between the points, so even calling them \"degrees\" is inaccurate." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:351 +#, no-c-format +msgid "When to use Geography Data type over Geometry data type" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:352 +#, no-c-format +msgid "The new GEOGRAPHY type allows you to store data in longitude/latitude coordinates, but at a cost: there are fewer functions defined on GEOGRAPHY than there are on GEOMETRY; those functions that are defined take more CPU time to execute." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:353 +#, no-c-format +msgid "The type you choose should be conditioned on the expected working area of the application you are building. Will your data span the globe or a large continental area, or is it local to a state, county or municipality?" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:355 +#, no-c-format +msgid "If your data is contained in a small area, you might find that choosing an appropriate projection and using GEOMETRY is the best solution, in terms of performance and functionality available." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:356 +#, no-c-format +msgid "If your data is global or covers a continental region, you may find that GEOGRAPHY allows you to build a system without having to worry about projection details. You store your data in longitude/latitude, and use the functions that have been defined on GEOGRAPHY." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:358 +#, no-c-format +msgid "If you don't understand projections, and you don't want to learn about them, and you're prepared to accept the limitations in functionality available in GEOGRAPHY, then it might be easier for you to use GEOGRAPHY than GEOMETRY. Simply load your data up as longitude/latitude and go from there." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:361 +#, no-c-format +msgid "Refer to for compare between what is supported for Geography vs. Geometry. For a brief listing and description of Geography functions, refer to " +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:367 +#, no-c-format +msgid "Geography Advanced FAQ" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:371 +#, no-c-format +msgid "Do you calculate on the sphere or the spheroid?" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:375 +#, no-c-format +msgid "By default, all distance and area calculations are done on the spheroid. You should find that the results of calculations in local areas match up will with local planar results in good local projections. Over larger areas, the spheroidal calculations will be more accurate than any calculation done on a projected plane." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:378 +#, no-c-format +msgid "All the geography functions have the option of using a sphere calculation, by setting a final boolean parameter to 'FALSE'. This will somewhat speed up calculations, particularly for cases where the geometries are very simple." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:384 +#, no-c-format +msgid "What about the date-line and the poles?" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:388 +#, no-c-format +msgid "All the calculations have no conception of date-line or poles, the coordinates are spherical (longitude/latitude) so a shape that crosses the dateline is, from a calculation point of view, no different from any other shape." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:396 +#, no-c-format +msgid "What is the longest arc you can process?" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:400 +#, no-c-format +msgid "We use great circle arcs as the \"interpolation line\" between two points. That means any two points are actually joined up two ways, depending on which direction you travel along the great circle. All our code assumes that the points are joined by the *shorter* of the two paths along the great circle. As a consequence, shapes that have arcs of more than 180 degrees will not be correctly modelled." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:407 +#, no-c-format +msgid "Why is it so slow to calculate the area of Europe / Russia / insert big geographic region here ?" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:411 +#, no-c-format +msgid "Because the polygon is so darned huge! Big areas are bad for two reasons: their bounds are huge, so the index tends to pull the feature no matter what query you run; the number of vertices is huge, and tests (distance, containment) have to traverse the vertex list at least once and sometimes N times (with N being the number of vertices in the other candidate feature)." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:416 +#, no-c-format +msgid "As with GEOMETRY, we recommend that when you have very large polygons, but are doing queries in small areas, you \"denormalize\" your geometric data into smaller chunks so that the index can effectively subquery parts of the object and so queries don't have to pull out the whole object every time. Just because you *can* store all of Europe in one polygon doesn't mean you *should*." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:425 +#, no-c-format +msgid "Using OpenGIS Standards" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:427 +#, no-c-format +msgid "The OpenGIS \"Simple Features Specification for SQL\" defines standard GIS object types, the functions required to manipulate them, and a set of meta-data tables. In order to ensure that meta-data remain consistent, operations such as creating and removing a spatial column are carried out through special procedures defined by OpenGIS." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:433 +#, no-c-format +msgid "There are two OpenGIS meta-data tables: SPATIAL_REF_SYS and GEOMETRY_COLUMNS. The SPATIAL_REF_SYS table holds the numeric IDs and textual descriptions of coordinate systems used in the spatial database." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:440 +#, no-c-format +msgid "The SPATIAL_REF_SYS Table and Spatial Reference Systems" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:442 +#, no-c-format +msgid "The spatial_ref_sys table is a PostGIS included and OGC compliant database table that lists over 3000 known spatial reference systems and details needed to transform/reproject between them." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:446 +#, no-c-format +msgid "Although the PostGIS spatial_ref_sys table contains over 3000 of the more commonly used spatial reference system definitions that can be handled by the proj library, it does not contain all known to man and you can even define your own custom projection if you are familiar with proj4 constructs. Keep in mind that most spatial reference systems are regional and have no meaning when used outside of the bounds they were intended for." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:449 +#, no-c-format +msgid "An excellent resource for finding spatial reference systems not defined in the core set is http://spatialreference.org/" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:451 +#, no-c-format +msgid "Some of the more commonly used spatial reference systems are: 4326 - WGS 84 Long Lat, 4269 - NAD 83 Long Lat, 3395 - WGS 84 World Mercator, 2163 - US National Atlas Equal Area, Spatial reference systems for each NAD 83, WGS 84 UTM zone - UTM zones are one of the most ideal for measurement, but only cover 6-degree regions." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:457 +#, no-c-format +msgid "Various US state plane spatial reference systems (meter or feet based) - usually one or 2 exists per US state. Most of the meter ones are in the core set, but many of the feet based ones or ESRI created ones you will need to pull from spatialreference.org." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:461 +#, no-c-format +msgid "For details on determining which UTM zone to use for your area of interest, check out the utmzone PostGIS plpgsql helper function." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:465 +#, no-c-format +msgid "The SPATIAL_REF_SYS table definition is as follows:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:468 +#, no-c-format +msgid "" + "CREATE TABLE spatial_ref_sys (\n" + " srid INTEGER NOT NULL PRIMARY KEY,\n" + " auth_name VARCHAR(256),\n" + " auth_srid INTEGER,\n" + " srtext VARCHAR(2048),\n" + " proj4text VARCHAR(2048)\n" + ")" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:470 +#, no-c-format +msgid "The SPATIAL_REF_SYS columns are as follows:" +msgstr "" + +#. Tag: ulink +#: using_postgis_dataman.xml:475 +#, no-c-format +msgid "SRID" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:478 +#, no-c-format +msgid "An integer value that uniquely identifies the Spatial Referencing System (SRS) within the database." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:484 +#, no-c-format +msgid "AUTH_NAME" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:487 +#, no-c-format +msgid "The name of the standard or standards body that is being cited for this reference system. For example, \"EPSG\" would be a valid AUTH_NAME." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:494 +#, no-c-format +msgid "AUTH_SRID" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:497 +#, no-c-format +msgid "The ID of the Spatial Reference System as defined by the Authority cited in the AUTH_NAME. In the case of EPSG, this is where the EPSG projection code would go." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:504 +#, no-c-format +msgid "SRTEXT" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:507 +#, no-c-format +msgid "The Well-Known Text representation of the Spatial Reference System. An example of a WKT SRS representation is:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:510 +#, no-c-format +msgid "" + "PROJCS[\"NAD83 / UTM Zone 10N\",\n" + " GEOGCS[\"NAD83\",\n" + " DATUM[\"North_American_Datum_1983\",\n" + " SPHEROID[\"GRS 1980\",6378137,298.257222101]\n" + " ],\n" + " PRIMEM[\"Greenwich\",0],\n" + " UNIT[\"degree\",0.0174532925199433]\n" + " ],\n" + " PROJECTION[\"Transverse_Mercator\"],\n" + " PARAMETER[\"latitude_of_origin\",0],\n" + " PARAMETER[\"central_meridian\",-123],\n" + " PARAMETER[\"scale_factor\",0.9996],\n" + " PARAMETER[\"false_easting\",500000],\n" + " PARAMETER[\"false_northing\",0],\n" + " UNIT[\"metre\",1]\n" + "]" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:512 +#, no-c-format +msgid "For a listing of EPSG projection codes and their corresponding WKT representations, see http://www.opengeospatial.org/. For a discussion of WKT in general, see the OpenGIS \"Coordinate Transformation Services Implementation Specification\" at http://www.opengeospatial.org/standards. For information on the European Petroleum Survey Group (EPSG) and their database of spatial reference systems, see http://www.epsg.org." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:525 +#, no-c-format +msgid "PROJ4TEXT" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:528 +#, no-c-format +msgid "PostGIS uses the Proj4 library to provide coordinate transformation capabilities. The PROJ4TEXT column contains the Proj4 coordinate definition string for a particular SRID. For example:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:533 +#, no-c-format +msgid "+proj=utm +zone=10 +ellps=clrk66 +datum=NAD27 +units=m" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:535 +#, no-c-format +msgid "For more information about, see the Proj4 web site at http://trac.osgeo.org/proj/. The spatial_ref_sys.sql file contains both SRTEXT and PROJ4TEXT definitions for all EPSG projections." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:546 +#, no-c-format +msgid "The GEOMETRY_COLUMNS VIEW" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:548 +#, no-c-format +msgid "In versions of PostGIS prior to 2.0.0, geometry_columns was a table that could be directly edited, and sometimes got out of synch with the actual definition of the geometry columns. In PostGIS 2.0.0, GEOMETRY_COLUMNS became a view with the same front-facing structure as prior versions, but reading from database system catalogs Its structure is as follows:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:552 +#, no-c-format +msgid "\\d geometry_columns" +msgstr "" + +#. Tag: screen +#: using_postgis_dataman.xml:553 +#, no-c-format +msgid "" + "View \"public.geometry_columns\"\n" + " Column | Type | Modifiers\n" + "-------------------+------------------------+-----------\n" + " f_table_catalog | character varying(256) |\n" + " f_table_schema | character varying(256) |\n" + " f_table_name | character varying(256) |\n" + " f_geometry_column | character varying(256) |\n" + " coord_dimension | integer |\n" + " srid | integer |\n" + " type | character varying(30) |" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:555 +#, no-c-format +msgid "The column meanings have not changed from prior versions and are:" +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:559 +#, no-c-format +msgid "F_TABLE_CATALOG, F_TABLE_SCHEMA, F_TABLE_NAME" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:562 +#, no-c-format +msgid "The fully qualified name of the feature table containing the geometry column. Note that the terms \"catalog\" and \"schema\" are Oracle-ish. There is not PostgreSQL analogue of \"catalog\" so that column is left blank -- for \"schema\" the PostgreSQL schema name is used (public is the default)." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:571 +#, no-c-format +msgid "F_GEOMETRY_COLUMN" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:574 +#, no-c-format +msgid "The name of the geometry column in the feature table." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:579 +#, no-c-format +msgid "COORD_DIMENSION" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:582 +#, no-c-format +msgid "The spatial dimension (2, 3 or 4 dimensional) of the column." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:588 +#, no-c-format +msgid "SRID" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:591 +#, no-c-format +msgid "The ID of the spatial reference system used for the coordinate geometry in this table. It is a foreign key reference to the SPATIAL_REF_SYS." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:598 +#, no-c-format +msgid "TYPE" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:601 +#, no-c-format +msgid "The type of the spatial object. To restrict the spatial column to a single type, use one of: POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, GEOMETRYCOLLECTION or corresponding XYM versions POINTM, LINESTRINGM, POLYGONM, MULTIPOINTM, MULTILINESTRINGM, MULTIPOLYGONM, GEOMETRYCOLLECTIONM. For heterogeneous (mixed-type) collections, you can use \"GEOMETRY\" as the type." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:610 +#, no-c-format +msgid "This attribute is (probably) not part of the OpenGIS specification, but is required for ensuring type homogeneity." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:620 +#, no-c-format +msgid "Creating a Spatial Table" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:622 +#, no-c-format +msgid "Creating a table with spatial data, can be done in one step. As shown in the following example which creates a roads table with a 2D linestring geometry column in WGS84 long lat" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:624 +#, no-c-format +msgid "" + "CREATE TABLE ROADS ( ID int4\n" + " , ROAD_NAME varchar(25), geom geometry(LINESTRING,4326) );" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:626 +#, no-c-format +msgid "We can add additional columns using standard ALTER TABLE command as we do in this next example where we add a 3-D linestring." +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:627 +#, no-c-format +msgid "ALTER TABLE roads ADD COLUMN geom2 geometry(LINESTRINGZ,4326);" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:629 +#, no-c-format +msgid "For backwards compability, you can still create a spatial table in two stages using the management functions." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:633 +#, no-c-format +msgid "Create a normal non-spatial table." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:635 +#, no-c-format +msgid "For example: CREATE TABLE ROADS ( ID int4, ROAD_NAME varchar(25) )" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:640 +#, no-c-format +msgid "Add a spatial column to the table using the OpenGIS \"AddGeometryColumn\" function. Refer to for more details." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:643 +#, no-c-format +msgid "" + "The syntax is: AddGeometryColumn(\n" + " <schema_name>,\n" + " <table_name>,\n" + " <column_name>,\n" + " <srid>,\n" + " <type>,\n" + " <dimension>\n" + ") Or, using current schema:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:643 +#, no-c-format +msgid "" + "AddGeometryColumn(\n" + " <table_name>,\n" + " <column_name>,\n" + " <srid>,\n" + " <type>,\n" + " <dimension>\n" + ")" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:645 +#, no-c-format +msgid "Example1: SELECT AddGeometryColumn('public', 'roads', 'geom', 423, 'LINESTRING', 2)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:648 +#, no-c-format +msgid "Example2: SELECT AddGeometryColumn( 'roads', 'geom', 423, 'LINESTRING', 2)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:653 +#, no-c-format +msgid "Here is an example of SQL used to create a table and add a spatial column (assuming that an SRID of 128 exists already):" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:656 +#, no-c-format +msgid "" + "CREATE TABLE parks (\n" + " park_id INTEGER,\n" + " park_name VARCHAR,\n" + " park_date DATE,\n" + " park_type VARCHAR\n" + ");\n" + "SELECT AddGeometryColumn('parks', 'park_geom', 128, 'MULTIPOLYGON', 2 );" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:658 +#, no-c-format +msgid "Here is another example, using the generic \"geometry\" type and the undefined SRID value of 0:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:661 +#, no-c-format +msgid "" + "CREATE TABLE roads (\n" + " road_id INTEGER,\n" + " road_name VARCHAR\n" + ");\n" + "SELECT AddGeometryColumn( 'roads', 'roads_geom', 0, 'GEOMETRY', 3 );" +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:665 +#, no-c-format +msgid "Manually Registering Geometry Columns in geometry_columns" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:666 +#, no-c-format +msgid "The AddGeometryColumn() approach creates a geometry column and also registers the new column in the geometry_columns table. If your software utilizes geometry_columns, then any geometry columns you need to query by must be registered in this view. Starting with PostGIS 2.0, geometry_columns is no longer editable and all geometry columns are autoregistered." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:670 +#, no-c-format +msgid "However they may be registered as a generic geometry column if the column was not defined as a specific type during creation." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:672 +#, no-c-format +msgid "Two of the cases where this may happen, but you can't use AddGeometryColumn, is in the case of SQL Views and bulk inserts. For these cases, you can correct the registration in the geometry_columns table by constraining the column. Note in PostGIS 2.0+ if your column is typmod based, the creation process would register it correctly, so no need to do anything." +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:677 +#, no-c-format +msgid "" + "--Lets say you have a view created like this\n" + "CREATE VIEW public.vwmytablemercator AS\n" + " SELECT gid, ST_Transform(geom,3395) As geom, f_name\n" + " FROM public.mytable;\n" + " \n" + "-- For it to register correctly in PostGIS 2.0+ \n" + "-- You need to cast the geometry\n" + "--\n" + "DROP VIEW public.vwmytablemercator;\n" + "CREATE VIEW public.vwmytablemercator AS\n" + " SELECT gid, ST_Transform(geom,3395)::geometry(Geometry, 3395) As geom, f_name\n" + " FROM public.mytable;\n" + " \n" + "-- If you know the geometry type for sure is a 2D POLYGON then you could do\n" + "DROP VIEW public.vwmytablemercator;\n" + "CREATE VIEW public.vwmytablemercator AS\n" + " SELECT gid, ST_Transform(geom,3395)::geometry(Polygon, 3395) As geom, f_name\n" + " FROM public.mytable;" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:678 +#, no-c-format +msgid "" + "--Lets say you created a derivative table by doing a bulk insert\n" + "SELECT poi.gid, poi.geom, citybounds.city_name\n" + "INTO myschema.my_special_pois\n" + "FROM poi INNER JOIN citybounds ON ST_Intersects(citybounds.geom, poi.geom);\n" + "\n" + "--Create 2d index on new table\n" + "CREATE INDEX idx_myschema_myspecialpois_geom_gist\n" + " ON myschema.my_special_pois USING gist(geom);\n" + " \n" + "-- If your points are 3D points or 3M points, \n" + "-- then you might want to create an nd index instead of a 2d index\n" + "-- like so\n" + "CREATE INDEX my_special_pois_geom_gist_nd \n" + " ON my_special_pois USING gist(geom gist_geometry_ops_nd);\n" + "\n" + "--To manually register this new table's geometry column in geometry_columns\n" + "-- Note that this approach will work for both PostGIS 2.0+ and PostGIS 1.4+\n" + "-- For PostGIS 2.0 it will also change the underlying structure of the table to\n" + "-- to make the column typmod based.\n" + "-- For PostGIS prior to 2.0, this technique can also be used to register views\n" + "SELECT populate_geometry_columns('myschema.my_special_pois'::regclass); \n" + "\n" + "--If you are using PostGIS 2.0 and for whatever reason, you\n" + "-- you need the old constraint based definition behavior \n" + "-- (such as case of inherited tables where all children do not have the same type and srid)\n" + "-- set new optional use_typmod argument to false\n" + "SELECT populate_geometry_columns('myschema.my_special_pois'::regclass, false);" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:680 +#, no-c-format +msgid "Although the old-constraint based method is still supported, a constraint-based geomentry column used directly in a view, will not register correctly in geometry_columns, as will a typmod one. In this example we define a column using typmod and another using constraints." +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:683 +#, no-c-format +msgid "" + "CREATE TABLE pois_ny(gid SERIAL PRIMARY KEY\n" + " , poi_name text, cat varchar(20)\n" + " , geom geometry(POINT,4326) );\n" + "SELECT AddGeometryColumn('pois_ny', 'geom_2160', 2160, 'POINT', 2, false);" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:684 +#, no-c-format +msgid "If we run in psql" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:685 +#, no-c-format +msgid "\\d pois_ny;" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:686 +#, no-c-format +msgid "We observe they are defined differently -- one is typmod, one is constraint" +msgstr "" + +#. Tag: screen +#: using_postgis_dataman.xml:687 +#, no-c-format +msgid "" + "Table \"public.pois_ny\"\n" + " Column | Type | Modifiers\n" + "\n" + "-----------+-----------------------+------------------------------------------------------\n" + " gid | integer | not null default nextval('pois_ny_gid_seq'::regclass)\n" + " poi_name | text |\n" + " cat | character varying(20) |\n" + " geom | geometry(Point,4326) |\n" + " geom_2160 | geometry |\n" + "Indexes:\n" + " \"pois_ny_pkey\" PRIMARY KEY, btree (gid)\n" + "Check constraints:\n" + " \"enforce_dims_geom_2160\" CHECK (st_ndims(geom_2160) = 2)\n" + " \"enforce_geotype_geom_2160\" CHECK (geometrytype(geom_2160) = 'POINT'::text \n" + " OR geom_2160 IS NULL)\n" + " \"enforce_srid_geom_2160\" CHECK (st_srid(geom_2160) = 2160)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:688 +#, no-c-format +msgid "In geometry_columns, they both register correctly" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:689 +#, no-c-format +msgid "" + "SELECT f_table_name, f_geometry_column, srid, type \n" + " FROM geometry_columns \n" + " WHERE f_table_name = 'pois_ny';" +msgstr "" + +#. Tag: screen +#: using_postgis_dataman.xml:690 +#, no-c-format +msgid "" + "f_table_name | f_geometry_column | srid | type\n" + "-------------+-------------------+------+-------\n" + "pois_ny | geom | 4326 | POINT\n" + "pois_ny | geom_2160 | 2160 | POINT" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:691 +#, no-c-format +msgid "However -- if we were to create a view like this" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:692 +#, no-c-format +msgid "" + "CREATE VIEW vw_pois_ny_parks AS \n" + "SELECT * \n" + " FROM pois_ny \n" + " WHERE cat='park';\n" + " \n" + "SELECT f_table_name, f_geometry_column, srid, type \n" + " FROM geometry_columns \n" + " WHERE f_table_name = 'vw_pois_ny_parks';" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:693 +#, no-c-format +msgid "The typmod based geom view column registers correctly, but the constraint based one does not." +msgstr "" + +#. Tag: screen +#: using_postgis_dataman.xml:695 +#, no-c-format +msgid "" + "f_table_name | f_geometry_column | srid | type\n" + "------------------+-------------------+------+----------\n" + " vw_pois_ny_parks | geom | 4326 | POINT\n" + " vw_pois_ny_parks | geom_2160 | 0 | GEOMETRY" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:697 +#, no-c-format +msgid "This may change in future versions of PostGIS, but for now To force the constraint based view column to register correctly, we need to do this:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:699 +#, no-c-format +msgid "" + "DROP VIEW vw_pois_ny_parks;\n" + "CREATE VIEW vw_pois_ny_parks AS \n" + "SELECT gid, poi_name, cat\n" + " , geom\n" + " , geom_2160::geometry(POINT,2160) As geom_2160 \n" + " FROM pois_ny \n" + " WHERE cat='park';\n" + "SELECT f_table_name, f_geometry_column, srid, type \n" + " FROM geometry_columns \n" + " WHERE f_table_name = 'vw_pois_ny_parks';" +msgstr "" + +#. Tag: screen +#: using_postgis_dataman.xml:700 +#, no-c-format +msgid "" + "f_table_name | f_geometry_column | srid | type\n" + "------------------+-------------------+------+-------\n" + " vw_pois_ny_parks | geom | 4326 | POINT\n" + " vw_pois_ny_parks | geom_2160 | 2160 | POINT" +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:704 +#, no-c-format +msgid "Ensuring OpenGIS compliancy of geometries" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:706 +#, no-c-format +msgid "PostGIS is compliant with the Open Geospatial Consortium’s (OGC) OpenGIS Specifications. As such, many PostGIS methods require, or more accurately, assume that geometries that are operated on are both simple and valid. For example, it does not make sense to calculate the area of a polygon that has a hole defined outside of the polygon, or to construct a polygon from a non-simple boundary line." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:713 +#, no-c-format +msgid "According to the OGC Specifications, a simple geometry is one that has no anomalous geometric points, such as self intersection or self tangency and primarily refers to 0 or 1-dimensional geometries (i.e. [MULTI]POINT, [MULTI]LINESTRING). Geometry validity, on the other hand, primarily refers to 2-dimensional geometries (i.e. [MULTI]POLYGON) and defines the set of assertions that characterizes a valid polygon. The description of each geometric class includes specific conditions that further detail geometric simplicity and validity." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:723 +#, no-c-format +msgid "A POINT is inheritably simple as a 0-dimensional geometry object." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:726 +#, no-c-format +msgid "MULTIPOINTs are simple if no two coordinates (POINTs) are equal (have identical coordinate values)." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:730 +#, no-c-format +msgid "A LINESTRING is simple if it does not pass through the same POINT twice (except for the endpoints, in which case it is referred to as a linear ring and additionally considered closed)." +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:745 +#, no-c-format +msgid "(a)" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:755 +#, no-c-format +msgid "(b)" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:767 +#, no-c-format +msgid "(c)" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:777 +#, no-c-format +msgid "(d)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:787 +#, no-c-format +msgid "(a) and (c) are simple LINESTRINGs, (b) and (d) are not." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:796 +#, no-c-format +msgid "A MULTILINESTRING is simple only if all of its elements are simple and the only intersection between any two elements occurs at POINTs that are on the boundaries of both elements." +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:811 +#, no-c-format +msgid "(e)" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:821 +#, no-c-format +msgid "(f)" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:831 +#, no-c-format +msgid "(g)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:841 +#, no-c-format +msgid "(e) and (f) are simple MULTILINESTRINGs, (g) is not." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:850 +#, no-c-format +msgid "By definition, a POLYGON is always simple. It is valid if no two rings in the boundary (made up of an exterior ring and interior rings) cross. The boundary of a POLYGON may intersect at a POINT but only as a tangent (i.e. not on a line). A POLYGON may not have cut lines or spikes and the interior rings must be contained entirely within the exterior ring." +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:868 +#, no-c-format +msgid "(h)" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:878 +#, no-c-format +msgid "(i)" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:888 +#, no-c-format +msgid "(j)" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:900 +#, no-c-format +msgid "(k)" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:910 +#, no-c-format +msgid "(l)" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:920 +#, no-c-format +msgid "(m)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:929 +#, no-c-format +msgid "(h) and (i) are valid POLYGONs, (j-m) cannot be represented as single POLYGONs, but (j) and (m) could be represented as a valid MULTIPOLYGON." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:941 +#, no-c-format +msgid "A MULTIPOLYGON is valid if and only if all of its elements are valid and the interiors of no two elements intersect. The boundaries of any two elements may touch, but only at a finite number of POINTs." +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:956 +#, no-c-format +msgid "(n)" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:966 +#, no-c-format +msgid "(o)" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:976 +#, no-c-format +msgid "(p)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:985 +#, no-c-format +msgid "(n) and (o) are not valid MULTIPOLYGONs. (p), however, is valid." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:994 +#, no-c-format +msgid "Most of the functions implemented by the GEOS library rely on the assumption that your geometries are valid as specified by the OpenGIS Simple Feature Specification. To check simplicity or validity of geometries you can use the ST_IsSimple() and ST_IsValid()" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1000 +#, no-c-format +msgid "" + "-- Typically, it doesn't make sense to check\n" + "-- for validity on linear features since it will always return TRUE.\n" + "-- But in this example, PostGIS extends the definition of the OGC IsValid\n" + "-- by returning false if a LineString has less than 2 *distinct* vertices.\n" + "gisdb=# SELECT\n" + " ST_IsValid('LINESTRING(0 0, 1 1)'),\n" + " ST_IsValid('LINESTRING(0 0, 0 0, 0 0)');\n" + "\n" + " st_isvalid | st_isvalid\n" + "------------+-----------\n" + " t | f" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1002 +#, no-c-format +msgid "By default, PostGIS does not apply this validity check on geometry input, because testing for validity needs lots of CPU time for complex geometries, especially polygons. If you do not trust your data sources, you can manually enforce such a check to your tables by adding a check constraint:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1008 +#, no-c-format +msgid "" + "ALTER TABLE mytable\n" + " ADD CONSTRAINT geometry_valid_check\n" + " CHECK (ST_IsValid(the_geom));" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1010 +#, no-c-format +msgid "If you encounter any strange error messages such as \"GEOS Intersection() threw an error!\" or \"JTS Intersection() threw an error!\" when calling PostGIS functions with valid input geometries, you likely found an error in either PostGIS or one of the libraries it uses, and you should contact the PostGIS developers. The same is true if a PostGIS function returns an invalid geometry for valid input." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1018 +#, no-c-format +msgid "Strictly compliant OGC geometries cannot have Z or M values. The ST_IsValid() function won't consider higher dimensioned geometries invalid! Invocations of AddGeometryColumn() will add a constraint checking geometry dimensions, so it is enough to specify 2 there." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:1028 +#, no-c-format +msgid "Dimensionally Extended 9 Intersection Model (DE-9IM)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1030 +#, no-c-format +msgid "It is sometimes the case that the typical spatial predicates (, , , , ...) are insufficient in and of themselves to adequately provide that desired spatial filter." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1042 +#, no-c-format +msgid "For example, consider a linear dataset representing a road network. It may be the task of a GIS analyst to identify all road segments that cross each other, not at a point, but on a line, perhaps invalidating some business rule. In this case, does not adequately provide the necessary spatial filter since, for linear features, it returns true only where they cross at a point." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1049 +#, no-c-format +msgid "One two-step solution might be to first perform the actual intersection () of pairs of road segments that spatially intersect (), and then compare the intersection's with 'LINESTRING' (properly dealing with cases that return GEOMETRYCOLLECTIONs of [MULTI]POINTs, [MULTI]LINESTRINGs, etc.)." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1057 +#, no-c-format +msgid "A more elegant / faster solution may indeed be desirable." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1071 +#, no-c-format +msgid "A second [theoretical] example may be that of a GIS analyst trying to locate all wharfs or docks that intersect a lake's boundary on a line and where only one end of the wharf is up on shore. In other words, where a wharf is within, but not completely within a lake, intersecting the boundary of a lake on a line, and where the wharf's endpoints are both completely within and on the boundary of the lake. The analyst may need to use a combination of spatial predicates to isolate the sought after features:" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1082 +#, no-c-format +msgid "(lake, wharf) = TRUE" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1086 +#, no-c-format +msgid "(lake, wharf) = FALSE" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1090 +#, no-c-format +msgid "((wharf, lake)) = 'LINESTRING'" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1095 +#, no-c-format +msgid "((((wharf), (lake)))) = 1" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1098 +#, no-c-format +msgid "... (needless to say, this could get quite complicated)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1107 +#, no-c-format +msgid "So enters the Dimensionally Extended 9 Intersection Model, or DE-9IM for short." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:1111 +#, no-c-format +msgid "Theory" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1113 +#, no-c-format +msgid "According to the OpenGIS Simple Features Implementation Specification for SQL, \"the basic approach to comparing two geometries is to make pair-wise tests of the intersections between the Interiors, Boundaries and Exteriors of the two geometries and to classify the relationship between the two geometries based on the entries in the resulting 'intersection' matrix.\"" +msgstr "" + +#. Tag: glossterm +#: using_postgis_dataman.xml:1124 +#, no-c-format +msgid "Boundary" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1127 +#, no-c-format +msgid "The boundary of a geometry is the set of geometries of the next lower dimension. For POINTs, which have a dimension of 0, the boundary is the empty set. The boundary of a LINESTRING are the two endpoints. For POLYGONs, the boundary is the linework that make up the exterior and interior rings." +msgstr "" + +#. Tag: glossterm +#: using_postgis_dataman.xml:1138 +#, no-c-format +msgid "Interior" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1141 +#, no-c-format +msgid "The interior of a geometry are those points of a geometry that are left when the boundary is removed. For POINTs, the interior is the POINT itself. The interior of a LINESTRING are the set of real points between the endpoints. For POLYGONs, the interior is the areal surface inside the polygon." +msgstr "" + +#. Tag: glossterm +#: using_postgis_dataman.xml:1152 +#, no-c-format +msgid "Exterior" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1155 +#, no-c-format +msgid "The exterior of a geometry is the universe, an areal surface, not on the interior or boundary of the geometry." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1162 +#, no-c-format +msgid "Given geometry a, where the I(a), B(a), and E(a) are the Interior, Boundary, and Exterior of a, the mathematical representation of the matrix is:" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:1174 using_postgis_dataman.xml:1184 using_postgis_dataman.xml:1268 using_postgis_dataman.xml:1281 +#, no-c-format +msgid "Interior" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:1176 using_postgis_dataman.xml:1190 using_postgis_dataman.xml:1271 using_postgis_dataman.xml:1304 +#, no-c-format +msgid "Boundary" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:1178 using_postgis_dataman.xml:1196 using_postgis_dataman.xml:1274 using_postgis_dataman.xml:1327 +#, no-c-format +msgid "Exterior" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:1185 +#, no-c-format +msgid "dim( I(a) ∩ I(b) )" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:1186 +#, no-c-format +msgid "dim( I(a) ∩ B(b) )" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:1187 +#, no-c-format +msgid "dim( I(a) ∩ E(b) )" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:1191 +#, no-c-format +msgid "dim( B(a) ∩ I(b) )" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:1192 +#, no-c-format +msgid "dim( B(a) ∩ B(b) )" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:1193 +#, no-c-format +msgid "dim( B(a) ∩ E(b) )" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:1197 +#, no-c-format +msgid "dim( E(a) ∩ I(b) )" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:1198 +#, no-c-format +msgid "dim( E(a) ∩ B(b) )" +msgstr "" + +#. Tag: emphasis +#: using_postgis_dataman.xml:1199 +#, no-c-format +msgid "dim( E(a) ∩ E(b) )" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1206 +#, no-c-format +msgid "Where dim(a) is the dimension of a as specified by but has the domain of {0,1,2,T,F,*}" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1213 +#, no-c-format +msgid "0 => point" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1217 +#, no-c-format +msgid "1 => line" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1221 +#, no-c-format +msgid "2 => area" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1225 +#, no-c-format +msgid "T => {0,1,2}" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1230 +#, no-c-format +msgid "F => empty set" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1234 +#, no-c-format +msgid "* => don't care" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1238 +#, no-c-format +msgid "Visually, for two overlapping polygonal geometries, this looks like:" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1285 using_postgis_dataman.xml:1297 using_postgis_dataman.xml:1331 using_postgis_dataman.xml:1343 +#, no-c-format +msgid "dim(...) = 2" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1291 using_postgis_dataman.xml:1308 using_postgis_dataman.xml:1320 using_postgis_dataman.xml:1337 +#, no-c-format +msgid "dim(...) = 1" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1314 +#, no-c-format +msgid "dim(...) = 0" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1355 +#, no-c-format +msgid "Read from left to right and from top to bottom, the dimensional matrix is represented, '212101212'." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1358 +#, no-c-format +msgid "A relate matrix that would therefore represent our first example of two lines that intersect on a line would be: '1*1***1**'" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1362 +#, no-c-format +msgid "" + "-- Identify road segments that cross on a line\n" + "SELECT a.id\n" + "FROM roads a, roads b\n" + "WHERE a.id != b.id \n" + "AND a.geom && b.geom\n" + "AND ST_Relate(a.geom, b.geom, '1*1***1**');" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1364 +#, no-c-format +msgid "A relate matrix that represents the second example of wharfs partly on the lake's shoreline would be '102101FF2'" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1368 +#, no-c-format +msgid "" + "-- Identify wharfs partly on a lake's shoreline\n" + "SELECT a.lake_id, b.wharf_id\n" + "FROM lakes a, wharfs b\n" + "WHERE a.geom && b.geom\n" + "AND ST_Relate(a.geom, b.geom, '102101FF2');" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1370 +#, no-c-format +msgid "For more information or reading, see:" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1374 +#, no-c-format +msgid "OpenGIS Simple Features Implementation Specification for SQL (version 1.1, section 2.1.13.2)" +msgstr "" + +#. Tag: ulink +#: using_postgis_dataman.xml:1379 +#, no-c-format +msgid "Dimensionally Extended Nine-Intersection Model (DE-9IM) by Christian Strobl" +msgstr "" + +#. Tag: ulink +#: using_postgis_dataman.xml:1383 +#, no-c-format +msgid "GeoTools: Point Set Theory and the DE-9IM Matrix" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1386 +#, no-c-format +msgid "Encyclopedia of GIS By Hui Xiong" +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:1396 +#, no-c-format +msgid "Loading GIS (Vector) Data" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1398 +#, no-c-format +msgid "Once you have created a spatial table, you are ready to upload GIS data to the database. Currently, there are two ways to get data into a PostGIS/PostgreSQL database: using formatted SQL statements or using the Shape file loader/dumper." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:1404 +#, no-c-format +msgid "Loading Data Using SQL" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1406 +#, no-c-format +msgid "If you can convert your data to a text representation, then using formatted SQL might be the easiest way to get your data into PostGIS. As with Oracle and other SQL databases, data can be bulk loaded by piping a large text file full of SQL \"INSERT\" statements into the SQL terminal monitor." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1412 +#, no-c-format +msgid "A data upload file (roads.sql for example) might look like this:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1415 +#, no-c-format +msgid "" + "BEGIN;\n" + "INSERT INTO roads (road_id, roads_geom, road_name)\n" + " VALUES (1,ST_GeomFromText('LINESTRING(191232 243118,191108 243242)',-1),'Jeff Rd');\n" + "INSERT INTO roads (road_id, roads_geom, road_name)\n" + " VALUES (2,ST_GeomFromText('LINESTRING(189141 244158,189265 244817)',-1),'Geordie Rd');\n" + "INSERT INTO roads (road_id, roads_geom, road_name)\n" + " VALUES (3,ST_GeomFromText('LINESTRING(192783 228138,192612 229814)',-1),'Paul St');\n" + "INSERT INTO roads (road_id, roads_geom, road_name)\n" + " VALUES (4,ST_GeomFromText('LINESTRING(189412 252431,189631 259122)',-1),'Graeme Ave');\n" + "INSERT INTO roads (road_id, roads_geom, road_name)\n" + " VALUES (5,ST_GeomFromText('LINESTRING(190131 224148,190871 228134)',-1),'Phil Tce');\n" + "INSERT INTO roads (road_id, roads_geom, road_name)\n" + " VALUES (6,ST_GeomFromText('LINESTRING(198231 263418,198213 268322)',-1),'Dave Cres');\n" + "COMMIT;" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1417 +#, no-c-format +msgid "The data file can be piped into PostgreSQL very easily using the \"psql\" SQL terminal monitor:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1420 +#, no-c-format +msgid "psql -d [database] -f roads.sql" +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:1424 +#, no-c-format +msgid "shp2pgsql: Using the ESRI Shapefile Loader" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1426 +#, no-c-format +msgid "The shp2pgsql data loader converts ESRI Shape files into SQL suitable for insertion into a PostGIS/PostgreSQL database either in geometry or geography format. The loader has several operating modes distinguished by command line flags:" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1431 +#, no-c-format +msgid "In addition to the shp2pgsql command-line loader, there is an shp2pgsql-gui graphical interface with most of the options as the command-line loader, but may be easier to use for one-off non-scripted loading or if you are new to PostGIS. It can also be configured as a plugin to PgAdminIII." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1438 +#, no-c-format +msgid "(c|a|d|p) These are mutually exclusive options:" +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1443 +#, no-c-format +msgid "-c" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1445 +#, no-c-format +msgid "Creates a new table and populates it from the shapefile. This is the default mode." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1453 +#, no-c-format +msgid "-a" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1455 +#, no-c-format +msgid "Appends data from the Shape file into the database table. Note that to use this option to load multiple files, the files must have the same attributes and same data types." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1464 using_postgis_dataman.xml:1853 +#, no-c-format +msgid "-d" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1466 +#, no-c-format +msgid "Drops the database table before creating a new table with the data in the Shape file." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1474 +#, no-c-format +msgid "-p" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1476 +#, no-c-format +msgid "Only produces the table creation SQL code, without adding any actual data. This can be used if you need to completely separate the table creation and data loading steps." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1489 +#, no-c-format +msgid "-?" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1491 +#, no-c-format +msgid "Display help screen." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1498 +#, no-c-format +msgid "-D" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1500 +#, no-c-format +msgid "Use the PostgreSQL \"dump\" format for the output data. This can be combined with -a, -c and -d. It is much faster to load than the default \"insert\" SQL format. Use this for very large data sets." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1509 +#, no-c-format +msgid "-s [<FROM_SRID%gt;:]<SRID>" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1511 +#, no-c-format +msgid "Creates and populates the geometry tables with the specified SRID. Optionally specifies that the input shapefile uses the given FROM_SRID, in which case the geometries will be reprojected to the target SRID. FROM_SRID cannot be specified with -D." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1522 +#, no-c-format +msgid "-k" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1524 +#, no-c-format +msgid "Keep identifiers' case (column, schema and attributes). Note that attributes in Shapefile are all UPPERCASE." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1532 +#, no-c-format +msgid "-i" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1534 +#, no-c-format +msgid "Coerce all integers to standard 32-bit integers, do not create 64-bit bigints, even if the DBF header signature appears to warrant it." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1542 +#, no-c-format +msgid "-I" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1544 +#, no-c-format +msgid "Create a GiST index on the geometry column." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1551 +#, no-c-format +msgid "-m" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1553 +#, no-c-format +msgid "-m a_file_name Specify a file containing a set of mappings of (long) column names to 10 character DBF column names. The content of the file is one or more lines of two names separated by white space and no trailing or leading space. For example:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1558 +#, no-c-format +msgid "" + "COLUMNNAME DBFFIELD1\n" + "AVERYLONGCOLUMNNAME DBFFIELD2" +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1564 +#, no-c-format +msgid "-S" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1566 +#, no-c-format +msgid "Generate simple geometries instead of MULTI geometries. Will only succeed if all the geometries are actually single (I.E. a MULTIPOLYGON with a single shell, or or a MULTIPOINT with a single vertex)." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1575 +#, no-c-format +msgid "-t <dimensionality>" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1577 +#, no-c-format +msgid "Force the output geometry to have the specified dimensionality. Use the following strings to indicate the dimensionality: 2D, 3DZ, 3DM, 4D." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1581 +#, no-c-format +msgid "If the input has fewer dimensions that specified, the output will have those dimensions filled in with zeroes. If the input has more dimensions that specified, the unwanted dimensions will be stripped." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1590 +#, no-c-format +msgid "-w" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1592 +#, no-c-format +msgid "Output WKT format, instead of WKB. Note that this can introduce coordinate drifts due to loss of precision." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1600 +#, no-c-format +msgid "-e" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1602 +#, no-c-format +msgid "Execute each statement on its own, without using a transaction. This allows loading of the majority of good data when there are some bad geometries that generate errors. Note that this cannot be used with the -D flag as the \"dump\" format always uses a transaction." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1612 +#, no-c-format +msgid "-W <encoding>" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1614 +#, no-c-format +msgid "Specify encoding of the input data (dbf file). When used, all attributes of the dbf are converted from the specified encoding to UTF8. The resulting SQL output will contain a SET CLIENT_ENCODING to UTF8 command, so that the backend will be able to reconvert from UTF8 to whatever encoding the database is configured to use internally." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1624 +#, no-c-format +msgid "-N <policy>" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1626 +#, no-c-format +msgid "NULL geometries handling policy (insert*,skip,abort)" +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1632 +#, no-c-format +msgid "-n" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1634 +#, no-c-format +msgid "-n Only import DBF file. If your data has no corresponding shapefile, it will automatically switch to this mode and load just the dbf. So setting this flag is only needed if you have a full shapefile set, and you only want the attribute data and no geometry." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1642 +#, no-c-format +msgid "-G" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1644 +#, no-c-format +msgid "Use geography type instead of geometry (requires lon/lat data) in WGS84 long lat (SRID=4326)" +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1650 +#, no-c-format +msgid "-T <tablespace>" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1652 +#, no-c-format +msgid "Specify the tablespace for the new table. Indexes will still use the default tablespace unless the -X parameter is also used. The PostgreSQL documentation has a good description on when to use custom tablespaces." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1660 +#, no-c-format +msgid "-X <tablespace>" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1662 +#, no-c-format +msgid "Specify the tablespace for the new table's indexes. This applies to the primary key index, and the GIST spatial index if -I is also used." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1670 +#, no-c-format +msgid "An example session using the loader to create an input file and uploading it might look like this:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1675 +#, no-c-format +msgid "" + "# shp2pgsql -c -D -s 4269 -i -I shaperoads.shp myschema.roadstable > roads.sql\n" + "# psql -d roadsdb -f roads.sql" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1677 +#, no-c-format +msgid "A conversion and upload can be done all in one step using UNIX pipes:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1681 +#, no-c-format +msgid "# shp2pgsql shaperoads.shp myschema.roadstable | psql -d roadsdb" +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:1686 +#, no-c-format +msgid "Retrieving GIS Data" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1688 +#, no-c-format +msgid "Data can be extracted from the database using either SQL or the Shape file loader/dumper. In the section on SQL we will discuss some of the operators available to do comparisons and queries on spatial tables." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:1694 +#, no-c-format +msgid "Using SQL to Retrieve Data" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1696 +#, no-c-format +msgid "The most straightforward means of pulling data out of the database is to use a SQL select query to reduce the number of RECORDS and COLUMNS returned and dump the resulting columns into a parsable text file:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1701 +#, no-c-format +msgid "" + "db=# SELECT road_id, ST_AsText(road_geom) AS geom, road_name FROM roads;\n" + "\n" + "road_id | geom | road_name\n" + "--------+-----------------------------------------+-----------\n" + " 1 | LINESTRING(191232 243118,191108 243242) | Jeff Rd\n" + " 2 | LINESTRING(189141 244158,189265 244817) | Geordie Rd\n" + " 3 | LINESTRING(192783 228138,192612 229814) | Paul St\n" + " 4 | LINESTRING(189412 252431,189631 259122) | Graeme Ave\n" + " 5 | LINESTRING(190131 224148,190871 228134) | Phil Tce\n" + " 6 | LINESTRING(198231 263418,198213 268322) | Dave Cres\n" + " 7 | LINESTRING(218421 284121,224123 241231) | Chris Way\n" + "(6 rows)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1703 +#, no-c-format +msgid "However, there will be times when some kind of restriction is necessary to cut down the number of fields returned. In the case of attribute-based restrictions, just use the same SQL syntax as normal with a non-spatial table. In the case of spatial restrictions, the following operators are available/useful:" +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1711 +#, no-c-format +msgid "&&" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1714 +#, no-c-format +msgid "This operator tells whether the bounding box of one geometry intersects the bounding box of another." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1720 +#, no-c-format +msgid "ST_OrderingEquals" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1723 +#, no-c-format +msgid "This tests whether two geometries are geometrically identical. For example, if 'POLYGON((0 0,1 1,1 0,0 0))' is the same as 'POLYGON((0 0,1 1,1 0,0 0))' (it is)." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1730 +#, no-c-format +msgid "=" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1733 +#, no-c-format +msgid "This operator is a little more naive, it only tests whether the bounding boxes of two geometries are the same." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1739 +#, no-c-format +msgid "Next, you can use these operators in queries. Note that when specifying geometries and boxes on the SQL command line, you must explicitly turn the string representations into geometries by using the \"ST_GeomFromText()\" function. The 312 is a fictitious spatial reference system that matches our data. So, for example:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1745 +#, no-c-format +msgid "" + "SELECT road_id, road_name\n" + " FROM roads\n" + " WHERE ST_OrderingEquals(roads_geom , ST_GeomFromText('LINESTRING(191232 243118,191108 243242)',312) ) ;" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1747 +#, no-c-format +msgid "The above query would return the single record from the \"ROADS_GEOM\" table in which the geometry was equal to that value." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1750 +#, no-c-format +msgid "When using the \"&&\" operator, you can specify either a BOX3D as the comparison feature or a GEOMETRY. When you specify a GEOMETRY, however, its bounding box will be used for the comparison." +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1755 +#, no-c-format +msgid "" + "SELECT road_id, road_name\n" + "FROM roads\n" + "WHERE roads_geom && ST_GeomFromText('POLYGON((...))',312);" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1757 +#, no-c-format +msgid "The above query will use the bounding box of the polygon for comparison purposes." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1760 +#, no-c-format +msgid "The most common spatial query will probably be a \"frame-based\" query, used by client software, like data browsers and web mappers, to grab a \"map frame\" worth of data for display. Using a \"BOX3D\" object for the frame, such a query looks like this:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1765 +#, no-c-format +msgid "" + "SELECT ST_AsText(roads_geom) AS geom\n" + "FROM roads\n" + "WHERE\n" + " roads_geom && ST_MakeEnvelope(191232, 243117,191232, 243119,312);" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1767 +#, no-c-format +msgid "Note the use of the SRID 312, to specify the projection of the envelope." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:1771 +#, no-c-format +msgid "Using the Dumper" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1773 +#, no-c-format +msgid "The pgsql2shp table dumper connects directly to the database and converts a table (possibly defined by a query) into a shape file. The basic syntax is:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1777 +#, no-c-format +msgid "pgsql2shp [<options>] <database> [<schema>.]<table>" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1779 +#, no-c-format +msgid "pgsql2shp [<options>] <database> <query>" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1781 +#, no-c-format +msgid "The commandline options are:" +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1785 +#, no-c-format +msgid "-f <filename>" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1788 +#, no-c-format +msgid "Write the output to a particular filename." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1793 +#, no-c-format +msgid "-h <host>" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1796 +#, no-c-format +msgid "The database host to connect to." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1801 +#, no-c-format +msgid "-p <port>" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1804 +#, no-c-format +msgid "The port to connect to on the database host." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1809 +#, no-c-format +msgid "-P <password>" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1812 +#, no-c-format +msgid "The password to use when connecting to the database." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1817 +#, no-c-format +msgid "-u <user>" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1820 +#, no-c-format +msgid "The username to use when connecting to the database." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1825 +#, no-c-format +msgid "-g <geometry column>" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1828 +#, no-c-format +msgid "In the case of tables with multiple geometry columns, the geometry column to use when writing the shape file." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1834 +#, no-c-format +msgid "-b" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1837 +#, no-c-format +msgid "Use a binary cursor. This will make the operation faster, but will not work if any NON-geometry attribute in the table lacks a cast to text." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1844 +#, no-c-format +msgid "-r" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1847 +#, no-c-format +msgid "Raw mode. Do not drop the gid field, or escape column names." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1856 +#, no-c-format +msgid "For backward compatibility: write a 3-dimensional shape file when dumping from old (pre-1.0.0) postgis databases (the default is to write a 2-dimensional shape file in that case). Starting from postgis-1.0.0+, dimensions are fully encoded." +msgstr "" + +#. Tag: term +#: using_postgis_dataman.xml:1864 +#, no-c-format +msgid "-m filename" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1866 +#, no-c-format +msgid "Remap identifiers to ten character names. The content of the file is lines of two symbols separated by a single white space and no trailing or leading space: VERYLONGSYMBOL SHORTONE ANOTHERVERYLONGSYMBOL SHORTER etc." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:1879 +#, no-c-format +msgid "Building Indexes" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1881 +#, no-c-format +msgid "Indexes are what make using a spatial database for large data sets possible. Without indexing, any search for a feature would require a \"sequential scan\" of every record in the database. Indexing speeds up searching by organizing the data into a search tree which can be quickly traversed to find a particular record. PostgreSQL supports three kinds of indexes by default: B-Tree indexes, R-Tree indexes, and GiST indexes." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1891 +#, no-c-format +msgid "B-Trees are used for data which can be sorted along one axis; for example, numbers, letters, dates. GIS data cannot be rationally sorted along one axis (which is greater, (0,0) or (0,1) or (1,0)?) so B-Tree indexing is of no use for us." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1898 +#, no-c-format +msgid "R-Trees break up data into rectangles, and sub-rectangles, and sub-sub rectangles, etc. R-Trees are used by some spatial databases to index GIS data, but the PostgreSQL R-Tree implementation is not as robust as the GiST implementation." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1905 +#, no-c-format +msgid "GiST (Generalized Search Trees) indexes break up data into \"things to one side\", \"things which overlap\", \"things which are inside\" and can be used on a wide range of data-types, including GIS data. PostGIS uses an R-Tree index implemented on top of GiST to index GIS data." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:1914 +#, no-c-format +msgid "GiST Indexes" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1916 +#, no-c-format +msgid "GiST stands for \"Generalized Search Tree\" and is a generic form of indexing. In addition to GIS indexing, GiST is used to speed up searches on all kinds of irregular data structures (integer arrays, spectral data, etc) which are not amenable to normal B-Tree indexing." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1921 +#, no-c-format +msgid "Once a GIS data table exceeds a few thousand rows, you will want to build an index to speed up spatial searches of the data (unless all your searches are based on attributes, in which case you'll want to build a normal index on the attribute fields)." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1926 +#, no-c-format +msgid "The syntax for building a GiST index on a \"geometry\" column is as follows:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1929 +#, no-c-format +msgid "CREATE INDEX [indexname] ON [tablename] USING GIST ( [geometryfield] );" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1930 +#, no-c-format +msgid "The above syntax will always build a 2D-index. To get the an n-dimensional index supported in PostGIS 2.0+ for the geometry type, you can create one using this syntax" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1931 +#, no-c-format +msgid "CREATE INDEX [indexname] ON [tablename] USING GIST ([geometryfield] gist_geometry_ops_nd);" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1933 +#, no-c-format +msgid "Building a spatial index is a computationally intensive exercise: on tables of around 1 million rows, on a 300MHz Solaris machine, we have found building a GiST index takes about 1 hour. After building an index, it is important to force PostgreSQL to collect table statistics, which are used to optimize query plans:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:1939 +#, no-c-format +msgid "" + "VACUUM ANALYZE [table_name] [(column_name)];\n" + "-- This is only needed for PostgreSQL 7.4 installations and below\n" + "SELECT UPDATE_GEOMETRY_STATS([table_name], [column_name]);" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1941 +#, no-c-format +msgid "GiST indexes have two advantages over R-Tree indexes in PostgreSQL. Firstly, GiST indexes are \"null safe\", meaning they can index columns which include null values. Secondly, GiST indexes support the concept of \"lossiness\" which is important when dealing with GIS objects larger than the PostgreSQL 8K page size. Lossiness allows PostgreSQL to store only the \"important\" part of an object in an index -- in the case of GIS objects, just the bounding box. GIS objects larger than 8K will cause R-Tree indexes to fail in the process of being built." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:1953 +#, no-c-format +msgid "Using Indexes" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1955 +#, no-c-format +msgid "Ordinarily, indexes invisibly speed up data access: once the index is built, the query planner transparently decides when to use index information to speed up a query plan. Unfortunately, the PostgreSQL query planner does not optimize the use of GiST indexes well, so sometimes searches which should use a spatial index instead default to a sequence scan of the whole table." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1962 +#, no-c-format +msgid "If you find your spatial indexes are not being used (or your attribute indexes, for that matter) there are a couple things you can do:" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1968 +#, no-c-format +msgid "Firstly, make sure statistics are gathered about the number and distributions of values in a table, to provide the query planner with better information to make decisions around index usage. For PostgreSQL 7.4 installations and below this is done by running update_geometry_stats([table_name, column_name]) (compute distribution) and VACUUM ANALYZE [table_name] [column_name] (compute number of values). Starting with PostgreSQL 8.0 running VACUUM ANALYZE will do both operations. You should regularly vacuum your databases anyways -- many PostgreSQL DBAs have VACUUM run as an off-peak cron job on a regular basis." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1982 +#, no-c-format +msgid "If vacuuming does not work, you can force the planner to use the index information by using the SET ENABLE_SEQSCAN=OFF command. You should only use this command sparingly, and only on spatially indexed queries: generally speaking, the planner knows better than you do about when to use normal B-Tree indexes. Once you have run your query, you should consider setting ENABLE_SEQSCAN back on, so that other queries will utilize the planner as normal." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1992 +#, no-c-format +msgid "As of version 0.6, it should not be necessary to force the planner to use the index with ENABLE_SEQSCAN." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:1999 +#, no-c-format +msgid "If you find the planner wrong about the cost of sequential vs index scans try reducing the value of random_page_cost in postgresql.conf or using SET random_page_cost=#. Default value for the parameter is 4, try setting it to 1 or 2. Decrementing the value makes the planner more inclined of using Index scans." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:2010 +#, no-c-format +msgid "Complex Queries" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2012 +#, no-c-format +msgid "The raison d'etre of spatial database functionality is performing queries inside the database which would ordinarily require desktop GIS functionality. Using PostGIS effectively requires knowing what spatial functions are available, and ensuring that appropriate indexes are in place to provide good performance. The SRID of 312 used in these examples is purely for demonstration. You should be using a REAL SRID listed in the the spatial_ref_sys table and one that matches the projection of your data. If your data has no spatial reference system specified, you should be THINKING very thoughtfully why it doesn't and maybe it should. If your reason is because you are modeling something that doesn't have a geographic spatial reference system defined such as the internals of a molecule or a good location on Mars to transport the human race in the event of a nuclear holocaust, then simply leave out the SRID or make one up and insert it in the spatial_ref_sys table." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:2026 +#, no-c-format +msgid "Taking Advantage of Indexes" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2028 +#, no-c-format +msgid "When constructing a query it is important to remember that only the bounding-box-based operators such as && can take advantage of the GiST spatial index. Functions such as ST_Distance() cannot use the index to optimize their operation. For example, the following query would be quite slow on a large table:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:2035 +#, no-c-format +msgid "" + "SELECT the_geom\n" + "FROM geom_table\n" + "WHERE ST_Distance(the_geom, ST_GeomFromText('POINT(100000 200000)', 312)) < 100" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2037 +#, no-c-format +msgid "This query is selecting all the geometries in geom_table which are within 100 units of the point (100000, 200000). It will be slow because it is calculating the distance between each point in the table and our specified point, ie. one ST_Distance() calculation for each row in the table. We can avoid this by using the && operator to reduce the number of distance calculations required:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:2044 +#, no-c-format +msgid "" + "SELECT the_geom\n" + "FROM geom_table\n" + "WHERE ST_DWithin(the_geom, ST_MakeEnvelope(90900, 190900, 100100, 200100,312), 100)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2046 +#, no-c-format +msgid "This query selects the same geometries, but it does it in a more efficient way. Assuming there is a GiST index on the_geom, the query planner will recognize that it can use the index to reduce the number of rows before calculating the result of the ST_distance() function. Notice that the ST_MakeEnvelope geometry which is used in the && operation is a 200 unit square box centered on the original point - this is our \"query box\". The && operator uses the index to quickly reduce the result set down to only those geometries which have bounding boxes that overlap the \"query box\". Assuming that our query box is much smaller than the extents of the entire geometry table, this will drastically reduce the number of distance calculations that need to be done." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:2060 +#, no-c-format +msgid "Change in Behavior" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2062 +#, no-c-format +msgid "As of PostGIS 1.3.0, most of the Geometry Relationship Functions, with the notable exceptions of ST_Disjoint and ST_Relate, include implicit bounding box overlap operators." +msgstr "" + +#. Tag: title +#: using_postgis_dataman.xml:2069 +#, no-c-format +msgid "Examples of Spatial SQL" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2071 +#, no-c-format +msgid "The examples in this section will make use of two tables, a table of linear roads, and a table of polygonal municipality boundaries. The table definitions for the bc_roads table is:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:2075 +#, no-c-format +msgid "" + "Column | Type | Description\n" + "------------+-------------------+-------------------\n" + "gid | integer | Unique ID\n" + "name | character varying | Road Name\n" + "the_geom | geometry | Location Geometry (Linestring)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2077 +#, no-c-format +msgid "The table definition for the bc_municipality table is:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:2080 +#, no-c-format +msgid "" + "Column | Type | Description\n" + "-----------+-------------------+-------------------\n" + "gid | integer | Unique ID\n" + "code | integer | Unique ID\n" + "name | character varying | City / Town Name\n" + "the_geom | geometry | Location Geometry (Polygon)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2085 +#, no-c-format +msgid "What is the total length of all roads, expressed in kilometers?" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2090 +#, no-c-format +msgid "You can answer this question with a very simple piece of SQL:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:2093 +#, no-c-format +msgid "" + "SELECT sum(ST_Length(the_geom))/1000 AS km_roads FROM bc_roads;\n" + "\n" + "km_roads\n" + "------------------\n" + "70842.1243039643\n" + "(1 row)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2099 +#, no-c-format +msgid "How large is the city of Prince George, in hectares?" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2103 +#, no-c-format +msgid "This query combines an attribute condition (on the municipality name) with a spatial calculation (of the area):" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:2107 +#, no-c-format +msgid "" + "SELECT\n" + " ST_Area(the_geom)/10000 AS hectares\n" + "FROM bc_municipality\n" + "WHERE name = 'PRINCE GEORGE';\n" + "\n" + "hectares\n" + "------------------\n" + "32657.9103824927\n" + "(1 row)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2113 +#, no-c-format +msgid "What is the largest municipality in the province, by area?" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2118 +#, no-c-format +msgid "This query brings a spatial measurement into the query condition. There are several ways of approaching this problem, but the most efficient is below:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:2122 +#, no-c-format +msgid "" + "SELECT\n" + " name,\n" + " ST_Area(the_geom)/10000 AS hectares\n" + "FROM\n" + " bc_municipality\n" + "ORDER BY hectares DESC\n" + "LIMIT 1;\n" + "\n" + "name | hectares\n" + "---------------+-----------------\n" + "TUMBLER RIDGE | 155020.02556131\n" + "(1 row)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2124 +#, no-c-format +msgid "Note that in order to answer this query we have to calculate the area of every polygon. If we were doing this a lot it would make sense to add an area column to the table that we could separately index for performance. By ordering the results in a descending direction, and them using the PostgreSQL \"LIMIT\" command we can easily pick off the largest value without using an aggregate function like max()." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2136 +#, no-c-format +msgid "What is the length of roads fully contained within each municipality?" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2141 +#, no-c-format +msgid "This is an example of a \"spatial join\", because we are bringing together data from two tables (doing a join) but using a spatial interaction condition (\"contained\") as the join condition rather than the usual relational approach of joining on a common key:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:2147 +#, no-c-format +msgid "" + "SELECT\n" + " m.name,\n" + " sum(ST_Length(r.the_geom))/1000 as roads_km\n" + "FROM\n" + " bc_roads AS r,\n" + " bc_municipality AS m\n" + "WHERE\n" + " ST_Contains(m.the_geom,r.the_geom)\n" + "GROUP BY m.name\n" + "ORDER BY roads_km;\n" + "\n" + "name | roads_km\n" + "----------------------------+------------------\n" + "SURREY | 1539.47553551242\n" + "VANCOUVER | 1450.33093486576\n" + "LANGLEY DISTRICT | 833.793392535662\n" + "BURNABY | 773.769091404338\n" + "PRINCE GEORGE | 694.37554369147\n" + "..." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2149 +#, no-c-format +msgid "This query takes a while, because every road in the table is summarized into the final result (about 250K roads for our particular example table). For smaller overlays (several thousand records on several hundred) the response can be very fast." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2158 +#, no-c-format +msgid "Create a new table with all the roads within the city of Prince George." +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2163 +#, no-c-format +msgid "This is an example of an \"overlay\", which takes in two tables and outputs a new table that consists of spatially clipped or cut resultants. Unlike the \"spatial join\" demonstrated above, this query actually creates new geometries. An overlay is like a turbo-charged spatial join, and is useful for more exact analysis work:" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:2170 +#, no-c-format +msgid "" + "CREATE TABLE pg_roads as\n" + "SELECT\n" + " ST_Intersection(r.the_geom, m.the_geom) AS intersection_geom,\n" + " ST_Length(r.the_geom) AS rd_orig_length,\n" + " r.*\n" + "FROM\n" + " bc_roads AS r,\n" + " bc_municipality AS m\n" + "WHERE m.name = 'PRINCE GEORGE' AND ST_Intersects(r.the_geom, m.the_geom);" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2176 +#, no-c-format +msgid "What is the length in kilometers of \"Douglas St\" in Victoria?" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:2181 +#, no-c-format +msgid "" + "SELECT\n" + " sum(ST_Length(r.the_geom))/1000 AS kilometers\n" + "FROM\n" + " bc_roads r,\n" + " bc_municipality m\n" + "WHERE r.name = 'Douglas St' AND m.name = 'VICTORIA'\n" + " AND ST_Contains(m.the_geom, r.the_geom) ;\n" + "\n" + "kilometers\n" + "------------------\n" + "4.89151904172838\n" + "(1 row)" +msgstr "" + +#. Tag: para +#: using_postgis_dataman.xml:2187 +#, no-c-format +msgid "What is the largest municipality polygon that has a hole?" +msgstr "" + +#. Tag: programlisting +#: using_postgis_dataman.xml:2192 +#, no-c-format +msgid "" + "SELECT gid, name, ST_Area(the_geom) AS area\n" + "FROM bc_municipality\n" + "WHERE ST_NRings(the_geom) > 1\n" + "ORDER BY area DESC LIMIT 1;\n" + "\n" + "gid | name | area\n" + "-----+--------------+------------------\n" + "12 | SPALLUMCHEEN | 257374619.430216\n" + "(1 row)" +msgstr "" + diff --git a/doc/po/de_DE/using_raster_dataman.xml.po b/doc/po/de_DE/using_raster_dataman.xml.po new file mode 100644 index 000000000..8114334f5 --- /dev/null +++ b/doc/po/de_DE/using_raster_dataman.xml.po @@ -0,0 +1,1317 @@ +# SOME DESCRIPTIVE TITLE. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2015-09-29 12:21+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: using_raster_dataman.xml:3 +#, no-c-format +msgid "Raster Data Management, Queries, and Applications" +msgstr "" + +#. Tag: title +#: using_raster_dataman.xml:5 +#, no-c-format +msgid "Loading and Creating Rasters" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:6 +#, no-c-format +msgid "For most use cases, you will create PostGIS rasters by loading existing raster files using the packaged raster2pgsql raster loader." +msgstr "" + +#. Tag: title +#: using_raster_dataman.xml:9 +#, no-c-format +msgid "Using raster2pgsql to load rasters" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:10 +#, no-c-format +msgid "The raster2pgsql is a raster loader executable that loads GDAL supported raster formats into sql suitable for loading into a PostGIS raster table. It is capable of loading folders of raster files as well as creating overviews of rasters." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:13 +#, no-c-format +msgid "Since the raster2pgsql is compiled as part of PostGIS most often (unless you compile your own GDAL library), the raster types supported by the executable will be the same as those compiled in the GDAL dependency library. To get a list of raster types your particular raster2pgsql supports use the -G switch. These should be the same as those provided by your PostGIS install documented here if you are using the same gdal library for both." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:16 +#, no-c-format +msgid "The older version of this tool was a python script. The executable has replaced the python script. If you still find the need for the Python script Examples of the python one can be found at GDAL PostGIS Raster Driver Usage. Please note that the raster2pgsql python script may not work with future versions of PostGIS raster and is no longer supported." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:21 +#, no-c-format +msgid "When creating overviews of a specific factor from a set of rasters that are aligned, it is possible for the overviews to not align. Visit http://trac.osgeo.org/postgis/ticket/1764 for an example where the overviews do not align." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:23 +#, no-c-format +msgid "EXAMPLE USAGE:" +msgstr "" + +#. Tag: programlisting +#: using_raster_dataman.xml:24 +#, no-c-format +msgid "raster2pgsql raster_options_go_here raster_file someschema.sometable > out.sql" +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:28 +#, no-c-format +msgid "-?" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:30 +#, no-c-format +msgid "Display help screen. Help will also display if you don't pass in any arguments." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:37 +#, no-c-format +msgid "-G" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:39 +#, no-c-format +msgid "Print the supported raster formats." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:46 +#, no-c-format +msgid "(c|a|d|p) These are mutually exclusive options:" +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:51 +#, no-c-format +msgid "-c" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:53 +#, no-c-format +msgid "Create new table and populate it with raster(s), this is the default mode" +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:60 +#, no-c-format +msgid "-a" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:62 +#, no-c-format +msgid "Append raster(s) to an existing table." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:69 +#, no-c-format +msgid "-d" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:71 +#, no-c-format +msgid "Drop table, create new one and populate it with raster(s)" +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:78 +#, no-c-format +msgid "-p" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:80 +#, no-c-format +msgid "Prepare mode, only create the table." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:91 +#, no-c-format +msgid "Raster processing: Applying constraints for proper registering in raster catalogs" +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:96 +#, no-c-format +msgid "-C" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:98 +#, no-c-format +msgid "Apply raster constraints -- srid, pixelsize etc. to ensure raster is properly registered in raster_columns view." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:104 +#, no-c-format +msgid "-x" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:106 +#, no-c-format +msgid "Disable setting the max extent constraint. Only applied if -C flag is also used." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:112 +#, no-c-format +msgid "-r" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:114 +#, no-c-format +msgid "Set the constraints (spatially unique and coverage tile) for regular blocking. Only applied if -C flag is also used." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:125 +#, no-c-format +msgid "Raster processing: Optional parameters used to manipulate input raster dataset" +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:130 +#, no-c-format +msgid "-s <SRID>" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:132 +#, no-c-format +msgid "Assign output raster with specified SRID. If not provided or is zero, raster's metadata will be checked to determine an appropriate SRID." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:139 +#, no-c-format +msgid "-b BAND" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:141 +#, no-c-format +msgid "Index (1-based) of band to extract from raster. For more than one band index, separate with comma (,). If unspecified, all bands of raster will be extracted." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:149 +#, no-c-format +msgid "-t TILE_SIZE" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:151 +#, no-c-format +msgid "Cut raster into tiles to be inserted one per table row. TILE_SIZE is expressed as WIDTHxHEIGHT or set to the value \"auto\" to allow the loader to compute an appropriate tile size using the first raster and applied to all rasters." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:158 +#, no-c-format +msgid "-P" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:160 +#, no-c-format +msgid "Pad right-most and bottom-most tiles to guarantee that all tiles have the same width and height." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:170 +#, no-c-format +msgid "-R, --register" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:172 +#, no-c-format +msgid "Register the raster as a filesystem (out-db) raster." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:173 +#, no-c-format +msgid "Only the metadata of the raster and path location to the raster is stored in the database (not the pixels)." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:178 +#, no-c-format +msgid "-l OVERVIEW_FACTOR" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:179 +#, no-c-format +msgid "Create overview of the raster. For more than one factor, separate with comma(,). Overview table name follows the pattern o_overview factor_table, where overview factor is a placeholder for numerical overview factor and table is replaced with the base table name. Created overview is stored in the database and is not affected by -R. Note that your generated sql file will contain both the main table and overview tables." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:187 +#, no-c-format +msgid "-N NODATA" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:189 +#, no-c-format +msgid "NODATA value to use on bands without a NODATA value." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:201 +#, no-c-format +msgid "Optional parameters used to manipulate database objects" +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:206 using_raster_dataman.xml:235 +#, no-c-format +msgid "-q" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:208 +#, no-c-format +msgid "Wrap PostgreSQL identifiers in quotes" +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:213 +#, no-c-format +msgid "-f COLUMN" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:215 +#, no-c-format +msgid "Specify name of destination raster column, default is 'rast'" +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:221 +#, no-c-format +msgid "-F" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:223 +#, no-c-format +msgid "Add a column with the name of the file" +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:228 +#, no-c-format +msgid "-n COLUMN" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:230 +#, no-c-format +msgid "Specify the name of the filename column. Implies -F." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:237 +#, no-c-format +msgid "Wrap PostgreSQL identifiers in quotes." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:242 +#, no-c-format +msgid "-I" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:244 +#, no-c-format +msgid "Create a GiST index on the raster column." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:251 +#, no-c-format +msgid "-M" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:253 +#, no-c-format +msgid "Vacuum analyze the raster table." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:261 +#, no-c-format +msgid "-k" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:263 +#, no-c-format +msgid "Skip NODATA value checks for each raster band." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:271 +#, no-c-format +msgid "-T tablespace" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:273 +#, no-c-format +msgid "Specify the tablespace for the new table. Note that indices (including the primary key) will still use the default tablespace unless the -X flag is also used." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:282 +#, no-c-format +msgid "-X tablespace" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:284 +#, no-c-format +msgid "Specify the tablespace for the table's new index. This applies to the primary key and the spatial index if the -I flag is used." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:293 +#, no-c-format +msgid "-Y" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:295 +#, no-c-format +msgid "Use copy statements instead of insert statements." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:306 +#, no-c-format +msgid "-e" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:307 +#, no-c-format +msgid "Execute each statement individually, do not use a transaction." +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:311 +#, no-c-format +msgid "-E ENDIAN" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:312 +#, no-c-format +msgid "Control endianness of generated binary output of raster; specify 0 for XDR and 1 for NDR (default); only NDR output is supported now" +msgstr "" + +#. Tag: term +#: using_raster_dataman.xml:316 +#, no-c-format +msgid "-V version" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:317 +#, no-c-format +msgid "Specify version of output format. Default is 0. Only 0 is supported at this time." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:320 +#, no-c-format +msgid "An example session using the loader to create an input file and uploading it chunked in 100x100 tiles might look like this:" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:321 +#, no-c-format +msgid "You can leave the schema name out e.g demelevation instead of public.demelevation and the raster table will be created in the default schema of the database or user" +msgstr "" + +#. Tag: programlisting +#: using_raster_dataman.xml:323 +#, no-c-format +msgid "" + "raster2pgsql -s 4326 -I -C -M *.tif -F -t 100x100 public.demelevation > elev.sql\n" + "psql -d gisdb -f elev.sql" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:325 +#, no-c-format +msgid "A conversion and upload can be done all in one step using UNIX pipes:" +msgstr "" + +#. Tag: programlisting +#: using_raster_dataman.xml:327 +#, no-c-format +msgid "raster2pgsql -s 4326 -I -C -M *.tif -F -t 100x100 public.demelevation | psql -d gisdb" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:329 +#, no-c-format +msgid "Load rasters Massachusetts state plane meters aerial tiles into a schema called aerial and create a full view, 2 and 4 level overview tables, use copy mode for inserting (no intermediary file just straight to db), and -e don't force everything in a transaction (good if you want to see data in tables right away without waiting). Break up the rasters into 128x128 pixel tiles and apply raster constraints. Use copy mode instead of table insert. (-F) Include a field called filename to hold the name of the file the tiles were cut from." +msgstr "" + +#. Tag: programlisting +#: using_raster_dataman.xml:331 +#, no-c-format +msgid "raster2pgsql -I -C -e -Y -F -s 26986 -t 128x128 -l 2,4 bostonaerials2008/*.jpg aerials.boston | psql -U postgres -d gisdb -h localhost -p 5432" +msgstr "" + +#. Tag: programlisting +#: using_raster_dataman.xml:333 +#, no-c-format +msgid "" + "--get a list of raster types supported:\n" + "raster2pgsql -G" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:335 +#, no-c-format +msgid "The -G commands outputs a list something like" +msgstr "" + +#. Tag: screen +#: using_raster_dataman.xml:336 +#, no-c-format +msgid "" + "Available GDAL raster formats:\n" + " Virtual Raster\n" + " GeoTIFF\n" + " National Imagery Transmission Format\n" + " Raster Product Format TOC format\n" + " ECRG TOC format\n" + " Erdas Imagine Images (.img)\n" + " CEOS SAR Image\n" + " CEOS Image\n" + " JAXA PALSAR Product Reader (Level 1.1/1.5)\n" + " Ground-based SAR Applications Testbed File Format (.gff)\n" + " ELAS\n" + " Arc/Info Binary Grid\n" + " Arc/Info ASCII Grid\n" + " GRASS ASCII Grid\n" + " SDTS Raster\n" + " DTED Elevation Raster\n" + " Portable Network Graphics\n" + " JPEG JFIF\n" + " In Memory Raster\n" + " Japanese DEM (.mem)\n" + " Graphics Interchange Format (.gif)\n" + " Graphics Interchange Format (.gif)\n" + " Envisat Image Format\n" + " Maptech BSB Nautical Charts\n" + " X11 PixMap Format\n" + " MS Windows Device Independent Bitmap\n" + " SPOT DIMAP\n" + " AirSAR Polarimetric Image\n" + " RadarSat 2 XML Product\n" + " PCIDSK Database File\n" + " PCRaster Raster File\n" + " ILWIS Raster Map\n" + " SGI Image File Format 1.0\n" + " SRTMHGT File Format\n" + " Leveller heightfield\n" + " Terragen heightfield\n" + " USGS Astrogeology ISIS cube (Version 3)\n" + " USGS Astrogeology ISIS cube (Version 2)\n" + " NASA Planetary Data System\n" + " EarthWatch .TIL\n" + " ERMapper .ers Labelled\n" + " NOAA Polar Orbiter Level 1b Data Set\n" + " FIT Image\n" + " GRIdded Binary (.grb)\n" + " Raster Matrix Format\n" + " EUMETSAT Archive native (.nat)\n" + " Idrisi Raster A.1\n" + " Intergraph Raster\n" + " Golden Software ASCII Grid (.grd)\n" + " Golden Software Binary Grid (.grd)\n" + " Golden Software 7 Binary Grid (.grd)\n" + " COSAR Annotated Binary Matrix (TerraSAR-X)\n" + " TerraSAR-X Product\n" + " DRDC COASP SAR Processor Raster\n" + " R Object Data Store\n" + " Portable Pixmap Format (netpbm)\n" + " USGS DOQ (Old Style)\n" + " USGS DOQ (New Style)\n" + " ENVI .hdr Labelled\n" + " ESRI .hdr Labelled\n" + " Generic Binary (.hdr Labelled)\n" + " PCI .aux Labelled\n" + " Vexcel MFF Raster\n" + " Vexcel MFF2 (HKV) Raster\n" + " Fuji BAS Scanner Image\n" + " GSC Geogrid\n" + " EOSAT FAST Format\n" + " VTP .bt (Binary Terrain) 1.3 Format\n" + " Erdas .LAN/.GIS\n" + " Convair PolGASP\n" + " Image Data and Analysis\n" + " NLAPS Data Format\n" + " Erdas Imagine Raw\n" + " DIPEx\n" + " FARSITE v.4 Landscape File (.lcp)\n" + " NOAA Vertical Datum .GTX\n" + " NADCON .los/.las Datum Grid Shift\n" + " NTv2 Datum Grid Shift\n" + " ACE2\n" + " Snow Data Assimilation System\n" + " Swedish Grid RIK (.rik)\n" + " USGS Optional ASCII DEM (and CDED)\n" + " GeoSoft Grid Exchange Format\n" + " Northwood Numeric Grid Format .grd/.tab\n" + " Northwood Classified Grid Format .grc/.tab\n" + " ARC Digitized Raster Graphics\n" + " Standard Raster Product (ASRP/USRP)\n" + " Magellan topo (.blx)\n" + " SAGA GIS Binary Grid (.sdat)\n" + " Kml Super Overlay\n" + " ASCII Gridded XYZ\n" + " HF2/HFZ heightfield raster\n" + " OziExplorer Image File\n" + " USGS LULC Composite Theme Grid\n" + " Arc/Info Export E00 GRID\n" + " ZMap Plus Grid\n" + " NOAA NGS Geoid Height Grids" +msgstr "" + +#. Tag: title +#: using_raster_dataman.xml:339 +#, no-c-format +msgid "Creating rasters using PostGIS raster functions" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:340 +#, no-c-format +msgid "On many occasions, you'll want to create rasters and raster tables right in the database. There are a plethora of functions to do that. The general steps to follow." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:342 +#, no-c-format +msgid "Create a table with a raster column to hold the new raster records which can be accomplished with:" +msgstr "" + +#. Tag: programlisting +#: using_raster_dataman.xml:343 +#, no-c-format +msgid "CREATE TABLE myrasters(rid serial primary key, rast raster);" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:346 +#, no-c-format +msgid "There are many functions to help with that goal. If you are creating rasters not as a derivative of other rasters, you will want to start with: , followed by " +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:348 +#, no-c-format +msgid "You can also create rasters from geometries. To achieve that you'll want to use perhaps accompanied with other functions such as or or any of the family of other map algebra functions." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:350 +#, no-c-format +msgid "There are even many more options for creating new raster tables from existing tables. For example you can create a raster table in a different projection from an existing one using " +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:352 +#, no-c-format +msgid "Once you are done populating your table initially, you'll want to create a spatial index on the raster column with something like:" +msgstr "" + +#. Tag: programlisting +#: using_raster_dataman.xml:353 +#, no-c-format +msgid "CREATE INDEX myrasters_rast_st_convexhull_idx ON myrasters USING gist( ST_ConvexHull(rast) );" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:354 +#, no-c-format +msgid "Note the use of since most raster operators are based on the convex hull of the rasters." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:355 +#, no-c-format +msgid "Pre-2.0 versions of PostGIS raster were based on the envelop rather than the convex hull. For the spatial indexes to work properly you'll need to drop those and replace with convex hull based index." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:356 +#, no-c-format +msgid "Apply raster constraints using " +msgstr "" + +#. Tag: title +#: using_raster_dataman.xml:361 +#, no-c-format +msgid "Raster Catalogs" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:362 +#, no-c-format +msgid "There are two raster catalog views that come packaged with PostGIS. Both views utilize information embedded in the constraints of the raster tables. As a result the catalog views are always consistent with the raster data in the tables since the constraints are enforced." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:366 +#, no-c-format +msgid "raster_columns this view catalogs all the raster table columns in your database." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:369 +#, no-c-format +msgid "raster_overviews this view catalogs all the raster table columns in your database that serve as overviews for a finer grained table. Tables of this type are generated when you use the -l switch during load." +msgstr "" + +#. Tag: title +#: using_raster_dataman.xml:373 +#, no-c-format +msgid "Raster Columns Catalog" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:374 +#, no-c-format +msgid "The raster_columns is a catalog of all raster table columns in your database that are of type raster. It is a view utilizing the constraints on the tables so the information is always consistent even if you restore one raster table from a backup of another database. The following columns exist in the raster_columns catalog." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:376 +#, no-c-format +msgid "If you created your tables not with the loader or forgot to specify the -C flag during load, you can enforce the constraints after the fact using so that the raster_columns catalog registers the common information about your raster tiles." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:381 +#, no-c-format +msgid "r_table_catalog The database the table is in. This will always read the current database." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:384 +#, no-c-format +msgid "r_table_schema The database schema the raster table belongs to." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:387 +#, no-c-format +msgid "r_table_name raster table" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:390 +#, no-c-format +msgid "r_raster_column the column in the r_table_name table that is of type raster. There is nothing in PostGIS preventing you from having multiple raster columns per table so its possible to have a raster table listed multiple times with a different raster column for each." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:393 +#, no-c-format +msgid "srid The spatial reference identifier of the raster. Should be an entry in the ." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:396 +#, no-c-format +msgid "scale_x The scaling between geometric spatial coordinates and pixel. This is only available if all tiles in the raster column have the same scale_x and this constraint is applied. Refer to for more details." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:399 +#, no-c-format +msgid "scale_y The scaling between geometric spatial coordinates and pixel. This is only available if all tiles in the raster column have the same scale_y and the scale_y constraint is applied. Refer to for more details." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:402 +#, no-c-format +msgid "blocksize_x The width (number of pixels across) of each raster tile . Refer to for more details." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:405 +#, no-c-format +msgid "blocksize_y The width (number of pixels down) of each raster tile . Refer to for more details." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:408 +#, no-c-format +msgid "same_alignment A boolean that is true if all the raster tiles have the same alignment . Refer to for more details." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:411 +#, no-c-format +msgid "regular_blocking If the raster column has the spatially unique and coverage tile constraints, the value with be TRUE. Otherwise, it will be FALSE." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:414 +#, no-c-format +msgid "num_bands The number of bands in each tile of your raster set. This is the same information as what is provided by" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:417 +#, no-c-format +msgid "pixel_types An array defining the pixel type for each band. You will have the same number of elements in this array as you have number of bands. The pixel_types are one of the following defined in ." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:420 +#, no-c-format +msgid "nodata_values An array of double precision numbers denoting the nodata_value for each band. You will have the same number of elements in this array as you have number of bands. These numbers define the pixel value for each band that should be ignored for most operations. This is similar information provided by ." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:423 +#, no-c-format +msgid "out_db An array of boolean flags indicating if the raster bands data is maintained outside the database. You will have the same number of elements in this array as you have number of bands." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:426 +#, no-c-format +msgid "extent This is the extent of all the raster rows in your raster set. If you plan to load more data that will change the extent of the set, you'll want to run the function before load and then reapply constraints with after load." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:429 +#, no-c-format +msgid "spatial_index A boolean that is true if raster column has a spatial index." +msgstr "" + +#. Tag: title +#: using_raster_dataman.xml:434 +#, no-c-format +msgid "Raster Overviews" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:435 +#, no-c-format +msgid "raster_overviews catalogs information about raster table columns used for overviews and additional information about them that is useful to know when utilizing overviews. Overview tables are cataloged in both raster_columns and raster_overviews because they are rasters in their own right but also serve an additional special purpose of being a lower resolution caricature of a higher resolution table. These are generated along-side the main raster table when you use the -l switch in raster loading or can be generated manually using ." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:436 +#, no-c-format +msgid "Overview tables contain the same constraints as other raster tables as well as additional informational only constraints specific to overviews." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:437 +#, no-c-format +msgid "The information in raster_overviews does not duplicate the information in raster_columns. If you need the information about an overview table present in raster_columns you can join the raster_overviews and raster_columns together to get the full set of information you need." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:438 +#, no-c-format +msgid "Two main reasons for overviews are:" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:440 +#, no-c-format +msgid "Low resolution representation of the core tables commonly used for fast mapping zoom-out." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:441 +#, no-c-format +msgid "Computations are generally faster to do on them than their higher resolution parents because there are fewer records and each pixel covers more territory. Though the computations are not as accurate as the high-res tables they support, they can be sufficient in many rule-of-thumb computations." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:444 +#, no-c-format +msgid "The raster_overviews catalog contains the following columns of information." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:447 +#, no-c-format +msgid "o_table_catalog The database the overview table is in. This will always read the current database." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:450 +#, no-c-format +msgid "o_table_schema The database schema the overview raster table belongs to." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:453 +#, no-c-format +msgid "o_table_name raster overview table name" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:456 +#, no-c-format +msgid "o_raster_column the raster column in the overview table." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:460 +#, no-c-format +msgid "r_table_catalog The database the raster table that this overview services is in. This will always read the current database." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:463 +#, no-c-format +msgid "r_table_schema The database schema the raster table that this overview services belongs to." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:466 +#, no-c-format +msgid "r_table_name raster table that this overview services." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:469 +#, no-c-format +msgid "r_raster_column the raster column that this overview column services." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:472 +#, no-c-format +msgid "overview_factor - this is the pyramid level of the overview table. The higher the number the lower the resolution of the table. raster2pgsql if given a folder of images, will compute overview of each image file and load separately. Level 1 is assumed and always the original file. Level 2 is will have each tile represent 4 of the original. So for example if you have a folder of 5000x5000 pixel image files that you chose to chunk 125x125, for each image file your base table will have (5000*5000)/(125*125) records = 1600, your (l=2) o_2 table will have ceiling(1600/Power(2,2)) = 400 rows, your (l=3) o_3 will have ceiling(1600/Power(2,3) ) = 200 rows. If your pixels aren't divisible by the size of your tiles, you'll get some scrap tiles (tiles not completely filled). Note that each overview tile generated by raster2pgsql has the same number of pixels as its parent, but is of a lower resolution where each pixel of it represents (Power(2,overview_factor) pixels of the original)." +msgstr "" + +#. Tag: title +#: using_raster_dataman.xml:484 +#, no-c-format +msgid "Building Custom Applications with PostGIS Raster" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:485 +#, no-c-format +msgid "The fact that PostGIS raster provides you with SQL functions to render rasters in known image formats gives you a lot of optoins for rendering them. For example you can use OpenOffice / LibreOffice for rendering as demonstrated in Rendering PostGIS Raster graphics with LibreOffice Base Reports. In addition you can use a wide variety of languages as demonstrated in this section." +msgstr "" + +#. Tag: title +#: using_raster_dataman.xml:488 +#, no-c-format +msgid "PHP Example Outputting using ST_AsPNG in concert with other raster functions" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:489 +#, no-c-format +msgid "In this section, we'll demonstrate how to use the PHP PostgreSQL driver and the family of functions to output band 1,2,3 of a raster to a PHP request stream that can then be embedded in an img src html tag." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:492 using_raster_dataman.xml:504 +#, no-c-format +msgid "The sample query demonstrates how to combine a whole bunch of raster functions together to grab all tiles that intersect a particular wgs 84 bounding box and then unions with the intersecting tiles together returning all bands, transforms to user specified projection using , and then outputs the results as a png using ." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:495 +#, no-c-format +msgid "You would call the below using http://mywebserver/test_raster.php?srid=2249 to get the raster image in Massachusetts state plane feet." +msgstr "" + +#. Tag: programlisting +#: using_raster_dataman.xml:496 +#, no-c-format +msgid "" + "]]>" +msgstr "" + +#. Tag: title +#: using_raster_dataman.xml:499 +#, no-c-format +msgid "ASP.NET C# Example Outputting using ST_AsPNG in concert with other raster functions" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:500 +#, no-c-format +msgid "In this section, we'll demonstrate how to use Npgsql PostgreSQL .NET driver and the family of functions to output band 1,2,3 of a raster to a PHP request stream that can then be embedded in an img src html tag." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:503 +#, no-c-format +msgid "You will need the npgsql .NET PostgreSQL driver for this exercise which you can get the latest of from http://npgsql.projects.postgresql.org/. Just download the latest and drop into your ASP.NET bin folder and you'll be good to go." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:507 +#, no-c-format +msgid "This is same example as except implemented in C#." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:508 +#, no-c-format +msgid "You would call the below using http://mywebserver/TestRaster.ashx?srid=2249 to get the raster image in Massachusetts state plane feet." +msgstr "" + +#. Tag: programlisting +#: using_raster_dataman.xml:509 +#, no-c-format +msgid "" + "-- web.config connection string section --\n" + "\n" + " \n" + "]]>" +msgstr "" + +#. Tag: programlisting +#: using_raster_dataman.xml:510 +#, no-c-format +msgid "" + "// Code for TestRaster.ashx\n" + "\n" + "using System;\n" + "using System.Data;\n" + "using System.Web;\n" + "using Npgsql;\n" + "\n" + "public class TestRaster : IHttpHandler\n" + "{\n" + " public void ProcessRequest(HttpContext context)\n" + " {\n" + " \n" + " context.Response.ContentType = \"image/png\";\n" + " context.Response.BinaryWrite(GetResults(context));\n" + " \n" + " }\n" + "\n" + " public bool IsReusable {\n" + " get { return false; }\n" + " }\n" + "\n" + " public byte[] GetResults(HttpContext context)\n" + " {\n" + " byte[] result = null;\n" + " NpgsqlCommand command;\n" + " string sql = null;\n" + " int input_srid = 26986;\n" + " try {\n" + " using (NpgsqlConnection conn = new NpgsqlConnection(System.Configuration.ConfigurationManager.ConnectionStrings[\"DSN\"].ConnectionString)) {\n" + " conn.Open();\n" + "\n" + " if (context.Request[\"srid\"] != null)\n" + " {\n" + " input_srid = Convert.ToInt32(context.Request[\"srid\"]); \n" + " }\n" + " sql = @\"SELECT ST_AsPNG(\n" + " ST_Transform(\n" + " ST_AddBand(\n" + " ST_Union(rast,1), ARRAY[ST_Union(rast,2),ST_Union(rast,3)])\n" + " ,:input_srid) ) As new_rast \n" + " FROM aerials.boston \n" + " WHERE \n" + " ST_Intersects(rast, \n" + " ST_Transform(ST_MakeEnvelope(-71.1217, 42.227, -71.1210, 42.218,4326),26986) )\";\n" + " command = new NpgsqlCommand(sql, conn);\n" + " command.Parameters.Add(new NpgsqlParameter(\"input_srid\", input_srid));\n" + " \n" + " \n" + " result = (byte[]) command.ExecuteScalar();\n" + " conn.Close();\n" + " }\n" + "\n" + " }\n" + " catch (Exception ex)\n" + " {\n" + " result = null;\n" + " context.Response.Write(ex.Message.Trim());\n" + " }\n" + " return result;\n" + " }\n" + "}]]>" +msgstr "" + +#. Tag: title +#: using_raster_dataman.xml:513 +#, no-c-format +msgid "Java console app that outputs raster query as Image file" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:514 +#, no-c-format +msgid "This is a simple java console app that takes a query that returns one image and outputs to specified file." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:515 +#, no-c-format +msgid "You can download the latest PostgreSQL JDBC drivers from http://jdbc.postgresql.org/download.html" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:516 +#, no-c-format +msgid "You can compile the following code using a command something like:" +msgstr "" + +#. Tag: programlisting +#: using_raster_dataman.xml:517 +#, no-c-format +msgid "" + "set env CLASSPATH .:..\\postgresql-9.0-801.jdbc4.jar\n" + "javac SaveQueryImage.java\n" + "jar cfm SaveQueryImage.jar Manifest.txt *.class" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:518 +#, no-c-format +msgid "And call it from the command-line with something like" +msgstr "" + +#. Tag: programlisting +#: using_raster_dataman.xml:519 +#, no-c-format +msgid "java -jar SaveQueryImage.jar \"SELECT ST_AsPNG(ST_AsRaster(ST_Buffer(ST_Point(1,5),10, 'quad_segs=2'),150, 150, '8BUI',100));\" \"test.png\"" +msgstr "" + +#. Tag: programlisting +#: using_raster_dataman.xml:520 +#, no-c-format +msgid "" + "-- Manifest.txt --\n" + "" +msgstr "" + +#. Tag: programlisting +#: using_raster_dataman.xml:521 +#, no-c-format +msgid "" + "// Code for SaveQueryImage.java\n" + "" +msgstr "" + +#. Tag: title +#: using_raster_dataman.xml:525 +#, no-c-format +msgid "Use PLPython to dump out images via SQL" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:526 +#, no-c-format +msgid "This is a plpython stored function that creates a file in the server directory for each record. Requires you have plpython installed. Should work fine with both plpythonu and plpython3u." +msgstr "" + +#. Tag: programlisting +#: using_raster_dataman.xml:528 +#, no-c-format +msgid "" + "" +msgstr "" + +#. Tag: programlisting +#: using_raster_dataman.xml:529 +#, no-c-format +msgid "" + "--write out 5 images to the PostgreSQL server in varying sizes\n" + "-- note the postgresql daemon account needs to have write access to folder\n" + "-- this echos back the file names created;\n" + " SELECT write_file(ST_AsPNG(\n" + " ST_AsRaster(ST_Buffer(ST_Point(1,5),j*5, 'quad_segs=2'),150*j, 150*j, '8BUI',100)),\n" + " 'C:/temp/slices'|| j || '.png')\n" + " FROM generate_series(1,5) As j;\n" + " \n" + " write_file\n" + "---------------------\n" + " C:/temp/slices1.png\n" + " C:/temp/slices2.png\n" + " C:/temp/slices3.png\n" + " C:/temp/slices4.png\n" + " C:/temp/slices5.png" +msgstr "" + +#. Tag: title +#: using_raster_dataman.xml:532 +#, no-c-format +msgid "Outputting Rasters with PSQL" +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:533 +#, no-c-format +msgid "Sadly PSQL doesn't have easy to use built-in functionality for outputting binaries. This is a bit of a hack and based on one of the suggestions outlined in Clever Trick Challenge -- Outputting bytea with psql that piggy backs on PostgreSQL somewhat legacy large object support. To use first launch your psql commandline connected to your database." +msgstr "" + +#. Tag: para +#: using_raster_dataman.xml:536 +#, no-c-format +msgid "Unlike the python approach, this approach creates the file on your local computer." +msgstr "" + +#. Tag: screen +#: using_raster_dataman.xml:537 +#, no-c-format +msgid "" + "SELECT oid, lowrite(lo_open(oid, 131072), png) As num_bytes\n" + " FROM \n" + " ( VALUES (lo_create(0), \n" + " ST_AsPNG( (SELECT rast FROM aerials.boston WHERE rid=1) ) \n" + " ) ) As v(oid,png);\n" + "-- you'll get an output something like --\n" + " oid | num_bytes\n" + "---------+-----------\n" + " 2630819 | 74860\n" + " \n" + "-- next note the oid and do this replacing the c:/test.png to file path location\n" + "-- on your local computer\n" + " \\lo_export 2630819 'C:/temp/aerial_samp.png'\n" + " \n" + "-- this deletes the file from large object storage on db\n" + "SELECT lo_unlink(2630819);" +msgstr "" + -- 2.40.0