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

No update of CRS cache when modifying a custom CRS #16899

Closed
qgib opened this issue Jun 13, 2013 · 5 comments
Closed

No update of CRS cache when modifying a custom CRS #16899

qgib opened this issue Jun 13, 2013 · 5 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Projections/Transformations Related to coordinate reference systems or coordinate transformation
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Jun 13, 2013

Author Name: Leyan Ouyang (Leyan Ouyang)
Original Redmine Issue: 8058
Affected QGIS version: master
Redmine category:projection_support
Assignee: Marco Hugentobler


In 1.8, if I update a custom CRS, I can directly use the new value for this CRS, while in master, I have to restart QGIS to be able to use the updated parameters. They are displayed when I choose the CRS, but not used during the actual transformation, which is a severe regression in my opinion as it makes the whole custom CRS management very confusing.

This is due to the recent use of a cache to store CRS parameters (since commit 8dc0135). There is currently no way to update the cache, short of restarting QGIS.

I tried to write a simple updateCRSCache function, but it isn't giving the expected result. The CRS seems updated in the debug output, but nothing is redrawn. Here is what I wrote so far: https://github.com/leyan/Quantum-GIS/commits/custom_CRS

@qgib
Copy link
Contributor Author

qgib commented Jun 14, 2013

Author Name: Marco Hugentobler (@mhugent)


The updateCRSCache function is fine. However, there is also a crs transform cache that copies the crs and that needs to be updated as well (sorry, the crs / transform cache have mainly been made with the server usage in mind...). It should now work after 4061445, please test.

@qgib
Copy link
Contributor Author

qgib commented Jun 14, 2013

Author Name: Leyan Ouyang (Leyan Ouyang)


This works for me. Actually the behavior is not exactly the same, as the layers are reprojected automatically as soon as they are redrawn. Previously, the CRS had to be selected again for each layer before the new parameters can be used. I think the new behavior is better and that is a change I was planning to add anyway.

I added a pull request to deal with deleted custom CRS: #661

The whole custom CRS management still is a bit flaky, with a bad UI (I know, I did it ;) ) and a lot of things that should be more robust. Anyway, this was already the case in 1.8 so no regression there, I guess improvements will have to wait for the next version.

@qgib
Copy link
Contributor Author

qgib commented Jun 15, 2013

Author Name: Giovanni Manghi (@gioman)


can this be closed?


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Jun 15, 2013

Author Name: Marco Hugentobler (@mhugent)


I added a pull request to deal with deleted custom CRS

Applied. It would also be possible to just delete the crs cache entry for update and delete (if the crs is not cached, the entry will be created on next usage).

The whole custom CRS management still is a bit flaky, with a bad UI (I know, I did it ;) ) and a lot of things that should be more >robust. Anyway, this was already the case in 1.8 so no regression there, I guess improvements will have to wait for the next version.

I agree. It will be greatly appreciated if you improve custom crs handling and ui for the next version.

Thanks for your input and patches,
Marco

@qgib
Copy link
Contributor Author

qgib commented Jun 15, 2013

Author Name: Leyan Ouyang (Leyan Ouyang)


Yes, can be closed for me, the main issue is solved.


  • status_id was changed from Feedback to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Projections/Transformations Related to coordinate reference systems or coordinate transformation labels May 24, 2019
@qgib qgib added this to the Version 2.0.0 milestone May 24, 2019
@qgib qgib closed this as completed 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! Projections/Transformations Related to coordinate reference systems or coordinate transformation
Projects
None yet
Development

No branches or pull requests

1 participant