You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behaviour
Resulted isochrone geometries could be ordered by isochrone_distance (in descending our). This would benefit the user as the largest isochrone geometries (the most far-reaching isochrones) would stay below the smaller ones (the isochrone geometries with the smallest time-based or road-based distance to the destinations). This would be expected behaviour:
Current behaviour
The current behaviour visualizes the geometries as follows:
Additional context
To see the expected output, first, you have to export the output layer generated by the Catchment plugin as a GeoPackage or to a new GeoPackage. This enables you to run SQL and order the geometries by the isochrone_distance-column. In QGIS, you can execute SQL on your GeoPackage-files e.g. as follows:
Modify accordingly (layer name) the following SQL query and execute the query: SELECT * FROM "zones_30_min" ORDER BY isochrone_distance DESC
Without any transparency and visualized in a graduated (by the isochrone_distance-column) mode, the output visualization would be the following:
The text was updated successfully, but these errors were encountered:
Expected behaviour
Resulted isochrone geometries could be ordered by isochrone_distance (in descending our). This would benefit the user as the largest isochrone geometries (the most far-reaching isochrones) would stay below the smaller ones (the isochrone geometries with the smallest time-based or road-based distance to the destinations). This would be expected behaviour:
Current behaviour
The current behaviour visualizes the geometries as follows:
Additional context
To see the expected output, first, you have to export the output layer generated by the Catchment plugin as a GeoPackage or to a new GeoPackage. This enables you to run SQL and order the geometries by the isochrone_distance-column. In QGIS, you can execute SQL on your GeoPackage-files e.g. as follows:
Modify accordingly (layer name) the following SQL query and execute the query:
SELECT * FROM "zones_30_min" ORDER BY isochrone_distance DESC
Without any transparency and visualized in a graduated (by the isochrone_distance-column) mode, the output visualization would be the following:
The text was updated successfully, but these errors were encountered: