Override Automatic Scaling of Intersected Maps
Revision as of 20:23, 6 February 2008 by TakKendrick (talk | contribs) (initial dev task, worked through with Ward, and some of the needs that came out of the Oldcastle project)
<noinclude><big>[[OurWork]] < [[DevelopmentTeam]] < [[DevelopmentTeamPriorities|Priorities]] < </noinclude>[[{{subst:PAGENAME}}]] {{JustTinyEditIcon|{{subst:PAGENAME}}}}<noinclude></big> __NOTOC__ == What (summary) == Intersected Maps are currently centering based on an average location of all the point, and setting a default scale that works well on a regional level, but not on a national or global level (like we'll need for Oldcastle). The problem is when there's one or two extreme outliers, the map ends up centering on a location where their isn't any points at all. == Why this is important == Critical to the development of paying customers PortlandTech and Oldcastle (as well as developing technology for future portal sponsors). '''We've promised this functionality to Oldcastle.''' == [[DoneDone]] == DoneDone when scales have been set for pages like [[LASIK Centers in Manhattan, NY]], and the map correctly centers on Manhattan, Pages we know are throwing outliers into the maps: * [[TLCVision.com]] on [[LASIK Centers in Manhattan, NY]] == Steps to get to [[DoneDone]] == A couple of suggested changes: * As part of the address intersect call, we can pass a set of coordinates (lat, long) to it which dictates the "center" as well as the "zoom" level. If no coordinates/zoom level are specified, it does it's current "center on average" and zoom level. For example, we'd like to say specifically: <pre><address_intersect lat="37.351601" lon="-121.924896" zoom="10">PortlandTech, Web 2.0</address_intersect></pre> * Alternatively, the map excludes extreme outliers. Again, maybe there is a coordinate that says, "this is Portland" and it averages based on anything in a 30 mile radius of that coordinate. [[Category:DevelopmentTask]] </noinclude>