You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The second label is also used to create a label-property index to be used for looking up the node when building ways.
Copy file name to clipboardExpand all lines: README.md
+9-1Lines changed: 9 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -74,6 +74,13 @@ This has meant that the spatial library needed a major refactoring to work with
74
74
and simply add on the rights to create tokens and indexes. In 0.27.2 we instead use `RestrictedAccessMode`
75
75
to restrict the users access right to the built in `AccessModel.Static.SCHEMA` and then boost to enable
76
76
index and token writes. The difference is subtle and should only be possible to notice in Enterprise Edition.
77
+
* 0.28.0 tackles the ability to import multiple OSM files. The initial solution for Neo4j 4.x made use
78
+
of schema indexes keyed by the label and property. However, that means that all OSM imports would share
79
+
the same index. If they are completely disjointed data sets, this would not matter. But if you import
80
+
overlapping OSM files or different versions of the same file file, a mangled partial merger would result.
81
+
0.28.0 solves this by using different indexes, and keeping all imports completely separate.
82
+
The more complex problems of importing newer versions, and stitching together overlapping areas, are not
83
+
yet solved.
77
84
78
85
Consequences of the port to Neo4j 4.x:
79
86
@@ -347,6 +354,7 @@ The Neo4j Spatial Plugin is available for inclusion in the server version of Neo
347
354
*[v0.27.0 for Neo4j 4.0.3](https://github.com/neo4j-contrib/m2/blob/master/releases/org/neo4j/neo4j-spatial/0.27.0-neo4j-4.0.3/neo4j-spatial-0.27.0-neo4j-4.0.3-server-plugin.jar?raw=true)
348
355
*[v0.27.1 for Neo4j 4.1.7](https://github.com/neo4j-contrib/m2/blob/master/releases/org/neo4j/neo4j-spatial/0.27.1-neo4j-4.1.7/neo4j-spatial-0.27.1-neo4j-4.1.7-server-plugin.jar?raw=true)
349
356
*[v0.27.2 for Neo4j 4.2.3](https://github.com/neo4j-contrib/m2/blob/master/releases/org/neo4j/neo4j-spatial/0.27.2-neo4j-4.2.3/neo4j-spatial-0.27.2-neo4j-4.2.3-server-plugin.jar?raw=true)
357
+
*[v0.28.0 for Neo4j 4.2.3](https://github.com/neo4j-contrib/m2/blob/master/releases/org/neo4j/neo4j-spatial/0.28.0-neo4j-4.2.3/neo4j-spatial-0.28.0-neo4j-4.2.3-server-plugin.jar?raw=true)
350
358
351
359
For versions up to 0.15-neo4j-2.3.4:
352
360
@@ -463,7 +471,7 @@ Add the following repositories and dependency to your project's pom.xml:
0 commit comments