1、BRITISH STANDARD Geographic information Web map server interface ICS 35.240.70 BS EN ISO 19128:2008This British Standard was published under the authority of the Standards Policy and Strategy Committee on 24 January 2006 BSI 2009 National foreword The UK participation in its preparation was entruste
2、d to Technical Committee IST/36, Geographic information. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. This
3、 British Standard is the UK implementation of EN ISO 19128:2008. It is identical with ISO 19128:2005. It supersedes BS ISO 19128:2005, which is withdrawn. Compliance with a British Standard cannot confer immunity from legal obligations. BS EN ISO 19128:2008 Date Comments This corrigenda renumbers BS
4、 ISO 19128:2005 as BS EN ISO 19128:2008 ISBN 978 0 580 59293 5 Amendments/corrigenda issued since publication 30 June 2009EUROPEANSTANDARD NORMEEUROPENNE EUROPISCHENORM ENISO19128 January2008 ICS35.240.70 EnglishVersion GeographicinformationWebmapserverinterface(ISO 19128:2005) Informationgographiqu
5、eInterfacedecarteduserveur web(ISO19128:2005) ThisEuropeanStandardwasapprovedbyCENon15December2007. CENmembersareboundtocomplywiththeCEN/CENELECInternalRegulationswhichstipulatetheconditionsforgivingthisEuropean Standardthestatusofanationalstandardwithoutanyalteration.Uptodatelistsandbibliographical
6、referencesconcerningsuchnational standardsmaybeobtainedonapplicationtotheCENManagementCentreortoanyCENmember. ThisEuropeanStandardexistsinthreeofficialversions(English,French,German).Aversioninanyotherlanguagemadebytranslation undertheresponsibilityofaCENmemberintoitsownlanguageandnotifiedtotheCENMa
7、nagementCentrehasthesamestatusasthe officialversions. CENmembersarethenationalstandardsbodiesofAustria,Belgium,Bulgaria,Cyprus,CzechRepublic,Denmark,Estonia,Finland, France,Germany,Greece,Hungary,Iceland,Ireland,Italy,Latvia,Lithuania,Luxembourg,Malta,Netherlands,Norway,Poland,Portugal, Romania,Slov
8、akia,Slovenia,Spain,Sweden,SwitzerlandandUnitedKingdom. EUROPEANCOMMITTEEFORSTANDARDIZATION COMITEUROPENDENORMALISATION EUROPISCHESKOMITEEFRNORMUNG ManagementCentre:ruedeStassart,36B1050Brussels 2008CEN Allrightsofexploitationinanyformandbyanymeansreserved worldwideforCENnationalMembers. Ref.No.ENIS
9、O19128:2008:E Foreword The text of ISO 19128:2005 has been prepared by Technical Committee ISO/TC 211 “Geographic information/Geomatics” of the International Organization for Standardization (ISO) and has been taken over as EN ISO 19128:2008 by Technical Committee CEN/TC 287 “Geographic Information“
10、, the secretariat of which is held by NEN. This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by July 2008, and conflicting national standards shall be withdrawn at the latest by July 2008. Attention is
11、 drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN and/or CENELEC shall not be held responsible for identifying any or all such patent rights. According to the CEN/CENELEC Internal Regulations, the national standards organizations of the fol
12、lowing countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Sl
13、ovenia, Spain, Sweden, Switzerland and the United Kingdom. Endorsement notice The text of ISO 19128:2005 has been approved by CEN as EN ISO 19128:2008 without any modifications. BS EN ISO 19128:2008 ii iii ivContents Page Introduction v 1 Scope . 1 2 Conformance. 1 2.1 Conformance classes and requir
14、ements . 1 2.2 Basic WMS. 1 2.3 Queryable WMS. 1 3 Normative references . 1 4 Terms and definitions. 2 5 Abbreviated terms 3 6 Basic service elements 4 6.1 Introduction . 4 6.2 Version numbering and negotiation . 4 6.3 General HTTP request rules 5 6.4 General HTTP response rules . 7 6.5 Numeric and
15、Boolean values. 7 6.6 Output formats 8 6.7 Coordinate systems 8 6.8 Request parameter rules 12 6.9 Common request parameters 13 6.10 Service result 14 6.11 Service exceptions . 14 7 Web Map Service operations. 14 7.1 Introduction . 14 7.2 GetCapabilities (mandatory) 14 7.3 GetMap (mandatory) . 25 7.
16、4 GetFeatureInfo (optional) . 31 Annex A (normative) Conformance tests 34 Annex B (normative) CRS Definitions 37 Annex C (normative) Handling multi-dimensional data . 44 Annex D (normative) Web Map Service profile of ISO 8601. 50 Annex E (normative) XML Schemas. 52 Annex F (normative) UML model 63 A
17、nnex G (informative) Web Mapping Examples 68 Annex H (informative) XML examples 71 Bibliography . 76 BS EN ISO 19128:2008 vIntroduction A Web Map Service (WMS) produces maps of spatially referenced data dynamically from geographic information. This International Standard defines a “map” to be a port
18、rayal of geographic information as a digital image file suitable for display on a computer screen. A map is not the data itself. WMS-produced maps are generally rendered in a pictorial format such as PNG, GIF or JPEG, or occasionally as vector-based graphical elements in Scalable Vector Graphics (SV
19、G) or Web Computer Graphics Metafile (WebCGM) formats. This International Standard defines three operations: one returns service-level metadata; another returns a map whose geographic and dimensional parameters are well-defined; and an optional third operation returns information about particular fe
20、atures shown on a map. Web Map Service operations can be invoked using a standard web browser by submitting requests in the form of Uniform Resource Locators (URLs). The content of such URLs depends on which operation is requested. In particular, when requesting a map the URL indicates what informat
21、ion is to be shown on the map, what portion of the Earth is to be mapped, the desired coordinate reference system, and the output image width and height. When two or more maps are produced with the same geographic parameters and output size, the results can be accurately overlaid to produce a compos
22、ite map. The use of image formats that support transparent backgrounds (e.g. GIF or PNG) allows underlying maps to be visible. Furthermore, individual maps can be requested from different servers. The Web Map Service thus enables the creation of a network of distributed map servers from which client
23、s can build customized maps. Illustrative examples of map request URLs and their resulting maps are shown in Annex G. This International Standard applies to a Web Map Service instance that publishes its ability to produce maps rather than its ability to access specific data holdings. A basic WMS cla
24、ssifies its geographic information holdings into “Layers” and offers a finite number of predefined “Styles” in which to display those layers. This International Standard supports only named Layers and Styles, and does not include a mechanism for user-defined symbolization of feature data. NOTE The O
25、pen Geospatial Consortium (OGC) Styled Layer Descriptor (SLD) specification 6 defines a mechanism for user-defined symbolization of feature data instead of named Layers and Styles. In brief, an SLD-enabled WMS retrieves feature data from a Web Feature Service 7 and applies explicit styling informati
26、on provided by the user in order to render a map. BS EN ISO 19128:2008blank 1Geographic information Web map server interface 1 Scope This International Standard specifies the behaviour of a service that produces spatially referenced maps dynamically from geographic information. It specifies operatio
27、ns to retrieve a description of the maps offered by a server to retrieve a map, and to query a server about features displayed on a map. This International Standard is applicable to pictorial renderings of maps in a graphical format; it is not applicable to retrieval of actual feature data or covera
28、ge data values. 2 Conformance 2.1 Conformance classes and requirements This International Standard defines two conformance classes, one for a basic WMS, and the other for a queryable WMS. Each has two subclasses, one for clients and the other for servers. 2.2 Basic WMS A basic WMS shall support the
29、basic service elements (see Clause 6), the GetCapabilities operation (see 7.2), and the GetMap operation (see 7.3). To conform to this International Standard, a basic WMS shall satisfy the requirements of A.1 of the Abstract Test Suite in Annex A. 2.3 Queryable WMS A queryable WMS shall satisfy all
30、the requirements for a basic WMS, and shall also support the GetFeatureInfo operation (see 7.4). To conform to this International Standard, a queryable WMS shall satisfy all requirements of the Abstract Test Suite in Annex A. 3 Normative references The following referenced documents are indispensabl
31、e for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO 8601:2004, Data elements and interchange formats Information interchange Representation of dates
32、 and times ISO 19111, Geographic information Spatial referencing by coordinates ISO 19115:2003, Geographic information Metadata EPSG (February 2003), European Petroleum Survey Group Geodesy Parameters, Lott, R., Ravanas, B., Cain, J., Simonson, G, and Nicolai, R., eds., available at IETF RFC 2045 (N
33、ovember 1996), Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies, Freed, N. and Borenstein, N., eds., available at BS EN ISO 19128:20082 IETF RFC 2396 (August 1998), Uniform Resource Identifiers (URI): Generic Syntax, Berners-Lee, T., Fielding, N., and Masinter
34、, L., eds., available at IETF RFC 2616 (June 1999), Hypertext Transfer Protocol HTTP/1.1, Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and Berners-Lee, T., eds., available at UCUM, Unified Code for Units of Measure, Schadow, G. and McDonald, C.J. (eds.), version 1.5 XML 1.0, Extensib
35、le Markup Language (XML) 1.0, World Wide Web Consortium Recommendation, Bray, T., Paoli, J., Sperberg-McQueen, C.M., and Maler, E., eds., available at XML Schema, XML Schema Part 1: Structures, World Wide Web Consortium Recommendation, Thompson, H.S., Beech, D., Maloney, M., and Mendelsohn, N., eds.
36、, available at 4 Terms and definitions For the purposes of this document, the following terms and definitions apply. 4.1 client software component that can invoke an operation from a server 4.2 coordinate reference system coordinate system that is related to the real world by a datum ISO 19111 4.3 c
37、oordinate system set of mathematical rules for specifying how coordinates are to be assigned to points ISO 19111 4.4 geographic information information concerning phenomena implicitly or explicitly associated with a location relative to the Earth ISO 19101 4.5 interface named set of operations that
38、characterize the behaviour of an entity ISO 19119 4.6 layer basic unit of geographic information that may be requested as a map from a server 4.7 map portrayal of geographic information as a digital image file suitable for display on a computer screen 4.8 operation specification of a transformation
39、or query that an object may be called to execute ISO 19119 BS EN ISO 19128:2008 34.9 portrayal presentation of information to humans ISO 19117 4.10 request invocation of an operation by a client 4.11 response result of an operation returned from a server to a client 4.12 server a particular instance
40、 of a service 4.13 service distinct part of the functionality that is provided by an entity through interfaces ISO 14252 4.14 service metadata metadata describing the operations and geographic information available at a server 5 Abbreviated terms CDATA XML Character Data CRS Coordinate Reference Sys
41、tem CS Coordinate System DCP Distributed Computing Platform DTD Document Type Definition EPSG European Petroleum Survey Group GIF Graphics Interchange Format GIS Geographic Information System HTTP Hypertext Transfer Protocol IANA Internet Assigned Numbers Authority IERS International Earth Rotation
42、Service IETF Internet Engineering Task Force ITRF International Terrestrial Reference Frame ITRS IERS Terrestrial Reference System BS EN ISO 19128:20084 JPEG Joint Photographic Experts Group MIME Multipurpose Internet Mail Extensions NAD North American Datum OGC Open GIS Consortium PNG Portable Netw
43、ork Graphics RFC Request for Comments SVG Scalable Vector Graphics UCUM Unified Code for Units of Measure URL Uniform Resource Locator WebCGM Web Computer Graphics Metafile WCS Web Coverage Service WFS Web Feature Service WGS World Geodetic System WMS Web Map Service XML Extensible Markup Language 6
44、 Basic service elements 6.1 Introduction This clause specifies aspects of Web Map Server behaviour that are independent of particular operations or are common to several operations. 6.2 Version numbering and negotiation 6.2.1 Version number form and value The Web Map Service (WMS) defines a protocol
45、 version number. The version number applies to the XML schema and the request encodings defined in this International Standard. The version number contains three non-negative integers, separated by decimal points, in the form “x.y.z”. The numbers “y” and “z” shall not exceed 99. Implementations of t
46、his International Standard shall use the value “1.3.0” as the protocol version number. 6.2.2 Version number changes The protocol version number shall be changed with each revision of this International Standard. The number shall increase monotonically and shall comprise no more than three integers s
47、eparated by decimal points, with the first integer being the most significant. There may be gaps in the numerical sequence. Some numbers may denote draft versions. Servers and their clients need not support all defined versions, but shall obey the negotiation rules below. BS EN ISO 19128:2008 56.2.3
48、 Appearance in requests and in service metadata The version number shall appear in at least two places: in the service metadata and in the parameter list of client requests to a server. The version number used in a clients request of a particular server shall be equal to a version number which that server has declared it supports (except during negotiation, as described below). A server may support several versions, whose values clients may discover according to the negotiation rules. 6.2.4 Version number negotiation A WMS client may negotiate with a server to dete
