Skip to main content

The place is the reusable address record

An Alkax place represents a real-world destination that can be searched, shared, improved, verified, and used by another workflow.

What a place can contain​

  • title and category;
  • latitude and longitude;
  • generated Plus Code;
  • settlement and locality;
  • description and landmarks;
  • building, floor, and unit context;
  • moderated photos;
  • creator, claim, and ownership metadata;
  • verification, flag, quality, and review status.

Not every field is required. The useful minimum depends on the destination: a roadside meeting point may need a landmark, while an office in a large building may need floor and unit information.

Place lifecycle​

  1. A contributor creates the place.
  2. Alkax validates the coordinates and looks for nearby duplicates.
  3. The place becomes searchable and shareable when accepted.
  4. People improve, verify, flag, or claim it.
  5. Moderation and quality signals affect its trust and visibility.
  6. The record continues to represent the place as public arrival context changes.

Public place versus private workflow data​

A place is reusable network data. A delivery recipient’s contact, secure link, private instruction, or delivery-only entrance photo belongs to the delivery workflow and is not automatically public place data.