Skip to content
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

[BUG] Regression: new error message on routing #113

Closed
Robinlovelace opened this issue Dec 9, 2023 · 1 comment
Closed

[BUG] Regression: new error message on routing #113

Robinlovelace opened this issue Dec 9, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@Robinlovelace
Copy link
Member

Robinlovelace commented Dec 9, 2023

Describe the bug

Hitting a bug on a small routing job:

14:48:51.410 WARN (StreetVertexIndex.java:389) Couldn't link (53.7452, -1.5885)
Done in 0.1 mins                                                                                                                                                                                   
2023-12-09 14:48:51.64235 processing results
Error in UseMethod("st_as_sfc") : 
  no applicable method for 'st_as_sfc' applied to an object of class "NULL"

To Reproduce

u = "https://github.com/ITSLeeds/TDS/releases/download/22/NTEM_flow.geojson"
desire_lines = read_sf(u)
fromPlace <- lwgeom::st_startpoint(desire_lines)
toPlace <- lwgeom::st_endpoint(desire_lines)
fromPlace <- st_sf(data.frame(id = desire_lines$from, geometry = fromPlace))
toPlace <- st_sf(data.frame(id = desire_lines$to, geometry = toPlace))
  1. Create a new object called routes_drive_top, with driving routes between the OD pairs represented in the desire_lines object.

Calculate routes for the first three desire lines with the following command:

routes_drive_top = otp_plan(otpcon = otpcon,
                            fromPlace = fromPlace,
                            toPlace = toPlace,
                            fromID = fromPlace$id,
                            toID = toPlace$id,
                            mode = "CAR")

Expected behavior

I would expect something to be returned after all that routing, seems to fail too easy.

@Robinlovelace Robinlovelace added the bug Something isn't working label Dec 9, 2023
@mem48
Copy link
Contributor

mem48 commented May 5, 2024

Can't reproduce

I got

2024-05-05 08:54:42.426817 sending 502 routes requests using 44 threads
Done in 0.5 mins                                                                                                                                                         
2024-05-05 08:55:12.046603 processing results
2 routes returned errors. Unique error messages are:

2x messages: "We're sorry. The trip planner is temporarily unavailable. Please try again later."

2024-05-05 08:55:13.239178 done

And 500 out of 502 routes returned

@mem48 mem48 closed this as completed May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants