1# SOME DESCRIPTIVE TITLE. 2# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. 3# 4#, fuzzy 5msgid "" 6msgstr "" 7"Project-Id-Version: PACKAGE VERSION\n" 8"Report-Msgid-Bugs-To: https://bugs.kde.org\n" 9"POT-Creation-Date: 2021-09-11 01:55+0000\n" 10"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" 11"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" 12"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n" 13"MIME-Version: 1.0\n" 14"Content-Type: text/plain; charset=UTF-8\n" 15"Content-Transfer-Encoding: 8bit\n" 16 17#. Tag: title 18#: installation.xml:3 19#, no-c-format 20msgid "PostGIS Installation" 21msgstr "" 22 23#. Tag: para 24#: installation.xml:5 25#, no-c-format 26msgid "This chapter details the steps required to install PostGIS." 27msgstr "" 28 29#. Tag: title 30#: installation.xml:10 31#, no-c-format 32msgid "Short Version" 33msgstr "" 34 35#. Tag: para 36#: installation.xml:11 37#, no-c-format 38msgid "To compile assuming you have all the dependencies in your search path:" 39msgstr "" 40 41#. Tag: programlisting 42#: installation.xml:12 43#, no-c-format 44msgid "" 45"tar -xvfz postgis-&last_release_version;.tar.gz\n" 46"cd postgis-&last_release_version;\n" 47"./configure\n" 48"make\n" 49"make install" 50msgstr "" 51 52#. Tag: para 53#: installation.xml:13 54#, no-c-format 55msgid "" 56"Once PostGIS is installed, it needs to be enabled (<xref linkend=" 57"\"create_spatial_db\"/>) or upgraded (<xref linkend=\"upgrading\"/>) in each " 58"individual database you want to use it in." 59msgstr "" 60 61#. Tag: title 62#: installation.xml:23 63#, no-c-format 64msgid "Compiling and Install from Source" 65msgstr "" 66 67#. Tag: para 68#: installation.xml:26 69#, no-c-format 70msgid "" 71"Many OS systems now include pre-built packages for PostgreSQL/PostGIS. In " 72"many cases compilation is only necessary if you want the most bleeding edge " 73"versions or you are a package maintainer." 74msgstr "" 75 76#. Tag: para 77#: installation.xml:31 78#, no-c-format 79msgid "" 80"This section includes general compilation instructions, if you are compiling " 81"for Windows etc or another OS, you may find additional more detailed help at " 82"<ulink url=\"http://trac.osgeo.org/postgis/wiki/UsersWikiInstall\">PostGIS " 83"User contributed compile guides</ulink> and <ulink url=\"http://trac.osgeo." 84"org/postgis/wiki/DevWikiMain\">PostGIS Dev Wiki</ulink>." 85msgstr "" 86 87#. Tag: para 88#: installation.xml:33 89#, no-c-format 90msgid "" 91"Pre-Built Packages for various OS are listed in <ulink url=\"http://trac." 92"osgeo.org/postgis/wiki/UsersWikiPackages\">PostGIS Pre-built Packages</ulink>" 93msgstr "" 94 95#. Tag: para 96#: installation.xml:34 97#, no-c-format 98msgid "" 99"If you are a windows user, you can get stable builds via Stackbuilder or " 100"<ulink url=\"https://postgis.net/windows_downloads\">PostGIS Windows " 101"download site</ulink> We also have <ulink url=\"https://postgis.net/" 102"windows_downloads\">very bleeding-edge windows experimental builds</ulink> " 103"that are built usually once or twice a week or whenever anything exciting " 104"happens. You can use these to experiment with the in progress releases of " 105"PostGIS" 106msgstr "" 107 108#. Tag: para 109#: installation.xml:39 110#, no-c-format 111msgid "" 112"The PostGIS module is an extension to the PostgreSQL backend server. As " 113"such, PostGIS &last_release_version; <emphasis>requires</emphasis> full " 114"PostgreSQL server headers access in order to compile. It can be built " 115"against PostgreSQL versions &min_postgres_version; or higher. Earlier " 116"versions of PostgreSQL are <emphasis>not</emphasis> supported." 117msgstr "" 118 119#. Tag: para 120#: installation.xml:47 121#, no-c-format 122msgid "" 123"Refer to the PostgreSQL installation guides if you haven't already installed " 124"PostgreSQL. <ulink url=\"http://www.postgresql.org\"> http://www.postgresql." 125"org </ulink> ." 126msgstr "" 127 128#. Tag: para 129#: installation.xml:57 130#, no-c-format 131msgid "" 132"For GEOS functionality, when you install PostgresSQL you may need to " 133"explicitly link PostgreSQL against the standard C++ library:" 134msgstr "" 135 136#. Tag: programlisting 137#: installation.xml:62 138#, no-c-format 139msgid "LDFLAGS=-lstdc++ ./configure [YOUR OPTIONS HERE]" 140msgstr "" 141 142#. Tag: para 143#: installation.xml:64 144#, no-c-format 145msgid "" 146"This is a workaround for bogus C++ exceptions interaction with older " 147"development tools. If you experience weird problems (backend unexpectedly " 148"closed or similar things) try this trick. This will require recompiling your " 149"PostgreSQL from scratch, of course." 150msgstr "" 151 152#. Tag: para 153#: installation.xml:72 154#, no-c-format 155msgid "" 156"The following steps outline the configuration and compilation of the PostGIS " 157"source. They are written for Linux users and will not work on Windows or Mac." 158msgstr "" 159 160#. Tag: title 161#: installation.xml:79 162#, no-c-format 163msgid "Getting the Source" 164msgstr "" 165 166#. Tag: para 167#: installation.xml:81 168#, no-c-format 169msgid "" 170"Retrieve the PostGIS source archive from the downloads website <ulink url=" 171"\"&postgis_download_url;\"> &postgis_download_url; </ulink>" 172msgstr "" 173 174#. Tag: programlisting 175#: installation.xml:88 176#, no-c-format 177msgid "" 178"wget &postgis_download_url;\n" 179"tar -xvzf postgis-&last_release_version;.tar.gz" 180msgstr "" 181 182#. Tag: para 183#: installation.xml:90 184#, no-c-format 185msgid "" 186"This will create a directory called <varname>postgis-&last_release_version;</" 187"varname> in the current working directory." 188msgstr "" 189 190#. Tag: para 191#: installation.xml:96 192#, no-c-format 193msgid "" 194"Alternatively, checkout the source from the <ulink url=\"https://git-scm.com/" 195"\"> git </ulink> repository <ulink url=\"https://git.osgeo.org/gitea/postgis/" 196"postgis/\"> https://git.osgeo.org/gitea/postgis/postgis/ </ulink> ." 197msgstr "" 198 199#. Tag: programlisting 200#: installation.xml:108 201#, no-c-format 202msgid "git clone https://git.osgeo.org/gitea/postgis/postgis.git postgis" 203msgstr "" 204 205#. Tag: para 206#: installation.xml:110 207#, no-c-format 208msgid "" 209"Change into the newly created <varname>postgis</varname> directory to " 210"continue the installation." 211msgstr "" 212 213#. Tag: title 214#: installation.xml:118 215#, no-c-format 216msgid "Install Requirements" 217msgstr "" 218 219#. Tag: para 220#: installation.xml:120 221#, no-c-format 222msgid "PostGIS has the following requirements for building and usage:" 223msgstr "" 224 225#. Tag: emphasis 226#: installation.xml:125 227#, no-c-format 228msgid "Required" 229msgstr "" 230 231#. Tag: para 232#: installation.xml:130 233#, no-c-format 234msgid "" 235"PostgreSQL &min_postgres_version; or higher. A complete installation of " 236"PostgreSQL (including server headers) is required. PostgreSQL is available " 237"from <ulink url=\"http://www.postgresql.org\"> http://www.postgresql.org </" 238"ulink> ." 239msgstr "" 240 241#. Tag: para 242#: installation.xml:139 243#, no-c-format 244msgid "" 245"For a full PostgreSQL / PostGIS support matrix and PostGIS/GEOS support " 246"matrix refer to <ulink url=\"http://trac.osgeo.org/postgis/wiki/" 247"UsersWikiPostgreSQLPostGIS\">http://trac.osgeo.org/postgis/wiki/" 248"UsersWikiPostgreSQLPostGIS</ulink>" 249msgstr "" 250 251#. Tag: para 252#: installation.xml:145 253#, no-c-format 254msgid "" 255"GNU C compiler (<filename>gcc</filename>). Some other ANSI C compilers can " 256"be used to compile PostGIS, but we find far fewer problems when compiling " 257"with <filename>gcc</filename>." 258msgstr "" 259 260#. Tag: para 261#: installation.xml:153 262#, no-c-format 263msgid "" 264"GNU Make (<filename>gmake</filename> or <filename>make</filename>). For many " 265"systems, GNU <filename>make</filename> is the default version of make. Check " 266"the version by invoking <filename>make -v</filename>. Other versions of " 267"<filename>make</filename> may not process the PostGIS <filename>Makefile</" 268"filename> properly." 269msgstr "" 270 271#. Tag: para 272#: installation.xml:163 273#, no-c-format 274msgid "" 275"Proj reprojection library. Proj 4.9 or above is required. The Proj library " 276"is used to provide coordinate reprojection support within PostGIS. Proj is " 277"available for download from <ulink url=\"https://proj.org/\"> https://proj." 278"org/ </ulink> ." 279msgstr "" 280 281#. Tag: para 282#: installation.xml:175 283#, no-c-format 284msgid "" 285"GEOS geometry library, version 3.6 or greater, but GEOS 3.9+ is required to " 286"take full advantage of all the new functions and features. GEOS is available " 287"for download from <ulink url=\"http://trac.osgeo.org/geos/\"> http://trac." 288"osgeo.org/geos/ </ulink>." 289msgstr "" 290 291#. Tag: para 292#: installation.xml:183 293#, no-c-format 294msgid "" 295"LibXML2, version 2.5.x or higher. LibXML2 is currently used in some imports " 296"functions (ST_GeomFromGML and ST_GeomFromKML). LibXML2 is available for " 297"download from <ulink url=\"http://xmlsoft.org/downloads.html\">http://" 298"xmlsoft.org/downloads.html</ulink>." 299msgstr "" 300 301#. Tag: para 302#: installation.xml:190 303#, no-c-format 304msgid "" 305"JSON-C, version 0.9 or higher. JSON-C is currently used to import GeoJSON " 306"via the function ST_GeomFromGeoJson. JSON-C is available for download from " 307"<ulink url=\"https://github.com/json-c/json-c/releases\">https://github.com/" 308"json-c/json-c/releases/</ulink>." 309msgstr "" 310 311#. Tag: para 312#: installation.xml:198 313#, no-c-format 314msgid "" 315"GDAL, version 2+ is required 3+ is preferred. This is required for raster " 316"support. <ulink url=\"http://trac.osgeo.org/gdal/wiki/DownloadSource" 317"\">http://trac.osgeo.org/gdal/wiki/DownloadSource</ulink>." 318msgstr "" 319 320#. Tag: para 321#: installation.xml:206 322#, no-c-format 323msgid "" 324"If compiling with PostgreSQL+JIT, LLVM version >=6 is required <ulink url=" 325"\"https://trac.osgeo.org/postgis/ticket/4125\">https://trac.osgeo.org/" 326"postgis/ticket/4125</ulink>." 327msgstr "" 328 329#. Tag: emphasis 330#: installation.xml:215 331#, no-c-format 332msgid "Optional" 333msgstr "" 334 335#. Tag: para 336#: installation.xml:220 337#, no-c-format 338msgid "" 339"GDAL (pseudo optional) only if you don't want raster you can leave it out. " 340"Also make sure to enable the drivers you want to use as described in <xref " 341"linkend=\"raster_configuration\"/>." 342msgstr "" 343 344#. Tag: para 345#: installation.xml:228 346#, no-c-format 347msgid "" 348"GTK (requires GTK+2.0, 2.8+) to compile the shp2pgsql-gui shape file loader. " 349"<ulink url=\"http://www.gtk.org/\"> http://www.gtk.org/ </ulink> ." 350msgstr "" 351 352#. Tag: para 353#: installation.xml:238 354#, no-c-format 355msgid "" 356"SFCGAL, version 1.3.1 (or higher) could be used to provide additional 2D and " 357"3D advanced analysis functions to PostGIS cf <xref linkend=\"reference_sfcgal" 358"\"/>. And also allow to use SFCGAL rather than GEOS for some 2D functions " 359"provided by both backends (like ST_Intersection or ST_Area, for instance). A " 360"PostgreSQL configuration variable <code>postgis.backend</code> allow end " 361"user to control which backend he want to use if SFCGAL is installed (GEOS by " 362"default). Nota: SFCGAL 1.2 require at least CGAL 4.3 and Boost 1.54 (cf: " 363"<ulink url=\"https://oslandia.gitlab.io/SFCGAL/dev.html\">https://oslandia." 364"gitlab.io/SFCGAL/dev.html</ulink>) <ulink url=\"https://gitlab.com/Oslandia/" 365"SFCGAL/\">https://gitlab.com/Oslandia/SFCGAL/</ulink>." 366msgstr "" 367 368#. Tag: para 369#: installation.xml:246 370#, no-c-format 371msgid "" 372"In order to build the <xref linkend=\"Address_Standardizer\"/> you will also " 373"need PCRE <ulink url=\"http://www.pcre.org\">http://www.pcre.org</ulink> " 374"(which generally is already installed on nix systems). <code>Regex::" 375"Assemble</code> perl CPAN package is only needed if you want to rebuild the " 376"data encoded in <filename>parseaddress-stcities.h</filename>. <xref linkend=" 377"\"Address_Standardizer\"/> will automatically be built if it detects a PCRE " 378"library, or you pass in a valid <varname>--with-pcre-dir=/path/to/pcre</" 379"varname> during configure." 380msgstr "" 381 382#. Tag: para 383#: installation.xml:253 384#, no-c-format 385msgid "" 386"To enable ST_AsMVT protobuf-c library 1.1.0 or higher (for usage) and the " 387"protoc-c compiler (for building) are required. Also, pkg-config is required " 388"to verify the correct minimum version of protobuf-c. See <ulink url=" 389"\"https://github.com/protobuf-c/protobuf-c\">protobuf-c</ulink>. By default, " 390"Postgis will use Wagyu to validate MVT polygons faster which requires a c+" 391"+11 compiler. It will use CXXFLAGS and the same compiler as the PostgreSQL " 392"installation. To disable this and use GEOS instead use the <varname>--" 393"without-wagyu</varname> during the configure step." 394msgstr "" 395 396#. Tag: para 397#: installation.xml:262 398#, no-c-format 399msgid "" 400"CUnit (<filename>CUnit</filename>). This is needed for regression testing. " 401"<ulink url=\"http://cunit.sourceforge.net/\">http://cunit.sourceforge.net/</" 402"ulink>" 403msgstr "" 404 405#. Tag: para 406#: installation.xml:268 407#, no-c-format 408msgid "" 409"DocBook (<filename>xsltproc</filename>) is required for building the " 410"documentation. Docbook is available from <ulink url=\"http://www.docbook.org/" 411"\"> http://www.docbook.org/ </ulink> ." 412msgstr "" 413 414#. Tag: para 415#: installation.xml:279 416#, no-c-format 417msgid "" 418"DBLatex (<filename>dblatex</filename>) is required for building the " 419"documentation in PDF format. DBLatex is available from <ulink url=\"http://" 420"dblatex.sourceforge.net/\"> http://dblatex.sourceforge.net/ </ulink> ." 421msgstr "" 422 423#. Tag: para 424#: installation.xml:290 425#, no-c-format 426msgid "" 427"ImageMagick (<filename>convert</filename>) is required to generate the " 428"images used in the documentation. ImageMagick is available from <ulink url=" 429"\"http://www.imagemagick.org/\"> http://www.imagemagick.org/ </ulink> ." 430msgstr "" 431 432#. Tag: title 433#: installation.xml:304 434#, no-c-format 435msgid "Build configuration" 436msgstr "" 437 438#. Tag: para 439#: installation.xml:306 440#, no-c-format 441msgid "" 442"As with most linux installations, the first step is to generate the Makefile " 443"that will be used to build the source code. This is done by running the " 444"shell script" 445msgstr "" 446 447#. Tag: para 448#: installation.xml:316 449#, no-c-format 450msgid "" 451"With no additional parameters, this command will attempt to automatically " 452"locate the required components and libraries needed to build the PostGIS " 453"source code on your system. Although this is the most common usage of " 454"<command>./configure</command>, the script accepts several parameters for " 455"those who have the required libraries and programs in non-standard locations." 456msgstr "" 457 458#. Tag: para 459#: installation.xml:324 460#, no-c-format 461msgid "" 462"The following list shows only the most commonly used parameters. For a " 463"complete list, use the <command>--help</command> or <command>--help=short</" 464"command> parameters." 465msgstr "" 466 467#. Tag: para 468#: installation.xml:334 469#, no-c-format 470msgid "" 471"Starting with PostGIS 3.0, the library files generated by default will no " 472"longer have the minor version as part of the file name. This means all " 473"PostGIS 3 libs will end in <code>postgis-3</code>. This was done to make " 474"pg_upgrade easier, with downside that you can only install one version " 475"PostGIS 3 series in your server. To get the old behavior of file including " 476"the minor version: e.g. <code>postgis-3.0</code> add this switch to your " 477"configure statement." 478msgstr "" 479 480#. Tag: para 481#: installation.xml:349 482#, no-c-format 483msgid "" 484"This is the location the PostGIS loader executables and shared libs will be " 485"installed. By default, this location is the same as the detected PostgreSQL " 486"installation." 487msgstr "" 488 489#. Tag: para 490#: installation.xml:356 491#, no-c-format 492msgid "" 493"This parameter is currently broken, as the package will only install into " 494"the PostgreSQL installation directory. Visit <ulink url=\"http://trac.osgeo." 495"org/postgis/ticket/635\"> http://trac.osgeo.org/postgis/ticket/635 </ulink> " 496"to track this bug." 497msgstr "" 498 499#. Tag: para 500#: installation.xml:371 501#, no-c-format 502msgid "" 503"PostgreSQL provides a utility called <command>pg_config</command> to enable " 504"extensions like PostGIS to locate the PostgreSQL installation directory. Use " 505"this parameter (<command>--with-pgconfig=/path/to/pg_config</command>) to " 506"manually specify a particular PostgreSQL installation that PostGIS will " 507"build against." 508msgstr "" 509 510#. Tag: para 511#: installation.xml:385 512#, no-c-format 513msgid "" 514"GDAL, a required library, provides functionality needed for raster support " 515"<command>gdal-config</command> to enable software installations to locate " 516"the GDAL installation directory. Use this parameter (<command>--with-" 517"gdalconfig=/path/to/gdal-config</command>) to manually specify a particular " 518"GDAL installation that PostGIS will build against." 519msgstr "" 520 521#. Tag: para 522#: installation.xml:399 523#, no-c-format 524msgid "" 525"GEOS, a required geometry library, provides a utility called <command>geos-" 526"config</command> to enable software installations to locate the GEOS " 527"installation directory. Use this parameter (<command>--with-geosconfig=/path/" 528"to/geos-config</command>) to manually specify a particular GEOS installation " 529"that PostGIS will build against." 530msgstr "" 531 532#. Tag: para 533#: installation.xml:413 534#, no-c-format 535msgid "" 536"LibXML is the library required for doing GeomFromKML/GML processes. It " 537"normally is found if you have libxml installed, but if not or you want a " 538"specific version used, you'll need to point PostGIS at a specific " 539"<filename>xml2-config</filename> confi file to enable software installations " 540"to locate the LibXML installation directory. Use this parameter (<command>>--" 541"with-xml2config=/path/to/xml2-config</command>) to manually specify a " 542"particular LibXML installation that PostGIS will build against." 543msgstr "" 544 545#. Tag: para 546#: installation.xml:431 547#, no-c-format 548msgid "" 549"Proj is a reprojection library required by PostGIS. Use this parameter " 550"(<command>--with-projdir=/path/to/projdir</command>) to manually specify a " 551"particular Proj installation directory that PostGIS will build against." 552msgstr "" 553 554#. Tag: para 555#: installation.xml:443 556#, no-c-format 557msgid "Directory where iconv is installed." 558msgstr "" 559 560#. Tag: para 561#: installation.xml:452 562#, no-c-format 563msgid "" 564"<ulink url=\"http://oss.metaparadigm.com/json-c/\">JSON-C</ulink> is an MIT-" 565"licensed JSON library required by PostGIS ST_GeomFromJSON support. Use this " 566"parameter (<command>--with-jsondir=/path/to/jsondir</command>) to manually " 567"specify a particular JSON-C installation directory that PostGIS will build " 568"against." 569msgstr "" 570 571#. Tag: para 572#: installation.xml:464 573#, no-c-format 574msgid "" 575"<ulink url=\"http://www.pcre.org/\">PCRE</ulink> is an BSD-licensed Perl " 576"Compatible Regular Expression library required by address_standardizer " 577"extension. Use this parameter (<command>--with-pcredir=/path/to/pcredir</" 578"command>) to manually specify a particular PCRE installation directory that " 579"PostGIS will build against." 580msgstr "" 581 582#. Tag: para 583#: installation.xml:476 584#, no-c-format 585msgid "" 586"Compile the data import GUI (requires GTK+2.0). This will create shp2pgsql-" 587"gui graphical interface to shp2pgsql." 588msgstr "" 589 590#. Tag: para 591#: installation.xml:485 592#, no-c-format 593msgid "Compile without raster support." 594msgstr "" 595 596#. Tag: para 597#: installation.xml:493 598#, no-c-format 599msgid "" 600"Disable topology support. There is no corresponding library as all logic " 601"needed for topology is in postgis-&last_release_version; library." 602msgstr "" 603 604#. Tag: para 605#: installation.xml:502 606#, no-c-format 607msgid "" 608"By default PostGIS will try to detect gettext support and compile with it, " 609"however if you run into incompatibility issues that cause breakage of " 610"loader, you can disable it entirely with this command. Refer to ticket " 611"<ulink url=\"http://trac.osgeo.org/postgis/ticket/748\">http://trac.osgeo." 612"org/postgis/ticket/748</ulink> for an example issue solved by configuring " 613"with this. NOTE: that you aren't missing much by turning this off. This is " 614"used for international help/label support for the GUI loader which is not " 615"yet documented and still experimental." 616msgstr "" 617 618#. Tag: para 619#: installation.xml:513 620#, no-c-format 621msgid "" 622"By default PostGIS will not install with sfcgal support without this switch. " 623"<varname>PATH</varname> is an optional argument that allows to specify an " 624"alternate PATH to sfcgal-config." 625msgstr "" 626 627#. Tag: para 628#: installation.xml:522 629#, no-c-format 630msgid "" 631"Disable updating postgis_revision.h to match current HEAD of the git " 632"repository." 633msgstr "" 634 635#. Tag: para 636#: installation.xml:529 637#, no-c-format 638msgid "" 639"If you obtained PostGIS from the <ulink url=\"https://trac.osgeo.org/postgis/" 640"wiki/CodeRepository\"> code repository </ulink> , the first step is really " 641"to run the script" 642msgstr "" 643 644#. Tag: para 645#: installation.xml:541 646#, no-c-format 647msgid "" 648"This script will generate the <command>configure</command> script that in " 649"turn is used to customize the installation of PostGIS." 650msgstr "" 651 652#. Tag: para 653#: installation.xml:546 654#, no-c-format 655msgid "" 656"If you instead obtained PostGIS as a tarball, running <command>./autogen.sh</" 657"command> is not necessary as <command>configure</command> has already been " 658"generated." 659msgstr "" 660 661#. Tag: title 662#: installation.xml:555 663#, no-c-format 664msgid "Building" 665msgstr "" 666 667#. Tag: para 668#: installation.xml:557 669#, no-c-format 670msgid "" 671"Once the Makefile has been generated, building PostGIS is as simple as " 672"running" 673msgstr "" 674 675#. Tag: para 676#: installation.xml:566 677#, no-c-format 678msgid "" 679"The last line of the output should be \"<code>PostGIS was built " 680"successfully. Ready to install.</code>\"" 681msgstr "" 682 683#. Tag: para 684#: installation.xml:571 685#, no-c-format 686msgid "" 687"As of PostGIS v1.4.0, all the functions have comments generated from the " 688"documentation. If you wish to install these comments into your spatial " 689"databases later, run the command which requires docbook. The " 690"postgis_comments.sql and other package comments files raster_comments.sql, " 691"topology_comments.sql are also packaged in the tar.gz distribution in the " 692"doc folder so no need to make comments if installing from the tar ball. " 693"Comments are also included as part of the CREATE EXTENSION install." 694msgstr "" 695 696#. Tag: command 697#: installation.xml:581 installation.xml:605 698#, no-c-format 699msgid "make comments" 700msgstr "" 701 702#. Tag: para 703#: installation.xml:584 704#, no-c-format 705msgid "" 706"Introduced in PostGIS 2.0. This generates html cheat sheets suitable for " 707"quick reference or for student handouts. This requires xsltproc to build and " 708"will generate 4 files in doc folder <filename>topology_cheatsheet.html</" 709"filename>, <filename>tiger_geocoder_cheatsheet.html</filename>, " 710"<filename>raster_cheatsheet.html</filename>, <filename>postgis_cheatsheet." 711"html</filename>" 712msgstr "" 713 714#. Tag: para 715#: installation.xml:589 716#, no-c-format 717msgid "" 718"You can download some pre-built ones available in html and pdf from <ulink " 719"url=\"http://www.postgis.us/study_guides\">PostGIS / PostgreSQL Study " 720"Guides</ulink>" 721msgstr "" 722 723#. Tag: command 724#: installation.xml:592 725#, no-c-format 726msgid "make cheatsheets" 727msgstr "" 728 729#. Tag: title 730#: installation.xml:597 731#, no-c-format 732msgid "Building PostGIS Extensions and Deploying them" 733msgstr "" 734 735#. Tag: para 736#: installation.xml:599 737#, no-c-format 738msgid "" 739"The PostGIS extensions are built and installed automatically if you are " 740"using PostgreSQL 9.1+." 741msgstr "" 742 743#. Tag: para 744#: installation.xml:602 745#, no-c-format 746msgid "" 747"If you are building from source repository, you need to build the function " 748"descriptions first. These get built if you have docbook installed. You can " 749"also manually build with the statement:" 750msgstr "" 751 752#. Tag: para 753#: installation.xml:607 754#, no-c-format 755msgid "" 756"Building the comments is not necessary if you are building from a release " 757"tar ball since these are packaged pre-built with the tar ball already." 758msgstr "" 759 760#. Tag: para 761#: installation.xml:608 762#, no-c-format 763msgid "" 764"The extensions should automatically build as part of the make install " 765"process. You can if needed build from the extensions folders or copy files " 766"if you need them on a different server." 767msgstr "" 768 769#. Tag: programlisting 770#: installation.xml:610 771#, no-c-format 772msgid "" 773"cd extensions\n" 774"cd postgis\n" 775"make clean\n" 776"make\n" 777"export PGUSER=postgres #overwrite psql variables\n" 778"make check #to test before install\n" 779"make install\n" 780"# to test extensions\n" 781"make check RUNTESTFLAGS=--extension" 782msgstr "" 783 784#. Tag: para 785#: installation.xml:611 786#, no-c-format 787msgid "" 788"<code>make check</code> uses psql to run tests and as such can use psql " 789"environment variables. Common ones useful to override are <varname>PGUSER</" 790"varname>,<varname>PGPORT</varname>, and <varname>PGHOST</varname>. Refer to " 791"<ulink url=\"https://www.postgresql.org/docs/current/libpq-envars.html" 792"\">psql environment variables</ulink>" 793msgstr "" 794 795#. Tag: para 796#: installation.xml:613 797#, no-c-format 798msgid "" 799"The extension files will always be the same for the same version of PostGIS " 800"and PostgreSQL regardless of OS, so it is fine to copy over the extension " 801"files from one OS to another as long as you have the PostGIS binaries " 802"already installed on your servers." 803msgstr "" 804 805#. Tag: para 806#: installation.xml:615 807#, no-c-format 808msgid "" 809"If you want to install the extensions manually on a separate server " 810"different from your development, You need to copy the following files from " 811"the extensions folder into the <filename>PostgreSQL / share / extension</" 812"filename> folder of your PostgreSQL install as well as the needed binaries " 813"for regular PostGIS if you don't have them already on the server." 814msgstr "" 815 816#. Tag: para 817#: installation.xml:622 818#, no-c-format 819msgid "" 820"These are the control files that denote information such as the version of " 821"the extension to install if not specified. <filename>postgis.control, " 822"postgis_topology.control</filename>." 823msgstr "" 824 825#. Tag: para 826#: installation.xml:628 827#, no-c-format 828msgid "" 829"All the files in the /sql folder of each extension. Note that these need to " 830"be copied to the root of the PostgreSQL share/extension folder " 831"<filename>extensions/postgis/sql/*.sql</filename>, <filename>extensions/" 832"postgis_topology/sql/*.sql</filename>" 833msgstr "" 834 835#. Tag: para 836#: installation.xml:634 837#, no-c-format 838msgid "" 839"Once you do that, you should see <varname>postgis</varname>, " 840"<varname>postgis_topology</varname> as available extensions in PgAdmin -> " 841"extensions." 842msgstr "" 843 844#. Tag: para 845#: installation.xml:635 846#, no-c-format 847msgid "" 848"If you are using psql, you can verify that the extensions are installed by " 849"running this query:" 850msgstr "" 851 852#. Tag: programlisting 853#: installation.xml:636 854#, no-c-format 855msgid "" 856"SELECT name, default_version,installed_version\n" 857"FROM pg_available_extensions WHERE name LIKE 'postgis%' or name LIKE 'address" 858"%';\n" 859"\n" 860" name | default_version | installed_version\n" 861"------------------------------+-----------------+-------------------\n" 862" address_standardizer | &last_release_version; | " 863"&last_release_version;\n" 864" address_standardizer_data_us | &last_release_version; | " 865"&last_release_version;\n" 866" postgis | &last_release_version; | " 867"&last_release_version;\n" 868" postgis_raster | &last_release_version; | " 869"&last_release_version;\n" 870" postgis_sfcgal | &last_release_version; |\n" 871" postgis_tiger_geocoder | &last_release_version; | " 872"&last_release_version;\n" 873" postgis_topology | &last_release_version; |\n" 874"(6 rows)" 875msgstr "" 876 877#. Tag: para 878#: installation.xml:638 879#, no-c-format 880msgid "" 881"If you have the extension installed in the database you are querying, you'll " 882"see mention in the <varname>installed_version</varname> column. If you get " 883"no records back, it means you don't have postgis extensions installed on the " 884"server at all. PgAdmin III 1.14+ will also provide this information in the " 885"<varname>extensions</varname> section of the database browser tree and will " 886"even allow upgrade or uninstall by right-clicking." 887msgstr "" 888 889#. Tag: para 890#: installation.xml:642 891#, no-c-format 892msgid "" 893"If you have the extensions available, you can install postgis extension in " 894"your database of choice by either using pgAdmin extension interface or " 895"running these sql commands:" 896msgstr "" 897 898#. Tag: programlisting 899#: installation.xml:643 900#, no-c-format 901msgid "" 902"CREATE EXTENSION postgis;\n" 903"CREATE EXTENSION postgis_raster;\n" 904"CREATE EXTENSION postgis_sfcgal;\n" 905"CREATE EXTENSION fuzzystrmatch; --needed for postgis_tiger_geocoder\n" 906"--optional used by postgis_tiger_geocoder, or can be used standalone\n" 907"CREATE EXTENSION address_standardizer;\n" 908"CREATE EXTENSION address_standardizer_data_us;\n" 909"CREATE EXTENSION postgis_tiger_geocoder;\n" 910"CREATE EXTENSION postgis_topology;" 911msgstr "" 912 913#. Tag: para 914#: installation.xml:645 915#, no-c-format 916msgid "" 917"In psql you can use to see what versions you have installed and also what " 918"schema they are installed." 919msgstr "" 920 921#. Tag: programlisting 922#: installation.xml:646 923#, no-c-format 924msgid "" 925"\\connect mygisdb\n" 926"\\x\n" 927"\\dx postgis*" 928msgstr "" 929 930#. Tag: screen 931#: installation.xml:648 932#, no-c-format 933msgid "" 934"List of installed extensions\n" 935"-[ RECORD 1 ]-------------------------------------------------\n" 936"Name | postgis\n" 937"Version | &last_release_version;\n" 938"Schema | public\n" 939"Description | PostGIS geometry, geography, and raster spat..\n" 940"-[ RECORD 2 ]-------------------------------------------------\n" 941"Name | postgis_raster\n" 942"Version | 3.0.0dev\n" 943"Schema | public\n" 944"Description | PostGIS raster types and functions\n" 945"-[ RECORD 3 ]-------------------------------------------------\n" 946"Name | postgis_tiger_geocoder\n" 947"Version | &last_release_version;\n" 948"Schema | tiger\n" 949"Description | PostGIS tiger geocoder and reverse geocoder\n" 950"-[ RECORD 4 ]-------------------------------------------------\n" 951"Name | postgis_topology\n" 952"Version | &last_release_version;\n" 953"Schema | topology\n" 954"Description | PostGIS topology spatial types and functions" 955msgstr "" 956 957#. Tag: para 958#: installation.xml:650 959#, no-c-format 960msgid "" 961"Extension tables <varname>spatial_ref_sys</varname>, <varname>layer</" 962"varname>, <varname>topology</varname> can not be explicitly backed up. They " 963"can only be backed up when the respective <varname>postgis</varname> or " 964"<varname>postgis_topology</varname> extension is backed up, which only seems " 965"to happen when you backup the whole database. As of PostGIS 2.0.1, only srid " 966"records not packaged with PostGIS are backed up when the database is backed " 967"up so don't go around changing srids we package and expect your changes to " 968"be there. Put in a ticket if you find an issue. The structures of extension " 969"tables are never backed up since they are created with <code>CREATE " 970"EXTENSION</code> and assumed to be the same for a given version of an " 971"extension. These behaviors are built into the current PostgreSQL extension " 972"model, so nothing we can do about it." 973msgstr "" 974 975#. Tag: para 976#: installation.xml:655 977#, no-c-format 978msgid "" 979"If you installed &last_release_version;, without using our wonderful " 980"extension system, you can change it to be extension based by running the " 981"below commands to package the functions in their respective extension." 982msgstr "" 983 984#. Tag: programlisting 985#: installation.xml:659 986#, no-c-format 987msgid "" 988"CREATE EXTENSION postgis FROM unpackaged;\n" 989"CREATE EXTENSION postgis_raster FROM unpackaged;\n" 990"CREATE EXTENSION postgis_topology FROM unpackaged;\n" 991"CREATE EXTENSION postgis_tiger_geocoder FROM unpackaged;" 992msgstr "" 993 994#. Tag: title 995#: installation.xml:665 996#, no-c-format 997msgid "Testing" 998msgstr "" 999 1000#. Tag: para 1001#: installation.xml:667 1002#, no-c-format 1003msgid "If you wish to test the PostGIS build, run" 1004msgstr "" 1005 1006#. Tag: command 1007#: installation.xml:672 1008#, no-c-format 1009msgid "make check" 1010msgstr "" 1011 1012#. Tag: para 1013#: installation.xml:675 1014#, no-c-format 1015msgid "" 1016"The above command will run through various checks and regression tests using " 1017"the generated library against an actual PostgreSQL database." 1018msgstr "" 1019 1020#. Tag: para 1021#: installation.xml:681 1022#, no-c-format 1023msgid "" 1024"If you configured PostGIS using non-standard PostgreSQL, GEOS, or Proj " 1025"locations, you may need to add their library locations to the " 1026"<varname>LD_LIBRARY_PATH</varname> environment variable." 1027msgstr "" 1028 1029#. Tag: para 1030#: installation.xml:689 1031#, no-c-format 1032msgid "" 1033"Currently, the <command>make check</command> relies on the <code>PATH</code> " 1034"and <code>PGPORT</code> environment variables when performing the checks - " 1035"it does <emphasis>not</emphasis> use the PostgreSQL version that may have " 1036"been specified using the configuration parameter <command>--with-pgconfig</" 1037"command>. So make sure to modify your PATH to match the detected PostgreSQL " 1038"installation during configuration or be prepared to deal with the impending " 1039"headaches." 1040msgstr "" 1041 1042#. Tag: para 1043#: installation.xml:701 1044#, no-c-format 1045msgid "" 1046"If successful, make check will produce the output of almost 500 tests. The " 1047"results will look similar to the following (numerous lines omitted below):" 1048msgstr "" 1049 1050#. Tag: programlisting 1051#: installation.xml:706 1052#, no-c-format 1053msgid "" 1054"CUnit - A unit testing framework for C - Version 2.1-3\n" 1055" http://cunit.sourceforge.net/\n" 1056"\n" 1057" .\n" 1058" .\n" 1059" .\n" 1060"\n" 1061"Run Summary: Type Total Ran Passed Failed Inactive\n" 1062" suites 44 44 n/a 0 0\n" 1063" tests 300 300 300 0 0\n" 1064" asserts 4215 4215 4215 0 n/a\n" 1065"Elapsed time = 0.229 seconds\n" 1066"\n" 1067" .\n" 1068" .\n" 1069" .\n" 1070"\n" 1071"Running tests\n" 1072"\n" 1073" .\n" 1074" .\n" 1075" .\n" 1076"\n" 1077"Run tests: 134\n" 1078"Failed: 0\n" 1079"\n" 1080"\n" 1081"-- if you build with SFCGAL\n" 1082"\n" 1083" .\n" 1084" .\n" 1085" .\n" 1086"\n" 1087"Running tests\n" 1088"\n" 1089" .\n" 1090" .\n" 1091" .\n" 1092"\n" 1093"Run tests: 13\n" 1094"Failed: 0\n" 1095"\n" 1096"-- if you built with raster support\n" 1097"\n" 1098" .\n" 1099" .\n" 1100" .\n" 1101"\n" 1102"Run Summary: Type Total Ran Passed Failed Inactive\n" 1103" suites 12 12 n/a 0 0\n" 1104" tests 65 65 65 0 0\n" 1105" asserts 45896 45896 45896 0 n/a\n" 1106"\n" 1107"\n" 1108" .\n" 1109" .\n" 1110" .\n" 1111"\n" 1112"Running tests\n" 1113"\n" 1114" .\n" 1115" .\n" 1116" .\n" 1117"\n" 1118"Run tests: 101\n" 1119"Failed: 0\n" 1120"\n" 1121"-- topology regress\n" 1122"\n" 1123".\n" 1124".\n" 1125".\n" 1126"\n" 1127"Running tests\n" 1128"\n" 1129" .\n" 1130" .\n" 1131" .\n" 1132"\n" 1133"Run tests: 51\n" 1134"Failed: 0\n" 1135"\n" 1136"-- if you built --with-gui, you should see this too\n" 1137"\n" 1138" CUnit - A unit testing framework for C - Version 2.1-2\n" 1139" http://cunit.sourceforge.net/\n" 1140"\n" 1141" .\n" 1142" .\n" 1143" .\n" 1144"\n" 1145"Run Summary: Type Total Ran Passed Failed Inactive\n" 1146" suites 2 2 n/a 0 0\n" 1147" tests 4 4 4 0 0\n" 1148" asserts 4 4 4 0 n/a" 1149msgstr "" 1150 1151#. Tag: para 1152#: installation.xml:708 1153#, no-c-format 1154msgid "" 1155"The <varname>postgis_tiger_geocoder</varname> and " 1156"<varname>address_standardizer</varname> extensions, currently only support " 1157"the standard PostgreSQL installcheck. To test these use the below. Note: the " 1158"make install is not necessary if you already did make install at root of " 1159"PostGIS code folder." 1160msgstr "" 1161 1162#. Tag: para 1163#: installation.xml:709 1164#, no-c-format 1165msgid "For address_standardizer:" 1166msgstr "" 1167 1168#. Tag: programlisting 1169#: installation.xml:710 1170#, no-c-format 1171msgid "" 1172"cd extensions/address_standardizer\n" 1173"make install\n" 1174"make installcheck" 1175msgstr "" 1176 1177#. Tag: para 1178#: installation.xml:712 1179#, no-c-format 1180msgid "Output should look like:" 1181msgstr "" 1182 1183#. Tag: screen 1184#: installation.xml:713 1185#, no-c-format 1186msgid "" 1187"============== dropping database \"contrib_regression\" ==============\n" 1188"DROP DATABASE\n" 1189"============== creating database \"contrib_regression\" ==============\n" 1190"CREATE DATABASE\n" 1191"ALTER DATABASE\n" 1192"============== running regression test queries ==============\n" 1193"test test-init-extensions ... ok\n" 1194"test test-parseaddress ... ok\n" 1195"test test-standardize_address_1 ... ok\n" 1196"test test-standardize_address_2 ... ok\n" 1197"\n" 1198"=====================\n" 1199" All 4 tests passed.\n" 1200"=====================" 1201msgstr "" 1202 1203#. Tag: para 1204#: installation.xml:715 1205#, no-c-format 1206msgid "" 1207"For tiger geocoder, make sure you have postgis and fuzzystrmatch extensions " 1208"available in your PostgreSQL instance. The address_standardizer tests will " 1209"also kick in if you built postgis with address_standardizer support:" 1210msgstr "" 1211 1212#. Tag: programlisting 1213#: installation.xml:716 1214#, no-c-format 1215msgid "" 1216"cd extensions/postgis_tiger_geocoder\n" 1217"make install\n" 1218"make installcheck" 1219msgstr "" 1220 1221#. Tag: para 1222#: installation.xml:717 1223#, no-c-format 1224msgid "output should look like:" 1225msgstr "" 1226 1227#. Tag: screen 1228#: installation.xml:718 1229#, no-c-format 1230msgid "" 1231"============== dropping database \"contrib_regression\" ==============\n" 1232"DROP DATABASE\n" 1233"============== creating database \"contrib_regression\" ==============\n" 1234"CREATE DATABASE\n" 1235"ALTER DATABASE\n" 1236"============== installing fuzzystrmatch ==============\n" 1237"CREATE EXTENSION\n" 1238"============== installing postgis ==============\n" 1239"CREATE EXTENSION\n" 1240"============== installing postgis_tiger_geocoder ==============\n" 1241"CREATE EXTENSION\n" 1242"============== installing address_standardizer ==============\n" 1243"CREATE EXTENSION\n" 1244"============== running regression test queries ==============\n" 1245"test test-normalize_address ... ok\n" 1246"test test-pagc_normalize_address ... ok\n" 1247"\n" 1248"=====================\n" 1249"All 2 tests passed.\n" 1250"=====================" 1251msgstr "" 1252 1253#. Tag: title 1254#: installation.xml:722 1255#, no-c-format 1256msgid "Installation" 1257msgstr "" 1258 1259#. Tag: para 1260#: installation.xml:724 1261#, no-c-format 1262msgid "To install PostGIS, type" 1263msgstr "" 1264 1265#. Tag: command 1266#: installation.xml:729 1267#, no-c-format 1268msgid "make install" 1269msgstr "" 1270 1271#. Tag: para 1272#: installation.xml:732 1273#, no-c-format 1274msgid "" 1275"This will copy the PostGIS installation files into their appropriate " 1276"subdirectory specified by the <command>--prefix</command> configuration " 1277"parameter. In particular:" 1278msgstr "" 1279 1280#. Tag: para 1281#: installation.xml:740 1282#, no-c-format 1283msgid "" 1284"The loader and dumper binaries are installed in <filename>[prefix]/bin</" 1285"filename>." 1286msgstr "" 1287 1288#. Tag: para 1289#: installation.xml:747 1290#, no-c-format 1291msgid "" 1292"The SQL files, such as <filename>postgis.sql</filename>, are installed in " 1293"<filename>[prefix]/share/contrib</filename>." 1294msgstr "" 1295 1296#. Tag: para 1297#: installation.xml:754 1298#, no-c-format 1299msgid "" 1300"The PostGIS libraries are installed in <filename>[prefix]/lib</filename>." 1301msgstr "" 1302 1303#. Tag: para 1304#: installation.xml:761 1305#, no-c-format 1306msgid "" 1307"If you previously ran the <command>make comments</command> command to " 1308"generate the <filename>postgis_comments.sql</filename>, " 1309"<filename>raster_comments.sql</filename> file, install the sql file by " 1310"running" 1311msgstr "" 1312 1313#. Tag: command 1314#: installation.xml:768 1315#, no-c-format 1316msgid "make comments-install" 1317msgstr "" 1318 1319#. Tag: para 1320#: installation.xml:772 1321#, no-c-format 1322msgid "" 1323"<filename>postgis_comments.sql</filename>, <filename>raster_comments.sql</" 1324"filename>, <filename>topology_comments.sql</filename> was separated from the " 1325"typical build and installation targets since with it comes the extra " 1326"dependency of <command>xsltproc</command>." 1327msgstr "" 1328 1329#. Tag: title 1330#: installation.xml:781 1331#, no-c-format 1332msgid "Installing and Using the address standardizer" 1333msgstr "" 1334 1335#. Tag: para 1336#: installation.xml:782 1337#, no-c-format 1338msgid "" 1339"The <code>address_standardizer</code> extension used to be a separate " 1340"package that required separate download. From PostGIS 2.2 on, it is now " 1341"bundled in. For more information about the address_standardize, what it " 1342"does, and how to configure it for your needs, refer to <xref linkend=" 1343"\"Address_Standardizer\"/>." 1344msgstr "" 1345 1346#. Tag: para 1347#: installation.xml:784 1348#, no-c-format 1349msgid "" 1350"This standardizer can be used in conjunction with the PostGIS packaged tiger " 1351"geocoder extension as a replacement for the <xref linkend=\"Normalize_Address" 1352"\"/> discussed. To use as replacement refer to <xref linkend=" 1353"\"tiger_pagc_address_standardizing\"/>. You can also use it as a building " 1354"block for your own geocoder or use it to standardize your addresses for " 1355"easier compare of addresses." 1356msgstr "" 1357 1358#. Tag: para 1359#: installation.xml:788 1360#, no-c-format 1361msgid "" 1362"The address standardizer relies on PCRE which is usually already installed " 1363"on many Nix systems, but you can download the latest at: <ulink url=\"http://" 1364"www.pcre.org\">http://www.pcre.org</ulink>. If during <xref linkend=" 1365"\"installation_configuration\"/>, PCRE is found, then the address " 1366"standardizer extension will automatically be built. If you have a custom " 1367"pcre install you want to use instead, pass to configure <code>--with-" 1368"pcredir=/path/to/pcre</code> where <filename>/path/to/pcre</filename> is the " 1369"root folder for your pcre include and lib directories." 1370msgstr "" 1371 1372#. Tag: para 1373#: installation.xml:791 1374#, no-c-format 1375msgid "" 1376"For Windows users, the PostGIS 2.1+ bundle is packaged with the " 1377"address_standardizer already so no need to compile and can move straight to " 1378"<code>CREATE EXTENSION</code> step." 1379msgstr "" 1380 1381#. Tag: para 1382#: installation.xml:794 1383#, no-c-format 1384msgid "" 1385"Once you have installed, you can connect to your database and run the SQL:" 1386msgstr "" 1387 1388#. Tag: programlisting 1389#: installation.xml:795 1390#, no-c-format 1391msgid "CREATE EXTENSION address_standardizer;" 1392msgstr "" 1393 1394#. Tag: para 1395#: installation.xml:797 1396#, no-c-format 1397msgid "The following test requires no rules, gaz, or lex tables" 1398msgstr "" 1399 1400#. Tag: programlisting 1401#: installation.xml:798 1402#, no-c-format 1403msgid "" 1404"SELECT num, street, city, state, zip\n" 1405" FROM parse_address('1 Devonshire Place PH301, Boston, MA 02109');" 1406msgstr "" 1407 1408#. Tag: para 1409#: installation.xml:799 1410#, no-c-format 1411msgid "Output should be" 1412msgstr "" 1413 1414#. Tag: screen 1415#: installation.xml:800 1416#, no-c-format 1417msgid "" 1418"num | street | city | state | zip\n" 1419"-----+------------------------+--------+-------+-------\n" 1420" 1 | Devonshire Place PH301 | Boston | MA | 02109" 1421msgstr "" 1422 1423#. Tag: title 1424#: installation.xml:802 1425#, no-c-format 1426msgid "Installing Regex::Assemble" 1427msgstr "" 1428 1429#. Tag: para 1430#: installation.xml:803 1431#, no-c-format 1432msgid "" 1433"Perl Regex:Assemble is no longer needed for compiling address_standardizer " 1434"extension since the files it generates are part of the source tree. However " 1435"if you need to edit the <filename>usps-st-city-orig.txt</filename> or " 1436"<filename>usps-st-city-orig.txt usps-st-city-adds.tx</filename>, you need to " 1437"rebuild <filename>parseaddress-stcities.h</filename> which does require " 1438"Regex:Assemble." 1439msgstr "" 1440 1441#. Tag: programlisting 1442#: installation.xml:804 1443#, no-c-format 1444msgid "cpan Regexp::Assemble" 1445msgstr "" 1446 1447#. Tag: para 1448#: installation.xml:805 1449#, no-c-format 1450msgid "or if you are on Ubuntu / Debian you might need to do" 1451msgstr "" 1452 1453#. Tag: programlisting 1454#: installation.xml:806 1455#, no-c-format 1456msgid "sudo perl -MCPAN -e \"install Regexp::Assemble\"" 1457msgstr "" 1458 1459#. Tag: title 1460#: installation.xml:811 1461#, no-c-format 1462msgid "Installing, Upgrading Tiger Geocoder and loading data" 1463msgstr "" 1464 1465#. Tag: para 1466#: installation.xml:813 1467#, no-c-format 1468msgid "" 1469"Extras like Tiger geocoder may not be packaged in your PostGIS distribution. " 1470"If you are missing the tiger geocoder extension or want a newer version than " 1471"what your install comes with, then use the <filename>share/extension/" 1472"postgis_tiger_geocoder.*</filename> files from the packages in <ulink url=" 1473"\"http://postgis.net/windows_downloads/\">Windows Unreleased Versions</" 1474"ulink> section for your version of PostgreSQL. Although these packages are " 1475"for windows, the postgis_tiger_geocoder extension files will work on any OS " 1476"since the extension is an SQL/plpgsql only extension." 1477msgstr "" 1478 1479#. Tag: title 1480#: installation.xml:817 1481#, no-c-format 1482msgid "Tiger Geocoder Enabling your PostGIS database: Using Extension" 1483msgstr "" 1484 1485#. Tag: para 1486#: installation.xml:818 1487#, no-c-format 1488msgid "" 1489"If you are using PostgreSQL 9.1+ and PostGIS 2.1+, you can take advantage of " 1490"the new extension model for installing tiger geocoder. To do so:" 1491msgstr "" 1492 1493#. Tag: para 1494#: installation.xml:820 1495#, no-c-format 1496msgid "" 1497"First get binaries for PostGIS 2.1+ or compile and install as usual. This " 1498"should install the necessary extension files as well for tiger geocoder." 1499msgstr "" 1500 1501#. Tag: para 1502#: installation.xml:821 1503#, no-c-format 1504msgid "" 1505"Connect to your database via psql or pgAdmin or some other tool and run the " 1506"following SQL commands. Note that if you are installing in a database that " 1507"already has postgis, you don't need to do the first step. If you have " 1508"<varname>fuzzystrmatch</varname> extension already installed, you don't need " 1509"to do the second step either." 1510msgstr "" 1511 1512#. Tag: programlisting 1513#: installation.xml:822 1514#, no-c-format 1515msgid "" 1516"CREATE EXTENSION postgis;\n" 1517"CREATE EXTENSION fuzzystrmatch;\n" 1518"CREATE EXTENSION postgis_tiger_geocoder;\n" 1519"--this one is optional if you want to use the rules based standardizer " 1520"(pagc_normalize_address)\n" 1521"CREATE EXTENSION address_standardizer;" 1522msgstr "" 1523 1524#. Tag: para 1525#: installation.xml:824 1526#, no-c-format 1527msgid "" 1528"If you already have postgis_tiger_geocoder extension installed, and just " 1529"want to update to the latest run:" 1530msgstr "" 1531 1532#. Tag: programlisting 1533#: installation.xml:825 1534#, no-c-format 1535msgid "" 1536"ALTER EXTENSION postgis UPDATE;\n" 1537"ALTER EXTENSION postgis_tiger_geocoder UPDATE;" 1538msgstr "" 1539 1540#. Tag: para 1541#: installation.xml:826 1542#, no-c-format 1543msgid "" 1544"If you made custom entries or changes to <varname>tiger.loader_platform</" 1545"varname> and <varname>tiger.loader_variables</varname> you may need to " 1546"update these." 1547msgstr "" 1548 1549#. Tag: para 1550#: installation.xml:828 1551#, no-c-format 1552msgid "" 1553"To confirm your install is working correctly, run this sql in your database:" 1554msgstr "" 1555 1556#. Tag: programlisting 1557#: installation.xml:829 1558#, no-c-format 1559msgid "" 1560"SELECT na.address, na.streetname,na.streettypeabbrev, na.zip\n" 1561" FROM normalize_address('1 Devonshire Place, Boston, MA 02109') AS na;" 1562msgstr "" 1563 1564#. Tag: para 1565#: installation.xml:830 1566#, no-c-format 1567msgid "Which should output" 1568msgstr "" 1569 1570#. Tag: screen 1571#: installation.xml:831 1572#, no-c-format 1573msgid "" 1574"address | streetname | streettypeabbrev | zip\n" 1575"---------+------------+------------------+-------\n" 1576" 1 | Devonshire | Pl | 02109" 1577msgstr "" 1578 1579#. Tag: para 1580#: installation.xml:833 1581#, no-c-format 1582msgid "" 1583"Create a new record in <varname>tiger.loader_platform</varname> table with " 1584"the paths of your executables and server." 1585msgstr "" 1586 1587#. Tag: para 1588#: installation.xml:834 1589#, no-c-format 1590msgid "" 1591"So for example to create a profile called debbie that follows <code>sh</" 1592"code> convention. You would do:" 1593msgstr "" 1594 1595#. Tag: programlisting 1596#: installation.xml:835 1597#, no-c-format 1598msgid "" 1599"INSERT INTO tiger.loader_platform(os, declare_sect, pgbin, wget, " 1600"unzip_command, psql, path_sep,\n" 1601" loader, environ_set_command, county_process_command)\n" 1602"SELECT 'debbie', declare_sect, pgbin, wget, unzip_command, psql, path_sep,\n" 1603" loader, environ_set_command, county_process_command\n" 1604" FROM tiger.loader_platform\n" 1605" WHERE os = 'sh';" 1606msgstr "" 1607 1608#. Tag: para 1609#: installation.xml:836 1610#, no-c-format 1611msgid "" 1612"And then edit the paths in the <emphasis>declare_sect</emphasis> column to " 1613"those that fit Debbie's pg, unzip,shp2pgsql, psql, etc path locations." 1614msgstr "" 1615 1616#. Tag: para 1617#: installation.xml:838 1618#, no-c-format 1619msgid "" 1620"If you don't edit this <varname>loader_platform</varname> table, it will " 1621"just contain common case locations of items and you'll have to edit the " 1622"generated script after the script is generated." 1623msgstr "" 1624 1625#. Tag: para 1626#: installation.xml:840 1627#, no-c-format 1628msgid "" 1629"As of PostGIS 2.4.1 the Zip code-5 digit tabulation area <varname>zcta5</" 1630"varname> load step was revised to load current zcta5 data and is part of the " 1631"<xref linkend=\"Loader_Generate_Nation_Script\"/> when enabled. It is turned " 1632"off by default because it takes quite a bit of time to load (20 to 60 " 1633"minutes), takes up quite a bit of disk space, and is not used that often." 1634msgstr "" 1635 1636#. Tag: para 1637#: installation.xml:842 1638#, no-c-format 1639msgid "To enable it, do the following:" 1640msgstr "" 1641 1642#. Tag: programlisting 1643#: installation.xml:843 1644#, no-c-format 1645msgid "" 1646"UPDATE tiger.loader_lookuptables SET load = true WHERE table_name = " 1647"'zcta510';" 1648msgstr "" 1649 1650#. Tag: para 1651#: installation.xml:844 1652#, no-c-format 1653msgid "" 1654"If present the <xref linkend=\"Geocode\"/> function can use it if a boundary " 1655"filter is added to limit to just zips in that boundary. The <xref linkend=" 1656"\"Reverse_Geocode\"/> function uses it if the returned address is missing a " 1657"zip, which often happens with highway reverse geocoding." 1658msgstr "" 1659 1660#. Tag: para 1661#: installation.xml:847 1662#, no-c-format 1663msgid "" 1664"Create a folder called <filename>gisdata</filename> on root of server or " 1665"your local pc if you have a fast network connection to the server. This " 1666"folder is where the tiger files will be downloaded to and processed. If you " 1667"are not happy with having the folder on the root of the server, or simply " 1668"want to change to a different folder for staging, then edit the field " 1669"<varname>staging_fold</varname> in the <varname>tiger.loader_variables</" 1670"varname> table." 1671msgstr "" 1672 1673#. Tag: para 1674#: installation.xml:849 1675#, no-c-format 1676msgid "" 1677"Create a folder called temp in the <filename>gisdata</filename> folder or " 1678"wherever you designated the <varname>staging_fold</varname> to be. This will " 1679"be the folder where the loader extracts the downloaded tiger data." 1680msgstr "" 1681 1682#. Tag: para 1683#: installation.xml:851 1684#, no-c-format 1685msgid "" 1686"Then run the <xref linkend=\"Loader_Generate_Nation_Script\"/> SQL function " 1687"make sure to use the name of your custom profile and copy the script to a ." 1688"sh or .bat file. So for example to build the nation load:" 1689msgstr "" 1690 1691#. Tag: programlisting 1692#: installation.xml:852 1693#, no-c-format 1694msgid "" 1695"psql -c \"SELECT Loader_Generate_Nation_Script('debbie')\" -d geocoder -tA " 1696"> /gisdata/nation_script_load.sh" 1697msgstr "" 1698 1699#. Tag: para 1700#: installation.xml:855 1701#, no-c-format 1702msgid "Run the generated nation load commandline scripts." 1703msgstr "" 1704 1705#. Tag: programlisting 1706#: installation.xml:856 1707#, no-c-format 1708msgid "" 1709"cd /gisdata\n" 1710"sh nation_script_load.sh" 1711msgstr "" 1712 1713#. Tag: para 1714#: installation.xml:859 1715#, no-c-format 1716msgid "" 1717"After you are done running the nation script, you should have three tables " 1718"in your <code>tiger_data</code> schema and they should be filled with data. " 1719"Confirm you do by doing the following queries from psql or pgAdmin" 1720msgstr "" 1721 1722#. Tag: programlisting 1723#: installation.xml:860 1724#, no-c-format 1725msgid "SELECT count(*) FROM tiger_data.county_all;" 1726msgstr "" 1727 1728#. Tag: screen 1729#: installation.xml:861 1730#, no-c-format 1731msgid "" 1732"count\n" 1733"-------\n" 1734" 3233\n" 1735"(1 row)" 1736msgstr "" 1737 1738#. Tag: programlisting 1739#: installation.xml:862 1740#, no-c-format 1741msgid "SELECT count(*) FROM tiger_data.state_all;" 1742msgstr "" 1743 1744#. Tag: screen 1745#: installation.xml:863 1746#, no-c-format 1747msgid "" 1748"count\n" 1749"-------\n" 1750" 56\n" 1751"(1 row)" 1752msgstr "" 1753 1754#. Tag: para 1755#: installation.xml:866 1756#, no-c-format 1757msgid "" 1758"By default the tables corresponding to <varname>bg</varname>, " 1759"<varname>tract</varname>, <varname>tabblock</varname> are not loaded. These " 1760"tables are not used by the geocoder but are used by folks for population " 1761"statistics. If you wish to load them as part of your state loads, run the " 1762"following statement to enable them." 1763msgstr "" 1764 1765#. Tag: programlisting 1766#: installation.xml:868 1767#, no-c-format 1768msgid "" 1769"UPDATE tiger.loader_lookuptables SET load = true WHERE load = false AND " 1770"lookup_name IN('tract', 'bg', 'tabblock');" 1771msgstr "" 1772 1773#. Tag: para 1774#: installation.xml:869 1775#, no-c-format 1776msgid "" 1777"Alternatively you can load just these tables after loading state data using " 1778"the <xref linkend=\"Loader_Generate_Census_Script\"/>" 1779msgstr "" 1780 1781#. Tag: para 1782#: installation.xml:871 1783#, no-c-format 1784msgid "" 1785"For each state you want to load data for, generate a state script <xref " 1786"linkend=\"Loader_Generate_Script\"/>." 1787msgstr "" 1788 1789#. Tag: para 1790#: installation.xml:871 1791#, no-c-format 1792msgid "" 1793"DO NOT Generate the state script until you have already loaded the nation " 1794"data, because the state script utilizes county list loaded by nation script." 1795msgstr "" 1796 1797#. Tag: programlisting 1798#: installation.xml:873 1799#, no-c-format 1800msgid "" 1801"psql -c \"SELECT Loader_Generate_Script(ARRAY['MA'], 'debbie')\" -d geocoder " 1802"-tA > /gisdata/ma_load.sh" 1803msgstr "" 1804 1805#. Tag: para 1806#: installation.xml:875 1807#, no-c-format 1808msgid "Run the generated commandline scripts." 1809msgstr "" 1810 1811#. Tag: programlisting 1812#: installation.xml:876 1813#, no-c-format 1814msgid "" 1815"cd /gisdata\n" 1816"sh ma_load.sh" 1817msgstr "" 1818 1819#. Tag: para 1820#: installation.xml:878 1821#, no-c-format 1822msgid "" 1823"After you are done loading all data or at a stopping point, it's a good idea " 1824"to analyze all the tiger tables to update the stats (include inherited stats)" 1825msgstr "" 1826 1827#. Tag: programlisting 1828#: installation.xml:879 1829#, no-c-format 1830msgid "" 1831"SELECT install_missing_indexes();\n" 1832"vacuum (analyze, verbose) tiger.addr;\n" 1833"vacuum (analyze, verbose) tiger.edges;\n" 1834"vacuum (analyze, verbose) tiger.faces;\n" 1835"vacuum (analyze, verbose) tiger.featnames;\n" 1836"vacuum (analyze, verbose) tiger.place;\n" 1837"vacuum (analyze, verbose) tiger.cousub;\n" 1838"vacuum (analyze, verbose) tiger.county;\n" 1839"vacuum (analyze, verbose) tiger.state;\n" 1840"vacuum (analyze, verbose) tiger.zip_lookup_base;\n" 1841"vacuum (analyze, verbose) tiger.zip_state;\n" 1842"vacuum (analyze, verbose) tiger.zip_state_loc;" 1843msgstr "" 1844 1845#. Tag: title 1846#: installation.xml:882 1847#, no-c-format 1848msgid "Converting a Tiger Geocoder Regular Install to Extension Model" 1849msgstr "" 1850 1851#. Tag: para 1852#: installation.xml:883 1853#, no-c-format 1854msgid "" 1855"If you installed the tiger geocoder without using the extension model, you " 1856"can convert to the extension model as follows:" 1857msgstr "" 1858 1859#. Tag: para 1860#: installation.xml:885 1861#, no-c-format 1862msgid "" 1863"Follow instructions in <xref linkend=\"upgrade_tiger_geocoder\"/> for the " 1864"non-extension model upgrade." 1865msgstr "" 1866 1867#. Tag: para 1868#: installation.xml:886 1869#, no-c-format 1870msgid "" 1871"Connect to your database with psql or pgAdmin and run the following command:" 1872msgstr "" 1873 1874#. Tag: programlisting 1875#: installation.xml:887 1876#, no-c-format 1877msgid "CREATE EXTENSION postgis_tiger_geocoder FROM unpackaged;" 1878msgstr "" 1879 1880#. Tag: title 1881#: installation.xml:894 1882#, no-c-format 1883msgid "Tiger Geocoder Enabling your PostGIS database: Not Using Extensions" 1884msgstr "" 1885 1886#. Tag: para 1887#: installation.xml:895 1888#, no-c-format 1889msgid "First install PostGIS using the prior instructions." 1890msgstr "" 1891 1892#. Tag: para 1893#: installation.xml:899 installation.xml:959 1894#, no-c-format 1895msgid "" 1896"If you don't have an extras folder, download <ulink url=" 1897"\"&postgis_download_url;\">&postgis_download_url;</ulink>" 1898msgstr "" 1899 1900#. Tag: command 1901#: installation.xml:904 installation.xml:964 1902#, no-c-format 1903msgid "tar xvfz postgis-&last_release_version;.tar.gz" 1904msgstr "" 1905 1906#. Tag: command 1907#: installation.xml:908 1908#, no-c-format 1909msgid "cd postgis-&last_release_version;/extras/tiger_geocoder" 1910msgstr "" 1911 1912#. Tag: para 1913#: installation.xml:911 1914#, no-c-format 1915msgid "" 1916"Edit the <filename>tiger_loader_2015.sql</filename> (or latest loader file " 1917"you find, unless you want to load different year) to the paths of your " 1918"executables server etc or alternatively you can update the " 1919"<varname>loader_platform</varname> table once installed. If you don't edit " 1920"this file or the <varname>loader_platform</varname> table, it will just " 1921"contain common case locations of items and you'll have to edit the generated " 1922"script after the fact when you run the <xref linkend=" 1923"\"Loader_Generate_Nation_Script\"/> and <xref linkend=" 1924"\"Loader_Generate_Script\"/> SQL functions." 1925msgstr "" 1926 1927#. Tag: para 1928#: installation.xml:913 1929#, no-c-format 1930msgid "" 1931"If you are installing Tiger geocoder for the first time edit either the " 1932"<filename>create_geocode.bat</filename> script If you are on windows or the " 1933"<filename>create_geocode.sh</filename> if you are on Linux/Unix/Mac OSX with " 1934"your PostgreSQL specific settings and run the corresponding script from the " 1935"commandline." 1936msgstr "" 1937 1938#. Tag: para 1939#: installation.xml:917 1940#, no-c-format 1941msgid "" 1942"Verify that you now have a <varname>tiger</varname> schema in your database " 1943"and that it is part of your database search_path. If it is not, add it with " 1944"a command something along the line of:" 1945msgstr "" 1946 1947#. Tag: programlisting 1948#: installation.xml:917 1949#, no-c-format 1950msgid "ALTER DATABASE geocoder SET search_path=public, tiger;" 1951msgstr "" 1952 1953#. Tag: para 1954#: installation.xml:918 1955#, no-c-format 1956msgid "" 1957"The normalizing address functionality works more or less without any data " 1958"except for tricky addresses. Run this test and verify things look like this:" 1959msgstr "" 1960 1961#. Tag: programlisting 1962#: installation.xml:919 1963#, no-c-format 1964msgid "" 1965"SELECT pprint_addy(normalize_address('202 East Fremont Street, Las Vegas, " 1966"Nevada 89101')) As pretty_address;\n" 1967"pretty_address\n" 1968"---------------------------------------\n" 1969"202 E Fremont St, Las Vegas, NV 89101" 1970msgstr "" 1971 1972#. Tag: title 1973#: installation.xml:922 1974#, no-c-format 1975msgid "Using Address Standardizer Extension with Tiger geocoder" 1976msgstr "" 1977 1978#. Tag: para 1979#: installation.xml:923 1980#, no-c-format 1981msgid "" 1982"One of the many complaints of folks is the address normalizer function <xref " 1983"linkend=\"Normalize_Address\"/> function that normalizes an address for " 1984"prepping before geocoding. The normalizer is far from perfect and trying to " 1985"patch its imperfectness takes a vast amount of resources. As such we have " 1986"integrated with another project that has a much better address standardizer " 1987"engine. To use this new address_standardizer, you compile the extension as " 1988"described in <xref linkend=\"installing_pagc_address_standardizer\"/> and " 1989"install as an extension in your database." 1990msgstr "" 1991 1992#. Tag: para 1993#: installation.xml:926 1994#, no-c-format 1995msgid "" 1996"Once you install this extension in the same database as you have installed " 1997"<code>postgis_tiger_geocoder</code>, then the <xref linkend=" 1998"\"Pagc_Normalize_Address\"/> can be used instead of <xref linkend=" 1999"\"Normalize_Address\"/>. This extension is tiger agnostic, so can be used " 2000"with other data sources such as international addresses. The tiger geocoder " 2001"extension does come packaged with its own custom versions of <xref linkend=" 2002"\"rulestab\"/> ( <code>tiger.pagc_rules</code>) , <xref linkend=\"gaztab\"/> " 2003"(<code>tiger.pagc_gaz</code>), and <xref linkend=\"lextab\"/> (<code>tiger." 2004"pagc_lex</code>). These you can add and update to improve your standardizing " 2005"experience for your own needs." 2006msgstr "" 2007 2008#. Tag: title 2009#: installation.xml:929 2010#, no-c-format 2011msgid "Loading Tiger Data" 2012msgstr "" 2013 2014#. Tag: para 2015#: installation.xml:930 2016#, no-c-format 2017msgid "" 2018"The instructions for loading data are available in a more detailed form in " 2019"the <filename>extras/tiger_geocoder/tiger_2011/README</filename>. This just " 2020"includes the general steps." 2021msgstr "" 2022 2023#. Tag: para 2024#: installation.xml:931 2025#, no-c-format 2026msgid "" 2027"The load process downloads data from the census website for the respective " 2028"nation files, states requested, extracts the files, and then loads each " 2029"state into its own separate set of state tables. Each state table inherits " 2030"from the tables defined in <varname>tiger</varname> schema so that its " 2031"sufficient to just query those tables to access all the data and drop a set " 2032"of state tables at any time using the <xref linkend=" 2033"\"Drop_State_Tables_Generate_Script\"/> if you need to reload a state or " 2034"just don't need a state anymore." 2035msgstr "" 2036 2037#. Tag: para 2038#: installation.xml:933 2039#, no-c-format 2040msgid "In order to be able to load data you'll need the following tools:" 2041msgstr "" 2042 2043#. Tag: para 2044#: installation.xml:935 2045#, no-c-format 2046msgid "A tool to unzip the zip files from census website." 2047msgstr "" 2048 2049#. Tag: para 2050#: installation.xml:936 2051#, no-c-format 2052msgid "" 2053"For Unix like systems: <varname>unzip</varname> executable which is usually " 2054"already installed on most Unix like platforms." 2055msgstr "" 2056 2057#. Tag: para 2058#: installation.xml:937 2059#, no-c-format 2060msgid "" 2061"For Windows, 7-zip which is a free compress/uncompress tool you can download " 2062"from <ulink url=\"http://www.7-zip.org/\">http://www.7-zip.org/</ulink>" 2063msgstr "" 2064 2065#. Tag: para 2066#: installation.xml:939 2067#, no-c-format 2068msgid "" 2069"<filename>shp2pgsql</filename> commandline which is installed by default " 2070"when you install PostGIS." 2071msgstr "" 2072 2073#. Tag: para 2074#: installation.xml:940 2075#, no-c-format 2076msgid "" 2077"<filename>wget</filename> which is a web grabber tool usually installed on " 2078"most Unix/Linux systems." 2079msgstr "" 2080 2081#. Tag: para 2082#: installation.xml:941 2083#, no-c-format 2084msgid "" 2085"If you are on windows, you can get pre-compiled binaries from <ulink url=" 2086"\"http://gnuwin32.sourceforge.net/packages/wget.htm\">http://gnuwin32." 2087"sourceforge.net/packages/wget.htm</ulink>" 2088msgstr "" 2089 2090#. Tag: para 2091#: installation.xml:944 2092#, no-c-format 2093msgid "" 2094"If you are upgrading from tiger_2010, you'll need to first generate and run " 2095"<xref linkend=\"Drop_Nation_Tables_Generate_Script\"/>. Before you load any " 2096"state data, you need to load the nation wide data which you do with <xref " 2097"linkend=\"Loader_Generate_Nation_Script\"/>. Which will generate a loader " 2098"script for you. <xref linkend=\"Loader_Generate_Nation_Script\"/> is a one-" 2099"time step that should be done for upgrading (from 2010) and for new installs." 2100msgstr "" 2101 2102#. Tag: para 2103#: installation.xml:946 2104#, no-c-format 2105msgid "" 2106"To load state data refer to <xref linkend=\"Loader_Generate_Script\"/> to " 2107"generate a data load script for your platform for the states you desire. " 2108"Note that you can install these piecemeal. You don't have to load all the " 2109"states you want all at once. You can load them as you need them." 2110msgstr "" 2111 2112#. Tag: para 2113#: installation.xml:949 2114#, no-c-format 2115msgid "" 2116"After the states you desire have been loaded, make sure to run the: " 2117"<programlisting>SELECT install_missing_indexes();</programlisting> as " 2118"described in <xref linkend=\"Install_Missing_Indexes\"/>." 2119msgstr "" 2120 2121#. Tag: para 2122#: installation.xml:951 2123#, no-c-format 2124msgid "" 2125"To test that things are working as they should, try to run a geocode on an " 2126"address in your state using <xref linkend=\"Geocode\"/>" 2127msgstr "" 2128 2129#. Tag: title 2130#: installation.xml:954 2131#, no-c-format 2132msgid "Upgrading your Tiger Geocoder Install" 2133msgstr "" 2134 2135#. Tag: para 2136#: installation.xml:955 2137#, no-c-format 2138msgid "" 2139"If you have Tiger Geocoder packaged with 2.0+ already installed, you can " 2140"upgrade the functions at any time even from an interim tar ball if there are " 2141"fixes you badly need. This will only work for Tiger geocoder not installed " 2142"with extensions." 2143msgstr "" 2144 2145#. Tag: command 2146#: installation.xml:968 2147#, no-c-format 2148msgid "cd postgis-&last_release_version;/extras/tiger_geocoder/tiger_2011" 2149msgstr "" 2150 2151#. Tag: para 2152#: installation.xml:971 2153#, no-c-format 2154msgid "" 2155"Locate the <filename>upgrade_geocoder.bat</filename> script If you are on " 2156"windows or the <filename>upgrade_geocoder.sh</filename> if you are on Linux/" 2157"Unix/Mac OSX. Edit the file to have your postgis database credentials." 2158msgstr "" 2159 2160#. Tag: para 2161#: installation.xml:974 2162#, no-c-format 2163msgid "" 2164"If you are upgrading from 2010 or 2011, make sure to unremark out the loader " 2165"script line so you get the latest script for loading 2012 data." 2166msgstr "" 2167 2168#. Tag: para 2169#: installation.xml:975 2170#, no-c-format 2171msgid "Then run th corresponding script from the commandline." 2172msgstr "" 2173 2174#. Tag: para 2175#: installation.xml:979 2176#, no-c-format 2177msgid "" 2178"Next drop all nation tables and load up the new ones. Generate a drop script " 2179"with this SQL statement as detailed in <xref linkend=" 2180"\"Drop_Nation_Tables_Generate_Script\"/>" 2181msgstr "" 2182 2183#. Tag: programlisting 2184#: installation.xml:980 2185#, no-c-format 2186msgid "SELECT drop_nation_tables_generate_script();" 2187msgstr "" 2188 2189#. Tag: para 2190#: installation.xml:981 2191#, no-c-format 2192msgid "Run the generated drop SQL statements." 2193msgstr "" 2194 2195#. Tag: para 2196#: installation.xml:982 2197#, no-c-format 2198msgid "" 2199"Generate a nation load script with this SELECT statement as detailed in " 2200"<xref linkend=\"Loader_Generate_Nation_Script\"/>" 2201msgstr "" 2202 2203#. Tag: emphasis 2204#: installation.xml:983 2205#, no-c-format 2206msgid "For windows" 2207msgstr "" 2208 2209#. Tag: programlisting 2210#: installation.xml:984 2211#, no-c-format 2212msgid "SELECT loader_generate_nation_script('windows');" 2213msgstr "" 2214 2215#. Tag: emphasis 2216#: installation.xml:985 2217#, no-c-format 2218msgid "For unix/linux" 2219msgstr "" 2220 2221#. Tag: programlisting 2222#: installation.xml:986 2223#, no-c-format 2224msgid "SELECT loader_generate_nation_script('sh');" 2225msgstr "" 2226 2227#. Tag: para 2228#: installation.xml:987 2229#, no-c-format 2230msgid "" 2231"Refer to <xref linkend=\"tiger_geocoder_loading_data\"/> for instructions on " 2232"how to run the generate script. This only needs to be done once." 2233msgstr "" 2234 2235#. Tag: para 2236#: installation.xml:988 2237#, no-c-format 2238msgid "" 2239"You can have a mix of 2010/2011 state tables and can upgrade each state " 2240"separately. Before you upgrade a state to 2011, you first need to drop the " 2241"2010 tables for that state using <xref linkend=" 2242"\"Drop_State_Tables_Generate_Script\"/>." 2243msgstr "" 2244 2245#. Tag: title 2246#: installation.xml:995 2247#, no-c-format 2248msgid "Common Problems during installation" 2249msgstr "" 2250 2251#. Tag: para 2252#: installation.xml:996 2253#, no-c-format 2254msgid "" 2255"There are several things to check when your installation or upgrade doesn't " 2256"go as you expected." 2257msgstr "" 2258 2259#. Tag: para 2260#: installation.xml:1003 2261#, no-c-format 2262msgid "" 2263"Check that you have installed PostgreSQL &min_postgres_version; or newer, " 2264"and that you are compiling against the same version of the PostgreSQL source " 2265"as the version of PostgreSQL that is running. Mix-ups can occur when your " 2266"(Linux) distribution has already installed PostgreSQL, or you have otherwise " 2267"installed PostgreSQL before and forgotten about it. PostGIS will only work " 2268"with PostgreSQL &min_postgres_version; or newer, and strange, unexpected " 2269"error messages will result if you use an older version. To check the version " 2270"of PostgreSQL which is running, connect to the database using psql and run " 2271"this query:" 2272msgstr "" 2273 2274#. Tag: programlisting 2275#: installation.xml:1016 2276#, no-c-format 2277msgid "SELECT version();" 2278msgstr "" 2279 2280#. Tag: para 2281#: installation.xml:1018 2282#, no-c-format 2283msgid "" 2284"If you are running an RPM based distribution, you can check for the " 2285"existence of pre-installed packages using the <command>rpm</command> command " 2286"as follows: <command>rpm -qa | grep postgresql</command>" 2287msgstr "" 2288 2289#. Tag: para 2290#: installation.xml:1026 2291#, no-c-format 2292msgid "" 2293"If your upgrade fails, make sure you are restoring into a database that " 2294"already has PostGIS installed." 2295msgstr "" 2296 2297#. Tag: programlisting 2298#: installation.xml:1027 2299#, no-c-format 2300msgid "SELECT postgis_full_version();" 2301msgstr "" 2302 2303#. Tag: para 2304#: installation.xml:1031 2305#, no-c-format 2306msgid "" 2307"Also check that configure has correctly detected the location and version of " 2308"PostgreSQL, the Proj library and the GEOS library." 2309msgstr "" 2310 2311#. Tag: para 2312#: installation.xml:1038 2313#, no-c-format 2314msgid "" 2315"The output from configure is used to generate the <filename>postgis_config." 2316"h</filename> file. Check that the <varname>POSTGIS_PGSQL_VERSION</varname>, " 2317"<varname>POSTGIS_PROJ_VERSION</varname> and <varname>POSTGIS_GEOS_VERSION</" 2318"varname> variables have been set correctly." 2319msgstr "" 2320