Edge RTree resulting in no path found

[nreinicke]

When using the edge based rtree, with the following config:

Config

parallelism = 2
search_orientation = "edge"

[graph]
edge_list_input_file = "data/tomtom_metro_denver_network/edges-compass.csv.gz"
vertex_list_input_file = "data/tomtom_metro_denver_network/vertices-compass.csv.gz"
verbose = true

[traversal]
type = "distance"
distance_unit = "miles"

[plugin]
input_plugins = [
    { type = "edge_rtree", geometry_input_file = "data/tomtom_metro_denver_network/edges-geometries-enumerated.txt.gz", road_class_input_file = "data/tomtom_metro_denver_network/edges-road-class-enumerated.txt.gz" },
    { type = "grid_search" },
    { type = "load_balancer", weight_heuristic = { type = "haversine" } },
]
output_plugins = [
    { type = "summary" },
    { type = "traversal", geometry_input_file = "data/tomtom_metro_denver_network/edges-geometries-enumerated.txt.gz" },
]

I get the error:

ERROR routee_compass] Error: "no path exists between vertices 57208 and 356583"

There are no restrictions being applied here and so it's not a problem with certain edges being excluded from the search. I wonder if the edge based RTree is starting the search at a terminal vertex?

[robfitzgerald]

can you share the query you ran against this?

i also have had a few times where it just failed. note that this edge-based application configuration uses the edge-oriented search from SearchApp, which we haven't used up to this point. there could be a logic error in how that search handles its edge cases or otherwise translates to/from the vertex-oriented search.

[nreinicke]

Oops, yeah, here's the query:

{
  "origin_name": "NREL",
  "destination_name": "Comrade Brewing Company",
  "origin_x": -105.1710052,
  "origin_y": 39.7402804,
  "destination_x": -104.9009913,
  "destination_y": 39.6757025,
}

[robfitzgerald]

hmm, i don't know what could be causing it, so i'm guessing this task really involves running the debugger with this input.

[robfitzgerald]

Haven't seen this in a while, @nreinicke , maybe we close the issue?

[nreinicke]

Yep just tested the above query and did not see any errors.