BS 7666-5-2006 Spatial datasets for geographical referencing - Specification for a delivery point gazetteer《地理参考用空间数据集 交货点名录用规范》.pdf

1、BS 7666-5:2006Spatial datasets for geographical referencing Part 5: Specification for a delivery point gazetteerICS 07.040; 35.240.70NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBRITISH STANDARDPublishing and copyright informationThe BSI copyright notice displayed in this do

2、cument indicates when the document was last issued. BSI July 2006ISBN 0 580 48711 3The following BSI references relate to the work on this standard:Committee reference IST/36Draft for comment 05/30127197 DCPublication historyFirst published, July 2006Amendments issued since publicationAmd. no. Date

3、Text affectedBS 7666-5:2006 BSI 2006 iBS 7666-5:2006ContentsForeword iiIntroduction iii1 Scope 12 Normative references 13 Terms and definitions 14 Delivery point gazetteer requirements 15 Gazetteer metadata 26 Delivery point records 47 Data quality 6AnnexesAnnex A (normative) Checklist for conformit

4、y 7Annex B (normative) UML model for a delivery point gazetteer 7Annex C (informative) Codes 8Annex D (informative) Example of gazetteer metadata 9Annex E (informative) Example of a delivery address 9Annex F (informative) Examples of delivery point records 12List of figuresFigure 1 Delivery point ga

5、zetteer model 2Figure B.1 UML model for a gazetteer of delivery points 7List of tablesTable 1 Gazetteer metadata 3Table 2 Attributes of a delivery point 5Table C.1 Language codes 8Table C.2 Delivery point state codes 8Table D.1 Delivery address elements 10Summary of pagesThis document comprises a fr

6、ont cover, an inside front cover, pages i to iii, pages 1 to 15, an inside back cover and a back cover.ii BSI 2006BS 7666-5:2006ForewordPublishing informationThis part of BS 7666 was published by BSI and came into effect on 28 July 2006. It was prepared by Technical Committee IST/36, Geographic info

7、rmation. A list of organizations represented on this committee can be obtained on request to its secretary.Information about this documentBS 7666 was originally published over the period 1994 to 1996 in four parts.These four parts were revised separately over the period 2000 to 2002. During 2004 to

8、2005, all the parts were revised together. A new Part 0: General model for gazetteers and spatial referencing been added. This provides a common structure for gazetteers of any class of geographic object.BS 7666 now comprises the following parts: Part 0: General model for gazetteers and spatial refe

9、rencing;Part 1: Specification for a street gazetteer;Part 2: Specification for a land and property gazetteer;Part 5: Specification for a delivery point gazetteer.These parts supersede BS 7666-1:2000, BS 7666-2:2000, BS 7666-3:2000 and BS 7666-4:2002. The new Part 0 has subsumed Part 3: Specification

10、 for addresses. Part 1 has subsumed Part 4: Specification for recording public rights of way but in other respects is similar in scope to that published previously. The scope of Part 2 is largely unchanged. Part 5 is new in scope. Parts BS 7666-1:2000, BS 7666-2:2000, BS 7666-3:2000 and BS-7666-4:20

11、02 are now withdrawn. Thus Parts 3 and 4 will not form part of the standard. This part has been numbered Part 5 to avoid any confusion with the withdrawn standards.This part is new and provides a specification for a gazetteer of delivery points. It defines a delivery address, which is different from

12、 the geographic address defined in Part 0 of this Standard, in that it is a set of routing instructions, based upon the organizational structure of the delivery service organization rather than the actual real-world geography. It is applicable to a range of delivery and collection services, and not

13、only mail. Presentational conventionsThe provisions of this standard are presented in roman (i.e. upright) type. Its requirements are expressed in sentences in which the principal auxiliary verb is “shall”.Commentary, explanation and general informative material is presented in smaller italic type,

14、and does not constitute a normative element.Contractual and legal considerationsThis publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application.Compliance with a British Standard cannot confer immunity from legal obligations.

15、 BSI 2006 iiiBS 7666-5:2006IntroductionThis part of BS 7666 is designed to facilitate the creation and maintenance of delivery point gazetteers of varying scope, from specialist interest in a restricted area to universal coverage for general use. It has been designed in the expectation that such gaz

16、etteers will increasingly need to be matched, merged and cross-referenced in order to promote access to, and sharing of, delivery point data.A key design principle is that the application of this part of the standard, in conjunction with the other parts of BS 7666, will help to establish a common se

17、t of identifiers for use across a range of applications.This page deliberately left blankBS 7666-5:2006 BSI 2006 1BS 7666-5:20061 ScopeThis part of BS 7666 specifies the logical data structure and data content for a gazetteer of delivery points, for purposes of identification, access and validation

18、of service requests. It does not provide a database design or a transfer format. It provides a method of referencing delivery points by means of unique references and descriptive delivery addresses. This part of BS 7666 is for use by suppliers of delivery and collection services, such as distributio

19、n organizations. It facilitates data sharing to enable the provision of collaborative services, and provides a consistency of references for analysis and planning purposes.2 Normative referencesThe following referenced documents are indispensable for the application of this document. For dated refer

20、ences, only the reference cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.BS 7666-0, Spatial datasets for geographical referencing Part 0: General model for gazetters and spatial referencingBS ISO 8601, Data elements and interch

21、ange formats Information interchange Representation of dates and timesBS ISO 639-2, Codes for the representation of names of languages Part 2: Alpha-3 code3 Terms and definitionsFor the purposes of this part of BS 7666, the terms and definitions given in BS 7666-0 and the following apply.3.1 deliver

22、y pointpoint to which a service is delivered on a regular basisNOTE Examples of delivery points are buildings receiving mail or deliveries from couriers, industrial and commercial sites receiving deliveries of goods and buildings receiving waste collection services.4 Delivery point gazetteer require

23、mentsA delivery point gazetteer shall be a gazetteer as defined in Part 0 of this standard. Delivery points recorded in the gazetteer shall be locations as defined in Part 0 of this standard. These are shown in Figure 1. 2 BSI 2006BS 7666-5:2006Figure 1 Delivery point gazetteer model NOTE 1 The diag

24、ramming convention used in this figure is explained in Annex B. A Delivery Point Gazetteer is a specialization of a Gazetteer and a Delivery Point is a specializations of Location as defined in Part 0 of this British Standard. The gazetteer shall contain all instances of delivery points, as defined

25、by the gazetteer scope. NOTE 2 A checklist for conformity for a gazetteer of delivery points is given in Annex A. All dates recorded in the gazetteer shall be in accordance with BS ISO 8601, consistently either in the basic format (YYYYMMDD) or in the extended format (YYYY-MM-DD).5 Gazetteer metadat

26、a5.1 Mandatory elementsA gazetteer shall have the following mandatory (M) metadata elements:a) name: name of the gazetteer, e.g. “Postal Delivery Point Gazetteer”;b) scope: description of the content of the gazetteer, including the type of service received, e.g. “Premises receiving a postal delivery

27、 from Royal Mail”;c) territory of use: geographic domain of the gazetteer, e.g. “Great Britain”;d) gazetteer owner: the organization that has overall responsibility for the gazetteer, e.g. “Royal Mail”;e) custodian: organization or officer responsible for compilation and maintenance, e.g. “Royal Mai

28、l Address Management Unit”;f) coordinate system: coordinate reference system used to describe position, e.g. “National Grid of Great Britain”;g) spatial referencing system(s): the spatial reference system(s) used in the gazetteer e.g. “postal address”;h) current date: the date at which the gazetteer

29、 can be considered to be current.NOTE The current date is not necessarily the date of creation or date of last update of the gazetteer. LocationGazetteergazetteerspecializationlocation specializationaggregationDelivery Point GazetteerDelivery Point1n BSI 2006 3BS 7666-5:20065.2 Optional elementsA ga

30、zetteer shall have the following optional (O) metadata elements, where appropriate:a) metadata date: date of last update of metadata;b) language(s): the languages used in the gazetteer for names, identified by a three letter code as specified in BS ISO 639-2 (see Annex C); NOTE Where no language is

31、specified, a default of English is assumed. c) character set(s): any non-English character set(s) used to record entries in the gazetteer, e.g. Gaelic;d) coordinate axis units: unit of measure of coordinates, e.g. metres;e) primary classification scheme: details of any primary classification scheme

32、used to classify entries in the gazetteer;f) secondary classification scheme: details of any secondary classification scheme used to classify entries in the gazetteer;g) state coding scheme(s): details of any coding scheme used to define the logical state of a delivery point recorded in the gazettee

33、r (see Annex C);h) external cross-referencing scheme(s): details of external cross-referencing schemes used in the gazetteer, e.g. Unique Property Reference Numbers (UPRNs).5.3 StructureThe record shall be in accordance with Table 1.NOTE 1 A UML (Unified Modelling Language) model is shown in Annex A

34、, which also shows the associations with the other classes. Examples are given in Annex D. NOTE 2 As appropriate, additional metadata elements can be added by the user in the context of a particular gazetteer. Table 1 Gazetteer metadataName aUML name bObligation cMaximum occurrences dData type ename

35、 name M 1 CharacterStringscope scope M 1 CharacterStringterritory of use terOfUse M 1 CharacterStringmetadata date metaDat O 1 Datelanguage language O N Language fcharacter set charSet O N CharacterStringgazetteer owner gazOwner O 1 CharacterStringcustodian cust M 1 CharacterStringstate coding schem

36、e statCodScm O 1 CharacterStringcoordinate system coordSys M 1 CharacterStringcoordinate axis units coordUnit O 1 CharacterStringspatial referencing system spatRefSys M N CharacterStringprimary classification scheme pClassScm O 1 CharacterStringsecondary classification scheme sClassScm O 1 Character

37、String(Continued)4 BSI 2006BS 7666-5:20066 Delivery point records6.1 Delivery pointsEach record in the gazetteer shall identify a single instance of a delivery point.6.2 Mandatory attributesA delivery point recorded in the gazetteer shall have the following mandatory (M) attributes:a) identifier: un

38、ique identifier of the delivery point;b) start date: date at which the delivery point came into existence;NOTE 1 When the start date is not known, a notional date at which it is known to exist should be used, e.g. 2000-01-01.c) entry date: date when the delivery point was added to the gazetteer;d) u

39、pdate date: date of last update of the delivery point record;e) position: a pair of coordinates for the delivery point;NOTE 2 Coordinates should be given as full numeric values.f) spatial reference(s): one or more spatial references for the delivery point, in the form of a delivery address (see 6.5)

40、;g) administrator: organization responsible for defining the characteristics of the delivery point.6.3 Optional attributesWhere appropriate, a delivery point recorded in the gazetteer shall also have one or more of the following optional (O) attributes:a) alternative identifier: other identifier of

41、the delivery point;b) primary classification: classification of the delivery point according to a defined classification scheme;NOTE 1 The primary classification scheme is described in the metadata associated with the gazetteer (see 4.2.2).c) secondary classification: sub-classification of the deliv

42、ery point according to a defined classification scheme;NOTE 2 The secondary classification scheme is described in the metadata associated with the gazetteer (see 4.2.2).Table 1 (Continued)Name aUML name bObligation cMaximum occurrences dData type ecurrent date curdat M 1 Dateexternal cross-referenci

43、ng scheme extXRefScm O N CharacterStringa The form of the attribute.bThe name of the attribute used in the UML model.cWhether the attribute is mandatory (M) or optional (O).dWhether the attribute is single-valued (1) or may have multiple values (N).eThe allowable set of values for the attribute.fSee

44、 Annex C. BSI 2006 5BS 7666-5:2006d) external cross-reference: identifier of a related object recorded elsewhere, e.g. the Unique Property Reference Number (UPRN) of the basic land and property unit (BLPU) or BLPUs associated with the delivery point;e) end date: date at which delivery point ceased t

45、o exist;f) state: code identifying the logical status of the delivery point (see Annex C);NOTE 3 The state classification scheme is described in the metadata associated with the gazetteer (see 4.2.2).g) current state date: date at which delivery point achieved its current state;NOTE 4 When the curre

46、nt state date is not known, a date when it was known to be in that state should be used, e.g., the date when the delivery point was added to the gazetteer.h) related delivery point(s): the identifier of any related delivery point(s).6.4 StructureThe delivery point record shall be in accordance with

47、Table 2.NOTE 1 A UML (Unified Modelling Language) model is shown in Annex A, which also shows the associations with the other classes. Examples are given in Annex D. NOTE 2 As appropriate, additional attributes can be added by the user in the context of a particular application.NOTE 3 Tests for chec

48、king conformance for delivery point records are given in Annex B. Table 2 Attributes of delivery pointName aUML name bObligation cMaximum occurrences dData type eidentifier id M 1 CharacterStringalternative identifier altId O N CharacterStringprimary classification pClass O 1 CharacterStringsecondar

49、y classification sClass O 1 CharacterStringstart date startDat M 1 Dateentry date entryDat M 1 Dateupdate date updatDat M 1 Dateend date endDat O 1 Datestate stat O 1 CharacterStringcurrent state date curStatDat O 1 Dateposition position M 1 Point fadministrator admin M 1 CharacterStringspatial reference spatRef M N DeliveryAddressexternal cross-reference extXRef O N CharacterStringrelated delivery point relLoc O N Delivery pointa The form of the attribute.bThe name of the attribute used in the UML model.cWhether the attribute is mandatory (M) or optional