Closed danrademacher closed 5 years ago
An even shorter segment: http://localhost:8007/?loc=13,32.79235,-79.86246&route=32.79629,-79.89077,32.78840,-79.78781
/?loc=15,32.79243,-79.86777&route=32.79629,-79.89077,32.78856,-79.85152
smallest segment I can find that fails: /?loc=16,32.78985,-79.88143&route=32.79492,-79.88307,32.78479,-79.87399
http://localhost:8888/?loc=16,32.79412,-79.88683&route=32.79684,-79.88803,32.79132,-79.88007
Something about this turn: http://localhost:8888/?loc=18,32.79054,-79.88031&route=32.79132,-79.88007,32.78975,-79.87910
This works: http://localhost:8888/?loc=16,32.78653,-79.87779&route=32.78975,-79.87910,32.78319,-79.86934
Noticed in that last shot that something seemed off in the order of the blue chosen route lines. Redrew Church St. NOw it works
Reopening to see if we can assess cause for future reference
Prepping data update form
ecg_route_lines
toecg_route_lines_prod
And there's some error in this section of the route: https://map.greenway.org/?loc=12,32.79478,-79.90854&route=32.77612,-79.92711,32.82586,-79.81822 works fine there
Locally after changing table ref in config.js to
ecg_route_lines
http://localhost:8007/?loc=13,32.81108,-79.87767&route=32.79629,-79.89077,32.82586,-79.81822I have inspected each segment in production vs edit tables. Production has some additional segments not in the same area in the edited database, but most differences appear to be improvements (simplification, removing extraneous southbound line running parallel to both line, etc.
Not sure what is causing the router to break there. Works north to south otherwise.
Will look with fresh eyes on monday