# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# pibinko <pibinko@gmail.com>, 2013
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2013-12-02 15:37+0000\n"
+"Last-Translator: pibinko <pibinko@gmail.com>\n"
+"Language-Team: Italian (Italy) (http://www.transifex.com/projects/p/postgis-1/language/it_IT/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: it_IT\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. Tag: title
#: faq.xml:3
#, no-c-format
msgid "PostGIS Frequently Asked Questions"
-msgstr ""
+msgstr "Domande frequenti (F.A.Q) su PostGIS"
#. Tag: para
#: faq.xml:8
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 ""
+msgstr "Le mie applicazioni e i miei strumenti desktop funzionavano con PostGIS 1.5, ma non funzionano con PostGIS 2.0. Come posso risolvere la cosa?"
#. Tag: para
#: faq.xml:12
#, no-c-format
msgid ""
"A lot of deprecated functions were removed from the PostGIS code base in "
-"PostGIS 2.0. This has affected applications in addition to third-party tools "
-"such as Geoserver, MapServer, QuantumGIS, and OpenJump to name a few. There "
-"are a couple of ways to resolve this. For the third-party apps, you can try "
-"to upgrade to the latest versions of these which have many of these issues "
+"PostGIS 2.0. This has affected applications in addition to third-party tools"
+" such as Geoserver, MapServer, QuantumGIS, and OpenJump to name a few. There"
+" are a couple of ways to resolve this. For the third-party apps, you can try"
+" to upgrade to the latest versions of these which have many of these issues "
"fixed. For your own code, you can change your code to not use the functions "
"removed. Most of these functions are non ST_ aliases of ST_Union, ST_Length "
-"etc. and as a last resort, install the whole of <varname>legacy.sql</"
-"varname> or just the portions of <varname>legacy.sql</varname> you need."
-msgstr ""
+"etc. and as a last resort, install the whole of "
+"<varname>legacy.sql</varname> or just the portions of "
+"<varname>legacy.sql</varname> you need."
+msgstr "Diverse funzioni obsolete sono state eliminate dal codice PostGIS nella versione 2.0. Ciò ha avuto un effetto sulle applicazioni, oltre che su strumenti di terze parti quali Geoserver, MapServer, QuantumGIS e OpenJump, per citarne alcuni. Ci sono un paio di modi per risolvere il problema. Per le applicazioni di terze parti, potere provare ad aggiornarle alla versione più recente, in cui molti di questi problemi sono stati sistemati. Per il codice da che hai sviluppato tu, puoi modificare il codice in modo da non utilizzare le funzioni eliminate. [TO BE COMPLETED HAVING CLARIFIED ISSUE]"
#. Tag: para
#: faq.xml:18
"postgis.sql. You can install this file after you have installed postgis.sql "
"and spatial_ref_sys.sql to get back all the 200 some-odd old functions we "
"removed."
-msgstr ""
+msgstr "Il file <varname>legacy.sql</varname> è ubicato nella stessa cartella di postgis.sql. Puoi installare questo file dopo aver installato postgis.sql e spatial_ref_sys.sql per recuperare le circa 200 vecchie funzioni che abbiamo eliminato."
#. Tag: para
#: faq.xml:24
msgid ""
"I'm running PostgreSQL 9.0 and I can no longer read/view geometries in "
"OpenJump, Safe FME, and some other tools?"
-msgstr ""
+msgstr "Sto usando PostgreSQL 9.0 e non posso più leggere le geometrie in OpenJump, Safe FME e altri strumenti. Come mai?"
#. Tag: para
#: faq.xml:28
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 ""
+msgstr "In PostgreSQL 9.0+, la codifica di default per i dati di tipo bytea è stata modificata in esadecimale e i vecchi driver JDBC considerano sempre il formato di escape. Ciò ha avuto un effetto su alcune applicazioni, quali le applicazioni Java con i driver JDBC più vecchi o le applicazioni .NET che utilizzano il vecchio driver npgsql, che si aspetta di incontrare il vecchio comportamento di ST_AsBinary. Ci sono due approcci per far funzionare nuovamente il tutto."
#. Tag: para
#: faq.xml:32
#, no-c-format
msgid ""
"You can upgrade your JDBC driver to the latest PostgreSQL 9.0 version which "
-"you can get from <ulink url=\"http://jdbc.postgresql.org/download.html"
-"\">http://jdbc.postgresql.org/download.html</ulink>"
-msgstr ""
+"you can get from <ulink "
+"url=\"http://jdbc.postgresql.org/download.html\">http://jdbc.postgresql.org/download.html</ulink>"
+msgstr "Puoi aggiornare il driver JDBC alla versione PostgreSQL 9.0 più recente dal sito <ulink url=\"http://jdbc.postgresql.org/download.html\">http://jdbc.postgresql.org/download.html</ulink>"
#. Tag: para
#: faq.xml:34
#, no-c-format
msgid ""
-"If you are running a .NET app, you can use Npgsql 2.0.11 or higher which you "
-"can download from <ulink url=\"http://pgfoundry.org/frs/?"
-"group_id=1000140\">http://pgfoundry.org/frs/?group_id=1000140</ulink> and as "
-"described on <ulink url=\"http://fxjr.blogspot.com/2010/11/npgsql-2011-"
-"released.html\">Francisco Figueiredo's NpgSQL 2.0.11 released blog entry</"
-"ulink>"
-msgstr ""
+"If you are running a .NET app, you can use Npgsql 2.0.11 or higher which you"
+" can download from <ulink "
+"url=\"http://pgfoundry.org/frs/?group_id=1000140\">http://pgfoundry.org/frs/?group_id=1000140</ulink>"
+" and as described on <ulink "
+"url=\"http://fxjr.blogspot.com/2010/11/npgsql-2011-released.html\">Francisco"
+" Figueiredo's NpgSQL 2.0.11 released blog entry</ulink>"
+msgstr "Se stai usando un'applicazione .NET, puoi utilizzare Npgsql 2.0.11 o versioni superiori, scaricandolo da <ulink url=\"http://pgfoundry.org/frs/?group_id=1000140\">http://pgfoundry.org/frs/?group_id=1000140</ulink> e seguendo le istruzioni descritte nel <ulink url=\"http://fxjr.blogspot.com/2010/11/npgsql-2011-released.html\">blog di Francisco Figueiredo su NpgSQL 2.0.11 </ulink>"
#. Tag: para
#: faq.xml:38
msgid ""
"If upgrading your PostgreSQL driver is not an option, then you can set the "
"default back to the old behavior with the following change:"
-msgstr ""
+msgstr "Se non è possibile aggiornare il tuo driver PostgreSQL, puoi ripristinare il comportamento precedente con la seguente modifica:"
#. Tag: programlisting
#: faq.xml:39
#, no-c-format
msgid "ALTER DATABASE mypostgisdb SET bytea_output='escape';"
-msgstr ""
+msgstr "ALTER DATABASE mypostgisdb SET bytea_output='escape';"
#. Tag: para
#: faq.xml:46
msgid ""
"I tried to use PgAdmin to view my geometry column and it is blank, what "
"gives?"
-msgstr ""
+msgstr "Ho provato a usare PgAdmin per visualizzare la mia colonna della geometria e questa risulta vuota. Perché?"
#. Tag: para
#: faq.xml:50
msgid ""
"PgAdmin doesn't show anything for large geometries. The best ways to verify "
"you do have data in your geometry columns are?"
-msgstr ""
+msgstr "PgAdmin non mostra nulla nel caso di grandi geometrie. I modi migliori per verificare che vi siano dati presenti nelle vostre colonne di geometria sono:"
#. Tag: programlisting
#: faq.xml:53
#, 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 ""
+msgstr "-- se tutti i tuoi campi geometrici sono popolati, questa query non dovrebbe restituire alcun record \nSELECT somefield FROM mytable WHERE geom IS NULL;"
#. Tag: programlisting
#: faq.xml:55
#, no-c-format
msgid ""
"-- To tell just how large your geometry is do a query of the form\n"
-"--which will tell you the most number of points you have in any of your "
-"geometry columns\n"
+"--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 ""
+msgstr "-- Per conoscere giusto la dimensione di una geometria, è possibile eseguire una query in una forma \n--che vi dirà il più elevato numero di punti in una colonna di geometria\nSELECT MAX(ST_NPoints(geom)) FROM sometable;"
#. Tag: para
#: faq.xml:61
#, no-c-format
msgid "What kind of geometric objects can I store?"
-msgstr ""
+msgstr "Quale tipo di oggetti geometrici posso memorizzare?"
#. Tag: para
#: faq.xml:65
#, no-c-format
msgid ""
-"You can store point, line, polygon, multipoint, multiline, multipolygon, and "
-"geometrycollections. In PostGIS 2.0 and above you can also store TINS and "
+"You can store point, line, polygon, multipoint, multiline, multipolygon, and"
+" geometrycollections. In PostGIS 2.0 and above you can also store TINS and "
"Polyhedral Surfaces in the basic geometry type. These are specified in the "
"Open GIS Well Known Text Format (with XYZ,XYM,XYZM extensions). There are "
"three data types currently supported. The standard OGC geometry data type "
"similar type in Microsoft SQL Server 2008+). Only WGS 84 long lat "
"(SRID:4326) is supported by the geography data type. The newest family "
"member of the PostGIS spatial type family is raster for storing and "
-"analyzing raster data. Raster has its very own FAQ. Refer to <xref linkend="
-"\"RT_FAQ\"/> and <xref linkend=\"RT_reference\"/> for more details."
-msgstr ""
+"analyzing raster data. Raster has its very own FAQ. Refer to <xref "
+"linkend=\"RT_FAQ\"/> and <xref linkend=\"RT_reference\"/> for more details."
+msgstr "Potete memorizzare oggetti di tipo point, line, polygon, multipoint, multiline, multipolygon, and geometrycollections. In PostGIS 2.0 e versioni superiori potete anche memorizzare TINe e superfici poliedriche con la geometria di base. Questi tipi di dati sono specificati nello Well Known Text Format di Open GIS (con le estensioni XYZ,XYM,XYZM). Attualmente vi sono tre tipo di dati supportati. Le geometrie standard OGC, che usano un sistema di coordinate piano per le misure; i dati di tipo geografico, che utilizzano un sistema di coordinate geodetico (non OGC, ma ne trovate un tipo simile in Microsoft SQL Server 2008+). Il tipo di dati geografico supporta solamente il sistema di coordinate WGS 84 long lat (SRID:4326). L'ultimo membro della famiglia dei tipi di dati spaziali di PosGIS è poi il raster. Questo ha una sua FAQ dedicata. Vi rimandiamo a <xref linkend=\"RT_reference\"/> per ulteriori informazioni."
#. Tag: para
#: faq.xml:78
#, no-c-format
msgid "I'm all confused. Which data store should I use geometry or geography?"
-msgstr ""
+msgstr "Sono confuso. Quale tipo di dati dovrei usare, quello geometrico o quello geografico?"
#. Tag: para
#: faq.xml:82
"Short Answer: geography is a new data type that supports long range "
"distances measurements, but most computations on it are currently slower "
"than they are on geometry. If you use geography -- you don't need to learn "
-"much about planar coordinate systems. Geography is generally best if all you "
-"care about is measuring distances and lengths and you have data from all "
+"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 "
+"operations on it are generally faster -- sometimes as much as 10 fold faster"
+" for larger geometries. Geometry is best if you are pretty comfortable with "
"spatial reference systems or you are dealing with localized data where all "
"your data fits in a single <link linkend=\"spatial_ref_sys\">spatial "
"reference system (SRID)</link>, or you need to do a lot of spatial "
"processing. Note: It is fairly easy to do one-off conversions between the "
-"two types to gain the benefits of each. Refer to <xref linkend="
-"\"PostGIS_TypeFunctionMatrix\"/> to see what is currently supported and what "
-"is not."
-msgstr ""
+"two types to gain the benefits of each. Refer to <xref "
+"linkend=\"PostGIS_TypeFunctionMatrix\"/> to see what is currently supported "
+"and what is not."
+msgstr "In breve: il tipo di dati geografico è un nuovo tipo che supporta i calcoli delle lunghe distanze, tuttavia la maggior parte dei calcoli con questo tipo di dati sono più lenti che non con il tipo di dati geometrico. Se utilizzate il tipo geografico non serve imparare molto sui sistemi di coordinate planari. Questo tipo è in genere migliore se dovete misurare distanze e lunghezze e avete dati da tutto il mondo. Il tipo di dati geometrico è un tipo di dati più vecchio, ha maggiore supporto da strumenti di terze parti, e le operazioni su questo sono generalmente più veloci, a volte sino a 10 volte più veloci per le geometrie più grandi. Il tipo di dati geometrico è migliore se siete a vostro agio con i sistemi di riferimento spaziale o se stai lavorando con dati su scala locale, che siano compresi in un unico sistema di riferimento spaziale (<link linkend=\"spatial_ref_sys\">spatial reference system (SRID)</link>, o se devi svolgere molte elaborazioni spaziali. Nota: è abbastanza semplice eseguire conversioni da un tipo di dati all'altro in modo da avvantaggiarsi dei pregi di ciascun sistema. Ti rimandiamo a <xref linkend=\"PostGIS_TypeFunctionMatrix\"/> per vedere che quali funzioni sono attualmente supportate e quali no."
#. Tag: para
#: faq.xml:93
#, no-c-format
msgid ""
-"Long Answer: Refer to our more lengthy discussion in the <xref linkend="
-"\"PostGIS_GeographyVSGeometry\"/> and <link linkend="
-"\"PostGIS_TypeFunctionMatrix\">function type matrix</link>."
-msgstr ""
+"Long Answer: Refer to our more lengthy discussion in the <xref "
+"linkend=\"PostGIS_GeographyVSGeometry\"/> and <link "
+"linkend=\"PostGIS_TypeFunctionMatrix\">function type matrix</link>."
+msgstr "Risposta lunga: ti rimandiamo alla discussione più estesa <xref linkend=\"PostGIS_GeographyVSGeometry\"/> e <link linkend=\"PostGIS_TypeFunctionMatrix\">matrice dei tipi di funzione</link>."
#. Tag: para
#: faq.xml:101
#, no-c-format
msgid ""
"I have more intense questions about geography, such as how big of a "
-"geographic region can I stuff in a geography column and still get reasonable "
-"answers. Are there limitations such as poles, everything in the field must "
+"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 ""
+msgstr "Ho altre domande più profonde sulla geografia, ad esempio qual è la massima dimensione di una regione geografica che posso inserire in una colonna di tipo geography per continuare ad avere risultati ragionevoli. Ci sono limitazioni ai poli, tutto deve essere in un unico emisfero (come per SQL Server 2008)?"
#. Tag: para
#: faq.xml:105
#, no-c-format
msgid ""
"Your questions are too deep and complex to be adequately answered in this "
-"section. Please refer to our <xref linkend=\"PostGIS_Geography_AdvancedFAQ\"/"
-">."
-msgstr ""
+"section. Please refer to our <xref "
+"linkend=\"PostGIS_Geography_AdvancedFAQ\"/>."
+msgstr "Le tue domande sono troppo profonde e complesse per avere una risposta in questa sezione del documento. Ti rimandiamo alle nostre <xref linkend=\"PostGIS_Geography_AdvancedFAQ\"/>."
#. Tag: para
#: faq.xml:112
#, no-c-format
msgid "How do I insert a GIS object into the database?"
-msgstr ""
+msgstr "Come posso inserire un oggetto GIS nel database?"
#. Tag: para
#: faq.xml:116
#, no-c-format
msgid ""
"First, you need to create a table with a column of type \"geometry\" or "
-"\"geography\" to hold your GIS data. Storing geography type data is a little "
-"different than storing geometry. Refer to <xref linkend=\"Geography_Basics\"/"
-"> for details on storing geography."
-msgstr ""
+"\"geography\" to hold your GIS data. Storing geography type data is a little"
+" different than storing geometry. Refer to <xref "
+"linkend=\"Geography_Basics\"/> for details on storing geography."
+msgstr "Anzitutto devi creare una tabella con una colonna di tipo \"geometry\" o \"geography\" per contenere i dati GIS. Memorizzare i dati di tipo geografico e un po' diverso dal memorizzare dati geometrici. Ti rimandiamo a <xref linkend=\"Geography_Basics\"/> per i dettagli sulla gestione dei dati geografici."
#. Tag: para
#: faq.xml:120
msgid ""
"For geometry: Connect to your database with <filename>psql</filename> and "
"try the following SQL:"
-msgstr ""
+msgstr "Per la geometria: collegati al database con <filename>psql</filename> e prova a eseguire il seguente codice SQL:"
#. Tag: programlisting
#: faq.xml:124
msgid ""
"CREATE TABLE gtest ( ID int4, NAME varchar(20) );\n"
"SELECT AddGeometryColumn('', 'gtest','geom',-1,'LINESTRING',2);"
-msgstr ""
+msgstr "CREATE TABLE gtest ( ID int4, NAME varchar(20) );\nSELECT AddGeometryColumn('', 'gtest','geom',-1,'LINESTRING',2);"
#. Tag: para
#: faq.xml:126
#, no-c-format
msgid ""
"If the geometry column addition fails, you probably have not loaded the "
-"PostGIS functions and objects into this database. See the <xref linkend="
-"\"PGInstall\"/>."
-msgstr ""
+"PostGIS functions and objects into this database. See the <xref "
+"linkend=\"PGInstall\"/>."
+msgstr "Se l'aggiunta della colonna con la geometria non funziona, probabilmente non avete caricato le funzioni e gli oggetti PostGIS nel database. Vi rimandiamo a <xref linkend=\"PGInstall\"/>."
#. Tag: para
#: faq.xml:130
#, no-c-format
msgid ""
-"Then, you can insert a geometry into the table using a SQL insert statement. "
-"The GIS object itself is formatted using the OpenGIS Consortium \"well-known "
-"text\" format:"
-msgstr ""
+"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 "Fatto questo, puoi inserire una geometria nella tabella utilizzando un comando di INSERT SQL. L'oggetto GIS vero e proprio è formattato utilizzando le specifiche \"well-known text\" dell'OpenGIS Consortium:"
#. Tag: programlisting
#: faq.xml:134
" 'First Geometry', \n"
" ST_GeomFromText('LINESTRING(2 3,4 5,6 5,7 8)', -1)\n"
");"
-msgstr ""
+msgstr "INSERT INTO gtest (ID, NAME, GEOM) \nVALUES (\n 1, \n 'First Geometry', \n ST_GeomFromText('LINESTRING(2 3,4 5,6 5,7 8)', -1)\n);"
#. Tag: para
#: faq.xml:136
#, no-c-format
msgid ""
-"For more information about other GIS objects, see the <link linkend="
-"\"RefObject\">object reference</link>."
-msgstr ""
+"For more information about other GIS objects, see the <link "
+"linkend=\"RefObject\">object reference</link>."
+msgstr "Per ulteriori informazioni su altri oggetti GIS, si rimanda alla <link linkend=\"RefObject\">guida di riferimento sugli oggetti</link>."
#. Tag: para
#: faq.xml:139
#, no-c-format
msgid "To view your GIS data in the table:"
-msgstr ""
+msgstr "Per visualizzare i dati GIS nella tabella:"
#. Tag: programlisting
#: faq.xml:141
#, no-c-format
msgid "SELECT id, name, ST_AsText(geom) AS geom FROM gtest;"
-msgstr ""
+msgstr "SELECT id, name, ST_AsText(geom) AS geom FROM gtest;"
#. Tag: para
#: faq.xml:143
#, no-c-format
msgid "The return value should look something like this:"
-msgstr ""
+msgstr "Il valore restituito dovrebbe essere qualcosa tipo:"
#. Tag: programlisting
#: faq.xml:145
"----+----------------+-----------------------------\n"
" 1 | First Geometry | LINESTRING(2 3,4 5,6 5,7 8) \n"
"(1 row)"
-msgstr ""
+msgstr "id | name | geom\n----+----------------+-----------------------------\n 1 | First Geometry | LINESTRING(2 3,4 5,6 5,7 8) \n(1 row)"
#. Tag: para
#: faq.xml:151
#, no-c-format
msgid "How do I construct a spatial query?"
-msgstr ""
+msgstr "Come posso creare una query spaziale?"
#. Tag: para
#: faq.xml:155
msgid ""
"The same way you construct any other database query, as an SQL combination "
"of return values, functions, and boolean tests."
-msgstr ""
+msgstr "Nello stesso modo in cui creeresti qualsiasi altra query per il database, come combinazione SQL di valori, funzioni e test booleani."
#. Tag: para
#: faq.xml:158
#, no-c-format
msgid ""
-"For spatial queries, there are two issues that are important to keep in mind "
-"while constructing your query: is there a spatial index you can make use of; "
-"and, are you doing expensive calculations on a large number of geometries."
-msgstr ""
+"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 "Per le query spaziali, è bene tenere a mente due aspetti: se esiste un indice spaziale che puoi utilizzare, e se stai eseguendo calcoli impegnativi su un grande numero di geometrie."
#. Tag: para
#: faq.xml:163
#, 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 ""
+msgstr "In generale, vorrai considerare l'uso dell'operatore di intersezione (&&) che verifica se le bounding box degli elementi si intersecano. La ragione per cui l'operatore &&) è utile è perché questo operatore ne farà uso, accelerando di molto le query."
#. Tag: para
#: faq.xml:170
#, no-c-format
msgid ""
"You will also make use of spatial functions, such as Distance(), "
-"ST_Intersects(), ST_Contains() and ST_Within(), among others, to narrow down "
-"the results of your search. Most spatial queries include both an indexed "
+"ST_Intersects(), ST_Contains() and ST_Within(), among others, to narrow down"
+" the results of your search. Most spatial queries include both an indexed "
"test and a spatial function test. The index test serves to limit the number "
"of return tuples to only tuples that <emphasis>might</emphasis> meet the "
"condition of interest. The spatial functions are then use to test the "
"condition exactly."
-msgstr ""
+msgstr "Utilizzerai anche funzioni spaziali quali Distance(), ST_Intersects(), ST_Contains() and ST_Within(), tra le altre, per ridurre l'insieme dei risultati della ricerca. Molte interrogazioni spaziali comprendono sia un test legato a un indice, che un test spaziale. Il test legato all'indice serve a limitare il numero di tuple a quelle che <emphasis>potrebbero</emphasis> rispondere alle condizioni richieste. Le funzioni spaziali vanno poi a verificare in modo più esatto le condizioni."
#. Tag: programlisting
#: faq.xml:178
"FROM thetable \n"
"WHERE \n"
" ST_Contains(the_geom,'POLYGON((0 0, 0 10, 10 10, 10 0, 0 0))');"
-msgstr ""
+msgstr "SELECT id, the_geom \nFROM thetable \nWHERE \n ST_Contains(the_geom,'POLYGON((0 0, 0 10, 10 10, 10 0, 0 0))');"
#. Tag: para
#: faq.xml:184
#, no-c-format
msgid "How do I speed up spatial queries on large tables?"
-msgstr ""
+msgstr "Come posso accelerare le query spaziali su grandi tabelle?"
#. Tag: para
#: faq.xml:188
#, no-c-format
msgid ""
"Fast queries on large tables is the <emphasis>raison d'etre</emphasis> of "
-"spatial databases (along with transaction support) so having a good index is "
-"important."
-msgstr ""
+"spatial databases (along with transaction support) so having a good index is"
+" important."
+msgstr "La velocità delle query su tabelle di grandi dimensioni è la <emphasis>raison d'etre</emphasis> dei database spaziali (assieme al supporto delle transazioni), per cui avere un buon indice è importante."
#. Tag: para
#: faq.xml:192
msgid ""
"To build a spatial index on a table with a <varname>geometry</varname> "
"column, use the \"CREATE INDEX\" function as follows:"
-msgstr ""
+msgstr "Per creare un indice spaziale per una tabella con colonna <varname>geometry</varname> , utilizza la funzione \"CREATE INDEX\" secono le istruzioni seguenti:"
#. Tag: programlisting
#: faq.xml:196
#, no-c-format
msgid ""
"CREATE INDEX [indexname] ON [tablename] USING GIST ( [geometrycolumn] );"
-msgstr ""
+msgstr "CREATE INDEX [indexname] ON [tablename] USING GIST ( [geometrycolumn] );"
#. Tag: para
#: faq.xml:198
#, no-c-format
msgid ""
-"The \"USING GIST\" option tells the server to use a GiST (Generalized Search "
-"Tree) index."
-msgstr ""
+"The \"USING GIST\" option tells the server to use a GiST (Generalized Search"
+" Tree) index."
+msgstr "L'opzione \"USING GIST\" dice al server di utilizzare un indice GiST (Generalized Search Tree)."
#. Tag: para
#: faq.xml:202
#: faq.xml:212
#, no-c-format
msgid ""
-"For PostgreSQL 8.0.x and greater, just run the <command>VACUUM ANALYZE</"
-"command> command."
-msgstr ""
+"For PostgreSQL 8.0.x and greater, just run the <command>VACUUM "
+"ANALYZE</command> command."
+msgstr "Per PostgreSQL 8.0.x e versioni superiori, è sufficiente eseguire il comando <command>VACUUM ANALYZE</command>."
#. Tag: para
#: faq.xml:215
#, no-c-format
msgid ""
-"For PostgreSQL 7.4.x and below, run the <command>SELECT UPDATE_GEOMETRY_STATS"
-"()</command> command."
-msgstr ""
+"For PostgreSQL 7.4.x and below, run the <command>SELECT "
+"UPDATE_GEOMETRY_STATS()</command> command."
+msgstr "Per PostgreSQL 7.4.x e versioni precedenti, eseguite il comando <command>SELECT UPDATE_GEOMETRY_STATS()</command>."
#. Tag: para
#: faq.xml:222
#, no-c-format
msgid "Why aren't PostgreSQL R-Tree indexes supported?"
-msgstr ""
+msgstr "Perché gli indici R-Tree di PostgreSQL non sono supportati?"
#. Tag: para
#: faq.xml:226
"Early versions of PostGIS used the PostgreSQL R-Tree indexes. However, "
"PostgreSQL R-Trees have been completely discarded since version 0.6, and "
"spatial indexing is provided with an R-Tree-over-GiST scheme."
-msgstr ""
+msgstr "Le prime versioni di PostGIS usavano gli indici R-Tree di PostgreSQL. Tuttavia questi sono stati completamente abbandonati a partire dalla versione 0.6, e l'indicizzazione spaziale viene fornita con un approccio R-Tree attraverso GiST."
#. Tag: para
#: faq.xml:231
"undesirable for use with GIS features (note that these limitations are due "
"to the current PostgreSQL native R-Tree implementation, not the R-Tree "
"concept in general):"
-msgstr ""
+msgstr "I nostri test hanno mostrato che la velocità di ricerca per gli indici nativi con R-tree e quelli con GiST sono paragonabili. Gli indici nativi di PostgreSQL hanno due limitazioni che li rendono non desiderabili quando si tratta di elementi GIS (si noti che queste limitazioni sono dovute all'attuale implementazione degli indici R-Tree da parte di PostgreSQL e non al concetto di R-Tree in generale):"
#. Tag: para
#: faq.xml:239
#, no-c-format
msgid ""
-"R-Tree indexes in PostgreSQL cannot handle features which are larger than 8K "
-"in size. GiST indexes can, using the \"lossy\" trick of substituting the "
+"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 ""
msgid ""
"R-Tree indexes in PostgreSQL are not \"null safe\", so building an index on "
"a geometry column which contains null geometries will fail."
-msgstr ""
+msgstr "Gli indici R-Tree di PostgreSQL non sono \"a prova di NULL\", per cui creare un indice su una colonna di geometria che contenga valori nulli non funzionerà."
#. Tag: para
#: faq.xml:256
#, no-c-format
msgid ""
-"Why should I use the <varname>AddGeometryColumn()</varname> function and all "
-"the other OpenGIS stuff?"
-msgstr ""
+"Why should I use the <varname>AddGeometryColumn()</varname> function and all"
+" the other OpenGIS stuff?"
+msgstr "Perché dovrei usare la funzione <varname>AddGeometryColumn()</varname> e tutti gli altri elementi OpenGIS?"
#. Tag: para
#: faq.xml:261
#, no-c-format
msgid ""
-"If you do not want to use the OpenGIS support functions, you do not have to. "
-"Simply create tables as in older versions, defining your geometry columns in "
-"the CREATE statement. All your geometries will have SRIDs of -1, and the "
+"If you do not want to use the OpenGIS support functions, you do not have to."
+" Simply create tables as in older versions, defining your geometry columns "
+"in the CREATE statement. All your geometries will have SRIDs of -1, and the "
"OpenGIS meta-data tables will <emphasis>not</emphasis> be filled in "
"properly. However, this will cause most applications based on PostGIS to "
"fail, and it is generally suggested that you do use "
"<varname>AddGeometryColumn()</varname> to create geometry tables."
-msgstr ""
+msgstr "Se non volete utilizzare le funzioni di supporto per OpenGIS, non siete obbligati. E' sufficiente creare le tabelle come nelle versioni più vecchie, definendo le colonne per la geometria nel comando CREATE. Tutte le geometrie avranno uno SRID uguale a -1, e le tabelle con i metadati OpenGIS <emphasis>non</emphasis> saranno compilate correttamente. Tuttavia, ciò farà sì che la maggior parte delle applicazioni basate su PostGIS abbia problemi, e in genere è consigliabile usare <varname>AddGeometryColumn()</varname> per creare tabelle con la geometria."
#. Tag: para
#: faq.xml:270
"<varname>geometry_columns</varname> meta-data. Specifically, MapServer can "
"use the SRID of the geometry column to do on-the-fly reprojection of "
"features into the correct map projection."
-msgstr ""
+msgstr "MapServer è un'applicazione che fa uso dei medatati <varname>AddGeometryColumn()geometry_columns</varname>. In particolare, MapServer può utilizzare il valore SRID della colonna geometrica per eseguire riproiezioni cartografiche al volo."
#. Tag: para
#: faq.xml:279
#, no-c-format
msgid ""
"What is the best way to find all objects within a radius of another object?"
-msgstr ""
+msgstr "Qual è il modo migliore per trovare tutti gli oggetti entro un dato raggio da un altro oggetto?"
#. Tag: para
#: faq.xml:284
#, no-c-format
msgid ""
"To use the database most efficiently, it is best to do radius queries which "
-"combine the radius test with a bounding box test: the bounding box test uses "
-"the spatial index, giving fast access to a subset of data which the radius "
+"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 ""
+msgstr "Per utilizzare il database in modo efficiente, la cosa migliore è eseguire le query con un raggio assieme al test sulla bounding box: il test sulla bounding box ricorre all'indice spaziale, dando un accesso velocizzato a un sottoinsieme dei dati cui poi viene applicato il test sul raggio."
#. Tag: para
#: faq.xml:289
#, no-c-format
msgid ""
"The <varname>ST_DWithin(geometry, geometry, distance)</varname> function is "
-"a handy way of performing an indexed distance search. It works by creating a "
-"search rectangle large enough to enclose the distance radius, then "
+"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 ""
+msgstr "La funzione <varname>ST_DWithin(geometry, geometry, distance)</varname> è un sistema pratico per eseguire una ricerca per distanza indicizzata. Funziona creando un rettangolo di ricerca grande abbastanza da racchiudere il raggio di distanza specificato, e poi eseguendo una ricerca per distanza precisa sul sottoinsieme dei risultati, che viene indicizzato."
#. Tag: para
#: faq.xml:295
msgid ""
"For example, to find all objects with 100 meters of POINT(1000 1000) the "
"following query would work well:"
-msgstr ""
+msgstr "Per esempio, per trovare tutti gli oggetti entro 100 metri dal punto POINT(1000 1000), la seguente query funzionerebbe bene:"
#. Tag: programlisting
#: faq.xml:298
msgid ""
"SELECT * FROM geotable \n"
"WHERE ST_DWithin(geocolumn, 'POINT(1000 1000)', 100.0);"
-msgstr ""
+msgstr "SELECT * FROM geotable \nWHERE ST_DWithin(geocolumn, 'POINT(1000 1000)', 100.0);"
#. Tag: para
#: faq.xml:304
#, no-c-format
msgid "How do I perform a coordinate reprojection as part of a query?"
-msgstr ""
+msgstr "Come posso eseguire una riproiezione di coordinate come parte di una query?"
#. Tag: para
#: faq.xml:309
"a reprojection is as simple as referring to the desired destination SRID. "
"The below projects a geometry to NAD 83 long lat. The below will only work "
"if the srid of the_geom is not -1 (not undefined spatial ref)"
-msgstr ""
+msgstr "Per eseguire una riproiezione, sia il sistema di riferimento di coordinate di origine che quello di destinazione devono essere definiti nella tabella SPATIAL_REF_SYS, e le geometrie da riproiettare devono già avere uno SRID assegnato. Fatto questo, la riproiezione è semplice come riferirsi allo SRID desiderato per la destinazione. L'esempio proietta una geometria in NAD 83 long lat. Il caso sotto funzionerà solamente se lo SRID di the_geom non è -1 (il riferimento spaziale non deve essere indefinito)."
#. Tag: programlisting
#: faq.xml:316
#, no-c-format
msgid "SELECT ST_Transform(the_geom,4269) FROM geotable;"
-msgstr ""
+msgstr "SELECT ST_Transform(the_geom,4269) FROM geotable;"
#. Tag: para
#: faq.xml:322
#, no-c-format
msgid ""
-"I did an ST_AsEWKT and ST_AsText on my rather large geometry and it returned "
-"blank field. What gives?"
-msgstr ""
+"I did an ST_AsEWKT and ST_AsText on my rather large geometry and it returned"
+" blank field. What gives?"
+msgstr "Ho eseguito una ST_AsEWKT e ST_AsText su una geometria piuttosto grossa ed ho ottenuto un campo vuoto. Come mai?"
#. Tag: para
#: faq.xml:326
"You are probably using PgAdmin or some other tool that doesn't output large "
"text. If your geometry is big enough, it will appear blank in these tools. "
"Use PSQL if you really need to see it or output it in WKT."
-msgstr ""
+msgstr "Probabilmente stato usando PgAdmin o qualche altro strumento che non dà in uscita testi di grandi dimensioni. Se la vostra geometria è abbastanza grande, risulterà vuota in questi strumenti. Se dovete vederla o dovete vedere l'uscita in formato WKT potete usare PSQL,"
#. Tag: programlisting
#: faq.xml:329
#, no-c-format
msgid ""
"--To check number of geometries are really blank\n"
-" SELECT count(gid) FROM geotable WHERE "
-"the_geom IS NULL;"
-msgstr ""
+" SELECT count(gid) FROM geotable WHERE the_geom IS NULL;"
+msgstr "--Per verificare il numero di geometrie che sono effettivamente vuote\n SELECT count(gid) FROM geotable WHERE the_geom IS NULL;"
#. Tag: para
#: faq.xml:335
#, no-c-format
msgid ""
-"When I do an ST_Intersects, it says my two geometries don't intersect when I "
-"KNOW THEY DO. What gives?"
-msgstr ""
+"When I do an ST_Intersects, it says my two geometries don't intersect when I"
+" KNOW THEY DO. What gives?"
+msgstr "Quando eseguo ST_Intersects, mi dice che le mie due geometrie non si intersecano, mentre SO CHE LO FANNO. Come mai?"
#. Tag: para
#: faq.xml:339
"check <xref linkend=\"ST_IsValid\"/> or you are assuming they intersect "
"because ST_AsText truncates the numbers and you have lots of decimals after "
"it is not showing you."
-msgstr ""
+msgstr "Ciò in genere accade in due casi frequenti. O la tua geometria non è valida (controlla <xref linkend=\"ST_IsValid\"/>), oppure presumi che si intersechi perche ST_AsText esegue un troncamento dei numeri e hai molti decimali che non vengono mostrati."
#. Tag: para
#: faq.xml:347
#, no-c-format
msgid ""
-"I am releasing software that uses PostGIS, does that mean my software has to "
-"be licensed using the GPL like PostGIS? Will I have to publish all my code "
+"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 ""
+msgstr "Sto rilasciando software che utilizza PostGIS. Significa che dovrà utilizzare per questo la licenza GPL come PostGIS? Dovrò pubblicare tutto il mio codice se uso PostGIS?"
#. Tag: para
#: faq.xml:351
msgid ""
"Almost certainly not. As an example, consider Oracle database running on "
"Linux. Linux is GPL, Oracle is not, does Oracle running on Linux have to be "
-"distributed using the GPL? No. So your software can use a PostgreSQL/PostGIS "
-"database as much as it wants and be under any license you like."
-msgstr ""
+"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 "Quasi sicuramente no. Per esempio, considera un database Oracle su Linux. Linux è GPL. Oracle non lo è. L'Oracle che gira su Linux deve essere distribuito con licenza GPL? No. Pertanto il tuo software può utilizzare PostgreSQL/PostGIS quanto vuole, ed essere rilasciato sotto qualsiasi tipo di licenza."
#. Tag: para
#: faq.xml:352
#, no-c-format
msgid ""
"The only exception would be if you made changes to the PostGIS source code, "
-"and distributed your changed version of PostGIS. In that case you would have "
-"to share the code of your changed PostGIS (but not the code of applications "
-"running on top of it). Even in this limited case, you would still only have "
-"to distribute source code to people you distributed binaries to. The GPL "
+"and distributed your changed version of PostGIS. In that case you would have"
+" to share the code of your changed PostGIS (but not the code of applications"
+" running on top of it). Even in this limited case, you would still only have"
+" to distribute source code to people you distributed binaries to. The GPL "
"does not require that you <emphasis>publish</emphasis> your source code, "
"only that you share it with people you give binaries to."
-msgstr ""
+msgstr "L'unica eccezione sarebbe se hai eseguito delle modifiche al sorgente di PostGIS, e hai distribuito la versione modificata di PostGIS. In questo caso devi condividere il codice del PostGIS modificato (ma non il codice delle applicazioni che girano su questo). Anche in questo caso particolare, dovrai distribuire il codice sorgente a coloro cui hai distribuito i file binari. La licenza GPL non richiede che tu <emphasis>pubblichi</emphasis> il sorgente, ma solo che tu lo condivida con coloro a cui dai i file binari."
# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# pibinko <pibinko@gmail.com>, 2013-2014
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2014-01-02 17:12+0000\n"
+"Last-Translator: pibinko <pibinko@gmail.com>\n"
+"Language-Team: Italian (Italy) (http://www.transifex.com/projects/p/postgis-1/language/it_IT/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: it_IT\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. Tag: title
#: faq_raster.xml:3
#, no-c-format
msgid "PostGIS Raster Frequently Asked Questions"
-msgstr ""
+msgstr "Domande frequenti su PostGIS raster"
#. Tag: para
#: faq_raster.xml:9
#, no-c-format
msgid "Where can I find out more about the PostGIS Raster Project?"
-msgstr ""
+msgstr "Dove posso trovare altre informazioni sul progetto PostGIS Raster?"
#. Tag: para
#: faq_raster.xml:13
#, no-c-format
msgid ""
-"Refer to the <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster"
-"\">PostGIS Raster home page</ulink>."
-msgstr ""
+"Refer to the <ulink "
+"url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster\">PostGIS Raster home "
+"page</ulink>."
+msgstr "Visita la <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster\">home page</ulink> di PostGIS Raster."
#. Tag: para
#: faq_raster.xml:19
msgid ""
"Are there any books or tutorials to get me started with this wonderful "
"invention?"
-msgstr ""
+msgstr "Ci sono libri o manuali che mi possano introdurre a questa meravigliosa invenzione?"
#. Tag: para
#: faq_raster.xml:23
#, no-c-format
msgid ""
-"There is a full length beginner tutorial <ulink url=\"http://trac.osgeo.org/"
-"postgis/wiki/WKTRasterTutorial01\"> Intersecting vector buffers with large "
-"raster coverage using PostGIS Raster</ulink>. Jorge has a series of blog "
-"articles on PostGIS Raster that demonstrate how to load raster data as well "
-"as cross compare to same tasks in Oracle GeoRaster. Check out <ulink url="
-"\"http://gis4free.wordpress.com/category/postgis-raster/\">Jorge's PostGIS "
-"Raster / Oracle GeoRaster Series</ulink>. There is a whole chapter (more "
-"than 35 pages of content) dedicated to PostGIS Raster with free code and "
-"data downloads at <ulink url=\"http://www.postgis.us/chapter_13\">PostGIS in "
-"Action - Raster chapter</ulink>. You can <ulink url=\"http://www.postgis.us/"
-"page_buy_book\">buy PostGIS in Action</ulink> now from Manning in hard-copy "
-"(significant discounts for bulk purchases) or just the E-book format. You "
-"can also buy from Amazon and various other book distributors. All hard-copy "
-"books come with a free coupon to download the E-book version."
-msgstr ""
+"There is a full length beginner tutorial <ulink "
+"url=\"http://trac.osgeo.org/postgis/wiki/WKTRasterTutorial01\"> Intersecting"
+" vector buffers with large raster coverage using PostGIS Raster</ulink>. "
+"Jorge has a series of blog articles on PostGIS Raster that demonstrate how "
+"to load raster data as well as cross compare to same tasks in Oracle "
+"GeoRaster. Check out <ulink url=\"http://gis4free.wordpress.com/category"
+"/postgis-raster/\">Jorge's PostGIS Raster / Oracle GeoRaster Series</ulink>."
+" There is a whole chapter (more than 35 pages of content) dedicated to "
+"PostGIS Raster with free code and data downloads at <ulink "
+"url=\"http://www.postgis.us/chapter_13\">PostGIS in Action - Raster "
+"chapter</ulink>. You can <ulink "
+"url=\"http://www.postgis.us/page_buy_book\">buy PostGIS in Action</ulink> "
+"now from Manning in hard-copy (significant discounts for bulk purchases) or "
+"just the E-book format. You can also buy from Amazon and various other book "
+"distributors. All hard-copy books come with a free coupon to download the "
+"E-book version."
+msgstr "C'è un tutorial completo per principianti, dal titolo <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRasterTutorial01\"> Intersecting vector buffers with large raster coverage using PostGIS Raster</ulink>. Jorge ha nel suo blog una serie di articoli su PostGIS Raster che mostrano come caricare dati raster e che danno un confronto con le funzioni analoghe di Oracle GeoRaster. Controlla la <ulink url=\"http://gis4free.wordpress.com/category/postgis-raster/\">serie di articoli di Jorge su PostGIS Raster / Oracle GeoRaster</ulink>. C'è un intero capitolo (più di 35 pagine) dedicato a PostGIS Raster, assieme a codice libero e dati da scaricare alla pagina <ulink url=\"http://www.postgis.us/chapter_13\">PostGIS in Action - Raster chapter</ulink>. Potete <ulink url=\"http://www.postgis.us/page_buy_book\">acquistare</ulink> PostGIS in Action da Manning in versione cartacea (con sconti significativi per grossi quantitativi) oppore in versione E-book. Potete anche acquistare il libro da Amazon e da altri distributori. Tutte le copie cartacee contengono un buono per scaricare la versione E-book."
#. Tag: para
#: faq_raster.xml:30
#, no-c-format
msgid ""
-"Here is a review from a PostGIS Raster user <ulink url=\"http://"
-"fuzzytolerance.info/code/postgis-raster-ftw/\">PostGIS raster applied to "
-"land classification urban forestry</ulink>"
-msgstr ""
+"Here is a review from a PostGIS Raster user <ulink "
+"url=\"http://fuzzytolerance.info/code/postgis-raster-ftw/\">PostGIS raster "
+"applied to land classification urban forestry</ulink>"
+msgstr "Qui trovi una rassegna da parte di un utente di PostGIS Raster per <ulink url=\"http://fuzzytolerance.info/code/postgis-raster-ftw/\">applicazioni di classificazione del suolo nelle zone verdi urbane</ulink>."
#. Tag: para
#: faq_raster.xml:37
#, no-c-format
msgid "How do I install Raster support in my PostGIS database?"
-msgstr ""
+msgstr "Come installo il supporto Raster nel mio database PostGIS?"
#. Tag: para
#: faq_raster.xml:41
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 ""
+msgstr "Il modo più semplice è scaricare la versione binaria di PostGIS e della parte Raster, che sono attualmente disponibili per Windows e per le ultime versioni di Max OSX, partendo da una versione funzionante di PostGIS 2.0.0 o versioni superiori, con PostgreSQL 8.4, 9.0, o 9.1. Nota che in PostGIS 2.0 la parte Raster è completamente integrata, per cui dovrebbe essere compilata quando compilate PostGIS."
#. Tag: para
#: faq_raster.xml:43
"<ulink url=\"http://gis4free.wordpress.com/2011/03/10/how-to-install-and-"
"configure-postgis-raster-on-windows/\">How to Install and Configure PostGIS "
"raster on windows</ulink>"
-msgstr ""
+msgstr "Le istruzioni per installare ed eseguire il programma sotto Windows sono disponibili alla pagina <ulink url=\"http://gis4free.wordpress.com/2011/03/10/how-to-install-and-configure-postgis-raster-on-windows/\">How to Install and Configure PostGIS raster on windows</ulink>"
#. Tag: para
#: faq_raster.xml:44
#, no-c-format
msgid ""
-"If you are on windows, you can compile yourself, or use the <ulink url="
-"\"http://www.postgis.org/download/windows/experimental.php#wktraster\">pre-"
-"compiled PostGIS Raster windows binaries</ulink>. If you are on Mac OSX "
-"Leopard or Snow Leopard, there are binaries available at <ulink url=\"http://"
-"www.kyngchaos.com/software/postgres\">Kyng Chaos Mac OSX PostgreSQL/GIS "
-"binaries</ulink>."
-msgstr ""
+"If you are on windows, you can compile yourself, or use the <ulink "
+"url=\"http://www.postgis.org/download/windows/experimental.php#wktraster"
+"\">pre-compiled PostGIS Raster windows binaries</ulink>. If you are on Mac "
+"OSX Leopard or Snow Leopard, there are binaries available at <ulink "
+"url=\"http://www.kyngchaos.com/software/postgres\">Kyng Chaos Mac OSX "
+"PostgreSQL/GIS binaries</ulink>."
+msgstr "Su Windows, puoi compilare il programma da solo, oppure usare i <ulink url=\"http://www.postgis.org/download/windows/experimental.php#wktraster\">binari precompilati per Windows di PostGIS Raster</ulink>. Se sei su Mac OSX Leopard o Snow Leopard, i binari sono disponibili all'indirizzo di <ulink url=\"http://www.kyngchaos.com/software/postgres\">Kyng Chaos Mac OSX PostgreSQL/GIS</ulink>."
#. Tag: para
#: faq_raster.xml:50
"Then to enable raster support in your database, run the rtpostgis.sql file "
"in your database. To upgrade an existing install use "
"rtpostgis_upgrade_minor..sql instead of rtpostgis.sql"
-msgstr ""
+msgstr "Poi per abilitare il supporto raster nel tuo database, esegui il file rtpostgis.sql nel tuo database. Per aggiornare un'installazione esistente, utilizza rtpostgis_upgrade_minor..sql anziché rtpostgis.sql"
#. Tag: para
#: faq_raster.xml:51
msgid ""
"For other platforms, you generally need to compile yourself. Dependencies "
"are PostGIS and GDAL. For more details about compiling from source, please "
-"refer to <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/"
-"Documentation01#a2.3-CompilingandInstallingfromSources\">Installing PostGIS "
-"Raster from source (in prior versions of PostGIS)</ulink>"
-msgstr ""
+"refer to <ulink "
+"url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/Documentation01#a2.3-CompilingandInstallingfromSources\">Installing"
+" PostGIS Raster from source (in prior versions of PostGIS)</ulink>"
+msgstr "Per le altre piattaforme, in genere dovrai eseguire la compilazione da solo. Ci sono dipendenze da PostGISe da GDAL. Per ulteriori dettagli sulla compilazione da sorgente, vedi <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/Documentation01#a2.3-CompilingandInstallingfromSources\">Installing PostGIS Raster from source (in prior versions of PostGIS)</ulink>"
#. Tag: para
#: faq_raster.xml:57
#, no-c-format
msgid ""
-"I get error could not load library \"C:/Program Files/PostgreSQL/8.4/lib/"
-"rtpostgis.dll\": The specified module could not be found. or could not load "
-"library on Linux when trying to run rtpostgis.sql"
-msgstr ""
+"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 "Ottengo l'errore 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"
#. Tag: para
#: faq_raster.xml:62
#, no-c-format
msgid ""
"rtpostgis.so/dll is built with dependency on libgdal.dll/so. Make sure for "
-"Windows you have libgdal-1.dll in the bin folder of your PostgreSQL install. "
-"For Linux libgdal has to be in your path or bin folder."
-msgstr ""
+"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 "rtpostgis.so/dll is viene compilato con la dipendenza da libgdal.dll/so. Assicurati su Windows di avere libgdal-1.dll nella cartellabin folder della tua installazione PostgreSQL. Per Linux, libgdal deve essere nel tuo path o nella cartella bin."
#. Tag: para
#: faq_raster.xml:64
#, no-c-format
msgid ""
"You may also run into different errors if you don't have PostGIS installed "
-"in your database. Make sure to install PostGIS first in your database before "
-"trying to install the raster support."
-msgstr ""
+"in your database. Make sure to install PostGIS first in your database before"
+" trying to install the raster support."
+msgstr "Potresti anche riscontrare errori diversi se non hai PostGIS installato nel tuo database. Assicurati di installare PostGIS prima di provare a installare il supporto raster."
#. Tag: para
#: faq_raster.xml:71
#, no-c-format
msgid "How do I load Raster data into PostGIS?"
-msgstr ""
+msgstr "Come carico i dati raster in PostGIS?"
#. Tag: para
#: faq_raster.xml:75
#, no-c-format
msgid ""
-"The latest version of PostGIS comes packaged with a <varname>raster2pgsql</"
-"varname> raster loader executable capable of loading many kinds of rasters "
-"and also generating lower resolution overviews without any additional "
-"software. Please refer to <xref linkend=\"RT_Raster_Loader\"/> for more "
-"details. Pre-2.0 versions came with a <varname>raster2pgsql.py</varname> "
-"that required python with numpy and GDAL. This is no longer needed."
-msgstr ""
+"The latest version of PostGIS comes packaged with a "
+"<varname>raster2pgsql</varname> raster loader executable capable of loading "
+"many kinds of rasters and also generating lower resolution overviews without"
+" any additional software. Please refer to <xref "
+"linkend=\"RT_Raster_Loader\"/> for more details. Pre-2.0 versions came with "
+"a <varname>raster2pgsql.py</varname> that required python with numpy and "
+"GDAL. This is no longer needed."
+msgstr "La più recente versione di PostGIS è corredata dall'eseguibile <varname>raster2pgsql</varname> per il caricamento di diversi tipi di raster e anche per generare quadri d'insieme senza software aggiuntivo. Ti rimandiamo a <xref linkend=\"RT_Raster_Loader\"/> per ulteriori dettagli. Le versioni precedenti alla 2.0 avevano un programma <varname>raster2pgsql.py</varname> che richiedeva python, numpy e GDAL. Questo programma non è più necessario."
#. Tag: para
#: faq_raster.xml:81
#, no-c-format
msgid "What kind of raster file formats can I load into my database?"
-msgstr ""
+msgstr "Che tipo di formati raster posso caricare nel mio database?"
#. Tag: para
#: faq_raster.xml:85
#, no-c-format
msgid ""
"Any that your GDAL library supports. GDAL supported formats are documented "
-"<ulink url=\"http://www.gdal.org/formats_list.html\">GDAL File Formats</"
-"ulink>."
-msgstr ""
+"<ulink url=\"http://www.gdal.org/formats_list.html\">GDAL File "
+"Formats</ulink>."
+msgstr "Qualsiasi formato supportato dalla tua libreria GDAL. I formati supportati da GDAL sono <ulink url=\"http://www.gdal.org/formats_list.html\">documentati</ulink>."
#. Tag: para
#: faq_raster.xml:86
#, no-c-format
msgid ""
-"Your particular GDAL install may not support all formats. To verify the ones "
-"supported by your particular GDAL install, you can use"
-msgstr ""
+"Your particular GDAL install may not support all formats. To verify the ones"
+" supported by your particular GDAL install, you can use"
+msgstr "La tua particolare versione di GDAL potrebbe non supportare tutti i formati. Per verificare di preciso, puoi usare"
#. Tag: programlisting
#: faq_raster.xml:87
#, no-c-format
msgid "raster2pgsql -G"
-msgstr ""
+msgstr "raster2pgsql -G"
#. Tag: para
#: faq_raster.xml:93
#, no-c-format
msgid "Can I export my PostGIS raster data to other raster formats?"
-msgstr ""
+msgstr "Posso esportare i miei dati raster PostGIS ad altri formati raster?"
#. Tag: para
#: faq_raster.xml:97
#, no-c-format
msgid "<para>Yes</para>"
-msgstr ""
+msgstr "<para>Sì</para>"
#. Tag: para
#: faq_raster.xml:98
#, no-c-format
msgid ""
-"GDAL 1.7+ has a PostGIS raster driver, but is only compiled in if you choose "
-"to compile with PostgreSQL support."
-msgstr ""
+"GDAL 1.7+ has a PostGIS raster driver, but is only compiled in if you choose"
+" to compile with PostgreSQL support."
+msgstr "Dalla versione 1.7 in su, GDAL ha un driver per PostGIS Raster, ma viene compilato solo se scegli la compilazione con supporto PostgreSQL."
#. Tag: para
#: faq_raster.xml:99
msgid ""
"The driver currently doesn't support irregularly blocked rasters, although "
"you can store irregularly blocked rasters in PostGIS raster data type."
-msgstr ""
+msgstr "Al momento il driver non supporta i raster a blocchi irregolari, sebbene sia possibile memorizzare blocchi irregolari nel tipo dati PostGIS raster."
#. Tag: para
#: faq_raster.xml:101
msgid ""
"If you are compiling from source, you need to include in your configure "
"<programlisting>--with-pg=path/to/pg_config</programlisting> to enable the "
-"driver. Refer to <ulink url=\"http://trac.osgeo.org/gdal/wiki/BuildHints"
-"\">GDAL Build Hints</ulink> for tips on building GDAL against in various OS "
-"platforms."
-msgstr ""
+"driver. Refer to <ulink "
+"url=\"http://trac.osgeo.org/gdal/wiki/BuildHints\">GDAL Build Hints</ulink> "
+"for tips on building GDAL against in various OS platforms."
+msgstr "Se stai compilando il programma a partire dal sorgente, devi includere nel sorgente l'opzione <programlisting>--with-pg=path/to/pg_config</programlisting> per abilitare il driver. Ti rimandiamo alla pagina <ulink url=\"http://trac.osgeo.org/gdal/wiki/BuildHints\">GDAL Build Hints</ulink> per suggerimenti sulla compilazione di GDAL su divrse piattaforme."
#. Tag: para
#: faq_raster.xml:106
msgid ""
"If your version of GDAL is compiled with the PostGIS Raster driver you "
"should see PostGIS Raster in list when you do"
-msgstr ""
+msgstr "Se la tua versione di GDAL è compilata con il driver PostGIS Raster, dovresti trovare PostGIS Raster nella lista quando esegui"
#. Tag: programlisting
#: faq_raster.xml:108
#, no-c-format
msgid "gdalinfo --formats"
-msgstr ""
+msgstr "gdalinfo --formats"
#. Tag: para
#: faq_raster.xml:110
#, no-c-format
msgid "To get a summary about your raster via GDAL use gdalinfo:"
-msgstr ""
+msgstr "Per ottenere informazioni riassuntive sul tuo raster tramite GDAL, utilizza gdalinfo:"
#. Tag: programlisting
#: faq_raster.xml:111
msgid ""
"gdalinfo \"PG:host=localhost port=5432 dbname='mygisdb' user='postgres' "
"password='whatever' schema='someschema' table=sometable\""
-msgstr ""
+msgstr "gdalinfo \"PG:host=localhost port=5432 dbname='mygisdb' user='postgres' password='whatever' schema='someschema' table=sometable\""
#. Tag: para
#: faq_raster.xml:114
msgid ""
"To export data to other raster formats, use gdal_translate the below will "
"export all data from a table to a PNG file at 10% size."
-msgstr ""
+msgstr "Per esportare dati verso altri formati raster, utilizza gdal_translate. L'esempio sotto esporterà tutti i dati da una tabella a un file PNG col 10% della dimensione."
#. Tag: para
#: faq_raster.xml:116
msgid ""
"Depending on your pixel band types, some translations may not work if the "
"export format does not support that Pixel type. For example floating point "
-"band types and 32 bit unsigned ints will not translate easily to JPG or some "
-"others."
-msgstr ""
+"band types and 32 bit unsigned ints will not translate easily to JPG or some"
+" others."
+msgstr "A seconda dei tipi di banda dei pixel, alcune conversioni non funzioneranno, se il formato di esportazione non supprta un dato tipo di pixel. Per esempio, i tipi di banda a virgola mobile, o gli interi senza segno a 32 bit non si convertiranno bene in JPEG."
#. Tag: para
#: faq_raster.xml:119
#, no-c-format
msgid "Here is an example simple translation"
-msgstr ""
+msgstr "Ecco un esempio di una semplice conversione"
#. Tag: programlisting
#: faq_raster.xml:120
#, no-c-format
msgid ""
-"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' "
-"user='postgres' password=whatever' schema='someschema' table=sometable\" C:"
-"\\somefile.png"
-msgstr ""
+"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb'"
+" user='postgres' password=whatever' schema='someschema' table=sometable\" "
+"C:\\somefile.png"
+msgstr "gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' user='postgres' password=whatever' schema='someschema' table=sometable\" C:\\somefile.png"
#. Tag: para
#: faq_raster.xml:121
msgid ""
"You can also use SQL where clauses in your export using the where=... in "
"your driver connection string. Below are some using a where clause"
-msgstr ""
+msgstr "Puoi anche utilizzare la clausola SQL WHERE nell'esportazione, riportando il testo where=.... nella stringa di collegamento del driver. Sotto si riportano alcuni esempi che utilizzano la clausola where"
#. Tag: programlisting
#: faq_raster.xml:123
#, no-c-format
msgid ""
-"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' "
-"user='postgres' password=whatever' schema='someschema' table=sometable where="
-"\"owner='jimmy'\" \" C:\\somefile.png"
-msgstr ""
+"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb'"
+" user='postgres' password=whatever' schema='someschema' table=sometable "
+"where=\"owner='jimmy'\" \" C:\\somefile.png"
+msgstr "gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' user='postgres' password=whatever' schema='someschema' table=sometable where=\"owner='jimmy'\" \" C:\\somefile.png"
#. Tag: programlisting
#: faq_raster.xml:124
#, no-c-format
msgid ""
-"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' "
-"user='postgres' password=whatever' schema='someschema' table=sometable "
+"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb'"
+" user='postgres' password=whatever' schema='someschema' table=sometable "
"where='ST_Intersects(rast, ST_SetSRID(ST_Point(-71.032,42.3793),4326) )' \" "
"C:\\intersectregion.png"
-msgstr ""
+msgstr "gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' user='postgres' password=whatever' schema='someschema' table=sometable where='ST_Intersects(rast, ST_SetSRID(ST_Point(-71.032,42.3793),4326) )' \" C:\\intersectregion.png"
#. Tag: para
#: faq_raster.xml:125
#, no-c-format
msgid ""
-"To see more examples and syntax refer to <ulink url=\"http://trac.osgeo.org/"
-"gdal/wiki/frmts_wtkraster.html#a3.2-Readingrasterdatafromthedatabase"
-"\">Reading Raster Data of PostGIS Raster section</ulink>"
-msgstr ""
+"To see more examples and syntax refer to <ulink "
+"url=\"http://trac.osgeo.org/gdal/wiki/frmts_wtkraster.html#a3.2-Readingrasterdatafromthedatabase\">Reading"
+" Raster Data of PostGIS Raster section</ulink>"
+msgstr "Per vedere altri esempi e sintassi, si rimanda al paragrafo <ulink url=\"http://trac.osgeo.org/gdal/wiki/frmts_wtkraster.html#a3.2-Readingrasterdatafromthedatabase\">Leggere dati raster da un raster PostGIS</ulink>"
#. Tag: para
#: faq_raster.xml:130
msgid ""
"Are their binaries of GDAL available already compiled with PostGIS Raster "
"suppport?"
-msgstr ""
+msgstr "I binari di GDAL sono già disponibili con il supporto raster PostGIS?"
#. Tag: para
#: faq_raster.xml:132
#, no-c-format
msgid ""
-"Yes. Check out the page <ulink url=\"http://trac.osgeo.org/gdal/wiki/"
-"DownloadingGdalBinaries\">GDAL Binaries</ulink> page. Any compiled with "
-"PostgreSQL support should have PostGIS Raster in them."
-msgstr ""
+"Yes. Check out the page <ulink "
+"url=\"http://trac.osgeo.org/gdal/wiki/DownloadingGdalBinaries\">GDAL "
+"Binaries</ulink> page. Any compiled with PostgreSQL support should have "
+"PostGIS Raster in them."
+msgstr "Sì. Controlla la pagina <ulink url=\"http://trac.osgeo.org/gdal/wiki/DownloadingGdalBinaries\">GDAL Binaries</ulink>. Qualsiasi versione compilata con l'opzione di supporto per PostgreSQL dovrebbe avere il supporto per i raster PostGIS."
#. Tag: para
#: faq_raster.xml:134
#, no-c-format
msgid ""
-"We know for sure the following windows binaries have PostGIS Raster built in."
-msgstr ""
+"We know for sure the following windows binaries have PostGIS Raster built "
+"in."
+msgstr "Sappiamo per certo che i seguenti binari Windows hanno il supporto raster PostGIS."
#. Tag: para
#: faq_raster.xml:135
msgid ""
"<ulink url=\"http://fwtools.maptools.org/\">FWTools latest stable version "
"for Windows is compiled with Raster support</ulink>."
-msgstr ""
+msgstr "La versione più recente e stabile di <ulink url=\"http://fwtools.maptools.org/\">FWTools per Windows</ulink> è compilata con il supporto raster."
#. Tag: para
#: faq_raster.xml:136
"PostGIS Raster is undergoing many changes. If you want to get the latest "
"nightly build for Windows -- then check out the Tamas Szekeres nightly "
"builds built with Visual Studio which contain GDAL trunk, Python Bindings "
-"and MapServer executables and PostGIS Raster driver built-in. Just click the "
-"SDK bat and run your commands from there. <ulink url=\"http://vbkto.dyndns."
-"org/sdk/\">http://vbkto.dyndns.org/sdk/</ulink>. Also available are VS "
-"project files."
+"and MapServer executables and PostGIS Raster driver built-in. Just click the"
+" SDK bat and run your commands from there. <ulink "
+"url=\"http://vbkto.dyndns.org/sdk/\">http://vbkto.dyndns.org/sdk/</ulink>. "
+"Also available are VS project files."
msgstr ""
#. Tag: para
#: faq_raster.xml:145
#, no-c-format
msgid "What tools can I use to view PostGIS raster data?"
-msgstr ""
+msgstr "Quali strumenti posso usare per visualizzare i dati raster PostGIS?"
#. Tag: para
#: faq_raster.xml:149
"You can use MapServer compiled with GDAL 1.7+ and PostGIS Raster driver "
"support to view Raster data. QuantumGIS (QGIS) now supports viewing of "
"PostGIS Raster if you have PostGIS raster driver installed."
-msgstr ""
+msgstr "Puoi utilizzare Mapserver compilato con GDAL 1.7 o versioni superiori e con il supporto del driver raster PostGIS per vedere i dati raster. Quantum GIS (QGIS) inoltre supporta la visualizzazione dei raster PostGIS se hai il driver installato."
#. Tag: para
#: faq_raster.xml:151
msgid ""
"In theory any tool that renders data using GDAL can support PostGIS raster "
"data or support it with fairly minimal effort. Again for Windows, Tamas' "
-"binaries <ulink url=\"http://vbkto.dyndns.org/sdk/\">http://vbkto.dyndns.org/"
-"sdk/</ulink> are a good choice if you don't want the hassle of having to "
-"setup to compile your own."
-msgstr ""
+"binaries <ulink "
+"url=\"http://vbkto.dyndns.org/sdk/\">http://vbkto.dyndns.org/sdk/</ulink> "
+"are a good choice if you don't want the hassle of having to setup to compile"
+" your own."
+msgstr "In teoria qualsiasi strumento che utilizzi GDAL per la restituzione dei dati può supportare i raster PostGIS direttamente o con un minimo sforzo. Sempre per Windows, I binari di Tama <ulink url=\"http://vbkto.dyndns.org/sdk/\">http://vbkto.dyndns.org/sdk/</ulink> sono una buona scelta se non volete prendervi la briga di eseguire la compilazione in proprio."
#. Tag: para
#: faq_raster.xml:158
#, no-c-format
msgid "How can I add a PostGIS raster layer to my MapServer map?"
-msgstr ""
+msgstr "Come posso aggiungere uno strato raster PostGIS in una mappa di MapServer?"
#. Tag: para
#: faq_raster.xml:162
#, no-c-format
msgid ""
-"First you need GDAL 1.7 or higher compiled with PostGIS raster support. GDAL "
-"1.8 or above is preferred since many issues have been fixed in 1.8 and more "
-"PostGIS raster issues fixed in trunk version."
-msgstr ""
+"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 "Anzitutto ti serve GDAL 1.7 o superiore compilato con il supporto per raster PostGIS. E consigliata la versione 1.8 o superiore, dato che quest'ultima risolve numerosi problemi, e altri problemi con i raster PostGIS sono risolti nella versione trunk."
#. Tag: para
#: faq_raster.xml:164
#, no-c-format
msgid ""
-"You can much like you can with any other raster. Refer to <ulink url="
-"\"http://mapserver.org/input/raster.html\">MapServer Raster processing "
+"You can much like you can with any other raster. Refer to <ulink "
+"url=\"http://mapserver.org/input/raster.html\">MapServer Raster processing "
"options</ulink> for list of various processing functions you can use with "
"MapServer raster layers."
msgstr ""
msgid ""
"Below is an example of how you would define a PostGIS raster layer in "
"MapServer."
-msgstr ""
+msgstr "Sotto trovi un esempio di come definire uno strato raster PostGIS in MapServer."
#. Tag: para
#: faq_raster.xml:170
msgid ""
"The mode=2 is required for tiled rasters and was added in PostGIS 2.0 and "
"GDAL 1.8 drivers. This does not exist in GDAL 1.7 drivers."
-msgstr ""
+msgstr "L'opzione mode=2 serve per i raster con tile ed è stata aggiunta in PostGIS 2.0 con il driver GDAL 1.8. Non esiste nei driver GDAL 1.7."
#. Tag: programlisting
#: faq_raster.xml:171
" 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"
" COLOR 0 255 0\n"
" END\n"
"END"
-msgstr ""
+msgstr "-- visualizzare un raster con le opzioni standard\nLAYER\n NAME coolwktraster\n TYPE raster\n STATUS ON\n DATA \"PG:host=localhost port=5432 dbname='somedb' user='someuser' password='whatever' \n schema='someschema' table='cooltable' mode='2'\" \n PROCESSING \"NODATA=0\"\n PROCESSING \"SCALE=AUTO\"\n #... other standard raster processing functions here\n #... classes are optional but useful for 1 band data\n CLASS\n NAME \"boring\"\n EXPRESSION ([pixel] < 20)\n COLOR 250 250 250\n END\n CLASS\n NAME \"mildly interesting\"\n EXPRESSION ([pixel] > 20 AND [pixel] < 1000)\n COLOR 255 0 0\n END\n CLASS\n NAME \"very interesting\"\n EXPRESSION ([pixel] >= 1000)\n COLOR 0 255 0\n END\nEND"
#. Tag: programlisting
#: faq_raster.xml:173
" 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"
"END"
-msgstr ""
+msgstr "-- visualizzare un raster con le opzioni standard e la clausola where\nLAYER\n NAME soil_survey2009\n TYPE raster\n STATUS ON\n DATA \"PG:host=localhost port=5432 dbname='somedb' user='someuser' password='whatever' \n schema='someschema' table='cooltable' where='survey_year=2009' mode='2'\" \n PROCESSING \"NODATA=0\"\n #... other standard raster processing functions here\n #... classes are optional but useful for 1 band data\nEND"
#. Tag: para
#: faq_raster.xml:181
#, no-c-format
msgid "What functions can I currently use with my raster data?"
-msgstr ""
+msgstr "Quali funzioni posso attualmente utilizzare con i dati raster?"
#. Tag: para
#: faq_raster.xml:185
msgid ""
"Refer to the list of <xref linkend=\"RT_reference\"/>. There are more, but "
"this is still a work in progress."
-msgstr ""
+msgstr "Ti rimandiamo alla lista <xref linkend=\"RT_reference\"/>. Ce ne sono anche altre, ma si tratta di funzioni in via di sviluppo."
#. Tag: para
#: faq_raster.xml:187
#, no-c-format
msgid ""
-"Refer to the <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/"
-"PlanningAndFunding\">PostGIS Raster roadmap page</ulink> for details of what "
-"you can expect in the future."
-msgstr ""
+"Refer to the <ulink "
+"url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/PlanningAndFunding\">PostGIS"
+" Raster roadmap page</ulink> for details of what you can expect in the "
+"future."
+msgstr "Ti rimandiamo alla pagina <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/PlanningAndFunding\">PostGIS Raster roadmap page</ulink> per i dettagli sugli sviluppi attesti in futuro."
#. Tag: para
#: faq_raster.xml:195
msgid ""
"I am getting error ERROR: function st_intersects(raster, unknown) is not "
"unique or st_union(geometry,text) is not unique. How do I fix?"
-msgstr ""
+msgstr "Ottengo un errore ERROR: function st_intersects(raster, unknown) is not unique or st_union(geometry,text) is not unique. Come lo aggiusto?"
#. Tag: para
#: faq_raster.xml:199
"The function is not unique error happens if one of your arguments is a "
"textual representation of a geometry instead of a geometry. In these cases, "
"PostgreSQL marks the textual representation as an unknown type, which means "
-"it can fall into the st_intersects(raster, geometry) or st_intersects(raster,"
-"raster) thus resulting in a non-unique case since both functions can in "
-"theory support your request. To prevent this, you need to cast the geometry "
-"to a geometry."
-msgstr ""
+"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 "L'errore \"function is not unique\" si ha quando uno dei vostri argomenti e la rappresentazione testuale di una geometria, anziché una geometria vera e propria. In questi casi, PostgreSQL segna la rappresentazione testuale come tipo sconosciuto, che potrebbe essere applicato sia a st_intersects(raster, geometry) che a st_intersects(raster,raster), portando così a una situazione non univoca, dato che entrambe le funzioni supportano la tua richiesta. Al fine di evitare questa situazione, devi eseguire il cast della geometria in modo che sia effettivamente interpretata come geometria."
#. Tag: para
#: faq_raster.xml:200
#, no-c-format
msgid "For example if your code looks like this:"
-msgstr ""
+msgstr "Per esempio, se il tuo codice è tipo:"
#. Tag: programlisting
#: faq_raster.xml:201
"SELECT rast\n"
" FROM my_raster\n"
" WHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)');"
-msgstr ""
+msgstr "SELECT rast\n FROM my_raster\n WHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)');"
#. Tag: para
#: faq_raster.xml:202
#, no-c-format
msgid ""
-"Cast the textual geometry representation to a geometry by changing your code "
-"to this:"
-msgstr ""
+"Cast the textual geometry representation to a geometry by changing your code"
+" to this:"
+msgstr "Dei eseguire il cast della geometria come testo a una geometria vera e propria in questo modo:"
#. Tag: programlisting
#: faq_raster.xml:203
"SELECT rast\n"
" FROM my_raster\n"
" WHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)'::geometry);"
-msgstr ""
+msgstr "SELECT rast\n FROM my_raster\n WHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)'::geometry);"
#. Tag: para
#: faq_raster.xml:211
msgid ""
"How is PostGIS Raster different from Oracle GeoRaster (SDO_GEORASTER) and "
"SDO_RASTER types?"
-msgstr ""
+msgstr "Quali sono le differenze tra i raster di PostGIS, i GeoRaster di Oracle (SDO_GEORASTER) e i tipi SDO_RASTER?"
#. Tag: para
#: faq_raster.xml:215
#, no-c-format
msgid ""
"For a more extensive discussion on this topic, check out Jorge Arévalo "
-"<ulink url=\"http://gis4free.wordpress.com/2010/07/19/oracle-georaster-part-"
-"i/\">Oracle GeoRaster and PostGIS Raster: First impressions </ulink>"
-msgstr ""
+"<ulink url=\"http://gis4free.wordpress.com/2010/07/19/oracle-georaster-"
+"part-i/\">Oracle GeoRaster and PostGIS Raster: First impressions </ulink>"
+msgstr "Per una discussione dettagliata su questo argomento, dai un'occhiata all'articolo di Jorge Arévalo <ulink url=\"http://gis4free.wordpress.com/2010/07/19/oracle-georaster-part-i/\">Oracle GeoRaster and PostGIS Raster: First impressions </ulink>"
#. Tag: para
#: faq_raster.xml:216
#, 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
"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
# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# pibinko <pibinko@gmail.com>, 2013
+# Stefano Costa <steko@iosa.it>, 2013
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2013-11-27 09:02+0000\n"
+"Last-Translator: pibinko <pibinko@gmail.com>\n"
+"Language-Team: Italian (Italy) (http://www.transifex.com/projects/p/postgis-1/language/it_IT/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: it_IT\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. Tag: title
#: introduction.xml:3
#, no-c-format
msgid "Introduction"
-msgstr ""
+msgstr "Introduzione"
#. Tag: para
#: introduction.xml:5
"including full OpenGIS support, advanced topological constructs (coverages, "
"surfaces, networks), desktop user interface tools for viewing and editing "
"GIS data, and web-based access tools."
-msgstr ""
+msgstr "PostGIS è stato sviluppato da Refractions Research Inc come progetto di ricerca sui database spaziali. Refractions è una azienda nel settore GIS e database con sede a Victoria, British Columbia, in Canada, specializzata nell'integrazione di dati e nello sviluppo di software su misura. Abbiamo in programma di supportare e sviluppare PostGIS per gestire una gamma di funzionalità GIS importanti, tra cui un completo supporto OpenGIS, operazioni topologiche avanzate (estensioni, superfici, reti), strumenti desktop per la visualizzazione e l'editing di dati GIS, e strumenti web."
#. Tag: para
#: introduction.xml:15
"continually improved and funded by many FOSS4G Developers as well as "
"corporations all over the world that gain great benefit from its "
"functionality and versatility."
-msgstr ""
+msgstr "PostGIS è in fase di incubazione come progetto della OSGeo Foundation. PostGIS viene continuamente migliorato e sostenuto economicamente da molti sviluppatori FOSS4G e da aziende di tutto il mondo che ricavano grandi benefici dalle sue funzionalità e versatilità."
#. Tag: title
#: introduction.xml:21
#, no-c-format
msgid "Project Steering Committee"
-msgstr ""
+msgstr "Comitato di Coordinamento del Progetto"
#. Tag: para
#: introduction.xml:22
"and approves patches from the general PostGIS community and votes on "
"miscellaneous issues involving PostGIS such as developer commit access, new "
"PSC members or significant API changes."
-msgstr ""
+msgstr "Il comitato di coordinamento del progetto (in inglese Project Steering Commitee o PSC) coordina la direzione generale, i cicli di rilascio, la documentazione e le iniziative di divulgazione del progetto PostGIS. Inoltre il comitato fornisce supporto agli utenti, accetta e approva patch dalla comunità generale PostGIS e vota su questioni varie che coinvolgono PostGIS come l'accesso di commit per gli sviluppatori, i nuovi membri del comitato e modifiche della API."
#. Tag: term
#: introduction.xml:31
#, no-c-format
msgid "Mark Cave-Ayland"
-msgstr ""
+msgstr "Mark Cave-Ayland"
#. Tag: para
#: introduction.xml:33
"Coordinates bug fixing and maintenance effort, alignment of PostGIS with "
"PostgreSQL releases, spatial index selectivity and binding, loader/dumper, "
"and Shapefile GUI Loader, integration of new and new function enhancements."
-msgstr ""
+msgstr "Coordina la soluzione dei bug e le iniziative di manutenzione, l'allineamento di PostGIS con i rilasci di PostgreSQL"
#. Tag: term
#: introduction.xml:40
#, no-c-format
msgid "Regina Obe"
-msgstr ""
+msgstr "Regina Obe"
#. Tag: para
#: introduction.xml:42
#, no-c-format
msgid ""
"Buildbot Maintenance, windows production and experimental builds, "
-"Documentation, general user support on PostGIS newsgroup, X3D support, Tiger "
-"Geocoder Support, management functions, and smoke testing new functionality "
-"or major code changes."
-msgstr ""
+"Documentation, general user support on PostGIS newsgroup, X3D support, Tiger"
+" Geocoder Support, management functions, and smoke testing new functionality"
+" or major code changes."
+msgstr "Manutenzione Buildbot, build sperimentali e di produzione per Windows, documentazione, supporto per gli utenti nel newsgroup PostGIS, supporto X3D, Supporto per il geocodeo Tiger, funzioni di gestione, test di integrità funzionale per nuove funzioni o variazioni sostanziali del codice."
#. Tag: term
#: introduction.xml:49
#, no-c-format
msgid "Paul Ramsey (Chair)"
-msgstr ""
+msgstr "Paul Ramsey (Coordinatore)"
#. Tag: para
#: introduction.xml:51
"index), underlying geometry internal structures, GEOS functionality "
"integration and alignment with GEOS releases, loader/dumper, and Shapefile "
"GUI loader."
-msgstr ""
+msgstr "Cofondatore del progetto PostGIS. Correzione dei bug, supporto alla componente geografica, supporto per gli indici geografici e geometrici (2D, 3D, nD e qualsiasi altra cosa legata agli indici spaziali), strutture interne per la geometria, integrazione delle funzionalità GEOS e allineamento con le nuove versioni GEOS releases, loader/dumper, e interfaccia grafica per il loader Shapefile."
#. Tag: term
#: introduction.xml:57
#, no-c-format
msgid "Sandro Santilli"
-msgstr ""
+msgstr "Sandro Santilli"
#. Tag: para
#: introduction.xml:60
#, no-c-format
msgid ""
"Bug fixes and maintenance and integration of new GEOS functionality and "
-"alignment with GEOS releases, Topology support, and Raster framework and low "
-"level api functions."
-msgstr ""
+"alignment with GEOS releases, Topology support, and Raster framework and low"
+" level api functions."
+msgstr "Correzione di bug, manutenzione e integrazione delle nuove funzioalità GEOS, allineamento con le versioni di GEOS, supporto topologico, framework Raster e funzioni API di basso livello."
#. Tag: title
#: introduction.xml:67
#, no-c-format
msgid "Contributors Past and Present"
-msgstr ""
+msgstr "Collaboratori passati e presenti"
#. Tag: term
#: introduction.xml:71
#, no-c-format
msgid "Chris Hodgson"
-msgstr ""
+msgstr "Chris Hodgson"
#. Tag: para
#: introduction.xml:73
msgid ""
"Prior PSC Member. General development, site and buildbot maintenance, OSGeo "
"incubation management"
-msgstr ""
+msgstr "Ex-membro del comitato di coordinamento. Sviluppo generale, manutenzione del sito e del buildbot, gestione dell'incubazione OSGeo"
#. Tag: term
#: introduction.xml:77
#, no-c-format
msgid "Kevin Neufeld"
-msgstr ""
+msgstr "Kevin Neufeld"
#. Tag: para
#: introduction.xml:79
"Prior PSC Member. Documentation and documentation support tools, advanced "
"user support on PostGIS newsgroup, and PostGIS maintenance function "
"enhancements."
-msgstr ""
+msgstr "Ex-membro del comitato di coordinamento. Documentazione e strumenti di supporto alla documentazione. Supporto avanzato per gli utenti nel newsgroup PostGIS, miglioramenti alle funzioni di manutenzione PostGIS."
#. Tag: term
#: introduction.xml:85
#, no-c-format
msgid "Dave Blasby"
-msgstr ""
+msgstr "Dave Blasby"
#. Tag: para
#: introduction.xml:88
msgid ""
"The original developer/Co-founder of PostGIS. Dave wrote the server side "
"objects, index bindings, and many of the server side analytical functions."
-msgstr ""
+msgstr "Lo sviluppatore iniziale e uno dei cofondatori di PostGIS. Dave ha scritto il codice per gli oggetti lato server, il binding degli indici e molte delle funzioni analitiche lato server."
#. Tag: term
#: introduction.xml:95
#, no-c-format
msgid "Jeff Lounsbury"
-msgstr ""
+msgstr "Jeff Lounsbury"
#. Tag: para
#: introduction.xml:97
msgid ""
"Original development of the Shape file loader/dumper. Current PostGIS "
"Project Owner representative."
-msgstr ""
+msgstr "Sviluppo iniziale del loader/dumper per gli Shapefile. Attualmente rappresentante di Project Owner di PostGIS."
#. Tag: term
#: introduction.xml:102
#, no-c-format
msgid "Olivier Courtin"
-msgstr ""
+msgstr "Olivier Courtin"
#. Tag: para
#: introduction.xml:104
#, no-c-format
-msgid "Input output XML (KML,GML)/GeoJSON functions, 3D support and bug fixes."
-msgstr ""
+msgid ""
+"Input output XML (KML,GML)/GeoJSON functions, 3D support and bug fixes."
+msgstr "Funzioni di input e ouput XML (KML,GML)/GeoJSON, supporto 3D e correzione di bug."
#. Tag: term
#: introduction.xml:109
#, no-c-format
msgid "Mark Leslie"
-msgstr ""
+msgstr "Mark Leslie"
#. Tag: para
#: introduction.xml:111
msgid ""
"Ongoing maintenance and development of core functions. Enhanced curve "
"support. Shapefile GUI loader."
-msgstr ""
+msgstr "Continuo sviluppo e manutenzione delle funzioni di base. Supporto avanzanto per le curve. Interfaccia grafica per il loader di Shapefile."
#. Tag: term
#: introduction.xml:116
#, no-c-format
msgid "Pierre Racine"
-msgstr ""
+msgstr "Pierre Racine"
#. Tag: para
#: introduction.xml:118
#, no-c-format
msgid "Raster overall architecture, prototyping, programming support"
-msgstr ""
+msgstr "Architettura complessiva raster, prototipazione, supporto alla programmazione"
#. Tag: term
#: introduction.xml:123
#, no-c-format
msgid "Nicklas Avén"
-msgstr ""
+msgstr "Nicklas Avén"
#. Tag: para
#: introduction.xml:126
msgid ""
"Distance function enhancements (including 3D distance and relationship "
"functions) and additions, Windows testing, and general user support"
-msgstr ""
+msgstr "Miglioramenti e aggiunte alla funzione di distanza (comprese le funzioni di distanza 3D e di relazione), test su Windows e supporto generale agli utenti"
#. Tag: term
#: introduction.xml:131
#, no-c-format
msgid "Jorge Arévalo"
-msgstr ""
+msgstr "Jorge Arévalo"
#. Tag: para
#: introduction.xml:134
#, no-c-format
msgid "Raster development, GDAL driver support, loader"
-msgstr ""
+msgstr "Sviluppo raster, supporto per il driver GDAL, loader"
#. Tag: term
#: introduction.xml:139
#, no-c-format
msgid "Bborie Park"
-msgstr ""
+msgstr "Bborie Park"
#. Tag: para
#: introduction.xml:141
#, no-c-format
msgid "Raster development, raster loader"
-msgstr ""
+msgstr "Sviluppo raster, loader raster"
#. Tag: term
#: introduction.xml:146
#, no-c-format
msgid "Mateusz Loskot"
-msgstr ""
+msgstr "Mateusz Loskot"
#. Tag: para
#: introduction.xml:148
#, no-c-format
msgid "Raster loader, low level raster api functions"
-msgstr ""
+msgstr "Loader raster, funzioni API raster a basso livello"
#. Tag: term
#: introduction.xml:153
#, no-c-format
msgid "David Zwarg"
-msgstr ""
+msgstr "David Zwarg"
#. Tag: para
#: introduction.xml:156
#, no-c-format
msgid "Raster development"
-msgstr ""
+msgstr "Sviluppo raster"
#. Tag: term
#: introduction.xml:161
#, no-c-format
msgid "Other contributors: Individuals"
-msgstr ""
+msgstr "Altri collaboratori: persone fisiche"
#. Tag: para
#: introduction.xml:164
"In alphabetical order: Alex Bodnaru, Alex Mayrhofer, Andrea Peri, Andreas "
"Forø Tollefsen, Andreas Neumann, Anne Ghisla, Barbara Phillipot, Ben Jubb, "
"Bernhard Reiter, Brian Hamlin, Bruce Rindahl, Bruno Wolff III, Bryce L. "
-"Nordgren, Carl Anderson, Charlie Savage, Dane Springmeyer, David Skea, David "
-"Techer, Eduin Carrillo, Even Rouault, Frank Warmerdam, George Silva, Gerald "
-"Fenoy, Gino Lucrezi, Guillaume Lelarge, IIDA Tetsushi, Ingvild Nystuen, Jeff "
-"Adams, Jose Carlos Martinez Llari, Kashif Rasul, Klaus Foerster, Kris Jurka, "
-"Leo Hsu, Loic Dachary, Luca S. Percich, Maria Arias de Reyna, Mark Sondheim, "
-"Markus Schaber, Maxime Guillaud, Maxime van Noppen, Michael Fuhr, Nikita "
-"Shulga, Norman Vine, Rafal Magda, Ralph Mason, Richard Greenwood, Silvio "
-"Grosso, Steffen Macke, Stephen Frost, Tom van Tilburg, Vincent Picavet"
-msgstr ""
+"Nordgren, Carl Anderson, Charlie Savage, Dane Springmeyer, David Skea, David"
+" Techer, Eduin Carrillo, Even Rouault, Frank Warmerdam, George Silva, Gerald"
+" Fenoy, Gino Lucrezi, Guillaume Lelarge, IIDA Tetsushi, Ingvild Nystuen, "
+"Jeff Adams, Jose Carlos Martinez Llari, Kashif Rasul, Klaus Foerster, Kris "
+"Jurka, Leo Hsu, Loic Dachary, Luca S. Percich, Maria Arias de Reyna, Mark "
+"Sondheim, Markus Schaber, Maxime Guillaud, Maxime van Noppen, Michael Fuhr, "
+"Nikita Shulga, Norman Vine, Rafal Magda, Ralph Mason, Richard Greenwood, "
+"Silvio Grosso, Steffen Macke, Stephen Frost, Tom van Tilburg, Vincent "
+"Picavet"
+msgstr "In ordine alfabetico: Alex Bodnaru, Alex Mayrhofer, Andrea Peri, Andreas Forø Tollefsen, Andreas Neumann, Anne Ghisla, Barbara Phillipot, Ben Jubb, Bernhard Reiter, Brian Hamlin, Bruce Rindahl, Bruno Wolff III, Bryce L. Nordgren, Carl Anderson, Charlie Savage, Dane Springmeyer, David Skea, David Techer, Eduin Carrillo, Even Rouault, Frank Warmerdam, George Silva, Gerald Fenoy, Gino Lucrezi, Guillaume Lelarge, IIDA Tetsushi, Ingvild Nystuen, Jeff Adams, Jose Carlos Martinez Llari, Kashif Rasul, Klaus Foerster, Kris Jurka, Leo Hsu, Loic Dachary, Luca S. Percich, Maria Arias de Reyna, Mark Sondheim, Markus Schaber, Maxime Guillaud, Maxime van Noppen, Michael Fuhr, Nikita Shulga, Norman Vine, Rafal Magda, Ralph Mason, Richard Greenwood, Silvio Grosso, Steffen Macke, Stephen Frost, Tom van Tilburg, Vincent Picavet"
#. Tag: term
#: introduction.xml:221
#, no-c-format
msgid "Other contributors: Corporate Sponsors"
-msgstr ""
+msgstr "Altre collaborazioni: sponsor aziendali"
#. Tag: para
#: introduction.xml:224
msgid ""
"These are corporate entities that have contributed developer time, hosting, "
"or direct monetary funding to the PostGIS project"
-msgstr ""
+msgstr "Queste sono realtà aziendali o altre istituzioni che hanno contribuito al progetto PostGIS sotto forma di tempo sviluppatore, hosting o finanziamento economico"
#. Tag: para
#: introduction.xml:225
"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, Norwegian Forest and Landscape "
+"Consulting Engineers, LisaSoft, Logical Tracking & Tracing International"
+" AG, Michigan Tech Research Institute, Norwegian Forest and Landscape "
"Institute, OpenGeo, OSGeo, Oslandia, Paragon Corporation, R3 GIS,, "
"Refractions Research, Regione Toscana-SIGTA, Safe Software, Sirius "
"Corporation plc, Stadt Uster, UC Davis Center for Vectorborne Diseases, "
-"University of Laval, U.S Department of State (HIU), Vizzuality, Zonar Systems"
-msgstr ""
+"University of Laval, U.S Department of State (HIU), Vizzuality, Zonar "
+"Systems"
+msgstr "In ordine alfabetico: Arrival 3D, Associazione Italiana per l'Informazione Geografica Libera (GFOSS.it), AusVet, Avencia, Azavea, Cadcorp, CampToCamp, City of Boston (DND), Clever Elephant Solutions, Cooperativa Alveo, Deimos Space, Faunalia, Geographic Data BC, Hunter Systems Group, Lidwala Consulting Engineers, LisaSoft, Logical Tracking & Tracing International AG, Michigan Tech Research Institute, Norwegian Forest and Landscape Institute, OpenGeo, OSGeo, Oslandia, Paragon Corporation, R3 GIS, Refractions Research, Regione Toscana-SIGTA, Safe Software, Sirius Corporation plc, Stadt Uster, UC Davis Center for Vectorborne Diseases, University of Laval, U.S Department of State (HIU), Vizzuality, Zonar Systems"
#. Tag: term
#: introduction.xml:265
#, no-c-format
msgid "Crowd Funding Campaigns"
-msgstr ""
+msgstr "Campagne di finanziamento diffuso"
#. Tag: para
#: introduction.xml:268
"specifically focused on a particular feature or set of features. Each "
"sponsor chips in a small fraction of the needed funding and with enough "
"people/organizations contributing, we have the funds to pay for the work "
-"that will help many. If you have an idea for a feature you think many others "
-"would be willing to co-fund, please post to the <ulink url=\"http://www."
-"postgis.org/mailman/listinfo/postgis-users\">PostGIS newsgroup</ulink> your "
-"thoughts and together we can make it happen."
-msgstr ""
+"that will help many. If you have an idea for a feature you think many others"
+" would be willing to co-fund, please post to the <ulink "
+"url=\"http://www.postgis.org/mailman/listinfo/postgis-users\">PostGIS "
+"newsgroup</ulink> your thoughts and together we can make it happen."
+msgstr "Le campagne di finanziamento diffuso sono campagne che promuoviamo per finanziare funzionalità molto richieste e che possono servire a un gran numero di persone. Ogni campagna è dedicata in modo particolare a una data funzionalità o gruppo di funzionalità. Ogni sponsor partecipat con una quota ridotta rispetto al finanziamento richiesto, e con un numero sufficiente di persone e organizzazioni che contribuiscono, possiamo ottenere i fondi per retribuire un lavoro che servirà a molti. Se avete un'idea per una funzione che pensate possa essere cofinanziata anche da molti altri, vi preghiamo di condividere le vostre idee sul <ulink url=\"http://www.postgis.org/mailman/listinfo/postgis-users\">newsgroup PostGIS</ulink>, e insieme possiamo vedere di realizzarla."
#. Tag: para
#: introduction.xml:269
"PostGIS 2.0.0 was the first release we tried this strategy. We used <ulink "
"url=\"http://www.pledgebank.com\">PledgeBank</ulink> and we got two "
"successful campaigns out of it."
-msgstr ""
+msgstr "PostGIS 2.0.0 è stata la prima release con cui abbiamo tentato questa strategia. Abbiamo utilizzato <ulink url=\"http://www.pledgebank.com\">PledgeBank</ulink>, realizzando due campagne di successo."
#. Tag: para
#: introduction.xml:270
#, no-c-format
msgid ""
-"<ulink url=\"http://www.pledgebank.com/postgistopology\"><emphasis role="
-"\"bold\">postgistopology</emphasis></ulink> - 10 plus sponsors each "
+"<ulink url=\"http://www.pledgebank.com/postgistopology\"><emphasis "
+"role=\"bold\">postgistopology</emphasis></ulink> - 10 plus sponsors each "
"contributed $250 USD to build toTopoGeometry function and beef up topology "
"support in 2.0.0. It happened."
-msgstr ""
+msgstr "<ulink url=\"http://www.pledgebank.com/postgistopology\"><emphasis role=\"bold\">postgistopology</emphasis></ulink> - Oltre 10 sponsor hanno contribuito con 250 USD ciascuno per realizzare la funzione TopoGeometry e per migliorare il supporto della topologia nella versione 2.0.0. E' successo."
#. Tag: para
#: introduction.xml:271
#, no-c-format
msgid ""
-"<ulink url=\"http://www.pledgebank.com/postgis64windows\"><emphasis role="
-"\"bold\">postgis64windows</emphasis></ulink> - 20 someodd sponsors each "
-"contributed $100 USD to pay for the work needed to work out PostGIS 64-bit "
+"<ulink url=\"http://www.pledgebank.com/postgis64windows\"><emphasis "
+"role=\"bold\">postgis64windows</emphasis></ulink> - 20 someodd sponsors each"
+" contributed $100 USD to pay for the work needed to work out PostGIS 64-bit "
"on windows issues. It happened. We now have a 64-bit beta release for "
"PostGIS 2.0.0 and a final one planned for release that will be available on "
"PostgreSQL stack builder."
-msgstr ""
+msgstr "<ulink url=\"http://www.pledgebank.com/postgis64windows\"><emphasis role=\"bold\">postgis64windows</emphasis></ulink> - Una ventina di sponsor hanno contribuito con 100 USD ciascuno per retribuire il lavoro necessario per risolvere varie problematiche su PostGIS per Windows a 64 bit. E' successo. Ora abbiamo una versione beta per PostGIS 2.0.0 e una previsione per il rilascio di una versione finale che sarà disponibile con lo stack builder PostgreSQL."
#. Tag: term
#: introduction.xml:276
#, no-c-format
msgid "Important Support Libraries"
-msgstr ""
+msgstr "Librerie di supporto importanti"
#. Tag: para
#: introduction.xml:279
msgid ""
"The <ulink url=\"http://trac.osgeo.org/geos/\">GEOS</ulink> geometry "
"operations library, and the algorithmic work of Martin Davis in making it "
-"all work, ongoing maintenance and support of Mateusz Loskot, Sandro Santilli "
-"(strk), Paul Ramsey and others."
-msgstr ""
+"all work, ongoing maintenance and support of Mateusz Loskot, Sandro Santilli"
+" (strk), Paul Ramsey and others."
+msgstr "La libreria per operazioni geometriche <ulink url=\"http://trac.osgeo.org/geos/\">GEOS</ulink>, e il lavoro sugli algoritmi di Martin Davis per far funzionare il tutto, la manutenzione e il supporto continui di Mateusz Loskot, Sandro Santilli (strk), Paul Ramsey a altri."
#. Tag: para
#: introduction.xml:284
"Abstraction Library, by Frank Warmerdam and others is used to power much of "
"the raster functionality introduced in PostGIS 2.0.0. In kind, improvements "
"needed in GDAL to support PostGIS are contributed back to the GDAL project."
-msgstr ""
+msgstr "La libreria <ulink url=\"http://trac.osgeo.org/gdal/\">GDAL</ulink> (Geospatial Data Abstraction Library), di Frank Warmerdam e altri viene utilizzata per far funzionare gran parte delle funzionalità raster introdotte in PostGIS 2.0.0. I miglioramenti realizzati su GDAL per consentire il supporto di PostGIS sono stati restituiti come contributo al progetto GDAL."
#. Tag: para
#: introduction.xml:289
"The <ulink url=\"http://trac.osgeo.org/proj/\">Proj4</ulink> cartographic "
"projection library, and the work of Gerald Evenden and Frank Warmerdam in "
"creating and maintaining it."
-msgstr ""
+msgstr "La libreria di proiezione cartografica <ulink url=\"http://trac.osgeo.org/proj/\">Proj4</ulink>, e il lavoro di Gerald Evenden e Frank Warmerdam nel crearla e mantenerla."
#. Tag: para
#: introduction.xml:293
"flexibility of PostGIS would not be possible without the extensibility, "
"great query planner, GIST index, and plethora of SQL features provided by "
"PostgreSQL."
-msgstr ""
+msgstr "Ultimo, ma non ultimo, il database <ulink url=\"http://www.postgresql.org\">PostgreSQL</ulink>, il gigante sulle cui spalle sta PostGIS. Molta della velolcità e flessibilità di PostGIS non sarebbe possibile senza l'estensibilità, il grande query planner, l'indice GIST, e la varietà di caratteristiche SQL rese disponibili da PostgreSQL."
#. Tag: title
#: introduction.xml:302
#, no-c-format
msgid "More Information"
-msgstr ""
+msgstr "Altre informazioni"
#. Tag: para
#: introduction.xml:306
#, no-c-format
msgid ""
"The latest software, documentation and news items are available at the "
-"PostGIS web site, <ulink url=\"http://www.postgis.org\">http://www.postgis."
-"org</ulink>."
-msgstr ""
+"PostGIS web site, <ulink "
+"url=\"http://www.postgis.org\">http://www.postgis.org</ulink>."
+msgstr "Le versioni più recenti del software, della documentazione e le notizie sono disponibili sul sito web di PostGIS, <ulink url=\"http://www.postgis.org\">http://www.postgis.org</ulink>."
#. Tag: para
#: introduction.xml:312
#, no-c-format
msgid ""
"More information about the GEOS geometry operations library is available "
-"at<ulink url=\"http://trac.osgeo.org/geos/\"> http://trac.osgeo.org/geos/</"
-"ulink>."
-msgstr ""
+"at<ulink url=\"http://trac.osgeo.org/geos/\"> "
+"http://trac.osgeo.org/geos/</ulink>."
+msgstr "Ulteriori informazioni sulla libreria di operazioni geometriche GEOS sono disponibili alla pagina <ulink url=\"http://trac.osgeo.org/geos/\"> http://trac.osgeo.org/geos/</ulink>."
#. Tag: para
#: introduction.xml:318
#, no-c-format
msgid ""
-"More information about the Proj4 reprojection library is available at <ulink "
-"url=\"http://trac.osgeo.org/proj/\">http://trac.osgeo.org/proj/</ulink>."
-msgstr ""
+"More information about the Proj4 reprojection library is available at <ulink"
+" url=\"http://trac.osgeo.org/proj/\">http://trac.osgeo.org/proj/</ulink>."
+msgstr "Ulteriori informazioni sulla libreria di riproiezione Proj4 sono disponibili alla pagina <ulink url=\"http://trac.osgeo.org/proj/\">http://trac.osgeo.org/proj/</ulink>."
#. Tag: para
#: introduction.xml:324
#, no-c-format
msgid ""
"More information about the PostgreSQL database server is available at the "
-"PostgreSQL main site <ulink url=\"http://www.postgresql.org\">http://www."
-"postgresql.org</ulink>."
-msgstr ""
+"PostgreSQL main site <ulink "
+"url=\"http://www.postgresql.org\">http://www.postgresql.org</ulink>."
+msgstr "Ulteriori informazioni sul server database PostgreSQL database server sono disponibili dal sito principale di PostgreSQL <ulink url=\"http://www.postgresql.org\">http://www.postgresql.org</ulink>."
#. Tag: para
#: introduction.xml:330
#, no-c-format
msgid ""
"More information about GiST indexing is available at the PostgreSQL GiST "
-"development site, <ulink url=\"http://www.sai.msu.su/~megera/postgres/gist/"
-"\">http://www.sai.msu.su/~megera/postgres/gist/</ulink>."
-msgstr ""
+"development site, <ulink "
+"url=\"http://www.sai.msu.su/~megera/postgres/gist/\">http://www.sai.msu.su/~megera/postgres/gist/</ulink>."
+msgstr "Ulteriori informazioni sull'indicizzazione GiST sono disponibili sul sito di sviluppo di PostgreSQL GiST, <ulink url=\"http://www.sai.msu.su/~megera/postgres/gist/\">http://www.sai.msu.su/~megera/postgres/gist/</ulink>."
#. Tag: para
#: introduction.xml:336
msgid ""
"More information about MapServer internet map server is available at <ulink "
"url=\"http://mapserver.org/\">http://mapserver.org</ulink>."
-msgstr ""
+msgstr "Ulteriori informazioni sul map server internet MapServer sono disponibili su <ulink url=\"http://mapserver.org/\">http://mapserver.org</ulink>."
#. Tag: para
#: introduction.xml:342
#, no-c-format
msgid ""
"The "<ulink url=\"http://www.opengeospatial.org/standards/sfs\">Simple "
-"Features for Specification for SQL</ulink>" is available at the OpenGIS "
-"Consortium web site: <ulink url=\"http://www.opengeospatial.org/\">http://"
-"www.opengeospatial.org/</ulink>."
-msgstr ""
+"Features for Specification for SQL</ulink>" is available at the OpenGIS"
+" Consortium web site: <ulink "
+"url=\"http://www.opengeospatial.org/\">http://www.opengeospatial.org/</ulink>."
+msgstr "La documentazione su "<ulink url=\"http://www.opengeospatial.org/standards/sfs\">Simple Features for Specification for SQL</ulink>" è disponibile sul sito web dell'OpenGIS Consortium: <ulink url=\"http://www.opengeospatial.org/\">http://www.opengeospatial.org/</ulink>."
# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# Tommaso Di Bucchianico, 2013
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2013-11-30 05:55+0000\n"
+"Last-Translator: Tommaso Di Bucchianico\n"
+"Language-Team: Italian (Italy) (http://www.transifex.com/projects/p/postgis-1/language/it_IT/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: it_IT\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. Tag: title
#: performance_tips.xml:3
#, no-c-format
msgid "Performance tips"
-msgstr ""
+msgstr "Consigli per migliori prestazioni"
#. Tag: title
#: performance_tips.xml:6
#, no-c-format
msgid "Small tables of large geometries"
-msgstr ""
+msgstr "Piccole tabelle contenenti geometrie di grandi dimensioni"
#. Tag: title
#: performance_tips.xml:9
#, no-c-format
msgid "Problem description"
-msgstr ""
+msgstr "Descrizione del problema"
#. Tag: para
#: performance_tips.xml:11
#, no-c-format
msgid ""
"Current PostgreSQL versions (including 8.0) suffer from a query optimizer "
-"weakness regarding TOAST tables. TOAST tables are a kind of \"extension room"
-"\" used to store large (in the sense of data size) values that do not fit "
-"into normal data pages (like long texts, images or complex geometries with "
-"lots of vertices), see <ulink url=\"http://www.postgresql.org/docs/current/"
-"static/storage-toast.html\">the PostgreSQL Documentation for TOAST</ulink> "
-"for more information)."
-msgstr ""
+"weakness regarding TOAST tables. TOAST tables are a kind of \"extension "
+"room\" used to store large (in the sense of data size) values that do not "
+"fit into normal data pages (like long texts, images or complex geometries "
+"with lots of vertices), see <ulink "
+"url=\"http://www.postgresql.org/docs/current/static/storage-toast.html\">the"
+" PostgreSQL Documentation for TOAST</ulink> for more information)."
+msgstr "Le attuali versioni di PostgreSQL (compresa la versione 8.0) sono affette da un difetto del query optimizer riguardante le tabelle TOAST. Le tabelle TOAST sono una sorta di \"spazio aggiuntivo\" usato per memorizzare valori di grandi dimensioni (nel senso di dimensioni dei dati) che non possono essere salvati in normali pagine (per esempio lunghi testi, immagini o geometrie con molti vertici). Vedi <ulink url=\"http://www.postgresql.org/docs/current/static/storage-toast.html\">la documentazione PostgreSQL sulle tabelle TOAST</ulink> per maggiori informazioni)."
#. Tag: para
#: performance_tips.xml:19
"itself is small, but it uses lots of TOAST space. In our example case, the "
"table itself had about 80 rows and used only 3 data pages, but the TOAST "
"table used 8225 pages."
-msgstr ""
+msgstr "Il problema si presenta nel caso di tabelle contenenti geometrie di grandi dimensioni ma poche righe (per esempio una tabella contenente i confini di tutti gli stati europei ad alta risoluzione). In questo caso infatti la tabella in se è di piccole dimensioni ma usa molto spazio TOAST. Nel nostro esempio la tabella conteneva circa 80 righe e utilizzava solo 3 pagine di dati, ma la tabella TOAST ne utilizzava 8225."
#. Tag: para
#: performance_tips.xml:26
"is correct. But in our case, the && operator has to fetch every "
"geometry from disk to compare the bounding boxes, thus reading all TOAST "
"pages, too."
-msgstr ""
+msgstr "Ora si lanci una query che usi l'operatore && e che [MATCHES] solo poche righe. Il "
#. Tag: para
#: performance_tips.xml:35
msgid ""
"To see whether your suffer from this bug, use the \"EXPLAIN ANALYZE\" "
"postgresql command. For more information and the technical details, you can "
-"read the thread on the postgres performance mailing list: http://archives."
-"postgresql.org/pgsql-performance/2005-02/msg00030.php"
-msgstr ""
+"read the thread on the postgres performance mailing list: "
+"http://archives.postgresql.org/pgsql-performance/2005-02/msg00030.php"
+msgstr "Per controllare se i propri dati sono interessati da questo bug, si può usare il comando PostgreSQL \"EXPLAIN ANALYZE\". Per maggiori informazioni e dettagli tecnici consultare il corrispondente thread sulla mailing list di PostgreSQL: http://archives.postgresql.org/pgsql-performance/2005-02/msg00030.php"
#. Tag: title
#: performance_tips.xml:43
#, no-c-format
msgid "Workarounds"
-msgstr ""
+msgstr "Possibili soluzioni"
#. Tag: para
#: performance_tips.xml:45
msgid ""
"The PostgreSQL people are trying to solve this issue by making the query "
"estimation TOAST-aware. For now, here are two workarounds:"
-msgstr ""
+msgstr "Gli sviluppatori di PostgreSQL stanno cercando di risolvere il problema rendendo la valutazione della query indipendente dalla tabella TOAST. Per ora ci sono due possibili soluzioni alternative:"
#. Tag: para
#: performance_tips.xml:48
"The first workaround is to force the query planner to use the index. Send "
"\"SET enable_seqscan TO off;\" to the server before issuing the query. This "
"basically forces the query planner to avoid sequential scans whenever "
-"possible. So it uses the GIST index as usual. But this flag has to be set on "
-"every connection, and it causes the query planner to make misestimations in "
-"other cases, so you should \"SET enable_seqscan TO on;\" after the query."
-msgstr ""
+"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 "La è forzare il query planner ad usare l'indice spaziale usando il comando \"SET enable_seqscan TO off;\" prima di lanciare la query. Questo comando impedisce al query planner di usare lo scan sequenziale della tabella se possibile e lo forza quindi ad usare l'indice GIST. Tuttavia il comando deve essere lanciato ad ogni connessione e, per evitare di confondere il query planner in altri casi, il parametro deve essere resettato dopo l'esecuzione della query interessata con il comando \"SET enable_seqscan TO on;\" ."
#. Tag: para
#: performance_tips.xml:56
msgid ""
"The second workaround is to make the sequential scan as fast as the query "
"planner thinks. This can be achieved by creating an additional column that "
-"\"caches\" the bbox, and matching against this. In our example, the commands "
-"are like:"
-msgstr ""
+"\"caches\" the bbox, and matching against this. In our example, the commands"
+" are like:"
+msgstr "Il secondo metodo è rendere lo scan sequenziale così veloce come il query planner si aspetta che sia. Questo può essere raggiunto aggiungendo una colonna addizionale in cui salvare la bounding box di ogni geometria. Nel nostro esempio i comandi sarebbero:"
#. 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_Force_2d(the_geom));"
-msgstr ""
+msgstr "SELECT AddGeometryColumn('myschema','mytable','bbox','4326','GEOMETRY','2');\nUPDATE mytable SET bbox = ST_Envelope(ST_Force_2d(the_geom));"
#. Tag: para
#: performance_tips.xml:63
#, no-c-format
msgid ""
-"Now change your query to use the && operator against bbox instead of "
-"geom_column, like:"
-msgstr ""
+"Now change your query to use the && operator against bbox instead of"
+" geom_column, like:"
+msgstr "Ora la query deve essere modificata in modo da usare l'operatore && con la colonna bbox piuttosto che con la colonna geom_column:"
#. Tag: programlisting
#: performance_tips.xml:66
"SELECT geom_column \n"
"FROM mytable \n"
"WHERE bbox && ST_SetSRID('BOX3D(0 0,1 1)'::box3d,4326);"
-msgstr ""
+msgstr "SELECT geom_column\nFROM mytable\nWHERE bbox && ST_SetSRID('BOX3D(0 0,1 1)'::box3d,4326);"
#. Tag: para
#: performance_tips.xml:68
"\"in sync\". The most transparent way to do this would be triggers, but you "
"also can modify your application to keep the bbox column current or run the "
"UPDATE query above after every modification."
-msgstr ""
+msgstr "Ovviamente la colonna bbox deve essere mantenuta attuale quando si modificano o si aggiungono geometrie. La via più semplice per fare questo sarebbe con un trigger, oppure l'applicazione può essere modificata in modo da attualizzare anche la colonna bbox oppure si può lanciare l'UPDATE precedente dopo ogni modifica."
#. Tag: title
#: performance_tips.xml:77
#, no-c-format
msgid "CLUSTERing on geometry indices"
-msgstr ""
+msgstr "CLUSTERing di indici geometrici"
#. Tag: para
#: performance_tips.xml:79
#, no-c-format
msgid ""
"For tables that are mostly read-only, and where a single index is used for "
-"the majority of queries, PostgreSQL offers the CLUSTER command. This command "
-"physically reorders all the data rows in the same order as the index "
-"criteria, yielding two performance advantages: First, for index range scans, "
-"the number of seeks on the data table is drastically reduced. Second, if "
+"the majority of queries, PostgreSQL offers the CLUSTER command. This command"
+" physically reorders all the data rows in the same order as the index "
+"criteria, yielding two performance advantages: First, for index range scans,"
+" the number of seeks on the data table is drastically reduced. Second, if "
"your working set concentrates to some small intervals on the indices, you "
"have a more efficient caching because the data rows are spread along fewer "
-"data pages. (Feel invited to read the CLUSTER command documentation from the "
-"PostgreSQL manual at this point.)"
-msgstr ""
+"data pages. (Feel invited to read the CLUSTER command documentation from the"
+" PostgreSQL manual at this point.)"
+msgstr "Per tabelle che vengono per lo più solo lette, e dove un singolo indice è usato dalla maggior parte delle query, PostgreSQL offre il comando CLUSTER. Questo comando riordina fisicamente le righe in modo che l'ordine corrisponda a quello dell'indice. Con questo metodo si migliorano le prestazioni per due motivi: primo, il numero delle ricerche nella tabella dei dati è ridotto drasticamente. Secondo, se i dati interessati dalla query sono concentrati in un piccolo intervallo sull'indice, il processo di mettere in cache sarà più efficiente perché le righe saranno distribuite all'interno di poche pagine. (si invita a leggere la documentazione di PostgreSQL riguardante il comando CLUSTER)."
#. Tag: para
#: performance_tips.xml:89
"However, currently PostgreSQL does not allow clustering on PostGIS GIST "
"indices because GIST indices simply ignores NULL values, you get an error "
"message like:"
-msgstr ""
+msgstr "Attualmente però, PostgreSQL non permette di usare il clustering con indici GIST, perché gli indici GIST ignorano i valori nulli:"
#. Tag: programlisting
#: performance_tips.xml:93
msgid ""
"lwgeom=# CLUSTER my_geom_index ON my_table; \n"
"ERROR: cannot cluster when index access method does not handle null values\n"
-"HINT: You may be able to work around this by marking column \"the_geom\" NOT "
-"NULL."
-msgstr ""
+"HINT: You may be able to work around this by marking column \"the_geom\" NOT NULL."
+msgstr "lwgeom=# CLUSTER my_geom_index ON my_table;\nERROR: cannot cluster when index access method does not handle null values\nHINT: You may be able to work around this by marking column \"the_geom\" NOT NULL."
#. Tag: para
#: performance_tips.xml:95
#, no-c-format
msgid ""
-"As the HINT message tells you, one can work around this deficiency by adding "
-"a \"not null\" constraint to the table:"
-msgstr ""
+"As the HINT message tells you, one can work around this deficiency by adding"
+" a \"not null\" constraint to the table:"
+msgstr "Come suggerito dal messaggio di errore, è possibile aggirare il problema aggiungendo un vincolo \"NOT NULL\" alla tabella:"
#. Tag: programlisting
#: performance_tips.xml:98
msgid ""
"lwgeom=# ALTER TABLE my_table ALTER COLUMN the_geom SET not null; \n"
"ALTER TABLE"
-msgstr ""
+msgstr "lwgeom=# ALTER TABLE my_table ALTER COLUMN the_geom SET not null; \nALTER TABLE"
#. Tag: para
#: performance_tips.xml:100
"geometry column. Additionally, you must use the above method to add the "
"constraint, using a CHECK constraint like \"ALTER TABLE blubb ADD CHECK "
"(geometry is not null);\" will not work."
-msgstr ""
+msgstr "Ovviamente questo non funzionerà se la colonna the_geom già contiene valori nulli. Inoltre il vincolo dev'essere definito usando il comando precedente. Usare un vincolo CHECK del tipo \"ALTER TABLE blubb ADD CHECK (geometry is not null);\" non funzionerà."
#. Tag: title
#: performance_tips.xml:107
#, no-c-format
msgid "Avoiding dimension conversion"
-msgstr ""
+msgstr "Evitare la conversione della dimensione"
#. Tag: para
#: performance_tips.xml:109
#, no-c-format
msgid ""
-"Sometimes, you happen to have 3D or 4D data in your table, but always access "
-"it using OpenGIS compliant ST_AsText() or ST_AsBinary() functions that only "
-"output 2D geometries. They do this by internally calling the ST_Force_2d() "
+"Sometimes, you happen to have 3D or 4D data in your table, but always access"
+" it using OpenGIS compliant ST_AsText() or ST_AsBinary() functions that only"
+" output 2D geometries. They do this by internally calling the ST_Force_2d() "
"function, which introduces a significant overhead for large geometries. To "
"avoid this overhead, it may be feasible to pre-drop those additional "
"dimensions once and forever:"
-msgstr ""
+msgstr "A volte può accadere di avere dati in 3D o 4D, ma di accederli sempre usando funzioni che danno in output solo geometrie 2D come ST_AsText() oppure ST_AsBinary(). Queste funzioni processano internamente le geometrie eseguendo ST_Force2D() e questo può risultare in un peggioramento delle prestazioni significativo nel caso di geometrie di grandi dimensioni. Per evitare questo problema è consigliabile eliminare le dimensioni non utilizzate una volte e per sempre:"
#. Tag: programlisting
#: performance_tips.xml:116
msgid ""
"UPDATE mytable SET the_geom = ST_Force_2d(the_geom); \n"
"VACUUM FULL ANALYZE mytable;"
-msgstr ""
+msgstr "UPDATE mytable SET the_geom = ST_Force_2d(the_geom); \nVACUUM FULL ANALYZE mytable;"
#. Tag: para
#: performance_tips.xml:118
msgid ""
"Note that if you added your geometry column using AddGeometryColumn() "
"there'll be a constraint on geometry dimension. To bypass it you will need "
-"to drop the constraint. Remember to update the entry in the geometry_columns "
-"table and recreate the constraint afterwards."
-msgstr ""
+"to drop the constraint. Remember to update the entry in the geometry_columns"
+" table and recreate the constraint afterwards."
+msgstr "Se la colonna di tipo geometry è stata aggiunta usando la funzione AddGeometryColumn(), verrà creato anche un vincolo dimensionale sulla geometria. Per aggirare il vincolo sarà necessario cancellarlo. Ricorda di attualizzare il record nella tabella geometry_columns e di ricreare il vincolo successivamente. "
#. Tag: para
#: performance_tips.xml:124
"for temporary disk space. Additionally, if you have mixed dimension "
"geometries, restricting the UPDATE by \"WHERE dimension(the_geom)>2\" "
"skips re-writing of geometries that already are in 2D."
-msgstr ""
+msgstr "Nel caso di grandi tabelle può essere sensato dividere l'UPDATE in porzioni più piccole, usando la clausola WHERE con la chiave primaria o un altro criterio flessibile per attualizzare solo una parte della tabella , ed eseguendo un semplice \"VACUUM;\" tra gli UPDATE. Questo accorgimento ridurrà drasticamente il bisogno lo spazio temporaneo sul disco. Inoltre, se la colonna geometrica contiene geometrie con diverse dimensioni, si può limitare l'UPDATE con \"WHERE dimension(the_geom)>2\", evitando così di riscrivere le geometrie che sono già in 2D."
#. Tag: title
#: performance_tips.xml:136
#, no-c-format
msgid "Tuning your configuration"
-msgstr ""
+msgstr "Mettere a punto la configurazione"
#. Tag: para
#: performance_tips.xml:138
#, no-c-format
msgid ""
"These tips are taken from Kevin Neufeld's presentation \"Tips for the "
-"PostGIS Power User\" at the FOSS4G 2007 conference. Depending on your use of "
-"PostGIS (for example, static data and complex analysis vs frequently updated "
-"data and lots of users) these changes can provide significant speedups to "
-"your queries."
-msgstr ""
+"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 "Questi consigli sono tratti dalla presentazione di Kevin Neufeld \"Tips for the PostGIS Power User\" alla conferenza FOSS4G 2007. A seconda del contesto in cui viene usato PostGIS (per esempio dati statici e analisi complesse piuttosto che update frequenti e numerosi utenti) questi cambiamenti possono significare un significativo aumento della velocità delle query."
#. Tag: para
#: performance_tips.xml:144
#, no-c-format
msgid ""
"For a more tips (and better formatting), the original presentation is at "
-"<ulink url=\"http://2007.foss4g.org/presentations/view.php?"
-"abstract_id=117\"> http://2007.foss4g.org/presentations/view.php?"
-"abstract_id=117</ulink>."
-msgstr ""
+"<ulink "
+"url=\"http://2007.foss4g.org/presentations/view.php?abstract_id=117\"> "
+"http://2007.foss4g.org/presentations/view.php?abstract_id=117</ulink>."
+msgstr "Per più consigli (e una formattazione migliore) la presentazione originale è consultabile a <ulink url=\"http://2007.foss4g.org/presentations/view.php?abstract_id=117\"> http://2007.foss4g.org/presentations/view.php?abstract_id=117</ulink>."
#. Tag: title
#: performance_tips.xml:151
#, no-c-format
msgid "Startup"
-msgstr ""
+msgstr "Startup"
#. Tag: para
#: performance_tips.xml:153
#, no-c-format
msgid "These settings are configured in postgresql.conf:"
-msgstr ""
+msgstr "Queste impostazioni sono definite in postgresql.conf:"
#. Tag: ulink
#: performance_tips.xml:158
#, no-c-format
msgid "checkpoint_segments"
-msgstr ""
+msgstr "checkpoint_segments"
#. Tag: para
#: performance_tips.xml:163
msgid ""
"Maximum number of log file segments between automatic WAL checkpoints (each "
"segment is normally 16MB); default is 3"
-msgstr ""
+msgstr "Numero massimo di segmenti del log file tra checkpoint WAL (ogni segmento è normalmente 16MB); l'impostazione predefinita è 3."
#. Tag: para
#: performance_tips.xml:169
msgid ""
"Set to at least 10 or 30 for databases with heavy write activity, or more "
"for large database loads. Another article on the topic worth reading <ulink "
-"url=\"http://www.westnet.com/~gsmith/content/postgresql/chkp-bgw-83.htm"
-"\">Greg Smith: Checkpoint and Background writer</ulink>"
-msgstr ""
+"url=\"http://www.westnet.com/~gsmith/content/postgresql/chkp-"
+"bgw-83.htm\">Greg Smith: Checkpoint and Background writer</ulink>"
+msgstr "Impostare almeno su 10 o 30 per database con intensa attività di scrittura, o più quando si importa nel database grandi quantità di dati. Un altro articolo da leggere sull'argomento è <ulink url=\"http://www.westnet.com/~gsmith/content/postgresql/chkp-bgw-83.htm\">Greg Smith: Checkpoint and Background writer</ulink> "
#. Tag: para
#: performance_tips.xml:175
#, no-c-format
msgid "Possibly store the xlog on a separate disk device"
-msgstr ""
+msgstr "Se possibile, salvare il xlog su un disco separato"
#. Tag: ulink
#: performance_tips.xml:182
#, no-c-format
msgid "constraint_exclusion"
-msgstr ""
+msgstr "constraint_exclusion"
#. Tag: para
#: performance_tips.xml:187
msgid ""
"Default: off (prior to PostgreSQL 8.4 and for PostgreSQL 8.4+ is set to "
"partition)"
-msgstr ""
+msgstr "Il valore di default è \"off\" per versioni inferiori alla 8.4 e \"partition\" a partire dalla 8.4()"
#. Tag: para
#: performance_tips.xml:192
#, no-c-format
msgid ""
-"This is generally used for table partitioning. If you are running PostgreSQL "
-"versions below 8.4, set to \"on\" to ensure the query planner will optimize "
-"as desired. As of PostgreSQL 8.4, the default for this is set to \"partition"
-"\" which is ideal for PostgreSQL 8.4 and above since it will force the "
-"planner to only analyze tables for constraint consideration if they are in "
-"an inherited hierarchy and not pay the planner penalty otherwise."
-msgstr ""
+"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 "Generalmente usato per il partizionamento delle tabelle. Con versioni di PostgreSQL inferiori alla 8.4 impostare il parametro su \"on\" per permettere al query planner di ottimizzare secondo necessità. Da PostgreSQL 8.4, il valore di default è \"partition\", ideale per versioni 8.4 e superiori perché forza il query planner ad analizzare i vincoli delle tabelle solo se queste sono in una gerarchia di ereditarietà e non essere penalizzate dal planner in caso contrario."
#. Tag: ulink
#: performance_tips.xml:202
#, no-c-format
msgid "shared_buffers"
-msgstr ""
+msgstr "shared_buffers"
#. Tag: para
#: performance_tips.xml:207
#, no-c-format
msgid "Default: ~32MB"
-msgstr ""
+msgstr "Default: ~32MB"
#. Tag: para
#: performance_tips.xml:212
#, no-c-format
msgid "Set to about 1/3 to 3/4 of available RAM"
-msgstr ""
+msgstr "Impostare da 1/3 a 3/4 della RAM disponibile."
#. Tag: title
#: performance_tips.xml:220
#, no-c-format
msgid "Runtime"
-msgstr ""
+msgstr "Runtime"
#. Tag: para
#: performance_tips.xml:222
"<ulink url=\"http://www.postgresql.org/docs/current/static/runtime-config-"
"resource.html#GUC-WORK-MEM\">work_mem</ulink> (the memory used for sort "
"operations and complex queries)"
-msgstr ""
+msgstr "<ulink url=\"http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-WORK-MEM\">work_mem</ulink> (memoria usata per operazioni di ordinamento e query complesse)"
#. Tag: para
#: performance_tips.xml:228
#, no-c-format
msgid "Default: 1MB"
-msgstr ""
+msgstr "Default: 1MB"
#. Tag: para
#: performance_tips.xml:233
#, no-c-format
msgid "Adjust up for large dbs, complex queries, lots of RAM"
-msgstr ""
+msgstr "Aumentare il valore per grandi database, query complesse, abbondanza di RAM"
#. Tag: para
#: performance_tips.xml:238
#, no-c-format
msgid "Adjust down for many concurrent users or low RAM."
-msgstr ""
+msgstr "Diminuire il valore nel caso di molti utenti concorrenti oppure disponibilità di RAM ridotta"
#. Tag: para
#: performance_tips.xml:243
#, no-c-format
msgid "If you have lots of RAM and few developers:"
-msgstr ""
+msgstr "Nel caso di molta RAM e pochi programmatori:"
#. Tag: programlisting
#: performance_tips.xml:245
#, no-c-format
msgid "SET work_mem TO 1200000;"
-msgstr ""
+msgstr "SET work_mem TO 1200000;"
#. Tag: para
#: performance_tips.xml:250
"<ulink url=\"http://www.postgresql.org/docs/current/static/runtime-config-"
"resource.html#GUC-MAINTENANCE-WORK-MEM\">maintenance_work_mem</ulink> (used "
"for VACUUM, CREATE INDEX, etc.)"
-msgstr ""
+msgstr "<ulink url=\"http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-MAINTENANCE-WORK-MEM\">maintenance_work_mem</ulink> (usato per VACUUM, CREATE INDEX, etc.)"
#. Tag: para
#: performance_tips.xml:256
#, no-c-format
msgid "Default: 16MB"
-msgstr ""
+msgstr "Default: 16MB"
#. Tag: para
#: performance_tips.xml:261
#, no-c-format
msgid "Generally too low - ties up I/O, locks objects while swapping memory"
-msgstr ""
+msgstr "Generalmente troppo basso. Tiene occupati i processi Input/Output e blocca oggetti quando viene impegnata la memoria swap."
#. Tag: para
#: performance_tips.xml:266
msgid ""
"Recommend 32MB to 256MB on production servers w/lots of RAM, but depends on "
"the # of concurrent users. If you have lots of RAM and few developers:"
-msgstr ""
+msgstr "Si raccomandano 32MB oppure 256MB su server di produzione con molta RAM, ma dipende dal numero di utenti concorrenti. Nel caso di molta RAM e pochi sviluppatori:"
#. Tag: programlisting
#: performance_tips.xml:269
#, no-c-format
msgid "SET maintainence_work_mem TO 1200000;"
-msgstr ""
+msgstr "SET maintainence_work_mem TO 1200000;"
# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# pibinko <pibinko@gmail.com>, 2013
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
-"PO-Revision-Date: 2012-09-14 19:55+CEST\n"
-"Last-Translator: Sandro Santilli <strk@keybit.net>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2013-11-26 23:23+0000\n"
+"Last-Translator: pibinko <pibinko@gmail.com>\n"
+"Language-Team: Italian (Italy) (http://www.transifex.com/projects/p/postgis-1/language/it_IT/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: it_IT\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. Tag: title
#: postgis.xml:106
#: postgis.xml:114
#, no-c-format
msgid ""
-"<orgname><ulink url=\"http://www.cleverelephant.ca\">clever elephant</"
-"ulink></orgname> <address><city>Victoria</city> <state>British Columbia</"
-"state> <country>Canada</country> <email>pramsey@cleverelephant.ca</email></"
-"address>"
-msgstr ""
+"<orgname><ulink url=\"http://www.cleverelephant.ca\">clever "
+"elephant</ulink></orgname> <address><city>Victoria</city> <state>British "
+"Columbia</state> <country>Canada</country> "
+"<email>pramsey@cleverelephant.ca</email></address>"
+msgstr "<orgname><ulink url=\"http://www.cleverelephant.ca\">clever elephant</ulink></orgname> <address><city>Victoria</city> <state>British Columbia</state> <country>Canada</country> <email>pramsey@cleverelephant.ca</email></address>"
#. Tag: para
#: postgis.xml:124
"which allows GIS (Geographic Information Systems) objects to be stored in "
"the database. PostGIS includes support for GiST-based R-Tree spatial "
"indexes, and functions for analysis and processing of GIS objects."
-msgstr ""
-"PostGIS e' un'estensione per la base di dati relazionale ad oggetti PostgreSQL "
-"che consente di conservare oggetti GIS (Sistemi di Informazione Geografica) nella "
-"base di dati. PostGIS include il supporto per gli indici spaziali di tipo R-Tree "
-"basati sul GiST e le funzioni per l'analisi e il trattamento degli oggetti GIS."
+msgstr "PostGIS è un'estensione del database object-relational PostgreSQL che consente l'archiviazione di oggetti GIS (Geographic Information Systems). PostGIS comprende il supporto per gli indici spaziali R-Tree basati su GIST, e funzioni per l'analisi e l'elaborazione di oggetti GIS."
#. Tag: para
#: postgis.xml:133
#, no-c-format
msgid "This is the manual for version &last_release_version;"
-msgstr "Questo e' il manuale per la versione &last_release_version;"
+msgstr "Questo è il manuale per la versione &last_release_version;"
#. Tag: para
#: postgis.xml:134
#, no-c-format
msgid ""
-"This work is licensed under a <ulink url=\"http://creativecommons.org/"
-"licenses/by-sa/3.0/\">Creative Commons Attribution-Share Alike 3.0 License</"
-"ulink>. Feel free to use this material any way you like, but we ask that you "
-"attribute credit to the PostGIS Project and wherever possible, a link back "
-"to <ulink url=\"http://www.postgis.org\">http://www.postgis.org</ulink>."
-msgstr ""
+"This work is licensed under a <ulink "
+"url=\"http://creativecommons.org/licenses/by-sa/3.0/\">Creative Commons "
+"Attribution-Share Alike 3.0 License</ulink>. Feel free to use this material "
+"any way you like, but we ask that you attribute credit to the PostGIS "
+"Project and wherever possible, a link back to <ulink "
+"url=\"http://www.postgis.org\">http://www.postgis.org</ulink>."
+msgstr "Questa opera è rilasciata con una licenza <ulink url=\"http://creativecommons.org/licenses/by-sa/3.0/\">Creative Commons Attribution-Share Alike 3.0 License</ulink>. Siete liberi di utilizzare questo materiale come volete, ma vi chiediamo di citare il progetto PostGIS come fonte e, ove possibile, di inserire un link a <ulink url=\"http://www.postgis.org\">http://www.postgis.org</ulink>."
# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# aghisla <a.ghisla@gmail.com>, 2013
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2013-11-28 13:58+0000\n"
+"Last-Translator: aghisla <a.ghisla@gmail.com>\n"
+"Language-Team: Italian (Italy) (http://www.transifex.com/projects/p/postgis-1/language/it_IT/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: it_IT\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. Tag: title
#: reference.xml:3
#, no-c-format
msgid "PostGIS Reference"
-msgstr ""
+msgstr "Guida a PostGIS"
#. Tag: para
#: reference.xml:5
"The functions given below are the ones which a user of PostGIS is likely to "
"need. There are other functions which are required support functions to the "
"PostGIS objects which are not of use to a general user."
-msgstr ""
+msgstr "Le funzioni elencate sotto sono quelle di cui un utente PostGIS avrà più probabilmente bisogno. Ci sono altre funzioni, di supporto agli oggetti PostGIS, che non sono utili all'utente comune."
#. Tag: para
#: reference.xml:11
#, no-c-format
msgid ""
-"PostGIS has begun a transition from the existing naming convention to an SQL-"
-"MM-centric convention. As a result, most of the functions that you know and "
-"love have been renamed using the standard spatial type (ST) prefix. Previous "
-"functions are still available, though are not listed in this document where "
-"updated functions are equivalent. The non ST_ functions not listed in this "
-"documentation are deprecated and will be removed in a future release so STOP "
-"USING THEM."
-msgstr ""
+"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 "PostGIS ha iniziato una transizione dalla namin convention esistente a una convenzione SQL-MM-centrica. Di conseguenza, molte funzioni di uso comune sono state rinominate usando il prefisso standard \"spatial type\" (ST). Le funzioni precedenti sono tuttora disponibili, anche se non elencate nel presente documento. Al loro posto sono presenti le funzioni aggiornate corrispondenti. Le funzioni non ST_ che mancano in questo documento sono deprecate e verranno eliminate in una futura release, quindi NON VANNO PIÙ USATE."
#. Tag: chapter
#: reference.xml:16
"&reference_operator; &reference_measure; &reference_processing; "
"&reference_lrs; &reference_transaction; &reference_misc; "
"&reference_exception;"
-msgstr ""
+msgstr "&reference_type; &reference_management; &reference_constructor; &reference_accessor; &reference_editor; &reference_output; &reference_operator; &reference_measure; &reference_processing; &reference_lrs; &reference_transaction; &reference_misc; &reference_exception;"
# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# Tommaso Di Bucchianico, 2013
+# Tommaso Di Bucchianico, 2013
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2013-12-07 18:17+0000\n"
+"Last-Translator: Tommaso Di Bucchianico\n"
+"Language-Team: Italian (Italy) (http://www.transifex.com/projects/p/postgis-1/language/it_IT/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: it_IT\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. Tag: title
#: reference_management.xml:3
#, no-c-format
msgid "Management Functions"
-msgstr ""
+msgstr "Funzioni per la gestione del database"
#. Tag: refname
#: reference_management.xml:7
#, no-c-format
msgid "AddGeometryColumn"
-msgstr ""
+msgstr "AddGeometryColumn"
#. Tag: refpurpose
#: reference_management.xml:9
"Adds a geometry column to an existing table of attributes. By default uses "
"type modifier to define rather than constraints. Pass in false for "
"use_typmod to get old check constraint based behavior"
-msgstr ""
+msgstr "Aggiunge una colonna di tipo geometry in una tabella già esistente. Per default usa il modificatore di tipo per la definizione della geometria piuttosto che dei vincoli. Si può passare alla funzione il parametro use_typemod per attivare il vecchio meccanismo basato sui vincoli."
#. Tag: funcsynopsis
#: reference_management.xml:15
#, no-c-format
msgid ""
-"<funcprototype> <funcdef>text <function>AddGeometryColumn</function></"
-"funcdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></"
-"paramdef> <paramdef><type>varchar </type> <parameter>column_name</"
-"parameter></paramdef> <paramdef><type>integer </type> <parameter>srid</"
-"parameter></paramdef> <paramdef><type>varchar </type> <parameter>type</"
-"parameter></paramdef> <paramdef><type>integer </type> <parameter>dimension</"
-"parameter></paramdef> <paramdef choice=\"opt\"><type>boolean </type> "
+"<funcprototype> <funcdef>text "
+"<function>AddGeometryColumn</function></funcdef> <paramdef><type>varchar "
+"</type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar"
+" </type> <parameter>column_name</parameter></paramdef> "
+"<paramdef><type>integer </type> <parameter>srid</parameter></paramdef> "
+"<paramdef><type>varchar </type> <parameter>type</parameter></paramdef> "
+"<paramdef><type>integer </type> <parameter>dimension</parameter></paramdef> "
+"<paramdef choice=\"opt\"><type>boolean </type> "
"<parameter>use_typmod=true</parameter></paramdef> </funcprototype> "
-"<funcprototype> <funcdef>text <function>AddGeometryColumn</function></"
-"funcdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></"
-"paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></"
-"paramdef> <paramdef><type>varchar </type> <parameter>column_name</"
-"parameter></paramdef> <paramdef><type>integer </type> <parameter>srid</"
-"parameter></paramdef> <paramdef><type>varchar </type> <parameter>type</"
-"parameter></paramdef> <paramdef><type>integer </type> <parameter>dimension</"
-"parameter></paramdef> <paramdef choice=\"opt\"><type>boolean </type> "
+"<funcprototype> <funcdef>text "
+"<function>AddGeometryColumn</function></funcdef> <paramdef><type>varchar "
+"</type> <parameter>schema_name</parameter></paramdef> "
+"<paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef>"
+" <paramdef><type>varchar </type> "
+"<parameter>column_name</parameter></paramdef> <paramdef><type>integer "
+"</type> <parameter>srid</parameter></paramdef> <paramdef><type>varchar "
+"</type> <parameter>type</parameter></paramdef> <paramdef><type>integer "
+"</type> <parameter>dimension</parameter></paramdef> <paramdef "
+"choice=\"opt\"><type>boolean </type> "
"<parameter>use_typmod=true</parameter></paramdef> </funcprototype> "
-"<funcprototype> <funcdef>text <function>AddGeometryColumn</function></"
-"funcdef> <paramdef><type>varchar </type> <parameter>catalog_name</"
-"parameter></paramdef> <paramdef><type>varchar </type> "
-"<parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </"
-"type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </"
-"type> <parameter>column_name</parameter></paramdef> <paramdef><type>integer "
-"</type> <parameter>srid</parameter></paramdef> <paramdef><type>varchar </"
-"type> <parameter>type</parameter></paramdef> <paramdef><type>integer </type> "
-"<parameter>dimension</parameter></paramdef> <paramdef choice=\"opt"
-"\"><type>boolean </type> <parameter>use_typmod=true</parameter></paramdef> </"
-"funcprototype>"
-msgstr ""
+"<funcprototype> <funcdef>text "
+"<function>AddGeometryColumn</function></funcdef> <paramdef><type>varchar "
+"</type> <parameter>catalog_name</parameter></paramdef> "
+"<paramdef><type>varchar </type> "
+"<parameter>schema_name</parameter></paramdef> <paramdef><type>varchar "
+"</type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar"
+" </type> <parameter>column_name</parameter></paramdef> "
+"<paramdef><type>integer </type> <parameter>srid</parameter></paramdef> "
+"<paramdef><type>varchar </type> <parameter>type</parameter></paramdef> "
+"<paramdef><type>integer </type> <parameter>dimension</parameter></paramdef> "
+"<paramdef choice=\"opt\"><type>boolean </type> "
+"<parameter>use_typmod=true</parameter></paramdef> </funcprototype>"
+msgstr "<funcprototype> <funcdef>text <function>AddGeometryColumn</function></funcdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> <paramdef><type>integer </type> <parameter>srid</parameter></paramdef> <paramdef><type>varchar </type> <parameter>type</parameter></paramdef> <paramdef><type>integer </type> <parameter>dimension</parameter></paramdef> <paramdef choice=\"opt\"><type>boolean </type> <parameter>use_typmod=true</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>text <function>AddGeometryColumn</function></funcdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> <paramdef><type>integer </type> <parameter>srid</parameter></paramdef> <paramdef><type>varchar </type> <parameter>type</parameter></paramdef> <paramdef><type>integer </type> <parameter>dimension</parameter></paramdef> <paramdef choice=\"opt\"><type>boolean </type> <parameter>use_typmod=true</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>text <function>AddGeometryColumn</function></funcdef> <paramdef><type>varchar </type> <parameter>catalog_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> <paramdef><type>integer </type> <parameter>srid</parameter></paramdef> <paramdef><type>varchar </type> <parameter>type</parameter></paramdef> <paramdef><type>integer </type> <parameter>dimension</parameter></paramdef> <paramdef choice=\"opt\"><type>boolean </type> <parameter>use_typmod=true</parameter></paramdef> </funcprototype>"
#. Tag: title
#: reference_management.xml:92 reference_management.xml:188
#: reference_management.xml:862
#, no-c-format
msgid "Description"
-msgstr ""
+msgstr "Descrizione"
#. Tag: para
#: reference_management.xml:94
"error is thrown if the schemaname doesn't exist (or not visible in the "
"current search_path) or the specified SRID, geometry type, or dimension is "
"invalid."
-msgstr ""
+msgstr "Aggiunge una colonna di tipo geometry ad una tabella già esistente. <varname>schema_name</varname> è il nome dello schema contenente la tabella. <varname>srid</varname> deve essere un numero intero che si riferisce a un record presente nella tabella SPATIAL_REF_SYS. <varname>type</varname> deve essere una stringa corrispondente al tipo di geometria, per esempio 'POLYGON' oppure 'MULTILINESTRING'. La funzione produce un errore se lo schema non esiste (oppure non è visibile nel search_path attual), o la SRID specificata, il tipo di geometria o la dimensione sono invalidi."
#. Tag: para
#: reference_management.xml:104
"geometry_columns is a view that reads from system catalogs. It by default "
"also does not create constraints, but instead uses the built in type "
"modifier behavior of PostgreSQL. So for example building a wgs84 POINT "
-"column with this function is now equivalent to: <code>ALTER TABLE some_table "
-"ADD COLUMN geom geometry(Point,4326);</code>"
-msgstr ""
+"column with this function is now equivalent to: <code>ALTER TABLE some_table"
+" ADD COLUMN geom geometry(Point,4326);</code>"
+msgstr "Cambiamento nella versione 2.0.0: questa funzione non aggiorna più geometry_columns perché geometry_columns non è più una tabella ma una vista che estrae automaticamente le informazioni necessarie dal system catalog. Inoltre per default la funzione non crea vincoli ma usa il modificatore di tipi integrato in PostgreSQL. Per esempio: creare una colonna con tipo POINT e con SRID 4326 con questa funzione, ora è equivalente a:<code>ALTER TABLE some_table ADD COLUMN geom geometry(Point,4326);</code>"
#. Tag: para
#: reference_management.xml:107
msgid ""
"Changed: 2.0.0 If you require the old behavior of constraints use the "
"default <varname>use_typmod</varname>, but set it to false."
-msgstr ""
+msgstr "Cambiamento nella versione 2.0.0: il vecchio funzionamento con i vincoli può essere attivato passando alla funzione l'argomento <varname>use_typmod</varname> impostato su false."
#. Tag: para
#: reference_management.xml:111
"correctly because they inherit the typmod behavior of their parent table "
"column. Views that use geometry functions that output other geometries will "
"need to be cast to typmod geometries for these view geometry columns to be "
-"registered correctly in geometry_columns. Refer to <xref linkend="
-"\"Manual_Register_Spatial_Column\"/>."
-msgstr ""
+"registered correctly in geometry_columns. Refer to <xref "
+"linkend=\"Manual_Register_Spatial_Column\"/>."
+msgstr "Cambiamento in versione 2.0.0: le viste non possono più essere registrate in geometry_columns, a meno che le colonne geometry a cui fanno riferimento non siano state generate con typmod e usate senza funzioni wrapper. In questo caso la vista sarà registrata correttamente in geometry_columns perché eredita il typmod dalla colonna geometry originale. Le viste che usano funzioni che ritornano geometrie verranno registrate correttamente se il tipo delll'output della funzione verrà definito esplicitamente con la funzione CAST come typmod geometry."
#. Tag: para
#: reference_management.xml:117 reference_management.xml:194
#, no-c-format
msgid "&sfs_compliant;"
-msgstr ""
+msgstr "&sfs_compliant;"
#. Tag: para
#: reference_management.xml:118 reference_management.xml:195
#: reference_management.xml:868
#, no-c-format
msgid "&Z_support;"
-msgstr ""
+msgstr "&Z_support;"
#. Tag: para
#: reference_management.xml:119 reference_management.xml:196
#: reference_management.xml:869
#, no-c-format
msgid "&curve_support;"
-msgstr ""
+msgstr "&curve_support;"
#. Tag: para
#: reference_management.xml:120
msgid ""
"Enhanced: 2.0.0 use_typmod argument introduced. Defaults to creating typmod "
"geometry column instead of constraint-based."
-msgstr ""
+msgstr "Miglioramento nella version 2.0.0: introdotto il parametro use_typmod. Se settato su true (o se omesso) la funzione genererà una colonna geometry basata su typmod. Se settato su \"false\", la funzione genererà una colonna geometry con basata su vincoli geometrici."
#. Tag: title
#: reference_management.xml:124 reference_management.xml:203
#: reference_management.xml:683 reference_management.xml:784
#, no-c-format
msgid "Examples"
-msgstr ""
+msgstr "Esempi"
#. Tag: programlisting
#: reference_management.xml:126
"\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"
"(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"
" geom | Point | 4326 | 2\n"
" geom_c | Point | 4326 | 2\n"
" geomcp_c | CurvePolygon | 4326 | 2"
-msgstr ""
+msgstr "-- Creiamo uno schema in sui salvare i dati\nCREATE SCHEMA my_schema;\n-- Creiamo una Semplice tabella\nCREATE TABLE my_schema.my_spatial_table (id serial);\n\n-- La descrizione mostra una semplice tabella con un'unica colonna \"id\"\npostgis=# \\d my_schema.my_spatial_table\n Table \"my_schema.my_spatial_table\"\n Column | Type | Modifiers\n--------+---------+-------------------------------------------------------------------------\n id | integer | not null default nextval('my_schema.my_spatial_table_id_seq'::regclass)\n\n-- Aggiungiamo una colonna geometry\nSELECT AddGeometryColumn ('my_schema','my_spatial_table','geom',4326,'POINT',2);\n\n-- Aggiungiamo un'altra colonna geometry settando il parametro use_typmod = false, \n-- generando quindo una colonna geometry basata su vincoli\nSELECT AddGeometryColumn ('my_schema','my_spatial_table','geom_c',4326,'POINT',2, false);\n\n--Di nuovo aggiungiamo un'altra colonna geometry usando il vecchio meccanismo con vincoli\nAdd a curvepolygon using old constraint behavior\nSELECT AddGeometryColumn ('my_schema','my_spatial_table','geomcp_c',4326,'CURVEPOLYGON',2, false);\n\n-- Descriviamo di nuovo la tabella con le nuove 3 colonne geometry\n\\d my_schema.my_spatial_table\n addgeometrycolumn \n-------------------------------------------------------------------------\n my_schema.my_spatial_table.geomcp_c SRID:4326 TYPE:CURVEPOLYGON DIMS:2 \n(1 row)\n\n Table \"my_schema.my_spatial_table\"\n Column | Type | Modifiers \n----------+----------------------+-------------------------------------------------------------------------\n id | integer | not null default nextval('my_schema.my_spatial_table_id_seq'::regclass)\n geom | geometry(Point,4326) | \n geom_c | geometry | \n geomcp_c | geometry | \nCheck constraints:\n \"enforce_dims_geom_c\" CHECK (st_ndims(geom_c) = 2)\n \"enforce_dims_geomcp_c\" CHECK (st_ndims(geomcp_c) = 2)\n \"enforce_geotype_geom_c\" CHECK (geometrytype(geom_c) = 'POINT'::text OR geom_c IS NULL)\n \"enforce_geotype_geomcp_c\" CHECK (geometrytype(geomcp_c) = 'CURVEPOLYGON'::text OR geomcp_c IS NULL)\n \"enforce_srid_geom_c\" CHECK (st_srid(geom_c) = 4326)\n \"enforce_srid_geomcp_c\" CHECK (st_srid(geomcp_c) = 4326)\n \n-- Le colonne geometry sono automaticamante registrate in geometry_columns\nSELECT f_geometry_column As col_name, type, srid, coord_dimension As ndims \n FROM geometry_columns\n WHERE f_table_name = 'my_spatial_table' AND f_table_schema = 'my_schema';\n\n col_name | type | srid | ndims \n----------+--------------+------+-------\n geom | Point | 4326 | 2\n geom_c | Point | 4326 | 2\n geomcp_c | CurvePolygon | 4326 | 2"
#. Tag: title
#: reference_management.xml:130 reference_management.xml:208
#: reference_management.xml:873
#, no-c-format
msgid "See Also"
-msgstr ""
+msgstr "Vedi anche"
#. Tag: para
#: reference_management.xml:132
#, no-c-format
msgid ""
-", <xref linkend=\"DropGeometryTable\"/>, <xref linkend=\"geometry_columns\"/"
-">, <xref linkend=\"Manual_Register_Spatial_Column\"/>"
-msgstr ""
+", <xref linkend=\"DropGeometryTable\"/>, <xref "
+"linkend=\"geometry_columns\"/>, <xref "
+"linkend=\"Manual_Register_Spatial_Column\"/>"
+msgstr ", <xref linkend=\"DropGeometryTable\"/>, <xref linkend=\"geometry_columns\"/>, <xref linkend=\"Manual_Register_Spatial_Column\"/>"
#. Tag: refname
#: reference_management.xml:138
#, no-c-format
msgid "DropGeometryColumn"
-msgstr ""
+msgstr "DropGeometryColumn"
#. Tag: refpurpose
#: reference_management.xml:140
#, no-c-format
msgid "Removes a geometry column from a spatial table."
-msgstr ""
+msgstr "Rimuove una colonna geometry da una tabella spaziale"
#. Tag: funcsynopsis
#: reference_management.xml:145
#, no-c-format
msgid ""
-"<funcprototype> <funcdef>text <function>DropGeometryColumn</function></"
-"funcdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></"
-"paramdef> <paramdef><type>varchar </type> <parameter>column_name</"
-"parameter></paramdef> </funcprototype> <funcprototype> <funcdef>text "
-"<function>DropGeometryColumn</function></funcdef> <paramdef><type>varchar </"
-"type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar "
-"</type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar "
-"</type> <parameter>column_name</parameter></paramdef> </funcprototype> "
-"<funcprototype> <funcdef>text <function>DropGeometryColumn</function></"
-"funcdef> <paramdef><type>varchar </type> <parameter>catalog_name</"
-"parameter></paramdef> <paramdef><type>varchar </type> "
-"<parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </"
-"type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </"
-"type> <parameter>column_name</parameter></paramdef> </funcprototype>"
-msgstr ""
+"<funcprototype> <funcdef>text "
+"<function>DropGeometryColumn</function></funcdef> <paramdef><type>varchar "
+"</type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar"
+" </type> <parameter>column_name</parameter></paramdef> </funcprototype> "
+"<funcprototype> <funcdef>text "
+"<function>DropGeometryColumn</function></funcdef> <paramdef><type>varchar "
+"</type> <parameter>schema_name</parameter></paramdef> "
+"<paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef>"
+" <paramdef><type>varchar </type> "
+"<parameter>column_name</parameter></paramdef> </funcprototype> "
+"<funcprototype> <funcdef>text "
+"<function>DropGeometryColumn</function></funcdef> <paramdef><type>varchar "
+"</type> <parameter>catalog_name</parameter></paramdef> "
+"<paramdef><type>varchar </type> "
+"<parameter>schema_name</parameter></paramdef> <paramdef><type>varchar "
+"</type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar"
+" </type> <parameter>column_name</parameter></paramdef> </funcprototype>"
+msgstr "<funcprototype> <funcdef>text <function>DropGeometryColumn</function></funcdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>text <function>DropGeometryColumn</function></funcdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>text <function>DropGeometryColumn</function></funcdef> <paramdef><type>varchar </type> <parameter>catalog_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> </funcprototype>"
#. Tag: para
#: reference_management.xml:190
"Removes a geometry column from a spatial table. Note that schema_name will "
"need to match the f_table_schema field of the table's row in the "
"geometry_columns table."
-msgstr ""
+msgstr "Rimuove una colonna geometry da una tabella spaziale. Il campo schema_name deve corrispondere al campo f_table_schema in geometry_columns."
#. Tag: para
#: reference_management.xml:198
"that since geometry_columns is now a view against the system catalogs, you "
"can drop a geometry column like any other table column using <code>ALTER "
"TABLE</code>"
-msgstr ""
+msgstr "Cambiamento nella versione 2.0.0: questa funzione è mantenuta per retrocompatibilità. Attualmente, essendo geometry_columns una vista basata sul system catalog, una colonna geometry può essere rimossa come qualsiasi altra colonna con <code>ALTER TABLE</code>"
#. Tag: programlisting
#: reference_management.xml:205
"-- In PostGIS 2.0+ the above is also equivalent to the standard\n"
"-- the standard alter table. Both will deregister from geometry_columns\n"
"ALTER TABLE my_schema.my_spatial_table DROP column geom;"
-msgstr ""
+msgstr "SELECT DropGeometryColumn ('my_schema','my_spatial_table','geom');\n ----RESULT output ---\n dropgeometrycolumn\n------------------------------------------------------\n my_schema.my_spatial_table.geom effectively removed.\n \n-- In PostGIS 2.0+ questo comando è equivalente al comando standard\n-- alter table. Ambedue i comandi rimuoveranno la colonna da geometry_columns\nALTER TABLE my_schema.my_spatial_table DROP column geom;"
#. Tag: para
#: reference_management.xml:210
#, no-c-format
-msgid ""
-", <xref linkend=\"DropGeometryTable\"/>, <xref linkend=\"geometry_columns\"/>"
-msgstr ""
+msgid ", <xref linkend=\"DropGeometryTable\"/>, <xref linkend=\"geometry_columns\"/>"
+msgstr ", <xref linkend=\"DropGeometryTable\"/>, <xref linkend=\"geometry_columns\"/>"
#. Tag: refname
#: reference_management.xml:216
#, no-c-format
msgid "DropGeometryTable"
-msgstr ""
+msgstr "DropGeometryTable"
#. Tag: refpurpose
#: reference_management.xml:218
#, no-c-format
msgid "Drops a table and all its references in geometry_columns."
-msgstr ""
+msgstr "Rimuove una tabella e tutte le sue referenze da geometry_columns"
#. Tag: funcsynopsis
#: reference_management.xml:223
#, no-c-format
msgid ""
-"<funcprototype> <funcdef>boolean <function>DropGeometryTable</function></"
-"funcdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></"
-"paramdef> </funcprototype> <funcprototype> <funcdef>boolean "
-"<function>DropGeometryTable</function></funcdef> <paramdef><type>varchar </"
-"type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar "
+"<funcprototype> <funcdef>boolean "
+"<function>DropGeometryTable</function></funcdef> <paramdef><type>varchar "
"</type> <parameter>table_name</parameter></paramdef> </funcprototype> "
-"<funcprototype> <funcdef>boolean <function>DropGeometryTable</function></"
-"funcdef> <paramdef><type>varchar </type> <parameter>catalog_name</"
-"parameter></paramdef> <paramdef><type>varchar </type> "
-"<parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </"
-"type> <parameter>table_name</parameter></paramdef> </funcprototype>"
-msgstr ""
+"<funcprototype> <funcdef>boolean "
+"<function>DropGeometryTable</function></funcdef> <paramdef><type>varchar "
+"</type> <parameter>schema_name</parameter></paramdef> "
+"<paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef>"
+" </funcprototype> <funcprototype> <funcdef>boolean "
+"<function>DropGeometryTable</function></funcdef> <paramdef><type>varchar "
+"</type> <parameter>catalog_name</parameter></paramdef> "
+"<paramdef><type>varchar </type> "
+"<parameter>schema_name</parameter></paramdef> <paramdef><type>varchar "
+"</type> <parameter>table_name</parameter></paramdef> </funcprototype>"
+msgstr "<funcprototype> <funcdef>boolean <function>DropGeometryTable</function></funcdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>boolean <function>DropGeometryTable</function></funcdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>boolean <function>DropGeometryTable</function></funcdef> <paramdef><type>varchar </type> <parameter>catalog_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> </funcprototype>"
#. Tag: para
#: reference_management.xml:256
"Drops a table and all its references in geometry_columns. Note: uses "
"current_schema() on schema-aware pgsql installations if schema is not "
"provided."
-msgstr ""
+msgstr "Rimuove una tabella spaziale e tutte le sue referenze da geometry_columns. Nota: utilizza la funzione PostgreSQL current_schema() se lo schema non è passato come argomento."
#. Tag: para
#: reference_management.xml:261
msgid ""
"Changed: 2.0.0 This function is provided for backward compatibility. Now "
"that since geometry_columns is now a view against the system catalogs, you "
-"can drop a table with geometry columns like any other table using <code>DROP "
-"TABLE</code>"
-msgstr ""
+"can drop a table with geometry columns like any other table using <code>DROP"
+" TABLE</code>"
+msgstr "Cambiamento nella versione 2.0.0: questa funzione è mantenuta per retrocompatibilità. Attualmente, essendo geometry_columns una vista basata sul system catalog, una tabella spaziale può essere rimossa come qualsiasi altra tabella con <code>DROP TABLE</code>"
#. Tag: programlisting
#: reference_management.xml:269
" \n"
"-- The above is now equivalent to --\n"
"DROP TABLE my_schema.my_spatial_table;"
-msgstr ""
+msgstr "SELECT DropGeometryTable ('my_schema','my_spatial_table');\n----RESULT output ---\nmy_schema.my_spatial_table dropped.\n \n-- Il comando sopra è ora equivalente a --\nDROP TABLE my_schema.my_spatial_table;"
#. Tag: para
#: reference_management.xml:274
#, no-c-format
-msgid ""
-", <xref linkend=\"DropGeometryColumn\"/>, <xref linkend=\"geometry_columns\"/"
-">"
-msgstr ""
+msgid ", <xref linkend=\"DropGeometryColumn\"/>, <xref linkend=\"geometry_columns\"/>"
+msgstr ", <xref linkend=\"DropGeometryColumn\"/>, <xref linkend=\"geometry_columns\"/>"
#. Tag: refname
#: reference_management.xml:281
#, no-c-format
msgid "PostGIS_Full_Version"
-msgstr ""
+msgstr "PostGIS_Full_Version"
#. Tag: refpurpose
#: reference_management.xml:283
#, no-c-format
msgid "Reports full postgis version and build configuration infos."
-msgstr ""
+msgstr "Riporta informazioni sulla versione completa di Postgis e sulla configurazione della compilazione."
#. Tag: funcprototype
#: reference_management.xml:289
msgid ""
"<funcdef>text <function>PostGIS_Full_Version</function></funcdef> "
"<paramdef></paramdef>"
-msgstr ""
+msgstr "<funcdef>text <function>PostGIS_Full_Version</function></funcdef> <paramdef></paramdef>"
#. Tag: para
#: reference_management.xml:300
"Reports full postgis version and build configuration infos. Also informs "
"about synchronization between libraries and scripts suggesting upgrades as "
"needed."
-msgstr ""
+msgstr "Riporta informazioni sulla versione completa di Postgis e sulla configurazione della compilazione. Effettua anche un confronto tra librerie e script e suggerisce l'aggiornamento dove ce ne sia bisogno."
#. Tag: programlisting
#: reference_management.xml:308
"SELECT PostGIS_Full_Version();\n"
" postgis_full_version\n"
"----------------------------------------------------------------------------------\n"
-" POSTGIS=\"1.3.3\" GEOS=\"3.1.0-CAPI-1.5.0\" PROJ=\"Rel. 4.4.9, 29 Oct "
-"2004\" USE_STATS\n"
+" POSTGIS=\"1.3.3\" GEOS=\"3.1.0-CAPI-1.5.0\" PROJ=\"Rel. 4.4.9, 29 Oct 2004\" USE_STATS\n"
"(1 row)"
-msgstr ""
+msgstr "SELECT PostGIS_Full_Version();\n postgis_full_version\n----------------------------------------------------------------------------------\n POSTGIS=\"1.3.3\" GEOS=\"3.1.0-CAPI-1.5.0\" PROJ=\"Rel. 4.4.9, 29 Oct 2004\" USE_STATS\n(1 row)"
#. Tag: para
#: reference_management.xml:314
#, no-c-format
msgid ""
-", <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref linkend="
-"\"PostGIS_Lib_Version\"/>, <xref linkend=\"PostGIS_LibXML_Version\"/>, <xref "
+", <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref "
+"linkend=\"PostGIS_Lib_Version\"/>, <xref "
+"linkend=\"PostGIS_LibXML_Version\"/>, <xref "
"linkend=\"PostGIS_PROJ_Version\"/>, <xref linkend=\"PostGIS_Version\"/>"
-msgstr ""
+msgstr ", <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref linkend=\"PostGIS_Lib_Version\"/>, <xref linkend=\"PostGIS_LibXML_Version\"/>, <xref linkend=\"PostGIS_PROJ_Version\"/>, <xref linkend=\"PostGIS_Version\"/>"
#. Tag: refname
#: reference_management.xml:327
#, no-c-format
msgid "PostGIS_GEOS_Version"
-msgstr ""
+msgstr "PostGIS_GEOS_Version"
#. Tag: refpurpose
#: reference_management.xml:329
#, no-c-format
msgid "Returns the version number of the GEOS library."
-msgstr ""
+msgstr "Riporta il numero della versione della libreria GEOS."
#. Tag: funcprototype
#: reference_management.xml:335
msgid ""
"<funcdef>text <function>PostGIS_GEOS_Version</function></funcdef> "
"<paramdef></paramdef>"
-msgstr ""
+msgstr "<funcdef>text <function>PostGIS_GEOS_Version</function></funcdef> <paramdef></paramdef>"
#. Tag: para
#: reference_management.xml:346
msgid ""
"Returns the version number of the GEOS library, or <varname>NULL</varname> "
"if GEOS support is not enabled."
-msgstr ""
+msgstr "Riporta il numero di versione della libreria GEOS oppure <varname>NULL</varname> se il supporto a GEOS non è attivato."
#. Tag: programlisting
#: reference_management.xml:353
"----------------------\n"
" 3.1.0-CAPI-1.5.0\n"
"(1 row)"
-msgstr ""
+msgstr "SELECT PostGIS_GEOS_Version();\n postgis_geos_version\n----------------------\n 3.1.0-CAPI-1.5.0\n(1 row)"
#. Tag: para
#: reference_management.xml:359
#, no-c-format
msgid ""
-", <xref linkend=\"PostGIS_Lib_Version\"/>, <xref linkend="
-"\"PostGIS_LibXML_Version\"/>, <xref linkend=\"PostGIS_PROJ_Version\"/>, "
-"<xref linkend=\"PostGIS_Version\"/>"
-msgstr ""
+", <xref linkend=\"PostGIS_Lib_Version\"/>, <xref "
+"linkend=\"PostGIS_LibXML_Version\"/>, <xref "
+"linkend=\"PostGIS_PROJ_Version\"/>, <xref linkend=\"PostGIS_Version\"/>"
+msgstr ", <xref linkend=\"PostGIS_Lib_Version\"/>, <xref linkend=\"PostGIS_LibXML_Version\"/>, <xref linkend=\"PostGIS_PROJ_Version\"/>, <xref linkend=\"PostGIS_Version\"/>"
#. Tag: refname
#: reference_management.xml:369
#, no-c-format
msgid "PostGIS_LibXML_Version"
-msgstr ""
+msgstr "PostGIS_LibXML_Version"
#. Tag: refpurpose
#: reference_management.xml:371
#, no-c-format
msgid "Returns the version number of the libxml2 library."
-msgstr ""
+msgstr "Riporta il numero della versione della libreria libxml2."
#. Tag: funcprototype
#: reference_management.xml:377
msgid ""
"<funcdef>text <function>PostGIS_LibXML_Version</function></funcdef> "
"<paramdef></paramdef>"
-msgstr ""
+msgstr "<funcdef>text <function>PostGIS_LibXML_Version</function></funcdef> <paramdef></paramdef>"
#. Tag: para
#: reference_management.xml:388
#, no-c-format
msgid "Returns the version number of the LibXML2 library."
-msgstr ""
+msgstr "Riporta il numero della versione della libreria LibXML2."
#. Tag: para
#: reference_management.xml:389
#, no-c-format
msgid "Availability: 1.5"
-msgstr ""
+msgstr "Disponibilità: dalla versione 1.5."
#. Tag: programlisting
#: reference_management.xml:395
"----------------------\n"
" 2.7.6\n"
"(1 row)"
-msgstr ""
+msgstr "SELECT PostGIS_LibXML_Version();\n postgis_libxml_version\n----------------------\n 2.7.6\n(1 row)"
#. Tag: para
#: reference_management.xml:401
#, no-c-format
msgid ""
-", <xref linkend=\"PostGIS_Lib_Version\"/>, <xref linkend="
-"\"PostGIS_PROJ_Version\"/>, <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref "
-"linkend=\"PostGIS_Version\"/>"
-msgstr ""
+", <xref linkend=\"PostGIS_Lib_Version\"/>, <xref "
+"linkend=\"PostGIS_PROJ_Version\"/>, <xref "
+"linkend=\"PostGIS_GEOS_Version\"/>, <xref linkend=\"PostGIS_Version\"/>"
+msgstr ", <xref linkend=\"PostGIS_Lib_Version\"/>, <xref linkend=\"PostGIS_PROJ_Version\"/>, <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref linkend=\"PostGIS_Version\"/>"
#. Tag: refname
#: reference_management.xml:411
#, no-c-format
msgid "PostGIS_Lib_Build_Date"
-msgstr ""
+msgstr "PostGIS_Lib_Build_Date"
#. Tag: refpurpose
#: reference_management.xml:413
#, no-c-format
msgid "<refpurpose>Returns build date of the PostGIS library.</refpurpose>"
-msgstr ""
+msgstr "<refpurpose>Riporta la data della compilazione della libreria PostGIS.</refpurpose>"
#. Tag: funcprototype
#: reference_management.xml:418
msgid ""
"<funcdef>text <function>PostGIS_Lib_Build_Date</function></funcdef> "
"<paramdef></paramdef>"
-msgstr ""
+msgstr "<funcdef>text <function>PostGIS_Lib_Build_Date</function></funcdef> <paramdef></paramdef>"
#. Tag: para
#: reference_management.xml:429
#, no-c-format
msgid "<para>Returns build date of the PostGIS library.</para>"
-msgstr ""
+msgstr "<para>Riporta la data della compilazione della libreria PostGIS.</para>"
#. Tag: programlisting
#: reference_management.xml:435
"------------------------\n"
" 2008-06-21 17:53:21\n"
"(1 row)"
-msgstr ""
+msgstr "SELECT PostGIS_Lib_Build_Date();\n postgis_lib_build_date\n------------------------\n 2008-06-21 17:53:21\n(1 row)"
#. Tag: refname
#: reference_management.xml:441
#, no-c-format
msgid "PostGIS_Lib_Version"
-msgstr ""
+msgstr "PostGIS_Lib_Version"
#. Tag: refpurpose
#: reference_management.xml:443
#, no-c-format
msgid ""
"<refpurpose>Returns the version number of the PostGIS library.</refpurpose>"
-msgstr ""
+msgstr "<refpurpose>Riporta il numero di versione della libreria PostGIS.</refpurpose>"
#. Tag: funcprototype
#: reference_management.xml:449
#, no-c-format
msgid ""
-"<funcdef>text <function>PostGIS_Lib_Version</function></funcdef> <paramdef></"
-"paramdef>"
-msgstr ""
+"<funcdef>text <function>PostGIS_Lib_Version</function></funcdef> "
+"<paramdef></paramdef>"
+msgstr "<funcdef>text <function>PostGIS_Lib_Version</function></funcdef> <paramdef></paramdef>"
#. Tag: para
#: reference_management.xml:460
#, no-c-format
msgid "<para>Returns the version number of the PostGIS library.</para>"
-msgstr ""
+msgstr "<para>Riporta il numero di versione della libreria PostGIS.</para>"
#. Tag: programlisting
#: reference_management.xml:466
"---------------------\n"
" 1.3.3\n"
"(1 row)"
-msgstr ""
+msgstr "SELECT PostGIS_Lib_Version();\n postgis_lib_version\n---------------------\n 1.3.3\n(1 row)"
#. Tag: para
#: reference_management.xml:472
#, no-c-format
msgid ""
-", <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref linkend="
-"\"PostGIS_LibXML_Version\"/>, <xref linkend=\"PostGIS_PROJ_Version\"/>, "
-"<xref linkend=\"PostGIS_Version\"/>"
-msgstr ""
+", <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref "
+"linkend=\"PostGIS_LibXML_Version\"/>, <xref "
+"linkend=\"PostGIS_PROJ_Version\"/>, <xref linkend=\"PostGIS_Version\"/>"
+msgstr ", <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref linkend=\"PostGIS_LibXML_Version\"/>, <xref linkend=\"PostGIS_PROJ_Version\"/>, <xref linkend=\"PostGIS_Version\"/>"
#. Tag: refname
#: reference_management.xml:482
#, no-c-format
msgid "PostGIS_PROJ_Version"
-msgstr ""
+msgstr "PostGIS_PROJ_Version"
#. Tag: refpurpose
#: reference_management.xml:484
#, no-c-format
msgid "Returns the version number of the PROJ4 library."
-msgstr ""
+msgstr "Riporta il numero di versione della libreria PROJ4."
#. Tag: funcprototype
#: reference_management.xml:490
msgid ""
"<funcdef>text <function>PostGIS_PROJ_Version</function></funcdef> "
"<paramdef></paramdef>"
-msgstr ""
+msgstr "<funcdef>text <function>PostGIS_PROJ_Version</function></funcdef> <paramdef></paramdef>"
#. Tag: para
#: reference_management.xml:501
msgid ""
"Returns the version number of the PROJ4 library, or <varname>NULL</varname> "
"if PROJ4 support is not enabled."
-msgstr ""
+msgstr "Riporta il numero di versione della libreria PROJ4, oppure <varname>NULL</varname> se il supporto a PROJ4 non è attivato."
#. Tag: programlisting
#: reference_management.xml:508
"-------------------------\n"
" Rel. 4.4.9, 29 Oct 2004\n"
"(1 row)"
-msgstr ""
+msgstr "SELECT PostGIS_PROJ_Version();\n postgis_proj_version\n-------------------------\n Rel. 4.4.9, 29 Oct 2004\n(1 row)"
#. Tag: para
#: reference_management.xml:514 reference_management.xml:556
#, no-c-format
msgid ""
-", <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref linkend="
-"\"PostGIS_Lib_Version\"/>, <xref linkend=\"PostGIS_LibXML_Version\"/>, <xref "
-"linkend=\"PostGIS_Version\"/>"
-msgstr ""
+", <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref "
+"linkend=\"PostGIS_Lib_Version\"/>, <xref "
+"linkend=\"PostGIS_LibXML_Version\"/>, <xref linkend=\"PostGIS_Version\"/>"
+msgstr ", <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref linkend=\"PostGIS_Lib_Version\"/>, <xref linkend=\"PostGIS_LibXML_Version\"/>, <xref linkend=\"PostGIS_Version\"/>"
#. Tag: refname
#: reference_management.xml:524
#, no-c-format
msgid "PostGIS_Scripts_Build_Date"
-msgstr ""
+msgstr "PostGIS_Scripts_Build_Date"
#. Tag: refpurpose
#: reference_management.xml:526
#, no-c-format
msgid "<refpurpose>Returns build date of the PostGIS scripts.</refpurpose>"
-msgstr ""
+msgstr "<refpurpose>Riporta la data della compilazione degli script PostGIS.</refpurpose>"
#. Tag: funcprototype
#: reference_management.xml:531
msgid ""
"<funcdef>text <function>PostGIS_Scripts_Build_Date</function></funcdef> "
"<paramdef></paramdef>"
-msgstr ""
+msgstr "<funcdef>text <function>PostGIS_Scripts_Build_Date</function></funcdef> <paramdef></paramdef>"
#. Tag: para
#: reference_management.xml:542
#, no-c-format
msgid "<para>Returns build date of the PostGIS scripts.</para>"
-msgstr ""
+msgstr "<para>Riporta la data della compilazione degli script PostGIS.</para>"
#. Tag: para
#: reference_management.xml:544
#, no-c-format
msgid "Availability: 1.0.0RC1"
-msgstr ""
+msgstr "Disponibilità: dalla versione 1.0.0RC1"
#. Tag: programlisting
#: reference_management.xml:550
"-------------------------\n"
" 2007-08-18 09:09:26\n"
"(1 row)"
-msgstr ""
+msgstr "SELECT PostGIS_Scripts_Build_Date();\n postgis_scripts_build_date\n-------------------------\n 2007-08-18 09:09:26\n(1 row)"
#. Tag: refname
#: reference_management.xml:566
#, no-c-format
msgid "PostGIS_Scripts_Installed"
-msgstr ""
+msgstr "PostGIS_Scripts_Installed"
#. Tag: refpurpose
#: reference_management.xml:568
msgid ""
"<refpurpose>Returns version of the postgis scripts installed in this "
"database.</refpurpose>"
-msgstr ""
+msgstr "<refpurpose>Riporta il numero della versione degli script PostGIS installati del database.</refpurpose>"
#. Tag: funcprototype
#: reference_management.xml:574
msgid ""
"<funcdef>text <function>PostGIS_Scripts_Installed</function></funcdef> "
"<paramdef></paramdef>"
-msgstr ""
+msgstr "<funcdef>text <function>PostGIS_Scripts_Installed</function></funcdef> <paramdef></paramdef>"
#. Tag: para
#: reference_management.xml:585
#, no-c-format
msgid ""
-"<para>Returns version of the postgis scripts installed in this database.</"
-"para>"
-msgstr ""
+"<para>Returns version of the postgis scripts installed in this "
+"database.</para>"
+msgstr "<para>Riporta il numero della versione degli script PostGIS installati del database.</para>"
#. Tag: para
#: reference_management.xml:589
#, no-c-format
msgid ""
-"If the output of this function doesn't match the output of <xref linkend="
-"\"PostGIS_Scripts_Released\"/> you probably missed to properly upgrade an "
-"existing database. See the <link linkend=\"upgrading\">Upgrading</link> "
-"section for more info."
-msgstr ""
+"If the output of this function doesn't match the output of <xref "
+"linkend=\"PostGIS_Scripts_Released\"/> you probably missed to properly "
+"upgrade an existing database. See the <link "
+"linkend=\"upgrading\">Upgrading</link> section for more info."
+msgstr "Se l'output di questa funzione non corrisponde all'output di <xref linkend=\"PostGIS_Scripts_Released\"/>, probabilmente gli script installati nel database devono essere aggiornati. Vedi la sezione <link linkend=\"upgrading\">Aggiornamento</link> per più informazioni."
#. Tag: para
#: reference_management.xml:596 reference_management.xml:642
#, no-c-format
msgid "Availability: 0.9.0"
-msgstr ""
+msgstr "Disponibilità: dalla versione 0.9.0"
#. Tag: programlisting
#: reference_management.xml:602
"-------------------------\n"
" 1.5.0SVN\n"
"(1 row)"
-msgstr ""
+msgstr "SELECT PostGIS_Scripts_Installed();\n postgis_scripts_installed\n-------------------------\n 1.5.0SVN\n(1 row)"
#. Tag: para
#: reference_management.xml:608
#, no-c-format
msgid ""
-", <xref linkend=\"PostGIS_Scripts_Released\"/>, <xref linkend="
-"\"PostGIS_Version\"/>"
-msgstr ""
+", <xref linkend=\"PostGIS_Scripts_Released\"/>, <xref "
+"linkend=\"PostGIS_Version\"/>"
+msgstr ", <xref linkend=\"PostGIS_Scripts_Released\"/>, <xref linkend=\"PostGIS_Version\"/>"
#. Tag: refname
#: reference_management.xml:614
#, no-c-format
msgid "PostGIS_Scripts_Released"
-msgstr ""
+msgstr "PostGIS_Scripts_Released"
#. Tag: refpurpose
#: reference_management.xml:616
msgid ""
"<refpurpose>Returns the version number of the postgis.sql script released "
"with the installed postgis lib.</refpurpose>"
-msgstr ""
+msgstr "<refpurpose>Riporta il numero di versione dello script postgis.sql rilasciato con la libreria PostGIS installata.</refpurpose>"
#. Tag: funcprototype
#: reference_management.xml:622
msgid ""
"<funcdef>text <function>PostGIS_Scripts_Released</function></funcdef> "
"<paramdef></paramdef>"
-msgstr ""
+msgstr "<funcdef>text <function>PostGIS_Scripts_Released</function></funcdef> <paramdef></paramdef>"
#. Tag: para
#: reference_management.xml:633
#, no-c-format
msgid ""
-"<para>Returns the version number of the postgis.sql script released with the "
-"installed postgis lib.</para>"
-msgstr ""
+"<para>Returns the version number of the postgis.sql script released with the"
+" installed postgis lib.</para>"
+msgstr "<para>Riporta il numero di versione dello script postgis.sql rilasciato con la libreria PostGIS installata.</para>"
#. Tag: para
#: reference_management.xml:637
msgid ""
"Starting with version 1.1.0 this function returns the same value of <xref "
"linkend=\"PostGIS_Lib_Version\"/>. Kept for backward compatibility."
-msgstr ""
+msgstr "Dalla versione 1.1.0 questa funzione ritorna lo stesso valore di <xref linkend=\"PostGIS_Lib_Version\"/>. Viene mantenuta per retrocompatibilità."
#. Tag: programlisting
#: reference_management.xml:648
"-------------------------\n"
" 1.3.4SVN\n"
"(1 row)"
-msgstr ""
+msgstr "SELECT PostGIS_Scripts_Released();\n postgis_scripts_released\n-------------------------\n 1.3.4SVN\n(1 row)"
#. Tag: para
#: reference_management.xml:654
#, no-c-format
msgid ""
-", <xref linkend=\"PostGIS_Scripts_Installed\"/>, <xref linkend="
-"\"PostGIS_Lib_Version\"/>"
-msgstr ""
+", <xref linkend=\"PostGIS_Scripts_Installed\"/>, <xref "
+"linkend=\"PostGIS_Lib_Version\"/>"
+msgstr ", <xref linkend=\"PostGIS_Scripts_Installed\"/>, <xref linkend=\"PostGIS_Lib_Version\"/>"
#. Tag: refname
#: reference_management.xml:660
#, no-c-format
msgid "PostGIS_Version"
-msgstr ""
+msgstr "PostGIS_Version"
#. Tag: refpurpose
#: reference_management.xml:662
#, no-c-format
msgid ""
-"<refpurpose>Returns PostGIS version number and compile-time options.</"
-"refpurpose>"
-msgstr ""
+"<refpurpose>Returns PostGIS version number and compile-time "
+"options.</refpurpose>"
+msgstr "<refpurpose>Riporta il numero della versione di PostGIS e le opzioni della compilazione.</refpurpose>"
#. Tag: funcprototype
#: reference_management.xml:668
#, no-c-format
msgid ""
-"<funcdef>text <function>PostGIS_Version</function></funcdef> <paramdef></"
-"paramdef>"
-msgstr ""
+"<funcdef>text <function>PostGIS_Version</function></funcdef> "
+"<paramdef></paramdef>"
+msgstr "<funcdef>text <function>PostGIS_Version</function></funcdef> <paramdef></paramdef>"
#. Tag: para
#: reference_management.xml:679
#, no-c-format
msgid "<para>Returns PostGIS version number and compile-time options.</para>"
-msgstr ""
+msgstr "<para>Riporta il numero della versione di PostGIS e le opzioni della compilazione.</para>"
#. Tag: programlisting
#: reference_management.xml:685
"---------------------------------------\n"
" 1.3 USE_GEOS=1 USE_PROJ=1 USE_STATS=1\n"
"(1 row)"
-msgstr ""
+msgstr "SELECT PostGIS_Version();\n postgis_version\n---------------------------------------\n 1.3 USE_GEOS=1 USE_PROJ=1 USE_STATS=1\n(1 row)"
#. Tag: para
#: reference_management.xml:691
#, no-c-format
msgid ""
-", <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref linkend="
-"\"PostGIS_Lib_Version\"/>, <xref linkend=\"PostGIS_LibXML_Version\"/>, <xref "
+", <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref "
+"linkend=\"PostGIS_Lib_Version\"/>, <xref "
+"linkend=\"PostGIS_LibXML_Version\"/>, <xref "
"linkend=\"PostGIS_PROJ_Version\"/>"
-msgstr ""
+msgstr ", <xref linkend=\"PostGIS_GEOS_Version\"/>, <xref linkend=\"PostGIS_Lib_Version\"/>, <xref linkend=\"PostGIS_LibXML_Version\"/>, <xref linkend=\"PostGIS_PROJ_Version\"/>"
#. Tag: refname
#: reference_management.xml:701
#, no-c-format
msgid "Populate_Geometry_Columns"
-msgstr ""
+msgstr "Populate_Geometry_Columns"
#. Tag: refpurpose
#: reference_management.xml:703
#, no-c-format
msgid ""
-"Ensures geometry columns are defined with type modifiers or have appropriate "
-"spatial constraints This ensures they will be registered correctly in "
+"Ensures geometry columns are defined with type modifiers or have appropriate"
+" spatial constraints This ensures they will be registered correctly in "
"<varname>geometry_columns</varname> view. By default will convert all "
"geometry columns with no type modifier to ones with type modifiers. To get "
"old behavior set <varname>use_typmod=false</varname>"
-msgstr ""
+msgstr "Si accerta che le colonne geometry siano definite con typemod oppure abbiano gli appropriati vincoli spaziali e conseguentemente siano correttamente registrate nella vista <varname>geometry_columns</varname>. Per default la funzione converte tutte le colonne geometry definite senza typemod in geometry con typemod. Per ottenere il vecchio meccanismo con i vincoli spaziali si può settare la variabile <varname>use_typmod=false</varname>"
#. Tag: funcsynopsis
#: reference_management.xml:709
#, no-c-format
msgid ""
-"<funcprototype> <funcdef>text <function>Populate_Geometry_Columns</"
-"function></funcdef> <paramdef><type>boolean </type> "
+"<funcprototype> <funcdef>text "
+"<function>Populate_Geometry_Columns</function></funcdef> "
+"<paramdef><type>boolean </type> "
"<parameter>use_typmod=true</parameter></paramdef> </funcprototype> "
-"<funcprototype> <funcdef>int <function>Populate_Geometry_Columns</function></"
-"funcdef> <paramdef><type>oid</type> <parameter>relation_oid</parameter></"
-"paramdef> <paramdef><type>boolean </type> <parameter>use_typmod=true</"
-"parameter></paramdef> </funcprototype>"
-msgstr ""
+"<funcprototype> <funcdef>int "
+"<function>Populate_Geometry_Columns</function></funcdef> "
+"<paramdef><type>oid</type> <parameter>relation_oid</parameter></paramdef> "
+"<paramdef><type>boolean </type> "
+"<parameter>use_typmod=true</parameter></paramdef> </funcprototype>"
+msgstr "<funcprototype> <funcdef>text <function>Populate_Geometry_Columns</function></funcdef> <paramdef><type>boolean </type> <parameter>use_typmod=true</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>int <function>Populate_Geometry_Columns</function></funcdef> <paramdef><type>oid</type> <parameter>relation_oid</parameter></paramdef> <paramdef><type>boolean </type> <parameter>use_typmod=true</parameter></paramdef> </funcprototype>"
#. Tag: para
#: reference_management.xml:728
"Ensures geometry columns have appropriate type modifiers or spatial "
"constraints to ensure they are registered correctly in "
"<varname>geometry_columns</varname> table."
-msgstr ""
+msgstr "Si accerta che le colonne geometry siano definite con typemod oppure abbiano gli appropriati vincoli spaziali e conseguentemente siano correttamente registrate nella vista <varname>geometry_columns</varname>."
#. Tag: para
#: reference_management.xml:730
"where each child table may have different geometry type, the old check "
"constraint behavior is still supported. If you need the old behavior, you "
"need to pass in the new optional argument as false "
-"<varname>use_typmod=false</varname>. When this is done geometry columns will "
-"be created with no type modifiers but will have 3 constraints defined. In "
+"<varname>use_typmod=false</varname>. When this is done geometry columns will"
+" be created with no type modifiers but will have 3 constraints defined. In "
"particular, this means that every geometry column belonging to a table has "
"at least three constraints:"
-msgstr ""
+msgstr "Per retrocompatibilità e per particolari casi come tabelle con ereditarietà, dove le tabelle che ereditano potrebbero avere altri tipi di geometria, il meccanismo con i vincoli spaziali è ancora supportato. Se questo dovesse essere necessario, è sufficiente passare come false il nuovo argomento opzionale <varname>use_typmod=false</varname>. In questo modo la colonna geometry verrà creata senza type modifier e avrà 3 vincoli definiti. In particolare questo significa che ogni colonna geometry avrà almeno 3 vincoli spaziali:"
#. Tag: para
#: reference_management.xml:738
msgid ""
"<varname>enforce_dims_the_geom</varname> - ensures every geometry has the "
"same dimension (see <xref linkend=\"ST_NDims\"/>)"
-msgstr ""
+msgstr "<varname>enforce_dims_the_geom</varname> - assicura che tutte le geometrie hanno la stessa dimensione (vedi <xref linkend=\"ST_NDims\"/>)"
#. Tag: para
#: reference_management.xml:744
msgid ""
"<varname>enforce_geotype_the_geom</varname> - ensures every geometry is of "
"the same type (see <xref linkend=\"GeometryType\"/>)"
-msgstr ""
+msgstr "<varname>enforce_geotype_the_geom</varname> - assicura che tutte le geometrie sono dello stesso tipo (vedi <xref linkend=\"GeometryType\"/>)"
#. Tag: para
#: reference_management.xml:750
msgid ""
"<varname>enforce_srid_the_geom</varname> - ensures every geometry is in the "
"same projection (see <xref linkend=\"ST_SRID\"/>)"
-msgstr ""
+msgstr "<varname>enforce_srid_the_geom</varname> - - assicura che tutte le geometrie hanno la stessa proiezione (vedi <xref linkend=\"ST_SRID\"/>)"
#. Tag: para
#: reference_management.xml:756
"If a table <varname>oid</varname> is provided, this function tries to "
"determine the srid, dimension, and geometry type of all geometry columns in "
"the table, adding constraints as necessary. If successful, an appropriate "
-"row is inserted into the geometry_columns table, otherwise, the exception is "
-"caught and an error notice is raised describing the problem."
-msgstr ""
+"row is inserted into the geometry_columns table, otherwise, the exception is"
+" caught and an error notice is raised describing the problem."
+msgstr "Se alla funzione viene passato l' <varname>oid</varname> di una tabella, questa cerca di determinare srid, dimensione e tipo della geometria di tutte le colonne geometry della tabella, aggiungendo i vincoli se necessario. In caso di successo, una riga viene inserita nella tabella geometry_columns, altrimenti viene lanciata un'eccezione con un messaggio che descrive il problema."
#. Tag: para
#: reference_management.xml:763
"geometries in the view, inserting appropriate entries into the "
"<varname>geometry_columns</varname> table, but nothing is done to enforce "
"constraints."
-msgstr ""
+msgstr "Se alla funzione viene passato l'<varname>oid</varname> di una vista, questa cerca di determinare srid, dimensione e tipo della geometria di tutte le colonne geometry della vista, inserendo le appropriate righe nella tabella geometry_columns. I vincoli spaziali non vengono controllati né definiti."
#. Tag: para
#: reference_management.xml:769
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 "
"<varname>geometry_columns</varname> table. The parameterized version simply "
-"returns the number of rows inserted into the <varname>geometry_columns</"
-"varname> table."
-msgstr ""
+"returns the number of rows inserted into the "
+"<varname>geometry_columns</varname> table."
+msgstr "La variante senza parametri è un semplice wrapper per la variante parametrizzata, che prima svuota e poi riempie la tabella geometry_columns per ogni vista e tabella spaziale nel database, aggiungendo gli appropriate vincoli spaziali. La funzione ritorna un sommario con il numero delle colonne geometry trovate e di quelle inserite in <varname>geometry_columns</varname>. La versione parametrizzata ritorna semplicemente il numero di righe inserite nella tabella <varname>geometry_columns</varname>."
#. Tag: para
#: reference_management.xml:777
#, no-c-format
msgid "Availability: 1.4.0"
-msgstr ""
+msgstr "Disponibilità: 1.4.0"
#. Tag: para
#: reference_management.xml:778
"constraints to constrain geometry types. You can still use check constraint "
"behavior instead by using the new <varname>use_typmod</varname> and setting "
"it to false."
-msgstr ""
+msgstr "Cambiamento nella versione 2.0.0: Per default la funzione utilizza ora type modifier invece di controllare i vincoli spaziali. il meccanismo con i vincoli può essere comunque attivato passando il parametro <varname>use_typmod</varname> e settandolo come false."
#. Tag: para
#: reference_management.xml:780
"Enhanced: 2.0.0 <varname>use_typmod</varname> optional argument was "
"introduced that allows controlling if columns are created with typmodifiers "
"or with check constraints."
-msgstr ""
+msgstr "Miglioramento nelle version 2.0.0: Il parametro opzionale <varname>use_typmod</varname> è stato introdotto per permettere di controllare se le colonne devono essere create con typmodifier oppure con i vincoli spaziali."
#. Tag: programlisting
#: reference_management.xml:786
#, no-c-format
msgid ""
"CREATE TABLE public.myspatial_table(gid serial, geom geometry);\n"
-"INSERT INTO myspatial_table(geom) VALUES(ST_GeomFromText('LINESTRING(1 2, 3 "
-"4)',4326) );\n"
-"-- This will now use typ modifiers. For this to work, there must exist "
-"data\n"
+"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"
"\\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 ""
+msgstr "CREATE TABLE public.myspatial_table(gid serial, geom geometry);\nINSERT INTO myspatial_table(geom) VALUES(ST_GeomFromText('LINESTRING(1 2, 3 4)',4326) );\n-- Il comando seguente usa typ modifiers. Per poter funzionare devono essere presenti dati nella tabella.\nSELECT Populate_Geometry_Columns('public.myspatial_table'::regclass);\n\npopulate_geometry_columns\n--------------------------\n 1\n \n \n\\d myspatial_table\n\n Table \"public.myspatial_table\"\n Column | Type | Modifiers \n--------+---------------------------+---------------------------------------------------------------\n gid | integer | not null default nextval('myspatial_table_gid_seq'::regclass)\n geom | geometry(LineString,4326) |"
#. Tag: programlisting
#: reference_management.xml:788
#, no-c-format
msgid ""
-"-- This will change the geometry columns to use constraints if they are not "
-"typmod or have constraints already. \n"
+"-- 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 ""
+msgstr "-- Il comando seguente modificherà le colonne geometry usando i vincoli spaziali se non sono state definite con typmod oppure non hanno già i vincoli spaziali.\n--Per poter funzionare devono essere presenti dati nella tabella.\nCREATE TABLE public.myspatial_table_cs(gid serial, geom geometry);\nINSERT INTO myspatial_table_cs(geom) VALUES(ST_GeomFromText('LINESTRING(1 2, 3 4)',4326) );\nSELECT Populate_Geometry_Columns('public.myspatial_table_cs'::regclass, false);\npopulate_geometry_columns\n--------------------------\n 1\n\\d myspatial_table_cs\n\n Table \"public.myspatial_table_cs\"\n Column | Type | Modifiers \n--------+----------+------------------------------------------------------------------\n gid | integer | not null default nextval('myspatial_table_cs_gid_seq'::regclass)\n geom | geometry | \nCheck constraints:\n \"enforce_dims_geom\" CHECK (st_ndims(geom) = 2)\n \"enforce_geotype_geom\" CHECK (geometrytype(geom) = 'LINESTRING'::text OR geom IS NULL)\n \"enforce_srid_geom\" CHECK (st_srid(geom) = 4326)"
#. Tag: refname
#: reference_management.xml:803
#, no-c-format
msgid "UpdateGeometrySRID"
-msgstr ""
+msgstr "UpdateGeometrySRID"
#. Tag: refpurpose
#: reference_management.xml:805
msgid ""
"Updates the SRID of all features in a geometry column, geometry_columns "
"metadata and srid table constraint"
-msgstr ""
+msgstr "Aggiorna lo SRID di tutti i record in una colonna geometry. Vengono aggiornati anche geometry_columns e il vincolo SRID della colonna."
#. Tag: funcsynopsis
#: reference_management.xml:810
#, no-c-format
msgid ""
-"<funcprototype> <funcdef>text <function>UpdateGeometrySRID</function></"
-"funcdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></"
-"paramdef> <paramdef><type>varchar </type> <parameter>column_name</"
-"parameter></paramdef> <paramdef><type>integer </type> <parameter>srid</"
-"parameter></paramdef> </funcprototype> <funcprototype> <funcdef>text "
-"<function>UpdateGeometrySRID</function></funcdef> <paramdef><type>varchar </"
-"type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar "
-"</type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar "
-"</type> <parameter>column_name</parameter></paramdef> "
-"<paramdef><type>integer </type> <parameter>srid</parameter></paramdef> </"
-"funcprototype> <funcprototype> <funcdef>text <function>UpdateGeometrySRID</"
-"function></funcdef> <paramdef><type>varchar </type> <parameter>catalog_name</"
-"parameter></paramdef> <paramdef><type>varchar </type> "
-"<parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </"
-"type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </"
-"type> <parameter>column_name</parameter></paramdef> <paramdef><type>integer "
-"</type> <parameter>srid</parameter></paramdef> </funcprototype>"
-msgstr ""
+"<funcprototype> <funcdef>text "
+"<function>UpdateGeometrySRID</function></funcdef> <paramdef><type>varchar "
+"</type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar"
+" </type> <parameter>column_name</parameter></paramdef> "
+"<paramdef><type>integer </type> <parameter>srid</parameter></paramdef> "
+"</funcprototype> <funcprototype> <funcdef>text "
+"<function>UpdateGeometrySRID</function></funcdef> <paramdef><type>varchar "
+"</type> <parameter>schema_name</parameter></paramdef> "
+"<paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef>"
+" <paramdef><type>varchar </type> "
+"<parameter>column_name</parameter></paramdef> <paramdef><type>integer "
+"</type> <parameter>srid</parameter></paramdef> </funcprototype> "
+"<funcprototype> <funcdef>text "
+"<function>UpdateGeometrySRID</function></funcdef> <paramdef><type>varchar "
+"</type> <parameter>catalog_name</parameter></paramdef> "
+"<paramdef><type>varchar </type> "
+"<parameter>schema_name</parameter></paramdef> <paramdef><type>varchar "
+"</type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar"
+" </type> <parameter>column_name</parameter></paramdef> "
+"<paramdef><type>integer </type> <parameter>srid</parameter></paramdef> "
+"</funcprototype>"
+msgstr "<funcprototype> <funcdef>text <function>UpdateGeometrySRID</function></funcdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> <paramdef><type>integer </type> <parameter>srid</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>text <function>UpdateGeometrySRID</function></funcdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> <paramdef><type>integer </type> <parameter>srid</parameter></paramdef> </funcprototype> <funcprototype> <funcdef>text <function>UpdateGeometrySRID</function></funcdef> <paramdef><type>varchar </type> <parameter>catalog_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>schema_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>table_name</parameter></paramdef> <paramdef><type>varchar </type> <parameter>column_name</parameter></paramdef> <paramdef><type>integer </type> <parameter>srid</parameter></paramdef> </funcprototype>"
#. Tag: para
#: reference_management.xml:864
"Updates the SRID of all features in a geometry column, updating constraints "
"and reference in geometry_columns. Note: uses current_schema() on schema-"
"aware pgsql installations if schema is not provided."
-msgstr ""
+msgstr "Aggiorna lo SRID di tutti i record in una colonna geometry, aggiornando anche geometry_columns e il vincolo SRID della colonna. Usa la funzione current_schema() se lo schema non è passato come argomento."
# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# Tommaso Di Bucchianico, 2013
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2013-05-12 08:39+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
+"PO-Revision-Date: 2013-12-09 19:33+0000\n"
+"Last-Translator: Tommaso Di Bucchianico\n"
+"Language-Team: Italian (Italy) (http://www.transifex.com/projects/p/postgis-1/language/it_IT/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: it_IT\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. Tag: title
#: reference_sfcgal.xml:4
#, no-c-format
msgid "Using SFCGAL Advanced 2D/3D functions"
-msgstr ""
+msgstr "Funzioni SFCGAL 2D/3D avanzate"
#. Tag: para
#: reference_sfcgal.xml:5
#, no-c-format
msgid "TODO Introduction part"
-msgstr ""
+msgstr "TODO Introduction part"
#. Tag: para
#: reference_sfcgal.xml:8
#, no-c-format
msgid "TODO Install part"
-msgstr ""
+msgstr "TODO Install part"
#. Tag: refname
#: reference_sfcgal.xml:14
#, no-c-format
msgid "ST_Extrude"
-msgstr ""
+msgstr "ST_Extrude"
#. Tag: refpurpose
#: reference_sfcgal.xml:16
#, no-c-format
msgid "Extrude a surface to a related volume"
-msgstr ""
+msgstr "Estrude una superficie a volume"
#. Tag: funcprototype
#: reference_sfcgal.xml:21
#, no-c-format
-msgid "<funcdef>geometry <function>ST_Extrude</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef> <paramdef><type>float</type> <parameter>x</parameter></paramdef> <paramdef><type>float</type> <parameter>y</parameter></paramdef> <paramdef><type>float</type> <parameter>z</parameter></paramdef>"
-msgstr ""
+msgid ""
+"<funcdef>geometry <function>ST_Extrude</function></funcdef> "
+"<paramdef><type>geometry</type> <parameter>geom</parameter></paramdef> "
+"<paramdef><type>float</type> <parameter>x</parameter></paramdef> "
+"<paramdef><type>float</type> <parameter>y</parameter></paramdef> "
+"<paramdef><type>float</type> <parameter>z</parameter></paramdef>"
+msgstr "<funcdef>geometry <function>ST_Extrude</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef> <paramdef><type>float</type> <parameter>x</parameter></paramdef> <paramdef><type>float</type> <parameter>y</parameter></paramdef> <paramdef><type>float</type> <parameter>z</parameter></paramdef>"
#. Tag: title
-#: reference_sfcgal.xml:32 reference_sfcgal.xml:61 reference_sfcgal.xml:90 reference_sfcgal.xml:119 reference_sfcgal.xml:148 reference_sfcgal.xml:177 reference_sfcgal.xml:206
+#: reference_sfcgal.xml:32 reference_sfcgal.xml:61 reference_sfcgal.xml:90
+#: reference_sfcgal.xml:119 reference_sfcgal.xml:148 reference_sfcgal.xml:177
+#: reference_sfcgal.xml:206
#, no-c-format
msgid "Description"
-msgstr ""
+msgstr "Descrizione"
#. Tag: para
-#: reference_sfcgal.xml:34 reference_sfcgal.xml:63 reference_sfcgal.xml:92 reference_sfcgal.xml:121 reference_sfcgal.xml:150 reference_sfcgal.xml:179 reference_sfcgal.xml:208
+#: reference_sfcgal.xml:34 reference_sfcgal.xml:63 reference_sfcgal.xml:92
+#: reference_sfcgal.xml:121 reference_sfcgal.xml:150 reference_sfcgal.xml:179
+#: reference_sfcgal.xml:208
#, no-c-format
msgid "Availability"
-msgstr ""
+msgstr "Disponibilità"
#. Tag: para
-#: reference_sfcgal.xml:35 reference_sfcgal.xml:64 reference_sfcgal.xml:93 reference_sfcgal.xml:122 reference_sfcgal.xml:151 reference_sfcgal.xml:180 reference_sfcgal.xml:209
+#: reference_sfcgal.xml:35 reference_sfcgal.xml:64 reference_sfcgal.xml:93
+#: reference_sfcgal.xml:122 reference_sfcgal.xml:151 reference_sfcgal.xml:180
+#: reference_sfcgal.xml:209
#, no-c-format
msgid "&sfcgal_required;"
-msgstr ""
+msgstr "&sfcgal_required;"
#. Tag: para
-#: reference_sfcgal.xml:36 reference_sfcgal.xml:65 reference_sfcgal.xml:94 reference_sfcgal.xml:123 reference_sfcgal.xml:152 reference_sfcgal.xml:181 reference_sfcgal.xml:210
+#: reference_sfcgal.xml:36 reference_sfcgal.xml:65 reference_sfcgal.xml:94
+#: reference_sfcgal.xml:123 reference_sfcgal.xml:152 reference_sfcgal.xml:181
+#: reference_sfcgal.xml:210
#, no-c-format
msgid "&Z_support;"
-msgstr ""
+msgstr "&Z_support;"
#. Tag: para
-#: reference_sfcgal.xml:37 reference_sfcgal.xml:66 reference_sfcgal.xml:95 reference_sfcgal.xml:124 reference_sfcgal.xml:153 reference_sfcgal.xml:182 reference_sfcgal.xml:211
+#: reference_sfcgal.xml:37 reference_sfcgal.xml:66 reference_sfcgal.xml:95
+#: reference_sfcgal.xml:124 reference_sfcgal.xml:153 reference_sfcgal.xml:182
+#: reference_sfcgal.xml:211
#, no-c-format
msgid "&P_support;"
-msgstr ""
+msgstr "&P_support;"
#. Tag: para
-#: reference_sfcgal.xml:38 reference_sfcgal.xml:67 reference_sfcgal.xml:96 reference_sfcgal.xml:125 reference_sfcgal.xml:154 reference_sfcgal.xml:183 reference_sfcgal.xml:212
+#: reference_sfcgal.xml:38 reference_sfcgal.xml:67 reference_sfcgal.xml:96
+#: reference_sfcgal.xml:125 reference_sfcgal.xml:154 reference_sfcgal.xml:183
+#: reference_sfcgal.xml:212
#, no-c-format
msgid "&T_support;"
-msgstr ""
+msgstr "&T_support;"
#. Tag: refname
#: reference_sfcgal.xml:46
#, no-c-format
msgid "ST_StraightSkeleton"
-msgstr ""
+msgstr "ST_StraightSkeleton"
#. Tag: refpurpose
#: reference_sfcgal.xml:48
#. Tag: funcprototype
#: reference_sfcgal.xml:53
#, no-c-format
-msgid "<funcdef>geometry <function>ST_StraightSkeleton</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
-msgstr ""
+msgid ""
+"<funcdef>geometry <function>ST_StraightSkeleton</function></funcdef> "
+"<paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
+msgstr "<funcdef>geometry <function>ST_StraightSkeleton</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
#. Tag: refname
#: reference_sfcgal.xml:75
#, no-c-format
msgid "ST_IsPlanar"
-msgstr ""
+msgstr "ST_IsPlanar"
#. Tag: refpurpose
#: reference_sfcgal.xml:77
#, no-c-format
msgid "Check if a surface is or not planar"
-msgstr ""
+msgstr "Verifica se una superficie è planare o meno."
#. Tag: funcprototype
#: reference_sfcgal.xml:82
#, no-c-format
-msgid "<funcdef>boolean <function>ST_IsPlanar</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
-msgstr ""
+msgid ""
+"<funcdef>boolean <function>ST_IsPlanar</function></funcdef> "
+"<paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
+msgstr "<funcdef>boolean <function>ST_IsPlanar</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
#. Tag: refname
#: reference_sfcgal.xml:104
#, no-c-format
msgid "ST_Orientation"
-msgstr ""
+msgstr "ST_Orientation"
#. Tag: refpurpose
#: reference_sfcgal.xml:106
#, no-c-format
msgid "Determine surface orientation"
-msgstr ""
+msgstr "Determina l'orientazione di una superficie."
#. Tag: funcprototype
#: reference_sfcgal.xml:111
#, no-c-format
-msgid "<funcdef>integer <function>ST_Orientation</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
-msgstr ""
+msgid ""
+"<funcdef>integer <function>ST_Orientation</function></funcdef> "
+"<paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
+msgstr "<funcdef>integer <function>ST_Orientation</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
#. Tag: refname
#: reference_sfcgal.xml:133
#, no-c-format
msgid "ST_ForceLHR"
-msgstr ""
+msgstr "ST_ForceLHR"
#. Tag: refpurpose
#: reference_sfcgal.xml:135
#, no-c-format
msgid "Force LHR orientation"
-msgstr ""
+msgstr "Forza l'orientazione di tipo LHR"
#. Tag: funcprototype
#: reference_sfcgal.xml:140
#, no-c-format
-msgid "<funcdef>geometry <function>ST_ForceLHR</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
-msgstr ""
+msgid ""
+"<funcdef>geometry <function>ST_ForceLHR</function></funcdef> "
+"<paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
+msgstr "<funcdef>geometry <function>ST_ForceLHR</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
#. Tag: refname
#: reference_sfcgal.xml:161
#, no-c-format
msgid "ST_MinkowskiSum"
-msgstr ""
+msgstr "ST_MinkowskiSum"
#. Tag: refpurpose
#: reference_sfcgal.xml:163
#, no-c-format
msgid "Perform Minkowski sum"
-msgstr ""
+msgstr "Effettua la somma di Minkowski."
#. Tag: funcprototype
#: reference_sfcgal.xml:168
#, no-c-format
-msgid "<funcdef>geometry <function>ST_Minkowski</function></funcdef> <paramdef><type>geometry</type> <parameter>geom1</parameter></paramdef> <paramdef><type>geometry</type> <parameter>geom2</parameter></paramdef>"
-msgstr ""
+msgid ""
+"<funcdef>geometry <function>ST_Minkowski</function></funcdef> "
+"<paramdef><type>geometry</type> <parameter>geom1</parameter></paramdef> "
+"<paramdef><type>geometry</type> <parameter>geom2</parameter></paramdef>"
+msgstr "<funcdef>geometry <function>ST_Minkowski</function></funcdef> <paramdef><type>geometry</type> <parameter>geom1</parameter></paramdef> <paramdef><type>geometry</type> <parameter>geom2</parameter></paramdef>"
#. Tag: refname
#: reference_sfcgal.xml:191
#, no-c-format
msgid "ST_Tesselate"
-msgstr ""
+msgstr "ST_Tesselate"
#. Tag: refpurpose
#: reference_sfcgal.xml:193
#, no-c-format
msgid "Perform surface Tesselation"
-msgstr ""
+msgstr "Effettua tassellazione di una superficie"
#. Tag: funcprototype
#: reference_sfcgal.xml:198
#, no-c-format
-msgid "<funcdef>geometry <function>ST_Tesselate</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
-msgstr ""
-
+msgid ""
+"<funcdef>geometry <function>ST_Tesselate</function></funcdef> "
+"<paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
+msgstr "<funcdef>geometry <function>ST_Tesselate</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# Tommaso Di Bucchianico, 2013
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 21:04+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2013-12-01 05:50+0000\n"
+"Last-Translator: Tommaso Di Bucchianico\n"
+"Language-Team: Italian (Italy) (http://www.transifex.com/projects/p/postgis-1/language/it_IT/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: it_IT\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. Tag: para
#: reference_type.xml:5
"This section lists the PostgreSQL data types installed by PostGIS. Note we "
"describe the casting behavior of these which is very important especially "
"when designing your own functions."
-msgstr ""
+msgstr "Questa sezione illustra i tipi di dati di PostgreSQL che vengono installati da Postgis. Vengono illustrati anche i metodi per eseguire il cast tra diversi tipi, cosa particolarmente importante per la realizzazione di funzioni proprie."
#. Tag: para
#: reference_type.xml:8
"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 ""
+msgstr "Effettuare il cast significa forzare un tipo in un altro tipo di dato. PostgreSQL è tra i pochi database che offrono la possibilità di definire comportamento di casting per tipi personalizzati e le funzioni usate per il casting. Un cast può essere definito come automatico: non è necessario utilizzare la funzione CAST(myfoo As otherfootype) oppure myfoo::otherfootype se si esegue una funzione che supporta unicamente il tipo otherfootype. In questo caso il cast avverrà automaticamente."
#. Tag: para
#: reference_type.xml:13
msgid ""
"The danger of relying on automatic cast behavior is when you have an "
"overloaded function say one that takes a box2d and one that takes a box3d "
-"but no geometry. What happens is that both functions are equally good to use "
-"with geometry since geometry has an autocast for both -- so you end up with "
-"an ambiguous function error. To force PostgreSQL to choose, you do a CAST"
-"(mygeom As box3d) or mygeom::box3d."
-msgstr ""
+"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 "Un rischio dell'usare un cast automatico può esserci quando si ha una funzione sovraccaricata, per esempio una funzione che accetta come argomento un box2d e un'altra che accetta un box3d ma nessuna che accetti un geometry. In questo caso le due funzioni possono essere utilizzate con un tipo geometry, perché geometry supporta il cast automatico verso box2d e box3d, e si avrà quindi un errore che indica che la funzione è ambigua. Per forzare PostgreSQL ad effettuare la scelta giusta bisogna effettuare un cast specifico con CAST(mygeom AS box3d) oppure mygeom::box3d"
#. Tag: para
#: reference_type.xml:17
"<emphasis>At least as of PostgreSQL 8.3</emphasis> - Everything can be CAST "
"to text (presumably because of the magical unknown type), so no defined "
"CASTS for that need to be present for you to CAST an object to text."
-msgstr ""
+msgstr "<emphasis>A partire dalla versione PostgreSQL 8.3</emphasis> - È possibile effettuare il CAST di ogni tipo a \"text\" (presumibilmente per merito del magico tipo \"unknown\"), quindi non è necessario definire esplicitamente il CAST di un oggetto a \"text\"."
#. Tag: title
#: reference_type.xml:20
#, no-c-format
msgid "PostgreSQL PostGIS Geometry/Geography/Box Types"
-msgstr ""
+msgstr "PostgreSQL PostGIS tipi Geometry/Geography/Box "
#. Tag: refname
#: reference_type.xml:24
#, no-c-format
msgid "<refname>box2d</refname>"
-msgstr ""
+msgstr "<refname>box2d</refname>"
#. Tag: refpurpose
#: reference_type.xml:25
msgid ""
"A box composed of x min, ymin, xmax, ymax. Often used to return the 2d "
"enclosing box of a geometry."
-msgstr ""
-"Un rettangolo composto da xmin, ymin, xmax, ymax. "
-"Spesso usato per restituire il rettangolo che racchiude una geometria."
+msgstr "Un rettangolo composto dalle coordinate xmin,ymin,xmax,ymax. Spesso è usato per ritornare l'estensione 2D della geometria."
#. Tag: title
#: reference_type.xml:29 reference_type.xml:40 reference_type.xml:79
"box2d is a spatial data type used to represent the enclosing box of a "
"geometry or set of geometries. ST_Extent in earlier versions prior to "
"PostGIS 1.4 would return a box2d."
-msgstr ""
+msgstr "box2d è un tipo di dato spaziale usato per rappresentare in rettangolo contenente una geometria o un insieme di geometrie. In versioni precedenti Postgis 1.4, la funzione ST_Extent ritorna un box2d."
#. Tag: refname
#: reference_type.xml:35
#, no-c-format
msgid "<refname>box3d</refname>"
-msgstr ""
+msgstr "<refname>box3d</refname>"
#. Tag: refpurpose
#: reference_type.xml:36
msgid ""
"A box composed of x min, ymin, zmin, xmax, ymax, zmax. Often used to return "
"the 3d extent of a geometry or collection of geometries."
-msgstr ""
+msgstr "Un parallelepipedo composto dalle coordinate xmin, ymin, zmin, xmax, ymax, zmax. Spesso usato per ritornare l'estensione 3D di una geometria o di una collezione di geometrie."
#. Tag: para
#: reference_type.xml:41
msgid ""
"box3d is a postgis spatial data type used to represent the enclosing box of "
"a geometry or set of geometries. ST_3DExtent returns a box3d object."
-msgstr ""
+msgstr "box3d è un tipo spaziale di Postgis usato per rappresentare il parallelepipedo contente una geometria o un insieme di geometrie. La funzione ST_3DExtent ritorna un oggetto box3d."
#. Tag: title
#: reference_type.xml:45 reference_type.xml:84 reference_type.xml:160
#, no-c-format
msgid "Casting Behavior"
-msgstr ""
+msgstr "Comportamento in caso di CAST"
#. Tag: para
#: reference_type.xml:46 reference_type.xml:85 reference_type.xml:161
msgid ""
"This section lists the automatic as well as explicit casts allowed for this "
"data type"
-msgstr ""
+msgstr "Questa sezione illustra le modalità di CAST - automatici e espliciti - permessi per questo tipo di dato"
#. Tag: entry
#: reference_type.xml:51 reference_type.xml:90 reference_type.xml:166
#, no-c-format
msgid "Cast To"
-msgstr ""
+msgstr "Cast verso"
#. Tag: entry
#: reference_type.xml:52 reference_type.xml:91 reference_type.xml:167
#, no-c-format
msgid "Behavior"
-msgstr ""
+msgstr "Comportamento"
#. Tag: entry
#: reference_type.xml:55 reference_type.xml:94
#, no-c-format
msgid "<entry>box</entry>"
-msgstr ""
+msgstr "<entry>box</entry>"
#. Tag: entry
#: reference_type.xml:56 reference_type.xml:60 reference_type.xml:64
#: reference_type.xml:107 reference_type.xml:111 reference_type.xml:115
#, no-c-format
msgid "automatic"
-msgstr ""
+msgstr "automatico"
#. Tag: entry
#: reference_type.xml:59 reference_type.xml:98
#, no-c-format
msgid "<entry>box2d</entry>"
-msgstr ""
+msgstr "<entry>box2d</entry>"
#. Tag: entry
#: reference_type.xml:63 reference_type.xml:170
#, no-c-format
msgid "<entry>geometry</entry>"
-msgstr ""
+msgstr "<entry>geometry</entry>"
#. Tag: refname
#: reference_type.xml:74
#, no-c-format
msgid "<refname>geometry</refname>"
-msgstr ""
+msgstr "<entry>geometry</entry>"
#. Tag: refpurpose
#: reference_type.xml:75
#, no-c-format
msgid "Planar spatial data type."
-msgstr ""
+msgstr "Tipi di dati spaziali piani."
#. Tag: para
#: reference_type.xml:80
msgid ""
"geometry is a fundamental postgis spatial data type used to represent a "
"feature in the Euclidean coordinate system."
-msgstr ""
+msgstr "Il tipo di dato \"geometry\" è un fondamentale tipo spaziale di Postgis usato per rappresentare una entità in un sistema di coordinate euclideo. "
#. Tag: entry
#: reference_type.xml:102
#, no-c-format
msgid "<entry>box3d</entry>"
-msgstr ""
+msgstr "<entry>box3d</entry>"
#. Tag: entry
#: reference_type.xml:106
#, no-c-format
msgid "bytea"
-msgstr ""
+msgstr "bytea"
#. Tag: entry
#: reference_type.xml:110
#, no-c-format
msgid "<entry>geography</entry>"
-msgstr ""
+msgstr "<entry>geography</entry>"
#. Tag: entry
#: reference_type.xml:114
#, no-c-format
msgid "text"
-msgstr ""
+msgstr "text"
#. Tag: title
#: reference_type.xml:123 reference_type.xml:143 reference_type.xml:179
#, no-c-format
msgid "See Also"
-msgstr ""
+msgstr "Vedi anche"
#. Tag: refname
#: reference_type.xml:130
#, no-c-format
msgid "geometry_dump"
-msgstr ""
+msgstr "geometry_dump"
#. Tag: refpurpose
#: reference_type.xml:131
"A spatial datatype with two fields - geom (holding a geometry object) and "
"path[] (a 1-d array holding the position of the geometry within the dumped "
"object.)"
-msgstr ""
+msgstr "Un tipo di dato spaziale composto da due campi: geom (contenente un oggetto geometry) e path[] (un array unidimensionale 1-d contenente la posizione della geometria all'interno della collezione)."
#. Tag: para
#: reference_type.xml:137
"navigation path within the dumped geometry to find this element. It is used "
"by the ST_Dump* family of functions as an output type to explode a more "
"complex geometry into its constituent parts and location of parts."
-msgstr ""
+msgstr "geometry_dump è un tipo composto formato da un oggetto geometry, associato al campo .geom, e path[] un array unidimensionale di interi (l'array inizia con 1. Per esempio path[1] ritorna il primo elemento) che definisce il percorso di ogni geometria all'interno della collezione. "
#. Tag: refname
#: reference_type.xml:150
#, no-c-format
msgid "<refname>geography</refname>"
-msgstr ""
+msgstr "<refname>geography</refname>"
#. Tag: refpurpose
#: reference_type.xml:151
#, no-c-format
msgid "Ellipsoidal spatial data type."
-msgstr ""
+msgstr "Tipi spaziali ellissoidi."
#. Tag: para
#: reference_type.xml:156
msgid ""
"geography is a spatial data type used to represent a feature in the round-"
"earth coordinate system."
-msgstr ""
+msgstr "geography è un tipo spaziale usato per rappresentare un'entità in un sistema di coordinate sferico valido per l'intero pianeta."
#. Tag: entry
#: reference_type.xml:171
#, no-c-format
msgid "explicit"
-msgstr ""
+msgstr "Esplicito"
#. Tag: para
#: reference_type.xml:180
#, no-c-format
msgid ", <xref linkend=\"PostGIS_Geography\"/>"
-msgstr ""
+msgstr ", <xref linkend=\"PostGIS_Geography\"/>"
# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# aghisla <a.ghisla@gmail.com>, 2013
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2013-11-28 09:40+0000\n"
+"Last-Translator: aghisla <a.ghisla@gmail.com>\n"
+"Language-Team: Italian (Italy) (http://www.transifex.com/projects/p/postgis-1/language/it_IT/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: it_IT\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. Tag: title
#: reporting.xml:3
#: reporting.xml:6
#, no-c-format
msgid "Reporting Software Bugs"
-msgstr "Segnalare Malfunzionamenti del Programma"
+msgstr "Segnalare Bug del Software"
#. 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 "
+"Reporting bugs effectively is a fundamental way to help PostGIS development."
+" The most effective bug report is that enabling PostGIS developers to "
"reproduce it, so it would ideally contain a script triggering it and every "
"information regarding the environment in which it was detected. Good enough "
"info can be extracted running <code>SELECT postgis_full_version()</code> "
"[for postgis] and <code>SELECT version()</code> [for postgresql]."
-msgstr ""
+msgstr "Segnalare efficacemente i bug è una modalità fondamentale per aiutare lo sviluppo di PostGIS. Il bug report più efficiente è quello che permette agli sviluppatori PostGIS di replicarlo, quindi idealmente contiene uno script che lo rende evidente e un elenco di informazioni sull'ambiente in cui si verifica. Le informazioni indispensabili possono essere estratte eseguendo code>SELECT postgis_full_version()</code> [per postgis] and <code>SELECT version()</code> [per postgresql]."
#. Tag: para
#: reporting.xml:16
#, no-c-format
msgid ""
"If you aren't using the latest release, it's worth taking a look at its "
-"<ulink url=\"http://svn.osgeo.org/postgis/trunk/NEWS\">release changelog</"
-"ulink> first, to find out if your bug has already been fixed."
-msgstr ""
+"<ulink url=\"http://svn.osgeo.org/postgis/trunk/NEWS\">release "
+"changelog</ulink> first, to find out if your bug has already been fixed."
+msgstr "Se non si sta usando l'ultima release, vale la pena leggere il <ulink url=\"http://svn.osgeo.org/postgis/trunk/NEWS\">release changelog dell'ultima versione</ulink>, per scoprire se il bug in questione è già stato risolto."
#. Tag: para
#: reporting.xml:21
#, no-c-format
msgid ""
-"Using the <ulink url=\"http://trac.osgeo.org/postgis/\">PostGIS bug tracker</"
-"ulink> will ensure your reports are not discarded, and will keep you "
-"informed on its handling process. Before reporting a new bug please query "
-"the database to see if it is a known one, and if it is please add any new "
-"information you have about it."
-msgstr ""
+"Using the <ulink url=\"http://trac.osgeo.org/postgis/\">PostGIS bug "
+"tracker</ulink> will ensure your reports are not discarded, and will keep "
+"you informed on its handling process. Before reporting a new bug please "
+"query the database to see if it is a known one, and if it is please add any "
+"new information you have about it."
+msgstr "Usare il <ulink url=\"http://trac.osgeo.org/postgis/\">PostGIS bug tracker</ulink> assicura che le segnalazioni non vadano perse, e permette di restare aggiornati sulla sua gestione. Prima di riportare un nuovo bug, per favore esaminate il database dei bug per vedere se è già stato segnalato, nel qual caso è opportuno aggiungere ad esso nuove informazioni."
#. Tag: para
#: reporting.xml:28
#, no-c-format
msgid ""
-"You might want to read Simon Tatham's paper about <ulink url=\"http://www."
-"chiark.greenend.org.uk/~sgtatham/bugs.html\">How to Report Bugs Effectively</"
-"ulink> before filing a new report."
-msgstr ""
+"You might want to read Simon Tatham's paper about <ulink "
+"url=\"http://www.chiark.greenend.org.uk/~sgtatham/bugs.html\">How to Report "
+"Bugs Effectively</ulink> before filing a new report."
+msgstr "Consigliamo la lettura del paper di Simon Tatham su <ulink url=\"http://www.chiark.greenend.org.uk/~sgtatham/bugs.html\">How to Report Bugs Effectively</ulink> (Come riportare bug in modo efficiente) prima di compilare un nuovo bug report."
#. Tag: title
#: reporting.xml:34
#, no-c-format
msgid "Reporting Documentation Issues"
-msgstr ""
+msgstr "Segnalare Problemi nella Documentazione"
#. 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 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 ""
+msgstr "La documentazione deve riflettere accuratamente le funzionalità e il comportamento del software. Se così non fosse, potrebbe essere dovuto a un bug del software o a un errore o mancanza della documentazione."
#. Tag: para
#: reporting.xml:40
#, no-c-format
msgid ""
-"Documentation issues can also be reported to the <ulink url=\"http://trac."
-"osgeo.org/postgis\">PostGIS bug tracker</ulink>."
-msgstr ""
+"Documentation issues can also be reported to the <ulink "
+"url=\"http://trac.osgeo.org/postgis\">PostGIS bug tracker</ulink>."
+msgstr "I problemi della documentazione possono essere riportati nel <ulink url=\"http://trac.osgeo.org/postgis\">bug tracker di PostGIS</ulink>."
#. Tag: para
#: reporting.xml:44
msgid ""
"If your revision is trivial, just describe it in a new bug tracker issue, "
"being specific about its location in the documentation."
-msgstr ""
+msgstr "Se la revisione è minore, basta descriverla in una nuova issue del bug tracker, specificando la sua posizione nella documentazione."
#. Tag: para
#: reporting.xml:47
"If your changes are more extensive, a Subversion patch is definitely "
"preferred. This is a four step process on Unix (assuming you already have "
"<ulink url=\"http://subversion.apache.org/\">Subversion</ulink> installed):"
-msgstr ""
+msgstr "Se i cambiamenti sono più estesi, è preferibile mandare una patch per Subversion. In Unix, si tratta di un processo in 4 fasi (assumendo di avere <ulink url=\"http://subversion.apache.org/\">Subversion</ulink> già installato):"
#. Tag: para
#: reporting.xml:54
#, no-c-format
msgid "Check out a copy of PostGIS' Subversion trunk. On Unix, type:"
-msgstr ""
+msgstr "Eseguire il checkout del trunk di PostGIS da Subversion. In Unix, digitare:"
#. Tag: command
#: reporting.xml:57
#, no-c-format
msgid "svn checkout http://svn.osgeo.org/postgis/trunk/"
-msgstr ""
+msgstr "svn checkout http://svn.osgeo.org/postgis/trunk/"
#. Tag: para
#: reporting.xml:60
#, no-c-format
msgid "This will be stored in the directory ./trunk"
-msgstr ""
+msgstr "I file saranno salvati nella cartella ./trunk"
#. Tag: para
#: reporting.xml:64
msgid ""
"Make your changes to the documentation with your favorite text editor. On "
"Unix, type (for example):"
-msgstr ""
+msgstr "Apportare le modifiche alla documentazione con l'editor di testo preferito. In Unix, ad esempio, digitare:"
#. Tag: command
#: reporting.xml:67
#, no-c-format
msgid "vim trunk/doc/postgis.xml"
-msgstr ""
+msgstr "vim trunk/doc/postgis.xml"
#. 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 ""
+"if you are not familiar with it please follow the example of the rest of the"
+" documentation."
+msgstr "Nota: la documentazione è scritta in DocBook XML, non in HTML, quindi se non si ha familiarità con esso conviene seguire lo stile della documentazione esistente."
#. Tag: para
#: reporting.xml:75
msgid ""
"Make a patch file containing the differences from the master copy of the "
"documentation. On Unix, type:"
-msgstr ""
+msgstr "Produrre una patch, cioè un file contenente le differenze rispetto alla copia master della documentazione. In Unix, digitare:"
#. Tag: command
#: reporting.xml:78
#, no-c-format
msgid "svn diff trunk/doc/postgis.xml > doc.patch"
-msgstr ""
+msgstr "svn diff trunk/doc/postgis.xml > doc.patch"
#. Tag: para
#: reporting.xml:83
#, no-c-format
msgid "Attach the patch to a new issue in bug tracker."
-msgstr ""
+msgstr "Allegare la patch a una nuova issue nel bug tracker."
# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# pibinko <pibinko@gmail.com>, 2013-2014
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2014-01-08 10:11+0000\n"
+"Last-Translator: pibinko <pibinko@gmail.com>\n"
+"Language-Team: Italian (Italy) (http://www.transifex.com/projects/p/postgis-1/language/it_IT/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: it_IT\n"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. Tag: title
#: using_raster_dataman.xml:3
#, no-c-format
msgid "Raster Data Management, Queries, and Applications"
-msgstr ""
+msgstr "Dati raster: gestione, interrogazione e applicazioni"
#. Tag: title
#: using_raster_dataman.xml:5
#, no-c-format
msgid "Loading and Creating Rasters"
-msgstr ""
+msgstr "Caricare e creare raster"
#. Tag: para
#: using_raster_dataman.xml:6
"For most use cases, you will create PostGIS rasters by loading existing "
"raster files using the packaged <varname>raster2pgsql</varname> raster "
"loader."
-msgstr ""
+msgstr "Nella maggior parte dei casi, creerete i raster PostGIS caricando file esterni tramite il raster loader <varname>raster2pgsql</varname> compreso nell'installazione."
#. Tag: title
#: using_raster_dataman.xml:9
#, no-c-format
msgid "Using raster2pgsql to load rasters"
-msgstr ""
+msgstr "Usare raster2pgsql per caricare i raster"
#. Tag: para
#: using_raster_dataman.xml:10
#, no-c-format
msgid ""
-"The <varname>raster2pgsql</varname> is a raster loader executable that loads "
-"GDAL supported raster formats into sql suitable for loading into a PostGIS "
+"The <varname>raster2pgsql</varname> 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 ""
+msgstr " <varname>raster2pgsql</varname> è un loader raster che trasforma i formati raster supportati da GDAL in formato SQL utile al caricamento in una tabella raster di PostGIS. Può caricare anche cartelle di file, e creare delle anteprime."
#. 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 <varname>-"
-"G</varname> switch. These should be the same as those provided by your "
-"PostGIS install documented here <xref linkend=\"RT_ST_GDALDrivers\"/> if you "
-"are using the same gdal library for both."
-msgstr ""
+"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 <varname>-G</varname> switch. These should be the same as those "
+"provided by your PostGIS install documented here <xref "
+"linkend=\"RT_ST_GDALDrivers\"/> if you are using the same gdal library for "
+"both."
+msgstr "Dato che in genere raster2pgsql viene compilato come parte di PostGIS (a meno che non abbiate compilato una vostra libreria GDAL a parte), i tipi di raster supportati dall'eseguibile saranno gli stessi che sono compilati per GDAL. Per avere una lista dei tipi di raster supportati dal vostro raster2pgsql utilizzate l'opzione <varname>-G</varname>. Questi tipi dovrebbero essere gli stessi disponibilii tramite la vostra installazione di PostGIS e documentati qui <xref linkend=\"RT_ST_GDALDrivers\"/>, se usate la stessa libreria gdal per entrambi i programmi."
#. 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 <ulink url=\"http://trac.osgeo."
-"org/gdal/wiki/frmts_wtkraster.html\">GDAL PostGIS Raster Driver Usage</"
-"ulink>. Please note that the raster2pgsql python script may not work with "
-"future versions of PostGIS raster and is no longer supported."
-msgstr ""
+"replaced the python script. If you still find the need for the Python script"
+" Examples of the python one can be found at <ulink "
+"url=\"http://trac.osgeo.org/gdal/wiki/frmts_wtkraster.html\">GDAL PostGIS "
+"Raster Driver Usage</ulink>. Please note that the raster2pgsql python script"
+" may not work with future versions of PostGIS raster and is no longer "
+"supported."
+msgstr "La vecchia versione di questo strumento era uno script in python. L'eseguibile sostituisce lo script in python. Se vi trovate ad avere bisogno dello script in Python, alcuni esempio sono reperibili alla pagina <ulink url=\"http://trac.osgeo.org/gdal/wiki/frmts_wtkraster.html\">GDAL PostGIS Raster Driver Usage</ulink>. Notate che lo script Python raster2pgsql potrebbe non funzionare con le future versioni di raster PostGIS e che non è più supportato."
#. 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 <ulink url="
-"\"http://trac.osgeo.org/postgis/ticket/1764\">http://trac.osgeo.org/postgis/"
-"ticket/1764</ulink> for an example where the overviews do not align."
+"aligned, it is possible for the overviews to not align. Visit <ulink "
+"url=\"http://trac.osgeo.org/postgis/ticket/1764\">http://trac.osgeo.org/postgis/ticket/1764</ulink>"
+" for an example where the overviews do not align."
msgstr ""
#. Tag: para
#: using_raster_dataman.xml:25
#, no-c-format
msgid "EXAMPLE USAGE:"
-msgstr ""
+msgstr "ESEMPIO DI UTILIZZO:"
#. Tag: programlisting
#: using_raster_dataman.xml:26
#, no-c-format
msgid ""
-"raster2pgsql <varname>raster_options_go_here</varname> <varname>raster_file</"
-"varname> <varname>someschema</varname>.<varname>sometable</varname> > out."
-"sql"
-msgstr ""
+"raster2pgsql <varname>raster_options_go_here</varname> "
+"<varname>raster_file</varname> "
+"<varname>someschema</varname>.<varname>sometable</varname> > out.sql"
+msgstr "raster2pgsql <varname>opzioni raster</varname> <varname>nome file raster</varname> <varname>snome schema</varname>.<varname>nome tabella</varname> > out.sql"
#. Tag: term
#: using_raster_dataman.xml:30
#, no-c-format
msgid "<term>-?</term>"
-msgstr ""
+msgstr "<term>-?</term>"
#. Tag: para
#: using_raster_dataman.xml:32
msgid ""
"Display help screen. Help will also display if you don't pass in any "
"arguments."
-msgstr ""
+msgstr "Mostra una schermata di aiuto. L'aiuto verra mostrato inoltre se non assegnate alcun parametro."
#. Tag: term
#: using_raster_dataman.xml:39
#, no-c-format
msgid "<term>-G</term>"
-msgstr ""
+msgstr "<term>-G</term>"
#. Tag: para
#: using_raster_dataman.xml:41
#, no-c-format
msgid "Print the supported raster formats."
-msgstr ""
+msgstr "Elenca i formati raster supportati."
#. Tag: term
#: using_raster_dataman.xml:48
#, no-c-format
msgid "(c|a|d|p) These are mutually exclusive options:"
-msgstr ""
+msgstr "(c|a|d|p) sono opzioni che is escludono una con l'altra:"
#. Tag: term
#: using_raster_dataman.xml:53
#, no-c-format
msgid "<term>-c</term>"
-msgstr ""
+msgstr "<term>-c</term>"
#. Tag: para
#: using_raster_dataman.xml:55
msgid ""
"Create new table and populate it with raster(s), <emphasis>this is the "
"default mode</emphasis>"
-msgstr ""
+msgstr "Crea una nuova tabella e carica in questa il/i raster. <emphasis>Questa è la modalita di default</emphasis>"
#. Tag: term
#: using_raster_dataman.xml:62
#, no-c-format
msgid "<term>-a</term>"
-msgstr ""
+msgstr "<term>-a</term>"
#. Tag: para
#: using_raster_dataman.xml:64
#, no-c-format
msgid "Append raster(s) to an existing table."
-msgstr ""
+msgstr "Accoda il o i raster a una tabella esistente."
#. Tag: term
#: using_raster_dataman.xml:71
#, no-c-format
msgid "<term>-d</term>"
-msgstr ""
+msgstr "<term>-d</term>"
#. Tag: para
#: using_raster_dataman.xml:73
#, no-c-format
msgid "Drop table, create new one and populate it with raster(s)"
-msgstr ""
+msgstr "Elimina la tabella, ne crea una nuova e vi carica il/i dati raster"
#. Tag: term
#: using_raster_dataman.xml:80
#, no-c-format
msgid "<term>-p</term>"
-msgstr ""
+msgstr "<term>-p</term>"
#. Tag: para
#: using_raster_dataman.xml:82
#, no-c-format
msgid "Prepare mode, only create the table."
-msgstr ""
+msgstr "Modalità di preparazione. Crea solamente la tabella."
#. Tag: term
#: using_raster_dataman.xml:93
#: using_raster_dataman.xml:98
#, no-c-format
msgid "<term>-C</term>"
-msgstr ""
+msgstr "<term>-C</term>"
#. Tag: para
#: using_raster_dataman.xml:100
#: using_raster_dataman.xml:106
#, no-c-format
msgid "<term>-x</term>"
-msgstr ""
+msgstr "<term>-x</term>"
#. Tag: para
#: using_raster_dataman.xml:108
#: using_raster_dataman.xml:114
#, no-c-format
msgid "<term>-r</term>"
-msgstr ""
+msgstr "<term>-r</term>"
#. Tag: para
#: using_raster_dataman.xml:116
msgid ""
"Raster processing: Optional parameters used to manipulate input raster "
"dataset"
-msgstr ""
+msgstr "Elaborazioni raster: parametri opzionali utilizzati nel trattamento dei dati raster in ingresso"
#. Tag: term
#: using_raster_dataman.xml:132
#, no-c-format
msgid "-s <SRID>"
-msgstr ""
+msgstr "-s <SRID>"
#. Tag: para
#: using_raster_dataman.xml:134
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 ""
+msgstr "Assegna lo SRID specificato al raster in uscita. Se non fornito o uguale a zero, saranno controllati i metadati del raster per determinare uno SRID appropriato."
#. Tag: term
#: using_raster_dataman.xml:141
#, no-c-format
msgid "-b BAND"
-msgstr ""
+msgstr "-b BANDA"
#. Tag: para
#: using_raster_dataman.xml:143
"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 ""
+msgstr "Indice (a partire da 1) della banda da estrarre dal raster. Per specificare più di un indice di banda, separare con una virgola (,). Se non specificato, saranno estratte tutte le bande."
#. Tag: term
#: using_raster_dataman.xml:151
#, no-c-format
msgid "-t TILE_SIZE"
-msgstr ""
+msgstr "-t DIMENSIONE_TILE"
#. Tag: para
#: using_raster_dataman.xml:153
#, no-c-format
msgid ""
-"Cut raster into tiles to be inserted one per table row. <varname>TILE_SIZE</"
-"varname> is expressed as WIDTHxHEIGHT."
-msgstr ""
+"Cut raster into tiles to be inserted one per table row. "
+"<varname>TILE_SIZE</varname> is expressed as WIDTHxHEIGHT."
+msgstr "Taglia un raster in tile da inserire in un record di tabella ciascuno. La <varname>DIMENSIONE TILE</varname> è espressa come LARGHEZZAxALTEZZA."
#. Tag: term
#: using_raster_dataman.xml:160
#, no-c-format
msgid "-R, --register"
-msgstr ""
+msgstr "-R, --register"
#. Tag: para
#: using_raster_dataman.xml:162
#: using_raster_dataman.xml:163
#, 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 ""
+"Only the metadata of the raster and path location to the raster is stored in"
+" the database (not the pixels)."
+msgstr "Nel database vengono salvati solo i metadati e il percorso del raster (non i pixel)."
#. Tag: term
#: using_raster_dataman.xml:168
#, no-c-format
msgid "-l <varname>OVERVIEW_FACTOR</varname>"
-msgstr ""
+msgstr "-l <varname>OVERVIEW_FACTOR</varname>"
#. Tag: para
#: using_raster_dataman.xml:169
#, no-c-format
msgid ""
-"Create overview of the raster. For more than one factor, separate with comma"
-"(,). Overview table name follows the pattern o_<varname>overview factor</"
-"varname>_<varname>table</varname>. Created overview is stored in the "
-"database and is not affected by -R. Note that your generated sql file will "
+"Create overview of the raster. For more than one factor, separate with "
+"comma(,). Overview table name follows the pattern o_<varname>overview "
+"factor</varname>_<varname>table</varname>. 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 ""
#: using_raster_dataman.xml:177
#, no-c-format
msgid "-N <varname>NODATA</varname>"
-msgstr ""
+msgstr "-N <varname>NODATA</varname>"
#. Tag: para
#: using_raster_dataman.xml:179
#, no-c-format
msgid "NODATA value to use on bands without a NODATA value."
-msgstr ""
+msgstr "Valore da usare come NODATA per le bande senza un valore NODATA."
#. Tag: term
#: using_raster_dataman.xml:191
#, no-c-format
msgid "Optional parameters used to manipulate database objects"
-msgstr ""
+msgstr "Parametri opzionali usati per la manipolazione di oggetti del database"
#. Tag: term
#: using_raster_dataman.xml:196
#, no-c-format
msgid "<term>-q</term>"
-msgstr ""
+msgstr "<term>-q</term>"
#. Tag: para
#: using_raster_dataman.xml:198
#: using_raster_dataman.xml:203
#, no-c-format
msgid "-f COLUMN"
-msgstr ""
+msgstr "-f COLONNA"
#. Tag: para
#: using_raster_dataman.xml:205
#, no-c-format
msgid "Specify name of destination raster column, default is 'rast'"
-msgstr ""
+msgstr "Specifica il nome della colonna di destinazione per i raster. Il default è 'rast'."
#. Tag: term
#: using_raster_dataman.xml:211
#, no-c-format
msgid "<term>-F</term>"
-msgstr ""
+msgstr "<term>-F</term>"
#. Tag: para
#: using_raster_dataman.xml:213
#, no-c-format
msgid "Add a column with the name of the file"
-msgstr ""
+msgstr "Aggiunge una colonna con il nome del file"
#. Tag: term
#: using_raster_dataman.xml:218
#, no-c-format
msgid "<term>-I</term>"
-msgstr ""
+msgstr "<term>-I</term>"
#. Tag: para
#: using_raster_dataman.xml:220
#, no-c-format
msgid "Create a GiST index on the raster column."
-msgstr ""
+msgstr "Crea un indice GiST sulla colonna raster."
#. Tag: term
#: using_raster_dataman.xml:227
#, no-c-format
msgid "<term>-M</term>"
-msgstr ""
+msgstr "<term>-M</term>"
#. Tag: para
#: using_raster_dataman.xml:229
#: using_raster_dataman.xml:236
#, no-c-format
msgid "-T <varname>tablespace</varname>"
-msgstr ""
+msgstr "-T <varname>tablespace</varname>"
#. Tag: para
#: using_raster_dataman.xml:238
"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 ""
+msgstr "Specificare il tablespace per la nuova tabella. Notare che gli indici (compresa la chiave primaria) useranno sempre il tablespace di default, a meno che non venga usato anche il flag -X."
#. Tag: term
#: using_raster_dataman.xml:247
#, no-c-format
msgid "-X <varname>tablespace</varname>"
-msgstr ""
+msgstr "-X <varname>tablespace</varname>"
#. Tag: para
#: using_raster_dataman.xml:249
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 ""
+msgstr "Specifica il tablespace per il nuovo indice della tabella. Si applica alla chiave primaria e all'indice spaziale se viene usato il flag -I"
#. Tag: term
#: using_raster_dataman.xml:258
#, no-c-format
msgid "<term>-Y</term>"
-msgstr ""
+msgstr "<term>-Y</term>"
#. Tag: para
#: using_raster_dataman.xml:260
#, no-c-format
msgid "Use copy statements instead of insert statements."
-msgstr ""
+msgstr "Utilizza comandi di copia anziché di inserimento."
#. Tag: term
#: using_raster_dataman.xml:271
#, no-c-format
msgid "<term>-e</term>"
-msgstr ""
+msgstr "<term>-e</term>"
#. Tag: para
#: using_raster_dataman.xml:272
#, no-c-format
msgid "Execute each statement individually, do not use a transaction."
-msgstr ""
+msgstr "Esegui ogni comando individualmente, non utilizzare una transazione."
#. Tag: term
#: using_raster_dataman.xml:276
#, no-c-format
msgid "-E ENDIAN"
-msgstr ""
+msgstr "-E ENDIAN"
#. Tag: para
#: using_raster_dataman.xml:277
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 ""
+msgstr "Controlla l'ordine dei byte prodotti nell'output binario del raster: specificare 0 per XDR e 1 per NDR (il default). Al momento viene supportato solo lo NDR."
#. Tag: term
#: using_raster_dataman.xml:281
#, no-c-format
msgid "-V <varname>version</varname>"
-msgstr ""
+msgstr "-V <varname>versione</varname>"
#. Tag: para
#: using_raster_dataman.xml:282
msgid ""
"Specify version of output format. Default is 0. Only 0 is supported at this "
"time."
-msgstr ""
+msgstr "Specifica la versione del formato in uscita. Il default è 0. Al momento 0 è l'unico supportato."
#. Tag: para
#: using_raster_dataman.xml:285
#, 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 ""
+"An example session using the loader to create an input file and uploading it"
+" chunked in 100x100 tiles might look like this:"
+msgstr "Una sessione di esempio che utilizzi il loader per creare un file di input e per caricarlo a pezzi di tile 100x100 potrebbe essere il seguente:"
#. Tag: para
#: using_raster_dataman.xml:286
"You can leave the schema name out e.g <varname>demelevation</varname> "
"instead of <varname>public.demelevation</varname> and the raster table will "
"be created in the default schema of the database or user"
-msgstr ""
+msgstr "Potete omettere il nome dello schema, per esempio <varname>demelevation</varname> al posto di <varname>public.demelevation</varname> e la tabella raster sarà creata nello schema di default del database o dell'utente"
#. Tag: programlisting
#: using_raster_dataman.xml:288
#, no-c-format
msgid ""
-"raster2pgsql -s 4236 -I -C -M *.tif -F -t 100x100 public.demelevation > elev."
-"sql\n"
+"raster2pgsql -s 4236 -I -C -M *.tif -F -t 100x100 public.demelevation > elev.sql\n"
"psql -d gisdb -f elev.sql"
-msgstr ""
+msgstr "raster2pgsql -s 4236 -I -C -M *.tif -F -t 100x100 public.demelevation > elev.sql\npsql -d gisdb -f elev.sql"
#. Tag: para
#: using_raster_dataman.xml:290
#, no-c-format
msgid "A conversion and upload can be done all in one step using UNIX pipes:"
-msgstr ""
+msgstr "La conversione e il caricamento possono essere eseguiti in un unico passaggio tramite le pipe UNIX:"
#. Tag: programlisting
#: using_raster_dataman.xml:292
#, no-c-format
msgid ""
-"raster2pgsql -s 4236 -I -C -M *.tif -F -t 100x100 public.demelevation | psql "
-"-d gisdb"
-msgstr ""
+"raster2pgsql -s 4236 -I -C -M *.tif -F -t 100x100 public.demelevation | psql"
+" -d gisdb"
+msgstr "raster2pgsql -s 4236 -I -C -M *.tif -F -t 100x100 public.demelevation | psql -d gisdb"
#. Tag: para
#: using_raster_dataman.xml:294
"Load rasters Massachusetts state plane meters aerial tiles into a schema "
"called <varname>aerial</varname> 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."
+"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:296
#, 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 ""
+"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 "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"
#. Tag: programlisting
#: using_raster_dataman.xml:298
msgid ""
"--get a list of raster types supported:\n"
"raster2pgsql -G"
-msgstr ""
+msgstr "--ottieni la lista dei tipi raster supportati:\nraster2pgsql -G"
#. Tag: para
#: using_raster_dataman.xml:300
#, no-c-format
msgid "The -G commands outputs a list something like"
-msgstr ""
+msgstr "Il parametro -G restituirà un elenco tipo"
#. Tag: screen
#: using_raster_dataman.xml:301
" Arc/Info Export E00 GRID\n"
" ZMap Plus Grid\n"
" NOAA NGS Geoid Height Grids"
-msgstr ""
+msgstr "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"
#. Tag: title
#: using_raster_dataman.xml:304
#, no-c-format
msgid "Creating rasters using PostGIS raster functions"
-msgstr ""
+msgstr "Creazione di raster tramite le funzioni raster di PostGIS"
#. Tag: para
#: using_raster_dataman.xml:305
"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 ""
+msgstr "In varie occasioni vorrete creare raster e tabelle raster direttamente nel database. Per questo esiste una pletora di funzioni. Questi sono i passi generali da seguire."
#. Tag: para
#: using_raster_dataman.xml:307
#, no-c-format
msgid ""
-"Create a table with a raster column to hold the new raster records which can "
-"be accomplished with:"
-msgstr ""
+"Create a table with a raster column to hold the new raster records which can"
+" be accomplished with:"
+msgstr "Creare una tabella con una colonna raster per contenere i nuovi valori raster può essere ottenuto da:"
#. Tag: programlisting
#: using_raster_dataman.xml:308
#, no-c-format
msgid "CREATE TABLE myrasters(rid serial primary key, rast raster);"
-msgstr ""
+msgstr "CREATE TABLE myrasters(rid serial primary key, rast raster);"
#. Tag: para
#: using_raster_dataman.xml:311
#, 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: <xref "
-"linkend=\"RT_ST_MakeEmptyRaster\"/>, followed by <xref linkend="
-"\"RT_ST_AddBand\"/>"
-msgstr ""
+"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: <xref "
+"linkend=\"RT_ST_MakeEmptyRaster\"/>, followed by <xref "
+"linkend=\"RT_ST_AddBand\"/>"
+msgstr "Esistono molte funzioni per assitervi verso questo obiettivo. Se state creando un raster non derivato da altri raster, inizierete con: <xref linkend=\"RT_ST_MakeEmptyRaster\"/>, seguito da <xref linkend=\"RT_ST_AddBand\"/>"
#. Tag: para
#: using_raster_dataman.xml:313
msgid ""
"You can also create rasters from geometries. To achieve that you'll want to "
"use <xref linkend=\"RT_ST_AsRaster\"/> perhaps accompanied with other "
-"functions such as <xref linkend=\"RT_ST_Union\"/> or <xref linkend="
-"\"RT_ST_MapAlgebraFct2\"/> or any of the family of other map algebra "
-"functions."
-msgstr ""
+"functions such as <xref linkend=\"RT_ST_Union\"/> or <xref "
+"linkend=\"RT_ST_MapAlgebraFct2\"/> or any of the family of other map algebra"
+" functions."
+msgstr "Potete anche creare raster a partire dalle geometria. Per questo userete <xref linkend=\"RT_ST_AsRaster\"/>, magari accompagnato da altre funzioni come <xref linkend=\"RT_ST_Union\"/> o <xref linkend=\"RT_ST_MapAlgebraFct2\"/>, o qualsiasi altra delle funzioni di algebra sulle mappe."
#. Tag: para
#: using_raster_dataman.xml:315
"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 <xref linkend=\"RT_ST_Transform\"/>"
-msgstr ""
+msgstr "Vi sono poi ancora più opzioni per creare nuove tabelle raster a partire da tabelle esistenti. Per esempio potete creare una tabella raster in una proiezione diversa da una tabella esistente usando <xref linkend=\"RT_ST_Transform\"/>"
#. Tag: para
#: using_raster_dataman.xml:317
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 ""
+msgstr "Una volta inseriti dei valori iniziali nella tabella, vorrete creare un indice spaziale sulla colonna raster, con un comando tipo:"
#. Tag: programlisting
#: using_raster_dataman.xml:318
#, no-c-format
msgid ""
-"CREATE INDEX myrasters_rast_st_convexhull_idx ON myrasters USING gist"
-"( ST_ConvexHull(rast) );"
-msgstr ""
+"CREATE INDEX myrasters_rast_st_convexhull_idx ON myrasters USING gist( "
+"ST_ConvexHull(rast) );"
+msgstr "CREATE INDEX myrasters_rast_st_convexhull_idx ON myrasters USING gist( ST_ConvexHull(rast) );"
#. Tag: para
#: using_raster_dataman.xml:319
#: using_raster_dataman.xml:320
#, 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 "
+"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:321
#, no-c-format
-msgid ""
-"Apply raster constraints using <xref linkend=\"RT_AddRasterConstraints\"/>"
+msgid "Apply raster constraints using <xref linkend=\"RT_AddRasterConstraints\"/>"
msgstr ""
#. Tag: title
#: using_raster_dataman.xml:326
#, no-c-format
msgid "Raster Catalogs"
-msgstr ""
+msgstr "Cataloghi raster"
#. Tag: para
#: using_raster_dataman.xml:327
"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 ""
+msgstr "Esistono due tipi di viste dei cataloghi raster fornite con PostGIS. Entrambe le viste utilizzano informazioni contenute nei dati sui limiti delle tabelle raster. Da ciò risulta che le viste dei cataloghi sono sempre consistenti con i dati raster nelle tabelle, dato che sono considerati i limiti di queste."
#. Tag: para
#: using_raster_dataman.xml:331
msgid ""
"<varname>raster_columns</varname> this view catalogs all the raster table "
"columns in your database."
-msgstr ""
+msgstr "<varname>raster_columns</varname> questa vista riporta il catalogo di tutte le colonne raster nel vostro database."
#. Tag: para
#: using_raster_dataman.xml:334
"columns in your database that serve as overviews for a finer grained table. "
"Tables of this type are generated when you use the <varname>-l</varname> "
"switch during load."
-msgstr ""
+msgstr "<varname>raster_overviews</varname> questa vista elenca tutte le colonne raste di tabelle nel vostro database che sono utilizzate come vista d'insieme per una tabella con maggiori dettagli. Le tabelle di questo tipo sono generate quando utilizzate l'opzione <varname>-l</varname> durante il caricamento."
#. Tag: title
#: using_raster_dataman.xml:338
#, no-c-format
msgid "Raster Columns Catalog"
-msgstr ""
+msgstr "Catalogo delle colonne raster"
#. Tag: para
#: using_raster_dataman.xml:339
#, no-c-format
msgid ""
"The <varname>raster_columns</varname> 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 "
+"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 <varname>raster_columns</varname> catalog."
-msgstr ""
+msgstr " <varname>raster_columns</varname> è un catalogo di tutte le colonne di tabelle che nel vostro database sono di tipo raster. E' una vista che utilizza i limiti applicati alle tabelle, per cui le informazioni sono sempre congruenti, anche se ripristinate una tabella raster dal backup di un altro database. Il catalogo <varname>raster_columns</varname> contiene le seguenti colonne."
#. Tag: para
#: using_raster_dataman.xml:341
msgid ""
"If you created your tables not with the loader or forgot to specify the "
"<varname>-C</varname> flag during load, you can enforce the constraints "
-"after the fact using <xref linkend=\"RT_AddRasterConstraints\"/> so that the "
-"<varname>raster_columns</varname> catalog registers the common information "
+"after the fact using <xref linkend=\"RT_AddRasterConstraints\"/> so that the"
+" <varname>raster_columns</varname> catalog registers the common information "
"about your raster tiles."
-msgstr ""
+msgstr "Se non avete creato le tabelle con il loader o vi siete dimenticati di specificare l'opzione <varname>-C</varname> durante il caricamento, potete far applicare i limiti a cose fatte utilizzando <xref linkend=\"RT_AddRasterConstraints\"/>, di modo che il catalogo <varname>raster_columns</varname> registri le informazioni sulle vostre tile raster."
#. Tag: para
#: using_raster_dataman.xml:346
msgid ""
"<varname>r_table_catalog</varname> The database the table is in. This will "
"always read the current database."
-msgstr ""
+msgstr "<varname>r_table_catalog</varname> Il database in cui si trova la tabella. Conterrà sempre il database corrente."
#. Tag: para
#: using_raster_dataman.xml:349
msgid ""
"<varname>r_table_schema</varname> The database schema the raster table "
"belongs to."
-msgstr ""
+msgstr "<varname>r_table_schema</varname> Lo schema database cui la tabella raster appartiene."
#. Tag: para
#: using_raster_dataman.xml:352
#, no-c-format
msgid "<varname>r_table_name</varname> raster table"
-msgstr ""
+msgstr "<varname>r_table_name</varname> tabella raster"
#. Tag: para
#: using_raster_dataman.xml:355
#, no-c-format
msgid ""
-"<varname>r_raster_column</varname> the column in the <varname>r_table_name</"
-"varname> 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 ""
+"<varname>r_raster_column</varname> the column in the "
+"<varname>r_table_name</varname> 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 "<varname>r_raster_column</varname> la colonna nella tabella <varname>r_table_name</varname> che è di tipo raster. Nulla in PostGIS vi impedisce di avere più colonne raster per tabella, per cui è possibile avere una tabella raster elencata più volte con il riferimento ogni volta a una colonna raster differente.."
#. Tag: para
#: using_raster_dataman.xml:358
msgid ""
"<varname>srid</varname> The spatial reference identifier of the raster. "
"Should be an entry in the <xref linkend=\"spatial_ref_sys\"/>."
-msgstr ""
+msgstr "<varname>srid</varname> L'identificatore del sistema di riferimento spaziale del raster. Dovrebbe essere una voce di <xref linkend=\"spatial_ref_sys\"/>."
#. Tag: para
#: using_raster_dataman.xml:361
#, no-c-format
msgid ""
-"<varname>scale_x</varname> The scaling between geometric spatial coordinates "
-"and pixel. This is only available if all tiles in the raster column have the "
-"same <varname>scale_x</varname> and this constraint is applied. Refer to "
-"<xref linkend=\"RT_ST_ScaleX\"/> for more details."
-msgstr ""
+"<varname>scale_x</varname> The scaling between geometric spatial coordinates"
+" and pixel. This is only available if all tiles in the raster column have "
+"the same <varname>scale_x</varname> and this constraint is applied. Refer to"
+" <xref linkend=\"RT_ST_ScaleX\"/> for more details."
+msgstr "<varname>scale_x</varname> Il rapporto di scala tra le coordinate geometriche e il pixel, disponibile solo se tutte le tile nella colonna raster hanno lo stesso valore di <varname>scale_x</varname> e questo limite è applicato. Si rimanda è <xref linkend=\"RT_ST_ScaleX\"/> per ulteriori dettagli."
#. Tag: para
#: using_raster_dataman.xml:364
#, no-c-format
msgid ""
-"<varname>scale_y</varname> The scaling between geometric spatial coordinates "
-"and pixel. This is only available if all tiles in the raster column have the "
-"same <varname>scale_y</varname> and the <varname>scale_y</varname> "
+"<varname>scale_y</varname> The scaling between geometric spatial coordinates"
+" and pixel. This is only available if all tiles in the raster column have "
+"the same <varname>scale_y</varname> and the <varname>scale_y</varname> "
"constraint is applied. Refer to <xref linkend=\"RT_ST_ScaleY\"/> for more "
"details."
-msgstr ""
+msgstr "<varname>scale_y</varname> Il rapporto di scala tra le coordinate geometriche e il pixel, disponibile solo se tutte le tile nella colonna raster hanno lo stesso valore di <varname>scale_y</varname> e questo limite è applicato. Si rimanda è <xref linkend=\"RT_ST_ScaleY\"/> per ulteriori dettagli."
#. Tag: para
#: using_raster_dataman.xml:367
msgid ""
"<varname>blocksize_x</varname> The width (number of pixels across) of each "
"raster tile . Refer to <xref linkend=\"RT_ST_Width\"/> for more details."
-msgstr ""
+msgstr "<varname>blocksize_x</varname> La larghezza (come numero di pixel in orizzontale) di ogni tile raster. Si rimanda a <xref linkend=\"RT_ST_Width\"/> per ulteriori dettagli."
#. Tag: para
#: using_raster_dataman.xml:370
msgid ""
"<varname>blocksize_y</varname> The width (number of pixels down) of each "
"raster tile . Refer to <xref linkend=\"RT_ST_Height\"/> for more details."
-msgstr ""
+msgstr "<varname>blocksize_y</varname> L'altezza (number of pixels in verticale) di ogni tile raster. Si rimanda a <xref linkend=\"RT_ST_Height\"/> per ulteriori dettagli."
#. Tag: para
#: using_raster_dataman.xml:373
#, no-c-format
msgid ""
"<varname>same_alignment</varname> A boolean that is true if all the raster "
-"tiles have the same alignment . Refer to <xref linkend=\"RT_ST_SameAlignment"
-"\"/> for more details."
-msgstr ""
+"tiles have the same alignment . Refer to <xref "
+"linkend=\"RT_ST_SameAlignment\"/> for more details."
+msgstr "<varname>stesso_allineamento</varname> Variabile booleana pari a \"vero\" se tutte le tile raster hanno lo stesso allineamento. Si rimanda a <xref linkend=\"RT_ST_SameAlignment\"/> per ulteriori dettagli."
#. Tag: para
#: using_raster_dataman.xml:376
#, no-c-format
msgid ""
-"<varname>regular_blocking</varname> This is a true/false constraint flag set "
-"on the table to denote that the tiles do not overlap, are of the same "
+"<varname>regular_blocking</varname> This is a true/false constraint flag set"
+" on the table to denote that the tiles do not overlap, are of the same "
"alignment, pixel size, srid etc. It is not really validated but just taken "
"as a given so should be used for informational. In the future we plan to "
"properly constrain this so that this inforamtion is guaranteed to be right "
"when it returns <varname>true</varname>"
-msgstr ""
+msgstr "<varname>regular_blocking</varname> è un valore vero/falso sulla tabella, per indicare che le tile non si sovrappongono, hanno lo stesso allineamento, dimensione del pixel, SRID, ecc. Non viene effettivamente validato, ma considerato così come è. Per questo l'indicazione dovrebbe essere considerata solo a titolo informativo. In futuro prevediamo di analizzare queste condizioni in modo più adeguato, per cui si garantirà che l'informazione è corretta quando il valore risulta <varname>true</varname>"
#. Tag: para
#: using_raster_dataman.xml:379
#, no-c-format
msgid ""
-"<varname>num_bands</varname> The number of bands in each tile of your raster "
-"set. This is the same information as what is provided by"
-msgstr ""
+"<varname>num_bands</varname> The number of bands in each tile of your raster"
+" set. This is the same information as what is provided by"
+msgstr "<varname>numero_bande</varname> Il numero delle bande in ogni tile del set di raster. Questa è la stessa informazione fornita da"
#. Tag: para
#: using_raster_dataman.xml:382
"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 <xref "
"linkend=\"RT_ST_BandPixelType\"/>."
-msgstr ""
+msgstr "<varname>pixel_types</varname> Un vettore che definisce il tipo di pixel per ciascuna banda. In questo vettore avrete un numero di elementi pari al numero delle bande. I valori di pixel_types possono essere tra quelli definiti in <xref linkend=\"RT_ST_BandPixelType\"/>."
#. Tag: para
#: using_raster_dataman.xml:385
msgid ""
"<varname>nodata_values</varname> An array of double precision numbers "
"denoting the <varname>nodata_value</varname> 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 <xref linkend="
-"\"RT_ST_BandNoDataValue\"/>."
-msgstr ""
+"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 <xref "
+"linkend=\"RT_ST_BandNoDataValue\"/>."
+msgstr "<varname>nodata_values</varname> Un vettore in doppia precisione che spefica i valori <varname>nodata_value</varname> per ciascuna banda. Avrete in questo vettore un numero di elementi pari al numero di bande. Questi numeri definiscono il valore del pixel che per ciascuna banda deve essere ignorato nella maggior parte delle operazioni. L'informazion è simile a quella fornita da <xref linkend=\"RT_ST_BandNoDataValue\"/>."
#. Tag: para
#: using_raster_dataman.xml:388
#, no-c-format
msgid ""
"<varname>extent</varname> 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 <xref linkend=\"RT_DropRasterConstraints\"/> "
-"function before load and then reapply constraints with <xref linkend="
-"\"RT_AddRasterConstraints\"/> after load."
+"raster set. If you plan to load more data that will change the extent of the"
+" set, you'll want to run the <xref linkend=\"RT_DropRasterConstraints\"/> "
+"function before load and then reapply constraints with <xref "
+"linkend=\"RT_AddRasterConstraints\"/> after load."
msgstr ""
#. Tag: title
"<varname>raster_overviews</varname> 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 <varname>raster_columns</varname> and <varname>raster_overviews</"
-"varname> 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 <varname>-l</varname> switch in raster loading."
+"both <varname>raster_columns</varname> and "
+"<varname>raster_overviews</varname> 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 <varname>-l</varname> "
+"switch in raster loading."
msgstr ""
#. Tag: para
msgid ""
"The information in <varname>raster_overviews</varname> does not duplicate "
"the information in <varname>raster_columns</varname>. If you need the "
-"information about an overview table present in <varname>raster_columns</"
-"varname> you can join the <varname>raster_overviews</varname> and "
-"<varname>raster_columns</varname> together to get the full set of "
-"information you need."
+"information about an overview table present in "
+"<varname>raster_columns</varname> you can join the "
+"<varname>raster_overviews</varname> and <varname>raster_columns</varname> "
+"together to get the full set of information you need."
msgstr ""
#. Tag: para
#: using_raster_dataman.xml:400
#, 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 "
+"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."
#, no-c-format
msgid ""
"<varname>overview_factor</varname> - 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 "
+"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) <varname>o_2</varname> table will have "
-"ceiling(1600/Power(2,2)) = 400 rows, your (l=3) <varname>o_3</varname> 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)."
+"to chunk 125x125, for each image file your base table will have "
+"(5000*5000)/(125*125) records = 1600, your (l=2) <varname>o_2</varname> "
+"table will have ceiling(1600/Power(2,2)) = 400 rows, your (l=3) "
+"<varname>o_3</varname> 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:443
#, no-c-format
msgid "Building Custom Applications with PostGIS Raster"
-msgstr ""
+msgstr "Costruire applicazioni personalizzate con PostGIS Raster"
#. Tag: para
#: using_raster_dataman.xml:444
"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 <ulink url=\"http://www.postgresonline.com/journal/"
-"archives/244-Rendering-PostGIS-Raster-graphics-with-LibreOffice-Base-Reports."
-"html\">Rendering PostGIS Raster graphics with LibreOffice Base Reports</"
-"ulink>. In addition you can use a wide variety of languages as demonstrated "
-"in this section."
-msgstr ""
+"demonstrated in <ulink "
+"url=\"http://www.postgresonline.com/journal/archives/244-Rendering-PostGIS-"
+"Raster-graphics-with-LibreOffice-Base-Reports.html\">Rendering PostGIS "
+"Raster graphics with LibreOffice Base Reports</ulink>. In addition you can "
+"use a wide variety of languages as demonstrated in this section."
+msgstr "Il fatto che PostGIS raster vi fornisca le funzioni per restituire i raster in formati di immagine noti vi dà diverse opzioni per visualizzarli. Per esempio potete utilizzare OpenOffice / LibreOffice, come mostrato alla pagina <ulink url=\"http://www.postgresonline.com/journal/archives/244-Rendering-PostGIS-Raster-graphics-with-LibreOffice-Base-Reports.html\">Rendering PostGIS Raster graphics with LibreOffice Base Reports</ulink>. Inoltre potete utilizzare diversi linguaggi, come illustrato in questo paragrafo."
#. Tag: title
#: using_raster_dataman.xml:447
#, no-c-format
msgid ""
"PHP Example Outputting using ST_AsPNG in concert with other raster functions"
-msgstr ""
+msgstr "Esempio di output in PHP, utilizzando ST_AsPNG assieme ad altre funzioni raster"
#. Tag: para
#: using_raster_dataman.xml:448
"the <xref linkend=\"RT_ST_AsGDALRaster\"/> 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 ""
+msgstr "In questo paragrafo mostreremo come utilizzare il driver PHP PostgreSQL e la famiglia di funzioni <xref linkend=\"RT_ST_AsGDALRaster\"/> per estrarre le bande 1,2,3 di un raster a una richiesta PHP che poi può essere inserita in un tag src di un'immagine HTML."
#. Tag: para
#: using_raster_dataman.xml:451 using_raster_dataman.xml:463
"intersecting tiles together returning all bands, transforms to user "
"specified projection using <xref linkend=\"RT_ST_Transform\"/>, and then "
"outputs the results as a png using <xref linkend=\"RT_ST_AsPNG\"/>."
-msgstr ""
+msgstr "La query di esempio mostra come combinare varie funzioni raster per recuperare tutte le tile che intersecano una data area rettangolare in wgs84, unisce le tile risultanti per tutte le bande con <xref linkend=\"RT_ST_Union\"/>, le trasforma in una proiezione specificata dall'utente con <xref linkend=\"RT_ST_Transform\"/> e infine crea un PNG in uscita tramite <xref linkend=\"RT_ST_AsPNG\"/>."
#. Tag: para
#: using_raster_dataman.xml:454
#, no-c-format
msgid ""
-"You would call the below using <programlisting>http://mywebserver/"
-"test_raster.php?srid=2249</programlisting> to get the raster image in "
-"Massachusetts state plane feet."
-msgstr ""
+"You would call the below using "
+"<programlisting>http://mywebserver/test_raster.php?srid=2249</programlisting>"
+" to get the raster image in Massachusetts state plane feet."
+msgstr "Andreste a chiamare il codice sotto utilizzando <programlisting>http://mywebserver/test_raster.php?srid=2249</programlisting> per ottenere l'immagine raster proiettata nel sistema di riferimento Massachusetts state plane feet."
#. Tag: programlisting
#: using_raster_dataman.xml:455
msgid ""
"<![CDATA[<?php\n"
"/** contents of test_raster.php **/\n"
-"$conn_str ='dbname=mydb host=localhost port=5432 user=myuser "
-"password=mypwd';\n"
+"$conn_str ='dbname=mydb host=localhost port=5432 user=myuser password=mypwd';\n"
"$dbconn = pg_connect($conn_str);\n"
"header('Content-Type: image/png'); \n"
-"/**If a particular projection was requested use it otherwise use mass state "
-"plane meters **/\n"
+"/**If a particular projection was requested use it otherwise use mass state plane meters **/\n"
"if (!empty( $_REQUEST['srid'] ) && is_numeric( $_REQUEST['srid']) ){\n"
" $input_srid = intval($_REQUEST['srid']);\n"
"}\n"
"else { $input_srid = 26986; }\n"
-"/** The set bytea_output may be needed for PostgreSQL 9.0+, but not for 8.4 "
-"**/\n"
+"/** The set bytea_output may be needed for PostgreSQL 9.0+, but not for 8.4 **/\n"
"$sql = \"set bytea_output='escape';\n"
"SELECT ST_AsPNG(ST_Transform(\n"
-" ST_AddBand(ST_Union(rast,1), ARRAY[ST_Union(rast,2),"
-"ST_Union(rast,3)])\n"
+" ST_AddBand(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, ST_Transform(ST_MakeEnvelope(-71.1217, 42.227, "
-"-71.1210, 42.218,4326),26986) )\"; \n"
+" ST_Intersects(rast, ST_Transform(ST_MakeEnvelope(-71.1217, 42.227, -71.1210, 42.218,4326),26986) )\"; \n"
"$result = pg_query($sql);\n"
"$row = pg_fetch_row($result);\n"
"pg_free_result($result);\n"
"if ($row === false) return;\n"
"echo pg_unescape_bytea($row[0]);\n"
"?>]]>"
-msgstr ""
+msgstr "<![CDATA[<?php\n/** contents of test_raster.php **/\n$conn_str ='dbname=mydb host=localhost port=5432 user=myuser password=mypwd';\n$dbconn = pg_connect($conn_str);\nheader('Content-Type: image/png'); \n/**If a particular projection was requested use it otherwise use mass state plane meters **/\nif (!empty( $_REQUEST['srid'] ) && is_numeric( $_REQUEST['srid']) ){\n $input_srid = intval($_REQUEST['srid']);\n}\nelse { $input_srid = 26986; }\n/** The set bytea_output may be needed for PostgreSQL 9.0+, but not for 8.4 **/\n$sql = \"set bytea_output='escape';\nSELECT ST_AsPNG(ST_Transform(\n ST_AddBand(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, ST_Transform(ST_MakeEnvelope(-71.1217, 42.227, -71.1210, 42.218,4326),26986) )\"; \n$result = pg_query($sql);\n$row = pg_fetch_row($result);\npg_free_result($result);\nif ($row === false) return;\necho pg_unescape_bytea($row[0]);\n?>]]>"
#. Tag: title
#: using_raster_dataman.xml:458
msgid ""
"ASP.NET C# Example Outputting using ST_AsPNG in concert with other raster "
"functions"
-msgstr ""
+msgstr "Esempio ASP.NET C# di output con ST_AsPNG, assieme ad altre funzioni raster"
#. Tag: para
#: using_raster_dataman.xml:459
#, no-c-format
msgid ""
"In this section, we'll demonstrate how to use Npgsql PostgreSQL .NET driver "
-"and the <xref linkend=\"RT_ST_AsGDALRaster\"/> 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 ""
+"and the <xref linkend=\"RT_ST_AsGDALRaster\"/> 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 "In questo paragrafo vi mostreremo come usare il driver .NET Npgsql e la famiglia di funzioni <xref linkend=\"RT_ST_AsGDALRaster\"/> per inviare in uscita le bande 1,2,3 di un raster a una richiesta PHP che può poi essere inserita nel tag src di un immagine html."
#. Tag: para
#: using_raster_dataman.xml:462
#, no-c-format
msgid ""
"You will need the npgsql .NET PostgreSQL driver for this exercise which you "
-"can get the latest of from <ulink url=\"http://npgsql.projects.postgresql."
-"org/\">http://npgsql.projects.postgresql.org/</ulink>. Just download the "
-"latest and drop into your ASP.NET bin folder and you'll be good to go."
-msgstr ""
+"can get the latest of from <ulink "
+"url=\"http://npgsql.projects.postgresql.org/\">http://npgsql.projects.postgresql.org/</ulink>."
+" Just download the latest and drop into your ASP.NET bin folder and you'll "
+"be good to go."
+msgstr "Per questo vi servirà il driver PostgreSQL npgsql .NET. Potete recuperare il più recente da <ulink url=\"http://npgsql.projects.postgresql.org/\">http://npgsql.projects.postgresql.org/</ulink>. Scaricatelo e salvatelo nella vostra cartella bin di ASP.NET per poter lavorare."
#. Tag: para
#: using_raster_dataman.xml:466
#, no-c-format
msgid ""
-"This is same example as <xref linkend=\"RT_PHP_Output\"/> except implemented "
-"in C#."
-msgstr ""
+"This is same example as <xref linkend=\"RT_PHP_Output\"/> except implemented"
+" in C#."
+msgstr "Questo è lo stesso esempio illustrato in <xref linkend=\"RT_PHP_Output\"/>, implementato in C#."
#. Tag: para
#: using_raster_dataman.xml:467
#, no-c-format
msgid ""
-"You would call the below using <programlisting>http://mywebserver/TestRaster."
-"ashx?srid=2249</programlisting> to get the raster image in Massachusetts "
-"state plane feet."
-msgstr ""
+"You would call the below using "
+"<programlisting>http://mywebserver/TestRaster.ashx?srid=2249</programlisting>"
+" to get the raster image in Massachusetts state plane feet."
+msgstr "Richiamerete il codice sotto come <programlisting>http://mywebserver/TestRaster.ashx?srid=2249</programlisting> per ottenere l'immagine raster nel sistema di riferimento Massachusetts state plane feet."
#. Tag: programlisting
#: using_raster_dataman.xml:468
"-- web.config connection string section --\n"
"<![CDATA[<connectionStrings>\n"
" <add name=\"DSN\" \n"
-" connectionString=\"server=localhost;database=mydb;Port=5432;User "
-"Id=myuser;password=mypwd\"/>\n"
+" connectionString=\"server=localhost;database=mydb;Port=5432;User Id=myuser;password=mypwd\"/>\n"
"</connectionStrings>]]>"
-msgstr ""
+msgstr "-- web.config connection string section --\n<![CDATA[<connectionStrings>\n <add name=\"DSN\" \n connectionString=\"server=localhost;database=mydb;Port=5432;User Id=myuser;password=mypwd\"/>\n</connectionStrings>]]>"
#. Tag: programlisting
#: using_raster_dataman.xml:469
" string sql = null;\n"
" int input_srid = 26986;\n"
" try {\n"
-" using (NpgsqlConnection conn = new NpgsqlConnection"
-"(System.Configuration.ConfigurationManager.ConnectionStrings[\"DSN\"]."
-"ConnectionString)) {\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"
+" 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"
+" 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"
+" 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"
+" command.Parameters.Add(new NpgsqlParameter(\"input_srid\", input_srid));\n"
" \n"
" \n"
" result = (byte[]) command.ExecuteScalar();\n"
" return result;\n"
" }\n"
"}]]>"
-msgstr ""
+msgstr "// Code for TestRaster.ashx\n<![CDATA[<%@ WebHandler Language=\"C#\" Class=\"TestRaster\" %>\nusing System;\nusing System.Data;\nusing System.Web;\nusing Npgsql;\n\npublic 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}]]>"
#. Tag: title
#: using_raster_dataman.xml:472
#, no-c-format
msgid "Java console app that outputs raster query as Image file"
-msgstr ""
+msgstr "app per Java console per esportare una query raster come file immagine"
#. Tag: para
#: using_raster_dataman.xml:473
msgid ""
"This is a simple java console app that takes a query that returns one image "
"and outputs to specified file."
-msgstr ""
+msgstr "Questa è una semplice app per console java che prende una query, ne restituisce la corrispondente immagine e la scrive in un file specificato."
#. Tag: para
#: using_raster_dataman.xml:474
#, no-c-format
msgid ""
-"You can download the latest PostgreSQL JDBC drivers from <ulink url=\"http://"
-"jdbc.postgresql.org/download.html\">http://jdbc.postgresql.org/download."
-"html</ulink>"
-msgstr ""
+"You can download the latest PostgreSQL JDBC drivers from <ulink "
+"url=\"http://jdbc.postgresql.org/download.html\">http://jdbc.postgresql.org/download.html</ulink>"
+msgstr "Potete scaricare i driver JDBC per PostgreSQL più recenti da <ulink url=\"http://jdbc.postgresql.org/download.html\">http://jdbc.postgresql.org/download.html</ulink>"
#. Tag: para
#: using_raster_dataman.xml:475
#, no-c-format
msgid "You can compile the following code using a command something like:"
-msgstr ""
+msgstr "Potete compilare il codice seguente con un comando tipo:"
#. Tag: programlisting
#: using_raster_dataman.xml:476
"set env CLASSPATH .:..\\postgresql-9.0-801.jdbc4.jar\n"
"javac SaveQueryImage.java\n"
"jar cfm SaveQueryImage.jar Manifest.txt *.class"
-msgstr ""
+msgstr "set env CLASSPATH .:..\\postgresql-9.0-801.jdbc4.jar\njavac SaveQueryImage.java\njar cfm SaveQueryImage.jar Manifest.txt *.class"
#. Tag: para
#: using_raster_dataman.xml:477
#, no-c-format
msgid "And call it from the command-line with something like"
-msgstr ""
+msgstr "E lanciarlo dalla riga di comando con un'istruzione tipo"
#. Tag: programlisting
#: using_raster_dataman.xml:478
#, 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 ""
+"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 "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\""
#. Tag: programlisting
#: using_raster_dataman.xml:479
"-- Manifest.txt --\n"
"<![CDATA[Class-Path: postgresql-9.0-801.jdbc4.jar\n"
"Main-Class: SaveQueryImage]]>"
-msgstr ""
+msgstr "-- Manifest.txt --\n<![CDATA[Class-Path: postgresql-9.0-801.jdbc4.jar\nMain-Class: SaveQueryImage]]>"
#. Tag: programlisting
#: using_raster_dataman.xml:480
"\n"
"public class SaveQueryImage {\n"
" public static void main(String[] argv) {\n"
-" System.out.println(\"Checking if Driver is registered with "
-"DriverManager.\");\n"
+" System.out.println(\"Checking if Driver is registered with DriverManager.\");\n"
" \n"
" try {\n"
-" //java.sql.DriverManager.registerDriver (new org.postgresql.Driver"
-"());\n"
+" //java.sql.DriverManager.registerDriver (new org.postgresql.Driver());\n"
" Class.forName(\"org.postgresql.Driver\");\n"
" } \n"
" catch (ClassNotFoundException cnfe) {\n"
" Connection conn = null;\n"
" \n"
" try {\n"
-" conn = DriverManager.getConnection(\"jdbc:postgresql://"
-"localhost:5432/mydb\",\"myuser\", \"mypwd\");\n"
+" conn = DriverManager.getConnection(\"jdbc:postgresql://localhost:5432/mydb\",\"myuser\", \"mypwd\");\n"
" conn.setAutoCommit(false);\n"
"\n"
" PreparedStatement sGetImg = conn.prepareStatement(argv[0]);\n"
" conn.close();\n"
" } \n"
" catch (SQLException se) {\n"
-" System.out.println(\"Couldn't connect: print out a stack trace and "
-"exit.\");\n"
+" System.out.println(\"Couldn't connect: print out a stack trace and exit.\");\n"
" se.printStackTrace();\n"
" System.exit(1);\n"
" } \n"
" }\n"
"}]]>"
-msgstr ""
+msgstr "// Code for SaveQueryImage.java\n<![CDATA[import java.sql.Connection;\nimport java.sql.SQLException;\nimport java.sql.PreparedStatement;\nimport java.sql.ResultSet;\nimport java.io.*;\n\npublic class SaveQueryImage {\n public static void main(String[] argv) {\n System.out.println(\"Checking if Driver is registered with DriverManager.\");\n \n try {\n //java.sql.DriverManager.registerDriver (new org.postgresql.Driver());\n Class.forName(\"org.postgresql.Driver\");\n } \n catch (ClassNotFoundException cnfe) {\n System.out.println(\"Couldn't find the driver!\");\n cnfe.printStackTrace();\n System.exit(1);\n }\n \n Connection conn = null;\n \n try {\n conn = DriverManager.getConnection(\"jdbc:postgresql://localhost:5432/mydb\",\"myuser\", \"mypwd\");\n conn.setAutoCommit(false);\n\n PreparedStatement sGetImg = conn.prepareStatement(argv[0]);\n \n ResultSet rs = sGetImg.executeQuery();\n \n FileOutputStream fout;\n try\n {\n rs.next();\n /** Output to file name requested by user **/\n fout = new FileOutputStream(new File(argv[1]) );\n fout.write(rs.getBytes(1));\n fout.close();\n }\n catch(Exception e)\n {\n System.out.println(\"Can't create file\");\n e.printStackTrace();\n }\n \n rs.close();\n sGetImg.close();\n conn.close();\n } \n catch (SQLException se) {\n System.out.println(\"Couldn't connect: print out a stack trace and exit.\");\n se.printStackTrace();\n System.exit(1);\n } \n }\n}]]>"
#. Tag: title
#: using_raster_dataman.xml:484
#, no-c-format
msgid "Use PLPython to dump out images via SQL"
-msgstr ""
+msgstr "Utilizzare PLPython per esportare immagini tramite SQL"
#. Tag: para
#: using_raster_dataman.xml:485
msgid ""
"This is a plpython stored function that creates a file in the server "
"directory for each record."
-msgstr ""
+msgstr "Questa è una stored function in plypython che crea nella cartella del server un file per ciascun record."
#. Tag: programlisting
#: using_raster_dataman.xml:486
#, no-c-format
msgid ""
"//plpython postgresql stored proc. Requires you have plpython installed\n"
-"<![CDATA[CREATE OR REPLACE FUNCTION write_file (param_bytes bytea, "
-"param_filepath text)\n"
+"<![CDATA[CREATE OR REPLACE FUNCTION write_file (param_bytes bytea, param_filepath text)\n"
"RETURNS text\n"
"AS $$\n"
"f = open(param_filepath, 'wb+')\n"
"f.write(param_bytes)\n"
"return param_filepath\n"
"$$ LANGUAGE plpythonu;]]>"
-msgstr ""
+msgstr "//plpython postgresql stored proc. Richiede l'installazione di plpython\n<![CDATA[CREATE OR REPLACE FUNCTION write_file (param_bytes bytea, param_filepath text)\nRETURNS text\nAS $$\nf = open(param_filepath, 'wb+')\nf.write(param_bytes)\nreturn param_filepath\n$$ LANGUAGE plpythonu;]]>"
#. Tag: programlisting
#: using_raster_dataman.xml:487
"-- 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"
+" 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"
" C:/temp/slices3.png\n"
" C:/temp/slices4.png\n"
" C:/temp/slices5.png"
-msgstr ""
+msgstr "--scrive cinque immagini sul server PostgreSQL con dimensioni variabili\n-- notaer che il l'account da cui gira il demone postgresql deve avere diritto di scrittura sulla cartella\n-- questo mostra i nomi dei file creati;\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"
#. Tag: title
#: using_raster_dataman.xml:490
#, no-c-format
msgid "Outputting Rasters with PSQL"
-msgstr ""
+msgstr "Produrre raster con PSQL"
#. Tag: para
#: using_raster_dataman.xml:491
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 <ulink url=\"http://people.planetpostgresql.org/andrew/index."
-"php?/archives/196-Clever-trick-challenge.html\">Clever Trick Challenge -- "
-"Outputting bytea with psql</ulink> that piggy backs on PostgreSQL somewhat "
-"legacy large object support. To use first launch your psql commandline "
-"connected to your database."
-msgstr ""
+"outlined in <ulink "
+"url=\"http://people.planetpostgresql.org/andrew/index.php?/archives/196"
+"-Clever-trick-challenge.html\">Clever Trick Challenge -- Outputting bytea "
+"with psql</ulink> that piggy backs on PostgreSQL somewhat legacy large "
+"object support. To use first launch your psql commandline connected to your "
+"database."
+msgstr "Purtroppo PSQL non dispone di una funzione comoda per l'esportazione di file binari. Quello che segue è una soluzione improvvisata derivante dai suggerimenti che trovate alla pagina <ulink url=\"http://people.planetpostgresql.org/andrew/index.php?/archives/196-Clever-trick-challenge.html\">Clever Trick Challenge -- Outputting bytea with psql</ulink> e che si appoggia al supporto di PostgreSQL per i tipi \"large object\". Per utilizzare questo sistema anzitutto lanciate la riga di comando psql e collegatevi al database."
#. Tag: para
#: using_raster_dataman.xml:494
msgid ""
"Unlike the python approach, this approach creates the file on your local "
"computer."
-msgstr ""
+msgstr "A differenza dell'approcio python, questo sistema crea il file in locale sul vostro computer."
#. Tag: screen
#: using_raster_dataman.xml:495
"---------+-----------\n"
" 2630819 | 74860\n"
" \n"
-"-- next note the oid and do this replacing the c:/test.png to file path "
-"location\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 ""
+msgstr "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-- otterrete qualcosa tipo --\n oid | num_bytes\n---------+-----------\n 2630819 | 74860\n \n-- prendete nota dell'oid e sostituite c:/test.png con il percorso del file \n-- sul vostro computer\n \\lo_export 2630819 'C:/temp/aerial_samp.png'\n \n-- questo cancella il file dall'archiviazione dei large objects nel database\nSELECT lo_unlink(2630819);"
# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# Dauro Lima Sobrinho <daurolima@gmail.com>, 2013
+# Thiago lima santos leão <th1agol1ma12@gmail.com>, 2013
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2013-11-27 20:23+0000\n"
+"Last-Translator: Dauro Lima Sobrinho <daurolima@gmail.com>\n"
+"Language-Team: Portuguese (Brazil) (http://www.transifex.com/projects/p/postgis-1/language/pt_BR/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: pt_BR\n"
+"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#. Tag: title
#: extras_historytable.xml:3
#, no-c-format
msgid "History Tracking"
-msgstr ""
+msgstr "Histórico de Rastreamento"
#. Tag: para
#: extras_historytable.xml:6
#, no-c-format
msgid ""
"Suppose you have a table of data that represents the current state of a "
-"particular geographic feature. A parcels table, or a roads table, or a fruit "
-"trees table, whatever. Generally, GIS tools understand a table as a single "
+"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 ""
+msgstr "Suponha que você tenha uma tabela que representa o estado atual de uma funcionalidade geográfica em particular. Uma tabela de parcelas, or uma tabela de estradas, or uma tabela de árvores frutíferas, seja o que for. Geralmente, ferramentas SIG entendem uma tabela como uma entidade única que pode atualizar, inserir e apagar registros. Como você permite que ferramentas SIG comuns a trabalhar com os seus dados, mantendo uma trilha de auditoria de que mudanças foram feitas, por quem, e em que estado o dado estava?"
#. Tag: para
#: extras_historytable.xml:10
msgid ""
"This <varname>history_table</varname> extra module provides some utility "
"functions for creating and maintaining history."
-msgstr ""
+msgstr "Este <varname>history_table</varname> módulo extra oferece algumas funcionalidade úteis para criar e manter histórico."
#. Tag: para
#: extras_historytable.xml:14
"added to the documentation in PostGIS 2.0. This package is written in "
"plpgsql and located in the <varname>extras/history_table</varname> of "
"PostGIS source tar balls and source repository."
-msgstr ""
+msgstr "A <varname>history_table</varname> também foi empacotada no PostGIS 1.5, mas adicionada a documentação no PostGIS 2.0. Esse pacote é escrito em plpgsql e está localizado em <varname>extras/history_table</varname> do código fonte e do repositório PostGIS."
#. Tag: para
#: extras_historytable.xml:15
"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 ""
+msgstr "Se você tem a tabela 'roads', este módulo manterá a 'roads_history' lateralmente, que contém todas as colunas da tabela pai, e as colunas adicionais abaixo:"
#. Tag: programlisting
#: extras_historytable.xml:16
" 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 ""
+msgstr "history_id | integer | not null default \n\ndate_added | timestamp without time zone | not null default now()\n\ndate_deleted | timestamp without time zone | \n\nlast_operation | character varying(30) | not null\n\nactive_user | character varying(90) | not null default \"current_user\"()\n\ncurrent_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 ""
+msgstr "Quando você insere um novo registro em 'roads' uma gravação é automativamente inserida em 'roads_history', com a 'date_added' preenchido, a 'date_deleted' com NULL, um único 'history_id', uma 'last_operation' de 'INSERT' e 'active_user' set."
#. Tag: para
#: extras_historytable.xml:23
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 ""
+msgstr "Quando você apaga uma gravação em 'roads', a gravação na tabela histórica *não* é apagada, mas a 'date_deleted' e determinada com a data atual."
#. Tag: para
#: extras_historytable.xml:26
"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 ""
+msgstr "Quando você atualização uma gravação em 'roads', a gravação atual tem 'date_deleted' preenchido e uma nova gravação é criada com determinação da 'date-added' e 'date_deleted' NULL."
#. Tag: para
#: extras_historytable.xml:30
msgid ""
"With this information maintained, it is possible to retrieve the history of "
"any record in the roads table:"
-msgstr ""
+msgstr "Com essas informações mantidas, é possível recuperar o histórico de qualquer gravação na tabela roads:"
#. Tag: programlisting
#: extras_historytable.xml:31
#, no-c-format
msgid "SELECT * FROM roads_history WHERE roads_pk = 111;"
-msgstr ""
+msgstr "SELECT * FROM roads_history WHERE roads_pk = 111;"
#. Tag: para
#: extras_historytable.xml:33
#, no-c-format
msgid "Or, to retrieve a view of the roads table at any point in the past:"
-msgstr ""
+msgstr "Ou, recuperar uma visão da table roads em qualquer ponto do passado:"
#. Tag: programlisting
#: extras_historytable.xml:34
"SELECT * FROM roads_history \n"
" WHERE date_added < 'January 1, 2001' AND \n"
" ( date_deleted >= 'January 1, 2001' OR date_deleted IS NULL );"
-msgstr ""
+msgstr "SELECT * FROM roads_history\n\nWHERE date_added < 'January 1, 2001' AND \n\n( date_deleted >= 'January 1, 2001' OR date_deleted IS NULL );"
#. Tag: refname
#: extras_historytable.xml:38
#, no-c-format
msgid "Postgis_Install_History"
-msgstr ""
+msgstr "Postgis_Install_History"
#. Tag: refpurpose
#: extras_historytable.xml:39
msgid ""
"Creates a table that will hold some interesting values for managing history "
"tables."
-msgstr ""
+msgstr "Cria uma tabela que irá armazenar alguns valores interessantes para o gerenciamento de tabelas de histórico."
#. Tag: funcprototype
#: extras_historytable.xml:44
msgid ""
"<funcdef>void <function>Postgis_Install_History</function></funcdef> "
"<paramdef></paramdef>"
-msgstr ""
+msgstr "<funcdef>void <function>Postgis_Install_History</function></funcdef> <paramdef></paramdef>"
#. Tag: title
#: extras_historytable.xml:52 extras_historytable.xml:92
#, no-c-format
msgid "Description"
-msgstr ""
+msgstr "Descrição"
#. Tag: para
#: extras_historytable.xml:54
msgid ""
"Creates a table that will hold some interesting values for managing history "
"tables. Creates a table called <varname>historic_information</varname>"
-msgstr ""
+msgstr "Cria uma tabela que irá armazenar alguns valores interessantes para o gerenciamento de tabelas de histórico.\nCria uma tabela chamada <varname>historic_information</varname>"
#. Tag: para
#: extras_historytable.xml:58 extras_historytable.xml:100
#, no-c-format
msgid "Availability: 1.5.0"
-msgstr ""
+msgstr "Disponibilidade: 1.5.0"
#. Tag: title
#: extras_historytable.xml:63 extras_historytable.xml:105
#, no-c-format
msgid "Examples"
-msgstr ""
+msgstr "Exemplos"
#. Tag: programlisting
#: extras_historytable.xml:65
#, no-c-format
msgid "SELECT postgis_install_history();"
-msgstr ""
+msgstr "SELECT postgis_install_history();"
#. Tag: title
#: extras_historytable.xml:71 extras_historytable.xml:113
#, no-c-format
msgid "See Also"
-msgstr ""
+msgstr "Veja também."
#. Tag: refname
#: extras_historytable.xml:77
#, no-c-format
msgid "Postgis_Enable_History"
-msgstr ""
+msgstr "Postgis_Enable_History"
#. Tag: refpurpose
#: extras_historytable.xml:78
#, no-c-format
msgid ""
-"Registers a tablein the history_information table for tracking and also adds "
-"in side line history table and insert, update, delete rules on the table."
-msgstr ""
+"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 "Registra na tabela history_information para rastreamento e também para adicionar na tabela history e inserir, atualizar e apagar regras na tabela."
#. Tag: funcprototype
#: extras_historytable.xml:83
"<funcdef>boolean <function>Postgis_Enable_History</function></funcdef> "
"<paramdef><type>text </type> <parameter>p_schema</parameter></paramdef> "
"<paramdef><type>text </type> <parameter>p_table</parameter></paramdef>"
-msgstr ""
+msgstr "<funcdef>boolean <function>Postgis_Enable_History</function></funcdef> <paramdef><type>text </type> <parameter>p_schema</parameter></paramdef> <paramdef><type>text </type> <parameter>p_table</parameter></paramdef>"
#. Tag: para
#: extras_historytable.xml:94
msgid ""
"Registers a table in the history_information table for tracking and also "
"adds in side line history table with same name as table but prefixed with "
-"<varname>history</varname> in the same schema as the original table. Puts in "
-"insert, update, delete rules on the table. Any inserts,updates,deletes of "
+"<varname>history</varname> in the same schema as the original table. Puts in"
+" insert, update, delete rules on the table. Any inserts,updates,deletes of "
"the geometry are recorded in the history table."
-msgstr ""
+msgstr "Registra na table history_information para rastreamento e também para adicionar na tabela history com o mesmo nome da tabela, mas com o prefixo <varname>history</varname> no mesmo esquema como tabela original. Coloca nas regras de inserção, atualização e deleção na tabela. Qualquer inserção, atualização e deleção de uma geometria são gravadas na tabela de histórico."
#. Tag: para
#: extras_historytable.xml:97
"This function currently relies on a geometry column being registered in "
"<varname>geometry_columns</varname> and fails if the geometry column is not "
"present in <varname>geometry_columns</varname> table."
-msgstr ""
+msgstr "Esta função atualmente depende da coluna geometria sendo registrada em <varname>geometry_columns</varname> e falhas se a coluna geometria não estiver presente na table <varname>geometry_columns</varname>."
#. Tag: programlisting
#: extras_historytable.xml:107
"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"
" date_added | last_operation | current_version\n"
"------------------------+----------------+-----------------\n"
" 2011-02-07 12:44:36.92 | INSERT | 2"
-msgstr ""
+msgstr "CREATE TABLE roads(gid SERIAL PRIMARY KEY, road_name varchar(150));\n\nSELECT AddGeometryColumn('roads', 'geom', 26986, 'LINESTRING', 2);\n\nSELECT postgis_enable_history('public', 'roads', 'geom') As register_table;\n\nregister_table\n\n--------------\n\nINSERT INTO roads(road_name, geom) \nVALUES('Test Street', ST_GeomFromText('LINESTRING(231660.5 832170,231647 832202,231627.5 832250.5)',26986));\n\n-- checagem detalhada da transação --\n\nSELECT date_added, last_operation, current_version \n\nFROM roads_history \n\nWHERE road_name = 'Test Street' ORDER BY date_added DESC;\n\ndate_added | last_operation | current_version\n\n------------------------+----------------+-----------------\n\n2011-02-07 12:44:36.92 | INSERT | 2"
# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# Dauro Lima Sobrinho <daurolima@gmail.com>, 2013-2014
+# georgersilva <georger.silva@gmail.com>, 2013
+# Marcelo Soares Souza <marcelo@juntadados.org>, 2014
+# Omar Fernando Pessoa <omar.pessoa@gmail.com>, 2013
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2014-07-28 21:12+0000\n"
+"Last-Translator: Dauro Lima Sobrinho <daurolima@gmail.com>\n"
+"Language-Team: Portuguese (Brazil) (http://www.transifex.com/projects/p/postgis-1/language/pt_BR/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: pt_BR\n"
+"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#. Tag: title
#: faq.xml:3
#, no-c-format
msgid "PostGIS Frequently Asked Questions"
-msgstr ""
+msgstr "Perguntas frequentes PostGIS"
#. Tag: para
#: faq.xml:8
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 ""
+msgstr "Minhas aplicações e ferramentas desktop funcionavam com PostGIS 1.5, mas não funcionam com o PostGIS 2.0. Como corrigir isto?"
#. Tag: para
#: faq.xml:12
#, no-c-format
msgid ""
"A lot of deprecated functions were removed from the PostGIS code base in "
-"PostGIS 2.0. This has affected applications in addition to third-party tools "
-"such as Geoserver, MapServer, QuantumGIS, and OpenJump to name a few. There "
-"are a couple of ways to resolve this. For the third-party apps, you can try "
-"to upgrade to the latest versions of these which have many of these issues "
+"PostGIS 2.0. This has affected applications in addition to third-party tools"
+" such as Geoserver, MapServer, QuantumGIS, and OpenJump to name a few. There"
+" are a couple of ways to resolve this. For the third-party apps, you can try"
+" to upgrade to the latest versions of these which have many of these issues "
"fixed. For your own code, you can change your code to not use the functions "
"removed. Most of these functions are non ST_ aliases of ST_Union, ST_Length "
-"etc. and as a last resort, install the whole of <varname>legacy.sql</"
-"varname> or just the portions of <varname>legacy.sql</varname> you need."
-msgstr ""
+"etc. and as a last resort, install the whole of "
+"<varname>legacy.sql</varname> or just the portions of "
+"<varname>legacy.sql</varname> you need."
+msgstr "Muitas funcionalidades obsoletas foram removidos da base de código do PostGIS na versão 2.0. Isto afetou aplicações e em especial, ferramentas de terceiros, como Geoserver, MapServer, QuantumGIS e OpenJump, para citar alguns casos. Existem algumas maneiras de resolver isto. Para aplicações de terceiros, você pode tentar atualizar para as versões mais atuais, muitas das quais corrigiram estes problemas. Para seu próprio código, você pode alterá-lo para não utilizar as funções removidas. A maior parte destas funções não possuem o prefixo ST_ de ST_Union, ST_Length, etc. Como um último recurso, você pode instalar todo o script legado <varname>legacy.sql</varname> ou apenas as porções de <varname>legacy.sql</varname> que você precisa."
#. Tag: para
#: faq.xml:18
"postgis.sql. You can install this file after you have installed postgis.sql "
"and spatial_ref_sys.sql to get back all the 200 some-odd old functions we "
"removed."
-msgstr ""
+msgstr "O arquivo <varname>legacy.sql</varname> está localizado na mesma pasta em que o arquivo postgis.sql. Você pode instalar este arquivo após a instalação do postgis.sql e spatial_ref_sys.sql, para ter de volta todas 200 funções que foram removidas."
#. Tag: para
#: faq.xml:24
msgid ""
"I'm running PostgreSQL 9.0 and I can no longer read/view geometries in "
"OpenJump, Safe FME, and some other tools?"
-msgstr ""
+msgstr "Estou rodando PostgreSQL 9.0 e não mais posso ler/visualizar geometrias no OpenJump, Safe FME e outras ferramentas?"
#. Tag: para
#: faq.xml:28
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 ""
+msgstr "No PostgreSQL 9.0+, o encoding padrão para dados bytea foi alterado para hex e outros drivers JDBC ainda assumem o formato escapado. Isto afetou aplicações Java utilizando drivers antigos JDBC ou aplicações .NET que usam drivers antigos npgsql e esperam o comportamento antigo de ST_AsBInary. Existem duas formas de resolver este problema."
#. Tag: para
#: faq.xml:32
#, no-c-format
msgid ""
"You can upgrade your JDBC driver to the latest PostgreSQL 9.0 version which "
-"you can get from <ulink url=\"http://jdbc.postgresql.org/download.html"
-"\">http://jdbc.postgresql.org/download.html</ulink>"
-msgstr ""
+"you can get from <ulink "
+"url=\"http://jdbc.postgresql.org/download.html\">http://jdbc.postgresql.org/download.html</ulink>"
+msgstr "Você pode atualizar seu driver JDBC para a última versão do PostgreSQL 9.0, que você obter em <ulink url=\"http://jdbc.postgresql.org/download.html\">http://jdbc.postgresql.org/download.html</ulink>."
#. Tag: para
#: faq.xml:34
#, no-c-format
msgid ""
-"If you are running a .NET app, you can use Npgsql 2.0.11 or higher which you "
-"can download from <ulink url=\"http://pgfoundry.org/frs/?"
-"group_id=1000140\">http://pgfoundry.org/frs/?group_id=1000140</ulink> and as "
-"described on <ulink url=\"http://fxjr.blogspot.com/2010/11/npgsql-2011-"
-"released.html\">Francisco Figueiredo's NpgSQL 2.0.11 released blog entry</"
-"ulink>"
-msgstr ""
+"If you are running a .NET app, you can use Npgsql 2.0.11 or higher which you"
+" can download from <ulink "
+"url=\"http://pgfoundry.org/frs/?group_id=1000140\">http://pgfoundry.org/frs/?group_id=1000140</ulink>"
+" and as described on <ulink "
+"url=\"http://fxjr.blogspot.com/2010/11/npgsql-2011-released.html\">Francisco"
+" Figueiredo's NpgSQL 2.0.11 released blog entry</ulink>"
+msgstr "Se você está utilizando uma aplicação .NET, você pode usar o driver Npgsql 2.0.11 ou melhor, que você fazer o download em <ulink url=\"http://pgfoundry.org/frs/?group_id=1000140\">http://pgfoundry.org/frs/?group_id=1000140</ulink> e descrito em <ulink url=\"http://fxjr.blogspot.com/2010/11/npgsql-2011-released.html\">Francisco Figueiredo's NpgSQL 2.0.11 released blog entry</ulink>."
#. Tag: para
#: faq.xml:38
msgid ""
"If upgrading your PostgreSQL driver is not an option, then you can set the "
"default back to the old behavior with the following change:"
-msgstr ""
+msgstr "Se realizar um upgrade dos drivers PostgreSQL não é uma opção, então você pode setar o valor padrão para o comportamento antigo, usando a seguinte mudança:"
#. Tag: programlisting
#: faq.xml:39
#, no-c-format
msgid "ALTER DATABASE mypostgisdb SET bytea_output='escape';"
-msgstr ""
+msgstr "ALTER DATABASE mypostgisdb SET bytea_output='escape';"
#. Tag: para
#: faq.xml:46
msgid ""
"I tried to use PgAdmin to view my geometry column and it is blank, what "
"gives?"
-msgstr ""
+msgstr "Tentei usar o PgAdmin para visualizar minhas colunas geométricas e ela está em branco?"
#. Tag: para
#: faq.xml:50
msgid ""
"PgAdmin doesn't show anything for large geometries. The best ways to verify "
"you do have data in your geometry columns are?"
-msgstr ""
+msgstr "PgAdmin não mostra nada para grandes colunas. A melhor maneira de garantir que você tem dados em suas colunas geométricas são"
#. Tag: programlisting
#: faq.xml:53
#, 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 ""
+msgstr "-- isto deve retornar zero registros se todos os seus campos geométricos estão preencidos \nSELECT somefield FROM mytable WHERE geom IS NULL;"
#. Tag: programlisting
#: faq.xml:55
#, no-c-format
msgid ""
"-- To tell just how large your geometry is do a query of the form\n"
-"--which will tell you the most number of points you have in any of your "
-"geometry columns\n"
+"--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 ""
+msgstr "-- Para ter uma ideia do tamanho de sua geometria, faça a query que vai lhe dizer o numero de pontos em suas colunas\nSELECT MAX(ST_NPoints(geom)) FROM tabela;"
#. Tag: para
#: faq.xml:61
#, no-c-format
msgid "What kind of geometric objects can I store?"
-msgstr ""
+msgstr "Quais tipos de objetos geométricos posso armazenar?"
#. Tag: para
#: faq.xml:65
#, no-c-format
msgid ""
-"You can store point, line, polygon, multipoint, multiline, multipolygon, and "
-"geometrycollections. In PostGIS 2.0 and above you can also store TINS and "
+"You can store point, line, polygon, multipoint, multiline, multipolygon, and"
+" geometrycollections. In PostGIS 2.0 and above you can also store TINS and "
"Polyhedral Surfaces in the basic geometry type. These are specified in the "
"Open GIS Well Known Text Format (with XYZ,XYM,XYZM extensions). There are "
"three data types currently supported. The standard OGC geometry data type "
"similar type in Microsoft SQL Server 2008+). Only WGS 84 long lat "
"(SRID:4326) is supported by the geography data type. The newest family "
"member of the PostGIS spatial type family is raster for storing and "
-"analyzing raster data. Raster has its very own FAQ. Refer to <xref linkend="
-"\"RT_FAQ\"/> and <xref linkend=\"RT_reference\"/> for more details."
-msgstr ""
+"analyzing raster data. Raster has its very own FAQ. Refer to <xref "
+"linkend=\"RT_FAQ\"/> and <xref linkend=\"RT_reference\"/> for more details."
+msgstr "Você pode armazenar pontos, linhas, polígonos, multipontos, multilinhas, multipolígonos e coleções geométricas. No PostGIS 2.0 ou melhor, você também pode armazenar TINS, superfícies polihédricas no tipo de geometria básico. Estes dados estão especificados no padrão Open GIS Well Known Text (com XYZ, XYM, XYZM). Existem três tipos de dados suportados. A geometria OGC padrão, que utiliza um sistema de coordenadas plano para medidas, o tipo de dados geografia, que utiliza um sistema de coordenadas geodésico (não faz parte do padrão OGC, mas existe um tipo similar no Microsoft SQL Server 2008+). Apenas o datum WGS 84 long lat (SRID 4326) é suportado pelo tipo dados geografia. O mais novo tipo de dados da família PostGIS é o raster, para armazenar e analisar dados em grade regular. Existe um FAQ somente para rasters, disponível em <xref linkend=\"RT_FAQ\"/> e <xref linkend=\"RT_reference\"/> para maiores detalhes."
#. Tag: para
#: faq.xml:78
#, no-c-format
msgid "I'm all confused. Which data store should I use geometry or geography?"
-msgstr ""
+msgstr "Estou confuso. Qual tipo de dados devo utilizar, geometria ou geografia?"
#. Tag: para
#: faq.xml:82
"Short Answer: geography is a new data type that supports long range "
"distances measurements, but most computations on it are currently slower "
"than they are on geometry. If you use geography -- you don't need to learn "
-"much about planar coordinate systems. Geography is generally best if all you "
-"care about is measuring distances and lengths and you have data from all "
+"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 "
+"operations on it are generally faster -- sometimes as much as 10 fold faster"
+" for larger geometries. Geometry is best if you are pretty comfortable with "
"spatial reference systems or you are dealing with localized data where all "
"your data fits in a single <link linkend=\"spatial_ref_sys\">spatial "
"reference system (SRID)</link>, or you need to do a lot of spatial "
"processing. Note: It is fairly easy to do one-off conversions between the "
-"two types to gain the benefits of each. Refer to <xref linkend="
-"\"PostGIS_TypeFunctionMatrix\"/> to see what is currently supported and what "
-"is not."
-msgstr ""
+"two types to gain the benefits of each. Refer to <xref "
+"linkend=\"PostGIS_TypeFunctionMatrix\"/> to see what is currently supported "
+"and what is not."
+msgstr "Resposta curta: geography é um novo tipo de dados que suporta medições de distância de longo alcance, mas a maioria dos cálculos sobre ele estão atualmente mais lento do que são na geometry. Se você usar geography -- você não precisará aprender muito sobre sistemas de coordenadas planar. Geography é geralmente melhor se tudo o que importa é a medição de distâncias e comprimentos e você tem dados de todo o mundo. Tipo de dado geometry é um tipo mais antigo de dados que possúi mais funções que o suportam, goza de maior apoio de ferramentas de terceiros, e as operações nele contidas são geralmente mais rápidas -- às vezes até 10 vezes mais rápido para geometrias maiores. Geometry é melhor se você se sentir confortável com sistemas de referência espacial ou se estiver lidando com dados localizados onde todos seus dados se encaixam em um único <link linkend=\"spatial_ref_sys\">Sistema Espacial de Referência (SRID)</link>, ou você precisará fazer muito processamento espacial. Nota: É bastante fácil de fazer conversões pontuais entre dois tipos para ganhar os benefícios de cada. Consulte <xref linkend=\"PostGIS_TypeFunctionMatrix\"/> para ver o que é, e não é suportado."
#. Tag: para
#: faq.xml:93
#, no-c-format
msgid ""
-"Long Answer: Refer to our more lengthy discussion in the <xref linkend="
-"\"PostGIS_GeographyVSGeometry\"/> and <link linkend="
-"\"PostGIS_TypeFunctionMatrix\">function type matrix</link>."
-msgstr ""
+"Long Answer: Refer to our more lengthy discussion in the <xref "
+"linkend=\"PostGIS_GeographyVSGeometry\"/> and <link "
+"linkend=\"PostGIS_TypeFunctionMatrix\">function type matrix</link>."
+msgstr "Resposta longa: Se refere a nossa mais longa discurssão no <xref linkend=\"PostGIS_GeographyVSGeometry\"/> e <link linkend=\"PostGIS_TypeFunctionMatrix\"> tipo de função matriz</link>."
#. Tag: para
#: faq.xml:101
#, no-c-format
msgid ""
"I have more intense questions about geography, such as how big of a "
-"geographic region can I stuff in a geography column and still get reasonable "
-"answers. Are there limitations such as poles, everything in the field must "
+"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 ""
+msgstr "Tenho questões mais aprofundadas sobre geography, tais como quão grande a geografia de uma região pode ser adicionada em uma coluna geography e continua razoavelmente responsiva. Existem limitações tais como pólos, tudo no campo deve caber em um hemisfério (como SQL Server 2008 tem), velocidade etc?"
#. Tag: para
#: faq.xml:105
#, no-c-format
msgid ""
"Your questions are too deep and complex to be adequately answered in this "
-"section. Please refer to our <xref linkend=\"PostGIS_Geography_AdvancedFAQ\"/"
-">."
-msgstr ""
+"section. Please refer to our <xref "
+"linkend=\"PostGIS_Geography_AdvancedFAQ\"/>."
+msgstr "Suas perguntas são profundas e complexas para serem respondindas de forma adequada nesta seção. Por favor, refira-se ao documento <xref linkend=\"PostGIS_Geography_AdvancedFAQ\"/>."
#. Tag: para
#: faq.xml:112
#, no-c-format
msgid "How do I insert a GIS object into the database?"
-msgstr ""
+msgstr "Como insiro um objeto GIS dentro do banco de dados?"
#. Tag: para
#: faq.xml:116
#, no-c-format
msgid ""
"First, you need to create a table with a column of type \"geometry\" or "
-"\"geography\" to hold your GIS data. Storing geography type data is a little "
-"different than storing geometry. Refer to <xref linkend=\"Geography_Basics\"/"
-"> for details on storing geography."
-msgstr ""
+"\"geography\" to hold your GIS data. Storing geography type data is a little"
+" different than storing geometry. Refer to <xref "
+"linkend=\"Geography_Basics\"/> for details on storing geography."
+msgstr "Primeiramente, você precisa criar uma tabela com uma coluna do tipo \"geometry\" ou \"geography\" para armazenar seus dados GIS. O armazenamento do dado do tipo \"geography\" é um pouco diferente do tipo \"geometry\". Consulte o documento <xref linkend=\"Geography_Basics\"/> para detalhes."
#. Tag: para
#: faq.xml:120
msgid ""
"For geometry: Connect to your database with <filename>psql</filename> and "
"try the following SQL:"
-msgstr ""
+msgstr "Para geometrias: conecte seu banco de dados com <filename>psql</filename> e tente o seguinte SQL:"
#. Tag: programlisting
#: faq.xml:124
msgid ""
"CREATE TABLE gtest ( ID int4, NAME varchar(20) );\n"
"SELECT AddGeometryColumn('', 'gtest','geom',-1,'LINESTRING',2);"
-msgstr ""
+msgstr "CREATE TABLE gtest ( ID int4, NAME varchar(20) );\n\nSELECT AddGeometryColumn('', 'gtest','geom',-1,'LINESTRING',2);"
#. Tag: para
#: faq.xml:126
#, no-c-format
msgid ""
"If the geometry column addition fails, you probably have not loaded the "
-"PostGIS functions and objects into this database. See the <xref linkend="
-"\"PGInstall\"/>."
-msgstr ""
+"PostGIS functions and objects into this database. See the <xref "
+"linkend=\"PGInstall\"/>."
+msgstr "Se a adição da coluna geométrica falhar, provavelmente você não instalou o PostGIS dentro deste banco de dados. Veja <xref linkedn=\"PGInstall\"/>"
#. Tag: para
#: faq.xml:130
#, no-c-format
msgid ""
-"Then, you can insert a geometry into the table using a SQL insert statement. "
-"The GIS object itself is formatted using the OpenGIS Consortium \"well-known "
-"text\" format:"
-msgstr ""
+"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 "Após a criação da tabela, você pode inserir uma geometria através de um comando SQL INSERT. O objeto GIS em si é formatado utilizando o formato OGC WKT (\"well known text\"):"
#. Tag: programlisting
#: faq.xml:134
" 'First Geometry', \n"
" ST_GeomFromText('LINESTRING(2 3,4 5,6 5,7 8)', -1)\n"
");"
-msgstr ""
+msgstr "INSERT INTO gtest (ID, NAME, GEOM) \n\nVALUES (\n\n1, \n\n'First Geometry', \n\nST_GeomFromText('LINESTRING(2 3,4 5,6 5,7 8)', -1)\n\n);"
#. Tag: para
#: faq.xml:136
#, no-c-format
msgid ""
-"For more information about other GIS objects, see the <link linkend="
-"\"RefObject\">object reference</link>."
-msgstr ""
+"For more information about other GIS objects, see the <link "
+"linkend=\"RefObject\">object reference</link>."
+msgstr "Para maiores informações sobre outros objetos GIS, veja a <link linkend=\"RefObject\">referência de objetos</link>."
#. Tag: para
#: faq.xml:139
#, no-c-format
msgid "To view your GIS data in the table:"
-msgstr ""
+msgstr "Para visualizar seus dados GIS na tabela:"
#. Tag: programlisting
#: faq.xml:141
#, no-c-format
msgid "SELECT id, name, ST_AsText(geom) AS geom FROM gtest;"
-msgstr ""
+msgstr "SELECT id, name, ST_AsText(geom) AS geom FROM gtest;"
#. Tag: para
#: faq.xml:143
#, no-c-format
msgid "The return value should look something like this:"
-msgstr ""
+msgstr "O valor de retorno deve se parecer com algum assim:"
#. Tag: programlisting
#: faq.xml:145
"----+----------------+-----------------------------\n"
" 1 | First Geometry | LINESTRING(2 3,4 5,6 5,7 8) \n"
"(1 row)"
-msgstr ""
+msgstr "id | name | geom\n\n----+----------------+-----------------------------\n\n1 | First Geometry | LINESTRING(2 3,4 5,6 5,7 8) \n\n(1 row)"
#. Tag: para
#: faq.xml:151
#, no-c-format
msgid "How do I construct a spatial query?"
-msgstr ""
+msgstr "Como construo uma pesquisa geoespacial?"
#. Tag: para
#: faq.xml:155
msgid ""
"The same way you construct any other database query, as an SQL combination "
"of return values, functions, and boolean tests."
-msgstr ""
+msgstr "Da mesma forma como você constrói qualquer pesquisa no banco de dados, com SQL em uma combinação de valores de retorno, funções e testes de álgebra booleana."
#. Tag: para
#: faq.xml:158
#, no-c-format
msgid ""
-"For spatial queries, there are two issues that are important to keep in mind "
-"while constructing your query: is there a spatial index you can make use of; "
-"and, are you doing expensive calculations on a large number of geometries."
-msgstr ""
+"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 "Para pesquisas geoespaciais, existem duas questões que são importantes de se ter em mente durante sua construção: existe um índice geoespacial que você pode utilizar; e, você está realizando cálculos computacionalmente caros em um número grande de geometrias."
#. Tag: para
#: faq.xml:163
#, 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 ""
+msgstr "Em geral, você vai querer utilizar os operadores de interseção (&&) que testa se os retângulos envolventes de feições se intersecionam. A razão que torna o operador && útil é que existe um índice geoespacial para acelear a resolução do teste, que será utilizado pelo operador. Isto pode tornar as pesquisas muito mais rápidas."
#. Tag: para
#: faq.xml:170
#, no-c-format
msgid ""
"You will also make use of spatial functions, such as Distance(), "
-"ST_Intersects(), ST_Contains() and ST_Within(), among others, to narrow down "
-"the results of your search. Most spatial queries include both an indexed "
+"ST_Intersects(), ST_Contains() and ST_Within(), among others, to narrow down"
+" the results of your search. Most spatial queries include both an indexed "
"test and a spatial function test. The index test serves to limit the number "
"of return tuples to only tuples that <emphasis>might</emphasis> meet the "
"condition of interest. The spatial functions are then use to test the "
"condition exactly."
-msgstr ""
+msgstr "Você ainda pode usar funções geoespaciais, como ST_Distance(), ST_Intersects(), ST_Contains() e ST_Within(), entre outras, para filtrar ainda mais os resultados de sua pesquisa. A maior parte das pesquisas geoespaciais incluem ambos testes: um teste indexado e um teste de função geoespacial. O teste indexado serve para limitar o número de tuplas para as que <emphasis>podem</emphasis> ter a condição de interesse. As funções geoespaciais servem para testar a condição exatamente como esperado."
#. Tag: programlisting
#: faq.xml:178
"FROM thetable \n"
"WHERE \n"
" ST_Contains(the_geom,'POLYGON((0 0, 0 10, 10 10, 10 0, 0 0))');"
-msgstr ""
+msgstr "SELECT id, the_geom\n\nFROM thetable \n\nWHERE \n\nST_Contains(the_geom,'POLYGON((0 0, 0 10, 10 10, 10 0, 0 0))');"
#. Tag: para
#: faq.xml:184
#, no-c-format
msgid "How do I speed up spatial queries on large tables?"
-msgstr ""
+msgstr "Como acelero pesquisas geoespaciais em grandes tabelas?"
#. Tag: para
#: faq.xml:188
#, no-c-format
msgid ""
"Fast queries on large tables is the <emphasis>raison d'etre</emphasis> of "
-"spatial databases (along with transaction support) so having a good index is "
-"important."
-msgstr ""
+"spatial databases (along with transaction support) so having a good index is"
+" important."
+msgstr "Pesquisas rápidas em tabelas grandes é a <emphasis>raison d'etre</emphasis> de banco de dados geoespaciais (bem como suporte a transações), então ter um bom índice é importante."
#. Tag: para
#: faq.xml:192
msgid ""
"To build a spatial index on a table with a <varname>geometry</varname> "
"column, use the \"CREATE INDEX\" function as follows:"
-msgstr ""
+msgstr "Para criar um índice espacial em uma tabela com uma coluna <varname>geometry</varname>, utilize a função \"CREATE INDEX\" que segue abaixo:"
#. Tag: programlisting
#: faq.xml:196
#, no-c-format
msgid ""
"CREATE INDEX [indexname] ON [tablename] USING GIST ( [geometrycolumn] );"
-msgstr ""
+msgstr "CREATE INDEX [indexname] ON [tablename] USING GIST ( [geometrycolumn] );"
#. Tag: para
#: faq.xml:198
#, no-c-format
msgid ""
-"The \"USING GIST\" option tells the server to use a GiST (Generalized Search "
-"Tree) index."
-msgstr ""
+"The \"USING GIST\" option tells the server to use a GiST (Generalized Search"
+" Tree) index."
+msgstr "A opção \"USING GIST\" diz ao servidor que utilize um indice GIST (Generalized Search Tree)."
#. Tag: para
#: faq.xml:202
msgid ""
"GiST indexes are assumed to be lossy. Lossy indexes uses a proxy object (in "
"the spatial case, a bounding box) for building the index."
-msgstr ""
+msgstr "Índeces GIST são assumidamente lossy. Índices lossy usam um objeto de busca (em casos espaciais, uma bounding box) para contruir o índice."
#. Tag: para
#: faq.xml:207
"You should also ensure that the PostgreSQL query planner has enough "
"information about your index to make rational decisions about when to use "
"it. To do this, you have to \"gather statistics\" on your geometry tables."
-msgstr ""
+msgstr "Você também deveria garantir que o plano de acesso do PostgreSQL tem informações suficientes sobre seu índice para fazer decisões racionais sobre quando utilizá-lo. Para fazer isso, você deve atualizar as estatísticas nas suas tabelas geométricas."
#. Tag: para
#: faq.xml:212
#, no-c-format
msgid ""
-"For PostgreSQL 8.0.x and greater, just run the <command>VACUUM ANALYZE</"
-"command> command."
-msgstr ""
+"For PostgreSQL 8.0.x and greater, just run the <command>VACUUM "
+"ANALYZE</command> command."
+msgstr "Para o PostgreSQL 8.0.x ou posterior, apenas executeo o comando <command>VACUUM ANALYZE</command>."
#. Tag: para
#: faq.xml:215
#, no-c-format
msgid ""
-"For PostgreSQL 7.4.x and below, run the <command>SELECT UPDATE_GEOMETRY_STATS"
-"()</command> command."
-msgstr ""
+"For PostgreSQL 7.4.x and below, run the <command>SELECT "
+"UPDATE_GEOMETRY_STATS()</command> command."
+msgstr "Para o PostgreSQL 7.4.x ou anterior, execute o comando <command>SELECT UPDATE_GEOMETRY_STATS()</command>."
#. Tag: para
#: faq.xml:222
#, no-c-format
msgid "Why aren't PostgreSQL R-Tree indexes supported?"
-msgstr ""
+msgstr "Por que o índice do PostgreSQL R-Tree não é suportado?"
#. Tag: para
#: faq.xml:226
"Early versions of PostGIS used the PostgreSQL R-Tree indexes. However, "
"PostgreSQL R-Trees have been completely discarded since version 0.6, and "
"spatial indexing is provided with an R-Tree-over-GiST scheme."
-msgstr ""
+msgstr "Versões mais recentes do PostGIS no PostgreSQL usam indice R-Tree. Por outro lado, PostgreSQL R-Trees foi totalmente descontinuado desde a versão 0.6, e índice espacial é provido com um esquema R-Tree-over-GIST"
#. Tag: para
#: faq.xml:231
"undesirable for use with GIS features (note that these limitations are due "
"to the current PostgreSQL native R-Tree implementation, not the R-Tree "
"concept in general):"
-msgstr ""
+msgstr "Nossos testes tem mostrado que a velocidade de busca para o índice nativo R-Tree e o GIST são comparáveis. O nativo R-Tree tem duas limitações que dele indesejável para utlizar com funcionalidades GIS (note que essa limitação é devido a atual implementação do PostgreSQL, não do conceito R-Tree em geral):"
#. Tag: para
#: faq.xml:239
#, no-c-format
msgid ""
-"R-Tree indexes in PostgreSQL cannot handle features which are larger than 8K "
-"in size. GiST indexes can, using the \"lossy\" trick of substituting the "
+"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 ""
+msgstr "Índices R-Tree no PostgreSQL não podem manipular funcionalidades que são maiores que 8K em tamanho. Já os índices GIST podem, utilizando o truque \"lossy\" de substituição da bounding pela própria funcionalidade."
#. Tag: para
#: faq.xml:246
msgid ""
"R-Tree indexes in PostgreSQL are not \"null safe\", so building an index on "
"a geometry column which contains null geometries will fail."
-msgstr ""
+msgstr "Índices R-Tree no PostgreSQL não são \"null sage\", então construir um índice em uma coluna geometry que contenha null, falhará."
#. Tag: para
#: faq.xml:256
#, no-c-format
msgid ""
-"Why should I use the <varname>AddGeometryColumn()</varname> function and all "
-"the other OpenGIS stuff?"
-msgstr ""
+"Why should I use the <varname>AddGeometryColumn()</varname> function and all"
+" the other OpenGIS stuff?"
+msgstr "Porque eu devo utilizar a função <varname>AddGeometryColumn()</varname> e todas as outras coisas do OpenGIS?"
#. Tag: para
#: faq.xml:261
#, no-c-format
msgid ""
-"If you do not want to use the OpenGIS support functions, you do not have to. "
-"Simply create tables as in older versions, defining your geometry columns in "
-"the CREATE statement. All your geometries will have SRIDs of -1, and the "
+"If you do not want to use the OpenGIS support functions, you do not have to."
+" Simply create tables as in older versions, defining your geometry columns "
+"in the CREATE statement. All your geometries will have SRIDs of -1, and the "
"OpenGIS meta-data tables will <emphasis>not</emphasis> be filled in "
"properly. However, this will cause most applications based on PostGIS to "
"fail, and it is generally suggested that you do use "
"<varname>AddGeometryColumn()</varname> to create geometry tables."
-msgstr ""
+msgstr "Se você não quer utlizar o suporte à funções OpenGIS, você não precisa. Simplesmente crie tabelas como nas versões antigas, definindo as colunas geometry no comando CREATE. Todas suas geometrias terão SRIDs de -1, e as tabelas de metadados do OpenGIS <emphasis>não</emphasis> serão preenchidas apropriadamente. No entanto, causará falha na maioria das aplicações baseadas no PostGIS, e é geralmente aconselhado que utilize <varname>AddGeometryColumn()</varname> para criar tabelas geometry."
#. Tag: para
#: faq.xml:270
"<varname>geometry_columns</varname> meta-data. Specifically, MapServer can "
"use the SRID of the geometry column to do on-the-fly reprojection of "
"features into the correct map projection."
-msgstr ""
+msgstr "MapServer é uma aplicação que faz uso de <varname>geometry_columns</varname> metadado. Especificamente, MapServer pode user SRID da coluna geometry para fazer reprojeção on-the-fly das funcionalidades dentro de uma correta projeção no mapa."
#. Tag: para
#: faq.xml:279
#, no-c-format
msgid ""
"What is the best way to find all objects within a radius of another object?"
-msgstr ""
+msgstr "Qual é a melhor maneira de achar todos os objetos dentre um radius e outro objeto?"
#. Tag: para
#: faq.xml:284
#, no-c-format
msgid ""
"To use the database most efficiently, it is best to do radius queries which "
-"combine the radius test with a bounding box test: the bounding box test uses "
-"the spatial index, giving fast access to a subset of data which the radius "
+"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 ""
+msgstr "Para usar a base de dados mais eficientemente, é melhor fazer radius queries que combine com teste radius com teste bounding box: o teste bounding box usa índice espacial, dando rapidez no acesso para subconjunto de dados que o teste radius é aplicada."
#. Tag: para
#: faq.xml:289
#, no-c-format
msgid ""
"The <varname>ST_DWithin(geometry, geometry, distance)</varname> function is "
-"a handy way of performing an indexed distance search. It works by creating a "
-"search rectangle large enough to enclose the distance radius, then "
+"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 ""
+msgstr "A função <varname>ST_DWithin(geometry, geometry, distance)</varname> é uma forma conveniente de realizar uma busca distante no índice. Ele trabalha criando retângulo de busca suficiente para encobrir todo o raio, depois realiza uma busca exata da distância no subconjunto de resultados do índice."
#. Tag: para
#: faq.xml:295
msgid ""
"For example, to find all objects with 100 meters of POINT(1000 1000) the "
"following query would work well:"
-msgstr ""
+msgstr "Por exemplo, para encontrar todos os objetos com 100 metros de POINT(1000 1000) a query a seguir trabalharia corretamente:"
#. Tag: programlisting
#: faq.xml:298
msgid ""
"SELECT * FROM geotable \n"
"WHERE ST_DWithin(geocolumn, 'POINT(1000 1000)', 100.0);"
-msgstr ""
+msgstr "SELECT * FROM geotable\n\nWHERE ST_DWithin(geocolumn, 'POINT(1000 1000)', 100.0);"
#. Tag: para
#: faq.xml:304
#, no-c-format
msgid "How do I perform a coordinate reprojection as part of a query?"
-msgstr ""
+msgstr "Como posso fazer uma reprojeção de coordenadas como parte de uma query?"
#. Tag: para
#: faq.xml:309
"a reprojection is as simple as referring to the desired destination SRID. "
"The below projects a geometry to NAD 83 long lat. The below will only work "
"if the srid of the_geom is not -1 (not undefined spatial ref)"
-msgstr ""
+msgstr "Para realizar uma reprojeção, ambos as coordenadas fonte e destino devem estar definidas na tabela SPATIAL_REF_SYS, e a geometria reprojetada deve já ter um SRID setado para ela. Uma vez isso feito, a reprojeção é taõ simples quanto referenciar um SRID de destino desejado. The below projects a geometry to NAD 83 long lat. Abaixo apenas trabalhará se o srid do the_geom não for -1 (não indefinido spatial ref)"
#. Tag: programlisting
#: faq.xml:316
#, no-c-format
msgid "SELECT ST_Transform(the_geom,4269) FROM geotable;"
-msgstr ""
+msgstr "SELECT ST_Transform(the_geom,4269) FROM geotable;"
#. Tag: para
#: faq.xml:322
#, no-c-format
msgid ""
-"I did an ST_AsEWKT and ST_AsText on my rather large geometry and it returned "
-"blank field. What gives?"
-msgstr ""
+"I did an ST_AsEWKT and ST_AsText on my rather large geometry and it returned"
+" blank field. What gives?"
+msgstr "Faço uma ST_AsEWKT e ST_AsText na minha maior geometria e isso me retorna em branco. O que acontece?"
#. Tag: para
#: faq.xml:326
"You are probably using PgAdmin or some other tool that doesn't output large "
"text. If your geometry is big enough, it will appear blank in these tools. "
"Use PSQL if you really need to see it or output it in WKT."
-msgstr ""
+msgstr "Vocês está provavelmente utilizando PgAdmin ou outra ferramenta que não retorna grandes textos. Se sua geometria é muito grande, aparecerá vazio nessas ferramentas. Use PSQL se você realmente precisa ver isso ou retornar em WKT."
#. Tag: programlisting
#: faq.xml:329
#, no-c-format
msgid ""
"--To check number of geometries are really blank\n"
-" SELECT count(gid) FROM geotable WHERE "
-"the_geom IS NULL;"
-msgstr ""
+" SELECT count(gid) FROM geotable WHERE the_geom IS NULL;"
+msgstr "Para verificar o de geometrias que realmente estão vazias:\n\nSELECT count(gid) FROM geotable WHERE the_geom IS NULL;"
#. Tag: para
#: faq.xml:335
#, no-c-format
msgid ""
-"When I do an ST_Intersects, it says my two geometries don't intersect when I "
-"KNOW THEY DO. What gives?"
-msgstr ""
+"When I do an ST_Intersects, it says my two geometries don't intersect when I"
+" KNOW THEY DO. What gives?"
+msgstr "Quando eu faço um ST_Intersects, tenho o retorno que minhas duas geometrias não intersectam quando EU SEI QUE SIM. O que acontece?"
#. Tag: para
#: faq.xml:339
"check <xref linkend=\"ST_IsValid\"/> or you are assuming they intersect "
"because ST_AsText truncates the numbers and you have lots of decimals after "
"it is not showing you."
-msgstr ""
+msgstr "Isso geralmente acontece em dois casos comuns. Sua geometri é inválida -- verifique <xref linkend=\"ST_IsValid\"/> ou or você está assumindo que elas intesectam porque ST_AsText trucou os números e você tem muitos decimais que não estão sendo exibidos a você."
#. Tag: para
#: faq.xml:347
#, no-c-format
msgid ""
-"I am releasing software that uses PostGIS, does that mean my software has to "
-"be licensed using the GPL like PostGIS? Will I have to publish all my code "
+"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 ""
+msgstr "Estou liberando software que usa PostGIS, o que significa que meu software foi licenciado utilizado a GPL como PostGIS? Terei que publicar todo o meu código se utilizar o PostGIS?"
#. Tag: para
#: faq.xml:351
msgid ""
"Almost certainly not. As an example, consider Oracle database running on "
"Linux. Linux is GPL, Oracle is not, does Oracle running on Linux have to be "
-"distributed using the GPL? No. So your software can use a PostgreSQL/PostGIS "
-"database as much as it wants and be under any license you like."
-msgstr ""
+"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 "Com certeza não. Como exemplo, considere uma base de dados Oracle rodando no Linux. Linux é GPL. Oracle não, com o Oracle rodando no Linux tenho que distribuí-lo usando GPL? Não. Então seu software pode utilizar bases de dados PostgreSQL/PostGIS o quanto quiser e estar sob qualquer licença que queira."
#. Tag: para
#: faq.xml:352
#, no-c-format
msgid ""
"The only exception would be if you made changes to the PostGIS source code, "
-"and distributed your changed version of PostGIS. In that case you would have "
-"to share the code of your changed PostGIS (but not the code of applications "
-"running on top of it). Even in this limited case, you would still only have "
-"to distribute source code to people you distributed binaries to. The GPL "
+"and distributed your changed version of PostGIS. In that case you would have"
+" to share the code of your changed PostGIS (but not the code of applications"
+" running on top of it). Even in this limited case, you would still only have"
+" to distribute source code to people you distributed binaries to. The GPL "
"does not require that you <emphasis>publish</emphasis> your source code, "
"only that you share it with people you give binaries to."
-msgstr ""
+msgstr "A única exceção seria se você fizer mudanças no código fonte do PostGIS, e distribuir a versão da sua mudança do PostGIS. Neste caso você teria que cmpartilhar o código da sua mudança do PostGIS (mas não o código da aplicação que está rodando). Mesmo neste caso limitado, você apenas teria que distribuir o código fonte para pessoas que também distribuem binários. A GPL não exige que você <emphasis>publique</emphasis> seu código fonte, apenas que compartilhe com pessoas que distribuem binários também."
# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# Dauro Lima Sobrinho <daurolima@gmail.com>, 2013
+# georgersilva <georger.silva@gmail.com>, 2013
+# Omar Fernando Pessoa <omar.pessoa@gmail.com>, 2013
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2013-11-27 15:09+0000\n"
+"Last-Translator: Dauro Lima Sobrinho <daurolima@gmail.com>\n"
+"Language-Team: Portuguese (Brazil) (http://www.transifex.com/projects/p/postgis-1/language/pt_BR/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: pt_BR\n"
+"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#. Tag: title
#: faq_raster.xml:3
#, no-c-format
msgid "PostGIS Raster Frequently Asked Questions"
-msgstr ""
+msgstr "Perguntas frequentes PostGIS Raster"
#. Tag: para
#: faq_raster.xml:9
#, no-c-format
msgid "Where can I find out more about the PostGIS Raster Project?"
-msgstr ""
+msgstr "Onde posso saber mais sobre o projeto PostGIS Raster?"
#. Tag: para
#: faq_raster.xml:13
#, no-c-format
msgid ""
-"Refer to the <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster"
-"\">PostGIS Raster home page</ulink>."
-msgstr ""
+"Refer to the <ulink "
+"url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster\">PostGIS Raster home "
+"page</ulink>."
+msgstr "Consulte o sítio <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster\"> PostGIS Raster </ ulink>."
#. Tag: para
#: faq_raster.xml:19
msgid ""
"Are there any books or tutorials to get me started with this wonderful "
"invention?"
-msgstr ""
+msgstr "Existem livros ou tutoriais para aprender sobre esta maravilhosa invenção?"
#. Tag: para
#: faq_raster.xml:23
#, no-c-format
msgid ""
-"There is a full length beginner tutorial <ulink url=\"http://trac.osgeo.org/"
-"postgis/wiki/WKTRasterTutorial01\"> Intersecting vector buffers with large "
-"raster coverage using PostGIS Raster</ulink>. Jorge has a series of blog "
-"articles on PostGIS Raster that demonstrate how to load raster data as well "
-"as cross compare to same tasks in Oracle GeoRaster. Check out <ulink url="
-"\"http://gis4free.wordpress.com/category/postgis-raster/\">Jorge's PostGIS "
-"Raster / Oracle GeoRaster Series</ulink>. There is a whole chapter (more "
-"than 35 pages of content) dedicated to PostGIS Raster with free code and "
-"data downloads at <ulink url=\"http://www.postgis.us/chapter_13\">PostGIS in "
-"Action - Raster chapter</ulink>. You can <ulink url=\"http://www.postgis.us/"
-"page_buy_book\">buy PostGIS in Action</ulink> now from Manning in hard-copy "
-"(significant discounts for bulk purchases) or just the E-book format. You "
-"can also buy from Amazon and various other book distributors. All hard-copy "
-"books come with a free coupon to download the E-book version."
-msgstr ""
+"There is a full length beginner tutorial <ulink "
+"url=\"http://trac.osgeo.org/postgis/wiki/WKTRasterTutorial01\"> Intersecting"
+" vector buffers with large raster coverage using PostGIS Raster</ulink>. "
+"Jorge has a series of blog articles on PostGIS Raster that demonstrate how "
+"to load raster data as well as cross compare to same tasks in Oracle "
+"GeoRaster. Check out <ulink url=\"http://gis4free.wordpress.com/category"
+"/postgis-raster/\">Jorge's PostGIS Raster / Oracle GeoRaster Series</ulink>."
+" There is a whole chapter (more than 35 pages of content) dedicated to "
+"PostGIS Raster with free code and data downloads at <ulink "
+"url=\"http://www.postgis.us/chapter_13\">PostGIS in Action - Raster "
+"chapter</ulink>. You can <ulink "
+"url=\"http://www.postgis.us/page_buy_book\">buy PostGIS in Action</ulink> "
+"now from Manning in hard-copy (significant discounts for bulk purchases) or "
+"just the E-book format. You can also buy from Amazon and various other book "
+"distributors. All hard-copy books come with a free coupon to download the "
+"E-book version."
+msgstr "Existe um tutorial completo para iniciantes <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRasterTutorial01\"> Interseção de buffers de vetores com grande cobertura de varredura usando PostGIS Raster</ ulink>. Jorge tem uma série de artigos no blog do PostGIS Raster que demonstram como carregar dados raster bem como comparar as mesmas tarefas no Oracle GeoRaster. Confira <ulink url=\"http://gis4free.wordpress.com/category/postgis-raster/\"> Artigos de Jorge: PostGIS Raster / Oracle GeoRaster</ ulink>. Há um capítulo inteiro (mais de 35 páginas de conteúdo) dedicado a PostGIS Raster com código livre e dados para download em <ulink url=\"http://www.postgis.us/chapter_13\"> PostGIS em Ação - Capítulo Raster</ ulink>. Você pode <ulink url=\"http://www.postgis.us/page_buy_book\"> comprar a cópia impressa PostGIS em Ação </ ulink> agora de Manning (descontos significativos para compras em massa) ou apenas o formato E-book. Você também pode comprar na Amazon e outros distribuidores de livros. Todos os manuais impressos vêm com um cupom para baixar a versão E-book."
#. Tag: para
#: faq_raster.xml:30
#, no-c-format
msgid ""
-"Here is a review from a PostGIS Raster user <ulink url=\"http://"
-"fuzzytolerance.info/code/postgis-raster-ftw/\">PostGIS raster applied to "
-"land classification urban forestry</ulink>"
-msgstr ""
+"Here is a review from a PostGIS Raster user <ulink "
+"url=\"http://fuzzytolerance.info/code/postgis-raster-ftw/\">PostGIS raster "
+"applied to land classification urban forestry</ulink>"
+msgstr "Comentário de um usuário PostGIS Raster <ulink url=\"http://fuzzytolerance.info/code/postgis-raster-ftw/\"> raster PostGIS aplicado ao solo - classificação de silvicultura urbana </ ulink>"
#. Tag: para
#: faq_raster.xml:37
#, no-c-format
msgid "How do I install Raster support in my PostGIS database?"
-msgstr ""
+msgstr "Como instalar o suporte a raster no meu banco de dados PostGIS?"
#. Tag: para
#: faq_raster.xml:41
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 ""
+msgstr "A forma mais simples é realizar o download dos binários para o PostGIS e para o Raster, que estão disponíveis para Windows e últimas versões de Mac OSX. Primeiro você precisa de um PostGIS 2.0.0 ou maior e estar rodando PostgreSQL 8.4, 9.0 ou 9.1. No PostGIS 2.0, o PostGIS Raster está totalmente integrado, então ele também será compilado quando você compilar o PostGIS."
#. Tag: para
#: faq_raster.xml:43
"<ulink url=\"http://gis4free.wordpress.com/2011/03/10/how-to-install-and-"
"configure-postgis-raster-on-windows/\">How to Install and Configure PostGIS "
"raster on windows</ulink>"
-msgstr ""
+msgstr "Instruções para instalação no Windows estão disponíveis em <ulink url=\"http://gis4free.wordpress.com/2011/03/10/how-to-install-and-configure-postgis-raster-on-windows/\">Como instalar e configurar o PostGIS Raster no Windows</ulink>"
#. Tag: para
#: faq_raster.xml:44
#, no-c-format
msgid ""
-"If you are on windows, you can compile yourself, or use the <ulink url="
-"\"http://www.postgis.org/download/windows/experimental.php#wktraster\">pre-"
-"compiled PostGIS Raster windows binaries</ulink>. If you are on Mac OSX "
-"Leopard or Snow Leopard, there are binaries available at <ulink url=\"http://"
-"www.kyngchaos.com/software/postgres\">Kyng Chaos Mac OSX PostgreSQL/GIS "
-"binaries</ulink>."
-msgstr ""
+"If you are on windows, you can compile yourself, or use the <ulink "
+"url=\"http://www.postgis.org/download/windows/experimental.php#wktraster"
+"\">pre-compiled PostGIS Raster windows binaries</ulink>. If you are on Mac "
+"OSX Leopard or Snow Leopard, there are binaries available at <ulink "
+"url=\"http://www.kyngchaos.com/software/postgres\">Kyng Chaos Mac OSX "
+"PostgreSQL/GIS binaries</ulink>."
+msgstr "Se estiver usando Windows, você pode compilar você mesmo, ou usar a versão <ulink url=\"http://www.postgis.org/download/windows/experimental.php#wktraster\">pre-compilada de PostGIS Raster para Windows</ulink>. Se você estiver em Mac OSX Leopard ou Snow Leopard, há binários disponíveis em <ulink url=\"http://www.kyngchaos.com/software/postgres\"> Kyng Chaos Mac OSX PostgreSQL / GIS binários </ ulink>."
#. Tag: para
#: faq_raster.xml:50
"Then to enable raster support in your database, run the rtpostgis.sql file "
"in your database. To upgrade an existing install use "
"rtpostgis_upgrade_minor..sql instead of rtpostgis.sql"
-msgstr ""
+msgstr "Para habilitar o suporte a rasters em seu banco de dados, rode o arquivo rtpostgis.sql. Para atualizar uma instalação existente, utilize o script rtpostgis_upgrade_minor.sql ao invés do arquivo rtpostgis.sql."
#. Tag: para
#: faq_raster.xml:51
msgid ""
"For other platforms, you generally need to compile yourself. Dependencies "
"are PostGIS and GDAL. For more details about compiling from source, please "
-"refer to <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/"
-"Documentation01#a2.3-CompilingandInstallingfromSources\">Installing PostGIS "
-"Raster from source (in prior versions of PostGIS)</ulink>"
-msgstr ""
+"refer to <ulink "
+"url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/Documentation01#a2.3-CompilingandInstallingfromSources\">Installing"
+" PostGIS Raster from source (in prior versions of PostGIS)</ulink>"
+msgstr "Em outras plataformas, você geralmente precisará compilar as dependências você mesmo. As dependências são PostGIS e GDAL. Para maiores detalhes sobre a compilação dos fontes, refira ao link <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/Documentation01#a2.3-CompilingandInstallingfromSources\">Instalando o PostGIS Raster do fonte (em versões anteriores do PostGIS)</ulink>"
#. Tag: para
#: faq_raster.xml:57
#, no-c-format
msgid ""
-"I get error could not load library \"C:/Program Files/PostgreSQL/8.4/lib/"
-"rtpostgis.dll\": The specified module could not be found. or could not load "
-"library on Linux when trying to run rtpostgis.sql"
-msgstr ""
+"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 "Recebo um erro que não foi possível carregar a biblioteca \"C:/Program Files/PblostgreSQL/8.4/lib/rtpostgis.dll\": O módulo especificado não pode ser encontrado ou não foi possível carregar a biblioteca no linux ao executar rtpostgis.sql"
#. Tag: para
#: faq_raster.xml:62
#, no-c-format
msgid ""
"rtpostgis.so/dll is built with dependency on libgdal.dll/so. Make sure for "
-"Windows you have libgdal-1.dll in the bin folder of your PostgreSQL install. "
-"For Linux libgdal has to be in your path or bin folder."
-msgstr ""
+"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 "rtpostgis.so/dll é construído com dependências da libgdal.so/dll. Tenha certeza no Windows que você tenha o arquivo libgdal-1.dll na pasta bin de sua instalação do PostgreSQL. Para Linux, a libgdal deve estar no PATH ou na pasta bin."
#. Tag: para
#: faq_raster.xml:64
#, no-c-format
msgid ""
"You may also run into different errors if you don't have PostGIS installed "
-"in your database. Make sure to install PostGIS first in your database before "
-"trying to install the raster support."
-msgstr ""
+"in your database. Make sure to install PostGIS first in your database before"
+" trying to install the raster support."
+msgstr "Você também pode encontrar erros diferentes se você não tem o PostGIS instalado em seu banco de dados. Tenha certeza de instalar primeiro o PostGIS em seu banco de dados antes de tentar instalar o suporte a raster."
#. Tag: para
#: faq_raster.xml:71
#, no-c-format
msgid "How do I load Raster data into PostGIS?"
-msgstr ""
+msgstr "Como carrego dados raster dentro de meu banco PostGIS?"
#. Tag: para
#: faq_raster.xml:75
#, no-c-format
msgid ""
-"The latest version of PostGIS comes packaged with a <varname>raster2pgsql</"
-"varname> raster loader executable capable of loading many kinds of rasters "
-"and also generating lower resolution overviews without any additional "
-"software. Please refer to <xref linkend=\"RT_Raster_Loader\"/> for more "
-"details. Pre-2.0 versions came with a <varname>raster2pgsql.py</varname> "
-"that required python with numpy and GDAL. This is no longer needed."
-msgstr ""
+"The latest version of PostGIS comes packaged with a "
+"<varname>raster2pgsql</varname> raster loader executable capable of loading "
+"many kinds of rasters and also generating lower resolution overviews without"
+" any additional software. Please refer to <xref "
+"linkend=\"RT_Raster_Loader\"/> for more details. Pre-2.0 versions came with "
+"a <varname>raster2pgsql.py</varname> that required python with numpy and "
+"GDAL. This is no longer needed."
+msgstr "A última versão do PostGIS vem com o carregador <varname>raster2pgsql</varname>, capaz de importar vários tipos de rasters, também capaz de gerar visões de menor resolução sem qualquer outro software adicional. Refira ao <xref linkend=\"RT_Raster_Loader\"/> para maiores detalhes. Versões anteriores a 2.0 também vem com um script <varname>raster2pgsql.py</varname>, que requer Python, com suporte a numpy e GDAL. Isto não é mais necessário."
#. Tag: para
#: faq_raster.xml:81
#, no-c-format
msgid "What kind of raster file formats can I load into my database?"
-msgstr ""
+msgstr "Quais tipos de arquivos raster posso carregar em meu banco de dados?"
#. Tag: para
#: faq_raster.xml:85
#, no-c-format
msgid ""
"Any that your GDAL library supports. GDAL supported formats are documented "
-"<ulink url=\"http://www.gdal.org/formats_list.html\">GDAL File Formats</"
-"ulink>."
-msgstr ""
+"<ulink url=\"http://www.gdal.org/formats_list.html\">GDAL File "
+"Formats</ulink>."
+msgstr "Qualquer raster que sua biblioteca GDAL suporte. Os formatos suportados pela GDAL estão documentados em <ulink url=\"http://www.gdal.org/formats_list.html\">GDAL File Formats</ulink>."
#. Tag: para
#: faq_raster.xml:86
#, no-c-format
msgid ""
-"Your particular GDAL install may not support all formats. To verify the ones "
-"supported by your particular GDAL install, you can use"
-msgstr ""
+"Your particular GDAL install may not support all formats. To verify the ones"
+" supported by your particular GDAL install, you can use"
+msgstr "Sua instalação específica da GDAL pode não suportar todos os formatos. Para verificar os formatos suportados em sua instalação, você pode usar"
#. Tag: programlisting
#: faq_raster.xml:87
#, no-c-format
msgid "raster2pgsql -G"
-msgstr ""
+msgstr "raster2pgsql -G"
#. Tag: para
#: faq_raster.xml:93
#, no-c-format
msgid "Can I export my PostGIS raster data to other raster formats?"
-msgstr ""
+msgstr "Posso exportar meus dados raster do banco de dados para outros formatos raster?"
#. Tag: para
#: faq_raster.xml:97
#, no-c-format
msgid "<para>Yes</para>"
-msgstr ""
+msgstr "<para>Sim</para>"
#. Tag: para
#: faq_raster.xml:98
#, no-c-format
msgid ""
-"GDAL 1.7+ has a PostGIS raster driver, but is only compiled in if you choose "
-"to compile with PostgreSQL support."
-msgstr ""
+"GDAL 1.7+ has a PostGIS raster driver, but is only compiled in if you choose"
+" to compile with PostgreSQL support."
+msgstr "GDAL 1.7+ tem um driver para PostGIS, mas somente é compilado se você habilitar esta opção no momento da compilação."
#. Tag: para
#: faq_raster.xml:99
msgid ""
"The driver currently doesn't support irregularly blocked rasters, although "
"you can store irregularly blocked rasters in PostGIS raster data type."
-msgstr ""
+msgstr "O driver não suporte rasters irregulares, apesar de ser possível de armazená-los no tipo de dados do PostGIS."
#. Tag: para
#: faq_raster.xml:101
msgid ""
"If you are compiling from source, you need to include in your configure "
"<programlisting>--with-pg=path/to/pg_config</programlisting> to enable the "
-"driver. Refer to <ulink url=\"http://trac.osgeo.org/gdal/wiki/BuildHints"
-"\">GDAL Build Hints</ulink> for tips on building GDAL against in various OS "
-"platforms."
-msgstr ""
+"driver. Refer to <ulink "
+"url=\"http://trac.osgeo.org/gdal/wiki/BuildHints\">GDAL Build Hints</ulink> "
+"for tips on building GDAL against in various OS platforms."
+msgstr "Se você está compilando os fontes, você precisa incluir em sua configuração <programlisting>--with-pg=caminho/para/pg_config</programlisting> para habilitar o driver. Veja <ulink url=\"http://trac.osgeo.org/gdal/wiki/BuildHints\">GDAL Build Hints</ulink> para dicas sobre como compilar a GDAL em várias plataformas e sistemas operacionais."
#. Tag: para
#: faq_raster.xml:106
msgid ""
"If your version of GDAL is compiled with the PostGIS Raster driver you "
"should see PostGIS Raster in list when you do"
-msgstr ""
+msgstr "Se sua versão da GDAL for compilada com o driver PostGIS, você deve ver PostGIS Raster na lista quando executar"
#. Tag: programlisting
#: faq_raster.xml:108
#, no-c-format
msgid "gdalinfo --formats"
-msgstr ""
+msgstr "gdalinfo --formats"
#. Tag: para
#: faq_raster.xml:110
#, no-c-format
msgid "To get a summary about your raster via GDAL use gdalinfo:"
-msgstr ""
+msgstr "Para visualizar um sumário sobre seu raster via GDAL use gdalinfo:"
#. Tag: programlisting
#: faq_raster.xml:111
msgid ""
"gdalinfo \"PG:host=localhost port=5432 dbname='mygisdb' user='postgres' "
"password='whatever' schema='someschema' table=sometable\""
-msgstr ""
+msgstr "gdalinfo \"PG:host=localhost port=5432 dbname='mygisdb' user='postgres' password='whatever' schema='someschema' table=sometable\""
#. Tag: para
#: faq_raster.xml:114
msgid ""
"To export data to other raster formats, use gdal_translate the below will "
"export all data from a table to a PNG file at 10% size."
-msgstr ""
+msgstr "Para exportar dados para outros formatos raster, use gdal_translate. O comando abaixo irá exportar todos os dados de uma tabela para um arquivo PNG com 10% de seu tamanho."
#. Tag: para
#: faq_raster.xml:116
msgid ""
"Depending on your pixel band types, some translations may not work if the "
"export format does not support that Pixel type. For example floating point "
-"band types and 32 bit unsigned ints will not translate easily to JPG or some "
-"others."
-msgstr ""
+"band types and 32 bit unsigned ints will not translate easily to JPG or some"
+" others."
+msgstr "Dependendo do tipo de bandas, algumas conversões (via GDAL) podem não funcionar, se o formato não suportar este tipo de banda. Por exemplo, bandas de ponto flutuante e inteiros de 32 bits sem sinal não serão facilmente convertidas em JPGs e alguns outros."
#. Tag: para
#: faq_raster.xml:119
#, no-c-format
msgid "Here is an example simple translation"
-msgstr ""
+msgstr "Aqui está um exemplo de uma simples conversão"
#. Tag: programlisting
#: faq_raster.xml:120
#, no-c-format
msgid ""
-"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' "
-"user='postgres' password=whatever' schema='someschema' table=sometable\" C:"
-"\\somefile.png"
-msgstr ""
+"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb'"
+" user='postgres' password=whatever' schema='someschema' table=sometable\" "
+"C:\\somefile.png"
+msgstr "gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' user='postgres' password=whatever' schema='someschema' table=sometable\" C:\\somefile.png"
#. Tag: para
#: faq_raster.xml:121
msgid ""
"You can also use SQL where clauses in your export using the where=... in "
"your driver connection string. Below are some using a where clause"
-msgstr ""
+msgstr "Você também pode usar clausulas SQL na sua exportação, com o parametro where=... em sua string de conexão. Abaixo estão alguns exemplos com a clausula where"
#. Tag: programlisting
#: faq_raster.xml:123
#, no-c-format
msgid ""
-"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' "
-"user='postgres' password=whatever' schema='someschema' table=sometable where="
-"\"owner='jimmy'\" \" C:\\somefile.png"
-msgstr ""
+"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb'"
+" user='postgres' password=whatever' schema='someschema' table=sometable "
+"where=\"owner='jimmy'\" \" C:\\somefile.png"
+msgstr "gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' user='postgres' password=whatever' schema='someschema' table=sometable where=\"owner='jimmy'\" \" C:\\somefile.png"
#. Tag: programlisting
#: faq_raster.xml:124
#, no-c-format
msgid ""
-"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' "
-"user='postgres' password=whatever' schema='someschema' table=sometable "
+"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb'"
+" user='postgres' password=whatever' schema='someschema' table=sometable "
"where='ST_Intersects(rast, ST_SetSRID(ST_Point(-71.032,42.3793),4326) )' \" "
"C:\\intersectregion.png"
-msgstr ""
+msgstr "gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost dbname='mygisdb' user='postgres' password=whatever' schema='someschema' table=sometable where='ST_Intersects(rast, ST_SetSRID(ST_Point(-71.032,42.3793),4326) )' \" C:\\intersectregion.png"
#. Tag: para
#: faq_raster.xml:125
#, no-c-format
msgid ""
-"To see more examples and syntax refer to <ulink url=\"http://trac.osgeo.org/"
-"gdal/wiki/frmts_wtkraster.html#a3.2-Readingrasterdatafromthedatabase"
-"\">Reading Raster Data of PostGIS Raster section</ulink>"
-msgstr ""
+"To see more examples and syntax refer to <ulink "
+"url=\"http://trac.osgeo.org/gdal/wiki/frmts_wtkraster.html#a3.2-Readingrasterdatafromthedatabase\">Reading"
+" Raster Data of PostGIS Raster section</ulink>"
+msgstr "Para visualizar mais exemplos e a sintaxe, confira a seção ulink url=\"http://trac.osgeo.org/gdal/wiki/frmts_wtkraster.html#a3.2-Readingrasterdatafromthedatabase\">Reading Raster Data of PostGIS Raster section</ulink>"
#. Tag: para
#: faq_raster.xml:130
msgid ""
"Are their binaries of GDAL available already compiled with PostGIS Raster "
"suppport?"
-msgstr ""
+msgstr "Existem binários pré-compilados já com suporte ao PostGIS Raster?"
#. Tag: para
#: faq_raster.xml:132
#, no-c-format
msgid ""
-"Yes. Check out the page <ulink url=\"http://trac.osgeo.org/gdal/wiki/"
-"DownloadingGdalBinaries\">GDAL Binaries</ulink> page. Any compiled with "
-"PostgreSQL support should have PostGIS Raster in them."
-msgstr ""
+"Yes. Check out the page <ulink "
+"url=\"http://trac.osgeo.org/gdal/wiki/DownloadingGdalBinaries\">GDAL "
+"Binaries</ulink> page. Any compiled with PostgreSQL support should have "
+"PostGIS Raster in them."
+msgstr "Sim. Cheque a página <ulink url=\"http://trac.osgeo.org/gdal/wiki/DownloadingGdalBinaries\">GDAL Binaries</ulink>. Qualquer um destes deve ter suporte ao PostGIS Raster."
#. Tag: para
#: faq_raster.xml:134
#, no-c-format
msgid ""
-"We know for sure the following windows binaries have PostGIS Raster built in."
-msgstr ""
+"We know for sure the following windows binaries have PostGIS Raster built "
+"in."
+msgstr "Temos certeza que os seguintes binários Windows tem suporte ao PostGIS Raster."
#. Tag: para
#: faq_raster.xml:135
msgid ""
"<ulink url=\"http://fwtools.maptools.org/\">FWTools latest stable version "
"for Windows is compiled with Raster support</ulink>."
-msgstr ""
+msgstr "<ulink url=\"http://fwtools.maptools.org/\">Última versão estável para Windows é compilada com suporte ao PostGIS Raster</ulink>"
#. Tag: para
#: faq_raster.xml:136
"PostGIS Raster is undergoing many changes. If you want to get the latest "
"nightly build for Windows -- then check out the Tamas Szekeres nightly "
"builds built with Visual Studio which contain GDAL trunk, Python Bindings "
-"and MapServer executables and PostGIS Raster driver built-in. Just click the "
-"SDK bat and run your commands from there. <ulink url=\"http://vbkto.dyndns."
-"org/sdk/\">http://vbkto.dyndns.org/sdk/</ulink>. Also available are VS "
-"project files."
-msgstr ""
+"and MapServer executables and PostGIS Raster driver built-in. Just click the"
+" SDK bat and run your commands from there. <ulink "
+"url=\"http://vbkto.dyndns.org/sdk/\">http://vbkto.dyndns.org/sdk/</ulink>. "
+"Also available are VS project files."
+msgstr "O PostGIS Raster está passando por muitas mudanças. Se você desejar a versão diária para Windows, cheque as builds feitas por Tamas Szekeres com Visual Studio, que contém o trunk GDAL, suporte a Python, MapServer e o driver PostGIS embutido. Clique no bat SDK e rode seus comandos a partir daí. <ulink url=\"http://vbkto.dyndns.org/sdk/\">http://vbkto.dyndns.org/sdk/</ulink>. Também estão disponíveis os projetos do Visual Studio."
#. Tag: para
#: faq_raster.xml:145
#, no-c-format
msgid "What tools can I use to view PostGIS raster data?"
-msgstr ""
+msgstr "Quais ferramentas posso usar para visualizar os dados do PostGIS Raster?"
#. Tag: para
#: faq_raster.xml:149
"You can use MapServer compiled with GDAL 1.7+ and PostGIS Raster driver "
"support to view Raster data. QuantumGIS (QGIS) now supports viewing of "
"PostGIS Raster if you have PostGIS raster driver installed."
-msgstr ""
+msgstr "Você pode utilizar o MapServer compilado com GDAL 1.7+ e o suporte ao PostGIS Raster. QuantumGIS (QGIS) também suporta a visualização de rasters no PostGIS se o driver estiver instalado."
#. Tag: para
#: faq_raster.xml:151
msgid ""
"In theory any tool that renders data using GDAL can support PostGIS raster "
"data or support it with fairly minimal effort. Again for Windows, Tamas' "
-"binaries <ulink url=\"http://vbkto.dyndns.org/sdk/\">http://vbkto.dyndns.org/"
-"sdk/</ulink> are a good choice if you don't want the hassle of having to "
-"setup to compile your own."
-msgstr ""
+"binaries <ulink "
+"url=\"http://vbkto.dyndns.org/sdk/\">http://vbkto.dyndns.org/sdk/</ulink> "
+"are a good choice if you don't want the hassle of having to setup to compile"
+" your own."
+msgstr "Na teoria, qualquer ferramenta que consiga renderizar dados utilizando a GDAL pode suportar o driver PostGIS com pouco esforço. Para Windows, os binários construídos por Tamas <ulink url=\"http://vbkto.dyndns.org/sdk/\">http://vbkto.dyndns.org/sdk/</ulink> são uma boa opção se você não deseja o trabalho de compilar tudo você mesmo."
#. Tag: para
#: faq_raster.xml:158
#, no-c-format
msgid "How can I add a PostGIS raster layer to my MapServer map?"
-msgstr ""
+msgstr "Como posso adicionar uma camada PostGIS Raster em meu mapa do MapServer?"
#. Tag: para
#: faq_raster.xml:162
#, no-c-format
msgid ""
-"First you need GDAL 1.7 or higher compiled with PostGIS raster support. GDAL "
-"1.8 or above is preferred since many issues have been fixed in 1.8 and more "
-"PostGIS raster issues fixed in trunk version."
-msgstr ""
+"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 "Primeiro você precisa da GDAL 1.7 ou maior, compilada com suporte ao PostGIS Raster. GDAL 1.8 ou maior é preferida, já que muitos problemas foram solucionados e muitas pendências com o PostGIS Raster resolvidas na versão trunk."
#. Tag: para
#: faq_raster.xml:164
#, no-c-format
msgid ""
-"You can much like you can with any other raster. Refer to <ulink url="
-"\"http://mapserver.org/input/raster.html\">MapServer Raster processing "
+"You can much like you can with any other raster. Refer to <ulink "
+"url=\"http://mapserver.org/input/raster.html\">MapServer Raster processing "
"options</ulink> for list of various processing functions you can use with "
"MapServer raster layers."
-msgstr ""
+msgstr "Você pode gostar muito do que pode ser feito com qualquer outro raster. Referência <ulink url=\"http://mapserver.org/input/raster.html\">MapServer Raster processing options</ulink> para listar várias funções de processamento que você pode utilizar com MapServer raster layers."
#. Tag: para
#: faq_raster.xml:167
"What makes PostGIS raster data particularly interesting, is that since each "
"tile can have various standard database columns, you can segment it in your "
"data source"
-msgstr ""
+msgstr "O que torna o PostGIS Raster tão interessante, é que cada tile pode ocupar diversas colunas padrão e você pode segmentar sua fonte de dados"
#. Tag: para
#: faq_raster.xml:169
msgid ""
"Below is an example of how you would define a PostGIS raster layer in "
"MapServer."
-msgstr ""
+msgstr "Abaixo está um exemplo de como você pode definir uma camada PostGIS Raster no MapServer."
#. Tag: para
#: faq_raster.xml:170
msgid ""
"The mode=2 is required for tiled rasters and was added in PostGIS 2.0 and "
"GDAL 1.8 drivers. This does not exist in GDAL 1.7 drivers."
-msgstr ""
+msgstr "O mode=2 é obrigatório para rasters dividos em tiles e este suporte foi adicionado no PostGIS 2.0 e nos drivers GDAL 1.8. Este suporte não existe na versão GDAL 1.7."
#. Tag: programlisting
#: faq_raster.xml:171
" 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"
" COLOR 0 255 0\n"
" END\n"
"END"
-msgstr ""
+msgstr "-- exibindo raster com opções padrões\n\nLAYER\n\nNAME coolwktraster\n\nTYPE raster\n\nSTATUS ON\n\nDATA \"PG:host=localhost port=5432 dbname='somedb' user='someuser' password='whatever' \n\nschema='someschema' table='cooltable' mode='2'\" \n\nPROCESSING \"NODATA=0\"\n\nPROCESSING \"SCALE=AUTO\"\n\n#... aqui, outras funções padrões de processamento raster\n\n#... classes são opcionais, mas úteis para 1 banda de dados\n\nCLASS\n\nNAME \"boring\"\n\nEXPRESSION ([pixel] < 20)\n\nCOLOR 250 250 250\n\nEND\n\nCLASS\n\nNAME \"mildly interesting\"\n\nEXPRESSION ([pixel] > 20 AND [pixel] < 1000)\n\nCOLOR 255 0 0\n\nEND\n\nCLASS\n\nNAME \"very interesting\"\n\nEXPRESSION ([pixel] >= 1000)\n\nCOLOR 0 255 0\n\nEND\n\nEND"
#. Tag: programlisting
#: faq_raster.xml:173
" 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"
"END"
-msgstr ""
+msgstr "-- exibindo raster com opções padrões e cláusula where\n\nLAYER\n\nNAME soil_survey2009\n\nTYPE raster\n\nSTATUS ON\n\nDATA \"PG:host=localhost port=5432 dbname='somedb' user='someuser' password='whatever' \n\nschema='someschema' table='cooltable' where='survey_year=2009' mode='2'\" \n\nPROCESSING \"NODATA=0\"\n\n#... aqui, outras funções padrões de processamento raster\n\n#... classes são opcionais, mas úteis para 1 banda de dados\n\nEND"
#. Tag: para
#: faq_raster.xml:181
#, no-c-format
msgid "What functions can I currently use with my raster data?"
-msgstr ""
+msgstr "Quais funcionalidades posso usar atualmente em meus dados raster?"
#. Tag: para
#: faq_raster.xml:185
msgid ""
"Refer to the list of <xref linkend=\"RT_reference\"/>. There are more, but "
"this is still a work in progress."
-msgstr ""
+msgstr "Se refere a lista <xref linkend=\"RT_reference\"/>. Existem mais, mas ainda está trabalhando na melhoria."
#. Tag: para
#: faq_raster.xml:187
#, no-c-format
msgid ""
-"Refer to the <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/"
-"PlanningAndFunding\">PostGIS Raster roadmap page</ulink> for details of what "
-"you can expect in the future."
-msgstr ""
+"Refer to the <ulink "
+"url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/PlanningAndFunding\">PostGIS"
+" Raster roadmap page</ulink> for details of what you can expect in the "
+"future."
+msgstr "Se refere a <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/PlanningAndFunding\">PostGIS Raster roadmap page</ulink> para detalhes do que você pode esperar para o futuro."
#. Tag: para
#: faq_raster.xml:195
msgid ""
"I am getting error ERROR: function st_intersects(raster, unknown) is not "
"unique or st_union(geometry,text) is not unique. How do I fix?"
-msgstr ""
+msgstr "Estou recebendo um erro ERROR: function st_intersects(raster, unknow) is not unique or st_union(geometry, text) is not unique. Como posso consertar este problema?"
#. Tag: para
#: faq_raster.xml:199
"The function is not unique error happens if one of your arguments is a "
"textual representation of a geometry instead of a geometry. In these cases, "
"PostgreSQL marks the textual representation as an unknown type, which means "
-"it can fall into the st_intersects(raster, geometry) or st_intersects(raster,"
-"raster) thus resulting in a non-unique case since both functions can in "
-"theory support your request. To prevent this, you need to cast the geometry "
-"to a geometry."
-msgstr ""
+"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 "Este erro ocorre se um de seus argumentos é uma representação textual de uma geometria ao invés de um objeto GEOMETRY. Nestes casos, PostgreSQL marca a representação textual como um tipo desconhecido, que significa que pode utilizar as funções st_intersects(raster, geometry) ou st_intersects(raster, raster), resultando em uma função não única, já que ambas, em teoria, poderiam suportar o pedido do usuário. Para prevenir isto, você deve converter sua representação textual da geometria para uma geometria de verdade (data type GEOMETRY)."
#. Tag: para
#: faq_raster.xml:200
#, no-c-format
msgid "For example if your code looks like this:"
-msgstr ""
+msgstr "Por exemplo, se seu código se parece com isto:"
#. Tag: programlisting
#: faq_raster.xml:201
"SELECT rast\n"
" FROM my_raster\n"
" WHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)');"
-msgstr ""
+msgstr "SELECT rast\n\nFROM my_raster\n\nWHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)');"
#. Tag: para
#: faq_raster.xml:202
#, no-c-format
msgid ""
-"Cast the textual geometry representation to a geometry by changing your code "
-"to this:"
-msgstr ""
+"Cast the textual geometry representation to a geometry by changing your code"
+" to this:"
+msgstr "Converta a representação textual geométrica para uma geometria, alterando seu código assim:"
#. Tag: programlisting
#: faq_raster.xml:203
"SELECT rast\n"
" FROM my_raster\n"
" WHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)'::geometry);"
-msgstr ""
+msgstr "SELECT rast\n\nFROM my_raster\n\nWHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)'::geometry);"
#. Tag: para
#: faq_raster.xml:211
msgid ""
"How is PostGIS Raster different from Oracle GeoRaster (SDO_GEORASTER) and "
"SDO_RASTER types?"
-msgstr ""
+msgstr "Como o PostGIS Raster é diferente do tipo Oracle GeoRaster (SDO_GEORASTER) e do tipo SDO_RASTER?"
#. Tag: para
#: faq_raster.xml:215
#, no-c-format
msgid ""
"For a more extensive discussion on this topic, check out Jorge Arévalo "
-"<ulink url=\"http://gis4free.wordpress.com/2010/07/19/oracle-georaster-part-"
-"i/\">Oracle GeoRaster and PostGIS Raster: First impressions </ulink>"
-msgstr ""
+"<ulink url=\"http://gis4free.wordpress.com/2010/07/19/oracle-georaster-"
+"part-i/\">Oracle GeoRaster and PostGIS Raster: First impressions </ulink>"
+msgstr "Para uma discurssão mais extensa sobre esse tópico, verifique Jorge Arévalo <ulink url=\"http://gis4free.wordpress.com/2010/07/19/oracle-georaster-part-i/\"> Oracle GeoRaster e PostGIS Raster: Primeiras impressões </ulink>"
#. Tag: para
#: faq_raster.xml:216
msgid ""
"The major advantage of one-georeference-by-raster over one-georeference-by-"
"layer is to allow:"
-msgstr ""
+msgstr "A maior vantagem do one-georeference-by-raster sobre one-georeference-by-layer é permitir:"
#. Tag: para
#: faq_raster.xml:217
#, no-c-format
msgid ""
"* coverages to be not necessarily rectangular (which is often the case of "
-"raster coverage covering large extents. See the possible raster arrangements "
-"in the documentation)"
-msgstr ""
+"raster coverage covering large extents. See the possible raster arrangements"
+" in the documentation)"
+msgstr "* coberturas não são necessariamente retangulares (que é frequentemente o caso do raster coverage cobrindo grandes extensões. Veja a possibilidade de arranjos raster na documentação)"
#. Tag: para
#: faq_raster.xml:218
msgid ""
"* rasters to overlaps (which is necessary to implement lossless vector to "
"raster conversion)"
-msgstr ""
+msgstr "* rasters para sobreposição (que é necessário para implementar perda de menos vetores para conversões raster)"
#. Tag: para
#: faq_raster.xml:219
"These arrangements are possible in Oracle as well, but they imply the "
"storage of multiple SDO_GEORASTER objects linked to as many SDO_RASTER "
"tables. A complex coverage can lead to hundreds of tables in the database. "
-"With PostGIS Raster you can store a similar raster arrangement into a unique "
-"table."
-msgstr ""
+"With PostGIS Raster you can store a similar raster arrangement into a unique"
+" table."
+msgstr "Estes arranjos também são possíveis no Oracle, mas eles implicam no armazenamento de múltiplos objetos SDO_GEORASTER conectados a muitas tabelas SDO_RASTER. Uma cobertura complexa pode liderar para centenas de tabelas no banco de dados. Com PostGIS Raster vocẽ pode gravar um arranjo raster similar dentro de uma única tabela."
#. Tag: para
#: faq_raster.xml:224
"Vector structures needs the flexibility to store discontinuous and non-"
"rectangular coverages. We think it is a big advantage that raster structure "
"should benefit as well."
-msgstr ""
+msgstr "É um pouco como se o PostGIS forçasse você a gravar apenas cobertura vetorial retangular cheia sem lacunas e sobreposições (uma perfeita camada topologica retangular). Isso é muito prático em algumas aplicações, mas na prática tem mostrado que não é realista ou desejável para a maioria das cobertura geográficas. Estruturas vetoriais necessitam da flexibilidade para gravar coberturas descontínuas e não retangulares. Nós acreditamos que uma grande vantagem que estruturas raster deveriam beneficiar também."
# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# Marcelo Soares Souza <marcelo@juntadados.org>, 2014
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2014-02-05 16:36+0000\n"
+"Last-Translator: Marcelo Soares Souza <marcelo@juntadados.org>\n"
+"Language-Team: Portuguese (Brazil) (http://www.transifex.com/projects/p/postgis-1/language/pt_BR/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: pt_BR\n"
+"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#. Tag: title
#: postgis.xml:106
#, no-c-format
msgid "PostGIS &last_release_version; Manual"
-msgstr ""
+msgstr "PostGIS &last_release_version; Manual"
#. Tag: affiliation
#: postgis.xml:114
#, no-c-format
msgid ""
-"<orgname><ulink url=\"http://www.cleverelephant.ca\">clever elephant</"
-"ulink></orgname> <address><city>Victoria</city> <state>British Columbia</"
-"state> <country>Canada</country> <email>pramsey@cleverelephant.ca</email></"
-"address>"
-msgstr ""
+"<orgname><ulink url=\"http://www.cleverelephant.ca\">clever "
+"elephant</ulink></orgname> <address><city>Victoria</city> <state>British "
+"Columbia</state> <country>Canada</country> "
+"<email>pramsey@cleverelephant.ca</email></address>"
+msgstr "<orgname><ulink url=\"http://www.cleverelephant.ca\">clever elephant</ulink></orgname> <address><city>Victoria</city> <state>British Columbia</state> <country>Canada</country> <email>pramsey@cleverelephant.ca</email></address>"
#. Tag: para
#: postgis.xml:124
"which allows GIS (Geographic Information Systems) objects to be stored in "
"the database. PostGIS includes support for GiST-based R-Tree spatial "
"indexes, and functions for analysis and processing of GIS objects."
-msgstr ""
+msgstr "PostGIS é uma extensão para o sistema de banco de dados objeto-relacional PostgreSQL que permite que objetos SIG (Sistema de Informação Geográfica) sejam armazenados em banco de dados. O PostGIS inclui suporte a índices espaciais baseado em GiST R-Tree, e funções para analise e processamento de objetos SIG."
#. Tag: para
#: postgis.xml:133
#, no-c-format
msgid "This is the manual for version &last_release_version;"
-msgstr ""
+msgstr "Este é o manual para a versão &last_release_version;"
#. Tag: para
#: postgis.xml:134
#, no-c-format
msgid ""
-"This work is licensed under a <ulink url=\"http://creativecommons.org/"
-"licenses/by-sa/3.0/\">Creative Commons Attribution-Share Alike 3.0 License</"
-"ulink>. Feel free to use this material any way you like, but we ask that you "
-"attribute credit to the PostGIS Project and wherever possible, a link back "
-"to <ulink url=\"http://www.postgis.org\">http://www.postgis.org</ulink>."
-msgstr ""
+"This work is licensed under a <ulink "
+"url=\"http://creativecommons.org/licenses/by-sa/3.0/\">Creative Commons "
+"Attribution-Share Alike 3.0 License</ulink>. Feel free to use this material "
+"any way you like, but we ask that you attribute credit to the PostGIS "
+"Project and wherever possible, a link back to <ulink "
+"url=\"http://www.postgis.org\">http://www.postgis.org</ulink>."
+msgstr "Este trabalho esta licenciado sobre a <ulink url=\"http://creativecommons.org/licenses/by-sa/3.0/\">Creative Commons Attribution-Share Alike 3.0 License</ulink>. Sinta-se livre para utilizar este material como quiser, mas pedimos que você atribua o crédito ao projeto PostGIS e sempre que possível cite o link <ulink url=\"http://www.postgis.org\">http://www.postgis.org</ulink>."
# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# Marcelo Soares Souza <marcelo@juntadados.org>, 2014
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2012-09-14 17:50+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2014-02-05 17:53+0000\n"
+"Last-Translator: Marcelo Soares Souza <marcelo@juntadados.org>\n"
+"Language-Team: Portuguese (Brazil) (http://www.transifex.com/projects/p/postgis-1/language/pt_BR/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: pt_BR\n"
+"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#. Tag: title
#: reference.xml:3
#, no-c-format
msgid "PostGIS Reference"
-msgstr ""
+msgstr "Referência do PostGIS"
#. Tag: para
#: reference.xml:5
"The functions given below are the ones which a user of PostGIS is likely to "
"need. There are other functions which are required support functions to the "
"PostGIS objects which are not of use to a general user."
-msgstr ""
+msgstr "As funções descritas abaixo são as que um usuário do PostGIS devem precisar. Existem outras funções que são necessárias para suportar os objetos PostGIS mas que não são de uso comum pelo usuário."
#. Tag: para
#: reference.xml:11
#, no-c-format
msgid ""
-"PostGIS has begun a transition from the existing naming convention to an SQL-"
-"MM-centric convention. As a result, most of the functions that you know and "
-"love have been renamed using the standard spatial type (ST) prefix. Previous "
-"functions are still available, though are not listed in this document where "
-"updated functions are equivalent. The non ST_ functions not listed in this "
-"documentation are deprecated and will be removed in a future release so STOP "
-"USING THEM."
-msgstr ""
+"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 "O PostGIS iniciou uma transição da convenção de nomenclatura existente para uma convenção em torno do SQL-MM. Como resultado, a maioria das funções que você conhece e ama foram renomeadas usando o padrão de tipo espacial (com o prefixo ST). As funções anteriores ainda existem, porém não são listadas nesta documentação onde as funções atualizadas são equivalentes. As funções que não possuem prefixo ST_ não listadas nesta documentação estão obsoletas e serão removidas em futuros lançamentos, então PAREM DE UTILIZÁ-LAS."
#. Tag: chapter
#: reference.xml:16
"&reference_operator; &reference_measure; &reference_processing; "
"&reference_lrs; &reference_transaction; &reference_misc; "
"&reference_exception;"
-msgstr ""
+msgstr "&reference_type; &reference_management; &reference_constructor; &reference_accessor; &reference_editor; &reference_output; &reference_operator; &reference_measure; &reference_processing; &reference_lrs; &reference_transaction; &reference_misc; &reference_exception;"
# SOME DESCRIPTIVE TITLE.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
-#, fuzzy
+#
+# Translators:
+# Dauro Lima Sobrinho <daurolima@gmail.com>, 2014
+# Marcelo Soares Souza <marcelo@juntadados.org>, 2014
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: PostGIS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2013-05-12 08:39+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
-"Language: \n"
+"PO-Revision-Date: 2014-08-01 21:21+0000\n"
+"Last-Translator: Dauro Lima Sobrinho <daurolima@gmail.com>\n"
+"Language-Team: Portuguese (Brazil) (http://www.transifex.com/projects/p/postgis-1/language/pt_BR/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Language: pt_BR\n"
+"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#. Tag: title
#: reference_sfcgal.xml:4
#, no-c-format
msgid "Using SFCGAL Advanced 2D/3D functions"
-msgstr ""
+msgstr "Utilizando funções SFCGAL 2D/3D avançadas"
#. Tag: para
#: reference_sfcgal.xml:5
#, no-c-format
msgid "TODO Introduction part"
-msgstr ""
+msgstr "Parte da Introdução do TODO"
#. Tag: para
#: reference_sfcgal.xml:8
#, no-c-format
msgid "TODO Install part"
-msgstr ""
+msgstr "Parte de Instalação do TODO"
#. Tag: refname
#: reference_sfcgal.xml:14
#, no-c-format
msgid "ST_Extrude"
-msgstr ""
+msgstr "ST_Extrude"
#. Tag: refpurpose
#: reference_sfcgal.xml:16
#, no-c-format
msgid "Extrude a surface to a related volume"
-msgstr ""
+msgstr "Extrude uma superfície a um volume relacionado"
#. Tag: funcprototype
#: reference_sfcgal.xml:21
"<paramdef><type>float</type> <parameter>x</parameter></paramdef> "
"<paramdef><type>float</type> <parameter>y</parameter></paramdef> "
"<paramdef><type>float</type> <parameter>z</parameter></paramdef>"
-msgstr ""
+msgstr "<funcdef>geometry <function>ST_Extrude</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef> <paramdef><type>float</type> <parameter>x</parameter></paramdef> <paramdef><type>float</type> <parameter>y</parameter></paramdef> <paramdef><type>float</type> <parameter>z</parameter></paramdef>"
#. Tag: title
#: reference_sfcgal.xml:32 reference_sfcgal.xml:61 reference_sfcgal.xml:90
#: reference_sfcgal.xml:206
#, no-c-format
msgid "Description"
-msgstr ""
+msgstr "Descrição"
#. Tag: para
#: reference_sfcgal.xml:34 reference_sfcgal.xml:63 reference_sfcgal.xml:92
#: reference_sfcgal.xml:208
#, no-c-format
msgid "Availability"
-msgstr ""
+msgstr "Disponibilidade"
#. Tag: para
#: reference_sfcgal.xml:35 reference_sfcgal.xml:64 reference_sfcgal.xml:93
#: reference_sfcgal.xml:209
#, no-c-format
msgid "&sfcgal_required;"
-msgstr ""
+msgstr "&sfcgal_required;"
#. Tag: para
#: reference_sfcgal.xml:36 reference_sfcgal.xml:65 reference_sfcgal.xml:94
#: reference_sfcgal.xml:210
#, no-c-format
msgid "&Z_support;"
-msgstr ""
+msgstr "&Z_support;"
#. Tag: para
#: reference_sfcgal.xml:37 reference_sfcgal.xml:66 reference_sfcgal.xml:95
#: reference_sfcgal.xml:211
#, no-c-format
msgid "&P_support;"
-msgstr ""
+msgstr "&P_support;"
#. Tag: para
#: reference_sfcgal.xml:38 reference_sfcgal.xml:67 reference_sfcgal.xml:96
#: reference_sfcgal.xml:212
#, no-c-format
msgid "&T_support;"
-msgstr ""
+msgstr "&T_support;"
#. Tag: refname
#: reference_sfcgal.xml:46
#, no-c-format
msgid "ST_StraightSkeleton"
-msgstr ""
+msgstr "ST_StraightSkeleton"
#. Tag: refpurpose
#: reference_sfcgal.xml:48
#, no-c-format
msgid "Compute a straight skeleton from a geometry"
-msgstr ""
+msgstr "Calcule um esqueleto em linha reta de uma geometria"
#. Tag: funcprototype
#: reference_sfcgal.xml:53
msgid ""
"<funcdef>geometry <function>ST_StraightSkeleton</function></funcdef> "
"<paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
-msgstr ""
+msgstr "<funcdef>geometry <function>ST_StraightSkeleton</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
#. Tag: refname
#: reference_sfcgal.xml:75
#, no-c-format
msgid "ST_IsPlanar"
-msgstr ""
+msgstr "ST_IsPlanar"
#. Tag: refpurpose
#: reference_sfcgal.xml:77
#, no-c-format
msgid "Check if a surface is or not planar"
-msgstr ""
+msgstr "Verifique se a superfície é ou não planar"
#. Tag: funcprototype
#: reference_sfcgal.xml:82
msgid ""
"<funcdef>boolean <function>ST_IsPlanar</function></funcdef> "
"<paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
-msgstr ""
+msgstr "<funcdef>boolean <function>ST_IsPlanar</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
#. Tag: refname
#: reference_sfcgal.xml:104
#, no-c-format
msgid "ST_Orientation"
-msgstr ""
+msgstr "ST_Orientation"
#. Tag: refpurpose
#: reference_sfcgal.xml:106
#, no-c-format
msgid "Determine surface orientation"
-msgstr ""
+msgstr "Determine orientação da superfície"
#. Tag: funcprototype
#: reference_sfcgal.xml:111
msgid ""
"<funcdef>integer <function>ST_Orientation</function></funcdef> "
"<paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
-msgstr ""
+msgstr "<funcdef>integer <function>ST_Orientation</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
#. Tag: refname
#: reference_sfcgal.xml:133
#, no-c-format
msgid "ST_ForceLHR"
-msgstr ""
+msgstr "ST_ForceLHR"
#. Tag: refpurpose
#: reference_sfcgal.xml:135
#, no-c-format
msgid "Force LHR orientation"
-msgstr ""
+msgstr "Orientação força LHR"
#. Tag: funcprototype
#: reference_sfcgal.xml:140
msgid ""
"<funcdef>geometry <function>ST_ForceLHR</function></funcdef> "
"<paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
-msgstr ""
+msgstr "<funcdef>geometry <function>ST_ForceLHR</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
#. Tag: refname
#: reference_sfcgal.xml:161
#, no-c-format
msgid "ST_MinkowskiSum"
-msgstr ""
+msgstr "ST_MinkowskiSum"
#. Tag: refpurpose
#: reference_sfcgal.xml:163
#, no-c-format
msgid "Perform Minkowski sum"
-msgstr ""
+msgstr "Executar soma Minkowski"
#. Tag: funcprototype
#: reference_sfcgal.xml:168
"<funcdef>geometry <function>ST_Minkowski</function></funcdef> "
"<paramdef><type>geometry</type> <parameter>geom1</parameter></paramdef> "
"<paramdef><type>geometry</type> <parameter>geom2</parameter></paramdef>"
-msgstr ""
+msgstr "<funcdef>geometry <function>ST_Minkowski</function></funcdef> <paramdef><type>geometry</type> <parameter>geom1</parameter></paramdef> <paramdef><type>geometry</type> <parameter>geom2</parameter></paramdef>"
#. Tag: refname
#: reference_sfcgal.xml:191
#, no-c-format
msgid "ST_Tesselate"
-msgstr ""
+msgstr "ST_Tesselate"
#. Tag: refpurpose
#: reference_sfcgal.xml:193
#, no-c-format
msgid "Perform surface Tesselation"
-msgstr ""
+msgstr "Realize Tesselation superfície"
#. Tag: funcprototype
#: reference_sfcgal.xml:198
msgid ""
"<funcdef>geometry <function>ST_Tesselate</function></funcdef> "
"<paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
-msgstr ""
+msgstr "<funcdef>geometry <function>ST_Tesselate</function></funcdef> <paramdef><type>geometry</type> <parameter>geom</parameter></paramdef>"
projects / postgis / commitdiff