Ho Chi Minh City

Source identity and administrative path

The source row behind Ho Chi Minh City is GeoNames ID 1566083. Its recorded administrative path is Ho Chi Minh City (HCMC) → Vietnam, and GeoNames classifies the place as a populated place.

Ho Chi Minh City occurs once as a primary city label in this atlas sample; the numeric ID remains the durable source key if names change. The city row itself was updated 2025-10-19; that date belongs to the source record, not to every transport or visitor detail in the real destination.

Population position inside fixed cohorts

Within the fixed 1,206-record atlas, Ho Chi Minh City ranks 8 by recorded population. Inside the 13 selected Vietnam entries it ranks 1; inside the 632 entries in its broad region it ranks 5.

Its 14,002,598 population value is 11.01 times the 1,272,235 median for the country cohort and 13.89 times the 1,008,426 regional median. Ho Chi Minh City falls inside the leading tenth of this atlas's Vietnam population cohort.

Ho Chi Minh City's recorded value reaches at least twice the country-cohort median in this snapshot. These comparisons describe this selected dataset only; they are not current census rankings or official urban-area boundaries.

Nearest-reference pattern

Ho Chi Minh City's three nearest other atlas coordinates are Thuận An at 14.534 km with 588,616 recorded people; Thủ Đức at 15.815 km with 524,670 recorded people; Biên Hòa at 25.197 km with 1,272,235 recorded people. The closest-to-farthest distance spread is 10.663 km. Compared with Thuận An, Ho Chi Minh City's recorded population is 23.79 times as large. Against Ho Chi Minh City, Thuận An follows Thanh Pho Thuan An → Ho Chi Minh City (HCMC) → Vietnam in the source. Its point has higher latitude and higher longitude; it belongs to the same selected Vietnam cohort, uses the shared Asia/Ho_Chi_Minh identifier, and carries second-order administrative seat rather than populated place.

Its recorded population is below Ho Chi Minh City's. Against Ho Chi Minh City, Thủ Đức follows Quan Thu GJuc → Ho Chi Minh City (HCMC) → Vietnam in the source. Its point has higher latitude and higher longitude; it belongs to the same selected Vietnam cohort, uses the shared Asia/Ho_Chi_Minh identifier, and carries second-order administrative seat rather than populated place. Its recorded population is below Ho Chi Minh City's. Against Ho Chi Minh City, Biên Hòa follows Thanh Pho Bien Hoa → Dong Nai → Vietnam in the source.

Its point has higher latitude and higher longitude; it belongs to the same selected Vietnam cohort, uses the shared Asia/Ho_Chi_Minh identifier, and carries first-order administrative seat rather than populated place. Its recorded population is below Ho Chi Minh City's. Its nearest-neighbor distance ranks 207 of 1,206 from shortest to longest in the same snapshot. Ho Chi Minh City's nearest-coordinate gap falls between the tightest tenth and quarter of the atlas. This pattern can reveal whether other catalog references are geographically close, but it cannot establish whether a border crossing is possible or practical, or whether rail, road, fare, or journey-time connections exist.

Read as one record signature, GeoNames 1566083, the coordinate pair 10.8230 / 106.6297, country rank 1 of 13, and neighbor GeoNames 12382296 at 14.534 km bind Ho Chi Minh City to a reproducible comparison. That combined key distinguishes the row; it is not a recommendation or evidence of a physical connection.

Coordinate, time-zone and class cohorts

Ho Chi Minh City's reference point is 10.8230° north and 106.6297° east. The IANA identifier Asia/Ho_Chi_Minh is shared by 8 city rows in this catalog, while the GeoNames class PPL is shared by 243 rows. Ho Chi Minh City's row carries a first-order administrative label but no second-order label.

Ho Chi Minh City's point falls in the near-equatorial coordinate band used by this atlas's row checks. Ho Chi Minh City's time-zone field defines the narrower catalog cohort; its place class is shared more broadly. GeoNames supplies no elevation for Ho Chi Minh City, so the profile preserves that missing value instead of guessing terrain.

Together these fields form a reproducible identity check for this page, not a claim about walkability, climate or accessibility.