Make table writable for data import Lookup tables will probably be filled with data during import and thus should reside in the waterway schema, which is accordingly authorised. Touch only the one table relevant for bottlenecks here, as other data might be handled differently. Lookup tables referenced in out-commented columns not touched, as it is not yet clarified whether these columns will be removed completely. countries not touched neither, because it will be filled from different source and demo-data should have everything necessary to start importing bottlenecks.

--- a/schema/tap_tests_data.sql	Tue Sep 04 17:13:25 2018 +0200
+++ b/schema/tap_tests_data.sql	Tue Sep 04 21:41:45 2018 +0200
@@ -17,7 +17,7 @@
 INSERT INTO users.list_users VALUES (
     'sys_admin', 'test_sys_admin1', 'sys_admin1$', 'AT', NULL, 'zzz');
 
-INSERT INTO limiting_factors VALUES ('depth'), ('width');
+INSERT INTO waterway.limiting_factors VALUES ('depth'), ('width');
 
 INSERT INTO waterway.gauges (
     location, function_code, objname, geom, zero_point, source_organization)