Absolutely! You can totally force Algolia to sort results strictly by proximity to a specific point (like Times Square) while ignoring your custom likes ranking rule—no problem at all. Here's how to make it happen:

Key Background #

By default, Algolia uses your index's custom ranking rules (like likes) alongside geographic proximity if you're doing a location-based search. To override this and prioritize distance exclusively, you'll need to explicitly define the sorting order in your search request.

Step-by-Step Solution #

The most flexible way (without messing with your global index settings) is to use the sortBy parameter in your search call. This lets you override the default ranking formula for that specific query.

1. Define your geographic focus: Set the target coordinates (Times Square's lat/lng is 40.7580,-73.9855) using aroundLatLng.
2. Add any additional filters: Use the filters parameter to apply other criteria (e.g., category, price range).
3. Force distance-only sorting: Set sortBy to ["_geo_distance:asc"]—this tells Algolia to sort results only by how close they are to your target point, from nearest to farthest.

Example Code (JavaScript) #

// Assume you've initialized your Algolia index already
index.search('', { // Empty query if you just want filtered/sorted results
  aroundLatLng: '40.7580,-73.9855', // Times Square coordinates
  aroundRadius: 10000, // Optional: Limit results to 10km radius
  filters: 'type:cafe AND rating >= 4', // Your custom filters
  sortBy: ['_geo_distance:asc'] // Strictly sort by proximity, ignore `likes`
}).then(({ hits }) => {
  console.log('Results sorted by distance to Times Square:', hits);
});

Important Notes #

• The _geo_distance is an Algolia-built attribute that calculates distance from your specified point—using :asc ensures closest results come first.
• This sortBy parameter completely overrides your index's default customRanking settings (so your likes attribute won't factor into the order at all).
• If you need this sort order frequently, you could also create a replica of your index with a modified ranking formula (setting _geo_distance as the primary sort), but using sortBy per request is usually more flexible.

内容的提问来源于stack exchange，提问作者user2954587