-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
QGIS "Ballpark Transformations" #34983
Comments
From the QGIS Users list: Example: So I installed the relevant .gsb files in the correct directory with the other .gsb files, restarted and tried again to open the project. This time it did not come up with the message suggesting the download but instead just suggested using one of the other transformations which are less accurate than the proper OSTN15_NTv2 transformation. Need to know why it is doing the less accurate transformation and how to get it to do the correct transformation instead. |
Hi @rjhale1971 see #33929 and #34273 if the answer is satisfactory can we close this? cheers! |
Let me take a look! Sorry I'm just getting to this |
So I'm reading through the bug reports and in two sentences or less: Something in this project falls outside the specified grid so this is expected. (I may have completely botched that explanation) |
So not a bug? |
Reading through the two other reports I'm guessing this one has been handled - I guess my question would be when faced with this message it really points to a data issue falling outside of a grid? I only ask because I had another phone call today and I'm a bit fuzzy on the resolution shown in the other two bug reports. |
That would be the most common explanation. There's possibly other reasons a particular transform may fail causing a fallback ("ballpark") transform to be used though. |
Could the term ballpark be replaced by fallback or any of its related synonyms? Unless ballpark is the term in might cause more confusions in some language or crowds. I'm not sure what translations come up in qt for this, as the word can have three distinct meanings. |
@roya0045 I think that's up to individual translators to do -- the term already has usage elsewhere in English in the projection world. |
One more question - and this may be my general lack of not knowing enough on proj. If the "Ballpark transform" comes up - Do I need to fix it or can I just keep working. Does it affect future data collection or is the new data independent of the message.....and this may make no sense as it's been a long day. Other than that - this can be closed since I'm not the only one this has happened to...... |
No, it's not an error, it's just warning you that you aren't getting the exact results you expected. It would only be an issue if you are working on scales where the difference between the grid based transform and the fallback is an issue. QGIS can't make that decision for you, so it warns you, and it's up to you to decide if this is something you need to fix (e.g. by picking a more appropriate transform) or if it's acceptable given the context of your work. We could hide that message, but I'm a big fan of transparency in analysis and pushing all responsibility for making correct decisions back to users. |
Makes sense - I'd rather have it there (now that I know what's happening) than hide it. |
Can we just add some more understandable explanation? Many users are using QGIS in english even if that's not their primary language. |
@elpaso there is a more descriptive explanation available when you click the message |
To be clear, in the current PROJ implementation (and in the foreseable future), the ballpark transformation for horizontal datum shifting is a null transformation, that is we assume that the datums are identical, because we have no other information available. The error in doing so can range from 200 meters when transforming between datums < 1950 and modern datums, to just a few meters when transforming between modern datums. For vertical transformations (but QGIS is likely not triggering that a lot), there can be vertical ballpark transformations as well. For now they are null too, but we could potentially try to be smarter (see OSGeo/PROJ#1743) |
So for me (english speaking guy in the southern United States) I use the term "ballpark" when I need a very loose fitting answer. As in "How much to fix this car - can you give me a ballpark estimate" and 'ballpark' is know to be imprecise. I use the term guesstimate or estimate which it sounds like the ballpark transformation isn't doing - it's "not doing anything". For me (and I in no way can speak for the myriad of users out there) I like NULL transformation as that implies nothing happened. Ballpark makes it sound like SOMETHING happened - and whatever it was wasn't very precise - BUT - as far as I know that will be a North American way of looking at the word "ballpark". We can't even handle the metric system so take that for what it's worth. |
@rjhale1971 it's not doing a null transform. It's doing some transform, but not the one you asked for... |
What I need to know is whether qgis is doing the correct OSTN02 (or OSTN15) transformation within the area that it can and only doing the ballpark transformation outside this area or whether it is doing the approximate transformatoin over the whole area. Then need to know how to get it to do the full accuracy transformation in the area that it can. |
Can you share a sample project? |
Hi @nyalldawson Yes, of course, thank you very much for looking at this. Here is a project with these layers I was talking about: |
@PedroVenancio - perfect, fix inbound. You can safely ignore this warning for this project, it's just being overly pedantic. |
Really great @nyalldawson ! Thank you very much! |
for rendering We can safely use ballpark transforms without bothering the user here -- at the likely scale of layer extents there won't be an appreciable difference, and we aren't actually transforming any rendered points here anyway (just the layer extent) Fixes qgis#34983
But the point is that it is giving this warning on numerous different projects for many people now who are using a range of different CRS.
As I mentioned in one of the comments the various ballpark options offered for the UK system give a wide range of accuracies but none of them are the full OSTN02 or OSTN15 which is needed when using differential gps and highly accurate basemaps. Basically it gives the impression that you can't use qgis for survey grade mapping - is that now true? Either way this urgently needs to be sorted out.
…________________________________
From: Pedro Venancio <[email protected]>
Sent: 02 April 2020 01:01
To: qgis/QGIS <[email protected]>
Cc: Michael.Dodd <[email protected]>; Comment <[email protected]>
Subject: Re: [qgis/QGIS] QGIS "Ballpark Transformations" (#34983)
CAUTION: This mail comes from outside the University. Please consider this before opening attachments, clicking links, or acting on the content.
Really great @nyalldawson<https://github.com/nyalldawson> !
Thank you very much!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#34983 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AO4AYVTK3UIFF4AOK5HONGTRKPIWNANCNFSM4LFK4YAA>.
|
@mikedoddOU did you test the linked patch? |
How do I do that? |
Wait till it's merged and test the nightlies, and then report back here if you still see issues. |
OK, thanks |
for rendering We can safely use ballpark transforms without bothering the user here -- at the likely scale of layer extents there won't be an appreciable difference, and we aren't actually transforming any rendered points here anyway (just the layer extent) Fixes #34983
Awesome @nyalldawson ! Thank you very much! |
|
I'm on 3.16.14 and those warnings keep being raised!! Just open @PedroVenancio's project and change the map canvas CRS from EPSG:3763 to EPSG:20790... |
@AntonioPestana cannot confirm: |
You are absolutely right. I didn't notice that the "ballpark
transformation" warning was missing in the select transformation window!...
Sorry about that.
Giovanni Manghi ***@***.***> escreveu no dia sexta, 3/12/2021
à(s) 09:08:
… I'm on 3.16.14 and those warnings keep being raised!! Just open
@PedroVenancio <https://github.com/PedroVenancio>'s project and change
the map canvas CRS from EPSG:3763 to EPSG:20790...
@AntonioPestana <https://github.com/AntonioPestana> cannot confirm:
[image: image]
<https://user-images.githubusercontent.com/1951107/144576012-6a2eb5f2-0515-4f33-8807-cbffdb98b30e.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#34983 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARYXC6N2QIWHTTBXYVU5J2LUPCCJDANCNFSM4LFK4YAA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
It is not clear what was fixed. Most importantly, we never got an answer to this earlier concern:
Do I need to open a new issue for this? |
I received an email from two users with 3.12 asking about "Ballpark Transformations" - the exact phrase was "Used a Ballpark transformation from EPSG:4326 to EPSG: 2274".
I've been able to generate the message twice by:
I've found mention of it here: https://qgis.org/api/classQgsCoordinateTransform.html#a16adb051fafc25058c0040a310f1606b
The expanded message in QGIS is:
If I check the project properties there is no Datum Transformation defined after all this happens.
I'm assuming that if a project has no data and one jumps datums by changing the projection it's saying "Hey since there is no data this transformation is a "ballpark" i.e. not exact".
The text was updated successfully, but these errors were encountered: