update mosaicJSON.bounds type to tuple(float, float, float, float)

[vincentsarago]

The only way to enforce a list to be a 4 element object is by using Tuple and that's why we define bounds in rio-tiler as
tuple(float, float, float, float) (e.g. https://github.com/cogeotiff/rio-tiler/blob/a10a8c5be8b067dd3ecc72e76bfd740a2b3213c9/rio_tiler/io/base.py#L37)

In the mosaic model we are a bit too permissive with List[float]

cogeo-mosaic/cogeo_mosaic/mosaic.py

Line 69 in 7d01981

bounds: List[float] = Field([-180, -90, 180, 90])

Changing to Tuple[Float, Float, Float, Float] won't change how the object is stored on the json document

json.dumps((1,1,1,1))
'[1, 1, 1, 1]'

[kylebarron]

Unless you want three-dimensional bounds with a 6-element iterable 😉