Release Notes thru April 14th, 2015


#1

Added

  • demographic.income.* range CSDL targets and output fields, including “start”, “end” and “band” values. You can filter on either the start or end income value as an integer, for example demographic.income.end < 30000. The output will look similar to the example below:
{
  "income": {
    "start": 20000,
    "end": 29999,
    "band": "$20,000 - $29,999"
  }
}
  • An historics_id parameter has been added to our /dpu API endpoint to allow you to find the DPU cost of a given Historics query.
  • You will notice a new output field; twitter.geo_interpolated, which carries a boolean true/false value. This field will be set to true in a case where DataSift has derived a geo point from a geo polygon, so the geo point returned in interactions where "twitter.geo_interpolated": true may not necessarily be accurate. For example, if someone on Twitter checks in to “New York”, Twitter will return a geo-polygon for the boundaries of New York City (not the exact place the user was when they created the Tweet). DataSift will then derive a single geo-point from this polygon and return this as the lat/long value, so this value represents the centre of the geo-polygon, not the point from which the user sent their Tweet