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

Not accurate extent frame in map overview #12303

Closed
qgib opened this issue Dec 10, 2009 · 9 comments
Closed

Not accurate extent frame in map overview #12303

qgib opened this issue Dec 10, 2009 · 9 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! GUI/UX Related to QGIS application GUI or User Experience

Comments

@qgib
Copy link
Contributor

qgib commented Dec 10, 2009

Author Name: Maxim Dubinin (@simgislab)
Original Redmine Issue: 2243
Affected QGIS version: master
Redmine category:gui
Assignee: nobody -


If map overview is turned on and docked, the red extent frame is usually not accurate, i.e. either top/bottom bounds are missing until you start resizing.

Minor issue of course, but still.

Example: http://gis-lab.info/images/screenshots/20091205-kn6-11kb.jpg


@qgib
Copy link
Contributor Author

qgib commented Dec 10, 2009

Author Name: Giovanni Manghi (@gioman)


Are you sure that are "missing"? It seems to me that if enlarge width/height of the overview box than the lines do show in the right place.

By the way, other overview issues are: #12241 #12226 #11509

@qgib
Copy link
Contributor Author

qgib commented Dec 12, 2009

Author Name: Steven Mizuno (Steven Mizuno)


I believe the extent frame is operating correctly. The main intent of the frame is to show what area in the full map data is currently being displayed on the main map when zoomed in.

These are some factors that affect the display position of the rectangle:

  1. Aspect ratio of the Overview vs. main map canvas.

  2. the Overview shows the full extent exactly for all active layers (within its aspect ratio), but the zoom full extent actually puts a 5% additional buffer so the data are not right on the edge of the map. This will cause the rectangle to be outside the overview if both canvases have the same aspect ratio.

  3. The small matter of + or - one pixel due to conversion of floating point values to integer.

A better test is to zoom in until the rectangle is the smallest size it can be, then positioning the rectangle over a feature on the map. That feature will be displayed on the main map.

@qgib
Copy link
Contributor Author

qgib commented Mar 14, 2011

Author Name: Mayeul Kauffmann (@mayeulk)


In the example http://trac.osgeo.org/qgis/attachment/ticket/2243/wrong_overview.png, the overview is almost correct if I pan near the North of the areao of interest (Monaca). The more I go in the south, the more it is wrong. Having the pane docked or floating does not change anything.

@qgib
Copy link
Contributor Author

qgib commented Dec 16, 2011

Author Name: Giovanni Manghi (@gioman)


  • fixed_version_id was changed from Version 1.7.0 to Version 1.7.4

@qgib
Copy link
Contributor Author

qgib commented Apr 16, 2012

Author Name: Paolo Cavallini (@pcav)


  • crashes_corrupts_data was configured as 0
  • version was configured as master
  • fixed_version_id was changed from Version 1.7.4 to Version 1.8.0

@qgib
Copy link
Contributor Author

qgib commented Sep 4, 2012

Author Name: Paolo Cavallini (@pcav)


  • fixed_version_id was changed from Version 1.8.0 to Version 2.0.0

@qgib
Copy link
Contributor Author

qgib commented Jun 28, 2014

Author Name: Jürgen Fischer (@jef-n)


  • fixed_version_id was changed from Version 2.0.0 to Future Release - Lower Priority

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • regression was configured as 0
  • pull_request_patch_supplied was configured as 0
  • easy_fix 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/


  • resolution was configured as 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! GUI/UX Related to QGIS application GUI or User Experience labels May 24, 2019
@qgib qgib added this to the Future Release - Lower Priority milestone May 24, 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! GUI/UX Related to QGIS application GUI or User Experience
Projects
None yet
Development

No branches or pull requests

1 participant