Closed (works as designed)
Project:
Openlayers
Version:
7.x-3.x-dev
Component:
OL Views
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
14 Dec 2011 at 13:36 UTC
Updated:
10 Mar 2014 at 10:12 UTC
Jump to comment: Most recent
Comments
Comment #1
zzolo commentedHey @philippejadin.
There is client side clustering in this module as provided by the OL library. But, its not very robust, and you will still run into problems client-side with that much data.
There is no integration with bounding box and live pull from Views. This is slowly in the works, integrating with the views_geojson module, as this is the most natural way to do this in the OL library.
But, overall, the API for this module is fairly robust enough for you to make this happen with custom code.
Comment #2
philippejadin commentedThank you for this anwer.
Would you think that using only openlayers + a custom sql query on the database would be simple and to the point?
I fear that the stack of views + geojson + geojson view + custom glue code would be unnecessary and very slow for each map move by the end user.
A single sql query can return the nodes in a specific bounding box area with their ID and titles, this is much simplier imho.
Comment #3
nod_If you have something working, by all means have a look at #1360260: Add views filter to provide proximity search of Geofields :)
Comment #4
kloewer commentedWe are having about the same issue of displaying 1.500 Entries on a map.
How did you fix this?
Comment #5
dasjosee #1547610: Plan server-side geo clustering for drupal 7
Comment #6
ifrikUsing postcodes: Depending on how large the area of a postcode is, you could filter on the postcode and only display nodes that have the same postcode. The same goes for additional regions (e.g. provinces, councils - depending on the existing administrative borders). That would reduce the number of nodes to be displayed, which could then be clustered (using your map's behaviour settings).
If the postcodes cover only small areas you could check whether this support request has helpful ideas: https://drupal.org/node/1735210
From a user point of you: I suppose the users will never actually use a map that displays all 20.000 nodes anyway so maybe it is more useful anyway to start on a more focused map?
Comment #7
batje commentedThe proposed solutions should give you a way forward:
Client side clustering
Server side clustering
Filtering the results
Or, of course, combinations of these.