Tile Service Creation

[lossyrob]

The Tile Service Creation API endpoint takes a request with a list of images, and a unique identifier.

This will submit the workflow to SWF for that tiling job.

{
    // REQUIRED: ID for the tile service being created
    // MUST BE UNIQUE
    "id" : "55b671ac2b67227a79b4f3fb",

    // REQUIRED: List of s3 URIs to images.
    // Must be from a publicly accessible bucket.
    // The order of the images is the priority of the images in the mosaic, with
    // images higher in the list being higher priority than images lower in the list.
    // So if a pixel is covered by more than one image, the image higher in the list
    // will have it's pixel shown.
    // Images must be RGB GeoTiffs with the format specified by OIN.
    images : [
        "http://hotosm-oam.s3.amazonaws.com/356f564e3a0dc9d15553c17cf4583f21-9.tif",
        "http://hotosm-oam.s3.amazonaws.com/356f564e3a0dc9d15553c17cf4583f21-24.tif",
        "http://hotosm-oam.s3.amazonaws.com/356f564e3a0dc9d15553c17cf4583f21-20.tif"
    ]
}

[mojodna]

id should be assigned by the server and returned for use as a token to determine status and refer to the tile service.

@tassia notes that the QGIS plugin has metadata available for all images, so if we want to support optional info about file size / image dimensions / resolution (to help estimate how large the tiling job is), that's possible.