JP2010129017A - Server, system, and method for retrieving map - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a server, system, and method for retrieving a map for allowing copy and paste of an explanatory note and link to a web-site about the explanatory note. <P>SOLUTION: The server for retrieving the map includes a map database that divides the whole map into a plurality of mesh-like blocks, has a data structure where the blocks are hierarchized in a plurality of stages of different sizes according to the scale, and includes a plurality of map image files for storing map image data including a plurality of explanatory notes about the map of each block with a position coordinate. The server includes bound databases that correspond to the map image files about the map of the blocks one to one, and store explanatory note character strings of the all or a part of the plurality of explanatory notes stored in the map image files, the maps of the blocks, and the position coordinate described in an explanatory note coordinate space of equal scale. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention provides a map search system having a search server that responds to map image data based on a request, a terminal device, and a map search server to which the terminal device is connected via a communication network, and a terminal device. The present invention relates to a map search method using a map search system having a map search server to which the terminal device is connected via a communication network, and in particular, a copy-and-paste operation for a note that is integrally created on a map as map image data The present invention also relates to a map search server, a map search system, and a map search method that interactively provide information about a note based on an operation by an input unit for the note.

  A map search system in which a terminal device of a user's personal computer, portable information terminal, mobile phone or the like accesses a map search server via a communication network such as the Internet, receives map image data from the map search server, and displays it It has been known.

  Maps are generally created as vector data consisting of lines, planes, character strings, symbols, etc., but map search data on the Internet takes map image data into consideration, taking into account server and client resources and line speed. Rasterized, stored in a server, and distributed to clients as image data.

  In such a map service, letters and numbers on the map other than basic elements such as mountains, rivers, roads, address marks, map symbols, etc., names and types of objects without map symbols, altitude, etc. Map notes (hereinafter abbreviated as "notes") such as height values, facility names, and store names are created as map image data, so the notes displayed on the client screen can be copied and pasted. Could not provide detailed information about the note (interactive).

  As described above, in the case of a map service on the Internet, map data is distributed as image data to a client, so that the user cannot interactively browse information about notes on the map. For example, even if you have a note that you don't know what kind of facility it is, and you want to check its meaning on the Internet, you must enter the same string into the search window while looking at the note.

  For this reason, a method of superimposing icons of guidance information on stores and facilities such as banks, convenience stores, hospitals, temples and shrines on a map by a user operation is common. In this way, when the map service is made interactive using icons, if there are many icons to be displayed, the icons may be covered on the map, making it difficult to see the map itself, and if the icons overlap each other The operability of the map service will be significantly impaired. Patent Documents 1 and 2 are prior arts for displaying stores and facilities on a map on the screen of a terminal device using icons.

  In Patent Document 1, when the number of facilities existing in the display area of the map is equal to or greater than a predetermined value, the icon is not displayed on the map, but is represented by a subwindow provided at a predetermined position on the display screen. It is described that when an icon is displayed and a representative icon is selected by the user, a facility icon indicating a facility belonging to the selected representative icon is displayed.

In Patent Literature 2, an icon belonging to which genre is displayed for each display level in the mesh file and an icon belonging to which genre is hidden is stored in a display control table, and the display level of the map image is stored. Accordingly, it is described that display / non-display of icons of each genre is controlled based on control information stored in the display control table.
JP 2006-275661 A JP 2004-163592 A

  However, in Patent Document 1, when the number of facilities existing in the map display area is greater than or equal to a predetermined value, the icon is not a store icon, but a representative icon grouped by business type, etc. It is not possible to know what kind of store it is, and it is only after clicking on the representative icon that you can see where each facility is located. There is a problem that it takes time to click the icon.

  Further, in Patent Document 2, it is necessary to create a separate table for controlling the display of icons for each genre according to the display level.

  Furthermore, in both Patent Documents 1 and 2, since the annotation on the map is provided to the user as image data integrated with other elements, the annotation can be copied and pasted and interactively searched. There is a problem that it is not possible.

  The present invention has been made in view of the above problems, and an object thereof is to provide a map search server, a map search system, and a map search method capable of copying and pasting notes and linking a note to a website. To do.

  According to invention of Claim 1, it is a map search server, Comprising: The whole map is divided | segmented into several mesh-like blocks, and the data structure hierarchized into the several step from which the size of the said block differs according to a reduced scale And a map database including a plurality of map image files for storing map image data including a plurality of annotations along with position coordinates for the map of each block, and the map image file for the map of the block on a one-to-one basis Correspondingly, for the note character strings of all or some of the plurality of notes stored in the map image file, the position coordinates described in the same coordinate scale space as the map of the block are bounced along with the note character strings. As a bounce database and as a map image file based on the request to send map image data A map image data response unit that responds to the map image data, and a response to the bounce data stored in the bounce database corresponding to the map image file in which the map image data that the map image data response unit responds is stored. A map search server including a bounce data response unit is provided.

  According to a second aspect of the present invention, in the first aspect of the present invention, each of the bounce data is stored in the notes defined in the plurality of notes stored in the corresponding map image file. A first record including a bounce identifier uniquely specified, the note character string and the position coordinates of the note character string, and a second record including data regarding a link destination to a server providing information regarding the note regarding the bounce identifier A map search server is provided.

  According to a third aspect of the present invention, in the first aspect of the invention, the bounce data specifies the note character string, the position coordinates of the note character string, and the type of facility or store represented by the note character string. There is provided a map search server including a first record including a note identifier to be recorded, and a second record including data relating to a link destination to a server that provides information regarding the facility or store represented by the note identifier for each note identifier. .

  According to a fourth aspect of the present invention, there is provided the map search server according to the second or third aspect, wherein the first record and the second record are physically stored in separate files.

  According to a fifth aspect of the present invention, in the first aspect of the invention, the bounce data response unit receives data related to a link destination to a search engine that provides information about the search keyword based on the search keyword. A map search server is provided.

  According to a sixth aspect of the invention, in the first aspect of the invention, when the note character string of the bounce data is interrupted from the map of the block corresponding to the bounce data, the scale of the same scale as the block is provided. There is provided a map search server in which position coordinates described in a note coordinate space including the note character string are stored as the bounce data in the bounce database.

  According to invention of Claim 7, it is a map search system which has a terminal device and the map search server to which this terminal device was connected via the communication network, Comprising: The said map search server is a several map. The map image data is divided into mesh-like blocks and has a data structure hierarchized into a plurality of stages with different block sizes according to the scale, and map image data including a plurality of notes about the map of each block together with position coordinates A map database including a plurality of map image files to be stored and a one-to-one correspondence with the map image file for the map of the block, and all or some of the plurality of notes stored in the map image file As the bounce data, the position coordinates described in the note coordinate space of the block and the isometric scale of the block are used as the bounce data. Based on the bounce database to be stored, the map image data response unit that responds to the map image data stored in the corresponding map image file based on the transmission request of the map image data, and the map image data that the map image data response unit has responded to A bounce data response unit that responds to the bounce data stored in the bounce database corresponding to the map image file stored in the bounce database, and the terminal device corresponds to the map image file corresponding to the map image file. A map image data request unit for requesting the map search server to transmit map image data stored in the map, a map image data response receiving unit for receiving map image data responded from the map image data response unit, and the bounces Data A bounce data response receiving unit that receives bounce data responded by the pounce unit, and a map image that displays the map image data at a screen position corresponding to the position coordinates of the map image data received by the map image data response receiving unit Map search system with data display.

  According to the invention described in claim 8, in the invention described in claim 7, when a predetermined operation is performed on the display area of the screen indicated by the cursor indicated by the input means, the note character string of the bounce data is displayed. Based on the position coordinates, the cursor indicates a predetermined display area of a note included in the map image data, determines whether the bounce data related to the note is defined, and the bounce data is defined. If so, there is provided a map search system further comprising a bounce data display unit for displaying data related to the note including the note character string of the bounce data on the screen.

  According to a ninth aspect of the present invention, in the eighth aspect of the invention, the terminal device is a predetermined unit by an input unit for a display area of the note character string included in the data displayed by the bounce data display unit. There is provided a map search system further comprising a copy and paste control unit for copying the note character string to a buffer memory and pasting the copied note character string to the buffer memory based on the operation.

  According to a tenth aspect of the present invention, in the eighth aspect, each of the bounce data is stored in the notes defined in the plurality of notes stored in the corresponding map image file. A first record including a bounce identifier uniquely specified, the note character string and the position coordinates of the note character string, and a second record including data regarding a link destination to a server providing information regarding the note regarding the bounce identifier The terminal device, when a predetermined operation is performed by the input means on the display area of the data related to the note displayed by the bounce data display unit, the bounce identifier of the bounce data related to the note If data related to the link destination is set, a map search system that requests the server to provide information related to the note. Beam is provided.

  According to an eleventh aspect of the invention, in the eighth aspect of the invention, the terminal device stops at a data display area related to the note displayed by the bounce data display unit, with the cursor pointed to by the input means. If the first link destination is set for the bounce identifier of the bounce data related to the note when the predetermined operation is performed, the server provides detailed information regarding the note based on the first link destination. When a predetermined operation is performed in which the first request part to request and the cursor indicated by the input unit overlap the display area of the data related to the note displayed by the bounce data display part, the bounce data related to the note When the second link destination is set for the bounce identifier, the note is based on the second link destination. Moreover map search system and a second request unit for requesting the provision of fine information to the server is provided.

  According to a twelfth aspect of the invention, in the eighth aspect of the invention, the bounce data specifies the note character string, the position coordinates of the note character string, and the type of facility or store represented by the note character string. And a second record including data relating to a link destination to a server that provides information on the facility or store indicated by the note identifier for each of the note identifiers. When a predetermined operation is performed in the display area of the data related to the note displayed by the bounce data display unit indicated by the cursor indicated by the means, the link destination is set for the note identifier of the bounce data related to the note. If set, request the server to provide information on the facility or store of the note based on the link destination. Moreover map search system equipped is provided a quest section.

  According to a thirteenth aspect of the invention, in the seventh aspect of the invention, the bounce data response unit includes, in the response, information about a search engine that searches for information about the search keyword based on the search keyword, The terminal device indicates when a predetermined operation is performed in the display area of the data related to the note displayed by the bounce data display unit indicated by the cursor indicated by the input means, or when the cursor indicated by the input means indicates When a predetermined operation is performed in a predetermined display area of a note included in the map image data, a map search system that requests the search engine to search using a note character string of bounce data related to the note as a search keyword Is provided.

  According to the invention described in claim 14, there is provided a map search method, a step of requesting transmission of map image data corresponding to the position information based on the position information, and a plurality of whole maps based on the request. The map image data is divided into a plurality of mesh-like blocks, and has a data structure hierarchized into a plurality of stages with different block sizes according to the scale. Reading out map image data corresponding to the position information from a map database including a plurality of map image files stored together with the response, and receiving the map image data transmitted as the response; The map image file to which the map image data transmitted as a response is stored is stored. Requesting transmission of bounce data to be performed, and notes of all or a part of the plurality of notes stored in the map image file in one-to-one correspondence with the map image file for the map of the block The bounce data corresponding to the map image data that has been responded is read out from the bounce database that stores the position coordinates described in the note coordinate space of the same scale as the map of the block as the bounce data together with the note character string, as a response. A map search method comprising: a step of transmitting; a step of receiving the bounce data transmitted as the response; and a step of displaying the map image data on a screen at a position corresponding to a position coordinate of the map image data. Provided.

  According to the invention of claim 15, in the invention of claim 14, the map image data included in each map image file is based on a map intermediate file storing map data excluding notes and the map data. A note intermediate file that stores coordinate and size data of the generated note is created, and the position coordinate of the note character string of the bounce data is based on the coordinate and size of the note stored in the note intermediate file. A map search method is provided.

  According to the first aspect of the present invention, there is a one-to-one correspondence with the map image file in which the map image data is stored, and the bounce data including the note character string and the position coordinates of the note character string is converted into the note on the map image data. Since it is created separately, an interactive search such as a copy and paste operation can be performed on the note character string in the bounce data displayed on the screen. In addition, since something is not placed on the map, the visibility is improved as compared with the case where an icon is placed. Furthermore, since the notes are arranged so as not to overlap in principle, the operability is improved as compared with the case of placing icons.

  According to the second aspect of the present invention, since the bounce data includes the information related to the link destination to the server that provides the information related to the note, detailed information related to the note is provided interactively without performing a separate search or the like. It becomes possible.

  According to the invention described in claim 3, for each type of facility or store represented by the note, the bounce data includes information on the link destination to the server that provides detailed information about the facility or store, so the note represents Detailed information on facilities and stores can be provided interactively.

  According to the fourth aspect of the present invention, since the first record and the second record are physically created in separate files, the link destination for the bounce identifier or the link destination for the note identifier only for the link destination that can be set. Therefore, it is easy to deal with changes and additions to the link destination, and the bounce database maintainability is improved.

  According to the invention described in claim 5, since the map search server transmits data related to the link destination to the search engine as bounce data as a response, the user does not copy and paste the note, and the search key is searched for the note to the search engine. The search request can be made interactive, and the operability for the user is improved.

  According to the invention described in claim 6, when the note character string is interrupted from the map of the corresponding block, the position coordinates described in the note coordinate space including the note character string of the same scale as the block are used as the bounce data. In the drag operation of the map displayed on the screen, it is possible to reliably specify the annotation of the map image data displayed on the screen.

  According to the seventh aspect of the present invention, there is a one-to-one correspondence with a map image file storing map image data, a one-to-one correspondence with a map image file storing map image data, and a note character string. Since the bounce data including the position coordinates of the note character string is created separately from the note on the map image data, interactive operations such as copy and paste operations are performed on the note character string in the bounce data displayed on the screen. Search is possible. In addition, since something is not placed on the map, the visibility is improved as compared with the case where an icon is placed. Furthermore, since the notes are arranged so as not to overlap in principle, the operability is improved as compared with the case of placing icons.

  According to the eighth aspect of the present invention, when a predetermined display area of the note in which the bounce data on the map image data displayed on the screen is defined by the cursor, the note character string on the bounce data is displayed on the screen. Since it is displayed on the screen, copy and paste operations can be performed.

  According to the ninth aspect of the present invention, since the note displayed on the terminal device can be copied and pasted by the operation of the input means, interactive browsing with respect to the note becomes possible.

  According to the tenth aspect of the present invention, since the bounce data includes the information related to the link destination to the server providing the information related to the note, detailed information related to the note is provided interactively without performing a separate search or the like. It becomes possible.

  According to the eleventh aspect, when a predetermined operation is performed on the display area of the note character string after the cursor stops in the display area of the note character string of the bounce data, the first link for the bounce identifier is displayed. Based on this, detailed information about the note can be provided from the server. Furthermore, when the cursor is moved to the display area of the note character string, detailed information regarding the note can be provided based on the second link for the bounce identifier. Thereby, the user operability is further improved.

  According to the twelfth aspect of the invention, for each type of facility or store represented by the note, information on a link destination to a server that provides detailed information about the facility or store is set, so the facility or store represented by the note Detailed information on the information can be interactively provided by the operation of the input means.

  According to the invention of claim 13, since the data related to the link destination to the search engine is transmitted as the bounce data, the user makes a search request using the note as a search key to the search engine without copying and pasting the note. It becomes possible to make it interactive, and user operability is improved.

  According to the fourteenth aspect of the present invention, there is a one-to-one correspondence with a map image file in which map image data is stored, a one-to-one correspondence with a map image file in which map image data is stored, and a note character string. Since the bounce data including the position coordinates of the note character string is created separately from the note on the map image data, interactive operations such as copy and paste operations are performed on the note character string in the bounce data displayed on the screen. Search is possible. In addition, since something is not placed on the map, the visibility is improved as compared with the case where an icon is placed. Furthermore, since the notes are arranged so as not to overlap in principle, the operability is improved as compared with the case of placing icons.

  According to the fifteenth aspect of the present invention, the notes stored in the map image file as the map image data and the notes of the bounce data are created based on the position coordinates and the size of the notes stored in the note intermediate file. Therefore, both positions and sizes can be easily and reliably matched.

First Embodiment FIG. 1 is a block diagram of a map search system according to a first embodiment of the present invention. As shown in FIG. 1, the map search system 1 includes a plurality of terminal devices 2 # i (i = 1 to n) and the terminal devices 2 # i (i = 1 to n) through a communication network 4 such as the Internet. A connected map search server 6 is provided. Reference numeral 2 # i indicates an arbitrary one of a plurality of terminal devices, but is abbreviated as 2 below.

  The terminal device 2 is a PC (Personal Computer), a PDA (Personal Digital Assistant), a mobile phone terminal, a car navigation device, a digital television, or the like through the communication network 4 according to a predetermined communication protocol, for example, HTTP (Hyper Text Transfer Protocol). The communication terminal receives a map search service from the map search server 6. Of course, the communication protocol may be a protocol other than HTTP as long as communication with the map search server 6 is possible via the communication network 4.

  Although not shown, the terminal device 2 includes a CPU, a display device, an input unit, a ROM, a main memory, a storage medium, an I / O controller, a communication interface unit, and the like. The CPU executes an operating system (OS), a program related to map search, and the like. The display device is a monitor screen that displays a map image or the like, or a TV screen such as a digital television.

  The input means is a GUI (Graphical User Interface) environment that provides an intuitive input operation to a keyboard or the like that can input characters and numbers, and an image such as a map output on the screen of the display device. A mouse or the like capable of performing a predetermined operation (click operation) or an operation of placing the cursor on the display area where the character string is displayed (mouse over operation) after the position is specified and the cursor is stopped. A copy and paste operation can be performed on a character string displayed on the screen.

  Specifically, the input means is a keyboard, a mouse, a touch pad or the like in a PC, and a PDA is a screen control means or a touch pen based on a tap operation on the touch panel with a number / character input key, a cursor key, or a finger. Yes, it is a screen control means based on a number or character input key, a cursor key, or a finger tap operation in a mobile phone terminal. In a car navigation device, it is based on a number / character input on the screen or a touch operation with a finger at the cursor position. Screen control means.

  The ROM is a memory for storing an OS program such as a BIOS executed by the CPU when the terminal device 2 is activated. The main memory is a main memory that is loaded by various programs and executed by the CPU. The storage medium is a storage medium such as a hard disk or an optical disk, and stores various programs such as a map search program, map data distributed from the map search server 6, and various data such as bounce data described later. The I / O controller controls reading and writing of data from the CPU to the storage medium. The communication interface unit manages an interface between the communication network 6 and the CPU.

  The communication network 6 is a communication network such as the Internet, and is connected to the terminal device 2 by a wired communication cable such as an optical fiber, connected wirelessly via a wireless LAN access point, or mobile The case where it connects by radio | wireless via a mobile network like a telephone terminal etc. is included.

The map search server 6 includes a map index DB 8, a map DB 10, and a bounce DB 12, and has the following functions.
(1) When a request for transmitting a location information list (for example, an HTTP request) is received from a search key such as an address, a facility name, a postal code, and a telephone number from a terminal device 2 according to a predetermined protocol, for example, HTTP, The index DB 8 is searched, and a position information list of the corresponding latitude and longitude is transmitted as a response (for example, an HTTP response). The above-described method for specifying the search key is an example for obtaining position information, and of course, it can be obtained by other methods.
(2) Upon receiving a request (for example, an HTTP request) for transmitting map image data corresponding to the position information selected by a click operation or the like from the position information list from the terminal device 2, the map DB 10 uses the position information as a key. A map image file ID for uniquely identifying the map image file, reading map image data from the map image file stored in the map DB 10 including the map image data of the point indicated by the position information, And the range of the region represented by the map image data stored in the map image file (hereinafter, the region range of the map image data), for example, the block of the region range of the map image data in which the entire map is divided into meshes The latitude and longitude of the upper left corner and the latitude and longitude of the lower right corner of the map coordinate space with the specified point on the map as the origin. Response map image data to the terminal device 2 (eg, HTTP response) to a.
(3) Upon receiving a request for transmission of bounce data corresponding to the map image data responded from the terminal device 2, for example, a map image file storing the responded map image data specified from the terminal device 2 in the request Based on the ID, the bounce data corresponding to the map image file in which the map image data is stored is read from the bounce DB 12 and transmitted to the terminal device 2 as a response (for example, an HTTP response).

  As described later, the bounce data is data relating to each note, and includes a note character string, note coordinates, a note ID, and the like. In addition, as will be described later, the entire map is divided into a plurality of mesh-like blocks, and has a data structure hierarchized into a plurality of stages in which the size of the block differs according to the scale, and a plurality of maps for each block A plurality of map image files for storing the map image data including the annotations together with the position coordinates are created, and bounce data is created for the block, and the bounce data has a one-to-one correspondence with the map image file. The bounce data subject to the response is specified.

  Similar to the terminal device 2, the hardware configuration of the map search server 6 includes a CPU, a display device, an input unit, a ROM, a main memory, a storage medium, an I / O controller, a communication interface unit, and the like. Since the function of each hardware is the same as that of the terminal device 2, description is abbreviate | omitted. A WWW (World Wide Web) server 14 is a server arranged on the communication network 4, for example, a server that functions as a search engine.

  FIG. 2 is a functional block relating to a map search of the terminal device 2 in FIG. As shown in FIG. 2, the functional block related to the map search includes an event catch unit 20, a request unit 22, a response reception unit 24, a data display unit 26, and a copy and paste control unit 28, which are stored in a storage device. The stored program is loaded into the main memory and realized by the execution of the program by the CPU.

  The event catching unit 20 confirms that the input of the search keyword for the map search to the search window has been completed by clicking the search button using an input means such as a mouse, and the position information in the position information list is clicked by the input means such as a mouse. User input means such as selection by operation, click operation etc. on the note on the map image data displayed on the screen, operation of copying and pasting bounce data, etc. Various event occurrences based on operations are caught, and the request unit 22 and the copy and paste control unit 28 are called with information necessary for processing such as a search keyword and position information as parameters.

  The request unit 22 includes a position information request unit 30, a map image data request unit 32, and a bounce data request unit 34. The location information request unit 30 designates an address, a zip code, a facility name, and the like that designate a display target map input by the user in the search window, and sends a location information list of the corresponding latitude and longitude to the map search server 6. Make a request (for example, an HTTP request). A method for specifying a display target map such as position information can be specified in addition to specifying a search keyword, and may be specified in accordance with each specification method.

  The map image data request unit 32 transmits the transmission of map image data including the selected latitude / longitude point by clicking the position information of the latitude / longitude of the map displayed on the screen, for example, the position information list. A request (for example, HTTP request) is made to the search server 6.

  At this time, in the map search server 6, the response of the map image data is performed in units of map image files. Therefore, the request for the map image data is necessary to display the selected latitude / longitude point at the center of the map display screen. This is done according to the number of map image files.

  The bounce data request unit 34 requests transmission of bounce data corresponding to the map image file in which the received map image data is stored (for example, an HTTP request). For example, a map image file ID in which map image data is stored is transmitted from the map search server 6 to the terminal device 2 as a response, a map image file ID is specified, and bounce data corresponding to the ID is requested.

  The response receiving unit 24 receives a response to the request from the map search server 6, and includes a position information response receiving unit 40, a map image data response receiving unit 42, and a bounce data response receiving unit 44.

  The position information response receiving unit 40 receives a position information list that is a response from the map search server 6 to the position information request of the position information request unit 30. The map image data response receiving unit 42 receives the map image data, which is a response from the map search server 6 to the map image data request of the map image data request unit 32, the latitude / longitude indicating the area range of the map image data, and the map image file ID. Receive.

  The bounce data response receiving unit 44 receives bounce data that is a response from the map search server 6 to the bounce data request of the bounce data request unit 34. As described later, the bounce data includes data of a plurality of attributes such as a bounce ID, a note character string, a note ID, a note coordinate, and a latitude / longitude for each note, and is stored in the array area.

  The format of the bounce data is a text format or an XML format. In the case of the text format, the attribute value is stored in the array area for each note according to the bounce data format such as the attribute delimiter. In the case of the XML format, for each note based on the designation by the tag or the like. Each attribute value is stored in the array area.

  The data display unit 26 includes a map image data display unit 50 and a bounce data display unit 52. From the map image data received by the map image data response receiving unit 44 and the area range of the map image data, the map image data display unit 50 is arranged such that the latitude and longitude specified as position information are located at the center of the map display screen. The map image data to be displayed is edited to generate map display screen data, and the map is displayed on the map display screen.

  At this time, when displaying on the screen using the map image data of a plurality of map image files, the movement amount of the position coordinates of the map image data stored in each map image file is calculated, and each map image is calculated according to this movement amount. Edit the data to generate map display screen data.

  In addition, if it is necessary to scale the map image data, the map image data should be edited according to the amount of movement of the position coordinates of the map image data after the map image data has been enlarged or reduced. Then, map display screen data is generated and a map is displayed on the map display screen. The map image data may be enlarged or reduced after editing the position coordinates of the map image data according to the movement amount.

  The bounce data display unit 52 calculates position coordinates in a note coordinate space (described later) in which bounce data corresponding to the position indicated by the cursor indicated by the mouse or the like is described, and the position coordinates indicate the note character string of the bounce data. It is determined whether or not it is included in the enclosing rectangle, and if it is determined that it is included in the enclosing rectangle of the note character string of the bounce data, it is displayed on the screen that the bounce data related to the note is defined. When a predetermined operation such as a click is performed on the note on the map image data, data including the note character string on the bounce data related to the note is displayed in a pop-up balloon. For example, as shown in FIG. 17, the bounce data relating to the note ABC on the map image data is displayed in a pop-up balloon. At this time, when the address, the nearest station, and the telephone number related to the note are included as the bounce data, these data are also displayed in a pop-up balloon. If an image of a store or facility is designated as bounce data, the image is displayed in a pop-up balloon.

  Hereinafter, a predetermined display area where a note on the map image data is displayed, for example, a display area surrounding the character string of the note is referred to as a note display area on the map image data. There are horizontal writing, vertical writing, and two columns of note character strings. Like horizontal writing, note character strings on the bounce data are displayed on the screen in a single horizontal row. To do. A data display area including the note character string on the bounce data is referred to as a note display area on the bounce data.

  Here, if the map image data displayed on the screen has been enlarged or reduced, the position coordinate of the note character string of the bounce data is scaled at the same scale as the scale for the map image data, and then the map corresponding to the bounce data. Edit the position coordinates according to the same movement amount as the movement amount of the map image data in the image file, determine whether the position coordinates are included in the rectangle surrounding the note character string of the bounce data, and include it in the note character string If so, a note string is displayed on the screen. Note that, similarly to the map image data, enlargement / reduction of the bounce data may be performed after the position coordinates of the bounce data are edited according to the movement amount.

  As will be described later, not only the bounce data has a one-to-one correspondence with the map image file, but the map image data related to the map of the block corresponding to the map image file has a predetermined position of the corresponding block as the origin, and from the origin. Described in the map coordinate space of a predetermined range in the vertical and horizontal directions, the bounce data is also described in the note coordinate space of the same range as the map image coordinate space, with the corresponding region as the origin at the same predetermined position as the map image data .

  Therefore, by overlapping the origin of the map coordinate space and the origin of the note coordinate space, the note on the map image data and the note on the bounce data are exactly overlapped, and the map image can be specified by clicking the note display area on the data. Thus, the note on the corresponding bounce data can be reliably displayed. Even if the user scrolls or drags the map on the screen, the position coordinates of the note on the map image data can be known from the position coordinates of the note character string on the bounce data. By clicking, the note on the corresponding bounce data can be reliably displayed on the screen.

  When a copy operation is performed on the note character string on the bounce data displayed on the screen by an input means such as a mouse or a keyboard, the copy and paste control unit 28 stores the note character string in the buffer memory, and the mouse When a note is pasted by an input means such as a keyboard or a keyboard, the copied note character string is pasted.

  Copy and paste assumes a scene where the WWW server 14 serving as a search engine is accessed and a note is copied as a search keyword and then pasted in a search window for interactive browsing. Here, the character string includes all characters of the note used on the map such as alphanumeric characters, kanji, katakana, hiragana and symbols.

  Also for vertically written and two-column note character strings, the note character strings on the bounce data are displayed in a horizontal row on the screen, and can be copied and pasted. The above program can be realized by Ajax (Asynchronous JavaScript + XML). Java is a registered trademark.

  FIG. 3 is a functional block diagram of the map search server 6 in FIG. As shown in FIG. 3, the map search server 6 includes a request receiving unit 60, a position information acquiring unit 62, a map image data acquiring unit 64, a bounce data acquiring unit 66, and a transmitting unit 68, and is stored in a storage device. The corresponding program is loaded into the main memory, and is realized by executing the program by the CPU.

  The request receiving unit 60 includes a position information request receiving unit 80, a map image data request receiving unit 82, and a bounce data request receiving unit 84. The location information request receiving unit 80 receives a request for a location information list in which a search keyword such as an address, a facility name, and a zip code is specified from the terminal device 2, and outputs the search keyword to the location information acquisition unit 62.

  The map image data request receiving unit 82 receives a request for map image data for which position information is specified from the terminal device 2, and outputs the position information to the map image data acquiring unit 64. The bounce data request receiving unit 84 receives a bounce data request in which information (for example, a map image file ID) specifying bounce data is received from the terminal device 2, and receives information specifying the bounce data as a bounce data acquisition unit. 66.

  The position information acquisition unit 62 searches the map index DB 8 based on the search keyword received by the position information request reception unit 80 and acquires a position information list. The map image data acquisition unit 64 searches the map DB 10 from the location information received by the map image data request reception unit 82, and stores the map DB 10 including the map image data of the point indicated by the location information. Map image data is acquired from the map image file corresponding to the image file ID, the regional range of the map image data stored in the map image file, and the map image file ID. The bounce data acquisition unit 66 searches the bounce DB 12 from the map image file ID received by the bounce data request reception unit 84 and acquires the corresponding bounce data.

  Even if the bounce data is not requested from the terminal device 2, the map search server 6 responds the bounce data together with the map image data and the area range of the map image data. For example, the map image data and the area After responding together with the range, the bounce data may be automatically responded. In this case, the bounce data request unit 34 in FIG. 2 is not necessary.

  The transmission unit 68 includes a position information response unit 86, a map image data response unit 88, and a bounce data response unit 90. The location information response unit 86 transmits the location information list acquired by the location information acquisition unit 62 to the terminal device 2 as a response (for example, an HTTP response).

  The map image data response unit 88 transmits the map image data acquired by the map image data acquisition unit 64, the map image file ID, and the area range of the map image data to the terminal device 2 as a response (for example, an HTTP response). The bounce data response unit 90 transmits the bounce data acquired by the bounce data acquisition unit 66 to the terminal device 2 as a response (HTTP response).

  In this embodiment, the terminal device 2 generates the map display screen by editing the position coordinates of the map image data and the bounce data so that the point of latitude and longitude is the center of the map display screen. On the server 6 side, the movement amount of the map image data stored in the plurality of map image files is calculated so that the latitude and longitude indicated by the position information are centered, and the position coordinates of the map image data are edited according to the movement amount. Then, the position coordinates of the note on the bounce data may be edited according to the same movement amount, and the map image data and the bounce data may be responded. Alternatively, the response may be made after editing the bounce data into a format such as HTML. By carrying out like this, the processing burden of the terminal device 2 can be reduced.

  FIG. 4 is a diagram showing a configuration example of the map index DB 8 in FIG. As shown in FIG. 4, the map index DB 8 stores position information of the corresponding latitude and longitude with respect to the address, postal code, facility name, and the like. When an address, a zip code, a facility name, etc. are specified by the terminal device 2 as a search keyword, the map index DB 8 is searched based on the search keyword, and position information of latitude and longitude including the address, zip code, facility name, etc. is obtained. can get.

  FIG. 5 is a diagram showing a logical configuration diagram of the map DB 10 and the bounce DB 12 in FIG. 1, and in particular, FIG. 5 (a) is a diagram showing map image data, and FIG. 5 (b) is a diagram showing bounce data. . As shown in FIG. 5A, a primary map obtained by dividing an entire map, for example, a Japanese map into meshes (blocks) of a predetermined size (about 80 km × about 80 km), and a primary mesh is divided into 8 × 8. The secondary mesh, the secondary mesh is divided into 10 × 10, and further divided into a high-order mesh and a quaternary mesh. Map image data of a region included in each mesh is stored as a map image file corresponding to each mesh. As the mesh becomes higher, the mesh map range becomes smaller and the scale becomes larger.

  The map image data in the map of each mesh is described in a predetermined range of map coordinate space in the vertical and horizontal directions with a predetermined position of the mesh, for example, the upper left corner as the origin, and a map image file is created. Thus, the map image data has a data structure hierarchized into a plurality of stages having different mesh sizes according to the scale. On the other hand, as shown in FIG. 5B, the note on the bounce data is the same as the map coordinate space, where the same area as the map of each mesh for the map image data has the same point as the origin of the map coordinate space. It is described in the annotation coordinate space of the range.

  If there is no note to be stored as bounce data in the mesh, bounce data is not created. However, if bounce data exists in the mesh, the map image file corresponding to the mesh is uniquely determined, and the bounce data The map image file corresponding to the data corresponds to one-to-one (if the mesh in which the bounce data exists is different, the corresponding map image file is different). In the following, it is described that the map image file and the bounce data for each area correspond one-to-one.

  For example, as shown in FIG. 6A, in a map of a certain mesh, a map coordinate space having an origin (0, 0), a maximum horizontal coordinate value xmax, and a maximum vertical coordinate value ymax; For the note coordinate space corresponding to the mesh shown in b), the point corresponding to the origin position (0, 0), the maximum horizontal coordinate value xmax, and the maximum vertical coordinate value ymax are the same.

  Accordingly, the position coordinates of the four points on the lower left, lower right, upper right, and upper left of the rectangle surrounding the note ABCD on the map image data are the same as the position coordinates of the note ABCD on the bounce data shown in FIG. When the origins of are overlaid, the note on the bounce data exactly matches the note on the map.

  FIG. 7 is a diagram showing a configuration diagram of the map DB 10 in FIG. As shown in FIG. 7, the map DB 10 includes a map image index file 100 and a plurality of map image files 102 # i (i = 1 to n). The map index file 100 stores a map image file ID, latitude / longitude 1 and latitude / longitude 2, and a map image file name for each map image file 102 # i (i = 1 to n).

  Each map image file ID is an identifier that uniquely identifies each map image file 102 # i (i = 1 to n). For example, the map image file name is xxx. If it is gif, xxx excluding the extension is the map image file ID.

  Latitude and longitude 1 and 2 indicate the regional range of the map image data stored in the map image file 102 # i (i = 1 to n). For example, the latitude and longitude 1 is a mesh corresponding to the map image file. The latitude / longitude of the origin point, latitude / longitude 2, is the latitude / longitude of the lower right corner of the mesh.

  The map image file is a file name in which map image data of the mesh area is stored. Each map image file 102 # i (i = 1 to n) is an image data file in which map data including a note is rasterized for each mesh, and is, for example, a GIF format map image file.

  FIG. 8 is a logical configuration diagram of the bounce DB 12 in FIG. As shown in FIG. 8, the bounce DB 12 is a file that stores attribute values such as a map image file ID, a bounce ID, a note, a note ID, coordinates, and a latitude and longitude. The map image file ID is an ID of one of the map image files 102 # i (i = 1 to n) corresponding to the bounce data. The bounce ID is a bounce data identifier for uniquely identifying the note registered in the note on the map image data stored in the corresponding map image file 102 # i as a note. This bounce ID is present in the image of the map image file for one map image file ID, and there are as many bounce IDs as the number of notes registered in the bounce DB 12 as bounce data.

  A note is a note string. The note ID is a note identifier indicating the type of the note such as a temple, restaurant, hospital, hotel / inn. The coordinates represent the position and size of the note character string, and are, for example, the lower left, lower right, upper right, and upper left coordinates of a rectangle surrounding the note character string. The notation has horizontal writing, vertical writing, and two columns. The latitude / longitude is the latitude / longitude where the facility indicated by the note is located. The bounce ID, note, note ID, coordinates, latitude and longitude, etc. are referred to as bounce data. As the bounce data, an attribute designating an address of a store or facility related to the note, a telephone number, the nearest station, or an image of the store or facility may be added.

  FIG. 9 is a diagram illustrating a manufacturing process of the bounce DB 12. In step S2, which is an indispensable process for creating a map, a tool is used to store an annotation created for each mesh area, for example, in a map intermediate file 110 that stores map data in a vector data format. The read map data is read and displayed on the display device.

  A note is created based on the map displayed on the screen. For example, a note character string expressed in a vector data format, and note data at a position coordinate indicating the location and size of the note are stored in the note intermediate file 112 as text. Store as a file. At this time, in principle, the notes are arranged so as not to overlap.

  In step S4, a note to be registered is selected from the note character strings stored in the note intermediate file 112, and the note character string and position coordinates are stored in the bounce DB 12 together with the map image file ID, bounce ID, note ID, and latitude / longitude. .

  On the other hand, in step S6, the map data of the map intermediate file 110 and the notes of the note intermediate file 112 are rasterized and combined with the map image data to create the map image file 102. The note intermediate file 112 is a product of the work of arranging the note so that it is easy to see in step S2 (called drawing), and is stored in the bounce DB 12 generated based on the note data stored in the note intermediate file 112. Note that the note on the bounce data and the note on the map image data stored in the map image file 102 exactly match.

  FIG. 10 is a diagram illustrating a physical configuration example of the bounce DB 12. As shown in FIG. 10, the bounce data corresponding to the map image file 102 # i (i = 1 to n) is composed of the bounce file 104 # i (i = 1 to n) corresponding to the file on a one-to-one basis. The The file name matches the file name of the corresponding map image file 102 # i except for the extension. Accordingly, the corresponding bounce data is easily specified by the map image file ID of the map image file 102 # i.

  FIG. 11 is a diagram illustrating a method of creating bounce data when a note extends over a plurality of meshes. For example, if the note CDEF breaks in each of the two mesh maps and spans the note coordinate space corresponding to the two meshes, the note is created in the note coordinate space corresponding to each existing mesh. In this case, note CDEF bounce data is generated for two meshes. In each mesh, the coordinate in the note coordinate space obtained by extending the note coordinate space so as to continuously include the note ABCD on an equal scale is set as the position coordinate of the note.

  For example, the letter EF of the note CDEF protrudes to the right in the left mesh, and the lower right coordinates and upper right coordinates of the note CDEF are set larger than the maximum value of the horizontal axis in the note coordinate space corresponding to the mesh. In the right mesh, the character CD of the note CDEF protrudes to the left and becomes smaller than the minimum value 0 on the horizontal axis, and the lower left coordinate and upper left coordinate of the note CDEF are set to be negative.

  As a result, even when the note is interrupted from the map coordinate space corresponding to the map image file, the note on the map image data and the note on the bounce data exactly match each other. As a result, when a note on the map image data displayed on the screen is clicked in an operation such as scrolling, dragging, enlarging or reducing the map, the note of the corresponding bounce data is surely displayed on the screen. it can. Then, even for a note that is partially broken, the note character string on the bounce data can be displayed on the screen by clicking the note on the map image data, and the note can be copied and pasted.

  12 is a diagram showing an example of map image data stored in the map image file, and FIG. 13 is a diagram showing an example of bounce data corresponding to the map image data of FIG. As shown in FIG. 13, the bounce data is stored in a text file corresponding to the map image file on a one-to-one basis.

  SetLabel is the map image file ID, tid is the bounce ID, text is the note character string, Specid is the note identifier, coordinates is the coordinates, lat is the latitude, and lon is the longitude attribute name, and the attribute value is stored as the bounce data ing.

  Since the attribute name and attribute value are surrounded by special symbols, the other attribute names and attribute values are delimited, and the boundaries of each bounce data are delimited by special symbols. Necessary attribute values can be extracted. In this example, the bounce DB 12 is in the text format, but may be constructed with an XML format document.

  14 is a process flowchart of the terminal device 2, FIG. 15 is a process flowchart of the map search server 6, and FIG. 16 is a sequence chart. When accessing the map search server 6, the corresponding page is responded from the map search server 6, and the terminal device receives the response and displays the page on the screen.

  It is assumed that the event is caught in step S20 in FIG. For example, when a position search keyword, for example, Yayoi, Bunkyo-ku, Tokyo, is input to the search window and an operation for instructing the end of input, for example, a “search button” is pressed by a click operation, this click operation is caught as an event. . In step S22, the terminal device 2 designates a location search keyword to the map search server 6 and requests location information, as indicated by (2) in FIG.

  In step S <b> 48 in FIG. 15, the map search server 6 receives a request from the terminal device 2. In step S50, it is determined whether position information is requested. If the determination is affirmative, the process proceeds to step S52. If the determination is negative, the process proceeds to step S58. Here, since position information has been requested, the process proceeds to step S52.

  In step S52, the map index DB 8 is searched based on the position search keyword. In step S54, a position information list corresponding to the position search keyword is acquired. In step S56, as indicated by (4) in FIG. 16, the position search server 6 transmits the position information list to the terminal device 2 as a response.

  The position information list responded from the map search server 6 is received in step S24 in FIG. In step S26, the position information list is displayed on the screen. It is assumed that the user has selected position information from the position information list displayed on the screen by a click operation or the like.

  The selection by the click operation or the like is caught as an event in step S20, and in step S28, the terminal device 2 specifies the selected position information as shown in (6) in FIG. Request transmission to the map search server 6.

  When the map search server 6 receives the request at step S48 in FIG. 15 and the determination at step S50 is negative, the map search server 6 determines at step S58 whether or not the request is a request for map image data. The process proceeds to step S60.

  In step S60, the map index file 100 in the map DB 10 is searched using the position information as a search key. In step S62, the map image data 102 from which the map image data of the location indicated by the position information is stored (the corresponding map image file is represented by 102), and the map of the map image file 102 from the map index file 100 are displayed. The latitude longitude 1 and 2 which show the area range of image file ID and map image data are acquired.

  In step S64, the map search server 6 transmits the map image data, the map image file ID, and the latitude / longitude 1 and 2 as a map image data response, as indicated by (8) in FIG.

  The terminal device 2 receives the map image data response in step S30 in FIG. In step S32, as shown at (10) in FIG. 16, a map image file ID is designated and transmission of bounce data corresponding to the map image file is requested.

  The map search server 6 receives the request at step S48 in FIG. 15, and proceeds to step S68 when the determination at step S66 is affirmative through the processing at step S50, step S58, and step S66. In step S68, the bounce DB 12 is searched using the map image file ID as a search key. For example, a bounce file 104 having a file name indicated by the map image file ID (a corresponding bounce file is represented by 104) is searched.

  In step S70, the bounce data corresponding to the map image file ID is read from the bounce DB 12, for example, the bounce file 104, and acquired. In step S72, the bounce data is transmitted as a response, as indicated by (12) in FIG.

  The terminal device 2 receives the bounce data response in step S34 in FIG. In step S36, the map image data and the region range (latitude and longitude 1, 2) of the received map image data and map image data are set so that the latitude and longitude specified as the position information are located at the center of the map display screen. The position coordinates of are edited to generate map display screen data.

  At this time, when displaying on the screen using the map image data of a plurality of map image files, the movement amount of the position coordinates of the map image data stored in each map image file is calculated, and each map image is calculated according to this movement amount. Edit the data to generate map display screen data.

  In addition, if it is necessary to scale the map image data, the map image data should be edited according to the amount of movement of the position coordinates of the map image data after the map image data has been enlarged or reduced. Then, map display screen data is generated and a map is displayed on the map display screen. In step S38, the map screen data is displayed on the screen.

  It is assumed that the user performs a click operation on the note display area on the map image data. In step S40, the terminal device 2 calculates position coordinates in the note coordinate space in which the bounce data corresponding to the position indicated by the cursor indicated by the mouse or the like is described, and the position coordinates indicate the note character string of the bounce data. It is determined whether or not the position coordinates of the four surrounding points are included in the quadrangle indicated, and if included in the quadrangle including the note character string, as shown in (16) and FIG. Display a string in a pop-up balloon. At this time, if an address, telephone number, nearest station, store or facility image is specified as the bounce data, these data are also displayed in a balloon.

  Here, if the map image data displayed on the screen has been enlarged or reduced, the position coordinate of the note character string of the bounce data is scaled at the same scale as the scale for the map image data, and then the map corresponding to the bounce data. The position coordinates are edited according to the same movement amount as the movement amount of the map image data in the image file, and it is determined whether or not the position coordinates are included in the rectangle surrounding the note character string of the bounce data. If so, display the note string in a pop-up balloon.

  It is assumed that the user performs a copy operation of the note character string on the bounce data displayed on the screen. This copy operation is event-caught in step S20. In step S44, the note character string is copied to the buffer. It is assumed that the user accesses the WWW server 14 as a search engine. A page is transmitted from the WWW server 14 and displayed on the screen.

  It is assumed that the user pastes the copied note in the search window and clicks the search button. The terminal device 2 designates a note copied and pasted to the WWW server 14 as a search keyword, makes a search request, and displays a page list related to the search keyword returned from the WWW server 14. Thereby, interactive browsing becomes possible.

  According to the present embodiment described above, something is not placed on the map like an icon, so that the map does not become difficult to see, and the visibility is improved as compared with the case where the icon is placed. Further, since the notes on the map are positioned so as not to overlap in principle, the operability is improved as compared with the case of placing icons.

  Since the note string itself can be provided as text instead of an image, it is possible to copy and paste the note, and to provide detailed information on the note that has not been easily known so far. It was.

  In addition, a predetermined area of the display area of the data including the note character string on the bounce data displayed on the screen, for example, the latitude and longitude included in the bounce data is displayed in a hop-up balloon together with the note character string, and the latitude When the longitude is clicked, based on the latitude and longitude of the note in the bounce data included in the response of the bounce data, the surrounding map and the note will be displayed in detail so that the note will be the center of the map. May be. Thereby, the map information around the note to be searched is obtained in detail, and the operability for the user is improved.

  In addition, when the user clicks the note display area on the map image data, the note character string on the corresponding bounce data is not displayed on the screen, but the map image data is displayed on the screen, and then the bounce data is displayed. The note on the bounce data may be automatically superimposed on the note on the map image based on the position coordinates. In this case, the note on the map image data and the note on the bounce data are displayed exactly overlapped on the screen. Copy and paste operations can be performed on the note character string on the bounce data.

Second Embodiment FIG. 18 is a block diagram of a map search system 146 according to a second embodiment of the present invention. Components that are substantially the same as those in FIG. 1 are given the same reference numerals. . The description of the components having the same reference numerals is omitted.

  In the present embodiment, a URL (Uniform Resource Locator) 1 when a predetermined operation (click operation) is performed after the cursor is stopped in the note display area on the bounce data and the note display on the bounce data are displayed in the bounce data. It is possible to set the link destination URL2 when the cursor is moved over the area (mouse over operation). For the bounce data in which URL1 or URL2 is set, the link destination is set according to the user click operation or mouse over operation. This is different from the first embodiment in that the page is displayed. Note that the click operation and the mouse over operation are not limited to those performed by the mouse, but may be performed by other input means.

  The terminal device 148 # i (i = 1 to n) displays the linked page for the bounce data in which URL1 or URL2 is set according to the user's click operation in the note display area or mouse-over operation. This is different from the terminal device 20 # i (i = 1 to n) in FIG.

  The bounce DB 152 is different from the bounce DB 12 in FIG. 1 in that for each bounce data, a link destination URL 1 at the time of a click operation and / or a link destination URL 2 of a mouse over operation can be set.

  The map search server 150 adds the URL 1 and / or URL 2 of the link destination to the terminal device 148 (an arbitrary terminal device is represented by 148) as a part of the bounce data in addition to the bounce data of the first embodiment. This is different from the map search server 6 in FIG.

  FIG. 19 is a functional block diagram of the terminal device 148 in FIG. 18, and components that are substantially the same as those in FIG. 2 are given the same reference numerals. In the request unit 160, a bounce click data request unit 162 and a bounce mouse over data request unit 164 are added.

  When a predetermined area of the note display area on the bounce data, for example, a quadrangular area surrounding the note character string, is clicked, the bounce click data request unit 162 corresponds from the position on the screen surrounding the note character string. The bounce ID of the bounce data of the note is acquired, and it is determined whether or not the link destination URL1 is set for the bounce ID. If URL1 is set, the link destination page is transmitted to the WWW server 14. Request.

  When the mouse is over a predetermined area of the note display area on the bounce data, for example, a rectangular area surrounding the note character string, the bounce mouse over data request unit 164 starts from the position on the screen of the area surrounding the note character string. The bounce ID of the bounce data of the corresponding note is acquired, and it is determined whether or not the link destination URL2 is set for the bounce ID. If URL2 is set, the WWW server 14 sends the link destination page Request transmission.

  Here, the WWW server 14 indicates the link destination URL 1 and URL 2 servers, and may be the map search server 150 depending on the settings of the URL 1 and URL 2. URL1 is a page in the server where the facility / store related to the note provides detailed information, for example, the URL of the official homepage of the store, etc., and URL2 is a map search server explaining the outline of the facility / store related to the note 6, for example, the URL of a page describing features such as a store more detailed than the bounce data.

  When the bounce data includes the address of the store or facility related to the note, the telephone number, the designation of the nearest station, the image of the store or facility, etc., the page linked by the URL 2 will explain the other outlines. If data is included but bounce data is sufficient, URL2 can be omitted.

  When the note display area on the map image data is clicked, the bounce click data request unit 162 acquires the bounce ID of the bounce data of the corresponding note from the position on the screen of the note display area, and the bounce ID. It is determined whether or not the link destination URL1 is set, and if the URL1 is set, the WWW server 14 may be requested to transmit the link destination page.

  When the note display area on the map image data is moused over, the bounce mouse over data request unit 164 obtains the bounce ID of the bounce data of the corresponding note from the position on the screen of the note display area, and the bounce It is determined whether or not the link destination URL 2 is set for the ID, and if the URL 2 is set, the WWW server 14 may be requested to transmit the link destination page.

  In the response receiving unit 166, a bounce click data response unit 168 and a bounce mouse over data response unit 170 are added. The bounce click data response unit 168 receives bounce click data that is a response to the request of the bounce click data request unit 162. The bounce mouse over data response unit 170 receives bounce mouse over data that is a response to the request from the bounce mouse over data request unit 164.

  A bounce click data display unit 174 and a bounce mouse over data display unit 176 are added to the data display unit 172. The bounce click data display unit 174 displays the bounce click data received by the bounce click data response reception unit 168 on the screen. The bounce mouse over data display unit 176 displays the bounce mouse over data received by the bounce mouse over data response receiving unit 170 in a pop-up balloon. For example, the bounce mouse over data is displayed in a pop-up balloon over the note display area on the bounce data.

  FIG. 20 is a functional block diagram of the map search server 150 in FIG. 18, and the same reference numerals are given to substantially the same components as those in FIG. The bounce data acquisition unit 180 adds the link destination URL 1 at the time of the click operation and / or the link destination URL 2 at the time of the mouse-over operation to the bounce data and acquires the bounce data acquisition unit in FIG. 66.

  The bounce data response unit 184 in the transmission unit 182 responds by adding the link destination URL 1 at the time of the click operation and / or the link destination URL 2 at the time of the mouse over operation to the bounce data in FIG. Different from the bounce data response unit 90 of FIG.

  FIG. 21 is a logical configuration diagram of the bounce DB 152 in FIG. As shown in FIG. 21 (a), in the bounce DB 152, in addition to substantially the same components as the bounce DB 12 in FIG. 8, for each map image file ID as shown in FIG. 21 (b). The bounce ID and URL1 are set for the note for which the link destination at the time of the click operation can be set.

  Further, as shown in FIG. 21C, for each map image file ID, a bounce ID and URL2 are set for a note that can set a link destination at the time of a mouse-over operation. As described above, URL1 and URL2 are set in the bounce DB 152 only for the notes that can be set as the link destination in each operation during the click operation and the mouse-over operation.

  Here, the bounce data (first record) shown in FIG. 21 (a) is stored in the first file, and the bounce data (second record) shown in FIG. 21 (b) is stored in a second file different from the first file. Store the bounce data (third record) shown in FIG. 21 (c) in a third file different from the first and second files, and physically separate the first to third files and build them separately. This improves the maintainability of the database when URL1 and URL2 are frequently added / changed.

  Note that the attributes of URL1 and URL2 may be added to the bounce DB 152 shown in FIG. 21A, an attribute value may be set for the attribute, and if there is no attribute value, that fact may be set.

  FIG. 22 is a process flowchart of the terminal device 148. FIG. 23 is a process flowchart of the map search server 150. FIG. 24 is a sequence chart. Hereinafter, the processing of the map search system 146 will be described with reference to these drawings.

  The processes in steps S102 to S112 in FIG. 22 are the same as the processes in steps S22 to S32 in FIG. Further, the processing in steps S148 to S166 in FIG. 23 is the same as the processing in steps S48 to S66 in FIG. (50) to (58) in FIG. 24 are the same as the sequences (2) to (8) in FIG.

  In step S168 in FIG. 23, the bounce DB 152 is searched. In addition to the search process of the bounce DB 12 in step S68 in FIG. 16, the bounce ID and URL1, and the bounce ID and the map image file ID are used as keys. Search for URL2. In step S170, in addition to the bounce data similar to that in step S70, the bounce ID and URL1 and the bounce ID and URL2 are acquired for the set note.

  In step S172, in addition to the bounce data response in step S72, as shown in (60) in FIG. 24, the bounce ID and URL1, and the bounce ID and URL2 are set as the bounce data for the notes in which URL1 and URL2 are set. It transmits to the terminal device 148 as a response.

  In step S114 in FIG. 22, in addition to the bounce data response similar to that in step S32 in FIG. Receive. In steps S116 to S120, processing similar to that in steps S36 to S40 in FIG. 14 is performed.

  It is assumed that the note display area on the bounce data is clicked. In step S128, the terminal device 148 acquires the bounce data of the corresponding note from the display coordinates of the clicked note display area, determines whether or not URL1 is set for the bounce ID of this bounce data, and URL1 If it is set, as shown at (66) in FIG. 24, URL1 is designated, and the transmission of the page is requested to the WWW server 14.

  As shown at (68) in FIG. 24, the WWW server 14 transmits the page specified by URL1 as a bounce click data response. In step S130, the terminal device 148 receives the bounce click data response. In step S132, the bounce click data is displayed on the screen as indicated by (70) in FIG.

  It is assumed that the mouse is moved to the note display area on the bounce data. In step S134, the terminal device 148 obtains the bounce data of the corresponding note from the display coordinates of the note display area where the mouse-over operation has been performed, determines whether URL2 is set for the bounce ID of this bounce data, If URL2 is set, as shown at (72) in FIG. 24, URL2 is designated and a page transmission request is made to the WWW server 14.

  The WWW server 14 transmits the page specified by URL2 as a bounce mouse over data response, as indicated by (74) in FIG. In step S136, the terminal device 148 receives the bounce data response. In step S138, as shown at (76) in FIG. 24, the mouse-over data is displayed in a pop-up balloon over the note display area on the bounce data.

  Note that the bounce data is indicated by the URL when only one link destination URL is set and any one of the click operation and the mouse over operation is operated on the terminal device 148 side, for example, when the click operation is performed. For example, when the other page is operated, the linked page may not be displayed even when the mouse is operated.

  According to the second embodiment described above, in addition to the effects of the first embodiment, it is possible to set a link for a note, and the user does not separately search for an object on the map. It becomes possible to examine information related to the spot. Moreover, by setting the outline of the facility related to the note more detailed than the bounce data in the URL2 page and setting the URL1 for more detailed information, simple information can be obtained from the bounce data, More detailed information can be obtained from the URL2 page, and more detailed information can be obtained from the URL1 page, so that information related to the spot can be examined according to the purpose.

Third Embodiment FIG. 25 is a block diagram of a map search system 198 according to a third embodiment of the present invention. Components that are substantially the same as those in FIG. 1 are given the same reference numerals. . The description of the components having the same reference numerals is omitted.

  In this embodiment, the map search server 202 transmits the URL of the search engine 206 as a bounce data response, and when the note display area is clicked, the note is specified as a search keyword to the search engine 206, and the search It differs from the first embodiment in that a request is made.

  When the note display area on the bounce data is clicked, the terminal device 200 # i (i = 1 to n) designates the URL of the search engine 206 and the clicked note as a search keyword and searches the search engine 206. Is different from the terminal device 2 # i (i = 1 to n) in FIG.

  The bounce DB 204 is different from the bounce DB 12 in FIG. 1 in that the URL of the search engine 206 is set. The map search server 202 adds the URL of the search engine 206 to the terminal device 200 (an arbitrary terminal device is represented by 200) as a part of the bounce data in addition to the bounce data of the first embodiment. Is different from the map search server 6 in FIG.

  FIG. 26 is a functional block diagram of the terminal device 200 in FIG. 25, and the same reference numerals are given to substantially the same components as those in FIG. When the note display area on the bounce data is clicked, the bounce information search request unit 212 in the request unit 210 designates the note as a search key and requests the search engine 206 to search.

  The search result list response receiving unit 216 in the response receiving unit 214 receives the search result list response from the search engine 206. The search result list display unit 220 in the data display unit 218 displays the search result list on the screen.

  FIG. 27 is a functional block diagram of the map search server 202 in FIG. 25, and components that are substantially the same as those in FIG. 3 are given the same reference numerals. The bounce data acquisition unit 230 differs from the bounce data acquisition unit 66 in FIG. 3 in that the URL of the search engine 206 is added to the bounce data for acquisition.

  The bounce data response unit 234 in the transmission unit 232 is different from the bounce data response unit 90 in FIG. 3 in that it responds by adding the URL of the search engine 206 to the bounce data.

  FIG. 28 is a logical configuration diagram of the bounce DB 204 in FIG. As shown in FIG. 28 (a), the bounce DB 204 includes the URL of the search engine 206 as shown in FIG. 28 (b) in addition to substantially the same components as the bounce DB 12 in FIG. Is set. FIG. 29 is a process flowchart of the terminal device 200. FIG. 30 is a process flowchart of the map search server 202. FIG. 31 is a sequence chart. FIG. 32 shows a display example of a search result list. Hereinafter, the processing of the map search system 198 will be described with reference to these drawings.

  The processes in steps S152 to S162 in FIG. 29 are the same as the processes in steps S22 to S32 in FIG. Also, the processing of steps S188 to S206 in FIG. 30 is the same as the processing of steps S48 to S66 in FIG. (100) to (108) in FIG. 31 are the same as the sequences (2) to (8) in FIG.

  The map search server 202 searches the bounce DB 204 in step S208 in FIG. 30, but searches the URL of the search engine 206 in addition to the search process of the bounce DB 12 in step S68. In step S210, the URL of the search engine 206 is acquired in addition to the bounce data similar to step S70.

  In step S212, in addition to the bounce data response in step S72, the URL of the search engine 206 is transmitted to the terminal device 200 as a bounce data response, as indicated by (110) in FIG.

  In step S164 in FIG. 29, the terminal device 200 receives a bounce data response in which the URL of the search engine 206 is added to the response similar to step S32 in FIG. In steps S166 to S170, processing similar to that in steps S36 to S42 in FIG. 14 is performed.

  It is assumed that the note display area on the bounce data is clicked. In step S178, the URL of the search engine 206 and the clicked note are designated as search keywords, and a request is made to the search engine 206 as indicated by (116) in FIG.

  The search engine 206 searches according to the search keyword, and responds with a search result list as indicated by (118) in FIG. In step S180, a search result list response is received. In step S182, a search result list is displayed as shown at (120) in FIG. For example, when the note is an AB hotel, when the note display area on the bounce data related to this note is clicked, the AB hotel is designated as a search keyword, the search engine 206 is requested to search, and the search engine 206 searches. When the result list response is received, for example, as shown in FIG. 32, an arrow pointing to the note AB hotel on the map image data displayed on the map screen is displayed, and the bounce data is displayed separately from the map display area. A search result list is displayed below the area. The user can display the desired page by clicking the desired page in the search result list. Thus, the user can search for information related to the note without directly accessing the search engine 206 and inputting a search keyword.

  When the note display area on the map image data is clicked, the note character string on the bounce data related to the note included in the note display area is designated as a search key, and a search is requested to the search engine 206. Also good.

  According to the third embodiment described above, in addition to the effects of the first embodiment, when a user clicks on a note without copying and pasting, a search request is sent to the search engine 206 using the note as a search key. As a result, the user operability is further improved.

Fourth Embodiment FIG. 33 is a block diagram of a map search system 248 according to a fourth embodiment of the present invention. Components that are substantially the same as those in FIG. 1 are given the same reference numerals. . The description of the components having the same reference numerals is omitted.

  In the present embodiment, for each type of facility or the like to be annotated, the URL of the service server 256 # i (i = 1 to n) as a WWW server that provides information in the field corresponding to the type is the bounce data response. When a predetermined area of the note display area on the bounce data is clicked, it corresponds to the URL set according to the type of the note. The point which makes the request to the service server 256 differs from 1st Embodiment.

  When the note display area on the bounce data is clicked, the terminal device 250 # i (i = 1 to n) specifies the URL corresponding to the clicked note type, and the corresponding service server 256 # i ( It differs from the terminal device 2 # i (i = 1 to n) in FIG. 1 in that the information provision is requested to i = 1 to n). The bounce DB 254 is different from the bounce DB 12 in FIG. 1 in that the URL of the service server 256 # i (i = 1 to n) is set according to the note ID representing the type of note.

  The map search server 252 responds to the terminal device 250 with the URL of the service server 256 # i (i = 1 to n) corresponding to the type of note in addition to the bounce data of the first embodiment. Different from the map search server 6 in FIG. The service server 256 # i (i = 1 to n) is a WWW server that provides information on fields such as health, travel, and gourmet.

  FIG. 34 is a functional block diagram of the terminal device 250 in FIG. 32, and components that are substantially the same as those in FIG. 2 are given the same reference numerals. When the type-specific service server request unit 262 in the request unit 260 is clicked on a predetermined region of the note display region on the bounce data, for example, the note type name corresponding to the note ID displayed by the bounce data display unit 52, The bounce data of the corresponding note is obtained from the position on the screen of the note display area, the URL set for the note ID of the bounce data is designated, and the corresponding service server 256 is requested to transmit the page.

  The type-specific service server response receiver 266 in the response receiver 264 receives a page as a response from the service server 256. The response page display unit 270 in the data display unit 268 displays the page received by the type-specific service server response reception unit 266 on the screen.

  FIG. 35 is a functional block diagram of the map search server 252 in FIG. 33, and constituent elements substantially the same as those in FIG. 3 are given the same reference numerals. The bounce data acquisition unit 270 differs from the bounce data acquisition unit 66 in FIG. 3 in that the URL of the service server 256 is acquired for each note ID as the bounce data.

  The bounce data response unit 274 in the transmission unit 272 is different from the bounce data response unit 90 in FIG. 3 in that the URL of the service server 256 for each note ID is added to the bounce data.

  FIG. 36 is a logical configuration diagram of the bounce DB 254 in FIG. As shown in FIG. 36 (a), the bounce DB 254 is added to substantially the same components as the bounce DB 12 in FIG. 8, and for each map image file ID as shown in FIG. 36 (b). The URL of the service server 256 is set for the note ID.

  If the note is a hospital, the URL of the hospital related information, the travel related information if it is a hotel or inn, and the URL of the gourmet information search server 256 if it is the restaurant name are set. In addition, when there is no service server that provides information regarding the field related to the note, the URL of a WWW server such as a search engine is set.

  Here, the bounce data (first record) shown in FIG. 36 (a) is stored in the first file, and the bounce data (second record) shown in FIG. 36 (b) is stored in the second file. By physically separating the second file and building it separately, it is easy to add or change URLs, and the maintainability of the database is improved. Note that a URL attribute may be added to the bounce DB 252 shown in FIG. 36A, and a link destination URL as an attribute value may be set in the attribute.

  FIG. 37 is a process flowchart of the terminal device 250. FIG. 38 is a process flowchart of the map search server 252. FIG. 39 is a sequence chart. Hereinafter, the processing of the map search system 248 will be described with reference to these drawings.

  The processing in steps S252 to S262 in FIG. 37 is the same as the processing in steps S22 to S32 in FIG. Also, the processing of steps S288 to S306 in FIG. 38 is the same as the processing of steps S48 to S66 in FIG. (130) to (138) in FIG. 39 are the same as the sequences (2) to (8) in FIG.

  In step S308, the map search server 252 searches the bounce DB 254. In addition to the search process of the bounce DB 12 in step S68, the map search server 252 searches for the URL using the note ID included in the bounce data as a search key.

  In step S310, the URL for the note ID is acquired in addition to the bounce data similar to that in step S70. In step S312, in addition to the bounce data in step S72, the URL for the note ID is transmitted to the terminal device 250 as a bounce data response, as indicated by (140) in FIG.

  In step S264 in FIG. 37, the terminal device 250 receives a bounce data response in which a URL for the note ID is added to the bounce data similar to step S32 in FIG. In steps S266 to S270, processing similar to that in steps S36 to S40 in FIG. 14 is performed.

  It is assumed that a predetermined area of the note display area on the bounce data, for example, a note type name corresponding to the note ID is clicked. In step S278, the URL for the note ID of the bounce data of the corresponding note is acquired from the display coordinates of the clicked note display area, and as indicated by (146) in FIG. 39, the URL for the note ID of the bounce data is obtained. A URL is specified and a request is made to the service server 256.

  The service server 256 responds to the page as indicated by (148) in FIG. In step S280, the responded page is received. In step S282, a page is displayed as indicated by (150) in FIG.

  According to the fourth embodiment described above, in addition to the effects of the first embodiment, since the request is made to the service server that provides information according to the type of the clicked note, the user simply clicks on information in the relevant field. Can be easily obtained, and the operability for the user is improved.

1 is a schematic configuration diagram of a map search system according to a first embodiment of the present invention. It is a functional block diagram of the terminal device in FIG. It is a functional block diagram of the map search server in FIG. It is a block diagram of map index DB in FIG. It is a figure which shows the correspondence of map DB and bounce DB. It is a figure which shows the relationship between the note on map image data, and the note on bounce data. It is a block diagram of map DB. It is a logical block diagram of a bounce DB. It is a figure which shows the preparation methods of bounce DB. It is a figure which shows the relationship between a map image file and a bounce file. It is explanatory drawing of the bounce data in case a note has protruded. It is a figure which shows an example of map image data. It is a figure which shows an example of bounce data. It is an operation | movement flowchart of a terminal device. It is an operation | movement flowchart of a map search server. It is a sequence chart of a 1st embodiment of the present invention. It is a figure which shows the example of a display of bounce data. It is a schematic block diagram of the map search system by 2nd Embodiment of this invention. It is a functional block diagram of the terminal device in FIG. It is a functional block diagram of the map search server in FIG. It is a logical block diagram of a bounce DB. It is an operation | movement flowchart of a terminal device. It is an operation | movement flowchart of a map search server. It is a sequence chart of a 2nd embodiment of the present invention. It is a schematic block diagram of the map search system by 3rd Embodiment of this invention. It is a functional block diagram of the terminal device in FIG. It is a functional block diagram of the map search server in FIG. It is a logical block diagram of a bounce DB. It is an operation | movement flowchart of a terminal device. It is an operation | movement flowchart of a map search server. It is a sequence chart of a 3rd embodiment of the present invention. It is a figure which shows an example of a search result list. It is a schematic block diagram of the map search system by 4th Embodiment of this invention. It is a functional block diagram of the terminal device in FIG. It is a functional block diagram of the map search server of FIG. It is a logical block diagram of a bounce DB. It is an operation | movement flowchart of a terminal device. It is an operation | movement flowchart of a map search server. It is a sequence chart of a 4th embodiment of the present invention.

Explanation of symbols

2,140,200,250 Terminal device 4 Communication network 6,150,202,252 Map search server 8 Map index DB
10 Map DB
12,152,204,254 Bounce DB
14 WWW server 206 Search engine 256 Various service servers

Claims (15)

A map search server,
A map image that divides the entire map into a plurality of mesh-like blocks, has a data structure hierarchized into a plurality of stages with different block sizes according to the scale, and includes a plurality of notes for the map of each block A map database including a plurality of map image files for storing data together with position coordinates;
There is a one-to-one correspondence with the map image file for the map of the block, and the note character strings of all or some of the notes stored in the map image file have the same scale as the map of the block. A bounce database that stores the position coordinates described in the note coordinate space as bounce data together with the note character string;
A map image data response unit that responds to the map image data stored in the corresponding map image file based on a request to send map image data;
A bounce data response unit that responds to the bounce data stored in the bounce database, corresponding to the map image file in which the map image data to which the map image data response unit has responded is stored,
A map search server.   Each of the bounce data includes a bounce identifier that uniquely identifies the note among the notes defined in the plurality of notes stored in the corresponding map image file, the note character string, and the note character string. The map search server according to claim 1, comprising: a first record including position coordinates; and a second record including data relating to a link destination to a server that provides information relating to the note regarding the bounce identifier.   Each of the bounce data includes a first record that includes the note character string, a position coordinate of the note character string, and a note identifier that identifies a type of facility or store represented by the note character string, and the note identifier for each note identifier. The map search server of Claim 1 containing the 2nd record containing the data regarding the link destination to the server which provides the information regarding the facility or shop which represents.   The map search server according to claim 2 or 3, wherein the first record and the second record are physically stored in separate files.   The map search server according to claim 1, wherein the bounce data response unit includes, in the response, data related to a link destination to a search engine that provides information related to the search keyword based on the search keyword.   When the note character string of the bounce data is interrupted from the map of the block corresponding to the bounce data, the position coordinates described in the note coordinate space including the note character string of the same scale as the block are the bounce data. The map search server according to claim 1, wherein the map search server is stored as data in the bounce database. A map search system having a terminal device and a map search server to which the terminal device is connected via a communication network,
The map search server
A map image that divides the entire map into a plurality of mesh-like blocks, has a data structure hierarchized into a plurality of stages with different block sizes according to the scale, and includes a plurality of notes for the map of each block A map database including a plurality of map image files for storing data together with position coordinates;
There is a one-to-one correspondence with the map image file for the map of the block, and the note character strings of all or some of the notes stored in the map image file have the same scale as the map of the block. A bounce database that stores the position coordinates described in the note coordinate space as bounce data together with the note character string;
A map image data response unit that responds to the map image data stored in the corresponding map image file based on a request to send map image data;
A bounce data response unit that responds to the bounce data stored in the bounce database, corresponding to the map image file in which the map image data to which the map image data response unit has responded is stored,
The terminal device
A map image data request unit that requests the map search server to transmit map image data stored in the corresponding map image file, based on position information;
A map image data response receiving unit for receiving the map image data responded from the map image data response unit;
A bounce data response receiver for receiving bounce data responded by the bounce data response unit;
A map search system comprising a map image data display unit for displaying the map image data at a screen position corresponding to the position coordinates of the map image data received by the map image data response receiving unit.   When a predetermined operation is performed on the display area of the screen designated by the cursor designated by the input means, the cursor is included in the map image data based on the position coordinates of the note character string of the bounce data. A predetermined display area is determined, it is determined whether or not the bounce data related to the note is defined. If the bounce data is defined, the note including the note character string of the bounce data is defined. The map search system according to claim 7, further comprising a bounce data display unit that displays the data according to the above on the screen.   The terminal device copies the note character string to a buffer memory based on a predetermined operation by an input unit with respect to a display area of the note character string included in the data displayed by the bounce data display unit. The map search system according to claim 8, further comprising a copy and paste control unit for pasting the note character string copied to the memory. Each of the bounce data includes a bounce identifier that uniquely identifies the note among the notes defined in the plurality of notes stored in the corresponding map image file, the note character string, and the note character string. A first record that includes position coordinates; and a second record that includes data relating to a link destination to a server that provides information about the note for the bounce identifier;
When the terminal device performs a predetermined operation on the display area of the data related to the note displayed by the bounce data display unit by an input unit, the terminal device relates to the link destination for the bounce identifier of the bounce data related to the note The map search system according to claim 8, wherein, when data is set, the server requests the server to provide information related to the note.   The terminal device, when a predetermined operation is performed after the cursor pointed by the input unit is stopped in the display area of the data related to the note displayed by the bounce data display unit, the bounce data related to the note When the first link destination is set for the bounce identifier, the first request unit that requests the server to provide detailed information regarding the note based on the first link destination, and the cursor pointed by the input means is the bounce When a predetermined operation overlapping the display area of the data related to the note displayed by the data display unit is performed, when the second link destination is set for the bounce identifier of the bounce data related to the note, A second request unit that requests the server to provide detailed information on the note based on the second link destination; Map system of claim 8, equipped is provided. Each of the bounce data includes a first record that includes the note character string, a position coordinate of the note character string, and a note identifier that identifies a type of facility or store represented by the note character string, and the note identifier for each note identifier. A second record including data relating to a link destination to a server that provides information on the facility or store indicated by
When the terminal device performs a predetermined operation on the display area of the data related to the note displayed by the bounce data display unit indicated by the cursor indicated by the input unit, the note of the bounce data related to the note is displayed. The map search system according to claim 8, further comprising: a request unit that requests a server to provide information related to the facility or store of the note based on the link destination when the link destination is set for the identifier. The bounce data response unit includes, in the response, information related to a search engine that searches for information related to the search keyword based on the search keyword.
In the terminal device, when a predetermined operation is performed in the display area of the data related to the note displayed by the bounce data display unit indicated by the cursor indicated by the input means, or the cursor indicated by the input means The search engine is requested to perform a search using a note character string of bounce data related to the note as a search keyword when a predetermined operation is performed in a predetermined display area of the note included in the indicated map image data. 7. The map search system according to 7. A map search method,
Requesting transmission of map image data corresponding to the position information based on the position information;
Based on the request, the entire map is divided into a plurality of mesh-like blocks, and has a data structure hierarchized in a plurality of stages in which the sizes of the blocks differ according to the scale. Reading out map image data corresponding to the position information from a map database including a plurality of map image files storing map image data including the position coordinates together with position coordinates, and transmitting as a response;
Receiving the map image data transmitted as the response;
Requesting transmission of bounce data corresponding to the map image file in which the map image data transmitted as the response is stored;
There is a one-to-one correspondence with the map image file for the map of the block, and the note character strings of all or some of the notes stored in the map image file are the same scale as the map of the block. Reading the bounce data corresponding to the responded map image data from the bounce database storing the position coordinates described in the note coordinate space as the bounce data together with the note character string, and transmitting as a response;
Receiving the bounce data transmitted as the response;
Displaying the map image data on a screen at a position corresponding to the position coordinates of the map image data;
A map search method comprising:   The map image data included in each map image file is stored in a map intermediate file in which map data excluding notes is stored, and a note intermediate file that stores coordinate coordinates and size data of a note created based on the map data. The map search method according to claim 14, wherein the position coordinates of the note character string of the bounce data are generated based on the coordinates and size of the note stored in the note intermediate file.

Images