South Korea's road-name address system separates the road name, building number and additional details. Juso, the government's address information service, provides the authoritative lookup. The current postcode has five digits; the UPU records the replacement of the former six-digit system in August 2015. In its Roman-alphabet examples, the postcode follows the locality. Apartment building and unit components can appear as dong and ho. Keep those components distinct from the main building number instead of collapsing every number into a generic apartment field.
A useful Korean address test set includes a road with a simple building number, a number with an extension, and a building complex with a separate unit line. The example diagram is an invented fixture showing those roles, not a Juso-verified destination. Check that commas, hyphens and the leading zero in a postcode such as 04542 survive CSV imports. Also check the Korean-script version of a label separately from its romanized representation; a system can render one correctly while truncating the other. A postcode input should remain a text field, even when all accepted characters are digits.
On this page the name pool is Korean, but the geographic anchors are romanized city records. The engine samples from fifteen configured city records, including Seoul, Busan and Incheon, and chooses a code from the selected record's list. Street details are generated separately rather than looked up in the government's road-name database. Consequently a generated profile is a format fixture and a rough geographic example, not proof that its road, building and postcode agree at delivery-point level. Coordinates are scattered near the selected city; they do not locate the invented building.
Korean names and English-oriented form assumptions are another useful boundary. Our engine preserves Korean-script given names and surnames and suppresses an ASCII fallback middle name when the given name is non-Latin. The combined profile still uses the site's shared given-name-first layout. For a Korean family-name-first interface, use the exported fields rather than rearranging a display string by spaces. Run a generation, a profile copy and a JSON import through your own application, then compare field values before and after. The methodology page explains why rendering tests and address-verification tests need different fixtures.