Your members have locations but no map. This plugin puts them on one.

A map sits above the members directory with a pin for everyone who saved a location. Members attach a place to any activity update from the post form, and that check-in shows an inline map in the stream. You decide which roles can see another member's Check-ins tab.

Members set their location once on their profile through mapped xProfile fields, and the coordinates are geocoded and stored for the directory map and proximity search. A Nearby tab uses the visitor's browser location to show only members within a set radius.

Visitors type an address and a distance into the directory search to find members within that radius, in miles or kilometres. The same proximity search runs on the groups directory so people find the chapters and meetups closest to them.

You choose how much address detail other members see and can switch on coordinate obfuscation so public map pins are coarsened with a per-check-in offset. Raw coordinates stay in the database so proximity search keeps working.

Each group gets a location tab where admins enter the group's address, and every located group appears as a pin on the groups directory map. A [bpchkpro_groupmashupMap] shortcode drops a standalone group map onto any page.

OpenStreetMap through Leaflet renders the maps and Nominatim handles geocoding with no API key and no billing. If you prefer Google, switch the provider and verify your key against four Google endpoints from the settings screen.

A location picker is injected into the BuddyPress activity post form so members attach a place or GPS coordinates to any status update. The place name, latitude, and longitude are saved as activity meta under bpchk_place_details, and an inline map renders below the check-in in the stream and in oEmbed contexts. When Youzify is active the picker moves to its compatible hook. Each member gets a Check-ins tab on their profile and can delete their own check-ins.

A map renders above the members directory with a pin for every member who has a saved location, and clicking a pin opens an info window with the avatar, name, and address. A proximity search replaces or supplements the default search box with an address and radius form, in miles or kilometres, and a Nearby tab uses the visitor's browser location to list members within a configurable radius. Administrators can exclude individual members from the map pins while keeping them in the listing.

Each BuddyPress group gets a location tab where group admins enter the group's address as a single combined field or as separate street, city, state, postal, and country fields. Every located group appears as a pin on the groups directory map, and the groups directory gets its own address-and-radius proximity search. The group Check-ins tab label and slug are configurable, and specific groups can be excluded from the map pins.

Map one or more BuddyPress xProfile fields as a member's primary location, either a single combined address field or separate street, city, state, ZIP, and country fields. When the member saves their profile the address is geocoded and the coordinates are stored in user meta for the directory map and proximity search. Geocoding runs through the Google Geocoding API or through Nominatim, matching the map provider you chose.

Choose how much address detail other members see: full address, city and state, or city only. The privacy filter applies to profile display and directory listings while stored coordinates stay full for proximity search. Turn on coordinate obfuscation and every public map pin and check-in link uses a coarsened lat/lng with a deterministic per-check-in offset that scales with the privacy level, from about 110 metres up to about 11 kilometres. Raw coordinates in the database are never changed.

Two shortcodes drop standalone maps onto any post or page: [bpchkpro_mashupMap] for members and [bpchkpro_groupmashupMap] for groups, each with limit, filter, size, and type attributes. A Members Near Me sidebar widget lists members near a given location and radius, and an admin dashboard widget reports how many members and groups have locations plus the top cities. An optional expiration window (1, 6, 12, or 24 hours) lets an hourly cron delete check-ins after they age out, or keep them forever.

Pick Google Maps, which needs an API key and a billing account, or OpenStreetMap rendered through Leaflet, which needs no key at all. The geocoder follows the same choice: Google Geocoding for Google, Nominatim for OpenStreetMap. An admin AJAX action verifies a Google Maps API key against four Google endpoints (Geocoding, Places, Distance Matrix, and Directions) and reports which are ready. The plugin defaults to the keyless OpenStreetMap and Nominatim pair out of the box.