scanmap | mapping tool to track police activity | Map library

r - r0 is not a form supported by let. From the documentation:

-- Function: let let (, , , , ..., ) let ([, , , , ..., ], )

So, it seems like I was barking at the wrong tree here, trying to use Scan instead of Query :

The customer should not use ScanFilter, which is deprecated. List/Map datatypes are better suited to the new FilterExpression syntax. I suspect the problem is with the multi-value attribute with "N:" in the name; this doesn't seem close to the wire format. To use the "new" filter expressions, they should create ExpressionAttributeNames and ExpressionAttributeValues to tell the AWS SDK about the attributes for the filter, addExpressionAttributeNamesEntry and addExpressionAttributeValuesEntry.http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/dynamodbv2/datamodeling/DynamoDBScanExpression.html Also, I would be remiss if I didn't point out that Scan is absolutely not the right API action for this query; Query is the correct action. testName should be used with Query with a KeyConditionExpression to narrow the search down to the correct partition, and revision should be added to the same with the BETWEEN syntax. Scan is intended for backups and background operations, and in this case the customer's index schema can be used with Query to narrow the search. Caution them about using Scan; this is a fundamental best practice:http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/QueryAndScanGuidelines.html

So I've used Query instead :