OK....this is just for pilots using the
P4P + integrated Android device and controller only (ie. not a stand-alone phone set-up):
Here (now called: Here WeGo) requires any developer (like DJI... as a developer of the Android app DJI Go 4) to obtain an app ID and an app code to be integrated into the app code (DJI of course would have all this built into the DJI Go 4 app installed on their + controller with built-in Android device/screen). Now, apparently Here WeGo has available to app developers numerous map tile themes (base satellite map; administrative labels layer; street tile; line tile; etc, etc, etc, etc....lots of thematic layers to add to the app !). Also, Here WeGo offers map cache FOR SURE...no doubt about that.
We have no way of telling precisely how DJI has implemented the request parameters in Go 4 related to Here WeGo connections (I've included the Here WeGo developer code below, as an example to an app requesting a raster layer like a satellite image tile). I can only assume that some of the satellite image coverage that Here WeGo is serving up is possibly a not high enough resolution to withstand something like a scale of ~~ 1 : 10,000 (this scale number is purely a guess on my part! the scale would depend on the regional satellite or aerial image's maximum "zoom" resolved/resolution scale capability).
So, if we take for example the code below that calls up a satellite (or, aerial image) from the map rendering service that has: in Country x, County y, municipality z, a raster resolution that craps out at anything closer than a scale of 1 : 24,000 (say just for discussion, zoom level 5), and the COL parameter, and ZOOM parameter don't jive with the INFO parameter and the satellite tile renders at 1 : 10,000, then funky stuff like blur can happen (like when you zoom in way too far on a photograph), etc, etc...
https://{1-4}.aerial.maps.cit.api.here.com
/maptile/2.1/basetile/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}
?app_id={YOUR_APP_ID}
&app_code={YOUR_APP_CODE}
&{param}={value}
To me, the fix would happen in the DJI Go 4 app that is loaded onto the that special Android screen device that is the integrated + controller, and would not be a firm-ware tweak.
Anyhow, this is something that only DJI could address in an DJI Go 4 up-date "patch"...
Sorry for being so verbose LOL!
