It sounds like your colors.tsv file is not being used. Since this field only contains numeric values, it may be automatically assigned to a “continuous” type and it’s not currently possible to specify colors for continuous data.
My suggestion would be to specifically designate this field to the “ordinal” coloring type within your Auspice config JSON. Then the colors from your colors.tsv will be applied. The values in your colors.tsv should exactly match the values in your auspice.json, so the correct value should be 0.0.
@duxx could you post the section of the auspice config file which specifies this (if you have one) or (even better) the dataset JSON if it’s public?
You imply the non-zero values are using the hex codes you provide, so my guess is that there’s a in augur/auspice which is treating the zero as a falsy (i.e. invalid) value and that’s why it’s not working.
I don’t think my colors.tsv is not applied. because only 0 value is not applied, the other values are all applied.
I tried continuous type on coloring section, then auspice generate a new legend below.
mine was 0 0.05 0.1 0.15…
but auspice generate 0 0.111 0.222 0.333…
That’s not what I want anyway.
Thank you for your answer.
You imply the non-zero values are using the hex codes you provide, so my guess is that there’s a in augur/auspice which is treating the zero as a falsy (i.e. invalid) value and that’s why it’s not working.
in augur/auspice which is treating the zero as a falsy (i.e. invalid) value and that’s why it’s not working.