Exercise 2 - Indexing

You can think of an index in Elasticsearch as a database. Indexes contain documents and a document is of a given type. For example we might have an index called 'suburbs' and a type called 'suburb'. The index would contain documents which define suburbs and conform to the type 'suburb'.

In Elasticsearch each index has a mapping which is ike a schema definition for all the types within the index.

Elasticsearch supports two spatial types geo point and geo shape. Elasticsearch accepts GeoJSON as it's input geometry format. Because our source data is in Shapefile format we need to translate it into GeoJSON so we can insert it into an index. You can think of each record within our source datasets as a document which we'll insert into an Elasticsearch index.

Elasticsearch will automatically create a mapping for a document type when a new document type is indexed. When creating the mapping, Elasticsearch infers the field data types from the document. For example if we have a field called Name in our suburb dataset and it contains the suburb name 'Melbourne' then Elasticsearch will infer that the field type for the Name field is 'string'. Unfortunately Elasticsearch does not automatically infer the field types for spatial types, to do this we need to manually update the mapping.

In this exercise we're run the following steps using the suburb data:

Create a new index.

Insert a single document and get Elasticsearch to automatically create the mapping based upon that document.

Retrieve the mapping and modify the field type for the geometry.

Delete and recreate the index.

Insert the modified mapping.

Index our suburb data into the index.

Run a single script to load the accident data.

At the end of the exercise all the suburb data will be loaded into a new index called 'suburbs' and all the accident data will be loaded into an index called 'accidents'.