Data Series Proposal

* This proposal was not accepted by consensus of the 1.0 authors. *

Given the recent interest in expanding GeoJSON to represent various types of data collection series, I propose an optional extension to GeoJSON, the DataSeries property. dataSeries would be a property on the main feature not in the attributes object. It would follow one of the 2 formats presented below. This property would be optional and it would be perfectly valid for general clients to ignore it. However, for those clients which did read it, it would provide a standard representation of a data series without creating overly verbose feature collections to describe tightly coupled data.

dataSeries Syntax

Fixed Attributes & Arrays of Data

{ "type": "Feature",
  "geometry": {"type": "Point", "coordinates": [102.0, 0.5]},
  "properties": {"prop0": "value0"},
  "dataSeries":{
    {"properties":["time","air_pressure","air_temperature","salinity"],
     "data":[["2011-10-22 21:00:00Z","1017.4","19.4","35.18"],[...],[...]]
    }
}

Data is presented as a simple array and the collection series is an array of the value arrays. The key name for each observation in the value array is presented in the properties array.

Data Value Objects

{ "type": "Feature",
  "geometry": {"type": "Point", "coordinates": [102.0, 0.5]},
  "properties": {"prop0": "value0"},
  "dataSeries":{
     "data":[{"time":"2011-10-22 21:00:00Z","air_pressure":"1017.4","air_temperature":"19.4"},
             {"time":"2011-10-22 21:15:00Z","salinity":"35.18","water_temperature":"21.55"}
            ]
    }
}

Data is presented as an array of objects containing key:value pairs. This representation makes more sense for data series in which the same type of data is not recorded each time.