idnits 2.17.1 draft-butler-geojson-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 5, 2014) is 3551 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 7159 (Obsoleted by RFC 8259) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Independent H. Butler 3 Internet-Draft Hobu Inc. 4 Intended status: Informational M. Daly 5 Expires: February 6, 2015 Cadcorp 6 A. Doyle 7 MIT 8 S. Gillies 9 Mapbox Inc. 10 T. Schaub 11 OpenGeo 12 S. Drees 14 August 5, 2014 16 The GeoJSON Format 17 draft-butler-geojson-04 19 Abstract 21 GeoJSON is a geospatial data interchange format based on JavaScript 22 Object Notation (JSON). It defines several types of JSON objects and 23 the manner in which they are combined to represent data about 24 geographic features, their properties, and their spatial extents. 25 This document recommends a single coordinate reference system based 26 on WGS 84. Other coordinate reference systems are not recommended. 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on February 6, 2015. 45 Copyright Notice 47 Copyright (c) 2014 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 63 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 64 1.2. Conventions Used in This Document . . . . . . . . . . . . 4 65 1.3. Specification of GeoJSON . . . . . . . . . . . . . . . . 4 66 1.4. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4 67 1.5. Example . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 2. GeoJSON Object . . . . . . . . . . . . . . . . . . . . . . . 6 69 2.1. Geometry Object . . . . . . . . . . . . . . . . . . . . . 6 70 2.1.1. Position . . . . . . . . . . . . . . . . . . . . . . 6 71 2.1.2. Point . . . . . . . . . . . . . . . . . . . . . . . . 7 72 2.1.3. MultiPoint . . . . . . . . . . . . . . . . . . . . . 7 73 2.1.4. LineString . . . . . . . . . . . . . . . . . . . . . 7 74 2.1.5. MultiLineString . . . . . . . . . . . . . . . . . . . 7 75 2.1.6. Polygon . . . . . . . . . . . . . . . . . . . . . . . 7 76 2.1.7. MultiPolygon . . . . . . . . . . . . . . . . . . . . 8 77 2.1.8. Geometry Collection . . . . . . . . . . . . . . . . . 8 78 2.2. Feature Object . . . . . . . . . . . . . . . . . . . . . 8 79 2.3. Feature Collection Object . . . . . . . . . . . . . . . . 8 80 3. Coordinate Reference System . . . . . . . . . . . . . . . . . 8 81 4. Bounding Box . . . . . . . . . . . . . . . . . . . . . . . . 9 82 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 83 6. Interoperability Considerations . . . . . . . . . . . . . . . 10 84 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 85 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 86 8.1. Normative References . . . . . . . . . . . . . . . . . . 12 87 8.2. Informative References . . . . . . . . . . . . . . . . . 12 88 Appendix A. Geometry Examples . . . . . . . . . . . . . . . . . 12 89 A.1. Points . . . . . . . . . . . . . . . . . . . . . . . . . 12 90 A.2. LineStrings . . . . . . . . . . . . . . . . . . . . . . . 13 91 A.3. Polygons . . . . . . . . . . . . . . . . . . . . . . . . 13 92 A.4. MultiPoints . . . . . . . . . . . . . . . . . . . . . . . 14 93 A.5. MultiLineStrings . . . . . . . . . . . . . . . . . . . . 14 94 A.6. MultiPolygons . . . . . . . . . . . . . . . . . . . . . . 15 95 A.7. GeometryCollections . . . . . . . . . . . . . . . . . . . 16 96 Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 17 97 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 99 1. Introduction 101 GeoJSON is a format for encoding data about geographic features using 102 JavaScript Object Notation (JSON) [RFC7159]. The format is concerned 103 with features in the broadest sense; any thing with qualities that 104 are bounded in geographical space may be a feature whether it is a 105 physical structure or not. The concepts in GeoJSON are not new; they 106 are derived from pre-existing open geographic information system 107 standards (for COM, SQL, and XML) and have been streamlined to better 108 suit web application development using JSON. 110 GeoJSON comprises the seven concrete geometry types defined in the 111 OpenGIS Simple Features Implementation Specification for SQL [SFSQL]: 112 0-dimensional Point and MultiPoint; 1-dimensional curve LineString 113 and MultiLineString; 2-dimensional surface Polygon and MultiPolygon; 114 and the heterogeneous GeometryCollection. GeoJSON representations of 115 instances of these geometry types are analogous to the well-known 116 binary (WKB) and text (WKT) representations described in that same 117 specification. 119 GeoJSON also comprises the types Feature and FeatureCollection. 120 Feature objects in GeoJSON contain a geometry object with one of the 121 above geometry types and additional properties. A FeatureCollection 122 object contains an array of feature objects. This structure is 123 analogous to that of the Web Feature Service (WFS) response to 124 GetFeatures requests specified in [WFSv1] or to a KML Folder of 125 Placemarks [KMLv2.2]. Some implementations of the WFS specification 126 also provide GeoJSON formatted responses to GetFeature requests, but 127 there is no particular service model or feature type ontology implied 128 in the GeoJSON format specification. 130 Since its initial publication in 2008 [GJ2008], the GeoJSON format 131 specification has steadily grown in popularity. It is widely used in 132 JavaScript web mapping libraries, JSON-based document databases, and 133 web APIs. 135 1.1. Requirements Language 137 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 138 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 139 "OPTIONAL" in this document are to be interpreted as described in 140 [RFC2119]. 142 1.2. Conventions Used in This Document 144 The ordering of the members of any JSON object defined in this 145 document MUST be considered irrelevant, as specified by [RFC7159]. 147 Some examples use the combination of a JavaScript single line comment 148 (//) followed by an ellipsis (...) as placeholder notation for 149 content deemed irrelevant by the authors. These placeholders must of 150 course be deleted or otherwise replaced, before attempting to 151 validate the corresponding JSON code example. 153 Whitespace is used in the examples inside this document to help 154 illustrate the data structures, but is not required. Unquoted 155 whitespace is not significant in JSON. 157 1.3. Specification of GeoJSON 159 This document updates the original GeoJSON format specification 160 [GJ2008]. 162 1.4. Definitions 164 o JavaScript Object Notation (JSON), and the terms object, name, 165 value, array, number, true, false, and null are to be interpreted 166 as defined in [RFC7159]. 168 o Inside this document the term "geometry type" refers to the seven 169 case-sensitive strings: "Point", "MultiPoint", "LineString", 170 "MultiLineString", "Polygon", "MultiPolygon", and 171 "GeometryCollection". 173 o As another shorthand notation, the term "GeoJSON types" refers to 174 the nine case-sensitive strings "Feature", "FeatureCollection" and 175 the geometry types listed above. 177 1.5. Example 179 A GeoJSON feature collection: 181 { 182 "type": "FeatureCollection", 183 "features": [{ 184 "type": "Feature", 185 "geometry": { 186 "type": "Point", 187 "coordinates": [102.0, 0.5] 188 }, 189 "properties": { 190 "prop0": "value0" 191 } 192 }, { 193 "type": "Feature", 194 "geometry": { 195 "type": "LineString", 196 "coordinates": [ 197 [102.0, 0.0], 198 [103.0, 1.0], 199 [104.0, 0.0], 200 [105.0, 1.0] 201 ] 202 }, 203 "properties": { 204 "prop0": "value0", 205 "prop1": 0.0 206 } 207 }, { 208 "type": "Feature", 209 "geometry": { 210 "type": "Polygon", 211 "coordinates": [ 212 [ 213 [100.0, 0.0], 214 [101.0, 0.0], 215 [101.0, 1.0], 216 [100.0, 1.0], 217 [100.0, 0.0] 218 ] 219 ] 220 }, 221 "properties": { 222 "prop0": "value0", 223 "prop1": { 224 "this": "that" 225 } 226 } 227 }] 228 } 230 2. GeoJSON Object 232 GeoJSON always consists of a single object. This object (referred to 233 as the GeoJSON object below) represents a geometry, feature, or 234 collection of features. 236 o The GeoJSON object MUST have a member with the name "type". The 237 value of the member MUST be one of the GeoJSON types. 239 o The GeoJSON object MAY have any number of other members. 241 o A GeoJSON object MAY have a "bbox" member, the value of which MUST 242 be a bounding box array (see 4. Bounding Boxes). 244 2.1. Geometry Object 246 A geometry object is a GeoJSON object where the "type" value is one 247 of the geometry types. A GeoJSON geometry object of any type other 248 than "GeometryCollection" MUST have a member with the name 249 "coordinates". The value of the coordinates member is always an 250 array. The structure of the elements in this array is determined by 251 the type of geometry. GeoJSON processors MAY interpret geometry 252 objects with empty coordinates arrays as null objects. 254 2.1.1. Position 256 A position is the fundamental geometry construct. The "coordinates" 257 member of a geometry object is composed of either: 259 o one position (in the case of a Point geometry), 261 o an array of positions (LineString or MultiPoint geometries), 263 o an array of arrays of positions (Polygons, MultiLineStrings), 265 o or a multidimensional array of positions (MultiPolygon). 267 A position is represented by an array of numbers. There MUST be two 268 or more elements. The first two elements will be longitude and 269 latitude, or easting and northing, precisely in that order and using 270 decimal numbers. Altitude or elevation MAY be included as an 271 optional third element. 273 Additional position elements MAY be included but MUST follow the 274 three specified above and MAY be ignored by software. Interpretation 275 and meaning of additional elements is beyond the scope of this 276 specification. 278 Examples of positions and geometries are provided in "Appendix A. 279 Geometry Examples". 281 2.1.2. Point 283 For type "Point", the "coordinates" member MUST be a single position. 285 2.1.3. MultiPoint 287 For type "MultiPoint", the "coordinates" member MUST be an array of 288 positions. 290 2.1.4. LineString 292 For type "LineString", the "coordinates" member MUST be an array of 293 two or more positions. 295 2.1.5. MultiLineString 297 For type "MultiLineString", the "coordinates" member MUST be an array 298 of LineString coordinate arrays. 300 2.1.6. Polygon 302 To specify a constraint specific to polygons, it is useful to 303 introduce the concept of a linear ring: 305 o A linear ring is a closed LineString with 4 or more positions. 307 o The first and last positions are equivalent (they represent 308 equivalent points). 310 o A linear ring is the boundary of a surface or the boundary of a 311 hole in a surface. 313 Though a linear ring is not explicitly represented as a GeoJSON 314 geometry type, it leads to a canonical formulation of the Polygon 315 geometry type definition as follows: 317 o For type "Polygon", the "coordinates" member MUST be an array of 318 linear ring coordinate arrays. 320 o For Polygons with more than one of these rings, the first MUST be 321 the exterior ring and any others MUST be interior rings. The 322 exterior ring bounds the surface and the interiors rings (if 323 present) bound holes within the surface. 325 2.1.7. MultiPolygon 327 For type "MultiPolygon", the "coordinates" member MUST be an array of 328 Polygon coordinate arrays. 330 2.1.8. Geometry Collection 332 A GeoJSON object with type "GeometryCollection" is a geometry object 333 which represents a collection of geometry objects. A geometry 334 collection MUST have a member with the name "geometries". The value 335 corresponding to "geometries" is an array. Each element in this 336 array is a GeoJSON geometry object. 338 2.2. Feature Object 340 A GeoJSON object with the type "Feature" is a feature object. 342 o A feature object MUST have a member with the name "geometry". The 343 value of the geometry member SHALL be either a geometry object as 344 defined above or, in the the case that the feature is unlocated, a 345 JSON null value. 347 o A feature object MUST have a member with the name "properties". 348 The value of the properties member is an object (any JSON object 349 or a JSON null value). 351 o If a feature has a commonly used identifier, that identifier 352 SHOULD be included as a member of the feature object with the name 353 "id" and the value of this member is either a JSON string or 354 number. 356 2.3. Feature Collection Object 358 A GeoJSON object with the type "FeatureCollection" is a feature 359 collection object. An object of type "FeatureCollection" MUST have a 360 member with the name "features". The value corresponding to 361 "features" is an array. Each element in the array is a feature 362 object as defined above. 364 3. Coordinate Reference System 366 The default reference system for all GeoJSON coordinates SHALL be a 367 geographic coordinate reference system, using the [WGS84] datum, and 368 with longitude and latitude units of decimal degrees. This 369 coordinate reference system is equivalent to the OGC's "http:// 370 www.opengis.net/def/crs/OGC/1.3/CRS84" [OGCURL]. An OPTIONAL third 371 position element SHALL be the height in meters above the WGS 84 372 reference ellipsoid. For widest interoperability, GeoJSON data 373 SHOULD use this default coordinate reference system. 375 Other coordinate reference systems, including ones described by CRS 376 objects of the kind defined in [GJ2008] are NOT RECOMMENDED. GeoJSON 377 processing software SHALL NOT be expected to have access to 378 coordinate reference systems databases. Applications requiring CRS 379 other than the default MUST assume all responsibility for reference 380 system and coordinate accuracy. Furthermore, GeoJSON coordinates 381 MUST NOT under any circumstances use latitude, longitude order. See 382 Section 6, Interoperability Considerations, for guidance in 383 processing GeoJSON documents that do contain such a CRS object. 385 4. Bounding Box 387 A GeoJSON object MAY have a member named "bbox" to include 388 information on the coordinate range for its geometries, features, or 389 feature collections. The value of the bbox member MUST be an array 390 of length 2*n where n is the number of dimensions represented in the 391 contained geometries, with the lowest values for all axes followed by 392 the highest values. The axes order of a bbox follows the axes order 393 of geometries. 395 Example of a bbox member on a feature: 397 { 398 "type": "Feature", 399 "bbox": [-180.0, -90.0, 180.0, 90.0], 400 "geometry": { 401 "type": "Polygon", 402 "coordinates": [ 403 [ 404 [-180.0, 10.0], 405 [20.0, 90.0], 406 [180.0, -5.0], 407 [-30.0, -90.0] 408 ] 409 ] 410 } 411 //... 412 } 414 Example of a bbox member on a feature collection: 416 { 417 "type": "FeatureCollection", 418 "bbox": [100.0, 0.0, 105.0, 1.0], 419 "features": [ 420 //... 421 ] 422 } 424 5. Security Considerations 426 GeoJSON shares security issues common to all JSON content types. See 427 [RFC7159] Section 12 for additional information. GeoJSON does not 428 provide executable content. 430 As with other geographic data formats, e.g., [KMLv2.2], providing 431 details about the locations of sensitive persons, animals, habitats, 432 and facilities can expose them to unauthorized tracking or injury. 433 GeoJSON does not provide privacy or integrity services; if sensitive 434 data requires privacy or integrity protection the service must be 435 provided externally. 437 6. Interoperability Considerations 439 There are differences among geographic data formats over whether 440 latitude or longitude come first in a pair of numbers. Longitude 441 comes first in GeoJSON coordinates as it does in [KMLv2.2]. 443 The original GeoJSON format specification [GJ2008] included 444 descriptions of coordinate reference system (CRS) objects. These are 445 NOT RECOMMENDED but may be found in existing documents. When such a 446 CRS is encountered in GeoJSON, the document should be processed with 447 caution. The coordinate values may be projected, i.e., easting and 448 northing instead of longitude and latitude. 450 On encountering a named CRS object with a value of 451 "urn:ogc:def:crs:OGC:1.3:CRS84" or "http://www.opengis.net/def/crs/ 452 OGC/1.3/CRS84", processors SHOULD interpret the coordinates exactly 453 as in Section 2.1.1; these CRS are equivalent to the default 454 coordinate reference system. 456 Due to a history of changing and vernacular usage, extra caution is 457 required when processing GeoJSON that has a named CRS object with the 458 value "EPSG:4326." Heuristics may be necessary to interpret the 459 coordinates properly; they may not be in the required longitude, 460 latitude order. 462 When serving GeoJSON, use of CRS objects is NOT RECOMMENDED. If an 463 application requires coordinates in a reference system other than the 464 default, it MUST assume all responsibility for communicating this to 465 clients. 467 Regardless, GeoJSON coordinates MUST NOT under any circumstances use 468 latitude, longitude order. 470 7. IANA Considerations 472 The MIME media type for GeoJSON text is application/vnd.geo+json. 474 Type name: application 476 Subtype name: vnd.geo+json 478 Required parameters: n/a 480 Optional parameters: n/a 482 Encoding considerations: binary 484 Security considerations: See section 5 above 486 Interoperability considerations: See section 6 above 488 Published specification: draft-butler-geojson 490 Applications that use this media type: various 492 Additional information: 494 Magic number(s) : n/a 496 File extension(s) : .json, .geojson 498 Macintosh file type code : TEXT 500 Object Identifiers: n/a 502 Person to contact for further information: 504 Sean Gillies 506 sean.gillies@gmail.com 508 Intended usage: COMMON 510 Restrictions on usage: none 512 8. References 514 8.1. Normative References 516 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 517 Requirement Levels", BCP 14, RFC 2119, March 1997. 519 [RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data 520 Interchange Format", RFC 7159, March 2014. 522 8.2. Informative References 524 [GJ2008] Butler, H., Daly, M., Doyle, A., Gillies, S., Schaub, T., 525 and C. Schmidt, "The GeoJSON Format Specification", June 526 2008. 528 [KMLv2.2] Wilson, T., "OGC KML", OGC 07-147r2, April 2008. 530 [OGCURL] Cox, S., "OGC-NA Name type specification - definitions: 531 Part 1 - basic name", OGC 09-048r3, March 2010. 533 [SFSQL] OpenGIS Consortium, Inc., "OpenGIS Simple Features 534 Specification For SQL Revision 1.1", OGC 99-049, May 1999. 536 [WFSv1] Vretanos, P., "Web Feature Service Implementation 537 Specification", OGC 02-058, May 2002. 539 [WGS84] National Imagery and Mapping Agency, "Department of 540 Defense World Geodetic System 1984, Third Edition", 1984. 542 Appendix A. Geometry Examples 544 Each of the examples below represents a valid and complete GeoJSON 545 object. 547 A.1. Points 549 Point coordinates are in x, y order (easting, northing for projected 550 coordinates, longitude, latitude for geographic coordinates): 552 { 553 "type": "Point", 554 "coordinates": [100.0, 0.0] 555 } 557 A.2. LineStrings 559 Coordinates of LineString are an array of positions (see "2.1.1. 560 Position"): 562 { 563 "type": "LineString", 564 "coordinates": [ 565 [100.0, 0.0], 566 [101.0, 1.0] 567 ] 568 } 570 A.3. Polygons 572 Coordinates of a Polygon are an array of LinearRing (cf. "2.1.6 573 Polygon") coordinate arrays. The first element in the array 574 represents the exterior ring. Any subsequent elements represent 575 interior rings (or holes). 577 No holes: 579 { 580 "type": "Polygon", 581 "coordinates": [ 582 [ 583 [100.0, 0.0], 584 [101.0, 0.0], 585 [101.0, 1.0], 586 [100.0, 1.0], 587 [100.0, 0.0] 588 ] 589 ] 590 } 592 With holes: 594 { 595 "type": "Polygon", 596 "coordinates": [ 597 [ 598 [100.0, 0.0], 599 [101.0, 0.0], 600 [101.0, 1.0], 601 [100.0, 1.0], 602 [100.0, 0.0] 603 ], 604 [ 605 [100.2, 0.2], 606 [100.8, 0.2], 607 [100.8, 0.8], 608 [100.2, 0.8], 609 [100.2, 0.2] 610 ] 611 ] 612 } 614 A.4. MultiPoints 616 Coordinates of a MultiPoint are an array of positions:: 618 { 619 "type": "MultiPoint", 620 "coordinates": [ 621 [100.0, 0.0], 622 [101.0, 1.0] 623 ] 624 } 626 A.5. MultiLineStrings 628 Coordinates of a MultiLineString are an array of LineString 629 coordinate arrays: 631 { 632 "type": "MultiLineString", 633 "coordinates": [ 634 [ 635 [100.0, 0.0], 636 [101.0, 1.0] 637 ], 638 [ 639 [102.0, 2.0], 640 [103.0, 3.0] 641 ] 642 ] 643 } 645 A.6. MultiPolygons 647 Coordinates of a MultiPolygon are an array of Polygon coordinate 648 arrays: 650 { 651 "type": "MultiPolygon", 652 "coordinates": [ 653 [ 654 [ 655 [102.0, 2.0], 656 [103.0, 2.0], 657 [103.0, 3.0], 658 [102.0, 3.0], 659 [102.0, 2.0] 660 ] 661 ], 662 [ 663 [ 664 [100.0, 0.0], 665 [101.0, 0.0], 666 [101.0, 1.0], 667 [100.0, 1.0], 668 [100.0, 0.0] 669 ], 670 [ 671 [100.2, 0.2], 672 [100.8, 0.2], 673 [100.8, 0.8], 674 [100.2, 0.8], 675 [100.2, 0.2] 676 ] 677 ] 678 ] 679 } 681 A.7. GeometryCollections 683 Each element in the geometries array of a GeometryCollection is one 684 of the geometry objects described above: 686 { 687 "type": "GeometryCollection", 688 "geometries": [{ 689 "type": "Point", 690 "coordinates": [100.0, 0.0] 691 }, { 692 "type": "LineString", 693 "coordinates": [ 694 [101.0, 0.0], 695 [102.0, 1.0] 696 ] 697 }] 698 } 700 Appendix B. Contributors 702 The GeoJSON format is the product of discussion on the GeoJSON 703 mailing list: http://lists.geojson.org/listinfo.cgi/geojson- 704 geojson.org. 706 Comments are solicited and should be addressed to the GeoJSON mailing 707 list at geojson@lists.geojson.org or to the GeoJSON issue tracker at 708 https://github.com/geojson/draft-geojson/issues. 710 Authors' Addresses 712 H. Butler 713 Hobu Inc. 715 M. Daly 716 Cadcorp 718 A. Doyle 719 MIT 721 S. Gillies 722 Mapbox Inc. 724 Email: sean.gillies@gmail.com 725 URI: http://sgillies.net 727 T. Schaub 728 OpenGeo 729 S. Drees 730 Rheinaustr. 62 731 Bonn 53225 732 DE 734 Email: stefan@drees.name 735 URI: http://sdre.es/