Block *.yandex.net imagery

[deevroman]

Problem

Yandex Maps satellite images are not allowed to be used in OSM

Description

Example of use:

https://www.openstreetmap.org/changeset/147580817

The domain on which they are located is:
https://core-sat.maps.yandex.net/tiles?.....

In addition, Yandex has the Tiles API, which should also be blocked:

https://yandex.ru/dev/tiles/doc/ru/quickstart

https://tiles.api-maps.yandex.ru/....

Screenshots

No response

[tomhughes]

This is an operational issue, not a web site issue.

[tomhughes]

Requests to change the imagery blacklist need to come from DWG as described in openstreetmap/chef#623.

[grischard]

In the DWG chat, one comment was that if there's a block, it should be on *.maps.yandex.net because they have file hosting, image hosting etc. on that domain that has nothing to do with their maps.

[AntonKhorev]

When using yandex.ru/maps/

https://core-sat.maps.yandex.net/ = aerial imagery
https://core-renderer-tiles.maps.yandex.net/ = map tiles
other kind of tiles are also under maps.yandex.net

[talllguy]

It does not appear that yandex is in the imagery index, though it was proposed once here.

[pnorman]

In the DWG chat, one comment was that if there's a block, it should be on *.maps.yandex.net because they have file hosting, image hosting etc. on that domain that has nothing to do with their maps.

Has the DWG decided to request a change to the blacklist?

[grischard]

Green light from dwg for blocklisting:

*.api-maps.yandex.ru
*.maps.yandex.net

[tomhughes]

I thought @AntonKhorev said all the actual map tiles were under the maps.yandex.net domain?

[tomhughes]

Actually maybe I misunderstood what he was saying... Blocked both in openstreetmap/chef@92d4fd1.

[AntonKhorev]

maps.yandex.net has all tiles as used by the official yandex map app

api-maps.yandex.ru has tiles that anyone with an api key can use