MAPBOX_MAP_ID - Detailed description

Overview

Parameter:MAPBOX_MAP_ID
Category: OpenStreetMaps
Default value: mapbox.light
Product: eTASK.Other (OpenStreetMaps)

What does this parameter do?

This parameter determines the visual design and map style for all OpenStreetMap maps displayed in the eTASK FM portal. It specifies which predefined Mapbox map design is used—ranging from classic street maps to light and dark variants, as well as satellite or thematic views.

What is this parameter used for?

• Building Map Display: Determines the appearance of the map in the building form

• Portfolio overview: Defines the map style for the geographic portfolio view

• Uniform design: Ensures consistent map display throughout the portal

• User-friendliness: Enables customization to user preferences and corporate design

• Readability: Optimizes map readability depending on the use case (e.g., light background for better contrast)

Technical Details (for Administrators)

Format: Text string (predefined Mapbox Map ID)
Default value: mapbox.light

Valid values:

• mapbox.streets = Classic street map with detailed streets and labels

• mapbox.light = Light, simplified map with good contrast (default)

• mapbox.dark = Dark version for modern user interfaces

• mapbox.satellite = Satellite image view

• mapbox.streets-satellite = Combination of street map and satellite image

• mapbox.wheatpaste = Stylized poster look

• mapbox.streets-basic = Simplified street map

• mapbox.comic = Comic-style design

• mapbox.outdoors = Optimized for outdoor areas and topography

• mapbox.run-bike-hike = Specifically for paths and routes

• mapbox.pencil = Hand-drawn style

• mapbox.pirates = Vintage map style

• mapbox.emerald = Green color scheme

• mapbox.high-contrast = High contrast for better readability

Important notes:

• This setting affects all map views in the portal

• Changes will be visible immediately the next time a map is loaded

• Not all Map IDs are available in all Mapbox versions

• For more information on available styles: https://www.mapbox.com/developers/api/maps/#mapids

Interaction with other parameters:

• MAPBOX_ACCESS_TOKEN: Must be configured for maps to be displayed at all

• MAPBOX_STYLE: Alternative method for defining the style (if set, it overrides MAPBOX_MAP_ID)

• MAPQUEST_APP_KEY: Required for address search and geocoding

When should you change this value?

Change the value (select a different map style) if:

• The default design does not match your corporate design

• You want better readability through a different contrast

• Special requirements such as Dark Mode need to be implemented

• Satellite or hybrid view is more appropriate for specific use cases

Keep the default value (mapbox.light) if:

• The current display is functional and easy to read

• There are no specific design requirements

• You are in a test or development environment

• No decision has yet been made regarding the final design

Important Notes

1. Impact on all maps
   Changing this parameter affects all map displays in the portal simultaneously. It is not possible to use different map styles for different areas.

2. Preview before going live First
   test new map styles in a test or development environment to ensure readability and usability.

3. Check availability
   Not all Map IDs are available in all Mapbox plan versions or API versions. Check the current Mapbox documentation if you encounter issues.

4. Consider contrast
   Ensure that map markers (red pins for buildings) remain clearly visible on the selected background. Dark maps can cause issues here.

5. MAPBOX_STYLE as an alternative
   For advanced customization, you can use the MAPBOX_STYLE parameter, which allows for custom Mapbox styles. This overrides MAPBOX_MAP_ID.

Security

Does changing this parameter affect security?

No, this parameter has no direct security implications.

Practical example

Initial situation: A facility management company uses the eTASK portal with the default map style mapbox.light. The portal has a dark corporate design featuring primarily dark blue and gray tones. The light map display appears jarring in this design context and does not match the rest of the user interface.

Configuration: The administrator changes the parameter to a darker style:

After the change:

• All maps in the portal (building form, portfolio overview, etc.) now display a dark background

• The map display blends harmoniously into the dark corporate design

• Streets and labels are displayed in light colors on a dark background

• The red pins for buildings remain clearly visible against the dark background

• The visual appearance of the entire portal now appears consistent

Result: Users perceive the portal as having a unified design. The maps no longer appear out of place in the design. Positive feedback on the improved aesthetics. No negative impact on functionality or readability.

Alternative scenarios:

Scenario A – Satellite image for outdoor areas:

• Companies with large outdoor areas (parks, industrial sites)

• MAPBOX_MAP_ID = mapbox.satellite

• Advantage: Realistic view of the actual terrain structures

• Disadvantage: Street names and labels are missing

Scenario B – Hybrid for optimal orientation:

• Combination desired

• MAPBOX_MAP_ID = mapbox.streets-satellite

• Advantage: Satellite image with street names and labels

• Ideal for detailed route planning

Recommended setting

For standard installations:mapbox.light(light standard map)

Reason:

• Proven standard with good readability

• High contrast for clear orientation

• Works in most design contexts

• Low resource consumption

• Universally applicable for all use cases

For portals with a dark design:mapbox.dark for a consistent look

For special requirements: - Outdoor facility management: mapbox.satellite or mapbox.streets-satellite - High accessibility: mapbox.high-contrast - Outdoor/site: mapbox.outdoors

Tip: Get feedback from your users before changing the map style in the production environment. What looks good to administrators may not necessarily meet the expectations of everyday users.