It's working. It'll probably be as ugly as sin (I'm still experimenting with colour/possible gamma settings), but here it is : http://www.paris-promenades.com/pp_tp/index_numto0x.html .
...as long as I remain consistant in my method (using 0x000360, 360 as a hue) I can tweak the colours to a satisfactory result, but there ~does~ seem to be some sort of 'gamma factor' in play here: all modifications I make seem to be 'applied' to the base values of the existing Google styledMap options: my changes do not replace them completely. For example, a '0x000021' hue applied to transit lines (that seem to have only saturation and lightness options set (to make grey), I get orange (the 'default' hue seems to be red - seen in my other example where only the raised ssaturation/lightness options were working), whereas applying the same hue to roadways gives me green. Still tweaking. On Aug 24, 3:37 am, William <[email protected]> wrote: > On Aug 24, 9:38 am, Sefu <[email protected]> wrote:> The '#' problem > is still unsolved, but I managed to figure out the > > correct way of using the '0x' alternative... with the 'degree' > > declaration in HSL values (#ff0000, at 1º, would be 0x000001 - don't > > know the reason for those three leading 0's). > > Good work! Now we are making real progress ... removing the hex and # > altogether, I just tried simple hue values like hue: "60" for yellow, > "120" for green, "180" for cyan, "240" for blue etc. Or the transit > line example from your webpage, { hue: #ff9100 { is { hue: "34" } > > .... -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
