Bus station data processing method, electronic device and program product

Abstract

This disclosure provides a method, electronic device, and program product for processing bus stop data. The method includes acquiring bus stop data, which includes the location of the bus stop and at least one of the following: bus stop name and bus route information on the bus stop; aggregating the bus stop data to obtain bus stop data, which includes at least one of the following: bus stop platform area and bus stop data within the bus stop, with the platform platform area covering the locations of the bus stops within the bus stop; and sending the target bus stop data to the client according to a request for target bus stop data sent by the client, so that the client can display the target bus stop data. This technical solution can fundamentally reduce the problem of wasted capacity, improve the accuracy of production data, and the increased bus stop platform data enhances user awareness of the bus stop area. The increased bus stop data within the bus stop refines the granularity of the bus stop display down to the bus stop itself, making bus stop navigation more accurate for users.

Description

Technical Field

[0001] This disclosure relates to the field of big data technology, specifically to a method for processing bus station data, electronic equipment, and software products. Background Technology

[0002] In recent years, with the rapid development of the internet, people have become increasingly accustomed to using electronic maps to search for their destinations and the bus routes and stops they need to choose when traveling. Bus stops refer to vehicle parking areas within a certain range, and are aggregated based on existing vehicle stop locations. Current vehicle stop locations are obtained through both line-based data collection (data collection personnel ride the bus and collect data at the door) and point-based data collection (data collection personnel collect data at the bus stop sign). Due to differences in collection methods and accuracy, the stop location for the same bus route at the same bus stop can change repeatedly, resulting in significant accuracy deviations. Furthermore, multiple bus routes typically exist under the same bus stop, and each route requires the collection of its corresponding stop location, leading to redundant data processing. This results in significant wasted processing capacity and low accuracy when aggregating and generating stop data. Furthermore, when users search for bus stops, the electronic map only displays one bus stop location to represent that bus stop. However, for large bus stops such as hub stations or long bus stops, the area of ​​the bus stop is very large, including stops for multiple bus routes. This can lead to a significant discrepancy between the bus stop location displayed when users search for stops and the actual bus stop location where users board the bus. This can cause users to miss the bus because they cannot board the bus at the correct location in time, causing inconvenience to them. Summary of the Invention

[0003] To address the problems in the related technologies, this disclosure provides a bus stop data processing method, electronic device, and program product.

[0004] Firstly, this disclosure provides a method for processing bus stop data.

[0005] Specifically, the bus stop data processing method includes:

[0006] Acquire station data, which includes station location and at least one of the following: station name, bus route information on the station;

[0007] Platform data is obtained by aggregating the station pile data. The platform data includes at least one of the following: platform surface area and station pile data within the platform. The platform surface area covers the station pile locations within the platform.

[0008] Based on the platform data request sent by the client for the target platform, the platform data of the target platform is sent to the client so that the client can display the platform data of the target platform.

[0009] In one possible implementation, acquiring the pile data includes:

[0010] Based on historical station data, obtain initial station data;

[0011] Obtain actual pile data;

[0012] The initial pile data is updated based on the actual pile data to obtain the updated pile data.

[0013] In one possible implementation, the method further includes:

[0014] Based on the station data, a route between two stations that meet preset conditions is generated, and the route between stations corresponding to each bus route is obtained. The preset conditions include that the two stations are adjacent stations on the same bus route.

[0015] In response to receiving a bus route request from a client, the system determines the bus route requested in the bus route request, the bus route including connected inter-station routes;

[0016] The bus route is sent to the client so that the client can display the bus route.

[0017] In one possible implementation, the bus route request is a bus route navigation request, including a navigation start point and a navigation destination, and the method further includes:

[0018] If the bus route includes at least two bus routes, then the transfer type between the two adjacent bus routes is determined. The transfer type includes transfers at the same platform and at the same bus stop, and transfers at the same platform but at different bus stops.

[0019] The transfer type between two adjacent bus routes in the bus route is sent to the client so that the client can display the transfer type between the two adjacent bus routes in the bus route.

[0020] In one possible implementation, the method further includes:

[0021] In response to receiving a navigation request from a client in non-public transport navigation mode, if the navigation destination of the navigation request is a target station, the system returns the station data within the target station to the client, allowing the client to display the station data within the target station for the user to select the target station as the actual destination.

[0022] Secondly, this disclosure provides a method for processing bus stop data.

[0023] Specifically, the bus stop data processing method is applied to the client side and includes:

[0024] The system receives platform data of a target platform sent by the server. The platform data includes at least one of the following: platform surface area and station data of the station bollards within the platform. The platform surface area covers the station bollard locations within the platform. The station bollard data includes the station bollard location and at least one of the following: station bollard name and bus route information on the station bollard.

[0025] Display the platform surface of the target station and / or the pile data of the piles within the target station.

[0026] In one possible implementation, the platform data includes platform surface area and station pile data within the platform, wherein displaying the platform surface and / or station pile data of the target platform includes:

[0027] In response to receiving the initial display command for the platform, the platform surface of the target platform is displayed;

[0028] In response to the command to obtain detailed platform information, the platform surface of the target platform and the pile data of the piles within the target platform are displayed.

[0029] In one possible implementation, the method further includes:

[0030] In response to receiving the bus route retrieval instruction, a bus route request is sent to the server;

[0031] The system receives the requested bus route from the server, which includes connecting routes between stations.

[0032] The bus route is displayed.

[0033] In one possible implementation, the bus route request is a bus route navigation request, including a navigation start point and a navigation destination, and the method further includes:

[0034] If the bus route includes at least two bus lines, then the transfer type between two adjacent bus lines in the bus route is received and displayed. The transfer type includes same-platform same-station transfer and same-platform different-station transfer.

[0035] In one possible implementation, the method further includes:

[0036] In response to receiving a navigation instruction in non-public transport navigation mode, a navigation request in non-public transport navigation mode is sent to the server.

[0037] If the navigation destination of the navigation request is the target station, then the station data within the target station returned by the server is received;

[0038] Display the options corresponding to the station pile data within the target station;

[0039] In response to receiving a selection instruction for the option, navigation is performed with the location of the target station selected by the selection instruction as the actual destination.

[0040] Thirdly, this disclosure provides a bus stop data processing device.

[0041] Specifically, the bus stop data processing device includes:

[0042] The first acquisition module is configured to acquire station data, which includes the station location and at least one of the following: station name and bus route information on the station.

[0043] The aggregation module is configured to aggregate the station pile data to obtain platform data, wherein the platform data includes at least one of the following: platform surface area and station pile data within the platform, wherein the platform surface area covers the station pile positions within the platform.

[0044] The first sending module is configured to send the station data of the target station to the client based on the station data request sent by the client for the target station, so that the client can display the station data of the target station.

[0045] In one possible implementation, the first acquisition module is configured as follows:

[0046] Based on historical station data, obtain initial station data;

[0047] Obtain actual pile data;

[0048] The initial pile data is updated based on the actual pile data to obtain the updated pile data.

[0049] In one possible implementation, the device further includes:

[0050] The second acquisition module is configured to generate inter-station routes between two station posts that meet preset conditions based on the station post data, and to acquire the inter-station routes corresponding to each bus route. The preset conditions include that the two station posts are adjacent station posts on the same bus route.

[0051] The first determining module is configured to, in response to receiving a bus route request sent by a client, determine the bus route requested in the bus route request, the bus route including a series of inter-station routes.

[0052] The second sending module is configured to send the bus route to the client so that the client can display the bus route.

[0053] In one possible implementation, the bus route request is a bus route navigation request, including a navigation start point and a navigation destination, and the device further includes:

[0054] The second determining module is configured to determine the transfer type of two adjacent bus routes if the bus route includes a route of at least two bus lines. The transfer type includes same-platform same-station transfer and same-platform different-station transfer.

[0055] The third sending module is configured to send the transfer type of two adjacent bus routes in the bus route to the client so that the client can display the transfer type of the two adjacent bus routes in the bus route.

[0056] In one possible implementation, the device further includes:

[0057] The fourth sending module is configured to respond to a navigation request sent by a client in non-public transport navigation mode. If the navigation destination of the navigation request is a target station, the module returns the station data within the target station to the client, so that the client can display the station data within the target station for the user to select a station as the actual destination.

[0058] Fourthly, this disclosure provides a bus stop data processing device.

[0059] Specifically, the bus stop data processing device is applied to the client side and includes:

[0060] The first receiving module is configured to receive platform data of the target platform sent by the server. The platform data includes at least one of the following: platform surface area, station data of the station bollards within the platform, wherein the platform surface area covers the station bollard positions within the platform, and the station bollard data includes the station bollard position and at least one of the following: station bollard name, and bus route information on the station bollard.

[0061] The first display module is configured to display the platform surface of the target platform and / or the pile data of the piles within the target platform.

[0062] In one possible implementation, the platform data includes platform surface area and station pile data within the platform, and the first display module is configured to:

[0063] In response to receiving the initial display command for the platform, the platform surface of the target platform is displayed;

[0064] In response to the command to obtain detailed platform information, the platform surface of the target platform and the pile data of the piles within the target platform are displayed.

[0065] In one possible implementation, the device further includes:

[0066] The fifth sending module is configured to send a bus route request to the server in response to receiving a bus route retrieval instruction.

[0067] The second receiving module is configured to receive the bus route requested by the bus route request returned by the server, the bus route including a series of inter-station routes.

[0068] The second display module is configured to display the bus route.

[0069] In one possible implementation, the bus route request is a bus route navigation request, including a navigation start point and a navigation destination, and the device further includes:

[0070] The receiving and display module is configured to receive and display the transfer type of two adjacent bus routes in the bus route if the bus route includes a route with at least two bus lines. The transfer type includes same-platform same-station transfer and same-platform different-station transfer.

[0071] In one possible implementation, the device further includes:

[0072] The sixth sending module is configured to send a navigation request in non-public transport navigation mode to the server in response to receiving a navigation instruction in non-public transport navigation mode.

[0073] The third receiving module is configured to receive the station data within the target station returned by the server if the navigation destination of the navigation request is the target station.

[0074] The third display module is configured to display the station pile options corresponding to the station pile data within the target station platform;

[0075] The navigation module is configured to respond to receiving a selection instruction for the station option and navigate with the station location of the target station selected by the selection instruction as the actual destination.

[0076] Fifthly, embodiments of this disclosure provide an electronic device including a memory and a processor, wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method as described in any one of the first or second aspects.

[0077] In a sixth aspect, embodiments of this disclosure provide a computer-readable storage medium having computer instructions stored thereon that, when executed by a processor, implement the method as described in any one of the first or second aspects.

[0078] In a seventh aspect, this disclosure provides a computer program product including computer instructions that, when executed by a processor, implement the method steps as described in any one of the first or second aspects.

[0079] Eighthly, this disclosure provides a navigation method in which a navigation route is obtained based on at least a starting point, an ending point, and station data; navigation guidance is performed based on the navigation route; and the station data is processed based on either the first or second aspect of the method.

[0080] According to the technical solution provided in this disclosure, bus stops can be aggregated from station data to obtain bus platforms. When displaying bus stops, the platform surface of the bus stop can be displayed, or the platform surface and station data of the station stops within the bus stop can be displayed. Since the number of station stops for each bus stop is usually less than the number of bus routes and the station stop positions remain unchanged, aggregating bus stops from station data to obtain bus stops can fundamentally reduce the problem of wasted production capacity and improve the accuracy of production data. Moreover, the obtained bus stop data increases the platform surface, which can improve the user's understanding of the bus stop area. Increasing the station stop data within the bus stop refines the granularity of the bus stop display to the station stops, making the user's bus stop navigation more accurate.

[0081] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0082] Other features, objects, and advantages of this disclosure will become more apparent from the following detailed description of non-limiting embodiments, taken in conjunction with the accompanying drawings. In the drawings:

[0083] Figure 1A A flowchart illustrating a bus stop data processing method according to an embodiment of the present disclosure is shown.

[0084] Figure 1B A schematic diagram illustrating a display scenario of platform data according to an embodiment of the present disclosure is shown;

[0085] Figure 1C A schematic diagram showing a pile data acquisition interface according to an embodiment of the present disclosure;

[0086] Figure 1D A schematic diagram showing a bus stop on a bus route according to an embodiment of the present disclosure is provided.

[0087] Figure 2 A flowchart illustrating a bus stop data processing method according to an embodiment of the present disclosure is shown.

[0088] Figure 3 A schematic diagram of an application scenario system for bus stop data according to an embodiment of the present disclosure is shown.

[0089] Figure 4 A structural block diagram of a bus stop data processing apparatus according to an embodiment of the present disclosure is shown.

[0090] Figure 5 A structural block diagram of a bus stop data processing apparatus according to an embodiment of the present disclosure is shown.

[0091] Figure 6 A structural block diagram of an electronic device according to an embodiment of the present disclosure is shown;

[0092] Figure 7 A schematic diagram of the structure of a computer system suitable for implementing the method according to embodiments of the present disclosure is shown. Detailed Implementation

[0093] In the following, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings to enable those skilled in the art to readily implement them. Furthermore, for clarity, portions unrelated to the description of exemplary embodiments have been omitted from the drawings.

[0094] In this disclosure, it should be understood that terms such as “comprising” or “having” are intended to indicate the presence of features, figures, steps, behaviors, components, parts or combinations thereof disclosed in this specification, and are not intended to exclude the possibility of the presence or addition of one or more other features, figures, steps, behaviors, components, parts or combinations thereof.

[0095] It should also be noted that, unless otherwise specified, the embodiments and features described in this disclosure can be combined with each other. This disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0096] In this disclosure, the acquisition of user information or user data is done with the user's authorization or confirmation, or by the user's active choice.

[0097] As mentioned above, in recent years, with the rapid development of the internet, people have gradually become accustomed to using electronic maps to search for their destinations and the bus routes and stops they need to choose when traveling. Bus stops refer to vehicle parking areas within a certain range, and are all aggregated based on vehicle stop locations. Existing vehicle stop locations are obtained through line collection (data collection personnel ride the bus and collect data at the door) and point collection (data collection personnel collect data at the bus stop sign). Due to differences in collection methods and accuracy, the stop location for the same bus route at the same bus stop can change repeatedly, resulting in large accuracy deviations. Furthermore, multiple bus routes usually exist under the same bus stop, and each bus route requires the collection of corresponding vehicle stop locations, leading to redundant data processing. This results in significant wasted production capacity and low accuracy when aggregating and generating stop data. Furthermore, when users search for bus stops, the electronic map only displays one bus stop location to represent that bus stop. However, for large bus stops such as hub stations or long bus stops, the area of ​​the bus stop is very large, including stops for multiple bus routes. This can lead to a significant discrepancy between the bus stop location displayed when users search for stops and the actual bus stop location where users board the bus. This can cause users to miss the bus because they cannot board the bus at the correct location in time, causing inconvenience to them.

[0098] This disclosure provides a bus stop data processing method that aggregates bus stop data to obtain bus stops and displays the bus stop platform or the platform surface and the station stake data within the platform. Since the number of station stakes at each bus stop is usually less than the number of bus routes and the station stake positions remain unchanged, aggregating bus stops from station stake data can fundamentally reduce the problem of wasted capacity and improve the accuracy of production data. Moreover, the obtained bus stop data, by adding the bus stop platform, can enhance users' understanding of the bus stop area, and by adding the station stake data within the platform, the granularity of the bus stop display is refined to the station stake, making user navigation to the bus stop more accurate.

[0099] Figure 1A A flowchart illustrating a bus stop data processing method according to an embodiment of the present disclosure is shown. Figure 1A As shown, the bus stop data processing method includes the following steps S101-S103:

[0100] In step S101, station data is obtained, which includes station location and at least one of the following: station name and bus route information on the station;

[0101] In step S102, platform data is obtained by aggregating the station pile data. The platform data includes at least one of the following: platform surface area and station pile data within the platform. The platform surface area covers the station pile positions within the platform.

[0102] In step S103, the platform data of the target platform is sent to the client according to the platform data request sent by the client for the target platform, so that the client can display the platform data of the target platform.

[0103] In one possible implementation, the bus stop data processing method is applicable to a server capable of performing bus stop data processing, the server including a computer, computing device, electronic device, server, service cluster, etc.

[0104] In one possible implementation, the bus stop in this disclosure includes a stop for any type of public transport, such as buses, light rail, subways, etc., and each bus stop may have multiple bus routes stopping there. The bus stop may include at least one bollard, which is a public transport facility used to indicate the stopping location of the corresponding bus to users; for example, the bollard may be a bus stop sign.

[0105] In one possible implementation, the station marker data may include, in addition to the station marker location, one or both of the station marker name and bus route information on the station marker. The station marker name refers to the name of the station indicated by the station marker, and the bus route information on the station marker refers to the relevant information of the bus route operated by the bus indicated by the station marker. For example, if the station marker is a bus stop sign, the name of the station displayed on the bus stop sign is recorded as the station marker name; the bus route name displayed on the bus stop sign, such as Line X or Bus Route N, is the bus route information on the station marker.

[0106] In one possible implementation, station posts that meet aggregation criteria can be aggregated together to form a bus stop based on station post data. For example, based on the location of each station post, the distance between them and the road where the station post is located (e.g., on a main road or auxiliary road) can be obtained. The direction of the bus routes can be obtained based on the bus routes on the station posts. The aggregation criteria can be to aggregate station posts with the same direction of bus routes, distances between them within a preset range, similar names, and that do not cross intersections. After the bus stop is formed, the bus stop data can be obtained. This bus stop data includes the bus stop surface area and / or the station post data within the bus stop. Of course, the bus stop data may also include the bus stop location point, bus stop name, etc. The platform surface area can cover the positions of all the station piles aggregated within the platform; the platform location point is located within the platform surface area, for example, it can be located in the middle of the platform surface area; if all the station piles aggregated within the platform have the same name, then the platform name can be the name of the station piles within the platform; if the station piles aggregated within the platform have different names, then the platform name can be the same name of all the station piles within the platform. For example, if the name of station pile 1 is XX1 station and the name of station pile 2 is XX2 station, then the platform name can be XX station.

[0107] In one possible implementation, after the server aggregates the station data for each station, if it receives a station data request from a client for a target station, it can send the target station data to the client. Upon receiving the target station data, the client can display it. In one scenario, a user might use the client to search for a station A, which is the target station. In this case, the client can send a station data request to the server for station A's data. The server can respond by receiving the request and sending the station data for station A to the client: the station surface area and the station stake data within the station. After receiving the station data for station A, the client can display the station surface area and station stake data for station A on a map. In another scenario, a user might use a client to download map data for a specific geographic area for offline use. This map data includes station data for each station within that area. The client then sends a station data request to the server, requesting station data for each station within the geographic area. In this scenario, the target stations can be any station within the geographic area. After sending the station data for each station within the geographic area to the client, the server can also proactively send station data for certain stations to the client. For example, when the server detects the client is online, it might send the station data for certain stations within the geographic area to the client when their data is updated. In this case, the target stations are multiple stations within the map area whose data has been updated.

[0108] In one possible implementation, when displaying station data for a target station, in addition to displaying the station location and name, if the station data includes the station platform area, the client can display the station platform itself. If the station data includes station bollard data within the station, the client can display the location, name, and bus route information of each station bollard within the target station. If the station data includes both the station platform area and the station bollard data, the client can display either the station platform itself or both the station platform and the station bollard data as needed. Specific display schemes are described in the client-side embodiments.

[0109] Example, Figure 1B This diagram illustrates a display scenario of platform data according to an embodiment of the present disclosure. It is assumed that the platform data received by the client includes the platform location point, platform name, platform surface area, and station stake data within the platform, such as... Figure 1BAs shown, when the client displays platform data for station XXX, it can display a rectangular surface 11 as the platform surface of station XXX, a platform icon 12 at the platform location, the platform name "XXX Station" above the platform icon 12, station bollard icons 13 at the locations of each bollard within the platform surface, and a bus route text box 14 near the bollard icon 13, displaying the bus route name of that bollard. If in other examples the bollard name differs from the platform name, the corresponding bollard name can be displayed on the bollard icon 13. Of course, Figure 1B This is just one example of how platform data can be displayed. The display methods for each piece of data in this platform data can be varied, and will not be illustrated here.

[0110] In this embodiment, the basic unit for generating bus stop data is the bus stop marker. Compared with existing vehicle stops, the number of bus stop markers is smaller and their locations are fixed, which can reduce the problem of wasted capacity. Moreover, the station data aggregated from this bus stop marker data is more accurate. In addition, the generated station data also includes the bus stop marker data of the station platform area and / or the bus stop marker data within the station. The added station platform area can improve users' awareness of the station area, allowing them to plan their time in advance and avoid missing the bus. The added bus stop marker data within the station can refine the granularity of the station display down to the bus stop marker, making the user's station navigation more accurate.

[0111] In one possible implementation, step S101 of the above-described bus stop data processing method, namely, acquiring bus stop data, can also be implemented as the following steps:

[0112] Based on historical station data, obtain initial station data;

[0113] Obtain actual pile data;

[0114] The initial pile data is updated based on the actual pile data to obtain the updated pile data.

[0115] In this implementation, when the bus stop data processing method is implemented on the server side, due to the existence of a massive number of bus stop markers, it is not possible to collect all the bus stop data quickly. In order to implement this method quickly, the initial bus stop data can be inherited from the latest historical bus stop data. That is, the historical bus stop location in the historical bus stop data is used as the initial bus stop location, the historical bus stop name is used as the initial bus stop name, and the bus route information corresponding to the historical bus stop is used as the bus route information on the initial bus stop.

[0116] In this implementation, the server can obtain the actual station data collected by the data acquisition terminal. This actual station data can be point-based data, that is, data collected by the data acquisition personnel holding the data acquisition terminal at the actual location of the station. For example, Figure 1CThe diagram illustrates a data acquisition interface for pile foundations according to an embodiment of the present disclosure. The acquisition terminal has a positioning function; when the acquisition personnel reach the actual location of a pile foundation, they click the acquisition button, and the acquisition terminal can locate the position of the pile foundation. Simultaneously, the acquisition terminal can access… Figure 1C The station marker list interface 15 shows how to capture front and back photos of a station marker by clicking the front and back photo capture icons 151 and 152. The data acquisition terminal can then perform image recognition on these photos to obtain the bus route information and station name. It should be noted that while station markers typically only have information on their front and back, some irregularly shaped markers, such as triangular prisms, display information on all three sides. In such cases, clicking the other marker icon 153 in the station marker list interface 15 will capture a photo of the third side of the marker. Figure 1C This is just one of the data collection methods. There are also other data collection methods, such as data collection personnel manually entering bus route information and station names. These will not be listed here.

[0117] In this implementation, after the server obtains the actual bus stop data from the data acquisition terminal, it can continuously replace the initial bus stop data with the acquired actual bus stop data to obtain updated bus stop data. This updated data includes both the actual bus stop data and the unreplaced initial bus stop data. The server can then use the updated bus stop data to execute the aforementioned bus stop data processing method.

[0118] In one possible implementation, the existing technology uses the vehicle stops as the serial unit for bus routes. Therefore, each bus route needs to be created separately, leading to the duplication of many routes with identical data, resulting in route redundancy. To solve this problem, the aforementioned bus stop data processing method may further include the following steps:

[0119] Based on the station data, a route between two stations that meet preset conditions is generated, and the route between stations corresponding to each bus route is obtained. The preset conditions include that the two stations are adjacent stations on the same bus route.

[0120] In response to receiving a bus route request from a client, the system determines the bus route requested in the bus route request, the bus route including connected inter-station routes;

[0121] The bus route is sent to the client so that the client can display the bus route.

[0122] In this implementation, bus routes are created by connecting the routes between bus stops as the smallest unit. These routes can be created based on bus stop data, and can be generated between any two bus stops that meet preset conditions. These preset conditions include the two bus stops being adjacent stops on the same bus route. For example... Figure 1D The diagram illustrates a scenario of bollards on a bus route according to an embodiment of the present disclosure, such as... Figure 1D As shown, bus routes on station A are routes 1 and 2, bus routes on station B are routes 1 and 3, and bus routes on station C are routes 2 and 4. If station A and station B are adjacent stations on route 1, a one-stop route is generated between station A and station B. If station A and station C are adjacent stations on route 2, a one-stop route is generated between station A and station C.

[0123] In this embodiment, based on the location of the bollard, the bus route information on the bollard, and the inter-station route, the corresponding inter-station route can be matched for each bus route. In this way, each bus route can be connected by inter-station routes, and the same route in different bus routes can reuse the same inter-station route without repeated production, thus solving the problem of redundant route production.

[0124] In this implementation, the bus route request can be a bus route navigation request. When the client obtains the user's input navigation start and destination and receives the user's input bus navigation operation, it sends a bus route navigation request to the server. This request includes the navigation start and destination. The server can then plan a bus navigation route for the user based on these information, obtaining the corresponding bus route. This route can be formed by connecting the stops along the designated bus route. For example, assuming the server plans a bus navigation route for the user from station A1 to station A2 of bus route X, the route is formed by connecting the stops between station A1 and station A2 of bus route X. Alternatively, the bus route request can be a bus route search request. When the client obtains the user's input search operation for a target bus route, it sends a bus route search request to the server. This request includes target bus route information. The server can then obtain the corresponding bus route based on this information, forming the route. Of course, this bus route request can also be other requests used to request bus routes, which will not be illustrated here.

[0125] In one possible implementation, the bus route request is a bus route navigation request, including a navigation origin and a navigation destination, and the method further includes:

[0126] If the bus route includes at least two bus routes, then the transfer type between the two adjacent bus routes is determined. The transfer type includes transfers at the same platform and at the same bus stop, and transfers at the same platform but at different bus stops.

[0127] The transfer type between two adjacent bus routes in the bus route is sent to the client so that the client can display the transfer type between the two adjacent bus routes in the bus route.

[0128] In this implementation, when the server makes a bus navigation request based on the navigation start and end points in the bus route navigation request, if the planned bus route includes at least two bus lines, then the bus route planned by the server for the user requires a transfer. In this case, to facilitate the user's transfer, the transfer type of the two adjacent bus lines can be determined. If the two adjacent bus lines do not intersect at the same platform, the transfer type of the two adjacent bus lines is determined to be a transfer between different platforms. If the two adjacent bus lines intersect at the same platform and are on the same stop but on different stopes at the intersecting platform, the transfer type of the two adjacent bus lines is determined to be a transfer between different stopes at the same platform. If the two adjacent bus lines intersect at the same platform and are on the same stop but on the same stop at the intersecting platform, the transfer type of the two adjacent bus lines is determined to be a transfer between the same stop and the same stop at the same platform. The server can send the transfer types of two adjacent bus lines in the bus route to the client, so that the client can display the transfer types of the two adjacent bus lines when displaying the bus route, so that users can understand the transfer types and plan ahead.

[0129] In one possible implementation, the above-mentioned bus stop data processing method may further include the following steps:

[0130] In response to receiving a navigation request from a client in non-public transport navigation mode, if the navigation destination of the navigation request is a target station, the system returns the station data within the target station to the client, allowing the client to display the station data within the target station for the user to select the target station as the actual destination.

[0131] In this implementation, the non-public transport navigation mode can be a driving / cycling / walking navigation mode, etc. When the user enters the navigation start point and destination in the navigation search interface or the main map (the map displayed on the client), the client receives the navigation command entered by the user. At this time, the client sends a navigation request to the server, which carries the navigation start point and destination. If the navigation destination is a target bus stop, the server returns the bus stop data within that target bus stop to the client. The client then displays the bus stop options corresponding to the bus stop data within the target bus stop for the user to choose from. The user can select the bus stop they want to go to as their actual destination from these bus stop options. If the client obtains the navigation command in the navigation search interface, the client can display bus stop options in a pop-up window below the navigation destination input box in the navigation search interface. Each bus stop option displays the name of the bus route corresponding to a bus stop within the target bus stop. The user can select a target bus stop based on the bus stop options displayed by the client, and the client can then navigate to the actual destination using the location of that target bus stop. Of course, if the client obtains navigation instructions from the main map interface, the client can display each station option at the location of the target station in the main map interface. Each station option displays the name of the bus route corresponding to one station in the target station. The user can select a target station based on the station options displayed by the client, and the client can then use the location of that target station as the actual navigation destination.

[0132] For example, if a user is walking from their current location to a target bus stop to catch bus route XY, the user can select walking navigation mode in the client and enter the target bus stop as the navigation destination. The client will then send a navigation request in walking navigation mode to the server, requesting walking navigation information from the user's current location to the target bus stop. Upon receiving this request, the server determines the target bus stop as the navigation destination. Since the target bus stop has multiple bollards, each in a different location, and users need to go to different bollards to wait for different buses, the server can return the bollard data for the target bus stop to the client to accurately navigate the user to the bollard for the XY bus. The client displays the bollard data for each bollard within the target bus stop. The user can then select the bollard for the XY bus route as their actual destination, and the client can navigate the user to that bollard without the user needing to search for the corresponding bollard at the target bus stop location. This results in accurate navigation and a better user experience.

[0133] In this implementation, after the client obtains the location of the target bollard selected by the user, it can send the location of the target bollard as the actual navigation destination to the server, which will then plan the navigation route and send it to the client for display.

[0134] Of course, it should be noted that if the destination of the navigation request is not the target station, the server will plan the navigation route for the user according to the origin and destination in the navigation request.

[0135] Figure 2 A flowchart illustrating a bus stop data processing method according to an embodiment of the present disclosure is shown. Figure 2 As shown, the bus stop data processing method includes the following steps S201-S202:

[0136] In step S201, the platform data of the target platform sent by the server is received. The platform data includes at least one of the following: platform surface area, station pile data of the station piles in the platform, the platform surface area covers the station pile positions in the platform, and the station pile data includes the station pile position and at least one of the following: station pile name, bus route information on the station pile;

[0137] In step S202, the platform surface of the target station and / or the pile data of the piles within the target station are displayed.

[0138] In one possible implementation, the bus stop data processing method is applicable to a client capable of performing bus stop data processing. In practical applications, the client can be a desktop computer, tablet computer, laptop computer, smartphone, digital assistant, smart wearable device, etc. Of course, the client is not limited to the above-mentioned physical electronic devices; it can also be a logical entity written in a programming language that runs on the above-mentioned electronic devices. For example, the client can be an application running on the electronic device.

[0139] In one possible implementation, the bus stop in this disclosure includes a stop for any type of public transport, such as buses, light rail, subways, etc., and each bus stop may have multiple bus routes stopping there. The bus stop may include at least one bollard, which is a public transport facility used to indicate the stopping location of the corresponding bus to users; for example, the bollard may be a bus stop sign.

[0140] In one possible implementation, the station marker data may include, in addition to the station marker location, one or both of the following: station marker name and bus route information on the station marker. The station marker name refers to the name of the station indicated by the station marker, and the bus route information on the station marker refers to the relevant information of the bus route operated by the bus indicated by the station marker. For example, if the station marker is a bus stop sign, the name of the station displayed on the bus stop sign is recorded as the station marker name; the bus route name displayed on the bus stop sign, such as Line X or Bus Route N, is the bus route information on the station marker.

[0141] In one possible implementation, the server can collect station data and aggregate it to obtain station data. Typically, each station can be aggregated from at least one station. The station data includes the station platform area and / or the station data of the stations within the station. It may also include station location points, station names, etc. The station platform area can cover the locations of all aggregated station points within the station. The station location point is located within the station platform area, for example, in the middle of the platform platform area. If all aggregated station names are the same, the station name can be the station name of the station within the station. If the aggregated station names are different, the station name can be the same name of all station names within the station. For example, if station 1 is named XX1 and station 2 is named XX2, the station name can be XX Station.

[0142] In one possible implementation, after the server aggregates the station data for each station, if it receives a station data request from a client for a target station, it can send the target station data to the client. Upon receiving the target station data, the client can display it. In one scenario, a user might use the client to search for a station A, which is the target station. In this case, the client can send a station data request to the server for station A's data. The server can respond by receiving the request and sending the station data for station A to the client: the station surface area and the station stake data within the station. After receiving the station data for station A, the client can display the station surface area and station stake data for station A on a map. In another scenario, a user might use a client to download map data for a specific geographic area for offline use. This map data includes station data for each station within that area. The client then sends a station data request to the server, requesting station data for each station within the geographic area. In this scenario, the target stations can be any station within the geographic area. After sending the station data for each station within the geographic area to the client, the server can also proactively send station data for certain stations to the client. For example, when the server detects the client is online, it might send the station data for certain stations within the geographic area to the client when their data is updated. In this case, the target stations are multiple stations within the map area whose data has been updated.

[0143] In one possible implementation, when displaying station data for a target station, in addition to displaying the station location and name, if the station data includes the station platform area, the client can display the station platform itself. If the station data includes station bollard data within the station, the client can display the location, name, and bus route information of each station bollard within the target station. If the station data includes both the station platform area and the station bollard data, the client can display either the station platform itself or both the station platform and the station bollard data as needed.

[0144] For example, suppose the platform data received by the client includes the platform location, platform name, platform area, and station stake data within the platform, such as... Figure 1B As shown, when the client displays platform data for station XXX, it can display a rectangular surface 11 as the platform surface of station XXX, a platform icon 12 at the platform location, the platform name "XXX Station" above the platform icon 12, station bollard icons 13 at the locations of each bollard within the platform surface, and a bus route text box 14 near the bollard icon 13, displaying the bus route name of that bollard. If in other examples the bollard name differs from the platform name, the corresponding bollard name can be displayed on the bollard icon 13. Of course, Figure 1B This is just one example of how platform data can be displayed. The display methods for each piece of data in this platform data can be varied, and will not be illustrated here.

[0145] In one possible implementation, the platform data includes the platform surface area and the station pile data within the platform. Step S202 in the above-mentioned bus platform data processing method, which displays the platform surface and / or the station pile data within the target platform, can also be implemented as follows:

[0146] In response to receiving the initial display command for the platform, the platform surface of the target platform is displayed;

[0147] In response to the command to obtain detailed platform information, the platform surface of the target platform and the pile data of the piles within the platform are displayed.

[0148] In this embodiment, the initial display command for the station can be a search command input by the user for the target station or a click command input by the user on the main image displayed on the client for the target station. After the client receives the initial display command, it will display the platform surface of the target station, as well as the location and name of the target station. The detailed information display command for the station can be a zoom-in command input by the user for the area where the target station is located. After the client receives the detailed information display command, in addition to displaying the location and name of the target station, it will also display the platform surface of the target station and the pile data of the piles within the station. Specific display methods can be as follows: Figure 1B As shown, no further examples will be given here.

[0149] In this implementation, when the client displays the platform data of the target platform, if the platform area of ​​the target platform is larger than the preset area, it indicates that the target platform occupies a large area. To facilitate more accurate positioning for the user, the client can automatically generate a platform details display command to display the platform area of ​​the target platform and the station data of the stakes within the target platform. If the platform area of ​​the target platform is smaller than the preset area, it indicates that the target platform occupies a small area. In this case, the client can automatically generate an initial platform display command to display the platform area of ​​the target platform without displaying the station data of the stakes within the target platform.

[0150] In this implementation, when the client receives the initial display instruction for the station, if the client has cached the station data of the target station, the client can directly display the station surface of the target station; if the client does not have cached the station data of the target station, the client can send a station data request for the target station to the server, the server will return the station data of the target station to the client, and then the client can display the station surface of the target station.

[0151] In one possible implementation, the above-mentioned bus stop data processing method can also be implemented as follows:

[0152] In response to receiving the bus route retrieval instruction, a bus route request is sent to the server;

[0153] The system receives the requested bus route from the server, which includes connecting routes between stations.

[0154] The bus route is displayed.

[0155] In this implementation, bus routes are created by connecting the routes between bus stops as the smallest unit. These routes can be created based on bus stop data, and can be generated between any two bus stops that meet preset conditions. These preset conditions include the two bus stops being adjacent stops on the same bus route. Based on the location of the bus stops, the bus route information on the bus stops, and the route, a corresponding route can be matched for each bus route. In this way, all bus routes can be formed by connecting the routes, and the same routes within different bus routes can reuse the same route, eliminating the need for repeated creation and solving the problem of redundant route creation.

[0156] In this implementation, the bus route request can be a bus route navigation request. When the client obtains the user's input navigation start and destination and receives the user's input bus navigation operation, it sends a bus route navigation request to the server. This request includes the navigation start and destination. The server can then plan a bus navigation route for the user based on these information, obtaining the corresponding bus route. This route can be formed by connecting the stops along the designated bus route. For example, assuming the server plans a bus navigation route for the user from station A1 to station A2 of bus route X, the route is formed by connecting the stops between station A1 and station A2 of bus route X. Alternatively, the bus route request can be a bus route search request. When the client obtains the user's input search operation for a target bus route, it sends a bus route search request to the server. This request includes the name of the target bus route. The server can then obtain the corresponding bus route based on the target bus route name, which can be formed by connecting the stops along the target bus route. After receiving the bus route from the server, the client can directly display the bus route.

[0157] In one possible implementation, the bus route request is a bus route navigation request, including a navigation start point and a navigation destination, and the method may further include the following steps:

[0158] If the bus route includes at least two bus lines, then the transfer type between two adjacent bus lines in the bus route is received and displayed. The transfer type includes same-platform same-station transfer and same-platform different-station transfer.

[0159] In this implementation, when the server requests bus navigation based on the navigation start and end points in the bus route navigation request, if the planned bus route includes at least two bus lines, it indicates that the route planned by the server requires the user to transfer. To facilitate transfers, the server can determine the transfer type between the two adjacent bus lines. If the two adjacent bus lines are on the same stop at an intersecting platform, the transfer type is determined to be same-platform, same-stop transfer. If the two adjacent bus lines are on different stopes at an intersecting platform, the transfer type is determined to be same-platform, different-stop transfer. The server can send the transfer types of the two adjacent bus lines in the bus route to the client. Thus, when the client displays the bus route, it can show the transfer types of the two adjacent bus lines, allowing the user to understand the transfer types and plan ahead.

[0160] In one possible implementation, the above-mentioned bus stop data processing method may further include the following steps:

[0161] In response to receiving a navigation instruction in non-public transport navigation mode, a navigation request in non-public transport navigation mode is sent to the server.

[0162] If the navigation destination of the navigation request is the target station, then the station data within the target station returned by the server is received;

[0163] Displays the station pile options corresponding to the station pile data within the target station platform;

[0164] In response to receiving a selection instruction for the selected pile option, navigation is performed with the location of the target pile selected by the selection instruction as the actual destination.

[0165] In this implementation, the non-public transport navigation mode can be a driving / cycling / walking navigation mode, etc. When the user enters the navigation start point and destination in the navigation search interface or the main map (the map displayed on the client), the client receives the navigation command entered by the user. At this time, the client sends a navigation request to the server, which carries the navigation start point and destination. If the navigation destination is a target bus stop, the server returns the bus stop data within that target bus stop to the client. The client then displays the bus stop options corresponding to the bus stop data within the target bus stop for the user to choose from. The user can select the bus stop they want to go to as their actual destination from these bus stop options. If the client obtains the navigation command in the navigation search interface, the client can display bus stop options in a pop-up window below the navigation destination input box in the navigation search interface. Each bus stop option displays the name of the bus route corresponding to a bus stop within the target bus stop. The user can select a target bus stop based on the bus stop options displayed by the client, and the client can then navigate to the actual destination using the location of that target bus stop. Of course, if the client obtains navigation instructions from the main map interface, the client can display each station option at the location of the target station in the main map interface. Each station option displays the name of the bus route corresponding to one station in the target station. The user can select a target station based on the station options displayed by the client, and the client can then use the location of that target station as the actual navigation destination.

[0166] For example, if a user is walking from their current location to a target bus stop to catch bus route XY, the user can select walking navigation mode in the client and enter the target bus stop as the navigation destination. The client will then send a navigation request in walking navigation mode to the server, requesting walking navigation information from the user's current location to the target bus stop. Upon receiving this request, the server determines the target bus stop as the navigation destination. Since the target bus stop has multiple bollards, each in a different location, and users need to go to different bollards to wait for different buses, the server can return the bollard data for the target bus stop to the client to accurately navigate the user to the bollard for the XY bus. The client displays the bollard data for each bollard within the target bus stop. The user can then select the bollard for the XY bus route as their actual destination, and the client can navigate the user to that bollard without the user needing to search for the corresponding bollard at the target bus stop location. This results in accurate navigation and a better user experience.

[0167] In this implementation, after the client obtains the location of the target bollard selected by the user, it can send the location of the target bollard as the actual navigation destination to the server, which will then plan the navigation route and send it to the client for display.

[0168] Of course, it should be noted that if the destination of the navigation request is not the target station, the server will plan the navigation route for the user according to the origin and destination in the navigation request.

[0169] Figure 3 This diagram illustrates a system illustration of an application scenario for bus stop data according to an embodiment of the present disclosure. Figure 3 As shown, the server includes a data production server 301, a POI (Point of Interest) server 302, and a transit planning server 303. The client 304 can be a user's handheld terminal, such as an app on a mobile phone. The data production server 301 can acquire station data and aggregate it to obtain platform data. It can also generate inter-station routes between two stations that meet preset conditions based on the station data and obtain the inter-station routes corresponding to each bus route. The data production server 301 can send the generated platform data to the POI server 302. In some other embodiments, the data production server 301 can also send the station data to the POI server 302 and send the platform data and the inter-station routes corresponding to each bus route to the transit planning server 303. When a user enters a search command for a target bus stop on client 304, client 304 can send a request for the target bus stop's data to POI server 302. POI server 302 can then return the target bus stop data to client 304. Client 304 can display the bus stop information based on this data. To view more detailed information about the target bus stop, the user can zoom in on the target bus stop area, and the client will display the bus stop data. If the user enters a navigation start point and destination on client 304 and selects a public transport route, the client will send a public transport route navigation request to public transport planning server 303. This request includes the navigation start point and destination. Public transport planning server 303 can then plan a public transport route for the user based on these points and send the corresponding bus route to client 304. This bus route can be formed by connecting the stops along the navigation route. Client 304 displays this bus route, allowing the user to follow it to take public transport.

[0170] This disclosure also provides a location-based service provision method, which uses the bus stop data processed by the above-described bus stop data processing method to provide location-based services to the service recipient. The location-based services include one or more of navigation, map rendering, and route planning.

[0171] In this embodiment of the disclosure, during location-based service processes, the station data can be used to provide better location services to the served object, such as navigation services, route planning services, and / or map rendering services. The served object can be a mobile phone, iPad, computer, smartwatch, vehicle, robot, etc. When navigating, planning routes, or rendering roads on a map for the served object, station data can be obtained based on the above method. Then, during navigation or route planning, the correct navigation actions can be output to the served object based on the station data. Furthermore, during map rendering, the station data can be rendered on the electronic map. Specific details can be found in the description of the station data processing method above, and will not be repeated here.

[0172] This disclosure also discloses a navigation method, wherein a navigation route is obtained based on at least a starting point, an ending point, and road conditions, and navigation guidance is performed based on the navigation route, wherein the road conditions are implemented based on any of the above methods.

[0173] Figure 4 A structural block diagram of a bus stop data processing apparatus according to an embodiment of the present disclosure is shown. This apparatus can be implemented as part or all of an electronic device through software, hardware, or a combination of both. Figure 4 As shown, the bus stop data processing device includes:

[0174] The first acquisition module 401 is configured to acquire station data, the station data including station location and at least one of the following: station name, bus route information on the station;

[0175] The aggregation module 402 is configured to aggregate the station pile data to obtain platform data, wherein the platform data includes at least one of the following: platform surface area and station pile data within the platform, wherein the platform surface area covers the station pile positions within the platform.

[0176] The first sending module 403 is configured to send the station data of the target station to the client according to the station data request sent by the client for the target station, so that the client can display the station data of the target station.

[0177] In one possible implementation, the first acquisition module 401 is configured as follows:

[0178] Based on historical station data, obtain initial station data;

[0179] Obtain actual pile data;

[0180] The initial pile data is updated based on the actual pile data to obtain the updated pile data.

[0181] In one possible implementation, the device further includes:

[0182] The second acquisition module is configured to generate inter-station routes between two station posts that meet preset conditions based on the station post data, and to acquire the inter-station routes corresponding to each bus route. The preset conditions include that the two station posts are adjacent station posts on the same bus route.

[0183] The first determining module is configured to, in response to receiving a bus route request sent by a client, determine the bus route requested in the bus route request, the bus route including a series of inter-station routes.

[0184] The second sending module is configured to send the bus route to the client so that the client can display the bus route.

[0185] In one possible implementation, the bus route request is a bus route navigation request, including a navigation start point and a navigation destination, and the device further includes:

[0186] The second determining module is configured to determine the transfer type of two adjacent bus routes if the bus route includes a route of at least two bus lines. The transfer type includes same-platform same-station transfer and same-platform different-station transfer.

[0187] The third sending module is configured to send the transfer type of two adjacent bus routes in the bus route to the client so that the client can display the transfer type of the two adjacent bus routes in the bus route.

[0188] In one possible implementation, the device further includes:

[0189] The fourth sending module is configured to respond to a navigation request sent by a client in non-public transport navigation mode. If the navigation destination of the navigation request is a target station, the module returns the station data within the target station to the client, so that the client can display the station data within the target station for the user to select a station as the actual destination.

[0190] The technical terms and features mentioned in this device implementation are the same or similar. For the explanation and description of the technical terms and features involved in this device, please refer to the explanation of the above method implementation, which will not be repeated here.

[0191] Figure 5 A structural block diagram of a bus stop data processing apparatus according to an embodiment of the present disclosure is shown. This apparatus can be implemented as part or all of an electronic device through software, hardware, or a combination of both. Figure 5 As shown, the bus stop data processing device includes:

[0192] The first receiving module 501 is configured to receive platform data of a target platform sent by the server. The platform data includes at least one of the following: platform surface area, station data of station posts within the platform, wherein the platform surface area covers the station post positions within the platform, and the station post data includes station post positions and at least one of the following: station post name, bus route information on the station post.

[0193] The first display module 502 is configured to display the platform surface of the target platform and / or the pile data of the piles within the target platform.

[0194] In one possible implementation, the platform data includes platform surface area and station pile data within the platform, and the first display module is configured to:

[0195] In response to receiving the initial display command for the platform, the platform surface of the target platform is displayed;

[0196] In response to the command to obtain detailed platform information, the platform surface of the target platform and the pile data of the piles within the target platform are displayed.

[0197] In one possible implementation, the device further includes:

[0198] The fifth sending module is configured to send a bus route request to the server in response to receiving a bus route retrieval instruction.

[0199] The second receiving module is configured to receive the bus route requested by the bus route request returned by the server, the bus route including a series of inter-station routes.

[0200] The second display module is configured to display the bus route.

[0201] In one possible implementation, the bus route request is a bus route navigation request, including a navigation start point and a navigation destination, and the device further includes:

[0202] The receiving and display module is configured to receive and display the transfer type of two adjacent bus routes in the bus route if the bus route includes a route with at least two bus lines. The transfer type includes same-platform same-station transfer and same-platform different-station transfer.

[0203] In one possible implementation, the device further includes:

[0204] The sixth sending module is configured to send a navigation request in non-public transport navigation mode to the server in response to receiving a navigation instruction in non-public transport navigation mode.

[0205] The third receiving module is configured to receive the station data within the target station returned by the server if the navigation destination of the navigation request is the target station.

[0206] The third display module is configured to display the station pile options corresponding to the station pile data within the target station platform;

[0207] The navigation module is configured to respond to receiving a selection instruction for the station option and navigate with the station location of the target station selected by the selection instruction as the actual destination.

[0208] The technical terms and features mentioned in this device implementation are the same or similar. For the explanation and description of the technical terms and features involved in this device, please refer to the explanation of the above method implementation, which will not be repeated here.

[0209] This disclosure also discloses an electronic device. Figure 6 A structural block diagram of an electronic device according to an embodiment of the present disclosure is shown.

[0210] like Figure 6 As shown, the electronic device 600 includes a memory 601 and a processor 602, wherein the memory 601 is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor 602 to implement the method according to embodiments of the present disclosure.

[0211] Figure 7 A schematic diagram of the structure of a computer system suitable for implementing the method according to embodiments of the present disclosure is shown.

[0212] like Figure 7 As shown, the computer system 700 includes a processing unit 701, which can execute various processes described in the above embodiments according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage section 708 into a random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the computer system 700. The processing unit 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0213] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed. The processing unit 701 can be implemented as a CPU, GPU, TPU, FPGA, NPU, etc.

[0214] In particular, according to embodiments of this disclosure, the methods described above can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising computer instructions that, when executed by a processor, implement the steps of the methods described above. In such embodiments, the computer program product can be downloaded and installed from a network via communication section 709, and / or installed from removable media 711.

[0215] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0216] The units or modules described in the embodiments of this disclosure can be implemented in software or programmable hardware. The described units or modules can also be located in a processor, and the names of these units or modules do not necessarily constitute a limitation on the unit or module itself.

[0217] In another aspect, this disclosure also provides a computer-readable storage medium, which may be a computer-readable storage medium included in the electronic device or computer system described above; or it may be a standalone computer-readable storage medium not assembled into a device. The computer-readable storage medium stores one or more programs, which are used by one or more processors to perform the methods described in this disclosure.

[0218] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the inventive concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

Claims

1. A method for processing bus stop data, applied on a server side, comprising: Acquire bus stop data, which includes the location of the bus stop and at least one of the following: bus stop name, bus route information on the bus stop; the bus stop is used to indicate the stopping location of the corresponding bus to the user; Platform data is obtained by aggregating the station pile data. The platform data includes at least one of the following: platform surface area and station pile data within the platform. The platform surface area covers the station pile locations within the platform. Based on the station data, a route between two stations that meet preset conditions is generated, and the route between stations corresponding to each bus route is obtained. The preset conditions include that the two stations are adjacent stations on the same bus route. In response to receiving a bus route request from a client, the system determines the bus route requested in the bus route request, the bus route including connected inter-station routes; The bus route is sent to the client so that the client can display the bus route; Based on the platform data request sent by the client for the target platform, the platform data of the target platform is sent to the client so that the client can display the platform data of the target platform.

2. The method according to claim 1, wherein, The acquisition of the station pile data includes: Based on historical station data, obtain initial station data; Obtain actual pile data; The initial pile data is updated based on the actual pile data to obtain the updated pile data.

3. The method according to claim 1, wherein, The bus route request is a bus route navigation request, including a navigation start point and a navigation destination. The method further includes: If the bus route includes at least two bus routes, then the transfer type between the two adjacent bus routes is determined. The transfer type includes transfers at the same platform and at the same bus stop, and transfers at the same platform but at different bus stops. The transfer type between two adjacent bus routes in the bus route is sent to the client so that the client can display the transfer type between the two adjacent bus routes in the bus route.

4. The method according to claim 1, wherein, The method further includes: In response to receiving a navigation request from a client in non-public transport navigation mode, if the navigation destination of the navigation request is a target station, the system returns the station data within the target station to the client, allowing the client to display the station data within the target station for the user to select the target station as the actual destination.

5. A method for processing bus stop data, applied to a client-side application, comprising: The system receives platform data of a target station sent by the server. The platform data is obtained by the server according to the method described in any one of claims 1-4. The platform data includes at least one of the following: platform surface area, station data of station bollards within the platform, wherein the platform surface area covers the station bollard positions within the platform, and the station bollard data includes the station bollard position and at least one of the following: station bollard name, and bus route information on the station bollard. Display the platform surface of the target station and / or the pile data of the piles within the target station.

6. The method according to claim 5, wherein, The platform data includes platform surface area and station pile data within the platform. Displaying the platform surface and / or station pile data of the target platform includes: In response to receiving the initial display command for the platform, the platform surface of the target platform is displayed; In response to the command to obtain detailed platform information, the platform surface of the target platform and the pile data of the piles within the target platform are displayed.

7. The method according to claim 5, wherein, The method further includes: In response to receiving the bus route retrieval instruction, a bus route request is sent to the server; The system receives the requested bus route from the server, which includes connecting routes between stations. The bus route is displayed.

8. The method according to claim 7, wherein, The bus route request is a bus route navigation request, including a navigation start point and a navigation destination. The method further includes: If the bus route includes at least two bus lines, then the transfer type between two adjacent bus lines in the bus route is received and displayed. The transfer type includes same-platform same-station transfer and same-platform different-station transfer.

9. The method according to claim 5, wherein, The method further includes: In response to receiving a navigation instruction in non-public transport navigation mode, a navigation request in non-public transport navigation mode is sent to the server. If the navigation destination of the navigation request is the target station, then the station data within the target station returned by the server is received; Displays the station pile options corresponding to the station pile data within the target station platform; In response to receiving a selection instruction for the selected pile option, navigation is performed with the location of the target pile selected by the selection instruction as the actual destination.

10. An electronic device comprising a memory and a processor; wherein, The memory is used to store one or more computer instructions, which are executed by the processor to implement the steps of the method according to any one of claims 1 to 9.

11. A computer program product comprising computer instructions that, when executed by a processor, implement the steps of the method according to any one of claims 1 to 9.

12. A navigation method, wherein, Obtain a navigation route calculated based at least on the starting point, ending point, and station data; provide navigation guidance based on the navigation route; and process the station data based on any one of the methods described in claims 1-9.

Images