Class: GeoServerInfoResponse

bemap.GeoServerInfoResponse()

new GeoServerInfoResponse()

BeNomad BeMap JavaScript API - GeoServerInfoResponse Response from `POST service/geoServerInfo/1.0` — the metadata for the geoserver named in the request: the list of services it exposes, the supported travel modes, the per-service resource limits, plus the copyright and supplier-terms strings the customer application is required to display. Wire shape (verified against a live beta response): { "availableGeoServerNames": ["osm","addok","here","nominatim"], "globalCopyright": "Here Maps 2026.1", "globalCopyrightUrl": "https://company.here.com/here/", "globalSupplierTerms": "Supplier Terms Applicable to Location Content", "globalSupplierTermsUrl": "http://corporate.navteq.com/supplier_terms.html", "transportTypes": ["PEDESTRIAN","BICYCLE","MOTORCYCLE","CAR",...], "truckAttributes": true, "servicesInfo": [{ fieldName, serviceName, title, description }, ...], "serviceLimits": [{ serviceName, key, argument, type, value, unit }, ...] }
Since:
  • 1.5.0
Source:

Methods

getLimitsForService(serviceName) → {Array.<bemap.GeoServerServiceLimit>}

All limits attached to the named server-side service. Returns `[]` if none. info.getLimitsForService('BenomadNearPoiService')
Parameters:
Name Type Description
serviceName String Server-side bean name (e.g. `'BenomadNearPoiService'`).
Source:
Returns:
Type
Array.<bemap.GeoServerServiceLimit>

hasService(serviceName) → {Boolean}

`true` when the selected geoserver exposes the named service. info.hasService('Routing') // true / false info.hasService('NearPoi') // true / false
Parameters:
Name Type Description
serviceName String As emitted by the server (`'Routing'`, `'Geocoding'`, `'NearPoi'`, ...).
Source:
Returns:
Type
Boolean

supportsTransport(transportType) → {Boolean}

`true` when the selected geoserver supports the named travel mode. info.supportsTransport(bemap.TransportMode.TRUCK) // true on 'here'
Parameters:
Name Type Description
transportType String
Source:
Returns:
Type
Boolean