neo4j-contrib / spatial

Neo4j Spatial is a library of utilities for Neo4j that faciliates the enabling of spatial operations on data. In particular you can add spatial indexes to already located data, and perform spatial operations on the data like searching for data within specified regions or within a specified distance of a point of interest. In addition classes are provided to expose the data to geotools and thereby to geotools enabled applications like geoserver and uDig.
http://neo4j-contrib.github.io/spatial
Other
781 stars 192 forks source link

Error in integrating neo4j with geoserver #368

Open simran0912 opened 4 years ago

simran0912 commented 4 years ago

abcdefg I am getting "Error creating data store, check the parameters. Error message: java.io.IOException: The filename, directory name, or volume label syntax is incorrect" error when integrating neo4j with geoserver.

This is the path (till neostore.id) which I mentioned in connection parameters but still I am getting the above error file://D:\research papers\irrigation\appneo4j\neo4jDatabases\database-62e909e0-5b57-4813-b070-b316f62333e4\installation-3.5.14\data\databases\graph.db\neostore.id

I am using the following versions for geoserver, neo4j and spatial plugin:

  1. geoserver-2.16.2
  2. neo4j 3.5.14 Enterprise version
  3. neo4j-spatial-0.26.2-neo4j-3.5.2-server-plugin

Any help on this error will be appreciated.

mprins commented 4 years ago

I think you will find that even if you get around this issue there are incompatibilities between your geoserver version and the version of geotools used in this neo4j spatial.

The geotools version must match with that of geoserver to even have a chance of working, check the geoserver release notes to find out which version matches with geotools 14.4.

craigtaverner commented 4 years ago

There are two pull-requests to upgrade geotools support (to versions 21 and 22 respectively) in the list of pull requests above. We hope to integrate one or both of these soon. If you need this urgently, you could also follow those PR's to their source and build them locally.