A logistics track address calibration method and system

Abstract

The present application discloses a logistics track address calibration method and system, including: generating multiple address combinations based on multiple logistics track information of the same logistics order number, each address combination consists of three adjacent track addresses, defining the first track address in each address combination as A, the second track address as B, and the third track address as C; determining the deviation coefficient β of track address B based on the distance information of track addresses A, B, and C, and judging whether the track address of each address combination is normal based on the deviation coefficient β; if the track address of the first address combination of two adjacent address combinations is abnormal and the track address of the second address combination is normal, then determining that the first track address in the first address combination is abnormal. This method and system can calibrate track addresses with the same name, greatly improving the accuracy of track identification.

Description

Technical Field

[0001] The present application relates to the field of logistics query technology, and in particular to a logistics track address calibration method and system, and a logistics track identification method and system. Background Art

[0002] Some logistics tracking systems map the logistics track information corresponding to the logistics order number on a map, allowing users to intuitively view the logistics transportation route. This is achieved by first matching the longitude and latitude of the corresponding geographical name from the track address in a geographic database, and then marking the track on the map based on the matched longitude and latitude information. This track marking method is mainly suitable for situations where the longitude and latitude of the track address are unique.

[0003] International logistics involves thousands of logistics providers worldwide, and many geographically identical names. Many providers' systems provide non-standard tracking address information (for example, providing only simple tracking address names without administrative level information like country and city). This can lead to inaccurate tracking address identification when performing longitude and latitude matching. The prior art lacks a tracking address calibration method for address homonyms.

[0004] Furthermore, traditional logistics track identification methods typically retrieve the longitude and latitude information of track addresses directly from geographic databases. For international logistics tracking systems, this traditional identification method reduces the efficiency and accuracy of track identification due to the large number of track addresses that require calibration.

[0005] Other technical issues related to this application will be further elaborated later. The above content is only used to assist in understanding the technical solution of this application and does not mean that all of the above content is prior art. Summary of the Invention

[0006] The main purpose of this application is to provide a logistics track address calibration method and system, which can calibrate track addresses with the same name and significantly improve the accuracy of track identification. In addition, this application also provides a logistics track identification method and system, which can improve the efficiency and accuracy of logistics track identification.

[0007] To achieve the above objectives, the present application proposes a logistics track address calibration method, which includes:

[0008] Step S1: Generate an address list based on multiple logistics track information of the same logistics order number, and arrange the track addresses in the address list in the order of the corresponding logistics tracks;

[0009] Step S2: generating multiple address combinations from the trace addresses in the address list, each address combination consisting of three adjacent trace addresses, and defining the first trace address in each address combination as A, the second trace address as B, and the third trace address as C;

[0010] Step S3: Determine whether the track address of each address combination is normal based on a reasonable path algorithm, wherein the reasonable path algorithm includes:

[0011] Step S31: determining the midpoint O of the track addresses A and C, and determining the deviation coefficient β of the track address B according to the distance L between two positions among A, B, C and O;

[0012] Step S32: Determine the radius R of a reference circle based on the deviation coefficient β, where the reference circle has point O as its center;

[0013] Step S33: Determine whether the track address B is within the reference circle: if B is outside the reference circle, the track address of the corresponding address combination is determined to be abnormal; if B is within the reference circle, the track address of the corresponding address combination is determined to be normal;

[0014] Step S4: If, in two adjacent address combinations, the track address of the former address combination is abnormal and the track address of the latter address combination is normal, then it is determined that the first track address in the former address combination is abnormal.

[0015] Other technical features and technical effects of this application are described in the following part of the specification. The technical problem-solving ideas and related product design solutions of this application are as follows:

[0016] International logistics tracking systems need to track logistics tracking numbers from different countries and logistics providers. The resulting logistics track information is complex and often contains non-standard track address information. Furthermore, due to the numerous homonymous geographic names worldwide (for example, "New York" in the United States may represent New York State and New York City with different longitudes and latitudes; popular geographic names like San Diego and Victoria are located in many countries; and the relocation of governments, schools, and hospitals can also result in homonymous geographic names with varying longitudes and latitudes), it is difficult to accurately match track address names to the correct longitude and latitude (geographic coordinates) in the geographic database, thereby reducing the accuracy of track identification. If logistics tracks lack information such as country and city, it is difficult to automatically calibrate track addresses with homonymous addresses.

[0017] The applicant discovered that multiple track addresses of the same logistics order number have a certain correlation, and in order to shorten the logistics transportation time, most logistics transportation routes are basically in a straight line trend; at this time, if three adjacent track addresses of the same logistics order number are taken for comparison (such as the three adjacent track addresses A, B, and C generated successively), if B is not an abnormal address with the same name, then the distance AB should be smaller than the distance AC. In this way, it is possible to determine whether B is an abnormal address with the same name based on the size of the AB distance and the AC distance, and then calibrate the track address B. That is, a reference circle is constructed with point A as the center and the AC distance as the radius (circle 1, radius R1=L AC ), if the longitude and latitude of track address B are normal, then B will be inside circle 1; if the longitude and latitude of track address B are abnormal, then B will be outside circle 1.

[0018] However, for international logistics, the logistics trajectories of many logistics stages do not follow a linear trend. For example, the logistics transportation direction will often change in many special links, such as the initial collection stage, the final distribution stage, the stage of switching transportation modes (such as land to air, air to land, land to sea, sea to land), the customs entry and exit stage, or the detour transportation stage (such as encountering bays or mountains). At this time, even if the normal trajectory address B is B, the distance AB may be greater than the distance AC, making it difficult to calibrate the trajectory address B.

[0019] In addition, by analyzing a large amount of historical logistics track information, obtaining the longitude and latitude of each track address, calculating the distance between each track address, and performing comparative analysis, it was found that many abnormal track addresses have the following pattern: if the midpoint of AC is used as the center of the circle and half of the distance between AC is used as the radius to construct a basic circle (circle 2, radius R2=L AO =L CO =0.5*L AC ), and enlarge the radius of circle 2 by β times to form a new reference circle (circle 3, radius R2=β*L AO ), so that circle 3 covers most of the normal track address B, then the larger the AC distance is, the smaller the value of the magnification β is.

[0020] refer to Figure 2 , assuming that track addresses A and C are normal, track address B may be abnormal, ABC constitutes an address combination. If the midpoint O is the center of the circle, β*L AO is the radius (R=β*L AO) constructs a reference circle (circle 3). Then, whether track address B is abnormal can be determined by determining whether it is within circle 3. In other words, if B is within circle 3 (e.g., B1), then B's longitude and latitude are normal; if B is outside circle 3 (e.g., B2), then B's longitude and latitude are abnormal. A larger magnification factor β indicates a greater degree of deviation for B, so β ​​can be called the deviation coefficient for track address B.

[0021] In specific implementation, the deviation coefficient β of the track address B can be determined according to the distance L between any two positions among A, B, C and O (such as the distances BO, AC, AB, etc.), and then the radius R of the reference circle (with O as the center) can be determined based on the deviation coefficient β. R=β*L AO , then determines whether B is within the reference circle. If B is not within the reference circle (either outside or on the reference circle), the longitude and latitude of the track address B or address combination are considered abnormal. If B is within the reference circle, the longitude and latitude of the track address B or address combination are considered normal. In this application, this method of determining whether a track address or address combination is abnormal based on information related to the reference circle is called a reasonable path algorithm.

[0022] When the distance L between positions B and O BO When determining β by the size, it is known that L BO The following values ​​of and β can identify the track addresses of most abnormal longitudes and latitudes. BO When it is in the interval [0KM, 20KM), β can be set to 10±0.5; when L BO When it is in the interval [20KM, 50KM), β can be taken as 17±1; when L BO When it is in the interval [50KM, 100KM), β can be taken as 13±0.5; when L BO When the range is [100KM, 200KM), β can be taken as 2.7±0.2; when L BO When the range is [200KM, 500KM), β can be taken as 2.6±0.2; when L BO When the range is [500KM, 1000KM), β can be set to 1.8±0.2; when L BO When it is in the interval [1000KM, +∞), β can be taken as 1.8±0.2.

[0023] Since the β values ​​of the interval [100KM, 200KM) and the interval [200KM, 500KM) are very close, they can be merged into one overall interval; that is, when L BOWhen it is in the interval [100KM, 500KM), β can be taken as 2.7±0.2. The β corresponding to the interval [500KM, 1000KM) and the interval [1000KM, +∞) are almost unchanged, and they can also be merged into one overall interval; that is, when L BO When it is in the interval [500KM, +∞), β can be taken as 1.8±0.2. From the above data, we can also know that when L BO When the speed is greater than 50 km, the L BO As the value of L increases, the value of β decreases; BO When the distance is less than 50 km, β does not have this decreasing characteristic. BO When the distance is greater than 500 km, β begins to stabilize; therefore, when L BO Or when other offset distances are greater than 500 km, β takes a fixed value.

[0024] In order to simplify the calculation, when judging whether the track address B is within the reference circle, the reference circle is not constructed, and only the distance L of BO is compared. BO and reference circle radius R (R=β*L AO ) size, if L BO If it is less than R, then B is judged to be inside the reference circle; otherwise, B is judged to be outside the reference circle.

[0025] The reasonable path algorithm can only determine whether the address combination ABC has an anomaly; it cannot determine which specific track address within ABC has an anomaly. To this end, multiple track addresses for the same logistics order number can be used to generate multiple address combinations. The reasonable path algorithm can then be used to determine whether the track addresses in each address combination have an anomaly. Step S41: If, between two adjacent address combinations, the track address of the first address combination is anomaly and the track address of the second address combination is normal, then the first track address in the first address combination is determined to be anomaly.

[0026] For example, in Case 1, the same logistics order number contains six sequentially ordered tracking addresses: D, E, F, G, H, and I. These can generate four adjacent address combinations: DEF, EFG, FGH, and GHI. If the tracking address of address combination DEF is abnormal (indicating that tracking addresses D, E, and F are also likely abnormal), but the tracking address of the subsequent adjacent address combination EFG is normal (indicating that tracking addresses E, F, and G are all normal), it can be determined that the first tracking address D in the previous address combination DEF is abnormal.

[0027] This track address calibration method can calibrate track addresses with the same name when administrative-level information such as country and city is missing from the logistics track. This allows for the early identification of track addresses with abnormal longitude and latitude, significantly improving the accuracy of track address latitude and longitude and track identification. This ensures track address accuracy even in the event of detours, return trips, or the presence of duplicate addresses during transportation.

[0028] Furthermore, the present application also provides a logistics track identification method, the method comprising:

[0029] Step K1: Create a logistics provider database and a master table database. The logistics provider database is used to store the track address name information of the corresponding logistics provider, and the master table database is used to store the track address name and latitude and longitude information of the corresponding logistics provider;

[0030] Step K2: matching the corresponding longitude and latitude information from the geographic database according to the track address of the historical logistics track, and performing a calibration operation on the track address, wherein the calibration operation includes correcting the longitude and latitude of the abnormal track address;

[0031] Step K3: storing the calibrated track address information in the logistics provider database and the master table database respectively, and associating the track address information in the logistics provider database and the master table database;

[0032] Step K4: In response to the logistics track identification instruction, according to the track address name of the logistics track to be identified and the information of the logistics provider to which it belongs, the target track address of the corresponding logistics provider is matched in the logistics provider database; based on the target track address, the corresponding longitude and latitude information is obtained from the general table database;

[0033] Step K5: Generate a track mark on the map based on the latitude and longitude information of the target track address.

[0034] Other technical features and technical effects of this application are described in the following part of the specification. The technical problem-solving ideas and related product design solutions of this application are as follows:

[0035] International logistics tracking systems process billions of shipment queries annually, creating a high probability of anomalies in the longitude and latitude of track addresses, requiring calibration of numerous track addresses. Directly deriving longitude and latitude from a geographic database for track identification significantly increases the likelihood of track identification errors, necessitating pre-calibration of track addresses before identification.

[0036] However, the trajectory address calibration method based on the reasonable path algorithm requires at least 2 address combinations or 4 trajectory addresses to perform the calibration operation. It cannot calibrate the logistics trajectory in the early stage of logistics. For example, if there are only 1-3 trajectory addresses, it is difficult to determine which trajectory address is abnormal.

[0037] The applicant has discovered that most logistics providers typically only provide transportation services within a specific country. When a package needs to continue shipping to another country (a second country), it is often entrusted to a local logistics provider in that second country. When calibrating track addresses, adding supplier-specific constraints can identify the most likely track address with the same name, which can then be used as the initial calibration track address for track identification.

[0038] Based on the above concept, the applicant proposed a preliminary method for tracking track addresses using a dual address database. Specifically, the method involves first creating a logistics provider database and a master database. The logistics provider database is used to store the track address name information (excluding longitude and latitude information) of the corresponding logistics provider, while the master database is used to store the track address name, longitude and latitude of the corresponding logistics provider, and other information. Then, using the track addresses of historical logistics tracks, a reasonable path algorithm is used to calibrate the track addresses, identify track addresses with abnormal longitude and latitude, and correct the abnormal longitude and latitude. The calibrated track address information is then stored in the logistics provider database and the master database, respectively. The logistics provider database records the logistics provider and the corresponding track address name (address text), while the master database records the complete information, including the logistics provider, track address name, longitude and latitude, and longitude. The logistics provider database and the master database are linked, allowing the system to directly retrieve the corresponding detailed information (such as longitude and latitude, logistics provider, etc.) in the master database based on the simple information in the logistics provider database (such as the logistics provider and / or track address name).

[0039] When a logistics track identification task needs to be performed, first match the target track address of the corresponding logistics provider in the logistics provider database according to the track address name of the logistics track to be identified and the information of the logistics provider to which it belongs (the target track address refers to the track address in the logistics provider database with the same name as the track address to be identified); then, based on the target track address, retrieve the corresponding latitude and longitude information from the general table database, and then generate a track identification on the map.

[0040] This logistics track identification method can identify tracks even when the track address of a logistics order number is incomplete, improving track identification accuracy. Furthermore, through the collaborative division of labor between the logistics business database and the master table database, it can significantly increase the speed of track address queries and perform batch identification of track addresses, shortening track identification time and avoiding interruptions in track identification caused by logistics track calibration operations. It can also improve the efficiency of subsequent continuous dimensional correction of track addresses. Track identification can be performed quickly even if the track address spans different countries.

[0041] Furthermore, the present application also includes systems corresponding to various methods, wherein the systems include the functional modules involved in the present application, execute the operating instructions of the corresponding functional modules or the corresponding methods, and output relevant data information to the system front-end interface. The systems are stored in a server and / or computer device including a processor, and the processor is used to execute the operating instructions of the system.

[0042] Disclaimer: The functional modules of this application can be integrated with each other, or can exist independently, or a functional module can serve as a submodule of another functional module; step numbers such as S1, S2 do not limit the order of the corresponding operation steps.

[0043] The following are the explanations of some professional terms in this application.

[0044] (1) GeoNames is a free global geographic database, and Nominatim is a global open source geocoding and reverse geocoding library. Both GeoNames and Nominatim are geographic databases that can perform address matching. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The accompanying drawings are used to provide further understanding of the present application and do not constitute a limitation of the present application; the contents shown in the accompanying drawings may be real data of the embodiments and fall within the scope of protection of the present application.

[0046] Figure 1 This is a flow chart of a logistics track address calibration method in one embodiment of the present application.

[0047] Figure 2 This is a schematic diagram of the reasonable path algorithm in one embodiment of the present application.

[0048] Figure 3 Schematic diagram of the logistics tracking system structure in one embodiment of the present application.

[0049] Figure 4 This is a flow chart of a logistics track identification method in one embodiment of the present application. DETAILED DESCRIPTION

[0050] In order to make the purpose, technical solutions and advantages of this application more clear, the following is a further detailed description of the embodiments of this application through specific implementation methods combined with the accompanying drawings. It should be understood that the specific embodiments described here are only used to explain this application and are not used to limit this application.

[0051] refer to Figure 1-Figure 3 , this application proposes a logistics track address calibration method, including the following steps S1-S4.

[0052] Step S1: Generate an address list based on multiple logistics track information for the same logistics order number. The track addresses in the address list are arranged in the order of the corresponding logistics tracks. For example, from all logistics tracks for a certain logistics order number, logistics tracks containing the same track address are removed, and then the track addresses are arranged in the chronological order of the logistics tracks corresponding to each track address to obtain the address list.

[0053] Step S2: Generate multiple address combinations from the trace addresses in the address list. Each address combination consists of three adjacent trace addresses. Define the first trace address in each address combination as A, the second trace address as B, and the third trace address as C. For example, if the address list contains six trace addresses D, E, F, G, H, and I, which are generated in sequence, they can be split into four address combinations: DEF, EFG, FGH, and GHI. In the address combination DEF, the first trace address D is defined as A, the second trace address E is defined as B, and the third trace address F is defined as C.

[0054] Step S3: Determine whether the trajectory address of each address combination is normal based on a reasonable path algorithm, the reasonable path algorithm includes: Step S31: Determine the midpoint position O of the trajectory addresses A and C, and determine the deviation coefficient β of the trajectory address B based on the distance L between the two positions in A, B, C and O; Step S32: Determine the radius R of the reference circle based on the deviation coefficient β, and the reference circle takes point O as the center; Step S33: Determine whether the trajectory address B is within the reference circle: If B is outside the reference circle, the trajectory address of the corresponding address combination is determined to be abnormal; if B is within the reference circle, the trajectory address of the corresponding address combination is determined to be normal. In other embodiments, point A, point C, or other points on the straight line AC except point O can be used as the center of the circle, with β*L AO Construct a reference circle for the radius, and then perform track address anomaly judgment.

[0055] Step S4: If, in two adjacent address combinations, the track address of the first address combination is abnormal and the track address of the second address combination is normal, then the first track address in the first address combination is determined to be abnormal. In this application, an abnormal track address indicates that the longitude and latitude of the corresponding track address need to be calibrated, and a normal track address indicates that the longitude and latitude of the corresponding track address do not need to be calibrated for the time being.

[0056] In one embodiment, when determining which specific trace address in an address combination is abnormal, the following procedure may be performed (step S42): if, of two adjacent address combinations, the trace address of the first address combination is normal and the trace address of the second address combination is abnormal, then the third trace address in the second address combination is determined to be abnormal. For example, in the aforementioned case 1, if the trace address of address combination DEF is normal (indicating that trace addresses D, E, and F are all normal), but the trace address of the subsequent adjacent address combination EFG is abnormal (indicating that trace addresses E, F, and G may all be abnormal), then the third trace address G in the second address combination EFG can be determined to be abnormal.

[0057] When the trajectory addresses of two adjacent address combinations are both normal or both abnormal (when both address combinations are abnormal, it is difficult to determine whether the corresponding trajectory addresses are abnormal based solely on the trajectory address information of the same logistics order number), the abnormal trajectory address judgment of the current two address combinations can be skipped, and the abnormal trajectory address judgment of the next adjacent address combination can be performed until the abnormal trajectory address judgment of all address combinations is completed. For example, in Case 1, after judging that the trajectory addresses of the address combinations DEF and EFG are abnormal, the judgments are performed in the order of EFG and FGH, and FGH and GHI, until the judgment of the last address combination is completed. It should be noted that when judging that the trajectory addresses of all address combinations are abnormal, only step S41 or step S42 can be used for judgment, or both step S41 and step S42 can be used for judgment.

[0058] When calculating the distance between two addresses (locations), this application uses the geodesic function in the geopy library to calculate the geographic distance between the two geographic coordinates. To determine the longitude and latitude of the midpoint between the two addresses, first convert the longitude and latitude of the two addresses from degrees to radians, then convert them to Cartesian coordinates. The average of the Cartesian coordinates of the two addresses is then calculated and converted back to geographic coordinates (latitude and longitude) to obtain the longitude and latitude data of the midpoint between the two addresses.

[0059] In one embodiment, before performing the track address calibration in step S1, a determination is made as to whether the track information corresponding to the track address contains administrative level information (e.g., country and city information). If it does not, steps S1-S4 are performed. If it does, and the administrative level information does not match the corresponding track address, the track address is determined to be abnormal (steps S1-S4 are not performed again). If it does, and the administrative level information matches the corresponding track address, steps S1-S4 are performed again. In this way, the longitude and latitude of the track address can be further calibrated using the administrative level information, improving the accuracy of the longitude and latitude information of the track address.

[0060] The applicant discovered that due to certain reasons, a small number of track addresses will be judged as normal in the track address calibration of some logistics order numbers, but will be judged as abnormal in the track address calibration of other logistics order numbers. For this reason, when performing track address calibration, the trust level γ of each track address is additionally calculated. The trust level γ is the ratio of the number of calibrations N1 that are judged to be normal after calibration to the total number of calibrations N2 of the track address. For example, a track address has been calibrated a total of 100 times, of which 98 times were judged to be normal. Then the trust level of this track address is 0.98, which is the ratio of 98 to 100. By calculating the trust level of different logistics companies or different periods, we can know the degree of data anomalies in the logistics tracking process, and avoid the impact of track address calibration errors caused by accidental factors (such as geographic database updates, data parsing errors, etc.).

[0061] In related embodiments, track addresses with high confidence levels can be used to calibrate other track addresses. For example, when determining that the track addresses of adjacent address combinations are abnormal, if the track addresses of both the preceding and succeeding address combinations are abnormal, then a determination is made as to whether the confidence level of each track address in the preceding address combination is greater than a preset value (e.g., the preset confidence level is set to 0.8). If the confidence level is greater than (or equal to) the preset value, the corresponding track address is determined to be normal; if the confidence level is less than the preset value, the corresponding track address is determined to be abnormal. The track address of the succeeding address combination can be calibrated without confidence level and, together with the next adjacent address combination, through step S41 or step S42. In this way, the accuracy of the track address can be further improved.

[0062] In one embodiment, the logistics track address calibration method can also be: based on multiple logistics track information of the same logistics order number, generate multiple address combinations respectively, each address combination consists of three adjacent track addresses, and define the first track address in each address combination as A, the second track address as B, and the third track address as C; judge whether the track address of each address combination is normal: determine the deviation coefficient β of the track address B based on the geographic location information of the track addresses A, B, and C, and judge whether the track address of each address combination is normal based on the deviation coefficient β; if in two adjacent address combinations, the track address of the previous address combination is abnormal and the track address of the latter address combination is normal, then determine that the first track address in the previous address combination is abnormal.

[0063] refer to Figure 3-Figure 4 ,This application proposes a logistics track identification method, including the following steps K1-K5.

[0064] Step K1: Create a logistics provider database and a master database. The logistics provider database is used to store the track address name information of the corresponding logistics provider, and the master database is used to store the track address name and longitude and latitude information of the corresponding logistics provider. The master database can also store information such as the address combination corresponding to the track address and the calibration status.

[0065] Step K2: Based on the historical logistics track address, the corresponding longitude and latitude information is matched in the geographic database. The track address is calibrated. This calibration includes correcting the longitude and latitude of abnormal track addresses. For example, using a reasonable path algorithm, track addresses with abnormal longitude and latitude are identified and then corrected.

[0066] Step K3: Store the calibrated track address information in the logistics provider database and the master database, respectively. Link the track address information in the logistics provider database and the master database. For example, this can be done using a hash value to maintain data consistency between the two databases and facilitate subsequent expansion and maintenance of track address data. The logistics provider database and the master database can store uncalibrated track address information and update the corresponding information after the track address is calibrated. Alternatively, they can store only the calibrated track address information.

[0067] Step K4: In response to the logistics track identification instruction, the target track address of the corresponding logistics provider is matched in the logistics provider database based on the track address name and the logistics provider information of the logistics track to be identified. In other words, the target track address has the same track address name and the same logistics provider as the logistics track to be identified. The corresponding longitude and latitude information is then obtained from the master table database based on the target track address.

[0068] Step K5: Generate a track mark on the map based on the latitude and longitude information of the target track address.

[0069] In related embodiments, each historical logistics track information tracked by the logistics tracking system can be calibrated, and the calibrated track address information can be stored in the logistics provider database and the master table database. When a track address needs to be identified, the corresponding longitude and latitude information can be directly matched (parsed) from the logistics provider database and the master table database for identification. If a track address does not match the target track address in the logistics provider database, the track address is matched with the geographic database. If the corresponding longitude and latitude information is matched, the track address is calibrated and the operation of step K3 is executed. If the corresponding longitude and latitude information is not matched, the track address is deemed invalid.

[0070] In one embodiment, the number of geographic databases can be one or more. When a track address fails to match the corresponding longitude and latitude information in any geographic database, the track address is determined to be invalid and stored in the logistics provider database. When the track address can be matched to the corresponding longitude and latitude information in any geographic database, a calibration operation is performed on the track address, and the operation of step K3 is executed. For example, track address matching can be performed using two different geographic databases, GeoNames and Nominatim, to improve the accuracy of track address recognition. If no longitude and latitude are matched in all geographic databases, it indicates that there may be a problem with the corresponding track address. In this case, it is only recorded in the logistics provider database (not in the general table database) to mark that the track address has been processed. This prevents the same track address from falling into the exception database (log database) again, causing data redundancy and repeated processing by the system.

[0071] In one embodiment, because the sheer volume of data required to update offline databases (the logistics provider database and the master database) to online data is excessive, updated track address information is marked with a timestamp. When track address information in the logistics provider database and / or master database is updated, the timestamp of the corresponding track address is updated. If a newer timestamp indicates that the track address information has changed, when synchronously updating track address information in related online or offline databases, only the latest timestamp is needed to update the corresponding information, significantly accelerating information synchronization between databases.

[0072] In one embodiment, when calibrating the track address, steps S3 and S4 can be improved. In step S33, when B is outside the reference circle, the track address corresponding to B is recorded in the log file. If a track address is recorded multiple times in the log file among multiple track addresses for the same logistics order number, then the track address is determined to be abnormal. In this way, step S4 can be omitted.

[0073] In one embodiment, when performing a calibration operation on a track address, a correction operation is performed on an abnormal track address, including: obtaining the previous track address and the next track address of the abnormal track address in the corresponding logistics order number, defining the previous track address as A, the abnormal track address as B, and the next track address as C, and determining the midpoint position O between track addresses A and C. Re-obtaining all longitude and latitude information corresponding to the abnormal track address from the geographic database, and then calculating the deviation coefficient β1 of each longitude and latitude one by one, and taking the longitude and latitude with the smallest deviation coefficient β1 as the corrected longitude and latitude, where β1=L BO / L AO , L BO is the distance of BO, L AOThe distance to the AO is then updated based on the corrected longitude and latitude, and a corresponding timestamp is generated. This allows for batch automatic correction of abnormal track addresses, significantly improving the accuracy of the track address longitude and latitude.

[0074] The above description is only a preferred embodiment of the present application and does not limit the patent scope of the present application. All equivalent transformations made using the contents of the present application specification and drawings under the inventive concept of the present application, or direct / indirect application in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A logistics track address calibration method, characterized in that: The method comprises: Step S1: Generate an address list based on multiple logistics track information of the same logistics order number, and arrange the track addresses in the address list in the order of the corresponding logistics tracks; Step S2: generating multiple address combinations from the trace addresses in the address list, each address combination consisting of three adjacent trace addresses, defining the first trace address in each address combination as A, the second trace address as B, and the third trace address as C; Step S3: Determine whether the track address of each address combination is normal based on a reasonable path algorithm, wherein the reasonable path algorithm includes: Step S31: Determine the midpoint O of the track address A and C based only on the distance L between the B and O positions. BO Determine the deviation coefficient β of the track address B: When L BO When it is in the interval [0KM, 20KM), the value range of β is 10±0.5; and / or, when L BO When it is in the interval [20KM, 50KM), the value range of β is 17±1; and / or, when L BO When it is in the interval [50KM, 100KM), the value range of β is 13±0.5; and / or, when L BO When it is in the interval [100KM, 500KM), the value range of β is 2.7±0.2; and / or, when L BO When it is in the interval [500KM, +∞), the value range of β is 1.8±0.2; Step S32: Determine the radius R of the reference circle based on the deviation coefficient β. The reference circle has point O as its center. The radius of the reference circle R=β*L AO , where L AO Half the AC distance; Step S33: Determine whether the track address B is within the reference circle: if B is outside the reference circle, the track address of the corresponding address combination is determined to be abnormal; if B is within the reference circle, the track address of the corresponding address combination is determined to be normal; Step S4: Determine the abnormal track address based on the track combination, including: Step S41: If, in two adjacent address combinations, the track address of the first address combination is abnormal and the track address of the second address combination is normal, then it is determined that the first track address in the first address combination is abnormal; Step S42: If, in two adjacent address combinations, the track address of the former address combination is normal and the track address of the latter address combination is abnormal, then it is determined that the third track address in the latter address combination is abnormal.

2. The method according to claim 1, wherein When L BO When it is greater than 50 km, as L BO As the value of increases, the value of β shows a decreasing trend; and / or, when L BO When the distance is greater than 500 km, β takes a fixed value.

3. The method according to claim 1, wherein When judging whether the track address B is within the reference circle, compare the BO distance L BO and the reference circle radius R, if L BO If it is less than R, then B is judged to be inside the reference circle; otherwise, B is judged to be outside the reference circle.

4. The method according to claim 1, wherein Step S4 further includes: if, in two adjacent address combinations, the track address of the former address combination is normal and the track address of the latter address combination is abnormal, then determining that the third track address in the latter address combination is abnormal.

5. The method according to claim 1, wherein Before executing step S1, first determine whether the trajectory information corresponding to the trajectory address contains administrative level information: if it does not contain administrative level information, continue to execute the operations of steps S1-S4; if it contains administrative level information, and the administrative level information does not match the corresponding trajectory address, then determine that the corresponding trajectory address is abnormal; if it contains administrative level information, and the administrative level information and the corresponding trajectory address match, then continue to execute the operations of steps S1-S4.

6. The method according to claim 1, wherein When judging whether the track addresses of adjacent address combinations are abnormal, if the track addresses of the previous address combination and the next address combination in the two adjacent address combinations are both abnormal, then it is judged whether the confidence level of each track address in the previous address combination is greater than a preset value. If it is greater than the preset value, the corresponding track address is judged to be normal; if it is less than the preset value, the corresponding track address is judged to be abnormal. The confidence level is the ratio of the number of calibrations of the corresponding track address that is judged to be normal after calibration to the total number of calibrations of the corresponding track address.

7. A logistics track address calibration system, characterized in that: The system is used to execute the operating instructions contained in the logistics trajectory address calibration method described in any one of claims 1-6.

Images