KR100783767B1 - System for distributing geographic information - Google Patents

Abstract

A system for providing geographic information is provided to exchange and distribute the huge geographic information efficiently by distributing and utilizing the geographic information even if formats of the geographic information are different each other. An editing client(300) reads/edits the geographic information stored in a database(100) and stores the edited geographic information to the database. An operator solution(200) encodes the geographic information stored in the database according to a geographic information exchange procedure using a predetermined program and outputs the encoded geographic information to other operator solutions(400). The operator solution includes a GML(Geographic Markup Language) module(250). The GML module includes an internal schema analyzer analyzing attribute of an internal schema of the stored geographic information, a schema converter mapping the analyzed attribute of the internal schema to the attribute of a GML application schema, a GML schema definer generating the mapped internal schema as a GML application schema document, an instance separator, an encoder, and a GML document generator.

Description

Spatial Geographic Information System {SYSTEM FOR DISTRIBUTING GEOGRAPHIC INFORMATION}

1 is a view schematically showing a system for providing spatial geographic information according to the present invention.

2 is a diagram schematically illustrating a process of exchanging spatial geographic information using a spatial geographic information providing system according to the present invention.

3 is a diagram showing the internal structure of a spatial geographic information providing system according to the present invention.

4 is a diagram illustrating a management procedure of a spatial geographic information database.

5 is a diagram illustrating a management procedure of a GML shared schema.

6 illustrates an authentication procedure of an editing client.

7 is a diagram illustrating an editing procedure of spatial geographic information.

8 is a diagram illustrating a procedure for transmitting edited spatial geographic information.

9 is a diagram illustrating a procedure for receiving edited spatial geographic information.

(Explanation of symbols for the main parts of the drawing)

100: spatial geographic information database

200: Operator Solution

300: editing client

The present invention relates to a spatial geographic information providing system, and more particularly, to an information providing system capable of distributing geospatial information even under different spatial geographic information formats.

As information technology advances, the life cycle of software such as hardware, DBMS, and GIS is shortening. Therefore, spatial information should be constructed so that it can be used regardless of the type of GIS engine or spatial DBMS. However, in most cases, the overlapping investment is generated for collecting spatial information.

On the other hand, as the National Spatial Data Infrastructure (NSDI) establishment project, the amount of spatial information in Korea continues to increase, creating new added value, and a viewer who wants easy spatial information services rather than software requiring complex functions. The potential of the market is increasing. In addition, it requires the provision of remote civil services and administrative services using spatial information such as topographical maps, thematic maps, and cadastral maps. In addition, digital map producers require services of verified and refined spatial information through a clearinghouse.

However, spatial information based on distributed environment is not only huge but also very complicated, and is used in different S / W or H / W environments.

In this regard, research on interoperability of spatial information is centered on the International Organization for Standardization Technical Committee (ISO / TC 211), OpenGIS Consortium (OGC), etc. to describe not only metadata of spatial information but also model proposal and data format. Standardization is in progress. In particular, OGC's open GIS data suggests Abstract Specification based on object technology and Implementation Specification in distributed environment such as CORBA and OLE / COM for interoperability of spatial information in heterogeneous distributed computing environment. It is a common standard specification called Geography Markup Language (GML) that can be provided to software developers.

Most of the GIS data developed so far are specialized to operate only on a specific provider's GIS engine. Therefore, a huge cost is required to change the GIS used. Therefore, it is necessary to introduce a technology that can be used regardless of the type of GIS engine or spatial DBMS, thereby enabling the construction and updating of spatial information.

The present invention aims to efficiently exchange and distribute vast spatial geographic information by presenting a desirable model and possibility that the spatial geographic information can be distributed and utilized even under different spatial geographic information formats.

In order to achieve the above object, the present invention provides a system for providing spatial geographic information in a network, comprising: a database for storing predetermined spatial geographic information; An editing client that reads and edits the spatial geographic information stored in the database and re-saves it in the database; And an operator solution which encodes and stores the spatial geographic information edited and stored by the editing client according to a spatial geographic information exchange procedure according to a predetermined protocol and outputs the same through a network.

In addition, the protocol is assumed to be ISO-19118 and GML 3.0.

The operator solution may include an internal schema analyzer configured to analyze an attribute of an internal schema of the spatial geographic information stored in the database, and a schema converter configured to map an attribute of the analyzed internal schema to an attribute of the application schema. And an GML schema definition unit that defines the mapped internal schema as a GML application schema document, and an instance separation unit that separates the read spatial geographic information for each instance based on an internal schema analyzed by the internal schema analysis unit. And an encoding unit for encoding the separated instances into a data type of the GML application schema based on the mapped internal schema, and a data structure type of the GML application schema based on the GML application schema document. Build a GML document generator to convert a GML document with Comparing GML module; is made.

The operator solution may output the edited spatial geographic information to another operator solution through the network at regular intervals immediately after the reception from the editing client ends or at a predetermined time after the termination of the reception. It further comprises a production data provider module for performing a user authentication to allow access to the database for a client.

In addition, the editing client includes: an authentication module for maintaining authentication information about a user who uses the editing client; A change data management module for storing the edited spatial geographic information generated by the user's editing in its own storage means; And a network module in communication with the database and the operator solution, and transmits the edited spatial geographic information to the operator solution as the editing ends, and if the transmission is not successful, the edited spatial geography. Temporarily storing the information in the change data management module, characterized in that the retransmission is attempted every predetermined period.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

1. Defining spatial geographic information exchange system

The present invention aims to obtain desired information from vast spatial geographic information by presenting a desirable model and possibility of distributing and utilizing spatial geographic information in different formats. It fully reflects the GML standard specification so that it can fully accommodate the advantages of both standards. In addition, the present invention enables to provide and exchange spatial geospatial information in various formats because the geospatial information and the schema defining the format are managed separately.

2. Structure of Spatial Geographic Information System

2.1 Business Architecture

2.1.1 Overall System Structure

The spatial geographic information providing system is largely divided into an operator solution 200, an editing client 300, and a spatial geographic information database 100 as shown in FIGS. 1 and 3.

When the spatial geographic information is edited by the editing client 300, the operator solution 200 receives the information indicating the editing or the entire edited data, and shares it with other linked operator solutions 400. Meanwhile, information about sharing and operation is stored and managed in the operation database 220. When the editing client 300 edits the spatial geographic information of the spatial geographic information database 100 to which it belongs, the editing information (information of the changed part and the changed contents of the edited part in the spatial geographic information) or editing thereof is edited. It serves to transmit the entire data of the spatial geographic information to the operator solution 200.

Looking at these in detail using the functional aspects are as follows.

First, look at the role of the operator solution (200).

A. Edit Client Management

Registering the editing client 300 or the user of the editing client (editing user).

-Individually grants access rights to the spatial geographic information database 100 within the spatial geographic information providing system for each editing user.

B. Managing Access Information in Spatial Geographic Information Databases

Register and manage access information for the spatial geographic information database 100 accessible by the operator solution 200.

C. Management of other spatial geographic information provision system

Maintain a request for registration of spatial geospatial information databases and exchange of geospatial information within another geospatial information providing system (or operator solution 400 of the other geospatial information providing system) to be associated.

-Management of the list of internal shared schemas (shared schemas) per associated operator solution 400.

Request and register a list of external shared schemas (application schema or GML application schema) by associated operator solution 400.

D. Shared Schema Management

Create a shared schema from the internal spatial geographic information database 100.

Storing all or part of the spatial geographic information maintained by the internal spatial geographic information database 100.

E. Application Schema Management.

-If the data of some of the application schemas of the data shared in other spatial geographic information provision system is another type of application schema, create and manage a separate application schema for this.

-The application schema can store some or all of the internal shared schema information of other spatial geographic information provision system.

F. Editing Information Management by Editing Client

When the editing client 300 edits and modifies the spatial geographic information of the internal spatial geographic information database 100, the edited data and the editing information are collected.

G. Spatial Geographic Information Exchange Management

The edited data collected from the editing client 300 is transmitted to another spatial geographic information providing system linked through a network.

When data is received from another spatial geographic information providing system, the received data is stored in the internal spatial geographic information database 100.

H. Request Large Geospatial Geographic Information

-In addition to the edited data, you can request the entire data of the spatial geographic information database of the other spatial geographic information providing system linked to it, and the requested other spatial geographic information providing system creates and transmits a shape file for the entire data.

I. History Management

-History management for data sharing and creation and modification of application schemas.

-History management for sending and receiving requests for large spatial geographic information.

Next, the role of the editing client 300 will be described.

A. Internal Spatial Geographic Information Database (100) Connection Management

-After authentication of the editing user through the operator solution 200, a list of accessible spatial geographic information databases is provided and maintained.

Access any one of the databases 100 in the list of accessible spatial geographic information databases.

B. Editing Information Management

-Edit If the user has completed or canceled editing the spatial geographic information, maintain what they have done.

C. Send edit information

After editing is completed, the edited data is provided to the operator solution 200.

In case the data transmission to the operator solution 200 is interrupted and the edited data is not completely delivered, the edited data is temporarily stored in a predetermined storage means and then retransmitted for a predetermined period, and the transmission is successful. Delete temporary saved information.

When the editing client 300 is executed or terminated, if there is a state in which the temporarily stored edited data exists in the editing client 300, the temporary stored data is provided to the operator solution 200 immediately or at predetermined intervals.

2.1.2 Block System Structure

The spatial geographic information providing system is composed of an interworking of the editing client 300, the spatial geographic information database 100, and the operator solution 200. In addition, the flow order of the data to be shared, starting from the editing client 300, and collecting and generating detailed edit information by linking the operator solution 200 and the spatial geographic information database 100, and associated with the edit information The process is terminated by completing the transfer to another operator solution 400.

2.1.3 Spatial Geographic Information Exchange Procedure

A process for exchanging spatial geographic information through a spatial geographic information providing system for sharing spatial geographic information using a protocol including ISO-19118 and GML of OGC may be expressed as shown in FIG. 2. This can be largely explained in five steps.

The first is to map internal shared schema and internal spatial geographic information into data that can be interpreted and used by the encoding service. Secondly, the encoding service generates GML document data based on the GML shared schema (application schema). The third is the process of transmitting the encoded GML data to another system through the network for distribution and distribution. The fourth step is to reverse the second step to map the data sent from other systems to the internal schema. That is, the received GML data is decoded based on the GML application schema. The last step is to map and transform the decoded GML data from another system into an internal database by an internal schema.

2.2 Software Architecture

2.2.1 Key Modules and Data Flow in Spatial Geographic Information System

The data flow between the operator solution 200 and the editing client 300 can be understood with reference to FIG. 3. The editing client 300 obtains access information to the spatial geographic information database 100 from the application web service module 240 (a module providing various services through SOAP in the operator solution) of the operator solution through the authentication module 330. Afterwards, the spatial geographic information is edited as necessary, and the edited information and the edited data accumulated in the change data management module are transferred to the operator solution 200. The operator solution 200 performs a data exchange procedure for distributing and sharing spatial geographic information with other systems through the application web service module 240.

There are five core components of the operator solution 200 which performs such a role, including the GIS data provider module 230, the GML module 250, the application web service module 240, the operational data provider module 220, Network module 260.

First, the GIS data provider module 230 provides meta information about a GIS (spatial geographic information) data source, enables anyone to develop using standard specifications for the implementation of common GIS data, and It is developed to allow access to all commercial and emergency GIS data through defined interfaces.

Second, the GML module 250 manages GML schema to share data among heterogeneous spatial geographic information systems, performs encoding function of spatial geographic information, and converts the received GML data into internal spatial geographic information of an internal shared schema. This module is responsible for converting or reversing.

Third, the application web service module 240 performs a process corresponding to a request of a specific function in the editing client 300 or the associated operator solution 400, and provides a service for outputting a result of the execution.

Fourth, the operation data provider module 220 is stored in the operation database 220 that stores the setting information for the operator solution 200 of the operator and internal management information for the operator solution 200 to perform a predefined function. It accesses and edits the information or mediates the application web service module to perform the functions requested by the server administrator.

Fifth, the network module 260 is in charge of SOAP and HTTP file transfer services to perform data transmission and reception with the editing client 300 or another operator solution 400.

2.2.2 GIS Data Provider Module and GML Module

The GIS data provider module 230 and the GML module 250 have different internal processing methods, but the user interface is similar in that the standard interface specifications are the same. In other words, by defining a standard interface for accessing data, it is designed to be extended to all formats dealing with GIS data in the future, thereby providing convenience of system analysis and development.

The role of the GIS data provider module 230 in the spatial geographic information providing system maintains and outputs information on the input and output of the spatial geographic information and the internal shared schema to and from the spatial geographic information database 100, and outputs them as necessary. It provides basic data for generating GML document data and application schema for the distribution of information, and serves to input data encoded in the GML module 250 to an internal database.

As shown in FIG. 3, the GML module 250 has various configurations, and the functions performed by the components and the data flow thereof are as follows.

First, the GML schema generation function analyzes the definition of the property of the internal schema in the internal schema analyzer based on the internal schema information received from the GIS data provider module 230 and transmits the definition to the schema converter 252. The schema conversion unit 252 performs an attribute type conversion operation by mapping an internal schema attribute to an attribute type of the GML schema, and generates a GML schema standard document of OGC in the GML schema definition unit 253 with the converted attribute type.

Second, the flow of the GML document data generation function receives the internal spatial geographic information from the GIS data provider module 230 to the instant separation unit 255 of the GML module 250 and verifies the data by comparing with the internal schema. The verified data is transmitted to the encoder 256 (instance converter). The encoding unit 256 encodes spatial geographic information in the form of GML data, and converts the encoded data into a data structure format of the GML document through the GML generation module 257 to generate GML document data.

2.3. Sequence diagram by function

Data for information exchange converts the information maintained in the spatial geographic information database 100 into the GML data format to perform transmission and reception as GML document data, and to separate the modified record information between other systems. Configure the ID. When editing is performed in a specific spatial geographic information providing system or requests a large amount of data from a shared spatial geographic information database from another linked spatial geographic information providing system, it is transmitted and received in the shape file format of ArcGIS. Hereinafter, the flow of the spatial geographic information exchange procedure by the spatial geographic information providing system will be described.

2.3.1 Managing the Geospatial Information Database

The operator adds, deletes, and modifies access information that allows the editing users to access the spatial geographic information database 100 by accessing the administrator screen of the operator solution 200 through a web browser. This is referred to FIG. 4.

First, the server administrator who manages the operator solution 200 starts the application web service module 240 of the operator solution 200 and lists the spatial geographic information database 100 linked to the operator solution 200. Request (S21). The application web service module 240 accesses the operation database 220, obtains a list of the spatial geographic information database 100 that can be connected and connected to the operation database 220, and outputs the list. After checking the list, the server administrator may select and modify the access information as necessary (S23), and the modified information is stored in the operation database 220 (S24). Thereafter, when the spatial geographic information database 100 to be linked is added by the server manager, the access information is updated through the above-described process and stored in the operation database 220 (S25 and S26).

2.3.2 Shared Schema Management

In order to create a shared schema to be used for exchanging spatial geographic information, the administrator for the operator solution 200 accesses the application web service module 240 administrator screen, selects and accesses a spatial geographic information database for creating an internal shared schema, and then Retrieve schema information. All or part of the fields (attributes) to be shared in this schema are designated and stored in the form of a schema file in GML format, and managed to transmit GML shared schema information when requested by another operator solution 400 linked thereto. This is referred to FIG. 5.

When the server manager requests a connection list using the application web service module 240 to select the spatial geographic information database 100 to which the server manager wants to connect (S31), the application web service module 240 sends a request to the operation database 220. Access information about the spatial geographic information database 100 that is accessible and accessible is obtained and output to the server administrator (S33). The server manager selects the spatial geographic information database 100 to be connected and requests information related to the shared schema used by the spatial geographic information database 100 (S33). The application web service module 240 provides the GIS data provider module 230 with access information on the selected spatial geographic information database 100 to access the selected spatial geographic information database 100 (S34). The GIS data provider module 230 retrieves and maintains shared schema information of the spatial geographic information database 100 corresponding to the access information (S35). Thereafter, the application web service module 240 reads the shared schema information maintained by the GIS data provider module 230, and outputs the shared schema information to be checked by the server administrator (S36), and the server administrator selects the required shared schema ( S37). When the selection of the server manager is completed, the application web service module 240 provides schema information on the selected shared schema to the GML module 250 (S38) and simultaneously stores the information on the operation database 220 (S38 '). The GML module 250 converts the provided application schema information into a GML format and stores it in a predetermined storage (S39).

2.3.3 Edit User Authentication

The editing user accesses the application web service module 240 through a dedicated editing client 300 of the spatial geographic information providing system, receives user authentication, and accesses the spatial geographic information database information and session information serving as a service authentication code. You get it. This is referred to FIG. 6.

In order to use the editing client 300, an editing user who wants to edit spatial geographic information inputs user information such as his ID and password into the editing client 300 (S41). The editing client 300 provides the input user information to the application web service module 240 of the operator solution 200 (S42), and the application web service module 240 accesses the operation database 220 to the editing user. The authority to check and authenticate (S43, S44). If the editing user is authenticated, the authentication session and the authorization list are provided to the editing client 300 (S45), and the editing user then accesses the spatial geographic information database 100 using the authenticated access authority, Editing such as modification, change, etc. of the geographical information can be performed (S47).

2.3.4 Collect Editing Information

The editing user edits the spatial geographic information in the spatial geographic information database 100 connected through the procedure as shown in FIG. 6, and the edited data is collected by the editing client 300 and transmitted to the application web service module 240. do. The application web service module 240 which receives this is connected to the spatial geographic information database 100 to perform validation of the edited information, converts the spatial geographic information into GML document data, and transmits it to the other operator solution 400 linked thereto. do. The transfer to the associated other operator solution 400 is performed by a real-time setting and schedule cycle (monthly, weekly, daily, hourly, minute) in which the operator solution manager performs the exchange of spatial geographic information as soon as editing information is received. Non-real time setting can be selected. This is referred to FIG. 7.

The editing user who accesses the spatial geographic information database 100 stores the edited information in the change data management module 320 when the spatial geographic information is edited (S51 and S52). After editing by the editing user is terminated (S53), the spatial geographic information that is edited and stored in the change data management module 320 is provided to the application web service module 240 (S54). In this case, when the editing client 300 is provided with some or all of the spatial geographic information to be edited among the spatial geographic information of the spatial geographic information database 100, and all the editing is completed in the editing client 300 itself, information related to the change ( Or, it is assumed that the edited space geographic information as a whole is stored in the spatial geographic information database 100 through the application web service module 240. Meanwhile, the application web service module 240 provided with the edited information by the editing client 300 provides the information to the GIS data provider module 230 (S55), and the GIS data provider module 230 is a space. The geographic information database 100 is accessed to store the edited information (S56). Meanwhile, the application web service module 240 provides the edited spatial geographic information to the GML module 250 (S57), so that the edited data can be converted into the GML format, and the converted data is stored in a predetermined storage. It is stored and maintained (S58). In addition, the edited data or the information related to the edit, the edited data or the information related to the edit converted into the GML format are stored in the operation database 220 (S59).

2.3.5 Send Editing Information

The operator solution 200 transmits the edited information as GML data to another spatial geographic information providing system to be linked according to the setting of the spatial geographic information exchange cycle (real time or non real time). This is referred to FIG. 8.

In other words, assuming that operator solution A and operator solution B are connected to each other through a network such as the Internet, the application web service module of operator solution A may retrieve an edit list that is maintained in the operator database of operator solution A, and may be processed ( If data (not shared) is found (S61), the GML document data for the unprocessed data is read and transmitted to the application web service module of the operator solution B (S62, S63). In this case, the transmission may be performed at the time when editing of the spatial geographic information is terminated in the editing client 300, or may be performed according to a time defined by an editing user or a server administrator, and may be performed by another operator solution 400. May be performed at the time the request for access from the server occurs.

2.3.6 Receive Editing Information

The received GML document data is converted into a data format of an internal shared schema used in the spatial geographic information database 100 of the received operator solution 200 and stored. This is referred to FIG. 9.

When the GML document data including the data edited in the application web service module A is transmitted and received by the application web service module B (S71), the application web service module B first stores the data in a predetermined file storage and an operation database. At the same time (S72, S73), the GML module is used to convert the data to the format (internal shared schema) used in the spatial geographic information database of the operator solution B (S74). The converted data is stored in the spatial geographic information database through the GIS data provider module (S75 and S76). In addition, it stores to the operation database for the performance of these operations (S77).

2.3.7 Internal Shared Schema and GML Schema Examples for Spatial Geographic Information Databases

When the internal shared schema of the spatial geographic information database 100 is as shown in the table below, the conversion to the GML schema (application schema) is shown below.

Field name LENGTH RN_RNM RN_RNO RN_CRT Geometry type DOUBLE STRING LONG DATETIME MultiLineString

<? xml version = "1.0" encoding = "ksc5601"?>

<xs: schema targetNamespace = "http://www.sundosoft.com/des"

xmlns: des = "http://www.sundosoft.com/des"

xmlns: xs = "http://www.w3.org/2001/XMLSchema"

xmlns: gml = "http://www.opengis.net/gml"

elementFormDefault = "qualified" attributeFormDefault = "unqualified">

<xs: import namespace = "http://www.opengis.net/gml"

schemaLocation = ". \ common_profile.xsd" />

<xs: element name = "bc_roads" substitutionGroup = "gml: _Feature">

<xs: complexType>

<xs: complexContent>

<xs: extension base = "des: bc_roads_Type" />

</ xs: complexContent>

</ xs: complexType>

</ xs: element>

<xs: complexType name = "bc_roads_Type">

<xs: annotation>

<xs: documentation> SpatialReference </ xs: documentation>

</ xs: annotation>

<xs: complexContent>

<xs: extension base = "gml: AbstractFeatureType">

<xs: sequence>

<xs: element ref = "des: LENGTH" minOccurs = "0" nillable = "true" />

<xs: element ref = "des: RN_RNM" minOccurs = "0" nillable = "true" />

<xs: element ref = "des: RN_RNO" minOccurs = "0" nillable = "true" />

<xs: element ref = "des: RN_CRT" minOccurs = "0" nillable = "true" />

<xs: element ref = "gml: MultiLineString" minOccurs = "0" />

</ xs: sequence>

</ xs: extension>

</ xs: complexContent>

</ xs: complexType>

<xs: element name = "LENGTH" type = "xs: double">

<xs: annotation>

<xs: documentation> Length </ xs: documentation>

</ xs: annotation>

</ xs: element>

<xs: element name = "RN_RNM" type = "xs: string">

<xs: annotation>

<xs: documentation> Road name </ xs: documentation>

</ xs: annotation>

</ xs: element>

<xs: element name = "RN_RNO" type = "xs: long">

<xs: annotation>

<xs: documentation> Road Number </ xs: documentation>

</ xs: annotation>

</ xs: element>

<xs: element name = "RN_CRT" type = "xs: dateTime">

<xs: annotation>

<xs: documentation> Completion date </ xs: documentation>

</ xs: annotation>

</ xs: element>

</ xs: schema>

The GML schema will have internal shared schema information of the spatial geographic information database 100 and alternative field names for each additional field (attribute), so that when linked with another system, the field name of the spatial geographic information database of the spatial geographic information providing system Although different, the content data can be easily applied if they are the same.

2.3.8 Examples of GML Data

One record for the GML schema example may be expressed as the following in the GML data format.

<? xml version = "1.0" encoding = "EUC-KR"?>

<FeatureCollection xmlns = "http://www.sundosoft.com/des"

xmlns: gml = "http://www.opengis.net/gml"

xmlns: des = "http://www.sundosoft.com/des"

xmlns: xlink = "http://www.w3.org/1999/xlink"

xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance"

xsi: schemaLocation = "http://www.sundosoft.com/des C: \ roads.xsd">

<gml: featureMember>

<des: bc_roads id = "roads_01" updateFlag = "create">

<des: LENGTH> 2163.48 </ des: LENGTH>

<des: RN_RNM> No1 Road </ des: RN_RNM>

<des: RN_RNO> 1 </ des: RN_RNO>

<des: RN_CRT> 2007-01-24 15:51:00 </ des: RN_CRT>

<gml: MultiLineString>

<gml: lineStringMember>

<gml: LineString>

<gml: coordinates> 494475.711,5433016.819 494982.701,5435041.951 </ gml: coordinates>

</ gml: LineString>

</ gml: lineStringMember>

</ gml: MultiLineString>

</ des: bc_roads>

</ gml: featureMember>

</ FeatureCollection>

According to the present invention having the above-described configuration, it is possible to distribute and utilize spatial geographic information even under different spatial geographic information formats, thereby efficiently exchanging and distributing vast spatial geographic information. In addition, since the present invention manages the spatial geographic information and the schema separately, it is possible to process various geospatial information formats.

Claims (7)

A system for providing spatial geographic information in a network, A database for storing predetermined spatial geographic information; An editing client that reads and edits spatial geographic information stored in the database and re-saves it in the database; And And an operator solution that encodes and stores the spatial geographic information edited and edited by the editing client according to a spatial geographic information exchange procedure using a predetermined protocol, and outputs it to the other operator solution through a network. The operator solution, An internal schema analyzer for analyzing an attribute of an internal schema of spatial geographic information edited and stored in the database, a schema converter for mapping an attribute of the analyzed internal schema to an attribute of a GML application schema, and the mapped internal schema A GML schema definition unit that defines a GML application schema document, An instance separator that separates the edited and stored spatial geographic information for each instance based on an internal schema analyzed by the internal schema analyzer, and based on an internal schema mapped by the schema converter An GML encoding unit encoding the data format of the GML application schema and the encoded instances into a GML document having a data structure type of the GML application schema based on the GML application schema document defined by the GML schema definition unit. Spatial geographic information providing system comprising a GML module having a document generation unit. The method of claim 1, The protocol is a spatial geographic information providing system, characterized in that ISO-19118 and GML 3.0. delete The method of claim 2, The operator solution outputs the edited and stored spatial geographic information to another operator solution through the network at regular intervals immediately after the reception from the editing client ends or at a predetermined time after the termination of the reception. Spatial geographic information provision system. The method of claim 2, The operator solution further comprises an operational data provider module for performing user authentication to allow the editing client access to the database. The method of claim 5, The editing client is: An authentication module for maintaining authentication information for a user using the editing client; A change data management module for storing the spatial geographic information edited by the user in its own storage means; And And a network module in communication with the database and the operator solution. The method of claim 6, The editing client transmits the spatial geographic information edited by the user to the operator solution as the editing ends, and temporarily stores the spatial geographic information edited by the user in the change data management module when the transmission is not successful. Spatial geographic information providing system characterized in that for attempting to retransmission after a predetermined period.

Images