geoview-core - v2.2.0
    Preparing search index...

    Class LegendsLayerSet

    A Layer-set working with the LayerSetController at handling a result set of registered layers and synchronizing events happening on them (in this case when the layers are going through the layer statuses and legend querying) with a store for UI updates.

    Hierarchy (View Summary)

    Index

    Constructors

    Properties

    controllerRegistry: ControllerRegistry

    The controller registry to work with

    layerDomain: LayerDomain

    The LayerDomain to work with

    mapViewer: MapViewer

    The MapViewer to work with

    The resultSet object as existing in the base class, retyped here as a TypeLegendResultSet

    Methods

    • Processes layer data to query features on it, if the layer path can be queried.

      Parameters

      • geoviewLayer: AbstractGVLayer

        The geoview layer

      • queryType: QueryType

        The query type

      • location: TypeLocation

        The location for the query

      • queryGeometry: boolean = true

        Optional whether to query geometry

      • OptionalabortController: AbortController

        Optional abort controller

      Returns Promise<TypeFeatureInfoResult>

      A promise that resolves with the query results

    • Aligns records with information provided by OutFields from layer config.

      This will update fields in and delete unwanted fields from the arrayOfRecords.

      Parameters

      • layerEntryConfig: AbstractBaseLayerEntryConfig

        The layer entry config object

      • arrayOfRecords: TypeFeatureInfoEntry[]

        Features to delete fields from

      Returns void

    • Determines whether the retrieved feature info records contain real attribute fields

      (i.e., key-value properties) or whether they were returned in a fallback HTML/plain-text form, which commonly occurs with WMS GetFeatureInfo responses. This is used primarily to detect when a WMS service cannot return structured feature attributes and instead provides the feature data as a single HTML or plain-text block. Logic summary:

      • For WMS layers (OgcWmsLayerEntryConfig):
        • If the first record contains exactly one property and that property is either html or plain_text, the method considers the response not to contain actual fields.
      • For all other cases, the method assumes records contain valid structured attributes.

      Parameters

      • layerConfig: AbstractBaseLayerEntryConfig

        The layer configuration used to determine whether special WMS handling applies

      • arrayOfRecords: TypeFeatureInfoEntry[]

        The retrieved feature info entries representing attributes or raw text content

      Returns boolean

      true if the feature info records contain real attribute fields; false if they consist only of fallback HTML or plain-text content