isochrones generated almost rectangular polygons

[ARFWellingtonCE]

Hello,
I tried to generate isochrones of the "Truck" category, at times of 15,30,60 and 90 minutes, and some points generated almost rectangular polygons.
The total was 28/2484 that presented such an error.
I managed to fix some by generating random points within the areas of interest, but two still insisted on not generating the isochrones correctly.
Below is an image with an example of the 28 isochrones with the error mentioned above.

P.S. I tested with 120 random points on each feature and none of them managed to generate the isochrone and other points were normally generated isochrones.

[nilsnolde]

Interesting, never seen that. Can you provide some example lat/lon for some of those points? 3-4 would be enough. Thanks!

I transferred the issue to upstream Valhalla, where the issue really lies.

[nilsnolde]

Hmpf somehow I can’t transfer stuff across orgs. Once we have the coords, I’ll open it there manually.

[ARFWellingtonCE]

Hello,
I will send the file of the elements where the area generates the problem, even generating points outside the centroid.

Centr_HEX_erro_Isocro8.csv

These are the centroids with error in a hexagon mesh generated within QGis itself, and the only field to generate such a mesh is the horizontal distance (between the bases of the hexagons) of 380.

[nilsnolde]

Can you also tell us what costing options you used? View > Panels > Log Messages in QGIS. This plugin will print the parameters for each request there. Please copy/paste one of those right here.

[ARFWellingtonCE]

Versão do QGIS: 3.30.2-'s-Hertogenbosch
Código de revisão do QGIS: 0992b533
Versão do Qt: 5.15.3
Versão do Python: 3.9.5
Versão do GDAL: 3.6.4
Versão do GEOS: 3.11.2-CAPI-1.17.2
Versão do PROJ: Rel. 9.2.0, March 1st, 2023
Versão PDAL: 2.5.2 (git-version: 6573a3)
Algoritmo iniciado as: 2023-12-15T10:55:45
Algoritmo 'Isochrones Truck' iniciando…
Entrada de parâmetros:
{ 'INPUT_FIELD' : 'id', 'INPUT_MODE' : 0, 'INPUT_POINT_LAYER' : 'D:\github\points\8Points.shp', 'INPUT_PROVIDER' : 0, 'avoid_locations' : None, 'axle_load' : None, 'contours' : '15,30,60,90', 'contours_distance' : '', 'country_crossing_cost' : None, 'country_crossing_penalty' : None, 'denoise' : '', 'ferry_cost' : None, 'gate_cost' : None, 'generalize' : '', 'hazmat' : False, 'height' : None, 'length' : None, 'maneuver_penalty' : None, 'polygons' : 0, 'show_locations' : False, 'toll_booth_cost' : None, 'toll_booth_penalty' : None, 'use_ferry' : None, 'use_highways' : None, 'weight' : None, 'width' : None }

OverQueryLimit: Retrying...
OverQueryLimit: Retrying...
Execution completed in 7.65 segundos
Resultados:
{'OUTPUT_TIME': 'Isochrones_Truck_55d6a66d_094b_4c28_b24e_8da1b2f8549a'}

Carregando camada resultante
Algoritmo 'Isochrones Truck' finalizado

[nilsnolde]

'INPUT_MODE' : 0 is that auto/car? I'm pretty sure it is, just making sure..

[ARFWellingtonCE]

'INPUT_MODE' : 0 = fastest
'INPUT_MODE' : 1 = Shortest

[nilsnolde]

Ah no it says truck right there.. never mind then

[chrstnbwnkl]

I've had a look at this, @ARFWellingtonCE, and the square shape just indicates an "empty" isochrone. If you want to follow up on the topic, I have laid it out in more detail in here: valhalla/valhalla#4459 (comment). What you can do immediately to at least not get empty results is look at what specific truck width and height values apply to your use case and update them in the request parameters. If they are below the max values read from the OSM way tags, you should get non-empty results.