Examples of CQLIndexReader

org.neo4j.gis.spatial.indexfilter.CQLIndexReader

This class enables support for CQL based dynamic layers. This means the filtering on the result set is based on matches to a CQL query. Some key differences between CQL queries and JSON queries are:

CQL will operate on the geometry itself, performing spatial operations, but also requiring the geometry to be created from the graph. This makes it slower than the JSON approach, but richer from a GIS perspective
JSON will operate on the graph itself, and so it is more specific to the data model, and not at all specific to the GIS meaning of the data. This makes it faster, but more complex to develop to. You really need to know your graph structure well to write a complex JSON query. For simple single-node property matches, this is the easiest solution.

@author dwins

        // Make a standard JSON based dynamic layer
        return new DynamicIndexReader((LayerTreeIndexReader) parent.index, query);
      } else {
        // Make a CQL based dynamic layer
        try {
          return new CQLIndexReader((LayerTreeIndexReader) parent.index, this, query);
        } catch (CQLException e) {
          throw new SpatialDatabaseException("Error while creating CQL based DynamicLayer", e);
        }
      }
    } else {

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.

Examples of CQLIndexReader

Examples of org.neo4j.gis.spatial.indexfilter.CQLIndexReader