anchor.diff:  
   [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):
  +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:
  +Windows:
   
     set PATH=C:\path\to\georocket-cli-1.0.1-SNAPSHOT\bin;%PATH%
   ====
  
positive.code: .The architecture of GeoRocket
  image::images/architecture.svg[alt="GeoRocket architecture diagram", width="70%", align="center"]
  
  The import process starts in the upper left corner. Every imported file is first split into individual chunks. Depending on the input format chunks have different meanings. CityGML files, for example, are split into individual `cityObjectMember` objects which are typically the buildings of a city model.
  
  Attached to each chunk is metadata containing additional information describing the chunk. This includes tags specified by the client and other automatically generated attributes.
  
  The chunks are put into the GeoRocket data store. There are several data store implementations supporting different back-ends such as Amazon S3, HDFS, MongoDB or the local hard drive (default).
  
  Immediately after a chunk has been put into the data store the indexer starts working asynchronously in the background. It reads new chunks from the data store and analyses them for known patterns. It recognises spatial coordinates, attributes and other content. The indexer creates a directory of every item found--the '`index`'.
  
  The export process starts with querying the indexer for chunks matching the <<query-language, criteria>> supplied by the client. These chunks are then retrieved from the data store (together with their metadata) and merged into a result file.
  
  
negative.code: 
  == Introduction
  
  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.
  