Override Automatic Scaling of Intersected Maps
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 Dev has deployed the capability and the Content Team (Tak) has set scales 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 -
VancouverTech/Groups -
VancouverTech/Media -
VancouverTech/Companies -
VancouverTech/Companies/Web Design -
VancouverTech/Companies/Hardware -
VancouverTech/Companies/Graphic Design -
SeattleTech/Groups -
SeattleTech/Media -
SeattleTech/Companies -
SeattleTech/Companies/Web_2.0 -
SeattleTech/Companies/Law Firms -
SeattleTech/Companies/Marketing -
PortlandTech/Groups/Organizations
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:
<address_intersect lat="37.351601" lon="-121.924896" zoom="10">PortlandTech, Web 2.0</address_intersect>
- If lat, lon and/or zoom are specified, their respective values will be used and not the default.
- 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.
Related Issues
- I was testing something else out and noticed that the intersected maps don't show up at all when Javascript ISN'T enabled (which makes sense). The resulting white space is a little annoying/confusing. How difficult would it be to have in this case a bordered box that says, "turn on Javascript to see the map" just so that users knew there was something that was missing? -- TakKendrick
