Release 2025.10.0

Fixes

• Refactor Neo4jSpatialFeatureReader to use ECQL instead of CQL by @Andy2003 (#453)

Code-Cleanup

• Replace system.out and system.err by Java logging framework by @Andy2003 (#451)

Updated dependencies

• Update dependencies by @Andy2003 (#454)

Release 2025.07

Features

• Add a spatial function to convert WKT to Geo-JSON by @Andy2003 (#406)
• Add support for native point array properties by @Andy2003 (#404)
• add function to convert neo4j native point(s) to WKT format by @Andy2003 (#409)
• Add Index Configuration Feature to Neo4j Spatial by @Andy2003 (#410)
• Make spatial query procedures read only by @Andy2003 (#403)

Documentation

• Migrate docs to be generated via antora by @Andy2003 (#421)
• Change the nav-structure so more pages are listed at the main navigation by @Andy2003 (#426)
• Enhance spatial documentation with clearer descriptions and examples by @Andy2003 (#433)

Updated dependencies

• Bump cookie and express in /docs by @dependabot[bot] (#431)
• update to neo4j 5.26 and geo-tools 32.2 by @Andy2003 (#432)

Release 5.26.0

Features

• Add a spatial function to convert WKT to Geo-JSON by @Andy2003 (#406)
• Add support for native point array properties by @Andy2003 (#404)
• add function to convert neo4j native point(s) to WKT format by @Andy2003 (#409)
• Add Index Configuration Feature to Neo4j Spatial by @Andy2003 (#410)
• Make spatial query procedures read only by @Andy2003 (#403)

Documentation

• Migrate docs to be generated via antora by @Andy2003 (#421)
• Change the nav-structure so more pages are listed at the main navigation by @Andy2003 (#426)
• Enhance spatial documentation with clearer descriptions and examples by @Andy2003 (#433)

Updated dependencies

• Bump cookie and express in /docs by @dependabot[bot] (#431)
• update to neo4j 5.26 and geo-tools 32.2 by @Andy2003 (#432)

Release 5.20.0

Updated dependencies

• update to neo4j 5.20 by @Andy2003 (#419)

Release 5.19.0

Note: From this release onwards, the versioning of this plugin will be adjusted to match the major and minor version of Neo4j to which the plugin is compatible.

Features

• Add github workflow for pr-builds by @Andy2003 (#397)
• migrate all tests to junit jupiter by @Andy2003 (#402)
• Add Shortcut for spatial.intersects procedure by @Andy2003 (#412)
• Create release workflow by @Andy2003 (#414)

Code-Cleanup

• Add .editorconfig and apply the new codestyle + optimize imports by @Andy2003 (#396)
• cleanup code (apply intellij code inspection fixes) by @Andy2003 (#398)
• update copyright by @Andy2003 (#400)
• update copyright by @Andy2003 (#401)
• replace custom map method by Map::of by @Andy2003 (#405)
• code-cleanup: static methods, @override by @Andy2003 (#407)
• Split up procedures and functions into separate classes by @Andy2003 (#408)
• Fix the Asciidoc build by @Andy2003 (#411)
• Replace Travis badge by GitHub build badge by @Andy2003 (#415)

Updated dependencies

• update dependencies by @Andy2003 (#399)

Spatial 0.28.1-neo4j-4.4.3

Ported to Neo4j 4.4.3

This version of Neo4j changed many dependencies and was built with JDK17. We were not able to use JDK17 to build Spatial but did need to upgrade many dependencies to get things working.

One particularly big upgrade was the move from Junit4 to Junit5 which required changes to every single test class.

The lastest version of Geotools does not support JDK17 and so we will hold off upgrading completely to JDK17 before Geotools has completed their port.

Spatial 0.28.1-neo4j-4.3.10

Ported to Neo4j 4.3

Neo4j 4.3 has an issue with leaking RelationshipTraversalCursor, and we needed to do some workarounds to avoid this issue, usually by exhausting the iterator, which can have a higher performance cost in some cases. We updated the version number to 0.28.1 to reflect these bug-fixes / workarounds.

Spatial 0.28.0-neo4j-4.2.3

Version 0.28 begins work on trying to deal work multiple OSM imports. For this release, we disallow importing the same OSM file twice, unless you specify two separate layers, and we also ensure that the indexes are not mixed up between the layers, something that was the case in all previous releases.

To achieve this, two main changes were made:

• Use unique labels for indexing within multiple OSM layers.
  Essentially when adding nodes of a particular label, we also add a label with a unique name for indexing purposes.
  The unique name is made of the original name plus a hex suffix made of the MD5 hash of the layer name.
  For example, the layer geom1 will have an MD5 hash of its name 9ECE5459EA0D46FC556E5E3F454A0795.
  Then when adding an OSM node we label the node with both:

  • OSMNode
  • OSMNode_9ECE5459EA0D46FC556E5E3F454A0795

• Remove use of old reference nodes, reducing deadlocks.
  This change is not backwards compatible, as the spatial model is different. Layers created in earlier versions would not be readable in this one.
  To protect against that we throw exceptions on all SpatialDatabaseService. layer finding methods, if they detect the old format. The exception requests that the database be upgraded.
  This can be done in the Java API with the upgradeFromOldModel method, or via procedures using spatial.upgrade.

Spatial 0.27.2-neo4j-4.2.3

Port of the 0.27 branch to Neo4j 4.2. This is a smaller change than the port to 4.1 and a much smaller change that that to 4.0.
Please read the release notes of those releases to understand the full scope of the changes.

For 4.2, the change was more subtle. Mostly only internal API's around the use of Path instead of File.
One change that could be noticed by users is the IndexManager.IndexAccessMode class.
In the 0.27.0 and 0.27.1 versions, we used OverridenAccessMode to take the users existing access mode and simply add on the rights to create tokens and indexes. In 0.27.2 we instead use RestrictedAccessMode to restrict the users access right to the built-in AccessModel.Static.SCHEMA and then boost to enable index and token writes.
The difference is subtle and should only be possible to notice in Enterprise Edition.

Spatial 0.27.1-neo4j-4.1.7

Port to Neo4j 4.1.7. This is very much like the port to 4.0, and involves the same changes and considerations.
Please read the release notes for that release for a more complete view of the extensive changes required to port to Neo4j 4.x.

In addition, some smaller changes were required to support 4.1.7. Mostly some internal API changes:

• Transaction type names
• IndexSeek API change
• Stricter checks on parameters containing Node objects

This last change means that if we return a Node from one transaction, we cannot pass it into a spatial procedure in another transaction. Users have to either lookup the node again in the new transaction, or use some new procedures we provide here:

• spatial.addNode.byId
• spatial.addNodes.byId
• spatial.removeNode.byId
• spatial.removeNodes.byId

Also the removeNode procedures now return nodeId instead of node