anchor.diff:  === GET file
   
   Search the data store for chunks that match a given <<query-language, query>>. Merge the chunks found and return the result as a file.
  -<<scrolling,Scrolling>> is also available.
   
   ===== Resource URL
   
  
positive.code: Dates must be given in the form `YYYY-MM-DD`, `YYYY-MM` or `YYYY`. Times must be given as `HH:mm:ss`, `HH:mm` or `HH`.
  ====
  
  ==== Get property values
  
  Get all values of a property with the following command:
  
negative.code: </CityModel>
  ----
  
  [[get-property-values]]
  === GET property values
  
  Get a list of all values of a property from all chunks matching a given <<query-language, query>>. Properties are key-value pairs that you can attach to your data to make it searchable.
  
  NOTE: Duplicate values are not filtered out. See the <<get-property-value-command, get property value command>> for more information.
  
  WARNING: Properties belong to metadata and should not be mixed up with indexed attributes contained in the imported data (such as CityGML generic attributes or GeoJSON properties). For indexed attributes, see the <<get-attribute-values>> endpoint instead.
  
  ===== Resource URL
  
    /store/:path
  
  ===== Parameters
  
  [cols="1,2"]
  |===
  | *property* +
    _(required)_
  | The name of the property whose values should be returned.
  | *path* +
    _(optional)_
  | The absolute path to a layer to search. Omit this parameter to query the whole data store.
  | *search* +
    _(optional)_
  | A URL-encoded <<query-language, query string>>. If no query string is provided, the property values of all chunks from the requested layer will be returned.
  |===
  
  ===== Status codes
  
  [cols="1,2"]
  |===
  | *200*
  | The operation was successful
  | *400*
  | The provided information was invalid (e.g. malformed query)
  | *404*
  | The requested chunks were not found or the query returned an empty result
  | *500*
  | An unexpected error occurred on the server side
  |===
  
  ===== Example request
  
    GET /store/CityModel?property=type&search=LOD1+textured+13.378,52.515,13.380,52.517 HTTP/1.1
  
  ===== Example response
  
  ----
  HTTP/1.1 200 OK
  Transfer-Encoding: chunked
  
  ["Building", "Building", "Building", "Tree", ... "Tree", "Building", "Tree", "Street"]
  ----
  
  [[get-attribute-values]]
  === GET indexed attribute values
  
  Get a list of all values of an indexed attribute from all chunks matching a given <<query-language, query>>. In contrast to properties, indexed attributes are information inside the imported chunks (such as CityGML generic attributes or GeoJSON properties).
  
  NOTE: Similar to the <<get-property-values>> endpoint, duplicate values are not filtered out.
  
  ===== Resource URL
  
    /store/:path
  
  ===== Parameters
  
  [cols="1,2"]
  |===
  | *attribute* +
    _(required)_
  | The name of the indexed attribute whose values should be returned.
  | *path* +
    _(optional)_
  | The absolute path to a layer to search. Omit this parameter to query the whole data store.
  | *search* +
    _(optional)_
  | A URL-encoded <<query-language, query string>>. If no query string is provided, the attribute values of all chunks from the requested layer will be returned.
  |===
  
  ===== Status codes
  
  [cols="1,2"]
  |===
  | *200*
  | The operation was successful
  | *400*
  | The provided information was invalid (e.g. malformed query)
  | *404*
  | The requested chunks were not found or the query returned an empty result
  | *500*
  | An unexpected error occurred on the server side
  |===
  
  ===== Example request
  
    GET /store/CityModel?attribute=Street&search=LOD1 HTTP/1.1
  
  ===== Example response
  
  ----
  HTTP/1.1 200 OK
  Transfer-Encoding: chunked
  
  ["Main Street", "Main Street", "5th Avenue", "Lake Street", ... "5th Avenue", "5th Avenue", "Lake Street", "Main Street"]
  ----
  
  === POST file
  