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
Module 1 sometimes create dummy layers for m1_via_point/m1_start_point/m1_stricken_area, which in turn creates empty gpkg files in the geoserver_data_dir, and this results in error when query module is trying to load these gpkgs as queryable layers.
The text was updated successfully, but these errors were encountered:
JowieXiang
changed the title
Query: remove m1_via_point/m1_start_point/m1_stricken_area from queriable layers
Query: remove m1_via_point/m1_start_point/m1_stricken_area/m1_time_map from queriable layers
Nov 30, 2020
Module 1 sometimes create dummy layers for m1_via_point/m1_start_point/m1_stricken_area, which in turn creates empty gpkg files in the geoserver_data_dir, and this results in error when query module is trying to load these gpkgs as queryable layers.
Isn't it solved by restricting the query module to access PERMANENT mapset layers only?
Anyway, creating broken files is probably not a good idea...
Module 1 sometimes create dummy layers for m1_via_point/m1_start_point/m1_stricken_area, which in turn creates empty gpkg files in the geoserver_data_dir, and this results in error when query module is trying to load these gpkgs as queryable layers.
The text was updated successfully, but these errors were encountered: