Project

General

Profile

Question #1161

API: add more geometry objects

Added by Bernhard Koschiček-Krombholz over 1 year ago. Updated 11 months ago.

Status:
Closed
Priority:
Low
Category:
API
Target version:
-
Start date:
2020-02-21
Estimated time:

Description

In order to be really confirm with the geojson standard, the API has to differentiate more geometry objects than Point, Polygon, LineString and Geometry Collection. So we shoult add MultiPoint, MultiLineString and MultiPolygon.
"To maximize interoperability, implementations SHOULD avoid nested GeometryCollections. Furthermore, GeometryCollections composed of a single part or a number of parts of a single type SHOULD be avoided when that single part or a single object of multipart type(MultiPoint, MultiLineString, or MultiPolygon) could be used instead."
(https://tools.ietf.org/html/rfc7946#section-3.1.8)

I think for now we can leave it be, since it is not wrong, but for the next version it should be included.

History

#1

Updated by Alexander Watzinger over 1 year ago

  • Target version changed from 204 to 5.2.0
  • Status changed from New to Assigned
#2

Updated by Alexander Watzinger over 1 year ago

  • Subject changed from Add more geometry objects to API: add more geometry objects
#3

Updated by Alexander Watzinger over 1 year ago

  • Target version changed from 5.2.0 to API
#4

Updated by Bernhard Koschiček-Krombholz about 1 year ago

  • Assignee changed from Bernhard Koschiček-Krombholz to Stefan Eichert
#5

Updated by Stefan Eichert about 1 year ago

In the linked places the example given is as follows:

"geometry": {
        "type": "GeometryCollection",
        "geometries": [
            { "type": "Point",
              "coordinates": [-1.2879,51.6708],
              "when": {"timespans":[
                {"start":{"in":"1600"},"end":{"in":"1699"}}]},
              "citations": [
                {"label": "Getty TGN (retrieved 4 May 2018)",
                 "@id":"tgn:7011944"}],
              "certainty": "certain" 
            },
            { "type": "Point",
              "coordinates": [-1.31,51.64],
              "geo_wkt": "POLYGON ((-1.3077 51.6542, -1.2555 51.6542, -1.2555 51.6908, -1.3077 51.6908, -1.3077 51.6542))",
              "when": {"timespans":[{"start":{"in":"1700"}}]},
              "certainty": "uncertain" 
            }

So probably we should stick to this?
#6

Updated by Bernhard Koschiček-Krombholz about 1 year ago

  • Status changed from Assigned to Closed

Ok, I'm fine with it. It is easier this way, thank you.

#7

Updated by Alexander Watzinger 11 months ago

  • Target version deleted (API)
  • Tracker changed from Feature to Question

Also available in: Atom PDF