bounds

[mapsam]

This adds the bounds field to the Structure section, and includes some added text (in bold) from the current description:

The maximum extent of available map tiles. Bounds MUST define an area covered by all zoom levels. The bounds are represented in WGS:84 latitude and longitude values, in the order left, bottom, right, top. Values may be integers or floating point numbers. The minimum/maximum values for longitude and latitude are -180/180 and -90/90 respectively. Bounds MUST NOT "wrap" around the ante-meridian. If bounds are not present, the default value assumes the set of tiles is globally distributed.

The new addition covers questions from #25 and #23 at least for the v3 perspective, but they could be redefined in v4

cc @GretaCB

[GretaCB]

@mapsam

If bounds are not present, the default value assumes the set of tiles is globally distributed.

Per #37 (comment), should this specify MAY assume...?

[mapsam]

@GretaCB yes! Changing to

If bounds are not present, the default value MAY assume the set of tiles is globally distributed.

[GretaCB]

If bounds are not present, the default value assumes the set of tiles is globally distributed.

@mapsam Per the default value convo, how bout...

If bounds are not present, the default value MAY assume the set of tiles is globally distributed.

[GretaCB]

oh my goodness, de ja vous. Please disregard the comment above @mapsam . Seeing it was addressed per #39 (comment)

[mapsam]

@GretaCB no worries! A good reminder that including the text in the initial comment isn't terribly helpful after making updates 😄