Data Standards

Our base dataset combines public transport information, operator notices, facility guidance, field-check records, and user reports. Rather than relying on a single source, we compare multiple signals and prioritize guidance that is genuinely useful in real use cases.

For pages marked as real-time, we prioritize operator data delivered through APIs. For areas without live integration, we show the data reference date and an on-site-check notice so visitors can distinguish non-live guidance from live availability.

A 'real-time' label means the page is supported by operator-connected status or availability signals, and the interface is designed to take users back to the live map immediately. Even then, short-lived discrepancies may still occur due to on-site connectivity or timing gaps.

A 'non-live' label means that the record does not provide live availability. Published location and operating information can help with planning, but final availability must be confirmed on-site.

Public API records come from structured operator datasets such as the railway locker information, detail, and live-use APIs available through Korea's public data portal. Open-file records come from CSV, JSON, or documents published by public institutions, while facility-notice records are checked against official facility pages or public notices.

Candidates found through public search or user reports are not treated as confirmed facts immediately. We compare official guidance, coordinates, place names, and spot details, then record the verifiable source category and data reference date.

Information is reviewed regularly, and changes that directly affect user decisions, such as operator notices and location or pricing changes, are updated as quickly as possible. When something cannot be confirmed immediately, we present it conservatively based on the current verification level.

Our priorities favor high-demand hubs, areas with live integrations, and pages that recently received reports. Another important principle is that we do not try to make older pages look fresher than they really are.

The same locker can appear in multiple files or APIs, so we compare source identifiers, coordinates, place names, and spot details together. Similar-looking candidates are not merged automatically, and only records with a clear place and search intent are selected for search visibility.

A page's operator status time is the reference time for live availability. The data reference date is recorded by the source or during collection and processing; it is not a page-specific review-completion time or a live-availability timestamp.

Each locker detail is built from a database whose sources and fields are organized and reviewed by the operator. However, the data reference date does not itself prove when an individual page review was completed, so live-support and status-update timing are shown separately.

Correction requests move faster when they include the page URL, the exact field that needs to change, and a supporting link or photo. We do not publish reports as-is; we cross-check them with operator guidance or additional evidence before deciding whether to update the page.

BogwanBogwan is not a reservation or on-site operations service; it is a planning and guidance service designed to help before arrival. For pages without live integration, we do not guarantee vacancy, exact pricing, or operating hours.