here-ios-sdk-examples
here-ios-sdk-examples copied to clipboard
Issue to change style of water areas
Hi, it seems to me there's an issue with the style of water area (water0m, water3000m, river, lake, ocean...).
Describe the bug All the "water" zones are only applied after zooming out to a level of 6 and below not matter the zoom level provided to the color property definition.
Steps To Reproduce Steps to reproduce the behavior:
- take the example "map-customization-ios-swift" (I only change the property name and the geo+zoom to provided a meaningful and correct example)
- change color property to water0m
if map.getCustomizableScheme(floatSchemeName) != nil {
//it is not allowed to remove map scheme which is active.
//set to other map scheme then remove.
map.mapScheme = NMAMapSchemeNormalDay
map.removeCustomizableScheme(floatSchemeName)
}
//create customizable scheme with specific scheme name based on NMAMapSchemeNormalDay
if (colorScheme == nil) {
colorScheme = map.createCustomizableScheme(colorSchemeName, basedOn: NMAMapSchemeNormalDay)
}
let waterColor0m = colorScheme?.colorForProperty(NMASchemeColorProperty.waterColor0m, zoomLevel: 13.0)
waterColor0m?.red = 100
waterColor0m?.green = 100
waterColor0m?.blue = 133
//set color property
if let color = waterColor0m {
colorScheme?.setColorProperty(color, zoomRange: zoom)
}
//set map scheme to be customized scheme
map.mapScheme = colorSchemeName
map.set(geoCenter: NMAGeoCoordinates(latitude: 51.029138, longitude: 1.2032643), zoomLevel: 13, animation: NMAMapAnimation.none)
- The color is not applied
- Zoom out to at least a level of 6, the color is applied
Expected behavior
The water color should be changed instead of keeping the default color of the water0m from the NMAMapSchemeNormalDay
scheme.
Screenshots
ZOOM LEVEL 13:
ZOOME LEVEL 6:
Smartphone (please complete the following information):
- Device: iPhone 12 pro
- OS: iOS 14.6
- SDK Version: 3.18.4
Additional context Same issue happening on simulator and on the current Android version of the SDK
Thank you !
Hi @havenS, thanks for reporting and detailed description. Will create internal ticket for investigation and fix.