Create map-extent, map-input, map-link

[prushforth]

Tests Needed -

• map-extent checked (when no checked attribute present)
• map-extent label default and tests
  • if no label and only one map-extent hidden
  • hidden attribute tests for local and remote
  • testing positions when hiding one of the map-extents and re-adding or what not
• map-extent opacity attribute, check behavior with attribute/container style/ and behavior with how opacity changes through using slider or through API
• Templated feature going out of bounds, layer is disabled (was a bug on main)
• layer- hidden attribute test.

extension - Maps4HTML/mapml-extension#66

docs - Maps4HTML/web-map-doc#135

To Do when developing map-link

• handle query, its bounds, and its ability to be disabled in the layer control
• Create a new function for map-link that gets the min/max zoom limit based on it's inputs, sample code:

_getMinMaxZoom() {
    let input = this.querySelector('map-input[name=zoom]') || this.querySelector("map-meta[name=zoom]") || this.parentLayer.shadowRoot? this.parentLayer.shadowRoot.querySelector("map-meta[name=zoom]") : this.parentLayer.querySelector("map-meta[name=zoom]");
    if (input) {
     //
    } else {
      // use projection fallback
    }
  }

• layer not disabled when out of bounds if it has a query

Bugs that still exists
- Debug Mode - When you check and uncheck a layer in debug mode, the layer bounds don't show up when the layer is checked, but do when layer is unchecked. Behaves oppositely.

Bugs discovered on main

• map-link not respected when zoom changed by doing a zoomTo on a layer #896
• map-input is not respected for a map-extent and the tiles are still fetched at a lower zoom level #897

To Do Before closing PR

• bundle all element support js files into mapml.js (b6991c3)

Closes #886

[AliyanH]

Tests Needed -

• map-extent checked (when no checked attribute present)
• map-extent label default and tests
  • if no label and only one map-extent hidden
  • hidden attribute tests for local and remote
  • testing positions when hiding one of the map-extents and re-adding or what not
• map-extent opacity attribute, check behavior with attribute/container style/ and behavior with how opacity changes through using slider or through API
• Templated feature going out of bounds, layer is disabled (was a bug on main)
• layer- hidden attribute test.

extension -

• locale for dfExtent ("Sub-Layer") needed (Add Sub-layer to messages (for map-extent default label). mapml-extension#66)

docs -

• map-extent label "when an extent does not have a label, it is hidden" is no longer true
  • mapml documentation for attributes, ex. checked="checked" is required for the parser
• Add documentation for hidden attribute for layer to reflect this code for query layers on MapMLLayer.js -> getQueryTemplate:

if (
        this._layerEl.checked &&
        !this._layerEl.hidden &&
        this._mapmlLayerItem
      ) {

• For our API's we learned that they can only be used after the custom element is attached to the DOM. This needs to be reflected on the web-map-doc. Found using the features API experiment.
• Document map-change event for layer- element.
• Document the use of map-meta's inside of map-extents and how they work:

To Do when developing map-link

• handle query, its bounds, and its ability to be disabled in the layer control
• Create a new function for map-link that gets the min/max zoom limit based on it's inputs, sample code:

_getMinMaxZoom() {
    let input = this.querySelector('map-input[name=zoom]') || this.querySelector("map-meta[name=zoom]") || this.parentLayer.shadowRoot? this.parentLayer.shadowRoot.querySelector("map-meta[name=zoom]") : this.parentLayer.querySelector("map-meta[name=zoom]");
    if (input) {
     //
    } else {
      // use projection fallback
    }
  }

• layer not disabled when out of bounds if it has a query

Bugs that still exists
- Debug Mode - When you check and uncheck a layer in debug mode, the layer bounds don't show up when the layer is checked, but do when layer is unchecked. Behaves oppositely.

Bugs discovered on main

• map-link not respected when zoom changed by doing a zoomTo on a layer #896
• map-input is not respected for a map-extent and the tiles are still fetched at a lower zoom level #897

To Do Before closing PR

• bundle all element support js files into mapml.js

[prushforth]

Small issue discovered: when you change a remote, hidden, checked map-extent from checked to not checked in the SD (remove the attribute), then remove the hidden attribute to unhide the extent in the layer control, the extent appears checked in the layer control, and changing the checkbox to unchecked now displays the extent. (discovered in geoserver testing).