-
Notifications
You must be signed in to change notification settings - Fork 193
Exception Importing several OSM files #320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Unfortunately, importing to different layers do not do it either. // CREATING A LAYER 1 row available after 78 ms, consumed after another 4 ms // CHECKING 3 rows available after 43 ms, consumed after another 1 ms // IMPORTING FILE1 TO LAYER AA 1 row available after 11084 ms, consumed after another 0 ms // CREATING A LAYER 1 row available after 78 ms, consumed after another 0 ms // CREATING A 3RD LAYER 1 row available after 74 ms, consumed after another 0 ms // IMPORTING FILE 2 TO LAYER 3 |
Hi,
I met this issue while importing two files I exported from the openstreetmap website.
On a empty graph, exception occurred during the second import (no matter which file).
I reproduced it with the .osm files in the repo.
I can import map.osm, then map2.osm but then it fails to import one-street.osm (or two-street.osm).
neo4j> call spatial.importOSM('/home/jerome/OpenSource/spatial/map.osm');
+-------+
| count |
+-------+
| 55 |
+-------+
1 row available after 1691 ms, consumed after another 0 ms
neo4j> call spatial.importOSM('/home/jerome/OpenSource/spatial/map2.osm');
+-------+
| count |
+-------+
| 1072 |
+-------+
1 row available after 8323 ms, consumed after another 0 ms
neo4j> call spatial.importOSM('/home/jerome/OpenSource/spatial/one-street.osm');
Failed to invoke procedure
spatial.importOSM
: Caused by: java.util.NoSuchElementException: More than one element in org.neo4j.kernel.impl.coreapi.LegacyIndexProxy$1@5295b11d. First element is 'Node[856]' and the second element is 'Node[128027]'I'm using 3.1.6 community and Spatial v0.24 neo4j-spatial-0.24-neo4j-3.1.4-server-plugin.jar
The text was updated successfully, but these errors were encountered: