PostGIS 1.5.8 Manual - Fedora Project Packages GIT repositories

More documents

Recommendations

Info

PostGIS 1.5.8 Manual141 / 310--Buffer a point to get an approximation of a circle, convert to curve and then translate ←↪1,2 and scale it 3,4SELECT ST_AsText(ST_Transscale(ST_LineToCurve(ST_Buffer(’POINT(234 567)’, 3)),1,2,3,4));st_astext-----------------------------------------------------------------------------------------------------CURVEPOLYGON(CIRCULARSTRING(714 2276,711.363961030679 2267.51471862576,7052264,698.636038969321 2284.48528137424,714 2276))←↪See AlsoST_Affine, ST_Translate7.6 Geometry Outputs7.6.1 ST_AsBinaryST_AsBinary — Return the Well-Known Binary (WKB) representation of the geometry/geography without SRID meta data.Synopsisbytea ST_AsBinary(geometry g1);bytea ST_AsBinary(geography g1);bytea ST_AsBinary(geometry g1, text NDR_or_XDR);DescriptionReturns the Well-Known Binary representation of the geometry. There are 2 variants of the function. The first variant takes noendian encoding paramater and defaults to little endian. The second variant takes a second argument denoting the encoding -using little-endian (’NDR’) or big-endian (’XDR’) encoding.This is useful in binary cursors to pull data out of the database without converting it to a string representation.NoteThe WKB spec does not include the SRID. To get the OGC WKB with SRID format use ST_AsEWKBNoteST_AsBinary is the reverse of ST_GeomFromWKB for geometry. Use ST_GeomFromWKB to convert to a postgisgeometry from ST_AsBinary representation.Availability: 1.5.0 geography support was introduced.This method implements the OpenGIS Simple Features Implementation Specification for SQL 1.1. s2.1.1.1This method implements the SQL/MM specification. SQL-MM 3: 5.1.37This method supports Circular Strings and Curves
PostGIS 1.5.8 Manual142 / 310ExamplesSELECT ST_AsBinary(ST_GeomFromText(’POLYGON((0 0,0 1,1 1,1 0,0 0))’,4326));st_asbinary--------------------------------\001\003\000\000\000\001\000\000\000\005\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\360?\000\000\000\000\000\000\360?\000\000\000\000\000\000\360?\000\000\000\000\000\000\360?\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000(1 row)SELECT ST_AsBinary(ST_GeomFromText(’POLYGON((0 0,0 1,1 1,1 0,0 0))’,4326), ’XDR’);st_asbinary--------------------------------\000\000\000\000\003\000\000\000\001\000\000\000\005\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000?\360\000\000\000\000\000\000?\360\000\000\000\000\000\000?\360\000\000\000\000\000\000?\360\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000(1 row)See AlsoST_AsEWKB, ST_AsEWKT, ST_AsText, ST_GeomFromEWKB7.6.2 ST_AsEWKBST_AsEWKB — Return the Well-Known Binary (WKB) representation of the geometry with SRID meta data.Synopsisbytea ST_AsEWKB(geometry g1);bytea ST_AsEWKB(geometry g1, text NDR_or_XDR);DescriptionReturns the Well-Known Binary representation of the geometry with SRID metadata. There are 2 variants of the function.The first variant takes no endian encoding paramater and defaults to little endian. The second variant takes a second argumentdenoting the encoding - using little-endian (’NDR’) or big-endian (’XDR’) encoding.This is useful in binary cursors to pull data out of the database without converting it to a string representation.NoteThe WKB spec does not include the SRID. To get the OGC WKB format use ST_AsBinary
Page 1 and 2:
PostGIS 1.5.8 ManualiPostGIS 1.5.8
Page 4 and 5:
PostGIS 1.5.8 Manualiv6 Performance
Page 6:
PostGIS 1.5.8 Manualvi7.4.6 ST_Enve
Page 9 and 10:
PostGIS 1.5.8 Manualix7.8.38 ST_Wit
Page 11 and 12:
PostGIS 1.5.8 ManualxiA Appendix 28
Page 13 and 14:
PostGIS 1.5.8 ManualxiiiA.26.8 Othe
Page 15 and 16:
AbstractPostGIS is an extension to
Page 17 and 18:
PostGIS 1.5.8 Manual2 / 310Pierre R
Page 19 and 20:
PostGIS 1.5.8 Manual4 / 310• GNU
Page 21 and 22:
PostGIS 1.5.8 Manual6 / 310NoteIf y
Page 23 and 24:
PostGIS 1.5.8 Manual8 / 310regress_
Page 25 and 26:
PostGIS 1.5.8 Manual10 / 310Restore
Page 27 and 28:
PostGIS 1.5.8 Manual12 / 310Chapter
Page 29 and 30:
PostGIS 1.5.8 Manual14 / 310The "US
Page 31 and 32:
Page 33 and 34:
PostGIS 1.5.8 Manual18 / 3104.1.3 S
Page 35 and 36:
PostGIS 1.5.8 Manual20 / 310Allowab
Page 37 and 38:
PostGIS 1.5.8 Manual22 / 3104.3.1 T
Page 39 and 40:
PostGIS 1.5.8 Manual24 / 310AddGeom
Page 41 and 42:
PostGIS 1.5.8 Manual26 / 310(a)(b)(
Page 43 and 44:
PostGIS 1.5.8 Manual28 / 310(k) (l)
Page 45 and 46:
PostGIS 1.5.8 Manual30 / 310For exa
Page 47 and 48:
PostGIS 1.5.8 Manual32 / 310Given g
Page 49 and 50:
PostGIS 1.5.8 Manual34 / 310For mor
Page 51 and 52:
PostGIS 1.5.8 Manual36 / 3106 | LIN
Page 53 and 54:
PostGIS 1.5.8 Manual38 / 3104.6.2 U
Page 55 and 56:
PostGIS 1.5.8 Manual40 / 3103. What
Page 57 and 58:
Page 59 and 60:
PostGIS 1.5.8 Manual44 / 310FILTER
Page 61 and 62:
PostGIS 1.5.8 Manual46 / 310The sec
Page 63 and 64:
PostGIS 1.5.8 Manual48 / 3105.3.2 B
Page 65 and 66:
PostGIS 1.5.8 Manual50 / 310SELECT
Page 67 and 68:
Page 69 and 70:
PostGIS 1.5.8 Manual54 / 3107.1.5 g
Page 71 and 72:
PostGIS 1.5.8 Manual56 / 310’::te
Page 73 and 74:
PostGIS 1.5.8 Manual58 / 310Example
Page 75 and 76:
PostGIS 1.5.8 Manual60 / 310See Als
Page 77 and 78:
PostGIS 1.5.8 Manual62 / 310Descrip
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
PostGIS 1.5.8 Manual68 / 310This me
Page 85 and 86:
PostGIS 1.5.8 Manual70 / 310-71.104
Page 87 and 88:
Page 90 and 91:
PostGIS 1.5.8 Manual75 / 310This me
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
PostGIS 1.5.8 Manual83 / 310Build p
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107: PostGIS 1.5.8 Manual91 / 310This me
Page 108 and 109: PostGIS 1.5.8 Manual93 / 310See Als
Page 110 and 111: PostGIS 1.5.8 Manual95 / 310Synopsi
Page 112 and 113: PostGIS 1.5.8 Manual97 / 3107.4.6 S
Page 114 and 115: PostGIS 1.5.8 Manual99 / 310See Als
Page 116 and 117: PostGIS 1.5.8 Manual101 / 310Descri
Page 118 and 119: PostGIS 1.5.8 Manual103 / 310NoteSQ
Page 120 and 121: PostGIS 1.5.8 Manual105 / 310This m
Page 122 and 123: PostGIS 1.5.8 Manual107 / 3105340 |
Page 124 and 125: PostGIS 1.5.8 Manual109 / 310Exampl
Page 130 and 131: PostGIS 1.5.8 Manual115 / 3107.4.28
Page 136 and 137: PostGIS 1.5.8 Manual121 / 310See Al
Page 138 and 139: PostGIS 1.5.8 Manual123 / 310--Noth
Page 142 and 143: PostGIS 1.5.8 Manual127 / 310--If c
Page 150 and 151: PostGIS 1.5.8 Manual135 / 310Synops
Page 152 and 153: PostGIS 1.5.8 Manual137 / 310------
Page 158 and 159: PostGIS 1.5.8 Manual143 / 310NoteST
Page 160 and 161: PostGIS 1.5.8 Manual145 / 310text S
Page 162 and 163: PostGIS 1.5.8 Manual147 / 310SELECT
Page 164 and 165: PostGIS 1.5.8 Manual149 / 310--3d l
Page 166 and 167: PostGIS 1.5.8 Manual151 / 310NoteTh
Page 172 and 173: PostGIS 1.5.8 Manual157 / 310Cautio
Page 182 and 183: PostGIS 1.5.8 Manual167 / 310Closes
Page 184 and 185: PostGIS 1.5.8 Manual169 / 310LINEST
Page 188 and 189: PostGIS 1.5.8 Manual173 / 310Import
Page 192 and 193: PostGIS 1.5.8 Manual177 / 310CREATE
Page 194 and 195: PostGIS 1.5.8 Manual179 / 310Line 1
Page 202 and 203: PostGIS 1.5.8 Manual187 / 310NoteTh
Page 206 and 207:
PostGIS 1.5.8 Manual191 / 310NoteCu
Page 208 and 209:
PostGIS 1.5.8 Manual193 / 3107.8.25
Page 210 and 211:
PostGIS 1.5.8 Manual195 / 310FROM (
Page 212 and 213:
PostGIS 1.5.8 Manual197 / 310longes
Page 214 and 215:
PostGIS 1.5.8 Manual199 / 310This f
Page 216 and 217:
PostGIS 1.5.8 Manual201 / 3107.8.32
Page 218 and 219:
PostGIS 1.5.8 Manual203 / 3107.8.35
Page 220 and 221:
PostGIS 1.5.8 Manual205 / 310Shorte
Page 222 and 223:
PostGIS 1.5.8 Manual207 / 310LINEST
Page 224 and 225:
PostGIS 1.5.8 Manual209 / 3107.9 Ge
Page 226 and 227:
PostGIS 1.5.8 Manual211 / 310endcap
Page 228 and 229:
PostGIS 1.5.8 Manual213 / 310This w
Page 230 and 231:
PostGIS 1.5.8 Manual215 / 310Descri
Page 232 and 233:
PostGIS 1.5.8 Manual217 / 310This m
Page 234 and 235:
PostGIS 1.5.8 Manual219 / 310220229
Page 236 and 237:
PostGIS 1.5.8 Manual221 / 310The or
Page 238 and 239:
Page 240 and 241:
PostGIS 1.5.8 Manual225 / 310This f
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
PostGIS 1.5.8 Manual231 / 310FROM (
Page 248 and 249:
PostGIS 1.5.8 Manual233 / 310See Al
Page 250 and 251:
PostGIS 1.5.8 Manual235 / 310--Safe
Page 252 and 253:
PostGIS 1.5.8 Manual237 / 310GEOMET
Page 254 and 255:
PostGIS 1.5.8 Manual239 / 3107.10.2
Page 256 and 257:
PostGIS 1.5.8 Manual241 / 310st_ast
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
PostGIS 1.5.8 Manual249 / 310See Al
Page 266 and 267:
Page 268 and 269:
PostGIS 1.5.8 Manual253 / 310BOX(23
Page 270 and 271:
PostGIS 1.5.8 Manual255 / 310NoteSi
Page 272 and 273:
PostGIS 1.5.8 Manual257 / 310---73-
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
PostGIS 1.5.8 Manual265 / 310Exampl
Page 282 and 283:
PostGIS 1.5.8 Manual267 / 310• ST
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
PostGIS 1.5.8 Manual279 / 310Functi
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
PostGIS 1.5.8 Manual285 / 3108.9.2
Page 302 and 303:
PostGIS 1.5.8 Manual287 / 310Append
Page 304 and 305:
PostGIS 1.5.8 Manual289 / 310#1602,
Page 306 and 307:
PostGIS 1.5.8 Manual291 / 310A.9 Re
Page 308 and 309:
PostGIS 1.5.8 Manual293 / 310A.10.4
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
Page 322 and 323:
Page 324 and 325:
show all

PostGIS 1.5.8 Manual - Fedora Project Packages GIT repositories

Create successful ePaper yourself

Delete template?

Save as template?