1# SOME DESCRIPTIVE TITLE. 2# 3# Translators: 4# pibinko <pibinko@gmail.com>, 2013-2014 5msgid "" 6msgstr "" 7"Project-Id-Version: PostGIS\n" 8"Report-Msgid-Bugs-To: https://bugs.kde.org\n" 9"POT-Creation-Date: 2020-02-01 19:38+0000\n" 10"PO-Revision-Date: 2018-07-22 03:18+0000\n" 11"Last-Translator: georgersilva <georger.silva@gmail.com>\n" 12"Language-Team: Italian (Italy) (http://www.transifex.com/postgis/postgis/" 13"language/it_IT/)\n" 14"Language: it_IT\n" 15"MIME-Version: 1.0\n" 16"Content-Type: text/plain; charset=UTF-8\n" 17"Content-Transfer-Encoding: 8bit\n" 18"Plural-Forms: nplurals=2; plural=(n != 1);\n" 19 20#. Tag: title 21#: faq_raster.xml:3 22#, no-c-format 23msgid "PostGIS Raster Frequently Asked Questions" 24msgstr "Domande frequenti su PostGIS raster" 25 26#. Tag: para 27#: faq_raster.xml:8 28#, no-c-format 29msgid "Where can I find out more about the PostGIS Raster Project?" 30msgstr "Dove posso trovare altre informazioni sul progetto PostGIS Raster?" 31 32#. Tag: para 33#: faq_raster.xml:12 34#, no-c-format 35msgid "" 36"Refer to the <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster" 37"\">PostGIS Raster home page</ulink>." 38msgstr "" 39"Visita la <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster\">home " 40"page</ulink> di PostGIS Raster." 41 42#. Tag: para 43#: faq_raster.xml:18 44#, no-c-format 45msgid "" 46"Are there any books or tutorials to get me started with this wonderful " 47"invention?" 48msgstr "" 49"Ci sono libri o manuali che mi possano introdurre a questa meravigliosa " 50"invenzione?" 51 52#. Tag: para 53#: faq_raster.xml:22 54#, no-c-format 55msgid "" 56"There is a full length beginner tutorial <ulink url=\"http://trac.osgeo.org/" 57"postgis/wiki/WKTRasterTutorial01\"> Intersecting vector buffers with large " 58"raster coverage using PostGIS Raster</ulink>. Jorge has a series of blog " 59"articles on PostGIS Raster that demonstrate how to load raster data as well " 60"as cross compare to same tasks in Oracle GeoRaster. Check out <ulink url=" 61"\"http://gis4free.wordpress.com/category/postgis-raster/\">Jorge's PostGIS " 62"Raster / Oracle GeoRaster Series</ulink>. There is a whole chapter (more " 63"than 35 pages of content) dedicated to PostGIS Raster with free code and " 64"data downloads at <ulink url=\"https://www.manning.com/books/postgis-in-" 65"action-second-edition\">PostGIS in Action - Raster chapter</ulink>. You can " 66"<ulink url=\"http://www.postgis.us/page_buy_book\">buy PostGIS in Action</" 67"ulink> now from Manning in hard-copy (significant discounts for bulk " 68"purchases) or just the E-book format. You can also buy from Amazon and " 69"various other book distributors. All hard-copy books come with a free coupon " 70"to download the E-book version." 71msgstr "" 72 73#. Tag: para 74#: faq_raster.xml:29 75#, no-c-format 76msgid "" 77"Here is a review from a PostGIS Raster user <ulink url=\"http://" 78"fuzzytolerance.info/blog/2010/10/26/2010-10-26-postgis-raster-ftw/\">PostGIS " 79"raster applied to land classification urban forestry</ulink>" 80msgstr "" 81 82#. Tag: para 83#: faq_raster.xml:36 84#, no-c-format 85msgid "How do I install Raster support in my PostGIS database?" 86msgstr "Come installo il supporto Raster nel mio database PostGIS?" 87 88#. Tag: para 89#: faq_raster.xml:40 90#, no-c-format 91msgid "" 92"Starting with PostGIS 2.0 PostGIS Raster is fully integrated, so it will be " 93"compiled when you compile PostGIS." 94msgstr "" 95 96#. Tag: para 97#: faq_raster.xml:41 98#, no-c-format 99msgid "" 100"Instructions for installing and running under windows are available at " 101"<ulink url=\"http://gis4free.wordpress.com/2011/03/10/how-to-install-and-" 102"configure-postgis-raster-on-windows/\">How to Install and Configure PostGIS " 103"raster on windows</ulink>" 104msgstr "" 105"Le istruzioni per installare ed eseguire il programma sotto Windows sono " 106"disponibili alla pagina <ulink url=\"http://gis4free.wordpress." 107"com/2011/03/10/how-to-install-and-configure-postgis-raster-on-windows/\">How " 108"to Install and Configure PostGIS raster on windows</ulink>" 109 110#. Tag: para 111#: faq_raster.xml:42 112#, no-c-format 113msgid "" 114"If you are on windows, you can compile yourself, or use the <ulink url=" 115"\"http://postgis.net/windows_downloads\">pre-compiled PostGIS Raster windows " 116"binaries</ulink>. If you are on Mac OSX Leopard or Snow Leopard, there are " 117"binaries available at <ulink url=\"http://www.kyngchaos.com/software/postgres" 118"\">Kyng Chaos Mac OSX PostgreSQL/GIS binaries</ulink>." 119msgstr "" 120 121#. Tag: para 122#: faq_raster.xml:48 123#, no-c-format 124msgid "" 125"For other platforms, install PostGIS from your software repository. For more " 126"details about compiling from source, please refer to <ulink url=\"http://" 127"trac.osgeo.org/postgis/wiki/WKTRaster/Documentation01#a2.3-" 128"CompilingandInstallingfromSources\">Installing PostGIS Raster from source</" 129"ulink>" 130msgstr "" 131 132#. Tag: para 133#: faq_raster.xml:54 134#, no-c-format 135msgid "" 136"I get error could not load library \"C:/Program Files/PostgreSQL/8.4/lib/" 137"rtpostgis.dll\": The specified module could not be found. or could not load " 138"library on Linux when trying to run rtpostgis.sql" 139msgstr "" 140"Ottengo l'errore could not load library \"C:/Program Files/PostgreSQL/8.4/" 141"lib/rtpostgis.dll\": The specified module could not be found. or could not " 142"load library on Linux when trying to run rtpostgis.sql" 143 144#. Tag: para 145#: faq_raster.xml:59 146#, no-c-format 147msgid "" 148"rtpostgis.so/dll is built with dependency on libgdal.dll/so. Make sure for " 149"Windows you have libgdal-1.dll in the bin folder of your PostgreSQL install. " 150"For Linux libgdal has to be in your path or bin folder." 151msgstr "" 152"rtpostgis.so/dll is viene compilato con la dipendenza da libgdal.dll/so. " 153"Assicurati su Windows di avere libgdal-1.dll nella cartellabin folder della " 154"tua installazione PostgreSQL. Per Linux, libgdal deve essere nel tuo path o " 155"nella cartella bin." 156 157#. Tag: para 158#: faq_raster.xml:61 159#, no-c-format 160msgid "" 161"You may also run into different errors if you don't have PostGIS installed " 162"in your database. Make sure to install PostGIS first in your database before " 163"trying to install the raster support." 164msgstr "" 165"Potresti anche riscontrare errori diversi se non hai PostGIS installato nel " 166"tuo database. Assicurati di installare PostGIS prima di provare a installare " 167"il supporto raster." 168 169#. Tag: para 170#: faq_raster.xml:68 171#, no-c-format 172msgid "How do I load Raster data into PostGIS?" 173msgstr "Come carico i dati raster in PostGIS?" 174 175#. Tag: para 176#: faq_raster.xml:72 177#, no-c-format 178msgid "" 179"The latest version of PostGIS comes packaged with a <varname>raster2pgsql</" 180"varname> raster loader executable capable of loading many kinds of rasters " 181"and also generating lower resolution overviews without any additional " 182"software. Please refer to <xref linkend=\"RT_Raster_Loader\"/> for more " 183"details." 184msgstr "" 185 186#. Tag: para 187#: faq_raster.xml:78 188#, no-c-format 189msgid "What kind of raster file formats can I load into my database?" 190msgstr "Che tipo di formati raster posso caricare nel mio database?" 191 192#. Tag: para 193#: faq_raster.xml:82 194#, no-c-format 195msgid "" 196"Any that your GDAL library supports. GDAL supported formats are documented " 197"<ulink url=\"http://www.gdal.org/formats_list.html\">GDAL File Formats</" 198"ulink>." 199msgstr "" 200"Qualsiasi formato supportato dalla tua libreria GDAL. I formati supportati " 201"da GDAL sono <ulink url=\"http://www.gdal.org/formats_list.html" 202"\">documentati</ulink>." 203 204#. Tag: para 205#: faq_raster.xml:83 206#, no-c-format 207msgid "" 208"Your particular GDAL install may not support all formats. To verify the ones " 209"supported by your particular GDAL install, you can use" 210msgstr "" 211"La tua particolare versione di GDAL potrebbe non supportare tutti i formati. " 212"Per verificare di preciso, puoi usare" 213 214#. Tag: programlisting 215#: faq_raster.xml:84 216#, no-c-format 217msgid "raster2pgsql -G" 218msgstr "raster2pgsql -G" 219 220#. Tag: para 221#: faq_raster.xml:90 222#, no-c-format 223msgid "Can I export my PostGIS raster data to other raster formats?" 224msgstr "Posso esportare i miei dati raster PostGIS ad altri formati raster?" 225 226#. Tag: para 227#: faq_raster.xml:94 228#, no-c-format 229msgid "<para>Yes</para>" 230msgstr "<para>Sì</para>" 231 232#. Tag: para 233#: faq_raster.xml:95 234#, no-c-format 235msgid "" 236"GDAL has a PostGIS raster driver, but is only compiled in if you choose to " 237"compile with PostgreSQL support." 238msgstr "" 239 240#. Tag: para 241#: faq_raster.xml:96 242#, no-c-format 243msgid "" 244"The driver currently doesn't support irregularly blocked rasters, although " 245"you can store irregularly blocked rasters in PostGIS raster data type." 246msgstr "" 247"Al momento il driver non supporta i raster a blocchi irregolari, sebbene sia " 248"possibile memorizzare blocchi irregolari nel tipo dati PostGIS raster." 249 250#. Tag: para 251#: faq_raster.xml:98 252#, no-c-format 253msgid "" 254"If you are compiling from source, you need to include in your configure " 255"<programlisting>--with-pg=path/to/pg_config</programlisting> to enable the " 256"driver. Refer to <ulink url=\"http://trac.osgeo.org/gdal/wiki/BuildHints" 257"\">GDAL Build Hints</ulink> for tips on building GDAL against in various OS " 258"platforms." 259msgstr "" 260"Se stai compilando il programma a partire dal sorgente, devi includere nel " 261"sorgente l'opzione <programlisting>--with-pg=path/to/pg_config</" 262"programlisting> per abilitare il driver. Ti rimandiamo alla pagina <ulink " 263"url=\"http://trac.osgeo.org/gdal/wiki/BuildHints\">GDAL Build Hints</ulink> " 264"per suggerimenti sulla compilazione di GDAL su divrse piattaforme." 265 266#. Tag: para 267#: faq_raster.xml:103 268#, no-c-format 269msgid "" 270"If your version of GDAL is compiled with the PostGIS Raster driver you " 271"should see PostGIS Raster in list when you do" 272msgstr "" 273"Se la tua versione di GDAL è compilata con il driver PostGIS Raster, " 274"dovresti trovare PostGIS Raster nella lista quando esegui" 275 276#. Tag: programlisting 277#: faq_raster.xml:105 278#, no-c-format 279msgid "gdalinfo --formats" 280msgstr "gdalinfo --formats" 281 282#. Tag: para 283#: faq_raster.xml:107 284#, no-c-format 285msgid "To get a summary about your raster via GDAL use gdalinfo:" 286msgstr "" 287"Per ottenere informazioni riassuntive sul tuo raster tramite GDAL, utilizza " 288"gdalinfo:" 289 290#. Tag: programlisting 291#: faq_raster.xml:108 292#, no-c-format 293msgid "" 294"gdalinfo \"PG:host=localhost port=5432 dbname='mygisdb' user='postgres' " 295"password='whatever' schema='someschema' table=sometable\"" 296msgstr "" 297"gdalinfo \"PG:host=localhost port=5432 dbname='mygisdb' user='postgres' " 298"password='whatever' schema='someschema' table=sometable\"" 299 300#. Tag: para 301#: faq_raster.xml:111 302#, no-c-format 303msgid "" 304"To export data to other raster formats, use gdal_translate the below will " 305"export all data from a table to a PNG file at 10% size." 306msgstr "" 307"Per esportare dati verso altri formati raster, utilizza gdal_translate. " 308"L'esempio sotto esporterà tutti i dati da una tabella a un file PNG col 10% " 309"della dimensione." 310 311#. Tag: para 312#: faq_raster.xml:113 313#, no-c-format 314msgid "" 315"Depending on your pixel band types, some translations may not work if the " 316"export format does not support that Pixel type. For example floating point " 317"band types and 32 bit unsigned ints will not translate easily to JPG or some " 318"others." 319msgstr "" 320"A seconda dei tipi di banda dei pixel, alcune conversioni non " 321"funzioneranno, se il formato di esportazione non supprta un dato tipo di " 322"pixel. Per esempio, i tipi di banda a virgola mobile, o gli interi senza " 323"segno a 32 bit non si convertiranno bene in JPEG." 324 325#. Tag: para 326#: faq_raster.xml:116 327#, no-c-format 328msgid "Here is an example simple translation" 329msgstr "Ecco un esempio di una semplice conversione" 330 331#. Tag: programlisting 332#: faq_raster.xml:117 333#, no-c-format 334msgid "" 335"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost port=5432 " 336"dbname='mygisdb' user='postgres' password='whatever' schema='someschema' " 337"table=sometable\" C:\\somefile.png" 338msgstr "" 339 340#. Tag: para 341#: faq_raster.xml:118 342#, no-c-format 343msgid "" 344"You can also use SQL where clauses in your export using the where=... in " 345"your driver connection string. Below are some using a where clause" 346msgstr "" 347"Puoi anche utilizzare la clausola SQL WHERE nell'esportazione, riportando il " 348"testo where=.... nella stringa di collegamento del driver. Sotto si " 349"riportano alcuni esempi che utilizzano la clausola where" 350 351#. Tag: programlisting 352#: faq_raster.xml:120 353#, no-c-format 354msgid "" 355"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost port=5432 " 356"dbname='mygisdb' user='postgres' password='whatever' schema='someschema' " 357"table=sometable where='filename=\\'abcd.sid\\''\" \" C:\\somefile.png" 358msgstr "" 359 360#. Tag: programlisting 361#: faq_raster.xml:121 362#, no-c-format 363msgid "" 364"gdal_translate -of PNG -outsize 10% 10% \"PG:host=localhost port=5432 " 365"dbname='mygisdb' user='postgres' password='whatever' schema='someschema' " 366"table=sometable where='ST_Intersects(rast, " 367"ST_SetSRID(ST_Point(-71.032,42.3793),4326) )' \" C:\\intersectregion.png" 368msgstr "" 369 370#. Tag: para 371#: faq_raster.xml:122 372#, no-c-format 373msgid "" 374"To see more examples and syntax refer to <ulink url=\"http://trac.osgeo.org/" 375"gdal/wiki/frmts_wtkraster.html#a3.2-Readingrasterdatafromthedatabase" 376"\">Reading Raster Data of PostGIS Raster section</ulink>" 377msgstr "" 378"Per vedere altri esempi e sintassi, si rimanda al paragrafo <ulink url=" 379"\"http://trac.osgeo.org/gdal/wiki/frmts_wtkraster.html#a3.2-" 380"Readingrasterdatafromthedatabase\">Leggere dati raster da un raster PostGIS</" 381"ulink>" 382 383#. Tag: para 384#: faq_raster.xml:127 385#, no-c-format 386msgid "" 387"Are their binaries of GDAL available already compiled with PostGIS Raster " 388"suppport?" 389msgstr "I binari di GDAL sono già disponibili con il supporto raster PostGIS?" 390 391#. Tag: para 392#: faq_raster.xml:129 393#, no-c-format 394msgid "" 395"Yes. Check out the page <ulink url=\"http://trac.osgeo.org/gdal/wiki/" 396"DownloadingGdalBinaries\">GDAL Binaries</ulink> page. Any compiled with " 397"PostgreSQL support should have PostGIS Raster in them." 398msgstr "" 399"Sì. Controlla la pagina <ulink url=\"http://trac.osgeo.org/gdal/wiki/" 400"DownloadingGdalBinaries\">GDAL Binaries</ulink>. Qualsiasi versione " 401"compilata con l'opzione di supporto per PostgreSQL dovrebbe avere il " 402"supporto per i raster PostGIS." 403 404#. Tag: para 405#: faq_raster.xml:131 406#, no-c-format 407msgid "" 408"PostGIS Raster is undergoing many changes. If you want to get the latest " 409"nightly build for Windows -- then check out the Tamas Szekeres nightly " 410"builds built with Visual Studio which contain GDAL trunk, Python Bindings " 411"and MapServer executables and PostGIS Raster driver built-in. Just click the " 412"SDK bat and run your commands from there. <ulink url=\"www.gisinternals.com" 413"\">http://www.gisinternals.com</ulink>. Also available are VS project files." 414msgstr "" 415 416#. Tag: para 417#: faq_raster.xml:135 418#, no-c-format 419msgid "" 420"<ulink url=\"http://fwtools.maptools.org/\">FWTools latest stable version " 421"for Windows is compiled with Raster support</ulink>." 422msgstr "" 423"La versione più recente e stabile di <ulink url=\"http://fwtools.maptools." 424"org/\">FWTools per Windows</ulink> è compilata con il supporto raster." 425 426#. Tag: para 427#: faq_raster.xml:141 428#, no-c-format 429msgid "What tools can I use to view PostGIS raster data?" 430msgstr "Quali strumenti posso usare per visualizzare i dati raster PostGIS?" 431 432#. Tag: para 433#: faq_raster.xml:145 434#, no-c-format 435msgid "" 436"You can use MapServer compiled with GDAL 1.7+ and PostGIS Raster driver " 437"support to view Raster data. QGIS supports viewing of PostGIS Raster if you " 438"have PostGIS raster driver installed." 439msgstr "" 440 441#. Tag: para 442#: faq_raster.xml:147 443#, no-c-format 444msgid "" 445"In theory any tool that renders data using GDAL can support PostGIS raster " 446"data or support it with fairly minimal effort. Again for Windows, Tamas' " 447"binaries <ulink url=\"www.gisinternals.com\">http://www.gisinternals.com</" 448"ulink> are a good choice if you don't want the hassle of having to setup to " 449"compile your own." 450msgstr "" 451 452#. Tag: para 453#: faq_raster.xml:154 454#, no-c-format 455msgid "How can I add a PostGIS raster layer to my MapServer map?" 456msgstr "" 457"Come posso aggiungere uno strato raster PostGIS in una mappa di MapServer?" 458 459#. Tag: para 460#: faq_raster.xml:158 461#, no-c-format 462msgid "" 463"First you need GDAL 1.7 or higher compiled with PostGIS raster support. GDAL " 464"1.8 or above is preferred since many issues have been fixed in 1.8 and more " 465"PostGIS raster issues fixed in trunk version." 466msgstr "" 467"Anzitutto ti serve GDAL 1.7 o superiore compilato con il supporto per raster " 468"PostGIS. E consigliata la versione 1.8 o superiore, dato che quest'ultima " 469"risolve numerosi problemi, e altri problemi con i raster PostGIS sono " 470"risolti nella versione trunk." 471 472#. Tag: para 473#: faq_raster.xml:160 474#, no-c-format 475msgid "" 476"You can much like you can with any other raster. Refer to <ulink url=" 477"\"http://mapserver.org/input/raster.html\">MapServer Raster processing " 478"options</ulink> for list of various processing functions you can use with " 479"MapServer raster layers." 480msgstr "" 481 482#. Tag: para 483#: faq_raster.xml:163 484#, no-c-format 485msgid "" 486"What makes PostGIS raster data particularly interesting, is that since each " 487"tile can have various standard database columns, you can segment it in your " 488"data source" 489msgstr "" 490 491#. Tag: para 492#: faq_raster.xml:165 493#, no-c-format 494msgid "" 495"Below is an example of how you would define a PostGIS raster layer in " 496"MapServer." 497msgstr "" 498"Sotto trovi un esempio di come definire uno strato raster PostGIS in " 499"MapServer." 500 501#. Tag: para 502#: faq_raster.xml:166 503#, no-c-format 504msgid "" 505"The mode=2 is required for tiled rasters and was added in PostGIS 2.0 and " 506"GDAL 1.8 drivers. This does not exist in GDAL 1.7 drivers." 507msgstr "" 508"L'opzione mode=2 serve per i raster con tile ed è stata aggiunta in PostGIS " 509"2.0 con il driver GDAL 1.8. Non esiste nei driver GDAL 1.7." 510 511#. Tag: programlisting 512#: faq_raster.xml:167 513#, no-c-format 514msgid "" 515"-- displaying raster with standard raster options\n" 516"LAYER\n" 517" NAME coolwktraster\n" 518" TYPE raster\n" 519" STATUS ON\n" 520" DATA \"PG:host=localhost port=5432 dbname='somedb' user='someuser' " 521"password='whatever'\n" 522" schema='someschema' table='cooltable' mode='2'\"\n" 523" PROCESSING \"NODATA=0\"\n" 524" PROCESSING \"SCALE=AUTO\"\n" 525" #... other standard raster processing functions here\n" 526" #... classes are optional but useful for 1 band data\n" 527" CLASS\n" 528" NAME \"boring\"\n" 529" EXPRESSION ([pixel] < 20)\n" 530" COLOR 250 250 250\n" 531" END\n" 532" CLASS\n" 533" NAME \"mildly interesting\"\n" 534" EXPRESSION ([pixel] > 20 AND [pixel] < 1000)\n" 535" COLOR 255 0 0\n" 536" END\n" 537" CLASS\n" 538" NAME \"very interesting\"\n" 539" EXPRESSION ([pixel] >= 1000)\n" 540" COLOR 0 255 0\n" 541" END\n" 542"END" 543msgstr "" 544 545#. Tag: programlisting 546#: faq_raster.xml:169 547#, no-c-format 548msgid "" 549"-- displaying raster with standard raster options and a where clause\n" 550"LAYER\n" 551" NAME soil_survey2009\n" 552" TYPE raster\n" 553" STATUS ON\n" 554" DATA \"PG:host=localhost port=5432 dbname='somedb' user='someuser' " 555"password='whatever'\n" 556" schema='someschema' table='cooltable' " 557"where='survey_year=2009' mode='2'\"\n" 558" PROCESSING \"NODATA=0\"\n" 559" #... other standard raster processing functions here\n" 560" #... classes are optional but useful for 1 band data\n" 561"END" 562msgstr "" 563 564#. Tag: para 565#: faq_raster.xml:177 566#, no-c-format 567msgid "What functions can I currently use with my raster data?" 568msgstr "Quali funzioni posso attualmente utilizzare con i dati raster?" 569 570#. Tag: para 571#: faq_raster.xml:181 572#, no-c-format 573msgid "" 574"Refer to the list of <xref linkend=\"RT_reference\"/>. There are more, but " 575"this is still a work in progress." 576msgstr "" 577"Ti rimandiamo alla lista <xref linkend=\"RT_reference\"/>. Ce ne sono anche " 578"altre, ma si tratta di funzioni in via di sviluppo." 579 580#. Tag: para 581#: faq_raster.xml:183 582#, no-c-format 583msgid "" 584"Refer to the <ulink url=\"http://trac.osgeo.org/postgis/wiki/WKTRaster/" 585"PlanningAndFunding\">PostGIS Raster roadmap page</ulink> for details of what " 586"you can expect in the future." 587msgstr "" 588"Ti rimandiamo alla pagina <ulink url=\"http://trac.osgeo.org/postgis/wiki/" 589"WKTRaster/PlanningAndFunding\">PostGIS Raster roadmap page</ulink> per i " 590"dettagli sugli sviluppi attesti in futuro." 591 592#. Tag: para 593#: faq_raster.xml:191 594#, no-c-format 595msgid "" 596"I am getting error ERROR: function st_intersects(raster, unknown) is not " 597"unique or st_union(geometry,text) is not unique. How do I fix?" 598msgstr "" 599"Ottengo un errore ERROR: function st_intersects(raster, unknown) is not " 600"unique or st_union(geometry,text) is not unique. Come lo aggiusto?" 601 602#. Tag: para 603#: faq_raster.xml:195 604#, no-c-format 605msgid "" 606"The function is not unique error happens if one of your arguments is a " 607"textual representation of a geometry instead of a geometry. In these cases, " 608"PostgreSQL marks the textual representation as an unknown type, which means " 609"it can fall into the st_intersects(raster, geometry) or st_intersects(raster," 610"raster) thus resulting in a non-unique case since both functions can in " 611"theory support your request. To prevent this, you need to cast the textual " 612"representation of the geometry to a geometry." 613msgstr "" 614 615#. Tag: para 616#: faq_raster.xml:196 617#, no-c-format 618msgid "For example if your code looks like this:" 619msgstr "Per esempio, se il tuo codice è tipo:" 620 621#. Tag: programlisting 622#: faq_raster.xml:197 623#, no-c-format 624msgid "" 625"SELECT rast\n" 626" FROM my_raster\n" 627" WHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)');" 628msgstr "" 629"SELECT rast\n" 630" FROM my_raster\n" 631" WHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)');" 632 633#. Tag: para 634#: faq_raster.xml:198 635#, no-c-format 636msgid "" 637"Cast the textual geometry representation to a geometry by changing your code " 638"to this:" 639msgstr "" 640"Dei eseguire il cast della geometria come testo a una geometria vera e " 641"propria in questo modo:" 642 643#. Tag: programlisting 644#: faq_raster.xml:199 645#, no-c-format 646msgid "" 647"SELECT rast\n" 648" FROM my_raster\n" 649" WHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)'::geometry);" 650msgstr "" 651"SELECT rast\n" 652" FROM my_raster\n" 653" WHERE ST_Intersects(rast, 'SRID=4326;POINT(-10 10)'::geometry);" 654 655#. Tag: para 656#: faq_raster.xml:205 657#, no-c-format 658msgid "" 659"How is PostGIS Raster different from Oracle GeoRaster (SDO_GEORASTER) and " 660"SDO_RASTER types?" 661msgstr "" 662"Quali sono le differenze tra i raster di PostGIS, i GeoRaster di Oracle " 663"(SDO_GEORASTER) e i tipi SDO_RASTER?" 664 665#. Tag: para 666#: faq_raster.xml:209 667#, no-c-format 668msgid "" 669"For a more extensive discussion on this topic, check out Jorge Arévalo " 670"<ulink url=\"http://gis4free.wordpress.com/2010/07/19/oracle-georaster-part-" 671"i/\">Oracle GeoRaster and PostGIS Raster: First impressions </ulink>" 672msgstr "" 673"Per una discussione dettagliata su questo argomento, dai un'occhiata " 674"all'articolo di Jorge Arévalo <ulink url=\"http://gis4free.wordpress." 675"com/2010/07/19/oracle-georaster-part-i/\">Oracle GeoRaster and PostGIS " 676"Raster: First impressions </ulink>" 677 678#. Tag: para 679#: faq_raster.xml:210 680#, no-c-format 681msgid "" 682"The major advantage of one-georeference-by-raster over one-georeference-by-" 683"layer is to allow:" 684msgstr "" 685 686#. Tag: para 687#: faq_raster.xml:211 688#, no-c-format 689msgid "" 690"* coverages to be not necessarily rectangular (which is often the case of " 691"raster coverage covering large extents. See the possible raster arrangements " 692"in the documentation)" 693msgstr "" 694 695#. Tag: para 696#: faq_raster.xml:212 697#, no-c-format 698msgid "" 699"* rasters to overlaps (which is necessary to implement lossless vector to " 700"raster conversion)" 701msgstr "" 702 703#. Tag: para 704#: faq_raster.xml:213 705#, no-c-format 706msgid "" 707"These arrangements are possible in Oracle as well, but they imply the " 708"storage of multiple SDO_GEORASTER objects linked to as many SDO_RASTER " 709"tables. A complex coverage can lead to hundreds of tables in the database. " 710"With PostGIS Raster you can store a similar raster arrangement into a unique " 711"table." 712msgstr "" 713 714#. Tag: para 715#: faq_raster.xml:218 716#, no-c-format 717msgid "" 718"It's a bit like if PostGIS would force you to store only full rectangular " 719"vector coverage without gaps or overlaps (a perfect rectangular topological " 720"layer). This is very practical in some applications but practice has shown " 721"that it is not realistic or desirable for most geographical coverages. " 722"Vector structures needs the flexibility to store discontinuous and non-" 723"rectangular coverages. We think it is a big advantage that raster structure " 724"should benefit as well." 725msgstr "" 726 727#. Tag: para 728#: faq_raster.xml:226 729#, no-c-format 730msgid "" 731"raster2pgsql load of large file fails with String of N bytes is too long for " 732"encoding conversion?" 733msgstr "" 734 735#. Tag: para 736#: faq_raster.xml:230 737#, no-c-format 738msgid "" 739"raster2pgsql doesn't make any connections to your database when generating " 740"the file to load. If your database has set an explicit client encoding " 741"different from your database encoding, then when loading large raster files " 742"(above 30 MB in size), you may run into a <code>bytes is too long for " 743"encoding conversion</code>." 744msgstr "" 745 746#. Tag: para 747#: faq_raster.xml:232 748#, no-c-format 749msgid "" 750"This generally happens if for example you have your database in UTF8, but to " 751"support windows apps, you have the client encoding set to <code>WIN1252</" 752"code>." 753msgstr "" 754 755#. Tag: para 756#: faq_raster.xml:233 757#, no-c-format 758msgid "" 759"To work around this make sure the client encoding is the same as your " 760"database encoding during load. You can do this by explicitly setting the " 761"encoding in your load script. Example, if you are on windows:" 762msgstr "" 763 764#. Tag: programlisting 765#: faq_raster.xml:234 766#, no-c-format 767msgid "set PGCLIENTENCODING=UTF8" 768msgstr "" 769 770#. Tag: para 771#: faq_raster.xml:235 772#, no-c-format 773msgid "If you are on Unix/Linux" 774msgstr "" 775 776#. Tag: programlisting 777#: faq_raster.xml:236 778#, no-c-format 779msgid "export PGCLIENTENCODING=UTF8" 780msgstr "" 781 782#. Tag: para 783#: faq_raster.xml:237 784#, no-c-format 785msgid "" 786"Gory details of this issue are detailed in <ulink url=\"http://trac.osgeo." 787"org/postgis/ticket/2209\">http://trac.osgeo.org/postgis/ticket/2209</ulink>" 788msgstr "" 789 790#. Tag: para 791#: faq_raster.xml:243 792#, no-c-format 793msgid "" 794"I'm getting error <code>ERROR: RASTER_fromGDALRaster: Could not open bytea " 795"with GDAL. Check that the bytea is of a GDAL supported format.</code> when " 796"using ST_FromGDALRaster or <code>ERROR: rt_raster_to_gdal: Could not load " 797"the output GDAL driver</code> when trying to use ST_AsPNG or other raster " 798"input functions." 799msgstr "" 800 801#. Tag: para 802#: faq_raster.xml:248 803#, no-c-format 804msgid "" 805"As of PostGIS 2.1.3 and 2.0.5, a security change was made to by default " 806"disable all GDAL drivers and out of db rasters. The release notes are at " 807"<ulink url=\"http://postgis.net/2014/05/19/postgis-2.0.6_and_2.1.3\">PostGIS " 808"2.0.6, 2.1.3 security release</ulink>. In order to reenable specific drivers " 809"or all drivers and reenable out of database support, refer to <xref linkend=" 810"\"install_short_version\"/>." 811msgstr "" 812
