Use <map-featurecaption> as the feature label and accessible name by default

[prushforth]

If a <map-feature> contains a <map-featurecaption>, the feature should be visually labelled, using map text label defaults built into the user agent stylesheet, amended by the user stylesheet and potentially customized by the server-provided style rules found in <map-link rel=stylesheet> and <map-style>.

The <map-geometry> should be used to control the label placement algorithm.

If a feature is tiled into parts, it should be possible to merge the geometry parts using a standard attribute name which has a common value across the parts. The label placement algorthim could use the resulting re-assembled geometry as required.

CSS rules could be used to substitute content to be rendered in place of <map-featurecaption>, but <map-featurecaption> would be the "batteries-included" default, which would help accessibility I think.

[AliyanH]

As discussed, possible overlapping problems may exist with this approach:

Similarly, when zoomed out, we will face the issue of improper label size since no media query exists yet to incorporate map scale which would be used to adjust size accordingly.

[prushforth]

There are going to be challenges, but it should be possible to have a default rendering heuristic perhaps. For example, a <map-feature> has a zoom attribute aka native zoom, and perhaps we could limit the default rendering to that zoom value.

As far as overlapping labels goes, yes, this would require some label collision detection logic to be built into the renderer I guess.

Good to keep discussing what might be involved for now.

[prushforth]

For consideration https://en.wikipedia.org/wiki/Automatic_label_placement