City NOA: Data Compliance Gates Export

The real risk in city NOA is not whether it drives but whether the data it collects can leave China legally, a line that decides if a smart-driving package can be sold overseas as-is. Makers used to race on smoothness; now they race on whether the whole data chain survives two jurisdictions. For exporters the question is simple: does the data clear customs before the car does.

An eight-agency guide requires a Class-A mapping license for navigation maps; only 14 to 25 firms nationwide hold it (Baidu, Amap, NavInfo), and raw geodata is blocked from leaving China.

On the compliance math: by the first three quarters of 2025 domestic L2 penetration reached 64%, and data volume rose with it; battery-management data is now important data under a 27-category, 51-item list.

The impact is on model choice: Tesla shows the two-way wall clearly, its FSD imagery barred from export, the US barring AI training on Chinese data, and BIS banning Chinese software and hardware from the 2027 model year. Importers must ask which data stays in China and which functions rely on a local data loop, or the car may sell but ship with features cut.

Before judging a smart-driving car for export, request three papers. First, the data-export compliance statement and mapping license, naming the Class-A partner. Second, a feature list marking which capabilities need local data and which run offline. Third, the target market data and map rules from the channel, with compliance cost in the quote. For a market compliance path, share the local rules and the car data interfaces.