Hello Rik,

First of all, congrats for your module. It's amazing!

I'm trying to use the FacetAPI to create some facets to filter the content returned. Is this possible?

My scenario is:

1) A lot of nodes with address field and Geofield
2) A view filtering the content by the user location (via HTML5 or IP)
3) Some facets to remove (or include) States and Cities to open or close the range around the user.

Any clue about it?

Thank you so much!

CommentFileSizeAuthor
#5 shot2.png66.04 KBpmichelazzo
#3 shot1.png71.07 KBpmichelazzo
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

pmichelazzo’s picture

By the way,

I can't buy a beer for you (you deserve that).

Tell to them to accept credit cards outside from Canada and US :)

RdeBoer’s picture

Thanks Paulino!

Will let the TSM guys know about the payment options.

I remember from discussions on this forum that people have used IPGV&M with Apache Solr and Search API. I don't know about FacetAPI.

IPGV&M is built on Views -- so as long as Views returns the results in the same way as it does when used without FacetAPI and with/without Search API then it **should** work, I'd say.

Do you intend to use client-side marker clustering via Leaflet MarkerCluster? As you'll be limited to a few thousand to 5000 markers.

Rik

pmichelazzo’s picture

FileSize
71.07 KB
pmichelazzo’s picture

Hello Rik,

Thanks for you fast answer.

Looking around this situation yesterday and trying to use search API and facet API, I can't find the "holy grail" field to do what I need (proximity). Actually I've found a field to do that using the Search API Location (another module) but I don't have the option to give a HTML5 localization (the screenshot attached show it).

Search API need an special kind of Views to show the results (based on the Search Index) and there, unfortunately, I can't see the IPGV&M there.

I don't intent to use maps or something like this to show the results. I just need to know where is the user, sort the results table using this information and give them the option to change this location for another one. Now I accomplish the second task using the Search API location module (the second attachment show it) but the result's sort is a pain right now.

Just a comment, I patched the geofield (https://drupal.org/node/2011340) and it's working 100% with IPGV&M but not with Search API and Search API Location. Is this my mistake?

Thank you and give me an option to pay you a beer (this is not valid for Victoria. Nobody can drink that ;)

pmichelazzo’s picture

FileSize
66.04 KB
RdeBoer’s picture

Hi Paulino,

Couldn't agree more with you on Victoria Bitter! Luckily there's some great micro-breweries in Victoria now, so we don't need to drink that stuff.

I have no experience with the Search API Location module. Isn't that module meant to work the Location module rather than Geofield?

Rik

pmichelazzo’s picture

Hi Rik,

Good to hear about the micro-breweries. I lived close of you 10 years ago and, on that time, we had only Victoria there. Was a mess :)

Well, the Search API Location module works with Geofield. I was tested with Location module and doesn't work very well.

I'm using this module because the Apache Solr server to index content and facets. This module use the latitude/longitude parameters to calculate a range between the results and the location. So, if I give these data (lat/log) coming from somewhere (I really don't know where), for the view, I think that I can solve my problem.

If you have any insight about it, I appreciate.

Regards from the other side of the world.

RdeBoer’s picture

Not really anything to add.
Closing due to inactivity.
Please re-open if necessary.
Rik