User's Manual for Spatial Data Product …User's Manual for Spatial Data Product Specification...

Technical Report of the Geographical Survey Institute A1-No.264

User's Manual for Spatial Data Product

Specification Description

May 2002

ii

Preface to English Edition

In Japan, the Geographical Survey Institute and private companies have jointly created and updated the Japanese

Standards for Geographic Information (JSGI) in accordance with several standards in the draft stage to arrange

implementation tests and utilization manuals since before the international standard based on ISO/TC211 is

issued.

User's Manual for Spatial Data Product Specification Description is created to spread the standards based on

ISO/TC211 in Japan. This manual assumes that national organizations, local public organizations, and private

companies use the ISO standards, and has the purpose that is different from that of ISO19131 Data Product

Specifications. However, in order to help consider creating the standard for data product specifications or use the

ISO standards in countries, this English version is created.

The original of this manual is created from JSGI that is created in Japanese based on the draft standard created in

English. Therefore, this English version is created through the processes of translation from English to Japanese,

and from Japanese to English. Because of the time limit, the retranslated English technical terms are not

examined carefully, and note that some terms are not correct.

XML tag names are described alphabetically, but many of them are based on the Japanese alphabet (Roman

character) notation instead of English because it is assumed that they are used in Japan. These tag names are not

forcibly translated into English but "Note(E)" is appended to them. Japanese own terms are also supplemented

with "Note(E)," but some of unimportant terms may remain in Japanese or have no supplementary explanation.

Appendix B gives an overview of Japan Metadata Profile, UML and XML, and is included in Contents, but is

omitted.

Because JSGI is not based on the latest ISO/TC211 draft standard and Japanese-own revisions are made in JSGI,

care is needed to use JSGI. For example, JSGI-Metadata remains based on the ISO19115 First Draft because the

Japan Metadata Profile (JMP) in which Japanese own revisions are made based on the First Draft has already been

used for clearinghouses in Japan. Other JSGI standards are about half a year to one year later than the latest ISO

draft standard. In future, JSGI and utilization manuals will also be updated as standardization by ISO makes

progress.

The English version of some reports on and materials related to the results of implementation tests will also be

created and released.

The Secretariat of Joint Research Project

Geographical Survey Institute

May 2002

i

Table of Contents

Chapter 1 Overview ........................................................................................................................ 1

1. Product Specification Description.....................................................................................3 1.1 Requirement Specification and Procurement Specification ........................................................ 3

1.2 Product Specification and Production Specification ............................................................... 3

1.3 Product Specification description .......................................................................................... 5

3. Purpose of This Manual....................................................................................................6

4. Scope of This Manual .......................................................................................................8

5. Using This Manual...........................................................................................................8

Chapter 2 Geographic Information Standard..................................................................................... 9

1. Purpose of Geographic Information Standard..................................................................9

2. Overview of Geographic Information Standard.............................................................. 11 2.1 Data Structure ............................................................................................................... 12

2.2 Quality......................................................................................................................... 12 2.3 Metadata ...................................................................................................................... 13

2.4 Encoding...................................................................................................................... 13

2.5 Spatial Reference System................................................................................................ 14

2.6 Feature Catalogue .......................................................................................................... 15

Chapter 3 Contents of Product specification description.................................................................... 16

1. Overview of Spatial Data................................................................................................16 1.1 Purpose of Spatial Data................................................................................................... 16

1.2 Geographic Scope of Data............................................................................................... 17 1.3 Temporal Scope............................................................................................................. 17

1.4 References (Spatial Reference System, Coordinate System, Temporal Reference, Weights and

Measures) ............................................................................................................................ 17

1.5 Temporal Reference System............................................................................................ 18

2. Contents of Data to be Acquired.....................................................................................18 2.1 Feature Definition.......................................................................................................... 19

2.1.1 Overview of feature definition ................................................................................... 20 2.1.2 Feature definition technique ...................................................................................... 20

2.1.2.1 Feature definition ............................................................................................... 20

2.1.2.2 Spatial attribute .................................................................................................. 21

2.1.2.3 Temporal attribute .............................................................................................. 21

2.1.2.4 Thematic attribute and thematic diagram................................................................ 22

2.1.2.5 Feature relationship ............................................................................................ 22

2.2 Data Structure and Application Schema............................................................................. 24

ii

2.2.1 Data structure.......................................................................................................... 24

2.2.2 Application schema ................................................................................................. 25

2.2.3 UML class diagram................................................................................................. 28

2.3 Quality......................................................................................................................... 29

2.3.1 Quality (concept and necessity).................................................................................. 29

2.3.1.1 Concept............................................................................................................ 29

2.3.1.2 Necessity.......................................................................................................... 30 2.3.2 Quality contents ...................................................................................................... 30

2.3.2.1 Completeness .................................................................................................... 32

2.3.2.2 Logic consistency............................................................................................... 33

2.3.2.3 Positional accuracy............................................................................................. 33

2.3.2.4 Temporal accuracy............................................................................................. 34

2.3.2.5 Thematic accuracy............................................................................................. 35

2.4 Requirement Definition Table .......................................................................................... 35 2.4.1 Example of requirement definition ............................................................................. 35

2.4.2 Contents of requirement definition.............................................................................. 36

2.5 Example of Describing Application Schema for Feature....................................................... 38

2.6 Required Quality ........................................................................................................... 39

2.6.1 Describing quality requirement definition .................................................................... 39

2.6.2 Analyzing required quality........................................................................................ 40

2.6.3 Notes on defining quality.......................................................................................... 42

3. Quality Evaluation Method............................................................................................44 3.1 Quality Comparison Targets (Material and Spot)................................................................. 44

3.1.1 Quality comparison material...................................................................................... 44

3.1.2 Notes on quality comparison material......................................................................... 44

3.1.2.1 Material for data creation..................................................................................... 44

3.1.2.2 Temporal scope.................................................................................................. 44

3.1.2.3 Data not described in quality comparison material................................................... 44

3.2 Concrete Evaluation Method ........................................................................................... 44 3.2.1 Direct evaluation method .......................................................................................... 45

3.2.1.1 External evaluation method and internal evaluation method....................................... 45

3.2.1.2 Means of implementing direct evaluation method .................................................... 45

3.2.1.3 Full inspection................................................................................................... 46

3.2.1.4 Sampling inspection ........................................................................................... 46

3.2.1.5 Visual inspection................................................................................................... 47

3.2.1.6 Inspection survey.................................................................................................. 47

3.2.2 Indirect evaluation method........................................................................................ 47 3.2.3 Concrete example of describing quality evaluation method............................................. 47

3.2.3.1 Typified quality evaluation method........................................................................ 48

iii

3.2.3.2 Quality evaluation list ......................................................................................... 50

3.2.3.3 Evaluating quality evaluation results...................................................................... 50

4. Metadata........................................................................................................................52 4.1 Use of Metadata ............................................................................................................ 52

4.2 Metadata Structure and Items........................................................................................... 52

4.3 Example of Description .................................................................................................. 57

5. Encoding Specification....................................................................................................58 5.1 Encoding...................................................................................................................... 58

5.2 Data Interchange............................................................................................................ 58

5.3 Encoding Rule .............................................................................................................. 60

5.4 Example of Coding DTD ................................................................................................ 63

6. Contents (Product)..........................................................................................................64

7. Other Items ....................................................................................................................65 7.1 Definition of Term ......................................................................................................... 65 7.2 Materials ...................................................................................................................... 65

7.3 Restriction.................................................................................................................... 65

7.4 Reference Standards and Special Terms ............................................................................. 66

Chapter 4 Flow of Creating a Product specification description.......................................................... 67

1. Purpose of This Chapter.................................................................................................67

2. Chapters and Items to Be Described in a Product specification description...................67

3. Procedure of Creating a Product specification description..............................................68 3.1 Defining Requirements................................................................................................... 69 3.2 Examining an Application Schema ................................................................................... 69

3.2.1 Defining a feature (described in Section 2.1 of Chapter III)............................................. 69

3.2.2 UML class chart (described in Section 2.2 of Chapter III)............................................... 73

3.2.2.1 Defining an attribute ........................................................................................... 73

3.2.2.2 Defining a feature relationship (described in Section 2.1.2.5 of Chapter III).................. 74

3.3 Examining a Range and a Reference System...................................................................... 75

3.3.1 Range (Sections 1.2 and 1.3 of Chapter III).................................................................. 75 3.3.2 Reference system (Sections 1.4 and 1.5 of Chapter III)................................................... 75

3.4 Examining Data Quality (Described in Sections 2 and 3 of Chapter III)................................... 76

3.4.1 Quantitative quality.................................................................................................. 76

3.4.2 Non-quantitative quality ........................................................................................... 79

3.5 Examining the Data Evaluation Method ............................................................................ 79

3.5.1 Selecting a quality evaluation method (described in Section 3.2 of Chapter III).................. 79

3.5.2 Comparison target (described in Section 3.1 of Chapter III; see also Section 7.2) ................ 79

3.6 Examining Metadata (Described in Section 4 of Chapter III)................................................. 79

iv

3.6.1 Examining a profile ................................................................................................. 79

3.6.2 Instructing to create metadata .................................................................................... 80

3.7 Examining the Creation of a Encoding Specification (Described in Section 5 of Chapter III) ...... 80

3.7.1 Schema conversion rules........................................................................................... 80

3.7.2 Instance conversion rules .......................................................................................... 83

3.7.3 Description for when an enumerated type thematic attribute exists ................................... 84

3.8 Organizing Data ............................................................................................................ 85 3.8.1 Abstract of product (Section 1.1 of Chapter III) ............................................................ 85

3.8.2 Check of delivered goods.......................................................................................... 85

3.8.3 Reference standards and specifications (Section 7.4 of Chapter III).................................. 86

3.8.4 Terms and abbreviations (Section 7.1 of Chapter III) ..................................................... 86

3.8.5 Identifying a product specification description.............................................................. 86

Appendix A Typical Examples of Product specification descriptions................................................... 87

1. Example of Spatial Data Foundation 2500.....................................................................87

2. Example of Disaster Prevention System Data (Creation Experiment)...........................91

3. Example of River Spatial Data.......................................................................................99

Appendix B Reference Material (in Japanese)............................................................................... 103

1. Explanation of Metadata Editor for Metadata Standard Format JMP (Abstract) .......103

2. Overview of UML (Necessity and Effects) ....................................................................103

3. Overview of XML (Necessity and Effects)..................................................................... 119

Appendix C Participants...................................................................................................... 120

Participanting Enterprises List of Joint Research Project..................................................120

Members List of developing User’s Manual for Product Specification Description (Japanese Edition)...............................................................................................................................121

User's Manual for Spatial Data Product Specification Description, GSI TR A1-No.264 1

Spatial Data Product Specification Creation Manual

Chapter 1 Overview

Diffusion of the GIS is expected to lead to stimulation of economic and social activities and improve the

quality of the life of the people. The requirement that may be critical to the realization of its effect is that

such spatial data as map data that forms the GIS framework is created early, distributed as the social

infrastructure, and used in a wide range of applications. Efforts toward standardization related to spatial

data have been made worldwide as well as in Japan to arrange the environment in which data is effectively

used.

International standards related to spatial data have been sequentially completed through ISO/TX211

activity. In response to this, in Japan, the "geographic information standard" is being arranged as a national

standard. The standards that have been reviewed by ISO/TC211 and approved at the regular convention of

ISO have been sequentially translated and prepared as Japan Industrial Standards (JIS).

Regarding spatial data itself, such infrastructure spatial data as maps above all, such public organizations

as countries and local self-governing bodies that have arranged basic maps since before are expected to

create and publish the data by adopting the digital system. Private companies have also emerged to work

on creation and sale of spatial data as a new business opportunity. However, if each of these data items is

created in its specific format, it may cause hindrance to its distribution. Therefore, the standard must be

defined to eliminate the causes of hindrance. In this connection, it is significant to disseminate the

geographic information standard that is the spatial data standard in Japan.

This manual summarizes the technical items required by these public organizations(Ministry of Land,

Infrastructure and Transport) and private sectors to arrange spatial data based on the "geographic information

standard" and with efficient arrangement and effective use of data kept in mind. This manual also assumes

that the organizations utilize it as the guide for creating the fundamental product specification to create

spatial data in future.

This manual is based on joint research made by Geographical Survey Institute of the Ministry of

Construction and 38 private companies (listed at the end of this manual) as part of "Research on Operation


of Geographic Information Standard" (1999 to 2001), joint research made by government and private sector

initiated by the Ministry of Construction.


1. Product Specification Description

1.1 Requirement Specification and Procurement Specification

Generally, when a product is manufactured, the specification according to which the product is

manufactured must be clarified. This is also true of spatial data. Unless the purpose, contents, and quality

of spatial data to be created are clarified, the target spatial data cannot be created. In other words, a certain

spatial data must be created based on the requirements of the person who requires the data. When spatial

data is to be used, various conditions of which the product (dataset) is required are called requirements specification. The examples of required specification are how spatial data is to be utilized, what feature is

included in the dataset, what is the definition of the feature (including acquisition criteria), and what is the

degree of its quality. The recording format of spatial data to be created, as digital data must also be clarified.

Spatial data is actually created based on this required specification.

If a person who has clarified the required specification does not create data but requests other person, the item

that clearly specifies the request contents is required before request. This item is called procurement

specification. In addition to the required specification, the order specification consists of the agreements if data is not created by the term of work or as specified (quality is low) or such order and delivery condition

items as the format in which data is to be delivered. Generally, when a local self-governing body consigns a

business and places an order, the "generic specification" is used. This clearly specifies the items common to

the action of order when a self-governing body places an order for a consigned business. Consequently, the

common specification can be said to be a part of order specification excluding the required specification.

1.2 Product Specification and Production Specification

Then, it becomes a problem how spatial data is actually created. What specifies such items as equipment to be used, its performance, and inspection method in each process in detail is called production specification.

Most of specifications have referred to this creation specification before. The public survey regulations that

have been used in the survey field may also be a kind of creation specification.

In this way, the specification depends on the situation where and the purpose for which it is used. So what is

a really important matter? In order to use a certain GIS to do something, it may be most important to clarify

the person (planner) who plans to create spatial data that can conform to it, the person (creator) who creates or

is asked to create spatial data, the person (user) who attempts to use spatial data created by other person for other than the original purpose of creating it, and the requirement (performance) of spatial data as product

although it may slightly differ depending on each situation. What clearly specifies this requirement is called

product specification in geographic information. That is, it materializes the required specification.

When spatial data is created, information technology is indispensable. Spatial data cannot be created

without computer. This information technology is continuing to evolve rapidly. Under the present

conditions, the personal computer is said to be obsolete after three months. Software that incorporates new

technologies is also materialized one after another day by day. If information technology is used to create

spatial data in this way, such work method-oriented specification as creation specification may not be created by the person who plans to create spatial data but may be created by the creator who is devoted to actual

creation to use the latest technology. The side that entrusts creation of spatial data should devote all its

energies to clarify the requirement of the spatial data whenever possible. Giving an order in accordance with


the conventional creation specification is significant in that the creation technique and the performance of

equipment to be used secure the quality of the created product. As described later, however, it is only a part

of quality and giving an order in accordance with the creation specification is also likely to hinder the ingenuity

of the creator.

The general public seems to imagine that map creation and spatial data creation closely resemble each other.

Map creation places great importance on standardization of the positional precision and representation method

of the feature to be represented, and map creation in general has similar requirement even if the reduced scale is different. On the other hand, when spatial data is created, a planner is free to decide what is converted to

data and the level of positional precision at which data is created (variety of needs). As compared with map

creation, the significance of standardizing the creation technique is considerably lower. However, the

creation specification, that is, the policy for the creation method as to how what equipment is used to create

data is required. When spatial data is created, the creation specification is actually creator dependent and may

be an agreement for only one creation time. Actually, such specification as this will be created as the

working Specifications by a creator to carry out work in future, and may be presented to the creation consignor (planner). Figure 1-1 shows the relationship among the specifications in the range from planning

of spatial data creation to use of spatial data.

Figure 1-1

Note1 (E)

In the "requirement specifications," "procurement specifications," and "production specifications," Japanese terms

are translated into English, and the English expression may not always make sense.

Note2 (E)

The Public Survey Work Regulation is the engineering specifications used by central or local government

organizations to give an order for business related to survey. In Japan, the Survey Act requires that the planning

organization establish the Public Survey Work Regulation beforehand.

Note3 (E)

The Work Specifications describe the concrete method and plan for performing work.

Planning

Prodcustionn specification

(creation method)

Use

Production specification

Procurement specification

Creation


1.3 Product Specification description

The product specification description summarizes the previously described product specification using

the common representation technique. For example, in the specification list of such electronic equipment

as personal computer, the representation of the same matter depends on the manufacturers. If the

representation of the specification is not standardized in this way, it is difficult for the general public to select a really desired product. What summarizes the product specification description represented using the

common representation technique or the product specification is expected to be very useful in distributing

spatial data to people from all levels of society.

From a practical viewpoint, the product specification description is used by the person who planned to

create spatial data to clearly specify its requirement, and can be said to be an integral part of the order

specification when spatial data is created. The general user of spatial data usually uses the clearinghouse to

search for the user-desired spatial data. The user then determines from metadata in the clearinghouse whether the spatial data is the user-desired data. The user may also be able to determine whether the data

conforms to the user's requirement more by browsing the application schema. If the product specification

description is also opened to the user, more detailed contents will ensure that user's choice is based on the

product specification description.

2. Positioning of This Manual

This manual is not intended for creation of the product specification description that simply clarifies the

requirement specification of spatial data but serves as a guide to creation of the product specification

description that summarizes the requirement specification for creating spatial data based on the "geographic information standard." Because the "geographic information standard" conforms to ISO 19100 series and

is intended for geographic information and information processing engineer, it can no longer be denied that it

is slightly difficult for the general public. This manual helps even the general public who plans to create

spatial data create the product specification description for spatial data based on the "geographic information

standard." Actually, however, an expert must be asked to create the product specification description or the

"geographic information standard" must be understood. Otherwise, the primary product specification

description cannot be created. The "geographic information standard" is the standard of the concept concerning geographic information,

and assumes that information technology is utilized. Therefore, the "object-oriented" concept handled by

information technology must be understood. An overview of UML (Unified Modeling Language) handled

by the application schema and XML (eXtensible Markup Language) used for encoding must also be

required as knowledge. In this sense, this manual also contains an explanatory implication of the

"geographic information standard." Because this manual aims at being practically utilized to create actual

spatial data, this manual is also expected to be utilized as the guideline for operating the "geographic

information standard." Figure 1-2 shows the relationship between the "geographic information standard" and the interchange standards.


Figure 1-2

3. Purpose of This Manual

The product specification description that is created according to this manual aims at creating spatial data based on the "geographic information standard" first. The purpose of this manual is enabling

understanding of an overview of "geographic information standard" and creation of the product specification

description that suits all items of the standard. As previously described, however, the "geographic

information standard" itself must also be referenced for details. Creation of the actual product specification

description also requires such special know ledges as UML and XML for information technology. These

knowledges must also be left to experts or learned from proper reference books whenever appropriate.

The second purpose of this manual is promoting introduction of the latest technology by changing the creation specification-oriented specification that have conventionally been used between the person who

places an order and the person who receives the order to the product specification-oriented specification. In

a rapid technological innovation age like today, the fixed work policy-oriented specification is likely to

hinder efficient creation of spatial data. The requirements of spatial data really depend on the situation

where it is used. To request creation of this spatial data, the person who places an order should make

efforts to clarify the data requirements and leave the creation method to the creator.

Today the usefulness of the GIS has been recognized in many fields. However, it is hard to say that

arrangement of spatial data that is the contents of the GIS is underway. Although the national spatial data infrastructure arrangement project has been accelerated rapidly, arrangement of spatial data to be actually

utilized must be indebted to efforts of self-governing bodies and private sector. Promoting spatial data

arrangement by using this manual in this case is one of purposes of this manual.

IInntteerrcchhaannggee ssttaannddaarrdd Feature catalog

PPrroodduucctt ssppeecciiffiiccaattiioonn

DDaattaa ssttrruuccttuurree MMeettaaddaattaa

EEnnccooddiinngg mmeetthhoodd

SSppaattiiaall rreeffeerreennccee QQuuaalliittyy

Production Specification creation

PPoorrttrraayyaall

Spatial data based on "geographic information standard"

TTeerrmmiinnoollooggyy


The law has required public survey notification when a self-governing body creates a map since before.

This is the system used by the nation to make adjustment so that similar survey and map creation are not

doubly done. Unless the specification contents of spatial data are clear, the same spatial data is likely to be

created in many fields to result in duplicated investment. In this sense, the requirement that this manual is

used to create the product specification description and metadata is created may help prevent this duplicate

investment. Regarding a map that is used in a wide range, it was necessary to represent features as

accurately and in details as possible according to the graphical regulations. However, spatial data may not always require this condition. If the positional relationship between features is clear, the accuracy of

feature shape itself may not be so important. For this reason, working like conventional map creation may

create more products than necessary. This goes against more efficient work and results in an increasing

burden through the project that is always costly. If the product specification description is available to

clarify the requirement of spatial data to be created, such excess specification will also be prevented. This

may reduce the arrangement cost of spatial data.

From the viewpoint of spatial data user, the product specification description that is created according to this manual can become a material that helps understand details of data set that is difficult to know from

metadata. This manual does not require that the product specification description be opened, but the

opened product specification description may not only become a material useful for the user to know more

detailed contents of the data set but also lead to promotion of spatial data interchange (reuse).

As previously described, this manual aims at contributing much to diffusion of the GIS finally.


4. Scope of This Manual

The product specification description creation manual gives some instructions on how the product

specification description is created on the assumption that a person plans to create spatial data for a purpose

and the third party other than the person is requested to create data. Because we known from our

experience that the person who plans to create spatial data and the person who actually creates data often

differ when spatial data is created, explanations are given on such the assumption. This manual can also be

used to create the product specification description in the situation that differs from this assumption. In a word, the product specification description for spatial data describes details of spatial data and can be said to

be a plan of spatial data. In other word, the product specification description describes what ideal spatial

data to be created should be like, or not only represents what true spatial data to be created should be but also

serves as a yardstick for examining whether the created data is based on the plan. This manual should be

used with this point kept in mind.

5. Using This Manual This manual has four chapters and two appendixes. Chapter 1, "Overview" describes the definition of

product specification description and the entire organization of this manual. Chapter 2, "Geographic

Information Standard" briefly explains the geographic information standard. Chapter 3, "Contents of

Product specification description" explains various terms used to create the product specification description.

Chapter 4, "Flow of Creating Product specification description" is the core of this manual. Doing work

according to this flow facilitates creation of the product specification description. Appendix A, "Examples

of Product specification description" contains some samples of product specification description.

Appendix B, "Reference Materials" describes the required reference materials or the method of obtaining them.

This manual may be read from Chapter 2 sequentially, but Chapter 4, "Flow of Creating Product

specification description" that is the core of this manual can be read carefully and the Chapters 2 and 3 can

be read when an unclear term or the concept difficult to understand appears. If more detailed knowledge

about the geographic information standard must be obtained, the geographic information standard itself

should be read. This manual is created based on the geographic information standard as of March 2002

and may be revised in future.


Chapter 2 Geographic Information Standard

In various businesses, various information items have been conventionally put in order and analyzed on

paper and used to make decision. However, needless to say, at present, computer, word processor, and

spreadsheet software have been introduced to contribute to more efficient business. This is also true of

maps. A line has been drawn for city planning on a paper map by now. Because the map is used in a

wide range and effective, it has been more and more frequently input to the computer and utilized. As a result, spatial data has been created at every location and distributed via such electronic media as floppy disk

and MO disk and Internet network. Such spatial data of high utility value as this does not serve as simple

information but provides the information infrastructure in a broad sense. Consequently, ISO/TC211 was

established in 1994 to aim at worldwide distribution of this spatial data (geographic information) and the

international standard related to this spatial data (geographic information) has been reviewed. The

geographic information standard in Japan is the domestic standard that takes into account the actual situation

of Japan based on the contents reviewed by ISO/TC211. If the items reviewed by ISO/TC211 become the international standard, the items will be prepared as Japan Industrial Standard (JIS) eventually. Naturally

enough, this Japan Industrial Standard (JIS) may become closely related to the geographic information

standard. This chapter gives an overview of this geographic information standard.

1. Purpose of Geographic Information Standard

The GIS is one of the most important technologies in future development of Japan. Conventionally,

information in various businesses has been repeatedly put in order and conveyed on paper. Needless to say,

the computer was introduced for what is called OA in the past, and various equipments such as word processors and software have been introduced to contribute to more efficient business. However, although

a map is used in a wide range and effective, its characteristics have delayed input of the map to the computer

for utilization. The GIS has attracted attention as the system that enables handling of this map on the

computer as well as instantaneously ensures spatial analysis that has required considerable labor and time

before. Data handled by this GIS is called spatial data. Its entity ranges from digitized information about

a paper map, various statistical information items, spot photo, and aerial photo to CAD data. Such

information related to the position can be handled in a wide range. The GIS vendors have released various GISs ranging from the system that simply displays a map on the

computer to the system that ensures advanced spatial analysis. As with word processor data, interchange of

such various spatial data as these between the systems whose vendors are different is not easy. Because

information related to a map, in other word, information related to the position is handled; spatial data is

positioned as the information infrastructure in the same way as the infrastructure for the conventional lifeline.

Therefore, promoting creation and distribution of spatial data is a great problem vital to future development

of Japan.

From 1980s to the present, the GIS has been developed under the control of private sector. Spatial data on which this GIS is based is also entirely dependent on the GIS, and has been created according to its

specific standard. That is, a big problem that the data format varies between systems occurred. If data is

to be used in other system, an effort to create a conversion program is indispensable. This means that a


conversion program is created for each relevant system. It is an inefficient situation in which a new

interchange program is developed each time a new GIS is developed. This means that distribution of

spatial data cannot be expected. If information as to the coordinate system on which mutual geographic

information is based, the method of projections of the map from which the information is digitized and the

data structure of the information is not known, it becomes difficult to use geographic information for desired

spatial analysis.

For this reason, the geographic information standard aims at distribution of spatial data by presenting several elements that make up geographic information that has been or will be created according to such

standard specifications as metadata, application schema, and catalogue to ensure smooth data intercahnge

between different systems.


Figure 2-1

2. Overview of Geographic Information Standard

The geographic information standard is established with the actual situation in Japan taken into account

based on the items reviewed by ISO/TC211, and conforms to ISO/TC211. Currently, the items reviewed

by ISO/TC211 include 35 items from "reference model" to "geographic information item registration

procedure" (as of November 2001). The geographic information standard covers the items limited to such

System A System B

System C System D

Present state of mutual use of spatial

System A System B

System C System D

Geographic


the contents required for data interchange as spatial data structure, quality, metadata, catalogue, and spatial

reference but does not include all items. However, the increase of the target items when necessary in future

is planned. This section gives an overview of the items being currently reviewed.

2.1 Data Structure

The item that is most important for spatial data is the data structure. It is necessary to define information

items, e.g., which feature is defined, what its spatial attribute is, what thematic attribute is contained, and how the feature is related to other feature. The geographic information standard identifies how spatial data

is visible or available conceptually and logically as the spatial data structure and describes the data structure

as "application schema" to specify how the elements is represented based on the concept of application

schema. There are several techniques of writing such data structure as this. The geographic information

standard specifies that the UML class diagram often used by system engineering is used to write the data

structure. This is because people concerned in geographic information jointly possess various spatial data

structures accurately through the common representation of UML. The feature specified here is defined to be directly or indirectly related to the positions on the earth. A

feature consists of feature attribute, feature relationship, and feature function as follows:

Feature

Feature

attribute

Spatial attribute

Temporal attribute

Thematic attribute

Quality attribute

Geographic identifier

Feature

relationship

Set

General and special

Spatial topology

Temporal topology

Logic

Feature function

Not applicable in “spatial data structure”

Geometric and topological

object elements

Temporal geometric and temporal

topological elements

Graphics, character, numeric,

image, and voice

Figure 2-2

2.2 Quality

There are all sorts of quality, and the definition of quality depends on the industries and persons. The

quality of spatial data in the geographic information standard refers to the difference between the requirement (called universe of discourse) for spatial data described in the product specification description

and actual spatial data. Therefore, the items that exist in the real world and spatial data are not always

compared for evaluation. Spatial data is compared with the requirement described in the product


specification description for evaluation. In short, this means that quality cannot be described without the

product specification descriptions in which the universe of discourse is clarified.

Imagine a guide map, for example. On the guide map, major objects and the roads to arrive at them are

drawn, but the extended or winding roads are not always accurate. However, the quality required of the

guide map is the accuracy of only connection between major objects and roads. If only the connection is

correct, the guide map has high quality.

If quality is evaluated in particular, what is regarded as true must be clear. In the spatial data that centers on the conventional paper map, the latest condition on the spot was regarded as true and compared with

spatial data to evaluate quality. However, attention should be paid to the fact that there are many conditions

other than the above condition in spatial data.

2.3 Metadata

Metadata is said to be data of data. This is because metadata is data that represents various attributes of

data itself. The examples of metadata include the scope covered by the data, creation date, and creation organization. Metadata also contains the history (this is called genealogical information) of the dataset,

which is effective for maintaining and managing the dataset.

Arranging such metadata as this and using the Internet to register it in the clearinghouse enables the

person who intends to use data to easily confirm the location of the desired data. The person may also be

able to obtain the data. The geographic information standard requires that metadata is created for the

convenience of users.

2.4 Encoding Actual spatial data must be coded based on a certain rule in the format in which the computer can

understand it. The format is close to the format that has conventionally been called format. When

particularly spatial data is interchanged, it must be coded using the common coding method. This is called

encoding rule in data interchange. Actually, the internal data format (the item that specifies this is called

internal schema) of each GIS is converted to the common data format using conversion software. The side

that receives this data must convert it to the internal database specific to the system. This common coding

rule for data format is the encoding rule. Figure 2-3 shows the concept of these items. Many coding methods for data are available, but they must also have meaning in the future and enable

representation of various data structures without being effective for only a specific GIS. The geographic

information standard adopts XML (extensible Markup Language) as the coding method for data. While

HTML (HyperText Markup Language) is the internationally standardized coding method for various

documents, XML is said to be the coding method suitable for coding while giving meaning to the document

structure. The validity of XML for such data including diagrams as spatial data is also recognized and

specified by ISO/TC211. This XML is the coding method that can represent the meaning of data and

enables the user to be free to add the meaning. In other words, XML has the portion that defines the contents of XML, and the creator can be free to define this portion. This is why XLM is called extensible.

XML puts data between codes called tags to clarify the meaning of the data.


Applicationschema

I

Defines

Data flow

System A

Internaldatabase

Internalschema

A

Filesystem

Transferservices

Encodingservice

R

MAIiA

d

System B

Internaldatabase

Internalschema

B

Filesystem

Transferservices

Encodingservice

R-1

MIBiB

d

Data transfer

System boundary System boundary Figure 2-3

2.5 Spatial Reference System

Relating a feature to the position on the earth using the GIS requires that the position of the feature be

specified with such indexes as longitude and latitude. This mechanism is called spatial reference system.

In order to specify the position, it may be directly pointed out with such indexes as longitude and latitude or indirectly pointed out with an address and a lot number. The former method is called spatial reference

(direct reference), and the latter method is called spatial reference using a geographic identifier (indirect

reference). Figure 2-4 shows the concept of these methods.

For direct reference, the definition of the coordinate system must be clear. For indirect reference, the

gazetteer in which such a substitute for coordinates as an address (called geographic identifier) and

coordinates are related is required.


Figure 2-4

2.6 Feature Catalogue

A feature catalogue defines various features contained in spatial data. ISO/TC211 reviews only the

feature catalogue method and only exemplifies the catalogue of actual feature. ISO/TC211 considers that

the feature catalogue classifies and arranges the features (called instances) that exist in the real world by their functions. If such a feature catalogue is created, it ensures common definition and recognition of feature

and provides a material useful for spatial data interchange.

Feature

Spatial reference using coordinates Spatial reference using geographic

Position


Chapter 3 Contents of Product specification description

The product specification description must contain an overview of spatial data, the contents of data to be

acquired, encoding specification, quality, and metadata. For this reason, the product specification

description has the following chapters. However, application schema, encoding specification, quality, and

metadata should be summarized as annexed materials because there are many situations where they are used

individually.

Product specification description

Product specification description (main part)

１． Abstract of Product

２． Contents of Capturing Dataset

３． Data evaluation Method

４． Metadata ５． Encoding Specification

６． Delivered goods

７． Other Items Annexed material Application Schema Feature Requirement Definition

Feature Application Schema Description (UML Class Diagram)

Encoding Specification Feature Encoding Specification (*and Sample)

DTD or XML Schema

Quality Quality Requirement and Confirmation Method Definition Metadata Metadata (JMP)

(*Gazetteer)

*: Option

(Figure 3-1 Example of basic organization of product specification description)

The product specification description contains an overview of target spatial data and the names of annexed materials. All of these contents are also recorded in metadata and utilized to interchange and reuse

data.

The product specification description also corresponds to the conventional special remark specification.

The annexed material is positioned as technical material.

This chapter aims at understanding knowledge for reading the product specification description according

to the basic organization of the product specification description.

1. Overview of Spatial Data This section gives an overview of spatial data specified in the product specification.

1.1 Purpose of Spatial Data

The concrete purpose and method of using this dataset are described to help understand the product


specification. Generally, these contents are transcribed to metadata to provide information that represents

the quality of data in qualitative and general ways.

Example of description

Spatial data to be created based on this specification aims at enabling identification of the road conditions and the

positions of disaster prevention facilities, dangerous facilities, storage facilities, evacuation facilities, medical facilities,

amusement facilities and search of evacuation route to draft the plan for area disaster prevention on the assumption that

an earthquake occurs or to control traffic when a disaster occurs.

1.2 Geographic Scope of Data

The geographic scope of spatial data is described. The methods for representing the geographic scope

include the method for specifying it from such known ranges as metropolis and districts and municipalities,

the method for specifying the range surrounded by specific roads or rivers, and the method for specifying it

according to the coordinate values. Generally, these contents are transcribed in metadata to provide information that represents the geographic

range of data.


Whole XX city area

From Long. XX"YY' E to Long. XX"ZZ' E, and from lat. ××" ・・' N to lat. ××" ××' N

Around XX station (see Attached Diagram.)

1.3 Temporal Scope

The temporal scope of data to be arranged is described.

If the source material from which data is to be created is specified, the temporal scope indicated by the

source material becomes the temporal scope of data. If a dataset contains multiple features and data is to be

created from different source materials, the temporal scope of data must be clearly specified for each feature.

Generally, these contents are transcribed in metadata to provide information that represents the temporal

scope of data.


As of March 31, 1998

1.4 References (Spatial Reference System, Coordinate System, Temporal Reference, Weights and

Measures)

Spatial reference system includes spatial reference system based on coordinates and spatial reference

system based on a geographic identifier. To use the spatial reference system based on coordinates to represent data, describe the geodetic datum to

comply, planar coordinate system, and vertical datum.

・Geodetic system to comply ……World geodetic system, Tokyo Datum, etc.


・Planar coordinate system……Plane rectangular coordinate system, geographic coordinate system,

UTM coordinate system, etc.

・Vertical datum…………Height from mean sea level, height from ellipsoid to comply, etc.

These contents provide the data creation criteria and are also transcribed to metadata.

In Japan, "Tokyo Datum -, Plane Rectangular Coordinate System XX, elevation from mean sea level" is

often used.

In the planar rectangular coordinate system, the number of the coordinate system to apply based on the geographic scope of data is described. In the UTM coordinate system, the zone number is described.

In spatial reference system based on geographic identifier, the type of identifier and the structure of the

gazetteer that indicates the correspondence between the identifier and positional coordinates are described

together. The gazetteer is created from the dataset as required.

As the unit of coordinate value, m is generally used. Significant figures are also described as XX

decimals.

Note (E)

The plane rectangular coordinate system specified in this section is the plane rectangular coordinate system

having 19 data decided in accordance with the Survey Act in Japan.

1.5 Temporal Reference System

In Japan, the year based on Christian or Japanese era and the month and day based on the Gregorian

calendar are used for date. The geographic information standard clearly specifies the correspondence

between calendar dates and the Julian day number. The following lists the examples of the dates. Japanese era

Date of year based on Japanese era

Date based on Christian era

Julian day number

Meiji M05.12.02 M06.01.01 M45.07.30

1872-12-31 1873-01-01 1912-07-30

2405159 2405160 2419614

Taisho T01.07.31 T15.12.25

1912-07-31 1926-12-25

2419615 2424875

Showa S01.12.26 S64.01.07

1926-12-26 1989-01-07

2424876 2447534

Heisei H01.01.08 1989-01-08 2447535 For time, the Japanese local time (JST: Japanese Standard Time) is generally described. The CUT

(Coordinated Universal Time) on which data interchange is based may also be described.

Like expressions "the xxxx's" and "xxxx Era" used in geology and archeology, for example, temporal

reference is also available to specify only sequence without using the date and time. When this temporal reference system is used, the name and sequence are described.

2. Contents of Data to be Acquired

In this section, the contents (type, structure, and required quality) of data are described. However, these

contents are generally created as attached materials because they are often described in large quantities and

are easier to use in the separate volume format when the product specification description is used.


As basic know ledges about the geographic information standard to understand the described contents,

feature definition, data structure and application schema, and quality is explained. The examples of entries

in the feature requirement definition created with all of these items included, feature application schema, and

required quality are explained.

2.1 Feature Definition

A dataset contains many features. Various definitions can exist depending on how this feature is used. If a feature called "road" is to be defined, for example, the person who assumes the feature to be used like a

navigation system will define it based on only road centerline. The person who actually manages the road

will define the feature based on the road range and define that the range includes "roadway," "sidewalk," and

"median strip." In this way, a feature cannot be strictly defined without clarifying the purpose of using the

dataset.


2.1.1 Overview of feature definition

The geographic information standard defines the feature configuration as shown in Figure 3-2.

Figure 3-2

The feature relationship is described as shown in Figure 3-3.

Figure 3-3

In this way, an attempt to define a feature is nothing but defining the feature attributes (spatial attribute, temporal attribute, and thematic attribute) and feature relationship that make up the feature.

2.1.2 Feature definition technique

(1) Clarification of purpose (function)

The feature definition technique is clarifying the function of the feature first. The function means how

the feature is used. The feature cannot be defined without clarifying this purpose.

(2) Classification and arrangement of feature Features spatially exist individually. Classifying and arranging these individual features by types and

characteristics helps understand them and makes it easy to use them.

(3) Definition of attribute

The attribute of the feature is then defined. Feature attributes include spatial attribute, temporal attribute,

and thematic attribute, and each of them is defined. Information related to quality as to what a feature is

based on, (e.g., it is based on material A or positional accuracy must be xx) is also important.

(4) Feature relationship

Finally, how a feature is related to other features must also be defined.

2.1.2.1 Feature definition

An overview of feature is described and defined using a natural language in the feature requirement definition.

Feature

Feature attribute

Spatial attribute Temporal attribute Thematic attribute

(Topological relationship) (Feature relationship)

Feature

Feature

Feature

Feature

Feature

Feature

Feature

Feature


For example, define a building. A building is a person-accessible construction with a roof. If the building is

defined in this way, building at large seems to have been able to be defined. However, this does not clarify

whether the eaves or wall periphery of the building is used to actually draw the shape of the building. A person

may not intend to recognize a small construction such as a bus stop as a building. Even if access to the eaves of a

small entrance hall is omitted, no problem may occur in terms of the purpose. In this way, because it is difficult

to define even substantial object strictly, it is more difficult to define unsubstantial road centerline or intersection

strictly. However, an effort should be made to define the feature as strictly as possible.

What must be noted is general definition and clarification of what is called acquisition criteria as to where

to measure and how scale or less on which measurement is omitted for actual measurement on the spot.

These acquisition criteria can also be said to be spatial attribute definition. For example, in the schematic

explanation in "Survey Regulations of Ministry of Land, Infrastructure and Transport," an ordinary building

is "two-story or less architecture and three-story or more architecture built of wood." In the explanation of

digital mapping acquisition criteria in the above survey regulations, it is "acquiring the periphery (start point

and end point coordinates match)." The former is equivalent to feature definition, and the latter is equivalent to spatial attribute definition.

In any case, the quality described later, particularly the target entity that enables inspection of

completeness must be defined as clearly as possible.

Note (E)

The Feature Requirement Definition Table is the feature catalogue used to design the application

schema and is independently specified in the JSGI. For details, see Section 2.4.2.

2.1.2.2 Spatial attribute

Spatial attribute refers to the geometric element and topological element of the feature. The geometric

element refers to point, line, and plane. For example, a line or plane is used to represent a building.

Naturally, one feature may also have multiple spatial attributes of different types.

A feature without spatial attribute can exist. There are several types of lines, and the most common line

is GM_Curve. For details, refer to the geographic information standard.

The topological element is the geometric element relationship. If a site is represented, for example, the boundary lines that are multiple geometric elements are associated with it.

2.1.2.3 Temporal attribute

The thematic attribute can also have the temporal attribute to represent the attribute related to time.

However, the temporal attribute is effective in extracting a feature by its existing period or explicitly

specifying temporal association between features.

(1) Temporal reference system package The elements that represent the temporal coordinate system such as the method of establishing the

calendars, e.g., Christian era and Japanese calendars and the data types for describing the temporal position

on the temporal coordinate system are defined.


(2) Temporal object package

The elements for representing the temporal position (e.g., month X day Y, year Z) and period (start date

and time and end date and time) and the elements for representing the topological temporal relationship

(relationship as to whether it is relatively new or old instead of absolute time) are defined.

2.1.2.4 Thematic attribute and thematic diagram The thematic attribute has conventionally been called attribute. For example, the lot number, owner,

classification, and land use type (lot of the land having only one address) are the thematic attributes.

A thematic attribute is named for identification. The data type, domain, and multiplicity of thematic

attribute are also described.

The data type includes integer, character string, real number, and date. The character string includes

alphanumeric character string and kanji character string.

The domain is the range of the values that an attribute value can take. If the attribute indicates a numeric value, "0 or more to less than 3,000" become the domain. If the attribute indicates a road manager,

enumerative values such as "nation," "metropolis and districts," and "municipalities" become the domain.

Multiplicity is the definition as to how many thematic attribute values are in a feature. If this value is 1,

a thematic attribute value always exists. If this value is 0,1, zero or one thematic attribute value exists and

can be omitted.

The thematic diagram is an attached diagram unlike the primary spatial attribute. The most common

thematic diagram is an annotation. When an administrative district is defined as a feature and its name is

defined as the thematic attribute, the name is indicated on a map. In this case, the character is called thematic diagram. Something like a leader is also the thematic diagram.

2.1.2.5 Feature relationship

In feature definition, defining the feature relationship is very important work.

The feature relationship is stipulated as a sentence in the feature requirement definition stage. However,

this must be represented in the UML notation in the class diagram creation stage.

This section explains the examples of defining the feature relationship using the feature in spatial data as an example.

(1) Building and site: Example indicating intensive relationship

If the site and building are defined as features independently and other feature (e.g., factory) is used to

manage the site and the building on the site together, three classes of "site," "building," and "factory" are

created.

At this time, there is the relationship that "the site and building make up part of the factory" among the class

of "factory" and classes of "site" and "building." This relationship is described in the following class diagram:


(2) Building classification: Example indicating general relationship

A building can be classified due to its property in various ways. However, the building has basic

attribute that is common to different classifications. As the technique often used for this classification,

classification code is used for judgment. However, assume that a building is classified by classes.

(3) Park and gate to park: Example indicating any relationship on GIS application to be used

On the assumption that "park" and "gate to park" are defined as classes, there are no positional relationship between the park and the gate to park, and the system using this data must associate two features,

the connected line, association name, role name, and multiplicity are exemplified.

[Connection type]

Because this relationship is defined arbitrarily, it is simply connected by a line.

[Relationship name]

If super class of "building" has common

attributes of building such as name and

construction date, only specific attributes

may be defined for each of sub-classes of

"reinforced" and "wooden." (in a

sub-class, the attribute of name can be used

without definition.)

Building

Name

Construction date

Wooden

Reinforced

Reinforcing rod

diameter

Because the site remains and the building

exists until pulled down even if the factory

(company) goes bankrupt, the "site" and

"building" remain even if the "factory"

disappears. This intensive relationship is

indicated by an outline diamond-shaped

symbol. If a parent object diappears and

child objects cannot exist, the black

diamond-shaped symbol is used.

Building

Site

Factory

Access Gate

１ 0..*

Gate to park

Park


Any name can be assigned to the relationship so that the relationship between two classes can be easily

known. In this example, the relationship name is "access," but can also be omitted if the relationship is

clear.

[Role name]

Any name can also be assigned to the role so that the role of each class in the relationship can be easily

known. The role name of the gate to park is "gate." Because the role of the park can be explicitly

understood even if the role name of the park is not indicated, the role name is not defined. In this way, the role name can also be omitted if not particularly required.

[Multiplicity]

Regarding the quantitative relationship as to how many gates one park has, a park without fence or wall like

a field may have no gate. From this, it can be considered that "there is zero or more park for one park."

This quantitative relationship between objects is represented by "multiplicity" and described near each class

of connection indicating the relationship.

2.2 Data Structure and Application Schema

The application schema defines the structure of features included in a dataset. The geographic

information standard specifies that this application schema is indicated using the UML class diagram.

However, this section describes the significance of data structure definition during data distribution and the

contents of application schema and gives an overview of the UML class diagram.

2.2.1 Data structure

(1) Importance of data structure The data structure is very important not only for spatial data but only in using the system, and greatly affects the

function specification, performance, maintainability, and expandability of the system. In the conventional spatial

data structure, for example, the layer (portrayal layer) is one of data structures, and how this structure is decided

determines the function specification such as superposition. During data interchange with other system, the data

structures are also associated in units of layers. When GIS software is developed and maintained and data

interchange is done, the data structure must be concretely understood.

In this way, it is important to understand the contents of data structure well to use and interchange data. For

this reason, the data structure must be coded in the format in which human can understand it. However, because

the spatial data structure is complex and no general coding method is available, specific representation is often

used for each GIS engine, and hinders the understanding of the spatial data structure.

(2) Data structure for data interchange

As previously described, the concept and terms of spatial data structure vary depending on the GIS engines that

handle spatial data, and they are based on the proprietary technologies of the GIS vendors. It is necessary to be

familiar with the GIS engines to understand the structure of spatial data handled by the GIS engines. However, it

is impossible for every one to understand many GIS engines in details. Establishment of the universal technique

of coding the spatial data structure is indispensable to wide-range distribution and effective use of spatial data

items of various GIS engines. Conventionally, the interchange formats of CAD in common use and GIS and the


DM format have been used for data interchange. However, they simply convey geometric information and

attribute information of feature alone, and cannot represent the feature relationship that is primarily useful

information of spatial data.

To solve these problems, the geographic information standard adopts the standard technique of coding the data

structure, which is called application schema

2.2.2 Application schema (1) Application schema

The geographic information standard defines the standard for coding the spatial data structure, which is

called "application schema." As previously described, the application schema defines the spatial data

structure. It mainly defines the property (attribute) of a feature and the feature relationship.

The geographic information standard centers on a feature in the spatial data structure to classify the

attribute of the feature (feature attribute) into the following three attributes:

(1)"Spatial feature" indicating spatial (geometric and topological) characteristics (2)"Temporal attribute" indicating the temporal characteristics

(3)"Thematic attribute" indicating the property of the feature other than spatial and temporal

characteristics

Creating the application schema for spatial data can mean that these attributes and the relationship

between features are defined for each feature to create the document that enables any one to understand the

data structure.

The application schema is defined based on the concept of data structure called object orientation

described later, and the UML class diagram is adopted as the standard method for coding the data structure. UML is a graphical language used to represent the object-oriented data structure simply, and enables flexible

representation of various attribute information items of spatial data, the classification of the feature that takes

the place of the conventional layer, and the relationship between features.

(2) Object orientation

In the system technology field, compared with the conventional system development technique, the

concept called object orientation has recently been expected to improve the productivity, expandability, and reusability of the system rapidly.

Spatial data in object orientation is handled by combining graphical data and character information data

intrinsic to a feature，and this combination is called "object." Object-oriented spatial data is a group of

feature data whose structure is represented by assuming each of features appearing on a map to be an object,

defining information that each feature should have and the relationship between features as objects, and

associating the objects with one another.

In conventional spatial data, a feature is assumed to consist of two separate data items, graphical data and

character information data，which are managed separately and associated by only program algorithm. In any concept, spatial data through the system is visible to the spatial data user in the same way.

However, because the structure of conventional spatial data must be opened to the outside to output the data

from the system to the outside for interchange, the structure in which information is linked in the system


must be coded simply. Because object-oriented spatial data has no special association between graphical

information and attribute information but simply exists as an object (feature), it does not require explanation

based on a specific system technology. In addition, because the standard coding method called UML is

established, the data structure of object-oriented spatial data is universally indicated relatively easier than that

of conventional spatial data.


(3) Class

In the object-oriented concept, the devised object is classified based on its property to define what object it

is. The defined object is called "class" and defining is called "classifying."

When the object-oriented data structure is designed, it is important to "classify" various features and

clarify what relationship there is between "classes." The designed class structure can be represented using the diagram called UML "class diagram."

A class refers to the definition itself, and individual features that actually exist are called instances for the

class. If there is a "bridge" class that defines a bridge, for example, Seto Bridge and Naruto Bridge are

instances for the bridge class.

(4) Contents of application schema

The application schema is the documented definitions of the feature attribute and feature relationship in

the dataset. Because the UML class diagram alone cannot code many portions of the application schema, the material in table format is used as part of application schema to indicate the feature requirement. This

manual explains this material as feature requirement definition.

As a concrete example of the contents of application schema, assume that the feature attributes of two

Attribute information

Processing that enables the user

to handle data as a feature easily

through association by program

Coordinate information

x, y, z,…


Owner: XX

Feature

Data structure View from system user

Graphic information data 【C

onventional spatial data

】

Graphic information


Object

Coordinate information:

x,y,z…

Attribute information: Owner:

XX

Feature

Data is originally defined

as a feature.

View from system user Data structure

【Object-oriented spatial data

】

Figure 3-4 Data structure and system mechanism


features, "park" and "gate to park" and the relationship between two features are defined. Then, assume

that these two features are then defined and the UML class diagram is indicated. Because this manual

explains the UML class diagram and feature requirement definition separately, this section only gives an

overview of application schema.

[Feature attribute of park]

・Spatial attribute: Plane (the park site is defined by a plane.)

・Temporal attribute: Park establishment date ・Thematic attribute: Name, manager (classification, e.g., nation, prefecture, city, town, village, and

private), and area

[Feature attribute of gate to park]

・Spatial attribute: Point (the position of the gate to park is defined by a point.)

・Temporal attribute: Traffic time (period of time the gate is open: X:XX to X:XX)

・Thematic attribute: Park name and whether vehicle (traffic) is allowed

[Relationship between park and gate to park] ・One or more gates to park or no gate to park may exist for one park (the park like a field may have no

explicit gate).

・There is an association that the gate to park and the park can recognize between

them instead of geometric association related to coordinate position.

[Class diagram]

2.2.3 UML class diagram

(1) UML

UML is developed as the coding method for modeling a large-scale system based on object orientation in

the software field. UML is called Unified Modeling Language, and is a graphical language for using a

visual and simple diagram to code the entire system. UML is authorized by OMG (Object Management

Group), an international software industry group, and is a defacto standard for documenting the

object-oriented system.

(2) Coding method of UML class diagram

UML is positioned as Language by its name, but diagrams are used to represent the major portion. In

Access Gate

１ 0..*

Gate to park

Spatial attribute: Point

Temporal attribute:

Traffic time

Thematic attribute:

Name

Whether vehicle is allowed

Park

Spatial attribute: Plane

Temporal attribute:

Establishment date

Thematic attribute:

Name

Manager

Area

Belonging


UML, several types of diagrams called "class diagram," "use case diagram," and "sequence diagram" are

defined. UML uses these diagrams to represent the system and data structure. However, all types of

diagrams need not necessarily be used, and a required diagram is generally created according to the target to

be coded.

The class diagram above all is the form of a diagram into which various targets on the system are defined

as objects, they are classified, and the relationship between classes is put.

The appendix to this manual explains the coding method of the class diagram but does not describe all

specifications of UML class diagram. Because the geographic information standard defines the coding

rules, refer to the explanation of "Rules for Application Schema," "Spatial Schema," and "Temporal

Schema" in the geographic information standard and other related documents such as commercially

available UML manuals for details.

Figure 3-5 Example of general UML class diagram

2.3 Quality

Defining the contents and precision that data should have clearly is very important both in creating data

and for the user to handle the data. In the product specification description, these items must be described

in accordance with the geogrpahic information standard. This section describes the concept of quality and

the methods for defining and confirming quality.

2.3.1 Quality (concept and necessity) 2.3.1.1 Concept

The geographic information standard assumes that when the person who plans to create data defines the

quality required of the product according to the purpose of using it, the data creator can create data that

GM_Curve

１＋line

TP_Edge

１＋edge

National road

+dmId : DMID

+name : CharacterString

GM_LineString

１..* ＋segment

GM_Curve

１..* ＋line

GM_LineString

１..* ＋segment

+dmId : DMID

chushinsen

+chushinsenIchi:Integer

≪Feature≫ ≪Feature≫

Boundary between


assures the quality required by the product specification description regardless of the creation technique.

For this reason, the data planner must clearly describe the ideal data quality contents (required quality) the

data planner considers or data quality definition and acceptance inspection method as required in the product

specification description for the data creator.

In this way, by describing quality in the product specification description for comparison with created data,

it is possible to identify "how much the quality of actually created data differs from the ideal required quality

the data planner considers (= quality to suit the purpose)"(definition of quality in the geographic information standard).

However, note that high quality does not mean that the standard deviation for error is small or the error

percentage is low as an absolute value as usual but means that the created data satisfies the required quality

defined in the product specification description.

2.3.1.2 Necessity

When the conventional paper map is created, the standard based on a reduced scale is generally used as a criterion that indicates the quality of data at large. All data items can be defined as the required quality

defined by the work regulation by presenting only reduced scale. However, because the required quality is

uniform for all features regardless of the purpose, some features have quality that exceeds the level required

by the purpose to cause a bad effect that data exceeds the specification.

To solve this problem, the geographic information standard enables a data planner to define the required

quality for each data item and configure data flexibly and economically to suit the purpose.

If quality is explicitly specified in the product specification description, it is easier for the data user to

identify the data contents by referring to the product specification description and metadata in addition to when data is created, resulting in promoting reuse of spatial data.

2.3.2 Quality contents

Spatial data contains simply digital graphical information about features as well as attribute data and

image data based on character information from the level of purpose of using spatial data. Therefore, the

data planner must define not only the positional precision of features that has been regarded as important

before but also the quality that corresponds to data in these various formats. At this time, true data is source data to be created (if a paper map is source data, it is true data). In quality requirement, source data must be

true data.

The geographic information standard enables quality to be described by two major systems (quantitative

quality information and qualitative quality information) to ensure that such data quality be defined.

Quantitative quality information is classified into five items "completeness," "logic consistency,"

"positional accuracy," "temporal accuracy," and "thematic accuracy," which are called data quality elements.

Each data quality element has a smaller classification of quality items called data quality subelement in

which quality items at large are systematized. This section gives an overview of data quality elements. For details, refer to the geographic information standard.

Qualitative quality information is classified into three items "purpose," "usage," and "lineage," which are

called data quality overview elements. When spatial data is created, the purpose (ground for creating data),


usage (application using dataset), and lineage (processes through which the dataset is created) of data are

described to indicate quality.


図Ｘ－Ｘデータ品質の体系図

2.3.2.1 Completeness

Completeness describes whether a feature, feature attribute, and feature relationship exist, or the permissible level of the amount of actual data for data items that are specified to acquire in the product

specification description.

Completeness has two data quality subelements "omission" and "commission."

(1) Commission

This element indicates whether unnecessary data is acquired. Basically, the ratio of permissible excess

data in total number of relevant data items in feature units is indicated by percentage.

[Example] Compared with the school ledger, the excess ratio of the number of features that are recognized as school

is 0%.

(2) Omission

This element indicates whether the data item that must be acquired is included in the dataset. Basically,

the ratio of permissible omitted data in total number of relevant data items in feature units is indicated by

percentage.

[Example]

Compared with the school ledger, the omission ratio of the number of features that are recognized as school is 0%.

Data quality overview element

Data quality element

Completeness

Logic consistency

Positional accuracy

Temporal accuracy

Thematic accuracy

Purpose

Genealogy

Usage

Data quality subelement

Data quality subelement

Subdivide data quality elements

・・・

Quantitative quality

Non-quantiative quality


2.3.2.2 Logic consistency

Logic consistency indicates the permissible level of logical inconsistency related to the data structure,

attribute to be added, and relationship between data items.

Logic consistency has four data quality subelements, "conceptual consistency," domain consistency,"

"format consistency," and "topological consistency."

（１） Conceptual consistency

This element indicates whether data is created according to the conceptual schema rule. The ratio of permissible error in total number of relevant data items is indicated by percentage.

[Example]

The spatial schema of the acquired feature is the specified spatial object.

（２） Domain consistency

This element indicates whether data is within a fixed range. The ratio of permission error in total

number of relevant data items is indicated by percentage.

[Example] Only municipal codes that exist in the municipalities to which municipal codes must be assigned are

included.

(3) Format consistency

This element indicates whether the data that is defined to be coded in a format has a correct format. The

ratio of permissible error in the total number of relevant data items is indicated by a percentage of target

record. However, format consistency is not specified for each data item but is specified in the entire

dataset.

[Example] The error in the tag name of data created as XML document is 0%.

(4) Topological consistency

This element indicates whether topological information about data is valid according to the definition of

topological relationship defined in the application schema. The ratio of permissible error in total number of

relevant data items is indicated by percentage. However, topological consistency is not specified for each

data item but is specified in the entire dataset.

[Example] Municipal and administrative data that must be plane data is always closed.

2.3.2.3 Positional accuracy

Positional accuracy describes the accuracy of the position for each data item. That is, different positional

accuracy can be defined according to the purpose of using each data item. If sea level data is required, the

accuracy of planar position and the positional accuracy of sea level are described.

Positional accuracy consists of three data quality subelements, "absolute or external accuracy," "relative or

internal accuracy," and "grid data positional accuracy." (1) Absolute or external accuracy

This element indicates the level at which the coordinate values of the acquired feature approach the

feature coordinates that are or are assumed to be true. The uneven level at which they approach the


coordinates is indicated by permissible average square error and standard deviation.

[Example]

Compared with the coordinate values obtained by performing inspection and observation that are 5% of

on-the-spot measurement (technique that enables acquisition of absolute positional precision of 10 cm or

less), the acquired road intersection coordinates have average square error of within ±0.5 m.

(2) Relative or internal accuracy

This element indicates the level at which the acquired positional precision between features approaches the relative position assumed to be true. The uneven level at which it approaches the relative position is

indicated by permissible average square error and standard deviation.

[Example]

Compared with the distance obtained by performing inspection and observation that are 5% of on-the-spot

measurement (technique that enables acquisition of relative positional precision of 10 cm or less), the

acquired distance between buildings has average square error of within ±0.5 m.

(3) Grid data positional accuracy This element indicates the level at which the pixel coordinate values of raster data such as aerial photo

approach the coordinates assumed to be true. The uneven level at which they approach the coordinates is

indicated by permissible average square error and standard deviation.

[Example]

Compared with the coordinate values obtained by observation using the GPS, the coordinate values of the

feature in one pixel of raster data have average square error of within ±0.5 m.

2.3.2.4 Temporal accuracy Temporal accuracy indicates the accuracy of temporary feature attribute and temporal feature relationship,

and consists of three data quality subelements, "temporal measurement accuracy," "temporal consistency,"

and "temporal validity."

(1) Temporal measurement accuracy

This element indicates the level at which the time recorded as data approach the time checked by the more

precise timer (error in time measurement). The uneven level of the accuracy is indicated by permissible

average square error and standard deviation.

(2) Temporal consistency

This element indicates whether the sequence of the time recorded as data is accurate. The ratio of

permissible error in total number of relevant data items is indicated by percentage.

[Example]

The acquired building data whose temporal attributes are "start date" and "completion date" contains no

data whose completion date is older than start date.

(3) Temporal validity This element indicates whether data within the temporal range defined by the product specification

description is stored correctly. The ratio of permissible error in total number of relevant data items is

indicated by percentage.


[Example]

The dataset specified to contain the building existing as of January 1, 2000 contains no data about the

buidling built after January 1, 2000.

2.3.2.5 Thematic accuracy

Thematic accuracy indicates whether the classification and attribute value of thematic attribute added to

data are accurate, and consists of three data quality subelements, "classification accuracy," "qualitative attribute accuracy," and "quantitative attribute accuracy."

(1) Classification accuracy

This element indicates whether data (feature and feature attribute) is classified correctly. The ratio of

permissible error in total number of relevant data items is indicated by percentage.

[Example]

The acquired data is all specified class data items.

(2) Qualitative attribute accuracy This element indicates the accuracy of qualitative attribute of attribute data. The ratio of permissible

error in total number of relevant data items is indicated by percentage.

[Example]

"Road name" in road data is the name that exists in the material used to acquire data.

(3) Quantitative attribute accuracy

This element indicates the level at which the attribute value of the quantitative attribute of attribute data

approaches the data value that is or is assumed to be true. The uneven level of the accuracy is indicated by

permissible average square error and standard deviation. [Example]

Compared with actual extension in road ledger, "road extension" of road data has difference of within

2%.

2.4 Requirement Definition Table

2.4.1 Example of requirement definition

All data items (features) to be acquired are described as the requirement definition. In the requirement definition, the required items are described for each feature.


(Figure 3-5 Example of requirement definition)

2.4.2 Contents of requirement definition

This section explains the contents of the requirement definition.

Entry Contents

Feature name Actual phenomenon name in abstract concept Definition of feature Describe the definition for specifying actual phenomenon. Acquisition criterion Clearly describes acquisition position and orientation and

scope of each feature. Example of acquisition Illustrate an example of acquiring each feature according to

acquisition criterion. Name Name of attribute that specifies spatial characteristics of the

feature Definition Describe the defintion for specifying the spatial characteristics

of the feature. Type Describe the date type (e.g., point, line, or plane) for specifying

spatial characteristics of the feature. Quality evaluation material

Describe information used to evaluate spatial characteristic quality of the feature.

Spatial attribute

Positional accuracy Describe acquisition positional precision of feature.

Zahyokei Coordinate system for reference point Integer 1～19 2 digits 1..2 Reference point result table

Name Definition Quantity

Name Definition Type Unit Range Format Quantity Quality evaluation material Kijyunten_Shubetsu Reference point type Integer 1～7 1 digit 1 Reference point result table

Kijyunten_Code Reference point code Half-size character string

1 Reference point result table

Kijyunten_Name Reference point name Full-size character string

1 Reference point result table

Related attribute

Type Thematic attribute Temporal accuracy

Creator：

Feature name

Definition o f feature

Acquisition criterion

Name Definition Quantity Kijyunten_Ichi Position of reference point 1

Temporal attribute

Type Quality evaluation material Positional accuracy Point Reference point result table

The feature refers to the point that provides reference (e.g., coordinates, height, orientation, and distance at horizontal position) for information according to each purpose.

The central position of the building is acquired.

Spatial attribute

Reference point Example of acquisition

Acquisition position

X X coordinate for reference point Real number ｍ 2 decimal

places 0..1 Reference point result table

Y Y coordinate for reference point Real number ｍ 2 decimal


H Sea level at reference point Real number ｍ 2 decimal


Temporal attribute

Not required if type is level point.

Not required if type is level point.

Name

Name

Regional range of feature Usage ・

Other

Related thematic attribute name Portrayal code

Feature related

Definition Related feature name


Quantity Describe the quantity (multiplicity) of spatial data for one instance of the feature.

Name Name of attribute that specifies temporal characteristics of the feature

Definition Describe the definition for specifying temporal characteristics of the feature.

Type Describe the data type for specifying temporal characteristics of the feature.

Quality evaluation material

Describe information used to evaluate temporal characteristic quality of the feature.

Positional accuracy Describe acquisition temporal precision of the feature.

Temporal attribute

Quantity Describe the quantity (multiplicity) of temporal data for one instance of the feature.

Name Name of attribute that specifies thematic characteristics of the feature

Definition Describe the definition for specifying thematic characteristics of the feature.

Type Describe the data type for specifying thematic characteristics of the feature.

Unit Describe the unit of data that indicates thematic characteristics of the feature.

Range Describe the range of data that indicates thematic characteristics of the feature.

Format Describe information about the limit on number of characters and ○ decimal places.

Quantity Describe the quantity (multiplicity) of thematic data for one instance of the feature.

Quality evaluation material

Describe information used to evaluate thematic characteristic quality of the feature.

Thematic attribute

Related attribute Describe other attribute related to the relevant thematic attribute.

Name Name of diagram that must be drawn in thematic characteristics of the feature

Related thematic attribute name

Describe the name of thematic attribute related to the relevant thematic diagram.

Thematic diagram

Portrayal code Describe code for referencing the portrayal method for the relevant thematic diagram.

Name Describe the name for specifying other feature related to the relevant feature.

Definition Describe the definition for specifying other feature related to the relevant feature in natural language.

Feature related

Related feature name Describe the name of other feature related to the relevant feature.

Regional range of feature Describe the regional range in which the feature applies. Usage Describe the purpose of using the feature and the method for

using it. Other Describe note and remarks.


2.5 Example of Describing Application Schema for Feature

The UML class diagram is described for each requirement definition.

GM_Curve

１＋line

TP_Edge

１＋edge

Natinal road

+dmId : DMID

+name : CharacterString

GM_LineString

１..* ＋segment

GM_Curve

１..* ＋line

GM_LineString

１..* ＋segment

+dmId : DMID

chushinsen

+chushinsenIchi:Integer

≪Feature≫ ≪Feature≫

Boundary of sidewalk and road chushinsen centerline


2.6 Required Quality

2.6.1 Describing quality requirement definition

Describe the required quality for each feature in the following quality requirement definition:

Creation date:

Creator:

Feature

Quality requirement Remarks

Excess

Omission

Range consistency

Format consistency

Topological consistency

Absolute or externalaccuracy

Relative or internalaccuracy

Grid data positionalaccuracy

Temporal measurementaccuracy

Temporal consistency

Temporal validity

Qualitative attributeaccuracy

Quantitative attributeaccuracy

Supplementation

Userdefinition

Quality Requirement and Confirmation Method Definition

Temporalaccuracy

Quality element

Thematicaccuracy

Classification accuracy

Completeness

Positionalaccuracy

Logicconsistency


2.6.2 Analyzing required quality

Analyze the quality requirement definition to create the quality requirement classification table covering

all required quality as the example listed in the following table. At this time, logic consistency is not

analyzed because the required quality is automatically inspected at the same level for total number.

(Example of quality requirement classification table) Classification by quality requirement

Quality element

S Ａ B C D

Completeness

No omission and excess are permitted.

It is desirable that there is no omission and excess.

Omission and excess are slightly permitted.

Omission and excess are permitted to some extent.

Evaluation is not needed.

Positional accuracy

High positional accuracy is required.

Specified level of positional accuracy is required.

Positional accuracy is less strict than the specified value.

Positional accuracy is much less strict than the specified value.


Temporal accuracy

No error is permitted. It is desirable that there is no error.

Slight error is permitted.

Error is permitted to some extent.


Thematic accuracy

No error is permitted. It is desirable that there is no error.

Slight error is permitted.

Error is permitted to some extent.


Classification by quality requirement

S: No error is permitted (an error loses the value as product.)

A: It is desirable that there is no error.

B: Slight error is permitted.

C: Error is permitted to some extent.

D: The quality element need not be evaluated.

Decide the required quality for each feature according to the quality requirement classification table. If

there are many features to be handled, work can be smoothly done by typifying features by quality as listed

in the following table that summarizes the features whose required quality is the same:

(Example of typifying features)

Completeness Positional accuracy

Temporal accuracy

Thematic accuracy

Feature name

S

S

B

A

Reference point, …

A

B

B

B

Road, railroad, rivers, bridge, …

B

C

B

B

Building,…

C

C

C

C

Vegetation, small object,…

・・・


Decide the quality standard for the typified feature groups. As shown in the example of the following

quality standard table, weight the quality standard for each quality element. Regarding positional accuracy,

decide the specified values of positional accuracy as a separate table and describe them in the product

specification description.

(Example of quality standard table) Quality element Quality subelement S A B C

Excess Quality standard: 0%

Quality standard: Less than 5%


Quality standard: Less than 20% Completeness

Omission Quality standard: 0%




Conceptual consistency Quality standard: 0%

Quality standard: 0%



Domain consistency Quality standard: 0%




Format consistency Quality standard: 0%




Logic consistency

Topological consistency Quality standard: 0%




Absolute or external accuracy

Twice or more higher than specified value: 0%

Twice or more higher than the specified value: Less than 5%



Relative or internal accuracy





Positional accuracy

Grid data positional accuracy





Temporal measurement accuracy

Quality standard 0%




Temporal consistency Quality standard 0%




Temporal accuracy

Temporal validity Quality standard 0%




Classification accuracy Quality standard 0%




Qualitative attribute accuracy

Quality standard 0%



Quality standard: Less than 20% Thematic accuracy

Quantitative attribute accuracy





Inspection at level D shall not be done for any items.


(Specified value of positional accuracy) S A B C D

0.25m 0.25m 0.70m 1.75m Not specified.

2.6.3 Notes on defining quality

One of points to consider when quality requirement definition is created is setting of quality standard

value (range). However, because the nature of a standard value itself depends on the data items and the

criteria for setting the standard value depend on the purposes, it is difficult to provide a uniform rule for setting a standard value.

For example, when a standard value to be set is as high as error rate of 0%, data precision gets better, but

creation cost also proportionately becomes bigger. The contents set in the standard value may greatly affect

dataset creation. Therefore, the cost-effectiveness for using dataset also becomes one of judgment criteria

for setting the standard value.

As judgment criteria for setting the standard value, the purpose of using data, for example, is classified

according to whether the data affects personal life and property, has a great economic damage if an error occurs, is handled by administrative business, or is the one for which a geometrical shape is regarded

important. Providing the base of judgment criteria for each of the classifications is also one of the methods

for setting the standard value.

In any case, when the standard value is set to define quality, it is necessary to conduct full examination

while also referring to the criteria in the conventional work regulations

As reference for deciding the standard value of positional accuracy, the following lists the positional

accuracy of the maps on a reduced scale in the conventional public survey regulation of the Ministry of Land, Infrastructure and Transport.

*Reference (Calculated from public survey regulation of Ministry of Land,

Infrastructure and Transport)

Reduced scale Absolute precision Planar position

Absolute precision Sea level

1:250 ±0.125ｍ ±0.33ｍ 1:500 ±0.25ｍ ±0.33ｍ 1:1000 ±0.70ｍ ±0.33ｍ 1:2500 ±1.75ｍ ±0.67ｍ 1:5000 ±3.50ｍ ±1.67ｍ 1:10000 ±7.00ｍ ±3.33ｍ 1:25000 ±17.5ｍ ±5.00ｍ 1:50000 ±35.0ｍ ±10.0ｍ 1:200000 ±140ｍ ±40.0ｍ

(Note) Numeric values mean the standard deviation.


3. Quality Evaluation Method

If data is created according to the product specification description, it is necessary to evaluate whether the

delivered dataset satisfies the required quality. What summarizes this evaluation is the quality evaluation

method. When data creation is requested, describing the quality evaluation method in the product

specification description to present it to the creator beforehand may lead to improvement in quality.

3.1 Quality Comparison Targets (Material and Spot)

3.1.1 Quality comparison material After a dataset is created, the data creator must evaluate whether the required quality is secured. The

dataset and the material that is or is regarded true are compared to confirm whether the required quality is

satisfied. Therefore, the quality comparison material must be concretely described clearly in the product

specification description as the material that should be used for quality evaluation and is true or is regarded

true.

3.1.2 Notes on quality comparison material 3.1.2.1 Material for data creation

The data creator can use any materials to create a dataset if the required quality is secured. The quality

comparison material need not always be used as the material for creating a dataset.

3.1.2.2 Temporal scope

Because the product specification description specifies the temporal scope of data, the temporal scope of

quality comparison material must also be clarified in the material. Particularly if the quality comparison

material depends on each data item, note consistency between the quality comparison materials when they are created. Care must be used particularly when the existing material is used with on-the-spot

investigation as quality comparison material because there is a time-lag between the point in time the

existing material was created and the point in time on-the-spot investigation is done (current point in time).

3.1.2.3 Data not described in quality comparison material

The created dataset may contain data that does not exist on the quality comparison material. It is also

necessary to consider how quality is confirmed for such data.

3.2 Concrete Evaluation Method

Quality requirement definition requires that only quality value be specified instead of the method for

confirming the quality value. However, when the required quality is defined, it is necessary to concretely

specify how acceptance evaluation is conducted.

The quality evaluation method is divided into direct evaluation method and indirect evaluation method.

The direct evaluation method compares the quality confirmation material and the created dataset to evaluate

quality. The indirect evaluation method uses information related to genealogical data to estimate or suppose quality. The direct evaluation method includes the external direct evaluation method and internal direct

evaluation method. The external direct evaluation method compares a dataset and quality confirmation

material and on-the-spot survey result for inspection. The internal direct evaluation method evaluates quality


through inspection that can be performed with only data in the created dataset, and refers to topological

structure check and format check. Figure 3-6 shows the classification of quality evaluation method.

Figure 3-6 Classification of quality evaluation method

3.2.1 Direct evaluation method

Direct evaluation refers to direct evaluation for the finally created dataset itself, and is classified into external

evaluation and internal evaluation.

3.2.1.1 External evaluation method and internal evaluation method

The external evaluation technique compares the created dataset and data on universe of discourse for

evaluation. For example, the positional accuracy is compared with the on-the-spot remeasurement results or the source material.

Example 1 Whether the building owner name is correct as compared with the ledger

Example 2 Whether the road name in the dataset is the same as the name in road ledger

The internal evaluation technique uses only created dataset itself for evaluation. Because the digitized

dataset itself is evaluated, automatic inspection for the entire dataset is used.

Example 3 Whether the district line created as a district is closed (topological consistency)

3.2.1.2 Means of implementing direct evaluation method

Both external evaluation method and internal evaluation method have two considerations. They are

full inspection or sampling inspection and automatic inspection or manual inspection, visual inspection or

Quality

Direct

Indirect

External

Internal

Full

Sampling

Visual

Automatic

Visual

inspection

Full Automatic


inspection survey that determines the inspection target.

3.2.1.3 Full inspection

Full inspection literally inspects the total number of individual features in a dataset. Actually, because

the inspection targets often exist in large quantities, the inspection cost often becomes big. In addition to

automatic information using computer, it may be better to perform sampling inspection for data at less

important level. Full inspection requires that all items in the population specified in the scope of data quality be tested.

Table 3-1 lists the full inspection procedure to be used.

Table 3-1 Full inspection procedure

Step Description

Define an item An item is the minimum unit to be inspected. A feature, feature attribute,

or feature relationship can become an item.

Inspect an item in scope of data

quality

All items in the scope of data quality are inspected.

Remarks: Full inspection is most suitable for a small population and the test that can be automatically

completed. This method should be used to evaluate quality of data item at high important level.

3.2.1.4 Sampling inspection

The sampling inspection technique does not cover the total number of targets, but arbitrarily extracts

X％ of the total number for inspection. Practically, the evaluation criteria that determine how much

percent of targets is sampled or how much percent of the sampled data passes the inspection to accept the entire data are difficult.

Sampling inspection requires that the items sufficient for obtaining the data quality evaluation results in

a population be tested. Table 3-2 lists the sampling inspection procedure to be used.

Table 3-2 Sample inspection procedure

Step Description

Define sampling inspection method The sampling inspection method includes simple random sampling method

and stratified sampling method (e.g., sampling by feature type, feature

relationship or area), multistage sampling method, and intentional sampling

method.

Define an item An item is a minimum unit to be inspected. A feature, feature attribute, or

feature relationship can become an item.

Divide scope of data quality

(population) into lots

A lot is a set of items in the scope of data quality to be sampled and

inspected. Each lot must consist of items created under as the same


condition as and at the same time as possible.

Divide a lot into sampling units A sampling unit is the district of the lot to be inspected.

Define sampling rate or sampling

size

The sampling rate provides information as to how much items were sampled

from each lot on the average for inspection.

Select sampling unit The sampling units are selected for the required number to satisfy the

sampling rate and sampling size of items.

Inspect items in a sampling unit All items in a sampling unit are inspected.

3.2.1.5 Visual inspection

Visual inspection outputs data on display or paper to visually inspect it. This method is suitable for

inspection for a relative positional shift.

3.2.1.6 Inspection survey

The inspection survey method uses the method satisfying the required quality to recreate data and compares it with the data to be inspected for inspection. For positional accuracy, quality can be evaluated

by only inspection survey. This method is suitable for inspection for positional accuracy, but should be

used as required because the inspection cost becomes big.

3.2.2 Indirect evaluation method

The indirect evaluation technique does not evaluate the finally created dataset itself but evaluates quality

according to the technique used to create the dataset and the performance of equipment used. This technique has been used for the products that conform to the convenntional creation specification. The

creation specification can also be said to ensure quality of dataset based on this indirect evaluation.

This technique should be used only if the direct evaluation method cannot be used. Usage information

records the use of a dataset. This information is effective in searching the dataset created or used for a

specific application. Genealogical information records information about creation and history of a dataset.

For example, information about materials used to create a dataset and information about the creation process

used are included in the genealogical information. This information is effective in judging whether a

dataset is suitable for the given utilization. One of the examples is genealogical metadata related to the numerical feature model file created from image acquired under the fixed condition through stereo

interrelation. The evaluator empirically knows that the average square error at the horizontal position of

this kind of image is 10 m, or knows from genealogical metadata on digitized feature map drawn on a scale

of 1:25,000 that it complies with the requirement of basic map of the city planner. Purpose information

describes the purpose for which a dataset was created. The purpose may support a specific requirement or

may be widely used much. This information is effective in identifying the possible value of a dataset.

3.2.3 Concrete example of describing quality evaluation method

The required quality of data to be created may depend on each of features. The quality evaluation

method is decided for each of typified features and described in each quality standard. The method for


handling defective products is also described.

3.2.3.1 Typified quality evaluation method

Typifying the quality evaluation method is defining basic evaluation methods according to the quality

evaluation method. The quality evaluation method specified in this section refers to the following

techniques:

1 Full inspection and automatic inspection 2 Full inspection and manual inspection

3 Sampling inspection and manual inspection

(1) Full inspection and automatic inspection

The full inspection and automatic inspection method uses the computer to inspect the total number. This

method is used to evaluate logic consistency. This method may also be able to be used to evaluate

completeness and qualitative attribute accuracy in thematic accuracy. However, this method is likely to be used to evaluate logic consistency for only numeric large-scale feature data.

Because the computer is used to perform inspection, this method applies to the total number. This

inspection requires that the alogrithm of the program used be reported using metadata.

(2) Full inspection and manual inspection

This inspection method inspects the total number visually or through on-the-spot survey. Spatial data

inspection is often manually performed.

Full inspection inspects all target items. Therefore, all items are extracted to verify whether they are acceptable. If the number of defective products is within the standard value as compared with the total

number of items, it is acceptable.

If the positional accuracy of a linear feature is evaluated, what the total number refers to is a problem.

However, it will refer to the positional coordinates of a refraction point in numeric large-scale feature data.

(3) Sampling inspection and manual inspection

Main inspection of spatial data is sampling inspection and manual inspection. As this technqiue, the following procedure is used:


(1)

Form a lot

(2) Divide into inspection units

(3) Extract inspection units

(4) Inspect inspection units

(5) Judge acceptance or rejection

Sampling inspection procedure

1 Form a lot

・ Specify the range of the same stratification as a lot.

2 Divide into inspection units

・ Divide the lot into inspection units in rectangular area.

・ The size of an inspection unit is 200 m east and west and 150 m north and south in numeric

large-scale feature data. The area of one inspection unit may be adjusted to become about

1/1,000 of the lot area, but adjustment of the unit to a very small area is prohibited.

・ An inspection unit may be divided into such recognized areas as large section and subsection. 3 Extract inspection units

・ Extract inspection units corresponding to the JISZ9002 Sampling Table from the lot.

・ To sample inspection units, use the simple random sampling or stratified sampling method.

The stratified sampling method extracts a feature from the feature group that is the target

quality evaluation unit and further performs random sampling.

・ If inspection units in the lot are less than the number of inspection units required in the

JISZ9002 Sampling Table, full inspection shall be performed. 4 Inspect inspection units

・ Perform inspection in quality evaluation units that consist of typified feature groups.

・ Inspect the total number of extracted inspection units.

・ Compare inspection units with the quality standard of the typified feature groups to divide

them into acceptable product and defective product.

5 Judge acceptance or rejection

Repeat these steps for

each quality

evaluation unit for

which quality is

evaluated


・ If defective products are equal to or less than the number of defective products in the

JISZ9002 Sampling Table, it is acceptable. If they exceed the number of defective products,

it is rejected.

・ Repeat steps (4) and (5) for all quality evaluation units that consist of typified feature groups.

3.2.3.2 Quality evaluation list

The following quality evaluation list is set and described for the feature group (quality evaluation unit) for

which the quality standard is set:

(Example of quality evaluation list) Quality element Quality subelement S A B C

Excess Manual and full Manual and sampling

Manual and sampling

Manual and sampling Completeness

Omission Manual and full Manual and sampling

Manual and sampling

Manual and sampling

Conceptual consistency Automatic and full

Automatic and full

Automat ic and full

Automatic and full

Domain consistency Automatic and full

Automatic and full

Automatic and full

Automatic and full

Format consistency Automatic and full

Automatic and full

Automatic and full

Automatic and full

Logic consistency


Automatic and full

Automatic and full

Automatic and full

Automatic and full


Manual and full Manual and sampling

Manual and sampling

Manual and sampling



Manual and sampling

Manual and sampling Positional accuracy



Manual and sampling

Manual and sampling



Manual and sampling

Manual and sampling

Temporal consistency Manual and full Manual and sampling

Manual and sampling

Manual and sampling

Temporal accuracy

Temporal validity Manual and full Manual and sampling

Manual and sampling

Manual and sampling

Classification accuracy Manual and full Manual and sampling

Manual and sampling

Manual and sampling

Qualitative attribute accuracy


Manual and sampling

Manual and sampling Thematic accuracy

Quantitative attribute accuracy


Manual and sampling

Manual and sampling

Inspection at level D shall not be performed for any items.

3.2.3.3 Evaluating quality evaluation results

The value of a spatial dataset as a product remains small after some spatial data is only delivered.

herefore, quality of the spatial dataset as a product is assumed to be acceptable only if the results of quality

evaluation for all quality evaluation units are acceptable.


For final evaluation of quality evaluation results, "100% acceptance/rejection" for evaluating combined

data quality is used. This "100% acceptance/rejection" method determines the product to be acceptable

only when all quality evaluation units are acceptable. This will report only quality evaluation results.

If an acceptable product is determined to be defective as a result of inspection, correction of the defective

part can be requested and the product can be accepted after redelivery on a contract. However, for the

quality evaluation results for metadata, the results before redelivery will be described.


4. Metadata

In the product specification description, the request to create metadata is described.

Note(E)

Metadata is coded based on JMP instead of ISO19115.

4.1 Use of Metadata As described in "II. Geographic Informatin," metadata is created in roder to open spatial data reference

information to the public through the clearinghouse (information center). The geographic standard

specifies that metadata is coded in XML so that spatial data reference information can be accessed from

any personal computer connected to the Internet.

The standard format of metadata is classified into two types of conformity levels according to its use.

(1)Conformity level 1

Metadata at this level aims at identification of an overview of spatial data and search of spatial data, and consists of minimum catalogue information required for using it at the clearinghouse and quality

description information (data quality information and genealogical information). These information

items can incorporate reference information, person-in-charge information (including address

information), online information source, and scope information as intermediate repetition items (see

Figure 4-2).

(2)Conformity level 2

Metadata at this level consists of the items required for complete description of spatial data. The

items required for identification, evaluation, extraction, and adoption of data and management of spatial data information are available (see Figure 4-3).

In the product specification description, "conformity level" and "contents of items that are clear when

an order is given" must be clearly described.

4.2 Metadata Structure and Items

Metadata has the structure shown in Figure 4-1, and consists of one major item (catalogue information. Data quality information or genealogical information may also be included)) at

conformity level 1 and eight sections (identification information, data quality information, genealogical

information, spatial data representation information, reference system information, feature catalogue

information, distribution information, and metadata information) at conformity level 2.

A section consists of the groups of intermediate entity that have the contents interrelated to one

another and metadata elements. An intermediate item consists of the groups of other intermediate

items that have the contents interrelated to one another and metadata elements.

Intermediate items include the item that is repetitively referenced from the major item and other intermediate items, and this is called intermediate repetition item.


Metadata structure

Figure 4-1

Major item

IntermediaIntermedia Intermediat

～

Metadata element

Metadata element

Metadata element


0. Catalogue information

2.Data quality information

3.Genealogical information

9.Reference information

10.Person-in-charge information

11.Address information

12.Range information

Figure 4-2 Major item and intermediate repetition item of

13.Online information

Metadata major item Intermediate repetition item

1.Identification information

2.Data quality information

3.Genealogical information

9.Reference information

10.Person-in-charge information

11.Address information

12.Range information

Figure 4-3 Major item and intermediate repetition item of

4.Spatial data representation

5.Reference system information

6.Feature catalogue

7.Distribution information

8.Metadata reference

13.Online information source

Metadat major item Intermediate repetition item


Table 4-4 Major items and main intermediate items of metadata

Major item Description Main intermediate item 0. Catalogue information Major item for describing catalogue information

used to support the clearinghouse activity. This item may also contain data quality information or genealogical information that is a major item.

Activity identification information, person-in-charge information, coordinate-based range of earth surface, geographic identify -based range of earth surface, classification, keyword information

1. Identification information Major item for describing information used to identify data uniquely. This item indicates the title and creator of a dataset and other basic information.

Identification reference, activity identification information, image identification information, status, dataset range, classification, major contact destination, reference image, dataset relativity, dataset constraint

2. Data quality information Major item for describing data quality. This item indicates general evaluation information about data quality. The maximum number of times the intermediate item "data quality" is described is N.

Scale on which data quality was applied, explanation of scale on which data quality was applied, spatial scope of data quality, data quality evaluation (report type, qualitative evaluation, quantitative evaluation)

3. Genealogical information Major item for describing usage of data, information source, and creation method. This item explains the information source used to configure a dataset, work done, and the person in charge of work.

Usage, genealogy

4. Spatial data representation information

Major item for explaining the mechanism that represents spatial data. This item indicates information about the data model (e.g., vector, raster, and image) used to represent the spatial attribute in a dataset.

Spatial vector representation information, spatial raster representation information, spatial image representation information

5. Reference system information

Major item for explaining the time and spatial reference system with which a dataset complies. This item indicates the reference system with which positional data and temporal data to be used in a dataset comply and the means of coding them

Temporal reference system information, spatial reference system information

6. Feature catalogue information

Major item for explaining the type, attribute, function, and interrelation of features included in a dataset. This item indicates catalogue information about features used for the dataset subject to metadata and their attribute. If multiple catalogue information items are available, they can be described more than once in the intermediate items.

External feature catalogue, internal feature catalogue (feature type, feature function, feature attribute, feature interrelation)

7. Distribution information Major item for describing the person who issues and distributes data and information incidental to distribution. This item describes information about distributin of a dataset.

Distributor information, distribution data format information

8. Metadata reference information

Major item for describing information about validity of metadata and person in charge of metadata. This item describes information about metadata created for a dataset.

Metadata file identifier, metadata file parent identifier, dataset application schema name, metadata date information, contact destination for metadata, metadata standard information, metadata extension information, incidental metadata information


Table X Intermediate repetition items Intermediate repetition item Description

9. Reference information

Intermediate item that specifies the reference format. When this item is inserted, the title of referenced dataset must always be described. "Person-in-charge" information must always be repetitively used to describe information about the creator and issuer as intermediate items. In addition, the issue date and time must always be described as reference date. Be sure that what the version of data can be identified if it is not the first version, the series name can be identified if data is a series product, the volume and issue can be identified if data is separated to multiple volumes and issues. Detailed information such as "alias," "dataset identifier," and "other reference" may be added.

10. Person-in-charge information

Intermediate item that describes information about the person (group or individul) in charge. When this item is inserted, at least the personal name, organization name or title of the person in charge must be used. The address of the person in charge must also be described by inserting "address information. When this item isinserted into "reference information," a variable (1 = originator/2 = issuer/3 = manager) is set in "person-in-charge title code."

11. Address information

Intermediate item that indicates an address When this item is inserted, "nation" must always be described. In addition to this, "zip code," "metropolis and districts," "municipalities," "location," "phone number," "TDD/TTY phone number," "fax number," "e-mail address," "information time," and "contact guide" can be freely described. "Online information" can be described according to the intermediate repetition item "oneline information source."

12. Scope information Intermediate item that indicates spatial scope (plane and height) and temporal scope of data. This major item is described for the number of items that different values in "boundary polygon," "vertical scope," and "spatial scope."

13. Online information source

Information source information used to acuqire data. URL is mandatory.

Appendix B, "Metadata Elements" specify the contents of major item, intermediate, and metadata

element. The metadata element has seven attributes that indicate its characteristics.

Table 4-5 Metadata element attributes Element attribute Description

Name Label assigned to a metadata element Tag Short name assigned to a metadata element. If metadata is coded in SGML or XML, this specified

short name must be used. Definition Explanation of a metadata element Requirement Descriptor that specifies the coding condition for a metadata element.

・Mandatory (M): A metadata element must always be coded.

・Conditional (C): If a dataset has the specified characteristics, its metadata element should be coded.

・Optional (O): A metadata element may or may not be coded. A wide range of optional metadata elements are available on the assumption that metadata is completely documented.

Maximum coding count Descriptor that specifies the maximum number of instances that may be coded. If the instance is coded only once, this descriptor is 1. When the instance is permitted to be repeated, this descriptor is N.

Data type Descriptor that specifies the type of clear value that represents a metadata element. The examples are text, integer, real number, and date.

Domain Descriptor that specifies the range (domain) of the values that each metadata element can take. For "free coding," it indicates that there is no constraint on the occurrence of a field.


4.3 Example of Description

This section gives an exmaple of describing the product specification description. For details about the

meaning and format of the items to be described, see Appendix B, "Reference Materials" and separate

manuals.

When metadata is coded in XML, the tool "JMP Editor" can be downloaded from the following site and

used to code metadata in the EXEL format and output it in the XML format (see Appendix B, "Reference Manuals").

http://www.gsi-mc.go.jp/REPORT/GIS-ISO/KMGIS/download.html#edittool

[Example of description] Assume that metadata at conformity level 1 is created in the XML format based on the Japan Metadata

Profile (JMP). Describe the specified contents for the following items:

<カタログ情報> <題名>製品仕様書作成マニュアル記入例 <シリーズ名>製品仕様書作成マニュアル

<活動識別情報> <活動型>研究 <活動名称>地理情報標準の運用に関する研究

<参照日>20010330 - <責任者情報>

<責任者個人名> <責任者組織名>（財）日本測量調査技術協会</party_org> <責任者職務コード>003

<責任者住所> <国>Jｐ <郵便番号> 102-0083 <都道府県>東京都 <市区町村>千代田区 <所在地> 麹町 3-2 錦屋ビル 5Ｆ

<データ集合の範囲> <地理的識別子による地表の範囲> <地表の範囲名称>○○県△△市全域

<時間的範囲の日時>200103 <データ集合言語コード>Ja <データ集合の文字符号集号>ShiftJIS <要約>災害時の対応および防災計画を立案する時に必要な道路・各種施設の地理情報 <目的>地震等の災害を想定した地域防災計画の立案や災害時の交通規制を行うために，道路状況や防災施設，

危険施設，貯蔵施設，避難施設，医療施設，娯楽施設等の位置の把握および避難誘導道路の検索などを可

能とすること（中略）

<系譜情報の有無>001 <データ品質情報の有無>001 <空間表現型コード>002 <空間参照系型>002 <フォーマット名>地理情報標準1.1版における記録仕様 <適合性レベルのコード>001 <メタデータの言語コード>Ja <メタデータの文字符号セット>ShiftJIS

Note(E)


The above table is not translated because it has Japanese own specifications.

5. Encoding Specification

5.1 Encoding

As widely known, it is very important to enable interchange of spatial data between different GISs for effective

use of spatial data. The geographic information standard defines the basic concept of data interchange between

different systems. Encoding specified in this section refers to the process that converts the contents and structure

of spatial data to the conformable format based on the specified rule (encoding rule) in order to interchange and

save spatial data. The encoding rule is required for recording spatial data on electronic media based on the

application schema that defines the spatial data structure. However, the geographic information standard does

not define the digital media, communication format, and transfer protocol.

For this reason, "encoding" requires that the application schema exists and is coded in UML (Unified

Modelling Language) as specified in "Rule for Application Schema" in the geographic information standard. In UML, however, the encoding rule for data interchange is not specified. In "encoding," the encoding rule

based on XML (Extensible Markup Language) is defined.

Establishing the "encoding" standard promotes sharing of spatial data between different GISs and enables joint

possession and wider use of spatial data, elimination of information loss during data interchange, and maintenance

and assurance of quality.

5.2 Data Interchange

If a dataset is sent from a system to other system, both systems must agree on the following three items:

Output format and conversion method are decided

Corres- pondence

符号化

Spatial data provider

Spatial data specification

Spatial data to be converted

Feature catalogue

Appli- cation

schema

Metadata

Spatial data to be

provided

Data conversion to

standard specification

Design feature based on spatial data structure

Data conversion to

original specification

Spatial data to be used

En- coding

Spatial data user

Claringhouse

Spatial data specification

Appli- cation schema

Input format and conversion method are decided

En- coding

Corres- pondence


・ The common application schema is defined.

・ An agreement on the encoding rule to apply is reached.

・ An agreement on the transfer protocol to be used is reached.

The application schema defines the contents and structure of spatial data, and is specified in "Rule for

Application Schema" in the geographic information standard. The encoding rule defines the conversion rule for

creating the system-independent data structure, and is specified for "encoding." The transfer protocol defines the

procedue for physically transferring a dataset between systems, and is not specified in the geogrpahic information

standard.

The following is an overview of typical data interchange between different systems:

Applicationschema

I

Defines

Data flow

System A

Internaldatabase

Internalschema

A

Filesystem

Transferservices

Encodingservice

R

MAIiA

d

System B

Internaldatabase

Internalschema

B

Filesystem

Transferservices

Encodingservice

R-1

MIBiB

d

Data transfer

System boundary System boundary

Figure Overview of data interchange

Both systems A and B hold data in the internal database accoding to the system-specific internal schemas.

The internal schemas generally vary with both systems. Transfer of a dataset from the internal database of

system A to the internal database of system B requires the following steps to be taken:

１）Convert internal data in system A to the data structure according to the common application schema.

This implements suitable software MAI to convert individual data from the concept of internal schema to the concept defined in the application schema and leads data i with the "application schema-specific

data structure."

２）Execute encoding service with the encoding rule R for creating the system-independent data structure


applied. As a result, dataset d encoded in XML is created. The encoding service is the software

component that implements the encoding rule to provide the interfaces to the encoding function and

decoding function.

３）Call the transfer service to send the encoded dataset d to system B. The transfer service performs

actual data transfer according to the transfer protocol on which systems A and B agreed.

４）Take the above steps in the reverse order to create the internal dataset in system B.

In "encoding," the encoding rule for the encoding service is specified and the entire data interchange

process is not specified. Therefore, only the encoding procedure in the above step 2) and the decoding

procedure in the reverse order are standardized.

5.3 Encoding Rule

The encoding rule defines the method that converts (encodes) individual data items (instances) according

to the application schema. This encoding rule includes (1) schema conversion rule and (2) instance conversion rule.

(1) Schema conversion rule

This rule is the method that creates DTD in XML according to the structure of spatial data

coded by application schema. Currently, conversion to the XML schema is also under

consideration.

Common definition part XML declaration

Basic DTD reference Standard DTD reference Shared data definition

Class definition part Define

Element

Attribute

Class itself for each class

Class definition part

：

<? xml version="1.0" encoding=" Shift_JIS "?> <!ENTITY % standard.declarations SYSTEM " NSGI_Standard

. dtd ">

%standard.declarations; <!ENTITY % spatial.declarations SYSTEM " NSGI_Spatial

. dtd "> %spatial.declarations; <! ENTITY % DMIDElements 'EMPTY' > <!ENTITY % DMIDAttributes '

code CDATA #REQUIRED no CDATA #REQUIRED' >

<!ELEMENT dmId %DMIDElements ; > <!ATTLIST dmId %DMIDAttributes ; >

<!ELEMENT point %GM_PointElements ; > <!ATTLIST point %IM_ObjectAttributes ;

%GM_PointAttributes ; >

<! ENTITY % EkiElements '( dmId , point )' > <!ENTITY % EkiAttributes '

name CDATA #REQUIRED' > <!ELEMENT Eki %EkiElements ; > <!ATTLIST Eki %IM_ObjectAttributes ;

%EkiAttributes ; >

<! ENTITY % Object '( Eki | )'> <!ENTITY % standard_post .declarations SYSTEM

" NSGI_Standard_post . dtd ">

%standard_post .declarations;

Common definition part Object list definition Basic DTD reference


(2) Instance conversion rule

The instances are converted to create an XML document according to the schema conversion

rule.

1 Head of XML document

Place XML declaration and document type declaration at the beginning of a dataset.

<?xml version="1.0" encoding="Shift_JIS" ?> <!DOCTYPE GI SYSTEM "creation-manual.dtd">

2 Metadata information Place one exchangeMetadata element at the beginning of GI element. Set information about

dataset name, creation date, and encoding rule being used in this element.

XML document sample <exchangeMetadata>

<datasetCitation> <title>Creation experiment data sample</title> <date>YYYY-MM-DD</date>

</datasetCitation> <encoding>

<citation> <title>Geographic information standard XML encoding rule</title> <date>2000-07-05</date> </citation> <toolName /> <toolVersion />

</encoding> </exchangeMetadata>

Set a dataset name in the title element and the dataset creation date in date element on the left. The left indicates information about the encoding rule. Set this value. Blank information about the tool.

3 Dataset information

The exchangeMetadata element is followed by the dataset element where the contents of spatial data are created. Place one dataset Information element at the beginning of the

H e a d o f X M L d o c u m e n t

< G I >

< /GI>

< e x c h a n g e M e t a d a t a >

< / e x c h a n g e M e t a d a t a > M e t a d a t a i n f o r m a t i o n

< d a t a s e t >

< /dataset>

<datase t In fo rmat i on>

< / d a t a s e t I n f o r m a t i o n > D a t a s e t i n f o r m a t i o n

F e a t u r e i n f o r m a t i o n

dataset element. Define information about spatial reference system definition used for a

dataset and the scope covered by the dataset in this element.

(4) XML XML (Extensive Markup Language) is an Internet-supporting languge of the SGML (Standard Generalized

Markup Language developed by the ISO (International Organization for Standardization). W3C (World

Wide Web Consortium), the organization that standardizes the Web technology, is standardizing this language.

In 1998, XML standard Ver.10 was recommended. SGML is the language developed by ISO to ensure

document compatibility in various software environments, but was not suitable for distribution because its

specification is complex.

The field in which XML is used is roughly classified into "document," "Web page," and "data."

For "document," the common format called XML facilitates interchange of structured document information even between different organizations.

For "Web page," XML enables data processing capability to be improved by dividing the Web page into

data and design, while HTML currently used to describe a Web page is representation-oriented.

However, XML has recently attracted particularly considerable attention because needs for XML increases

in the "data" field. The typical examples are EC (Electronic Commerce) and EAI (Enterprise Application

Integration) fields. The interchange of information between different organizations and systems has

conventionally required that a specific standard and mechanism be decided. An effort has been made to use XML to standardize the interchange of information.

For this reason, in "Revision of Basic Administrative Computerization Action Program" (Cabinet decision

in December 20, 1997), the Government has decided that the international standard (SGML) is adopted as the

XML document  <datasetInformation id="F0_0001">

<SC_CRS id="CRS01"> <RS_Identifier>JPL06</RS_Identifier> <remarks>Planar rectangular coordinate system VI</remarks>

</SC_CRS> <datasetExtent>

<Shape id="F0S0001"> <CRS idref="CRS01" /> <patch> <controlPoint>xxx1 yyy1</controlPoint> <controlPoint>xxx2 yyy2</controlPoint> <controlPoint>xxx3 yyy3</controlPoint> <controlPoint>xxx4 yyy4</controlPoint> <controlPoint>xxx1 yyy1</controlPoint> <interpolation>planar</interpolation> </patch> </Shape>

</datasetExtent> </datasetInformation>

id is unique in a dataset. Set "F0_0001" in dataset information，and "F0S001" in Shape in the dataset information. For spatial reference system (CRS), define "CRS01" here to enable that features can be specified. Shape sets the spatial scope covered by a dataset. Coordinate values are based on the planar rectanglular coordinate system. The unit is meter. Describe the values with 2 decimals precision. Specify "planar" for interpolation.

document structure format of electronic official document in order to develop the infrastructure for promoting

administrative computerization, but is currently attempting to ensure compatibility with XML.

In line with the above background, the geographic information standard that promotes sharing of spatial data

adopts XML as the description language of a dataset that becomes an entity of data interchange.

5.4 Example of Coding DTD

This section explains DTD as an example of encoding specification described in the product specification

description.

 (1) <!ELEMENT Shubetu %Integer>

<!ELEMENT Hyoko %Real >

<!ELEMENT Name %CharacterString >

<!ELEMENT SokuryouDate %Date >

<!ELEMENT ShutokuDate %Date >

(2) <!ENTITY % KijuntenElement ‘(point,period?,

Shubetu,

Hyoko, Name,

SokuryouDate,

ShutokuDate)’ >

(3) <!ENTITY % KijuntenAttribute ‘ ‘ >

(4) <!ELEMENT Kijunten %KijuntenElement ; >

(5) <!ATTLIST Kijunten %IM_ObjectAttributes; %KijuntenAttribute; >

(1) Defining thematic attribute

The ELEMENT statements declare all thematic attribute items. This declaration makes the

definition in KijuntenElement in (2) valid.

(2) Defining substitute character string for reference point element The parameter ENTITY statement defines a reference point element. In the above example, the

substitute character string '(Point, Period, Shubetu, Hyoko,..., ShutokuData)' is defined for

KijntenElement (class name + Element). Assume that this substitute character string gives role

name (role) and thematic attribute in the UML class diagram. However, the geometric element

package based on the spatial schema, GM_point or GM_Curve or the temporal attribute

TM_Period can also be specified here, but the geographic information standard always uses a role

name. Therefore, a role name must be defined as followings. Basically, a role name will be defined in Spatial.dtd.

Multiplicity of elements is also specified here. For example, the question mark "?" following

the Period role name indicates that the element appears 0 time or once according to the XML

syntax. In other words, it indicates that the Period element may not exist. The thematic attribute

is defined in (1) and referenced in (2).

Role name


<!ELEMENT Point %GM_PointElements; >

<!ELEMENT Period %TM_PeriodElements;>

(*) GM_PointElements is defined in spatial.dtd.

<!ENTITY % GM_PointElements ‘(CRS,Position)’ >

CRS and Position are also defined.

(*) TM_PeriodElements is defined in Temporary.dtd. <!ENTITY % TM_PeriodElements ‘( )’ >

(*) Multiplicity

+ One or more repetition (1..+) * 0 or more repetition (0..*) ? 0 time or only once（0..1）

(3) Defning substitute character string for reference point attribute

The parameter ENTITY statement uses a substitute character string to give a dummy for

KijuntenAttribute.

(4) Defining reference point

The ELEMENT statement defines the reference point element. In this example, the reference

point class (Kijunten) represents that the reference point elements form a hierarchical structure with elements Point, Period, Shubetu, ... by referencing KijuntenElements.

(5) Defining reference point attribute

The thematic attribute of a reference point is defined. Attribute definition uses the ATTLIST

statement to specify KijuntenAttribute specified in (2) as well as always inherits

IM_ObjectAttributes (instance model attribute: Defined in standard DTD). This adds reference

point attributes (ID and UUID).

6. Contents (Product)

The configuration of the product created according to this product specification description is described

(equivalent to the product in the order specification).

[Example of description]

Reference point

Point Period Shubetu ShutokuDate


Dataset 1 set Quality confirmation report and confirmation material 1 set Metadata 1 set

7. Other Items

7.1 Definition of Term The explanation of the term used in this product specification description is described.

[Example of description] Conform to Geographic Information Standard Edition 1.1 unless otherwise specified in this product specification description.

7.2 Materials

The source material used to create geographic information and the material to be used as the quality

confirmation standard are described. If geographic information to be crated satisfies the required quality,

any materials may be used. Although the source material to be used need not always be specified, the

material that provides the quality confirmation standard must always be specified. If there is a difference between materials to be used as the quality confirmation standard or between the

materials and the materials on the spot, which material is adopted must be described (see the explanation of

quality evaluation method).

[Example of description] The following lists the materials (source materials) to be referenced to create geographic information

and materials (confirmation materials) used to confirm quality. For materials used to confirm quality for each feature, refer to the quality confirmation definition. The materials used to create geographic information are described in genealogical information in metadata regardless of whether they are listed in the following table.

When there is a difference between confirmation materails or between the materials and the materials on the spot, the latest materials created shall be adopted.

Material classification Name Format Creation (revision) date

Source material Basic forest map Map (1/10000) 1995.9.30 Source material and confirmation material Basic city planning map Map (1/2500) 1991.3.31

Source material and confirmation material

Road ledger index map Map (1/10000）・DXF 2000.3.31

Confirmation material Whole residential map Map (1/10000） 1998.3.30

Confirmation material Town household population table Excel 2000.10.1

Confirmation material Park ledger Book 1999.10.1

7.3 Restriction

The restrictions and notes on using the created geographic information are described.


This product is based on the basic city planning map, and such data as distance and area cannot be used to register land.

7.4 Reference Standards and Special Terms The standards and rules that should be followed in addition to this specification to create geographic

information are described if they should be clearly specified.

If the special terms and abbreviations used by the product specification description creator are used in the

specification, the definition of the terms are clearly described as required so that the geographic information

creator can understand the meaning accurately.


Chapter 4 Flow of Creating a Product specification description

1. Purpose of This Chapter

This chapter describes the flow (procedure) of creating a product specification description based on the

description of geographic information standard in Chapter 2 and of a product specification description in Chapter 3. This chapter is aimed at allowing you to create a product specification description by simply

following the flow described in it.

If you are not sure about the meaning of a term or what to do, see a corresponding section of Chapter 3

indicated in each step of the flow. This feature is provided so that you can use the description of a product

specification description in Chapter 3 like a dictionary.

2. Chapters and Items to Be Described in a Product specification description

Basically, things to be described in a product specification description are the same as those described in

Chapter 3. The following shows a basic pattern to give you an idea on what to be described in a product

specification description and what chapters to be contained in it.

<Basic Pattern of Chapters>

Chapter 0 Identification of Product specification description Description

Chapter1 Abstract of Product １．１ Purpose

１．２ Extent (Spatial, Temporal)

１．３ Reference System

Chapter2 Contents of Capturing Dataset

２．１ Data Element

２．２ Data Structure

２．３ Quality Chapter3 Data Evaluation Method

Chapter4 Metadata

Chapter5 Encoding Specification

５．１ File Format

５．２ Recording Media

Chapter6 Delivered Goods

Chapter7 Others

７．１ Reference Standards and Specifications ７．２ Term Definitions

７．３ Reference


3. Procedure of Creating a Product specification description

A system consists of hardware, software, and data as well as people and organizations that use them.

Creation of a data specification is part of the process of analysis and design of a system. You never create a

data specification without analyzing or designing the entire system. However, this chapter picks up and

describes only the processes concerning data for the sake of explanation of a product specification

description of spatial data.

First, the basic procedure of creating a product specification description is shown in Figure 1. Then,

what to do in each step is described.

Defining requirements

Examining a scope and a

reference system

Collecting and organizing

data

Examining a data evaluation

method

Examining an encoding

specification

Examining meta data

Examining data quality

Checking the delivered goods

Organizing the terms Identifying the product

specification

Checking the r eference

Examining an application

schema

Examining data elements Examining a data structure

Examining

quality

Summary


Figure 1 Flow of creating a product specification description

3.1 Defining Requirements

Define functions to be implemented in the system. This step should not be completed at once.

Determine the functions while listening to the opinions of users of the system and getting feedback from a

subsequent step of designing features. If you cannot identify an application system because, for example, you want to organize data to sell it,

define the expected use.

Example

・Find a route from an arbitrary point to the nearest shelter.

・Specify an "arbitrary point" on a map screen.

・The "shelter" means the entrance of the shelter. ・Display the found route on a map screen.

3.2 Examining an Application Schema

The following describes the procedure of creating an application schema of spatial data as well as

precautions on it. In a product specification description, describe a definition document and a UML class

chart as an application schema and create them in parallel.

3.2.1 Defining a feature (described in Section 2.1 of Chapter III) It is convenient to fill out a form such as a "spatial data requirement definition" to summarize spatial data

as a feature requirement.

(1) Extracting a feature

Read the system requirements, extract a feature class, and give it a class name. Also, describe the

function of a feature because of which the feature class is extracted.

(2) Defining an attribute Define an attribute that each of the feature classes has to implement the function. There are three types

of attributes: "Spatial attribute" representing a spatial characteristic, "temporal attribute" representing a

temporal characteristic, and "thematic attribute" representing a feature's property other than a spatial or

temporal characteristic. Select an attribute for each of the features.

An attribute has a data type such as character type and integer type, which are defined in the geographic

information standard. As for spatial attributes, many kinds of classes are already defined in the geographic

information standard for each of the geometric and topological attributes. To determine a spatial attribute

to define a geographic requirement, you need to be careful to read the section on spatial schemas in the geographic information standard to select an appropriate spatial attribute. As for temporal attributes,

classes that represent each of the instant and the period as a date, time of day, or era, etc. are defined in the

section on temporal schemas.


(3) Defining a feature relationship

As for a relationship between features, define the role of a feature and the relationship between features

specifically as text.

(4) Requirement for quality

Although, in the geographic information standard, an application schema does not include quality

information, describe quality for each feature type or attribute type at this point even if you do not need to

determine details. If, for example, you examine road data to find the shortest route, you can assume a structure using a

topological primitive as a spatial attribute. Furthermore, you can also specify a connection relationship

using quality instead of a topological primitive.

Road

Distance ( )

Road to connect( )

GM_Curve

Shape 1

TP_Edge

Topology 1

Crossing

End

point

Conn

ectio

TP_Node

GM_Point

Topology 1 Position 1

Figure Example of road using a topological primitive

Road

Distance( )

Road to connect ( )

GM_Curve

Shape 1

Quality of Form

Either of the starting or end

point must have the same

coordinate as the starting or

end point of another road.

Figure Example of road not using a topological primitive

(5) Creating a definition document

Organize the examination results for (1) to (4) in a document. The geographic information standard

specifies the items to be entered although it does not specify the style for them.

Table 5b Explanation of a feature requirement definition Item to enter Content

Feature name Name of a phenomenon in the real world as an abstract concept

Feature definition Describe a definition used to specify a phenomenon in the real


world. Acquisition standard Clearly describe the position and direction of acquiring a

feature, the scope of application, etc. Acquisition example Schematically show an example of acquiring a feature

according to the acquisition standard. Name Name of attribute that specifies the spatial characteristic of a

feature. Definition Describe a definition used to specify the spatial characteristic

of a feature. Type Describe a data type (such as a point, line, and plane) used to

specify the spatial characteristic of a feature. Quality evaluation material

Describe information used to evaluate the spatial characteristic quality of a feature.

Positional accuracy Describe the precision of position for acquiring a feature.

Spatial attribute

Quantity Describe the quantity (multiplicity) of spatial data for one instance of a feature.

Name Name of attribute that specifies the temporal characteristic of a feature.

Definition Describe a definition used to specify the temporal characteristic of a feature.

Type Describe a data type used to specify the temporal characteristic of a feature.

Quality evaluation data

Describe information used to evaluate the temporal characteristic quality of a feature.

Positional accuracy Describe the precision of time for acquiring a feature.

Temporal attribute

Quantity Describe the quantity (multiplicity) of temporal data for one instance of a feature.

Name Name of attribute that specifies the thematic characteristic of a feature.

Definition Describe a definition used to specify the thematic characteristic of a feature.

Type Describe a data type used to specify the thematic characteristic of a feature.

Unit Describe the unit of data that represents the thematic characteristic of a feature.

Value range Describe the range of data that represents the thematic characteristic of a feature.

Style Describe such information as the limitation on the number of characters and the required number of decimal places.

Quantity Describe the quantity (multiplicity) of thematic data for one instance of a feature.

Quality evaluation data

Describe information used to evaluate the thematic characteristic quality of a feature.

Thematic attribute

Related attribute Describe other attributes related to the concerned thematic attribute.

Name Name of a figure that needs to be drawn, out of the thematic characteristics of a feature.

Thematic figure

Name of related thematic attribute

Describe the name of a thematic attribute related to the concerned thematic figure.


Portrayal code Describe a code used to refer to the portrayal of the concerned thematic figure.

Name Describe a name used to specify another feature related to the concerned feature.

Definition In a natural language, describe a definition used to specify another feature related to the concerned feature.

Feature association

Related feature name Describe the name of another feature related to the concerned feature.

Regional range of feature Describe a regional range in which a feature is applied. Application and usage Describe the purpose of using a feature, usage of the feature,

etc. Other Describe precautions, remarks. etc.

The following shows an example of application schema document (hereafter called the "feature requirement

definition").


Creation date:

Creator:Featurename

Featuredefinitio

n

Acquisiton

criteria

Name Definition QuantityKijyunten

_IchiPosition of reference point 1

Name Definition Quantity

Name Definition Type Unit Value range Style QuantityQuality evaluation materialKijyunten_Shubetsu

Type of reference pointInteger 1 to 7 1 digit 1 Reference point result table

Kijyunten_Code

Code of reference pointEn-size character string 1 Reference point result table

Kijyunten_Name

Name of reference pointEm-size character string 1 Reference point result table

Zahyokei Coordinate system of reference pointInteger 1 to 19 2 digits 1..2 Reference point result table

X X-coordinate of reference pointReal number ｍ 2 decimalplaces

0..1 Reference point result table

Y Y-coordinate of reference pointReal number ｍ 2 decimalplaces


H Altitude of reference pointReal number ｍ 2 decimalplaces


Name

Name

Regionalrange offeatureApplicati o n a n d

usageOther

Thematic figure

Name of a related thematic attribute Portrayal code

Feature associationDefinition Related feature name

Not required ifthe type is aNot required ifthe type is areference point

Related attribute

Thematic attribute

Temporal attribute

Type Quality evaluation material Positional accuracy

Type Quality evaluation material Positional accuracy

Point Reference point result table

A point of reference (such as horizontal-positioncoordinate, height, directon, and distance) for informaionaccording to each purpose.

Acquire the central position of a structure.

Spatial attribute

Table 5a Sample feature requirement definition

Reference point (Kijyunten) Acquisition example

Acquisitionposition

3.2.2 UML class chart (described in Section 2.2 of Chapter III)

Use a UML class chart to illustrate the definitions of attribute and feature association (if the data type is a class).

3.2.2.1 Defining an attribute

Based on the characteristic of a feature obtained through examination of feature requirements, describe


the feature class attribute (feature class). The following shows an example.

・Example of a "road" class

A road class with a curve "Keijyo" as a spatial attribute, a name "Meisho" that is a character string as a

thematic attribute, a width "Fukuin" that is a numeric value, and a pavement type "HosoShubetsu" that is a

character string.

・Example of a "manhole" class

A manhole class with a contour (plane) "Gaikei" and a lid (real circle) "Futa" as spatial attributes, a name

"Meisho" that is a character string as a thematic attribute, an earth covering "Dokaburi" that is a numeric value.

3.2.2.2 Defining a feature relationship (described in Section 2.1.2.5 of Chapter III)

Use a UML class chart to illustrate in details a feature relationship, which is described as text in the step of

feature requirement definition.

Keijyo

≪Feature≫

DOURO

Meisho：String

Fukuin：Integer

HosoShubetsu：String

GM_Curve

１

[Class chart (UML notation)]

[Class chart (UML notation)]

≪Feature≫

MAN-HOLE

Meisho：String

Dokaburi：Integer

GM_Surface

１

GM_Curve

Futa １ Gaikei


See Chapter 3 for an example.

3.3 Examining a Range and a Reference System

Specify a range and a reference system that concern all the dataset.

3.3.1 Range (Sections 1.2 and 1.3 of Chapter III)

Describe a geographic range and a temporal range used to create a dataset.

(1) Geographic range Describe a geographic range in text using geographic identifiers such as "all the areas of XX Prefecture"

or "a one-kilometer range from the XX-kilometer post to the YY-kilometer post". You may use a brief

map to supplement the description if it seems difficult to understand. Alternatively, use coordinate values

to show the range of a rectangle or polygon. The spatial reference system for the coordinate values in this

case should be the one specified as shown below.

(2) Temporal range

A temporal range is not "time or period in which data is organized" but "time or period represented by data", i.e., "when data is about". When you create data based on a material, the temporal range of the

original material should be the temporal range of data to be created. Thus, be careful that the same

temporal range is specified for the data as the original material. If you specify different original materials

for each feature, specify a temporal range for each feature type.

3.3.2 Reference system (Sections 1.4 and 1.5 of Chapter III)

(1) Spatial reference system based on coordinates

Specify an applicable geodetic system, a coordinate system that indicates a horizontal position, and a coordinate system that indicates a vertical position. In Japan, the global geodetic system is often used (or the

Japanese geodetic system is used before a revised law is enacted in April 2002). As the horizontal coordinate

system, the plane rectangular coordinate system, longitude and latitude, and UTM coordinate system are used.

As the vertical coordinate system, the altitude based on the mean sea level and the compliance ellipsoidal heights

are used.

When you use either of these existing geodetic systems or coordinate systems, specify its name (plus a system

number if you use the plane rectangular coordinate system or a zone number if you specify the UTM coordinate

system). When you use an original geodetic system or coordinate system, specify a parameter value.

Additionally, specify the unit of a coordinate value and the number of decimal places. The geographic

information standard does not include a specification on units. Specify an appropriate number of decimal places

so that there is no contradiction in the quality of positional accuracy.

In the specification of the geographic information standard, you can define a coordinate system for each of the

spatial attributes. Logically speaking, therefore, you can specify the longitude and latitude coordinate system for

one building and the plane rectangular coordinate system for another building. However, you are recommended

to use only one coordinate system for a dataset.

For you reference:


Japanese geodetic system (Tokyo Datum) Was specified in Article 11 (Measurement Standards) of the Measurement Law before revision.

Global geodetic system (Japanese Geodetic Datum 2000)

The requirements of the geodetic system are specified in Article 11 of the Measurement Law after

revision. The semi-major axis and the flattening are specified in the Measurement Law's Cabinet Order

revised at the same time.

Plane rectangular coordinate system

See the description on the plane rectangular coordinate system in the Construction Ministry's Notice No.

3059 released on October 11, 1968.

(2) Spatial reference system based on geographic identifiers

To perform spatial reference based on geographic identifiers, present the identifier type (place name, facility

name, etc.) and the structure of a gazetteer indicated by a pair of an identifier and a coordinate.

(3) Temporal reference system

In Japan, a date includes a year in the Christian era or Japanese imperial era and a month and a day in the

Gregorian calendar. The geographic information standard specifies that the correspondence between a date

in each calendar and a Julian day number must be defined.

Imperial era

Date with year in imperial era

Date in Christian era Julian day number

Meiji M05.12.02 M06.01.01 M45.07.30

1872-12-31 1873-01-01 1912-07-30

2405159 2405160 2419614

Taisho T01.07.31 T15.12.25

1912-07-31 1926-12-25

2419615 2424875

Showa S01.12.26 S64.01.07

1926-12-26 1989-01-07

2424876 2447534

Heisei H01.01.08 1989-01-08 2447535

As time, usually the local time in Japan (Japan Standard Time) is used. This time applies unless

otherwise specified. Data exchange is based on the Coordinated Universal Time.

For example, there is a temporal reference that specifies only an order without using a date or time, such

as "era" or "period" used in geology or archaeology. To use such a temporal reference type, specify a name

and an order.

3.4 Examining Data Quality (Described in Sections 2 and 3 of Chapter III)

3.4.1 Quantitative quality

(1) Determining the range of quality

According to the use purpose, determine the quality for a dataset, feature type, attribute, or feature


relationship. Alternatively, you can determine the quality only for a specific instance. There is no concept

that a certain precision must be maintained for data according to the scale. You can define any data quality

according to the operation. Furthermore, the geographic information standard does not limit the quality to

a positional precision although, so far, many precisions concerned positions.

To eliminate omission of quality descriptions, you are recommended to use a procedure for organizing

data for each feature type and, as required, for each attribute or feature relationship. If, as a result, the same

quality can be applied to all the feature types in a dataset, describe it as the quality of the dataset. (2) Selecting quality elements

A quality element is a sort of quality classification. There are five elements (completeness, logical

consistency, positional accuracy, temporal accuracy, and thematic accuracy) and 14 subelements under them.

In addition to these, a user can add any quality element or quality subelement. It is an effective way for

eliminating omission of quality descriptions to list all the quality elements and subelements in advance and

fill out the quality requirements. Table 6 shows an example.

(3) Defining quality Measure the quality using a difference between the ideal and the reality. In a definition of quality, give a

value to be measured and a threshold value to be used on the measured value to determine if the quality is

conforming. For example, define that the product is acceptable if the error rate is such-and-such percent

or lower or the standard deviation of an error is such-and-such or less. If you describe no pass/fail criteria,

simply report a measured value.

The data evaluation method is described in the next chapter.


Table 6 Quality requirement and data evaluation method definition

Creation date: / / /

Creator:

Feature


Excess

Omission

Value range consistency

Format consistency


Absolute or externalaccuracyRelative or internalaccuracyGrid data positionalaccuracyTemporal measurementaccuracy

Temporal consistency

Temporal validity

Accuracy of qualitativeattributeAccuracy of quantitativeattribute

Remarks

Completeness

Positionalaccuracy

Logicalconsistency

Userdefinition

Quality Requirement and Check Method Definition

Temporalaccuracy

Quality element

Thematicaccuracy

Accuracy of classification

To examine data quality, define quality requirements in this field.

To examine a data evaluation method, define a data evaluation method

in this field.


3.4.2 Non-quantitative quality

In the concept of a product specification description, a creation method is basically not specified.

However, you can specify the original material depending on the use purpose of a product.

In such a case, specify "what, from what, and how to create" including the following items:

- Original material name

- Target feature type name - How to use the original material

3.5 Examining the Data Evaluation Method

Describe the arrangements on the quality requirements and fill out the Quality Requirements and Remarks

fields of the data evaluation method definition shown in Table 6. Since the quality requirements and the

evaluation method should be summarized in the same table. You can describe the quality requirements and

the data evaluation method only in one chapter.

3.5.1 Selecting a quality evaluation method (described in Section 3.2 of Chapter III)

According to the definition of quality elements, select a quality evaluation method.

(1) Direct and indirect evaluation methods

Give preference to the direct evaluation method.

(2) External and internal evaluation methods

The use of the internal evaluation method enables full and automatic inspection and enhances the

precision of the evaluation. Wherever possible, select the internal evaluation method. You can apply it to the value range consistency, format consistency, topological consistency, and temporal consistency.

(3) Full and sampling inspections

Select the full inspection wherever possible, for example, when data can be compared with other data that

indicates a universe of discourse. In other cases, decide on an appropriate inspection in consideration of the

number of instances.

(4) Automatic and visual inspections

Give preference to the automatic inspection.

3.5.2 Comparison target (described in Section 3.1 of Chapter III; see also Section 7.2)

If you have selected an external evaluation method, furnish a material to be compared against or another

measurement method assumed more accurate.

3.6 Examining Metadata (Described in Section 4 of Chapter III)

3.6.1 Examining a profile

The geographic information standard specifies full-set metadata as well as core metadata, which consists

only of major part. Additionally, the Japan Metadata Profile is shown as reference. Examine which of the


three specifications you want to adopt or whether you want to adopt a specification that you define for

yourself.

Perform this examination, not for each dataset but for a sizable unit such as a dataset series or an

organization that creates data.

3.6.2 Instructing to create metadata

In a product specification description, describe metadata elements to be created together with data. Of the metadata elements, quality information can be written by the data creator. However, other

elements should be created by the party that commissions the creation of data because some of them are the

same as described in a product specification description and others concern the party that commissions the

creation of data.

3.7 Examining the Creation of a Encoding Specification (Described in Section 5 of Chapter III)

For exchange of data between different systems, common application schemas, encoding rules, and

transmission protocol are required. An application schema is described in Chapter 3. There are offline

and online procedures for a transmission protocol but they are not specified in a product specification

description. This section describes the procedure of creating an encoding specification. Encoding rules

refer to a set of rules of conversion into exchange data with an independent data structure from the system.

The first group consists of schema conversion rules and the second group consists of instance conversion

rules. The former is used to convert an application schema described in UML into a DTD in XML. The

latter is used to convert data created according to an application schema into an XML instance.

3.7.1 Schema conversion rules

There is a possibility of automatically creating a DTD from an application schema, which is not a

common practice yet. This section specifically describes how to create a DTD in XML.

(1) Defining a DTD as a premise

A feature requirement definition or class chart (UML chart) defines the attribute of each feature (class) and the feature association. These definitions are reflected in a DTD in XML. The DTD, used to verify

the validity of an XML document, bears an important role in implementing the encoding and decoding

functions in data exchange. Since the geographic information standard defines a basic standard DTD

declaration, this declaration must be utilized as a premise. In addition to this standard DTD, six more

DTDs are actually required.

1 Standard definition (std.dtd)

2 Spatial attribute definition (Spatial.dtd) 3 Temporal attribute definition (Temporal.dtd)

4 Meta data definition (Metadata.dtd)

5 Direct reference definition (DirectPositioning.dtd)

6 Indirect reference definition (IndirectPositioning.dtd)

(2) Referring to a DTD definition

<?XML version=”1.0” encoding=”Shift_JIS” ?> 



<!ENTITY % standard.declations SYSTEM “std.dtd” >

 <!ENTITY % spatial.declarations SYSTEM “Spatial.dtd” >



<!ENTITY % temparal.declarations SYSTEM “Temporal.dtd” >

You can create a DTD by referring to the above DTD definitions.

（３） Correspondence between a UML class chart and the description in a DTD

The geographic information standard specifies that an application schema should be described using a

UML class chart. Using a simple UML class chart as an example, this section describes the

correspondence and relationship between it and a DTD.

In this case, the spatial and temporal schemas are in an aggregation relationship (composite) to the reference

point class. Therefore, the spatial and temporal schemas are represented as internal tags in a reference point

class. However, the geographic information standard specifies that a thematic attribute should also exist as

GM_Point TM_Period

Kijunten

≪Feature≫

＋Shubetu : Integer

＋Hyoko : Real

＋SokuryouDate : Date

＋ShutokuDate : Date

＋Name : CharacterString

Point Period Role name

Thematic attribute

Spatial attribute Temporal attribute

Application schema description

Class name

an internal tag of the reference point class. Thus, declare the items of a thematic attribute as follows:

 (1) <!ELEMENT Shubetu %Integer>

<!ELEMENT Hyoko %Real >

<!ELEMENT Name %CharacterString >

<!ELEMENT SokuryouDate %Date >

<!ELEMENT ShutokuDate %Date >

(2) <!ENTITY % KijuntenElement ‘(point,period?,

Shubetu, Hyoko,

Name,

SokuryouDate,

ShutokuDate)’ >

(3) <!ENTITY % KijuntenAttribute ‘ ‘ >

(4) <!ELEMENT Kijunten %KijuntenElement ; >

(5) <!ATTLIST Kijunten %IM_ObjectAttributes; %KijuntenAttribute; >

(1) Defining a thematic attribute

Declare all the thematic attribute items in an ELEMENT statement. This declaration makes the KijuntenElement definition in (2) effective.

(2) Defining a substitution string for a reference point element

In a parameter ENTITY statement, define a reference point element. In the above example, a

substitution string "（Point, Period? Shubetu, Hyoko, …, ShutokuDate）" is defined for

KijntenElement (class name + Element). This substitution string must give a role name (role) and

a thematic attribute in a UML class chart. Although you can specify GM_point and GM_Curve

that are a geometric element package based on a spatial schema or TM_Period that is a temporal

attribute, the geographic information standard specifies that a role name should always be used. Therefore, you need to define a role name as shown below and the role name should be defined

basically in Spatial.dtd.

Furthermore, specify the multiplicity of elements here. For example, a question mark (?)

added to the end of the Period role name means that the element appears never or once according

to the XML syntax. In other words, the Period element may not exist. Define a thematic

attribute in (1) and refer to it in ②.

<!ELEMENT Point %GM_PointElements; > <!ELEMENT Period %TM_PeriodElements;>

（*）GM_PointElements is defined in spatial.dtd.

<!ENTITY % GM_PointElements ‘(CRS,Position)’ >

CRS and Position are defined likewise.

Role name


（*）TM_PeriodElements is defined in Temporary.dtd.

<!ENTITY % TM_PeriodElements ‘( )’ >

(*) About multiplicity

＋ Repeated once or more (1..+)

＊ Repeated never or once or more (0..*)

？ Repeated never or once (0..1)

(3) Defining a substitute string for a reference point attribute

In a parameter ENTITY statement, give a dummy in a substitution string for KijuntenAttribute.

(4) Defining a reference point

Define a reference point element in an ELEMENT statement. In this example, the reference

point class (Kijunten) refers to KijuntenElements to express that the reference point is in a

hierarchical structure as the elements: Point, Period, Shubetu, etc.

(5) Defining a reference point attribute

Define the thematic attribute of a reference point. If, in an ATTLIST statement,

KijuntenAttribute specified in (2) is specified as an attribute definition, then IM_ObjectAttributes (instance model attribute: defined in a standard DTD) is invariably inherited at the same time.

This adds a reference point attribute (ID and UUID).

3.7.2 Instance conversion rules

The following shows a sample of encoding an XML document from the above reference point, DTD.

A thematic attribute is created as an internal tag of the reference point. A spatial attribute is defined in

Spaial.dtd if the DTD is given a role name, point. <!ENTITY %GM_PointElements ‘(CRS,position)’>

<!ELEMENT Point %GM_PointElements; >

This extracts data into the CRS and the position tag. This also applies if role names, curve (line) and

shape (plane) are referenced.

Reference point

Point Period Shubetu ShutokuDate

<Kijunten id=”K0002”

uuid=”0002”

<Point id=”P0001” uuid=”0003”>

<CRS idref=”CRS01” />

<position>xxx1 yyy1</position>

</Point> <Period id=”T0001”>

<begin>20011112</begin>

</Period> <Shubetu>”1”</Shubetu>

<Hyoko>”100.22”</Hyoko>

<Name>”XX's Grade 2 triangulation point”</Name>

<SokuryouDate>”2001/11/12”</SokuryouDate>

<ShutokuDate>”2001/11/12”</ShutokuDate>

</Kijunten>

3.7.3 Description for when an enumerated type thematic attribute exists

Generally speaking, many of the thematic attributes are enumerated type thematic attributes. In a

conventional description method, it is difficult to define an enumerated type thematic attribute. Therefore,

the following application schemas, DTDs, and XML descriptions should be adopted. In other words, an

enumerated type attribute should be handled as an attribute without creating an internal tag.

- Class chart

- DTD

Spatial attribute

Temporal attribute

IM_ObjectAttributes

Thematic attribute

+ Pay

+ Free

<<Enumeration>>

Doro_Yuryo

<<feature>>

Douro

+name[0..*]:STRING

+Yuryo:Doro_Yuryo

+KokudoBango[0..*] :INTEGER

+curve: GM_Curve

Enumerated type

thematic attribute


<!ENTITY % Douro_Yuryo 'Yuryo (Pay|Free) “Free” #REQUIRED ' >

<!ENTITY % DouroElements 'Name*,KokudoBango*,curve' > <!ENTITY % DouroAttributes %Douro_Yuryo; >

<!ELEMENT Douro (%DouroElements;) >

<!ATTLIST Douro %IM_ObjectAttributes; %DouroAttributes; >

- XML document

<Douro id=”d00001” uuid=”d000001”

Yuryo=”Free”>

<Name>Route 1</Name>

<KokudouBango>1</KokudouBango>

<curve id=”000001”

uuid=”000002”> <CRS idref=”crs000001”/>

<segment>

<controlPoint>504000 108000</controlPoint>

<controlPoint>504000 108001</controlPoint>

<interpolation>linear</interpolation>

</segment>

</curve>

</Douro>

3.8 Organizing Data

Add the following information when you disclose a product specification description to the outside, for

example, to commission the creation of data based on the established product specification description.

3.8.1 Abstract of product (Section 1.1 of Chapter III)

First, create an abstract based on the defined requirements and the contents of application schemas and

add it to the beginning of a product specification description. (1) Purpose of creating data

(2) Abstract of data

(3) Use of data

3.8.2 Check of delivered goods

Express the result created based on a product specification description using a unit that can be physically

identified.


File in which dataset is recorded One

File in which metadata quality information is recorded One

3.8.3 Reference standards and specifications (Section 7.4 of Chapter III)

3.8.4 Terms and abbreviations (Section 7.1 of Chapter III) Out of the terms used in a product specification description, describe terms and abbreviations not defined

in other standards, etc. that are quoted. For a term, describe a name, pronunciation, definition and, if

required, examples and remarks. For an abbreviation, describe a name, non-abbreviated formal name,

definition and, if required, examples and remarks.

3.8.5 Identifying a product specification description

In this item, describe a product specification description itself. (1) Title

Give a title that uniquely identifies this product specification description. Add a version number if

required.

(2) Series

Describe a series name if a dataset to be created based on this product specification description is part of a

dataset series.

(3) Date

Describe a date at which the product specification description is created or published.

(4) Person in charge

Describe the person to which an inquiry about this product specification description should be addressed as well

as a telephone number, facsimile number, mail address, and/or address that can be used for the inquiry.


Appendix A Typical Examples of Product specification descriptions

1. Example of Spatial Data Foundation 2500

Product specification description for 1/2500 Spatial Data Foundation (Plan)

1. Abstract of Product

1.1 Purpose of Product

Spatial data to be created based on this specification shall be used as basic data to be used in a geographic

information system and as skeletal data to be used to allocate spatial data in a correct position.

1.2 Regional Range of Data

The range of spatial data to be created shall be the entire region of XX City of YY Prefecture.

1.3 Temporal Range of Data

The temporal range of spatial data to be created shall be, in principle, the creation date of a loaned material

described in Section 7.2.

1.4 Coordinate System

The coordinate system and the measurement unit shall be as follows:

Applicable measurement system : Japanese measurement system (Tokyo Datum) Horizontal-position coordinate type: Plane rectangular coordinate system XX

(Construction Ministry's Notice No. 3059 released on October 11, 1968)

Altitude standard: Mean sea level of Tokyo Bay, in reference to the Japanese original benchmark

Unit: Meter (up to two decimal places)

Dimensions of spatial coordinates: Two

Temporal standard: Japan Standard Time


2. Contents of Capturing Dataset

2.1 Data Elements

Capture the following spatial data elements: No. Feature type name Feature class name 1 City, ward, town, or village Sichouson 2 Village or town section Ooaza 3 Block Gaiku 4 Road line Dourosen 5 Railroad line Tetudousen 6 Station Eki 7 Railroad site Tetusiki 8 Urban park Tosikouen 9 School site Gakkou 10 Shrine and temple precinct Jinjyajiin 11 Graveyard Boti 12 Other place Bati 13 River Kasen 14 Lake, pond, etc. Kosyou 15 Coastline Kaigansen 16 Public building Koukyoutatemono 17 Reference point Kijyunten

Note (E):

The feature class names in the above table are Japanese words in alphabet (roma-ji notation).

The requirements of data to be captured are shown in a requirement definition in the attached document.


2.2 Data Structure

Spatial data to be created shall have the following capturing form and attributes to be added. In this

example, only part of the items are shown.

(1) City, ward, town, or village; village or town section; and block

Sichouson

Curve : GM_Curve

≪Feature≫

Ooaza

Curve : GM_Curve

≪Feature≫

Gaiku

Shape : GM_Surface

≪Feature≫

Name : String

GeoID : SI_LocationInstance

NamePos : AP_Text

２．３ Quality Each of spatial data to be created shall have quality that meets the one defined in Attachment 3 (Quality

Requirements and Evaluation Method Definition).

3. Data Evaluation Method

For each of the captured items, check the quality according to the method defined in Attachment 3

(indicated earlier) and summarizes the result to create a quality check report.

4. Metadata

Create metadata according to the Japan Metadata Profile (JMP).


5.1 File Format

Record a dataset in a recording media according to the encoding specification provided in the attached

document.

5.2 Recording Media

Store a dataset or metadata in a magneto-optical disk (640 MB).


6. Delivered Goods, etc.

6.1 This product consists of the following:

・Dataset One

・Quality check report One

・Metadata One

7. Others

7.1 Definitions of Special Terms

Use the terms defined in the geographic information standard except for those defined in this specification.

7.2 Reference

To capture numeric data, use the following data or use it as reference.

1/2500 national base map

1/2500 urban planning map

1/2500 digital map

1/10000 topographic map

Digital map 10000 (comprehensive)

Control point data XX Civil Engineering Office service area map

Cadastral map

Note (E):

The above references are map materials or map data available in Japan.


2. Example of Disaster Prevention System Data (Creation Experiment)

Product specification description for Disaster Prevention Spatial Data (Plan) 1. Purpose of Product

1.1 Purpose of Product

Spatial data to be created based on this specification shall be used to establish a community disaster prevention plan on the assumption of an earthquake and perform traffic regulation during a disaster by

allowing people, for example, to recognize the road status and the positions of disaster prevention facilities,

dangerous facilities, storage facilities, shelter facilities, medical care facilities, and entertainment facilities

and to find emergency evacuation routes.

1.2 Regional Range of Data

The range of spatial data to be created shall be the entire region of XX City of YY Prefecture.


The temporal range of spatial data to be created shall be the creation date of a loaned material.

1.4 Coordinate System

The coordinate system and the measurement unit shall be as follows:

Applicable measurement system : Japanese measurement system (Tokyo Datum)

Horizontal-position coordinate type: Plane rectangular coordinate system VI (Construction Ministry's Notice No. 3059 released on October 11, 1968)

Altitude standard: Mean sea level of Tokyo Bay, in reference to the Japanese original benchmark

Unit: Meter (up to two decimal places)

Dimensions of spatial coordinates: Two

Temporal standard: Japan Standard Time


2. Abstract of Capturing Dataset

２．1 Types of Capturing Data

Capture the following spatial data elements: No. Feature type name Feature class name 1 School GAKKOU 2 School entrance GAKKOU_IRIGUCHI 3 Hospital BYOUIN 4 Hospital entrance BYOUIN_IRIGUCHI 5 Park KOUEN 6 Park entrance KOUEN_IRIGUCHI 7 Shrine or temple JINJYABUKKAKU 8 Shrine or temple entrance JINJYAKUKKAKU_IRIGUCHI 9 Factory KOUJYOU 10 Gas station GASORINSTAND 11 Gas tank GASUTANKU 12 Commercial establishment SYOUGYOUSHISETSU 13 Movie theater EIGAKAN 14 Theater GEKIJYOU 15 Major building TATEMONO 16 Road center line CHUSHINSEN 17 Road crossing, etc. KOUSATEN 18 Road edge DOUROEN 19 Roadside tree GAIROJU 20 Railroad center line TETSUDOU 21 Station EKI 22 River or waterway KASEN 23 Lake or marsh KOSYOU 24 Reference point KIJUNTEN 25 Administrative district GYOUSEIKAI 26 Town or village section OAZA 27 Block GAIKU 28 Fire prevention facility BOUKA 29 Urban planning area or zone TOSHIKEIKAKUCHIIKICHIKU 30 Aerial photograph KOUKUUSYASHIN

Note (E):

The feature class names in the above table are Japanese words in alphabet (roma-ji notation).

２．2 Requirements of Capturing Data

The requirements of data to be captured shall, for each item to be captured, conform to the attached

feature requirement definition. Furthermore, the enumerated type shall conform to the attached

enumerated feature attribute or feature attribute value. In this example, only part of the items are shown.


2.3 Data Structure

The forms of data to be captured and an attribute to be added are as shown below. In this example, only

part of the items is shown.

Feature type name: School (GAKKOU)

GAKKOU

Shape : GM_Surface

GAKKOU_KUBUN : Integer

≪Feature≫

GAKKOU_NAME : CharacterString

GAKKOU_MENSEKI : Real

1..*

GAKKOU_IRIGUCHI

Iriguchi

Feature type name: School entrance (GAKKOU_IRIGUCHI)

GAKKOU

1..*

GAKKOU_IRIGUCHI

Point : GM_Point

Iriguchi ≪Feature≫


2.4 Quality Requirements and Evaluation Method

Each of the spatial data to be created shall meet the following quality. In this example, only part of the

items is shown.

Supplementary remarks *1 The loaned data is based on the "List of Loaned Data from XX City". *2 As a sample, use three meshes arbitrarily selected from the 24 meshes into which the entire area is

divided (one mesh is 250 m by 250 m).

Creation date: XX/XX/XX Quality Requirement and Check Method Creator: YYY

Feature


Excess Error rate: 0% Full comparison inspection on loaned data (*1) and a dataset output chart. * Report a quality value in a

percentage (number of errors divided by total).

Omission Error rate: 0%

Full inspection using a program * Report a quality value in a


Format consistency －－

Topological consistency －－

Error value against site survey assumed as true

: Standard deviation of 1.75 m or less

Relative or internal accuracy －－

Grid data positional accuracy －－

Temporal measurement accuracy －－

Temporal consistency －－

Temporal validity －－

Accuracy of classification －－

Full comparison inspection on loaned data (*1) and dataset output information. * Report a quality value in a


Accuracy of quantitative attribute

Error rate for each item : 5% or less

Attribute value code in the thematic attribute value range

Error rate for each value out of the value range: 0% Logical

consistency

－－

School

Quality element

Site survey using a measurement method having a 15-cm accuracy based on national triangulation points and reference points of the concerned city * 12.5% sample (*2) inspection

Absolute or external

accuracy Positional

accuracy


Complete- ness

Temporal

accuracy

Thematic

accuracy

User definition －

Accuracy of qualitative attribute

Error rate for each item: 0%



For each of the captured items, check the quality according to a data evaluation method and create a

quality check report as follows:

Creation date: XX/XX/XX Creator: YYY Co., Ltd.

Feature

Spatial attribute

Quality requirement Quality evaluation method

actually used Quality evaluation

result

Excess Error rate: 0% Full comparison inspection on loaned data and a dataset output chart. * Report a quality value in a percentage

(number of errors divided by total).

0% (conforming)

Omission Error rate: 0%


Attribute value code in the thematic attribute value range Error rate for each value out of the value range: 0%

Full inspection using a program * Report a quality value in a percentage

(number of errors divided by total). 0% (conforming)


Error value against site survey assumed as true: Standard deviation of 1.75 m or less

Site survey using a measurement method having a 15-cm accuracy based on national triangulation points and reference points of the concerned city * 12.5% sample (*2) inspection (See

the sample range chart.)

0.32 m (conforming)

Quality Check Report

School

School site (plane)

Quality element

User definition

Comple- teness

Logical consistency

－－－－

Format consistency

－－－


－－－


－－－


－－－


－－－

Temporal consistency －－－

Temporal validity －－－

Accuracy of classification －－－

Accuracy of qualitative attribute

Error rate for each item: 0% Full comparison inspection on loaned data and dataset output information. * Report a quality value in a


0% (conforming)

Accuracy of quantitative attribute

Error rate for each item: 5% or less

0% (conforming)

Thematic accuracy

Positional accuracy

Temporal accuracy

0% (conforming)

4. Metadata



5.1 File Format Record a dataset in a recording media according to the following specification. In this example, only part

of the items is shown.

Feature type name: School (GAKKOU)

Encoding specification table Type Name in alphabet Multiplic

ity Data type Encoding method Tag name

Feature class GAKKOU ― TEI: Feature element with ID GAKKO Thematic attribute

GAKKOU_NAME 1 CharacterString A: Attribute list NAME

Thematic attribute

GAKKOU_KUBUN 1 Integer A: Attribute list KUBUN

Thematic attribute

GAKKOU_MENSEKI 1 Real A: Attribute list MENSEKI

Spatial attribute Shape 1 GM_Surface CE: Consisting element Shape Integration association

Iriguchi 1..* GAKKOU_IRIGUCHI CE: Consisting element GIRI

XML document sample  <GAKKO id="F1_0001" NAME="ｘｘｘ" KUBUN="1" MENSEKI="nnn.n">

<Shape id="F1S0001"> <CRS idref="CRS01" /> <patch>

<controlPoint>xxx1 yyy1</controlPoint> <controlPoint>xxx2 yyy2</controlPoint> <controlPoint>xxx3 yyy3</controlPoint> <controlPoint>xxx4 yyy4</controlPoint> <controlPoint>xxx1 yyy1</controlPoint> <interpolation>planar</interpolation>

</patch> </Shape>

 <GIRI id="F2_0001" >

：：

</GIRI> </GAKKO>

id, which is unique in a dataset, shall be "F1_nnnn" (nnnn is a serial number) for a "school" feature or "F1Snnnn" (nnnn is a serial number) for a shape in it. For CRS, specify "CRS01" that has been defined in the common definition part. A coordinate value, based on the plane rectangular coordinate system, shall be in meters and have up to two decimal places. For interpolation, specify "planar". Describe the "School entrance" feature in the "School" feature tags.

XML Schema <complexType name="GAKKO" base="IM_Object" derivedBy="extension" >

<group name="GAKKOElements"> <element name="Shape" type="GM_Surface" />


<element name="GIRI" type="GIRI" maxOccurs="*" />

</group> <attributeGroup name="GAKKOAttributes">

<attribute name="NAME" type="CharacterString" /> <attribute name="KUBUN" type="Integer" > <enumeration value="1" /> <enumeration value="2" /> <enumeration value="3" /> <enumeration value="4" /> <enumeration value="5" /> <enumeration value="6" /> </attribute> <attribute name="MENSEKI" type="Real" />

</attributeGroup> </complexType> DTD <!ENTITY % GAKKOElements '(Shape, GIRI+)' > <!ENTITY % GAKKOAttributes ' NAME CDATA #REQUIRED KUBUN (1|2|3|4|5|6) #REQUIRED MENSEKI CDATA #REQUIRED ' > <!ELEMENT GAKKO %GAKKOElements; > <!ATTLIST GAKKO %IM_ObjectAttributes; %GAKKOAttributes; >

Shape is defined in common.

5.2 Recording Media


6. Delivered Goods, etc.

6.1 This product consists of the following: ・Dataset One


・Metadata One

7. Others



7.2 Reference

As required, use the following materials or use them as reference.


End

Content Loan date Remarks

Product name

DM data

Road network data Road ledger data Cho and chome polygon

Oaza code Residence indication data Aerial photograph images

Park data School zone data Reference point data

Roadside tree routes

List of elementary school attendance zones

Household population by cho and chome

List of educational facilities

List of hospitals Residence indication total map

Disaster prevention map for home use

Urban planning map

Elementary and junior high school district map

Parks and green spaces distribution map

List of offices that handle

Form

Table (B4), 12 Map (1/10,000)

Map (1/30,000)

Pamphlet

Table (A4), 2

Table (A3), 3 Table (A4), 6

Table (A4), 1

Data (shape) Data (shape, mdb)

Data (mr SID)

Data (mdb)

Data (DM)

Data (shape)

Data (shape, mdb)

Map (1/10,000)

Map (1/10,000)

Data (shape)

Data (shape)

Data (shape)

Data (shape, mdb)

Name, number, classification, address Location map, list of parks (including areas), list of green ways and green spaces

Application district, fire-prevention and semi-fire-prevention zones, etc.

Disaster prevention map (shelters, fire stations, emergency medical organizations, etc.)

Name, number of beds, specialties, locations, telephones

Name, site area, etc.

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX

XX. X. XX


3. Example of River Spatial Data

Product specification description for Spatial Data Creation Experiment (Plan)

１． Abstract of Capturing Dataset

1.1 Purpose and Usages

This specification is aimed at unifying standards for creating "river foundation data" used by a river manager to promote a river project and defining detailed contents of a standard data element.

Data that complies with this standard is assumed to be used on a GIS to be constructed by a river manager.

The following lists some major usages of the data:

(1) Using data for daily management

Display the flow volumes, water levels, and other information continuously measured for daily

management of a river and a river facility, together with their positions. This is a usage pattern like a

telemeter. (2) Performing simulation

Simulate on a computer how much flood damage is expected from the precipitation in a certain area

(which can be calculated as such-and-such year probability) based on the information on a river and land

forms and other peripheral information in order to learn the range of expected damage during a disaster. A

hazard map can be created based on this information.

(3) Creating a material

Use this data to create a explanatory material for an external or internal meeting or a material to be used to

explain a drawing for report or project map (such as construction plane or intersection view, etc. for a project implemented in the previous, current, or next or subsequent fiscal year or a plan view that illustrates middle-

or long-term project plan).

Furthermore, a hazard map, etc. is assumed to be used, for example, to create a material for analysis of

project effects or explanation of the project to the concerned residents.

(4) Using data as a basic map for emergency responses

Use this data for information analysis and report when a disaster occurs or is expected to occur. If a river

course is buried by a landslide or debris avalanche as well as a flood, the data may be used to learn the riverbed inclination, flow volume, catchments area, etc.

1.2 Regional Range (Rectangular Range, Infinite-form Range, and Description)

As the regional range, this specification applies to river courses, tributaries, inundated districts, and

catchment area of a first-grade river system or major second-grade river system's river section for which a

river course renovation plan exists.


The temporal range of spatial data to be created shall be the creation date of an original material.


１．4 Coordinate System (Reference System, Coordinate System, Time, and Weights and Measures)

Applicable measurement system Japanese measurement system (Tokyo Datum)

Horizontal-position coordinate type

Using as the origin the lower left corner of each map contour of a 1/2500 national base map. The direction to the right is the positive direction of X. The direction to the up is the positive direction of Y. The upper right corner is (2000, 1500). This is a normalized coordinate system in units of meters.

Altitude standard Mean sea level of Tokyo Bay, in reference to the Japanese original benchmark

Unit Meter (up to two decimal places)

Temporal standard Japan Standard Time

2. Abstract of Capturing Dataset

2.1 Data Elements

The spatial data to be captured, being targeted at features directly related to a river operation, include the

following items:

Kilometer stake Traverse line Low-water channel stake Current embankment normal line Current low-water channel normal line River center line River course polygon Low-water channel polygon Node

For details, see the feature requirement definition provided in the attached document.

2.2 Data Structure

The forms of data to be captured and an attribute to be added shall conform to the application schema provided in the attached document.

2.3 Quality

Each of the spatial data to be created shall meet the quality defined in the quality requirement and

evaluation method definition provided in the attached document.



For each of the captured items, check the quality according to a method defined in the quality requirement

and evaluation method definition provided in the attached document, and summarize the results to create a

quality check report.

4. Metadata



5.1 File Format

Record a dataset in a recording media according to the encoding specification provided in the attached

document.

5.2 Recording Media


6. Product, etc.

6.1 This product consists of the following:

・Dataset One


・Metadata One

7. Others



7.2 Reference

・ Current plane view or DM data

・ Sluiceway ledger

・ Bridge survey ledger

・ Hydrological ledger

・ Flood and inundation hazardous area map

・ List of structures in rivers

・ Important flood-prevention points

・ Lengthwise and crosswise survey result

・ River area map


・ Land, Infrastructure and Transportation Ministry River Codes ・ Embankment ledger


Appendix B Reference Material (in Japanese) 1. Explanation of Metadata Editor for Metadata Standard Format JMP (Abstract) 1.1 Abstract

JMP の適合性レベル１ * JMP 附属書A-B.xlsを掲載 JMP の適合性レベル2 * JMP 附属書A-B.xlsを掲載

* Ⅱのメタデータについての解説とダブらなければ，メタデータのサンプルを掲載する？ 1.2 About JMP Editor JMP Editorは，地理情報標準-メタデータ第1.1版によって定義されている適合性レベル１（JMP）のメタデータの作成を支援するツールである。本ツールを用いることで，JMP 準拠のメタデータ（XML形式のファイル）を作成することができる。

■本ツールの特徴ツールにはMicrosoft Excelを採用。（Microsoft Excel97®以上に対応）このエディタを使用することで，JMP のメタデータスキーマを再現し，大項目-中項目，

繰り返し中項目の入力を，別個のワークシート上で行うことが可能である。また，ボタンやドロップダウンリストを用いて，極力ユーザーによるキー入力操作を軽減するようになっている。 ■本ツールの入手方法下記の国土地理院ホームページからダウンロードできる。入手先URLは以下のとおり http://www.gsi-mc.go.jp/REPORT/GIS-ISO/KMGIS/download.html#hyoujun オンライン以外での入手方法，お問い合わせ先国土交通省国土地理院企画部地理情報システム推進室 TEL：0000-00-0000，FAX：0000-00-0000

2. Overview of UML (Necessity and Effects) 2.1 What is the Unified Modeling Language (UML)?

UMLは，業務のシステム化などを行う際に広く利用されているオブジェクト指向モデリング

言語であり，空間データの構造をUMLを用いた図式によって表現することが可能である。また，さまざまな種類のオブジェクトモデル，オブジェクト指向分析・設計法で使用すること

を目的としているため，非常に自由度の高いノーテーションとなっている。

2.2 Necessity of Description in UML 空間データの構造を明らかにするためには，個々の地物を定義し，各々の地物が持っている特

性を定義し，地物と地物の間の相互関係を定義する必要がある。地理情報標準では，ノーテーションと用語を定義することが可能な UML を用いた図式によっ

て，空間データの構造を表現する。詳しくは，『2.2 データ構造・応用スキーマ』を参照くださ

い。 2.3 Effects of Description in UML 空間データを設計する段階で，その目的・用途にうまく対応した地物の定義を行うことによっ


て，利用しやすい空間データの作成が可能である。参考URL：http://www.w3.org/XML/（XMLの技術仕様に関するW3Cのホームページ）

http://www.jp.biztalk.org/BizTalk/default.htm（XML による電子データ交換の標準仕様に関するマイクロソフト社のホームページ）

2.4 Notation of UML Class Chart

（１）クラスの記法

クラスは３つの区切りを持った矩形で表す。例えば、ある不動産会社において建物の情報を管

理するシステムで使用する空間データを作成するにあたって、建物というクラスを定義する。（図

２参照）

①クラス名・ステレオタイプ

クラスには、クラスの名前、属性をそれぞれ記述する。

クラスには名前を付け（クラス名）、いちばん上の区画に記述する。クラス名の上には必須では

ないが、必要に応じてクラスの大分類を記述することができ、これを“ステレオタイプ”と呼ぶ。

これはそのクラスがどういったものかをわかりやすくするためのものである。ちなみに、この例

での“Feature”とは地理情報標準において定められており、このクラスが地物であることを示す

ステレオタイプである。

②属性

それぞれのクラスには種々の属性の名称とデータ型を定義することができ、それらを 2番目の

区画に記述する。属性名称の先頭に＋や－の記号をつけることにより、各属性が外部に公開する

かどうか（可視性）といった一種のセキュリティを設定することができる。

図２．クラスの記法

任意の名称

＋形状：面

－建物ID：整数

＋名前：文字列

－住所：文字列

《Feature》

建物クラス名

属性属性名称とデータ型を書く

－記号：外部から参照不可

＋記号：外部から参照可能可視性：属性、操作の先頭に記述する。

※属性の初期値など、さらに詳細情報の記述も可能であり、他の参考書籍を参照のこと。

ステレオタイプクラスの大分類に相当


③その他

本来のUMLクラス図ではシステムの構造を記述する場合、“操作”や“振る舞い”と呼ばれる、

そのクラスが持っているべき機能を記述するが、空間データでは操作を定義しても利用する GIS

ソフトによってその操作を実現できないこともあることから、地理情報標準での応用スキーマで

は操作の記述はしないことになっている。

例として図２のクラスでは、以下の情報を示している・クラスの名前は「建物」

・クラスの大分類（ステレオタイプ）は地物（Feature）である。

・属性として「形状」「建物 ID」「名前」「住所」を持つが、「名前」と「形状」以外は

外部からは参照できない

クラス図は、正式には上記のクラス表記方法に基づいて記述されるものであるが、ここでの解

説では、すべて正式な表記法で記述すると図式が煩雑となるため、必要に応じて省略形で記述し

ているので、実際に応用スキーマを記述する際には注意が必要である。

（２）クラス間関連の記法

クラスが二つ以上存在するような場合には、それぞれのクラス間になんらかの関連を持ってい

る場合もある。クラス図ではそれらの関連も表現することができる。例えば、企業に勤める会社

員が企業で働くというモデルをクラス図で表現すると図３のように書ける。

この例では、“公園”と“公園入り口”というふたつの地物クラスが存在し、入り口から見て“出

入り”という関連を持っている。それぞれのクラスは、名前や住所、管理者、通行時間帯などの

それぞれ独自の属性を持っている。また“出入り”という関連における“公園入り口”クラスの

役割（ロール）としては、“入り口”となる。このようにクラス名が役割を直接示すような場合、

UML クラス図の記法ではロール名を省略することも可能であるが、地理情報標準においては、

後の符号化における作業でロール名が必要となるため、必ず定義する。

これらクラスのインスタンスを考えると、ひとつの公園にはいくつか複数の入り口が存在する。

クラス図ではこれらインスタンス間の数量的な関係も記述する。

公園と入り口それぞれのインスタンス間の数量的な関係は、ひとつの公園（１）に対して複数の

入り口（0．．＊）のような形式で示し、記述する。これを多重度と呼ぶ。

図３．簡単なクラス図

公園

名前

住所

管理者

公園入り口

名前

車両通行可否

通行時間帯

出入り入り口

0..* 1

所属


この例の場合、公園にはいくつかの入り口があるが、原っぱのような柵のない公園の場合には、

明示的な入り口というものが存在しないケース（入り口が 0 個）もあるため、0 個以上複数とい

うことで 0．．＊となっている。

このようにクラス図では、次の表に示す記法によりクラス間を線分で結び、それらに各種の注

記を加えることにより、クラス間の関連が記述できるようになっている。しかしながら、システ

ム上でこれらの関係付けをどのように実装するかについては、それぞれのアプリケーションシス

テムでの機能にゆだねるものであり、データ構造は特定のシステムから分離独立するものである。

（３）その他の記法

UMLクラス図では、“ノート”と呼ばれる、自由なコメントなどのテキスト情報を図６のよう

な形式で記述することができる。ノートは単独でクラス図に書き込んでもよいし、破線によって

クラス図中の要素に結び付けるような使用もできる。

関連の名前記法

関連（association）

集約（aggregation）

ｺﾝﾎﾟｼﾞｼｮﾝ（composition）※合成や複合と呼ぶ場合もある

汎化（generalization）

依存（dependency）

誘導可能性（navigability）

実現（realization）


図５．多重度の記法

1 対１

1 対０または0..1

1 対０以上＊

1 対1 以上 1..

1 対１または1,4

1 対１～３ 1..3

1 対３以上 3..1

図６．ノート

自由に内容を記述可能


2. Example of Association between Classes

クラス間の関連は図４に示すような図式で表される。ここでは一般的な関連と汎化、集約・コンポ

ジションの例について示す。

（１）関連

クラス図において、クラス間の関連の表記形式では、関連名、ロール名を用いて自由に命名す

ることが可能である。関連における方向（主語からそれ以外の目的語等への方向）

を指定するために、関連名の横に印をつけることもできる。

※図３の場合、クラス間に主語－目的語といった関係が無いので,省略されている。

（２）汎化

汎化は関連の一形態で、クラス間において親子関係を持ち、属性の共通する部分を親から子へ継承

するような関係である。相対的に子供側のクラスから見て親側のクラスを“スーパークラス”、親クラ

スから見て子供側のクラスを“サブクラス”と呼ぶ。

継承関係においては、スーパークラスで定義した属性が、サブクラス側で改めて定義しなくてもそ

図７．クラス図の全体イメージ

クラスB

属性

関連名役割A 役割B

1..* 1

クラスA

属性

多重度

ロール名関連名

集約

クラスb

属性

汎化

コメントや説明

クラスa

属性

関連

ノート

コメントや説明

ノート

（単独）


のまま利用できるため、煩雑な定義から解放されるといったメリットがある。汎化を示す線分には親

側のクラスに三角記号をつける。

《例》汎化

（３）集約・コンポジション

集約は関連の一形態で、関連するクラス間に“全体－部分”というような関係を持ったものを

集約関係にあるという。集約関係は含む側のクラスに菱形記号をつける。菱形には塗りつぶした

ものと白ぬきの２種類がある。黒塗りの菱形は“コンポジション”、または“複合”や“合成”などと呼ばれ、より結びつきが

強く、部分が全体に完全に含まれるような強い集約関係を示すものである。

《例》集約

《例》コンポジション

３．代表的な空間データの応用スキーマの記述例

単一のクラスで構成出来る空間データの例ａ）基準点

（１）概要説明

湖池

湖池貯水池

橋梁

橋脚橋桁

工場

敷地建物

橋梁という地物が橋脚と橋桁から構成されるものとす

る。もしも、橋梁自体が無くなる（撤去）ような場合、

全体の部分である橋脚、橋桁は全体である橋梁が無くな

れば、当然存在しえない。

このような関係のとき、コンポジションが使われる。

工場という地物が建物と敷地から構成されるも

のとする。工場としての存在が無くなる（移転や

倒産）ような場合、全体である工場が無くなって

も、部分である建物は独立して存在できる（例え

ば、ビール工場跡をレストランとして再利用）。

このような関係のとき、集約が使われる。

水域として湖池を定義した場合、湖池のなかには

分類上、湖も池も貯水池も含まれる。湖池として

の基本的な属性は共通としたいが、それぞれ独自

の属性も持たせたいといった場合、汎化の関係を

使えば、それらの関係が表現できる。


基準点測量成果の管理

測量法に基づき測量された、三角点、基準点の座標値、標高をデータ交換可能な空間データとし

て管理する。

（２）地図イメージ

作成する空間データセットの地図イメージを下図に示す。（●が三角点、基準点を示す）地図イメ

ージで示す背景の地形図は含まれない。

（３）地物定義

本例の空間データセットは、基準点データだけとする。背景となる地形図や写真図は空間データ

セットに含まないことを前提とする。この場合の地物クラスは、基準点データしかないため応用ス

キーマは基準点データのクラスのみとなる。次ページにその応用スキーマの定義を記載する。


【基準点地物の定義】種別名称多重度データ型定義

地物名称 Kijyunten （基準点）

－三角点、基準点の座標値・標高を示す

地物名空間属性点１ GM_Point 三角点、基準点座標値主題属性 Shubetu

（基準点種別）１ KijyunShubetu 三角点、基準点の種別名称

主題属性 Hyoko （標高値）

１ Real 標高値

主題属性 Name （基準点名称）

１ CharacterString 三角点、基準点の名称

主題属性 SokuryouDate （測量年月日）

１ Date 実測した年月日

主題属性 ShutokuDate （取得年月日）

１ Date 承認された年月日

時間属性 Period １ TM_Period

（４）UMLクラス図

基準点空間データ構造をUMLクラス図で表現すると以下の図となる。空間スキーマの表現の仕方

によって異なる表記方法があるため、２つの例を記載する。

① 空間スキーマのパッケージ群を自分のクラス図に含めて表記する場合。


Kiyunten

＋Point : GM_Point

≪Feature≫

＋Shubetu : Kijyunshubetu

＋Hyoko : Real

＋Period : TM_Period



<<Enumeration>>

Kijyunsyubetu

１等三角点=’1’

２等三角点=’2’

３等三角点=’3’

４等三角点=’4’

１級基準点=’5’

２級基準点=’6’

３級基準点=’7’

４級基準点=’8’

基準点を地図上に表すとき、図形の形はシンボルを用いる場合が多いと考えられる。このときの位

置はシンボルの中心１点で表現出来る。空間スキーマでは、点を示すGM_Pointがこれに当たるため

空間属性とした。主題属性のうち、基準点種別をユーザー定義型とし種別名称をコードで入力する

こととする。


② 空間スキーマのパッケージ群を自分のクラス図の外に表記する場合

GM_Point TM_Period

Kiyunten

≪Feature≫

＋Shubetu : Kijyunshubetu

＋Hyoko : Real




<<Enumeration>>

Kijyunsyubetu

１等三角点=’1’

２等三角点=’2’

３等三角点=’3’

４等三角点=’4’

１級基準点=’5’

２級基準点=’6’

３級基準点=’7’

４級基準点=’8’

この例では空間スキーマのパッケージ群を外に出したため、地物（Feature）基準点が空間スキーマ

GM_Point、時間スキーマTM_Periodから構成されていること、つまりGM_Point、TM_Periodは

Kijyunten（地物）の部分であることを示している。これを合成という。合成の場合、Kijyuntenが消

えるとGM_Point、TM_Periodも同時に消滅する。

クラス間の関連には、合成以外に集約がある。集約は合成と同じように全体と部分の関係を示す

が、合成のように全体が消えても部分のクラスは消滅しない。

地理情報標準では列挙データ型のクラスのステレオタイプが定義されている。このステレオタイプ

を使用して表記した例を示す。


２～３種類のクラスでクラス間の関連を使用する空間データの例

ｂ）区域界


都市計画業務データの管理

都市計画業務を行う場合、その管理データとして都市計画区域、地域地区、都市施設、市街地開

発事業などがある。都市計画決定および都市計画関連の分類から、都市計画区域、都市施設、災害

防止のデータ等を交換可能な空間データとする。

（２）地図イメージ

作成する空間データの地図イメージを下図に示す。背景図は含まない、都市計画区域、都市施設、

災害防止の区域データを空間データとして取得する。


本例の空間データセットは、都市計画区域、災害防止の災害危険区域を空間データとして取得す

る。

【都市計画分類地物の定義】種別名称多重度データ型定義

地物名称 ToshikeikakuBunrui

（都市計画分類）

－都市計画を示す地物名

空間属性面 GM_Suface 領域の面

主題属性 BunyaName

（分野名）

１ EnumBname 分類レベル名

主題属性 Bname

（分類地物名）

０..＊ CharacterString 地物の名称

主題属性 city_code

（市区町村ｺｰﾄﾞ）

１ CharacterString 全国地方公共団体コード


【都市計画区域地物の定義】


種別名称多重度データ型定義

地物名称 Toshikeikakukettei

（都市計画区域）

－都市計画区域を示す地物名

主題属性 cpa_cp_authority

（都市計画者）

１ CharacterString 都市計画法第５条で定められる者

主題属性 cpa_number

（告示番号）

１ Integer 都市計画決定を定める時に取得す

る番号

主題属性 cpa_notification_date

（告示年月日）

１ Date 都市計画法第５条第５項、省令第３

条で定められる公告があった日

主題属性 cpa_name

（区域名称）

１ CharacterString 省令第２条第１項第１号で定めら

れる都市計画区域の名称

主題属性 cpa_area

（都市計画区域内面積）

１ Real

主題属性 cpa_population

（都市計画区域内人口）

１ Integer 省令第２条第２項第３号で定めら

れる人口


【災害防止の災害危険区域地物の定義】


地物名称 Saigaikiken

（災害危険区域）

－災害危険区域を示す地物名

主題属性 dhz_name

（区域名称）

１ CharacterString 事務手続き上指定区域毎に付した名称

主題属性 dhz_number

（指定番号）

１ Integer 事務手続き上指定区域毎に付した番号

主題属性 dhz_date

（指定年月日）

１ Date 公告の年月日

主題属性 dhz_area

（区域面積）

１ Real 土地の区域の面積




①空間スキーマのパッケージ群とユーザー定義クラスを自分のクラス図の中に表記した場合

<<Feature>>

災害危険区域(Saigaikiken)

+dhz_name:CharacterString

+dhz_number:Integr

+dhz_date:Date

+dhz_area:Real

+surface:GM_Surface

+Period:TM_Period

０..＊

０..＊

<<Feature>>

都市計画区域(Toshikeikakukuiki)

+cpa_cp_authority:CharacterString

+cpa_numbe:Integer

+cpa_notification_date:Date

+cpa_name:CharacterString

+cpa_area:Real

+cpa_population:Integer

+surface:GM_Surface

+Period:TM_Period

<<Feature>>

都市計画分類(Toshikeikakubunrui)

+BunyaName:enumBname

+Bname:CharacterString

+city_code:CharacterString

+surface:GM_Surface

+Period:TM_Period

+cpa_number

+dhz_number

<<Enumeration>>

enumBname

都市計画区域=’1’

市街化調整区域=’2’

地域地区=’3’

促進区域=’4’

遊休土地転換利用促進地区=’5’

被災市街地復興推進地域=’6’

都市施設=’7’

市街地開発事業=’8’

市街地開発事業等予定区域=’9’

地区計画等=’10’

この例は、都市計画分類という面の図形を、より具体的な場所として表したい場合、都市計画区

域、災害危険区域という地物との間の関係を白抜きの三角形と実線で定義する継承関係で表す。

また、クラスの多重度は０．．＊で０個から無限大までのインスタンス定義可能としている。多重

度の右に記載しているのはロール名と呼ばれる定義で、関連先クラスとのより厳密な役割を表す。

クラス間の関係は、前項の基準点の例にあった、合成、集約と継承との違いは、合成、集約は全

体－部分の関係で、継承は親クラスをより具体化したクラスという関係である。すなわち、都市

計画分類というクラスの面図形は、都市計画区域としての属性、災害危険区域としての属性を各々

クラスとすることで表現することが出来る。


クラス関連に位相構造を持つ空間データの例

ｃ）管渠とマンホール


下水道施設の管理

地方自治体で社会資本整備の一環として下水道施設をGISシステムで管理している。このデータ

の一部をデータ交換可能な空間データにする。管理しているデータの内、汚水施設の管渠、マンホ

ールを空間データとする。

アプリケーション機能

・上流・下流検索、追跡

・施設保守位置確認

・施設状況管理

（２）地図イメージ作成する空間データセットの地図イメージを下図に示す。背景の地形図はデータセットに含まれな

い。地図イメージ上に表示されている数値は、各設備の個別管理情報であり、このデータは空間デ

ータセットのインスタンスとして表現される。

マ

ン

ホ

ー

ル

枡

取付管

管渠


本例の空間データセットは、管渠、マンホール、取付管データの３種類のみとする。但し、アプ

リケーション機能に上流・下流検索とあるため、管渠のネットワークが必要となる。また、管渠に

は取付管が接続しているのでこの接続関係を示すため、空間スキーマの位相要素を定義する。各設

備の状況を把握するため時間スキーマを定義しその設備が使用可能かを判断する情報とする。各設

備の個別管理情報をインスタンス化し施設管理を可能とする。以下に地物クラスの定義を記載する。【管渠地物の定義】


地物名称 Kankyo －管渠を示す地物名


（管渠）

空間属性有向線１ GM_OrientableCurve 管渠

空間属性位相要素１ TP_Edge マンホールと接続する位相要素

主題属性 Kubun

（処理区分）

１ enumKubun 処理区分（第一処理区第一分区）

主題属性 KankyoNo

（管渠番号）

１ Integer 管渠管理番号

主題属性 Kankyochou

（管渠延長）

１ Real 管渠延長（39.13m）

主題属性 SekouNen

（施工年度）

0..1 CharacterString 施工年度（平成 06年度）


【マンホール地物の定義】


地物名称 ManHole

（マンホール）

－マンホール

空間属性点１ GM_Point マンホール

空間属性位相要素１ TP_Node 管渠と接続する位相要素

主題属性 Kubun

（処理区分）

１ enumKubun 処理区分（第一処理区第一分区）

主題属性 HoleNO

（ﾏﾝﾎｰﾙ番号）

１ Integer マンホール管理番号

主題属性 SekouNen

（施工年度）

0..1 CharacterString 施工年度（平成 06年度）




１ +edge

+node

+boundary ２

<<Enumeration>>

enumKubun

第一処理区第一分区=’1’

第一処理区第二分区=’2’

第一処理区第三分区=’3’

第二処理区第一分区=’4’

第二処理区第二分区=’5’

第三処理区第一分区=’6’

第三処理区第二分区=’7’

第三処理区第三分区=’8’

第三処理区第四分区=’9’

<<feature>>

管渠(Kankyo)

+Kubun:eumKubun

+KankyoNo:Integer

+Kanrochou:Real

+SekouNen[0..1]:CharacterString

+curve:GM_OrientableCurve

+Period:TM_Period

<<feature>>

マンホール(ManHole)

+Kubun:eumKubun

+HoleNo:Integer

+SekouNen[0..1]:CharacterString

+point:GM_Point

+Period:TM_Period

TP_Edge

TP_Node

１

上図は下水道施設管理の一例をクラス図で示している。管渠とマンホールの関係は、幾何的に線と

点に分かれている。これを、連続した物として捉える考え方に位相構造というのがあり地理情報標

準にもパッケージとして用意されている。この位相パッケージを使用して、管渠とマンホールを連

続した物として管理し、主題属性のインスタンスにより上流、下流の判断が可能になる。この例で

は、幾何属性が線である管渠に対して線の位相TP_Edgeを使用し、点のマンホールは、TP_Nodeを

使用する。また、位相属性のTP_EdgeとTP_NodeはTP_NodeからTP_Edgeに向けて関連を定義する。

ロールはTP_Edge側に境界を意味するBoundaryを記載する。


3. Overview of XML (Necessity and Effects) 3.1 What is the Extensible Markup Language (XML)?

World Wide Web Consortium（W3C）の SGMLワーキンググループが仕様を策定したマーク

アップ言語である。1982年に XML1.0が勧告されている。データをタグセットで挟むだけで，あらゆる形式のデータを同一のプロトコルで処理できるた

め，クライアント側の機種やＯＳ，プラットフォームに関係なく，種々のデータをインターネッ

ト上で自由に交換することが可能である。 3.2 Necessity of Description in XML 空間データを幅広い用途で共通利用するためには，応用スキーマで表現された空間データ構造

から，物理形式への変換を行う際に使用する符号化規則を共通化する必要がある。地理情報標準では，汎用的な符号化規則としてXMLを用いて記述する。詳しくは，『5. 記録仕

様・符号化法』を参照ください。 3.3 Effects of Description in XML 空間データの構造を，そのデータの応用スキーマの定義に従って，個々の地物とその地物属性

を表現する事が可能である。また，位相構造や地物間関係などの情報も，応用スキーマの定義に

基づいて記述することができる。また，利用の際には，データの仕様や書式にとらわれずに，XML で記述された符号化規則に

基づいて，データを取り出して利用することが可能となる。

参考図書：「標準XML完全解説」（XML/SGMLサロン著技術評論社発行）参考URL：http://www.w3.org/XML/（XMLの技術仕様に関するW3Cのホームページ）

http://www.jp.biztalk.org/BizTalk/default.htm（XMLによる電子データ交換の標準仕

様に関するマイクロソフト社のホームページ）


Appendix C Participants

Participanting Enterprises List of Joint Research Project

Enterprise Name Aero Asahi Corporation ASIA AIR SUTVEY Co., LTD Chuoh Constructions Co., LTD Dawn corporation FUJITSU LIMITED FUKKEN Co., LTD HASSHU Co., LTD. HOKKAIDO CHIZU Co., LTD IBM Japn, Ltd Informatix Inc. INTAGE Inc. JEC Co., Ltd. JECT Co., Ltd. Kanko Co., Ltd KIMOTO Co., LTD Kokusai Kogyo Co.Ltd Michinoku Keikaku Co., Ltd Mitsui Zosen Systems Research Inc. Naigai Engineering Co., Ltd Nakanihon Air Service Co., Ltd NAKANIWA SURVEY & CONSULTANT Co., LTD. NEWJEC Inc. Nihon Computer Graphic Co., Ltd NIPPON KOEI Co., LTD Nippon Unisys, Ltd. NISSOKU Co., LTD NTT DATA CORPORATION OHBA Co.，LTD Pasco corporation Sanwacon Shobunsha Publicationｓ, Inc. SHOWA TAISEIGEOTECH Co., LTD TAMANO CONSTRUCTIONS Co., LTD Tokyo Gas Co.,Ltd Tokyo Map Research Co., LTD WESCO Inc. ZENRIN Co., LTD. （Participating Enterprises are listed in alphabetical order）


Members List of developing User’s Manual for Product Specification Description (Japanese Edition)

Member Name Organization Name Naoki GOTOU Aero Asahi Corporation Noburou ISHIYAMA Geographical Survey Institute Minoru KATOU SANWACON Co., Ltd． Akinori KIMOTO JEC Co., Ltd. Masatoshi KIMURA * Naigai Engineering Co., Ltd Toshio KITAHARA Geographical Survey Institute Mikio KUROSE WESCO Inc. Kazuo MAEJIMA NIPPON KOEI Co., LTD Manabu MAYA ASIA AIR SURVEY Co., LTD Masaaki NAKA Kanko Co., Ltd Yasuaki NONAKA Kokusai Kogyo Co. Ltd Hiroyuki OHONO Geographical Survey Institute Kenji SAITOU TAMANO CONSTRUCTIONS Co., LTD Chie TAKAHASHI INTAGE Inc. Masato TANDOU Kanko Co., Ltd Satoshi WATABE Michinoku Keikaku Co., Ltd Iwao YOKOYAMA TAISEIGEOTECH Co., LTD

* Team Leader

（Members are listed in alphabetical order, without honorific titles）

User's Manual for Spatial Data Product …User's Manual for Spatial Data Product Specification...

Documents

Transcript of User's Manual for Spatial Data Product …User's Manual for Spatial Data Product Specification...