Re: [Qgis-user] Updating a field set with default global variable on edit

[Karl Magnus Jönsson]

An option in the layer properties to save without username and password? Or a 
possibility to change database connection for a layer? To one connection with 
another user or a connection with no user stored. Could be useful. Though it is 
efficient to use an text editor to change it always feels a bit unsecure not 
using the GUI.

Karl-Magnus Jönsson 

-Ursprungligt meddelande-
Från: Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] För Fernando M. Roxo 
da Motta
Skickat: den 23 augusti 2017 02:28
Till: qgis-user@lists.osgeo.org
Ämne: Re: [Qgis-user] Updating a field set with default global variable on edit

On Tue, 22 Aug 2017 15:45:17 +0200, Casper Bertelsen  
wrote:


> Hi Ross,
> 
> If you make your project without saving username and password, the 
> project will prompt for a user and password when opened. Then each 
> member can login using their assigned login and thus making it 
> possible to use current_user in postgres.
> 
> To remove saved username and password from your current project file 
> (make a copy, beforehand), you can open it in a text editor and seach 
> for  untill you find
> 

  It seems to me that this can be useful for a lot of groups.   Could
this kind of save option be an interesting request for improvement?

  Slds.


> dbname='xx' host=yy port=5432 four lines above 
> and remove the username and password-part only .
> 
> 
> Mvh. / Best regards
> Casper Bertelsen
> 
> On 22/08/2017 15:36, McDonaldR wrote:
> >
> > Thanks Karl-Magnus
> >
> > We use triggers in the database already and they work perfectly but 
> > if we want to record the specific user creating and editing features 
> > then we’d have to create separate projects for each user.
> > At the moment the team of about 10 users all use a set of centrally 
> > stored project files – one for each different task.
> >
> > I found this post on Stackexchange
> > (https://gis.stackexchange.com/questions/217011/how-to-automatically
> > -update-wfs-edits-with-a-user-id) where global variables are used to 
> > populate fields when features are added.  However, as Matthias notes 
> > in the comments this doesn’t work on feature  “update”.  If this 
> > were possible then it would meet all our needs.  Maybe something 
> > that could be funded?
> >
> > Ross
> >
> > *From:*Karl Magnus Jönsson
> > [mailto:karl-magnus.jons...@kristianstad.se] *Sent:* 22 August 2017
> > 12:34 *To:* McDonaldR; qgis-user@lists.osgeo.org
> > *Subject:* SV: [Qgis-user] Updating a field set with default global 
> > variable on edit
> >
> > Hi!
> >
> > I’ve made the same things with triggers in the database. To avoid 
> > getting same username I’ve chosen not to save the username and 
> > password in the project. But then the user have to enter it every 
> > time the projects opens. If you can find a solution to your 
> > suggested approach it would be nice.
> >
> > *Karl-Magnus *
> >
> > *Från:*Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] *För 
> > *McDonaldR
> > *Skickat:* den 22 augusti 2017 13:12
> > *Till:* qgis-user@lists.osgeo.org 
> > *Ämne:* [Qgis-user] Updating a field set with default global 
> > variable on edit
> >
> > Hi List,
> >
> > Anyone know how to update a field that has a global variable set as 
> > the default value when records are edited (geometry and/or 
> > attributes)?
> >
> >
> > We have a QGIS project with a PostGIS layer loaded and configured 
> > with look-ups and relations so the users can update all the relevant 
> > fields. There are also "*created_by*" and "*updated_by*"
> > fields. These are updated by a trigger in the database with the 
> > "*current_user*" database variable. This works fine if you are the 
> > current user that added the layer to the project - the trigger works 
> > perfectly.
> >
> > If you give the project to someone else and they create and edit 
> > features in the layer the fields are still updated with your name as 
> > you are the person who added the layer to the project. Not what we 
> > want.
> >
> > QGIS has global variables and there are some new ones -
> > *user_account_name* and *user_full_name* that can be set as default 
> > values for the fields. When a new feature is created the field is 
> > populated with the correct name. Which is what we want.
> >
> > However, when we update an existing record we'd like the 
> > "*updated_by*" field to be updated with the current 
> > "*user_account_name*". Like a trigger in the database would do on 
> > update. Then we would have a better idea of the history of the 
> > feature.
> >
> > Ross
> >
> > *Ross McDonald | *GIS Data Coordinator | Angus Council, People, IT
> > | Angus House, Orchardbank Business Park, Sylvie Way, Forfar DD8 
> > | 1AT*|
> > t: 01307 476419*
> >
> > This message is strictly confidential. If you have received this in 
> > error, please inform the sender and remove it from your system. If 
> > received in error you may not copy, print, forward or use 

Re: [Qgis-user] Updating a field set with default global variable on edit

[Fernando M. Roxo da Motta]

On Tue, 22 Aug 2017 15:45:17 +0200, Casper Bertelsen
 wrote:


> Hi Ross,
> 
> If you make your project without saving username and password, the 
> project will prompt for a user and password when opened. Then each 
> member can login using their assigned login and thus making it
> possible to use current_user in postgres.
> 
> To remove saved username and password from your current project file 
> (make a copy, beforehand), you can open it in a text editor and seach 
> for  untill you find
> 

  It seems to me that this can be useful for a lot of groups.   Could
this kind of save option be an interesting request for improvement?

  Slds.


> dbname='xx' host=yy port=5432 four lines above 
> and remove the username and password-part only .
> 
> 
> Mvh. / Best regards
> Casper Bertelsen
> 
> On 22/08/2017 15:36, McDonaldR wrote:
> >
> > Thanks Karl-Magnus
> >
> > We use triggers in the database already and they work perfectly but
> > if we want to record the specific user creating and editing
> > features then we’d have to create separate projects for each user.
> > At the moment the team of about 10 users all use a set of centrally
> > stored project files – one for each different task.
> >
> > I found this post on Stackexchange 
> > (https://gis.stackexchange.com/questions/217011/how-to-automatically-update-wfs-edits-with-a-user-id)
> >  
> > where global variables are used to populate fields when features
> > are added.  However, as Matthias notes in the comments this doesn’t
> > work on feature  “update”.  If this were possible then it would
> > meet all our needs.  Maybe something that could be funded?
> >
> > Ross
> >
> > *From:*Karl Magnus Jönsson
> > [mailto:karl-magnus.jons...@kristianstad.se] *Sent:* 22 August 2017
> > 12:34 *To:* McDonaldR; qgis-user@lists.osgeo.org
> > *Subject:* SV: [Qgis-user] Updating a field set with default global 
> > variable on edit
> >
> > Hi!
> >
> > I’ve made the same things with triggers in the database. To avoid 
> > getting same username I’ve chosen not to save the username and 
> > password in the project. But then the user have to enter it every
> > time the projects opens. If you can find a solution to your
> > suggested approach it would be nice.
> >
> > *Karl-Magnus *
> >
> > *Från:*Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] *För 
> > *McDonaldR
> > *Skickat:* den 22 augusti 2017 13:12
> > *Till:* qgis-user@lists.osgeo.org 
> > *Ämne:* [Qgis-user] Updating a field set with default global
> > variable on edit
> >
> > Hi List,
> >
> > Anyone know how to update a field that has a global variable set as 
> > the default value when records are edited (geometry and/or
> > attributes)?
> >
> >
> > We have a QGIS project with a PostGIS layer loaded and configured
> > with look-ups and relations so the users can update all the
> > relevant fields. There are also "*created_by*" and "*updated_by*"
> > fields. These are updated by a trigger in the database with the
> > "*current_user*" database variable. This works fine if you are the
> > current user that added the layer to the project - the trigger
> > works perfectly.
> >
> > If you give the project to someone else and they create and edit 
> > features in the layer the fields are still updated with your name
> > as you are the person who added the layer to the project. Not what
> > we want.
> >
> > QGIS has global variables and there are some new ones - 
> > *user_account_name* and *user_full_name* that can be set as default 
> > values for the fields. When a new feature is created the field is 
> > populated with the correct name. Which is what we want.
> >
> > However, when we update an existing record we'd like the 
> > "*updated_by*" field to be updated with the current 
> > "*user_account_name*". Like a trigger in the database would do on 
> > update. Then we would have a better idea of the history of the
> > feature.
> >
> > Ross
> >
> > *Ross McDonald | *GIS Data Coordinator | Angus Council, People, IT
> > | Angus House, Orchardbank Business Park, Sylvie Way, Forfar DD8
> > | 1AT*| 
> > t: 01307 476419*
> >
> > This message is strictly confidential. If you have received this in 
> > error, please inform the sender and remove it from your system. If 
> > received in error you may not copy, print, forward or use it or any 
> > attachment in any way. This message is not capable of creating a
> > legal contract or a binding representation and does not represent
> > the views of Angus Council. Emails may be monitored for security
> > and network management reasons. Messages containing inappropriate
> > content may be intercepted. Angus Council does not accept any
> > liability for any harm that may be caused to the recipient system
> > or data on it by this message or any attachment.
> >
> > This message is strictly confidential. If you have received this in 
> > error, please inform the sender and remove it from your system. If 
> > received in 

Re: [Qgis-user] Updating a field set with default global variable on edit

[Lene Fischer]

Hi Casper,
So nice to see you answering questions at the QGIS user list.
Your knowledge is appreciated :)


Lene Fischer
Associate Professor

University of Copenhagen
Department of Geoscience and Natural Resource Management
Forest and Landscape College
Nødebovej 77a
3480 Fredensborg
Denmark


MOB +45 40115084
l...@ign.ku.dk


[cid:image001.gif@01D31B5F.195859E0]

[cid:image002.png@01D31B5F.195859E0]<@Lene_Fischer>



From: Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] On Behalf Of Casper 
Bertelsen
Sent: 22. august 2017 15:45
To: qgis-user@lists.osgeo.org
Subject: Re: [Qgis-user] Updating a field set with default global variable on 
edit

Hi Ross,

If you make your project without saving username and password, the project will 
prompt for a user and password when opened. Then each member can login using 
their assigned login and thus making it possible to use current_user in 
postgres.

To remove saved username and password from your current project file (make a 
copy, beforehand), you can open it in a text editor and seach for  
untill you find

dbname='xx' host=yy port=5432 four lines above  and 
remove the username and password-part only .

Mvh. / Best regards
Casper Bertelsen

On 22/08/2017 15:36, McDonaldR wrote:
Thanks Karl-Magnus

We use triggers in the database already and they work perfectly but if we want 
to record the specific user creating and editing features then we'd have to 
create separate projects for each user.  At the moment the team of about 10 
users all use a set of centrally stored project files - one for each different 
task.

I found this post on Stackexchange 
(https://gis.stackexchange.com/questions/217011/how-to-automatically-update-wfs-edits-with-a-user-id)
 where global variables are used to populate fields when features are added.  
However, as Matthias notes in the comments this doesn't work on feature  
"update".  If this were possible then it would meet all our needs.  Maybe 
something that could be funded?

Ross

From: Karl Magnus Jönsson [mailto:karl-magnus.jons...@kristianstad.se]
Sent: 22 August 2017 12:34
To: McDonaldR; qgis-user@lists.osgeo.org
Subject: SV: [Qgis-user] Updating a field set with default global variable on 
edit

Hi!
I've made the same things with triggers in the database. To avoid getting same 
username I've chosen not to save the username and password in the project. But 
then the user have to enter it every time the projects opens. If you can find a 
solution to your suggested approach it would be nice.

Karl-Magnus

Från: Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] För McDonaldR
Skickat: den 22 augusti 2017 13:12
Till: qgis-user@lists.osgeo.org
Ämne: [Qgis-user] Updating a field set with default global variable on edit

Hi List,

Anyone know how to update a field that has a global variable set as the default 
value when records are edited (geometry and/or attributes)?

We have a QGIS project with a PostGIS layer loaded and configured with look-ups 
and relations so the users can update all the relevant fields. There are also 
"created_by" and "updated_by" fields. These are updated by a trigger in the 
database with the "current_user" database variable. This works fine if you are 
the current user that added the layer to the project - the trigger works 
perfectly.

If you give the project to someone else and they create and edit features in 
the layer the fields are still updated with your name as you are the person who 
added the layer to the project. Not what we want.

QGIS has global variables and there are some new ones - user_account_name and 
user_full_name that can be set as default values for the fields. When a new 
feature is created the field is populated with the correct name. Which is what 
we want.

However, when we update an existing record we'd like the "updated_by" field to 
be updated with the current "user_account_name". Like a trigger in the database 
would do on update. Then we would have a better idea of the history of the 
feature.

Ross

Ross McDonald | GIS Data Coordinator | Angus Council, People, IT | Angus House, 
Orchardbank Business Park, Sylvie Way, Forfar DD8 1AT | t: 01307 476419


This message is strictly confidential. If you have received this in error, 
please inform the sender and remove it from your system. If received in error 
you may not copy, print, forward or use it or any attachment in any way. This 
message is not capable of creating a legal contract or a binding representation 
and does not represent the views of Angus Council. Emails may be monitored for 
security and network management reasons. Messages containing inappropriate 
content may be intercepted. Angus Council does not accept any liability for any 
harm that may be caused to the recipient system or data on it by this message 
or any attachment.

This message is strictly confidential. If you have received this in error, 
please inform 

Re: [Qgis-user] How to move 600 raster files -32000000m to x-direktion

[Andre Joost]

Am 22.08.2017 um 11:22 schrieb Richard McDonnell:

Hi,
This should be achievable using Warp, which can be found under *Raster,
Projections, Warp*.
Set your source SRS to EPSG: 25833, and your destination to EPSG: 4258



No, EPSG:4258 is in degrees.

Source CRS should be EPSG:25832 for zone 32N
+proj=utm +zone=32 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs

and EPSG:5652 as target CRS:
ETRS89 / UTM zone 32N (N-zE)
+proj=tmerc +lat_0=0 +lon_0=9 +k=0.9996 +x_0=3250 +y_0=0 
+ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs


HTH,
André Joost


___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Updating a field set with default global variable on edit

[Germán Carrillo]

Hi All,


to get field updates on vector layer edits (be they geometry or attribute
edits) you can use the AutoFields plugin [1]. You can use expressions just
like you do when setting default values in QGIS.


Regards,

Germán
---
[1]
http://geotux.tuxfamily.org/index.php/en/geo-blogs/item/333-autofields-plugin-for-qgis

2017-08-22 8:45 GMT-05:00 Casper Bertelsen :

> Hi Ross,
>
> If you make your project without saving username and password, the project
> will prompt for a user and password when opened. Then each member can login
> using their assigned login and thus making it possible to use current_user
> in postgres.
>
> To remove saved username and password from your current project file (make
> a copy, beforehand), you can open it in a text editor and seach for
>  untill you find
>
> dbname='xx' host=yy port=5432 four lines above 
> and remove the username and password-part only .
>
>
> Mvh. / Best regards
> Casper Bertelsen
>
> On 22/08/2017 15:36, McDonaldR wrote:
>
> Thanks Karl-Magnus
>
>
>
> We use triggers in the database already and they work perfectly but if we
> want to record the specific user creating and editing features then we’d
> have to create separate projects for each user.  At the moment the team of
> about 10 users all use a set of centrally stored project files – one for
> each different task.
>
>
>
> I found this post on Stackexchange (https://gis.stackexchange.
> com/questions/217011/how-to-automatically-update-wfs-edits-with-a-user-id)
> where global variables are used to populate fields when features are
> added.  However, as Matthias notes in the comments this doesn’t work on
> feature  “update”.  If this were possible then it would meet all our
> needs.  Maybe something that could be funded?
>
>
>
> Ross
>
>
>
> *From:* Karl Magnus Jönsson [mailto:karl-magnus.jons...@kristianstad.se
> ]
> *Sent:* 22 August 2017 12:34
> *To:* McDonaldR; qgis-user@lists.osgeo.org
> *Subject:* SV: [Qgis-user] Updating a field set with default global
> variable on edit
>
>
>
> Hi!
>
> I’ve made the same things with triggers in the database. To avoid getting
> same username I’ve chosen not to save the username and password in the
> project. But then the user have to enter it every time the projects opens.
> If you can find a solution to your suggested approach it would be nice.
>
>
>
> *Karl-Magnus *
>
>
>
> *Från:* Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org
> ] *För *McDonaldR
> *Skickat:* den 22 augusti 2017 13:12
> *Till:* qgis-user@lists.osgeo.org
> *Ämne:* [Qgis-user] Updating a field set with default global variable on
> edit
>
>
>
> Hi List,
>
>
>
> Anyone know how to update a field that has a global variable set as the
> default value when records are edited (geometry and/or attributes)?
>
>
> We have a QGIS project with a PostGIS layer loaded and configured with
> look-ups and relations so the users can update all the relevant fields.
> There are also "*created_by*" and "*updated_by*" fields. These are
> updated by a trigger in the database with the "*current_user*" database
> variable. This works fine if you are the current user that added the layer
> to the project - the trigger works perfectly.
>
> If you give the project to someone else and they create and edit features
> in the layer the fields are still updated with your name as you are the
> person who added the layer to the project. Not what we want.
>
> QGIS has global variables and there are some new ones -
> *user_account_name* and *user_full_name* that can be set as default
> values for the fields. When a new feature is created the field is populated
> with the correct name. Which is what we want.
>
> However, when we update an existing record we'd like the "*updated_by*"
> field to be updated with the current "*user_account_name*". Like a
> trigger in the database would do on update. Then we would have a better
> idea of the history of the feature.
>
>
>
> Ross
>
>
>
> *Ross McDonald | *GIS Data Coordinator | Angus Council, People, IT |
> Angus House, Orchardbank Business Park, Sylvie Way, Forfar DD8 1AT* | t:
> 01307 476419*
>
>
>
>
>
> This message is strictly confidential. If you have received this in error,
> please inform the sender and remove it from your system. If received in
> error you may not copy, print, forward or use it or any attachment in any
> way. This message is not capable of creating a legal contract or a binding
> representation and does not represent the views of Angus Council. Emails
> may be monitored for security and network management reasons. Messages
> containing inappropriate content may be intercepted. Angus Council does not
> accept any liability for any harm that may be caused to the recipient
> system or data on it by this message or any attachment.
>
>
> This message is strictly confidential. If you have received this in error,
> please inform the sender and remove it from your 

Re: [Qgis-user] Updating a field set with default global variable on edit

[McDonaldR]

I love this mailing list.  That is fantastic!

We're testing this out right now and it seems to be working exactly as we need 
it.

Thanks very much, Casper and Karl Magnus!

Ross

From: Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] On Behalf Of Casper 
Bertelsen
Sent: 22 August 2017 14:45
To: qgis-user@lists.osgeo.org
Subject: Re: [Qgis-user] Updating a field set with default global variable on 
edit

Hi Ross,

If you make your project without saving username and password, the project will 
prompt for a user and password when opened. Then each member can login using 
their assigned login and thus making it possible to use current_user in 
postgres.

To remove saved username and password from your current project file (make a 
copy, beforehand), you can open it in a text editor and seach for  
untill you find

dbname='xx' host=yy port=5432 four lines above  and 
remove the username and password-part only .

Mvh. / Best regards
Casper Bertelsen

On 22/08/2017 15:36, McDonaldR wrote:
Thanks Karl-Magnus

We use triggers in the database already and they work perfectly but if we want 
to record the specific user creating and editing features then we'd have to 
create separate projects for each user.  At the moment the team of about 10 
users all use a set of centrally stored project files - one for each different 
task.

I found this post on Stackexchange 
(https://gis.stackexchange.com/questions/217011/how-to-automatically-update-wfs-edits-with-a-user-id)
 where global variables are used to populate fields when features are added.  
However, as Matthias notes in the comments this doesn't work on feature  
"update".  If this were possible then it would meet all our needs.  Maybe 
something that could be funded?

Ross

From: Karl Magnus Jönsson [mailto:karl-magnus.jons...@kristianstad.se]
Sent: 22 August 2017 12:34
To: McDonaldR; qgis-user@lists.osgeo.org
Subject: SV: [Qgis-user] Updating a field set with default global variable on 
edit

Hi!
I've made the same things with triggers in the database. To avoid getting same 
username I've chosen not to save the username and password in the project. But 
then the user have to enter it every time the projects opens. If you can find a 
solution to your suggested approach it would be nice.

Karl-Magnus

Från: Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] För McDonaldR
Skickat: den 22 augusti 2017 13:12
Till: qgis-user@lists.osgeo.org
Ämne: [Qgis-user] Updating a field set with default global variable on edit

Hi List,

Anyone know how to update a field that has a global variable set as the default 
value when records are edited (geometry and/or attributes)?

We have a QGIS project with a PostGIS layer loaded and configured with look-ups 
and relations so the users can update all the relevant fields. There are also 
"created_by" and "updated_by" fields. These are updated by a trigger in the 
database with the "current_user" database variable. This works fine if you are 
the current user that added the layer to the project - the trigger works 
perfectly.

If you give the project to someone else and they create and edit features in 
the layer the fields are still updated with your name as you are the person who 
added the layer to the project. Not what we want.

QGIS has global variables and there are some new ones - user_account_name and 
user_full_name that can be set as default values for the fields. When a new 
feature is created the field is populated with the correct name. Which is what 
we want.

However, when we update an existing record we'd like the "updated_by" field to 
be updated with the current "user_account_name". Like a trigger in the database 
would do on update. Then we would have a better idea of the history of the 
feature.

Ross

Ross McDonald | GIS Data Coordinator | Angus Council, People, IT | Angus House, 
Orchardbank Business Park, Sylvie Way, Forfar DD8 1AT | t: 01307 476419


This message is strictly confidential. If you have received this in error, 
please inform the sender and remove it from your system. If received in error 
you may not copy, print, forward or use it or any attachment in any way. This 
message is not capable of creating a legal contract or a binding representation 
and does not represent the views of Angus Council. Emails may be monitored for 
security and network management reasons. Messages containing inappropriate 
content may be intercepted. Angus Council does not accept any liability for any 
harm that may be caused to the recipient system or data on it by this message 
or any attachment.

This message is strictly confidential. If you have received this in error, 
please inform the sender and remove it from your system. If received in error 
you may not copy, print, forward or use it or any attachment in any way. This 
message is not capable of creating a legal contract or a binding representation 
and does not represent the views of Angus 

Re: [Qgis-user] Updating a field set with default global variable on edit

[Casper Bertelsen]

Hi Ross,

If you make your project without saving username and password, the 
project will prompt for a user and password when opened. Then each 
member can login using their assigned login and thus making it possible 
to use current_user in postgres.


To remove saved username and password from your current project file 
(make a copy, beforehand), you can open it in a text editor and seach 
for  untill you find


dbname='xx' host=yy port=5432 four lines above 
and remove the username and password-part only .



Mvh. / Best regards
Casper Bertelsen

On 22/08/2017 15:36, McDonaldR wrote:


Thanks Karl-Magnus

We use triggers in the database already and they work perfectly but if 
we want to record the specific user creating and editing features then 
we’d have to create separate projects for each user.  At the moment 
the team of about 10 users all use a set of centrally stored project 
files – one for each different task.


I found this post on Stackexchange 
(https://gis.stackexchange.com/questions/217011/how-to-automatically-update-wfs-edits-with-a-user-id) 
where global variables are used to populate fields when features are 
added.  However, as Matthias notes in the comments this doesn’t work 
on feature  “update”.  If this were possible then it would meet all 
our needs.  Maybe something that could be funded?


Ross

*From:*Karl Magnus Jönsson [mailto:karl-magnus.jons...@kristianstad.se]
*Sent:* 22 August 2017 12:34
*To:* McDonaldR; qgis-user@lists.osgeo.org
*Subject:* SV: [Qgis-user] Updating a field set with default global 
variable on edit


Hi!

I’ve made the same things with triggers in the database. To avoid 
getting same username I’ve chosen not to save the username and 
password in the project. But then the user have to enter it every time 
the projects opens. If you can find a solution to your suggested 
approach it would be nice.


*Karl-Magnus *

*Från:*Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] *För 
*McDonaldR

*Skickat:* den 22 augusti 2017 13:12
*Till:* qgis-user@lists.osgeo.org 
*Ämne:* [Qgis-user] Updating a field set with default global variable 
on edit


Hi List,

Anyone know how to update a field that has a global variable set as 
the default value when records are edited (geometry and/or attributes)?



We have a QGIS project with a PostGIS layer loaded and configured with 
look-ups and relations so the users can update all the relevant 
fields. There are also "*created_by*" and "*updated_by*" fields. These 
are updated by a trigger in the database with the "*current_user*" 
database variable. This works fine if you are the current user that 
added the layer to the project - the trigger works perfectly.


If you give the project to someone else and they create and edit 
features in the layer the fields are still updated with your name as 
you are the person who added the layer to the project. Not what we want.


QGIS has global variables and there are some new ones - 
*user_account_name* and *user_full_name* that can be set as default 
values for the fields. When a new feature is created the field is 
populated with the correct name. Which is what we want.


However, when we update an existing record we'd like the 
"*updated_by*" field to be updated with the current 
"*user_account_name*". Like a trigger in the database would do on 
update. Then we would have a better idea of the history of the feature.


Ross

*Ross McDonald | *GIS Data Coordinator | Angus Council, People, IT | 
Angus House, Orchardbank Business Park, Sylvie Way, Forfar DD8 1AT*| 
t: 01307 476419*


This message is strictly confidential. If you have received this in 
error, please inform the sender and remove it from your system. If 
received in error you may not copy, print, forward or use it or any 
attachment in any way. This message is not capable of creating a legal 
contract or a binding representation and does not represent the views 
of Angus Council. Emails may be monitored for security and network 
management reasons. Messages containing inappropriate content may be 
intercepted. Angus Council does not accept any liability for any harm 
that may be caused to the recipient system or data on it by this 
message or any attachment.


This message is strictly confidential. If you have received this in 
error, please inform the sender and remove it from your system. If 
received in error you may not copy, print, forward or use it or any 
attachment in any way. This message is not capable of creating a legal 
contract or a binding representation and does not represent the views 
of Angus Council. Emails may be monitored for security and network 
management reasons.Messages containing inappropriate content may be 
intercepted. Angus Council does not accept any liability for any harm 
that may be caused to the recipient system or data on it by this 
message or any attachment.




___
Qgis-user mailing list

Re: [Qgis-user] Updating a field set with default global variable on edit

[McDonaldR]

Thanks Karl-Magnus

We use triggers in the database already and they work perfectly but if we want 
to record the specific user creating and editing features then we'd have to 
create separate projects for each user.  At the moment the team of about 10 
users all use a set of centrally stored project files - one for each different 
task.

I found this post on Stackexchange 
(https://gis.stackexchange.com/questions/217011/how-to-automatically-update-wfs-edits-with-a-user-id)
 where global variables are used to populate fields when features are added.  
However, as Matthias notes in the comments this doesn't work on feature  
"update".  If this were possible then it would meet all our needs.  Maybe 
something that could be funded?

Ross

From: Karl Magnus Jönsson [mailto:karl-magnus.jons...@kristianstad.se]
Sent: 22 August 2017 12:34
To: McDonaldR; qgis-user@lists.osgeo.org
Subject: SV: [Qgis-user] Updating a field set with default global variable on 
edit

Hi!
I've made the same things with triggers in the database. To avoid getting same 
username I've chosen not to save the username and password in the project. But 
then the user have to enter it every time the projects opens. If you can find a 
solution to your suggested approach it would be nice.

Karl-Magnus

Från: Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] För McDonaldR
Skickat: den 22 augusti 2017 13:12
Till: qgis-user@lists.osgeo.org
Ämne: [Qgis-user] Updating a field set with default global variable on edit

Hi List,

Anyone know how to update a field that has a global variable set as the default 
value when records are edited (geometry and/or attributes)?

We have a QGIS project with a PostGIS layer loaded and configured with look-ups 
and relations so the users can update all the relevant fields. There are also 
"created_by" and "updated_by" fields. These are updated by a trigger in the 
database with the "current_user" database variable. This works fine if you are 
the current user that added the layer to the project - the trigger works 
perfectly.

If you give the project to someone else and they create and edit features in 
the layer the fields are still updated with your name as you are the person who 
added the layer to the project. Not what we want.

QGIS has global variables and there are some new ones - user_account_name and 
user_full_name that can be set as default values for the fields. When a new 
feature is created the field is populated with the correct name. Which is what 
we want.

However, when we update an existing record we'd like the "updated_by" field to 
be updated with the current "user_account_name". Like a trigger in the database 
would do on update. Then we would have a better idea of the history of the 
feature.

Ross

Ross McDonald | GIS Data Coordinator | Angus Council, People, IT | Angus House, 
Orchardbank Business Park, Sylvie Way, Forfar DD8 1AT | t: 01307 476419


This message is strictly confidential. If you have received this in error, 
please inform the sender and remove it from your system. If received in error 
you may not copy, print, forward or use it or any attachment in any way. This 
message is not capable of creating a legal contract or a binding representation 
and does not represent the views of Angus Council. Emails may be monitored for 
security and network management reasons. Messages containing inappropriate 
content may be intercepted. Angus Council does not accept any liability for any 
harm that may be caused to the recipient system or data on it by this message 
or any attachment.

This message is strictly confidential. If you have received this in error, 
please inform the sender and remove it from your system. If received in error 
you may not copy, print, forward or use it or any attachment in any way. This 
message is not capable of creating a legal contract or a binding representation 
and does not represent the views of Angus Council. Emails may be monitored for 
security and network management reasons. Messages containing inappropriate 
content may be intercepted. Angus Council does not accept any liability for any 
harm that may be caused to the recipient system or data on it by this message 
or any attachment.
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] still seeing "globeplugin.dll....... could not be found" errors

[Chuck Yahrling]

I have been seeing this error in the Plugins tab of error console
consistently. I have installed 2.18.11 QGIS 32 1.and QGIS 64 on an updated
windows 7 machine.  Also just installed  QGIS 64 2.18.12 on the same win7
machine and on a different win pro 10/64 machine.  I checked and
globeplugin.dll does indeed reside in the system path listed, despite this
error:

"Failed to load C:/PROGRA~1/QGIS2~1.18/apps/qgis/plugins/globeplugin.dll
(Reason: Cannot load library
C:/PROGRA~1/QGIS2~1.18/apps/qgis/plugins/globeplugin.dll: The specified
module could not be found.)"

So some questions:

1.  What does globeplugin.dll  do, and is it part of QGIS or part of Google
Earth. Google Maps, etc as one search result suggested?

2. Do I need to fix this, and if so, what remedies do you suggest?

3. Does this have anything to do with the ~ characters listed in the path?

tnx in advance,  chuck



-- 
73, chuck

ab1vl.com
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Updating a field set with default global variable on edit

[Karl Magnus Jönsson]

No, it's no big deal. That's why we are using it. And it's only one time per 
qgis session.

Karl-Magnus

Från: Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] För Casper Bertelsen
Skickat: den 22 augusti 2017 14:34
Till: qgis-user@lists.osgeo.org
Ämne: Re: [Qgis-user] Updating a field set with default global variable on edit

Hi too,

Well logging into the QGIS-project should really be a big deal right ? - You 
only have to log in once no matter how many layers are loaded from the 
database. I have a table inside my QGIS project where I can create new users 
inside the database and administer reading/writing/admin-privileges.

Mvh. / Best regards
Casper Bertelsen

On 22/08/2017 13:34, Karl Magnus Jönsson wrote:
Hi!
I've made the same things with triggers in the database. To avoid getting same 
username I've chosen not to save the username and password in the project. But 
then the user have to enter it every time the projects opens. If you can find a 
solution to your suggested approach it would be nice.

Karl-Magnus

Från: Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] För McDonaldR
Skickat: den 22 augusti 2017 13:12
Till: qgis-user@lists.osgeo.org
Ämne: [Qgis-user] Updating a field set with default global variable on edit

Hi List,

Anyone know how to update a field that has a global variable set as the default 
value when records are edited (geometry and/or attributes)?

We have a QGIS project with a PostGIS layer loaded and configured with look-ups 
and relations so the users can update all the relevant fields. There are also 
"created_by" and "updated_by" fields. These are updated by a trigger in the 
database with the "current_user" database variable. This works fine if you are 
the current user that added the layer to the project - the trigger works 
perfectly.

If you give the project to someone else and they create and edit features in 
the layer the fields are still updated with your name as you are the person who 
added the layer to the project. Not what we want.

QGIS has global variables and there are some new ones - user_account_name and 
user_full_name that can be set as default values for the fields. When a new 
feature is created the field is populated with the correct name. Which is what 
we want.

However, when we update an existing record we'd like the "updated_by" field to 
be updated with the current "user_account_name". Like a trigger in the database 
would do on update. Then we would have a better idea of the history of the 
feature.

Ross

Ross McDonald | GIS Data Coordinator | Angus Council, People, IT | Angus House, 
Orchardbank Business Park, Sylvie Way, Forfar DD8 1AT | t: 01307 476419


This message is strictly confidential. If you have received this in error, 
please inform the sender and remove it from your system. If received in error 
you may not copy, print, forward or use it or any attachment in any way. This 
message is not capable of creating a legal contract or a binding representation 
and does not represent the views of Angus Council. Emails may be monitored for 
security and network management reasons. Messages containing inappropriate 
content may be intercepted. Angus Council does not accept any liability for any 
harm that may be caused to the recipient system or data on it by this message 
or any attachment.




___

Qgis-user mailing list

Qgis-user@lists.osgeo.org

List info: https://lists.osgeo.org/mailman/listinfo/qgis-user

Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Updating a field set with default global variable on edit

[Casper Bertelsen]

Hi too,

Well logging into the QGIS-project should really be a big deal right ? - 
You only have to log in once no matter how many layers are loaded from 
the database. I have a table inside my QGIS project where I can create 
new users inside the database and administer 
reading/writing/admin-privileges.


Mvh. / Best regards
Casper Bertelsen

On 22/08/2017 13:34, Karl Magnus Jönsson wrote:


Hi!

I’ve made the same things with triggers in the database. To avoid 
getting same username I’ve chosen not to save the username and 
password in the project. But then the user have to enter it every time 
the projects opens. If you can find a solution to your suggested 
approach it would be nice.


*Karl-Magnus *

*Från:*Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] *För 
*McDonaldR

*Skickat:* den 22 augusti 2017 13:12
*Till:* qgis-user@lists.osgeo.org
*Ämne:* [Qgis-user] Updating a field set with default global variable 
on edit


Hi List,

Anyone know how to update a field that has a global variable set as 
the default value when records are edited (geometry and/or attributes)?



We have a QGIS project with a PostGIS layer loaded and configured with 
look-ups and relations so the users can update all the relevant 
fields. There are also "*created_by*" and "*updated_by*" fields. These 
are updated by a trigger in the database with the "*current_user*" 
database variable. This works fine if you are the current user that 
added the layer to the project - the trigger works perfectly.


If you give the project to someone else and they create and edit 
features in the layer the fields are still updated with your name as 
you are the person who added the layer to the project. Not what we want.


QGIS has global variables and there are some new ones - 
*user_account_name* and *user_full_name* that can be set as default 
values for the fields. When a new feature is created the field is 
populated with the correct name. Which is what we want.


However, when we update an existing record we'd like the 
"*updated_by*" field to be updated with the current 
"*user_account_name*". Like a trigger in the database would do on 
update. Then we would have a better idea of the history of the feature.


Ross

*Ross McDonald | *GIS Data Coordinator | Angus Council, People, IT | 
Angus House, Orchardbank Business Park, Sylvie Way, Forfar DD8 1AT*| 
t: 01307 476419*


This message is strictly confidential. If you have received this in 
error, please inform the sender and remove it from your system. If 
received in error you may not copy, print, forward or use it or any 
attachment in any way. This message is not capable of creating a legal 
contract or a binding representation and does not represent the views 
of Angus Council. Emails may be monitored for security and network 
management reasons. Messages containing inappropriate content may be 
intercepted. Angus Council does not accept any liability for any harm 
that may be caused to the recipient system or data on it by this 
message or any attachment.




___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Updating a field set with default global variable on edit

[Karl Magnus Jönsson]

Hi!
I've made the same things with triggers in the database. To avoid getting same 
username I've chosen not to save the username and password in the project. But 
then the user have to enter it every time the projects opens. If you can find a 
solution to your suggested approach it would be nice.

Karl-Magnus

Från: Qgis-user [mailto:qgis-user-boun...@lists.osgeo.org] För McDonaldR
Skickat: den 22 augusti 2017 13:12
Till: qgis-user@lists.osgeo.org
Ämne: [Qgis-user] Updating a field set with default global variable on edit

Hi List,

Anyone know how to update a field that has a global variable set as the default 
value when records are edited (geometry and/or attributes)?

We have a QGIS project with a PostGIS layer loaded and configured with look-ups 
and relations so the users can update all the relevant fields. There are also 
"created_by" and "updated_by" fields. These are updated by a trigger in the 
database with the "current_user" database variable. This works fine if you are 
the current user that added the layer to the project - the trigger works 
perfectly.

If you give the project to someone else and they create and edit features in 
the layer the fields are still updated with your name as you are the person who 
added the layer to the project. Not what we want.

QGIS has global variables and there are some new ones - user_account_name and 
user_full_name that can be set as default values for the fields. When a new 
feature is created the field is populated with the correct name. Which is what 
we want.

However, when we update an existing record we'd like the "updated_by" field to 
be updated with the current "user_account_name". Like a trigger in the database 
would do on update. Then we would have a better idea of the history of the 
feature.

Ross

Ross McDonald | GIS Data Coordinator | Angus Council, People, IT | Angus House, 
Orchardbank Business Park, Sylvie Way, Forfar DD8 1AT | t: 01307 476419


This message is strictly confidential. If you have received this in error, 
please inform the sender and remove it from your system. If received in error 
you may not copy, print, forward or use it or any attachment in any way. This 
message is not capable of creating a legal contract or a binding representation 
and does not represent the views of Angus Council. Emails may be monitored for 
security and network management reasons. Messages containing inappropriate 
content may be intercepted. Angus Council does not accept any liability for any 
harm that may be caused to the recipient system or data on it by this message 
or any attachment.
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] Updating a field set with default global variable on edit

[McDonaldR]

Hi List,

Anyone know how to update a field that has a global variable set as the default 
value when records are edited (geometry and/or attributes)?

We have a QGIS project with a PostGIS layer loaded and configured with look-ups 
and relations so the users can update all the relevant fields. There are also 
"created_by" and "updated_by" fields. These are updated by a trigger in the 
database with the "current_user" database variable. This works fine if you are 
the current user that added the layer to the project - the trigger works 
perfectly.

If you give the project to someone else and they create and edit features in 
the layer the fields are still updated with your name as you are the person who 
added the layer to the project. Not what we want.

QGIS has global variables and there are some new ones - user_account_name and 
user_full_name that can be set as default values for the fields. When a new 
feature is created the field is populated with the correct name. Which is what 
we want.

However, when we update an existing record we'd like the "updated_by" field to 
be updated with the current "user_account_name". Like a trigger in the database 
would do on update. Then we would have a better idea of the history of the 
feature.

Ross

Ross McDonald | GIS Data Coordinator | Angus Council, People, IT | Angus House, 
Orchardbank Business Park, Sylvie Way, Forfar DD8 1AT | t: 01307 476419


This message is strictly confidential. If you have received this in error, 
please inform the sender and remove it from your system. If received in error 
you may not copy, print, forward or use it or any attachment in any way. This 
message is not capable of creating a legal contract or a binding representation 
and does not represent the views of Angus Council. Emails may be monitored for 
security and network management reasons. Messages containing inappropriate 
content may be intercepted. Angus Council does not accept any liability for any 
harm that may be caused to the recipient system or data on it by this message 
or any attachment.
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] How to move 600 raster files -32000000m to x-direktion

[Richard McDonnell]

Hi,
This should be achievable using Warp, which can be found under *Raster, 
Projections, Warp*.

Set your source SRS to EPSG: 25833, and your destination to EPSG: 4258

Hope this helps.
Regards,

Richard.


On 22/08/2017 08:33, Bernd Laskowski wrote:

Hi all,

i have to change 600 .tfw files from .tif Raster files
source: etrs89 zone 32
destination: etrs89 without zone 32.

For example:
from
   0.31746032
   0.
   0.
  -0.31746032
32408500.1587
5650999.8413
to
   0.31746032
   0.
   0.
  -0.31746032
408500.1587
5650999.8413

Does anyone know how to do that in an efficient way (the same to geotif)?


Regards
Bernd

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user


--
*_Richard McDonnell_*
*GIS Specialist PgD GIS AssocSCSI*
*OPW FRM Data Management*
*52 Stephens Green, Dublin 2.*
TEL: 01 6476543

OPW - Ag féachaint don am atá le teacht - Ag caomhnú ón am atá thart
OPW - Looking to the future - Caring for the past

***
Email Disclaimer: http://www.opw.ie/en/disclaimer/

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Maximum wfs layers in qgis?

[Richard McDonnell]

Hi,
If you also switch off the Cache for the WFS on QGIS. You can do this 
when you add the Layer, just uncheck the *Cache Feature* box for the 
layer you are trying to load.

Hope this helps!

Regards,

Richard.

On 21/08/2017 19:55, Dan Meerschaert wrote:
When I look in the cache/wfsprovider folder, there's another folder 
with almost three times the layer number in other files: 
wfs_cache_XX.sqlite, -shm, and -wal.


I had to track down a public wfs with a small enough sample set to be 
repeatable. This Python code gives the error in 2.18.7 and a 2.99 
nightly I grabbed for testing:


iface.addVectorLayer(' restrictToRequestBBOX=\'1\' 
srsname=\'EPSG:4326\' typename=\'sdr:nyu_2451_34490\' 
url=\'https://maps-public.geo.nyu.edu/geoserver/sdr/wfs\ 
' 
version=\'auto\' table="" sql=',"example01","WFS")


iface.addVectorLayer(' restrictToRequestBBOX=\'1\' 
srsname=\'EPSG:4326\' typename=\'sdr:nyu_2451_34490\' 
url=\'https://maps-public.geo.nyu.edu/geoserver/sdr/wfs\ 
' 
version=\'auto\' table="" sql=',"example02","WFS")


iface.addVectorLayer(' restrictToRequestBBOX=\'1\' 
srsname=\'EPSG:4326\' typename=\'sdr:nyu_2451_34490\' 
url=\'https://maps-public.geo.nyu.edu/geoserver/sdr/wfs\ 
' 
version=\'auto\' table="" sql=',"example03","WFS")


iface.addVectorLayer(' restrictToRequestBBOX=\'1\' 
srsname=\'EPSG:4326\' typename=\'sdr:nyu_2451_34490\' 
url=\'https://maps-public.geo.nyu.edu/geoserver/sdr/wfs\ 
' 
version=\'auto\' table="" sql=',"example04","WFS")


iface.addVectorLayer(' restrictToRequestBBOX=\'1\' 
srsname=\'EPSG:4326\' typename=\'sdr:nyu_2451_34490\' 
url=\'https://maps-public.geo.nyu.edu/geoserver/sdr/wfs\ 
' 
version=\'auto\' table="" sql=',"example05","WFS")


iface.addVectorLayer(' restrictToRequestBBOX=\'1\' 
srsname=\'EPSG:4326\' typename=\'sdr:nyu_2451_34490\' 
url=\'https://maps-public.geo.nyu.edu/geoserver/sdr/wfs\ 
' 
version=\'auto\' table="" sql=',"example06","WFS")


iface.addVectorLayer(' restrictToRequestBBOX=\'1\' 
srsname=\'EPSG:4326\' typename=\'sdr:nyu_2451_34490\' 
url=\'https://maps-public.geo.nyu.edu/geoserver/sdr/wfs\ 
' 
version=\'auto\' table="" sql=',"example07","WFS")


iface.addVectorLayer(' restrictToRequestBBOX=\'1\' 
srsname=\'EPSG:4326\' typename=\'sdr:nyu_2451_34490\' 
url=\'https://maps-public.geo.nyu.edu/geoserver/sdr/wfs\ 
' 
version=\'auto\' table="" sql=',"example08","WFS")


iface.addVectorLayer(' restrictToRequestBBOX=\'1\' 
srsname=\'EPSG:4326\' typename=\'sdr:nyu_2451_34490\' 
url=\'https://maps-public.geo.nyu.edu/geoserver/sdr/wfs\ 
' 
version=\'auto\' table="" sql=',"example09","WFS")


iface.addVectorLayer(' restrictToRequestBBOX=\'1\' 
srsname=\'EPSG:4326\' typename=\'sdr:nyu_2451_34490\' 
url=\'https://maps-public.geo.nyu.edu/geoserver/sdr/wfs\ 
' 
version=\'auto\' table="" sql=',"example00","WFS")


iface.addVectorLayer(' restrictToRequestBBOX=\'1\' 
srsname=\'EPSG:4326\' typename=\'sdr:nyu_2451_34490\' 
url=\'https://maps-public.geo.nyu.edu/geoserver/sdr/wfs\ 
' 
version=\'auto\' table="" sql=',"example11","WFS")


iface.addVectorLayer(' restrictToRequestBBOX=\'1\' 
srsname=\'EPSG:4326\' typename=\'sdr:nyu_2451_34490\' 
url=\'https://maps-public.geo.nyu.edu/geoserver/sdr/wfs\ 
' 
version=\'auto\' table="" sql=',"example12","WFS")


iface.addVectorLayer(' restrictToRequestBBOX=\'1\' 
srsname=\'EPSG:4326\' typename=\'sdr:nyu_2451_34490\' 
url=\'https://maps-public.geo.nyu.edu/geoserver/sdr/wfs\ 
' 
version=\'auto\' table="" sql=',"example13","WFS")


iface.addVectorLayer(' restrictToRequestBBOX=\'1\' 
srsname=\'EPSG:4326\' typename=\'sdr:nyu_2451_34490\' 
url=\'https://maps-public.geo.nyu.edu/geoserver/sdr/wfs\ 
' 
version=\'auto\' table="" sql=',"example14","WFS")


iface.addVectorLayer(' restrictToRequestBBOX=\'1\' 
srsname=\'EPSG:4326\' typename=\'sdr:nyu_2451_34490\' 
url=\'https://maps-public.geo.nyu.edu/geoserver/sdr/wfs\ 
' 
version=\'auto\' table="" sql=',"example15","WFS")


iface.addVectorLayer(' restrictToRequestBBOX=\'1\' 
srsname=\'EPSG:4326\' typename=\'sdr:nyu_2451_34490\' 
url=\'https://maps-public.geo.nyu.edu/geoserver/sdr/wfs\ 
' 
version=\'auto\' table="" sql=',"example16","WFS")

[Qgis-user] How to move 600 raster files -32000000m to x-direktion

[Bernd Laskowski]

Hi all,

i have to change 600 .tfw files from .tif Raster files
source: etrs89 zone 32
destination: etrs89 without zone 32.

For example:
from
   0.31746032
   0.
   0.
  -0.31746032
32408500.1587
5650999.8413
to
   0.31746032
   0.
   0.
  -0.31746032
408500.1587
5650999.8413

Does anyone know how to do that in an efficient way (the same to geotif)?


Regards
Bernd

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user