HCM2000 Open 56: Static road-network vehicle routing instances with time windows in Ho Chi Minh City

HCM2000 Open 56 is a semi-synthetic static vehicle-routing dataset with time windows for a study region in Ho Chi Minh City, Vietnam. Version 2.0.0-rc1 contains 56 instances with 2,000 synthetic customers and one depot each: 28 geometries paired with TW15/TW60 slack settings (R:20, C:18, RC:18 instances). The study rectangle is 106.55–106.72 E, 10.68–10.84 N, with a 3 km road buffer. The frozen OpenStreetMap source has base timestamp 2026-11-03T01:35:51Z. The directed routing graph has 290,548 nodes and 602,686 edges. The package distinguishes minimum travel time in seconds, distance along a selected fastest path in metres, and minimum network distance in metres. It includes source/graph manifests, customer files, feasible reference routes, generation and validation code, a data dictionary, reuse limitations, and illustrative HC/TA/SA results (1,680 runs; 10 seeds and 2,000,000 attempted moves per algorithm/instance). Final route coverage, capacity, time-window/depot-return feasibility and objective values have been independently checked. Customer locations, demands, service times, speeds and windows are generated assumptions, not observed delivery operations or measured traffic. TW15/TW60 denote ±15/±60-minute slack around a constructed reference schedule; paired instances share geometry and are not independent spatial samples. Turn restrictions are not enforced; conditional-tagged ways are excluded. The graph uses a motorcycle-oriented access interpretation and is not certified truck routing. No global optimality, minimum-fleet or state-of-the-art superiority is claimed. Database components retain ODbL-1.0 and OpenStreetMap attribution: © OpenStreetMap contributors, https://www.openstreetmap.org/copyright. The project code license is scoped separately in the package. This is a release candidate prepared for creator review; the reserved DOI is not registered until publication. Reproduction scope, numerical tolerances and any remaining release conditions are recorded in the supplied validation reports and RELEASE_STATUS.json.