I am FINALLY getting a chance to test this with real data and using a color coder. I used latest versions of FF, IE, Chrome. All of my polygons are simple four sided rectangles. All of my points are centroids of the polygons. I do not have any relevant polylines to test with. The four new settings work fine. A few other observations...
Test exhibit: http://dev.dgs.udel.edu/sites/maps/pubex.html 1) The bottom border is not displaying. The left, top, and right border are. 2) The legend (usually at the bottom of the map with point markers) is not appearing. Can we display some type of legend, either identical to the markers (balloons) or small squares? 3) On the map view showing both points and polys, the onclick event is not working for the polys. When that view is displayed, it prevents the onclick events from the other map views. It works fine when clicking the markers. Not sure why. Could be because the same item has both a point and polygon associated with it. Nothing good from Firebug. 4) The color coder is not working in Chrome. 5) The ordering of the polygons is important. The larger polygons should be displayed first (in the back) and smaller ones on top. In my example, it's displayed that way as my data feed is sorted by size. You could probably compute the cartesian area in pixels by using polygon.GBounds (or spherical area using GLatLngBounds but cartesian will do and perform better.) - John David Huynh wrote: > Hi all, > > Another new feature to check out / test is the support for polygons and > polylines together with point markers on a single map view: > > > http://trunk.simile-widgets.org/exhibit/examples/polymap/medieval-mediterranean.html > (data from John Saul) > > http://trunk.simile-widgets.org/exhibit/examples/polymap/election08.html > > The 3 walls on the first map are click-able. > > In addition to > ex:latlng=" expression " > you can also specify > ex:polygon=" expression " > ex:polyline=" expression " > Polygons and polylines must be in different properties than lat/lng > points, and each polygon or polyline is specified as a semicolon > separated string of lat/lng pairs, e.g., > > "43.773263,11.255505;43.773325,11.256141;43.773067,11.256157;43.773005,11.255497" > If your data happens to use something other than semicolons, say |, then > you can set the separator like so > ex:latlngPairSeparator="|" > If your lat/lng pairs happen to be lng/lat instead, you can also specify > that > ex:latlngOrder="lnglat" > > There are 4 more new settings > borderOpacity: default to 0.5 > borderWidth: default to 1 > borderColor: default to the color setting, or whatever that a color > coder specifies > opacity: for polygons' fills, default to 0.7 > > If you want to try it on your own exhibit, link to this API > http://trunk.simile-widgets.org/exhibit/api/exhibit-api.js > > Thanks, > > David > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SIMILE Widgets" 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/simile-widgets?hl=en -~----------~----~----~----~------~----~------~--~---
