JP2010182215A - Time series map data management system, terminal device, time series map data management method, and time series map data management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a means which shortens the time required for map display and map updating operations and visually distinguishes and recognizes facilities existing at present and facilities not existing, out of facilities displayed on a map. <P>SOLUTION: When an input part 18 of a terminal device 11 accepts a request for map display at an appointed date, a display control part 17 selects map data for displaying facilities available at the appointed date, out of map data on the basis of attribute data acquired by a DB management part 14 and distinguishes between facilities available at an acceptance date of the request for map display and facilities not available then and displays them respectively using first and second display forms. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a map data management system, a terminal device, a time-series map data management method, and a time-series map data management program, and more specifically to a technique for managing facility data on a map in time series.

  Map data is used for various purposes such as displaying maps and managing location information of facilities related to maps. Depending on the application, such as grasping map information that changes day by day, it may be required to provide a map at a certain point in the past as well as information at the present time.

  For time-series map data management, the generation of map data at regular intervals, such as every fiscal year, and a method of providing a map of a specified generation, and the time when the map database indicates when the geography fits. A technique for adding information has been proposed (Patent Document 1).

  For example, Patent Document 1 discloses a technology that enables a map corresponding to a time designated by a user to be displayed by attaching data such as generation time and disappearance time to each object representing a feature. Yes.

  In addition, a technology has been proposed in which a vehicle navigation apparatus selects facilities and sightseeing spot information based on the appearance corresponding to a designated date and time, and draws and displays the figure on a map (Patent Document 2).

Japanese Patent Laid-Open No. 11-312233 Japanese Patent Laid-Open No. 9-251266

When using maps such as managing equipment floor plan, it is possible to provide not only the current and past but also future maps, and visually understand the extent of equipment shortage on the map. It is a useful tool for improvement.
In the conventional technology for managing the generation of map data, there is a problem that the resources for data retention double every update time, and only map data for a very limited period can be retained depending on system limitations.

Further, in an environment where map data is distributed to clients via a network, a large load of map data generally flows through the network, which increases the network load. In patent document 1, the time-sequential change of map data is hold | maintained as difference data, and the difference map data is communicated via a network for every map data search. Furthermore, when reading the map, it is necessary to reflect the difference data for each feature on the original map data, and when registering the map, the difference from the original map data is extracted for each feature. Processing and management processing are required. Also in Patent Document 2, every time the map display is updated, an aspect (graphic data) reading process corresponding to a specified date is performed.
Therefore, when Patent Document 1 and Patent Document 2 are applied to a map data distribution environment via a network, the load on the network increases due to transmission / reception of difference data and graphic data to be drawn, and time is required for map display and map update operations. There is a problem of requiring.

  In addition, when managing equipment status that changes in time series, it is useful to be able to recognize equipment that exists on the specified date but does not currently exist. In particular, when displaying a map of the future and managing the floor plan of the equipment, it is desirable to visually distinguish the equipment that currently exists and the equipment that is planned to be installed in the future.

  In order to solve at least one of the above-mentioned problems, the present invention is a time-series map data management system for time-series managing facility data on a map, and includes map data used for displaying facilities on a map, and A database for storing attribute data including a start date and an end date of use of the equipment; a display unit for displaying a map; an input unit for receiving a map display request; and map data and attribute data via a network A map management unit that includes a database management unit that obtains data from a database and a display control unit that performs processing for displaying map data based on attribute data and outputs the map data to the display unit. When the request is received, the display control unit specifies the specified map data based on the attribute data acquired by the database management unit. The map data for displaying the equipment used on the date of selection is selected, and the equipment used on the day the map display request is received is distinguished from the equipment that is not used. The display processing is performed using the above display format.

  The terminal device includes an input unit for inputting a date specification and a display unit for displaying a map and facility information. The display unit inputs a specified date and a date specification input from the input unit. The map and the facility information based on the specified date are displayed together with the specified date and the specified date together with the input date.

  In addition, the problems disclosed by the present invention and the solutions thereof will be clarified by the column of the best mode for carrying out the invention and the drawings.

  According to the present invention, the time required for map display and map update operation can be shortened. In addition, among the facilities displayed on the map, it is possible to visually distinguish and recognize currently existing facilities and non-existing facilities.

  Hereinafter, embodiments will be described with reference to the drawings.

  FIG. 1 is a conceptual diagram of a map management system.

  The map management system 1 includes a map display unit 2, a map date 3, a menu unit including a search 4, an edit 5, and a calendar 6.

  The map display unit 2 displays a map of a designated place and a designated date. The map shows the background of equipment symbols such as telephone poles and cables, roads, and house frames. For example, when displaying a map of a future date, the equipment that exists as of today is displayed as a solid line, and the planned equipment that is planned to be installed in the future is a dotted line Actual results and plans are displayed separately.

  The location of the map to be displayed is specified by displaying a search menu when selecting Search 4. The search menu can be specified by address. When displaying a map of a date other than today, the calendar screen 7 is displayed when the calendar 6 is selected, and the date is selected and designated. When the date is designated, a map of the designated date of the place currently displayed on the map display unit 2 is displayed.

  When editing an equipment symbol, a menu of equipment registration, equipment deletion, and equipment change is displayed when Edit 5 is selected. The edit menu allows selection of equipment symbols, drawing on the map display unit 2, and setting of equipment attributes.

  FIG. 2 is an explanatory diagram showing a schematic configuration of the map management system 1.

  The map management system 1 includes a server device 10 and a terminal device 11. The terminal device 11 is connected to the server device 10 via a communication network such as the Internet.

  Data processed by the map management system 1 is stored in the server device 10. The server device 10 includes a map DB 12 and an equipment information DB 13. Map data used for map display is stored in the map DB 12, and equipment attribute data for equipment management, for example, the start date and end date of use of each equipment is provided in the equipment information DB 13. Stored in

  The map data in the map DB 12 includes shape data of equipment such as cables and utility poles, and is linked to attribute data in the corresponding equipment information DB 13. However, in the case where the attribute data is not necessary for the equipment symbol that is not subject to management, for example, the equipment symbol that is the background of roads, contour lines, etc., it is preferable to adopt a format that does not hold the attribute data in the equipment information DB 13.

  Further, the map data in the map DB 12 is not stored for each date or year, but all map data including the present and future are stored for only one generation. For example, a current utility pole and a utility pole scheduled to be installed one month later are managed as map data of the same format without distinction.

  By providing start date and end date data as attribute data of each facility and managing time-series information, it is possible to hold map data over the past and future without holding multiple generations of map data.

  A general-purpose computer may be employed as the server device.

  The terminal device 11 can also employ a general-purpose computer. The storage device 15 such as a hard disk drive has programs (DB management unit 14, analysis unit 16, display control unit 17), and each program is read into the memory 22 for calculation. It is executed by the CPU 23 as the apparatus. In addition, it includes an input unit 18, a display unit 19, and a communication unit 20 that handles data exchange with external devices. The terminal device 11 is connected to the intranet / Internet by the communication unit 20. The I / O unit 21 performs data buffering and various mediation processes between various functional units of the terminal device 11 and the communication unit 20.

  The DB management unit 14 adds, updates, and reads data stored in the map DB 12 and the facility information DB 13. The analysis unit 16 analyzes the operation input to the input unit 18, performs processing such as map data, and instructs the DB management unit 14 and the display control unit 17 to perform processing. The display control unit 17 outputs map data and the like to the display unit 19 in accordance with an instruction from the analysis unit 16.

  The input unit 18 is composed of a keyboard and a mouse, receives an input of a user operation, and passes it to the analysis unit 16. The display unit 19 is a display or the like, and outputs the image data received from the display control unit 17 on the screen.

  In addition, you may take the form which provides a part of functional part shown in figure via the communication network from another computer or server.

  FIG. 3A is a layer configuration diagram of map data. Map data is managed by a storage layer. The storage layer holds a plurality of layers such as a cable layer, a utility pole layer, and a house frame layer. A desired map can be displayed by arbitrarily extracting and overlaying the map data of each layer. Arbitrary layers can be added as necessary.

  FIG. 3B shows an example of a layer setting table. The attributes of each layer can be set by user designation, and the symbol line type, line color, and line width can be designated for each layer. Furthermore, each layer can be set for reference and update for each layer. Equipment layers that are not subject to management, for example, background layers such as roads and contour lines, cannot be updated by the user, replaced with the latest map data at regular intervals such as the fiscal year, and can only be referenced Is good. In addition, the equipment layer such as cables and utility poles to be managed may be updated by the user and adopt a format that can be updated sequentially.

  Map data acquired from the map DB 12 via the network is processed by the analysis unit 16 in accordance with a user-specified definition, and output to the display unit 19 by the display control unit 17.

  A set of map data in the map DB 12 constitutes a wide range of maps such as the Tohoku region. Each map data is obtained by dividing a wide range of maps into mesh units and storing them. The mesh unit is an area obtained by dividing a wide-range map into a mesh shape, and is divided into, for example, 100 [m] square areas.

  When displaying a map at an arbitrary location, map data for a plurality of meshes in the vicinity of the location, for example, 3 × 5 meshes is acquired, configured by the display control unit 17, and output to the display unit 19. By arbitrarily specifying the mesh range to be read, it is possible to display a map of a desired range.

  FIG. 4 is an explanatory diagram showing an example of the structure of map data stored in the map DB 12. On the left side of the figure, a map example of a cable layer corresponding to each map data is illustrated. The map data is stored as an object corresponding to each facility such as a cable and a power pole for each mesh. The data items for the cable located in the center mesh of the map example are as shown on the right side of the figure.

  The ID is an identifier that is uniquely assigned to each facility. Equipment that exists in a plurality of map data across the mesh is associated by this ID. Moreover, this ID links with the attribute data of equipment information DB13. The layer number and the mesh number are position information of each facility corresponding to the above-described storage layer and mesh. The serial number is an identifier uniquely assigned in the same mesh and the same layer.

  Each object includes shape data serving as map display data. The shape data in FIG. 4 is point sequence data of the vertices A, B, and C when the cable is displayed, and the coordinate values in the mesh of each of the vertices A, B, and C are stored.

  The invalid flag stores an identifier indicating whether each object is valid or invalid. An identifier indicating invalidity is stored in an object that is desired not to accept a user operation during facility editing.

The invalid flag for all objects stored in the map DB 12 stores an identifier indicating validity, but the use of each facility stored in the facility information DB 13 is used only for the map data read in the map display. A valid or invalid identifier is temporarily stored using the start date and end date of the key as keys. For example, when the date of the map requested to be displayed is December 1, 2008, the equipment whose end date is before December 1, 2008 does not exist or is not used as of December 1, 2008 Therefore, an attribute value indicating invalidity is set in the invalid flag so that a user operation is not accepted.
In the line type, line color, and line width, values set in the user-specified layer attributes shown in FIG. 3B are stored. For the map data read at the time of displaying the map, the facilities existing at the time of the date when the display is requested are displayed with the line type, line color, and line width set in the layer attribute. On the other hand, for the drawing of equipment that does not currently exist but is planned to be used at the date of display, or has been used, the display format has been changed to visually distinguish it from existing equipment. To do. Furthermore, in order to distinguish the drawing of equipment that does not exist at the date of display from the equipment that exists, both the layer attribute settings and the display format of equipment that does not currently exist but are used at the date of display Different display formats are used. For example, for the drawing of equipment that does not currently exist but is used at the date when the display is requested, the line type is changed from a solid line to a dotted line, and the equipment that does not exist at the date when the map display is requested For the drawing of, the line color is changed to be transparent so that it cannot be seen by the user. The display format such as the line type corresponding to the status of each facility is selected with reference to the setting file. Setting by the user may be possible.

  FIG. 5 is a diagram illustrating a configuration example of the facility information DB 13. The attribute data stored in the facility information DB 13 includes an ID, a mesh number, a facility name, a start date, an end date, a facility attribute, a pre-change ID, and a post-change ID. The object to be stored in the facility information DB 13 is preferably only data on facilities that require time-series management, such as cables and utility poles other than map data corresponding to the background such as contour lines and roads.

  The ID is linked to the ID of the map data shown in FIG. 4, and the same value as the map data of FIG. 4 is stored for the data indicating the same equipment. In the mesh number, the mesh number where the equipment is located is stored, and in the case of equipment existing across the mesh, a plurality of mesh numbers are stored. The name of the facility is stored in the facility name. The start date and the end date store the date when the use of the equipment starts and the date when the use ends, respectively, and are used as key data for determining the display format and valid / invalid when displaying the map. In the equipment attribute, various equipment-specific attributes are stored. A format in which a plurality of equipment attributes can be stored may be used. When there is a change in the map data, the ID of the map data before change is stored in the ID before change, and the ID of the map data after change is stored in the ID after change.

  FIG. 6 shows an equipment registration screen. When the edit 5 menu of FIG. 1 is selected, the display control unit 17 causes the display unit 19 to display the facility registration, facility change, and facility deletion menus according to the instruction of the analysis unit 16, and the map display unit 2 displays the facility symbol. Add, change or delete operations are possible. The equipment registration screen is activated by the display control unit 17 at the timing when the map data operation is completed in the equipment registration or equipment change operation in the map display unit 2 and is displayed on the display unit 19. However, if the map data is not changed in the equipment change operation and only the attribute data is changed, for example, only the start date and end date are changed due to the plan change, the equipment registration screen should be started directly by the user operation. Is also possible.

  The setting items on the equipment registration screen are composed of, for example, a name, a start date, an end date, and equipment attributes. As the start date, the date of the currently displayed map may be automatically displayed and no user operation may be accepted.

  For the other items, the set value is displayed, and if it is a new additional equipment, it is displayed blank. Regarding the end date, a date after the start date can be set.

  The input of each item can be selected from a text input from a keyboard or a pull-down menu with a mouse.

  Hereinafter, a processing flow for realizing the present embodiment will be described. Various operations described below are realized by each program that the terminal device 11 reads into the memory 22 and executes as appropriate. Each program is composed of codes for performing various operations described below.

  FIG. 7 is a flowchart showing map display processing.

  When a user's operation for selecting the calendar 6 menu is received by the input unit 18 in a state where a map at an arbitrary location is displayed on the map display unit 2, the display control unit 17 displays the calendar screen 7 on the display unit 19.

  When the date of the map to be displayed on the calendar screen 7 is designated by a user operation, the designated display date and today's date are read into the memory 22 by the analysis unit 16 (step S101).

  Similarly, the vertical M × horizontal N mesh numbers M1 (X1, Y1) to Mmn (Xmn, Ymn) and the number of meshes in the currently displayed map are read into the memory 22 (step S102). M and N are the numbers of vertical and horizontal meshes of the currently displayed area, and M1 to Mmn are values obtained by arranging the mesh numbers of the map data to be displayed in order from the upper left to the lower right of the map display unit 2. is there.

  The processing of the next steps S103 to 108 is executed by the analysis unit 16.

  An initial value 1 is set to a counter c1 that counts the number of meshes of the processed map data (step S103).

  Here, the counter c1 is compared with the number of meshes. When the counter c1 is equal to or smaller than the number of meshes, the process proceeds to the next process. When the counter c1 is larger than the number of meshes, all the meshes have been processed, and the entire designated map range is displayed on the map display unit 12, so the map display process is terminated (step S104). .

  When the counter c1 is equal to or less than the number of meshes, the mesh number Mc1 is set to the read mesh number indicating the mesh number of the map data read from the map DB 12. The mesh number Mc1 indicates the c1th mesh number of the mesh numbers M1 to Mmn (step S105).

  When the read mesh number is set, the map display switching process (FIG. 8) is called (step S106). The map display switching process will be described later.

  The processed map data of mesh number Mc1 is transferred to the display control unit 17, and the display control unit 17 causes the display unit 19 to output the map data (step S107).

  Finally, 1 is added to the counter c1, and the process returns to step S105 (step S108).

  FIG. 8 is a flowchart of the map display switching process called from the display process (FIG. 7) or the update process (FIG. 9). The read mesh number, display date, and today's date are passed from the display process or update process that is the caller.

  The analysis unit 16 instructs the DB management unit 14 to acquire map data of the designated read mesh number from the map DB 12 via the network (step S201). However, this step is skipped if the map data of the read mesh number has already been read when called from the display process.

  Next, the DB management unit 14 acquires the attribute data of the facility from the facility information DB 13 using the read mesh number as a key and reads it into the memory 22 via the network. In the attribute data to be read, the mesh number is the read mesh number, and the attribute data satisfies any of the following three conditions.

  (Condition 1) Attribute data whose start date is after the display date. (Condition 2) Attribute data whose start date is later than today's date. (Condition 3) Attribute data whose end date is earlier than the display date.

  The attribute data of (Condition 1) indicates the attribute data of the equipment that will be used after the display date. The attribute data of (Condition 2) indicates the attribute data of the equipment whose use starts after today. The attribute data of (Condition 3) indicates the attribute data of equipment that will be used before the display date. The map program stores the read attribute data S1 to SN and the number of attribute data (step S202).

  The processing of the next steps S203 to S208 is executed by the analysis unit 16.

  An initial value 1 is set to a counter c2 that counts the number of attribute data of the processed attribute data (step S203).

  Here, the counter c2 is compared with the number of attribute data. If the counter c2 is less than or equal to the number of attribute data, the process proceeds to the next process. If the counter c2 is greater than the number of attribute data, the map display switching process is terminated because all attribute data has been processed (step S204). .

  In the next process, the start date and end date of the attribute data Sc2 are determined (step S205). The attribute data Sc2 indicates the c2th attribute data of the attribute data S1 to SN. If the start date of the attribute data Sc2 is attribute data after the display date, or the end date is attribute data before the display date, the process proceeds to step S206. Otherwise, if the start date is attribute data after today's date, the process proceeds to step S207.

  In step S206, map data to be linked is processed using the ID of the data items of the attribute data Sc2 as a key (step S206). Since the equipment symbol to be processed here is an equipment symbol that does not exist at the specified display date, the display format is changed and the editing operation is invalidated. The display control unit 17 is instructed, for example, the line color in the already-read target facility map data is changed to transparent, and the invalid flag identifier is changed to valid.

  Similarly, in step S207, the map data to be linked is processed using the ID as a key among the data items of the attribute data Sc2 (step S207). Here, the map data to be processed does not actually exist on today's date but is a planned or existing facility that exists on the display date. Therefore, a process for displaying the map data separately from the existing facility is performed. For example, the display control unit 17 is instructed to change the line type of the map data of the target equipment already read into a dotted line. As long as the change process can be distinguished from the existing equipment, it is possible to set other than the dotted line.

  Finally, 1 is added to the counter c2, and the process returns to step S204 (step S208).

  FIG. 9 is a flowchart showing the map update process.

  When a user operation for selecting the edit 5 menu is received in a state where a map at an arbitrary location is displayed on the map display unit 2, an update operation of map data in the map display unit 2 is enabled. When the execution of the update operation of the map data is confirmed, the analysis unit 16 reads the display date, which is the date of the map currently displayed, into the memory 22 (step S301). However, when the update operation execution is confirmed, the changed ID is referred to in the attribute data of the equipment. If the post-change ID exists, the update of the same equipment is present in the future, so the update operation is disabled and the confirmation operation is cancelled. In this case, a message that cannot be changed may be output on the display screen.

  Next, the edit type is read by the analysis unit 16 (step S302), and the edit type is determined (step S303). If the edit type is changed, the process proceeds to step S304. If added, the process proceeds to step S307. If deleted, the process proceeds to step S309.

  In steps S304 to S306, processing when the editing type is changed is executed. The analysis unit 16 reads the old attribute data before editing and the new attribute data after editing into the memory 22 (step S304), sets the previous day of the display date as the end date of the old attribute data, and sets the new attribute data in the changed ID. The ID of the old attribute data is set in the ID and the pre-change ID (step S305), and the DB management unit 14 registers in the equipment information DB 13 via the network (step S306).

  When the edit type is added, the analysis unit 16 executes the process when the edit type is added, and the added new attribute data is read into the memory 22 (step S307). The read new attribute data is registered in the facility information DB 13 via the network by the DB management unit 14 (step S308).

  If the edit type is deletion, the analysis unit 16 instructs the DB management unit 14 to delete the old attribute data from the facility information DB 13 (step S309).

  In the subsequent steps, the mesh number M of the area where the equipment edited by the analysis unit 16 is located is read into the memory 22 (step S310), and the map data of the mesh number M is loaded into the map DB 12 by the DB management unit 14. Registration is performed (step S311). At this time, the line type, line color, and line width in the map data store default setting values designated by the user for each layer, and the invalid flag stores an attribute value indicating invalidity.

  When the map data is registered in the map DB 12, a re-reading process of the updated location map data is executed. The analysis unit 16 sets the mesh number M as the read mesh number (step S312), and calls the map display switching process (step S313).

  Finally, the map data of mesh number M read in the map display switching process is output to the map display unit 2 by the display control unit 17 (step S314).

  As described above, according to the present embodiment, data such as the start date and end date of use of each facility is provided as attribute data, and time series information is managed, so that multiple generations of map data are not retained. It is possible to hold map data over the past and future, and it is effective in suppressing the increase in system resources.

  In addition, when map data is searched by specifying a date, the map data of the corresponding part is read regardless of the date, and the map data determination process in which the specified date falls between the start date and the end date The map data of the specified date can be displayed by the method of changing the display format such as the color of the map data at each facility, and when the map data is searched by specifying another date, it is already read By changing the display format such as the line type color of each map data, it is possible to display the map data of the new specified date without newly reading the difference data of the map data. The time required for the update operation can be shortened.

  Furthermore, in an environment in which the server device 10 delivers map data to the terminal device 11 via the network, it is possible to reduce the load on the network by preventing the map data difference from frequently flowing through the network.

  In addition, even if there is a change in map data due to equipment relocation or plan change, the calculation data load and network load are reduced by eliminating the need for map data difference data extraction processing and difference data management processing. Get the effect.

  Furthermore, the present invention provides a method capable of visually distinguishing and recognizing equipment that is planned to be used at the time of the date designated for display and existing equipment.

  The forms of the present system and apparatus are not limited to the described embodiments, and can be changed in a timely manner without departing from the spirit of the present invention.

It is a conceptual diagram of the map management system 1 in this embodiment. It is a schematic block diagram of the map management system 1 in this embodiment. (a) It is an example of a layer structure of map data. (b) An example of a layer setting table. It is explanatory drawing which shows the example of map data structure stored in map DB12 in this embodiment. It is an example of composition of equipment information DB13 in this embodiment. It is explanatory drawing of the equipment registration screen in this embodiment. It is a flowchart which shows the map display process in this embodiment. It is a flowchart of the map display switching process in this embodiment. It is a flowchart which shows the map update process in this embodiment.

DESCRIPTION OF SYMBOLS 1 ... Map management system 2 ... Map display part 7 ... Calendar screen 10 ... Server apparatus 11 ... Terminal device 12 ... Map DB
13 ... Facility information DB
DESCRIPTION OF SYMBOLS 14 ... DB management part 15 ... Memory | storage device 16 ... Analysis part 17 ... Display control part 18 ... Input part 19 ... Display part 20 ... Communication part 21 ... I / O
22 ... Memory 23 ... CPU

Claims (17)

A time-series map data management system for time-series managing facility data on a map,
A database for storing map data used for displaying the equipment on a map, and attribute data including a start date and an end date of use of the equipment;
A display unit that displays the map; an input unit that accepts a request for map display; a database management unit that acquires the map data and attribute data from the database via a network; and the map data based on the attribute data A display device that includes a display control unit that performs a process of displaying and outputs to the display unit,
When the input unit receives a map display request specifying a date,
Based on the attribute data acquired by the database management unit,
The display control unit
Among the map data, select the map data for displaying the equipment used on the specified date, the equipment used on the day when the request for map display is received and the equipment not used A time-series map data management system characterized in that processing is performed using the first and second display formats in distinction. The time-series map data management system according to claim 1,
The map display request includes designation of a display area,
The database management unit
The attribute data of the facility in the area where the input unit has received a request for map display is obtained from the database,
A time-series map data management system, wherein each map data of the area is acquired from the database when the display unit does not display the area. The time-series map data management system according to claim 1 or 2,
The display control unit
A time-series map data management system for performing processing for displaying map data for displaying equipment not used on the specified date using a third display format. A time-series map data management system according to claim 3,
The time-series map data management system, wherein the third display format is different from the first and second display formats. A time-series map data management system according to any one of claims 1 to 4,
The first display format is a solid line display,
The time-series data management system, wherein the second display format is a display by dotted lines. The time-series map data management system according to any one of claims 3 to 5,
3. The time-series map data management system, wherein the third display format is a display with a transparent color. A terminal device that communicates with a server device including a database that stores facility data on a map via a network,
A display for displaying a map;
An input unit for accepting a map display request;
Database data used to display the equipment on a map, and a database management unit for obtaining attribute data including a start date and an end date of use of the equipment from the database via a network,
A display control unit that performs processing for displaying the map data based on the attribute data and outputs the display data to the display unit;
When the input unit receives a map display request specifying a date,
Based on the attribute data acquired by the database management unit,
The display control unit
The map data for displaying the equipment used on the designated date is selected from the map data, and the equipment used on the date for which the display is requested is distinguished from the equipment not used. Separately, a terminal device that performs display processing using the first and second display formats, respectively. The terminal device according to claim 7,
The map display request includes designation of a display area,
The database management unit
The attribute data of the facility in the area where the input unit has received a request for map display is obtained from the database,
When the display unit does not display the area, each map data of the area is acquired from the database. The terminal device according to claim 7 or 8, wherein
The display control unit
The terminal apparatus characterized by performing the process which displays the map data for displaying the equipment which is not used on the said designated date using a 3rd display format. The terminal device according to claim 9,
The terminal device characterized in that the third display format is different from the first and second display formats. The terminal device according to any one of claims 7 to 10,
The first display format is a solid line display,
The terminal apparatus according to claim 2, wherein the second display format is a display by dotted lines. The terminal device according to claim 10 or 11,
The terminal device according to claim 3, wherein the third display format is display in a transparent color. A time series map data management method in which a database for storing facility data on a map and a terminal device communicate via a network,
The database stores map data used to display the equipment on a map, and attribute data including a start date and an end date of use of the equipment,
The terminal device is
Accept map request,
Obtaining the map data and attribute data from the database via a network,
Perform processing to display the map data based on the attribute data, and output to the display unit,
When the map display request is date designation, the map data for displaying the equipment used on the designated date is selected from the map data based on the acquired attribute data. A time series characterized by distinguishing between the equipment used and the equipment not in use on the day when a request for map display is received, and performing processing using the first and second display formats, respectively. Map data management method. A time series map data management program in a terminal device used in a system for time series management of facility data on a map,
Receiving a map display request;
Obtaining attribute data including map data used to display the equipment on a map and start date and end date of use of the equipment from a database, and
Performing a process of displaying the map data based on the attribute data and outputting to the display unit;
When the map display request is date designation, the map data for displaying the equipment used on the designated date is selected from the map data based on the acquired attribute data. Distinguishing between the equipment used and the equipment not used on the day when the request for map display is received, and executing the process of displaying using the first and second display formats respectively. A featured time-series map data management program. A terminal device including an input unit for inputting a date specification and a display unit for displaying a map and facility information;
The display unit displays a specified date input from the input unit and a map and facility information based on the date on which the date specification is input, together with the specified date and the date on which the date specification is input. A terminal device. The terminal device according to claim 15,
The terminal device, wherein the display of the display unit changes depending on a date on which the designation of the date is input. The terminal device according to claim 16, wherein
The terminal device, wherein the display on the display unit changes depending on the designated date.

Images