Skip to content
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

Refreshing a vector layer does not change feature count #21872

Closed
qgib opened this issue Nov 17, 2015 · 4 comments
Closed

Refreshing a vector layer does not change feature count #21872

qgib opened this issue Nov 17, 2015 · 4 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Vectors Related to general vector layer handling (not specific data formats)

Comments

@qgib
Copy link
Contributor

qgib commented Nov 17, 2015

Author Name: Mehmet Selim BILGIN (@MSBilgin)
Original Redmine Issue: 13848
Affected QGIS version: 2.12.0
Redmine category:vectors


In QGIS 2.12, normally when clicking Show feature count button on the right click menu of a vector layer, calculates layer's feature count shows the number near the feature layer name in Layers Panel. If a layer that comes from a database it calculates correctly at first time but in case of deleting or adding some rows from another applications, feature count doesnt change when clicking again Show feature count button. It is strange that the changes (new features)are shown in QGIS canvas but not affects feature count.


Related issue(s): #21933 (relates)
Redmine related issue(s): 13911


@qgib
Copy link
Contributor Author

qgib commented Dec 6, 2015

Author Name: Sebastian Dietrich (Sebastian Dietrich)


Confirmed in master (dc73fb2), using PostgreSQL.

I found that adding features worked, if they were shown on the canvas. Apparently QGIS notices that a feature it received for drawing is new and adds it to its internal count.

Deleting features however does not reduce the feature count shown. The following does not help:

  • zooming and panning
  • disable and re-enable the show feature count option
  • using the Refresh function in the Map Navigation Toolbar

What did help in my case was using the Filter... dialog and simply confirming the already present SQL filter.

See also #21933, which is basically the same but for the layer extent.

@qgib
Copy link
Contributor Author

qgib commented May 26, 2016

Author Name: Saber Razmjooei (@saberraz)


  • category_id was configured as Vectors

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • easy_fix was configured as 0
  • regression was configured as 0

@qgib
Copy link
Contributor Author

qgib commented Mar 9, 2019

Author Name: Giovanni Manghi (@gioman)


End of life notice: QGIS 2.18 LTR

Source:
http://blog.qgis.org/2019/03/09/end-of-life-notice-qgis-2-18-ltr/

QGIS 3.4 has recently become our new Long Term Release (LTR) version. This is a major step in our history – a long term release version based on the massive updates, library upgrades and improvements that we carried out in the course of the 2.x to 3x upgrade cycle.

We strongly encourage all users who are currently using QGIS 2.18 LTR as their preferred QGIS release to migrate to QGIS 3.4. This new LTR version will receive regular bugfixes for at least one year. It also includes hundreds of new functions, usability improvements, bugfixes, and other goodies. See the relevant changelogs for a good sampling of all the new features that have gone into version 3.4

Most plugins have been either migrated or incorporated into the core QGIS code base.

We strongly discourage the continued use of QGIS 2.18 LTR as it is now officially unsupported, which means we’ll not provide any bug fix releases for it.

You should also note that we intend to close all bug tickets referring to the now obsolete LTR version. Original reporters will receive a notification of the ticket closure and are encouraged to check whether the issue persists in the new LTR, in which case they should reopen the ticket.

If you would like to better understand the QGIS release roadmap, check out our roadmap page! It outlines the schedule for upcoming releases and will help you plan your deployment of QGIS into an operational environment.

The development of QGIS 3.4 LTR has been made possible by the work of hundreds of volunteers, by the investments of companies, professionals, and administrations, and by continuous donations and financial support from many of you. We sincerely thank you all and encourage you to collaborate and support the project even more, for the long term improvement and sustainability of the QGIS project.


  • resolution was changed from to end of life
  • status_id was changed from Open to Closed

@qgib qgib closed this as completed Mar 9, 2019
@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Vectors Related to general vector layer handling (not specific data formats) labels May 25, 2019
signedav pushed a commit to signedav/QGIS that referenced this issue May 27, 2019
src/python/qgspythonutilsimpl.cpp:596 produces "lost sys.stdout" when
qgis.utils.updateAvailablePlugins() returns.
signedav pushed a commit to signedav/QGIS that referenced this issue May 27, 2019
spatialthoughts pushed a commit to spatialthoughts/QGIS that referenced this issue Jun 10, 2019
src/python/qgspythonutilsimpl.cpp:596 produces "lost sys.stdout" when
qgis.utils.updateAvailablePlugins() returns.
spatialthoughts pushed a commit to spatialthoughts/QGIS that referenced this issue Jun 10, 2019
spatialthoughts pushed a commit to spatialthoughts/QGIS that referenced this issue Jun 10, 2019
src/python/qgspythonutilsimpl.cpp:596 produces "lost sys.stdout" when
qgis.utils.updateAvailablePlugins() returns.
spatialthoughts pushed a commit to spatialthoughts/QGIS that referenced this issue Jun 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Vectors Related to general vector layer handling (not specific data formats)
Projects
None yet
Development

No branches or pull requests

1 participant