# Location List

**Location List Functionality and Content:** The location list screen displays a user's relevant locations in a primary location (first navigation tab) that not only addresses the previous problem of users' inability to locate their followed locations, but also reinforces the primary value of BloomSky—providing weather through followed locations or purchased BloomSky weather stations. It provides adding, editing, rearranging, and removing capabilities for users to customize their list. In addition, the screen allows the user to quickly scan weather information for their entire list including weather station status and location weather conditions. To address the label problems that previously confused users, we ensured that only relevant and significant information necessary to determine a location is provided on the list. Further information would be provided after tapping on a location. To address the information hierarchy problems, we ensured logical information grouping and visual division **(see screens 1–2)**.

**Editing a Purchased Weather Station:** If a user decides to edit a purchased weather station, they can change the station's information including name, description, location, and search privacy. In addition, they can initiate station processes such repositioning the camera view, relocating a station or replacing a station while keeping continuation of data records, deactivating a station temporarily to e.g. change the wifi network, and linking a BloomSky indoor weather station if its placed at the same location. Information and functionality is ordered and grouped by frequency of change and relation to one another **(see 3)**.

**Renaming a Followed Station:** Users can rename a nickname for a followed location **(see 4)**. The nickname provides the option to use a more relevant and memorable name to the user (e.g. office, work, school) rather that using a default of address or weather station name designated by the owner.

**Mental Anchors:** To address the previous problems of navigational and informational confusion (i.e. "where am I" and "what am I looking at"), simple functionality such as renaming, removing & adding were designed as modals and locations being edited were referenced in order to create a strong association with where the user was in the app and what was being edited. **(see 4–6)**.


---

# Agent Instructions: 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:

```
GET https://docs.ecosphereprime.com/ecosphere/community-product/wireframe/location-list.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.