Shanghai Minhang spatial information

Formation and regional foundations

Municipal and district action arrangements use Xinzhuang Industrial Zone, a civilian spatial-information base and the Jiangchuan area as carriers for data, software, applications and business services. The stated ambitions have a 2026 deadline: CNY50 billion of activity, a group exceeding ten key firms, and six benchmark applications. None describes a result already delivered.

A utility map, reality model or location service can enter urban work only when lawful origin, coordinate reference, accuracy and date are visible. Minhang’s carriers, software firms and applications can connect field capture, cleaning, modelling, interfaces and sector workflows. After a technical demonstration, permissions, revisions, updates and correction ownership still determine whether the product can support engineering and operating decisions.

Core geography: Xinzhuang industry carriers–Jiangchuan application base–Minhang urban spatial services

Minhang spatial-information collaboration nodes

Links among field capture, software processing and sector use

Nodes show technical and business responsibility, not the real location or storage path of sensitive geographic information.

• Field survey and mobile capture — People and instruments capture field information within permission, scope and accuracy.
• Coordinate processing and quality checks — Transformation, registration, joining and attributes retain accuracy and date.
• Two- and three-dimensional models and services — Maps, reality models, analysis functions and standard interfaces form products.
• Permissions, revisions and security — Roles, access logs, update lots and backups limit misuse.
• Sector application integration — Utilities, construction, parks, water and commerce call location products.
• Field confirmation and continued updates — Operational change, completed works and user feedback drive the next maintenance cycle.

01 · How three carriers form Minhang’s industry network

Industry carriers, application bases and urban clients play different roles.

Shanghai’s action plan identifies Xinzhuang Industrial Zone, a civilian spatial-information base and the Jiangchuan base within roughly three square kilometres of planned carriers. They do not form a simple production line: offices, field capture, equipment tests and urban applications may sit in different places. Each project route follows the contracting entity, authorised work area and delivery site.

Upstream work includes instruments, mobile capture, base maps, compute, graphics engines and software engineering. Governance, modelling, analysis and interfaces sit between those inputs and municipal, park, construction or commercial use. Projects connect the layers; no firm has to perform all field, software and operating tasks, but each supplier must distinguish owned capability, partners and outsourced responsibility.

The plan’s CNY fifty billion scale, more than ten key firms and six benchmark applications point to 2026. They describe desired policy outcomes, not current output, firms already attracted or completed applications. A company or product still has to demonstrate its legal entity, Minhang operation, contract, people, product and customer acceptance on its own merits.

• Xinzhuang, the civilian spatial base and Jiangchuan form the planned area.
• Survey, software, cloud compute and applications meet through projects.
• Scale, key-firm and benchmark figures remain targets.

02 · What happens from field capture to a usable map

Area, coordinates, time and accuracy are fixed before fieldwork.

Before fieldwork, the client and surveyor fix area, objects, horizontal and vertical reference, scale or accuracy, and permitted times. Roads, sites, parks and indoor utilities differ in traffic, sight lines, lighting and safety, so instruments and methods change with them. Restricted areas, sensitive facilities and personal activity require permission and separation even if that leaves gaps.

Satellite positioning, total stations, laser point clouds, mobile imagery and aerial capture do not naturally share coordinates, density or time. Control points, clocks and transformation parameters register them, with overlap areas checked for displacement. Combining different dates or references without that work can produce a complete-looking but misplaced building or utility map.

Cleaning removes clear outliers, assigns attributes, separates features and handles occlusion, but manual changes cannot disappear under a generic label of optimisation. Hidden utilities, tree-covered roofs and active works are marked missing, inferred or awaiting resurvey. Raw lot, processing steps, software revision and editor remain traceable so a disputed coordinate can be reconstructed.

• The field plan states objects, permission, equipment and safety.
• Different sensors are registered to common coordinates and time.
• Outliers, gaps, occlusion and manual edits remain recorded.

03 · How instruments, compute and base maps shape delivery time

More data is not automatically more useful; instruments follow business accuracy.

Instrument choice begins with business accuracy, distance, movement and environment, not the highest possible point density. Utility location, park-outline updates and commercial-flow analysis require different coordinates and attributes; excessive capture only expands processing and storage. Calibration, battery, clock and sensor synchronisation are checked before work and again after severe temperature change or vibration.

High-resolution imagery, point clouds and textured models impose different transfer, processing, editing and publication loads. A project estimates raw, intermediate, backup and service capacity separately. Compute queues, uploads and reruns change the schedule beyond field days, while browser or mobile delivery adds tiling, levels of detail and caching work.

Base maps, imagery, geocoding, navigation, graphics engines and commercial components often come from outside providers. Their licences, request volumes, update dates and export rules directly affect the product. A price change or shutdown can break display, search and routing together, so contracts identify dependencies, cost ownership, replacement paths and portable formats for critical assets.

• Instrument accuracy, calibration and environment enter the result.
• Point clouds, imagery and models place different loads on storage and compute.
• Base maps, software components and services need rights and exit planning.

04 · How accuracy, date and coordinate reference enter acceptance

A spatial product needs field agreement, not merely an attractive display.

An accuracy of one metre might mean a single-point horizontal error, an average or a confidence level, each supporting very different engineering decisions. The statement includes coordinate component, statistic, sample size, terrain or occlusion and excluded areas. Street-level commercial analysis may tolerate one class, while excavation around buried utilities requires evidence matched to safety responsibility.

A spatial set may hold imagery date, field-check date, attribute-update date and system-release date. Showing only the latest publication can make buildings, roads and shops appear equally current when they are not. Each feature carries a usable date and update trigger, with rapidly changing construction areas flagged for field confirmation.

Acceptance points remain independent from field control and cover open ground, high-rise occlusion, road edges and complex structures. Attribute checks use signs, engineering records or operating staff to confirm diameter, purpose and status separately from coordinate accuracy. A failure leads to local correction, wider sampling or recapture, with the treated area marked in resubmission.

• Accuracy statements include metric, confidence, samples and applicable area.
• Map date and business-update date are not one timestamp.
• Sampling uses independent points, field comparison and exception handling.

05 · How models, interfaces and permissions enter daily operation

Visualisation is an entry point; operational value comes from current data, stable calls and limited access.

An attractive city or park model cannot support work if operators cannot find a pipe, device or work order. Buildings, floors, rooms, roads, utilities and assets link to existing identifiers, owners and business state before inspection, repair and engineering change can use them. Detail follows the task rather than imposing permanent rendering and maintenance costs for invisible features.

Sector systems query coordinates, addresses, asset attributes and analyses through interfaces, and one normal response proves little. Tests cover concurrent load, large areas, bad parameters, revision change, dependency outage and recovery, with clear behaviour for timeouts and visible stale results. Caller, purpose and returned revision are logged so an incident can trace its affected work.

Not every user needs exact critical infrastructure, building interiors or movement information. Views are masked, aggregated or hidden by role and task, while exports, bulk queries, shared links, backups and maintenance accounts receive the same control. Transfers, contract endings and project closure revoke temporary access promptly, and log retention follows risk and applicable rules.

• Model objects link to engineering, asset and business identifiers.
• Interfaces need revision, response, load and outage acceptance.
• Sensitive locations and personal movement are limited by purpose.

06 · How utilities, parks and commercial clients define demand

Clients need location products matched to work, not one common map.

Utility, water and road clients care about asset class, depth, diameter, age, status and owner, not attractive lines alone. Construction use distinguishes accuracy class, areas awaiting checks and field confirmation before excavation, so an asset-management map is not mistaken for safety setting-out. Completed works and routine repairs trigger updates or an initially accepted product will drift from reality.

Park operations can place buildings, roads, utilities, planting, parking and energy assets in one spatial frame, but value comes from links to inspections, repairs, tenants and consumption. A small zone first uses real work orders to test location, route and ownership before expansion. A three-dimensional model that cannot accept simple field changes soon becomes an exhibit opened only for visits.

Logistics siting, retail networks and footfall studies combine roads, residents, trade areas, travel time and anonymised location information, each with different date, sample and bias. The result may compare candidate zones without precisely forecasting one shop’s sales or one day’s traffic. The client fixes permissible decision, spatial unit and validation method so conclusions do not exceed their inputs.

• Utilities and construction emphasise accuracy, ownership, updates and field safety.
• Park operations connect assets, space, work orders and energy.
• Logistics and commerce state sample, period, bias and permitted decisions.

07 · Risks from capture rights, stale data and interface lock-in

Spatial errors can travel through interfaces into many operations, requiring rapid containment.

Roads, parks, sites and building interiors have different owners, so permission follows area, equipment and time rather than one broad entry approval. People, plates, addresses and movement in imagery are masked, anonymised or removed for the stated purpose, and raw access is narrower than final statistics. Partner contracts limit use, retention, onward distribution and incident responsibility.

Road works, demolition, tenant turnover and moved equipment make spatial products stale, while one wrong coordinate can spread into work orders, navigation and engineering drawings. An incident marks affected area, time lot and downstream systems, stops distribution and alerts users. Corrected results receive a new revision, reacceptance and replacement record rather than silently overwriting the basis of earlier decisions.

Some platforms hold models, attributes, workflows and accounts in proprietary formats or one service. They start quickly but can make later migration rebuild many relationships. Procurement requires export formats, dictionaries, interface documents, complete backups and a post-service access period. Restoring a small area and critical workflow independently tests whether backups, keys and tools truly support exit.

• Survey permission, base-map rights and personal information follow purpose.
• Stale results must be identified, isolated and withdrawn downstream.
• Proprietary formats and single services need portable data and exit drills.

08 · How an urban-asset use case is proved before expansion

A limited area proves capture, checking, use and updates before replication.

A controlled pilot may cover several park buildings, one road section or an asset-inspection zone where owner, identifiers, field staff and intended decisions are clear. Scope, objects, reference, accuracy, attributes, update rate and visible users are fixed with independent checkpoints. The area can be small, but real work orders, field changes and one failure drill must test the full loop.

The supplier uses intended instruments, processing, model structure and interfaces, rather than a manually polished one-off demonstration. Business staff query, locate, dispatch, verify and report errors under their own accounts while managers inspect role-based masking. When construction, removal or attribute change occurs, the pilot measures who initiates an update, how long it takes and when downstream users receive it.

Review combines coordinate and attribute pass rates, interface response, update time, user steps, and withdrawal and repair after an error. A prettier view that does not reduce field search, duplicate entry or stale information will only magnify maintenance burden. Wider deployment follows closed defects, independent operation and one successful update cycle, with instruments, data and service capacity expanded together.

• A pilot needs clear business ownership and independently checkable ground.
• Production data, user workflow, permissions and exceptions enter together.
• Expansion follows accuracy, updates, service time and business results, not model area.

Sources and reading notes

Survey capture, data governance, three-dimensional visualisation, platform software and sector applications are assessed as different products; one demonstration cannot stand in for all of them. Planned scale, firm counts and benchmark applications are future targets. A project still follows area, objects, acquisition permission, coordinate system, accuracy, update frequency, interface performance and maintenance scope.

• Shanghai’s action plan identifies Xinzhuang Industrial Zone, a municipal civilian spatial-information base and the Jiangchuan base as Minhang carriers covering about three square kilometres.
• The plan targets CNY50 billion in industry scale, more than ten key firms and six benchmark applications by 2026; all are targets.

Related companies

These companies have a locally relevant industry role supported by public information. Order is not a ranking, inclusion does not imply authorization, partnership or endorsement, and Hello China does not participate in or guarantee transactions.

A company may request a free correction or removal through the formal channel if its record is inaccurate or it does not wish to be shown. Do not send business licences, authorization letters or other sensitive files through insecure channels.

• Guangfu Technology — Shanghai Municipal Government documents the local base of Shanghai Minhang spatial information. The company’s official site describes related products or services and an operating presence in Shanghai.
• Jianglai Data — Shanghai Municipal Government documents the local base of Shanghai Minhang spatial information. The company’s official site describes related products or services and an operating presence in Shanghai.
• Zhentu Information — Shanghai Municipal Government documents the local base of Shanghai Minhang spatial information. The company’s official site describes related products or services and an operating presence in Shanghai.
• Request a company-record correction or removal — Requests are reviewed by a person, handled promptly after verification, free of charge and not tied to commercial cooperation.

Sources

Use the original publishers to check dates, scope and definitions; public material is not a transaction guarantee.

• Minhang spatial-information industry action plan — Shanghai Municipal Government
• Minhang spatial-information coordination and applications — Shanghai Municipal Government
• Minhang spatial-information support policy — Shanghai Municipal Government
• Zhentu company and product profile — Shanghai Zhentu Information Technology Co., Ltd.
• Jianglai Data official site — Shanghai Jianglai Data Technology Co., Ltd.
• Dingtuyi mapping platform — Shanghai Guangfu Technology Co., Ltd.