Not exactly the requested maps, since they are vector maps (and I don't even know if it's possible to get vector tiles in MOBAC), but their equivalent raster (accessible from the map you shown us, in the layer selection window).
I don't know if raster tiles are exactly identical to vector tiles, but they look at least very similar...
The URL I put in these bsh (that comes from the one in Web Access to the map) are for some of them quite obvious, like "&lang=fr", but some other are not really understandable, like "xnlp=CL_JSMv3.1.58.0"
Of course apikey is... key : without it, or with any other value, that do not work anymore...
What I can say is that
- if we remove xnlp=... it works exactly the same. At least today...
- if we remove the "&features=pois%3Aall"... that do not change (almost) anything : Pois are nevertheless displayed, with very little and rare differences in their name. Sometimes, one Poi is not displayed when parameter is missing, but most of them are displayed. Probably other values may exist for feature=, ... but I don't know them
- if we remove lang= all names are displayed in their native language (Rome in Italy becomes Roma, and Londres in UK becomes London), and if we set lang=en, all names are in english, etc...
- ppi= is relative to text size, and only 100 and 200 seem to be working. 100 being the default value, since same result if ppi= is completely removed
About the two "size" parameters, it's strange. Both of them accept only the values 256 and 512 (256 being the default value, if parameter is missing).
But the 1st parameter tileSize= do not change anything (at least in MOBAC) whatever its value is 256 or 512.
While the 2nd parameter size= actually drives the size of... generated tiles...
Atlases generated with both size (256 and 512) work the same in OruxMaps, but with size=512 it's like if a numeric zoom of 2x was applied (and of course, the generated atlas is twice larger or even more)
On the other hand, with size=512, texts are proportionally twice little than with size=256 (and vice versa)
According to me, the best is to set both to 256... or remove the two parameters, since 256 is the default value.
Last edit: Laurent Grenet 2024-11-14
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Quelqu'un peut-il tenter de faire un .bsh de la vue satellite/hybride du site HERE we go (ancien nokia maps)
https://wego.here.com/p/here%3Acm%3Anamedplace%3A20061916?map=49.06222,1.43015,18
Merci d'avance!
Not exactly the requested maps, since they are vector maps (and I don't even know if it's possible to get vector tiles in MOBAC), but their equivalent raster (accessible from the map you shown us, in the layer selection window).
I don't know if raster tiles are exactly identical to vector tiles, but they look at least very similar...
The URL I put in these bsh (that comes from the one in Web Access to the map) are for some of them quite obvious, like "&lang=fr", but some other are not really understandable, like "xnlp=CL_JSMv3.1.58.0"
Of course apikey is... key : without it, or with any other value, that do not work anymore...
What I can say is that
- if we remove xnlp=... it works exactly the same. At least today...
- if we remove the "&features=pois%3Aall"... that do not change (almost) anything : Pois are nevertheless displayed, with very little and rare differences in their name. Sometimes, one Poi is not displayed when parameter is missing, but most of them are displayed. Probably other values may exist for feature=, ... but I don't know them
- if we remove lang= all names are displayed in their native language (Rome in Italy becomes Roma, and Londres in UK becomes London), and if we set lang=en, all names are in english, etc...
- ppi= is relative to text size, and only 100 and 200 seem to be working. 100 being the default value, since same result if ppi= is completely removed
About the two "size" parameters, it's strange. Both of them accept only the values 256 and 512 (256 being the default value, if parameter is missing).
But the 1st parameter tileSize= do not change anything (at least in MOBAC) whatever its value is 256 or 512.
While the 2nd parameter size= actually drives the size of... generated tiles...
Atlases generated with both size (256 and 512) work the same in OruxMaps, but with size=512 it's like if a numeric zoom of 2x was applied (and of course, the generated atlas is twice larger or even more)
On the other hand, with size=512, texts are proportionally twice little than with size=256 (and vice versa)
According to me, the best is to set both to 256... or remove the two parameters, since 256 is the default value.
Last edit: Laurent Grenet 2024-11-14
Merci beaucoup!