Select crs

[myarjunar]

issue #27 #6

we will check whether the selected db has cogo scheme in it. If it doesn't have the schema then we will give an option to set one.

[myarjunar]

could you test this PR is it works as you expecting?? @NyakudyaA

[NyakudyaA]

Ok I am on it now.

[myarjunar]

@NyakudyaA sorry, I've just made a patch for this PR, you can pull it again. Thanks!

[NyakudyaA]

ok. But just to be sure how does the selected CRS affect the database operations

[myarjunar]

ok. But just to be sure how does the selected CRS affect the database operations

@NyakudyaA here, we will set the crs to the selected crs as soon as the layers are added by the plugin to the canvas.

[NyakudyaA]

Ok. That's fine. We assume that the user selects a CRS that corresponds to his database in the backend. Later we might need to add rules to check what database CRS has already been assigned to a table and compare this with the selected CRS so that a user can not select a CRS that is not the same as his database

[NyakudyaA]

I get the error message

[myarjunar]

@NyakudyaA my bad, I just made another patch for that.

Sent from my LGE Nexus 5 using FastHub

[NyakudyaA]

So from an earlier discussion with Gavin, the select CRS need to obey the following rules.

• After choosing/defining a database connection we need to check if the plugin layers exist in the database.

• Create another button that checks the database for plugin layers.

You could run a sql statement like
SELECT EXISTS (SELECT 1 AS result FROM pg_tables WHERE schemaname = 'public' AND tablename = 'beacons') This should return true if layers exist and false if it does not exist.

If the query return true for all the layers then we proceed to load them from the database.

• If plugin layers do not exist then the drop down for selecting a CRS becomes active and a user selects a CRS from the list. The CRS text should explain that selecting this CRS will mean it gets used in the database creation.

• Now a user should be able to click Setup database This will create the appropriate tables using the database ddl script in the database.

• Create another tab for help and we will populate it will the appropriate text

[myarjunar]

@NyakudyaA could you test this again for me?

[NyakudyaA]

I have tested it and it's doing the expected behavior. The only problem is that the CRS substitution is not happening properly. If I look at the function I see that the CRS is defined as 32632 for UTM 32N instead of 26332. Can you also change the text here?

The text should be The selected database does not contain tables and functions required for use of the plugin. Please select a CRS and click OK to proceed setting up a database using the chosen CRS.