anchor.diff:  For most cases there exists an ID-based filtering parameter (`ids`) for collection URLs
   that allow getting basic information of all referred resources with single request.
   
  -== Changes to the API
  +=== Changes to the API
   
   We aim to develop the API in a backwards compatible manner, i.e. features are only added while
   maintaining old semantics. However, we appreciate your feedback and will take it into account
  
positive.code: 
  
  [[overview]]
  = Overview
  
  HSL Park and Ride application contains information about parking facilities near public transportation hubs.
  Data is provided free-or-charge with XXX License.
  
negative.code: 
  
  [[hubs]]
  == Hubs
  
  Public transportation hubs are places where trains, buses, cars and bicycles converge.
  From a hub on may continue to all places reachable via public transportation.
  Hubs are named and defined as a location with optional address as well as a list
  of `facilityIds` that refer to parking facilities that are easily reachable from the hub.
  Basic information of those facilities may be searched from `facilities` resource using `ids`-parameter,
  or by querying for details of each facility separately.
  
  === Search Hubs
  
  Hubs may be searched by (hub) `ids`, `facilityIds` and `geometry` within optional `maxDistance`.
  <<spatial-search>> of hubs works similarly to facilities.
  
  
  === Hub Details
  
  At the time of writing this document there is no structural difference between individual hub resource
  (`hubs/123`) and an item in `hubs` collection resource.
  
  
  [[use-cases]]
  == Use-Case Examples
  
  === Park and Ride With a Navigator
  
  A navigation app may search for hubs within `maxDistance` of 1000 m of the selected route.
  A route is defined as a `LineString` `geometry` which is in essence just a list of coorinates.
  From the result a list of recommended facilities may be extracted and then
  prediction of spaces available at the estimated arrival time.
  