Re: [Qgis-user] bug in 3.10.2 (after upgrading from 3.10.1) with NULL being lost in PostGIS
It works great. I'll just roll back to the standalone 3.10.1 until they are in the next version. Thanks :) *Jason* On Tue, Feb 4, 2020 at 1:36 PM Alessandro Pasotti wrote: > Hi Jason, > > the quickest way to test current master for your case is to unzip the > latest build artifact for windows 64bits (it's a zip inside a zip) on your > PC and launch the qgis.exe binary you find inside. > No installation is required and it's completely standalone, there is no > Python but you don't need it for your test case. > > On every commit the artifact is automatically built: > https://github.com/qgis/QGIS/actions?query=workflow%3A%22Windows+cross+build+with+MXE%22 > > The patches are very recent and they will be backported to 3.10 but I'll > do that later this week. > > Let me know how it goes. > > > On Tue, Feb 4, 2020 at 8:47 PM Jason Carlson > wrote: > >> Hi Alessandro, >> >> Thanks for your response. >> >> I've only used the standalone installers so it took me a bit to figure >> out how to start QGIS when using the OSGeo4W installer. My standalone was >> version 3.10.2-0 and in the OSGeo4W installer I see a 3.10.2-2 as well as >> the development version of 3.11.0-72. >> >> Wasn't sure which one you meant. If you meant the 3.11.0-72 then the >> issue is gone. If you had meant the 3.10.2-2 branch then it is still there >> but I discovered more stuff that may help but won't explain until I confirm >> the version I was to test against. >> >> Jason >> >> On Tue, Feb 4, 2020 at 9:05 AM Alessandro Pasotti >> wrote: >> >>> >>> >>> On Tue, Feb 4, 2020 at 5:02 PM Jason Carlson >>> wrote: >>> >>>> Can anyone else confirm this before I submit it? >>>> >>> >>> >>> Can you please check latest master builds first? I've done a couple of >>> fixes in the past few days that might have an impact on this issue. >>> >>> If the issue is still there, please file a ticket and attach a small SQL >>> dump and a QGS project to reproduce the issue. >>> >>> >>> >>> >>> >>>> After I upgraded from 3.10.1 to 3.10.2 I noticed an issue that it no >>>> longer handles null values correctly when updating records in PostGIS. >>>> >>>> I rolled back to version 3.10.1 and the issue goes away. >>>> >>>> Here is more detail: >>>> I have some PostgreSQL tables that have fields that can be NULL or text >>>> but I have check constraint in place saying it has to be NULL or one of a >>>> list of specific strings. >>>> >>>> In 3.10.1 if I go to edit a record that has some fields set as NULL, >>>> when the QGIS attribute form loads for editing, it shows those fields as >>>> NULL inside the text field (they can be text or null). I can make changes >>>> to any fields and save and the NULL fields remain as NULL. >>>> >>>> In 3.10.2 if I go to edit the same record, the QGIS attribute form when >>>> displayed for editing the record does not show those fields as being NULL >>>> but an empty string. When I submit changes, any fields that should still be >>>> NULL are not being submitted as NULL as I get a check constraint error >>>> saying it doesn't fit the criteria. I've tried entering into those fields >>>> manually as NULL or 'NULL' or "NULL" and a dozen or so other guesses and it >>>> still fails. >>>> >>>> Again, if I roll back to version 3.10.1 it works as it has on many >>>> previous versions all the way back to 2.8 >>>> ___ >>>> 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 >>> >>> >>> >>> -- >>> Alessandro Pasotti >>> w3: www.itopen.it >>> >> > > -- > Alessandro Pasotti > w3: www.itopen.it > ___ 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] bug in 3.10.2 (after upgrading from 3.10.1) with NULL being lost in PostGIS
Hi Alessandro, Thanks for your response. I've only used the standalone installers so it took me a bit to figure out how to start QGIS when using the OSGeo4W installer. My standalone was version 3.10.2-0 and in the OSGeo4W installer I see a 3.10.2-2 as well as the development version of 3.11.0-72. Wasn't sure which one you meant. If you meant the 3.11.0-72 then the issue is gone. If you had meant the 3.10.2-2 branch then it is still there but I discovered more stuff that may help but won't explain until I confirm the version I was to test against. Jason On Tue, Feb 4, 2020 at 9:05 AM Alessandro Pasotti wrote: > > > On Tue, Feb 4, 2020 at 5:02 PM Jason Carlson > wrote: > >> Can anyone else confirm this before I submit it? >> > > > Can you please check latest master builds first? I've done a couple of > fixes in the past few days that might have an impact on this issue. > > If the issue is still there, please file a ticket and attach a small SQL > dump and a QGS project to reproduce the issue. > > > > > >> After I upgraded from 3.10.1 to 3.10.2 I noticed an issue that it no >> longer handles null values correctly when updating records in PostGIS. >> >> I rolled back to version 3.10.1 and the issue goes away. >> >> Here is more detail: >> I have some PostgreSQL tables that have fields that can be NULL or text >> but I have check constraint in place saying it has to be NULL or one of a >> list of specific strings. >> >> In 3.10.1 if I go to edit a record that has some fields set as NULL, when >> the QGIS attribute form loads for editing, it shows those fields as NULL >> inside the text field (they can be text or null). I can make changes to any >> fields and save and the NULL fields remain as NULL. >> >> In 3.10.2 if I go to edit the same record, the QGIS attribute form when >> displayed for editing the record does not show those fields as being NULL >> but an empty string. When I submit changes, any fields that should still be >> NULL are not being submitted as NULL as I get a check constraint error >> saying it doesn't fit the criteria. I've tried entering into those fields >> manually as NULL or 'NULL' or "NULL" and a dozen or so other guesses and it >> still fails. >> >> Again, if I roll back to version 3.10.1 it works as it has on many >> previous versions all the way back to 2.8 >> ___ >> 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 > > > > -- > Alessandro Pasotti > w3: www.itopen.it > ___ 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] bug in 3.10.2 (after upgrading from 3.10.1) with NULL being lost in PostGIS
Can anyone else confirm this before I submit it? After I upgraded from 3.10.1 to 3.10.2 I noticed an issue that it no longer handles null values correctly when updating records in PostGIS. I rolled back to version 3.10.1 and the issue goes away. Here is more detail: I have some PostgreSQL tables that have fields that can be NULL or text but I have check constraint in place saying it has to be NULL or one of a list of specific strings. In 3.10.1 if I go to edit a record that has some fields set as NULL, when the QGIS attribute form loads for editing, it shows those fields as NULL inside the text field (they can be text or null). I can make changes to any fields and save and the NULL fields remain as NULL. In 3.10.2 if I go to edit the same record, the QGIS attribute form when displayed for editing the record does not show those fields as being NULL but an empty string. When I submit changes, any fields that should still be NULL are not being submitted as NULL as I get a check constraint error saying it doesn't fit the criteria. I've tried entering into those fields manually as NULL or 'NULL' or "NULL" and a dozen or so other guesses and it still fails. Again, if I roll back to version 3.10.1 it works as it has on many previous versions all the way back to 2.8 ___ 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] PostGIS- erroneous query : Unable to get list of tables from DB
The error message would still suggest it is an access problem to the
topology table. Perhaps you need to take it a step further with your
postgres version and grant select to the user.
Not at my computer now but try something along the lines of:
GRANT SELECT ON topology TO username;
On Mon., Nov. 18, 2019, 5:10 p.m. Laurence Béchet, <
bechet.laure...@gmail.com> wrote:
> Thank you Jason for your answer.
> I've granted usage on schema topology to my user -> same problem. I even
> granted PUBLIC.
>
> There is something 'wrong' with the passed request itself as it fails in
> pgadmin as well (see it below).
>
> I have a very basic test.qgz file. I launch it with 3.4.13 (I've updated
> all my qgis versions), open the browser, connect to my db and see the
> tables. Same file, launched with 3.10.0, open browser, connect to my db
> (same profile so I guess same qgis-auth.db file I suppose) and get the
> 'failed to get layers' as described in the bug. I can see the sql request
> which failed and that one doesn't work either in pg_admin. Unfortunately
> the sql request passed with 3.4.13 is not displayed.
>
> SELECT
> l.f_table_name,l.f_table_schema,l.f_geometry_column,upper(l.type),l.srid,l.coord_dimension,c.relkind,obj_description(c.oid),array_agg(a.attname),
> count(CASE WHEN t.typname IN
> ('geometry','geography','topogeometry','raster') THEN 1 ELSE NULL END) , 1
> FROM geometry_columns l,pg_class c,pg_namespace n,pg_attribute a,pg_type t
> WHERE c.relname=l.f_table_name AND l.f_table_schema=n.nspname AND NOT
> a.attisdropped AND a.attrelid=c.oid AND a.atttypid=t.oid AND a.attnum>0 AND
> n.oid=c.relnamespace AND has_schema_privilege(n.nspname,'usage') AND
> has_table_privilege('"'||n.nspname||'"."'||c.relname||'"','select') GROUP
> BY 1,2,3,4,5,6,7,c.oid,11 UNION SELECT
> l.f_table_name,l.f_table_schema,l.f_geography_column,upper(l.type),l.srid,2,c.relkind,obj_description(c.oid),array_agg(a.attname),
> count(CASE WHEN t.typname IN
> ('geometry','geography','topogeometry','raster') THEN 1 ELSE NULL END) , 1
> FROM geography_columns l,pg_class c,pg_namespace n,pg_attribute a,pg_type t
> WHERE c.relname=l.f_table_name AND l.f_table_schema=n.nspname AND NOT
> a.attisdropped AND a.attrelid=c.oid AND a.atttypid=t.oid AND a.attnum>0 AND
> n.oid=c.relnamespace AND has_schema_privilege(n.nspname,'usage') AND
> has_table_privilege('"'||n.nspname||'"."'||c.relname||'"','select') GROUP
> BY 1,2,3,4,5,6,7,c.oid,11 UNION SELECT
> l.table_name,l.schema_name,l.feature_column,CASE WHEN l.feature_type = 1
> THEN 'MULTIPOINT' WHEN l.feature_type = 2 THEN 'MULTILINESTRING' WHEN
> l.feature_type = 3 THEN 'MULTIPOLYGON' WHEN l.feature_type = 4 THEN
> 'GEOMETRYCOLLECTION' END AS type,(SELECT srid FROM topology.topology t
> WHERE
> l.topology_id=t.id),2,c.relkind,obj_description(c.oid),array_agg(a.attname),
> count(CASE WHEN t.typname IN
> ('geometry','geography','topogeometry','raster') THEN 1 ELSE NULL END) , 1
> FROM topology.layer l,pg_class c,pg_namespace n,pg_attribute a,pg_type t
> WHERE c.relname=l.table_name AND l.schema_name=n.nspname AND NOT
> a.attisdropped AND a.attrelid=c.oid AND a.atttypid=t.oid AND a.attnum>0 AND
> n.oid=c.relnamespace AND has_schema_privilege(n.nspname,'usage') AND
> has_table_privilege('"'||n.nspname||'"."'||c.relname||'"','select') GROUP
> BY 1,2,3,4,5,6,7,c.oid,11 UNION SELECT
> l."table",l."schema",l."column",'POLYGON',l.srid,2,c.relkind,obj_description(c.oid),array_agg(a.attname),
> count(CASE WHEN t.typname IN
> ('geometry','geography','topogeometry','raster') THEN 1 ELSE NULL END) , 1
> FROM pointcloud_columns l,pg_class c,pg_namespace n,pg_attribute a,pg_type
> t WHERE c.relname=l."table" AND l."schema"=n.nspname AND NOT a.attisdropped
> AND a.attrelid=c.oid AND a.atttypid=t.oid AND a.attnum>0 AND
> n.oid=c.relnamespace AND has_schema_privilege(n.nspname,'usage') AND
> has_table_privilege('"'||n.nspname||'"."'||c.relname||'"','select') GROUP
> BY 1,2,3,4,5,6,7,c.oid,11 UNION SELECT
> l."r_table_name",l."r_table_schema",l."r_raster_column",'RASTER',l.srid,2,c.relkind,obj_description(c.oid),array_agg(a.attname),
> count(CASE WHEN t.typname IN
> ('geometry','geography','topogeometry','raster') THEN 1 ELSE NULL END) , 1
> FROM raster_columns l,pg_class c,pg_namespace n,pg_attribute a,pg_type t
> WHERE c.relname=l."r_table_name" AND l."r_table_schema"=n.nspname AND NOT
> a.attisdropped AND a.attrelid=c.oid AND a.atttypid=t.oid AND a.attnum>0 AND
> n.oid=c.relnamespace AND has_schema_privilege(n.nspname,'usage') AND
> has_table_privilege('"'||n.nspname||'"."'||c.relname||'&qu
Re: [Qgis-user] PostGIS- erroneous query : Unable to get list of tables from DB
I think your issue sounds like what I experienced and from what I dug up it can be as simple as what version of Postgres you were using (I was using Postgres version 10.10) not allowing any access to the "topology" schema. https://github.com/qgis/QGIS/issues/32483 I fixed by running the following SQL command (replace *USERNAME as the username* you are using to connect to postgres): *GRANT USAGE ON SCHEMA topology TO USERNAME;* it was also suggested you could instead give access to public but I'm not sure if that is as secure but maybe other issues are created if public doesn't have access, this is not my area of expertise. GRANT USAGE ON SCHEMA topology TO PUBLIC; Hope that helps. *Jason Carlson* On Fri, Nov 15, 2019 at 7:30 PM Laurence Béchet wrote: > Good afternoon, > > Windows 8.1 pro 64 bits > QGIS version 3.10.0-A Coruña QGIS code revision 6c816b4204 > > I have a postgresql db with Postgis enabled to which I connect using a pg > service. > It was working fine with the default profile. > > I created a new profile (settings/user profiles). My projects were still > displayed (tables located in the db) and looked ok. > > But when I wanted to add a new table from datasource manager/postgresql I > was prompted the first time to create a connection. I created the same one > as I had for the default profile. I tested the connection and it passed. I > clicked to 'connect' and nothing happened: no table list displayed. I > checked with DB/DB manager and I can see my tables. > I switched back to the former default profile: same behaviour (no tables > listed). > > There are different qgis-auth.db files (different sizes) in each profile > folder of C:\Users\\AppData\Roaming\QGIS\QGIS3\profiles (don't know > how to read them though) > > In the logs I found the following messages (PostGIS section): > 2019-11-16T12:27:02 WARNINGNOTICE: row number 0 is out of range > 0..-1 > 2019-11-16T12:28:20 WARNINGErroneous query: [ERROR: > permission denied for schema topology > 2019-11-16T12:28:20 WARNINGNOTICE: WARNING: there is no > transaction in progress > 2019-11-16T12:28:20 WARNINGUnable to get list of spatially enabled > tables from the database > > I don't have any problem with the default user and QGIS version > 3.4.13-Madeira > (I have not tried to create another profile with 3.4.13 because I need a > working version of qgis). > > The error message seems to point toward a lack of permission, but that > same user can run that query within pgadmin without any problems. > > Any idea where to look? I looked on internet but to no avail ... > > Thank you in advance > Laurence Bechet > *ARK IN THE PARK Volunteer Co-Ordinator* > *Cascades Ranger Station* > * Falls Road, Waitakere*, Auckland > ___ > 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 -- *Starland County* *Morrin, AB * *(403) 772-3793* **www.starlandcounty.com <http://www.starlandcounty.com>** * * *Our organization accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. The content of this message is confidential. If you have received it by mistake, please inform us by an email reply and then delete the message. It is forbidden to copy, forward, or in any way reveal the contents of this message to anyone. * ___ 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] QGIS 3.4.2 & 3 still very slow to work in Windows 10
Hi David, I'm new to the list so missed your previous communications but I've been using QGIS for about a year now. Here is a bit of my experience of moving to 3.4 from 2.8, hopefully it might be of use. I apologize if this is stuff you already tried as I didn't read back the history. When I moved from QGIS 2.8 to 3.4 back around Feb-March of this year, mine started hanging a lot and without any consistency on what I was doing at the time it would hang. It was also now crashing everytime I closed QGIS as well as more frequently while actually using it. I found 3 issues that fixed my problems. For me, what was causing the huge stalls every now and then, was an issue with my file storage. My project file was saved in a Google Drive folder. I knew it wasn't recommended to do this but I wasn't actually sharing it with others so the only changes were at my end so nothing should be locking the file at the other end. I also had them flagged for offline use so the system always kept them locally stored. I liked that by saving them in Google Drive I had versions of every change I made I could roll back too if I messed something up. Running it in this way on 2.8 never seemed to be an issue. As a side note, I only looked into this because I know ArcGIS didn't perform well at all if I tried saving any of the files in a Google Drive/Dropbox folder. I added a second hard drive and moved all my projects into it and the performance issues completely went away. The crashes however continued to happen and each update I installed seemed to make them more frequent. Sometimes I couldn't open a project at all but discovered if I opened it with QGIS last time, if I used QGIS with GRASS it would open it and the next time it did this I couldn't open it with the GRASS version anymore but I could with the regular version. Eventually one day I came into work and I could open QGIS but not my main project (not in either normal or with GRASS). I couldn't even open older versions of it. As I could open new or other old projects without issues, I started wondering if perhaps the previous hanging issues caused by having it on a shared drive caused some level of corruption that newer versions of QGIS just couldn't handle gracefully. I eventually just rebuilt my project completely and the stability issues while using QGIS went away. I'm glad I kept a text file that I copied all my complex formulas/expressions into for backups. However, it would still always crash when I closed QGIS but it was saving the project safely. The crashing on closing issue was resolved by accident while resolving another issue I had when I upgraded to 3.10 (or possibly a later version of 3.8) where zooming to a point location took me way off the map (didn't do that previously). Someone pointed me in the direction to look at what EPSG I was running my project as. I was using one that the former GIS person used, which was commonly used by higher levels of government in my region years ago so that was often our starting point. Reading up on the specs it didn't seem to be as compatible with some others. Turns out by changing to a different more common EPSG (still for my region), not only did those zooming to a point issues go away, it also no longer crashes when I close QGIS. Also using this different EPSG with QGIS 3.10 it opens my project in about 5-7 seconds now (fastest previously was about 20 seconds which was still at least 6 times faster than ArcGIS). Hope something in this is useful. *Jason Carlson* On Sun, Nov 10, 2019 at 11:32 AM David Addy wrote: > Just to update this issue. I am still getting slow start ups and qgis not > responding freeze ups just as bad on QGIS 3.8.3. > Every version since 3.4.1 have given these problems. > I have gone through all the files from old versions that I could find and > deleted them. > I have tried new profiles, disabling plug ins and removing the browser > panel. > I have tried turning off my Kaspersky security software. > None of these changes have made any significant difference. > I realise that only a few of us experience these issues, but there must be > an answer somewhere. > > > > -- > Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html > ___ > 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 -- *Starland County* *Morrin, AB * *(403) 772-3793* **www.starlandcounty.com <http://www.starlandcounty.com>** * * *Our organization accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. The content of this message is confidential. If you have received it by mistake, please inform us by an email reply and
Re: [Qgis-user] upgraded 3.10 project, now it no longer zooms to point location, but works on new projects
I think I solved the problem. I changed the projects EPSG to 4269 (what almost all my layers are in) and everything got squashed vertically. That also happened if I went to 4326 (and that one also threw out my styles as I often use map units for my styles). I then tried 3401 (which is just three of my layers) and everything looks to be working and the issue with not being able to zoom to a point goes away. The only downside was all my layout maps are blank but I just needed to reposition them and all is good. I did end up finding one layer in our archives that was EPSG 26912 and that was a really old municipality border shapefile so I'm guessing that used to be projects starting point years back. There was also a side benefit, before switching to EPSG 3401, everytime I closed QGIS it crashed. There was never any data corruption so it wasn't a big concern, but now it just closes as it should. Thanks for getting me looking in the right direction. *Jason Carlson* On Mon, Nov 4, 2019 at 10:51 AM Jason Carlson wrote: > Hi Matthias, > > All the older projects I inherited were using are EPSG is 26912 (NAD83/UTM > Zone 12N), however they don't have a single layer that uses that EPSG. > > This layer I'm seeing the issues with is EPSG:3401 (NAD83/Alberta 10-TM > (Resource)) > Most layers in my system that I import on a regular basis are EPSG: 4269 > The remaining few layers (mostly from 3rd party sources) are EPSG: 4326 > > As I don't actually have any layers that are 26912 in my project so it > struck me as odd why that was used. When I asked, the former GIS person > told to just keep using the same project 26912 for all new projects because > it works. I was new to GIS myself so I never questioned it, however, I have > since learned they didn't really understand GIS at all so I needed to > unlearn a lot of what they showed me. > > Because most of my layers were 4269, I have been using that in new > projects. I was thinking of changing that in existing projects but as they > all seemed to work fine, I never did look into messing with that. > > When I open the CRS tab of the Project Properties. In the "Recently used > coordinate ref systems" the top 7 are * Generated CRS, not standard ones. > > *Jason Carlson* > > IT/GIS Administrator > > *403.772.3793* > > > On Mon, Nov 4, 2019 at 10:02 AM Matthias Kuhn wrote: > >> Hi Jason, >> >> Which coordinate reference system did you define in your project? >> https://docs.qgis.org/3.4/en/docs/user_manual/working_with_projections/working_with_projections.html#project-coordinate-reference-systems >> >> Regards >> >> Matthias >> On 11/4/19 5:43 PM, Jason Carlson wrote: >> >> Hi all, I've been using QGIS for just over a year now and exclusively >> since about February as I didn't reinstall ArcGIS on my new computer at >> that time. >> >> In QGIS 3.10 if I open a project (created in a different previous version >> of QGIS ranging from 3.4 - 3.8) and then I: >> >>1. Open an attribute table of a layer that contains point geometry >>2. Select one of the records in that attribute table >>3. Click "Zoom Map to selected rows" >> >> It puts me hundreds of miles off my map entirely (so a blank screen). >> This only happens with records that have single point geom (if it is a line >> or polygon it works fine). >> >> If I remove the layer and re-add it back, the problem still exists. >> However, if I create a brand new project in 3.10 and add that exact same >> layer (all are stored in PostGIS database), the issue is not there and it >> works as expected. So the issue seems to stem from old "working" projects >> that are now opened in the newer version of QGIS. >> >> Has anyone else seen this or something similar? Is there anyway of fixing >> the project file without having to recreate it all from scratch so I can >> use these in the new version of QGIS? >> >> *Jason Carlson* >> >> IT/GIS Administrator >> >> *403.772.3793* >> >> *Starland County* >> *Morrin, AB * >> *(403) 772-3793* >> *www.starlandcounty.com <http://www.starlandcounty.com>* >> >> *Our organization accepts no liability for the content of this email, or >> for the consequences of any actions taken on the basis of the information >> provided, unless that information is subsequently confirmed in writing. The >> content of this message is confidential. If you have received it by >> mistake, please inform us by an email reply and then delete the message. It >> is forbidden to copy, forward, or in any way reveal the contents of this >> message to anyone. *
Re: [Qgis-user] upgraded 3.10 project, now it no longer zooms to point location, but works on new projects
Hi Matthias, All the older projects I inherited were using are EPSG is 26912 (NAD83/UTM Zone 12N), however they don't have a single layer that uses that EPSG. This layer I'm seeing the issues with is EPSG:3401 (NAD83/Alberta 10-TM (Resource)) Most layers in my system that I import on a regular basis are EPSG: 4269 The remaining few layers (mostly from 3rd party sources) are EPSG: 4326 As I don't actually have any layers that are 26912 in my project so it struck me as odd why that was used. When I asked, the former GIS person told to just keep using the same project 26912 for all new projects because it works. I was new to GIS myself so I never questioned it, however, I have since learned they didn't really understand GIS at all so I needed to unlearn a lot of what they showed me. Because most of my layers were 4269, I have been using that in new projects. I was thinking of changing that in existing projects but as they all seemed to work fine, I never did look into messing with that. When I open the CRS tab of the Project Properties. In the "Recently used coordinate ref systems" the top 7 are * Generated CRS, not standard ones. *Jason Carlson* IT/GIS Administrator *403.772.3793* On Mon, Nov 4, 2019 at 10:02 AM Matthias Kuhn wrote: > Hi Jason, > > Which coordinate reference system did you define in your project? > https://docs.qgis.org/3.4/en/docs/user_manual/working_with_projections/working_with_projections.html#project-coordinate-reference-systems > > Regards > > Matthias > On 11/4/19 5:43 PM, Jason Carlson wrote: > > Hi all, I've been using QGIS for just over a year now and exclusively > since about February as I didn't reinstall ArcGIS on my new computer at > that time. > > In QGIS 3.10 if I open a project (created in a different previous version > of QGIS ranging from 3.4 - 3.8) and then I: > >1. Open an attribute table of a layer that contains point geometry >2. Select one of the records in that attribute table >3. Click "Zoom Map to selected rows" > > It puts me hundreds of miles off my map entirely (so a blank screen). This > only happens with records that have single point geom (if it is a line or > polygon it works fine). > > If I remove the layer and re-add it back, the problem still exists. > However, if I create a brand new project in 3.10 and add that exact same > layer (all are stored in PostGIS database), the issue is not there and it > works as expected. So the issue seems to stem from old "working" projects > that are now opened in the newer version of QGIS. > > Has anyone else seen this or something similar? Is there anyway of fixing > the project file without having to recreate it all from scratch so I can > use these in the new version of QGIS? > > *Jason Carlson* > > IT/GIS Administrator > > *403.772.3793* > > *Starland County* > *Morrin, AB * > *(403) 772-3793* > *www.starlandcounty.com <http://www.starlandcounty.com>* > > *Our organization accepts no liability for the content of this email, or > for the consequences of any actions taken on the basis of the information > provided, unless that information is subsequently confirmed in writing. The > content of this message is confidential. If you have received it by > mistake, please inform us by an email reply and then delete the message. It > is forbidden to copy, forward, or in any way reveal the contents of this > message to anyone. * > > > ___ > Qgis-user mailing listqgis-u...@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 -- *Starland County* *Morrin, AB * *(403) 772-3793* **www.starlandcounty.com <http://www.starlandcounty.com>** * * *Our organization accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. The content of this message is confidential. If you have received it by mistake, please inform us by an email reply and then delete the message. It is forbidden to copy, forward, or in any way reveal the contents of this message to anyone. * ___ 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] upgraded 3.10 project, now it no longer zooms to point location, but works on new projects
Hi all, I've been using QGIS for just over a year now and exclusively since about February as I didn't reinstall ArcGIS on my new computer at that time. In QGIS 3.10 if I open a project (created in a different previous version of QGIS ranging from 3.4 - 3.8) and then I: 1. Open an attribute table of a layer that contains point geometry 2. Select one of the records in that attribute table 3. Click "Zoom Map to selected rows" It puts me hundreds of miles off my map entirely (so a blank screen). This only happens with records that have single point geom (if it is a line or polygon it works fine). If I remove the layer and re-add it back, the problem still exists. However, if I create a brand new project in 3.10 and add that exact same layer (all are stored in PostGIS database), the issue is not there and it works as expected. So the issue seems to stem from old "working" projects that are now opened in the newer version of QGIS. Has anyone else seen this or something similar? Is there anyway of fixing the project file without having to recreate it all from scratch so I can use these in the new version of QGIS? *Jason Carlson* IT/GIS Administrator *403.772.3793* -- *Starland County* *Morrin, AB * *(403) 772-3793* **www.starlandcounty.com <http://www.starlandcounty.com>** * * *Our organization accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. The content of this message is confidential. If you have received it by mistake, please inform us by an email reply and then delete the message. It is forbidden to copy, forward, or in any way reveal the contents of this message to anyone. * ___ 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
