> For the complete documentation index, see [llms.txt](https://docs.predicthq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.predicthq.com/getting-started/guides/geolocation-guides/searching-by-location.md).

# Searching by location

Performing a radial search using our Events API's `within` parameter is a common way to find events that impact your locations of interest. See our guide on [radial searches](https://docs.predicthq.com/getting-started/guides/geolocation-guides/searching-by-location/find-events-by-latitude-longitude-and-radius.md) and the within search parameter.

A radial search returns events based on their location and geometry type. The following image shows the result of the example radial search performed in our [WebApp](https://control.predicthq.com/search/events/map?category=public-holidays,observances,politics,conferences,expos,concerts,festivals,performing-arts,sports,community,daylight-savings,airport-delays,severe-weather,disasters,terror,academic\&place.scope=6252001\&active.gte=2020-08-06\&active.lte=2020-09-05\&state=active\&within=4mi%4040.6441,-73.9393): A 4-mile radius around a point in Brooklyn, New York, USA - the search area is the blue circle.

| LOCATION AND GEOMETRY TYPE                       | RADIAL SEARCH MATCHING CRITERION                                                                                                                                                                                                                                                                                                                                                                                               |
| ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Point event with Point geometry                  | The API returns the event if its point falls within the specified radius. In the following image, matching point events are the dots within the search area.                                                                                                                                                                                                                                                                   |
| Area event with Polygon or MultiPolygon geometry | The API returns the event if any part of its polygons intersects the specified radius. In the radial search map, matching events with polygons intersect the search area.                                                                                                                                                                                                                                                      |
| Area event with Point geometry                   | The API returns the event if the radial search location (the provided lat,lon coordinates regardless of radius) is a child place of the area event's place. In the radial search map, the dot outside the search area is an area event without a polygon. This event covers all of New York City, and since the radial search's location is in Brooklyn, a child place of New York City, the API also returns this area event. |

<figure><img src="https://2312509647-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNhzHETmXsrWeVBndqqJ%2Fuploads%2Fxqc5atsGKmidRIg6JtsK%2Fradial-search-control-center.png?alt=media&amp;token=71e83707-1ae7-43ba-a418-d87e04acccdf" alt="A map of a 4-mile radial search around a point in Brooklyn, with the blue search circle, matching point events inside it, and an area event for New York City outside it"><figcaption></figcaption></figure>

When searching for events around a specific business location—a store, hotel, or other fixed site—the recommended approach is to use a [Saved Location](https://docs.predicthq.com/api/saved-locations/overview.md). When you create a Saved Location from a lat/lon origin, PredictHQ automatically calculates [Predicted Impact Area](https://docs.predicthq.com/api/impact-area/get-impact-area.md) and stores it as the location boundary. You can then reference that location by `location_id` across the Events API, Features API, and Beam—without managing coordinates or boundaries manually.

If you need a simpler point-and-radius search without a Saved Location, you can use the `within` parameter directly as described earlier. In that case, see the [Predicted Impact Area API](https://docs.predicthq.com/api/impact-area/get-impact-area.md) with `area_type=radius` to get an appropriate radius for your location and industry.

You can also search for events occurring, in particular, Geonames Places using the `place.scope` parameter with Place ids. In our [Severe-Weather Events Data Engineering notebook](https://github.com/predicthq/phq-data-science-docs/blob/master/severe-weather-events/part_1_data_engineering.ipynb), we provide code examples to find Place ids for your locations of interest.<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.predicthq.com/getting-started/guides/geolocation-guides/searching-by-location.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
