Feed Map, Places, and Location Filters
How the Map and Places views behave, what Nearby and city filters really do, and what users should expect when location data is missing or mixed.
Where you see this in the app
These controls live in the feed at /feed.
The location-heavy controls are:
| UI control | What it changes |
|---|---|
Map | Shows posts on a map when the post has usable place coordinates |
Places | Groups visible posts by place instead of by thread or time |
Sort: Distance | Uses your current coordinates when the app has them |
City | Limits results to one city-level slice |
Nearby | Narrows to posts within the nearby radius |
This page is the deeper explanation for the cases where location-based browsing feels different from normal feed browsing.
Map vs Places view
Map and Places are related, but they are not the same view.
| View | What users should expect |
|---|---|
Map | A geographic browse mode that depends on posts having usable location coordinates |
Places | A grouped list of posts by place, even when users mainly care about venue names rather than pins |
Use Map when location itself is the decision tool. Use Places when you want to compare venues, cafes, events, or coworking spots as named destinations.
Nearby, city, and distance behavior
The location filters can stack, but they only work well when the app has enough location data.
| Control | Practical meaning |
|---|---|
City | Limit discovery to one city without requiring live device location |
Nearby | Prefer a local-radius view around the current user position |
Sort: Distance | Meaningful only when the app knows where you are and the post has place coordinates |
Important expectations:
Nearbyis stricter than simply selecting a city.Distancesorting is only useful when both sides of the comparison exist: your current position and the post's place position.- If you do not grant location access, city filtering can still work, but nearby/distance behavior becomes less precise or less useful.
Place grouping and unspecified location
The Places view groups posts by place identity first and only falls back when that information is missing.
That means users may see a grouping such as Unspecified location when a post is visible in the feed but does not have a fully usable place attachment.
This is intentional. The app is choosing to show the content instead of silently hiding it just because place metadata is incomplete.
Practical interpretation:
- a named place group means the post is tied to a recognizable place,
- an unspecified group means the content is still relevant but not cleanly place-bound,
- a map pin may be unavailable even when the same post still appears in list-style feed views.
Check-in and place expectations
Location discovery also connects to place pages and check-ins.
The main end-user mental model is:
- use the feed to discover by timing, relationships, or location,
- open a place page when the venue itself matters,
- use check-in actions when you want the app to reflect that you are actually on site.
If a post says it is missing a place, the fix is not in the map itself. The post or featured-workspace setup needs a proper place attached first.
See it in action
Previous
Feed, Discovery, and Following
How the feed works, what the main filters mean, and how Everyone, Following, views, hashtags, and timing filters shape discovery.
Next
Profile and Featured Workspace
How profile basics, the featured profile workspace, and the public workspace routes define your persistent public presence.