> For the complete documentation index, see [llms.txt](https://docs.sdv.dev/rdt/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sdv.dev/rdt/transformers-glossary/deep-data-understanding/phone-number/geoextractor.md).
# ＊ GeoExtractor
{% hint style="info" %}
**＊SDV Enterprise Feature.** This feature is available to our licensed users and is not currently in our public library. For more information, visit our page to [Explore SDV](https://docs.sdv.dev/sdv/explore/sdv-enterprise/compare-features).
{% endhint %}
The `GeoExtractor` extracts geographical context from the phone numbers so that they can be used later for data science. It keeps the original phone numbers so that the same exact numbers can be recovered during the reverse transform.
```python
from rdt.transformers.phone_number import GeoExtractor
transformer = GeoExtractor()
```
## Parameters
**`default_country`**: If phone number does not have an international country code, provide the country code to use.
(default) None
No default country. All phone numbers must have international country codes.
### Examples
```python
from rdt.transformers.phone_number import GeoExtractor
ge = GeoExtractor(default_country='US')
```
---
# 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.sdv.dev/rdt/transformers-glossary/deep-data-understanding/phone-number/geoextractor.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.
