Proposed easy fix: Add a function wrapper in "insert_obs_points_triggers_postgis.sql".
create or replace function public.ST_Line_Locate_Point (IN geom1 geometry, IN geom2 geometry) returns double precision language sql as $func$select st_linelocatepoint($1, $2)$$;
A more robust, future-proof, solution would probably be to check postGIS-version and use the relevant function call.
Since postGIS 2.1 the function ST_Line_Locate_Point is renamed to ST_LineLocatePoint. (https://postgis.net/docs/ST_LineLocatePoint.html)
Proposed easy fix: Add a function wrapper in "insert_obs_points_triggers_postgis.sql".
create or replace function public.ST_Line_Locate_Point (IN geom1 geometry, IN geom2 geometry) returns double precision language sql as $func$select st_linelocatepoint($1, $2)$$;A more robust, future-proof, solution would probably be to check postGIS-version and use the relevant function call.