node limitiations and multiple node location maps
andre75 - January 16, 2007 - 18:35
| Project: | GMap Module |
| Version: | 4.7.x-1.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | won't fix |
Jump to:
Description
I am still having lots of trouble with the node location map. I have maxed out my hosts mysql query limit when the GMAP module went beyond 700 queries:
http://www.opentravelinfo.com/map.html
For some reason I cannot get new nodes in anymore. Even though I have cached the page, i cannot recreate it with more nodes.
So I was wondering if there is a way to avoid having to look up all nodes that are on the map.
If that is not possible, I would like to split the map up into continents.
I would like to create multiple node location pages, each showing one complete continent (not loading all the others).
How can I make multiple continent pages instead of one large one that contains it all. In the admin menu of GMAP I can only set one location.
#1
have you tried turning on the clustering option? It will group nodes in close proximity into one marker until you zoom in to a closer distance - then it will show more of them
#2
Yes. I have selected "Enable clusterer.js" and I have Google map method: Dynamic
Its still far too much.
I have thought about this a little, and I was wondering if it would be possible to have a special gmap cache system, that duplicates the teaser and the link to the node. This way there is no need to load the complete node. This would also significantly speed up loading times for a large number of nodes.
Most of my nodes are book page type (don't know if that makes a difference).
#3
Um, I don't want to beat a dead horse, but is there any idea how to fix this?
#4
ok i'm having the same issue as well now but it could be a case of lack of memory to deal with the query - i'm in the process of setting up a dedicated server so i'll let you know what happens after i move everything - its going to be 2 weeks min
#5
This is wontfix for 4.7.
5.x-dev has MASSIVE improvements for the node map, but still is inefficient if you have a LOT of data... Perhaps a kml superoverlay would work... (Don't know how to go about generating one, though...)