-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SQL Create Statement #4
Comments
Open Issues:
|
solved - Primary key names cannot contain "." |
solved - - Use BEGIN; .... COMMIT; in progress - Add geometries with specific function from postgis |
Dear Dennis Can you tell me how to change the red part with the situation attribute? COMMENT ON COLUMN qgep.od_reach_point.obj_id IS 'INTERLIS OID mit Postfix/Präfix oder UUOID, see www.interlis.ch'; ALTER TABLE qgep.od_reach_point ADD COLUMN situation GEOMETRY; ALTER TABLE qgep.od_reach_point ADD COLUMN last_modification timestamp without time zone ; |
Hoi Andreas Case "postgres" 'PostGres SQL
'-- Prüft ob Geometrie = POINT, Alternativen http://postgis.refractions.net/documentation/manual-1.5/ch04.html#RefObject
Wäre das dann LINESTRING und POLYGON? Gruss |
You can add a geometry column as follows: There are two different ways: Postgis 1.5 and 2.0: SELECT AddGeometryColumn('schemaname', 'tablename', 'the_geom', 21781, 'POINT', 2); sample for qgep.od_reach: These statements should be executed after the CREATE TABLE statement. I believe that for Postgis 2.0 the above syntax also works, but in Postgis 2.0 there is also an easier way: Postgis 2.0 (only) CREATE TABLE qgep.od_reach possible geometries are: Code '21781' is the EPSG-code for the swiss projection system CH1903. LV95 uses the code '2056' see also http://postgis.refractions.net/docs/AddGeometryColumn.html and http://postgis.refractions.net/docs/using_postgis_dbmanagement.html I would first try to still use the old way that works in both Postgis 1.5 and Postgis 2.0. Later we may decide to only support Postgis 2.0. Thanks a lot, PS: Denis, please correct me if I stated something wrong ... |
Dear Colleagues @3nids: Could you continue to check the statement, while A is on holidays? Thanks and I hope we can continue to progress. Greetings Merci für das Update. Nun habe ich noch die folgenden Probleme: 1. Kommentare in SQL sind://* ------------ Relationships and Value Tables ----------- *// sollte also zu ----------------------- Relationships and Value Tables ------------ werden.
CONSTRAINT pkey_qgep.vl_reach_point_outlet_shape_code Das kommt noch ziemlich häufig vor.
das 2. Argument ist Tabelle ohne Schema - das Schema ist ja schon im ersten Argument angegeben. Kommt auch ein paar mal vor.
müsste heissen: COMMENT ON COLUMN qgep.od_wastewater_node.situation_geometry IS 'national position coordinates (N,E) (decisive reference point for sewer network simulation) / Landeskoordinate Nord/Ost (massgebender Bezugspunkt für die Kanalnetzberechnung ) / Coordonnées nationales Est/Nord (Point de référence déterminant pour le calcu'; situation --> situation_geometry. Kommt auch mehrmals vor.
detail_geometry3d_geometry -> detail_geometry3d |
Comment on 8.1.2. Arbitrary Precision Numbers will be adapted in next release Adapted in metadatabase - will be correct in next release |
In table qgep.od_organisation we need to translate the columns
My proposal:
|
No description provided.
The text was updated successfully, but these errors were encountered: