Supported standards and protocols

• Supported OGC standards
• Supported tile standards
• Supported security protocols

Supported OGC standards

In addition, the GeoRSS specification is supported.

Supported tile standards

SuperMap supports to generate and publish the standard specification tiles package, MBTiles and GeoPackage. Users don't need to convert these tiles into the formats supported only by SuperMap. In the following functions, the standard tiles are supported:

• Output MBTiles when browser map dynamically; Output MBTiles when using the function of distributed map cutting service
• Output GeoPackage when using the function of distributed map cutting service
• Publish the MBTiles and GeoPackage 1.0 tiles into map services directly

Supported security protocols

The following security protocols are supported:

• HTTPS

HTTPS (Hyper Text Transfer Protocol over Secure Socket Layer) consists of communication over Hypertext Transfer Protocol (HTTP) within a connection encrypted by Transport Layer Security, or its predecessor, Secure Sockets Layer. All the GIS services, management functions, services aggregation and clustering systems of SuperMap iServer support the HTTPS protocol.

• LDAP

LDAP (Lightweight Directory Access Protocol) has an extensible application. Most server systems use LDAP to store user accounts. In iServer, you can directly use the user accounts owned by LDAP server without having to create users again. By doing so, GIS systems and other applications within the organization can share the same set of user system, with lower costs and no redundancy.

• OAuth2

SuperMap supports QQ, Sina and WeChat accounts which are based on OAuth 2.0 protocol. Users can login to the GIS server directly with QQ or Sina accounts, or they can bind the QQ or Sina accounts with the existing account of Server to login. Additionally, iServer supports all third-party account logins under OAuth 2.0 in an extended manner.