Search Features

Search is built into expo-gaode-map and expo-gaode-map-navigation. It provides comprehensive POI (Point of Interest) search functionality based on AMap SDK, including keyword search, nearby search, route search, geocoding, and autocomplete features.

Standalone Search Package Maintenance Notice

2.2.33 is the last version that supports standalone expo-gaode-map-search integration. Starting with the next version, expo-gaode-map-search is no longer maintained as a standalone package.

After AMap Android SDK 10.0.700, the official remote dependency bundle changed from "map + location" to "map + location + search", and the remote dependency coordinate changed from com.amap.api:3dmap:latest.integration to com.amap.api:3dmap-location-search:latest.integration. Keeping search as a standalone package now creates unnecessary bundling and dependency-conflict cost, so search is maintained with core/navigation instead.

If a legacy project still needs the standalone package, pin expo-gaode-map-search@2.2.33. New projects should import search APIs from expo-gaode-map or expo-gaode-map-navigation.

Overview

The search module is now maintained inside the core package and the navigation package. You do not need to install expo-gaode-map-search for new projects.

Key Features

• ✅ POI Keyword Search - Search for places by keyword
• ✅ Nearby Search - Find POIs around a specific location
• ✅ Route Search - Search for POIs along a route
• ✅ Autocomplete - Get search suggestions in real-time
• ✅ Pagination - Support for large result sets
• ✅ Type Filtering - Filter by POI category
• ✅ Built-in Native Search - Available from expo-gaode-map or expo-gaode-map-navigation

---

Installation

1. Install the Package

# Map + location + search
npm install expo-gaode-map

# Or: map + location + search + navigation
npm install expo-gaode-map-navigation

# Legacy standalone integration only
npm install expo-gaode-map-search@2.2.33

2. Configure API Key

Make sure you have configured the AMap API Key in your app.json:

{
  "expo": {
    "plugins": [
      [
        "expo-gaode-map",
        {
          "android": {
            "apiKey": "your-android-api-key"
          },
          "ios": {
            "apiKey": "your-ios-api-key"
          }
        }
      ]
    ]
  }
}

The search module will automatically use the API Key configured in the core module, no additional configuration needed.

3. Rebuild the App

After installing the package, rebuild your app:

# For development build
npx expo prebuild
npx expo run:android
# or
npx expo run:ios

# For EAS Build
eas build --platform all

---

Basic Usage

Import the Module

import { 
  initSearch,
  searchPOI, 
  searchNearby,
  searchAlong,
  searchPolygon,
  getInputTips,
  type POI,
  type InputTip,
  type SearchResult,
  type InputTipsResult,
} from 'expo-gaode-map';

If you use the navigation package, import from expo-gaode-map-navigation:

import {
  initSearch,
  searchPOI,
  searchNearby,
  searchAlong,
  searchPolygon,
  getInputTips,
  type POI,
  type SearchResult,
} from 'expo-gaode-map-navigation';

If you configured keys via Config Plugin, the search module auto-initializes. Otherwise, call initSearch() once at startup.

Keyword Search

async function searchPlaces(keyword: string) {
  try {
    const result = await searchPOI({
      keyword,
      city: 'Beijing',
      pageNum: 1,
      pageSize: 20,
    });
    
    console.log(`Found ${result.total} results`);
    return result.pois;
  } catch (error) {
    console.error('Search failed:', error);
    return [];
  }
}

Nearby Search

async function searchNearby(location: { latitude: number; longitude: number }) {
  try {
    const result = await searchNearby({
      center: location,
      keyword: 'restaurant',
      radius: 2000,
      pageNum: 1,
    });
    
    return result.pois;
  } catch (error) {
    console.error('Nearby search failed:', error);
    return [];
  }
}

Autocomplete

async function getSuggestions(keyword: string) {
  try {
    const result = await getInputTips({
      keyword,
      city: 'Beijing',
    });
    
    return result.tips;
  } catch (error) {
    console.error('Autocomplete failed:', error);
    return [];
  }
}

---

Complete Example

Here's a complete example of a search map application:

import React, { useState } from 'react';
import { View, TextInput, FlatList, Text, StyleSheet, TouchableOpacity } from 'react-native';
import { MapView, Marker, searchPOI, type MapViewRef, type POI } from 'expo-gaode-map';

export default function SearchMapScreen() {
  const [keyword, setKeyword] = useState('');
  const [results, setResults] = useState<POI[]>([]);
  const [selectedPOI, setSelectedPOI] = useState<POI | null>(null);
  const mapRef = React.useRef<MapViewRef>(null);

  const handleSearch = async () => {
    if (!keyword.trim()) return;
    
    try {
      const result = await searchPOI({
        keyword,
        city: 'Beijing',
        pageNum: 1,
        pageSize: 20
      });
      
      setResults(result.pois);
      
      if (result.pois.length > 0) {
        setSelectedPOI(result.pois[0]);
        await mapRef.current?.setCenter(result.pois[0].location, true);
      }
    } catch (error) {
      console.error('Search failed:', error);
    }
  };

  const handleSelectPOI = async (poi: POI) => {
    setSelectedPOI(poi);
    await mapRef.current?.setCenter(poi.location, true);
  };

  return (
    <View style={styles.container}>
      {/* Search Bar */}
      <View style={styles.searchBar}>
        <TextInput
          style={styles.input}
          value={keyword}
          onChangeText={setKeyword}
          placeholder="Search for places"
          onSubmitEditing={handleSearch}
        />
      </View>

      {/* Map */}
      <MapView
        ref={mapRef}
        style={styles.map}
        initialCameraPosition={{
          target: { latitude: 39.908692, longitude: 116.397477 },
          zoom: 15,
        }}
      >
        {results.map((poi) => (
          <Marker
            key={poi.id}
            position={poi.location}
            title={poi.name}
            snippet={poi.address}
            onMarkerPress={() => handleSelectPOI(poi)}
          />
        ))}
      </MapView>

      {/* Results List */}
      {results.length > 0 && (
        <View style={styles.results}>
          <FlatList
            data={results}
            keyExtractor={(item) => item.id}
            renderItem={({ item }) => (
              <TouchableOpacity
                style={[
                  styles.resultItem,
                  selectedPOI?.uid === item.uid && styles.selectedItem
                ]}
                onPress={() => handleSelectPOI(item)}
              >
                <Text style={styles.name}>{item.name}</Text>
                <Text style={styles.address}>{item.address}</Text>
              </TouchableOpacity>
            )}
          />
        </View>
      )}
    </View>
  );
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
  },
  searchBar: {
    position: 'absolute',
    top: 50,
    left: 20,
    right: 20,
    zIndex: 10,
    backgroundColor: 'white',
    borderRadius: 8,
    shadowColor: '#000',
    shadowOffset: { width: 0, height: 2 },
    shadowOpacity: 0.25,
    shadowRadius: 3.84,
    elevation: 5,
  },
  input: {
    height: 45,
    paddingHorizontal: 15,
    fontSize: 16,
  },
  map: {
    flex: 1,
  },
  results: {
    position: 'absolute',
    bottom: 0,
    left: 0,
    right: 0,
    maxHeight: 300,
    backgroundColor: 'white',
  },
  resultItem: {
    padding: 15,
    borderBottomWidth: 1,
    borderBottomColor: '#f0f0f0',
  },
  selectedItem: {
    backgroundColor: '#e3f2fd',
  },
  name: {
    fontSize: 16,
    fontWeight: '600',
    marginBottom: 4,
  },
  address: {
    fontSize: 14,
    color: '#666',
  },
});

---

API Reference

The search module provides the following methods:

searchPOI

Search for POIs by keyword.

Parameters:

• keyword - Search keyword
• city - City name or code
• types - POI type codes joined by |
• pageNum - Page number (default: 1)
• pageSize - Results per page (default: 20, max: 50)

Returns: POISearchResult

---

searchNearby

Search for nearby POIs around a location.

Parameters:

• center - Center coordinates
• keyword - Search keyword
• types - POI type codes joined by |
• radius - Search radius in meters (default: 1000, max: 50000)
• pageNum - Page number
• pageSize - Results per page

Returns: POISearchResult

---

searchAlong

Search for POIs along a route.

Parameters:

• polyline - Route points (at least 2)
• keyword - Search keyword
• types - POI type codes joined by |
• range - Search range in meters (default: 500, max: 1000)

Returns: POISearchResult

---

getInputTips

Get input suggestions (autocomplete).

Parameters:

• keyword - Input keyword
• city - City name or code
• types - POI type codes joined by |

Returns: InputTipsResult

---

Common Use Cases

1. Search Near Current Location

import { ExpoGaodeMapModule, searchNearby } from 'expo-gaode-map';

async function searchNearMe(keyword: string) {
  const location = await ExpoGaodeMapModule.getCurrentLocation();
  const result = await searchNearby({
    center: {
      latitude: location.latitude,
      longitude: location.longitude
    },
    keyword,
    radius: 5000
  });
  
  return result.pois;
}

2. Search Along Driving Route

import { searchAlong } from 'expo-gaode-map';

async function findGasStationsOnRoute(start: Coordinate, end: Coordinate) {
  const result = await searchAlong({
    keyword: 'gas station',
    polyline: [start, end],
    range: 1000,
  });
  
  return result.pois;
}

3. Category Search

import { searchPOI } from 'expo-gaode-map';

async function searchByCategory(category: string, city: string) {
  // 040000 = Dining, 050000 = Shopping, etc.
  const result = await searchPOI({
    keyword: '',
    city,
    types: category,
    pageSize: 50
  });
  
  return result.pois;
}

---

FAQs

Q: Why is the standalone search package no longer recommended?

A: After AMap Android SDK 10.0.700, the official remote dependency bundle includes map, location, and search together. Keeping search separate increases dependency-conflict risk, so native search is now maintained inside expo-gaode-map and expo-gaode-map-navigation. Standalone expo-gaode-map-search is only for legacy projects pinned to 2.2.33.

Q: Do I need to configure the API Key separately for the search module?

A: No, the search module automatically uses the API Key configured in the core module. You only need to configure it once in app.json.

Q: What's the difference between searchPOI and searchNearby?

A:

• searchPOI - City-wide search by keyword, suitable for general searches
• searchNearby - Search within a specific radius around a point, suitable for "nearby" searches

Q: How do I handle "No results found"?

A: When result.pois.length === 0, you can check result.suggestion for suggested keywords or cities to help users refine their search.

Q: Are there API rate limits?

A: Yes, AMap API has request frequency limits. For production apps, consider implementing caching and request debouncing strategies.

Q: How do I get the complete POI type code list?

A: Refer to AMap POI Classification for the complete list.

---

Related Documentation

• Search API Reference
• Search Examples
• Core Module API
• Getting Started