1# SOME DESCRIPTIVE TITLE. 2# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. 3# 4#, fuzzy 5msgid "" 6msgstr "" 7"Project-Id-Version: PACKAGE VERSION\n" 8"Report-Msgid-Bugs-To: http://bugs.kde.org\n" 9"POT-Creation-Date: 2019-10-06 23:49+0000\n" 10"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" 11"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" 12"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n" 13"Language: \n" 14"MIME-Version: 1.0\n" 15"Content-Type: text/plain; charset=UTF-8\n" 16"Content-Transfer-Encoding: 8bit\n" 17 18#. Tag: para 19#: reference_srs.xml:5 20#, no-c-format 21msgid "These functions work with the Spatial Reference System of geometries." 22msgstr "" 23 24#. Tag: title 25#: reference_srs.xml:9 26#, no-c-format 27msgid "Spatial Reference System Functions" 28msgstr "" 29 30#. Tag: refname 31#: reference_srs.xml:13 32#, no-c-format 33msgid "ST_SetSRID" 34msgstr "" 35 36#. Tag: refpurpose 37#: reference_srs.xml:15 38#, no-c-format 39msgid "Set the SRID on a geometry to a particular integer value." 40msgstr "" 41 42#. Tag: funcprototype 43#: reference_srs.xml:21 44#, no-c-format 45msgid "" 46"<funcdef>geometry <function>ST_SetSRID</function></funcdef> " 47"<paramdef><type>geometry </type> <parameter>geom</parameter></paramdef> " 48"<paramdef><type>integer </type> <parameter>srid</parameter></paramdef>" 49msgstr "" 50 51#. Tag: title 52#: reference_srs.xml:34 reference_srs.xml:81 reference_srs.xml:145 53#, no-c-format 54msgid "Description" 55msgstr "" 56 57#. Tag: para 58#: reference_srs.xml:36 59#, no-c-format 60msgid "" 61"Sets the SRID on a geometry to a particular integer value. Useful in " 62"constructing bounding boxes for queries." 63msgstr "" 64 65#. Tag: para 66#: reference_srs.xml:40 67#, no-c-format 68msgid "" 69"This function does not transform the geometry coordinates in any way - it " 70"simply sets the meta data defining the spatial reference system the geometry " 71"is assumed to be in. Use <xref linkend=\"ST_Transform\"/> if you want to " 72"transform the geometry into a new projection." 73msgstr "" 74 75#. Tag: para 76#: reference_srs.xml:45 77#, no-c-format 78msgid "&sfs_compliant;" 79msgstr "" 80 81#. Tag: para 82#: reference_srs.xml:46 reference_srs.xml:89 reference_srs.xml:179 83#, no-c-format 84msgid "&curve_support;" 85msgstr "" 86 87#. Tag: title 88#: reference_srs.xml:50 reference_srs.xml:94 reference_srs.xml:185 89#, no-c-format 90msgid "Examples" 91msgstr "" 92 93#. Tag: para 94#: reference_srs.xml:51 95#, no-c-format 96msgid "-- Mark a point as WGS 84 long lat --" 97msgstr "" 98 99#. Tag: programlisting 100#: reference_srs.xml:52 101#, no-c-format 102msgid "" 103"SELECT ST_SetSRID(ST_Point(-123.365556, 48.428611),4326) As wgs84long_lat;\n" 104"-- the ewkt representation (wrap with ST_AsEWKT) -\n" 105"SRID=4326;POINT(-123.365556 48.428611)" 106msgstr "" 107 108#. Tag: para 109#: reference_srs.xml:53 110#, no-c-format 111msgid "" 112"-- Mark a point as WGS 84 long lat and then transform to web mercator " 113"(Spherical Mercator) --" 114msgstr "" 115 116#. Tag: programlisting 117#: reference_srs.xml:54 118#, no-c-format 119msgid "" 120"SELECT ST_Transform(ST_SetSRID(ST_Point(-123.365556, 48.428611),4326),3785) " 121"As spere_merc;\n" 122"-- the ewkt representation (wrap with ST_AsEWKT) -\n" 123"SRID=3785;POINT(-13732990.8753491 6178458.96425423)" 124msgstr "" 125 126#. Tag: title 127#: reference_srs.xml:58 reference_srs.xml:99 reference_srs.xml:219 128#, no-c-format 129msgid "See Also" 130msgstr "" 131 132#. Tag: para 133#: reference_srs.xml:60 134#, no-c-format 135msgid "" 136", <xref linkend=\"ST_AsEWKT\"/>, <xref linkend=\"ST_SRID\"/>, <xref linkend=" 137"\"ST_Transform\"/>, <xref linkend=\"UpdateGeometrySRID\"/>" 138msgstr "" 139 140#. Tag: refname 141#: reference_srs.xml:67 142#, no-c-format 143msgid "ST_SRID" 144msgstr "" 145 146#. Tag: refpurpose 147#: reference_srs.xml:68 148#, no-c-format 149msgid "" 150"Returns the spatial reference identifier for the ST_Geometry as defined in " 151"spatial_ref_sys table." 152msgstr "" 153 154#. Tag: funcprototype 155#: reference_srs.xml:73 156#, no-c-format 157msgid "" 158"<funcdef>integer <function>ST_SRID</function></funcdef> " 159"<paramdef><type>geometry </type> <parameter>g1</parameter></paramdef>" 160msgstr "" 161 162#. Tag: para 163#: reference_srs.xml:83 164#, no-c-format 165msgid "" 166"Returns the spatial reference identifier for the ST_Geometry as defined in " 167"spatial_ref_sys table. <xref linkend=\"spatial_ref_sys\"/>" 168msgstr "" 169 170#. Tag: para 171#: reference_srs.xml:84 172#, no-c-format 173msgid "" 174"spatial_ref_sys table is a table that catalogs all spatial reference systems " 175"known to PostGIS and is used for transformations from one spatial reference " 176"system to another. So verifying you have the right spatial reference system " 177"identifier is important if you plan to ever transform your geometries." 178msgstr "" 179 180#. Tag: para 181#: reference_srs.xml:87 182#, no-c-format 183msgid "&sfs_compliant; s2.1.1.1" 184msgstr "" 185 186#. Tag: para 187#: reference_srs.xml:88 188#, no-c-format 189msgid "&sqlmm_compliant; SQL-MM 3: 5.1.5" 190msgstr "" 191 192#. Tag: programlisting 193#: reference_srs.xml:96 194#, no-c-format 195msgid "" 196"SELECT ST_SRID(ST_GeomFromText('POINT(-71.1043 42.315)',4326));\n" 197" --result\n" 198" 4326" 199msgstr "" 200 201#. Tag: para 202#: reference_srs.xml:101 203#, no-c-format 204msgid "" 205", <xref linkend=\"ST_GeomFromText\"/>, <xref linkend=\"ST_SetSRID\"/>, <xref " 206"linkend=\"ST_Transform\"/>" 207msgstr "" 208 209#. Tag: refname 210#: reference_srs.xml:107 211#, no-c-format 212msgid "ST_Transform" 213msgstr "" 214 215#. Tag: refpurpose 216#: reference_srs.xml:109 217#, no-c-format 218msgid "" 219"Return a new geometry with its coordinates transformed to a different " 220"spatial reference system." 221msgstr "" 222 223#. Tag: funcsynopsis 224#: reference_srs.xml:114 225#, no-c-format 226msgid "" 227"<funcprototype> <funcdef>geometry <function>ST_Transform</function></" 228"funcdef> <paramdef><type>geometry </type> <parameter>g1</parameter></" 229"paramdef> <paramdef><type>integer </type> <parameter>srid</parameter></" 230"paramdef> </funcprototype> <funcprototype> <funcdef>geometry " 231"<function>ST_Transform</function></funcdef> <paramdef><type>geometry </type> " 232"<parameter>geom</parameter></paramdef> <paramdef><type>text </type> " 233"<parameter>to_proj</parameter></paramdef> </funcprototype> <funcprototype> " 234"<funcdef>geometry <function>ST_Transform</function></funcdef> " 235"<paramdef><type>geometry </type> <parameter>geom</parameter></paramdef> " 236"<paramdef><type>text </type> <parameter>from_proj</parameter></paramdef> " 237"<paramdef><type>text </type> <parameter>to_proj</parameter></paramdef> </" 238"funcprototype> <funcprototype> <funcdef>geometry <function>ST_Transform</" 239"function></funcdef> <paramdef><type>geometry </type> <parameter>geom</" 240"parameter></paramdef> <paramdef><type>text </type> <parameter>from_proj</" 241"parameter></paramdef> <paramdef><type>integer </type> <parameter>to_srid</" 242"parameter></paramdef> </funcprototype>" 243msgstr "" 244 245#. Tag: para 246#: reference_srs.xml:147 247#, no-c-format 248msgid "" 249"Returns a new geometry with its coordinates transformed to a different " 250"spatial reference system. The destination spatial reference " 251"<varname>to_srid</varname> may be identified by a valid SRID integer " 252"parameter (i.e. it must exist in the <varname>spatial_ref_sys</varname> " 253"table). Alternatively, a spatial reference defined as a PROJ.4 string can be " 254"used for <varname>to_proj</varname> and/or <varname>from_proj</varname>, " 255"however these methods are not optimized. If the destination spatial " 256"reference system is expressed with a PROJ.4 string instead of an SRID, the " 257"SRID of the output geometry will be set to zero. With the exception of " 258"functions with <varname>from_proj</varname>, input geometries must have a " 259"defined SRID." 260msgstr "" 261 262#. Tag: para 263#: reference_srs.xml:161 264#, no-c-format 265msgid "" 266"ST_Transform is often confused with <xref linkend=\"ST_SetSRID\"/>. " 267"ST_Transform actually changes the coordinates of a geometry from one spatial " 268"reference system to another, while ST_SetSRID() simply changes the SRID " 269"identifier of the geometry." 270msgstr "" 271 272#. Tag: para 273#: reference_srs.xml:166 274#, no-c-format 275msgid "" 276"Requires PostGIS be compiled with Proj support. Use <xref linkend=" 277"\"PostGIS_Full_Version\"/> to confirm you have proj support compiled in." 278msgstr "" 279 280#. Tag: para 281#: reference_srs.xml:170 282#, no-c-format 283msgid "" 284"If using more than one transformation, it is useful to have a functional " 285"index on the commonly used transformations to take advantage of index usage." 286msgstr "" 287 288#. Tag: para 289#: reference_srs.xml:174 290#, no-c-format 291msgid "" 292"Prior to 1.3.4, this function crashes if used with geometries that contain " 293"CURVES. This is fixed in 1.3.4+" 294msgstr "" 295 296#. Tag: para 297#: reference_srs.xml:176 298#, no-c-format 299msgid "Enhanced: 2.0.0 support for Polyhedral surfaces was introduced." 300msgstr "" 301 302#. Tag: para 303#: reference_srs.xml:177 304#, no-c-format 305msgid "Enhanced: 2.3.0 support for direct PROJ.4 text was introduced." 306msgstr "" 307 308#. Tag: para 309#: reference_srs.xml:178 310#, no-c-format 311msgid "&sqlmm_compliant; SQL-MM 3: 5.1.6" 312msgstr "" 313 314#. Tag: para 315#: reference_srs.xml:180 316#, no-c-format 317msgid "&P_support;" 318msgstr "" 319 320#. Tag: para 321#: reference_srs.xml:186 322#, no-c-format 323msgid "Change Massachusetts state plane US feet geometry to WGS 84 long lat" 324msgstr "" 325 326#. Tag: programlisting 327#: reference_srs.xml:187 328#, no-c-format 329msgid "" 330"SELECT ST_AsText(ST_Transform(ST_GeomFromText('POLYGON((743238 " 331"2967416,743238 2967450,\n" 332" 743265 2967450,743265.625 2967416,743238 2967416))',2249),4326)) As " 333"wgs_geom;\n" 334"\n" 335" wgs_geom\n" 336"---------------------------\n" 337" POLYGON((-71.1776848522251 42.3902896512902,-71.1776843766326 " 338"42.3903829478009,\n" 339"-71.1775844305465 42.3903826677917,-71.1775825927231 " 340"42.3902893647987,-71.177684\n" 341"8522251 42.3902896512902));\n" 342"(1 row)\n" 343"\n" 344"--3D Circular String example\n" 345"SELECT ST_AsEWKT(ST_Transform(ST_GeomFromEWKT('SRID=2249;" 346"CIRCULARSTRING(743238 2967416 1,743238 2967450 2,743265 2967450 3,743265.625 " 347"2967416 3,743238 2967416 4)'),4326));\n" 348"\n" 349" st_asewkt\n" 350"--------------------------------------------------------------------------------------\n" 351" SRID=4326;CIRCULARSTRING(-71.1776848522251 42.3902896512902 " 352"1,-71.1776843766326 42.3903829478009 2,\n" 353" -71.1775844305465 42.3903826677917 3,\n" 354" -71.1775825927231 42.3902893647987 3,-71.1776848522251 42.3902896512902 4)" 355msgstr "" 356 357#. Tag: para 358#: reference_srs.xml:188 359#, no-c-format 360msgid "" 361"Example of creating a partial functional index. For tables where you are not " 362"sure all the geometries will be filled in, its best to use a partial index " 363"that leaves out null geometries which will both conserve space and make your " 364"index smaller and more efficient." 365msgstr "" 366 367#. Tag: programlisting 368#: reference_srs.xml:190 369#, no-c-format 370msgid "" 371"CREATE INDEX idx_the_geom_26986_parcels\n" 372" ON parcels\n" 373" USING gist\n" 374" (ST_Transform(the_geom, 26986))\n" 375" WHERE the_geom IS NOT NULL;" 376msgstr "" 377 378#. Tag: para 379#: reference_srs.xml:192 380#, no-c-format 381msgid "" 382"Examples of using PROJ.4 text to transform with custom spatial references." 383msgstr "" 384 385#. Tag: programlisting 386#: reference_srs.xml:193 387#, no-c-format 388msgid "" 389"-- Find intersection of two polygons near the North pole, using a custom " 390"Gnomic projection\n" 391"-- See http://boundlessgeo.com/2012/02/flattening-the-peel/\n" 392" WITH data AS (\n" 393" SELECT\n" 394" ST_GeomFromText('POLYGON((170 50,170 72,-130 72,-130 50,170 50))', " 395"4326) AS p1,\n" 396" ST_GeomFromText('POLYGON((-170 68,-170 90,-141 90,-141 68,-170 68))', " 397"4326) AS p2,\n" 398" '+proj=gnom +ellps=WGS84 +lat_0=70 +lon_0=-160 +no_defs'::text AS gnom\n" 399" )\n" 400" SELECT ST_AsText(\n" 401" ST_Transform(\n" 402" ST_Intersection(ST_Transform(p1, gnom), ST_Transform(p2, gnom)),\n" 403" gnom, 4326))\n" 404" FROM data;\n" 405" st_astext\n" 406" --------------------------------------------------------------------------------\n" 407" POLYGON((-170 74.053793645338,-141 73.4268621378904,-141 68,-170 68,-170 " 408"74.053793645338))" 409msgstr "" 410 411#. Tag: title 412#: reference_srs.xml:197 413#, no-c-format 414msgid "Configuring transformation behaviour" 415msgstr "" 416 417#. Tag: para 418#: reference_srs.xml:198 419#, no-c-format 420msgid "" 421"Sometimes coordinate transformation involving a grid-shift can fail, for " 422"example if PROJ.4 has not been built with grid-shift files or the coordinate " 423"does not lie within the range for which the grid shift is defined. By " 424"default, PostGIS will throw an error if a grid shift file is not present, " 425"but this behaviour can be configured on a per-SRID basis either by testing " 426"different <varname>to_proj</varname> values of PROJ.4 text, or altering the " 427"<varname>proj4text</varname> value within the <varname>spatial_ref_sys</" 428"varname> table." 429msgstr "" 430 431#. Tag: para 432#: reference_srs.xml:208 433#, no-c-format 434msgid "" 435"For example, the proj4text parameter +datum=NAD87 is a shorthand form for " 436"the following +nadgrids parameter:" 437msgstr "" 438 439#. Tag: programlisting 440#: reference_srs.xml:209 441#, no-c-format 442msgid "+nadgrids=@conus,@alaska,@ntv2_0.gsb,@ntv1_can.dat" 443msgstr "" 444 445#. Tag: para 446#: reference_srs.xml:210 447#, no-c-format 448msgid "" 449"The @ prefix means no error is reported if the files are not present, but if " 450"the end of the list is reached with no file having been appropriate (ie. " 451"found and overlapping) then an error is issued." 452msgstr "" 453 454#. Tag: para 455#: reference_srs.xml:211 456#, no-c-format 457msgid "" 458"If, conversely, you wanted to ensure that at least the standard files were " 459"present, but that if all files were scanned without a hit a null " 460"transformation is applied you could use:" 461msgstr "" 462 463#. Tag: programlisting 464#: reference_srs.xml:212 465#, no-c-format 466msgid "+nadgrids=@conus,@alaska,@ntv2_0.gsb,@ntv1_can.dat,null" 467msgstr "" 468 469#. Tag: para 470#: reference_srs.xml:213 471#, no-c-format 472msgid "" 473"The null grid shift file is a valid grid shift file covering the whole world " 474"and applying no shift. So for a complete example, if you wanted to alter " 475"PostGIS so that transformations to SRID 4267 that didn't lie within the " 476"correct range did not throw an ERROR, you would use the following:" 477msgstr "" 478 479#. Tag: programlisting 480#: reference_srs.xml:214 481#, no-c-format 482msgid "" 483"UPDATE spatial_ref_sys SET proj4text = '+proj=longlat +ellps=clrk66 " 484"+nadgrids=@conus,@alaska,@ntv2_0.gsb,@ntv1_can.dat,null +no_defs' WHERE srid " 485"= 4267;" 486msgstr "" 487 488#. Tag: para 489#: reference_srs.xml:221 490#, no-c-format 491msgid "" 492", <xref linkend=\"ST_AsText\"/>, <xref linkend=\"ST_SetSRID\"/>, <xref " 493"linkend=\"UpdateGeometrySRID\"/>" 494msgstr "" 495