Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
SpatialIndex not created on Import
See original GitHub issueI just saw that the SpatialIndex is not created when using the import function instead of the web function.
Obviously the reason for this is that the SpatialIndex creation part is in the web module but Import does not use the web module.
A reasonable solution could be to move the package com.graphhopper.spatialrules to the tools. We would further need to create a dependency from web to tools.
Another solution could be to move the package com.graphhopper.spatialrules to the core, which would result in no additional dependencies.
WDYT?
Issue Analytics
- State:
- Created 6 years ago
- Comments:17 (17 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
There is the famous Android 64K reference limit that makes dependencies there very important to watch. Workarounds exist, but each with its own impact. Also Android org.json package is not so advanced as Gson or Jackson.
Perfect, now I get where the org.json stuff came from.