anchor.diff:  }
   ----
   
  -
  -See the https://github.com/lambdamatic/lambdamatic-mongodb-citibikesnyc[NYC Bikes sample application] for more details.
  -
  -=== Projections
  -
  -In some cases, you may not want to retrieve all the documents'fields from MongoDB,
  -but just the ones you want to display in the UI. Lambdamatic supports `Projection`
  -as well, using the following syntax:
  +The `Location` class is a special data-type provided by Lambdamatic. It is converted
  +into a custom BSON document or query document.
  +
  +See the https://github.com/lambdamatic/lambdamatic-mongodb-citibikesnyc[NYC Bike Stations sample application] for more details.
  +
  +===== Combining Operators
  +
  +
  +===== Queries on Collections
  +
  +*TODO*
  +
  +===== Queries on Maps
  +
  +*TODO*
  +
  +
  +==== Projections
  +
  +In some cases, users do not want to retrieve all the documents'fields from MongoDB,
  +but only the ones that need to be processed in the business layer or displayed in the UI.
  +Lambdamatic supports projection as well, using the following syntax:
   
   [code,java]
   ----
  
positive.code: = Lambdamatic: Query MongoDB with Lambda Expressions
  
  == Status
  
  Prototype (with its share of missing features and bugs)
  
  
  == Project Configuration
  
  In your `pom.xml`, add the following dependency:
  
  [code,xml]
  ----
  <dependency>
    <groupId>org.lambdamatic</groupId>
  
negative.code: }
  ----
  
  ===== Operators
  
  ===== Geo-searching
  
  More interestingly, you can leverage MongoDB's geosearch capabilities to find
  all `BikeStation` that are `IN_SERVICE` and within a given area:
  
  [source,java]
  ----
  import org.lambdamatic.mongodb.types.geospatial.Location;
  ...
  