anchor.diff:  
   == Introduction
   
  -GeoRocket is a high-performance data store for geospatial files. It can store 3D city models (e.g. CityGML), GML files or any other XML-based geospatial data sets. GeoRocket provides the following features:
  +GeoRocket is a high-performance data store for geospatial files. It can store GeoJSON files, 3D city models (e.g. CityGML), GML files or any other XML-based geospatial data sets. GeoRocket provides the following features:
   
   * High performance data storage with multiple back-ends such as Amazon S3, MongoDB, distributed file systems (e.g. HDFS or Ceph), or your local hard drive (enabled by default)
   * Support for high-speed search features based on the popular Open-Source framework https://www.elastic.co/[Elasticsearch]. You can perform spatial queries and search for attributes, layers and tags.
  
positive.code: 
  [NOTE]
  ====
  In the following sections it is assumed that you have the `georocket` executable in your path. If you have not done so already, you may add it to your path with the following command (Linux):
  
    export PATH=/path/to/georocket-cli-1.0.1-SNAPSHOT/bin:$PATH
  
  Or under Windows do:
  
    set PATH=C:\path\to\georocket-cli-1.0.1-SNAPSHOT\bin;%PATH%
  ====
  
negative.code: 
  The advantage of keeping a secondary data store is that it is created automatically in the background when new data is added to GeoRocket. This avoids manual processing. Individual processors may even keep the secondary data store up to date incrementally and only re-create those parts that have changed since it has been created or updated the last time.
  
  === Glossary
  
  This section contains a list of terms often used in this document and in GeoRocket.
  
  Chunk:: A part of an imported file, typically a geospatial feature (e.g. a building from a 3D city model).
  Metadata:: Information about a chunk (such as user-defined tags and properties, as well as derived attributes).
  Secondary data store:: A store for data that is automatically derived from chunks in the main data store (e.g. https://www.khronos.org/gltf[glTF] files derived from imported CityGML chunks).
  Tag:: A user-defined label that can be attached to one or more chunks in order to categorise data. In contrast to a layer, multiple tags can be attached to a chunk.
  Property:: A user-defined key-value pair that can be attached to a chunk. Multiple properties can be attached to one chunk, but the key must be unique. Properties belong to metadata and should not be mixed up with attributes contained in the imported data (such as CityGML generic attributes or GeoJSON properties).
  Layer:: A way to structure the data store. Can be compared to folders or directories on a hard drive. In contrast to tags, a chunk can only be stored in one layer. Chunks without a layer are kept in the root layer named `/`. Layers can be structured hierarchically, but parent layers always include all chunks of their children.
  
  == Getting started
  
  GeoRocket consists of two components: the server and the command-line interface (CLI). Download the _Server_ and _CLI_ bundles from the GeoRocket website and extract them to a directory of your choice.
  