Would be great to support markercluster in the geo map

[ungentilgarcon]

https://github.com/Leaflet/Leaflet.markercluster

It makes so much sense, let's think on how it could be setted up in topo

[clemsos]

yes, this should be a priority.

We can use this lib : https://yuzhva.github.io/react-leaflet-markercluster/

[ungentilgarcon]

yeah, it sounds great, but I need you on this

[clemsos]

Yep sure. You can look into this lib that makes easy to use with our actual react app https://github.com/YUzhva/react-leaflet-markercluster <https://github.com/YUzhva/react-leaflet-markercluster>

…

On 2 May 2018, at 16:23, gregory bahde ***@***.***> wrote: yeah, it sounds great, but I need you on this — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#172 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAtXTitu8EKCctgmo1NDT6Tvexua5sVkks5tucFVgaJpZM4Tjj8F>.

[ungentilgarcon]

installing (with meteor npm since npm doesn't find the package ) returns this:
npm WARN leaflet.markercluster@1.3.0 requires a peer of leaflet@~1.0.3 but none was installed.

Also, the code is quite unstable yet

[ungentilgarcon]

full return:

└── UNMET PEER DEPENDENCY leaflet@1.3.1

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/babel-cli/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN leaflet.markercluster@1.3.0 requires a peer of leaflet@~1.0.3 but none was installed.

[clemsos]

What is the version of leaflet installed currently ? npm list | grep leaflet

…

On Thu, May 3, 2018, 8:35 AM gregory bahde ***@***.***> wrote: full return: └── UNMET PEER DEPENDENCY ***@***.*** npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/babel-cli/node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for ***@***.***: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN ***@***.*** requires a peer of leaflet@~1.0.3 but none was installed. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#172 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAtXTgVDAL0minXRVisl69wK_KWWbQL5ks5tuqVNgaJpZM4Tjj8F> .

[clemsos]

Actually this looks more promising : https://github.com/OpenGov/react-leaflet-cluster-layer

[ungentilgarcon]

npm ERR! peerinvalid Peer react-leaflet@1.9.1 wants leaflet@^1.3.0
npm ERR! peerinvalid Peer react-leaflet-cluster-layer@0.0.3 wants leaflet@^0.7.7
:/

[clemsos]

The main question is what will be the best approach for clustering. To cluster, the network we need to first cluster the markers based on zoom, then parse edges again corresponding to the clustered nodes. We need to solve marker clustering first.

…

On 4 May 2018, at 09:48, gregory bahde ***@***.***> wrote: npm ERR! peerinvalid Peer ***@***.*** wants leaflet@^1.3.0 npm ERR! peerinvalid Peer ***@***.*** wants leaflet@^0.7.7 :/ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#172 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAtXThbqx3wCiUNaDFlabkA9dzNF1hMYks5tvBXcgaJpZM4Tjj8F>.