Alternatives to GetFeatureInfo in overview of the core

[joanma747]

Explain that the modular APIs allow for combining modules for OGC API Features and OGC API Coverage to get the same functionality.

Add an explanation in "Overview/Relationship to other OGC API standards"
"In order to offer an equivalent mechanism of GetFeatureInfo you should implement this and that requirements class in the OGC API this and that..."
For collections that offer items:
I/J should be transformed to long/lat WGS84 in the client side and support the BBOX query of a single point like the /collections/{collectionId}/items?bbox=lon,lat,lon,lat
For collections that are offered as coverages:
/collections/{collectionId}/coverage?bbox=lon,lat,lon,lat
(opengeospatial/ogcapi-coverages#112)

[joanma747]

remove "d" and add a note on deltas.

[joanma747]

Add a comment on when to use maps and when to use tiles. (in relation to dynamic maps and vector tiles.

[joanma747]

Done on regular telco