> 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/predicthq-data/ranks/local-rank.md). # Local Rank Local Rank is a numeric value on a logarithmic scale between 0 and 100 to represent the impact of an event to its local area. Local Rank may vary even though the PHQ Rank of the events are the same. For example, a conference with 1,000 people in attendance (with PHQ Rank 50) has a [Local Rank of 43 in Hong Kong](https://events.predicthq.com/events/KKtBoCYP3gWPvgGhnp) where the local population density is around 64,000, while a [Local Rank of 65 in Dublin, Ireland](https://events.predicthq.com/events/0lrweBnDZKrr) where the local population density is around 5,000. Local Rank has this property: * Local Rank is comparable between the attended events in terms of the event’s impact to its local area. --- # 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/predicthq-data/ranks/local-rank.md?ask=&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.