Hi, there; 

  As I'm reading one of the articles on the code front page 
(http://googlegeodevelopers.blogspot.com/2011/05/turn-up-power-of-your-fusion-tables.html)
 
I'm thinking that the new direction of how Maps and FusionTables interact is 
incompatible with my (just went live last week) Boise State Campus Map 
<http://maps.boisestate.edu>, and I thought I might ask for some ideas.

   In particular, the layer limit is going to provide a challenge for me.  I 
currently have four conceptually distinct layers (buildings, parking, 
'other', and WiFi coverage), and the first three each have at least three 
individually selectable subcategories which might generate their own layer. 
  It's pretty easy to exceed 5 layers.   Currently, if I select 7 or more 
layers, the map goes blank, but we decided that was a low enough occurrence 
event to live with for now.  The real solution is to have the FusionTable 
query language support 'OR', but that's a discussion in a different forum. 

   What I would like in this discussion are ideas how I can take my FT layer 
data and style it so I don't take away from what I have already delivered.  
I'm sure there are methods, but I'm not seeing them immediately.  

    Some of my data is point only, some is polygon, or polyline only, and 
about 1/3 consists of a polygon with an associated marker point.   Generally 
I render the polygons with an FT query layer, and the markers with a 
visualization query from FT so I can have custom markers.  I do this as a 
compromise between the simplicity and speed of a pure FusionTable solution, 
but without marker customization, and rendering each feature individually, 
with the attendant performance hit on older systems and possibly running 
into the feature count limit as well. 

    My first thought was to treat the polygons as the dynamically styled 
layer, but there are more than the limit of 5 styles already represented, so 
that would lead to a reduction of display.  Also, the problem only gets 
worse as additional conceptually distinct layers are requested.  As an 
example, the map currently doesn't show how the limits of the campus 
no-smoking area, and that shouldn't be shown by default to avoid visual 
confusion.   Further thought just takes me nowhere.

   So, dear readers:  Any ideas? 

best regards, 
Joe

    

    

-- 
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.

Reply via email to