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