> For the complete documentation index, see [llms.txt](https://xnet-mobile.gitbook.io/xnet-mobile-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xnet-mobile.gitbook.io/xnet-mobile-docs/deploy-connect-earn/quickstart-1/location-location-location.md).

# Location, Location, Location

### Selecting Potential Locations for XNET Deployments <a href="#ideal-locations-for-xnet-installations" id="ideal-locations-for-xnet-installations"></a>

Choosing the right location is key to maximizing your network’s efficiency and rewards. Ideal deployment sites feature high foot traffic, substantial user density, and frequent WiFi usage—such as restaurants, bars, airports, shopping malls, parks, transit hubs, event venues, and university campuses.

<table><thead><tr><th width="161.125">Location Type ✅</th><th width="232.4296875">Description</th><th width="187.8515625">Estimated Foot Traffic/month</th><th width="112.60546875">Average Dwell Time (per visit)</th></tr></thead><tbody><tr><td><strong>Airports</strong></td><td>Constant influx of travelers needing quick access to data.</td><td>100,000 - 1,000,000</td><td>1 - 2 hrs</td></tr><tr><td><strong>Restaurants, Bars, Cafes</strong></td><td>Popular with both local and visiting patrons who often stay for extended periods.</td><td>3,000 - 10,000+</td><td>20 - 60 min</td></tr><tr><td><strong>Public Parks</strong></td><td>Increasingly equipped with Wi-Fi for public use, especially in urban centers.</td><td>50,000 - 100,000</td><td>30 - 60 min</td></tr><tr><td><strong>Shopping Malls</strong></td><td>Large numbers of visitors with high smartphone usage.</td><td>50,000 - 500,000+</td><td>1 - 2 hrs</td></tr><tr><td><strong>Public Transit Stations</strong></td><td>Subways, train stations, and bus terminals where people use downtime to browse the internet.</td><td>200,000 - 600,000+</td><td>10 - 30 min</td></tr><tr><td><strong>University Campuses</strong></td><td>Dense concentrations of tech-savvy students who frequently access online resources.</td><td>50,000 - 200,000+</td><td>60 - 90 min</td></tr><tr><td><strong>Event Venues</strong></td><td>Stadiums, concert halls, and conference centers with large crowds needing access to social media and online services.</td><td>10,000 - 100,000+</td><td>2 - 4 hrs</td></tr><tr><td><strong>Libraries and Museums</strong></td><td>Spaces where visitors stay for long periods and often need access to informational resources.</td><td>5,000 - 20,000+</td><td>1 - 2 hrs</td></tr><tr><td><strong>Tourist Attractions</strong></td><td>High traffic landmarks where tourists often require internet access for navigation and information.</td><td>20,000 - 300,000+</td><td>1 - 2 hrs</td></tr><tr><td><strong>Large Hotels and Resorts</strong></td><td>Guests and conference attendees utilize network access for both personal and business purposes.</td><td>10,000 - 50,000+</td><td>3 - 6 hrs</td></tr></tbody></table>

***Conversely, some locations may not be so ideal for XNET installations.***

<table><thead><tr><th>Location Type 🚫</th><th>Description</th><th width="136.6875">Estimated Foot Traffic/month</th><th width="144.65625">Average Dwell Time (per visit)</th></tr></thead><tbody><tr><td><strong>Single Family Residential Areas</strong></td><td>Limited number of users, not valuable to carriers.</td><td>&#x3C; 100</td><td>15 - 30 mins</td></tr><tr><td><strong>Rural Locations</strong></td><td>Sparse populations and low density.</td><td>&#x3C; 5,000</td><td>15 - 30 mins</td></tr><tr><td><strong>Industrial Zones</strong></td><td>Areas primarily for industry, minimal public access.</td><td>&#x3C; 1,000</td><td>10 - 20 mins</td></tr><tr><td><strong>Private Offices</strong></td><td>Small businesses or corporate offices that do not receive significant external visitors.</td><td>100 - 1000</td><td>30 - 60 mins</td></tr><tr><td><strong>Areas with Low Pedestrian Traffic</strong></td><td>Places where people primarily travel by car, such as remote rest stops or drive-through services.</td><td>&#x3C; 5,000</td><td>&#x3C;10 - 15 mins</td></tr><tr><td><strong>Non-Metro Residential Buildings</strong></td><td>Apartment complexes in suburban or rural areas with insufficient user density.</td><td>&#x3C; 2,000</td><td>30 - 45 mins</td></tr><tr><td><strong>Farm and Agricultural Areas</strong></td><td>Very low demand for public Wi-Fi.</td><td>&#x3C; 1,000</td><td>10 - 20 mins</td></tr></tbody></table>

{% embed url="<https://www.youtube.com/watch?index=3&list=PLaRtTPxAvZ8VYbQ5Z3iCl3_wj_-mxWuzq&v=7wW487c2FeU>" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://xnet-mobile.gitbook.io/xnet-mobile-docs/deploy-connect-earn/quickstart-1/location-location-location.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.