1# SOME DESCRIPTIVE TITLE. 2# 3# Translators: 4# pibinko <pibinko@gmail.com>, 2013 5# pibinko <pibinko@gmail.com>, 2013 6# Sandro Santilli <strk.io>, 2015 7# Sandro Santilli <strk@kbt.io>, 2015 8# Sandro Santilli <strk@kbt.io>, 2015 9msgid "" 10msgstr "" 11"Project-Id-Version: PostGIS\n" 12"Report-Msgid-Bugs-To: https://bugs.kde.org\n" 13"POT-Creation-Date: 2021-09-11 01:55+0000\n" 14"PO-Revision-Date: 2018-07-22 02:56+0000\n" 15"Last-Translator: georgersilva <georger.silva@gmail.com>\n" 16"Language-Team: Italian (Italy) (http://www.transifex.com/postgis/postgis/" 17"language/it_IT/)\n" 18"Language: it_IT\n" 19"MIME-Version: 1.0\n" 20"Content-Type: text/plain; charset=UTF-8\n" 21"Content-Transfer-Encoding: 8bit\n" 22"Plural-Forms: nplurals=2; plural=(n != 1);\n" 23 24#. Tag: title 25#: installation.xml:3 26#, no-c-format 27msgid "PostGIS Installation" 28msgstr "Installazione PostGIS" 29 30#. Tag: para 31#: installation.xml:5 32#, no-c-format 33msgid "This chapter details the steps required to install PostGIS." 34msgstr "Questo capitolo elenca i passi necessari all'installazione di PostGIS." 35 36#. Tag: title 37#: installation.xml:10 38#, no-c-format 39msgid "Short Version" 40msgstr "Versione sintetica" 41 42#. Tag: para 43#: installation.xml:11 44#, no-c-format 45msgid "To compile assuming you have all the dependencies in your search path:" 46msgstr "" 47"Per compilare, assumendo di avere tutte le dipendenze nel percorso di " 48"ricerca:" 49 50#. Tag: programlisting 51#: installation.xml:12 52#, fuzzy, no-c-format 53msgid "" 54"tar -xvfz postgis-&last_release_version;.tar.gz\n" 55"cd postgis-&last_release_version;\n" 56"./configure\n" 57"make\n" 58"make install" 59msgstr "" 60"tar xvfz postgis-&last_release_version;.tar.gz\n" 61"cd postgis-&last_release_version;\n" 62"./configure\n" 63"make\n" 64"make install" 65 66#. Tag: para 67#: installation.xml:13 68#, fuzzy, no-c-format 69msgid "" 70"Once PostGIS is installed, it needs to be enabled (<xref linkend=" 71"\"create_spatial_db\"/>) or upgraded (<xref linkend=\"upgrading\"/>) in each " 72"individual database you want to use it in." 73msgstr "" 74"Una volta installato PostGIS, bisogna abilitarlo individualmente nei " 75"database in cui si vuole usare." 76 77#. Tag: title 78#: installation.xml:23 79#, no-c-format 80msgid "Compiling and Install from Source" 81msgstr "" 82 83#. Tag: para 84#: installation.xml:26 85#, no-c-format 86msgid "" 87"Many OS systems now include pre-built packages for PostgreSQL/PostGIS. In " 88"many cases compilation is only necessary if you want the most bleeding edge " 89"versions or you are a package maintainer." 90msgstr "" 91"Ormai molti sistemi operativi contengono pacchetti precompilati per " 92"PostgreSQL/PostGIS. In molti casi la compilazione è necessaria solamente se " 93"volete l'ultimissima versione o se siete uno dei manutentori dei pacchetti." 94 95#. Tag: para 96#: installation.xml:31 97#, no-c-format 98msgid "" 99"This section includes general compilation instructions, if you are compiling " 100"for Windows etc or another OS, you may find additional more detailed help at " 101"<ulink url=\"http://trac.osgeo.org/postgis/wiki/UsersWikiInstall\">PostGIS " 102"User contributed compile guides</ulink> and <ulink url=\"http://trac.osgeo." 103"org/postgis/wiki/DevWikiMain\">PostGIS Dev Wiki</ulink>." 104msgstr "" 105"Questo paragrafo comprende le istruzioni generali per la compilazione. Se " 106"state compilando su Windows o su un altro sistema operativo, potete trovare " 107"istruzioni più dettagliate alle pagine <ulink url=\"http://trac.osgeo.org/" 108"postgis/wiki/UsersWikiInstall\">PostGIS User contributed compile guides</" 109"ulink> e <ulink url=\"http://trac.osgeo.org/postgis/wiki/DevWikiMain" 110"\">PostGIS Dev Wiki</ulink>." 111 112#. Tag: para 113#: installation.xml:33 114#, no-c-format 115msgid "" 116"Pre-Built Packages for various OS are listed in <ulink url=\"http://trac." 117"osgeo.org/postgis/wiki/UsersWikiPackages\">PostGIS Pre-built Packages</ulink>" 118msgstr "" 119"I pacchetti precompilati per i vari sistemi operativi sono elencati alla " 120"pagina <ulink url=\"http://trac.osgeo.org/postgis/wiki/UsersWikiPackages" 121"\">PostGIS Pre-built Packages</ulink>" 122 123#. Tag: para 124#: installation.xml:34 125#, fuzzy, no-c-format 126msgid "" 127"If you are a windows user, you can get stable builds via Stackbuilder or " 128"<ulink url=\"https://postgis.net/windows_downloads\">PostGIS Windows " 129"download site</ulink> We also have <ulink url=\"https://postgis.net/" 130"windows_downloads\">very bleeding-edge windows experimental builds</ulink> " 131"that are built usually once or twice a week or whenever anything exciting " 132"happens. You can use these to experiment with the in progress releases of " 133"PostGIS" 134msgstr "" 135"Se siete un utente Windows, potete reperire le versioni stabili tramite " 136"Stackbuilder o la pagina <ulink url=\"http://www.postgis.org/download/" 137"windows/\">PostGIS Windows download</ulink>. Inoltre potete scaricare <ulink " 138"url=\"http://www.postgis.org/download/windows/experimental.php\">le " 139"ultimissime versioni sperimentati per Windows</ulink>, che vengono create " 140"una o due volte alla settimana, quando ci sono aggiornamenti interessanti. " 141"Potete utilizzare queste versioni per fare prove con le versioni in via di " 142"sviluppo di PostGIS" 143 144#. Tag: para 145#: installation.xml:39 146#, no-c-format 147msgid "" 148"The PostGIS module is an extension to the PostgreSQL backend server. As " 149"such, PostGIS &last_release_version; <emphasis>requires</emphasis> full " 150"PostgreSQL server headers access in order to compile. It can be built " 151"against PostgreSQL versions &min_postgres_version; or higher. Earlier " 152"versions of PostgreSQL are <emphasis>not</emphasis> supported." 153msgstr "" 154"Il modulo PostGIS è un'estensione del server PostgreSQL. Pertanto, + " 155"<emphasis>indispensabile</emphasis> che PostGIS &last_release_version; abbia " 156"pieno accesso agli header di PostgreSQL server per potersi compilare. Può " 157"essere compilato con versioni di PostgreSQL dalla &min_postgres_version; " 158"in su. Le versioni precedenti di PostgreSQL <emphasis>non</emphasis> sono " 159"supportate." 160 161#. Tag: para 162#: installation.xml:47 163#, no-c-format 164msgid "" 165"Refer to the PostgreSQL installation guides if you haven't already installed " 166"PostgreSQL. <ulink url=\"http://www.postgresql.org\"> http://www.postgresql." 167"org </ulink> ." 168msgstr "" 169"Vi rimandiamo alle guide per l'installazione di PostgreSQL, se questo non è " 170"stato ancora installato. <ulink url=\"http://www.postgresql.org\"> http://" 171"www.postgresql.org </ulink> ." 172 173#. Tag: para 174#: installation.xml:57 175#, no-c-format 176msgid "" 177"For GEOS functionality, when you install PostgresSQL you may need to " 178"explicitly link PostgreSQL against the standard C++ library:" 179msgstr "" 180"Per le funzionalità legate a GEOS, quando installate PostgresSQL è possibile " 181"che dobbiate esplicitamente linkare PostgreSQL con la libreria C++ standard:" 182 183#. Tag: programlisting 184#: installation.xml:62 185#, no-c-format 186msgid "LDFLAGS=-lstdc++ ./configure [YOUR OPTIONS HERE]" 187msgstr "LDFLAGS=-lstdc++ ./configure [INSERITE QUI LE VOSTRE OPZIONI]" 188 189#. Tag: para 190#: installation.xml:64 191#, no-c-format 192msgid "" 193"This is a workaround for bogus C++ exceptions interaction with older " 194"development tools. If you experience weird problems (backend unexpectedly " 195"closed or similar things) try this trick. This will require recompiling your " 196"PostgreSQL from scratch, of course." 197msgstr "" 198"Questa è una soluzione alla buona per l'interazione con finte eccezioni C++ " 199"con gli strumenti di sviluppo più datati. Se riscontrate problemi anomali " 200"(chiusura inattesa del server o casi simili), provate questo trucco. Ciò " 201"richiederà ovviamente di ricompilare PostgreSQL da zero." 202 203#. Tag: para 204#: installation.xml:72 205#, no-c-format 206msgid "" 207"The following steps outline the configuration and compilation of the PostGIS " 208"source. They are written for Linux users and will not work on Windows or Mac." 209msgstr "" 210"I passaggi seguenti ripercorrono la procedura per configurare e compilare il " 211"sorgente di PostGIS. Sono scritti per utenti Linux e non funzioneranno su " 212"Windows o Mac." 213 214#. Tag: title 215#: installation.xml:79 216#, no-c-format 217msgid "Getting the Source" 218msgstr "Reperire il codice sorgente" 219 220#. Tag: para 221#: installation.xml:81 222#, no-c-format 223msgid "" 224"Retrieve the PostGIS source archive from the downloads website <ulink url=" 225"\"&postgis_download_url;\"> &postgis_download_url; </ulink>" 226msgstr "" 227 228#. Tag: programlisting 229#: installation.xml:88 230#, no-c-format 231msgid "" 232"wget &postgis_download_url;\n" 233"tar -xvzf postgis-&last_release_version;.tar.gz" 234msgstr "" 235 236#. Tag: para 237#: installation.xml:90 238#, no-c-format 239msgid "" 240"This will create a directory called <varname>postgis-&last_release_version;</" 241"varname> in the current working directory." 242msgstr "" 243"Questo passaggio creerà una cartella denominata <varname>postgis-" 244"&last_release_version;</varname> nella cartella di lavoro attuale." 245 246#. Tag: para 247#: installation.xml:96 248#, fuzzy, no-c-format 249msgid "" 250"Alternatively, checkout the source from the <ulink url=\"https://git-scm.com/" 251"\"> git </ulink> repository <ulink url=\"https://git.osgeo.org/gitea/postgis/" 252"postgis/\"> https://git.osgeo.org/gitea/postgis/postgis/ </ulink> ." 253msgstr "" 254"In alternativa, potete eseguire un checkout del sorgente dalla repository " 255"<ulink url=\"http://subversion.apache.org/\"> svn </ulink> <ulink url=" 256"\"http://svn.osgeo.org/postgis/trunk/\"> http://svn.osgeo.org/postgis/trunk/ " 257"</ulink> ." 258 259#. Tag: programlisting 260#: installation.xml:108 261#, no-c-format 262msgid "git clone https://git.osgeo.org/gitea/postgis/postgis.git postgis" 263msgstr "" 264 265#. Tag: para 266#: installation.xml:110 267#, fuzzy, no-c-format 268msgid "" 269"Change into the newly created <varname>postgis</varname> directory to " 270"continue the installation." 271msgstr "" 272"Entrate nella cartella appena creata, <varname>postgis-&last_release_version;" 273"</varname>, per proseguire con l'installazione." 274 275#. Tag: title 276#: installation.xml:118 277#, no-c-format 278msgid "Install Requirements" 279msgstr "" 280 281#. Tag: para 282#: installation.xml:120 283#, no-c-format 284msgid "PostGIS has the following requirements for building and usage:" 285msgstr "" 286"PostGIS necessita dei seguenti requisiti per la compilazione e l'utilizzo:" 287 288#. Tag: emphasis 289#: installation.xml:125 290#, no-c-format 291msgid "Required" 292msgstr "Necessari" 293 294#. Tag: para 295#: installation.xml:130 296#, no-c-format 297msgid "" 298"PostgreSQL &min_postgres_version; or higher. A complete installation of " 299"PostgreSQL (including server headers) is required. PostgreSQL is available " 300"from <ulink url=\"http://www.postgresql.org\"> http://www.postgresql.org </" 301"ulink> ." 302msgstr "" 303"PostgreSQL &min_postgres_version; o versioni superiori. E' necessaria " 304"un'installazione completa di PostgreSQL (compresi gli header del server). " 305"PostgreSQL è disponibile al sito <ulink url=\"http://www.postgresql.org\"> " 306"http://www.postgresql.org </ulink> ." 307 308#. Tag: para 309#: installation.xml:139 310#, no-c-format 311msgid "" 312"For a full PostgreSQL / PostGIS support matrix and PostGIS/GEOS support " 313"matrix refer to <ulink url=\"http://trac.osgeo.org/postgis/wiki/" 314"UsersWikiPostgreSQLPostGIS\">http://trac.osgeo.org/postgis/wiki/" 315"UsersWikiPostgreSQLPostGIS</ulink>" 316msgstr "" 317"Per una matrice di supporto completa per PostgreSQL / PostGIS e PostGIS/GEOS " 318"vi rimandiamo a <ulink url=\"http://trac.osgeo.org/postgis/wiki/" 319"UsersWikiPostgreSQLPostGIS\">http://trac.osgeo.org/postgis/wiki/" 320"UsersWikiPostgreSQLPostGIS</ulink>" 321 322#. Tag: para 323#: installation.xml:145 324#, no-c-format 325msgid "" 326"GNU C compiler (<filename>gcc</filename>). Some other ANSI C compilers can " 327"be used to compile PostGIS, but we find far fewer problems when compiling " 328"with <filename>gcc</filename>." 329msgstr "" 330"Compilatore GNU C (<filename>gcc</filename>). Per la compilazione possono " 331"essere utilizzati anche altri compilatori ANSI C, ma abbiamo riscontrato " 332"molti meno problemi nella compilazione con <filename>gcc</filename>." 333 334#. Tag: para 335#: installation.xml:153 336#, no-c-format 337msgid "" 338"GNU Make (<filename>gmake</filename> or <filename>make</filename>). For many " 339"systems, GNU <filename>make</filename> is the default version of make. Check " 340"the version by invoking <filename>make -v</filename>. Other versions of " 341"<filename>make</filename> may not process the PostGIS <filename>Makefile</" 342"filename> properly." 343msgstr "" 344"GNU Make (<filename>gmake</filename> or <filename>make</filename>). Per " 345"molti sistem, GNU <filename>make</filename> è la versione di default di " 346"make. Potete controllare la versione tramite il comando <filename>make -v</" 347"filename>. Altre versioni di <filename>make</filename> potrebbero non " 348"elaborare il <filename>Makefile</filename> di PostGIS in modo corretto." 349 350#. Tag: para 351#: installation.xml:163 352#, no-c-format 353msgid "" 354"Proj reprojection library. Proj 4.9 or above is required. The Proj library " 355"is used to provide coordinate reprojection support within PostGIS. Proj is " 356"available for download from <ulink url=\"https://proj.org/\"> https://proj." 357"org/ </ulink> ." 358msgstr "" 359 360#. Tag: para 361#: installation.xml:175 362#, no-c-format 363msgid "" 364"GEOS geometry library, version 3.6 or greater, but GEOS 3.9+ is required to " 365"take full advantage of all the new functions and features. GEOS is available " 366"for download from <ulink url=\"http://trac.osgeo.org/geos/\"> http://trac." 367"osgeo.org/geos/ </ulink>." 368msgstr "" 369 370#. Tag: para 371#: installation.xml:183 372#, no-c-format 373msgid "" 374"LibXML2, version 2.5.x or higher. LibXML2 is currently used in some imports " 375"functions (ST_GeomFromGML and ST_GeomFromKML). LibXML2 is available for " 376"download from <ulink url=\"http://xmlsoft.org/downloads.html\">http://" 377"xmlsoft.org/downloads.html</ulink>." 378msgstr "" 379"LibXML2, versione 2.5.x superiore. LibXML2 è attualmente usata per alcune " 380"delle funzioni di importazione (ST_GeomFromGML and ST_GeomFromKML). LibXML2 " 381"può essere scaricata da <ulink url=\"http://xmlsoft.org/downloads.html" 382"\">http://xmlsoft.org/downloads.html</ulink>." 383 384#. Tag: para 385#: installation.xml:190 386#, no-c-format 387msgid "" 388"JSON-C, version 0.9 or higher. JSON-C is currently used to import GeoJSON " 389"via the function ST_GeomFromGeoJson. JSON-C is available for download from " 390"<ulink url=\"https://github.com/json-c/json-c/releases\">https://github.com/" 391"json-c/json-c/releases/</ulink>." 392msgstr "" 393 394#. Tag: para 395#: installation.xml:198 396#, no-c-format 397msgid "" 398"GDAL, version 2+ is required 3+ is preferred. This is required for raster " 399"support. <ulink url=\"http://trac.osgeo.org/gdal/wiki/DownloadSource" 400"\">http://trac.osgeo.org/gdal/wiki/DownloadSource</ulink>." 401msgstr "" 402 403#. Tag: para 404#: installation.xml:206 405#, fuzzy, no-c-format 406msgid "" 407"If compiling with PostgreSQL+JIT, LLVM version >=6 is required <ulink url=" 408"\"https://trac.osgeo.org/postgis/ticket/4125\">https://trac.osgeo.org/" 409"postgis/ticket/4125</ulink>." 410msgstr "" 411"Attualmente questo parametro non funzione, dato che il pacchetto si " 412"installerà solamente nella cartella di installazione di PostgreSQL. Potete " 413"visitare la pagina <ulink url=\"http://trac.osgeo.org/postgis/ticket/635\"> " 414"http://trac.osgeo.org/postgis/ticket/635 </ulink> per seguire l'evoluzione " 415"di questo bug." 416 417#. Tag: emphasis 418#: installation.xml:215 419#, no-c-format 420msgid "Optional" 421msgstr "Opzionali" 422 423#. Tag: para 424#: installation.xml:220 425#, no-c-format 426msgid "" 427"GDAL (pseudo optional) only if you don't want raster you can leave it out. " 428"Also make sure to enable the drivers you want to use as described in <xref " 429"linkend=\"raster_configuration\"/>." 430msgstr "" 431 432#. Tag: para 433#: installation.xml:228 434#, no-c-format 435msgid "" 436"GTK (requires GTK+2.0, 2.8+) to compile the shp2pgsql-gui shape file loader. " 437"<ulink url=\"http://www.gtk.org/\"> http://www.gtk.org/ </ulink> ." 438msgstr "" 439"GTK (è necessario GTK+2.0, 2.8+) serve per compilare il loader shp2pgsql-gui " 440"shape. <ulink url=\"http://www.gtk.org/\"> http://www.gtk.org/ </ulink> ." 441 442#. Tag: para 443#: installation.xml:238 444#, no-c-format 445msgid "" 446"SFCGAL, version 1.3.1 (or higher) could be used to provide additional 2D and " 447"3D advanced analysis functions to PostGIS cf <xref linkend=\"reference_sfcgal" 448"\"/>. And also allow to use SFCGAL rather than GEOS for some 2D functions " 449"provided by both backends (like ST_Intersection or ST_Area, for instance). A " 450"PostgreSQL configuration variable <code>postgis.backend</code> allow end " 451"user to control which backend he want to use if SFCGAL is installed (GEOS by " 452"default). Nota: SFCGAL 1.2 require at least CGAL 4.3 and Boost 1.54 (cf: " 453"<ulink url=\"https://oslandia.gitlab.io/SFCGAL/dev.html\">https://oslandia." 454"gitlab.io/SFCGAL/dev.html</ulink>) <ulink url=\"https://gitlab.com/Oslandia/" 455"SFCGAL/\">https://gitlab.com/Oslandia/SFCGAL/</ulink>." 456msgstr "" 457 458#. Tag: para 459#: installation.xml:246 460#, no-c-format 461msgid "" 462"In order to build the <xref linkend=\"Address_Standardizer\"/> you will also " 463"need PCRE <ulink url=\"http://www.pcre.org\">http://www.pcre.org</ulink> " 464"(which generally is already installed on nix systems). <code>Regex::" 465"Assemble</code> perl CPAN package is only needed if you want to rebuild the " 466"data encoded in <filename>parseaddress-stcities.h</filename>. <xref linkend=" 467"\"Address_Standardizer\"/> will automatically be built if it detects a PCRE " 468"library, or you pass in a valid <varname>--with-pcre-dir=/path/to/pcre</" 469"varname> during configure." 470msgstr "" 471 472#. Tag: para 473#: installation.xml:253 474#, no-c-format 475msgid "" 476"To enable ST_AsMVT protobuf-c library 1.1.0 or higher (for usage) and the " 477"protoc-c compiler (for building) are required. Also, pkg-config is required " 478"to verify the correct minimum version of protobuf-c. See <ulink url=" 479"\"https://github.com/protobuf-c/protobuf-c\">protobuf-c</ulink>. By default, " 480"Postgis will use Wagyu to validate MVT polygons faster which requires a c+" 481"+11 compiler. It will use CXXFLAGS and the same compiler as the PostgreSQL " 482"installation. To disable this and use GEOS instead use the <varname>--" 483"without-wagyu</varname> during the configure step." 484msgstr "" 485 486#. Tag: para 487#: installation.xml:262 488#, no-c-format 489msgid "" 490"CUnit (<filename>CUnit</filename>). This is needed for regression testing. " 491"<ulink url=\"http://cunit.sourceforge.net/\">http://cunit.sourceforge.net/</" 492"ulink>" 493msgstr "" 494"CUnit (<filename>CUnit</filename>). Serve per i collaudi di regressione. " 495"<ulink url=\"http://cunit.sourceforge.net/\">http://cunit.sourceforge.net/</" 496"ulink>" 497 498#. Tag: para 499#: installation.xml:268 500#, no-c-format 501msgid "" 502"DocBook (<filename>xsltproc</filename>) is required for building the " 503"documentation. Docbook is available from <ulink url=\"http://www.docbook.org/" 504"\"> http://www.docbook.org/ </ulink> ." 505msgstr "" 506"DocBook (<filename>xsltproc</filename>) è necessario per creare la " 507"documentazione. Docbook è disponibile sul sito <ulink url=\"http://www." 508"docbook.org/\"> http://www.docbook.org/ </ulink> ." 509 510#. Tag: para 511#: installation.xml:279 512#, no-c-format 513msgid "" 514"DBLatex (<filename>dblatex</filename>) is required for building the " 515"documentation in PDF format. DBLatex is available from <ulink url=\"http://" 516"dblatex.sourceforge.net/\"> http://dblatex.sourceforge.net/ </ulink> ." 517msgstr "" 518"DBLatex (<filename>dblatex</filename>) è necessario per creare la " 519"documentazione in formato PDF. DBLatex è disponibile dal sito <ulink url=" 520"\"http://dblatex.sourceforge.net/\"> http://dblatex.sourceforge.net/ </" 521"ulink> ." 522 523#. Tag: para 524#: installation.xml:290 525#, no-c-format 526msgid "" 527"ImageMagick (<filename>convert</filename>) is required to generate the " 528"images used in the documentation. ImageMagick is available from <ulink url=" 529"\"http://www.imagemagick.org/\"> http://www.imagemagick.org/ </ulink> ." 530msgstr "" 531"ImageMagick (<filename>convert</filename>) viene utilizzato per generare le " 532"immagini utilizzate nella documentazione. ImageMagick è disponibile sul sito " 533"<ulink url=\"http://www.imagemagick.org/\"> http://www.imagemagick.org/ </" 534"ulink> ." 535 536#. Tag: title 537#: installation.xml:304 538#, fuzzy, no-c-format 539msgid "Build configuration" 540msgstr "Configurazione" 541 542#. Tag: para 543#: installation.xml:306 544#, no-c-format 545msgid "" 546"As with most linux installations, the first step is to generate the Makefile " 547"that will be used to build the source code. This is done by running the " 548"shell script" 549msgstr "" 550"Come in molte installazioni Linux, il primo passo consiste nel generare il " 551"Makefile che sarà poi utilizzato che compilare il codice sorgente. Per " 552"questo si esegue lo script da shell" 553 554#. Tag: para 555#: installation.xml:316 556#, no-c-format 557msgid "" 558"With no additional parameters, this command will attempt to automatically " 559"locate the required components and libraries needed to build the PostGIS " 560"source code on your system. Although this is the most common usage of " 561"<command>./configure</command>, the script accepts several parameters for " 562"those who have the required libraries and programs in non-standard locations." 563msgstr "" 564"Se non si specificano parametri aggiuntivi, questo comando cercherà di " 565"individuare automaticamente le componenti e le librerie necessarie per " 566"compilare il codice sorgente PostGIS sul vostro sistema. Benché questa sia " 567"la modalità di utilizzo più comune per <command>./configure</command>, lo " 568"script accetta vari parametri per coloro che tengono le librerie e i " 569"programmi necessari in percorsi non standard." 570 571#. Tag: para 572#: installation.xml:324 573#, no-c-format 574msgid "" 575"The following list shows only the most commonly used parameters. For a " 576"complete list, use the <command>--help</command> or <command>--help=short</" 577"command> parameters." 578msgstr "" 579"La lista seguente riporta solamente i parametri usati più di frequente. Per " 580"una lista completa, utilizzate i parametri <command>--help</command> o " 581"<command>--help=short</command>." 582 583#. Tag: para 584#: installation.xml:334 585#, no-c-format 586msgid "" 587"Starting with PostGIS 3.0, the library files generated by default will no " 588"longer have the minor version as part of the file name. This means all " 589"PostGIS 3 libs will end in <code>postgis-3</code>. This was done to make " 590"pg_upgrade easier, with downside that you can only install one version " 591"PostGIS 3 series in your server. To get the old behavior of file including " 592"the minor version: e.g. <code>postgis-3.0</code> add this switch to your " 593"configure statement." 594msgstr "" 595 596#. Tag: para 597#: installation.xml:349 598#, fuzzy, no-c-format 599msgid "" 600"This is the location the PostGIS loader executables and shared libs will be " 601"installed. By default, this location is the same as the detected PostgreSQL " 602"installation." 603msgstr "" 604"Questo è il percorso in cui saranno installate le librerie PostGIS e gli " 605"script SQL. Come default, questo percorso coincide con quello rilevato per " 606"l'installazione di PostgreSQL." 607 608#. Tag: para 609#: installation.xml:356 610#, no-c-format 611msgid "" 612"This parameter is currently broken, as the package will only install into " 613"the PostgreSQL installation directory. Visit <ulink url=\"http://trac.osgeo." 614"org/postgis/ticket/635\"> http://trac.osgeo.org/postgis/ticket/635 </ulink> " 615"to track this bug." 616msgstr "" 617"Attualmente questo parametro non funzione, dato che il pacchetto si " 618"installerà solamente nella cartella di installazione di PostgreSQL. Potete " 619"visitare la pagina <ulink url=\"http://trac.osgeo.org/postgis/ticket/635\"> " 620"http://trac.osgeo.org/postgis/ticket/635 </ulink> per seguire l'evoluzione " 621"di questo bug." 622 623#. Tag: para 624#: installation.xml:371 625#, no-c-format 626msgid "" 627"PostgreSQL provides a utility called <command>pg_config</command> to enable " 628"extensions like PostGIS to locate the PostgreSQL installation directory. Use " 629"this parameter (<command>--with-pgconfig=/path/to/pg_config</command>) to " 630"manually specify a particular PostgreSQL installation that PostGIS will " 631"build against." 632msgstr "" 633"PostgreSQL fornisce una utility chiamata <command>pg_config</command> per " 634"consentire a estensioni quali PostGIS di individuare la cartella di " 635"installazione di PostgreSQL. Utilizzate questo parametro (<command>--with-" 636"pgconfig=/path/to/pg_config</command>) per specificare manualmente una " 637"particolare installazione di PostgreSQL per la quale PostGIS sarà compilato." 638 639#. Tag: para 640#: installation.xml:385 641#, no-c-format 642msgid "" 643"GDAL, a required library, provides functionality needed for raster support " 644"<command>gdal-config</command> to enable software installations to locate " 645"the GDAL installation directory. Use this parameter (<command>--with-" 646"gdalconfig=/path/to/gdal-config</command>) to manually specify a particular " 647"GDAL installation that PostGIS will build against." 648msgstr "" 649"GDAL è una libreria necessaria per il supporto raster. Utilizzare il comando " 650"<command>gdal-config</command> per consentire all'installazione di " 651"individuare la cartella di installazione di GDAL, oppure utilizzare il " 652"parametro <command>--with-gdalconfig=/path/to/gdal-config</command> per " 653"indicare manualmente specifica installazione di GDAL con cui compilare " 654"PostGIS." 655 656#. Tag: para 657#: installation.xml:399 658#, no-c-format 659msgid "" 660"GEOS, a required geometry library, provides a utility called <command>geos-" 661"config</command> to enable software installations to locate the GEOS " 662"installation directory. Use this parameter (<command>--with-geosconfig=/path/" 663"to/geos-config</command>) to manually specify a particular GEOS installation " 664"that PostGIS will build against." 665msgstr "" 666"GEOS, una libreria necessaria per gestire le geometrie, fornisce una utility " 667"chiamata <command>geos-config</command> per consentire alla procedura di " 668"installazione di individuare la cartella di installazione di GEOS. E' " 669"possibile utilizzare questo parametro (<command>--with-geosconfig=/path/to/" 670"geos-config</command>) per indicare manualmente una specifica installazione " 671"di GEO da utilizzare per la compilazione." 672 673#. Tag: para 674#: installation.xml:413 675#, no-c-format 676msgid "" 677"LibXML is the library required for doing GeomFromKML/GML processes. It " 678"normally is found if you have libxml installed, but if not or you want a " 679"specific version used, you'll need to point PostGIS at a specific " 680"<filename>xml2-config</filename> confi file to enable software installations " 681"to locate the LibXML installation directory. Use this parameter (<command>>--" 682"with-xml2config=/path/to/xml2-config</command>) to manually specify a " 683"particular LibXML installation that PostGIS will build against." 684msgstr "" 685"LibXML è la libreria richiesta dai comandi GeomFromKML/GML. Se la libreria è " 686"installata, viene normalmente localizzata automaticamente, ma se non è " 687"installata, o se volete utilizzare una versione specifica, dovete rimandare " 688"PostGIS a uno specifico file di configurazione <filename>xml2-config</" 689"filename> per consentire all'installazione di localizzare la cartella di " 690"installazione di LibXML. Utilizzate questo parametro (<command>>--with-" 691"xml2config=/path/to/xml2-config</command>) per indicare manualmente il " 692"riferimento a una specifica installazione di LibXML per la compilazione di " 693"PostGIS." 694 695#. Tag: para 696#: installation.xml:431 697#, fuzzy, no-c-format 698msgid "" 699"Proj is a reprojection library required by PostGIS. Use this parameter " 700"(<command>--with-projdir=/path/to/projdir</command>) to manually specify a " 701"particular Proj installation directory that PostGIS will build against." 702msgstr "" 703"Proj4 è una libreria di riproiezione richiesta da PostGIS. Utilizzate questo " 704"parametro (<command>--with-projdir=/path/to/projdir</command>) per indicare " 705"manualmente una specifica cartella di installazione di Proj4 per la " 706"compilazione di PostGIS." 707 708#. Tag: para 709#: installation.xml:443 710#, no-c-format 711msgid "Directory where iconv is installed." 712msgstr "Cartella di installazione di iconv." 713 714#. Tag: para 715#: installation.xml:452 716#, no-c-format 717msgid "" 718"<ulink url=\"http://oss.metaparadigm.com/json-c/\">JSON-C</ulink> is an MIT-" 719"licensed JSON library required by PostGIS ST_GeomFromJSON support. Use this " 720"parameter (<command>--with-jsondir=/path/to/jsondir</command>) to manually " 721"specify a particular JSON-C installation directory that PostGIS will build " 722"against." 723msgstr "" 724"<ulink url=\"http://oss.metaparadigm.com/json-c/\">JSON-C</ulink> è una " 725"libreria JSON con licenza MIR utilizzata da PostGIS per supportare " 726"ST_GeomFromJSON. Utilizzare questo parametro (<command>--with-jsondir=/path/" 727"to/jsondir</command>) per indicare manualmente una specifica cartella di " 728"installazione che PostGIS userà per la compilazione." 729 730#. Tag: para 731#: installation.xml:464 732#, no-c-format 733msgid "" 734"<ulink url=\"http://www.pcre.org/\">PCRE</ulink> is an BSD-licensed Perl " 735"Compatible Regular Expression library required by address_standardizer " 736"extension. Use this parameter (<command>--with-pcredir=/path/to/pcredir</" 737"command>) to manually specify a particular PCRE installation directory that " 738"PostGIS will build against." 739msgstr "" 740 741#. Tag: para 742#: installation.xml:476 743#, no-c-format 744msgid "" 745"Compile the data import GUI (requires GTK+2.0). This will create shp2pgsql-" 746"gui graphical interface to shp2pgsql." 747msgstr "" 748"Compilare l'interfaccia grafica per l'importazione di dati (richiede GTK" 749"+2.0). Questo passaggio creerà shp2pgsql-gui, interfaccia grafica per " 750"shp2pgsql." 751 752#. Tag: para 753#: installation.xml:485 754#, fuzzy, no-c-format 755msgid "Compile without raster support." 756msgstr "Installazione del supporto raster" 757 758#. Tag: para 759#: installation.xml:493 760#, no-c-format 761msgid "" 762"Disable topology support. There is no corresponding library as all logic " 763"needed for topology is in postgis-&last_release_version; library." 764msgstr "" 765 766#. Tag: para 767#: installation.xml:502 768#, no-c-format 769msgid "" 770"By default PostGIS will try to detect gettext support and compile with it, " 771"however if you run into incompatibility issues that cause breakage of " 772"loader, you can disable it entirely with this command. Refer to ticket " 773"<ulink url=\"http://trac.osgeo.org/postgis/ticket/748\">http://trac.osgeo." 774"org/postgis/ticket/748</ulink> for an example issue solved by configuring " 775"with this. NOTE: that you aren't missing much by turning this off. This is " 776"used for international help/label support for the GUI loader which is not " 777"yet documented and still experimental." 778msgstr "" 779"Normalmente PostGIS cercherà di rilevare il supporto per gettext e di " 780"utilizzarlo nella compilazione. Tuttavia, se risocontrate problemi di " 781"compatibilità che determinano interruzioni del loader, potete disabilitare " 782"il supporto con questo comando. Potete fare riferimento al ticket <ulink " 783"url=\"http://trac.osgeo.org/postgis/ticket/748\">http://trac.osgeo.org/" 784"postgis/ticket/748</ulink> per un esempio di un caso risolto utilizzando " 785"questa particolare configurazione. NOTA: disattivanto questa opzione non vi " 786"perdete molto, dato che è utilizzata per il supporto internazionale o per le " 787"etichette nel loader, che non sono ancora ben documentate e in forma " 788"sperimentale." 789 790#. Tag: para 791#: installation.xml:513 792#, no-c-format 793msgid "" 794"By default PostGIS will not install with sfcgal support without this switch. " 795"<varname>PATH</varname> is an optional argument that allows to specify an " 796"alternate PATH to sfcgal-config." 797msgstr "" 798 799#. Tag: para 800#: installation.xml:522 801#, no-c-format 802msgid "" 803"Disable updating postgis_revision.h to match current HEAD of the git " 804"repository." 805msgstr "" 806 807#. Tag: para 808#: installation.xml:529 809#, fuzzy, no-c-format 810msgid "" 811"If you obtained PostGIS from the <ulink url=\"https://trac.osgeo.org/postgis/" 812"wiki/CodeRepository\"> code repository </ulink> , the first step is really " 813"to run the script" 814msgstr "" 815"Se avete ottenuto PostGIS dalla <ulink url=\"http://svn.osgeo.org/postgis/" 816"trunk/\"> repository </ulink> SVN , il primo passo consiste nell'eseguire lo " 817"script" 818 819#. Tag: para 820#: installation.xml:541 821#, no-c-format 822msgid "" 823"This script will generate the <command>configure</command> script that in " 824"turn is used to customize the installation of PostGIS." 825msgstr "" 826"Questo script genererà lo script <command>configure</command>, che a sua " 827"volta viente utilizzato per personalizzare l'installazione di PostGIS." 828 829#. Tag: para 830#: installation.xml:546 831#, no-c-format 832msgid "" 833"If you instead obtained PostGIS as a tarball, running <command>./autogen.sh</" 834"command> is not necessary as <command>configure</command> has already been " 835"generated." 836msgstr "" 837"Se invece avete ottenuto PostGIS come file tar, non sarà necessario eseguire " 838"<command>./autogen.sh</command>, dato che <command>configure</command> sarà " 839"già stato generato." 840 841#. Tag: title 842#: installation.xml:555 843#, no-c-format 844msgid "Building" 845msgstr "Compilazione" 846 847#. Tag: para 848#: installation.xml:557 849#, no-c-format 850msgid "" 851"Once the Makefile has been generated, building PostGIS is as simple as " 852"running" 853msgstr "" 854"Una volta creato il Makefile, compilare PostGIS è semplice come eseguire" 855 856#. Tag: para 857#: installation.xml:566 858#, no-c-format 859msgid "" 860"The last line of the output should be \"<code>PostGIS was built " 861"successfully. Ready to install.</code>\"" 862msgstr "" 863"L'ultima linea dei messaggi in uscita dovrebbe essere \"<code>PostGIS was " 864"built successfully. Ready to install.</code>\"" 865 866#. Tag: para 867#: installation.xml:571 868#, no-c-format 869msgid "" 870"As of PostGIS v1.4.0, all the functions have comments generated from the " 871"documentation. If you wish to install these comments into your spatial " 872"databases later, run the command which requires docbook. The " 873"postgis_comments.sql and other package comments files raster_comments.sql, " 874"topology_comments.sql are also packaged in the tar.gz distribution in the " 875"doc folder so no need to make comments if installing from the tar ball. " 876"Comments are also included as part of the CREATE EXTENSION install." 877msgstr "" 878 879#. Tag: command 880#: installation.xml:581 installation.xml:605 881#, no-c-format 882msgid "make comments" 883msgstr "make comments" 884 885#. Tag: para 886#: installation.xml:584 887#, no-c-format 888msgid "" 889"Introduced in PostGIS 2.0. This generates html cheat sheets suitable for " 890"quick reference or for student handouts. This requires xsltproc to build and " 891"will generate 4 files in doc folder <filename>topology_cheatsheet.html</" 892"filename>, <filename>tiger_geocoder_cheatsheet.html</filename>, " 893"<filename>raster_cheatsheet.html</filename>, <filename>postgis_cheatsheet." 894"html</filename>" 895msgstr "" 896"Introdotto in PostGIS 2.0. Questa opzione genera degli opuscoli riassuntivi " 897"in formato HTML, utili come riferimento speditivo o per distribuzione agli " 898"studenti. Richiede xsltproc e genererà 4 file della cartella doc: " 899"<filename>topology_cheatsheet.html</filename>, " 900"<filename>tiger_geocoder_cheatsheet.html</filename>, " 901"<filename>raster_cheatsheet.html</filename>, <filename>postgis_cheatsheet." 902"html</filename>" 903 904#. Tag: para 905#: installation.xml:589 906#, no-c-format 907msgid "" 908"You can download some pre-built ones available in html and pdf from <ulink " 909"url=\"http://www.postgis.us/study_guides\">PostGIS / PostgreSQL Study " 910"Guides</ulink>" 911msgstr "" 912"Ne potete scaricare alcuni già pronti sia in formato HTML che PDF dalla " 913"pagina <ulink url=\"http://www.postgis.us/study_guides\">PostGIS / " 914"PostgreSQL Study Guides</ulink> " 915 916#. Tag: command 917#: installation.xml:592 918#, no-c-format 919msgid "make cheatsheets" 920msgstr "make cheatsheets" 921 922#. Tag: title 923#: installation.xml:597 924#, no-c-format 925msgid "Building PostGIS Extensions and Deploying them" 926msgstr "Compilazione e installazione delle estensioni PostGIS" 927 928#. Tag: para 929#: installation.xml:599 930#, no-c-format 931msgid "" 932"The PostGIS extensions are built and installed automatically if you are " 933"using PostgreSQL 9.1+." 934msgstr "" 935"Le estensioni di PostGIS vengono compilate e installate automaticamente se " 936"state utilizzando PostgreSQL 9.1+." 937 938#. Tag: para 939#: installation.xml:602 940#, no-c-format 941msgid "" 942"If you are building from source repository, you need to build the function " 943"descriptions first. These get built if you have docbook installed. You can " 944"also manually build with the statement:" 945msgstr "" 946"Se state compilando a partire dalla repository del sorgente, dovete prima " 947"compilare le descrizioni delle funzioni. Queste vengono create se avete " 948"docbook installato. Potete anche eseguire la compilazione manualmente " 949"tramite il comando:" 950 951#. Tag: para 952#: installation.xml:607 953#, no-c-format 954msgid "" 955"Building the comments is not necessary if you are building from a release " 956"tar ball since these are packaged pre-built with the tar ball already." 957msgstr "" 958"Creare i file dei commenti non è necessario se state compilando a partire " 959"dal file tar, dato che questi file sono inclusi nel file tar stesso." 960 961#. Tag: para 962#: installation.xml:608 963#, fuzzy, no-c-format 964msgid "" 965"The extensions should automatically build as part of the make install " 966"process. You can if needed build from the extensions folders or copy files " 967"if you need them on a different server." 968msgstr "" 969"Se state compilando per PostgreSQL 9.1, le estensioni dovrebbero essere " 970"create automaticamente nel corso del processo di make install. Se serve, " 971"potete eseguire la compilazione a partire dalle cartelle delle estensioni, o " 972"potete copiare i file se ne avete bisogno su un altro server." 973 974#. Tag: programlisting 975#: installation.xml:610 976#, no-c-format 977msgid "" 978"cd extensions\n" 979"cd postgis\n" 980"make clean\n" 981"make\n" 982"export PGUSER=postgres #overwrite psql variables\n" 983"make check #to test before install\n" 984"make install\n" 985"# to test extensions\n" 986"make check RUNTESTFLAGS=--extension" 987msgstr "" 988 989#. Tag: para 990#: installation.xml:611 991#, no-c-format 992msgid "" 993"<code>make check</code> uses psql to run tests and as such can use psql " 994"environment variables. Common ones useful to override are <varname>PGUSER</" 995"varname>,<varname>PGPORT</varname>, and <varname>PGHOST</varname>. Refer to " 996"<ulink url=\"https://www.postgresql.org/docs/current/libpq-envars.html" 997"\">psql environment variables</ulink>" 998msgstr "" 999 1000#. Tag: para 1001#: installation.xml:613 1002#, fuzzy, no-c-format 1003msgid "" 1004"The extension files will always be the same for the same version of PostGIS " 1005"and PostgreSQL regardless of OS, so it is fine to copy over the extension " 1006"files from one OS to another as long as you have the PostGIS binaries " 1007"already installed on your servers." 1008msgstr "" 1009"I file delle estensioni sono sempre gli stessi a pari versione di PostGIS, a " 1010"prescindere dal sistema operativo, per cui non ci sono problemi a copiare i " 1011"file delle estensioni da un sistema operativo a un altro, fintanto che i " 1012"file binari di PostGIS sono già installati sui vostri server." 1013 1014#. Tag: para 1015#: installation.xml:615 1016#, no-c-format 1017msgid "" 1018"If you want to install the extensions manually on a separate server " 1019"different from your development, You need to copy the following files from " 1020"the extensions folder into the <filename>PostgreSQL / share / extension</" 1021"filename> folder of your PostgreSQL install as well as the needed binaries " 1022"for regular PostGIS if you don't have them already on the server." 1023msgstr "" 1024"Se volete installare le estensioni manualmente su un server separato, " 1025"diverso da quello di sviluppo, dovete copiare i seguenti file dalla cartella " 1026"delle estensioni nella cartella <filename>PostgreSQL / share / extension</" 1027"filename> della vostra installazione PostgreSQL, così come i file binari per " 1028"la versione normale di PostGIS, se questi già non sono presenti sul server." 1029 1030#. Tag: para 1031#: installation.xml:622 1032#, no-c-format 1033msgid "" 1034"These are the control files that denote information such as the version of " 1035"the extension to install if not specified. <filename>postgis.control, " 1036"postgis_topology.control</filename>." 1037msgstr "" 1038"Questi sono i file di controllo che indicano informazioni come la versione " 1039"dell'estensione da installare, se non specificata. <filename>postgis." 1040"control, postgis_topology.control</filename>." 1041 1042#. Tag: para 1043#: installation.xml:628 1044#, no-c-format 1045msgid "" 1046"All the files in the /sql folder of each extension. Note that these need to " 1047"be copied to the root of the PostgreSQL share/extension folder " 1048"<filename>extensions/postgis/sql/*.sql</filename>, <filename>extensions/" 1049"postgis_topology/sql/*.sql</filename>" 1050msgstr "" 1051"Tutti i file nella cartella /sql di ciascuna estesnione. Da notare che quesi " 1052"devono essere copiati nella cartella principale delle estensioni di " 1053"PostgreSQL, share/extension <filename>extensions/postgis/sql/*.sql</" 1054"filename>, <filename>extensions/postgis_topology/sql/*.sql</filename>" 1055 1056#. Tag: para 1057#: installation.xml:634 1058#, no-c-format 1059msgid "" 1060"Once you do that, you should see <varname>postgis</varname>, " 1061"<varname>postgis_topology</varname> as available extensions in PgAdmin -> " 1062"extensions." 1063msgstr "" 1064"Una volta eseguita questa operazione, dovreste vedere <varname>postgis</" 1065"varname>, <varname>postgis_topology</varname> come estensioni disponibili in " 1066"PgAdmin -> extensions." 1067 1068#. Tag: para 1069#: installation.xml:635 1070#, no-c-format 1071msgid "" 1072"If you are using psql, you can verify that the extensions are installed by " 1073"running this query:" 1074msgstr "" 1075"Se state utilizzando psql, potete verificare l'avvenuta installazione delle " 1076"estensioni tramite questa query:" 1077 1078#. Tag: programlisting 1079#: installation.xml:636 1080#, no-c-format 1081msgid "" 1082"SELECT name, default_version,installed_version\n" 1083"FROM pg_available_extensions WHERE name LIKE 'postgis%' or name LIKE 'address" 1084"%';\n" 1085"\n" 1086" name | default_version | installed_version\n" 1087"------------------------------+-----------------+-------------------\n" 1088" address_standardizer | &last_release_version; | " 1089"&last_release_version;\n" 1090" address_standardizer_data_us | &last_release_version; | " 1091"&last_release_version;\n" 1092" postgis | &last_release_version; | " 1093"&last_release_version;\n" 1094" postgis_raster | &last_release_version; | " 1095"&last_release_version;\n" 1096" postgis_sfcgal | &last_release_version; |\n" 1097" postgis_tiger_geocoder | &last_release_version; | " 1098"&last_release_version;\n" 1099" postgis_topology | &last_release_version; |\n" 1100"(6 rows)" 1101msgstr "" 1102 1103#. Tag: para 1104#: installation.xml:638 1105#, no-c-format 1106msgid "" 1107"If you have the extension installed in the database you are querying, you'll " 1108"see mention in the <varname>installed_version</varname> column. If you get " 1109"no records back, it means you don't have postgis extensions installed on the " 1110"server at all. PgAdmin III 1.14+ will also provide this information in the " 1111"<varname>extensions</varname> section of the database browser tree and will " 1112"even allow upgrade or uninstall by right-clicking." 1113msgstr "" 1114"Se avete le estensioni installate nel database che state interrogando, " 1115"vedrete questo fatto menzionato nella colonna <varname>installed_version</" 1116"varname>. Se non vengono riportari record nel risultato, significa che non " 1117"avete alcuna estensione installata sul server. PgAdmin III 1.14+ fornirà " 1118"inoltre questa informazione nella sezione <varname>extensions</varname> " 1119"dell'albero di navigazione del database e consentirà anche l'aggiornamento o " 1120"la disinstallazione tramite clic del tasto destro del mouse." 1121 1122#. Tag: para 1123#: installation.xml:642 1124#, no-c-format 1125msgid "" 1126"If you have the extensions available, you can install postgis extension in " 1127"your database of choice by either using pgAdmin extension interface or " 1128"running these sql commands:" 1129msgstr "" 1130"Se le estensioni sono disponibili, potete installare l'estensione postgis " 1131"nel database da voi scelto utilizzando l'interfaccia pgAdmin per le " 1132"estensioni o eseguendo i seguenti comandi SQL:" 1133 1134#. Tag: programlisting 1135#: installation.xml:643 1136#, no-c-format 1137msgid "" 1138"CREATE EXTENSION postgis;\n" 1139"CREATE EXTENSION postgis_raster;\n" 1140"CREATE EXTENSION postgis_sfcgal;\n" 1141"CREATE EXTENSION fuzzystrmatch; --needed for postgis_tiger_geocoder\n" 1142"--optional used by postgis_tiger_geocoder, or can be used standalone\n" 1143"CREATE EXTENSION address_standardizer;\n" 1144"CREATE EXTENSION address_standardizer_data_us;\n" 1145"CREATE EXTENSION postgis_tiger_geocoder;\n" 1146"CREATE EXTENSION postgis_topology;" 1147msgstr "" 1148 1149#. Tag: para 1150#: installation.xml:645 1151#, no-c-format 1152msgid "" 1153"In psql you can use to see what versions you have installed and also what " 1154"schema they are installed." 1155msgstr "" 1156 1157#. Tag: programlisting 1158#: installation.xml:646 1159#, no-c-format 1160msgid "" 1161"\\connect mygisdb\n" 1162"\\x\n" 1163"\\dx postgis*" 1164msgstr "" 1165 1166#. Tag: screen 1167#: installation.xml:648 1168#, no-c-format 1169msgid "" 1170"List of installed extensions\n" 1171"-[ RECORD 1 ]-------------------------------------------------\n" 1172"Name | postgis\n" 1173"Version | &last_release_version;\n" 1174"Schema | public\n" 1175"Description | PostGIS geometry, geography, and raster spat..\n" 1176"-[ RECORD 2 ]-------------------------------------------------\n" 1177"Name | postgis_raster\n" 1178"Version | 3.0.0dev\n" 1179"Schema | public\n" 1180"Description | PostGIS raster types and functions\n" 1181"-[ RECORD 3 ]-------------------------------------------------\n" 1182"Name | postgis_tiger_geocoder\n" 1183"Version | &last_release_version;\n" 1184"Schema | tiger\n" 1185"Description | PostGIS tiger geocoder and reverse geocoder\n" 1186"-[ RECORD 4 ]-------------------------------------------------\n" 1187"Name | postgis_topology\n" 1188"Version | &last_release_version;\n" 1189"Schema | topology\n" 1190"Description | PostGIS topology spatial types and functions" 1191msgstr "" 1192 1193#. Tag: para 1194#: installation.xml:650 1195#, no-c-format 1196msgid "" 1197"Extension tables <varname>spatial_ref_sys</varname>, <varname>layer</" 1198"varname>, <varname>topology</varname> can not be explicitly backed up. They " 1199"can only be backed up when the respective <varname>postgis</varname> or " 1200"<varname>postgis_topology</varname> extension is backed up, which only seems " 1201"to happen when you backup the whole database. As of PostGIS 2.0.1, only srid " 1202"records not packaged with PostGIS are backed up when the database is backed " 1203"up so don't go around changing srids we package and expect your changes to " 1204"be there. Put in a ticket if you find an issue. The structures of extension " 1205"tables are never backed up since they are created with <code>CREATE " 1206"EXTENSION</code> and assumed to be the same for a given version of an " 1207"extension. These behaviors are built into the current PostgreSQL extension " 1208"model, so nothing we can do about it." 1209msgstr "" 1210"Per le tabelle delle estensioni <varname>spatial_ref_sys</varname>, " 1211"<varname>layer</varname> e <varname>topology</varname> non è possibile " 1212"eseguire un backup esplicito. Il backup può essere eseguito solo quando " 1213"viene fatto il backup delle corrispondenti estensioni <varname>postgis</" 1214"varname> o <varname>postgis_topology</varname>, il che pare avvenga " 1215"solamente quando eseguite un backup dell'intero database. Alla versione " 1216"2.0.1, quando viene eseguito il backup del database, gli unici oggetti di " 1217"cui viene fatta copia sono i record srid non facenti parte di PostGIS. " 1218"Pertanto non modificare gli SRID facenti parte dell'installazione, " 1219"aspettandovi poi di trovare le vostre modiche nel backup. Se ci sono " 1220"problemi, aprite un ticket. Neanche delle strutture delle tabelle delle " 1221"estensioni viene eseguito un backup, dato che sono create con <code>CREATE " 1222"EXTENSION</code>, e si presume che siano le stesse per una data versione " 1223"dell'estensione. Questo comportamento è inserito nell'attuale modello delle " 1224"estensioni, per cui non c'è molto che l'utente può fare." 1225 1226#. Tag: para 1227#: installation.xml:655 1228#, no-c-format 1229msgid "" 1230"If you installed &last_release_version;, without using our wonderful " 1231"extension system, you can change it to be extension based by running the " 1232"below commands to package the functions in their respective extension." 1233msgstr "" 1234 1235#. Tag: programlisting 1236#: installation.xml:659 1237#, no-c-format 1238msgid "" 1239"CREATE EXTENSION postgis FROM unpackaged;\n" 1240"CREATE EXTENSION postgis_raster FROM unpackaged;\n" 1241"CREATE EXTENSION postgis_topology FROM unpackaged;\n" 1242"CREATE EXTENSION postgis_tiger_geocoder FROM unpackaged;" 1243msgstr "" 1244 1245#. Tag: title 1246#: installation.xml:665 1247#, no-c-format 1248msgid "Testing" 1249msgstr "" 1250 1251#. Tag: para 1252#: installation.xml:667 1253#, no-c-format 1254msgid "If you wish to test the PostGIS build, run" 1255msgstr "Se volete eseguire un test sul PostGIS compilato, eseguite" 1256 1257#. Tag: command 1258#: installation.xml:672 1259#, no-c-format 1260msgid "make check" 1261msgstr "make check" 1262 1263#. Tag: para 1264#: installation.xml:675 1265#, no-c-format 1266msgid "" 1267"The above command will run through various checks and regression tests using " 1268"the generated library against an actual PostgreSQL database." 1269msgstr "" 1270"Il comando di cui sopra eseguirà vari controlli e collaudi di regressione, " 1271"utilizzando la libreria generata per un database PostgreSQL effettivo." 1272 1273#. Tag: para 1274#: installation.xml:681 1275#, fuzzy, no-c-format 1276msgid "" 1277"If you configured PostGIS using non-standard PostgreSQL, GEOS, or Proj " 1278"locations, you may need to add their library locations to the " 1279"<varname>LD_LIBRARY_PATH</varname> environment variable." 1280msgstr "" 1281"Se avete configurato PostGIS utilizzando percorsi non standard per " 1282"PostgreSQL, GEOS o Proj4, potreste dover aggiungere il percorso di queste " 1283"librerie nella variabile di ambiente LD_LIBRARY_PATH" 1284 1285#. Tag: para 1286#: installation.xml:689 1287#, no-c-format 1288msgid "" 1289"Currently, the <command>make check</command> relies on the <code>PATH</code> " 1290"and <code>PGPORT</code> environment variables when performing the checks - " 1291"it does <emphasis>not</emphasis> use the PostgreSQL version that may have " 1292"been specified using the configuration parameter <command>--with-pgconfig</" 1293"command>. So make sure to modify your PATH to match the detected PostgreSQL " 1294"installation during configuration or be prepared to deal with the impending " 1295"headaches." 1296msgstr "" 1297"Attualmente il comando <command>make check</command> fa riferimento alle " 1298"variabili di ambiente <code>PATH</code> e <code>PGPORT</code> nello " 1299"svolgimento dei controlli - e <emphasis>non</emphasis> utilizza la versione " 1300"PostgreSQL che può essere stata specificata nella configurazione con il " 1301"parametro <command>--with-pgconfig</command>. Perciò assicuratevi che la " 1302"vostra variabile PATH corrisponda all'installazione di PostgreSQL rilevata " 1303"durante al configurazione, o preparatevi ad affrontare una serie di " 1304"grattacapi." 1305 1306#. Tag: para 1307#: installation.xml:701 1308#, no-c-format 1309msgid "" 1310"If successful, make check will produce the output of almost 500 tests. The " 1311"results will look similar to the following (numerous lines omitted below):" 1312msgstr "" 1313 1314#. Tag: programlisting 1315#: installation.xml:706 1316#, no-c-format 1317msgid "" 1318"CUnit - A unit testing framework for C - Version 2.1-3\n" 1319" http://cunit.sourceforge.net/\n" 1320"\n" 1321" .\n" 1322" .\n" 1323" .\n" 1324"\n" 1325"Run Summary: Type Total Ran Passed Failed Inactive\n" 1326" suites 44 44 n/a 0 0\n" 1327" tests 300 300 300 0 0\n" 1328" asserts 4215 4215 4215 0 n/a\n" 1329"Elapsed time = 0.229 seconds\n" 1330"\n" 1331" .\n" 1332" .\n" 1333" .\n" 1334"\n" 1335"Running tests\n" 1336"\n" 1337" .\n" 1338" .\n" 1339" .\n" 1340"\n" 1341"Run tests: 134\n" 1342"Failed: 0\n" 1343"\n" 1344"\n" 1345"-- if you build with SFCGAL\n" 1346"\n" 1347" .\n" 1348" .\n" 1349" .\n" 1350"\n" 1351"Running tests\n" 1352"\n" 1353" .\n" 1354" .\n" 1355" .\n" 1356"\n" 1357"Run tests: 13\n" 1358"Failed: 0\n" 1359"\n" 1360"-- if you built with raster support\n" 1361"\n" 1362" .\n" 1363" .\n" 1364" .\n" 1365"\n" 1366"Run Summary: Type Total Ran Passed Failed Inactive\n" 1367" suites 12 12 n/a 0 0\n" 1368" tests 65 65 65 0 0\n" 1369" asserts 45896 45896 45896 0 n/a\n" 1370"\n" 1371"\n" 1372" .\n" 1373" .\n" 1374" .\n" 1375"\n" 1376"Running tests\n" 1377"\n" 1378" .\n" 1379" .\n" 1380" .\n" 1381"\n" 1382"Run tests: 101\n" 1383"Failed: 0\n" 1384"\n" 1385"-- topology regress\n" 1386"\n" 1387".\n" 1388".\n" 1389".\n" 1390"\n" 1391"Running tests\n" 1392"\n" 1393" .\n" 1394" .\n" 1395" .\n" 1396"\n" 1397"Run tests: 51\n" 1398"Failed: 0\n" 1399"\n" 1400"-- if you built --with-gui, you should see this too\n" 1401"\n" 1402" CUnit - A unit testing framework for C - Version 2.1-2\n" 1403" http://cunit.sourceforge.net/\n" 1404"\n" 1405" .\n" 1406" .\n" 1407" .\n" 1408"\n" 1409"Run Summary: Type Total Ran Passed Failed Inactive\n" 1410" suites 2 2 n/a 0 0\n" 1411" tests 4 4 4 0 0\n" 1412" asserts 4 4 4 0 n/a" 1413msgstr "" 1414 1415#. Tag: para 1416#: installation.xml:708 1417#, no-c-format 1418msgid "" 1419"The <varname>postgis_tiger_geocoder</varname> and " 1420"<varname>address_standardizer</varname> extensions, currently only support " 1421"the standard PostgreSQL installcheck. To test these use the below. Note: the " 1422"make install is not necessary if you already did make install at root of " 1423"PostGIS code folder." 1424msgstr "" 1425 1426#. Tag: para 1427#: installation.xml:709 1428#, no-c-format 1429msgid "For address_standardizer:" 1430msgstr "" 1431 1432#. Tag: programlisting 1433#: installation.xml:710 1434#, no-c-format 1435msgid "" 1436"cd extensions/address_standardizer\n" 1437"make install\n" 1438"make installcheck" 1439msgstr "" 1440 1441#. Tag: para 1442#: installation.xml:712 1443#, no-c-format 1444msgid "Output should look like:" 1445msgstr "" 1446 1447#. Tag: screen 1448#: installation.xml:713 1449#, no-c-format 1450msgid "" 1451"============== dropping database \"contrib_regression\" ==============\n" 1452"DROP DATABASE\n" 1453"============== creating database \"contrib_regression\" ==============\n" 1454"CREATE DATABASE\n" 1455"ALTER DATABASE\n" 1456"============== running regression test queries ==============\n" 1457"test test-init-extensions ... ok\n" 1458"test test-parseaddress ... ok\n" 1459"test test-standardize_address_1 ... ok\n" 1460"test test-standardize_address_2 ... ok\n" 1461"\n" 1462"=====================\n" 1463" All 4 tests passed.\n" 1464"=====================" 1465msgstr "" 1466 1467#. Tag: para 1468#: installation.xml:715 1469#, no-c-format 1470msgid "" 1471"For tiger geocoder, make sure you have postgis and fuzzystrmatch extensions " 1472"available in your PostgreSQL instance. The address_standardizer tests will " 1473"also kick in if you built postgis with address_standardizer support:" 1474msgstr "" 1475 1476#. Tag: programlisting 1477#: installation.xml:716 1478#, no-c-format 1479msgid "" 1480"cd extensions/postgis_tiger_geocoder\n" 1481"make install\n" 1482"make installcheck" 1483msgstr "" 1484 1485#. Tag: para 1486#: installation.xml:717 1487#, no-c-format 1488msgid "output should look like:" 1489msgstr "" 1490 1491#. Tag: screen 1492#: installation.xml:718 1493#, no-c-format 1494msgid "" 1495"============== dropping database \"contrib_regression\" ==============\n" 1496"DROP DATABASE\n" 1497"============== creating database \"contrib_regression\" ==============\n" 1498"CREATE DATABASE\n" 1499"ALTER DATABASE\n" 1500"============== installing fuzzystrmatch ==============\n" 1501"CREATE EXTENSION\n" 1502"============== installing postgis ==============\n" 1503"CREATE EXTENSION\n" 1504"============== installing postgis_tiger_geocoder ==============\n" 1505"CREATE EXTENSION\n" 1506"============== installing address_standardizer ==============\n" 1507"CREATE EXTENSION\n" 1508"============== running regression test queries ==============\n" 1509"test test-normalize_address ... ok\n" 1510"test test-pagc_normalize_address ... ok\n" 1511"\n" 1512"=====================\n" 1513"All 2 tests passed.\n" 1514"=====================" 1515msgstr "" 1516 1517#. Tag: title 1518#: installation.xml:722 1519#, no-c-format 1520msgid "Installation" 1521msgstr "Installazione" 1522 1523#. Tag: para 1524#: installation.xml:724 1525#, no-c-format 1526msgid "To install PostGIS, type" 1527msgstr "Per installare PostGIS, digitate" 1528 1529#. Tag: command 1530#: installation.xml:729 1531#, no-c-format 1532msgid "make install" 1533msgstr "make install" 1534 1535#. Tag: para 1536#: installation.xml:732 1537#, no-c-format 1538msgid "" 1539"This will copy the PostGIS installation files into their appropriate " 1540"subdirectory specified by the <command>--prefix</command> configuration " 1541"parameter. In particular:" 1542msgstr "" 1543"Questo comando copierà i file per l'installazione di PostGIS nelle cartelle " 1544"appropriate, specificate tramite il parametro di configurazione <command>--" 1545"prefix</command>. In particolare:" 1546 1547#. Tag: para 1548#: installation.xml:740 1549#, no-c-format 1550msgid "" 1551"The loader and dumper binaries are installed in <filename>[prefix]/bin</" 1552"filename>." 1553msgstr "" 1554"I file binari del loader e del dumper vengono installati in " 1555"<filename>[prefix]/bin</filename>." 1556 1557#. Tag: para 1558#: installation.xml:747 1559#, no-c-format 1560msgid "" 1561"The SQL files, such as <filename>postgis.sql</filename>, are installed in " 1562"<filename>[prefix]/share/contrib</filename>." 1563msgstr "" 1564"I file SQL, quali <filename>postgis.sql</filename>, vengono installati in " 1565"<filename>[prefix]/share/contrib</filename>." 1566 1567#. Tag: para 1568#: installation.xml:754 1569#, no-c-format 1570msgid "" 1571"The PostGIS libraries are installed in <filename>[prefix]/lib</filename>." 1572msgstr "" 1573"Le librerie PostGIS vengono installate in <filename>[prefix]/lib</filename>." 1574 1575#. Tag: para 1576#: installation.xml:761 1577#, no-c-format 1578msgid "" 1579"If you previously ran the <command>make comments</command> command to " 1580"generate the <filename>postgis_comments.sql</filename>, " 1581"<filename>raster_comments.sql</filename> file, install the sql file by " 1582"running" 1583msgstr "" 1584"Se avete eseguito il comando <command>make comments</command> per generare i " 1585"file <filename>postgis_comments.sql</filename> e <filename>raster_comments." 1586"sql</filename>, installate i file SQL eseguendo" 1587 1588#. Tag: command 1589#: installation.xml:768 1590#, no-c-format 1591msgid "make comments-install" 1592msgstr "make comments-install" 1593 1594#. Tag: para 1595#: installation.xml:772 1596#, no-c-format 1597msgid "" 1598"<filename>postgis_comments.sql</filename>, <filename>raster_comments.sql</" 1599"filename>, <filename>topology_comments.sql</filename> was separated from the " 1600"typical build and installation targets since with it comes the extra " 1601"dependency of <command>xsltproc</command>." 1602msgstr "" 1603"<filename>postgis_comments.sql</filename>, <filename>raster_comments.sql</" 1604"filename>, e <filename>topology_comments.sql</filename> sono separati dai " 1605"tipici obiettivi per il build e per l'installazione, dato che hanno una " 1606"ulteriore dipendenza da <command>xsltproc</command>." 1607 1608#. Tag: title 1609#: installation.xml:781 1610#, no-c-format 1611msgid "Installing and Using the address standardizer" 1612msgstr "" 1613 1614#. Tag: para 1615#: installation.xml:782 1616#, no-c-format 1617msgid "" 1618"The <code>address_standardizer</code> extension used to be a separate " 1619"package that required separate download. From PostGIS 2.2 on, it is now " 1620"bundled in. For more information about the address_standardize, what it " 1621"does, and how to configure it for your needs, refer to <xref linkend=" 1622"\"Address_Standardizer\"/>." 1623msgstr "" 1624 1625#. Tag: para 1626#: installation.xml:784 1627#, no-c-format 1628msgid "" 1629"This standardizer can be used in conjunction with the PostGIS packaged tiger " 1630"geocoder extension as a replacement for the <xref linkend=\"Normalize_Address" 1631"\"/> discussed. To use as replacement refer to <xref linkend=" 1632"\"tiger_pagc_address_standardizing\"/>. You can also use it as a building " 1633"block for your own geocoder or use it to standardize your addresses for " 1634"easier compare of addresses." 1635msgstr "" 1636 1637#. Tag: para 1638#: installation.xml:788 1639#, no-c-format 1640msgid "" 1641"The address standardizer relies on PCRE which is usually already installed " 1642"on many Nix systems, but you can download the latest at: <ulink url=\"http://" 1643"www.pcre.org\">http://www.pcre.org</ulink>. If during <xref linkend=" 1644"\"installation_configuration\"/>, PCRE is found, then the address " 1645"standardizer extension will automatically be built. If you have a custom " 1646"pcre install you want to use instead, pass to configure <code>--with-" 1647"pcredir=/path/to/pcre</code> where <filename>/path/to/pcre</filename> is the " 1648"root folder for your pcre include and lib directories." 1649msgstr "" 1650 1651#. Tag: para 1652#: installation.xml:791 1653#, no-c-format 1654msgid "" 1655"For Windows users, the PostGIS 2.1+ bundle is packaged with the " 1656"address_standardizer already so no need to compile and can move straight to " 1657"<code>CREATE EXTENSION</code> step." 1658msgstr "" 1659 1660#. Tag: para 1661#: installation.xml:794 1662#, no-c-format 1663msgid "" 1664"Once you have installed, you can connect to your database and run the SQL:" 1665msgstr "" 1666 1667#. Tag: programlisting 1668#: installation.xml:795 1669#, no-c-format 1670msgid "CREATE EXTENSION address_standardizer;" 1671msgstr "" 1672 1673#. Tag: para 1674#: installation.xml:797 1675#, no-c-format 1676msgid "The following test requires no rules, gaz, or lex tables" 1677msgstr "" 1678 1679#. Tag: programlisting 1680#: installation.xml:798 1681#, no-c-format 1682msgid "" 1683"SELECT num, street, city, state, zip\n" 1684" FROM parse_address('1 Devonshire Place PH301, Boston, MA 02109');" 1685msgstr "" 1686 1687#. Tag: para 1688#: installation.xml:799 1689#, no-c-format 1690msgid "Output should be" 1691msgstr "" 1692 1693#. Tag: screen 1694#: installation.xml:800 1695#, no-c-format 1696msgid "" 1697"num | street | city | state | zip\n" 1698"-----+------------------------+--------+-------+-------\n" 1699" 1 | Devonshire Place PH301 | Boston | MA | 02109" 1700msgstr "" 1701 1702#. Tag: title 1703#: installation.xml:802 1704#, no-c-format 1705msgid "Installing Regex::Assemble" 1706msgstr "" 1707 1708#. Tag: para 1709#: installation.xml:803 1710#, no-c-format 1711msgid "" 1712"Perl Regex:Assemble is no longer needed for compiling address_standardizer " 1713"extension since the files it generates are part of the source tree. However " 1714"if you need to edit the <filename>usps-st-city-orig.txt</filename> or " 1715"<filename>usps-st-city-orig.txt usps-st-city-adds.tx</filename>, you need to " 1716"rebuild <filename>parseaddress-stcities.h</filename> which does require " 1717"Regex:Assemble." 1718msgstr "" 1719 1720#. Tag: programlisting 1721#: installation.xml:804 1722#, no-c-format 1723msgid "cpan Regexp::Assemble" 1724msgstr "" 1725 1726#. Tag: para 1727#: installation.xml:805 1728#, no-c-format 1729msgid "or if you are on Ubuntu / Debian you might need to do" 1730msgstr "" 1731 1732#. Tag: programlisting 1733#: installation.xml:806 1734#, no-c-format 1735msgid "sudo perl -MCPAN -e \"install Regexp::Assemble\"" 1736msgstr "" 1737 1738#. Tag: title 1739#: installation.xml:811 1740#, no-c-format 1741msgid "Installing, Upgrading Tiger Geocoder and loading data" 1742msgstr "Installare o aggiornare il Geocode per Tiger e caricare i dati" 1743 1744#. Tag: para 1745#: installation.xml:813 1746#, no-c-format 1747msgid "" 1748"Extras like Tiger geocoder may not be packaged in your PostGIS distribution. " 1749"If you are missing the tiger geocoder extension or want a newer version than " 1750"what your install comes with, then use the <filename>share/extension/" 1751"postgis_tiger_geocoder.*</filename> files from the packages in <ulink url=" 1752"\"http://postgis.net/windows_downloads/\">Windows Unreleased Versions</" 1753"ulink> section for your version of PostgreSQL. Although these packages are " 1754"for windows, the postgis_tiger_geocoder extension files will work on any OS " 1755"since the extension is an SQL/plpgsql only extension." 1756msgstr "" 1757 1758#. Tag: title 1759#: installation.xml:817 1760#, no-c-format 1761msgid "Tiger Geocoder Enabling your PostGIS database: Using Extension" 1762msgstr "" 1763 1764#. Tag: para 1765#: installation.xml:818 1766#, no-c-format 1767msgid "" 1768"If you are using PostgreSQL 9.1+ and PostGIS 2.1+, you can take advantage of " 1769"the new extension model for installing tiger geocoder. To do so:" 1770msgstr "" 1771 1772#. Tag: para 1773#: installation.xml:820 1774#, no-c-format 1775msgid "" 1776"First get binaries for PostGIS 2.1+ or compile and install as usual. This " 1777"should install the necessary extension files as well for tiger geocoder." 1778msgstr "" 1779 1780#. Tag: para 1781#: installation.xml:821 1782#, no-c-format 1783msgid "" 1784"Connect to your database via psql or pgAdmin or some other tool and run the " 1785"following SQL commands. Note that if you are installing in a database that " 1786"already has postgis, you don't need to do the first step. If you have " 1787"<varname>fuzzystrmatch</varname> extension already installed, you don't need " 1788"to do the second step either." 1789msgstr "" 1790 1791#. Tag: programlisting 1792#: installation.xml:822 1793#, no-c-format 1794msgid "" 1795"CREATE EXTENSION postgis;\n" 1796"CREATE EXTENSION fuzzystrmatch;\n" 1797"CREATE EXTENSION postgis_tiger_geocoder;\n" 1798"--this one is optional if you want to use the rules based standardizer " 1799"(pagc_normalize_address)\n" 1800"CREATE EXTENSION address_standardizer;" 1801msgstr "" 1802 1803#. Tag: para 1804#: installation.xml:824 1805#, no-c-format 1806msgid "" 1807"If you already have postgis_tiger_geocoder extension installed, and just " 1808"want to update to the latest run:" 1809msgstr "" 1810 1811#. Tag: programlisting 1812#: installation.xml:825 1813#, no-c-format 1814msgid "" 1815"ALTER EXTENSION postgis UPDATE;\n" 1816"ALTER EXTENSION postgis_tiger_geocoder UPDATE;" 1817msgstr "" 1818 1819#. Tag: para 1820#: installation.xml:826 1821#, no-c-format 1822msgid "" 1823"If you made custom entries or changes to <varname>tiger.loader_platform</" 1824"varname> and <varname>tiger.loader_variables</varname> you may need to " 1825"update these." 1826msgstr "" 1827 1828#. Tag: para 1829#: installation.xml:828 1830#, no-c-format 1831msgid "" 1832"To confirm your install is working correctly, run this sql in your database:" 1833msgstr "" 1834 1835#. Tag: programlisting 1836#: installation.xml:829 1837#, no-c-format 1838msgid "" 1839"SELECT na.address, na.streetname,na.streettypeabbrev, na.zip\n" 1840" FROM normalize_address('1 Devonshire Place, Boston, MA 02109') AS na;" 1841msgstr "" 1842 1843#. Tag: para 1844#: installation.xml:830 1845#, no-c-format 1846msgid "Which should output" 1847msgstr "" 1848 1849#. Tag: screen 1850#: installation.xml:831 1851#, no-c-format 1852msgid "" 1853"address | streetname | streettypeabbrev | zip\n" 1854"---------+------------+------------------+-------\n" 1855" 1 | Devonshire | Pl | 02109" 1856msgstr "" 1857 1858#. Tag: para 1859#: installation.xml:833 1860#, no-c-format 1861msgid "" 1862"Create a new record in <varname>tiger.loader_platform</varname> table with " 1863"the paths of your executables and server." 1864msgstr "" 1865 1866#. Tag: para 1867#: installation.xml:834 1868#, no-c-format 1869msgid "" 1870"So for example to create a profile called debbie that follows <code>sh</" 1871"code> convention. You would do:" 1872msgstr "" 1873 1874#. Tag: programlisting 1875#: installation.xml:835 1876#, no-c-format 1877msgid "" 1878"INSERT INTO tiger.loader_platform(os, declare_sect, pgbin, wget, " 1879"unzip_command, psql, path_sep,\n" 1880" loader, environ_set_command, county_process_command)\n" 1881"SELECT 'debbie', declare_sect, pgbin, wget, unzip_command, psql, path_sep,\n" 1882" loader, environ_set_command, county_process_command\n" 1883" FROM tiger.loader_platform\n" 1884" WHERE os = 'sh';" 1885msgstr "" 1886 1887#. Tag: para 1888#: installation.xml:836 1889#, no-c-format 1890msgid "" 1891"And then edit the paths in the <emphasis>declare_sect</emphasis> column to " 1892"those that fit Debbie's pg, unzip,shp2pgsql, psql, etc path locations." 1893msgstr "" 1894 1895#. Tag: para 1896#: installation.xml:838 1897#, no-c-format 1898msgid "" 1899"If you don't edit this <varname>loader_platform</varname> table, it will " 1900"just contain common case locations of items and you'll have to edit the " 1901"generated script after the script is generated." 1902msgstr "" 1903 1904#. Tag: para 1905#: installation.xml:840 1906#, no-c-format 1907msgid "" 1908"As of PostGIS 2.4.1 the Zip code-5 digit tabulation area <varname>zcta5</" 1909"varname> load step was revised to load current zcta5 data and is part of the " 1910"<xref linkend=\"Loader_Generate_Nation_Script\"/> when enabled. It is turned " 1911"off by default because it takes quite a bit of time to load (20 to 60 " 1912"minutes), takes up quite a bit of disk space, and is not used that often." 1913msgstr "" 1914 1915#. Tag: para 1916#: installation.xml:842 1917#, no-c-format 1918msgid "To enable it, do the following:" 1919msgstr "" 1920 1921#. Tag: programlisting 1922#: installation.xml:843 1923#, no-c-format 1924msgid "" 1925"UPDATE tiger.loader_lookuptables SET load = true WHERE table_name = " 1926"'zcta510';" 1927msgstr "" 1928 1929#. Tag: para 1930#: installation.xml:844 1931#, no-c-format 1932msgid "" 1933"If present the <xref linkend=\"Geocode\"/> function can use it if a boundary " 1934"filter is added to limit to just zips in that boundary. The <xref linkend=" 1935"\"Reverse_Geocode\"/> function uses it if the returned address is missing a " 1936"zip, which often happens with highway reverse geocoding." 1937msgstr "" 1938 1939#. Tag: para 1940#: installation.xml:847 1941#, no-c-format 1942msgid "" 1943"Create a folder called <filename>gisdata</filename> on root of server or " 1944"your local pc if you have a fast network connection to the server. This " 1945"folder is where the tiger files will be downloaded to and processed. If you " 1946"are not happy with having the folder on the root of the server, or simply " 1947"want to change to a different folder for staging, then edit the field " 1948"<varname>staging_fold</varname> in the <varname>tiger.loader_variables</" 1949"varname> table." 1950msgstr "" 1951 1952#. Tag: para 1953#: installation.xml:849 1954#, no-c-format 1955msgid "" 1956"Create a folder called temp in the <filename>gisdata</filename> folder or " 1957"wherever you designated the <varname>staging_fold</varname> to be. This will " 1958"be the folder where the loader extracts the downloaded tiger data." 1959msgstr "" 1960 1961#. Tag: para 1962#: installation.xml:851 1963#, no-c-format 1964msgid "" 1965"Then run the <xref linkend=\"Loader_Generate_Nation_Script\"/> SQL function " 1966"make sure to use the name of your custom profile and copy the script to a ." 1967"sh or .bat file. So for example to build the nation load:" 1968msgstr "" 1969 1970#. Tag: programlisting 1971#: installation.xml:852 1972#, no-c-format 1973msgid "" 1974"psql -c \"SELECT Loader_Generate_Nation_Script('debbie')\" -d geocoder -tA " 1975"> /gisdata/nation_script_load.sh" 1976msgstr "" 1977 1978#. Tag: para 1979#: installation.xml:855 1980#, no-c-format 1981msgid "Run the generated nation load commandline scripts." 1982msgstr "" 1983 1984#. Tag: programlisting 1985#: installation.xml:856 1986#, no-c-format 1987msgid "" 1988"cd /gisdata\n" 1989"sh nation_script_load.sh" 1990msgstr "" 1991 1992#. Tag: para 1993#: installation.xml:859 1994#, no-c-format 1995msgid "" 1996"After you are done running the nation script, you should have three tables " 1997"in your <code>tiger_data</code> schema and they should be filled with data. " 1998"Confirm you do by doing the following queries from psql or pgAdmin" 1999msgstr "" 2000 2001#. Tag: programlisting 2002#: installation.xml:860 2003#, no-c-format 2004msgid "SELECT count(*) FROM tiger_data.county_all;" 2005msgstr "" 2006 2007#. Tag: screen 2008#: installation.xml:861 2009#, no-c-format 2010msgid "" 2011"count\n" 2012"-------\n" 2013" 3233\n" 2014"(1 row)" 2015msgstr "" 2016 2017#. Tag: programlisting 2018#: installation.xml:862 2019#, no-c-format 2020msgid "SELECT count(*) FROM tiger_data.state_all;" 2021msgstr "" 2022 2023#. Tag: screen 2024#: installation.xml:863 2025#, no-c-format 2026msgid "" 2027"count\n" 2028"-------\n" 2029" 56\n" 2030"(1 row)" 2031msgstr "" 2032 2033#. Tag: para 2034#: installation.xml:866 2035#, no-c-format 2036msgid "" 2037"By default the tables corresponding to <varname>bg</varname>, " 2038"<varname>tract</varname>, <varname>tabblock</varname> are not loaded. These " 2039"tables are not used by the geocoder but are used by folks for population " 2040"statistics. If you wish to load them as part of your state loads, run the " 2041"following statement to enable them." 2042msgstr "" 2043 2044#. Tag: programlisting 2045#: installation.xml:868 2046#, no-c-format 2047msgid "" 2048"UPDATE tiger.loader_lookuptables SET load = true WHERE load = false AND " 2049"lookup_name IN('tract', 'bg', 'tabblock');" 2050msgstr "" 2051 2052#. Tag: para 2053#: installation.xml:869 2054#, no-c-format 2055msgid "" 2056"Alternatively you can load just these tables after loading state data using " 2057"the <xref linkend=\"Loader_Generate_Census_Script\"/>" 2058msgstr "" 2059 2060#. Tag: para 2061#: installation.xml:871 2062#, no-c-format 2063msgid "" 2064"For each state you want to load data for, generate a state script <xref " 2065"linkend=\"Loader_Generate_Script\"/>." 2066msgstr "" 2067 2068#. Tag: para 2069#: installation.xml:871 2070#, no-c-format 2071msgid "" 2072"DO NOT Generate the state script until you have already loaded the nation " 2073"data, because the state script utilizes county list loaded by nation script." 2074msgstr "" 2075 2076#. Tag: programlisting 2077#: installation.xml:873 2078#, no-c-format 2079msgid "" 2080"psql -c \"SELECT Loader_Generate_Script(ARRAY['MA'], 'debbie')\" -d geocoder " 2081"-tA > /gisdata/ma_load.sh" 2082msgstr "" 2083 2084#. Tag: para 2085#: installation.xml:875 2086#, no-c-format 2087msgid "Run the generated commandline scripts." 2088msgstr "" 2089 2090#. Tag: programlisting 2091#: installation.xml:876 2092#, no-c-format 2093msgid "" 2094"cd /gisdata\n" 2095"sh ma_load.sh" 2096msgstr "" 2097 2098#. Tag: para 2099#: installation.xml:878 2100#, no-c-format 2101msgid "" 2102"After you are done loading all data or at a stopping point, it's a good idea " 2103"to analyze all the tiger tables to update the stats (include inherited stats)" 2104msgstr "" 2105 2106#. Tag: programlisting 2107#: installation.xml:879 2108#, no-c-format 2109msgid "" 2110"SELECT install_missing_indexes();\n" 2111"vacuum (analyze, verbose) tiger.addr;\n" 2112"vacuum (analyze, verbose) tiger.edges;\n" 2113"vacuum (analyze, verbose) tiger.faces;\n" 2114"vacuum (analyze, verbose) tiger.featnames;\n" 2115"vacuum (analyze, verbose) tiger.place;\n" 2116"vacuum (analyze, verbose) tiger.cousub;\n" 2117"vacuum (analyze, verbose) tiger.county;\n" 2118"vacuum (analyze, verbose) tiger.state;\n" 2119"vacuum (analyze, verbose) tiger.zip_lookup_base;\n" 2120"vacuum (analyze, verbose) tiger.zip_state;\n" 2121"vacuum (analyze, verbose) tiger.zip_state_loc;" 2122msgstr "" 2123 2124#. Tag: title 2125#: installation.xml:882 2126#, no-c-format 2127msgid "Converting a Tiger Geocoder Regular Install to Extension Model" 2128msgstr "" 2129 2130#. Tag: para 2131#: installation.xml:883 2132#, no-c-format 2133msgid "" 2134"If you installed the tiger geocoder without using the extension model, you " 2135"can convert to the extension model as follows:" 2136msgstr "" 2137 2138#. Tag: para 2139#: installation.xml:885 2140#, no-c-format 2141msgid "" 2142"Follow instructions in <xref linkend=\"upgrade_tiger_geocoder\"/> for the " 2143"non-extension model upgrade." 2144msgstr "" 2145 2146#. Tag: para 2147#: installation.xml:886 2148#, no-c-format 2149msgid "" 2150"Connect to your database with psql or pgAdmin and run the following command:" 2151msgstr "" 2152 2153#. Tag: programlisting 2154#: installation.xml:887 2155#, no-c-format 2156msgid "CREATE EXTENSION postgis_tiger_geocoder FROM unpackaged;" 2157msgstr "" 2158 2159#. Tag: title 2160#: installation.xml:894 2161#, no-c-format 2162msgid "Tiger Geocoder Enabling your PostGIS database: Not Using Extensions" 2163msgstr "" 2164 2165#. Tag: para 2166#: installation.xml:895 2167#, no-c-format 2168msgid "First install PostGIS using the prior instructions." 2169msgstr "" 2170"Anzitutto installate PostGIS utilizzando le istruzioni riportate sopra." 2171 2172#. Tag: para 2173#: installation.xml:899 installation.xml:959 2174#, no-c-format 2175msgid "" 2176"If you don't have an extras folder, download <ulink url=" 2177"\"&postgis_download_url;\">&postgis_download_url;</ulink>" 2178msgstr "" 2179 2180#. Tag: command 2181#: installation.xml:904 installation.xml:964 2182#, no-c-format 2183msgid "tar xvfz postgis-&last_release_version;.tar.gz" 2184msgstr "tar xvfz postgis-&last_release_version;.tar.gz" 2185 2186#. Tag: command 2187#: installation.xml:908 2188#, no-c-format 2189msgid "cd postgis-&last_release_version;/extras/tiger_geocoder" 2190msgstr "" 2191 2192#. Tag: para 2193#: installation.xml:911 2194#, no-c-format 2195msgid "" 2196"Edit the <filename>tiger_loader_2015.sql</filename> (or latest loader file " 2197"you find, unless you want to load different year) to the paths of your " 2198"executables server etc or alternatively you can update the " 2199"<varname>loader_platform</varname> table once installed. If you don't edit " 2200"this file or the <varname>loader_platform</varname> table, it will just " 2201"contain common case locations of items and you'll have to edit the generated " 2202"script after the fact when you run the <xref linkend=" 2203"\"Loader_Generate_Nation_Script\"/> and <xref linkend=" 2204"\"Loader_Generate_Script\"/> SQL functions." 2205msgstr "" 2206 2207#. Tag: para 2208#: installation.xml:913 2209#, no-c-format 2210msgid "" 2211"If you are installing Tiger geocoder for the first time edit either the " 2212"<filename>create_geocode.bat</filename> script If you are on windows or the " 2213"<filename>create_geocode.sh</filename> if you are on Linux/Unix/Mac OSX with " 2214"your PostgreSQL specific settings and run the corresponding script from the " 2215"commandline." 2216msgstr "" 2217 2218#. Tag: para 2219#: installation.xml:917 2220#, no-c-format 2221msgid "" 2222"Verify that you now have a <varname>tiger</varname> schema in your database " 2223"and that it is part of your database search_path. If it is not, add it with " 2224"a command something along the line of:" 2225msgstr "" 2226 2227#. Tag: programlisting 2228#: installation.xml:917 2229#, no-c-format 2230msgid "ALTER DATABASE geocoder SET search_path=public, tiger;" 2231msgstr "ALTER DATABASE geocoder SET search_path=public, tiger;" 2232 2233#. Tag: para 2234#: installation.xml:918 2235#, no-c-format 2236msgid "" 2237"The normalizing address functionality works more or less without any data " 2238"except for tricky addresses. Run this test and verify things look like this:" 2239msgstr "" 2240 2241#. Tag: programlisting 2242#: installation.xml:919 2243#, no-c-format 2244msgid "" 2245"SELECT pprint_addy(normalize_address('202 East Fremont Street, Las Vegas, " 2246"Nevada 89101')) As pretty_address;\n" 2247"pretty_address\n" 2248"---------------------------------------\n" 2249"202 E Fremont St, Las Vegas, NV 89101" 2250msgstr "" 2251"SELECT pprint_addy(normalize_address('202 East Fremont Street, Las Vegas, " 2252"Nevada 89101')) As pretty_address;\n" 2253"pretty_address\n" 2254"---------------------------------------\n" 2255"202 E Fremont St, Las Vegas, NV 89101" 2256 2257#. Tag: title 2258#: installation.xml:922 2259#, no-c-format 2260msgid "Using Address Standardizer Extension with Tiger geocoder" 2261msgstr "" 2262 2263#. Tag: para 2264#: installation.xml:923 2265#, no-c-format 2266msgid "" 2267"One of the many complaints of folks is the address normalizer function <xref " 2268"linkend=\"Normalize_Address\"/> function that normalizes an address for " 2269"prepping before geocoding. The normalizer is far from perfect and trying to " 2270"patch its imperfectness takes a vast amount of resources. As such we have " 2271"integrated with another project that has a much better address standardizer " 2272"engine. To use this new address_standardizer, you compile the extension as " 2273"described in <xref linkend=\"installing_pagc_address_standardizer\"/> and " 2274"install as an extension in your database." 2275msgstr "" 2276 2277#. Tag: para 2278#: installation.xml:926 2279#, no-c-format 2280msgid "" 2281"Once you install this extension in the same database as you have installed " 2282"<code>postgis_tiger_geocoder</code>, then the <xref linkend=" 2283"\"Pagc_Normalize_Address\"/> can be used instead of <xref linkend=" 2284"\"Normalize_Address\"/>. This extension is tiger agnostic, so can be used " 2285"with other data sources such as international addresses. The tiger geocoder " 2286"extension does come packaged with its own custom versions of <xref linkend=" 2287"\"rulestab\"/> ( <code>tiger.pagc_rules</code>) , <xref linkend=\"gaztab\"/> " 2288"(<code>tiger.pagc_gaz</code>), and <xref linkend=\"lextab\"/> (<code>tiger." 2289"pagc_lex</code>). These you can add and update to improve your standardizing " 2290"experience for your own needs." 2291msgstr "" 2292 2293#. Tag: title 2294#: installation.xml:929 2295#, no-c-format 2296msgid "Loading Tiger Data" 2297msgstr "Caricamento dei dati Tiger" 2298 2299#. Tag: para 2300#: installation.xml:930 2301#, no-c-format 2302msgid "" 2303"The instructions for loading data are available in a more detailed form in " 2304"the <filename>extras/tiger_geocoder/tiger_2011/README</filename>. This just " 2305"includes the general steps." 2306msgstr "" 2307"Le istruzioni dettagliate per il caricamento dei dati sono disponibili nel " 2308"file <filename>extras/tiger_geocoder/tiger_2011/README</filename>. Di " 2309"seguito si illustrano i passaggi generali." 2310 2311#. Tag: para 2312#: installation.xml:931 2313#, no-c-format 2314msgid "" 2315"The load process downloads data from the census website for the respective " 2316"nation files, states requested, extracts the files, and then loads each " 2317"state into its own separate set of state tables. Each state table inherits " 2318"from the tables defined in <varname>tiger</varname> schema so that its " 2319"sufficient to just query those tables to access all the data and drop a set " 2320"of state tables at any time using the <xref linkend=" 2321"\"Drop_State_Tables_Generate_Script\"/> if you need to reload a state or " 2322"just don't need a state anymore." 2323msgstr "" 2324"Il processo di caricamento scarica i dati per ciascuno stato richiesto dal " 2325"sito del censimento, estrare i file, e li carica nelle rispettive tabelle. " 2326"La tabella di ogni stato eredita le proprietà dalle tabelle definite nello " 2327"schema <varname>tiger</varname>, per cui è sufficiente eseguire le " 2328"interrogazioni su queste tabelle per accedere a tutti i dati. E' altresì " 2329"possibile cancellare le tabelle per un dato stato tramite lo script <xref " 2330"linkend=\"Drop_State_Tables_Generate_Script\"/>, qualora aveste necessità di " 2331"ricaricare uno stato o se questo non vi serve più." 2332 2333#. Tag: para 2334#: installation.xml:933 2335#, no-c-format 2336msgid "In order to be able to load data you'll need the following tools:" 2337msgstr "Per caricare i dati avrete bisogno dei seguenti strumenti:" 2338 2339#. Tag: para 2340#: installation.xml:935 2341#, no-c-format 2342msgid "A tool to unzip the zip files from census website." 2343msgstr "Uno strumento per decomprimere i file zip dal sito web dei censimenti." 2344 2345#. Tag: para 2346#: installation.xml:936 2347#, no-c-format 2348msgid "" 2349"For Unix like systems: <varname>unzip</varname> executable which is usually " 2350"already installed on most Unix like platforms." 2351msgstr "" 2352"Per sistemi tipo Unix: l'eseguibile <varname>unzip</varname> è di soiito già " 2353"installato." 2354 2355#. Tag: para 2356#: installation.xml:937 2357#, no-c-format 2358msgid "" 2359"For Windows, 7-zip which is a free compress/uncompress tool you can download " 2360"from <ulink url=\"http://www.7-zip.org/\">http://www.7-zip.org/</ulink>" 2361msgstr "" 2362"Per Windows, 7-zip è uno strumento libero di compressione/decompressione, " 2363"che può essere scaricato dal sito <ulink url=\"http://www.7-zip.org/" 2364"\">http://www.7-zip.org/</ulink>" 2365 2366#. Tag: para 2367#: installation.xml:939 2368#, no-c-format 2369msgid "" 2370"<filename>shp2pgsql</filename> commandline which is installed by default " 2371"when you install PostGIS." 2372msgstr "" 2373"Il programam da riga di comando <filename>shp2pgsql</filename>, che viene " 2374"installato di base quando nistallate PostGIS." 2375 2376#. Tag: para 2377#: installation.xml:940 2378#, no-c-format 2379msgid "" 2380"<filename>wget</filename> which is a web grabber tool usually installed on " 2381"most Unix/Linux systems." 2382msgstr "" 2383"<filename>wget</filename> è uno strumento per la copia di file da web, " 2384"solitamente installato nella maggior parte dei sistemi Unix/Linux." 2385 2386#. Tag: para 2387#: installation.xml:941 2388#, no-c-format 2389msgid "" 2390"If you are on windows, you can get pre-compiled binaries from <ulink url=" 2391"\"http://gnuwin32.sourceforge.net/packages/wget.htm\">http://gnuwin32." 2392"sourceforge.net/packages/wget.htm</ulink>" 2393msgstr "" 2394"Se siete su Windows, potete reperire i file binari precompilati da <ulink " 2395"url=\"http://gnuwin32.sourceforge.net/packages/wget.htm\">http://gnuwin32." 2396"sourceforge.net/packages/wget.htm</ulink>" 2397 2398#. Tag: para 2399#: installation.xml:944 2400#, no-c-format 2401msgid "" 2402"If you are upgrading from tiger_2010, you'll need to first generate and run " 2403"<xref linkend=\"Drop_Nation_Tables_Generate_Script\"/>. Before you load any " 2404"state data, you need to load the nation wide data which you do with <xref " 2405"linkend=\"Loader_Generate_Nation_Script\"/>. Which will generate a loader " 2406"script for you. <xref linkend=\"Loader_Generate_Nation_Script\"/> is a one-" 2407"time step that should be done for upgrading (from 2010) and for new installs." 2408msgstr "" 2409 2410#. Tag: para 2411#: installation.xml:946 2412#, no-c-format 2413msgid "" 2414"To load state data refer to <xref linkend=\"Loader_Generate_Script\"/> to " 2415"generate a data load script for your platform for the states you desire. " 2416"Note that you can install these piecemeal. You don't have to load all the " 2417"states you want all at once. You can load them as you need them." 2418msgstr "" 2419 2420#. Tag: para 2421#: installation.xml:949 2422#, no-c-format 2423msgid "" 2424"After the states you desire have been loaded, make sure to run the: " 2425"<programlisting>SELECT install_missing_indexes();</programlisting> as " 2426"described in <xref linkend=\"Install_Missing_Indexes\"/>." 2427msgstr "" 2428"Dopo aver caricato i dati per gli stati cui siete interessati, assicuratevi " 2429"di eseguire: <programlisting>SELECT install_missing_indexes();</" 2430"programlisting> come descritto in <xref linkend=\"Install_Missing_Indexes\"/" 2431">." 2432 2433#. Tag: para 2434#: installation.xml:951 2435#, no-c-format 2436msgid "" 2437"To test that things are working as they should, try to run a geocode on an " 2438"address in your state using <xref linkend=\"Geocode\"/>" 2439msgstr "" 2440"Per vedere se le cose funzionano come dovrebbero, provate a eseguire la " 2441"geocodifica di un indirizzo nel vostro stato utilizzando <xref linkend=" 2442"\"Geocode\"/>" 2443 2444#. Tag: title 2445#: installation.xml:954 2446#, no-c-format 2447msgid "Upgrading your Tiger Geocoder Install" 2448msgstr "Aggiornamento del installazione del Geocoder Tiger" 2449 2450#. Tag: para 2451#: installation.xml:955 2452#, no-c-format 2453msgid "" 2454"If you have Tiger Geocoder packaged with 2.0+ already installed, you can " 2455"upgrade the functions at any time even from an interim tar ball if there are " 2456"fixes you badly need. This will only work for Tiger geocoder not installed " 2457"with extensions." 2458msgstr "" 2459 2460#. Tag: command 2461#: installation.xml:968 2462#, no-c-format 2463msgid "cd postgis-&last_release_version;/extras/tiger_geocoder/tiger_2011" 2464msgstr "cd postgis-&last_release_version;/extras/tiger_geocoder/tiger_2011" 2465 2466#. Tag: para 2467#: installation.xml:971 2468#, no-c-format 2469msgid "" 2470"Locate the <filename>upgrade_geocoder.bat</filename> script If you are on " 2471"windows or the <filename>upgrade_geocoder.sh</filename> if you are on Linux/" 2472"Unix/Mac OSX. Edit the file to have your postgis database credentials." 2473msgstr "" 2474 2475#. Tag: para 2476#: installation.xml:974 2477#, no-c-format 2478msgid "" 2479"If you are upgrading from 2010 or 2011, make sure to unremark out the loader " 2480"script line so you get the latest script for loading 2012 data." 2481msgstr "" 2482 2483#. Tag: para 2484#: installation.xml:975 2485#, no-c-format 2486msgid "Then run th corresponding script from the commandline." 2487msgstr "" 2488 2489#. Tag: para 2490#: installation.xml:979 2491#, no-c-format 2492msgid "" 2493"Next drop all nation tables and load up the new ones. Generate a drop script " 2494"with this SQL statement as detailed in <xref linkend=" 2495"\"Drop_Nation_Tables_Generate_Script\"/>" 2496msgstr "" 2497"Poi cancellate tutte le tabelle delle nazioni e caricate quelle nuove. " 2498"Potete generare uno script per la cancellazione con il codice SQL illustrato " 2499"in <xref linkend=\"Drop_Nation_Tables_Generate_Script\"/>" 2500 2501#. Tag: programlisting 2502#: installation.xml:980 2503#, no-c-format 2504msgid "SELECT drop_nation_tables_generate_script();" 2505msgstr "SELECT drop_nation_tables_generate_script();" 2506 2507#. Tag: para 2508#: installation.xml:981 2509#, no-c-format 2510msgid "Run the generated drop SQL statements." 2511msgstr "Eseguite i comandi SQL DROP che vengono generati." 2512 2513#. Tag: para 2514#: installation.xml:982 2515#, no-c-format 2516msgid "" 2517"Generate a nation load script with this SELECT statement as detailed in " 2518"<xref linkend=\"Loader_Generate_Nation_Script\"/>" 2519msgstr "" 2520"Generate uno script per il caricamento di uno stato con l'istruzione SELECT " 2521"come illustrato in <xref linkend=\"Loader_Generate_Nation_Script\"/>" 2522 2523#. Tag: emphasis 2524#: installation.xml:983 2525#, no-c-format 2526msgid "For windows" 2527msgstr "Per Windows" 2528 2529#. Tag: programlisting 2530#: installation.xml:984 2531#, no-c-format 2532msgid "SELECT loader_generate_nation_script('windows');" 2533msgstr "SELECT loader_generate_nation_script('windows');" 2534 2535#. Tag: emphasis 2536#: installation.xml:985 2537#, no-c-format 2538msgid "For unix/linux" 2539msgstr "Per unix/linux" 2540 2541#. Tag: programlisting 2542#: installation.xml:986 2543#, no-c-format 2544msgid "SELECT loader_generate_nation_script('sh');" 2545msgstr "SELECT loader_generate_nation_script('sh');" 2546 2547#. Tag: para 2548#: installation.xml:987 2549#, no-c-format 2550msgid "" 2551"Refer to <xref linkend=\"tiger_geocoder_loading_data\"/> for instructions on " 2552"how to run the generate script. This only needs to be done once." 2553msgstr "" 2554"Fate riferimento a <xref linkend=\"tiger_geocoder_loading_data\"/> per " 2555"istruzioni su come eseguire lo script generato. Questo passaggio deve essere " 2556"eseguito solo una volta." 2557 2558#. Tag: para 2559#: installation.xml:988 2560#, no-c-format 2561msgid "" 2562"You can have a mix of 2010/2011 state tables and can upgrade each state " 2563"separately. Before you upgrade a state to 2011, you first need to drop the " 2564"2010 tables for that state using <xref linkend=" 2565"\"Drop_State_Tables_Generate_Script\"/>." 2566msgstr "" 2567"Potete avere una combinazione di tabelle degli stati sia per il 2010 che per " 2568"il 2011 e potete aggiornare ogni stato separatamente. Prima di aggiornare " 2569"uno stato al 2011, dovete prima eliminare la corrispondente tabella 2012 " 2570"utilizzando <xref linkend=\"Drop_State_Tables_Generate_Script\"/>. " 2571 2572#. Tag: title 2573#: installation.xml:995 2574#, no-c-format 2575msgid "Common Problems during installation" 2576msgstr "" 2577 2578#. Tag: para 2579#: installation.xml:996 2580#, no-c-format 2581msgid "" 2582"There are several things to check when your installation or upgrade doesn't " 2583"go as you expected." 2584msgstr "" 2585"Quando l'installazione o l'aggiornamento non vanno come previsto, diverse " 2586"cose vanno controllate." 2587 2588#. Tag: para 2589#: installation.xml:1003 2590#, no-c-format 2591msgid "" 2592"Check that you have installed PostgreSQL &min_postgres_version; or newer, " 2593"and that you are compiling against the same version of the PostgreSQL source " 2594"as the version of PostgreSQL that is running. Mix-ups can occur when your " 2595"(Linux) distribution has already installed PostgreSQL, or you have otherwise " 2596"installed PostgreSQL before and forgotten about it. PostGIS will only work " 2597"with PostgreSQL &min_postgres_version; or newer, and strange, unexpected " 2598"error messages will result if you use an older version. To check the version " 2599"of PostgreSQL which is running, connect to the database using psql and run " 2600"this query:" 2601msgstr "" 2602"Controllate di aver installato PostgreSQL &min_postgres_version; o più " 2603"recente, e che state compilando con il sorgente PostgreSQL nella versione " 2604"corrispondente alla versione di PostgreSQL che sta girando. Si possono " 2605"verificare casi di confusione quando la vostra distribuzione (Linux) ha " 2606"PostgreSQL già installao, o quando avete installato PostgreSQL in precedenza " 2607"e ve ne siete dimenticati. PostGIS funzionerà solo con PostgreSQL " 2608"&min_postgres_version; o più recente, e si potrebbero ricevere messaggi di " 2609"errore strani o inattesi se utilizzate una versione più vecchia. Per " 2610"verificare quale versione di PostgreSQL sta girando, collegatevi al database " 2611"utilizzando psql ed eseguite la seguente query:" 2612 2613#. Tag: programlisting 2614#: installation.xml:1016 2615#, no-c-format 2616msgid "SELECT version();" 2617msgstr "SELECT version();" 2618 2619#. Tag: para 2620#: installation.xml:1018 2621#, no-c-format 2622msgid "" 2623"If you are running an RPM based distribution, you can check for the " 2624"existence of pre-installed packages using the <command>rpm</command> command " 2625"as follows: <command>rpm -qa | grep postgresql</command>" 2626msgstr "" 2627"Se state utilizzando una distribuzione basata su RPM, potete verificare la " 2628"presenza di pacchetti preinstallati utilizzando il comando <command>rpm</" 2629"command> con la seguente sintassi: <command>rpm -qa | grep postgresql</" 2630"command>" 2631 2632#. Tag: para 2633#: installation.xml:1026 2634#, no-c-format 2635msgid "" 2636"If your upgrade fails, make sure you are restoring into a database that " 2637"already has PostGIS installed." 2638msgstr "" 2639"Se l'aggiornamento non funziona, assicuratevi di eseguire il ripristino in " 2640"un database che abbia già PostGIS installato." 2641 2642#. Tag: programlisting 2643#: installation.xml:1027 2644#, no-c-format 2645msgid "SELECT postgis_full_version();" 2646msgstr "SELECT postgis_full_version();" 2647 2648#. Tag: para 2649#: installation.xml:1031 2650#, fuzzy, no-c-format 2651msgid "" 2652"Also check that configure has correctly detected the location and version of " 2653"PostgreSQL, the Proj library and the GEOS library." 2654msgstr "" 2655"Inoltre, verificate che configure abbia correttamente individuato il " 2656"percorso e la versione di PostgreSQL, della libreria Proj4 e della libreria " 2657"GEOS." 2658 2659#. Tag: para 2660#: installation.xml:1038 2661#, no-c-format 2662msgid "" 2663"The output from configure is used to generate the <filename>postgis_config." 2664"h</filename> file. Check that the <varname>POSTGIS_PGSQL_VERSION</varname>, " 2665"<varname>POSTGIS_PROJ_VERSION</varname> and <varname>POSTGIS_GEOS_VERSION</" 2666"varname> variables have been set correctly." 2667msgstr "" 2668"L'uscita da configure viene utilizzata per generare il file " 2669"<filename>postgis_config.h</filename>. Controllate che le variabili " 2670"<varname>POSTGIS_PGSQL_VERSION</varname>, <varname>POSTGIS_PROJ_VERSION</" 2671"varname> e <varname>POSTGIS_GEOS_VERSION</varname> siano assegnate " 2672"correttamente." 2673 2674#, no-c-format 2675#~ msgid "" 2676#~ "If successful, the output of the test should be similar to the following:" 2677#~ msgstr "" 2678#~ "Se il test è positivo, l'uscita dovrebbe essere simile alla seguente:" 2679 2680#~ msgid "Loader/Dumper" 2681#~ msgstr "Loader/Dumper" 2682 2683#~ msgid "" 2684#~ "The data loader and dumper are built and installed automatically as part " 2685#~ "of the PostGIS build. To build and install them manually:" 2686#~ msgstr "" 2687#~ "Il loader e il dumper dei dati sono compilati e installati " 2688#~ "automaticamente con PostGIS. Per compilarli e installarli manualmente:" 2689 2690#~ msgid "" 2691#~ "# cd postgis-&last_release_version;/loader\n" 2692#~ "# make\n" 2693#~ "# make install" 2694#~ msgstr "" 2695#~ "# cd postgis-&last_release_version;/loader\n" 2696#~ "# make\n" 2697#~ "# make install" 2698 2699#~ msgid "" 2700#~ "The loader is called <filename>shp2pgsql</filename> and converts ESRI " 2701#~ "Shape files into SQL suitable for loading in PostGIS/PostgreSQL. The " 2702#~ "dumper is called <filename>pgsql2shp</filename> and converts PostGIS " 2703#~ "tables (or queries) into ESRI Shape files. For more verbose " 2704#~ "documentation, see the online help, and the manual pages." 2705#~ msgstr "" 2706#~ "Il loader si chiama <filename>shp2pgsql</filename> e converte gli " 2707#~ "Shapefile ESRI in formato SQL adatto al caricamento in PostGIS/" 2708#~ "PostgreSQL. Il dumper si chiama <filename>pgsql2shp</filename> e converte " 2709#~ "le tabelle (o le query) di PostGIS in formato Shapefile ESRI. Per una " 2710#~ "documentazione più estesa, si rimanda alla guida in linea e alle pagine " 2711#~ "del manuale." 2712 2713#~ msgid "" 2714#~ "Please refer to <xref linkend=\"make_install_postgis_extensions\"/> for " 2715#~ "more details about querying installed/available extensions and upgrading " 2716#~ "extensions, or switching from a non-extension install to an extension " 2717#~ "install." 2718#~ msgstr "" 2719#~ "Vedi <xref linkend=\"make_install_postgis_extensions\"/> per maggiori " 2720#~ "informazioni riguardo l'ispezione delle estensioni installate/disponibili " 2721#~ "e il loro aggiornamento, o per passare da un'installazione semplice ad " 2722#~ "una per estensioni." 2723 2724#, fuzzy 2725#~ msgid "Configuring raster" 2726#~ msgstr "Configurazione" 2727 2728#, fuzzy 2729#~ msgid "" 2730#~ "svn checkout https://svn.osgeo.org/postgis/trunk/ postgis-" 2731#~ "&last_release_version;" 2732#~ msgstr "" 2733#~ "svn checkout http://svn.osgeo.org/postgis/trunk/ postgis-" 2734#~ "&last_release_version;" 2735 2736#~ msgid "Creating a spatial database using EXTENSIONS" 2737#~ msgstr "Creare un database spaziale con le ESTENSIONI" 2738 2739#~ msgid "" 2740#~ "If you are using PostgreSQL 9.1+ and have compiled and installed the " 2741#~ "extensions/ postgis modules, you can create a spatial database the new " 2742#~ "way." 2743#~ msgstr "" 2744#~ "Se state utilizzando PostgreSQL9.1 o superiore e avete compilato e " 2745#~ "installato i moduli delle estensioni postgis, potete creare un database " 2746#~ "spaziale col nuovo sistema." 2747 2748#~ msgid "createdb [yourdatabase]" 2749#~ msgstr "createdb [il_tuo_database]" 2750 2751#~ msgid "psql -d [yourdatabase] -c \"CREATE EXTENSION postgis;\"" 2752#~ msgstr "psql -d [il_tuo_database] -c \"CREATE EXTENSION postgis;\"" 2753 2754#, fuzzy 2755#~ msgid "" 2756#~ "Raster is packaged as a separate extension and installable with command:" 2757#~ msgstr "" 2758#~ "La topologia è compresa in un'estensione separata e può essere installata " 2759#~ "con il comando:" 2760 2761#, fuzzy 2762#~ msgid "psql -d [yourdatabase] -c \"CREATE EXTENSION postgis_raster;\"" 2763#~ msgstr "psql -d [il_tuo_database] -c \"CREATE EXTENSION postgis;\"" 2764 2765#~ msgid "" 2766#~ "Topology is packaged as a separate extension and installable with command:" 2767#~ msgstr "" 2768#~ "La topologia è compresa in un'estensione separata e può essere installata " 2769#~ "con il comando:" 2770 2771#~ msgid "psql -d [yourdatabase] -c \"CREATE EXTENSION postgis_topology;\"" 2772#~ msgstr "psql -d [il_tuo_database] -c \"CREATE EXTENSION postgis_topology;\"" 2773 2774#~ msgid "" 2775#~ "If you plan to restore an old backup from prior versions in this new db, " 2776#~ "run:" 2777#~ msgstr "" 2778#~ "Se prevedete di ripristinare un vecchio backup, da una versione " 2779#~ "precedente, nel nuovo database, eseguite:" 2780 2781#~ msgid "psql -d [yourdatabase] -f legacy.sql" 2782#~ msgstr "psql -d [il_tuo_database] -f legacy.sql" 2783 2784#~ msgid "" 2785#~ "You can later run <filename>uninstall_legacy.sql</filename> to get rid of " 2786#~ "the deprecated functions after you are done with restoring and cleanup." 2787#~ msgstr "" 2788#~ "Potete successivamente eseguire <filename>uninstall_legacy.sql</filename> " 2789#~ "per sbarazzarvi delle funzioni obsolete, dopo che avete concluso il " 2790#~ "ripristino e la pulizia del database." 2791 2792#~ msgid "" 2793#~ "The first step in creating a PostGIS database is to create a simple " 2794#~ "PostgreSQL database." 2795#~ msgstr "" 2796#~ "Il primo passo per creare un database PostGIS consiste nel creare un " 2797#~ "semplice database PostgreSQL." 2798 2799#~ msgid "" 2800#~ "Many of the PostGIS functions are written in the PL/pgSQL procedural " 2801#~ "language. As such, the next step to create a PostGIS database is to " 2802#~ "enable the PL/pgSQL language in your new database. This is accomplish by " 2803#~ "the command below command. For PostgreSQL 8.4+, this is generally already " 2804#~ "installed" 2805#~ msgstr "" 2806#~ "Molte delle funzioni PostGIS sono scritte nel linguaggio procedurale PL/" 2807#~ "pgSQL. Pertanto, il prossimo passo per creare un database PostGIS " 2808#~ "consiste nell'abilitare il linguaggio PL/pgSQL nel vostro database. Per " 2809#~ "questo deve essere eseguito il comando riportato sotto. Per PostgreSQL " 2810#~ "8.4+, in genere PL/pgSQL è già installato" 2811 2812#~ msgid "createlang plpgsql [yourdatabase]" 2813#~ msgstr "createlang plpgsql [il_tuo_database]" 2814 2815#~ msgid "" 2816#~ "Now load the PostGIS object and function definitions into your database " 2817#~ "by loading the <filename>postgis.sql</filename> definitions file (located " 2818#~ "in <filename>[prefix]/share/contrib</filename> as specified during the " 2819#~ "configuration step)." 2820#~ msgstr "" 2821#~ "Poi caricate le definizioni degli oggetti e delle funzioni PostGIS, " 2822#~ "tramite il file di definizioni <filename>postgis.sql</filename> (ubicato " 2823#~ "in <filename>[prefix]/share/contrib</filename> come specificato in fase " 2824#~ "di configurazione)." 2825 2826#~ msgid "psql -d [yourdatabase] -f postgis.sql" 2827#~ msgstr "psql -d [il_tuo_database] -f postgis.sql" 2828 2829#~ msgid "" 2830#~ "For a complete set of EPSG coordinate system definition identifiers, you " 2831#~ "can also load the <filename>spatial_ref_sys.sql</filename> definitions " 2832#~ "file and populate the <varname>spatial_ref_sys</varname> table. This will " 2833#~ "permit you to perform ST_Transform() operations on geometries." 2834#~ msgstr "" 2835#~ "Per un insieme completo dei sistemi di coordinate con gli identificatori " 2836#~ "EPSG potete caricare il file di definizioni <filename>spatial_ref_sys." 2837#~ "sql</filename> e caricare i valori nella tabella " 2838#~ "<varname>spatial_ref_sys</varname>. Ciò vi consentirà di eseguire le " 2839#~ "operazioni ST_Transform() sulle geometrie." 2840 2841#~ msgid "psql -d [yourdatabase] -f spatial_ref_sys.sql" 2842#~ msgstr "psql -d [il_tuo_database] -f spatial_ref_sys.sql" 2843 2844#~ msgid "" 2845#~ "If you wish to add comments to the PostGIS functions, the final step is " 2846#~ "to load the <filename>postgis_comments.sql</filename> into your spatial " 2847#~ "database. The comments can be viewed by simply typing <command>\\dd " 2848#~ "[function_name]</command> from a <command>psql</command> terminal window." 2849#~ msgstr "" 2850#~ "Se volete aggiungere i commenti alle funzioni PostGIS, l'ultimo passo " 2851#~ "consiste nel caricare <filename>postgis_comments.sql</filename> nel " 2852#~ "vostro database spaziale. I commenti possono essere visti digitando " 2853#~ "<command>\\dd [nome funzione]</command> da una finestra <command>psql</" 2854#~ "command>." 2855 2856#~ msgid "psql -d [yourdatabase] -f postgis_comments.sql" 2857#~ msgstr "psql -d [[il_tuo_database] -f postgis_comments.sql" 2858 2859#~ msgid "Install raster support" 2860#~ msgstr "Installazione del supporto raster" 2861 2862#~ msgid "psql -d [yourdatabase] -f rtpostgis.sql" 2863#~ msgstr "psql -d [il_tuo_database] -f rtpostgis.sql" 2864 2865#~ msgid "" 2866#~ "Install raster support comments. This will provide quick help info for " 2867#~ "each raster function using psql or PgAdmin or any other PostgreSQL tool " 2868#~ "that can show function comments" 2869#~ msgstr "" 2870#~ "Installazione dei commenti per il supporto raster. Questo fornisce una " 2871#~ "guida sintetica per ciascuna funzione raster utilizzando psql o PgAdmin o " 2872#~ "qualsiasi altro strumento di PostgreSQL che possa mostrare i commenti " 2873#~ "alle funzioni" 2874 2875#~ msgid "psql -d [yourdatabase] -f raster_comments.sql" 2876#~ msgstr "psql -d [il_tuo_database] -f raster_comments.sql" 2877 2878#~ msgid "Install topology support" 2879#~ msgstr "Installazione del supporto per la topologia" 2880 2881#~ msgid "psql -d [yourdatabase] -f topology/topology.sql" 2882#~ msgstr "psql -d [il_tuo_database] -f topology/topology.sql" 2883 2884#~ msgid "" 2885#~ "Install topology support comments. This will provide quick help info for " 2886#~ "each topology function / type using psql or PgAdmin or any other " 2887#~ "PostgreSQL tool that can show function comments" 2888#~ msgstr "" 2889#~ "Installa i commenti per il supporto topologico. Questa opzione fornisce " 2890#~ "una guida rapida per ciascuna delle funzioni e i tipi topologici, tramite " 2891#~ "psql o PgAdmin o qualsiasi altro strumento PostgreSQL con la capacità di " 2892#~ "mostrare i commenti delle funzioni" 2893 2894#~ msgid "psql -d [yourdatabase] -f topology/topology_comments.sql" 2895#~ msgstr "psql -d [il_tuo_database] -f topology/topology_comments.sql" 2896 2897#~ msgid "" 2898#~ "There is an alternative <filename>legacy_minimal.sql</filename> you can " 2899#~ "run instead which will install barebones needed to recover tables and " 2900#~ "work with apps like MapServer and GeoServer. If you have views that use " 2901#~ "things like distance / length etc, you'll need the full blown " 2902#~ "<filename>legacy.sql</filename>" 2903#~ msgstr "" 2904#~ "E' inoltre disponibile un file alternativo (<filename>legacy_minimal.sql</" 2905#~ "filename>) che potete eseguire per installare i componenti minimi " 2906#~ "richiesti per ripristinare le tabelle e operare con applicazioni come " 2907#~ "MapServer e GeoServer. Se avete delle viste che utilizzano elementi come " 2908#~ "distanza, lunghezza, ecc, vi servirà il file completo <filename>legacy." 2909#~ "sql</filename>" 2910 2911#~ msgid "Create a spatially-enabled database from a template" 2912#~ msgstr "" 2913#~ "Creare un database con funzionalità spaziali a partire da uno schema di " 2914#~ "esempio" 2915 2916#~ msgid "" 2917#~ "Some packaged distributions of PostGIS (in particular the Win32 " 2918#~ "installers for PostGIS >= 1.1.5) load the PostGIS functions into a " 2919#~ "template database called <varname>template_postgis</varname>. If the " 2920#~ "<varname>template_postgis</varname> database exists in your PostgreSQL " 2921#~ "installation then it is possible for users and/or applications to create " 2922#~ "spatially-enabled databases using a single command. Note that in both " 2923#~ "cases, the database user must have been granted the privilege to create " 2924#~ "new databases." 2925#~ msgstr "" 2926#~ "Alcune distribuzioni pacchettizzate di PostGIS (in particolare i file di " 2927#~ "installazione Win32 per PostGIS > 1.1.5) caricano le funzioni PostGIS in " 2928#~ "un database di esempio denominato <varname>template_postgis</varname>. Se " 2929#~ "il database <varname>template_postgis</varname> esiste nella vostra " 2930#~ "installazione PostgreSQL, allora è possibile per utenti e applicazioni " 2931#~ "creare database con funzioni spaziali utilizzando un singolo comando. Da " 2932#~ "notare che in entrambi i casi all'utente del database deve essere " 2933#~ "riconosciuto il ruolo di creare nuovi database." 2934 2935#~ msgid "From the shell:" 2936#~ msgstr "Dalla riga di comando:" 2937 2938#~ msgid "# createdb -T template_postgis my_spatial_db" 2939#~ msgstr "# createdb -T template_postgis my_spatial_db" 2940 2941#~ msgid "From SQL:" 2942#~ msgstr "Da SQL:" 2943 2944#~ msgid "postgres=# CREATE DATABASE my_spatial_db TEMPLATE=template_postgis" 2945#~ msgstr "postgres=# CREATE DATABASE my_spatial_db TEMPLATE=template_postgis" 2946 2947#~ msgid "Upgrading" 2948#~ msgstr "Aggiornamento" 2949 2950#~ msgid "" 2951#~ "Upgrading existing spatial databases can be tricky as it requires " 2952#~ "replacement or introduction of new PostGIS object definitions." 2953#~ msgstr "" 2954#~ "L'aggiornamento di database spaziali preesistenti può essere complicato, " 2955#~ "perché richiede la sostituzione o l'introduzione di nuove definizioni di " 2956#~ "oggetti PostGIS." 2957 2958#~ msgid "" 2959#~ "Unfortunately not all definitions can be easily replaced in a live " 2960#~ "database, so sometimes your best bet is a dump/reload process." 2961#~ msgstr "" 2962#~ "Purtroppo non tutte le definizioni possono essere sostituite facilmente " 2963#~ "in un database attivo, per cui in alcuni casi la cosa migliore è seguire " 2964#~ "un processo di scaricamento e ricaricamento dei dati." 2965 2966#~ msgid "" 2967#~ "If you installed your database using extensions, you'll need to upgrade " 2968#~ "using the extension model as well. If you installed using the old sql " 2969#~ "script way, then you should upgrade using the sql script way. Please " 2970#~ "refer to the appropriate." 2971#~ msgstr "" 2972#~ "Se avete installato il database con le estensioni, dovrete eseguire anche " 2973#~ "l'aggiornamento con il modello delle estensioni. Se avete invece eseguito " 2974#~ "l'installazione con il vecchio sistema dello script SQL, anche " 2975#~ "l'aggiornamento dovrà essere eseguito con lo script SQL. Fate riferimento " 2976#~ "al paragrafo corrispondente." 2977 2978#~ msgid "" 2979#~ "This section applies only to those who installed PostGIS not using " 2980#~ "extensions. If you have extensions and try to upgrade with this approach " 2981#~ "you'll get messages like:" 2982#~ msgstr "" 2983#~ "Questo paragrafo vale solo per coloro che hanno installato PostGIS senza " 2984#~ "estensioni. Se avete le estensioni e provate a eseguire l'aggiornamento " 2985#~ "con questo sistema, otterrete messaggi tipo:" 2986 2987#~ msgid "can't drop ... because postgis extension depends on it" 2988#~ msgstr "" 2989#~ "non posso eseguire il DROP, dato che c'è una dipendenza dell'estensione " 2990#~ "PostGIS" 2991 2992#, fuzzy 2993#~ msgid "" 2994#~ "The same procedure applies to raster, topology and sfcgal extensions, " 2995#~ "with upgrade files named <filename>rtpostgis_upgrade.sql</filename>, " 2996#~ "<filename>topology_upgrade.sql</filename> and <filename>sfcgal_upgrade." 2997#~ "sql</filename> respectively. If you need them:" 2998#~ msgstr "" 2999#~ "La stessa procedura si applica alle estensioni per i raster e per la " 3000#~ "topologia, i cui file si chiamano rispettivamente " 3001#~ "<filename>rtpostgis_upgrade*.sql</filename> e <filename>topology_upgrade*." 3002#~ "sql</filename> respectively. Se vi servono:" 3003 3004#~ msgid "" 3005#~ "The <xref linkend=\"PostGIS_Full_Version\"/> function should inform you " 3006#~ "about the need to run this kind of upgrade using a \"procs need upgrade\" " 3007#~ "message." 3008#~ msgstr "" 3009#~ "La funzione <xref linkend=\"PostGIS_Full_Version\"/> dovrebbe informarvi " 3010#~ "della necessita di eseguire questo tipo di aggiornamento attraverso un " 3011#~ "messaggio tipo \"procs need upgrade\"." 3012 3013#~ msgid "" 3014#~ "If you originally installed PostGIS with extensions, then you need to " 3015#~ "upgrade using extensions as well. Doing a minor upgrade with extensions, " 3016#~ "is fairly painless." 3017#~ msgstr "" 3018#~ "Se inizialmente avete installato PostGIS con le estensioni, anche " 3019#~ "l'aggiornamento dovrà essere eseguito con le estensioni. Eseguire un " 3020#~ "aggiornamento di una versione minore con le estensioni è un'operazione " 3021#~ "abbastanza tranquilla." 3022 3023#~ msgid "" 3024#~ "ALTER EXTENSION postgis UPDATE TO \"&last_release_version;\";\n" 3025#~ "ALTER EXTENSION postgis_topology UPDATE TO \"&last_release_version;\";" 3026#~ msgstr "" 3027#~ "ALTER EXTENSION postgis UPDATE TO \"&last_release_version;\";\n" 3028#~ "ALTER EXTENSION postgis_topology UPDATE TO \"&last_release_version;\";" 3029 3030#~ msgid "If you get an error notice something like:" 3031#~ msgstr "Se ottenete un errore tipo:" 3032 3033#~ msgid "No migration path defined for ... to &last_release_version;" 3034#~ msgstr "No migration path defined for ... to &last_release_version;" 3035 3036#~ msgid "" 3037#~ "The dump/reload process is assisted by the postgis_restore.pl script " 3038#~ "which takes care of skipping from the dump all definitions which belong " 3039#~ "to PostGIS (including old ones), allowing you to restore your schemas and " 3040#~ "data into a database with PostGIS installed without getting duplicate " 3041#~ "symbol errors or bringing forward deprecated objects." 3042#~ msgstr "" 3043#~ "Il processo di scaricamento e ricaricamento dei dati viene assistito " 3044#~ "dallo script postgis_restore.pl. Questo si fa carico di saltare nello " 3045#~ "scaricamento tutte le definizioni che fanno parte di PostGIS (comprese " 3046#~ "quelle obsolete), consentendo così di ripristinare gli schemi e i dati in " 3047#~ "un database con PostGIS senza ottenere errori legati alla presenza di " 3048#~ "simboli duplicati e senza portarsi dietro oggetti obsoleti. " 3049 3050#~ msgid "" 3051#~ "Supplementary instructions for windows users are available at <ulink url=" 3052#~ "\"http://trac.osgeo.org/postgis/wiki/UsersWikiWinUpgrade\">Windows Hard " 3053#~ "upgrade</ulink>." 3054#~ msgstr "" 3055#~ "Ulteriori istruzioni per gli utenti Windows sono disponibili alla pagina " 3056#~ "<ulink url=\"http://trac.osgeo.org/postgis/wiki/UsersWikiWinUpgrade" 3057#~ "\">Windows Hard upgrade</ulink>." 3058 3059#~ msgid "The Procedure is as follows:" 3060#~ msgstr "La procedura è la seguente:" 3061 3062#~ msgid "" 3063#~ "Create a \"custom-format\" dump of the database you want to upgrade " 3064#~ "(let's call it <varname>olddb</varname>) include binary blobs (-b) and " 3065#~ "verbose (-v) output. The user can be the owner of the db, need not be " 3066#~ "postgres super account." 3067#~ msgstr "" 3068#~ "Create un dump \"con formato personalizzato\" del database da aggiornare " 3069#~ "(che chiameremo <varname>olddb</varname>), includendo i blob binari (-b) " 3070#~ "e con uscita dettagliata (-v). L'utente può essere il proprietario del " 3071#~ "database, non serve avere privilegi da amministratore." 3072 3073#~ msgid "" 3074#~ "pg_dump -h localhost -p 5432 -U postgres -Fc -b -v -f \"/somepath/olddb." 3075#~ "backup\" olddb" 3076#~ msgstr "" 3077#~ "pg_dump -h localhost -p 5432 -U postgres -Fc -b -v -f \"/somepath/olddb." 3078#~ "backup\" olddb" 3079 3080#~ msgid "" 3081#~ "Do a fresh install of PostGIS in a new database -- we'll refer to this " 3082#~ "database as <varname>newdb</varname>. Please refer to <xref linkend=" 3083#~ "\"create_new_db\"/> and <xref linkend=\"create_new_db_extensions\"/> for " 3084#~ "instructions on how to do this." 3085#~ msgstr "" 3086#~ "Eseguire un'installazione da zero di PostGIS in un nuovo database -- " 3087#~ "chiameremo questo database <varname>newdb</varname>. Vi rimandiamo a " 3088#~ "<xref linkend=\"create_new_db\"/> e <xref linkend=" 3089#~ "\"create_new_db_extensions\"/> per le relative istruzioni." 3090 3091#~ msgid "" 3092#~ "The spatial_ref_sys entries found in your dump will be restored, but they " 3093#~ "will not override existing ones in spatial_ref_sys. This is to ensure " 3094#~ "that fixes in the official set will be properly propagated to restored " 3095#~ "databases. If for any reason you really want your own overrides of " 3096#~ "standard entries just don't load the spatial_ref_sys.sql file when " 3097#~ "creating the new db." 3098#~ msgstr "" 3099#~ "Le voci spatial_ref_sys presenti nel vostro dump saranno ripristinate, ma " 3100#~ "non avranno la precedenza su quelle esistenti in spatial_ref_sys. Ciò è " 3101#~ "per assicurarsi che l'elenco ufficiale venga correttamente trasmesso ai " 3102#~ "database ripristinati. Se per una qualsiasi ragione volete davvero che le " 3103#~ "vostre definizioni siano considerate al posto di quelle standard, potete " 3104#~ "evitare di caricare spatial_ref_sys.sql nel momento in cui create il " 3105#~ "nuovo database." 3106 3107#~ msgid "" 3108#~ "If your database is really old or you know you've been using long " 3109#~ "deprecated functions in your views and functions, you might need to load " 3110#~ "<filename>legacy.sql</filename> for all your functions and views etc. to " 3111#~ "properly come back. Only do this if _really_ needed. Consider upgrading " 3112#~ "your views and functions before dumping instead, if possible. The " 3113#~ "deprecated functions can be later removed by loading " 3114#~ "<filename>uninstall_legacy.sql</filename>." 3115#~ msgstr "" 3116#~ "Se il vostro database è molto vecchio, o sapete che avete utilizzato " 3117#~ "nelle vostre viste e nelle vostre funzioni delle funzioni obsolete, " 3118#~ "potreste dover caricare il file <filename>legacy.sql</filename>. Eseguite " 3119#~ "questa operazione solo se vi serve _veramente_. Considerate la " 3120#~ "possibilità di aggiornare le vostre viste e le voste funzioni prima di " 3121#~ "eseguire il dump, se possibile. Le funzioni obsolete possono poi essere " 3122#~ "rimosse caricando il file <filename>uninstall_legacy.sql</filename>. " 3123 3124#~ msgid "" 3125#~ "Restore your backup into your fresh <varname>newdb</varname> database " 3126#~ "using postgis_restore.pl. Unexpected errors, if any, will be printed to " 3127#~ "the standard error stream by psql. Keep a log of those." 3128#~ msgstr "" 3129#~ "Ripristinate il vostro backup nel nuovo database <varname>newdb</varname> " 3130#~ "tramite postgis_restore.pl. Eventuali errori imprevisti, se presenti, " 3131#~ "saranno trascritti da psql sull'uscita standard error. Tenete una traccia " 3132#~ "di tali errori." 3133 3134#~ msgid "" 3135#~ "perl utils/postgis_restore.pl \"/somepath/olddb.backup\" | psql -h " 3136#~ "localhost -p 5432 -U postgres newdb 2> errors.txt" 3137#~ msgstr "" 3138#~ "perl utils/postgis_restore.pl \"/somepath/olddb.backup\" | psql -h " 3139#~ "localhost -p 5432 -U postgres newdb 2> errors.txt" 3140 3141#~ msgid "Errors may arise in the following cases:" 3142#~ msgstr "Si potrebbero riscontrare errori nei casi seguenti:" 3143 3144#~ msgid "" 3145#~ "Some of your views or functions make use of deprecated PostGIS objects. " 3146#~ "In order to fix this you may try loading <filename>legacy.sql</filename> " 3147#~ "script prior to restore or you'll have to restore to a version of PostGIS " 3148#~ "which still contains those objects and try a migration again after " 3149#~ "porting your code. If the <filename>legacy.sql</filename> way works for " 3150#~ "you, don't forget to fix your code to stop using deprecated functions and " 3151#~ "drop them loading <filename>uninstall_legacy.sql</filename>." 3152#~ msgstr "" 3153#~ "Alcune delle vostre viste o funzioni fanno uso di oggetti PostGIS " 3154#~ "obsoleti. Per risolvere questo problema potete provare a caricare lo " 3155#~ "script <filename>legacy.sql</filename> prima del ripristino, oppure " 3156#~ "dovrete eseguire il ripristino in una versione di PostGIS che ancora " 3157#~ "contenga quegli oggetti, e poi ritentare la migrazione dopo aver adattato " 3158#~ "il codice alla nuova versione. Se il sistema <filename>legacy.sql</" 3159#~ "filename> vi funziona, non dimenticate di sistemare il vostro codice, " 3160#~ "eliminando i riferimenti alle funzioni obsolete, e poi disinstallate " 3161#~ "tutti i vecchi riferimenti tramite <filename>uninstall_legacy.sql</" 3162#~ "filename>." 3163 3164#~ msgid "" 3165#~ "In order to fix this you should copy your custom SRS to a SRID with a " 3166#~ "valid value (maybe in the 910000..910999 range), convert all your tables " 3167#~ "to the new srid (see <xref linkend=\"UpdateGeometrySRID\"/>), delete the " 3168#~ "invalid entry from spatial_ref_sys and re-construct the check(s) with:" 3169#~ msgstr "" 3170#~ "Per sistemare questo problema dovete copiare il vostro SRS personalizzato " 3171#~ "in un SRID con un valore valido (nell'intervallo 910000..910999), " 3172#~ "convertire tutte le tabelle nel nuovo SRID (vedi <xref linkend=" 3173#~ "\"UpdateGeometrySRID\"/>), cancellare la voce non valida da " 3174#~ "spatial_ref_sys e ricostruire il controllo o in controlli con:" 3175 3176#~ msgid "" 3177#~ "ALTER TABLE spatial_ref_sys ADD CONSTRAINT spatial_ref_sys_srid_check " 3178#~ "check (srid > 0 AND srid < 999000 );" 3179#~ msgstr "" 3180#~ "ALTER TABLE spatial_ref_sys ADD CONSTRAINT spatial_ref_sys_srid_check " 3181#~ "check (srid > 0 AND srid < 999000 );" 3182 3183#~ msgid "ALTER TABLE spatial_ref_sys ADD PRIMARY KEY(srid));" 3184#~ msgstr "ALTER TABLE spatial_ref_sys ADD PRIMARY KEY(srid));" 3185 3186#~ msgid "" 3187#~ "The raster support is currently optional, but installed by default. For " 3188#~ "enabling using the PostgreSQL 9.1+ extensions model raster is required. " 3189#~ "Using the extension enable process is preferred and more user-friendly. " 3190#~ "To spatially enable your database:" 3191#~ msgstr "" 3192#~ "Il supporto per i raster è attualmente opzionale, ma installato di " 3193#~ "default. Per abilitare l'uso di PostGIS come estensione (supportato da " 3194#~ "PostgreSQL 9.1+) è necessario il supporto raster. Usare PostGIS come " 3195#~ "estensione è il procedimento preferito e maggiormente user-friendly. Per " 3196#~ "abilitare spazialmente il tuo database:" 3197 3198#~ msgid "" 3199#~ "The rest of this chapter goes into detail each of the above installation " 3200#~ "steps." 3201#~ msgstr "" 3202#~ "La restante parte di questo capitolo entra nel dettaglio di ciascuno dei " 3203#~ "passi di installazione riportati soprta." 3204 3205#~ msgid "" 3206#~ "Compile with raster support. This will build rtpostgis-" 3207#~ "&last_release_version; library and rtpostgis.sql file. This may not be " 3208#~ "required in final release as plan is to build in raster support by " 3209#~ "default." 3210#~ msgstr "" 3211#~ "Compilare con supporto raster. Questo compilerà la libreria rtpostgis-" 3212#~ "&last_release_version; e il file rtpostgis.sql. Potrebbe non essere " 3213#~ "necessario nella release finale, dato che si prevede di avere il supporto " 3214#~ "raster come default." 3215 3216#~ msgid "" 3217#~ "If you installed postgis without raster support, you'll need to install " 3218#~ "raster support first (using the full <filename>rtpostgis.sql</filename>" 3219#~ msgstr "" 3220#~ "Se avete installato PostGIS senza supporto raster, dovrete prima " 3221#~ "installare il supporto raster (utilizzando tutto il file " 3222#~ "<filename>rtpostgis.sql</filename>" 3223 3224#~ msgid "" 3225#~ "Then you can run the below commands to package the functions in their " 3226#~ "respective extension." 3227#~ msgstr "" 3228#~ "Poi potete eseguire i comandi seguenti per creare i pacchetti di funzioni " 3229#~ "nelle estensioni corrispondenti." 3230