SuperMap iServer Smart City Integration: Getting Manhole Telemetry onto a China GIS Platform

On a mainland-China municipal project, the GIS platform is rarely the engineer’s decision. It arrives in the tender specification, in the xinchuang domestic-substitution mandate, or as the prime contractor’s house standard. By the time it reaches you, the requirement says SuperMap iServer.

Chen Yu’s team won a district drainage contract in Chengdu with 1,100 smart manhole covers named as the monitored asset. The covers were ordered, the gateway was on site, and nobody on the team had published streaming data to iServer before. Three weeks in, the pilot stopped on a support message he still quotes: the data flow service requires a licence the project had not bought.

That single gap is the whole problem. A SuperMap iServer smart city integration is a documented process, but the vendor documentation is organised by product feature, which is not the same as organised by task.

This guide closes the distance. It covers the four ways manhole telemetry reaches iServer, the streaming pipeline expressed for a manhole fleet, the licence prerequisite that quietly stops Chinese pilots, and what actually breaks in an ArcGIS migration. The wider field-to-map architecture sits in our cluster guide; this article is the China-platform spoke.

Specifying the field hardware alongside the platform? See the Black Ant smart manhole cover range, which publishes this telemetry natively over NB-IoT, LoRaWAN, or MQTT.

What SuperMap iServer Actually Is

SuperMap iServer is a GIS server from SuperMap Software, a Chinese GIS vendor. It publishes spatial data as web services (REST map, data, 3D, and OGC), aggregates services from multiple sources, and streams real-time sensor data through an add-on Streaming Service. It runs on-premises or in containers, and it is the China smart city GIS platform most municipal tenders name.

That definition matters because the English web has almost none of it. Search the term and you land in the SuperMap iServer documentation, its training PDFs, or a product walkthrough written for someone who already bought the licence. There’s no independent English article on the platform, and none connecting it to a fleet of sensors.

Is SuperMap iServer a GIS Server or a Dashboard?

iServer is infrastructure, not a visualisation tool: the map your district authority opens in a browser is a client of iServer, not iServer itself.

Administration sits at /iserver/manager/ on the default port 8090, started from bin/startup.bat. If you’ve run GeoServer, the shape is familiar. If you’ve run ArcGIS Server, the concepts map more directly than the interface does.

The service families you will actually use

Three families carry a smart-city integration. REST Data Service gives feature-level read and write over HTTP, which telemetry needs because it accepts edits. REST Map Service renders the maps your dashboards open. OGC services (WMS, WFS, WCS, WMTS) provide standards-based output, which keeps a tender’s optionality clause satisfied.

What this article is not

It’s not a case for open source and not an ArcGIS tutorial. If your project can choose its own stack with no licence budget, the open-source QGIS, PostGIS, and GeoServer baseline is the honest answer, and we’ve written that pipeline. This article is for the team handed SuperMap iServer that needs telemetry to reach it.

Why SuperMap iServer, On a Smart City Project: The XinChuang Context

The platform is rarely chosen on features. If you are reading this from outside China, the reason is a policy you may not have met: xinchuang.

XinChuang is shorthand for information-technology application innovation, and in practice it means domestic substitution of foreign technology in government and state-enterprise systems. The companion phrase independent and controllable, frames the goal as reducing dependence on a foreign stack rather than cutting cost.

For xinchuang GIS, the effect is concrete. Industry analysis reports that ArcGIS Enterprise is no longer the core base for new government projects, largely because of weak adaptation to domestic ARM processors. SuperMap iServer, by contrast, is certified across Phytium  and Kunpeng  CPUs, Kylin  and UOS operating systems, and DM  and Kingbase databases, with private deployment and  cryptography support.

Treat that as market analysis rather than a named regulation, and be ready to evidence the certifications to a compliance reviewer.

Set against ArcGIS, SuperMap iServer is the domestic alternative most Chinese municipal tenders name, and the table below is how the three stacks separate.

Consideration	ArcGIS	SuperMap iServer	QGIS / PostGIS / GeoServer
China procurement	Not the reported base for new XinChuang projects	Certified across domestic CPU, OS, and database stacks	Needs a domestic fork to be compliant
Licence shape	Per user plus per capability	Per CPU core, plus separately priced modules	Free; support is the real cost
Streaming tier	Velocity, a separate subscription	Streaming Service Extension Module, purchased separately	Free, but you build the pipeline
National datum	Configurable	CGCS2000 support built for the market	Configurable

The most useful thing to know is how the mandate is applied: preserve what exists and control what is new. New modules go onto domestic platforms, and existing foreign bases are often kept and aggregated rather than replaced. Migration cost, not functional gap, is described as the primary obstacle.

Where replacement has happened it’s real: a reported Ministry of Water Resources “one map” project moved 160 TB and more than 500 thematic services onto domestic hardware. Treat that as reported, not measured.

The policy chain is first-party and citable. The Ministry of Housing and Urban-Rural Development published the Technical Guidelines for the Urban Information Modeling (CIM) Basic Platform in 2021. The 14th Five-Year Plan for National Informatization then named it “One Map” management, followed by the “Real-Scene 3D China” notice of 2022, and the National Development and Reform Commission’s 2025 action plan named it TIM, CIM, and BIM. Manhole telemetry is a small dataset within those platforms. It still has to conform.

Start Underground: What the Manhole Cover Must Publish

Every competitor starts inside the iServer manager. Your constraints are set in the pit, so start there.

A payload that reaches iServer without a custom parser looks like this.

{
  "device_id": "MH-2291",
  "ts": "2026-09-23T03:10:42Z",
  "lat": 39.90420,
  "lon": 116.40740,
  "tilt_deg": 14.8,
  "level_mm": 412,
  "h2s_ppm": 6.1,
  "ch4_pct_lel": 3,
  "batt_v": 3.42,
  "alarm_flags": ["TILT", "LEVEL"]
}

Four decisions hide in those ten fields. The timestamp goes out in UTC so nothing is rewritten at the GIS boundary. Coordinates arrive as WGS84 decimal degrees from the commissioning GPS fix.

Identity travels as a stable device_id matching a field in the asset register, because that string becomes your join key and, in the streaming path, your geofence subject. Alarm flags are derived at the device, so the edge can raise a local alert when the cloud path is down.

Publish interval versus battery budget

More frequent reporting means more radio time, and radio time dominates the power draw on a device sealed in a pit for years. A 15-minute cadence supports multi-year operation. A 30-second cadence needs a larger cell, and the cell becomes the cost driver rather than the radio.

Run the arithmetic before a sales conversation. A fleet of 1,100 covers on a 15-minute cadence produces 105,600 messages a day, about 1.2 per second. That rate is irrelevant to iServer’s capacity and entirely relevant to your battery replacement schedule.

What happens when the uplink drops

A device that discards readings when the network is unreachable makes the platform look broken and destroys the record exactly when the event matters. Buffering belongs at the edge. Black Ant’s IoT Data Collection Terminal aggregates a local fleet, normalises the payloads, and holds readings until the uplink returns, then forwards them in order. Ask any supplier to state buffering depth in messages and retention in hours, in writing, before you order.

Four Ways Manhole Telemetry Reaches SuperMap iServer

A SuperMap iServer smart city integration has four real paths from a pit to an iServer feature. They differ in latency, effort, and licence tier, and picking wrongly is expensive to undo.

Path	Latency	Effort	Licence tier	Best for
Batch import	Hours	Low	Base edition	The pilot that has to ship this week
REST Data Service with editing	Seconds	Medium	Base edition	The workable default for a small fleet
Streaming receiver	Sub-second	High	Advanced tier plus the Streaming module	Alarm propagation and live geofencing
Service aggregation	Native to the source	Low	Base edition	Telemetry that already lives elsewhere

1. Batch import. The correct first step on almost every project, because it proves the field mapping and the coordinate system against real data before anyone buys a licence. It’s a dead end at fleet scale: a manual import can’t serve a dashboard that’s supposed to refresh itself.
2. REST Data Service with editing enabled. The workable default for a few hundred devices, and it uses nothing beyond a base licence. The trade is that you write the schedule, the retry logic, and the idempotency yourself. If your devices publish over MQTT, that logic is the same middleware bridge described in the MQTT-to-GIS integration deep dive, so read that before you write it twice.
3. A Kafka or MQTT receiver into the SuperMap Streaming Service for IoT. The real-time path a smart-city programme is usually imagining, and the only one that supports live geofencing. It’s also the path with a licence prerequisite, covered below. Confirm the tier before you design against it.
4. Service aggregation. iServer can publish and aggregate third-party remote services, including ArcGIS Server REST services and services from GeoServer or online basemaps. If your telemetry already lives in another platform, aggregation reads it where it is rather than moving it.

Two notes that save rework:

• If the tender cites OGC compliance, SuperMap’s OGC output is why, and it preserves the option to swap platforms later.
• Chinese municipal projects generally specify CGCS2000 (EPSG:4490), with the streaming client reprojecting rather than storing geometry twice. That has its own traps, so the detail lives in the coordinate-system section below.

The Streaming Pipeline, Expressed for a Manhole Fleet

SuperMap’s Using Streaming Service is the primary reference for this tier. What it doesn’t do is start at a manhole. Here’s the same pipeline with a manhole fleet wired into each stage.

The Streaming Service is built on Spark Streaming and needs a Spark cluster; iServer ships a built-in Spark option. A flow processing model has four parts, Receiver, Filter, Mapper, and Sender, and the process reads as receive, parse, filter, process, output. Models are stored as a .streaming file whose two top-level sections are SparkParameter and Stream.

Here is that structure illustratively. It is a conceptual model showing the four stages, not a copy of a vendor file.

{
  "SparkParameter": { "appName": "manhole-fleet-stream", "batchIntervalSeconds": 30 },
  "Stream": {
    "Receiver": { "type": "Kafka", "topic": "manhole/+/telemetry" },
    "Filter": { "type": "Spatial", "relation": "contain",
                "geofence": "district-07",
                "states": ["enter", "stay", "exit"] },
    "Mapper": { "fields": [
      { "from": "ts", "to": "eventTime", "type": "DATETIME" },
      { "from": "level_mm", "to": "level", "type": "INT32" } ] },
    "Sender": { "targets": ["DataFlowService", "iServerDataStore"] }
  }

Receivers support Socket, WebSocket, TCP, HTTP, JMS, and Kafka, with CSV, TXT, JSON, and GeoJSON as input formats. Filters are attribute-based or spatial. Mappers handle field mapping, computed fields, and coordinate transformation. Senders emit to the data flow service for live clients and to iServer DataStore, an Elasticsearch-based store, for history.

The geofence filter: why “stay” is the state that matters

Spatial filters support geofencing with relations such as contain and disjoint, and geofence state is tracked as enter, stay, or exit. Most teams build on enter and exit and ignore the middle state.

Liang Bo runs the drainage crew for a district of 90 square kilometres, and the state machine changed his maintenance week. A cover that tilts and recovers is a passing lorry. A cover that tilts and stays tilted is theft or a collapse.

The water level reads the same way. Level that stays above the invert across a soak period is a blockage building; a single spike is rain. Tying the alarm to duration rather than one reading cut the crew’s false callouts by roughly half.

Field mapping: from the payload to iServer feature metadata

The mapper is where your payload becomes a feature. Map the sensor fields once and reuse the table.

Payload field	iServer feature field	Type	Example
device_id	id	TEXT	MH-2291
ts	eventTime	DATETIME	2026-09-23T03:10:42Z
lon, lat	geometry	Point	116.40740, 39.90420
level_mm	level	INT32	412
tilt_deg	tilt	DOUBLE	14.8
h2s_ppm	h2s	DOUBLE	6.1
ch4_pct_lel	ch4	DOUBLE	3
batt_v	battery	DOUBLE	3.42
alarm_flags	alarm	TEXT	TILT, LEVEL

Keep the identity field a string, not an integer. Manhole IDs carry prefixes in every real asset register, and re-keying them mid-project is avoidable pain.

Sizing the sensor tier for a district pilot? Send us your fleet count and reporting cadence and we will model the edge buffer depth and the message rate for it. Talk to the Black Ant engineering team.

Publishing the SuperMap iServer DataFlow Service, and Subscribing From a Client

Publishing turns a running model into something a dashboard can consume. The sequence is short:

1. Confirm the Spark cluster is reachable and validate the model against a sample record.
2. Choose Quickly publish Streaming Service in the manager and select the data source.
3. Confirm the service publishes to a dataflow node or a general node, then set the output targets.
4. Start the service and watch the manager for the first records.

Service management lives at /iserver/manager/services/{streamingServiceName}/.

The DataFlow REST resource: broadcast, subscribe, and what a client receives

The SuperMap iServer REST API reference documents the endpoint as <services_uri>/{servicename}/dataflow[.<format>], supporting GET and HEAD, with broadcast and subscribe as child resources and rjson, json, html, and xml as formats. A GET returns the capabilities and the metadata a client needs to open the stream.

{
  "capabilities": "broadcast,subscribe",
  "featureMetaData": {
    "epsg": 3857,
    "featureType": "Point",
    "fieldInfos": [
      { "name": "id", "type": "TEXT" },
      { "name": "level", "type": "INT32" }
    ]
  },
  "streamUrls": [
    { "transpot": "ws",
      "url": "ws://192.168.17.116:8091/iserver/services/manhole/dataflow/" }
  ]

Two things to note. The featureMetaData reports the service’s own epsg, which is how you catch a projection mismatch before a client renders a point in the wrong province. And transpot is the vendor’s spelling in its own response, not ours.

The WebSocket path, and the port that is not 8090

Clients subscribe over WebSocket, and the standard example is ws://<host>:8800/iserver/services/{ServiceName}/dataflow. The port is not the REST port and it isn’t fixed: the response above returns 8091, because the value comes from the deployment’s own configuration.

Read the port from streamUrls rather than hard-coding it, because a client assuming 8090 fails silently against a healthy service. The subscribe child adds filter attributes and a dynamic projection parameter, so one dashboard can follow a single district and reproject on subscribe.

The Licence Prerequisite That Stops Smart City Pilots

Which SuperMap iServer Edition Supports Streaming?

The Streaming Service is an extension module, and it isn’t part of the base licence. SuperMap’s own Product editions and modules page lists it as a module that needs additional purchase, documented as available on the professional and advanced edition packages. Deployment guidance adds a second condition: the SuperMap iServer data flow service must be published to a dataflow node or a general node.

Two documents from the same vendor describe these facts and never cross-reference each other. The publishing guide doesn’t say streaming needs a specific tier; the editions page doesn’t say the smart-city pilot needs the module. As a result, a team can follow every instruction correctly and still meet a “licence required” message with no explanation, which is exactly how a pilot stalls in week three.

Core-based licensing, and what “16 cores” means for your plan

SuperMap moved to core-based licensing, constraining the number of CPU logical cores the iServer machine may use. Tiers are 16 cores, 32 cores, and an additive +2 cores module that can’t be licensed alone. If you budgeted a 48-core virtual machine out of habit, you have three options: buy up to the tier, cap the licence below the host’s core count, or size the machine to the licence. Check the core count before the server is ordered; changing a VM specification is cheaper than changing a contract.

What it costs: reading a public price list honestly

SuperMap doesn’t publish a rate card, so any figure is a reference point. A Hong Kong Construction Industry Council published product price document (PA25-032) lists iServer Advanced at approximately HK$483,300 for purchase and HK$149,900 per year for subscription, with a service extension module at approximately HK$215,750 per module.

Use it as an order of magnitude, not a quote: one jurisdiction, one year, excluding technical services. What it shows is the ratio. The streaming module is roughly half the base licence, which isn’t the assumption most teams bring to a first budget.

What you have	Streaming Service available?	What to verify before design
Base edition	Not as documented	Whether a base tier can register a dataflow node at all
SuperMap iServer Advanced or Professional edition licence	Yes, with the Streaming Service Extension Module added	That the module is a contract line, not just the base licence
Ultra or later tier	Reported to bundle more of the extension stack	Which modules are built in versus still additive in your release

Verify edition names against your release before writing them into a tender. SuperMap has shipped Standard/Advanced/Ultra from 11i(2024) onward, Standard/Professional/Enterprise historically, and regional documentation using Basic/Standard/Advanced/Premium. The module rule holds across all of them; the tier name does not.

Migrating From ArcGIS to SuperMap: What Actually Breaks

An ArcGIS to SuperMap migration is the question the vendor defers and every project asks. The honest answer: smaller than you fear in the database, larger than you expect in the styling.

Feature geometry and attributes move well. Esri feature classes, subtypes, and domains have direct analogues, and a shapefile or File Geodatabase export imports cleanly. What breaks is the layer around the data.

Map documents don’t convert, so layouts, label expressions, and symbology get rebuilt. Field types need a pass, because a date stored as text in Esri behaves differently once iServer types it. Arcade expressions have no direct equivalent, and anything written in ModelBuilder is a rewrite.

A utility that moved 12 years of ArcGIS feature classes found the geometry arrived intact inside a week. Rebuilding 40 web maps and their symbology took a full quarter. Budget for redesign rather than conversion, and migrate one service at a time so you can compare outputs.

What Coordinate System Do Chinese Municipal Projects Require?

Most Chinese municipal projects specify CGCS2000 (EPSG:4490), China’s national coordinate system and the geodetic datum that superseded Xian 1980 and Beijing 1954. That is not the WGS84 decimal degrees your devices publish, nor the Web Mercator your old ArcGIS services rendered in. Expect a reprojection step between device payload and stored feature, and confirm the EPSG the data flow service reports in its featureMetaData matches what your client renders. Coordinate systems, not radios, are the quiet integration killer in this market, and WGS84 versus local CRS in GIS integration covers the transformation theory and the pre-flight checklist.

Is ArcGIS to SuperMap Migration Worth It?

Migrate when the platform is mandated, the estate is small, or a refresh is already scheduled. Do not migrate when the only goal is satisfying a tender clause, because iServer can publish and aggregate third-party services, including ArcGIS Server REST services, and aggregation satisfies more tenders than teams expect. If your target is Esri’s streaming tier, streaming into ArcGIS Velocity is a different problem with its own traps.

Key Takeaways

Underground telemetry fails upstream far more often than it fails on the map, and a SuperMap iServer smart city integration is not an exception.

• SuperMap iServer is a GIS server that publishes and aggregates REST and OGC services, and Chinese municipal tenders name it most often because of the xinchuang domestic-substitution mandate, not a feature comparison.
• Four paths reach iServer: batch import, REST Data Service with editing, a streaming receiver, and service aggregation. Only streaming supports live geofencing, and only streaming carries the licence prerequisite.
• Confirm the Streaming Service Extension Module is a contract line, check the licence core count before the server is ordered, and read featureMetaData.epsg and the port from streamUrls rather than assuming them. ArcGIS migration moves geometry and attributes cleanly but rebuilds map documents, field types, and analysis; CGCS2000 (EPSG:4490) adds a reprojection step.

Talk to the Black Ant engineering team about your project’s sensor mix, or start with the reference architecture in our field-to-map integration guide.