-
Notifications
You must be signed in to change notification settings - Fork 19
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
Historique parcelle : mapping des codes / valeurs de filiation #192
Comments
MaelREBOUX
changed the title
Historique parcelle : mapping des code / valeurs de filiation
Historique parcelle : mapping des codes / valeurs de filiation
Jun 2, 2016
à coupler avec #189 |
PR --> 3liz/QgisCadastrePlugin#160 |
En mode crade : CREATE TABLE qgis3_master.filiation
(
filiation text NOT NULL,
filiation_lib text,
CONSTRAINT filiation_pkey PRIMARY KEY (filiation)
);
ALTER TABLE qgis3_master.filiation OWNER TO qgis;
INSERT INTO qgis3_master.filiation VALUES ('D','Division');
INSERT INTO qgis3_master.filiation VALUES ('R','Réunion');
INSERT INTO qgis3_master.filiation VALUES ('T','Transfert'); |
pierrejego
pushed a commit
that referenced
this issue
Nov 27, 2018
link to #192 and #189 After reading https://www.postgresql.org/docs/9.6/datatype-character.html I have put column as text. I wil probably do the same in other properties table
Modifications effectuées dans cadastrapp, ajout de la table + jointure sur les requêtes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
L'attribut parcelledetails.type_filiation contient des codes.
Le document de référence N_BAT12.pdf de la DGFiP indique p 4 :
Je propose donc :
Pas urgent : mettre en enhancement.
The text was updated successfully, but these errors were encountered: