with yesterday's model everything looked like that
in the special structure
we have triggers in the db to update it
I worked on them (they are fast now!)
But forgot to re-enable them after some testing
So the symbology did not update
brb, moving from office to home
just sent it to the internship
seems latex has missing support for some special
t character in the romanian charset
the pdf's are now linked from the documentation index.html
This message was deleted
@m-kuhn Documents linked with relations update.
is there a password set for the virtual machine?
hi
is there a username as well?
(guiding somebody else remote :) )
oh, seems its documented
I'm trying to restore the latest qgep data model and I get
pg_restore: [archiver (db)] Error from TOC entry 846; 1259 23699 MATERIALIZED VIEW vw_network_segment postgres
pg_restore: [archiver (db)] could not execute query: ERROR: function st_curvetoline(public.geometry, integer) does not exist
LINE 1: SELECT ST_CurveToLine($1, 32)
^
HINT: No function matches the given name and argument types. You might need to add explicit type casts.
QUERY: SELECT ST_CurveToLine($1, 32)
CONTEXT: SQL function "st_curvetoline" during inlining
Command was: CREATE MATERIALIZED VIEW vw_network_segment AS
WITH reach_parts AS (
SELECT row_number() OVER (ORDER BY od_reach_p...
pg_restore: [archiver (db)] could not execute query: ERROR: relation "vw_network_segment" does not exist
Command was: ALTER TABLE vw_network_segment OWNER TO postgres;
@m-kuhn any ideas?
<datasource>service='pg_qgep' key='"obj_id"' srid=21781 type=LineString table="qgep"."vw_qgep_reach" (progression_geometry) sql=</datasource><datasource>service='pg_qgep' key='"obj_id"' srid=21781 type=CompoundCurve table="qgep"."vw_qgep_reach" (progression_geometry) sql=</datasource>