Spatial 0.25.2-neo4j-3.3.0

Release 0.25 introduced a new geohash index for points. However, that release had only the barest API for Java access. This update 0.25.2 provides a more extensive Java and Cypher procedures API for using the Geohash index. For Neo4j 3.0 (update 0.25.1) this primarily means:

• the new spatial.addPointLayerGeohash(name) procedure
• the addition of the type 'geohash' for the second parameter to spatial.addLayer(name,type) procedure. See spatial.layerTypes() for the complete list.

For Neo4j 3.1, 3.2 and 3.3 (update 0.25.2) we have also made use of the ability of procedures to have optional arguments and added two additional arguments to the other point layer creation procedures:

• spatial.addPointLayer(name,indexType,crsName)
• spatial.addPointLayerXY(name,xProperty,yProperty,indexType,crsName)
• spatial.addPointLayerWithConfig(name,encoderConfig,indexType,crsName)

The default for indexType, if omitted, is rtree. The only other allowed value is geohash. The crsName is currently a placeholder for more extensive CRS support, and right now only wgs84 is supported.

Spatial 0.25.2-neo4j-3.2.5

Release 0.25 introduced a new geohash index for points. However, that release had only the barest API for Java access. This update 0.25.2 provides a more extensive Java and Cypher procedures API for using the Geohash index. For Neo4j 3.0 (update 0.25.1) this primarily means:

• the new spatial.addPointLayerGeohash(name) procedure
• the addition of the type 'geohash' for the second parameter to spatial.addLayer(name,type) procedure. See spatial.layerTypes() for the complete list.

For Neo4j 3.1, 3.2 and 3.3 (update 0.25.2) we have also made use of the ability of procedures to have optional arguments and added two additional arguments to the other point layer creation procedures:

• spatial.addPointLayer(name,indexType,crsName)
• spatial.addPointLayerXY(name,xProperty,yProperty,indexType,crsName)
• spatial.addPointLayerWithConfig(name,encoderConfig,indexType,crsName)

The default for indexType, if omitted, is rtree. The only other allowed value is geohash. The crsName is currently a placeholder for more extensive CRS support, and right now only wgs84 is supported.

Spatial 0.25.2-neo4j-3.1.4

Release 0.25 introduced a new geohash index for points. However, that release had only the barest API for Java access. This update 0.25.2 provides a more extensive Java and Cypher procedures API for using the Geohash index. For Neo4j 3.0 (update 0.25.1) this primarily means:

• the new spatial.addPointLayerGeohash(name) procedure
• the addition of the type 'geohash' for the second parameter to spatial.addLayer(name,type) procedure. See spatial.layerTypes() for the complete list.

For Neo4j 3.1, 3.2 and 3.3 (update 0.25.2) we have also made use of the ability of procedures to have optional arguments and added two additional arguments to the other point layer creation procedures:

• spatial.addPointLayer(name,indexType,crsName)
• spatial.addPointLayerXY(name,xProperty,yProperty,indexType,crsName)
• spatial.addPointLayerWithConfig(name,encoderConfig,indexType,crsName)

The default for indexType, if omitted, is rtree. The only other allowed value is geohash. The crsName is currently a placeholder for more extensive CRS support, and right now only wgs84 is supported.

Spatial 0.25.1-neo4j-3.0.8

Release 0.25 introduced a new geohash index for points. However, that release had only the barest API for Java access. This update 0.25.1 provides a more extensive Java and Cypher procedures API for using the Geohash index. For Neo4j 3.0 this primarily means:

• the new spatial.addPointLayerGeohash(name) procedure
• the addition of the type 'geohash' for the second parameter to spatial.addLayer(name,type) procedure. See spatial.layerTypes() for the complete list.

For Neo4j 3.1, 3.2 and 3.3 we have made use of the ability of procedures to have optional arguments and added two additional arguments to the other point layer creation procedures:

• spatial.addPointLayer(name,indexType,crsName)
• spatial.addPointLayerXY(name,xProperty,yProperty,indexType,crsName)
• spatial.addPointLayerWithConfig(name,encoderConfig,indexType,crsName)

The default for indexType, if omitted, is rtree. The only other allowed value is geohash. The crsName is currently a placeholder for more extensive CRS support, and right now only wgs84 is supported.

Spatial 0.25-neo4j-3.3.0

Version 0.25 contains two primary changes:

• Addition of a GeoHash based index for point-only layers
• Change of license to GPL

The geohash index uses Neo4j's existing support for explicit string indexes, and follows the current pattern of manually adding nodes to the index during the layer.add operation. Each node will have its point location geohashed and the string result added to the index. Subsequent searches (including geopipes searches) will create a geohash prefix search against the index.

The change to GPL was something that should have been done back with Neo4j itself changed to GPL, however, it was overlooked at the time, leaving the spatial library using the AGPL (which Neo4j itself used before).

Spatial 0.25-neo4j-3.2.5

Version 0.25 contains two primary changes:

• Addition of a GeoHash based index for point-only layers
• Change of license to GPL

The geohash index uses Neo4j's existing support for explicit string indexes, and follows the current pattern of manually adding nodes to the index during the layer.add operation. Each node will have its point location geohashed and the string result added to the index. Subsequent searches (including geopipes searches) will create a geohash prefix search against the index.

The change to GPL was something that should have been done back with Neo4j itself changed to GPL, however, it was overlooked at the time, leaving the spatial library using the AGPL (which Neo4j itself used before).

Spatial 0.25-neo4j-3.1.4

Version 0.25 contains two primary changes:

• Addition of a GeoHash based index for point-only layers
• Change of license to GPL

The geohash index uses Neo4j's existing support for explicit string indexes, and follows the current pattern of manually adding nodes to the index during the layer.add operation. Each node will have its point location geohashed and the string result added to the index. Subsequent searches (including geopipes searches) will create a geohash prefix search against the index.

The change to GPL was something that should have been done back with Neo4j itself changed to GPL, however, it was overlooked at the time, leaving the spatial library using the AGPL (which Neo4j itself used before).

Spatial 0.25-neo4j-3.0.8

Version 0.25 contains two primary changes:

• Addition of a GeoHash based index for point-only layers
• Change of license to GPL

The geohash index uses Neo4j's existing support for explicit string indexes, and follows the current pattern of manually adding nodes to the index during the layer.add operation. Each node will have its point location geohashed and the string result added to the index. Subsequent searches (including geopipes searches) will create a geohash prefix search against the index.

The change to GPL was something that should have been done back with Neo4j itself changed to GPL, however, it was overlooked at the time, leaving the spatial library using the AGPL (which Neo4j itself used before).

Spatial 0.24.1-neo4j-3.2.5

Ported Neo4j Spatial 0.24.1 to Neo4j 3.2.5

Spatial 0.24.1-neo4j-3.1.4

This is release is mostly just bringing the 0.24.1 version up to date with master, which involves some refactoring around the generation of documentation, and adding descriptions to the procedures. There is, however, also a bugfix in handling Dates in the shapefile importer. We built against 3.1.4, although it should work for all 3.1.x versions except the unfortunate 3.1.2.

For the bugfix see 01e61a2 for details.