﻿id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
21432	[WIP PATCH] Tile images so that we can zoom in to full resolution	taylor.smock	taylor.smock	"I'm using an undocumented Mapillary API for inspiration for this. I won't be using the API in the Mapillary plugin (yet -- I'm going to ask them if they can make the API documented and public, specifically for 360 images). Undocumented api looks like this: `/<image_id>/tiles?z=<zoom>&fields=url,z,x,y`.

Example responses:
* Image 514627522880380
{{{#!json
{""width"":3840,""height"":2160,""id"":""514627522880380""}
}}}
{{{#!json
{
  ""data"": [
    {
      ""url"": ""https://example.com"",
      ""z"": 11,
      ""x"": 0,
      ""y"": 0
    },
    {
      ""url"": ""https://example.com"",
      ""z"": 11,
      ""x"": 1,
      ""y"": 0
    },
    {
      ""url"": ""https://example.com"",
      ""z"": 11,
      ""x"": 0,
      ""y"": 1
    },
    {
      ""url"": ""https://example.com"",
      ""z"": 11,
      ""x"": 1,
      ""y"": 1
    }
  ]
}

}}}
{{{#!json
{
  ""data"": [
    {
      ""url"": ""https://example.com"",
      ""z"": 12,
      ""x"": 0,
      ""y"": 0
    },
    {
      ""url"": ""https://example.com"",
      ""z"": 12,
      ""x"": 1,
      ""y"": 0
    },
    {
      ""url"": ""https://example.com"",
      ""z"": 12,
      ""x"": 2,
      ""y"": 0
    },
    {
      ""url"": ""https://example.com"",
      ""z"": 12,
      ""x"": 3,
      ""y"": 0
    },
    {
      ""url"": ""https://example.com"",
      ""z"": 12,
      ""x"": 0,
      ""y"": 1
    },
    {
      ""url"": ""https://example.com"",
      ""z"": 12,
      ""x"": 1,
      ""y"": 1
    },
    {
      ""url"": ""https://example.com"",
      ""z"": 12,
      ""x"": 2,
      ""y"": 1
    },
    {
      ""url"": ""https://example.com"",
      ""z"": 12,
      ""x"": 3,
      ""y"": 1
    },
    {
      ""url"": ""https://example.com"",
      ""z"": 12,
      ""x"": 0,
      ""y"": 2
    },
    {
      ""url"": ""https://example.com"",
      ""z"": 12,
      ""x"": 1,
      ""y"": 2
    },
    {
      ""url"": ""https://example.com"",
      ""z"": 12,
      ""x"": 2,
      ""y"": 2
    },
    {
      ""url"": ""https://example.com"",
      ""z"": 12,
      ""x"": 3,
      ""y"": 2
    }
  ]
}
}}}

The returned images are 1024x1024, except for those on the bottom/left edges.

At zoom 11, we have a 1x1 return, with a maximum size of 1024x1024.

(0, 1) and (1, 1) is 1024 × 64.
This indicates that the height for the tiled images is 1024 + 64, or 1088.

At zoom 12, we have a 4x3 return, with a maximum size of 4096x3072 (width x height). This is ""full resolution"".
(3, 2) is 768 × 112.

From this, we see that the maximum size doubles between z11 and z12. Conveniently, 2^zoom^ == max size (2^11^ = 2048, 2^12^ = 4096).

For JOSM internal use, we might want to use 256x256 (I think the imagery tiles use that)."	enhancement	assigned	normal	Longterm	Core image mapping			tile zoom	StephaneP
