12 weeks of milestone, some I crossed, some to cross, indeed a lots to contribute. It was Google Summer of Code'17 which show me a way and drived me to contribute for world's largest open source community, Drupal. These awesome 3 months of summer spent in developing a project "Creating Great GeoSpatial Experience for Drupal ", have filled me with great zeal and zest. The adventurous journey of thousand lines of code comes to an end. However this post is not about my personal experience but a summary of the tasks accomplished and outstandings throughout the project.
Hi folks, this week is the last week of Google Summer of Code'17 and as I promised to deliver a complete working Search_Api_Location Module by the end of this summer, finally today I am going to guide you how to install and configure the module. All patches have been pushed to Drupal code base, an Alpha version of the same will be released soon.
Hi folks, one more week to end Google Summer of Code'17. As I promised to finish the project in these 3 months, this week I have completed porting all the required features for the Alpha release of the module and submitted all the required tests for it. You can have a look on this issue also. As you know our module implicitly depends upon the Search API Solr, in fact it will take more 3-4 days to fix the issue and help release of the module.
If you can remember in the last post I had discussed about representing the imploded heat map array on a map. I ended up with a solution to use SolrHeatMapLayer library extensively with my module. I had to hack the library up to some extent as it was explicitly coupled to solr server. And my module depends on Solr via search api and Search api location plugin.
Plotting markers on a map is easy using the tooling that is readily available. However, what if you want to add a large number of markers to a map when building a search interface? The problem is that things start to clutter and it’s hard to view the results. The solution is to group results together into one marker. You can do that on the client using client-side scripting, but as the number of results grows, this might not be the best option from a performance perspective.