-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression in color property styling between 0.32.x and 0.33.x #4496
Comments
The same happened to a couple of my styles where I was using a function colour value for no data. There was a new feature in v33.0: 'Add ability to specify default property value for undefined or invalid property values used in property functions. #4175' Before v33: After v33: |
Reduced test case:
It's not a categorical function, so at first glance #4175 isn't related. |
The Can you change the data source to use numeric values for this property? |
Thanks @jfirebaugh for looking into this! I could not figure out why one of my layers worked and not the other. I will convert my properties to numerical values. When Studio updates to 0.34+ it will make it easier to spot those issues. I'm closing since this is the expected behavior. |
mapbox-gl-js version: 0.34.0
Steps to Trigger Behavior
Expected Behavior
The rendering should match the result seen on Studio.
Actual Behavior
Some of the layers with property function coloring are rendered in black (#000000) instead of the desired function.
For those layers, other property styling works as intended (e.g. radius).
Some other layers of similar type are rendered correctly. Trying to turn compositing on or off did not have any effect.
The only example I have of this bug is the link posted above. Sorry if the data is messy!
v0.33 - v0.34


v0.25 - v0.32
The text was updated successfully, but these errors were encountered: