Add new search_format_types mapping for government index
Reorganise government index mappings & make more of it excluded from all
Add and use MultiJson

also use double quotes as per the coding standards
CODING STANDARD POLICE
sketch of the advanced search method
Tweak advanced_search query handling

* remove fuzziness from the query_string (it's not supported)
* handle boolean properties properly
* for single value terms, don't wrap the filter in an array
Correct conversion from page/per_page params to from/size query
Allow for pagination in clients, return total with results
add world locations
add index name to the logging output
formatting
tidy up mappings

using strings as we now use slugs
Add tests around ElasticSearch#advanced_search

Tidy up the implementation while we're at it.
Test the return value of advanced_search

It's not just an array of documents, so we should be explicit about it.
Test the app.rb implementation of advanced_search
Provide integration tests for the advanced_search endpoint
Respond to code style fixes pointed out by @fatbusinessman
Return a hash instead of an array, it's more intention revealing
Be more strict about boolean parsing

Specifically, just allow true/1 and false/0. true/false is obvious, 1/0 is to help with hooking up rails checkboxes to a frontend that can just pass values straight through.
Reject a request if values for boolean and date properties are weird

Reject any request for a filter on a boolean where the value is not true/1/false/0.  Reject any request for a filter on a date where the value is not a hash with 'before' and/or 'after' keys and the value of those keys is not YYYY-MM-DD formatted.