Google Satellite not rendering properly

CHRO-BE commented 2 years ago

What is the bug or the crash?

Since switching to a new desktop, I have had an issue with the Google satellite tiles where when I zoom in or out, the layer does not always render, leaving me with a blank screen with occasionally a strip of the satellite at the far right of the screen. I have tried using a different datasource for the satellite, updating QGIS and switching around my screen display, but nothing has worked. I do not get the same issue with Google Street Map, and I never had the issue on my old desktop. QGIS Problem

Steps to reproduce the issue

Since this issue seems specific to my desktop, I don't know if it can be reproduced.

Versions

QGIS version 3.22.5-Białowieża QGIS code revision c2723178 Qt version 5.15.2 Python version 3.9.5 GDAL/OGR version 3.4.1 PROJ version 8.2.1 EPSG Registry database version v10.041 (2021-12-03) GEOS version 3.10.2-CAPI-1.16.0 SQLite version 3.37.2 PDAL version 2.3.0 PostgreSQL client version 13.0 SpatiaLite version 5.0.1 QWT version 6.1.3 QScintilla2 version 2.11.5 OS version Windows 10 Version 2009

Active Python plugins ZoomToPostcode 1.0 db_manager 0.1.20 grassprovider 2.12.99 MetaSearch 0.3.5 processing 2.12.99 sagaprovider 2.12.99 what3words 4.1

Supported QGIS version

[X] I'm running a supported QGIS version according to the roadmap.

New profile

[X] I tried with a new QGIS profile

Additional context

No response

emeggiolaro commented 2 years ago

Same issue here (Ryzen 2400G)

MargarethWarburton commented 2 years ago

I have encountered the same issue. When working in the Print Layout Interface the satellite imagery works without any problems. (The link I use for the XYZ Tiles Connection: https://www.google.cn/maps/vt?lyrs=s@189&gl=cn&x={x}&y={y}&z={z} )

QGIS-Version 3.24.3-Tisler QGIS-Codeversion cf22b74e Qt-Version 5.15.3 Python-Version 3.9.5 GDAL-Version 3.4.3 PROJ-Version 9.0.0 EPSG-Registraturdatenbankversion v10.054 (2022-02-13) GEOS-Version 3.10.2-CAPI-1.16.0 SQLite-Version 3.38.1 PDAL-Version 2.3.0 PostgreSQL-Client-Version unknown SpatiaLite-Version 5.0.1 QWT-Version 6.1.6 QScintilla2-Version 2.13.1 BS-Version Windows 10 Version 2009

Aktive Python-Erweiterungen db_manager 0.1.20 grassprovider 2.12.99 MetaSearch 0.3.6 processing 2.12.99 sagaprovider 2.12.99

QGIS-Version 3.24.3-Tisler QGIS-Codeversion cf22b74e Qt-Version 5.15.3 Python-Version 3.9.5 GDAL-Version 3.4.3 PROJ-Version 9.0.0 EPSG-Registraturdatenbankversion v10.054 (2022-02-13) GEOS-Version 3.10.2-CAPI-1.16.0 SQLite-Version 3.38.1 PDAL-Version 2.3.0 PostgreSQL-Client-Version unknown SpatiaLite-Version 5.0.1 QWT-Version 6.1.6 QScintilla2-Version 2.13.1 BS-Version Windows 10 Version 2009

Aktive Python-Erweiterungen db_manager 0.1.20 grassprovider 2.12.99 MetaSearch 0.3.6 processing 2.12.99 sagaprovider 2.12.99

CHRO-BE commented 2 years ago

Its the same for me - the rendering works just fine in the layout setting. I think it must be a problem with the display resolution, as on the default for my desktop (2560 x 1440) I get the rendering problem, but when I reduce it, the problem either stops, or happens less frequently.

cousinmao commented 2 years ago

Same here. Using QGIS 3.26 (Buenos Aires). CHRO-BE's solution works. My monitor is also 2560x1440, and reducing it does fix the issue. Thanks.

gioman commented 2 years ago

Any message in QGIS logs?

cousinmao commented 2 years ago

Not that I could find.

github-actions[bot] commented 2 years ago

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue. In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue. If there is no further activity on this issue, it will be closed in a week.

github-actions[bot] commented 2 years ago

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue. Or, if you have any further questions, there are also further support channels that can help you.

rawhead303 commented 1 year ago

I have this same issue in both 3.22 and 3.3 beta.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">

QGIS version | 3.22.16-Białowieża | QGIS code revision | 6f08e4d7b0 -- | -- | -- | -- Qt version | 5.14.2 Python version | 3.8.7 GDAL/OGR version | 3.2.1 PROJ version | 6.3.2 EPSG Registry database version | v9.8.6 (2020-01-22) GEOS version | 3.9.1-CAPI-1.14.2 SQLite version | 3.31.1 PostgreSQL client version | 12.3 SpatiaLite version | 4.3.0a QWT version | 6.1.4 QScintilla2 version | 2.11.4 OS version | macOS 13.2 | | | Active Python plugins kmltools | 3.1.27 contour | 2.0.12 geoscience | 1.9 qfieldsync | v4.3.1 Qgis2threejs | 2.7.1 mmqgis | 2021.9.10 Mergin | 2023.1 processing | 2.12.99 sagaprovider | 2.12.99 grassprovider | 2.12.99 db_manager | 0.1.20 MetaSearch | 0.3.5 QGIS version 3.22.16-Białowieża QGIS code revision [6f08e4d7b0](https://github.com/qgis/QGIS/commit/6f08e4d7b0) Qt version 5.14.2 Python version 3.8.7 GDAL/OGR version 3.2.1 PROJ version 6.3.2 EPSG Registry database version v9.8.6 (2020-01-22) GEOS version 3.9.1-CAPI-1.14.2 SQLite version 3.31.1 PostgreSQL client version 12.3 SpatiaLite version 4.3.0a QWT version 6.1.4 QScintilla2 version 2.11.4 OS version macOS 13.2 Active Python plugins kmltools 3.1.27 contour 2.0.12 geoscience 1.9 qfieldsync v4.3.1 Qgis2threejs 2.7.1 mmqgis 2021.9.10 Mergin 2023.1 processing 2.12.99 sagaprovider 2.12.99 grassprovider 2.12.99 db_manager 0.1.20 MetaSearch 0.3.5 Changing screen resolutions does not help. However, I only see this on my Intel/iMac (3.8 GHz 8 core i7, AMD Radeon Pro 5500 XT 8GB / 72 GB DDR4) and not on my M1 Macbook Air, running 3.28 Firenze.

wyliehorn commented 1 year ago

One of my colleagues still has this issue. If you re-open it I will send any feedback required.

agiudiceandrea commented 1 year ago

@wyliehorn this issue report is still open.

wyliehorn commented 1 year ago

Thanks. What information do you require? I would like to help in any way I can.

wyliehorn commented 1 year ago

Details are as described by @CHRO-BE at the start of this thread.

mypitaya commented 1 year ago

hi, used Biatoweiza & Ferenze, neither of the two versions satisfied the rendering of map layers.

DEM shows good,
Tried All Google Maps e.g. hybrid, terrain, roadmap, streetmap, but only shows light blue, black, or white in canvas
Delete all maps and re-install, but the same.

in view of the above, are these BUGs to these Versions? I was using the Old Version before, it was fine running.

please rescue me, need to have this report badly...thanks for comments & suggestions

pbfi commented 1 year ago

I have this problem too. 3.32.0-Lima. Mac OS 13.5.1. Cheers.

losbaltica commented 1 year ago

I had the same problem, but after switching to different google satellite endpoint it worked for me.

After switching from: http://www.google.cn/maps/vt?lyrs=s@189&gl=cn&x={x}&y={y}&z={z}

to: https://mt1.google.com/vt/lyrs=s&x={x}&y={y}&z={z}

It start rendering correctly...

nicpottier commented 11 months ago

FWIW changing URLs also fixed it for me.

mypitaya commented 11 months ago

thanks,

changing to this [https://mt1.google.com/vt/lyrs=s&x={x}&y={y}&z={z}]

got a reply from Google

That’s an error.

Your client has issued a malformed or illegal request. That’s all we know.

hriihima commented 10 months ago

I had the same problem, but after switching to different google satellite endpoint it worked for me.

After switching from: http://www.google.cn/maps/vt?lyrs=s@189&gl=cn&x={x}&y={y}&z={z}

to: https://mt1.google.com/vt/lyrs=s&x={x}&y={y}&z={z}

It start rendering correctly...

Worked for me as well

wyliehorn commented 10 months ago

Glad to hear that this fix worked for you too :)

Wylie On 27/11/2023 08:31:04, hriihima @.> wrote: I had the same problem, but after switching to different google satellite endpoint it worked for me. After switching from: @.&gl=cn&x={x}&y={y}&z={z} @.&gl=cn&x=%7Bx%7D&y=%7By%7D&z=%7Bz%7D] to: https://mt1.google.com/vt/lyrs=s&x={x}&y={y}&z={z} [https://mt1.google.com/vt/lyrs=s&x=%7Bx%7D&y=%7By%7D&z=%7Bz%7D] It start rendering correctly... Worked for me as well — Reply to this email directly, view it on GitHub [https://github.com/qgis/QGIS/issues/48114#issuecomment-1827357092], or unsubscribe [https://github.com/notifications/unsubscribe-auth/AYTJBGFKJ2L274AQBIKW4MDYGRFT5AVCNFSM5SY66ZD2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBSG4ZTKNZQHEZA]. You are receiving this because you were mentioned.Message ID: @.> [285f9d80-ce13-4efe-af07-fbcd07e4dd3f]

qgis / QGIS