"Global secondary index cell does not project [geometryid]"

[sgillies]

Query in the cardboard script isn't working for my new table. The fio program below is the Fiona CLI (replacement for ogrinfo).

$ ./cardboard sgillies-shade --export | fio info
endpoint undefined
your table is ready sgillies-shade
{"count": 288, "crs": "+datum=WGS84 +no_defs +proj=longlat", "driver": "GeoJSON", "bounds": [-106.523437, 39.571822, -106.435546, 39.639537], "schema": {"geometry": "Polygon", "properties": {"val": "int", "id": "str"}}}
$ ./cardboard sgillies-shade --query="-107,39,-106,40"
endpoint undefined
your table is ready sgillies-shade
{ [ValidationException: One or more parameter values were invalid: Global secondary index cell does not project [geometryid]]
  message: 'One or more parameter values were invalid: Global secondary index cell does not project [geometryid]',
  code: 'ValidationException',
  time: Thu Sep 18 2014 13:46:44 GMT-0600 (MDT),
  statusCode: 400,
  retryable: false }

Removing 'geometryid' from the query options in cardboard.bboxQuery() doesn't break the tests, @mick, but then I get an empty result collection.

[mick]

Yep. Its because geometryid is no more, instead we are keeping the full url to the feature on s3 as s3url But that should have make some tests fail.

[sgillies]

After 06876e8 I'm getting the results I expect:

$ ./cardboard sgillies-shade --query="-107,39,-106,40" | fio info
endpoint undefined
your table is ready sgillies-shade
{"count": 288, "crs": "+datum=WGS84 +no_defs +proj=longlat", "driver": "GeoJSON", "bounds": [-106.523437, 39.571822, -106.435546, 39.639537], "schema": {"geometry": "Polygon", "properties": {"val": "int", "id": "str"}}}
$ ./cardboard sgillies-shade --query="-108,39,-107,40" | fio info
endpoint undefined
your table is ready sgillies-shade
{"count": 0, "crs": "+datum=WGS84 +no_defs +proj=longlat", "driver": "GeoJSON", "bounds": [0.0, 0.0, 0.0, 0.0], "schema": {"geometry": "Unknown", "properties": {}}}

[sgillies]

Conclusion: empty results in my case, using cardboard on dynamodb and not dynalite, were due to the bounding box params being undefined when the post-query bbox filtering was done.