include neighbors of cluster cores in map app

[jkoschinsky]

include neighbors of cluster cores in map app since explaining to people what a cluster core is might be confusing vs just visualizing the whole cluster.

[Makosak]

i'm not sure if this would be helpful vs the clusters as they are now -- can be confusing in either case, and multiple counties already show up in the clusters? I'm just nervous that switching that will be pretty dramatic and may change the results/make comparisons difficult in future weeks? If we didn't just publish the research brief with results, etc, would be more open to it. other thoughts?

[Makosak]

From Xun:

I just added a new function: GetNeighbors(map_uid, weight_uid, idx) to GeodaProxy class (global object gda_proxy) in index.js.
After click the “Local Clustering” button, the spatial weights (define who’s who’s neighbor) will be created for local clustering and a unique weights id is assigned. The map also has a unique id, which can be accessed by calling global function: getCurrentWuuid(), e.g. in attached screen, returns {map_uuid: “county_usafacts.geojson”, w_uuid: “w_queen100"}
Then, using map unique id and weights unique id, one can call GetNeighbors() function to get the neighbors of i-th object in current map. See the example lines of code in attached screen:

get the neighbors of the county (id=100):

Tagging as task for JS engineer.

[Makosak]

@rbrtmrtn @ariisrael a bit more cmplex but the function to call neighbors was generated by Xun already, so would just need to connect things. This is also around the "LISA" clustering map