1# SOME DESCRIPTIVE TITLE. 2# 3# Translators: 4# pvernier <admin@datamadre.com>, 2013 5# David Martinez Morata, 2013 6# David Martinez Morata, 2013 7# nramire1 nramire1, 2017 8# pvernier <admin@datamadre.com>, 2013 9msgid "" 10msgstr "" 11"Project-Id-Version: PostGIS\n" 12"Report-Msgid-Bugs-To: http://bugs.kde.org\n" 13"POT-Creation-Date: 2018-09-16 15:38+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: Spanish (http://www.transifex.com/postgis/postgis/language/" 17"es/)\n" 18"Language: es\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 "Instalación de PostGIS" 29 30#. Tag: para 31#: installation.xml:5 32#, no-c-format 33msgid "This chapter details the steps required to install PostGIS." 34msgstr "" 35"En este capítulo se detallan los pasos necesarios para instalar PostGIS ." 36 37#. Tag: title 38#: installation.xml:10 39#, no-c-format 40msgid "Short Version" 41msgstr "Versión corta" 42 43#. Tag: para 44#: installation.xml:11 45#, no-c-format 46msgid "To compile assuming you have all the dependencies in your search path:" 47msgstr "" 48 49#. Tag: programlisting 50#: installation.xml:12 51#, no-c-format 52msgid "" 53"tar xvfz postgis-&last_release_version;.tar.gz\n" 54"cd postgis-&last_release_version;\n" 55"./configure\n" 56"make\n" 57"make install" 58msgstr "" 59"tar xvfz postgis-&last_release_version;.tar.gz\n" 60"cd postgis-&last_release_version;\n" 61"./configure\n" 62"make\n" 63"make install" 64 65#. Tag: para 66#: installation.xml:13 67#, no-c-format 68msgid "" 69"Once postgis is installed, it needs to be enabled in each individual " 70"database you want to use it in." 71msgstr "" 72 73#. Tag: para 74#: installation.xml:14 75#, no-c-format 76msgid "" 77"The raster support is currently optional, but installed by default. For " 78"enabling using the PostgreSQL 9.1+ extensions model raster is required. " 79"Using the extension enable process is preferred and more user-friendly. To " 80"spatially enable your database:" 81msgstr "" 82 83#. Tag: programlisting 84#: installation.xml:15 85#, no-c-format 86msgid "" 87"psql -d yourdatabase -c \"CREATE EXTENSION postgis;\"\n" 88"psql -d yourdatabase -c \"CREATE EXTENSION postgis_topology;\"\n" 89"-- if you built with sfcgal support --\n" 90"psql -d yourdatabase -c \"CREATE EXTENSION postgis_sfcgal;\"\n" 91"\n" 92"-- if you want to install tiger geocoder --\n" 93"psql -d yourdatabase -c \"CREATE EXTENSION fuzzystrmatch\"\n" 94"psql -d yourdatabase -c \"CREATE EXTENSION postgis_tiger_geocoder;\"\n" 95"\n" 96"-- if you installed with pcre\n" 97"-- you should have address standardizer extension as well\n" 98"psql -d yourdatabase -c \"CREATE EXTENSION address_standardizer;\"" 99msgstr "" 100"psql -d yourdatabase -c \"CREATE EXTENSION postgis;\"\n" 101"psql -d yourdatabase -c \"CREATE EXTENSION postgis_topology;\"\n" 102"-- if you built with sfcgal support --\n" 103"psql -d yourdatabase -c \"CREATE EXTENSION postgis_sfcgal;\"\n" 104"\n" 105"-- if you want to install tiger geocoder --\n" 106"psql -d yourdatabase -c \"CREATE EXTENSION fuzzystrmatch\"\n" 107"psql -d yourdatabase -c \"CREATE EXTENSION postgis_tiger_geocoder;\"\n" 108"\n" 109"-- if you installed with pcre\n" 110"-- you should have address standardizer extension as well\n" 111"psql -d yourdatabase -c \"CREATE EXTENSION address_standardizer;\"" 112 113#. Tag: para 114#: installation.xml:18 115#, no-c-format 116msgid "" 117"Please refer to <xref linkend=\"make_install_postgis_extensions\"/> for more " 118"details about querying installed/available extensions and upgrading " 119"extensions, or switching from a non-extension install to an extension " 120"install." 121msgstr "" 122 123#. Tag: para 124#: installation.xml:20 125#, no-c-format 126msgid "" 127"For those running who decided for some reason not to compile with raster " 128"support, or just are old-fashioned, here are longer more painful " 129"instructions for you:" 130msgstr "" 131 132#. Tag: para 133#: installation.xml:21 134#, no-c-format 135msgid "" 136"All the .sql files once installed will be installed in share/contrib/postgis-" 137"&last_minor_version; folder of your PostgreSQL install" 138msgstr "" 139 140#. Tag: programlisting 141#: installation.xml:24 142#, no-c-format 143msgid "" 144"createdb yourdatabase\n" 145"createlang plpgsql yourdatabase\n" 146"psql -d yourdatabase -f postgis.sql\n" 147"psql -d yourdatabase -f postgis_comments.sql\n" 148"psql -d yourdatabase -f spatial_ref_sys.sql\n" 149"psql -d yourdatabase -f topology.sql\n" 150"psql -d yourdatabase -f topology_comments.sql\n" 151"\n" 152"-- only if you compiled with raster (GDAL)\n" 153"psql -d yourdatabase -f rtpostgis.sql\n" 154"psql -d yourdatabase -f raster_comments.sql\n" 155"\n" 156"--if you built with sfcgal support --\n" 157"psql -d yourdatabase -f sfcgal.sql\n" 158"psql -d yourdatabase -f sfcgal_comments.sql" 159msgstr "" 160"createdb yourdatabase\n" 161"createlang plpgsql yourdatabase\n" 162"psql -d yourdatabase -f postgis.sql\n" 163"psql -d yourdatabase -f postgis_comments.sql\n" 164"psql -d yourdatabase -f spatial_ref_sys.sql\n" 165"psql -d yourdatabase -f topology.sql\n" 166"psql -d yourdatabase -f topology_comments.sql\n" 167"\n" 168"-- only if you compiled with raster (GDAL)\n" 169"psql -d yourdatabase -f rtpostgis.sql\n" 170"psql -d yourdatabase -f raster_comments.sql\n" 171"\n" 172"--if you built with sfcgal support --\n" 173"psql -d yourdatabase -f sfcgal.sql\n" 174"psql -d yourdatabase -f sfcgal_comments.sql" 175 176#. Tag: para 177#: installation.xml:26 178#, no-c-format 179msgid "" 180"The rest of this chapter goes into detail each of the above installation " 181"steps." 182msgstr "" 183"El resto del capitulo entra en los detalles de cada uno de los pasos de " 184"instalación anteriores." 185 186#. Tag: para 187#: installation.xml:31 188#, no-c-format 189msgid "" 190"As of PostGIS 2.1.3, out-of-db rasters and all raster drivers are disabled " 191"by default. In order to re-enable these, you need to set the following " 192"environment variables <varname>POSTGIS_GDAL_ENABLED_DRIVERS</varname> and " 193"<varname>POSTGIS_ENABLE_OUTDB_RASTERS</varname> in the server environment. " 194"For PostGIS 2.2, you can use the more cross-platform approach of setting the " 195"corresponding <xref linkend=\"PostGIS_GUC\"/>." 196msgstr "" 197 198#. Tag: para 199#: installation.xml:34 200#, no-c-format 201msgid "If you want to enable offline raster:" 202msgstr "" 203 204#. Tag: programlisting 205#: installation.xml:35 206#, no-c-format 207msgid "POSTGIS_ENABLE_OUTDB_RASTERS=1" 208msgstr "POSTGIS_ENABLE_OUTDB_RASTERS=1" 209 210#. Tag: para 211#: installation.xml:36 212#, no-c-format 213msgid "Any other setting or no setting at all will disable out of db rasters." 214msgstr "" 215 216#. Tag: para 217#: installation.xml:37 218#, no-c-format 219msgid "" 220"In order to enable all GDAL drivers available in your GDAL install, set this " 221"environment variable as follows" 222msgstr "" 223 224#. Tag: programlisting 225#: installation.xml:38 226#, no-c-format 227msgid "POSTGIS_GDAL_ENABLED_DRIVERS=ENABLE_ALL" 228msgstr "POSTGIS_GDAL_ENABLED_DRIVERS=ENABLE_ALL" 229 230#. Tag: para 231#: installation.xml:39 232#, no-c-format 233msgid "" 234"If you want to only enable specific drivers, set your environment variable " 235"as follows:" 236msgstr "" 237 238#. Tag: programlisting 239#: installation.xml:40 240#, no-c-format 241msgid "POSTGIS_GDAL_ENABLED_DRIVERS=\"GTiff PNG JPEG GIF XYZ\"" 242msgstr "POSTGIS_GDAL_ENABLED_DRIVERS=\"GTiff PNG JPEG GIF XYZ\"" 243 244#. Tag: para 245#: installation.xml:42 246#, no-c-format 247msgid "If you are on windows, do not quote the driver list" 248msgstr "" 249 250#. Tag: para 251#: installation.xml:44 252#, no-c-format 253msgid "" 254"Setting environment variables varies depending on OS. For PostgreSQL " 255"installed on Ubuntu or Debian via apt-postgresql, the preferred way is to " 256"edit <filename>/etc/postgresql/<replaceable>10</replaceable>/" 257"<replaceable>main</replaceable>/environment</filename> where 9.3 refers to " 258"version of PostgreSQL and main refers to the cluster." 259msgstr "" 260 261#. Tag: para 262#: installation.xml:47 263#, no-c-format 264msgid "" 265"On windows, if you are running as a service, you can set via System " 266"variables which for Windows 7 you can get to by right-clicking on Computer-" 267">Properties Advanced System Settings or in explorer navigating to " 268"<varname>Control Panel\\All Control Panel Items\\System</varname>. Then " 269"clicking <emphasis>Advanced System Settings ->Advanced->Environment " 270"Variables</emphasis> and adding new system variables." 271msgstr "" 272 273#. Tag: para 274#: installation.xml:49 275#, no-c-format 276msgid "" 277"After you set the environment variables, you'll need to restart your " 278"PostgreSQL service for the changes to take effect." 279msgstr "" 280 281#. Tag: title 282#: installation.xml:53 283#, no-c-format 284msgid "Install Requirements" 285msgstr "" 286 287#. Tag: para 288#: installation.xml:55 289#, no-c-format 290msgid "PostGIS has the following requirements for building and usage:" 291msgstr "PostGIS tiene los siguientes requisitos para compilarlo y usarlo:" 292 293#. Tag: emphasis 294#: installation.xml:60 295#, no-c-format 296msgid "Required" 297msgstr "Requerido" 298 299#. Tag: para 300#: installation.xml:65 301#, no-c-format 302msgid "" 303"PostgreSQL &min_postgres_version; or higher. A complete installation of " 304"PostgreSQL (including server headers) is required. PostgreSQL is available " 305"from <ulink url=\"http://www.postgresql.org\"> http://www.postgresql.org </" 306"ulink> ." 307msgstr "" 308"PostgreSQL &min_postgres_version; o superior. Una instalación completa de " 309"PostgreSQL (incluyendo las cabeceras del servidor) es necesaria. PostgreSQL " 310"esta disponible en <ulink url=\"http://www.postgresql.org\"> http://www." 311"postgresql.org </ulink> ." 312 313#. Tag: para 314#: installation.xml:74 315#, no-c-format 316msgid "" 317"For a full PostgreSQL / PostGIS support matrix and PostGIS/GEOS support " 318"matrix refer to <ulink url=\"http://trac.osgeo.org/postgis/wiki/" 319"UsersWikiPostgreSQLPostGIS\">http://trac.osgeo.org/postgis/wiki/" 320"UsersWikiPostgreSQLPostGIS</ulink>" 321msgstr "" 322"Para conocer las compatibilidades entre versiones de PostgreSQL/PostGIS y " 323"PostGIS/GEOS puede ver una matriz de compatibilidades en <ulink url=\"http://" 324"trac.osgeo.org/postgis/wiki/UsersWikiPostgreSQLPostGIS\">http://trac.osgeo." 325"org/postgis/wiki/UsersWikiPostgreSQLPostGIS</ulink>" 326 327#. Tag: para 328#: installation.xml:80 329#, no-c-format 330msgid "" 331"GNU C compiler (<filename>gcc</filename>). Some other ANSI C compilers can " 332"be used to compile PostGIS, but we find far fewer problems when compiling " 333"with <filename>gcc</filename>." 334msgstr "" 335"compilador GNU C (<filename>gcc</filename>). Otros compiladores ANSI C " 336"pueden utilizarse para compilar PostGIS, pero encontraremos menos problemas " 337"al compilar con <filename>gcc</filename>." 338 339#. Tag: para 340#: installation.xml:88 341#, no-c-format 342msgid "" 343"GNU Make (<filename>gmake</filename> or <filename>make</filename>). For many " 344"systems, GNU <filename>make</filename> is the default version of make. Check " 345"the version by invoking <filename>make -v</filename>. Other versions of " 346"<filename>make</filename> may not process the PostGIS <filename>Makefile</" 347"filename> properly." 348msgstr "" 349"GNU Make (<filename>gmake</filename> or <filename>make</filename>). Para " 350"muchos sistemas , GNU <filename>make</filename> es la versión por defecto de " 351"make. Para verificar la versión de make podemos ejecutar el siguiente " 352"comando <filename>make -v</filename>. Otras versiones de <filename>make</" 353"filename> pueden no procesar el fichero PostGIS <filename>Makefile</" 354"filename> de forma correcta." 355 356#. Tag: para 357#: installation.xml:98 358#, no-c-format 359msgid "" 360"Proj4 reprojection library, version 4.9.0 or greater. Proj4 4.9 or above is " 361"needed to take advantage of improved geodetic. The Proj4 library is used to " 362"provide coordinate reprojection support within PostGIS. Proj4 is available " 363"for download from <ulink url=\"http://trac.osgeo.org/proj/\"> http://trac." 364"osgeo.org/proj/ </ulink> ." 365msgstr "" 366 367#. Tag: para 368#: installation.xml:110 369#, no-c-format 370msgid "" 371"GEOS geometry library, version 3.5 or greater, but GEOS 3.7+ is recommended " 372"to take full advantage of all the new functions and features. You should " 373"have at least GEOS 3.5, without which you will be missing some major " 374"enhancements such as <xref linkend=\"ST_ClipByBox2D\"/> and <xref linkend=" 375"\"ST_Subdivide\"/>. GEOS is available for download from <ulink url=\"http://" 376"trac.osgeo.org/geos/\"> http://trac.osgeo.org/geos/ </ulink> and 3.5+ is " 377"backward-compatible with older versions so fairly safe to upgrade." 378msgstr "" 379 380#. Tag: para 381#: installation.xml:119 382#, no-c-format 383msgid "" 384"LibXML2, version 2.5.x or higher. LibXML2 is currently used in some imports " 385"functions (ST_GeomFromGML and ST_GeomFromKML). LibXML2 is available for " 386"download from <ulink url=\"http://xmlsoft.org/downloads.html\">http://" 387"xmlsoft.org/downloads.html</ulink>." 388msgstr "" 389"LibXML2, versión 2.5.x o superior. LibXML2 se usa actualmente en alguna " 390"funciones para importar (ST_GeomFromGML y ST_GeomFromKML). LibXML2 esta " 391"disponible para su descarga en <ulink url=\"http://xmlsoft.org/downloads.html" 392"\">http://xmlsoft.org/downloads.html</ulink>." 393 394#. Tag: para 395#: installation.xml:126 396#, no-c-format 397msgid "" 398"JSON-C, version 0.9 or higher. JSON-C is currently used to import GeoJSON " 399"via the function ST_GeomFromGeoJson. JSON-C is available for download from " 400"<ulink url=\"https://github.com/json-c/json-c/releases\">https://github.com/" 401"json-c/json-c/releases/</ulink>." 402msgstr "" 403 404#. Tag: para 405#: installation.xml:134 406#, no-c-format 407msgid "" 408"GDAL, version 1.8 or higher (1.9 or higher is strongly recommended since " 409"some things will not work well or behavior differently with lower versions). " 410"This is required for raster support and to be able to install with " 411"<code>CREATE EXTENSION postgis</code> so highly recommended for those " 412"running 9.1+. <ulink url=\"http://trac.osgeo.org/gdal/wiki/DownloadSource" 413"\">http://trac.osgeo.org/gdal/wiki/DownloadSource</ulink>." 414msgstr "" 415 416#. Tag: para 417#: installation.xml:141 418#, fuzzy, no-c-format 419msgid "" 420"If compiling with PostgreSQL+JIT, LLVM version >=6 is required <ulink url=" 421"\"https://trac.osgeo.org/postgis/ticket/4125\">https://trac.osgeo.org/" 422"postgis/ticket/4125</ulink>." 423msgstr "" 424"Este parámetro está roto actualmente, ya que el paquete sólo se instalará en " 425"el directorio de instalación de PostgreSQL. Para seguir avence de este bug " 426"visita <ulink url=\"http://trac.osgeo.org/postgis/ticket/635\"> http://trac." 427"osgeo.org/postgis/ticket/635 </ulink>" 428 429#. Tag: emphasis 430#: installation.xml:149 431#, no-c-format 432msgid "Optional" 433msgstr "Opcional" 434 435#. Tag: para 436#: installation.xml:154 437#, no-c-format 438msgid "" 439"GDAL (pseudo optional) only if you don't want raster and don't care about " 440"installing with <code>CREATE EXTENSION postgis</code> can you leave it out. " 441"Keep in mind other extensions may have a requires postgis extension which " 442"will prevent you from installing them unless you install postgis as an " 443"extension. So it is highly recommended you compile with GDAL support." 444msgstr "" 445 446#. Tag: para 447#: installation.xml:158 448#, no-c-format 449msgid "" 450"Also make sure to enable the drivers you want to use as described in <xref " 451"linkend=\"install_short_version\"/>." 452msgstr "" 453 454#. Tag: para 455#: installation.xml:161 456#, no-c-format 457msgid "" 458"GTK (requires GTK+2.0, 2.8+) to compile the shp2pgsql-gui shape file loader. " 459"<ulink url=\"http://www.gtk.org/\"> http://www.gtk.org/ </ulink> ." 460msgstr "" 461"GTK (GTK+2.0, 2.8+ requerida) para compilar el cargador de shapefiles " 462"shp2pgsql-gui. <ulink url=\"http://www.gtk.org/\"> http://www.gtk.org/ </" 463"ulink> ." 464 465#. Tag: para 466#: installation.xml:171 467#, no-c-format 468msgid "" 469"SFCGAL, version 1.1 (or higher) could be used to provide additional 2D and " 470"3D advanced analysis functions to PostGIS cf <xref linkend=\"reference_sfcgal" 471"\"/>. And also allow to use SFCGAL rather than GEOS for some 2D functions " 472"provided by both backends (like ST_Intersection or ST_Area, for instance). A " 473"PostgreSQL configuration variable <code>postgis.backend</code> allow end " 474"user to control which backend he want to use if SFCGAL is installed (GEOS by " 475"default). Nota: SFCGAL 1.2 require at least CGAL 4.3 and Boost 1.54 (cf: " 476"<ulink url=\"http://oslandia.github.io/SFCGAL/installation.html\">http://" 477"oslandia.github.io/SFCGAL/installation.html</ulink>) <ulink url=\"https://" 478"github.com/Oslandia/SFCGAL\">https://github.com/Oslandia/SFCGAL</ulink>." 479msgstr "" 480 481#. Tag: para 482#: installation.xml:179 483#, no-c-format 484msgid "" 485"In order to build the <xref linkend=\"Address_Standardizer\"/> you will also " 486"need PCRE <ulink url=\"http://www.pcre.org\">http://www.pcre.org</ulink> " 487"(which generally is already installed on nix systems). <code>Regex::" 488"Assemble</code> perl CPAN package is only needed if you want to rebuild the " 489"data encoded in <filename>parseaddress-stcities.h</filename>. <xref linkend=" 490"\"Address_Standardizer\"/> will automatically be built if it detects a PCRE " 491"library, or you pass in a valid <varname>--with-pcre-dir=/path/to/pcre</" 492"varname> during configure." 493msgstr "" 494 495#. Tag: para 496#: installation.xml:186 497#, no-c-format 498msgid "" 499"To enable ST_AsMVT protobuf-c library (for usage) and the protoc-c compiler " 500"(for building) are required. Also, pkg-config is required to verify the " 501"correct minimum version of protobuf-c. See <ulink url=\"https://github.com/" 502"protobuf-c/protobuf-c\">protobuf-c</ulink>." 503msgstr "" 504 505#. Tag: para 506#: installation.xml:194 507#, no-c-format 508msgid "" 509"CUnit (<filename>CUnit</filename>). This is needed for regression testing. " 510"<ulink url=\"http://cunit.sourceforge.net/\">http://cunit.sourceforge.net/</" 511"ulink>" 512msgstr "" 513"CUnit (<filename>CUnit</filename>). Se necesita para hacer test de " 514"regresión. <ulink url=\"http://cunit.sourceforge.net/\">http://cunit." 515"sourceforge.net/</ulink>" 516 517#. Tag: para 518#: installation.xml:200 519#, no-c-format 520msgid "" 521"DocBook (<filename>xsltproc</filename>) is required for building the " 522"documentation. Docbook is available from <ulink url=\"http://www.docbook.org/" 523"\"> http://www.docbook.org/ </ulink> ." 524msgstr "" 525"DocBook (<filename>xsltproc</filename>) es necesario para compilar la " 526"documentación. Docbook esta disponible en <ulink url=\"http://www.docbook." 527"org/\"> http://www.docbook.org/ </ulink> ." 528 529#. Tag: para 530#: installation.xml:211 531#, no-c-format 532msgid "" 533"DBLatex (<filename>dblatex</filename>) is required for building the " 534"documentation in PDF format. DBLatex is available from <ulink url=\"http://" 535"dblatex.sourceforge.net/\"> http://dblatex.sourceforge.net/ </ulink> ." 536msgstr "" 537"DBLatex (<filename>dblatex</filename>) necesario para construir la " 538"documentación en formato PDF. DBLatex esta disponible en <ulink url=\"http://" 539"dblatex.sourceforge.net/\"> http://dblatex.sourceforge.net/ </ulink> ." 540 541#. Tag: para 542#: installation.xml:222 543#, no-c-format 544msgid "" 545"ImageMagick (<filename>convert</filename>) is required to generate the " 546"images used in the documentation. ImageMagick is available from <ulink url=" 547"\"http://www.imagemagick.org/\"> http://www.imagemagick.org/ </ulink> ." 548msgstr "" 549"ImageMagick (<filename>convert</filename>) es necesario para generar las " 550"imágenes empleadas en la documentación. ImageMagick esta disponible en<ulink " 551"url=\"http://www.imagemagick.org/\"> http://www.imagemagick.org/ </ulink> ." 552 553#. Tag: title 554#: installation.xml:235 555#, no-c-format 556msgid "Getting the Source" 557msgstr "Obteniendo el código fuente" 558 559#. Tag: para 560#: installation.xml:237 561#, no-c-format 562msgid "" 563"Retrieve the PostGIS source archive from the downloads website <ulink url=" 564"\"&postgis_download_url;\"> &postgis_download_url; </ulink>" 565msgstr "" 566 567#. Tag: programlisting 568#: installation.xml:244 569#, no-c-format 570msgid "" 571"wget &postgis_download_url;\n" 572"tar -xvzf postgis-&last_release_version;.tar.gz" 573msgstr "" 574 575#. Tag: para 576#: installation.xml:246 577#, no-c-format 578msgid "" 579"This will create a directory called <varname>postgis-&last_release_version;</" 580"varname> in the current working directory." 581msgstr "" 582"Esto creara un directorio llamado <varname>postgis-&last_release_version;</" 583"varname> en el directorio de trabajo actual." 584 585#. Tag: para 586#: installation.xml:252 587#, no-c-format 588msgid "" 589"Alternatively, checkout the source from the <ulink url=\"http://subversion." 590"apache.org/\"> svn </ulink> repository <ulink url=\"http://svn.osgeo.org/" 591"postgis/trunk/\"> http://svn.osgeo.org/postgis/trunk/ </ulink> ." 592msgstr "" 593"De forma alternativa se puede obtener el código fuente del repositorio " 594"<ulink url=\"http://subversion.apache.org/\"> svn </ulink> <ulink url=" 595"\"http://svn.osgeo.org/postgis/trunk/\"> http://svn.osgeo.org/postgis/trunk/ " 596"</ulink> ." 597 598#. Tag: programlisting 599#: installation.xml:264 600#, no-c-format 601msgid "" 602"svn checkout http://svn.osgeo.org/postgis/trunk/ postgis-" 603"&last_release_version;" 604msgstr "" 605"svn checkout http://svn.osgeo.org/postgis/trunk/ postgis-" 606"&last_release_version;" 607 608#. Tag: para 609#: installation.xml:266 610#, no-c-format 611msgid "" 612"Change into the newly created <varname>postgis-&last_release_version;</" 613"varname> directory to continue the installation." 614msgstr "" 615"Vaya al nuevo directorio <varname>postgis-&last_release_version;</varname> " 616"creado para continuar con la instalación." 617 618#. Tag: title 619#: installation.xml:274 620#, no-c-format 621msgid "Compiling and Install from Source: Detailed" 622msgstr "" 623 624#. Tag: para 625#: installation.xml:277 626#, no-c-format 627msgid "" 628"Many OS systems now include pre-built packages for PostgreSQL/PostGIS. In " 629"many cases compilation is only necessary if you want the most bleeding edge " 630"versions or you are a package maintainer." 631msgstr "" 632"Muchos Sistemas Operativos incluyen ya paquetes precompilados PostgreSQL/" 633"PostGIS. En la mayoría de casos no es necesario compilar salvo si quieres " 634"las ultimas versiones o eres alguien que hace mantenimiento de paquetes." 635 636#. Tag: para 637#: installation.xml:282 638#, no-c-format 639msgid "" 640"This section includes general compilation instructions, if you are compiling " 641"for Windows etc or another OS, you may find additional more detailed help at " 642"<ulink url=\"http://trac.osgeo.org/postgis/wiki/UsersWikiInstall\">PostGIS " 643"User contributed compile guides</ulink> and <ulink url=\"http://trac.osgeo." 644"org/postgis/wiki/DevWikiMain\">PostGIS Dev Wiki</ulink>." 645msgstr "" 646"Esta sección incluye las instrucciones generales de compilado, si estas " 647"compilando en Windows o otro Sistema Operativo, puedes encontrar información " 648"adicional detallada en <ulink url=\"http://trac.osgeo.org/postgis/wiki/" 649"UsersWikiInstall\">PostGIS User contributed compile guides</ulink> y <ulink " 650"url=\"http://trac.osgeo.org/postgis/wiki/DevWikiMain\">PostGIS Dev Wiki</" 651"ulink>." 652 653#. Tag: para 654#: installation.xml:284 655#, no-c-format 656msgid "" 657"Pre-Built Packages for various OS are listed in <ulink url=\"http://trac." 658"osgeo.org/postgis/wiki/UsersWikiPackages\">PostGIS Pre-built Packages</ulink>" 659msgstr "" 660"Algunos paquetes precompilados para varios Sistemas Operativos están en " 661"<ulink url=\"http://trac.osgeo.org/postgis/wiki/UsersWikiPackages\">PostGIS " 662"Pre-built Packages</ulink>" 663 664#. Tag: para 665#: installation.xml:285 666#, no-c-format 667msgid "" 668"If you are a windows user, you can get stable builds via Stackbuilder or " 669"<ulink url=\"http://www.postgis.org/download/windows/\">PostGIS Windows " 670"download site</ulink> We also have <ulink url=\"http://www.postgis.org/" 671"download/windows/experimental.php\">very bleeding-edge windows experimental " 672"builds</ulink> that are built usually once or twice a week or whenever " 673"anything exciting happens. You can use these to experiment with the in " 674"progress releases of PostGIS" 675msgstr "" 676"Si eres usuario de Windows, puedes obtener versiones estables compiladas via " 677"Stackbuilder o <ulink url=\"http://www.postgis.org/download/windows/\"> " 678"sitio de descragas de PostGIS para Windows</ulink> También tenemos <ulink " 679"url=\"http://www.postgis.org/download/windows/experimental.php\">versiones " 680"experimentales para Windows </ulink> que son publicadas normalmente una o " 681"dos veces por semana o cuando algo interesante ocurre. Puedes utilizar estas " 682"para experimentar con las versiones de desarrollo de PostGIS" 683 684#. Tag: para 685#: installation.xml:290 686#, no-c-format 687msgid "" 688"The PostGIS module is an extension to the PostgreSQL backend server. As " 689"such, PostGIS &last_release_version; <emphasis>requires</emphasis> full " 690"PostgreSQL server headers access in order to compile. It can be built " 691"against PostgreSQL versions &min_postgres_version; or higher. Earlier " 692"versions of PostgreSQL are <emphasis>not</emphasis> supported." 693msgstr "" 694"El modulo PostGIS es una extensión del servidor PostgreSQL. Como tal, " 695"PostGIS &last_release_version; <emphasis>requiere</emphasis> PostgreSQL con " 696"acceso completo cabeceras del servidor con el fin de compilar. Puede ser " 697"compilado en PostgreSQL versiones &min_postgres_version;, o superior. Las " 698"versiones anteriores de PostgreSQL <emphasis>no</emphasis> son compatibles." 699 700#. Tag: para 701#: installation.xml:298 702#, no-c-format 703msgid "" 704"Refer to the PostgreSQL installation guides if you haven't already installed " 705"PostgreSQL. <ulink url=\"http://www.postgresql.org\"> http://www.postgresql." 706"org </ulink> ." 707msgstr "" 708"Si todavía no tienes instalado PostgreSQL puedes ir a la guía de instalación " 709"de PostgreSQL en <ulink url=\"http://www.postgresql.org\"> http://www." 710"postgresql.org </ulink> ." 711 712#. Tag: para 713#: installation.xml:308 714#, no-c-format 715msgid "" 716"For GEOS functionality, when you install PostgresSQL you may need to " 717"explicitly link PostgreSQL against the standard C++ library:" 718msgstr "" 719"Para tener compatibilidad con las funcionalidades GEOS, cuando instales " 720"PostgreSQL necesitar hacer un enlace explícito de PostgreSQL con la librería " 721"estándar C++:" 722 723#. Tag: programlisting 724#: installation.xml:313 725#, no-c-format 726msgid "LDFLAGS=-lstdc++ ./configure [YOUR OPTIONS HERE]" 727msgstr "LDFLAGS=-lstdc++ ./configure [PON TUS OPCIONES AQUI]" 728 729#. Tag: para 730#: installation.xml:315 731#, no-c-format 732msgid "" 733"This is a workaround for bogus C++ exceptions interaction with older " 734"development tools. If you experience weird problems (backend unexpectedly " 735"closed or similar things) try this trick. This will require recompiling your " 736"PostgreSQL from scratch, of course." 737msgstr "" 738"Esta es una falsa solución para excepciones de interacción de C++ con " 739"herramientas de desarrollo antiguas. Si experimentas problemas extraños " 740"(backend cerrado inesperadamente o cosas similares) prueba este truco. Para " 741"ello será necesario volver a compilar PostgreSQL desde cero, por supuesto." 742 743#. Tag: para 744#: installation.xml:323 745#, no-c-format 746msgid "" 747"The following steps outline the configuration and compilation of the PostGIS " 748"source. They are written for Linux users and will not work on Windows or Mac." 749msgstr "" 750"Los siguientes pasos describen la configuración y compilación del código " 751"fuente de PostGIS. Están escritas para usuarios Linux y no funcionaran con " 752"Windows o Mac." 753 754#. Tag: title 755#: installation.xml:330 756#, no-c-format 757msgid "Configuration" 758msgstr "Configuración" 759 760#. Tag: para 761#: installation.xml:332 762#, no-c-format 763msgid "" 764"As with most linux installations, the first step is to generate the Makefile " 765"that will be used to build the source code. This is done by running the " 766"shell script" 767msgstr "" 768"Como en la gran mayoría de instalaciones Linux, el primer paso es generar el " 769"Makefile que se utilizara para compilar el código fuente. Esto se hace " 770"ejecutando el script de shell." 771 772#. Tag: para 773#: installation.xml:342 774#, no-c-format 775msgid "" 776"With no additional parameters, this command will attempt to automatically " 777"locate the required components and libraries needed to build the PostGIS " 778"source code on your system. Although this is the most common usage of " 779"<command>./configure</command>, the script accepts several parameters for " 780"those who have the required libraries and programs in non-standard locations." 781msgstr "" 782"Sin parámetros adicionales, este comando intentara localizar los componentes " 783"y librerías necesarios para construir el código fuente PostGIS de forma " 784"automática en tu sistema. Aunque este es el uso mas común de <command>./" 785"configure</command>, el script acepta varios parámetros para aquellos que " 786"han instalado las librerías y programas en lugares no standard." 787 788#. Tag: para 789#: installation.xml:351 790#, no-c-format 791msgid "" 792"The following list shows only the most commonly used parameters. For a " 793"complete list, use the <command>--help</command> or <command>--help=short</" 794"command> parameters." 795msgstr "" 796"La siguiente lista muestra los parámetros utilizados mas comunes. Para " 797"obtener una lista completa, puedes utilizar los parámetros <command>--help</" 798"command> o <command>--help=short</command>." 799 800#. Tag: para 801#: installation.xml:361 802#, no-c-format 803msgid "" 804"This is the location the PostGIS libraries and SQL scripts will be installed " 805"to. By default, this location is the same as the detected PostgreSQL " 806"installation." 807msgstr "" 808"Esta es la localización donde se instalaran las librerías PostGIS y los " 809"scripts SQL. Por defecto, esta localización es la misma que la detectada " 810"para la instalación PostgreSQL." 811 812#. Tag: para 813#: installation.xml:368 814#, no-c-format 815msgid "" 816"This parameter is currently broken, as the package will only install into " 817"the PostgreSQL installation directory. Visit <ulink url=\"http://trac.osgeo." 818"org/postgis/ticket/635\"> http://trac.osgeo.org/postgis/ticket/635 </ulink> " 819"to track this bug." 820msgstr "" 821"Este parámetro está roto actualmente, ya que el paquete sólo se instalará en " 822"el directorio de instalación de PostgreSQL. Para seguir avence de este bug " 823"visita <ulink url=\"http://trac.osgeo.org/postgis/ticket/635\"> http://trac." 824"osgeo.org/postgis/ticket/635 </ulink>" 825 826#. Tag: para 827#: installation.xml:383 828#, no-c-format 829msgid "" 830"PostgreSQL provides a utility called <command>pg_config</command> to enable " 831"extensions like PostGIS to locate the PostgreSQL installation directory. Use " 832"this parameter (<command>--with-pgconfig=/path/to/pg_config</command>) to " 833"manually specify a particular PostgreSQL installation that PostGIS will " 834"build against." 835msgstr "" 836"PostgreSQL tiene una herramienta llamada <command>pg_config</command> para " 837"activar extensiones como PostGIS o para localizar el directorio de " 838"instalación de PostgreSQL. Utiliza este parámetro (<command>--with-pgconfig=/" 839"path/to/pg_config</command>) para especificar una instalación personalizada " 840"de PostgreSQL de forma manual que PostGIS utilizara para compilar. " 841 842#. Tag: para 843#: installation.xml:397 844#, no-c-format 845msgid "" 846"GDAL, a required library, provides functionality needed for raster support " 847"<command>gdal-config</command> to enable software installations to locate " 848"the GDAL installation directory. Use this parameter (<command>--with-" 849"gdalconfig=/path/to/gdal-config</command>) to manually specify a particular " 850"GDAL installation that PostGIS will build against." 851msgstr "" 852"GDAL, una biblioteca necesaria, proporciona la funcionalidad necesaria para " 853"el soporte de raster <command> gdal-config </command> para activar la " 854"instalación de software para localizar el directorio de instalación de GDAL. " 855"Utilice este parámetro (<command> - with-gdalconfig = / ruta /a/ gdal config-" 856"</command>) para especificar manualmente una instalación de GDAL " 857"personalizada que PostGIS utilizara para compilar." 858 859#. Tag: para 860#: installation.xml:411 861#, no-c-format 862msgid "" 863"GEOS, a required geometry library, provides a utility called <command>geos-" 864"config</command> to enable software installations to locate the GEOS " 865"installation directory. Use this parameter (<command>--with-geosconfig=/path/" 866"to/geos-config</command>) to manually specify a particular GEOS installation " 867"that PostGIS will build against." 868msgstr "" 869"GEOS, libreria de geometrías requerida, tiene una utilidad llamada " 870"<command>geos-config</command> para activar la localización del directorio " 871"de instalación del software GEOS. Utiliza este parametro (<command>--with-" 872"geosconfig=/path/to/geos-config</command>) para especificar de forma manual " 873"una instalación personalizada de GEOS que PostGIS puede utilizar para " 874"compilar." 875 876#. Tag: para 877#: installation.xml:425 878#, no-c-format 879msgid "" 880"LibXML is the library required for doing GeomFromKML/GML processes. It " 881"normally is found if you have libxml installed, but if not or you want a " 882"specific version used, you'll need to point PostGIS at a specific " 883"<filename>xml2-config</filename> confi file to enable software installations " 884"to locate the LibXML installation directory. Use this parameter (<command>>--" 885"with-xml2config=/path/to/xml2-config</command>) to manually specify a " 886"particular LibXML installation that PostGIS will build against." 887msgstr "" 888"LibXML es una libreria necesaria para procesar GeomFromKML/GML. Normalmente " 889"encontrara si tienes instalada la libreria libxml, pero si no esta " 890"instalada, o quieres usar una versión especifica, necesitaras que PostGIS " 891"apunte a un fichero de configuración particular <filename>xml2-config</" 892"filename> para localizar un directorio de instalación LibXML para activar la " 893"instalación del Software. Utiliza el siguiente parámetro (<command>>--with-" 894"xml2config=/path/to/xml2-config</command>) para especificar de forma manual " 895"una instalación personalizada de LibXML con la que compilar PostGIS." 896 897#. Tag: para 898#: installation.xml:443 899#, no-c-format 900msgid "" 901"Proj4 is a reprojection library required by PostGIS. Use this parameter " 902"(<command>--with-projdir=/path/to/projdir</command>) to manually specify a " 903"particular Proj4 installation directory that PostGIS will build against." 904msgstr "" 905"Proj4 es una libreria de reproyecciones necesaria de PostGIS. Utiliza el " 906"siguiente parametro (<command>--with-projdir=/path/to/projdir</command>) " 907"para definir manualmente una instalación personalizada de Proj4 para " 908"compilar PostGIS." 909 910#. Tag: para 911#: installation.xml:455 912#, no-c-format 913msgid "Directory where iconv is installed." 914msgstr "Directorio donde iconv esta instalado." 915 916#. Tag: para 917#: installation.xml:464 918#, no-c-format 919msgid "" 920"<ulink url=\"http://oss.metaparadigm.com/json-c/\">JSON-C</ulink> is an MIT-" 921"licensed JSON library required by PostGIS ST_GeomFromJSON support. Use this " 922"parameter (<command>--with-jsondir=/path/to/jsondir</command>) to manually " 923"specify a particular JSON-C installation directory that PostGIS will build " 924"against." 925msgstr "" 926"<ulink url=\"http://oss.metaparadigm.com/json-c/\">JSON-C</ulink>es una " 927"libreria con licencia MIT-licensed JSON necesaria para dar soporte a PostGIS " 928"ST_GeomFromJSON. Utiliza este parametro (<command>--with-jsondir=/path/to/" 929"jsondir</command>) para especificar de forma manual el directorio de " 930"instalación personalizado de instalación de JSON-C que PostGIS utilizara " 931"para compilar." 932 933#. Tag: para 934#: installation.xml:476 935#, no-c-format 936msgid "" 937"<ulink url=\"http://www.pcre.org/\">PCRE</ulink> is an BSD-licensed Perl " 938"Compatible Regular Expression library required by address_standardizer " 939"extension. Use this parameter (<command>--with-pcredir=/path/to/pcredir</" 940"command>) to manually specify a particular PCRE installation directory that " 941"PostGIS will build against." 942msgstr "" 943 944#. Tag: para 945#: installation.xml:488 946#, no-c-format 947msgid "" 948"Compile the data import GUI (requires GTK+2.0). This will create shp2pgsql-" 949"gui graphical interface to shp2pgsql." 950msgstr "" 951"Compilar la GUI de importar datos (necesita GTK+2.0). Esto creara una " 952"interfaz gráfica shp2pgsql-gui para el comando shp2pgsql." 953 954#. Tag: para 955#: installation.xml:497 956#, no-c-format 957msgid "" 958"Compile with raster support. This will build rtpostgis-" 959"&last_release_version; library and rtpostgis.sql file. This may not be " 960"required in final release as plan is to build in raster support by default." 961msgstr "" 962"Compilar con soporte para raster. Esto compilara la libreria rtpostgis-" 963"&last_release_version; y el fichero rtpostgis.sql. Esto puede no ser " 964"necesario en la versión final ya que el plan es dar soporte raster de forma " 965"predeterminada." 966 967#. Tag: para 968#: installation.xml:506 969#, no-c-format 970msgid "" 971"Disable topology support. There is no corresponding library as all logic " 972"needed for topology is in postgis-&last_release_version; library." 973msgstr "" 974 975#. Tag: para 976#: installation.xml:515 977#, no-c-format 978msgid "" 979"By default PostGIS will try to detect gettext support and compile with it, " 980"however if you run into incompatibility issues that cause breakage of " 981"loader, you can disable it entirely with this command. Refer to ticket " 982"<ulink url=\"http://trac.osgeo.org/postgis/ticket/748\">http://trac.osgeo." 983"org/postgis/ticket/748</ulink> for an example issue solved by configuring " 984"with this. NOTE: that you aren't missing much by turning this off. This is " 985"used for international help/label support for the GUI loader which is not " 986"yet documented and still experimental." 987msgstr "" 988"PostGIS intentara detectar soporte gettext y compilar con el por defecto, de " 989"todas formas si existen incompatibilidades que causan errores de carga, se " 990"puede desactivar por completo con este comando. Para ver un ejemplo de " 991"resolución de problemas configurando en gettext puedes ver el siguiente " 992"enlace <ulink url=\"http://trac.osgeo.org/postgis/ticket/748\">http://trac." 993"osgeo.org/postgis/ticket/748</ulink>. NOTA: No te pierdes mucho si " 994"desactivas esta opción. Se utiliza principalmente para soporte de ayuda/" 995"etiquetas internacionales en la GUI de carga, que actualmente no esta " 996"documentada y sigue siendo experimental." 997 998#. Tag: para 999#: installation.xml:526 1000#, no-c-format 1001msgid "" 1002"By default PostGIS will not install with sfcgal support without this switch. " 1003"<varname>PATH</varname> is an optional argument that allows to specify an " 1004"alternate PATH to sfcgal-config." 1005msgstr "" 1006 1007#. Tag: para 1008#: installation.xml:534 1009#, no-c-format 1010msgid "" 1011"If you obtained PostGIS from the SVN <ulink url=\"http://svn.osgeo.org/" 1012"postgis/trunk/\"> repository </ulink> , the first step is really to run the " 1013"script" 1014msgstr "" 1015"Si has obtenido PostGIS desde el <ulink url=\"http://svn.osgeo.org/postgis/" 1016"trunk/\"> repositorio </ulink> SVN, el primer paso es ejecutar el script" 1017 1018#. Tag: para 1019#: installation.xml:546 1020#, no-c-format 1021msgid "" 1022"This script will generate the <command>configure</command> script that in " 1023"turn is used to customize the installation of PostGIS." 1024msgstr "" 1025"Este Script generara el script <command>configure</command> que a su vez se " 1026"utiliza para personalizar la instalación de PostGIS." 1027 1028#. Tag: para 1029#: installation.xml:551 1030#, no-c-format 1031msgid "" 1032"If you instead obtained PostGIS as a tarball, running <command>./autogen.sh</" 1033"command> is not necessary as <command>configure</command> has already been " 1034"generated." 1035msgstr "" 1036"Si, por el contrario, as obtenido PostGIS como tarball, ejecutar <command>./" 1037"autogen.sh</command> no es necesario ya que ya se ha generado " 1038"<command>configure</command>." 1039 1040#. Tag: title 1041#: installation.xml:560 1042#, no-c-format 1043msgid "Building" 1044msgstr "Compilando" 1045 1046#. Tag: para 1047#: installation.xml:562 1048#, no-c-format 1049msgid "" 1050"Once the Makefile has been generated, building PostGIS is as simple as " 1051"running" 1052msgstr "" 1053"Una vez generado el Makefile, compilar PostGIS es tan simple como ejecutar" 1054 1055#. Tag: para 1056#: installation.xml:571 1057#, no-c-format 1058msgid "" 1059"The last line of the output should be \"<code>PostGIS was built " 1060"successfully. Ready to install.</code>\"" 1061msgstr "" 1062"La ultima linea de salida del terminal debe ser \"<code>PostGIS copilado con " 1063"éxito. Listo para instalar.</code>\"" 1064 1065#. Tag: para 1066#: installation.xml:576 1067#, no-c-format 1068msgid "" 1069"As of PostGIS v1.4.0, all the functions have comments generated from the " 1070"documentation. If you wish to install these comments into your spatial " 1071"databases later, run the command which requires docbook. The " 1072"postgis_comments.sql and other package comments files raster_comments.sql, " 1073"topology_comments.sql are also packaged in the tar.gz distribution in the " 1074"doc folder so no need to make comments if installing from the tar ball. " 1075"Comments are also included as part of the CREATE EXTENSION install." 1076msgstr "" 1077 1078#. Tag: command 1079#: installation.xml:586 installation.xml:610 1080#, no-c-format 1081msgid "make comments" 1082msgstr "make comments" 1083 1084#. Tag: para 1085#: installation.xml:589 1086#, no-c-format 1087msgid "" 1088"Introduced in PostGIS 2.0. This generates html cheat sheets suitable for " 1089"quick reference or for student handouts. This requires xsltproc to build and " 1090"will generate 4 files in doc folder <filename>topology_cheatsheet.html</" 1091"filename>, <filename>tiger_geocoder_cheatsheet.html</filename>, " 1092"<filename>raster_cheatsheet.html</filename>, <filename>postgis_cheatsheet." 1093"html</filename>" 1094msgstr "" 1095"Introducido en la version PostGIS 2.0. Esto genera hojas de referencia html " 1096"para una referencia rápida o para los folletos. Esto requiere xsltproc para " 1097"compilar y generará 4 ficheros en la carpeta doc " 1098"<filename>topology_cheatsheet.html</filename>, " 1099"<filename>tiger_geocoder_cheatsheet.html</filename>, " 1100"<filename>raster_cheatsheet.html</filename>, <filename>postgis_cheatsheet." 1101"html</filename>" 1102 1103#. Tag: para 1104#: installation.xml:594 1105#, no-c-format 1106msgid "" 1107"You can download some pre-built ones available in html and pdf from <ulink " 1108"url=\"http://www.postgis.us/study_guides\">PostGIS / PostgreSQL Study " 1109"Guides</ulink>" 1110msgstr "" 1111"Puedes descargar algunos ya compilados en formato html o pdf en <ulink url=" 1112"\"http://www.postgis.us/study_guides\"> Guias de Estudio PostGIS / " 1113"PostgreSQL</ulink>" 1114 1115#. Tag: command 1116#: installation.xml:597 1117#, no-c-format 1118msgid "make cheatsheets" 1119msgstr "make cheatsheets" 1120 1121#. Tag: title 1122#: installation.xml:602 1123#, no-c-format 1124msgid "Building PostGIS Extensions and Deploying them" 1125msgstr "Compilando e Instalando Extensiones de PostGIS" 1126 1127#. Tag: para 1128#: installation.xml:604 1129#, no-c-format 1130msgid "" 1131"The PostGIS extensions are built and installed automatically if you are " 1132"using PostgreSQL 9.1+." 1133msgstr "" 1134"Las extensiones de PosGIS son compiladas e instaladas de forma automatica si " 1135"estas utilizando la version 9.1+ de PostgreSQL" 1136 1137#. Tag: para 1138#: installation.xml:607 1139#, no-c-format 1140msgid "" 1141"If you are building from source repository, you need to build the function " 1142"descriptions first. These get built if you have docbook installed. You can " 1143"also manually build with the statement:" 1144msgstr "" 1145"Si estas compilando desde el repositorio de código fuente, necesitas " 1146"compilar primero la función descriptions. Si tienes instaldo docbook ya esta " 1147"compilado. También puedes compilarla manualmente con la sentencia:" 1148 1149#. Tag: para 1150#: installation.xml:612 1151#, no-c-format 1152msgid "" 1153"Building the comments is not necessary if you are building from a release " 1154"tar ball since these are packaged pre-built with the tar ball already." 1155msgstr "" 1156"Compilar los comentarios no es necesario si estas compilando desde un tar ya " 1157"que están en el paquete pre-compilados con el tar." 1158 1159#. Tag: para 1160#: installation.xml:613 1161#, no-c-format 1162msgid "" 1163"If you are building against PostgreSQL 9.1, the extensions should " 1164"automatically build as part of the make install process. You can if needed " 1165"build from the extensions folders or copy files if you need them on a " 1166"different server." 1167msgstr "" 1168"Si estas compilando para PostgreSQL 9.1, la extension debería compilarse de " 1169"forma automática como parte del proceso del comando make install. Si lo " 1170"necesitas, puedes compilar la extensión desde las carpetas de la extensión o " 1171"copiar los ficheros en un servidor diferente." 1172 1173#. Tag: programlisting 1174#: installation.xml:615 1175#, no-c-format 1176msgid "" 1177"cd extensions\n" 1178"cd postgis\n" 1179"make clean\n" 1180"make\n" 1181"make install\n" 1182"cd ..\n" 1183"cd postgis_topology\n" 1184"make clean\n" 1185"make\n" 1186"make install\n" 1187"cd ..\n" 1188"cd postgis_sfcgal\n" 1189"make clean\n" 1190"make\n" 1191"make install\n" 1192"\n" 1193"cd ..\n" 1194"cd address_standardizer\n" 1195"make clean\n" 1196"make\n" 1197"make install\n" 1198"make installcheck\n" 1199"\n" 1200"cd ..\n" 1201"cd postgis_tiger_geocoder\n" 1202"make clean\n" 1203"make\n" 1204"make install\n" 1205"make installcheck" 1206msgstr "" 1207"cd extensions\n" 1208"cd postgis\n" 1209"make clean\n" 1210"make\n" 1211"make install\n" 1212"cd ..\n" 1213"cd postgis_topology\n" 1214"make clean\n" 1215"make\n" 1216"make install\n" 1217"cd ..\n" 1218"cd postgis_sfcgal\n" 1219"make clean\n" 1220"make\n" 1221"make install\n" 1222"\n" 1223"cd ..\n" 1224"cd address_standardizer\n" 1225"make clean\n" 1226"make\n" 1227"make install\n" 1228"make installcheck\n" 1229"\n" 1230"cd ..\n" 1231"cd postgis_tiger_geocoder\n" 1232"make clean\n" 1233"make\n" 1234"make install\n" 1235"make installcheck" 1236 1237#. Tag: para 1238#: installation.xml:616 1239#, no-c-format 1240msgid "" 1241"The extension files will always be the same for the same version of PostGIS " 1242"regardless of OS, so it is fine to copy over the extension files from one OS " 1243"to another as long as you have the PostGIS binaries already installed on " 1244"your servers." 1245msgstr "" 1246"Los ficheros de la extension serán siempre los mismos para la misma versión " 1247"de PostgreSQL independientemente del Sistema Operativo, así que se pueden " 1248"copiar los ficheros de la extensión de un Sistema Operativo a otro si ya " 1249"tienes los binarios de PostGIS ya instalados en tus servidores." 1250 1251#. Tag: para 1252#: installation.xml:618 1253#, no-c-format 1254msgid "" 1255"If you want to install the extensions manually on a separate server " 1256"different from your development, You need to copy the following files from " 1257"the extensions folder into the <filename>PostgreSQL / share / extension</" 1258"filename> folder of your PostgreSQL install as well as the needed binaries " 1259"for regular PostGIS if you don't have them already on the server." 1260msgstr "" 1261"Si quieres instalar la extensión de forma manual en un servidor separado de " 1262"tu servidor de desarrollo, necesitas copiar los siguientes archivos de la " 1263"carpeta de la extensión en la carpeta <filename>PostgreSQL / share / " 1264"extension</filename> de la instalación de PostgreSQL y los binarios normales " 1265"para PostGIS si no los tienes instalados en el servidor." 1266 1267#. Tag: para 1268#: installation.xml:625 1269#, no-c-format 1270msgid "" 1271"These are the control files that denote information such as the version of " 1272"the extension to install if not specified. <filename>postgis.control, " 1273"postgis_topology.control</filename>." 1274msgstr "" 1275"Estos son los ficheros de control que contienen información como la versión " 1276"de la extensión a instalar si no lo has especificado. <filename>postgis." 1277"control, postgis_topology.control</filename>." 1278 1279#. Tag: para 1280#: installation.xml:631 1281#, no-c-format 1282msgid "" 1283"All the files in the /sql folder of each extension. Note that these need to " 1284"be copied to the root of the PostgreSQL share/extension folder " 1285"<filename>extensions/postgis/sql/*.sql</filename>, <filename>extensions/" 1286"postgis_topology/sql/*.sql</filename>" 1287msgstr "" 1288"Todos los ficheros en la carpeta /sql de la extension. Estos ficheros deben " 1289"ser copiados en la raiz de PostgreSQL en la carpeta share/extension " 1290"<filename>extensions/postgis/sql/*.sql</filename>, <filename>extensions/" 1291"postgis_topology/sql/*.sql</filename>" 1292 1293#. Tag: para 1294#: installation.xml:637 1295#, no-c-format 1296msgid "" 1297"Once you do that, you should see <varname>postgis</varname>, " 1298"<varname>postgis_topology</varname> as available extensions in PgAdmin -> " 1299"extensions." 1300msgstr "" 1301"Una vez hecho esto deberías ver <varname>postgis</varname>, " 1302"<varname>postgis_topology</varname> como extensiones disponibles en PgAdmin -" 1303"> extensiones." 1304 1305#. Tag: para 1306#: installation.xml:638 1307#, no-c-format 1308msgid "" 1309"If you are using psql, you can verify that the extensions are installed by " 1310"running this query:" 1311msgstr "" 1312"Si estas utilizando psql, puedes verificar que las extensiones están " 1313"instaladas ejecutando la siguiente sentencia:" 1314 1315#. Tag: programlisting 1316#: installation.xml:639 1317#, no-c-format 1318msgid "" 1319"SELECT name, default_version,installed_version\n" 1320"FROM pg_available_extensions WHERE name LIKE 'postgis%' or name LIKE 'address" 1321"%';\n" 1322"\n" 1323" name | default_version | installed_version\n" 1324"------------------------------+-----------------+-------------------\n" 1325" address_standardizer | &last_release_version; | " 1326"&last_release_version;\n" 1327" address_standardizer_data_us | &last_release_version; | " 1328"&last_release_version;\n" 1329" postgis | &last_release_version; | " 1330"&last_release_version;\n" 1331" postgis_sfcgal | &last_release_version; |\n" 1332" postgis_tiger_geocoder | &last_release_version; | " 1333"&last_release_version;\n" 1334" postgis_topology | &last_release_version; |\n" 1335"(6 rows)" 1336msgstr "" 1337"SELECT name, default_version,installed_version\n" 1338"FROM pg_available_extensions WHERE name LIKE 'postgis%' or name LIKE 'address" 1339"%';\n" 1340"\n" 1341" name | default_version | installed_version\n" 1342"------------------------------+-----------------+-------------------\n" 1343" address_standardizer | &last_release_version; | " 1344"&last_release_version;\n" 1345" address_standardizer_data_us | &last_release_version; | " 1346"&last_release_version;\n" 1347" postgis | &last_release_version; | " 1348"&last_release_version;\n" 1349" postgis_sfcgal | &last_release_version; |\n" 1350" postgis_tiger_geocoder | &last_release_version; | " 1351"&last_release_version;\n" 1352" postgis_topology | &last_release_version; |\n" 1353"(6 rows)" 1354 1355#. Tag: para 1356#: installation.xml:641 1357#, no-c-format 1358msgid "" 1359"If you have the extension installed in the database you are querying, you'll " 1360"see mention in the <varname>installed_version</varname> column. If you get " 1361"no records back, it means you don't have postgis extensions installed on the " 1362"server at all. PgAdmin III 1.14+ will also provide this information in the " 1363"<varname>extensions</varname> section of the database browser tree and will " 1364"even allow upgrade or uninstall by right-clicking." 1365msgstr "" 1366"Si tienes instalada una extension en la base de datos que estas consultando, " 1367"deberías verla mencionada la columna <varname>installed_version</varname>. " 1368"Si la consulta no devuelve ningún registro, significa que no tienes la " 1369"extension PostGIS instalada en el servidor. PgAdmin III 1.14+ muestra esta " 1370"información en la sección <varname>extensiones</varname> en el navegador de " 1371"bases de datos y permite actualizar o instalar haciendo click derecho." 1372 1373#. Tag: para 1374#: installation.xml:645 1375#, no-c-format 1376msgid "" 1377"If you have the extensions available, you can install postgis extension in " 1378"your database of choice by either using pgAdmin extension interface or " 1379"running these sql commands:" 1380msgstr "" 1381"Si la extension esta disponible, puedes instalar la extension postgis en la " 1382"base de datos de tu elección utilizando la interfaz de extensiones de " 1383"pgAdmin o ejecutando la siguiente sentencia:" 1384 1385#. Tag: programlisting 1386#: installation.xml:646 1387#, no-c-format 1388msgid "" 1389"CREATE EXTENSION postgis;\n" 1390"CREATE EXTENSION postgis_sfcgal;\n" 1391"CREATE EXTENSION fuzzystrmatch; --needed for postgis_tiger_geocoder\n" 1392"--optional used by postgis_tiger_geocoder, or can be used standalone\n" 1393"CREATE EXTENSION address_standardizer;\n" 1394"CREATE EXTENSION address_standardizer_data_us;\n" 1395"CREATE EXTENSION postgis_tiger_geocoder;\n" 1396"CREATE EXTENSION postgis_topology;" 1397msgstr "" 1398"CREATE EXTENSION postgis;\n" 1399"CREATE EXTENSION postgis_sfcgal;\n" 1400"CREATE EXTENSION fuzzystrmatch; --needed for postgis_tiger_geocoder\n" 1401"--optional used by postgis_tiger_geocoder, or can be used standalone\n" 1402"CREATE EXTENSION address_standardizer;\n" 1403"CREATE EXTENSION address_standardizer_data_us;\n" 1404"CREATE EXTENSION postgis_tiger_geocoder;\n" 1405"CREATE EXTENSION postgis_topology;" 1406 1407#. Tag: para 1408#: installation.xml:648 1409#, no-c-format 1410msgid "" 1411"In psql you can use to see what versions you have installed and also what " 1412"schema they are installed." 1413msgstr "" 1414 1415#. Tag: programlisting 1416#: installation.xml:649 1417#, no-c-format 1418msgid "" 1419"\\connect mygisdb\n" 1420"\\x\n" 1421"\\dx postgis*" 1422msgstr "" 1423"\\connect mygisdb\n" 1424"\\x\n" 1425"\\dx postgis*" 1426 1427#. Tag: screen 1428#: installation.xml:651 1429#, no-c-format 1430msgid "" 1431"List of installed extensions\n" 1432"-[ RECORD 1 ]-------------------------------------------------\n" 1433"-\n" 1434"Name | postgis\n" 1435"Version | &last_release_version;\n" 1436"Schema | public\n" 1437"Description | PostGIS geometry, geography, and raster spat..\n" 1438"-[ RECORD 2 ]-------------------------------------------------\n" 1439"-\n" 1440"Name | postgis_tiger_geocoder\n" 1441"Version | &last_release_version;\n" 1442"Schema | tiger\n" 1443"Description | PostGIS tiger geocoder and reverse geocoder\n" 1444"-[ RECORD 3 ]-------------------------------------------------\n" 1445"-\n" 1446"Name | postgis_topology\n" 1447"Version | &last_release_version;\n" 1448"Schema | topology\n" 1449"Description | PostGIS topology spatial types and functions" 1450msgstr "" 1451 1452#. Tag: para 1453#: installation.xml:653 1454#, no-c-format 1455msgid "" 1456"Extension tables <varname>spatial_ref_sys</varname>, <varname>layer</" 1457"varname>, <varname>topology</varname> can not be explicitly backed up. They " 1458"can only be backed up when the respective <varname>postgis</varname> or " 1459"<varname>postgis_topology</varname> extension is backed up, which only seems " 1460"to happen when you backup the whole database. As of PostGIS 2.0.1, only srid " 1461"records not packaged with PostGIS are backed up when the database is backed " 1462"up so don't go around changing srids we package and expect your changes to " 1463"be there. Put in a ticket if you find an issue. The structures of extension " 1464"tables are never backed up since they are created with <code>CREATE " 1465"EXTENSION</code> and assumed to be the same for a given version of an " 1466"extension. These behaviors are built into the current PostgreSQL extension " 1467"model, so nothing we can do about it." 1468msgstr "" 1469"No se pueden hacer copias de seguridad explicitas de las tablas de las " 1470"extensiones <varname>spatial_ref_sys</varname>, <varname>layer</varname>, " 1471"<varname>topology</varname>. Solo se pueden hacer copias de seguridad " 1472"explicitas cuando cuando se hacen copias de seguridad de sus respectivas " 1473"extensiones <varname>postgis</varname> or <varname>postgis_topology</" 1474"varname>, lo que al parecer ocurre cuando haces una copia de seguridad de la " 1475"base de datos completa. Con PostGIS 2.0.1, solo los srid no incluidos en " 1476"PostGIS son guardados cuando se hace una copia de seguridad de la base de " 1477"datos, así que no esperes que al cambiar alguno de los srid que incluye " 1478"PostGIS este en tu copia de seguridad. Envia un ticket si encuentras algún " 1479"problema. La estructura de las tabals de extensiones no se guardan en copias " 1480"de seguridad si son creadas con <code>CREATE EXTENSION</code> y son la misma " 1481"estructura para una version dada de una extension. Estos comportamientos " 1482"están incorporados en el modelo de extensiones PostgreSQL actual, así que " 1483"nada podemos hacer al respecto." 1484 1485#. Tag: para 1486#: installation.xml:658 1487#, no-c-format 1488msgid "" 1489"If you installed &last_release_version;, without using our wonderful " 1490"extension system, you can change it to be extension based by first upgrading " 1491"to the latest micro version running the upgrade scripts: " 1492"<filename>postgis_upgrade_22_minor.sql</filename>," 1493"<filename>raster_upgrade_22_minor.sql</filename>," 1494"<filename>topology_upgrade_22_minor.sql</filename>." 1495msgstr "" 1496 1497#. Tag: para 1498#: installation.xml:659 1499#, no-c-format 1500msgid "" 1501"If you installed postgis without raster support, you'll need to install " 1502"raster support first (using the full <filename>rtpostgis.sql</filename>" 1503msgstr "" 1504"Si ha instalado postgis sin el soporte raster, necesitara instalarlo primero " 1505"(usando el archivo <filename>rtpostgis.sql</filename>" 1506 1507#. Tag: para 1508#: installation.xml:660 1509#, no-c-format 1510msgid "" 1511"Then you can run the below commands to package the functions in their " 1512"respective extension." 1513msgstr "" 1514"Entonces podrá ejecutar los siguientes comandos para empaquetar las " 1515"funciones en sus extensiones respectivas.\n" 1516"\t\n" 1517" " 1518 1519#. Tag: programlisting 1520#: installation.xml:661 1521#, no-c-format 1522msgid "" 1523"CREATE EXTENSION postgis FROM unpackaged;\n" 1524"CREATE EXTENSION postgis_topology FROM unpackaged;\n" 1525"CREATE EXTENSION postgis_tiger_geocoder FROM unpackaged;" 1526msgstr "" 1527"CREATE EXTENSION postgis FROM unpackaged;\n" 1528"CREATE EXTENSION postgis_topology FROM unpackaged;\n" 1529"CREATE EXTENSION postgis_tiger_geocoder FROM unpackaged;" 1530 1531#. Tag: title 1532#: installation.xml:667 1533#, no-c-format 1534msgid "Testing" 1535msgstr "Tests" 1536 1537#. Tag: para 1538#: installation.xml:669 1539#, no-c-format 1540msgid "If you wish to test the PostGIS build, run" 1541msgstr "Si quieres hacer un test en la compilación de PostGIS, ejecuta" 1542 1543#. Tag: command 1544#: installation.xml:674 1545#, no-c-format 1546msgid "make check" 1547msgstr "make check" 1548 1549#. Tag: para 1550#: installation.xml:677 1551#, no-c-format 1552msgid "" 1553"The above command will run through various checks and regression tests using " 1554"the generated library against an actual PostgreSQL database." 1555msgstr "" 1556"El comando anterior ejecutará varias comprobaciones y tests de regresión " 1557"utilizando la librería generada para la version de base de datos PostgreSQL " 1558"actual." 1559 1560#. Tag: para 1561#: installation.xml:683 1562#, no-c-format 1563msgid "" 1564"If you configured PostGIS using non-standard PostgreSQL, GEOS, or Proj4 " 1565"locations, you may need to add their library locations to the " 1566"LD_LIBRARY_PATH environment variable." 1567msgstr "" 1568"Si has configurado PostGIS con instalaciones de PostgreSQL, GEOS, o Proj4 en " 1569"directorios personalizados, necesitaras añadir las localizaciones de las " 1570"librerías personalizadas en la variable de entorno LD_LIBRARY_PATH." 1571 1572#. Tag: para 1573#: installation.xml:691 1574#, no-c-format 1575msgid "" 1576"Currently, the <command>make check</command> relies on the <code>PATH</code> " 1577"and <code>PGPORT</code> environment variables when performing the checks - " 1578"it does <emphasis>not</emphasis> use the PostgreSQL version that may have " 1579"been specified using the configuration parameter <command>--with-pgconfig</" 1580"command>. So make sure to modify your PATH to match the detected PostgreSQL " 1581"installation during configuration or be prepared to deal with the impending " 1582"headaches." 1583msgstr "" 1584"Actualmente, el comando <command>make check</command> une las variables de " 1585"entorno <code>PATH</code> y <code>PGPORT</code> cundo ejecuta las " 1586"comprobaciones - <emphasis>no</emphasis> utiliza la version de PostgreSQL " 1587"especificada utilizando el parametro de configuración <command>--with-" 1588"pgconfig</command>. Así que hay que estar seguros de modificar la variable " 1589"de entorno PATH para que apunte a la instalación de PostgreSQL detectada " 1590"durante la configuración o estar preparado para tener algún que otro dolor " 1591"de cabeza." 1592 1593#. Tag: para 1594#: installation.xml:703 1595#, no-c-format 1596msgid "" 1597"If successful, the output of the test should be similar to the following:" 1598msgstr "" 1599"Si todo ha ido bien, la salida del comando de test debería ser similar a la " 1600"siguiente:" 1601 1602#. Tag: programlisting 1603#: installation.xml:708 1604#, no-c-format 1605msgid "" 1606"CUnit - A unit testing framework for C - Version 2.1-2\n" 1607" http://cunit.sourceforge.net/\n" 1608"\n" 1609"\n" 1610"Suite: computational_geometry\n" 1611" Test: test_lw_segment_side ...passed\n" 1612" Test: test_lw_segment_intersects ...passed\n" 1613" Test: test_lwline_crossing_short_lines ...passed\n" 1614" Test: test_lwline_crossing_long_lines ...passed\n" 1615" Test: test_lwline_crossing_bugs ...passed\n" 1616" Test: test_lwpoint_set_ordinate ...passed\n" 1617" Test: test_lwpoint_get_ordinate ...passed\n" 1618" Test: test_point_interpolate ...passed\n" 1619" Test: test_lwline_clip ...passed\n" 1620" Test: test_lwline_clip_big ...passed\n" 1621" Test: test_lwmline_clip ...passed\n" 1622" Test: test_geohash_point ...passed\n" 1623" Test: test_geohash_precision ...passed\n" 1624" Test: test_geohash ...passed\n" 1625" Test: test_geohash_point_as_int ...passed\n" 1626" Test: test_isclosed ...passed\n" 1627" Test: test_lwgeom_simplify ...passed\n" 1628"Suite: buildarea\n" 1629" Test: buildarea1 ...passed\n" 1630" Test: buildarea2 ...passed\n" 1631" Test: buildarea3 ...passed\n" 1632" Test: buildarea4 ...passed\n" 1633" Test: buildarea4b ...passed\n" 1634" Test: buildarea5 ...passed\n" 1635" Test: buildarea6 ...passed\n" 1636" Test: buildarea7 ...passed\n" 1637"Suite: geometry_clean\n" 1638" Test: test_lwgeom_make_valid ...passed\n" 1639"Suite: clip_by_rectangle\n" 1640" Test: test_lwgeom_clip_by_rect ...passed\n" 1641"Suite: force_sfs\n" 1642" Test: test_sfs_11 ...passed\n" 1643" Test: test_sfs_12 ...passed\n" 1644" Test: test_sqlmm ...passed\n" 1645"Suite: geodetic\n" 1646" Test: test_sphere_direction ...passed\n" 1647" Test: test_sphere_project ...passed\n" 1648" Test: test_lwgeom_area_sphere ...passed\n" 1649" Test: test_signum ...passed\n" 1650" Test: test_gbox_from_spherical_coordinates ...passed\n" 1651" Test: test_gserialized_get_gbox_geocentric ...passed\n" 1652" Test: test_clairaut ...passed\n" 1653" Test: test_edge_intersection ...passed\n" 1654" Test: test_edge_intersects ...passed\n" 1655" Test: test_edge_distance_to_point ...passed\n" 1656" Test: test_edge_distance_to_edge ...passed\n" 1657" Test: test_lwgeom_distance_sphere ...passed\n" 1658" Test: test_lwgeom_check_geodetic ...passed\n" 1659" Test: test_gserialized_from_lwgeom ...passed\n" 1660" Test: test_spheroid_distance ...passed\n" 1661" Test: test_spheroid_area ...passed\n" 1662" Test: test_lwpoly_covers_point2d ...passed\n" 1663" Test: test_gbox_utils ...passed\n" 1664" Test: test_vector_angle ...passed\n" 1665" Test: test_vector_rotate ...passed\n" 1666" Test: test_lwgeom_segmentize_sphere ...passed\n" 1667" Test: test_ptarray_contains_point_sphere ...passed\n" 1668" Test: test_ptarray_contains_point_sphere_iowa ...passed\n" 1669"Suite: GEOS\n" 1670" Test: test_geos_noop ...passed\n" 1671" Test: test_geos_subdivide ...passed\n" 1672" Test: test_geos_linemerge ...passed\n" 1673"Suite: Clustering\n" 1674" Test: basic_test ...passed\n" 1675" Test: nonsequential_test ...passed\n" 1676" Test: basic_distance_test ...passed\n" 1677" Test: single_input_test ...passed\n" 1678" Test: empty_inputs_test ...passed\n" 1679"Suite: Clustering Union-Find\n" 1680" Test: test_unionfind_create ...passed\n" 1681" Test: test_unionfind_union ...passed\n" 1682" Test: test_unionfind_ordered_by_cluster ...passed\n" 1683"Suite: homogenize\n" 1684" Test: test_coll_point ...passed\n" 1685" Test: test_coll_line ...passed\n" 1686" Test: test_coll_poly ...passed\n" 1687" Test: test_coll_coll ...passed\n" 1688" Test: test_geom ...passed\n" 1689" Test: test_coll_curve ...passed\n" 1690"Suite: encoded_polyline_input\n" 1691" Test: in_encoded_polyline_test_geoms ...passed\n" 1692" Test: in_encoded_polyline_test_precision ...passed\n" 1693"Suite: geojson_input\n" 1694" Test: in_geojson_test_srid ...passed\n" 1695" Test: in_geojson_test_bbox ...passed\n" 1696" Test: in_geojson_test_geoms ...passed\n" 1697"Suite: twkb_input\n" 1698" Test: test_twkb_in_point ...passed\n" 1699" Test: test_twkb_in_linestring ...passed\n" 1700" Test: test_twkb_in_polygon ...passed\n" 1701" Test: test_twkb_in_multipoint ...passed\n" 1702" Test: test_twkb_in_multilinestring ...passed\n" 1703" Test: test_twkb_in_multipolygon ...passed\n" 1704" Test: test_twkb_in_collection ...passed\n" 1705" Test: test_twkb_in_precision ...passed\n" 1706"Suite: serialization/deserialization\n" 1707" Test: test_typmod_macros ...passed\n" 1708" Test: test_flags_macros ...passed\n" 1709" Test: test_serialized_srid ...passed\n" 1710" Test: test_gserialized_from_lwgeom_size ...passed\n" 1711" Test: test_gbox_serialized_size ...passed\n" 1712" Test: test_lwgeom_from_gserialized ...passed\n" 1713" Test: test_lwgeom_count_vertices ...passed\n" 1714" Test: test_on_gser_lwgeom_count_vertices ...passed\n" 1715" Test: test_geometry_type_from_string ...passed\n" 1716" Test: test_lwcollection_extract ...passed\n" 1717" Test: test_lwgeom_free ...passed\n" 1718" Test: test_lwgeom_flip_coordinates ...passed\n" 1719" Test: test_f2d ...passed\n" 1720" Test: test_lwgeom_clone ...passed\n" 1721" Test: test_lwgeom_force_clockwise ...passed\n" 1722" Test: test_lwgeom_calculate_gbox ...passed\n" 1723" Test: test_lwgeom_is_empty ...passed\n" 1724" Test: test_lwgeom_same ...passed\n" 1725" Test: test_lwline_from_lwmpoint ...passed\n" 1726" Test: test_lwgeom_as_curve ...passed\n" 1727" Test: test_lwgeom_scale ...passed\n" 1728" Test: test_gserialized_is_empty ...passed\n" 1729" Test: test_gbox_same_2d ...passed\n" 1730"Suite: measures\n" 1731" Test: test_mindistance2d_tolerance ...passed\n" 1732" Test: test_rect_tree_contains_point ...passed\n" 1733" Test: test_rect_tree_intersects_tree ...passed\n" 1734" Test: test_lwgeom_segmentize2d ...passed\n" 1735" Test: test_lwgeom_locate_along ...passed\n" 1736" Test: test_lw_dist2d_pt_arc ...passed\n" 1737" Test: test_lw_dist2d_seg_arc ...passed\n" 1738" Test: test_lw_dist2d_arc_arc ...passed\n" 1739" Test: test_lw_arc_length ...passed\n" 1740" Test: test_lw_dist2d_pt_ptarrayarc ...passed\n" 1741" Test: test_lw_dist2d_ptarray_ptarrayarc ...passed\n" 1742" Test: test_lwgeom_tcpa ...passed\n" 1743" Test: test_lwgeom_is_trajectory ...passed\n" 1744"Suite: effectivearea\n" 1745" Test: do_test_lwgeom_effectivearea_lines ...passed\n" 1746" Test: do_test_lwgeom_effectivearea_polys ...passed\n" 1747"Suite: miscellaneous\n" 1748" Test: test_misc_force_2d ...passed\n" 1749" Test: test_misc_simplify ...passed\n" 1750" Test: test_misc_count_vertices ...passed\n" 1751" Test: test_misc_area ...passed\n" 1752" Test: test_misc_wkb ...passed\n" 1753" Test: test_grid ...passed\n" 1754"Suite: noding\n" 1755" Test: test_lwgeom_node ...passed\n" 1756"Suite: encoded_polyline_output\n" 1757" Test: out_encoded_polyline_test_geoms ...passed\n" 1758" Test: out_encoded_polyline_test_srid ...passed\n" 1759" Test: out_encoded_polyline_test_precision ...passed\n" 1760"Suite: geojson_output\n" 1761" Test: out_geojson_test_precision ...passed\n" 1762" Test: out_geojson_test_dims ...passed\n" 1763" Test: out_geojson_test_srid ...passed\n" 1764" Test: out_geojson_test_bbox ...passed\n" 1765" Test: out_geojson_test_geoms ...passed\n" 1766"Suite: gml_output\n" 1767" Test: out_gml_test_precision ...passed\n" 1768" Test: out_gml_test_srid ...passed\n" 1769" Test: out_gml_test_dims ...passed\n" 1770" Test: out_gml_test_geodetic ...passed\n" 1771" Test: out_gml_test_geoms ...passed\n" 1772" Test: out_gml_test_geoms_prefix ...passed\n" 1773" Test: out_gml_test_geoms_nodims ...passed\n" 1774" Test: out_gml2_extent ...passed\n" 1775" Test: out_gml3_extent ...passed\n" 1776"Suite: kml_output\n" 1777" Test: out_kml_test_precision ...passed\n" 1778" Test: out_kml_test_dims ...passed\n" 1779" Test: out_kml_test_geoms ...passed\n" 1780" Test: out_kml_test_prefix ...passed\n" 1781"Suite: svg_output\n" 1782" Test: out_svg_test_precision ...passed\n" 1783" Test: out_svg_test_dims ...passed\n" 1784" Test: out_svg_test_relative ...passed\n" 1785" Test: out_svg_test_geoms ...passed\n" 1786" Test: out_svg_test_srid ...passed\n" 1787"Suite: x3d_output\n" 1788" Test: out_x3d3_test_precision ...passed\n" 1789" Test: out_x3d3_test_geoms ...passed\n" 1790" Test: out_x3d3_test_option ...passed\n" 1791"Suite: ptarray\n" 1792" Test: test_ptarray_append_point ...passed\n" 1793" Test: test_ptarray_append_ptarray ...passed\n" 1794" Test: test_ptarray_locate_point ...passed\n" 1795" Test: test_ptarray_isccw ...passed\n" 1796" Test: test_ptarray_signed_area ...passed\n" 1797" Test: test_ptarray_unstroke ...passed\n" 1798" Test: test_ptarray_insert_point ...passed\n" 1799" Test: test_ptarray_contains_point ...passed\n" 1800" Test: test_ptarrayarc_contains_point ...passed\n" 1801" Test: test_ptarray_scale ...passed\n" 1802"Suite: printing\n" 1803" Test: test_lwprint_default_format ...passed\n" 1804" Test: test_lwprint_format_orders ...passed\n" 1805" Test: test_lwprint_optional_format ...passed\n" 1806" Test: test_lwprint_oddball_formats ...passed\n" 1807" Test: test_lwprint_bad_formats ...passed\n" 1808"Suite: SFCGAL\n" 1809" Test: test_sfcgal_noop ...passed\n" 1810"Suite: split\n" 1811" Test: test_lwline_split_by_point_to ...passed\n" 1812" Test: test_lwgeom_split ...passed\n" 1813"Suite: stringbuffer\n" 1814" Test: test_stringbuffer_append ...passed\n" 1815" Test: test_stringbuffer_aprintf ...passed\n" 1816"Suite: surface\n" 1817" Test: triangle_parse ...passed\n" 1818" Test: tin_parse ...passed\n" 1819" Test: polyhedralsurface_parse ...passed\n" 1820" Test: surface_dimension ...passed\n" 1821"Suite: Internal Spatial Trees\n" 1822" Test: test_tree_circ_create ...passed\n" 1823" Test: test_tree_circ_pip ...passed\n" 1824" Test: test_tree_circ_pip2 ...passed\n" 1825" Test: test_tree_circ_distance ...passed\n" 1826" Test: test_tree_circ_distance_threshold ...passed\n" 1827"Suite: triangulate\n" 1828" Test: test_lwgeom_delaunay_triangulation ...passed\n" 1829"Suite: twkb_output\n" 1830" Test: test_twkb_out_point ...passed\n" 1831" Test: test_twkb_out_linestring ...passed\n" 1832" Test: test_twkb_out_polygon ...passed\n" 1833" Test: test_twkb_out_multipoint ...passed\n" 1834" Test: test_twkb_out_multilinestring ...passed\n" 1835" Test: test_twkb_out_multipolygon ...passed\n" 1836" Test: test_twkb_out_collection ...passed\n" 1837" Test: test_twkb_out_idlist ...passed\n" 1838"Suite: varint\n" 1839" Test: test_zigzag ...passed\n" 1840" Test: test_varint ...passed\n" 1841" Test: test_varint_roundtrip ...passed\n" 1842"Suite: wkb_input\n" 1843" Test: test_wkb_in_point ...passed\n" 1844" Test: test_wkb_in_linestring ...passed\n" 1845" Test: test_wkb_in_polygon ...passed\n" 1846" Test: test_wkb_in_multipoint ...passed\n" 1847" Test: test_wkb_in_multilinestring ...passed\n" 1848" Test: test_wkb_in_multipolygon ...passed\n" 1849" Test: test_wkb_in_collection ...passed\n" 1850" Test: test_wkb_in_circularstring ...passed\n" 1851" Test: test_wkb_in_compoundcurve ...passed\n" 1852" Test: test_wkb_in_curvpolygon ...passed\n" 1853" Test: test_wkb_in_multicurve ...passed\n" 1854" Test: test_wkb_in_multisurface ...passed\n" 1855" Test: test_wkb_in_malformed ...passed\n" 1856"Suite: wkb_output\n" 1857" Test: test_wkb_out_point ...passed\n" 1858" Test: test_wkb_out_linestring ...passed\n" 1859" Test: test_wkb_out_polygon ...passed\n" 1860" Test: test_wkb_out_multipoint ...passed\n" 1861" Test: test_wkb_out_multilinestring ...passed\n" 1862" Test: test_wkb_out_multipolygon ...passed\n" 1863" Test: test_wkb_out_collection ...passed\n" 1864" Test: test_wkb_out_circularstring ...passed\n" 1865" Test: test_wkb_out_compoundcurve ...passed\n" 1866" Test: test_wkb_out_curvpolygon ...passed\n" 1867" Test: test_wkb_out_multicurve ...passed\n" 1868" Test: test_wkb_out_multisurface ...passed\n" 1869" Test: test_wkb_out_polyhedralsurface ...passed\n" 1870"Suite: wkt_input\n" 1871" Test: test_wkt_in_point ...passed\n" 1872" Test: test_wkt_in_linestring ...passed\n" 1873" Test: test_wkt_in_polygon ...passed\n" 1874" Test: test_wkt_in_multipoint ...passed\n" 1875" Test: test_wkt_in_multilinestring ...passed\n" 1876" Test: test_wkt_in_multipolygon ...passed\n" 1877" Test: test_wkt_in_collection ...passed\n" 1878" Test: test_wkt_in_circularstring ...passed\n" 1879" Test: test_wkt_in_compoundcurve ...passed\n" 1880" Test: test_wkt_in_curvpolygon ...passed\n" 1881" Test: test_wkt_in_multicurve ...passed\n" 1882" Test: test_wkt_in_multisurface ...passed\n" 1883" Test: test_wkt_in_tin ...passed\n" 1884" Test: test_wkt_in_polyhedralsurface ...passed\n" 1885" Test: test_wkt_in_errlocation ...passed\n" 1886"Suite: wkt_output\n" 1887" Test: test_wkt_out_point ...passed\n" 1888" Test: test_wkt_out_linestring ...passed\n" 1889" Test: test_wkt_out_polygon ...passed\n" 1890" Test: test_wkt_out_multipoint ...passed\n" 1891" Test: test_wkt_out_multilinestring ...passed\n" 1892" Test: test_wkt_out_multipolygon ...passed\n" 1893" Test: test_wkt_out_collection ...passed\n" 1894" Test: test_wkt_out_circularstring ...passed\n" 1895" Test: test_wkt_out_compoundcurve ...passed\n" 1896" Test: test_wkt_out_curvpolygon ...passed\n" 1897" Test: test_wkt_out_multicurve ...passed\n" 1898" Test: test_wkt_out_multisurface ...passed\n" 1899"\n" 1900"Run Summary: Type Total Ran Passed Failed Inactive\n" 1901" suites 38 38 n/a 0 0\n" 1902" tests 251 251 251 0 0\n" 1903" asserts 2468 2468 2468 0 n/a\n" 1904"\n" 1905"Elapsed time = 0.298 seconds\n" 1906"\n" 1907"Creating database 'postgis_reg'\n" 1908"Loading PostGIS into 'postgis_reg'\n" 1909" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/" 1910"postgis/postgis.sql\n" 1911" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/" 1912"postgis/postgis_comments.sql\n" 1913"Loading SFCGAL into 'postgis_reg'\n" 1914" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/" 1915"postgis/sfcgal.sql\n" 1916" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/" 1917"postgis/sfcgal_comments.sql\n" 1918"PostgreSQL 9.4.4, compiled by Visual C++ build 1800, 32-bit\n" 1919" Postgis 2.2.0dev - r13980 - 2015-08-23 06:13:07\n" 1920" scripts 2.2.0dev r13980\n" 1921" GEOS: 3.5.0-CAPI-1.9.0 r4088\n" 1922" PROJ: Rel. 4.9.1, 04 March 2015\n" 1923" SFCGAL: 1.1.0\n" 1924"\n" 1925"Running tests\n" 1926"\n" 1927" loader/Point .............. ok\n" 1928" loader/PointM .............. ok\n" 1929" loader/PointZ .............. ok\n" 1930" loader/MultiPoint .............. ok\n" 1931" loader/MultiPointM .............. ok\n" 1932" loader/MultiPointZ .............. ok\n" 1933" loader/Arc .............. ok\n" 1934" loader/ArcM .............. ok\n" 1935" loader/ArcZ .............. ok\n" 1936" loader/Polygon .............. ok\n" 1937" loader/PolygonM .............. ok\n" 1938" loader/PolygonZ .............. ok\n" 1939" loader/TSTPolygon ......... ok\n" 1940" loader/TSIPolygon ......... ok\n" 1941" loader/TSTIPolygon ......... ok\n" 1942" loader/PointWithSchema ..... ok\n" 1943" loader/NoTransPoint ......... ok\n" 1944" loader/NotReallyMultiPoint ......... ok\n" 1945" loader/MultiToSinglePoint ......... ok\n" 1946" loader/ReprojectPts ........ ok\n" 1947" loader/ReprojectPtsGeog ........ ok\n" 1948" loader/Latin1 .... ok\n" 1949" loader/Latin1-implicit .... ok\n" 1950" loader/mfile .... ok\n" 1951" dumper/literalsrid ....... ok\n" 1952" dumper/realtable ....... ok\n" 1953" affine .. ok\n" 1954" bestsrid .. ok\n" 1955" binary .. ok\n" 1956" boundary .. ok\n" 1957" cluster .. ok\n" 1958" concave_hull .. ok\n" 1959" ctors .. ok\n" 1960" dump .. ok\n" 1961" dumppoints .. ok\n" 1962" empty .. ok\n" 1963" forcecurve .. ok\n" 1964" geography .. ok\n" 1965" in_geohash .. ok\n" 1966" in_gml .. ok\n" 1967" in_kml .. ok\n" 1968" in_encodedpolyline .. ok\n" 1969" iscollection .. ok\n" 1970" legacy .. ok\n" 1971" long_xact .. ok\n" 1972" lwgeom_regress .. ok\n" 1973" measures .. ok\n" 1974" operators .. ok\n" 1975" out_geometry .. ok\n" 1976" out_geography .. ok\n" 1977" polygonize .. ok\n" 1978" polyhedralsurface .. ok\n" 1979" postgis_type_name .. ok\n" 1980" regress .. ok\n" 1981" regress_bdpoly .. ok\n" 1982" regress_index .. ok\n" 1983" regress_index_nulls .. ok\n" 1984" regress_management .. ok\n" 1985" regress_selectivity .. ok\n" 1986" regress_lrs .. ok\n" 1987" regress_ogc .. ok\n" 1988" regress_ogc_cover .. ok\n" 1989" regress_ogc_prep .. ok\n" 1990" regress_proj .. ok\n" 1991" relate .. ok\n" 1992" remove_repeated_points .. ok\n" 1993" removepoint .. ok\n" 1994" setpoint .. ok\n" 1995" simplify .. ok\n" 1996" simplifyvw .. ok\n" 1997" size .. ok\n" 1998" snaptogrid .. ok\n" 1999" split .. ok\n" 2000" sql-mm-serialize .. ok\n" 2001" sql-mm-circularstring .. ok\n" 2002" sql-mm-compoundcurve .. ok\n" 2003" sql-mm-curvepoly .. ok\n" 2004" sql-mm-general .. ok\n" 2005" sql-mm-multicurve .. ok\n" 2006" sql-mm-multisurface .. ok\n" 2007" swapordinates .. ok\n" 2008" summary .. ok\n" 2009" temporal .. ok\n" 2010" tickets .. ok\n" 2011" twkb .. ok\n" 2012" typmod .. ok\n" 2013" wkb .. ok\n" 2014" wkt .. ok\n" 2015" wmsservers .. ok\n" 2016" knn .. ok\n" 2017" hausdorff .. ok\n" 2018" regress_buffer_params .. ok\n" 2019" offsetcurve .. ok\n" 2020" relatematch .. ok\n" 2021" isvaliddetail .. ok\n" 2022" sharedpaths .. ok\n" 2023" snap .. ok\n" 2024" node .. ok\n" 2025" unaryunion .. ok\n" 2026" clean .. ok\n" 2027" relate_bnr .. ok\n" 2028" delaunaytriangles .. ok\n" 2029" clipbybox2d .. ok\n" 2030" subdivide .. ok\n" 2031" in_geojson .. ok\n" 2032" regress_sfcgal .. ok\n" 2033" sfcgal/empty .. ok\n" 2034" sfcgal/geography .. ok\n" 2035" sfcgal/legacy .. ok\n" 2036" sfcgal/measures .. ok\n" 2037" sfcgal/regress_ogc_prep .. ok\n" 2038" sfcgal/regress_ogc .. ok\n" 2039" sfcgal/regress .. ok\n" 2040" sfcgal/tickets .. ok\n" 2041" sfcgal/concave_hull .. ok\n" 2042" sfcgal/wmsservers .. ok\n" 2043" sfcgal/approximatemedialaxis .. ok\n" 2044" uninstall . /projects/postgis/branches/2.2/regress/00-regress-install/" 2045"share/contrib/postgis/uninstall_sfcgal.sql\n" 2046" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/" 2047"postgis/uninstall_postgis.sql\n" 2048". ok (4336)\n" 2049"\n" 2050"Run tests: 118\n" 2051"Failed: 0\n" 2052"\n" 2053"-- if you built --with-gui, you should see this too\n" 2054"\n" 2055" CUnit - A unit testing framework for C - Version 2.1-2\n" 2056" http://cunit.sourceforge.net/\n" 2057"\n" 2058"\n" 2059"Suite: Shapefile Loader File shp2pgsql Test\n" 2060" Test: test_ShpLoaderCreate() ...passed\n" 2061" Test: test_ShpLoaderDestroy() ...passed\n" 2062"Suite: Shapefile Loader File pgsql2shp Test\n" 2063" Test: test_ShpDumperCreate() ...passed\n" 2064" Test: test_ShpDumperDestroy() ...passed\n" 2065"\n" 2066"Run Summary: Type Total Ran Passed Failed Inactive\n" 2067" suites 2 2 n/a 0 0\n" 2068" tests 4 4 4 0 0\n" 2069" asserts 4 4 4 0 n/a" 2070msgstr "" 2071"CUnit - A unit testing framework for C - Version 2.1-2\n" 2072" http://cunit.sourceforge.net/\n" 2073"\n" 2074"\n" 2075"Suite: computational_geometry\n" 2076" Test: test_lw_segment_side ...passed\n" 2077" Test: test_lw_segment_intersects ...passed\n" 2078" Test: test_lwline_crossing_short_lines ...passed\n" 2079" Test: test_lwline_crossing_long_lines ...passed\n" 2080" Test: test_lwline_crossing_bugs ...passed\n" 2081" Test: test_lwpoint_set_ordinate ...passed\n" 2082" Test: test_lwpoint_get_ordinate ...passed\n" 2083" Test: test_point_interpolate ...passed\n" 2084" Test: test_lwline_clip ...passed\n" 2085" Test: test_lwline_clip_big ...passed\n" 2086" Test: test_lwmline_clip ...passed\n" 2087" Test: test_geohash_point ...passed\n" 2088" Test: test_geohash_precision ...passed\n" 2089" Test: test_geohash ...passed\n" 2090" Test: test_geohash_point_as_int ...passed\n" 2091" Test: test_isclosed ...passed\n" 2092" Test: test_lwgeom_simplify ...passed\n" 2093"Suite: buildarea\n" 2094" Test: buildarea1 ...passed\n" 2095" Test: buildarea2 ...passed\n" 2096" Test: buildarea3 ...passed\n" 2097" Test: buildarea4 ...passed\n" 2098" Test: buildarea4b ...passed\n" 2099" Test: buildarea5 ...passed\n" 2100" Test: buildarea6 ...passed\n" 2101" Test: buildarea7 ...passed\n" 2102"Suite: geometry_clean\n" 2103" Test: test_lwgeom_make_valid ...passed\n" 2104"Suite: clip_by_rectangle\n" 2105" Test: test_lwgeom_clip_by_rect ...passed\n" 2106"Suite: force_sfs\n" 2107" Test: test_sfs_11 ...passed\n" 2108" Test: test_sfs_12 ...passed\n" 2109" Test: test_sqlmm ...passed\n" 2110"Suite: geodetic\n" 2111" Test: test_sphere_direction ...passed\n" 2112" Test: test_sphere_project ...passed\n" 2113" Test: test_lwgeom_area_sphere ...passed\n" 2114" Test: test_signum ...passed\n" 2115" Test: test_gbox_from_spherical_coordinates ...passed\n" 2116" Test: test_gserialized_get_gbox_geocentric ...passed\n" 2117" Test: test_clairaut ...passed\n" 2118" Test: test_edge_intersection ...passed\n" 2119" Test: test_edge_intersects ...passed\n" 2120" Test: test_edge_distance_to_point ...passed\n" 2121" Test: test_edge_distance_to_edge ...passed\n" 2122" Test: test_lwgeom_distance_sphere ...passed\n" 2123" Test: test_lwgeom_check_geodetic ...passed\n" 2124" Test: test_gserialized_from_lwgeom ...passed\n" 2125" Test: test_spheroid_distance ...passed\n" 2126" Test: test_spheroid_area ...passed\n" 2127" Test: test_lwpoly_covers_point2d ...passed\n" 2128" Test: test_gbox_utils ...passed\n" 2129" Test: test_vector_angle ...passed\n" 2130" Test: test_vector_rotate ...passed\n" 2131" Test: test_lwgeom_segmentize_sphere ...passed\n" 2132" Test: test_ptarray_contains_point_sphere ...passed\n" 2133" Test: test_ptarray_contains_point_sphere_iowa ...passed\n" 2134"Suite: GEOS\n" 2135" Test: test_geos_noop ...passed\n" 2136" Test: test_geos_subdivide ...passed\n" 2137" Test: test_geos_linemerge ...passed\n" 2138"Suite: Clustering\n" 2139" Test: basic_test ...passed\n" 2140" Test: nonsequential_test ...passed\n" 2141" Test: basic_distance_test ...passed\n" 2142" Test: single_input_test ...passed\n" 2143" Test: empty_inputs_test ...passed\n" 2144"Suite: Clustering Union-Find\n" 2145" Test: test_unionfind_create ...passed\n" 2146" Test: test_unionfind_union ...passed\n" 2147" Test: test_unionfind_ordered_by_cluster ...passed\n" 2148"Suite: homogenize\n" 2149" Test: test_coll_point ...passed\n" 2150" Test: test_coll_line ...passed\n" 2151" Test: test_coll_poly ...passed\n" 2152" Test: test_coll_coll ...passed\n" 2153" Test: test_geom ...passed\n" 2154" Test: test_coll_curve ...passed\n" 2155"Suite: encoded_polyline_input\n" 2156" Test: in_encoded_polyline_test_geoms ...passed\n" 2157" Test: in_encoded_polyline_test_precision ...passed\n" 2158"Suite: geojson_input\n" 2159" Test: in_geojson_test_srid ...passed\n" 2160" Test: in_geojson_test_bbox ...passed\n" 2161" Test: in_geojson_test_geoms ...passed\n" 2162"Suite: twkb_input\n" 2163" Test: test_twkb_in_point ...passed\n" 2164" Test: test_twkb_in_linestring ...passed\n" 2165" Test: test_twkb_in_polygon ...passed\n" 2166" Test: test_twkb_in_multipoint ...passed\n" 2167" Test: test_twkb_in_multilinestring ...passed\n" 2168" Test: test_twkb_in_multipolygon ...passed\n" 2169" Test: test_twkb_in_collection ...passed\n" 2170" Test: test_twkb_in_precision ...passed\n" 2171"Suite: serialization/deserialization\n" 2172" Test: test_typmod_macros ...passed\n" 2173" Test: test_flags_macros ...passed\n" 2174" Test: test_serialized_srid ...passed\n" 2175" Test: test_gserialized_from_lwgeom_size ...passed\n" 2176" Test: test_gbox_serialized_size ...passed\n" 2177" Test: test_lwgeom_from_gserialized ...passed\n" 2178" Test: test_lwgeom_count_vertices ...passed\n" 2179" Test: test_on_gser_lwgeom_count_vertices ...passed\n" 2180" Test: test_geometry_type_from_string ...passed\n" 2181" Test: test_lwcollection_extract ...passed\n" 2182" Test: test_lwgeom_free ...passed\n" 2183" Test: test_lwgeom_flip_coordinates ...passed\n" 2184" Test: test_f2d ...passed\n" 2185" Test: test_lwgeom_clone ...passed\n" 2186" Test: test_lwgeom_force_clockwise ...passed\n" 2187" Test: test_lwgeom_calculate_gbox ...passed\n" 2188" Test: test_lwgeom_is_empty ...passed\n" 2189" Test: test_lwgeom_same ...passed\n" 2190" Test: test_lwline_from_lwmpoint ...passed\n" 2191" Test: test_lwgeom_as_curve ...passed\n" 2192" Test: test_lwgeom_scale ...passed\n" 2193" Test: test_gserialized_is_empty ...passed\n" 2194" Test: test_gbox_same_2d ...passed\n" 2195"Suite: measures\n" 2196" Test: test_mindistance2d_tolerance ...passed\n" 2197" Test: test_rect_tree_contains_point ...passed\n" 2198" Test: test_rect_tree_intersects_tree ...passed\n" 2199" Test: test_lwgeom_segmentize2d ...passed\n" 2200" Test: test_lwgeom_locate_along ...passed\n" 2201" Test: test_lw_dist2d_pt_arc ...passed\n" 2202" Test: test_lw_dist2d_seg_arc ...passed\n" 2203" Test: test_lw_dist2d_arc_arc ...passed\n" 2204" Test: test_lw_arc_length ...passed\n" 2205" Test: test_lw_dist2d_pt_ptarrayarc ...passed\n" 2206" Test: test_lw_dist2d_ptarray_ptarrayarc ...passed\n" 2207" Test: test_lwgeom_tcpa ...passed\n" 2208" Test: test_lwgeom_is_trajectory ...passed\n" 2209"Suite: effectivearea\n" 2210" Test: do_test_lwgeom_effectivearea_lines ...passed\n" 2211" Test: do_test_lwgeom_effectivearea_polys ...passed\n" 2212"Suite: miscellaneous\n" 2213" Test: test_misc_force_2d ...passed\n" 2214" Test: test_misc_simplify ...passed\n" 2215" Test: test_misc_count_vertices ...passed\n" 2216" Test: test_misc_area ...passed\n" 2217" Test: test_misc_wkb ...passed\n" 2218" Test: test_grid ...passed\n" 2219"Suite: noding\n" 2220" Test: test_lwgeom_node ...passed\n" 2221"Suite: encoded_polyline_output\n" 2222" Test: out_encoded_polyline_test_geoms ...passed\n" 2223" Test: out_encoded_polyline_test_srid ...passed\n" 2224" Test: out_encoded_polyline_test_precision ...passed\n" 2225"Suite: geojson_output\n" 2226" Test: out_geojson_test_precision ...passed\n" 2227" Test: out_geojson_test_dims ...passed\n" 2228" Test: out_geojson_test_srid ...passed\n" 2229" Test: out_geojson_test_bbox ...passed\n" 2230" Test: out_geojson_test_geoms ...passed\n" 2231"Suite: gml_output\n" 2232" Test: out_gml_test_precision ...passed\n" 2233" Test: out_gml_test_srid ...passed\n" 2234" Test: out_gml_test_dims ...passed\n" 2235" Test: out_gml_test_geodetic ...passed\n" 2236" Test: out_gml_test_geoms ...passed\n" 2237" Test: out_gml_test_geoms_prefix ...passed\n" 2238" Test: out_gml_test_geoms_nodims ...passed\n" 2239" Test: out_gml2_extent ...passed\n" 2240" Test: out_gml3_extent ...passed\n" 2241"Suite: kml_output\n" 2242" Test: out_kml_test_precision ...passed\n" 2243" Test: out_kml_test_dims ...passed\n" 2244" Test: out_kml_test_geoms ...passed\n" 2245" Test: out_kml_test_prefix ...passed\n" 2246"Suite: svg_output\n" 2247" Test: out_svg_test_precision ...passed\n" 2248" Test: out_svg_test_dims ...passed\n" 2249" Test: out_svg_test_relative ...passed\n" 2250" Test: out_svg_test_geoms ...passed\n" 2251" Test: out_svg_test_srid ...passed\n" 2252"Suite: x3d_output\n" 2253" Test: out_x3d3_test_precision ...passed\n" 2254" Test: out_x3d3_test_geoms ...passed\n" 2255" Test: out_x3d3_test_option ...passed\n" 2256"Suite: ptarray\n" 2257" Test: test_ptarray_append_point ...passed\n" 2258" Test: test_ptarray_append_ptarray ...passed\n" 2259" Test: test_ptarray_locate_point ...passed\n" 2260" Test: test_ptarray_isccw ...passed\n" 2261" Test: test_ptarray_signed_area ...passed\n" 2262" Test: test_ptarray_unstroke ...passed\n" 2263" Test: test_ptarray_insert_point ...passed\n" 2264" Test: test_ptarray_contains_point ...passed\n" 2265" Test: test_ptarrayarc_contains_point ...passed\n" 2266" Test: test_ptarray_scale ...passed\n" 2267"Suite: printing\n" 2268" Test: test_lwprint_default_format ...passed\n" 2269" Test: test_lwprint_format_orders ...passed\n" 2270" Test: test_lwprint_optional_format ...passed\n" 2271" Test: test_lwprint_oddball_formats ...passed\n" 2272" Test: test_lwprint_bad_formats ...passed\n" 2273"Suite: SFCGAL\n" 2274" Test: test_sfcgal_noop ...passed\n" 2275"Suite: split\n" 2276" Test: test_lwline_split_by_point_to ...passed\n" 2277" Test: test_lwgeom_split ...passed\n" 2278"Suite: stringbuffer\n" 2279" Test: test_stringbuffer_append ...passed\n" 2280" Test: test_stringbuffer_aprintf ...passed\n" 2281"Suite: surface\n" 2282" Test: triangle_parse ...passed\n" 2283" Test: tin_parse ...passed\n" 2284" Test: polyhedralsurface_parse ...passed\n" 2285" Test: surface_dimension ...passed\n" 2286"Suite: Internal Spatial Trees\n" 2287" Test: test_tree_circ_create ...passed\n" 2288" Test: test_tree_circ_pip ...passed\n" 2289" Test: test_tree_circ_pip2 ...passed\n" 2290" Test: test_tree_circ_distance ...passed\n" 2291" Test: test_tree_circ_distance_threshold ...passed\n" 2292"Suite: triangulate\n" 2293" Test: test_lwgeom_delaunay_triangulation ...passed\n" 2294"Suite: twkb_output\n" 2295" Test: test_twkb_out_point ...passed\n" 2296" Test: test_twkb_out_linestring ...passed\n" 2297" Test: test_twkb_out_polygon ...passed\n" 2298" Test: test_twkb_out_multipoint ...passed\n" 2299" Test: test_twkb_out_multilinestring ...passed\n" 2300" Test: test_twkb_out_multipolygon ...passed\n" 2301" Test: test_twkb_out_collection ...passed\n" 2302" Test: test_twkb_out_idlist ...passed\n" 2303"Suite: varint\n" 2304" Test: test_zigzag ...passed\n" 2305" Test: test_varint ...passed\n" 2306" Test: test_varint_roundtrip ...passed\n" 2307"Suite: wkb_input\n" 2308" Test: test_wkb_in_point ...passed\n" 2309" Test: test_wkb_in_linestring ...passed\n" 2310" Test: test_wkb_in_polygon ...passed\n" 2311" Test: test_wkb_in_multipoint ...passed\n" 2312" Test: test_wkb_in_multilinestring ...passed\n" 2313" Test: test_wkb_in_multipolygon ...passed\n" 2314" Test: test_wkb_in_collection ...passed\n" 2315" Test: test_wkb_in_circularstring ...passed\n" 2316" Test: test_wkb_in_compoundcurve ...passed\n" 2317" Test: test_wkb_in_curvpolygon ...passed\n" 2318" Test: test_wkb_in_multicurve ...passed\n" 2319" Test: test_wkb_in_multisurface ...passed\n" 2320" Test: test_wkb_in_malformed ...passed\n" 2321"Suite: wkb_output\n" 2322" Test: test_wkb_out_point ...passed\n" 2323" Test: test_wkb_out_linestring ...passed\n" 2324" Test: test_wkb_out_polygon ...passed\n" 2325" Test: test_wkb_out_multipoint ...passed\n" 2326" Test: test_wkb_out_multilinestring ...passed\n" 2327" Test: test_wkb_out_multipolygon ...passed\n" 2328" Test: test_wkb_out_collection ...passed\n" 2329" Test: test_wkb_out_circularstring ...passed\n" 2330" Test: test_wkb_out_compoundcurve ...passed\n" 2331" Test: test_wkb_out_curvpolygon ...passed\n" 2332" Test: test_wkb_out_multicurve ...passed\n" 2333" Test: test_wkb_out_multisurface ...passed\n" 2334" Test: test_wkb_out_polyhedralsurface ...passed\n" 2335"Suite: wkt_input\n" 2336" Test: test_wkt_in_point ...passed\n" 2337" Test: test_wkt_in_linestring ...passed\n" 2338" Test: test_wkt_in_polygon ...passed\n" 2339" Test: test_wkt_in_multipoint ...passed\n" 2340" Test: test_wkt_in_multilinestring ...passed\n" 2341" Test: test_wkt_in_multipolygon ...passed\n" 2342" Test: test_wkt_in_collection ...passed\n" 2343" Test: test_wkt_in_circularstring ...passed\n" 2344" Test: test_wkt_in_compoundcurve ...passed\n" 2345" Test: test_wkt_in_curvpolygon ...passed\n" 2346" Test: test_wkt_in_multicurve ...passed\n" 2347" Test: test_wkt_in_multisurface ...passed\n" 2348" Test: test_wkt_in_tin ...passed\n" 2349" Test: test_wkt_in_polyhedralsurface ...passed\n" 2350" Test: test_wkt_in_errlocation ...passed\n" 2351"Suite: wkt_output\n" 2352" Test: test_wkt_out_point ...passed\n" 2353" Test: test_wkt_out_linestring ...passed\n" 2354" Test: test_wkt_out_polygon ...passed\n" 2355" Test: test_wkt_out_multipoint ...passed\n" 2356" Test: test_wkt_out_multilinestring ...passed\n" 2357" Test: test_wkt_out_multipolygon ...passed\n" 2358" Test: test_wkt_out_collection ...passed\n" 2359" Test: test_wkt_out_circularstring ...passed\n" 2360" Test: test_wkt_out_compoundcurve ...passed\n" 2361" Test: test_wkt_out_curvpolygon ...passed\n" 2362" Test: test_wkt_out_multicurve ...passed\n" 2363" Test: test_wkt_out_multisurface ...passed\n" 2364"\n" 2365"Run Summary: Type Total Ran Passed Failed Inactive\n" 2366" suites 38 38 n/a 0 0\n" 2367" tests 251 251 251 0 0\n" 2368" asserts 2468 2468 2468 0 n/a\n" 2369"\n" 2370"Elapsed time = 0.298 seconds\n" 2371"\n" 2372"Creating database 'postgis_reg'\n" 2373"Loading PostGIS into 'postgis_reg'\n" 2374" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/" 2375"postgis/postgis.sql\n" 2376" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/" 2377"postgis/postgis_comments.sql\n" 2378"Loading SFCGAL into 'postgis_reg'\n" 2379" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/" 2380"postgis/sfcgal.sql\n" 2381" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/" 2382"postgis/sfcgal_comments.sql\n" 2383"PostgreSQL 9.4.4, compiled by Visual C++ build 1800, 32-bit\n" 2384" Postgis 2.2.0dev - r13980 - 2015-08-23 06:13:07\n" 2385" scripts 2.2.0dev r13980\n" 2386" GEOS: 3.5.0-CAPI-1.9.0 r4088\n" 2387" PROJ: Rel. 4.9.1, 04 March 2015\n" 2388" SFCGAL: 1.1.0\n" 2389"\n" 2390"Running tests\n" 2391"\n" 2392" loader/Point .............. ok\n" 2393" loader/PointM .............. ok\n" 2394" loader/PointZ .............. ok\n" 2395" loader/MultiPoint .............. ok\n" 2396" loader/MultiPointM .............. ok\n" 2397" loader/MultiPointZ .............. ok\n" 2398" loader/Arc .............. ok\n" 2399" loader/ArcM .............. ok\n" 2400" loader/ArcZ .............. ok\n" 2401" loader/Polygon .............. ok\n" 2402" loader/PolygonM .............. ok\n" 2403" loader/PolygonZ .............. ok\n" 2404" loader/TSTPolygon ......... ok\n" 2405" loader/TSIPolygon ......... ok\n" 2406" loader/TSTIPolygon ......... ok\n" 2407" loader/PointWithSchema ..... ok\n" 2408" loader/NoTransPoint ......... ok\n" 2409" loader/NotReallyMultiPoint ......... ok\n" 2410" loader/MultiToSinglePoint ......... ok\n" 2411" loader/ReprojectPts ........ ok\n" 2412" loader/ReprojectPtsGeog ........ ok\n" 2413" loader/Latin1 .... ok\n" 2414" loader/Latin1-implicit .... ok\n" 2415" loader/mfile .... ok\n" 2416" dumper/literalsrid ....... ok\n" 2417" dumper/realtable ....... ok\n" 2418" affine .. ok\n" 2419" bestsrid .. ok\n" 2420" binary .. ok\n" 2421" boundary .. ok\n" 2422" cluster .. ok\n" 2423" concave_hull .. ok\n" 2424" ctors .. ok\n" 2425" dump .. ok\n" 2426" dumppoints .. ok\n" 2427" empty .. ok\n" 2428" forcecurve .. ok\n" 2429" geography .. ok\n" 2430" in_geohash .. ok\n" 2431" in_gml .. ok\n" 2432" in_kml .. ok\n" 2433" in_encodedpolyline .. ok\n" 2434" iscollection .. ok\n" 2435" legacy .. ok\n" 2436" long_xact .. ok\n" 2437" lwgeom_regress .. ok\n" 2438" measures .. ok\n" 2439" operators .. ok\n" 2440" out_geometry .. ok\n" 2441" out_geography .. ok\n" 2442" polygonize .. ok\n" 2443" polyhedralsurface .. ok\n" 2444" postgis_type_name .. ok\n" 2445" regress .. ok\n" 2446" regress_bdpoly .. ok\n" 2447" regress_index .. ok\n" 2448" regress_index_nulls .. ok\n" 2449" regress_management .. ok\n" 2450" regress_selectivity .. ok\n" 2451" regress_lrs .. ok\n" 2452" regress_ogc .. ok\n" 2453" regress_ogc_cover .. ok\n" 2454" regress_ogc_prep .. ok\n" 2455" regress_proj .. ok\n" 2456" relate .. ok\n" 2457" remove_repeated_points .. ok\n" 2458" removepoint .. ok\n" 2459" setpoint .. ok\n" 2460" simplify .. ok\n" 2461" simplifyvw .. ok\n" 2462" size .. ok\n" 2463" snaptogrid .. ok\n" 2464" split .. ok\n" 2465" sql-mm-serialize .. ok\n" 2466" sql-mm-circularstring .. ok\n" 2467" sql-mm-compoundcurve .. ok\n" 2468" sql-mm-curvepoly .. ok\n" 2469" sql-mm-general .. ok\n" 2470" sql-mm-multicurve .. ok\n" 2471" sql-mm-multisurface .. ok\n" 2472" swapordinates .. ok\n" 2473" summary .. ok\n" 2474" temporal .. ok\n" 2475" tickets .. ok\n" 2476" twkb .. ok\n" 2477" typmod .. ok\n" 2478" wkb .. ok\n" 2479" wkt .. ok\n" 2480" wmsservers .. ok\n" 2481" knn .. ok\n" 2482" hausdorff .. ok\n" 2483" regress_buffer_params .. ok\n" 2484" offsetcurve .. ok\n" 2485" relatematch .. ok\n" 2486" isvaliddetail .. ok\n" 2487" sharedpaths .. ok\n" 2488" snap .. ok\n" 2489" node .. ok\n" 2490" unaryunion .. ok\n" 2491" clean .. ok\n" 2492" relate_bnr .. ok\n" 2493" delaunaytriangles .. ok\n" 2494" clipbybox2d .. ok\n" 2495" subdivide .. ok\n" 2496" in_geojson .. ok\n" 2497" regress_sfcgal .. ok\n" 2498" sfcgal/empty .. ok\n" 2499" sfcgal/geography .. ok\n" 2500" sfcgal/legacy .. ok\n" 2501" sfcgal/measures .. ok\n" 2502" sfcgal/regress_ogc_prep .. ok\n" 2503" sfcgal/regress_ogc .. ok\n" 2504" sfcgal/regress .. ok\n" 2505" sfcgal/tickets .. ok\n" 2506" sfcgal/concave_hull .. ok\n" 2507" sfcgal/wmsservers .. ok\n" 2508" sfcgal/approximatemedialaxis .. ok\n" 2509" uninstall . /projects/postgis/branches/2.2/regress/00-regress-install/" 2510"share/contrib/postgis/uninstall_sfcgal.sql\n" 2511" /projects/postgis/branches/2.2/regress/00-regress-install/share/contrib/" 2512"postgis/uninstall_postgis.sql\n" 2513". ok (4336)\n" 2514"\n" 2515"Run tests: 118\n" 2516"Failed: 0\n" 2517"\n" 2518"-- if you built --with-gui, you should see this too\n" 2519"\n" 2520" CUnit - A unit testing framework for C - Version 2.1-2\n" 2521" http://cunit.sourceforge.net/\n" 2522"\n" 2523"\n" 2524"Suite: Shapefile Loader File shp2pgsql Test\n" 2525" Test: test_ShpLoaderCreate() ...passed\n" 2526" Test: test_ShpLoaderDestroy() ...passed\n" 2527"Suite: Shapefile Loader File pgsql2shp Test\n" 2528" Test: test_ShpDumperCreate() ...passed\n" 2529" Test: test_ShpDumperDestroy() ...passed\n" 2530"\n" 2531"Run Summary: Type Total Ran Passed Failed Inactive\n" 2532" suites 2 2 n/a 0 0\n" 2533" tests 4 4 4 0 0\n" 2534" asserts 4 4 4 0 n/a" 2535 2536#. Tag: para 2537#: installation.xml:710 2538#, no-c-format 2539msgid "" 2540"The <varname>postgis_tiger_geocoder</varname> and " 2541"<varname>address_standardizer</varname> extensions, currenlty only support " 2542"the standard PostgreSQL installcheck. To test these use the below. Note: the " 2543"make install is not necessary if you already did make install at root of " 2544"PostGIS code folder." 2545msgstr "" 2546 2547#. Tag: para 2548#: installation.xml:711 2549#, no-c-format 2550msgid "For address_standardizer:" 2551msgstr "" 2552 2553#. Tag: programlisting 2554#: installation.xml:712 2555#, no-c-format 2556msgid "" 2557"cd extensions/address_standardizer\n" 2558"make install\n" 2559"make installcheck" 2560msgstr "" 2561 2562#. Tag: para 2563#: installation.xml:714 2564#, no-c-format 2565msgid "Output should look like:" 2566msgstr "" 2567 2568#. Tag: screen 2569#: installation.xml:715 2570#, no-c-format 2571msgid "" 2572"============== dropping database \"contrib_regression\" ==============\n" 2573"DROP DATABASE\n" 2574"============== creating database \"contrib_regression\" ==============\n" 2575"CREATE DATABASE\n" 2576"ALTER DATABASE\n" 2577"============== running regression test queries ==============\n" 2578"test test-init-extensions ... ok\n" 2579"test test-parseaddress ... ok\n" 2580"test test-standardize_address_1 ... ok\n" 2581"test test-standardize_address_2 ... ok\n" 2582"\n" 2583"=====================\n" 2584" All 4 tests passed.\n" 2585"=====================" 2586msgstr "" 2587 2588#. Tag: para 2589#: installation.xml:717 2590#, no-c-format 2591msgid "" 2592"For tiger geocoder, make sure you have postgis and fuzzystrmatch extensions " 2593"available in your PostgreSQL instance. The address_standardizer tests will " 2594"also kick in if you built postgis with address_standardizer support:" 2595msgstr "" 2596 2597#. Tag: programlisting 2598#: installation.xml:718 2599#, no-c-format 2600msgid "" 2601"cd extensions/postgis_tiger_geocoder\n" 2602"make install\n" 2603"make installcheck" 2604msgstr "" 2605 2606#. Tag: para 2607#: installation.xml:719 2608#, no-c-format 2609msgid "output should look like:" 2610msgstr "" 2611 2612#. Tag: screen 2613#: installation.xml:720 2614#, no-c-format 2615msgid "" 2616"============== dropping database \"contrib_regression\" ==============\n" 2617"DROP DATABASE\n" 2618"============== creating database \"contrib_regression\" ==============\n" 2619"CREATE DATABASE\n" 2620"ALTER DATABASE\n" 2621"============== installing fuzzystrmatch ==============\n" 2622"CREATE EXTENSION\n" 2623"============== installing postgis ==============\n" 2624"CREATE EXTENSION\n" 2625"============== installing postgis_tiger_geocoder ==============\n" 2626"CREATE EXTENSION\n" 2627"============== installing address_standardizer ==============\n" 2628"CREATE EXTENSION\n" 2629"============== running regression test queries ==============\n" 2630"test test-normalize_address ... ok\n" 2631"test test-pagc_normalize_address ... ok\n" 2632"\n" 2633"=====================\n" 2634"All 2 tests passed.\n" 2635"=====================" 2636msgstr "" 2637 2638#. Tag: title 2639#: installation.xml:724 2640#, no-c-format 2641msgid "Installation" 2642msgstr "Instalación" 2643 2644#. Tag: para 2645#: installation.xml:726 2646#, no-c-format 2647msgid "To install PostGIS, type" 2648msgstr "Para instalar PostGIS entre" 2649 2650#. Tag: command 2651#: installation.xml:731 2652#, no-c-format 2653msgid "make install" 2654msgstr "make install" 2655 2656#. Tag: para 2657#: installation.xml:734 2658#, no-c-format 2659msgid "" 2660"This will copy the PostGIS installation files into their appropriate " 2661"subdirectory specified by the <command>--prefix</command> configuration " 2662"parameter. In particular:" 2663msgstr "" 2664"Esto copiará los ficheros de instalación de PostGIS en el subdirectorio " 2665"especificado por el parámetro de configuración <command>--prefix</command> " 2666"del comando . En particular:" 2667 2668#. Tag: para 2669#: installation.xml:742 2670#, no-c-format 2671msgid "" 2672"The loader and dumper binaries are installed in <filename>[prefix]/bin</" 2673"filename>." 2674msgstr "" 2675"Los archivos binarios de carga y dumper estarán instalados en " 2676"<filename>[prefix]/bin</filename>." 2677 2678#. Tag: para 2679#: installation.xml:749 2680#, no-c-format 2681msgid "" 2682"The SQL files, such as <filename>postgis.sql</filename>, are installed in " 2683"<filename>[prefix]/share/contrib</filename>." 2684msgstr "" 2685"Los archivos SQL, tal como <filename>postgis.sql</filename>, están " 2686"instalados en <filename>[prefix]/share/contrib</filename>." 2687 2688#. Tag: para 2689#: installation.xml:756 2690#, no-c-format 2691msgid "" 2692"The PostGIS libraries are installed in <filename>[prefix]/lib</filename>." 2693msgstr "" 2694"Las librerías de PostGIS estarán instaladas en <filename>[prefix]/lib</" 2695"filename>." 2696 2697#. Tag: para 2698#: installation.xml:763 2699#, no-c-format 2700msgid "" 2701"If you previously ran the <command>make comments</command> command to " 2702"generate the <filename>postgis_comments.sql</filename>, " 2703"<filename>raster_comments.sql</filename> file, install the sql file by " 2704"running" 2705msgstr "" 2706"Si has ejecutado el comando <command>make comments</command> previamente " 2707"para generar los ficheros <filename>postgis_comments.sql</filename>, " 2708"<filename>raster_comments.sql</filename>, instala los ficheros sql " 2709"ejecutando:" 2710 2711#. Tag: command 2712#: installation.xml:770 2713#, no-c-format 2714msgid "make comments-install" 2715msgstr "make comments-install" 2716 2717#. Tag: para 2718#: installation.xml:774 2719#, no-c-format 2720msgid "" 2721"<filename>postgis_comments.sql</filename>, <filename>raster_comments.sql</" 2722"filename>, <filename>topology_comments.sql</filename> was separated from the " 2723"typical build and installation targets since with it comes the extra " 2724"dependency of <command>xsltproc</command>." 2725msgstr "" 2726"<filename>postgis_comments.sql</filename>, <filename>raster_comments.sql</" 2727"filename>, <filename>topology_comments.sql</filename> han sido separados de " 2728"la compilación y de la instalación típicos ya que tienen una dependencia " 2729"extra de la librería <command>xsltproc</command>." 2730 2731#. Tag: title 2732#: installation.xml:784 2733#, no-c-format 2734msgid "Creating a spatial database using EXTENSIONS" 2735msgstr "Crear una base de datos espacial utilizando EXTENSIONS" 2736 2737#. Tag: para 2738#: installation.xml:786 2739#, no-c-format 2740msgid "" 2741"If you are using PostgreSQL 9.1+ and have compiled and installed the " 2742"extensions/ postgis modules, you can create a spatial database the new way." 2743msgstr "" 2744"Si estas utilizando PostgreSQL 9.1+ y has compilado e instalado los módulos/" 2745"extensión PostGIS, puedes crear una base de datos espacial de otra manera." 2746 2747#. Tag: command 2748#: installation.xml:792 installation.xml:829 2749#, no-c-format 2750msgid "createdb [yourdatabase]" 2751msgstr "createdb [subasededatos]" 2752 2753#. Tag: para 2754#: installation.xml:795 2755#, no-c-format 2756msgid "" 2757"The core postgis extension installs PostGIS geometry, geography, raster, " 2758"spatial_ref_sys and all the functions and comments with a simple: " 2759"<programlisting>CREATE EXTENSION postgis;</programlisting> command." 2760msgstr "" 2761"El núcleo de la extensión postgis, instala geometry, geography, raster, " 2762"spatial_ref_sys y todos los comentarios de las funciones PostGIS con un " 2763"simple comando:<programlisting>CREATE EXTENSION postgis;</programlisting>." 2764 2765#. Tag: command 2766#: installation.xml:801 2767#, no-c-format 2768msgid "psql -d [yourdatabase] -c \"CREATE EXTENSION postgis;\"" 2769msgstr "psql -d [yourdatabase] -c \"CREATE EXTENSION postgis;\"" 2770 2771#. Tag: para 2772#: installation.xml:804 2773#, no-c-format 2774msgid "" 2775"Topology is packaged as a separate extension and installable with command:" 2776msgstr "" 2777"Topology esta compilado como una extensión separada y se puede instalar con " 2778"el comando:" 2779 2780#. Tag: command 2781#: installation.xml:809 2782#, no-c-format 2783msgid "psql -d [yourdatabase] -c \"CREATE EXTENSION postgis_topology;\"" 2784msgstr "psql -d [yourdatabase] -c \"CREATE EXTENSION postgis_topology;\"" 2785 2786#. Tag: para 2787#: installation.xml:812 installation.xml:909 2788#, no-c-format 2789msgid "" 2790"If you plan to restore an old backup from prior versions in this new db, run:" 2791msgstr "" 2792"Si estas pensando en restaurar una copia de seguridad de una vieja base de " 2793"datos desde una versión anterior en la nueva base de datos, ejecuta:" 2794 2795#. Tag: command 2796#: installation.xml:813 installation.xml:910 2797#, no-c-format 2798msgid "psql -d [yourdatabase] -f legacy.sql" 2799msgstr "psql -d [yourdatabase] -f legacy.sql" 2800 2801#. Tag: para 2802#: installation.xml:814 2803#, no-c-format 2804msgid "" 2805"If you need legacy functions, you'll need to reinstall the legacy.sql script " 2806"whenever you upgrade the minor version of PostGIS. E.g. if you upgraded from " 2807"2.4.3 to 2.5.0, then you need to reinstall the legacy.sql packaged with " 2808"2.5.0. This is because some of the functions make reference to the library " 2809"and the library is named with the minor in it." 2810msgstr "" 2811 2812#. Tag: para 2813#: installation.xml:817 installation.xml:914 2814#, no-c-format 2815msgid "" 2816"You can later run <filename>uninstall_legacy.sql</filename> to get rid of " 2817"the deprecated functions after you are done with restoring and cleanup." 2818msgstr "" 2819"Después podrás ejecutar <filename>uninstall_legacy.sql</filename> para " 2820"obtener el rid de las funciones obsoletas después de haber restaurado y " 2821"limpiado." 2822 2823#. Tag: title 2824#: installation.xml:821 2825#, no-c-format 2826msgid "Create a spatially-enabled database without using extensions" 2827msgstr "" 2828 2829#. Tag: para 2830#: installation.xml:823 2831#, no-c-format 2832msgid "" 2833"This is generally only needed if you built-PostGIS without raster support. " 2834"Since raster functions are part of the postgis extension, extension support " 2835"is not enabled if PostGIS is built without raster." 2836msgstr "" 2837 2838#. Tag: para 2839#: installation.xml:824 2840#, no-c-format 2841msgid "" 2842"The first step in creating a PostGIS database is to create a simple " 2843"PostgreSQL database." 2844msgstr "" 2845"El primer paso en la creación de una base de datos PostGIS es crear una " 2846"simple base de datos PostgreSQL." 2847 2848#. Tag: para 2849#: installation.xml:832 2850#, no-c-format 2851msgid "" 2852"Many of the PostGIS functions are written in the PL/pgSQL procedural " 2853"language. As such, the next step to create a PostGIS database is to enable " 2854"the PL/pgSQL language in your new database. This is accomplish by the " 2855"command below command. For PostgreSQL 8.4+, this is generally already " 2856"installed" 2857msgstr "" 2858"Varias de la funciones PostGIS están escritas en el lenguaje de " 2859"procedimientos PL/pgSQL. Como tal, el siguiente paso para crear una base de " 2860"datos PostGIS es habilitar el lenguaje PL/pgSQL en nuestra nueva base de " 2861"datos. Eso se hace con el comando siguiente. Para PostgreSQL 8.4+ está " 2862"normalmente ya instalado." 2863 2864#. Tag: command 2865#: installation.xml:840 2866#, no-c-format 2867msgid "createlang plpgsql [yourdatabase]" 2868msgstr "createlang plpgsql [subasededatos]" 2869 2870#. Tag: para 2871#: installation.xml:843 2872#, no-c-format 2873msgid "" 2874"Now load the PostGIS object and function definitions into your database by " 2875"loading the <filename>postgis.sql</filename> definitions file (located in " 2876"<filename>[prefix]/share/contrib</filename> as specified during the " 2877"configuration step)." 2878msgstr "" 2879"Ahora carga los objetos y la definición de funciones en tu base de datos " 2880"cargando el fichero de definiciones <filename>postgis.sql</filename> (este " 2881"fichero se encuentra en <filename>[prefix]/share/contrib</filename> como se " 2882"especificó durante la etapa de configuración)." 2883 2884#. Tag: command 2885#: installation.xml:851 2886#, no-c-format 2887msgid "psql -d [yourdatabase] -f postgis.sql" 2888msgstr "psql -d [yourdatabase] -f postgis.sql" 2889 2890#. Tag: para 2891#: installation.xml:854 2892#, no-c-format 2893msgid "" 2894"For a complete set of EPSG coordinate system definition identifiers, you can " 2895"also load the <filename>spatial_ref_sys.sql</filename> definitions file and " 2896"populate the <varname>spatial_ref_sys</varname> table. This will permit you " 2897"to perform ST_Transform() operations on geometries." 2898msgstr "" 2899"Para tener un juego completo de definiciones de sistemas de coordinas EPSG, " 2900"también se puede cargar el fichero de definiciones <filename>spatial_ref_sys." 2901"sql</filename> y rellenar tabla <varname>spatial_ref_sys</varname>. Esto te " 2902"permitida hacer operaciones de transformación ST_Transform() en las " 2903"geometrías." 2904 2905#. Tag: command 2906#: installation.xml:862 2907#, no-c-format 2908msgid "psql -d [yourdatabase] -f spatial_ref_sys.sql" 2909msgstr "psql -d [yourdatabase] -f spatial_ref_sys.sql" 2910 2911#. Tag: para 2912#: installation.xml:865 2913#, no-c-format 2914msgid "" 2915"If you wish to add comments to the PostGIS functions, the final step is to " 2916"load the <filename>postgis_comments.sql</filename> into your spatial " 2917"database. The comments can be viewed by simply typing <command>\\dd " 2918"[function_name]</command> from a <command>psql</command> terminal window." 2919msgstr "" 2920"Si quieres añadir los comentarios de las funciones PostGIS, el paso final es " 2921"cargar el fichero <filename>postgis_comments.sql</filename> en la base de " 2922"datos. Para ver los comentarios, simplemente ejecuta el comando <command>" 2923"\\dd [function_name]</command> en un terminal psql." 2924 2925#. Tag: command 2926#: installation.xml:873 2927#, no-c-format 2928msgid "psql -d [yourdatabase] -f postgis_comments.sql" 2929msgstr "psql -d [yourdatabase] -f postgis_comments.sql" 2930 2931#. Tag: para 2932#: installation.xml:876 2933#, no-c-format 2934msgid "Install raster support" 2935msgstr "Instalar el soporte raster" 2936 2937#. Tag: command 2938#: installation.xml:881 2939#, no-c-format 2940msgid "psql -d [yourdatabase] -f rtpostgis.sql" 2941msgstr "psql -d [yourdatabase] -f rtpostgis.sql" 2942 2943#. Tag: para 2944#: installation.xml:884 2945#, no-c-format 2946msgid "" 2947"Install raster support comments. This will provide quick help info for each " 2948"raster function using psql or PgAdmin or any other PostgreSQL tool that can " 2949"show function comments" 2950msgstr "" 2951"Instala los comentarios de soporte raster. Esto te dará información de ayuda " 2952"de forma rápida para cada función raster utilizando psql, pgAdmin o " 2953"cualquier otra herramienta PostgreSQL que permita ver los comentarios de las " 2954"funciones." 2955 2956#. Tag: command 2957#: installation.xml:890 2958#, no-c-format 2959msgid "psql -d [yourdatabase] -f raster_comments.sql" 2960msgstr "psql -d [yourdatabase] -f raster_comments.sql" 2961 2962#. Tag: para 2963#: installation.xml:892 2964#, no-c-format 2965msgid "Install topology support" 2966msgstr "Instalar el soporte de topología" 2967 2968#. Tag: command 2969#: installation.xml:897 2970#, no-c-format 2971msgid "psql -d [yourdatabase] -f topology/topology.sql" 2972msgstr "psql -d [yourdatabase] -f topology/topology.sql" 2973 2974#. Tag: para 2975#: installation.xml:900 2976#, no-c-format 2977msgid "" 2978"Install topology support comments. This will provide quick help info for " 2979"each topology function / type using psql or PgAdmin or any other PostgreSQL " 2980"tool that can show function comments" 2981msgstr "" 2982"Instala los comentarios de soporte de topología. Esto te dará información de " 2983"ayuda de forma rápida para cada función red topología utilizando psql, " 2984"pgAdmin o cualquier otra herramienta PostgreSQL que permita ver los " 2985"comentarios de las funciones." 2986 2987#. Tag: command 2988#: installation.xml:906 2989#, no-c-format 2990msgid "psql -d [yourdatabase] -f topology/topology_comments.sql" 2991msgstr "psql -d [yourdatabase] -f topology/topology_comments.sql" 2992 2993#. Tag: para 2994#: installation.xml:911 2995#, no-c-format 2996msgid "" 2997"There is an alternative <filename>legacy_minimal.sql</filename> you can run " 2998"instead which will install barebones needed to recover tables and work with " 2999"apps like MapServer and GeoServer. If you have views that use things like " 3000"distance / length etc, you'll need the full blown <filename>legacy.sql</" 3001"filename>" 3002msgstr "" 3003"Hay una alternativa, se puede ejecutar el fichero <filename>legacy_minimal." 3004"sql</filename> que instalará los elementos necesarios para reemplazar tablas " 3005"y que permitida trabajar con aplicaciones como MapServer y GeoServer. Si " 3006"tienes vistas que utilizan funciones tipo distancia/longitud etc, " 3007"necesitaras ejecutar el fichero <filename>legacy.sql</filename> completo." 3008 3009#. Tag: title 3010#: installation.xml:917 3011#, no-c-format 3012msgid "Installing and Using the address standardizer" 3013msgstr "" 3014 3015#. Tag: para 3016#: installation.xml:918 3017#, no-c-format 3018msgid "" 3019"The <code>address_standardizer</code> extension used to be a separate " 3020"package that required separate download. From PostGIS 2.2 on, it is now " 3021"bundled in. For more information about the address_standardize, what it " 3022"does, and how to configure it for your needs, refer to <xref linkend=" 3023"\"Address_Standardizer\"/>." 3024msgstr "" 3025 3026#. Tag: para 3027#: installation.xml:920 3028#, no-c-format 3029msgid "" 3030"This standardizer can be used in conjunction with the PostGIS packaged tiger " 3031"geocoder extension as a replacement for the <xref linkend=\"Normalize_Address" 3032"\"/> discussed. To use as replacement refer to <xref linkend=" 3033"\"tiger_pagc_address_standardizing\"/>. You can also use it as a building " 3034"block for your own geocoder or use it to standardize your addresses for " 3035"easier compare of addresses." 3036msgstr "" 3037 3038#. Tag: para 3039#: installation.xml:924 3040#, no-c-format 3041msgid "" 3042"The address standardizer relies on PCRE which is usually already installed " 3043"on many Nix systems, but you can download the latest at: <ulink url=\"http://" 3044"www.pcre.org\">http://www.pcre.org</ulink>. If during <xref linkend=" 3045"\"installation_configuration\"/>, PCRE is found, then the address " 3046"standardizer extension will automatically be built. If you have a custom " 3047"pcre install you want to use instead, pass to configure <code>--with-" 3048"pcredir=/path/to/pcre</code> where <filename>/path/to/pcre</filename> is the " 3049"root folder for your pcre include and lib directories." 3050msgstr "" 3051 3052#. Tag: para 3053#: installation.xml:927 3054#, no-c-format 3055msgid "" 3056"For Windows users, the PostGIS 2.1+ bundle is packaged with the " 3057"address_standardizer already so no need to compile and can move straight to " 3058"<code>CREATE EXTENSION</code> step." 3059msgstr "" 3060 3061#. Tag: para 3062#: installation.xml:930 3063#, no-c-format 3064msgid "" 3065"Once you have installed, you can connect to your database and run the SQL:" 3066msgstr "" 3067 3068#. Tag: programlisting 3069#: installation.xml:931 3070#, no-c-format 3071msgid "CREATE EXTENSION address_standardizer;" 3072msgstr "CREATE EXTENSION address_standardizer;" 3073 3074#. Tag: para 3075#: installation.xml:933 3076#, no-c-format 3077msgid "The following test requires no rules, gaz, or lex tables" 3078msgstr "" 3079 3080#. Tag: programlisting 3081#: installation.xml:934 3082#, no-c-format 3083msgid "" 3084"SELECT num, street, city, state, zip\n" 3085" FROM parse_address('1 Devonshire Place PH301, Boston, MA 02109');" 3086msgstr "" 3087 3088#. Tag: para 3089#: installation.xml:935 3090#, no-c-format 3091msgid "Output should be" 3092msgstr "" 3093 3094#. Tag: screen 3095#: installation.xml:936 3096#, no-c-format 3097msgid "" 3098"num | street | city | state | zip\n" 3099"-----+------------------------+--------+-------+-------\n" 3100" 1 | Devonshire Place PH301 | Boston | MA | 02109" 3101msgstr "" 3102 3103#. Tag: title 3104#: installation.xml:938 3105#, no-c-format 3106msgid "Installing Regex::Assemble" 3107msgstr "" 3108 3109#. Tag: para 3110#: installation.xml:939 3111#, no-c-format 3112msgid "" 3113"Perl Regex:Assemble is no longer needed for compiling address_standardizer " 3114"extension since the files it generates are part of the source tree. However " 3115"if you need to edit the <filename>usps-st-city-orig.txt</filename> or " 3116"<filename>usps-st-city-orig.txt usps-st-city-adds.tx</filename>, you need to " 3117"rebuild <filename>parseaddress-stcities.h</filename> which does require " 3118"Regex:Assemble." 3119msgstr "" 3120 3121#. Tag: programlisting 3122#: installation.xml:940 3123#, no-c-format 3124msgid "cpan Regexp::Assemble" 3125msgstr "" 3126 3127#. Tag: para 3128#: installation.xml:941 3129#, no-c-format 3130msgid "or if you are on Ubuntu / Debian you might need to do" 3131msgstr "" 3132 3133#. Tag: programlisting 3134#: installation.xml:942 3135#, no-c-format 3136msgid "sudo perl -MCPAN -e \"install Regexp::Assemble\"" 3137msgstr "" 3138 3139#. Tag: title 3140#: installation.xml:947 3141#, no-c-format 3142msgid "Installing, Upgrading Tiger Geocoder and loading data" 3143msgstr "Instalar o actualizar el geocodificador Tiger y cargar datos" 3144 3145#. Tag: para 3146#: installation.xml:949 3147#, no-c-format 3148msgid "" 3149"Extras like Tiger geocoder may not be packaged in your PostGIS distribution. " 3150"If you are missing the tiger geocoder extension or want a newer version than " 3151"what your install comes with, then use the <filename>share/extension/" 3152"postgis_tiger_geocoder.*</filename> files from the packages in <ulink url=" 3153"\"http://postgis.net/windows_downloads/\">Windows Unreleased Versions</" 3154"ulink> section for your version of PostgreSQL. Although these packages are " 3155"for windows, the postgis_tiger_geocoder extension files will work on any OS " 3156"since the extension is an SQL/plpgsql only extension." 3157msgstr "" 3158 3159#. Tag: title 3160#: installation.xml:953 3161#, no-c-format 3162msgid "Tiger Geocoder Enabling your PostGIS database: Using Extension" 3163msgstr "" 3164 3165#. Tag: para 3166#: installation.xml:954 3167#, no-c-format 3168msgid "" 3169"If you are using PostgreSQL 9.1+ and PostGIS 2.1+, you can take advantage of " 3170"the new extension model for installing tiger geocoder. To do so:" 3171msgstr "" 3172 3173#. Tag: para 3174#: installation.xml:956 3175#, no-c-format 3176msgid "" 3177"First get binaries for PostGIS 2.1+ or compile and install as usual. This " 3178"should install the necessary extension files as well for tiger geocoder." 3179msgstr "" 3180 3181#. Tag: para 3182#: installation.xml:957 3183#, no-c-format 3184msgid "" 3185"Connect to your database via psql or pgAdmin or some other tool and run the " 3186"following SQL commands. Note that if you are installing in a database that " 3187"already has postgis, you don't need to do the first step. If you have " 3188"<varname>fuzzystrmatch</varname> extension already installed, you don't need " 3189"to do the second step either." 3190msgstr "" 3191 3192#. Tag: programlisting 3193#: installation.xml:958 3194#, no-c-format 3195msgid "" 3196"CREATE EXTENSION postgis;\n" 3197"CREATE EXTENSION fuzzystrmatch;\n" 3198"CREATE EXTENSION postgis_tiger_geocoder;\n" 3199"--this one is optional if you want to use the rules based standardizer " 3200"(pagc_normalize_address)\n" 3201"CREATE EXTENSION address_standardizer;" 3202msgstr "" 3203 3204#. Tag: para 3205#: installation.xml:960 3206#, no-c-format 3207msgid "" 3208"If you already have postgis_tiger_geocoder extension installed, and just " 3209"want to update to the latest run:" 3210msgstr "" 3211 3212#. Tag: programlisting 3213#: installation.xml:961 3214#, no-c-format 3215msgid "" 3216"ALTER EXTENSION postgis UPDATE;\n" 3217"ALTER EXTENSION postgis_tiger_geocoder UPDATE;" 3218msgstr "" 3219"ALTER EXTENSION postgis UPDATE;\n" 3220"ALTER EXTENSION postgis_tiger_geocoder UPDATE;" 3221 3222#. Tag: para 3223#: installation.xml:962 3224#, no-c-format 3225msgid "" 3226"If you made custom entries or changes to <varname>tiger.loader_platform</" 3227"varname> and <varname>tiger.loader_variables</varname> you may need to " 3228"update these." 3229msgstr "" 3230 3231#. Tag: para 3232#: installation.xml:964 3233#, no-c-format 3234msgid "" 3235"To confirm your install is working correctly, run this sql in your database:" 3236msgstr "" 3237 3238#. Tag: programlisting 3239#: installation.xml:965 3240#, no-c-format 3241msgid "" 3242"SELECT na.address, na.streetname,na.streettypeabbrev, na.zip\n" 3243" FROM normalize_address('1 Devonshire Place, Boston, MA 02109') AS na;" 3244msgstr "" 3245"SELECT na.address, na.streetname,na.streettypeabbrev, na.zip\n" 3246" FROM normalize_address('1 Devonshire Place, Boston, MA 02109') AS na;" 3247 3248#. Tag: para 3249#: installation.xml:966 3250#, no-c-format 3251msgid "Which should output" 3252msgstr "" 3253 3254#. Tag: screen 3255#: installation.xml:967 3256#, no-c-format 3257msgid "" 3258"address | streetname | streettypeabbrev | zip\n" 3259"---------+------------+------------------+-------\n" 3260" 1 | Devonshire | Pl | 02109" 3261msgstr "" 3262 3263#. Tag: para 3264#: installation.xml:969 3265#, no-c-format 3266msgid "" 3267"Create a new record in <varname>tiger.loader_platform</varname> table with " 3268"the paths of your executables and server." 3269msgstr "" 3270 3271#. Tag: para 3272#: installation.xml:970 3273#, no-c-format 3274msgid "" 3275"So for example to create a profile called debbie that follows <code>sh</" 3276"code> convention. You would do:" 3277msgstr "" 3278 3279#. Tag: programlisting 3280#: installation.xml:971 3281#, no-c-format 3282msgid "" 3283"INSERT INTO tiger.loader_platform(os, declare_sect, pgbin, wget, " 3284"unzip_command, psql, path_sep,\n" 3285" loader, environ_set_command, county_process_command)\n" 3286"SELECT 'debbie', declare_sect, pgbin, wget, unzip_command, psql, path_sep,\n" 3287" loader, environ_set_command, county_process_command\n" 3288" FROM tiger.loader_platform\n" 3289" WHERE os = 'sh';" 3290msgstr "" 3291 3292#. Tag: para 3293#: installation.xml:972 3294#, no-c-format 3295msgid "" 3296"And then edit the paths in the <emphasis>declare_sect</emphasis> column to " 3297"those that fit Debbie's pg, unzip,shp2pgsql, psql, etc path locations." 3298msgstr "" 3299 3300#. Tag: para 3301#: installation.xml:974 3302#, no-c-format 3303msgid "" 3304"If you don't edit this <varname>loader_platform</varname> table, it will " 3305"just contain common case locations of items and you'll have to edit the " 3306"generated script after the script is generated." 3307msgstr "" 3308 3309#. Tag: para 3310#: installation.xml:976 3311#, no-c-format 3312msgid "" 3313"As of PostGIS 2.4.1 the Zip code-5 digit tabulation area <varname>zcta5</" 3314"varname> load step was revised to load current zcta5 data and is part of the " 3315"<xref linkend=\"Loader_Generate_Nation_Script\"/> when enabled. It is turned " 3316"off by default because it takes quite a bit of time to load (20 to 60 " 3317"minutes), takes up quite a bit of disk space, and is not used that often." 3318msgstr "" 3319 3320#. Tag: para 3321#: installation.xml:978 3322#, no-c-format 3323msgid "To enable it, do the following:" 3324msgstr "" 3325 3326#. Tag: programlisting 3327#: installation.xml:979 3328#, no-c-format 3329msgid "" 3330"UPDATE tiger.loader_lookuptables SET load = true WHERE table_name = " 3331"'zcta510';" 3332msgstr "" 3333 3334#. Tag: para 3335#: installation.xml:980 3336#, no-c-format 3337msgid "" 3338"If present the <xref linkend=\"Geocode\"/> function can use it if a boundary " 3339"filter is added to limit to just zips in that boundary. The <xref linkend=" 3340"\"Reverse_Geocode\"/> function uses it if the returned address is missing a " 3341"zip, which often happens with highway reverse geocoding." 3342msgstr "" 3343 3344#. Tag: para 3345#: installation.xml:983 3346#, no-c-format 3347msgid "" 3348"Create a folder called <filename>gisdata</filename> on root of server or " 3349"your local pc if you have a fast network connection to the server. This " 3350"folder is where the tiger files will be downloaded to and processed. If you " 3351"are not happy with having the folder on the root of the server, or simply " 3352"want to change to a different folder for staging, then edit the field " 3353"<varname>staging_fold</varname> in the <varname>tiger.loader_variables</" 3354"varname> table." 3355msgstr "" 3356 3357#. Tag: para 3358#: installation.xml:985 3359#, no-c-format 3360msgid "" 3361"Create a folder called temp in the <filename>gisdata</filename> folder or " 3362"whereever you designated the <varname>staging_fold</varname> to be. This " 3363"will be the folder where the loader extracts the downloaded tiger data." 3364msgstr "" 3365 3366#. Tag: para 3367#: installation.xml:987 3368#, no-c-format 3369msgid "" 3370"Then run the <xref linkend=\"Loader_Generate_Nation_Script\"/> SQL function " 3371"make sure to use the name of your custom profile and copy the script to a ." 3372"sh or .bat file. So for example to build the nation load:" 3373msgstr "" 3374 3375#. Tag: programlisting 3376#: installation.xml:988 3377#, no-c-format 3378msgid "" 3379"psql -c \"SELECT Loader_Generate_Nation_Script('debbie')\" -d geocoder -tA " 3380"> /gisdata/nation_script_load.sh" 3381msgstr "" 3382"psql -c \"SELECT Loader_Generate_Nation_Script('debbie')\" -d geocoder -tA " 3383"> /gisdata/nation_script_load.sh" 3384 3385#. Tag: para 3386#: installation.xml:991 3387#, no-c-format 3388msgid "Run the generated nation load commandline scripts." 3389msgstr "" 3390 3391#. Tag: programlisting 3392#: installation.xml:992 3393#, no-c-format 3394msgid "" 3395"cd /gisdata\n" 3396"sh nation_script_load.sh" 3397msgstr "" 3398"cd /gisdata\n" 3399"sh nation_script_load.sh" 3400 3401#. Tag: para 3402#: installation.xml:995 3403#, no-c-format 3404msgid "" 3405"After you are done running the nation script, you should have three tables " 3406"in your <code>tiger_data</code> schema and they should be filled with data. " 3407"Confirm you do by doing the following queries from psql or pgAdmin" 3408msgstr "" 3409 3410#. Tag: programlisting 3411#: installation.xml:996 3412#, no-c-format 3413msgid "SELECT count(*) FROM tiger_data.county_all;" 3414msgstr "SELECT count(*) FROM tiger_data.county_all;" 3415 3416#. Tag: screen 3417#: installation.xml:997 3418#, no-c-format 3419msgid "" 3420"count\n" 3421"-------\n" 3422" 3233\n" 3423"(1 row)" 3424msgstr "" 3425"count\n" 3426"-------\n" 3427" 3233\n" 3428"(1 row)" 3429 3430#. Tag: programlisting 3431#: installation.xml:998 3432#, no-c-format 3433msgid "SELECT count(*) FROM tiger_data.state_all;" 3434msgstr "SELECT count(*) FROM tiger_data.state_all;" 3435 3436#. Tag: screen 3437#: installation.xml:999 3438#, no-c-format 3439msgid "" 3440"count\n" 3441"-------\n" 3442" 56\n" 3443"(1 row)" 3444msgstr "" 3445"count\n" 3446"-------\n" 3447" 56\n" 3448"(1 row)" 3449 3450#. Tag: para 3451#: installation.xml:1002 3452#, no-c-format 3453msgid "" 3454"By default the tables corresponding to <varname>bg</varname>, " 3455"<varname>tract</varname>, <varname>tabblock</varname> are not loaded. These " 3456"tables are not used by the geocoder but are used by folks for population " 3457"statistics. If you wish to load them as part of your state loads, run the " 3458"following statement to enable them." 3459msgstr "" 3460 3461#. Tag: programlisting 3462#: installation.xml:1004 3463#, no-c-format 3464msgid "" 3465"UPDATE tiger.loader_lookuptables SET load = true WHERE load = false AND " 3466"lookup_name IN('tract', 'bg', 'tabblock');" 3467msgstr "" 3468 3469#. Tag: para 3470#: installation.xml:1005 3471#, no-c-format 3472msgid "" 3473"Alternatively you can load just these tables after loading state data using " 3474"the <xref linkend=\"Loader_Generate_Census_Script\"/>" 3475msgstr "" 3476 3477#. Tag: para 3478#: installation.xml:1007 3479#, no-c-format 3480msgid "" 3481"For each state you want to load data for, generate a state script <xref " 3482"linkend=\"Loader_Generate_Script\"/>." 3483msgstr "" 3484 3485#. Tag: para 3486#: installation.xml:1007 3487#, no-c-format 3488msgid "" 3489"DO NOT Generate the state script until you have already loaded the nation " 3490"data, because the state script utilizes county list loaded by nation script." 3491msgstr "" 3492 3493#. Tag: programlisting 3494#: installation.xml:1009 3495#, no-c-format 3496msgid "" 3497"psql -c \"SELECT Loader_Generate_Script(ARRAY['MA'], 'debbie')\" -d geocoder " 3498"-tA > /gisdata/ma_load.sh" 3499msgstr "" 3500"psql -c \"SELECT Loader_Generate_Script(ARRAY['MA'], 'debbie')\" -d geocoder " 3501"-tA > /gisdata/ma_load.sh" 3502 3503#. Tag: para 3504#: installation.xml:1011 3505#, no-c-format 3506msgid "Run the generated commandline scripts." 3507msgstr "" 3508 3509#. Tag: programlisting 3510#: installation.xml:1012 3511#, no-c-format 3512msgid "" 3513"cd /gisdata\n" 3514"sh ma_load.sh" 3515msgstr "" 3516"cd /gisdata\n" 3517"sh ma_load.sh" 3518 3519#. Tag: para 3520#: installation.xml:1014 3521#, no-c-format 3522msgid "" 3523"After you are done loading all data or at a stopping point, it's a good idea " 3524"to analyze all the tiger tables to update the stats (include inherited stats)" 3525msgstr "" 3526 3527#. Tag: programlisting 3528#: installation.xml:1015 3529#, no-c-format 3530msgid "" 3531"SELECT install_missing_indexes();\n" 3532"vacuum analyze verbose tiger.addr;\n" 3533"vacuum analyze verbose tiger.edges;\n" 3534"vacuum analyze verbose tiger.faces;\n" 3535"vacuum analyze verbose tiger.featnames;\n" 3536"vacuum analyze verbose tiger.place;\n" 3537"vacuum analyze verbose tiger.cousub;\n" 3538"vacuum analyze verbose tiger.county;\n" 3539"vacuum analyze verbose tiger.state;\n" 3540"vacuum analyze verbose tiger.zip_lookup_base;\n" 3541"vacuum analyze verbose tiger.zip_state;\n" 3542"vacuum analyze verbose tiger.zip_state_loc;" 3543msgstr "" 3544 3545#. Tag: title 3546#: installation.xml:1018 3547#, no-c-format 3548msgid "Converting a Tiger Geocoder Regular Install to Extension Model" 3549msgstr "" 3550 3551#. Tag: para 3552#: installation.xml:1019 3553#, no-c-format 3554msgid "" 3555"If you installed the tiger geocoder without using the extension model, you " 3556"can convert to the extension model as follows:" 3557msgstr "" 3558 3559#. Tag: para 3560#: installation.xml:1021 3561#, no-c-format 3562msgid "" 3563"Follow instructions in <xref linkend=\"upgrade_tiger_geocoder\"/> for the " 3564"non-extension model upgrade." 3565msgstr "" 3566 3567#. Tag: para 3568#: installation.xml:1022 3569#, no-c-format 3570msgid "" 3571"Connect to your database with psql or pgAdmin and run the following command:" 3572msgstr "" 3573 3574#. Tag: programlisting 3575#: installation.xml:1023 3576#, no-c-format 3577msgid "CREATE EXTENSION postgis_tiger_geocoder FROM unpackaged;" 3578msgstr "CREATE EXTENSION postgis_tiger_geocoder FROM unpackaged;" 3579 3580#. Tag: title 3581#: installation.xml:1030 3582#, no-c-format 3583msgid "Tiger Geocoder Enabling your PostGIS database: Not Using Extensions" 3584msgstr "" 3585 3586#. Tag: para 3587#: installation.xml:1031 3588#, no-c-format 3589msgid "First install PostGIS using the prior instructions." 3590msgstr "Primero debes instalar PostGIS con las instrucciones anteriores." 3591 3592#. Tag: para 3593#: installation.xml:1035 installation.xml:1095 3594#, no-c-format 3595msgid "" 3596"If you don't have an extras folder, download <ulink url=" 3597"\"&postgis_download_url;\">&postgis_download_url;</ulink>" 3598msgstr "" 3599 3600#. Tag: command 3601#: installation.xml:1040 installation.xml:1100 3602#, no-c-format 3603msgid "tar xvfz postgis-&last_release_version;.tar.gz" 3604msgstr "tar xvfz postgis-&last_release_version;.tar.gz" 3605 3606#. Tag: command 3607#: installation.xml:1044 3608#, no-c-format 3609msgid "cd postgis-&last_release_version;/extras/tiger_geocoder" 3610msgstr "" 3611 3612#. Tag: para 3613#: installation.xml:1047 3614#, no-c-format 3615msgid "" 3616"Edit the <filename>tiger_loader_2015.sql</filename> (or latest loader file " 3617"you find, unless you want to load different year) to the paths of your " 3618"executables server etc or alternatively you can update the " 3619"<varname>loader_platform</varname> table once installed. If you don't edit " 3620"this file or the <varname>loader_platform</varname> table, it will just " 3621"contain common case locations of items and you'll have to edit the generated " 3622"script after the fact when you run the <xref linkend=" 3623"\"Loader_Generate_Nation_Script\"/> and <xref linkend=" 3624"\"Loader_Generate_Script\"/> SQL functions." 3625msgstr "" 3626 3627#. Tag: para 3628#: installation.xml:1049 3629#, no-c-format 3630msgid "" 3631"If you are installing Tiger geocoder for the first time edit either the " 3632"<filename>create_geocode.bat</filename> script If you are on windows or the " 3633"<filename>create_geocode.sh</filename> if you are on Linux/Unix/Mac OSX with " 3634"your PostgreSQL specific settings and run the corresponding script from the " 3635"commandline." 3636msgstr "" 3637 3638#. Tag: para 3639#: installation.xml:1053 3640#, no-c-format 3641msgid "" 3642"Verify that you now have a <varname>tiger</varname> schema in your database " 3643"and that it is part of your database search_path. If it is not, add it with " 3644"a command something along the line of:" 3645msgstr "" 3646"Verifica que ahora tienes el esquema <varname>tiger</varname> en tu base de " 3647"datos y este forma parte de tu variable search_path en la base de datos. Si " 3648"no, añádelo con un comando parecido al siguiente:" 3649 3650#. Tag: programlisting 3651#: installation.xml:1053 3652#, no-c-format 3653msgid "ALTER DATABASE geocoder SET search_path=public, tiger;" 3654msgstr "ALTER DATABASE geocoder SET search_path=public, tiger;" 3655 3656#. Tag: para 3657#: installation.xml:1054 3658#, no-c-format 3659msgid "" 3660"The normalizing address functionality works more or less without any data " 3661"except for tricky addresses. Run this test and verify things look like this:" 3662msgstr "" 3663"La funcionalidad de normalización de direcciones funciona sin datos mas o " 3664"menos, excepto para direcciones complejas. Ejecuta el siguiente test y " 3665"verifica si se parece a esto:" 3666 3667#. Tag: programlisting 3668#: installation.xml:1055 3669#, no-c-format 3670msgid "" 3671"SELECT pprint_addy(normalize_address('202 East Fremont Street, Las Vegas, " 3672"Nevada 89101')) As pretty_address;\n" 3673"pretty_address\n" 3674"---------------------------------------\n" 3675"202 E Fremont St, Las Vegas, NV 89101" 3676msgstr "" 3677"SELECT pprint_addy(normalize_address('202 East Fremont Street, Las Vegas, " 3678"Nevada 89101')) As pretty_address;\n" 3679"pretty_address\n" 3680"---------------------------------------\n" 3681"202 E Fremont St, Las Vegas, NV 89101" 3682 3683#. Tag: title 3684#: installation.xml:1058 3685#, no-c-format 3686msgid "Using Address Standardizer Extension with Tiger geocoder" 3687msgstr "" 3688 3689#. Tag: para 3690#: installation.xml:1059 3691#, no-c-format 3692msgid "" 3693"One of the many complaints of folks is the address normalizer function <xref " 3694"linkend=\"Normalize_Address\"/> function that normalizes an address for " 3695"prepping before geocoding. The normalizer is far from perfect and trying to " 3696"patch its imperfectness takes a vast amount of resources. As such we have " 3697"integrated with another project that has a much better address standardizer " 3698"engine. To use this new address_standardizer, you compile the extension as " 3699"described in <xref linkend=\"installing_pagc_address_standardizer\"/> and " 3700"install as an extension in your database." 3701msgstr "" 3702 3703#. Tag: para 3704#: installation.xml:1062 3705#, no-c-format 3706msgid "" 3707"Once you install this extension in the same database as you have installed " 3708"<code>postgis_tiger_geocoder</code>, then the <xref linkend=" 3709"\"Pagc_Normalize_Address\"/> can be used instead of <xref linkend=" 3710"\"Normalize_Address\"/>. This extension is tiger agnostic, so can be used " 3711"with other data sources such as international addresses. The tiger geocoder " 3712"extension does come packaged with its own custom versions of <xref linkend=" 3713"\"rulestab\"/> ( <code>tiger.pagc_rules</code>) , <xref linkend=\"gaztab\"/> " 3714"(<code>tiger.pagc_gaz</code>), and <xref linkend=\"lextab\"/> (<code>tiger." 3715"pagc_lex</code>). These you can add and update to improve your standardizing " 3716"experience for your own needs." 3717msgstr "" 3718 3719#. Tag: title 3720#: installation.xml:1065 3721#, no-c-format 3722msgid "Loading Tiger Data" 3723msgstr "Cargando datos Tiger" 3724 3725#. Tag: para 3726#: installation.xml:1066 3727#, no-c-format 3728msgid "" 3729"The instructions for loading data are available in a more detailed form in " 3730"the <filename>extras/tiger_geocoder/tiger_2011/README</filename>. This just " 3731"includes the general steps." 3732msgstr "" 3733"Las instrucciones de carga de datos están disponibles de forma mas detallada " 3734"en <filename>extras/tiger_geocoder/tiger_2011/README</filename>. Esto solo " 3735"describe los pasos generales." 3736 3737#. Tag: para 3738#: installation.xml:1067 3739#, no-c-format 3740msgid "" 3741"The load process downloads data from the census website for the respective " 3742"nation files, states requested, extracts the files, and then loads each " 3743"state into its own separate set of state tables. Each state table inherits " 3744"from the tables defined in <varname>tiger</varname> schema so that its " 3745"sufficient to just query those tables to access all the data and drop a set " 3746"of state tables at any time using the <xref linkend=" 3747"\"Drop_State_Tables_Generate_Script\"/> if you need to reload a state or " 3748"just don't need a state anymore." 3749msgstr "" 3750"El proceso de carga, descarga datos desde el sitio web del censo de las " 3751"respectivas naciones de los estados pedidos, extrae los ficheros, y carga " 3752"cada estado en un conjunto separado por estados en su propia tabla. Cada " 3753"tabla de estado hereda el esquema de tablas definido en <varname>tiger</" 3754"varname> así que basta con hacer una consulta a estas tablas para acceder a " 3755"todos los datos de la tabla de estados en cualquier momento utilizando <xref " 3756"linkend=\"Drop_State_Tables_Generate_Script\"/> si necesita volver a cargar " 3757"un estado o si ya no lo necesitas mas." 3758 3759#. Tag: para 3760#: installation.xml:1069 3761#, no-c-format 3762msgid "In order to be able to load data you'll need the following tools:" 3763msgstr "Para poder cargar los datos necesitarás las siguientes herramientas:" 3764 3765#. Tag: para 3766#: installation.xml:1071 3767#, no-c-format 3768msgid "A tool to unzip the zip files from census website." 3769msgstr "" 3770"Una herramienta para descomprimir ficheros zip de la pagina web del censo." 3771 3772#. Tag: para 3773#: installation.xml:1072 3774#, no-c-format 3775msgid "" 3776"For Unix like systems: <varname>unzip</varname> executable which is usually " 3777"already installed on most Unix like platforms." 3778msgstr "" 3779"Para sistemas Unix: el ejecutable <varname>unzip</varname> que normalmente " 3780"esta instalado en la mayoría de sistemas Unix." 3781 3782#. Tag: para 3783#: installation.xml:1073 3784#, no-c-format 3785msgid "" 3786"For Windows, 7-zip which is a free compress/uncompress tool you can download " 3787"from <ulink url=\"http://www.7-zip.org/\">http://www.7-zip.org/</ulink>" 3788msgstr "" 3789"Para windows, 7-zip es una herramienta libre de compresión/descompresión que " 3790"puedes descargar en <ulink url=\"http://www.7-zip.org/\">http://www.7-zip." 3791"org/</ulink>" 3792 3793#. Tag: para 3794#: installation.xml:1075 3795#, no-c-format 3796msgid "" 3797"<filename>shp2pgsql</filename> commandline which is installed by default " 3798"when you install PostGIS." 3799msgstr "" 3800"El comando <filename>shp2pgsql</filename> que se instala por defecto cuando " 3801"instalas PostGIS." 3802 3803#. Tag: para 3804#: installation.xml:1076 3805#, no-c-format 3806msgid "" 3807"<filename>wget</filename> which is a web grabber tool usually installed on " 3808"most Unix/Linux systems." 3809msgstr "" 3810"<filename>wget</filename> que es una herramienta de captura web, normalmente " 3811"instalado en los sistemas Unix/Linux." 3812 3813#. Tag: para 3814#: installation.xml:1077 3815#, no-c-format 3816msgid "" 3817"If you are on windows, you can get pre-compiled binaries from <ulink url=" 3818"\"http://gnuwin32.sourceforge.net/packages/wget.htm\">http://gnuwin32." 3819"sourceforge.net/packages/wget.htm</ulink>" 3820msgstr "" 3821"Si estas en windows, puedes obtener ejecutables precompilados en <ulink url=" 3822"\"http://gnuwin32.sourceforge.net/packages/wget.htm\">http://gnuwin32." 3823"sourceforge.net/packages/wget.htm</ulink>" 3824 3825#. Tag: para 3826#: installation.xml:1080 3827#, no-c-format 3828msgid "" 3829"If you are upgrading from tiger_2010, you'll need to first generate and run " 3830"<xref linkend=\"Drop_Nation_Tables_Generate_Script\"/>. Before you load any " 3831"state data, you need to load the nation wide data which you do with <xref " 3832"linkend=\"Loader_Generate_Nation_Script\"/>. Which will generate a loader " 3833"script for you. <xref linkend=\"Loader_Generate_Nation_Script\"/> is a one-" 3834"time step that should be done for upgrading (from 2010) and for new installs." 3835msgstr "" 3836 3837#. Tag: para 3838#: installation.xml:1082 3839#, no-c-format 3840msgid "" 3841"To load state data refer to <xref linkend=\"Loader_Generate_Script\"/> to " 3842"generate a data load script for your platform for the states you desire. " 3843"Note that you can install these piecemeal. You don't have to load all the " 3844"states you want all at once. You can load them as you need them." 3845msgstr "" 3846 3847#. Tag: para 3848#: installation.xml:1085 3849#, no-c-format 3850msgid "" 3851"After the states you desire have been loaded, make sure to run the: " 3852"<programlisting>SELECT install_missing_indexes();</programlisting> as " 3853"described in <xref linkend=\"Install_Missing_Indexes\"/>." 3854msgstr "" 3855"Una vez que los estados que quieres han sido cargados, asegurare de " 3856"ejecutar: <programlisting>SELECT install_missing_indexes();</" 3857"programlisting> como se explica en <xref linkend=\"Install_Missing_Indexes\"/" 3858">." 3859 3860#. Tag: para 3861#: installation.xml:1087 3862#, no-c-format 3863msgid "" 3864"To test that things are working as they should, try to run a geocode on an " 3865"address in your state using <xref linkend=\"Geocode\"/>" 3866msgstr "" 3867"Para probar que las cosas han funcionado como deberían, intenta ejecutar una " 3868"geocodificacion en una dirección del estado descargado utilizando <xref " 3869"linkend=\"Geocode\"/>" 3870 3871#. Tag: title 3872#: installation.xml:1090 3873#, no-c-format 3874msgid "Upgrading your Tiger Geocoder Install" 3875msgstr "Actualizando la instalación del geocodificador Tiger" 3876 3877#. Tag: para 3878#: installation.xml:1091 3879#, no-c-format 3880msgid "" 3881"If you have Tiger Geocoder packaged with 2.0+ already installed, you can " 3882"upgrade the functions at any time even from an interim tar ball if there are " 3883"fixes you badly need. This will only work for Tiger geocoder not installed " 3884"with extensions." 3885msgstr "" 3886 3887#. Tag: command 3888#: installation.xml:1104 3889#, no-c-format 3890msgid "cd postgis-&last_release_version;/extras/tiger_geocoder/tiger_2011" 3891msgstr "cd postgis-&last_release_version;/extras/tiger_geocoder/tiger_2011" 3892 3893#. Tag: para 3894#: installation.xml:1107 3895#, no-c-format 3896msgid "" 3897"Locate the <filename>upgrade_geocoder.bat</filename> script If you are on " 3898"windows or the <filename>upgrade_geocoder.sh</filename> if you are on Linux/" 3899"Unix/Mac OSX. Edit the file to have your postgis database credentials." 3900msgstr "" 3901 3902#. Tag: para 3903#: installation.xml:1110 3904#, no-c-format 3905msgid "" 3906"If you are upgrading from 2010 or 2011, make sure to unremark out the loader " 3907"script line so you get the latest script for loading 2012 data." 3908msgstr "" 3909 3910#. Tag: para 3911#: installation.xml:1111 3912#, no-c-format 3913msgid "Then run th corresponding script from the commandline." 3914msgstr "" 3915 3916#. Tag: para 3917#: installation.xml:1115 3918#, no-c-format 3919msgid "" 3920"Next drop all nation tables and load up the new ones. Generate a drop script " 3921"with this SQL statement as detailed in <xref linkend=" 3922"\"Drop_Nation_Tables_Generate_Script\"/>" 3923msgstr "" 3924"Después, elimina todas las tabals de naciones y carga las nuevas. Genera un " 3925"script drop con esta sentencia SQL como se detalla en <xref linkend=" 3926"\"Drop_Nation_Tables_Generate_Script\"/>" 3927 3928#. Tag: programlisting 3929#: installation.xml:1116 3930#, no-c-format 3931msgid "SELECT drop_nation_tables_generate_script();" 3932msgstr "SELECT drop_nation_tables_generate_script();" 3933 3934#. Tag: para 3935#: installation.xml:1117 3936#, no-c-format 3937msgid "Run the generated drop SQL statements." 3938msgstr "Ejecuta la sentencia SQL drop" 3939 3940#. Tag: para 3941#: installation.xml:1118 3942#, no-c-format 3943msgid "" 3944"Generate a nation load script with this SELECT statement as detailed in " 3945"<xref linkend=\"Loader_Generate_Nation_Script\"/>" 3946msgstr "" 3947"Genera un script de carga de naciones con esta sentencia SELECT como se " 3948"detalla en <xref linkend=\"Loader_Generate_Nation_Script\"/>" 3949 3950#. Tag: emphasis 3951#: installation.xml:1119 3952#, no-c-format 3953msgid "For windows" 3954msgstr "Para windows" 3955 3956#. Tag: programlisting 3957#: installation.xml:1120 3958#, no-c-format 3959msgid "SELECT loader_generate_nation_script('windows');" 3960msgstr "SELECT loader_generate_nation_script('windows');" 3961 3962#. Tag: emphasis 3963#: installation.xml:1121 3964#, no-c-format 3965msgid "For unix/linux" 3966msgstr "Para unix/linux" 3967 3968#. Tag: programlisting 3969#: installation.xml:1122 3970#, no-c-format 3971msgid "SELECT loader_generate_nation_script('sh');" 3972msgstr "SELECT loader_generate_nation_script('sh');" 3973 3974#. Tag: para 3975#: installation.xml:1123 3976#, no-c-format 3977msgid "" 3978"Refer to <xref linkend=\"tiger_geocoder_loading_data\"/> for instructions on " 3979"how to run the generate script. This only needs to be done once." 3980msgstr "" 3981"Para mas información sobre como ejecutar los scripts generados visita <xref " 3982"linkend=\"tiger_geocoder_loading_data\"/>. Esto solo es necesario hacerlo " 3983"una vez." 3984 3985#. Tag: para 3986#: installation.xml:1124 3987#, no-c-format 3988msgid "" 3989"You can have a mix of 2010/2011 state tables and can upgrade each state " 3990"separately. Before you upgrade a state to 2011, you first need to drop the " 3991"2010 tables for that state using <xref linkend=" 3992"\"Drop_State_Tables_Generate_Script\"/>." 3993msgstr "" 3994"Puedes tener una mezcla de tablas de estados de 2010/2011 y puedes " 3995"actualizar cada estado por separado. Antes de actualizar un estado a la " 3996"versión de 2011 debes suprimir las tablas de este estado para 2010 " 3997"utilizando <xref linkend=\"Drop_State_Tables_Generate_Script\"/>." 3998 3999#. Tag: title 4000#: installation.xml:1130 4001#, no-c-format 4002msgid "Create a spatially-enabled database from a template" 4003msgstr "Crear una base de datos espacial desde una plantilla" 4004 4005#. Tag: para 4006#: installation.xml:1132 4007#, no-c-format 4008msgid "" 4009"Some packaged distributions of PostGIS (in particular the Win32 installers " 4010"for PostGIS >= 1.1.5) load the PostGIS functions into a template database " 4011"called <varname>template_postgis</varname>. If the " 4012"<varname>template_postgis</varname> database exists in your PostgreSQL " 4013"installation then it is possible for users and/or applications to create " 4014"spatially-enabled databases using a single command. Note that in both cases, " 4015"the database user must have been granted the privilege to create new " 4016"databases." 4017msgstr "" 4018"Algunas de las distribuciones precompiladas de PostGIS (en particular los " 4019"instaladores de Postgis >= 1.1.5 para sistemas Win32) carga las funciones " 4020"de PostGIS en una base de datos plantilla llamada <varname>template_postgis</" 4021"varname>. Si la base de datos <varname>template_postgis</varname> existe ya " 4022"en nuestra instalación de PostgreSQL, los usuarios y aplicaciones podrán " 4023"crear bases de datos espaciales con un simple comando. En ambos casos, el " 4024"usuario de la base de datos debe tener privilegios para crear nuevas bases " 4025"de datos" 4026 4027#. Tag: para 4028#: installation.xml:1143 4029#, no-c-format 4030msgid "From the shell:" 4031msgstr "En la linea de comandos:" 4032 4033#. Tag: programlisting 4034#: installation.xml:1147 4035#, no-c-format 4036msgid "# createdb -T template_postgis my_spatial_db" 4037msgstr "# createdb -T template_postgis my_spatial_db" 4038 4039#. Tag: para 4040#: installation.xml:1149 4041#, no-c-format 4042msgid "From SQL:" 4043msgstr "Desde SQL:" 4044 4045#. Tag: programlisting 4046#: installation.xml:1153 4047#, no-c-format 4048msgid "postgres=# CREATE DATABASE my_spatial_db TEMPLATE=template_postgis" 4049msgstr "postgres=# CREATE DATABASE my_spatial_db TEMPLATE=template_postgis" 4050 4051#. Tag: title 4052#: installation.xml:1157 4053#, no-c-format 4054msgid "Upgrading" 4055msgstr "Actualizando" 4056 4057#. Tag: para 4058#: installation.xml:1159 4059#, no-c-format 4060msgid "" 4061"Upgrading existing spatial databases can be tricky as it requires " 4062"replacement or introduction of new PostGIS object definitions." 4063msgstr "" 4064"Actualizar una base de datos espacial puede ser complejo ya que requiere " 4065"reemplazar o introducir nuevas definiciones de objetos PostGIS." 4066 4067#. Tag: para 4068#: installation.xml:1164 4069#, no-c-format 4070msgid "" 4071"Unfortunately not all definitions can be easily replaced in a live database, " 4072"so sometimes your best bet is a dump/reload process." 4073msgstr "" 4074"Desafortunadamente, no todas las definiciones pueden reemplazarse fácilmente " 4075"en una base de datos activa, así que algunas veces lo mejor es un proceso " 4076"copia de seguridad/recarga." 4077 4078#. Tag: para 4079#: installation.xml:1169 4080#, no-c-format 4081msgid "" 4082"PostGIS provides a SOFT UPGRADE procedure for minor or bugfix releases, and " 4083"a HARD UPGRADE procedure for major releases." 4084msgstr "" 4085"PostGIS incluye una SOFT UPGRADE (actualización ligera) para " 4086"actualizaciones menores o corrección de errores, y una HARD UPGRADE " 4087"(Actualización pesada) para versiones mayores." 4088 4089#. Tag: para 4090#: installation.xml:1174 4091#, no-c-format 4092msgid "" 4093"Before attempting to upgrade PostGIS, it is always worth to backup your " 4094"data. If you use the -Fc flag to pg_dump you will always be able to restore " 4095"the dump with a HARD UPGRADE." 4096msgstr "" 4097"Antes de realizar una actualización de PostGIS, es recomendable hacer una " 4098"copia de seguridad de los datos. Si utilizas la opción -Fc en el comando " 4099"pg_dump siempre podrás restaurar la copia realizada con un HARD UPDATE." 4100 4101#. Tag: title 4102#: installation.xml:1181 4103#, no-c-format 4104msgid "Soft upgrade" 4105msgstr "Actualizacion Ligera" 4106 4107#. Tag: para 4108#: installation.xml:1183 4109#, no-c-format 4110msgid "" 4111"If you installed your database using extensions, you'll need to upgrade " 4112"using the extension model as well. If you installed using the old sql script " 4113"way, then you should upgrade using the sql script way. Please refer to the " 4114"appropriate." 4115msgstr "" 4116"Si instalaste la base de datos utilizando extensiones, necesitaras " 4117"actualizar utilizando el modelo de extensiones tambien. Si instalaste " 4118"utilizando el antiguo metodo de script sql, necesitaras actualizar el metodo " 4119"de script sql. Consulta el metodo adecuado." 4120 4121#. Tag: title 4122#: installation.xml:1186 4123#, no-c-format 4124msgid "Soft Upgrade Pre 9.1+ or without extensions" 4125msgstr "" 4126"Actualización ligera anterior a la versión PostgreSQL 9.1+ o sin extensiones" 4127 4128#. Tag: para 4129#: installation.xml:1187 4130#, no-c-format 4131msgid "" 4132"This section applies only to those who installed PostGIS not using " 4133"extensions. If you have extensions and try to upgrade with this approach " 4134"you'll get messages like:" 4135msgstr "" 4136"Esta sección describe el método para quienes instalaron PostGIS sin utilizar " 4137"extensiones solamente. Si tienes extensiones e intentas actualizar con este " 4138"metodo, tendras mensajes como los siguientes:" 4139 4140#. Tag: programlisting 4141#: installation.xml:1188 4142#, no-c-format 4143msgid "can't drop ... because postgis extension depends on it" 4144msgstr "no se puede suprimir ... porque la extensión postgis depende de el" 4145 4146#. Tag: para 4147#: installation.xml:1189 4148#, no-c-format 4149msgid "" 4150"After compiling and installing (make install) you should find a " 4151"<filename>postgis_upgrade.sql</filename> and <filename>rtpostgis_upgrade." 4152"sql</filename> in the installation folders. For example <filename>/usr/share/" 4153"postgresql/9.3/contrib/postgis_upgrade.sql</filename>. Install the " 4154"<filename>postgis_upgrade.sql</filename>. If you have raster functionality " 4155"installed, you will also need to install the <filename>/usr/share/" 4156"postgresql/9.3/contrib/postgis_upgrade.sql</filename>. If you are moving " 4157"from PostGIS 1.* to PostGIS 2.* or from PostGIS 2.* prior to r7409, you need " 4158"to do a HARD UPGRADE." 4159msgstr "" 4160 4161#. Tag: programlisting 4162#: installation.xml:1193 4163#, no-c-format 4164msgid "psql -f postgis_upgrade.sql -d your_spatial_database" 4165msgstr "psql -f postgis_upgrade.sql -d your_spatial_database" 4166 4167#. Tag: para 4168#: installation.xml:1195 4169#, no-c-format 4170msgid "" 4171"The same procedure applies to raster and topology extensions, with upgrade " 4172"files named <filename>rtpostgis_upgrade*.sql</filename> and " 4173"<filename>topology_upgrade*.sql</filename> respectively. If you need them:" 4174msgstr "" 4175"El mimo proceso se emplea para las extensiones raster y topology, con " 4176"ficheros de actualizacion llamados <filename>rtpostgis_upgrade*.sql</" 4177"filename> y <filename>topology_upgrade*.sql</filename> respectivamente. Si " 4178"lo necesitas, entoces:" 4179 4180#. Tag: programlisting 4181#: installation.xml:1203 4182#, no-c-format 4183msgid "psql -f rtpostgis_upgrade.sql -d your_spatial_database" 4184msgstr "psql -f rtpostgis_upgrade.sql -d your_spatial_database" 4185 4186#. Tag: programlisting 4187#: installation.xml:1204 4188#, no-c-format 4189msgid "psql -f topology_upgrade.sql -d your_spatial_database" 4190msgstr "psql -f topology_upgrade.sql -d your_spatial_database" 4191 4192#. Tag: para 4193#: installation.xml:1207 4194#, no-c-format 4195msgid "" 4196"If you can't find the <filename>postgis_upgrade*.sql</filename> specific for " 4197"upgrading your version you are using a version too early for a soft upgrade " 4198"and need to do a HARD UPGRADE." 4199msgstr "" 4200"Si no puedes encontrar el fichero <filename>postgis_upgrade*.sql</filename> " 4201"especifico para actualizar tu version, estas utilizando una version previa " 4202"para una actualización ligera y necesitas hacer una actualización completa o " 4203"HARD UPGRADE." 4204 4205#. Tag: para 4206#: installation.xml:1213 4207#, no-c-format 4208msgid "" 4209"The <xref linkend=\"PostGIS_Full_Version\"/> function should inform you " 4210"about the need to run this kind of upgrade using a \"procs need upgrade\" " 4211"message." 4212msgstr "" 4213"La función <xref linkend=\"PostGIS_Full_Version\"/> debe darte la " 4214"información sobre la necesidad de ejecutar este tipo de actualización " 4215"utilizando el mensaje \"procs need upgrade\"." 4216 4217#. Tag: title 4218#: installation.xml:1220 4219#, no-c-format 4220msgid "Soft Upgrade 9.1+ using extensions" 4221msgstr "Actualizacion ligera 9.1+ utilizando extensiones" 4222 4223#. Tag: para 4224#: installation.xml:1221 4225#, no-c-format 4226msgid "" 4227"If you originally installed PostGIS with extensions, then you need to " 4228"upgrade using extensions as well. Doing a minor upgrade with extensions, is " 4229"fairly painless." 4230msgstr "" 4231"Si has instalado originalmente PostGIS con extensiones, entonces necesitas " 4232"actualizar utilizando extensiones también. Hacer una actualización menor con " 4233"extensiones es bastante sencillo." 4234 4235#. Tag: programlisting 4236#: installation.xml:1222 4237#, no-c-format 4238msgid "" 4239"ALTER EXTENSION postgis UPDATE TO \"&last_release_version;\";\n" 4240"ALTER EXTENSION postgis_topology UPDATE TO \"&last_release_version;\";" 4241msgstr "" 4242"ALTER EXTENSION postgis UPDATE TO \"&last_release_version;\";\n" 4243"ALTER EXTENSION postgis_topology UPDATE TO \"&last_release_version;\";" 4244 4245#. Tag: para 4246#: installation.xml:1223 4247#, no-c-format 4248msgid "If you get an error notice something like:" 4249msgstr "Si obtienes un error parecido a:" 4250 4251#. Tag: programlisting 4252#: installation.xml:1224 4253#, no-c-format 4254msgid "No migration path defined for ... to &last_release_version;" 4255msgstr "No migration path defined for ... to &last_release_version;" 4256 4257#. Tag: para 4258#: installation.xml:1225 4259#, no-c-format 4260msgid "" 4261"Then you'll need to backup your database, create a fresh one as described in " 4262"<xref linkend=\"create_new_db_extensions\"/> and then restore your backup " 4263"ontop of this new database." 4264msgstr "" 4265 4266#. Tag: para 4267#: installation.xml:1226 4268#, no-c-format 4269msgid "If you get a notice message like:" 4270msgstr "" 4271 4272#. Tag: programlisting 4273#: installation.xml:1227 4274#, no-c-format 4275msgid "" 4276"Version \"&last_release_version;\" of extension \"postgis\" is already " 4277"installed" 4278msgstr "" 4279 4280#. Tag: para 4281#: installation.xml:1228 4282#, no-c-format 4283msgid "" 4284"Then everything is already up to date and you can safely ignore it. " 4285"<emphasis role=\"bold\">UNLESS</emphasis> you're attempting to upgrade from " 4286"an SVN version to the next (which doesn't get a new version number); in that " 4287"case you can append \"next\" to the version string, and next time you'll " 4288"need to drop the \"next\" suffix again:" 4289msgstr "" 4290 4291#. Tag: programlisting 4292#: installation.xml:1234 4293#, no-c-format 4294msgid "" 4295"ALTER EXTENSION postgis UPDATE TO \"&last_release_version;next\";\n" 4296"ALTER EXTENSION postgis_topology UPDATE TO \"&last_release_version;next\";" 4297msgstr "" 4298"ALTER EXTENSION postgis UPDATE TO \"&last_release_version;next\";\n" 4299"ALTER EXTENSION postgis_topology UPDATE TO \"&last_release_version;next\";" 4300 4301#. Tag: para 4302#: installation.xml:1235 4303#, no-c-format 4304msgid "" 4305"If you installed PostGIS originally without a version specified, you can " 4306"often skip the reinstallation of postgis extension before restoring since " 4307"the backup just has <code>CREATE EXTENSION postgis</code> and thus picks up " 4308"the newest latest version during restore." 4309msgstr "" 4310 4311#. Tag: title 4312#: installation.xml:1242 4313#, no-c-format 4314msgid "Hard upgrade" 4315msgstr "Actualizacion pesada o HARD UPDATE" 4316 4317#. Tag: para 4318#: installation.xml:1244 4319#, no-c-format 4320msgid "" 4321"By HARD UPGRADE we mean full dump/reload of postgis-enabled databases. You " 4322"need a HARD UPGRADE when PostGIS objects' internal storage changes or when " 4323"SOFT UPGRADE is not possible. The <link linkend=\"release_notes\">Release " 4324"Notes</link> appendix reports for each version whether you need a dump/" 4325"reload (HARD UPGRADE) to upgrade." 4326msgstr "" 4327"Por actualización pesada se entiende una copia de seguridad/recarga completa " 4328"de datos en la base de datos espacial. Necesitas una actualización pesada " 4329"cuando los objetos internos de almacenamiento de PostGIS cambian o cuando " 4330"una actualización ligera no es posible. Las notas <link linkend=" 4331"\"release_notes\">Release Notes</link> del apéndice hay informes de cada " 4332"version y de si necesitas hacer una copia de seguridad/recarga de datos " 4333"(HARD UPGRADE) para actualizar." 4334 4335#. Tag: para 4336#: installation.xml:1253 4337#, no-c-format 4338msgid "" 4339"The dump/reload process is assisted by the postgis_restore.pl script which " 4340"takes care of skipping from the dump all definitions which belong to PostGIS " 4341"(including old ones), allowing you to restore your schemas and data into a " 4342"database with PostGIS installed without getting duplicate symbol errors or " 4343"bringing forward deprecated objects." 4344msgstr "" 4345"El proceso copia de seguridad/recarga de datos esta asistido por el script " 4346"postgis_restore.pl te toma en cuenta ignorar en la copia de seguridad todas " 4347"las definiciones que pertenecen a PostGIS (incluyendo las antiguas), " 4348"permitiéndote restaurar tus esquemas y datos en una base de datos con " 4349"PostGIS instalado sin tener que duplicar errores o trayendo objetos " 4350"rechazados." 4351 4352#. Tag: para 4353#: installation.xml:1262 4354#, no-c-format 4355msgid "" 4356"Supplementary instructions for windows users are available at <ulink url=" 4357"\"http://trac.osgeo.org/postgis/wiki/UsersWikiWinUpgrade\">Windows Hard " 4358"upgrade</ulink>." 4359msgstr "" 4360"Instruciones complementarias para windows están disponibles en <ulink url=" 4361"\"http://trac.osgeo.org/postgis/wiki/UsersWikiWinUpgrade\">Windows Hard " 4362"upgrade</ulink>." 4363 4364#. Tag: para 4365#: installation.xml:1265 4366#, no-c-format 4367msgid "The Procedure is as follows:" 4368msgstr "El procedimiento es como sigue:" 4369 4370#. Tag: para 4371#: installation.xml:1273 4372#, no-c-format 4373msgid "" 4374"Create a \"custom-format\" dump of the database you want to upgrade (let's " 4375"call it <varname>olddb</varname>) include binary blobs (-b) and verbose (-v) " 4376"output. The user can be the owner of the db, need not be postgres super " 4377"account." 4378msgstr "" 4379"Crea un \"formato personalizado\" de copia de seguridad de la base de datos " 4380"que asieres actualizar (llamemosla <varname>olddb</varname>) incluye " 4381"binarios bolb (-b) y salida verbose (-v). El usuario puede ser el " 4382"propietario de la base de datos, no necesitas una cuenta de superusuario " 4383"postgres." 4384 4385#. Tag: programlisting 4386#: installation.xml:1281 4387#, no-c-format 4388msgid "" 4389"pg_dump -h localhost -p 5432 -U postgres -Fc -b -v -f \"/somepath/olddb." 4390"backup\" olddb" 4391msgstr "" 4392"pg_dump -h localhost -p 5432 -U postgres -Fc -b -v -f \"/somepath/olddb." 4393"backup\" olddb" 4394 4395#. Tag: para 4396#: installation.xml:1287 4397#, no-c-format 4398msgid "" 4399"Do a fresh install of PostGIS in a new database -- we'll refer to this " 4400"database as <varname>newdb</varname>. Please refer to <xref linkend=" 4401"\"create_new_db\"/> and <xref linkend=\"create_new_db_extensions\"/> for " 4402"instructions on how to do this." 4403msgstr "" 4404"Haz una nueva instalación de PsotGIS en una nueva base de datos --la " 4405"llamaremos <varname>newdb</varname> en este ejemplo. Puedes obtener " 4406"información de como hacer esto en <xref linkend=\"create_new_db\"/> y <xref " 4407"linkend=\"create_new_db_extensions\"/>" 4408 4409#. Tag: para 4410#: installation.xml:1294 4411#, no-c-format 4412msgid "" 4413"The spatial_ref_sys entries found in your dump will be restored, but they " 4414"will not override existing ones in spatial_ref_sys. This is to ensure that " 4415"fixes in the official set will be properly propagated to restored databases. " 4416"If for any reason you really want your own overrides of standard entries " 4417"just don't load the spatial_ref_sys.sql file when creating the new db." 4418msgstr "" 4419"Las entradas que se encuentren en tu copia de seguridad de la tabla " 4420"spatial_ref_sys serán restauradas, pero pero no reescribiran las existentes " 4421"en la nueva tabla spatial_ref_sys. Esto es para asegurar que las soluciones " 4422"en el conjunto oficial se propagarán correctamente para las bases de datos " 4423"restauradas. Si por algún motivo, realmente quieres que tus entradas " 4424"reemplacen las entradas estándar simplemente no cargues el archivo " 4425"spatial_ref_sys.sql al crear la nueva db. " 4426 4427#. Tag: para 4428#: installation.xml:1304 4429#, no-c-format 4430msgid "" 4431"If your database is really old or you know you've been using long deprecated " 4432"functions in your views and functions, you might need to load " 4433"<filename>legacy.sql</filename> for all your functions and views etc. to " 4434"properly come back. Only do this if _really_ needed. Consider upgrading your " 4435"views and functions before dumping instead, if possible. The deprecated " 4436"functions can be later removed by loading <filename>uninstall_legacy.sql</" 4437"filename>." 4438msgstr "" 4439"Si tu base de datos es muy antigua o sabes que has estado utilizando " 4440"funciones rechazadas en tus vistas y funciones, necesitaras cargar el " 4441"fichero <filename>legacy.sql</filename> para todas tus funciones y vistas " 4442"para que funcionen correctamente. Haz esto solamente si es indispensable. " 4443"Considera actualizar tus vistas y funciones antes de hacer una copia de " 4444"seguridad si es posible. Las funciones rechazadas pueden borrarse cargando " 4445"el fichero <filename>uninstall_legacy.sql</filename> después." 4446 4447#. Tag: para 4448#: installation.xml:1320 4449#, no-c-format 4450msgid "" 4451"Restore your backup into your fresh <varname>newdb</varname> database using " 4452"postgis_restore.pl. Unexpected errors, if any, will be printed to the " 4453"standard error stream by psql. Keep a log of those." 4454msgstr "" 4455"Restaura tu copia de seguridad en tu nueva base de datos <varname>newdb</" 4456"varname> utilizando el script postgis_restore.pl. Si aparecen errores " 4457"inesperados, se imprimirán en la consola de psql. Ten un inventario de estos." 4458 4459#. Tag: programlisting 4460#: installation.xml:1328 4461#, no-c-format 4462msgid "" 4463"perl utils/postgis_restore.pl \"/somepath/olddb.backup\" | psql -h localhost " 4464"-p 5432 -U postgres newdb 2> errors.txt" 4465msgstr "" 4466"perl utils/postgis_restore.pl \"/somepath/olddb.backup\" | psql -h localhost " 4467"-p 5432 -U postgres newdb 2> errors.txt" 4468 4469#. Tag: para 4470#: installation.xml:1334 4471#, no-c-format 4472msgid "Errors may arise in the following cases:" 4473msgstr "Los errores se producirán en alguno de estos casos:" 4474 4475#. Tag: para 4476#: installation.xml:1340 4477#, no-c-format 4478msgid "" 4479"Some of your views or functions make use of deprecated PostGIS objects. In " 4480"order to fix this you may try loading <filename>legacy.sql</filename> script " 4481"prior to restore or you'll have to restore to a version of PostGIS which " 4482"still contains those objects and try a migration again after porting your " 4483"code. If the <filename>legacy.sql</filename> way works for you, don't forget " 4484"to fix your code to stop using deprecated functions and drop them loading " 4485"<filename>uninstall_legacy.sql</filename>." 4486msgstr "" 4487"Alguna de tus vistas o funciones hacen uso de funciones rechazadas de " 4488"objetos PostGIS. Para corregir estos deberás intentar cargar el script " 4489"<filename>legacy.sql</filename> antes de restaurar o deberás restaurar a una " 4490"version de PsotGIS que todavía contenga estos objetos e intentar hacer la " 4491"migración otra vez después de migrar tu código. Si el uso del fichero " 4492"<filename>legacy.sql</filename> funciona, no olvides corregir tu código para " 4493"dejar de utilizar funciones rechazadas, y elimina el script <filename>legacy." 4494"sql</filename> ejecutando <filename>uninstall_legacy.sql</filename>." 4495 4496#. Tag: para 4497#: installation.xml:1352 4498#, no-c-format 4499msgid "" 4500"Some custom records of spatial_ref_sys in dump file have an invalid SRID " 4501"value. Valid SRID values are bigger than 0 and smaller than 999000. Values " 4502"in the 999000.999999 range are reserved for internal use while values > " 4503"999999 can't be used at all. All your custom records with invalid SRIDs will " 4504"be retained, with those > 999999 moved into the reserved range, but the " 4505"spatial_ref_sys table would lose a check constraint guarding for that " 4506"invariant to hold and possibly also its primary key ( when multiple invalid " 4507"SRIDS get converted to the same reserved SRID value )." 4508msgstr "" 4509 4510#. Tag: para 4511#: installation.xml:1366 4512#, no-c-format 4513msgid "" 4514"In order to fix this you should copy your custom SRS to a SRID with a valid " 4515"value (maybe in the 910000..910999 range), convert all your tables to the " 4516"new srid (see <xref linkend=\"UpdateGeometrySRID\"/>), delete the invalid " 4517"entry from spatial_ref_sys and re-construct the check(s) with:" 4518msgstr "" 4519"Para corregir esto deberías copiar tus SRS personalizados en in SRID con un " 4520"valor (quizás en el rango de valores 910000..910999), convertir todas las " 4521"tablas al nuevo srid (ver como hacer esto en <xref linkend=" 4522"\"UpdateGeometrySRID\"/>), borrar las entradas invalidas de la tabla " 4523"spatial_ref_sys y reconstruir la o las restricciones chek con:" 4524 4525#. Tag: programlisting 4526#: installation.xml:1373 4527#, no-c-format 4528msgid "" 4529"ALTER TABLE spatial_ref_sys ADD CONSTRAINT spatial_ref_sys_srid_check check " 4530"(srid > 0 AND srid < 999000 );" 4531msgstr "" 4532"ALTER TABLE spatial_ref_sys ADD CONSTRAINT spatial_ref_sys_srid_check check " 4533"(srid > 0 AND srid < 999000 );" 4534 4535#. Tag: programlisting 4536#: installation.xml:1375 4537#, no-c-format 4538msgid "ALTER TABLE spatial_ref_sys ADD PRIMARY KEY(srid));" 4539msgstr "ALTER TABLE spatial_ref_sys ADD PRIMARY KEY(srid));" 4540 4541#. Tag: title 4542#: installation.xml:1386 4543#, no-c-format 4544msgid "Common Problems during installation" 4545msgstr "" 4546 4547#. Tag: para 4548#: installation.xml:1387 4549#, no-c-format 4550msgid "" 4551"There are several things to check when your installation or upgrade doesn't " 4552"go as you expected." 4553msgstr "" 4554"Hay varias cosas a comprobar cuando la instalación o actualización no han " 4555"fusionado como se esperaba." 4556 4557#. Tag: para 4558#: installation.xml:1394 4559#, no-c-format 4560msgid "" 4561"Check that you have installed PostgreSQL &min_postgres_version; or newer, " 4562"and that you are compiling against the same version of the PostgreSQL source " 4563"as the version of PostgreSQL that is running. Mix-ups can occur when your " 4564"(Linux) distribution has already installed PostgreSQL, or you have otherwise " 4565"installed PostgreSQL before and forgotten about it. PostGIS will only work " 4566"with PostgreSQL &min_postgres_version; or newer, and strange, unexpected " 4567"error messages will result if you use an older version. To check the version " 4568"of PostgreSQL which is running, connect to the database using psql and run " 4569"this query:" 4570msgstr "" 4571"Comprueba que tienes instalado PostgreSQL &min_postgres_version; o " 4572"posterior, y que estas compilando para esta version de PostgreSQL que estas " 4573"utilizando. Se pueden producir confusiones cuando tu distribución (Linux)ya " 4574"tiene instalada PostgreSQL, o has instalado antes PostgreSQL y lo has " 4575"olvidado. PostGIS solo funcionará con PostgreSQL &min_postgres_version; o " 4576"superior, y errores inesperados o extraños pueden ocurrir si utilizas una " 4577"version mas antigua. Para comprobar la version de PostgreSQL que esta " 4578"instalada y ejecutándose, conectare a la base de datos utilizando psql y " 4579"ejecuta la siguiente consulta:" 4580 4581#. Tag: programlisting 4582#: installation.xml:1407 4583#, no-c-format 4584msgid "SELECT version();" 4585msgstr "SELECT version();" 4586 4587#. Tag: para 4588#: installation.xml:1409 4589#, no-c-format 4590msgid "" 4591"If you are running an RPM based distribution, you can check for the " 4592"existence of pre-installed packages using the <command>rpm</command> command " 4593"as follows: <command>rpm -qa | grep postgresql</command>" 4594msgstr "" 4595"Si estas ejecutando una version basada en una distribución RPM, puedes " 4596"comprobar si existen paquetes pre-instalados utilizando el comando " 4597"<command>rpm</command> como sigue: <command>rpm -qa | grep postgresql</" 4598"command>" 4599 4600#. Tag: para 4601#: installation.xml:1417 4602#, no-c-format 4603msgid "" 4604"If your upgrade fails, make sure you are restoring into a database that " 4605"already has PostGIS installed." 4606msgstr "" 4607"Si tienes errores en la actualización, asegúrate de que estas restaurando tu " 4608"base de datos en una que tenga instalada PostGIS." 4609 4610#. Tag: programlisting 4611#: installation.xml:1418 4612#, no-c-format 4613msgid "SELECT postgis_full_version();" 4614msgstr "SELECT postgis_full_version();" 4615 4616#. Tag: para 4617#: installation.xml:1422 4618#, no-c-format 4619msgid "" 4620"Also check that configure has correctly detected the location and version of " 4621"PostgreSQL, the Proj4 library and the GEOS library." 4622msgstr "" 4623"Comprueba que tu configuración detecta la ubicación y la version correctas " 4624"de PostgreSQL, la librería Proj4 y la librería GEOS." 4625 4626#. Tag: para 4627#: installation.xml:1429 4628#, no-c-format 4629msgid "" 4630"The output from configure is used to generate the <filename>postgis_config." 4631"h</filename> file. Check that the <varname>POSTGIS_PGSQL_VERSION</varname>, " 4632"<varname>POSTGIS_PROJ_VERSION</varname> and <varname>POSTGIS_GEOS_VERSION</" 4633"varname> variables have been set correctly." 4634msgstr "" 4635"La salida de configure se utiliza para generar el fichero " 4636"<filename>postgis_config.h</filename>. Comprueba que la variables " 4637"<varname>POSTGIS_PGSQL_VERSION</varname>, <varname>POSTGIS_PROJ_VERSION</" 4638"varname> y <varname>POSTGIS_GEOS_VERSION</varname>, han sido bien " 4639"configuradas." 4640 4641#. Tag: title 4642#: installation.xml:1442 4643#, no-c-format 4644msgid "Loader/Dumper" 4645msgstr "Cargador/Dumper" 4646 4647#. Tag: para 4648#: installation.xml:1444 4649#, no-c-format 4650msgid "" 4651"The data loader and dumper are built and installed automatically as part of " 4652"the PostGIS build. To build and install them manually:" 4653msgstr "" 4654"El cargador y dumper de datos se compila e instala de forma automática como " 4655"parte de la distribución de PostGIS. Para compilar e instalar de forma " 4656"manual puedes ejecutar:" 4657 4658#. Tag: programlisting 4659#: installation.xml:1449 4660#, no-c-format 4661msgid "" 4662"# cd postgis-&last_release_version;/loader\n" 4663"# make\n" 4664"# make install" 4665msgstr "" 4666"# cd postgis-&last_release_version;/loader\n" 4667"# make\n" 4668"# make install" 4669 4670#. Tag: para 4671#: installation.xml:1451 4672#, no-c-format 4673msgid "" 4674"The loader is called <filename>shp2pgsql</filename> and converts ESRI Shape " 4675"files into SQL suitable for loading in PostGIS/PostgreSQL. The dumper is " 4676"called <filename>pgsql2shp</filename> and converts PostGIS tables (or " 4677"queries) into ESRI Shape files. For more verbose documentation, see the " 4678"online help, and the manual pages." 4679msgstr "" 4680"El cargador se llama <filename>shp2pgsql</filename> y convierte ficheros " 4681"Shape de ESRI en sentencias SQL necesarias para cargarlo en PostGIS/" 4682"PostgreSQL. El dumper se llama <filename>pgsql2shp</filename> y convierte " 4683"tablas PostGIS (o sentencias) en ficheros Shape de ESRI. Para mayor " 4684"información, puedes ver la información en linea y las pagnas del manual." 4685